Related
I was on the latest codename and everything was working fine, but wanted to see how 4.0.4 was running as is. I downloaded the stock AOSP build that was flashable by nikademus, downloaded gapps/root files as well. Followed instructions so far so good. Booted up and noticed that the ICS animation was gone and was replaced by just the "android" with the lighting going through it animation. Didn't really care about that so i let the phone do its thing, once it was done and i completed the account setup i rebooted like i normally do when flashing roms. when the phone came back I went into the settings to verify i was on the current version. I noticed that it said 4.0.4 0 4.0.4, thought that was odd and then something else that was odd was that my market was completely blacked out and the only way to see anything was the select something and then it would become visable. By then I knew something was wrong so i tried to boot into recovery via rom manager but it would not do anything. I tried to flash a custom recovery image again and it didnt let me because of su commands ? or something like that. At this point im freaking out because I have no SU permissions apparently, no CWM recovery, and the rom that im using is clearly messed up(not saying its the rom, it was probably something i did wrong) so i tried to use the galaxy nexus root toolkit program by WugFresh. I was going to try to go back to stock+unroot and then root after. I downloaded 4.0.2 and followed the command prompts and everything seemed to be working fine but when the phone was supposedly booting up it just got stuck on the Google screen with the unlocked padlock for a long time. I didnt see no boot animation or anything for about 10 min.
So I have no clue how to recover from this =(
Is my phone a paper weight now ? or can it be fixed ?
someone help me please lol
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
but i cant even get adb to see my device?
in order for me to use fastboot dont i need adb setup ?
I had adb setup but after this issue i cant go no further then the google screen
Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
^^^ what he said.
I have yet to see a bricked Galaxy Nexus.
Sent from the future.
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
AnthonyAldrete said:
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
Click to expand...
Click to collapse
Yes you're completely stock.
No more wugs for you sir.
You need to learn how to do this manually.
Check my sig.
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
halifaxjesse said:
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
10 chars.
...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
Ok guys i just got the Galaxy Nexus and im wanting to root it. But it came with the IMM76Q build. Everything im finding is for IMM76K. Is there a way to root it or am i stuck with a non rooted phone for now. It is the verizon one, any help would be nice
You have a galaxy nexus you are not stuck without root. However I am not sure about the tool box programs and your newer version. I believe you should still be able to use adb to unlock your boot loader and you should still be able to go into your recovery and flash a custom ROM with root or just flash the super user zip and that will give you root. Here is the super user zip if you need it. http://db.tt/GzpXFmUz
I used this zip to root my phone before. If you are not sure how to use adb or send commands manually you tube has some great videos to help.
In the toolkit you simply choose option 14 the one ending in "k". Its the same as the Q version with just a search bogus feature. Read the last page on that thread and the author tells you to use K. I just did it on two phones. Works perfect!
Which toolkit I could never get the gnex one to download. I know there's the other one 1.5 toolkit
Sent from my Galaxy Nexus using xda app-developers app
iceshark said:
In the toolkit you simply choose option 14 the one ending in "k". Its the same as the Q version with just a search bogus feature. Read the last page on that thread and the author tells you to use K. I just did it on two phones. Works perfect!
Click to expand...
Click to collapse
Worked for me as well. Used the toolkit.
Sent from my Galaxy Nexus using xda app-developers app
whitetiger2429 said:
Which toolkit I could never get the gnex one to download. I know there's the other one 1.5 toolkit
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
dont be lazy
http://forum.xda-developers.com/showthread.php?t=1529058
i for one will not help you if the toolkit for whatever reason fails.
currently using nexus toolkit 7.7 trying to relock my bootloader on imm76q and it isn't working. used the option for the 4.0.4 (imm76k)
ticholas said:
currently using nexus toolkit 7.7 trying to relock my bootloader on imm76q and it isn't working. used the option for the 4.0.4 (imm76k)
Click to expand...
Click to collapse
Use the back to stock tool.
Sent from my Galaxy Nexus using xda app-developers app
thanks, that should have been self explanatory.
Zepius said:
dont be lazy
http://forum.xda-developers.com/showthread.php?t=1529058
i for one will not help you if the toolkit for whatever reason fails.
Click to expand...
Click to collapse
Seriously, it's like, three commands.
Sent from my Galaxy Nexus using XDA Premium via Verizon Wireless
I had the same build on my last refurbished (aka like new) verizon phone that was sent out to me. I ran into problems using tool kit. It would hang in a bootloop after pushing SU installed with the tool kit. I basically downloaded the IMM76K factory image from Google Nexus page. Wiped the phone and did it the old fashion way via terminal or in windows cmd .
adb reboot bootloader
placed the latest SU in main folder of phone (aka root folder)
adb reboot bootloader
fastboot flash recovery recovery--and your version of clockwork
press the volume to recovery and press the power button
flashed zip..choose zip
reboot the phone
opened Rom Manager
flashed latest version of ClockworkMod for my phone.
But that's more than 3 steps.
paternal_techie said:
I had the same build on my last refurbished (aka like new) verizon phone that was sent out to me. I ran into problems using tool kit. It would hang in a bootloop after pushing SU installed with the tool kit. I basically downloaded the IMM76K factory image from Google Nexus page. Wiped the phone and did it the old fashion way via terminal or in windows cmd .
adb reboot bootloader
placed the latest SU in main folder of phone (aka root folder)
adb reboot bootloader
fastboot flash recovery recovery--and your version of clockwork
press the volume to recovery and press the power button
flashed zip..choose zip
reboot the phone
opened Rom Manager
flashed latest version of ClockworkMod for my phone.
But that's more than 3 steps.
Click to expand...
Click to collapse
That's interesting. I had no problems. Maybe you had an older toolkit version? I rooted mine on Tuesday.
Sent from my Galaxy Nexus using xda app-developers app
I'm gonna throw my ? In here since I'm totally unfamiliar with Samsung and nexus devices.
I bought my mom a gnex (sprint variant) for mothers day. I rooted it using fastboot and adb and put TWRP on it. My ? is, do I need to restore factory recovery for her (somehow ?) to accept this OTA she says sprint is trying to push? Its only 26mb, dunno what it is.
It's hard to find info in the nexus forums, just the way it's setup, and I say that as a 3yr xda addict.
Sent from my EVO using xda premium
whitetiger2429 said:
Ok guys i just got the Galaxy Nexus and im wanting to root it. But it came with the IMM76Q build. Everything im finding is for IMM76K. Is there a way to root it or am i stuck with a non rooted phone for now. It is the verizon one, any help would be nice
Click to expand...
Click to collapse
So phones are shipping with imm76q huh? Oh boy
killerapl said:
That's interesting. I had no problems. Maybe you had an older toolkit version? I rooted mine on Tuesday.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I had the latest version of toolkit but it just kept boot looping so I said "efff it" and did it manually. Now I have no problems whatsoever.
whitetiger2429 said:
Ok guys i just got the Galaxy Nexus and im wanting to root it. But it came with the IMM76Q build. Everything im finding is for IMM76K. Is there a way to root it or am i stuck with a non rooted phone for now. It is the verizon one, any help would be nice
Click to expand...
Click to collapse
the wugfresh toolkit works if you want to root it. I was able to root mine successfully with the toolkit, but the replacement phone is garbage. Keeps dropping signal.
i have a slightly different issue, but it's related - so, i didn't want to start another thread...
i got a replacement device from Asurion, and it came with IMM76Q. i unlocked and rooted, but the device, itself, had some issues. so, i am returning it and getting another replacement device. i've asked them to send me a new one, so we'll see...
anyway, before returning it, i wanted to lock, unroot, and go back to stock. but, i haven't seen anything that would let me return it back to stock IMM76Q - only stock IMM76K. i'm wondering if there is a way to get it back to stock IMM76Q, in case Asurion wants to give me a rash of crap for returning to them a device that is locked, unrooted, but only on IMM76K...??
huskerkate said:
i have a slightly different issue, but it's related - so, i didn't want to start another thread...
i got a replacement device from Asurion, and it came with IMM76Q. i unlocked and rooted, but the device, itself, had some issues. so, i am returning it and getting another replacement device. i've asked them to send me a new one, so we'll see...
anyway, before returning it, i wanted to lock, unroot, and go back to stock. but, i haven't seen anything that would let me return it back to stock IMM76Q - only stock IMM76K. i'm wondering if there is a way to get it back to stock IMM76Q, in case Asurion wants to give me a rash of crap for returning to them a device that is locked, unrooted, but only on IMM76K...??
Click to expand...
Click to collapse
Flash the IMM76K, then update to IMM76Q using the info in the "Official OTA Update URLs" sticky in the General section.
I was using Ics on galaxy s3, I rooted the phone and it was working fine. Today I update from ICS to Official Jelly Bean 4.1. I then went ahead and use the S3 tool kit to root the phone, now when phone reboot I can hear the sound but all I can see is blank screen. I can go to download mode, CWM recovery and that is it. Any idea?
I have the original odin file that I can use to reinstall the ICS.
I want to install official JB and want to root that. Any help out ther will be appreciated.
hkhan1 said:
I was using Ics on galaxy s3, I rooted the phone and it was working fine. Today I update from ICS to Official Jelly Bean 4.1. I then went ahead and use the S3 tool kit to root the phone, now when phone reboot I can hear the sound but all I can see is blank screen. I can go to download mode, CWM recovery and that is it. Any idea?
I have the original odin file that I can use to reinstall the ICS.
I want to install official JB and want to root that. Any help out ther will be appreciated.
Click to expand...
Click to collapse
First get your phone out of boot loop, use one of the stock files posted in the dev section (use the JB one since that's what you want to be on). Then use Odin to flash a custom recovery, boot into the recovery and flash the team epic root zip. Go to qbking77.com for a how to vid on the root process and links for the files you need. Its very simple.
Sent from my SPH-L710 using xda app-developers app
I have already installed official JB successfully. Just need to root it now. Thanks for the help.
Sent from my SPH-L710 using xda premium
Is this for real??
http://www.sammobile.com/firmwares/3/?download=31062
Yes it is. KitKat is now available for the Canadian Note II and S III.
It is real! :victory:
Samsung Galaxy Note 2 and Galaxy S3 upgrade to KitKat now available to download
Now, the real question is : is the bootloader locked ?!
Waiting rooted stock ROM:fingers-crossed:
Telus made their available earlier today, and Bell's is out now.
On a side note, does anyone know how to get the update on a rooted device? I just rooted mine a few weeks ago. Still running stock ROM, but nothing I've tried seems to work.
radapex said:
On a side note, does anyone know how to get the update on a rooted device? I just rooted mine a few weeks ago. Still running stock ROM, but nothing I've tried seems to work.
Click to expand...
Click to collapse
Forget it, you won't be able to get it through official OTA.
Once you're rooted, your only way to update is to wait for someone to create a flashable zip of the update, flash the entire ROM by downloading from samfirmware or wait for a custom ROM.
HiKsFiles said:
Forget it, you won't be able to get it through official OTA.
Once you're rooted, your only way to update is to wait for someone to create a flashable zip of the update, flash the entire ROM by downloading from samfirmware or wait for a custom ROM.
Click to expand...
Click to collapse
Tried updating over KIES - what an ordeal. Had to run through emergency recovery twice but finally got it. I wasn't using root access for a great deal - basically lose out on Greenify automanaging and being able to revoke permissions. I can live with that for a while.
I hear towelroot for the s5 works with the kk update.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
radapex said:
Tried updating over KIES - what an ordeal. Had to run through emergency recovery twice but finally got it. I wasn't using root access for a great deal - basically lose out on Greenify automanaging and being able to revoke permissions. I can live with that for a while.
Click to expand...
Click to collapse
KIES doesn't want to recognise my device and Odin is... either stuck on flashing system.img.ext4 or taking really long... heh
EDIT: Changed USB port and Cable and it flashed properly...
Great News!
That's really a great news!!! Anyone planning to make a flashable zipfile for this rom without the bootloader and knox? I preserve 4.1.2 bootloader on my phone since 4.3 came out. So far, is this update good ?? i heard battery life not really good...
Thanks guys!
Has anyone tried installing the firmware using Mobile Odin and using the Everroot option?
I'm not really willing to try it for myself as this is my daily driver phone...
I wouldn't recommend this update. I updated this morning and everything seemed fine until I tried running Waze on the way home from work. My device was plugged into power as it usually is, but now on this new version my battery is actually discharging WHILE connected to power.
Now to look into rolling back. This is a deal breaker.
Edit: And for the record, this drain is confirmed on two different Galaxy S3's in our house.
Ymodem-G said:
I wouldn't recommend this update. I updated this morning and everything seemed fine until I tried running Waze on the way home from work. My device was plugged into power as it usually is, but now on this new version my battery is actually discharging WHILE connected to power.
Now to look into rolling back. This is a deal breaker.
Edit: And for the record, this drain is confirmed on two different Galaxy S3's in our house.
Click to expand...
Click to collapse
Dis you update via OTA or odin with data wipe?
Sent from my SGH-I747M using XDA Free mobile app
I just installed update. I was rooted running flashed stock 4.4.3 rom... I used Android Toolkit from skipsoft and it worked..
I tried different ODIN versions with no joy.. Using the Android Toolkit somehow when it loaded ODIN the flash to stock 4.4.3 worked...
UPDATE: I disabled AVG while using toolkit, i had not using odin orginally it may be related to my issu
Be careful using the toolkit. Its been known to brick devices and cause other problems as well.
Yay. Pretty much the same as using any method I suppose. Got lucky I guess.
Is this new bootloader is locked to prevent downgrading to another bootloader ???
Its not "locked" (meaning you can still flash custom recoveries and kernels), but I fully expect it'll be the same as before with regard to downgrading.
DocHoliday77 said:
Its not "locked" (meaning you can still flash custom recoveries and kernels), but I fully expect it'll be the same as before with regard to downgrading.
Click to expand...
Click to collapse
Ok. So downgrading from 4.4 bootloader to 4.3 should not work i guess??? . Another question, With 4.4 bootloader, is it possible to flash a 4.3 Rom ???
Correct. Provided its like 4.3, you can only flash the same or newer firmware.
I believe you should still be able to flash older roms like before, but have not seen this confirmed yet.