X360Tools / PicoFlasher

GNU General Public License v3.0
361 stars 43 forks source link

"Console Not Found" #14

Open littlermac opened 2 years ago

littlermac commented 2 years ago

Hey there, I've used my Pico Flasher on two systems (a 4gb Corona and a Trinity), and it has worked great. But now, I am trying to use it for a third system (another 4gb Corona), and when I go to read the NAND in JRunner with Extras, I just get a "Console Not Found" error. I've tried this on another system (Another 4gb corona, the only other system I have around right now), and am getting the same error. It seems like another user here is having this issue as well but there seems to be no solution. I've checked my soldering several times as well as reflashed the pico a few times. Does anyone have any ideas as to what could be going on? Thanks!

nikdiklic commented 2 years ago

For 4GB Coronas, you have to follow the EMMC Flash soldering guide. Image

littlermac commented 2 years ago

Yes, this is how I have it wired. It has worked on another 4gb Corona in the past.

littlermac commented 2 years ago

Hit the wrong button, sorry.

ghost commented 2 years ago

Yup same issue here, PicoFlasher 3.0, my Pico only arrived today, I'd tested the soldering in my SD adaptor previously and it worked, was gonna leave this installed as a permanent nand reader for when I get the resistors I needed, but I legit can't do anything other than read "Console not found" with the Pico. I tested the wires with the SD adaptor again and it read absolutely fine, so im assuming its something to do with the Pico uf2 itself.

shooter556 commented 2 years ago

"Not found" could occur if you didn't operate in a proper sequence. Steps including: connecting wires from board to pico, connecting usb to computer, plug in the ac adapter to the board. Though I can't remember the proper sequence, but you can just try yourself to shuffle them to find a good one. Don't worry it would break anything if you try wrong. Just unplug all and try again.

ghost commented 2 years ago

"Not found" could occur if you didn't operate in a proper sequence. Steps including: connecting wires from board to pico, connecting usb to computer, plug in the ac adapter to the board. Though I can't remember the proper sequence, but you can just try yourself to shuffle them to find a good one. Don't worry it would break anything if you try wrong. Just unplug all and try again.

I spent 7 hours on this console yesterday, trust me I’ve tried every order possible.

littlermac commented 2 years ago

I, too, have used the suggested order as well as several others.

ghost commented 2 years ago

Spent another few hours working on the Corona I have this afternoon, checked continuity on pads which is fine, checked solder joints on Pico, all fine, resoldered the nand points, checked for continuity afterwards which is normal, tried several connection methods to get console to read, each time no console found. The same wires work fine in an SD Adaptor, I just don't wanna have to constantly use the SD card if I can leave the Pico in, but this is too much trouble.

EDIT: Just wired it up to my Trinity RGH which I know is fine, got one dump before it stopped reading the console, reflashing the uf2 had it detected for a single read before it went off again, so something is off, but i'm just gonna invest in a 4gb r/w clone kit

AcidzDev commented 1 year ago

Having the same issue with my picoflasher

Latest version of J-runner from Octal, Latest version of Picoflasher

2 Coronas both with Console not found. Verified RC2010 is present. Tried multiple usb cables, another pc. reflashed pico. Did the steps listed on Weekend modders site.

I know my pico will do a 4GB corona as i have used it for one a few months ago, did a trinity with it a week before this issue on the coronas. Both consoles to boot to the dashboard.

Not sure to what may be the issue, the only thing i have noticed is when I click the ? icon to identify the console J-runner freezes and gets a .NET error for operation time out. If i quit and try to reopen J-runner it takes about 5 mines to reopen it.

I will try to get the error log from J-runner as soon as i can.

Seroczynski commented 1 year ago

I have the same problem. Tested all connections, re-flashed Pico, ran flasher tool as admin. Still getting "Console Not Found" on my Corona 4GB.

Confirmed R2C10 is populated. Tried several methods of order in which to connect and power devices.

pablocool commented 1 year ago

Same here. I have successfully flashed Corona v2 4GB few months ago. Now I am trying another and still "Console Not Found". Console boots to dash successfully and R2C10 is populated.

pablocool commented 1 year ago

Now I noticed that problematic console has PHISON controller but no POST_OUT. So is it v2 or v4? I thought v4 has NAND in front of MOBO and v4 PHISION + NAND on the back.

skeyvin commented 1 year ago

Looks like everyone is stuck at this point. We need some help getting around this

pacman362 commented 12 months ago

I have 3 picos here all lasted 1-2 uses then do the no consul found ? would be nice to suss this out.

pacman362 commented 11 months ago

Hey there, I've used my Pico Flasher on two systems (a 4gb Corona and a Trinity), and it has worked great. But now, I am trying to use it for a third system (another 4gb Corona), and when I go to read the NAND in JRunner with Extras, I just get a "Console Not Found" error. I've tried this on another system (Another 4gb corona, the only other system I have around right now), and am getting the same error. It seems like another user here is having this issue as well but there seems to be no solution. I've checked my soldering several times as well as reflashed the pico a few times. Does anyone have any ideas as to what could be going on? Thanks!

Ok Update, fitted both my suspected FAKE Pico's with GENUINE RP2040's And im pleased to report they both work perfectly ! So in conclusion I suspect that the chips where indeed FAKE ! So all of you out there with dead Pico's Order yourselfs some new RP2040's and get reworking to bring them back from the dead for your RGH work.