Develop Bugs

Got OTA notification but....

...I downloaded the 4.0.4 update and went to install and reboot. But the phone got stuck at the screen with the android belly up and a exclamation point. Pulled the battery and rebooted and was at 4.0.2 still. Haven't gotten another OTA notification. Do I get another OTA alert or do I have to update manually.
I have a GSM Nexus, rooted but with stock 4.0.2. And I activated OTA RootKeeper before downloading the update. Any help will be greatly accepted.
Sent from my Galaxy Nexus using Tapatalk

Besides root and maybe unlock your bootloader, did you change anything in your system (install mods, different radio etc. or rename system files)? If you are not completely stock your OTA will not work and you will have to update manually or get back to Stock first.
Sent from my Galaxy Nexus using xda premium

Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk

Well the screen you were looking at (Android belly up) is the stock recovery. If you see that: no need to pull battery. Simply push volume up + power simultaneously and you'll get into the recovery menu. Scrolling through the options can be done with the volume buttons, select with the power button.
That said: I think no one knows for sure but I myself would not wait and update myself. There are a lot of guides here on how to do that and if you flash the stock images you will have the same as anyone who had the OTA. Make a proper backup first (you allways should)! You will lose all your data if you have to unlock your bootloader.
Sent from my Galaxy Nexus using xda premium

jrodsep said:
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus

stuu.f said:
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Is it possible to get the Stock Recovery Screen when you have CWM installed? Didn't think that was possible... that it would just boot into CWM recovery. That is why I didn't mention it (trying to learn here).

Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?

Lex_Michdeandroid said:
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Click to expand...
Click to collapse
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents

Viridis Draco said:
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Click to expand...
Click to collapse
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA

Lex_Michdeandroid said:
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section

Viridis Draco said:
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Click to expand...
Click to collapse
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Edit: would it be easier if I just get the stock recovery back and then try to get the OTA to turn up again?
Sent from my Transformer TF101 using XDA

Lex_Michdeandroid said:
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/

Viridis Draco said:
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Click to expand...
Click to collapse
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA

Lex_Michdeandroid said:
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
i agree, take your time and you wouldn't regret it

I want to manually flash 4.0.4 and stay unrooted. Should I use the GNex Toolkit to flash 4.0.4 directly or do I need to flash the same version I have on my phone?
Sent from my Galaxy Nexus using Tapatalk

I had the same issue described by the OP, the belly up android when trying to update to 4.0.4 from the OTA notification. I had previously changed to 4.0.2 yakju using efrant's instructions from the first post in this thread: http://forum.xda-developers.com/showthread.php?t=1391881
However, I had skipped the optional sections. In particular step 12 to flash the recovery partition. I went back and just executed step 12 (fastboot flash recovery recovery.img) and rebooted. Then I was able to update to 4.0.4 successfully from the OTA notification.
I'm guessing I didn't have the "stock recovery" because I previously had the default Samsung version?

Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA

Lex_Michdeandroid said:
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I had the same issue just now with my phone (unlocked, rooted, stock revcovery), but a quick reboot allowed the update to complete and I'm now on 4.0.4. Did you check the version number again after this latest attempt?

Yes, still 4.0.2.
And of course, my phone says I'm up to date. Lovely, NAAAAAT!
Sent from my Galaxy Nexus using XDA

Bought a Rooted GNEX have a Question

ok I got a real good deal on a GNEX on CL and the guy said it wasn't rooted and smart me believed him. Well from what I can tell the bootloader is unlocked, and it is rooted because I ran root checker and it has superuser and wifi tether.It does not seem to have a custom rom on it The problem I see is that it seems to have stock recovery but when I go from the bootloader screen to recovery it reboots the phone most of the time after sitting on the image of the android guy with a red triangle over him. I plan on doing the JB OTA update when it comes out . At this state I am just not sure what I should do to make my phone not mess up in the long run. I was thinking unrooting and locking the bootloadder and re flashing stock recovery would be a good idea kind of starting from scratch. Please let me know what yall think and thanks for your time oh and I am on Sprint

Yeah just Odin back to stock you should be fine. Also you'll be waiting a long time for an OTA of jelly bean at least on sprint. We already have a port of the preview OTA that the gsm version got. Only thing doesnt work is MMS for obvious reasons.
Sent from my Galaxy Nexus using xda premium

does odin happen to work on a Mac? also is their a SDK kit for mac?

also has anyone ran into this situation where recovery dosent work? can I flash stock recovery back on without being able to get to any recovery to begin with?

