Need help fast....stock galaxy nexus image available?

I remember doing this a while back. I have to download the SDK, do adb commands or something like that? We're going straight Linux here correct? I'll look for that route

We can do anything. I'm on Linux right now so if you can set it up I can tell you what to do.

If you're on Windows, download Wug's Toolkit or the GNex Toolkit. Then choose the "take it back to stock" option (or whatever the analogue is).
 
We can do anything. I'm on Linux right now so if you can set it up I can tell you what to do.

If you're on Windows, download Wug's Toolkit or the GNex Toolkit. Then choose the "take it back to stock" option (or whatever the analogue is).

Thanks. I think i got it to work. I put the .tar in the "Phone" section and not in PDA and now it's flashing. Weird....

There is a blue bar loading on my Nexus, and I've so far flashed the lte radio. It is now on system.img, but it is taking FOREVER. I know it's only supposed to take like 3 minutes, but it's taking like an hour or longer. However, I'm seeing the blue bar showing progress, so I'll take it.
 
Thanks. I think i got it to work. I put the .tar in the "Phone" section and not in PDA and now it's flashing. Weird....

There is a blue bar loading on my Nexus, and I've so far flashed the lte radio. It is now on system.img, but it is taking FOREVER. I know it's only supposed to take like 3 minutes, but it's taking like an hour or longer. However, I'm seeing the blue bar showing progress, so I'll take it.

Yeah sometimes it's better just to let it breathe, ya know? Good luck and keep me/us posted!
 
Yea it didn't work. It went through and said successful, and now it's right back to the screen with the opened up android stuck in fastboot "no boot or recovery image". The good news is I can get to fastboot mode (without this message) by holding all the hardware buttons. Problem is that my internet is messed up, so I'm typing this from my phone. I have the Android SDK downloaded, but I think it needs to download more files still through the SDK, correct?

Ugh...at least it powers on so I have some hope...
 
Yea it didn't work. It went through and said successful, and now it's right back to the screen with the opened up android stuck in fastboot "no boot or recovery image". The good news is I can get to fastboot mode (without this message) by holding all the hardware buttons. Problem is that my internet is messed up, so I'm typing this from my phone. I have the Android SDK downloaded, but I think it needs to download more files still through the SDK, correct?

Ugh...at least it powers on so I have some hope...

Yes you need the fastboot binary. Wugs is simple because it does all of that for ya and you can use it to fastboot.

Sent from Oliver, my Nuclear-Powered, Orb-Shaped Candy Device.
 
Man idk what is going on with AT&T, but it looks like my internet is down for the night. Also, is it possible that my NAND is damaged (since he accidentally flashed the Verizon radio)? Looks like I may have to sell this thing. At least the ESN is clean lol.
 
Man idk what is going on with AT&T, but it looks like my internet is down for the night. Also, is it possible that my NAND is damaged (since he accidentally flashed the Verizon radio)? Looks like I may have to sell this thing. At least the ESN is clean lol.

Honestly I have no idea. You will know if you can't fastboot a thing though. Use that first link I gave you then follow my guide in the Verizon forum for stock images. Just substitute the names...
 
well I've bricked it.

From what I've read, I have NAND rw corruption. When I try to unlock my bootloader, it jsut reboots and keeps rebooting (not even turning on, the computer just makes a noise like it's trying to read it) and even comes back to recovery menu.
 
got it working somehow and am now booting into Jelly Bean.

I flashed the original Sprint ROM and am moving right along now lol.

I think the problem was the battery didn't have enough juice to run the device through the booting, hence causing constant reboots and not being able to power on. However, idk about the bootloader staying locked and not unlocking, so I do believe I had a soft brick. Keep messing with Odin and flashed the F02 radio only and that did something to it. It came back on and it said the bootloader was unlocked at the bottom. I saw that and start fastboot flashing away lol...

After that I still had problems in fastboot, and that's when i started to let it charge for a while and that got it going...
 
got it working somehow and am now booting into Jelly Bean.

I flashed the original Sprint ROM and am moving right along now lol.

I think the problem was the battery didn't have enough juice to run the device through the booting, hence causing constant reboots and not being able to power on. However, idk about the bootloader staying locked and not unlocking, so I do believe I had a soft brick. Keep messing with Odin and flashed the F02 radio only and that did something to it. It came back on and it said the bootloader was unlocked at the bottom. I saw that and start fastboot flashing away lol...

After that I still had problems in fastboot, and that's when i started to let it charge for a while and that got it going...

Good to hear; let us know if you have any problems :)
 

Trending Posts

Members online

Forum statistics

Threads
956,411
Messages
6,968,099
Members
3,163,538
Latest member
boone