Hello,
i have some Problems with my Galaxy Nexus. I still try to Upgrade my Android from 4.1.2 to 4.2.1 but it allways, if CWRM check the Hashes, occur an Error and stop the Upgrade (OTA). It says, that the Build.prop have wrong hashes (i think, it is the problem, because there was postet a lot of letters and digits, looks like a hash). I used once a little hack, to enable my Bootsound but i deleted it and the entries in the build.prop also. So, where is the problem? I hope you can help me
Greetings
DrTrax
Phone: Galaxy Nexus
Android: Stock Android 4.1.2 (JZO54K)
Kernel: Stock Kernel
Root: YES (Superuser)
Busybox: 1.20.2-cm9
you modified your build.prop. thats all it takes.
you need an original build.prop to get the OTA.
okay and how could i restore it (whitout reinstallation)?
i never did a Nandroid, i only did a normal backup with the Galaxy Nexus Toolkit
Grab the build.prop from JZO54K factory image and push it to /system.
sent from my Google Galaxy Nexus
Hmm, i can't unzip the System.img :/
7Zip, WinRAR, unyaffs, deamon tools and VirtualBox couldn't unzip/mount or open it
Linux also don't unzip it
Can someone post the build.prop of a Galaxy Nexus (Android 4.1.2 yakju)?
I grabbed a Build.prop from my Friend's Phone (The same Phone, same Android, just non-root) and still don't work. Maybe, i must force the Update but i don't know how and what will happen with my Data (Apps, Data, Music, Videos, ...)
You can't 'force' the update, if you've modified it somehow that's why it's not working and until you get it back to stock it will continue to not work. You're better off biting the bullet and flash the stock factory image to 4.2.1 and then set the phone up again (backup sd card first, tho)
Okay, i fixed it
Well, problem was not really the Build.prop (Why did it prompt, that there was something wrong with the build.prop?!)
Problem was, that many Google-Apps was deactivated ^^ After reactivating and updating these Apps, it finally works
*CLOSEREQUEST*
Related
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)
hey all, i just updated my nexus phone to 4.2 using the galaxy nexus toolkit (9 i think) and the full image tgz file foun don the google factory images site.
while my install was successful i noticed some errors on the toolkit window. I have attached a screen snip of part of the window.
the errors were that the toolkit couldn't find some of the files needed, as far as I can tell though everything is going fine and my phone is reinstalling all my stuff as I type this.
if this is a full image why are some parts not included in it?
my first attempt was to install the ota update manually using fastboot and cwm but the zip had errors (possibly missing content, or what content there was was messed up somehow) and I had to abort, luckily the phone wasnt screwed and I was able to resort to the full image to update my phone.
i didn't get a shot of the cwm screen when the ota error came up...
batkinson001 said:
hey all, i just updated my nexus phone to 4.2 using the galaxy nexus toolkit (9 i think) and the full image tgz file foun don the google factory images site.
while my install was successful i noticed some errors on the toolkit window. I have attached a screen snip of part of the window.
the errors were that the toolkit couldn't find some of the files needed, as far as I can tell though everything is going fine and my phone is reinstalling all my stuff as I type this.
if this is a full image why are some parts not included in it?
my first attempt was to install the ota update manually using fastboot and cwm but the zip had errors (possibly missing content, or what content there was was messed up somehow) and I had to abort, luckily the phone wasnt screwed and I was able to resort to the full image to update my phone.
i didn't get a shot of the cwm screen when the ota error came up...
Click to expand...
Click to collapse
i don't know about that tool;
if you use google's flash-all.sh, you'll also see that warning.
anyways, you really want to know? ask Google.
Hey everyone, I am trying to deodex the stock rom but I am having some issue. So far I have flashed the stock rom from SAMMOBILE, done a factory reset, and installed unikernal v9 beta (Reference 2). Boot up, everything is fine can setup the phone, root checks out, everything works, all is well in the neighborhood. The next step however is more troublesome because I am having some trouble finding good information.
I have downloaded all the files in the following folders to my system and deodex them (as per reference 1);
- system/app
- system/framwork
- system/priv-app
But when i flash them the phone bootloops. Obviously I am missing some key step, but for the life of me I cannot figure it out. Any help?
References
1. http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596
2. http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-unikernel-v5-t3166295