kal7467 said:
also has anyone ran into this situation where recovery dosent work? can I flash stock recovery back on without being able to get to any recovery to begin with?
Click to expand...
Click to collapse
U can come back to stock recovery without any problem u can use gnex toolkit u ll be fine i guess , However JB rom available now are also awesome it works great without any problem ,except some apps yet to be updated for JB update

Stay away from toolkits. You can Fastboot flash the .img for the stock recovery boot and rom it self.
Sent from my Galaxy Nexus using xda premium

kal7467 said:
does odin happen to work on a Mac? also is their a SDK kit for mac?
Click to expand...
Click to collapse
No, Odin only works on windows.
There is no need for the SDK, all you need are the fastboot and adb files for Mac.
Look at the "flash" link in my signature. It has all the instructions on how to revert you device to stock. Mac-specific instructions are linked to a little further down.
Sent from my Galaxy Nexus using Tapatalk 2

how can i go back to stock from cyanogenmod 9 using gnex toolkit??

hi, i have a galaxy nexus with cyanogenmod 9 whick is android 4.0.4 (i did not flash it, it came with that rom) and i want to let the gnex in stock to get the jellybean update...
the thing is , i have seen a lot of guides but really it is too much, i was installing the drivers and then i saw the 100000 steps extra that i needed to do, and i just dont wanna do that lol... then i found the gnex toolkit (seems a lot easier) and there is an option to go back to stock, but i dont know if that works to go back from a rom like cyanogen or it just work for phones with stock roms that are rooted and with unlocked bootleader.

go ask in the toolkit thread since you are lazy.

You can use Wugfresh's toolkit to revert your GN to stock, and it will even give you the option to select which build you want, it would download it for you, follow the on screen instructions. You need unlock bootloader to flash stock, you can always lock it though.
Sent from my Galaxy Nexus using xda app-developers app

Savan Rajak said:
You can use Wugfresh's toolkit to revert your GN to stock, and it will even give you the option to select which build you want, it would download it for you, follow the on screen instructions. You need unlock bootloader to flash stock, you can always lock it though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
thanks for your answer, i'll download it.. i guess i have unlocked bootloader since this gnex is running cyanogen...
edit: thanks to that toolkit i was able to easily upgrade to jellybean without knowking much about this stuff.. thank you!! this thread can be closed now!!

[Request] Sprint 4.3 Stock ROM + Root

Hello everyone!
Im not sure if this post belongs in this thread, but I thought it would be best suited in the Sprint Galaxy Nexus thread.
Can someone please make a stock 4.3 rooted rom for the Sprint Galaxy Nexus? Or, if someone has already received the update, could you post a nand backup?
I want to update, but I dont want to lose root. However, If there isn't any other solution, I will definitely take the plunge
Sent from my Galaxy Nexus using Tapatalk 2

vincentallen2 said:
Hello everyone!
Im not sure if this post belongs in this thread, but I thought it would be best suited in the Sprint Galaxy Nexus thread.
Can someone please make a stock 4.3 rooted rom for the Sprint Galaxy Nexus? Or, if someone has already received the update, could you post a nand backup?
I want to update, but I dont want to lose root. However, If there isn't any other solution, I will definitely take the plunge
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.

tomh1979 said:
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.
Click to expand...
Click to collapse
Ive downloaded that yesterday, but just like QBKing said, itd probably be better to wait for a stock rooted option. I think it would be just less of a hassle than to go through all the motions of unrooting and updating.
Sent from my Galaxy Nexus using Tapatalk 2

tomh1979 said:
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.
Click to expand...
Click to collapse
when I updated from 4.1 to 4.2.1, I had CWM, and I got the ota, with it prompting me to keep root and disable recovery flash. I actually have the zip on my phone, I'm just scared of what will happen if I try to flash it. I don't have access to a PC, so there's no way to recover if I f*ck up.

mattchew86 said:
when I updated from 4.1 to 4.2.1, I had CWM, and I got the ota, with it prompting me to keep root and disable recovery flash. I actually have the zip on my phone, I'm just scared of what will happen if I try to flash it. I don't have access to a PC, so there's no way to recover if I f*ck up.
Click to expand...
Click to collapse
Nandroid backup just in case.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

tomh1979 said:
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.
Click to expand...
Click to collapse
If you're doubting the update don't, the OTA process involves sending the update 1 by 1 randomly so that everyone doesn't download the file at once and overload the download servers, causing bad downloads, and bricking devices and in the end you'll get unhappy customers.
Sent from my Galaxy Nexus using Tapatalk 4

