Related
Hi
I'm just absolutely confused with all the topics as every single one have different method .
I had my gnex replaced but it came with stock rom without volume bug fix. Been waiting for about half a week for an update but no updates. I've decided to root and flash 4.0.2 but I might need to return the phone again. Before I do so I want to revert to stock (everything) just to check if my phone will get any updates.
Could someone write small tutorial how to flash back from stock image. Ideally via adb or guide me to the right topic. And it has to be for image for the icl43d (or whatever the image number without volume bug fix)
Thanks in advance
EDIT:
Downloaded 7zip and now i can see all the files (bootloader etc.. ) i can manage on my own now
Ok I'm fine now. Didnt notice that image was compressed in
Sent from my Galaxy Nexus using xda premium
Update (5/2/2012):
I think I've isolated the issue as a broken recovery image. It appears that some of us received a broken 4.0.2 OTA and are now suffering for it.
This issue can be completely fixed by manually installing the 4.0.4 update. For reasons stated in my post below (message #9 in this thread), I do not think this issue can be fixed with an OTA update, so don't wait for Google to fix this. Fix it yourself or send it back for a refund.
----
Title says it all.
I have a completely stock GSM Nexus running 4.0.2, YAKJU build. Several times, I have received the notification that the 4.0.4 OTA update is available. Each time when I try to take the update, the phone reboots and gets stuck at the "Google" screen indefinitely.
At this point, the only way to shut the phone off is to remove the battery.
Has anyone else had this problem? I can't believe Google is unable to deliver a working update to a stock phone, especially after the months of delay this has been. (My phone is nearly unusable on 4.0.2 due to the keyboard lag, random reboots and other issues.)
I really don't want to mess with the bootloader due to warranty issues.
Same thing is happening here. Completely stock on 4.02, receive notification for 4.04, downloads, reboots to install, doesn't get past "Google". Not sure what's going on there...
Same here, tried twice now. Left it for about an hour and it went through a stage of the back of the phone getting warm (antenna location, I believe... at the top by the camera) then cooled down later. I thought maybe it was downloading the update? Not sure if it normally downloads before or after the reboot.
Additional info:
Mine's wasn't originally yakju, but I flashed to yakju 4.0.1 from yakjuux (or whatever) when I got it months ago, and was able to get the 4.0.2 update OTA just fine.
Mine was yakju out of the box, so I don't think it's a flashing issue.
Yep, mine too. YAKJU out of the box. I haven't done anything to mod this phone.
I'm going to try to manually update it in the next day or two and share results
No factory reset either
Huh. I thought maybe doing a factory reset from the Settings menu would help. In fact, I can't do that either!
After clicking through all of the confirmation dialogs, the phone reboots and.... get stuck at the Google screen. I have to pull the battery out, just as when applying the 4.0.4 update. Luckily the phone will start up again, but the wipe never happened.
It looks like there's a problem with some Galaxy Nexuses being able to go into recovery, perhaps?
Hi All
I got the exact same problem. Out-of-the-box, no mods, no root, 4.0.2. Got the OTA to 4.0.4 the third time this morning. Still can't pass the "Google" screen.
Solved -- sort of.
Hey all,
I spent some time investigating this issue. Here's what I've determined: for those of us affected with this problem, it appears that we somehow received a botched installation of 4.0.2 (the version we're running currently). What's the botch? Our phones don't have a working recovery image.
You can test this by trying to enter recovery. Turn off your phone. Then, simultaneously press and hold volume-UP, volume-DOWN, and POWER until a screen with an Android on his back appears. This is the fastboot screen. From here, you can choose 'Recovery'. If your phone is like mine, any attempt to go to Recovery will just put you in the dreaded Google logo loop.
So, what's the solution? I'm afraid the only way to resolve this yourself is to unlock the bootloader and do a complete install of the 4.0.4 image yourself. One step of that process is to flash an updated recovery image; this will cure the issue. Fortunately, on the Galaxy Nexus, you can easily re-lock the bootloader with a single command. I have done all of this and can confirm that it works.
If you're not comfortable unlocking the bootloader, the only other way to fix this is to send it back to the vendor. I have a strong suspicion that phones affected by this bug are unable to receive any further OTAs at all. This means Google can't fix your phone by pushing out a different OTA.
Final warning: until this is fixed, you can't do a factory reset, either -- that process will fail because it, too, uses the recovery. So don't plan on selling your phone on eBay until you get this fixed.
Your research is much appreciated modenastradale. It seems this is a fairly big **** up on Google's part. But I guess these things happen. I don't have any particular problems with unlocking the bootloader, I just didn't feel like wiping the phone right now and having to reinstall and set everything back up again which is why I've remained stock this whole time.
Unlike previous phones, this one has felt great out of the box, so I've never had the need to root it to get more performance out of it.
I guess this will be the project for the weekend. Yay!
Looks like a good opportunity for me to switch to the US version (takju).. even though it's 99.9% the same right now. Just in case they give us a better radio for the region.
Idea:
What if I flash the recovery only? (like step D.12 here: http://forum.xda-developers.com/showthread.php?t=1626895)
I already have an unlocked bootloader, so it looks like I wouldn't need to wipe the system to unlock it. I guess I would get the 4.0.2 full image and flash that recovery (not the 4.0.4), though I'm not sure it would made a difference anyway.
I might try it out, but still interested in maybe switching to Takju anyway. I thought about anything that I'd lose by wiping, and since almost everything is on google's cloud (gmail, google music, coctacts, pics on google+, etc) it's not a big deal to wipe.
Fixed
The method I suggested in the last post worked!
You need to be able to flash a recovery image though, which I think would mean you need an unlocked bootloader? The benefit of doing this over just flashing the complete 4.0.4 image is that you don't need to wipe the phone (assuming you already were unlocked)
In more detail, here are the steps I took.
- Preparation (I already had this done) - have Samsung drivers installed on your PC, ADB, fastboot, etc. - check other threads for how to, such as: LINK
- Follow this post's how-to for flashing the recovery image - the poster also has the stock 4.0.2 link, which I can't find on google's site anymore: LINK
- The only command I ended up using is
Code:
fastboot-windows.exe flash recovery F:\recovery.img
Where F:\ was the location I extracted the image file to.
- Restart via:
Code:
fastboot reboot
- When it restarted, it gave me the OTA notification and was able to install fine.
I don't know if the OTA notification would automatically show for everyone, if not you can try to check for updates in the settings or try some of the step on the thread: LINK
related issue
I found and issue on code.google.com that seems related to this.
I'm linking them in the hopes of getting some official response about this.
Just search for number 29954 on code.google.com as I'm not allowed to post links here yet.
This worked perfectly for me. Glad to have that done with. Didn't lose any data at all.
I have this issue also. Stock Galaxy Nexus from the Spain, no mods, not unlocked.
Its necesary unlock bootloader to flash a recovery image
I can reboot my Nexus after going through the install of 4.0.4 (my phone don't get stuck at the Google logo), but the version stays at 4.0.2 however.
Do I also have to unlock bootloader and flash 4.0.4 etc. or is there another way to work around the update problem?
Stock and unlocked Galaxy Nexus bought (and in use) in The Netherlands.
Thanks!
Hi,
New to this site and sorry if this is already discussed but:
I just recently got the official OTA notification for Jelly Bean for my GSM unlocked Galaxy Nexus, but here's the problem.
I bought the phone with yajkuxw 4.0.1 build on it (the one from Samsung) and flashed yakju 4.0.4 onto it. The bootloader is unlocked and it is rooted. There is not altered files on it (other than boot.img). So when I download and try to apply the 4.1 update, the phone restarts, starts the process and then freezes on the image of a little android man with his chest open with a red exclamation mark. I have re downloaded many times but no luck.
So far, I have unrooted and re-flashed the stock recovery.img on it and completely reinstalled the 4.0.4 build with nothing else on it...no luck. I locked and unlocked the bootloader and unrooted and rooted it a few times, still no luck. I have ToolKit v1.5.1 and all drivers, just a stupid problem. So everything I do, nothing works. I was hoping someone had an official untouched 4.0.1 build so I can install 4.1 directly from that that, OTA.
Please I do not want to flash 4.1 directly onto it, I wanna fix this problem so I can receive all future updates OTA!
Anyone else have this problem? Can anyone please help?
Cheers
Better to find answers from others threads, this is maybe last time when I answer to the same questions!
Download IMM76I "takju" Google Factory Image!
when it's downloaded you have to use 7-zip, winrar, or something like that to open it in Windows!
download this one: http://downloadandroidrom.com/file/GalaxyNexus/rooting/GalaxyNexusRootNew.zip
add the GalaxyNexusRootNew folder to
C:\
open the factory image file and copy files to the Galaxynexusrootnew folder and if factory image file has .zip file then open it and move the files from it to galaxynexusrootnew folder too
Download OTA update from JRN84D to JRO03C. add to galaxy nexus too.
Now boot you Nexus fastboot mode:
flash files by using fastboot flash, etc..
use these commands: http://forum.xda-developers.com/showthread.php?t=1625700 but you have to edit the file names to flash them..
then boot it when all is done and download jb-takju.zip, when it's downloaded move it to galaxy nexus and then from Galaxynexusroot folder you have to move the root bla bla bla.zip file to ROOT!
go to fastboot mode and type this one: fastboot flash recovery optimus_prime-touch-v5.5.0.4-6-GSM.img
Download radio XXLF1 flashable for fastboot and flash it via fastboot to Galaxy nexus: fastboot flash radio bla bla bla.img
now boot to rcovery mode and wipe dalvik cahce, wipe cache and now flash jb-takju.zip and then in CWM wipe factory/data flash again jb-takju.zip and now flash OTA update and reboot.. and now when those are done reboot and when it's done go to fastboot mode and flash bootloader JB's own bootloader..
I wrote this quickly because I don't have time so I hope you understood that how to do..
Here is the JB-takju.zip JRN84D for CWM http://download.clockworkmod.com/test/jb-takju.zip
FIXED!
Hey, just wanted to say the fix to the problem is to flash EVERY partition for your current version onto your Nexus (radio, bootloader, boot, system, userdata etc.). From there, the OTA works.
Cheers
Flash every partition
DanDaGamer said:
Hey, just wanted to say the fix to the problem is to flash EVERY partition for your current version onto your Nexus (radio, bootloader, boot, system, userdata etc.). From there, the OTA works.
Cheers
Click to expand...
Click to collapse
My problem is identical to yours... right down to starting with 4.0.1. I am hoping your fix of flashing every partition works for me as well.
Question: how do you flash every partition? I am asking because I thought I already did this when I initially moved to 4.0.4. However, you obviously did the same thing I did, so I am also hoping you know the reason I am asking
Looking forward to your reply
Andrew
Same
Andrew Field said:
My problem is identical to yours... right down to starting with 4.0.1. I am hoping your fix of flashing every partition works for me as well.
Question: how do you flash every partition? I am asking because I thought I already did this when I initially moved to 4.0.4. However, you obviously did the same thing I did, so I am also hoping you know the reason I am asking
Looking forward to your reply
Andrew
Click to expand...
Click to collapse
Would love to know as well Dan
Moby
Fixed
I was finally able to get Jelly Bean 4.1.1 Build number JRO03C
Here is what I did:
- Backed up my Android data
- Followed the instructions on http://forum.xda-developers.com/showthread.php?t=1626895
- The above completely "reformatted" my Android (so I lost all my data)
- Did not restore my applications... yet
- Turned off my phone's data connection, and only had WiFi.
- In "Settings"
- Selected the "About Phone" option
- Selected the "System Updates" option
- Clicked the "Check now" button
Finally the OTA update arrived and actually worked this time
Thanks
Andrew Field said:
I was finally able to get Jelly Bean 4.1.1 Build number JRO03C
Here is what I did:
- Backed up my Android data
- Followed the instructions on http://forum.xda-developers.com/showthread.php?t=1626895
- The above completely "reformatted" my Android (so I lost all my data)
- Did not restore my applications... yet
- Turned off my phone's data connection, and only had WiFi.
- In "Settings"
- Selected the "About Phone" option
- Selected the "System Updates" option
- Clicked the "Check now" button
Finally the OTA update arrived and actually worked this time
Click to expand...
Click to collapse
Thanks for that
Pink Tint after Jelly Bean update
I upgraded the phone to Jelly bean yesterday and weirdly this pinkish tint has started to appear which is slowly expanding. Is there anyway to stop it or fix it? Have attached the image.
Pink Tint after Jelly Bean update
I upgraded the phone to Jelly bean yesterday and weirdly this pinkish tint has started to appear which is slowly expanding. Is there anyway to stop it or fix it? Have attached the image.
Jellybean update freezes on the ASUS screen with the circling dots
The issue I'm facing is also an unsuccessful JB update, but a bit different.
I use an ASUS Infinity TF700T. I downloaded the Jellybean update this morning, and it went through the installation process, applying updates and recognizing apps. Then it rebooted as expected, but doesn't get past the ASUS splash screen with circle of dots. It sits there for over an hour.
I tried to hard reboot it a few times, and it still doesn't boot up. It gets as far as the circling dots and stays there.
When I plug it into my computer with USB, it's not visible to the computer.
My system is encrypted, and was working fine before the update. I haven't had any significant system problems before the update. I haven't noticed any encryption related problems (the encrypted login screen is still the same and takes the password, and then continues to try to boot, but doesn't complete the bootup.)
What are my options? Is a factory reset needed, as Andrew Field did?
FYI, My new ASUS infinity is not rooted.
Phuljum said:
The issue I'm facing is also an unsuccessful JB update, but a bit different.
I use an ASUS Infinity TF700T. I downloaded the Jellybean update this morning, and it went through the installation process, applying updates and recognizing apps. Then it rebooted as expected, but doesn't get past the ASUS splash screen with circle of dots. It sits there for over an hour.
I tried to hard reboot it a few times, and it still doesn't boot up. It gets as far as the circling dots and stays there.
When I plug it into my computer with USB, it's not visible to the computer.
My system is encrypted, and was working fine before the update. I haven't had any significant system problems before the update. I haven't noticed any encryption related problems (the encrypted login screen is still the same and takes the password, and then continues to try to boot, but doesn't complete the bootup.)
What are my options? Is a factory reset needed, as Andrew Field did?
FYI, My new ASUS infinity is not rooted.
Click to expand...
Click to collapse
Maybe you should ask in the ASUS forum...
Hi guys,
I have a problem upgrading my nexus to the latest 4.1.2 update.
My device found an update, downloaded it and rebooted to CWR.
It's starting to install and then I get error status 7. Installation failed.
I also tried to donload the update manually but same results.
My devices is rooted with an open bootloader.
TAKJU.
I've tried to seach the forum/stickies but couldn't find a solution.
can anyone please advise?
Thanks in advanced,
Do you have modified system files? Like did you modify your build.prop?
Having the su and superuser.apk does not matter, OTA will still go through.
Most likely because OP altered something within the /system/ or is using another radio other than the one supplied from OTA.
This is why I always say if you're going to root, don't "half-a.." it. Go for the whole thing. Rooting is a gateway drug to flashing
I did not modify system files etc..at least not on purpose..
zephiK - I'm not sure what you meant there. I don't remember how I rooted, but do you think the root was corrupted?
Can you help me fix this somehow?
I don't care to wipe if needed.
thanks!
Got the same situation as you, the update won't proceed as it can't pass the check to ensure the rom in your Nexus is the one valid for update. Search the thread and web, and the message that follow the error 7 code hint you what's the thing that's not match.
You scenario should not be the same as mine since everyone of us mess with our own Nexus in our liking. But I'll share my case to see if it get's you some insight.
First OTA and manual flash won't work, stop almost immediately as shown by the CWM progress bar. I saw the screen said something about system/calculator - Then I remember that I have use TB to backup and uninstall the stock calculator, image, and email.
Restore those 3 using TB, and try again.
This time, the progress bar moves, and it actually check and stop halfway in between before showing the Status 7 msg.
Then do some web search, someone said about the radio version, and I got bad battery drain anyway, so flashed the radio version, restart and reflash again.
This time progress a little bit longer, and still no dice. Status 7 msg says something about system/build.prop
Check my system folder on the Nexus, and find build.prop.bak, then remember I have messed around with build.prop before, trying to change the device name shown on the DHCP table on wifi routers.
Revert the change. Try flash again, and viola, it work. And now got my 4.1.2 running nice and smooth.
So pay an attention at what the string said in the status 7 msg, and you know why it won't start the update.
Hey, you mentioned you have a unlocked bootloader.
If you still can boot into android, download TitaniumBackup and backup all user apps and data, then pull the TitaniumBackup folder to your computer.
Then use fastboot to flash 4.1.2 image from Google.
Then finally use Titanium Backup to restore your stuff.
28907126 - Thanks for the info! It might help to others. I really didn't play with radio or system files.
Mach3.2 - Can you please direct me to a guide on how to flash the image?
Thanks for the help everyone.
naorca said:
Mach3.2 - Can you please direct me to a guide on how to flash the image?
Click to expand...
Click to collapse
There's a sticky at the top of this forum.
My phone prompted me to update to 4.1.2. Everytime I press install, it would boot and then stops half way with a red triangle icon. A few minutes later it will boot to 4.1.1. Someone suggested that it may be due to build.prop file. I mucked around with the build.prop trying to get google wallet to work. I don't care about the wallet anymore. All I want is to upgrade to 4.1.2 with no data loss.
Someone on this forum suggested using the GNex TOOLKIT V9.1 to flash Google Stock Image to phone and then the OTA update would work. If I do that, will I lost any data on the phone?
Sorry, NB to android. Thanks.
you messed with system files, the OTA will not install because of that.
you need to replace the files you modified with the original build.prop and any other files that you modified
if you want to go to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Ahh ... it took me a while to get my gnex configured to the way I want. That method sounds like a clean method but at the same time will wipes everything I have configured so far.
I should probably create a second thread to ask a different question, is there a way to disable the 4.1.2 OTA notification nag? I will keep this phone for another month or so before I pass it to someone else.
If you don't care about any changes you've made to the system partition, you can just flash the boot and system images. This will keep your data.
I upgraded this way before the official OTA was out. It will, of course, blow any changes you've made to /system away, but it will keep your user data and all your settings, etc. You normally don't upgrade by "dirty flashing" over top of another system, but nobody I've seen has reported any issues with going from stock 4.1 to stock 4.1.2 this way. I did it, and have had zero issues. Always take a nandroid backup if possible, just in case.
Follow efrant's guide, just only flash boot and system (and NOT userdata)