Savoca said:
Nandroid backup just in case.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If he loses root or custom recovery how's he gonna restore ? I'm thinking of trying it as well . I've made a nandroid , just wondering if I'd be able to get it restored complete with root and custom recovery ? Thanks

Jimlarck said:
If you're doubting the update don't, the OTA process involves sending the update 1 by 1 randomly so that everyone doesn't download the file at once and overload the download servers, causing bad downloads, and bricking devices and in the end you'll get unhappy customers.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
I never said I was doubting, just surprised I haven't seen anyone saying they got it yet since it was supposed to start rolling out yesterday,
Sent from my Nexus 7 using Tapatalk 4

I actually flashed the 155 mb zip and rooted using nexus toolkit and all is well.
Sent from my Galaxy Nexus using xda app-developers app

Been running stock rooted all day today. I just used Odin to go back to 4.2.1 and used that zip Phandroid (I think it was them) renamed it update.zip put it in root of storage. Booted the phone and it said there was an update. Choose to reboot and it installed it. Then fastboot flashed twrp and flashed an su zip. Granted It wiped my phone but I just used helium to restore data on some of my apps and everything has been fine
Sent from my Galaxy Nexus using Tapatalk

MonstaDriva said:
If he loses root or custom recovery how's he gonna restore ? I'm thinking of trying it as well . I've made a nandroid , just wondering if I'd be able to get it restored complete with root and custom recovery ? Thanks
Click to expand...
Click to collapse
Tl;dr custom recovery stayed, root obtained by flashing supersu.
Last night I used fastboot to flash system user data radios and boot images from the 4.2.1 factory image. Flashed the 4.3 zip in twrp. Made a nandroid of stock, then flashed supersu zip. All is good
Sent from my Galaxy Nexus using Tapatalk

I tried flashing the zip in TWRP and it failed. Not sure why maybe a bad download.

Savoca said:
Nandroid backup just in case.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I went ahead and flashed it, in CWM, and everything is working great. Had to reflash Superuser, in this case, Koush's Superuser, and everything is fine.

mattchew86 said:
I went ahead and flashed it, in CWM, and everything is working great. Had to reflash Superuser, in this case, Koush's Superuser, and everything is fine.
Click to expand...
Click to collapse
I renamed the file update.zip and tried this, and no go, what am I doing wrong, could it be due to being on a 4.2.2 ROM?
Sent from my Nexus 7 using Tapatalk 4

I tried a fresh download using CWM this time and it still failed. What am I missing?
Sent from my Nexus 7 using XDA Premium 4 mobile app

tomh1979 said:
I renamed the file update.zip and tried this, and no go, what am I doing wrong, could it be due to being on a 4.2.2 ROM?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I went and restored a backup of Stock 4.2.1, and just flashed over that. No wiping or anything. Do you have a Stock backup?

mattchew86 said:
I went and restored a backup of Stock 4.2.1, and just flashed over that. No wiping or anything. Do you have a Stock backup?
Click to expand...
Click to collapse
Nope, any chance on flashing a stock rooted ROM perhaps.
Sent from my Nexus 7 using Tapatalk 4

tomh1979 said:
Nope, any chance on flashing a stock rooted ROM perhaps.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
You could try it. My Stock ROM was rooted, and I all I had to do was reflash my Superuser zip after I let it boot up once, just to make sure the update took properly.

http://forum.xda-developers.com/showthread.php?t=1419170
Download the file from the linked thread there for our device and then pick which instruction set applies to you from the second post in that thread. Since I'm leaving Sprint and giving my Gnex to my two year old, I unrooted, returned to stock, and locked the device. After following the directions for adb sideload, everything came up great.

X
Sent from my Galaxy Nexus using xda app-developers app

[Q] Huge Mistake!

I hope i didnt just turn my phone into a paper weight.
I was following through doing everying in order to root my phone and didnt realize one thing until it was too late.
when the phone restarted a "verizon 4glte" screen splashed on the phone and it stuck that way. The problem is my phone is from sprint. Is there any way I can get it back to normal? I really have no idea how I missed that.
I think i downloaded the correct tar file or whatever file i need for the stock sprint setup, but i keep getting an error when installing it through odin.
how can i go back to my stock SPRINT rom without having to wipe everything?
pleeeaaaase help. much appreciated.

Download twrp odin file to get that recovery then download any rom zip and flash
Sent from my SPH-L900 using XDA Premium 4 mobile app

Thankfully there's a fix. You'll need to bypass the activation screen to enable usb debugging quickly before the nag screen appears. When the nag screen appears you'll need to reset the device and start over (after the nag screen is shown once it'll come back quicker next times). Once usb debugging is enabled you need to unlock the bootloader and then you'll be able to flash the L900 firmware. This method may be a bit dated as I used it on 4.1.2 (on an R950 but the L900 will be the same.)
Sent from my SPH-L900 using xda app-developers app

i dropped the phone off at a cell phone shop to get it fixed and they couldnt figure it out.
i did a little digging and found this out. the file i installed to mess up the phone was this:
root66_VZW_stock_system.tar
so my phone is running a rooted verizon os, i didnt know that.
if it helps, it says im running build number i605vraljb and android version 4.1.1
so i have super user access and debugging is enabled, now what?
so i'm guessing bootloader is already unlocked?
honestly, anyone that gives me info that actually gets my phone working will not only get a thanks but $50 through paypal. im dead serious.

Derf9280 said:
i dropped the phone off at a cell phone shop to get it fixed and they couldnt figure it out.
i did a little digging and found this out. the file i installed to mess up the phone was this:
root66_VZW_stock_system.tar
so my phone is running a rooted verizon os, i didnt know that.
if it helps, it says im running build number i605vraljb and android version 4.1.1
so i have super user access and debugging is enabled, now what?
so i'm guessing bootloader is already unlocked?
honestly, anyone that gives me info that actually gets my phone working will not only get a thanks but $50 through paypal. im dead serious.
Click to expand...
Click to collapse
Power down your phone. Hold power home and vol down at the same time to get to download mode. Using Odin on PC flash the file found her http://forum.xda-developers.com/showthread.php?t=2591898. That's up to date stock for your phone. If you still want root Google "kingo root" and use that to root
Sent from my SPH-L900 using Tapatalk

EVER ONE RE READ THE OP. HE CANNOT JUST ODIN BACK TO A SPRINT ROM. THE BOOTLOADER IS A VZW ONE AND ITS LOCKED.
Now that's out the way...read up on Adam Outlers CASUAL bootloader unlock for the VZW note 2. Follow his process and after your bootloader is unlocked you'll be able to flash the appropriate L900 tarball.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!

ecs87 said:
EVER ONE RE READ THE OP. HE CANNOT JUST ODIN BACK TO A SPRINT ROM. THE BOOTLOADER IS A VZW ONE AND ITS LOCKED.
Now that's out the way...read up on Adam Outlers CASUAL bootloader unlock for the VZW note 2. Follow his process and after your bootloader is unlocked you'll be able to flash the appropriate L900 tarball.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
Click to expand...
Click to collapse
Why would a stock rooted rom relock the bootloader
Sent from my SPH-L900 using Tapatalk

DisposableHero1985 said:
Why would a stock rooted rom relock the bootloader
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Because you did more than install a rom. You installed bootloader, radio, firmware, and rom from Verizon.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Because you did more than install a rom. You installed bootloader, radio, firmware, and rom from Verizon.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
BINGO.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!

when i run casual it says "phone not rooted, root your phoen with any vraljb rom"
going to work on it some more tonight and see what happens.
for some reason every tar file i try to instal fails except for the
root66_VZW_stock_system.tar file.

Derf9280 said:
when i run casual it says "phone not rooted, root your phoen with any vraljb rom"
going to work on it some more tonight and see what happens.
for some reason every tar file i try to instal fails except for the
root66_VZW_stock_system.tar file.
Click to expand...
Click to collapse
you accidentally installed a Verizon rom. You however DID NOT install a Verizon bootloader. Odin would not allow it. Thank God casual failed otherwise you'd be hard bricked. Ensure you have a custom recovery. Then wipe and flash my mc2 zip from here and you'll be straight again.
http://forum.xda-developers.com/showthread.php?t=2086769

Are you sure? Someone brought in a soft bricked R950 (I know...different model but as long as it's not on 4.3 I doubt it'd matter for this situation) with ALL VZW firmware on it. Bootloader and all. I had to run CASUAL to unlock the bootloader to accept the R950 USCC firmware. Without CASUAL it kept failing in Odin (to preserve the VZW Note II firmware).
Guess I shouldve done more digging to see exactly what the OP did before pointing straight to a locked bootloader. I'm pretty sure that's the case though...I don't see any other reason for a MD5 tarball to fail. I don't think that particular VZW firmware build has secureboot.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!