I got an OTA notification. I'm currently running the stock GB rom,
with s-off, rooted (unrevoked 3.21) and CWM 5.0.2.0. I have ADB
installed and working.
What do I need to do to apply update without messing up
existing root setup?
Anyone know what is being updated? Does it replace radio,
boot or recovery?
fuzzynco said:
I got an OTA notification. I'm currently running the stock GB rom,
with s-off, rooted (unrevoked 3.21) and CWM 5.0.2.0. I have ADB
installed and working.
What do I need to do to apply update without messing up
existing root setup?
Anyone know what is being updated? Does it replace radio,
boot or recovery?
Click to expand...
Click to collapse
Applying the ota will make you loose root, but as long as your s-off you can root again easily.
Not sure exactly whats updated. If your rooted the update will not go thru anyways. It checks to make sure you have the stock recovery, and that all of your original stock apps and system files are there and unchanged. To install you would have to go complete stock other than still being s-off.
it does nothing if you have a custom recovery file.
if you click install, it'll do the count down, but won't reboot.
when you manually reboot, it'll still be what you had.
my setup is:
S-ON
HBOOT: 0.92.0000
CWM: 5.0.2.0
Baseband: 2.15.10.07.07
GingerTiny v2
GingerSense 3.5
So, I need to replace CWR with stock recovery?
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
So, I need to replace CWR with stock recovery?
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
PS:
Is there a way to stop the prompting for
OTA installing?
thanks
yes, anyone know how to get it to stop prompting? should i just let it try to upate and fail (i have root/custom recovery)? i froze updater using TI and i tried editing build.prop but neither worked.
orphicone said:
yes, anyone know how to get it to stop prompting? should i just let it try to upate and fail (i have root/custom recovery)? i froze updater using TI and i tried editing build.prop but neither worked.
Click to expand...
Click to collapse
What line did you edit in the build.prop? What number did you replace and what did you use to replace it? I've been trying to narrow this down also since it's worked in the past. So far I see one user that claims the build is 210690.
So in the build.prop I'd be looking for the line that included "/XXXXXX:user..." and replace the old 6 digit number with the new.
iowabowtech said:
What line did you edit in the build.prop? What number did you replace and what did you use to replace it? .
Click to expand...
Click to collapse
I used root explorer but my editing wasn't very sophisticated. Hopefully someone can shed some light? Post the updated build.prop values for this build and which ones we have to change?
orphicone said:
I used root explorer but my editing wasn't very sophisticated. Hopefully someone can shed some light? Post the updated build.prop values for this build and which ones we have to change?
Click to expand...
Click to collapse
Check this out, hopefully I explained it a little better here. Maybe you could give it a shot or confirm if this is how you did it and if that's the number you edited?
http://forum.xda-developers.com/showpost.php?p=19371024&postcount=58
Open build.prop with the text editor and look for:
Code:
ro.htc.checkin.url =http://andchin.htc.com/android/checkin
Change the url to something else but dont leave it blank. This will prevent the phone from contacting thr update server.
fuzzynco said:
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
Click to expand...
Click to collapse
I hope someone posts a flashable version of this update for us on cwm. I'm in the same boat as you.
yeah me too
Chernyi said:
I hope someone posts a flashable version of this update for us on cwm. I'm in the same boat as you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347044
The above linked thread is to an entire ROM and requires wiping. Is it possible to create an update.zip to bump me up (and keep me rooted) if I am rooted and have CWM? I know this has been done for previous updates.
This method helped me turn off the annoying install reminders. I used it with Nils' Business Gingersense.
http://forum.xda-developers.com/showpost.php?p=19370543&postcount=993
I just went ahead and updated since mine is S-OFF.
The steps I used to update and re-root:
Make sure you have S-OFF.
Boot into Clockworkmod and Backup your phone just in case.
Download the following:
Stock Recovery: http://www.multiupload.com/86N0CZ8NO0
Clockworkmod Recovery: http://www.multiupload.com/UQ3Q5ZI0HO
SuperUser: http://androidsu.com/superuser/ (use binary only if you already had SuperUser app installed)
Copy OTA update in /cache to SD card and name it update.zip.
Copy recovery zip files and SuperUser zip (su-bin-3.0.3-efgh-signed.zip) to SD card.
Rename stock_recovery_PB31IMG.zip to just PB31IMG.zip.
Hold VOL-, press POWER to boot into bootloader.
Press VOL- to update recovery to stock. At this point, it may automatically install the update. If not (red exclamation), press VOL+ and POWER to get to the stock recovery menu and select "Apply update.zip from SD" to update manually.
When update completes and you're booted into Android, go to Settings, Applications, and turn off Quick Boot.
Rename or delete existing stock recovery .zip on SD card.
Rename Clockworkmod recovery, cwm_PB31IMG.zip, to PB31IMG.zip.
Shutdown or reboot phone and get into bootloader again, and this time flash Clockworkmod recovery.
Get into Clockworkmod and use it to flash su-bin-3.0.3-efgh-signed.zip.
Once it reboots, you will be updated and rooted.
GnatGoSplat said:
I just went ahead and updated since mine is S-OFF.
The steps I used to update and re-root:
1. Make sure you have S-OFF.
2. Copy OTA update in /cache to SD card and name it update.zip.
3. Copy stock recovery to SD card and make sure it's named PB31IMG.zip.
4. Hold VOL-, press POWER to boot into bootloader.
...
Where is the stock recovery file? There is nothing in /cache or /cache/recovery. For a brief time, the OTA update file for Gingerbread 4.08 was in /cache, but nothing in recovery. the update file has since disappeared, but not before I copied it to my sdcard, so I have that.
Also, I noticed after installing that version of Gingerbread on another phone that was not rooted, that once I did that the hboot menu did not appear when holding down the vol key while powering on. Maybe that is an S-off thing only.
Thanks.
Click to expand...
Click to collapse
I had to search Google for quite some time before finding the stock recovery and when i searched just now, all I found were broken links.
I won't be home for awhile, but let me know if you can't find the stock recovery and I'll upload it somewhere.
Oh yeah, you have to go into Settings, Applications, and turn off Fast Boot or Quick Boot in order to be able to get into bootloader when rebooting.
shoot
I wish I had read this thread before i messed up my phone. I was running fine rooted with unrevoked and I thought I'd be smart and get the OTA to install and worry about re-rooting later. It would never reboot so I did a factory reset. That only stuck mine in a Sense crash loop. I'm on PrimeXL's r40 ROM now for 24hours and I'm looking into what else might be available. It runs ok but I can't get Exchange mail for work because something about "device encryption enabled" policy, pic gallery won't show emmc folders, and keyboard auto-correct goes nuts in portrait mode on internet.
jonduncan99 said:
I wish I had read this thread before i messed up my phone. I was running fine rooted with unrevoked and I thought I'd be smart and get the OTA to install and worry about re-rooting later. It would never reboot so I did a factory reset. That only stuck mine in a Sense crash loop. I'm on PrimeXL's r40 ROM now for 24hours and I'm looking into what else might be available. It runs ok but I can't get Exchange mail for work because something about "device encryption enabled" policy, pic gallery won't show emmc folders, and keyboard auto-correct goes nuts in portrait mode on internet.
Click to expand...
Click to collapse
Are you wanting to go back to stock?
If so, are you S-OFF? If yes, it's pretty easy, you can just install the full Gingerbread RUU (the .exe file that installs from PC) to go back completely to stock and it'll boot for sure.
What I would do is do a backup with clockworkmod to SD.
Then install the RUU.
Flash clockworkmod back into it (this is why you need to be S-OFF).
Use clockworkmod to restore only your /data partition from SD.
Re-root by installing su.zip.
You should now be rooted, stock, and all your apps and settings should still be intact.
I don't know for sure the backup and restore will work from one ROM to the next, but it did work when I bricked my wife's Incredible and had to restore from RUU (though it was on stock ROM before and after).
Related
Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....
It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good
timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now
so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA
topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App
Nevermind I got the Su command to work
Sent from my PC36100 using XDA App
you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.
Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!
hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?
Build number 1.47.651.1 CL195459 release-keys
yea same here......and what is it that your trying to do...go back to stock ROM?
I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.
OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!
hi,
as far as i found out today it was recommended not to install the OTA-update that has been provided by HTC because I would lose my Root-rights.
Since this is not a problem for me I wanted to install it - but it fails everytime with messages like
E:failed to verify whole-file signature
[...]
Would it make sense to install it maunally? the download over the air was no problem, so i could easily put it into root-folder, rename it and install it manually. but do i have any other negative side effects except losing rootrights?
regards,
andre
Bootloops for one..
The cleaner way to run it, is to run the RUU (Do create a goldcard before you do), then run the OTA as update.zip, as Nature intended..
And why on earth would you need an OTA on a rooted phone. Just get the latest rooted ROM which would be more uptodate..If you just dont want root, do as above..
Well, no in this case it's just run the 2.29.405.2 RUU then you've not got to bother about the OTA!!
First i try to install as "zip from sd" with clockwork. But I become bootlooping phone.
Then I try to install with goldcard. All was ok. But when am try to install an app from market, my phone restarted at the point of installation.
Is any other way to update without RUU with clockwork?
Sent from my HTC Desire using XDA App
In a word, no. You can try a hard reset but best way is to flash the RUU. Gold card only needed if you have a branded hendset
droidzone said:
Bootloops for one..
The cleaner way to run it, is to run the RUU (Do create a goldcard before you do), then run the OTA as update.zip, as Nature intended..
And why on earth would you need an OTA on a rooted phone. Just get the latest rooted ROM which would be more uptodate..If you just dont want root, do as above..
Click to expand...
Click to collapse
the major disadvantage is loosing all information. or is titanium backup able to restore everything? i don't believe so.
regards,
andre
Titanium works on rooted phones, so you could flash stock, root it and then restore
does someone know why installing this OTA-upgrade is failing with signature-message?
Don't flash it if you're rooted - simple as that!!!
understood that. but i want to get some more infos on that.
beside this, since i have to flash a new rom anyway: which is a very good rom you are using? will everything be restored by titanium backup, or will the screens e.g. not be backuped and restored?
I'm on stock 2.29.405.2 and not rooted. It's a good ROM. You'll need to obviously root your phone again to restore the backup
bad loop... ;-)
get back to official rom with OTA but without restoring the backup... or stay on root... i think i will stay on root now. i will try the update this evening and check for the restore how far it works...
thanks for your effort.
HELP!!!
i tried now several times to install a shipped rom (2.10.405.2, 2.29.405.2), but it is not working! it restarts my desire, and it stays with the black screen and white HTC letters... error 171 is displayed afterwards... how can i resolve it? i tried already to download a rom as zip and tried to install it via unrevokedrecovery 2.5.0.7 via "apply update.zip", but it didn't work as well.
can someone help me???
regards,
andre
edit: after installing htcsync it worked again...
YOU CANNOT DOWNLOAD A STOCK ROM AND FLASH IT VIA CLOCKWORK MOD!!!
How many more time does it have to be said????
If you wanna try flash a custom ROM you don't select 'apply update.zip' - you go to flash ROM from SD card and choose the ROM you want to flash. If you don't know how to use CWM why the hell ahve you rooted?!!?
astrakid said:
HELP!!!
i tried now several times to install a shipped rom (2.10.405.2, 2.29.405.2), but it is not working! it restarts my desire, and it stays with the black screen and white HTC letters... error 171 is displayed afterwards... how can i resolve it? i tried already to download a rom as zip and tried to install it via unrevokedrecovery 2.5.0.7 via "apply update.zip", but it didn't work as well.
can someone help me???
regards,
andre
Click to expand...
Click to collapse
I honestly didnt understand what you're trying.
If you want to get the system unrooted, back to stock, then:
Read FAQ 5 and get the PB99IMG.zip
After getting PB99IMG.zip, put it in root of sdcard/goldcard,
Switch Off
Switch on with Back and Power. Keep it pressed.
The system will detect the file and prompt
Press Vol+ to start the RUU
To install a custom rom, "Install zip file" from Clockworkmod.
4. Volume down + power, not back. Back will take you to FASTBOOT
EddyOS said:
4. Volume down + power, not back. Back will take you to FASTBOOT
Click to expand...
Click to collapse
You're right..From Fastboot, it's one additional key..
Got the notification earlier today, went ahead and started downloading the update. I turned on 4G, it couldn't get 4G so i turned on wifi when it was at 12%
Download completed, it rebooted, showed the proper update screen, and now it gets to about 15% of the progress bar then shows the slanted triangle with an exclamation mark in it and little android dude under it.
Rebooted, tried again and same thing.
I'm thinking cuz i switched from downloading via 3g to wifi maybe file is corrupt?
I deleted the update file from /sdcard/download and tried again and same thing...
any ideas?
---update--
i pressed discard and then went to back to check for software update and it re-downloaded it but same thing..
Is it cuz its rooted? do i have to remove the root to put the OTA?
btw, its my gf's evo.. if it was mine i'd probably be running some other rom.
--update2--
So i flashed stock recovery then tried again, same thing but this time different images during the install process and the error
Went over to unrevoked's site, installed the unrevoked-forever-son.zip (had to flash clockwork recovery to flash that zip)
That still didn't do it.
Now i'm trying to get stock recovery back on but it won't ask me if i want to install it. I have it as PC36IMG.zip on the root of my sd card. When i first get into HBOOT it shows checking PC36IMG.zip and then no option to press volume up to install/flash it.
ALso i unziped PC36IMG.zip and attempted to flash recovery.img via fastboot but i get this:
[codr]sending 'recovery' (3779 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)[/code]
Anyone know what to do?
I'm having the same issue! Also rooted. I'd really like to not have to flash it from recovery so I don't have to re-do all my settings.
I'm having similar issues, but I'm not as far as you have gone. =)
Could you help me out on reflashing the stock recovery? 3.70 is the first OTA that has come out since I rooted (with unrevoked3), so I'm no expert. I'm downloading a stock PC36IMG.zip, but I don't want to replace everything if I can help it.
Hopefully once I have a stock recovery again I can give you a hand. =)
I'm no expert by any means but, I was rooted when the 1st OTA came out. I just flashed joey-krims stock rom over top my stock rom. I just wiped cache & dalvik cache. Didn't do a factory reset. All apps and data were preserved. And I just flashed joeys most recent update over top the last update, same procedure, same results. Only thing that happed was my weather bug widget had to be put back on the screen.
Milage may vary.
VaughnOnix said:
I'm having similar issues, but I'm not as far as you have gone. =)
Could you help me out on reflashing the stock recovery? 3.70 is the first OTA that has come out since I rooted (with unrevoked3), so I'm no expert. I'm downloading a stock PC36IMG.zip, but I don't want to replace everything if I can help it.
Hopefully once I have a stock recovery again I can give you a hand. =)
Click to expand...
Click to collapse
Download the PC36IMG.zip and place it on the root of your SD card. Reboot device while holding volume down, give it a sec and it should prompt you volume up to flash volume down to cancel.
Flashing the recovery will not erase/replace anything but the recovery itself.
there is something that gets missed every time.
the ota will not work unless u r on an odex completely stock rom!!!
when i say complete i mean all apps that came with the stock rom have to still be on it also.
otherwise... dont be surprised if it wont work.
just flash a new rom instead... that would be the better sol here.
aamikam said:
there is something that gets missed every time.
the ota will not work unless u r on an odex completely stock rom!!!
when i say complete i mean all apps that came with the stock rom have to still be on it also.
otherwise... dont be surprised if it wont work.
just flash a new rom instead... that would be the better sol here.
Click to expand...
Click to collapse
really?
That sucks... so is everyone that is rooted having the same issue with this OTA or does this happed to all OTA for rooted ussers?
(this is my gf's evo, i got a dell streak which isn't this hard to flash an official realease.. when they do release them is a different story)
yea, same here. Wife and I were running errands so I ran the OTA on her handset - no issues. Tried it on mine and got the same error with the thing over the Android. doh!
If I pop the battery out I can use the phone but now i want the update.
My device is rooted with UnrEVOked. Wife's is not rooted.
I am trying to restore the factory ROM and then try the update and whatever else I can salvage...
http://forum.xda-developers.com/showthread.php?t=685835
links to the factory ROM
http://rapidshare.com/files/3899834....651.1_Radio_1.39.00.04.26_release_171253.exe
djliquid said:
yea, same here. Wife and I were running errands so I ran the OTA on her handset - no issues. Tried it on mine and got the same error with the thing over the Android. doh!
If I pop the battery out I can use the phone but now i want the update.
My device is rooted with UnrEVOked. Wife's is not rooted.
I am trying to restore the factory ROM and then try the update and whatever else I can salvage...
http://forum.xda-developers.com/showthread.php?t=685835
links to the factory ROM
http://rapidshare.com/files/3899834....651.1_Radio_1.39.00.04.26_release_171253.exe
Click to expand...
Click to collapse
Same story here, rooted with unrevoked.
I would flash factory rom as you are doing but if i don't get it back to how it was, my gf would ***** till i die...
Ok this is pretty simple, just did it on my coworkers Evo will be doing mine once I am off call,
1. Use Rom manager to install ra recovery
2. Boot to recovery, and flash zip from SD card ( this step assumes us have copied the downloaded zip using root explorer from cache dir and saved to sd card)
3. Select the OTA 370 blablabla.zip file
4. after flash completes, don't reboot yet, select apply zip from SD card again, and flash root (I used a file called 2.2 root.zip I found on these boards some where)
5. Reboot and when it finishes ur phone will be rooted and updated, running stock recovery
*** note I answered from my phone so I don't have any of the links or files, I will try to place links next time i am at my computer. this will just update and not wipe anything from the phone **
detcup4evr said:
Ok this is pretty simple, just did it on my coworkers Evo will be doing mine once I am off call,
1. Use Rom manager to install ra recovery
2. Boot to recovery, and flash zip from SD card ( this step assumes us have copied the downloaded zip using root explorer from cache dir and saved to sd card)
3. Select the OTA 370 blablabla.zip file
4. after flash completes, don't reboot yet, select apply zip from SD card again, and flash root (I used a file called 2.2 root.zip I found on these boards some where)
5. Reboot and when it finishes ur phone will be rooted and updated, running stock recovery
*** note I answered from my phone so I don't have any of the links or files, I will try to place links next time i am at my computer. this will just update and not wipe anything from the phone **
Click to expand...
Click to collapse
Was your co worker rooted and having the same issues with the update failing before you did all this?
This method didn't work for me.
During the install via RA recovery it errors out after
Code:
verifying current system . . .
i get
Code:
assert failed: apply_patch_check("/system/app/Sprint_Navigation.apk", "E:unknown command [e788c9586bac4af50d9d6df17f6b9eac21fced4" ,]
E:unkown command [a044")]
E:Error in /sdcard/OTA_Supersonic_3.70.651.1-3.29.651.5_releasezq9ss6wyobuo26b5.zip
(Satus 7)
Installation aborted.
Is this all cuz i uninstalled sprint navigation?
fone_fanatic said:
Download the PC36IMG.zip and place it on the root of your SD card. Reboot device while holding volume down, give it a sec and it should prompt you volume up to flash volume down to cancel.
Flashing the recovery will not erase/replace anything but the recovery itself.
Click to expand...
Click to collapse
Thanks for the assist. Just to confirm, flashing a zip that weighs in at almost 200mb will only affect the recovery?
ok here is my problem i flash the rom install the update ans my 4G and wifi is having a error what am i doing wrong
VaughnOnix said:
Thanks for the assist. Just to confirm, flashing a zip that weighs in at almost 200mb will only affect the recovery?
Click to expand...
Click to collapse
NO you are correct, the 200MB PC36IMG.zip will reset everything!
I was referring to the stock recovery image (3 to 4MB file)
I noticed browsing through the forums and downloading files i need that different recovery and roms are name as PC36IMG.zip
So now everytime i download one, i either rename it or put it in a folder with the proper name..
dramadawgz said:
ok here is my problem i flash the rom install the update ans my 4G and wifi is having a error what am i doing wrong
Click to expand...
Click to collapse
Don't know why that is.. did you download and flash via recovery or you did the OTA update?
via recovery thats how i got it and it's killing me cause i need the update but i rather have a rooted EVO lol
dramadawgz said:
via recovery thats how i got it and it's killing me cause i need the update but i rather have a rooted EVO lol
Click to expand...
Click to collapse
Unrevoked will root it..
I'm restoring it to ship rom now then let it do the OTA restore Nandroot data backup and then unrevoked root..
ok ill give that a try cause i just redid it and im still getting the error message
Failing here too.... stuoid.
werxen what problems r u having
Ok, so what i did was downgrade to stock shipped rom
then had to do the 5 or so OTA's and finally on 3.70.651.1 but NOW I can't Root or flash clockwork mod which means i can't restore the nandroid backup
I ran into this post over at androidcentral Yes you can do OTA update if youve unrevoked forever heres how hope that helps you guys as i went through a headache and all this other crap to get this stupid OTA and now i can't even restore my backed up data!
Guess i have to wait for a better way to root the HBOOT 2.10 version
good luck to everyone else
root the phone will block future OTA update? even factory image installed?
I donwload rom manager from market, it says your 'rom does not support OTA update, please contact your developer', but I have pure factory image from google installed.
is it showing worong thing? or did it mess up my system? or I should never had clicked there?
ROM manager is talking about an ota update for a custom rom, which you aren't running. And if you want to know whether rooting will prevent a future official ota, a search will tell you the answer.
Sent from my Galaxy Nexus using XDA App
this article says yes. but other places say it might not, but ota update will remove the root.
citrix80 said:
it might not, but ota update will remove the root.
Click to expand...
Click to collapse
This.
Twice so far for me.
Rooting the stock ROM will not prevent OTA updates. I've had the Nexus One and now the Galaxy Nexus, and I can tell you that rooting will not prevent OTA updates, as long as you have stock recovery.
What will prevent OTA updates from installing is custom recovery. If you're using ClockwordMod recovery, you will get the OTA update notifications, but the actual update will fail to install. You can still install them manually by flashing the update yourself in recovery. It's easy.
In either case, you'll almost certainly need to re-root afterwards.
stock recovery? you mean stock image from google.
logically it make sense custom roms don't get update because they are modified from orginal copy, updates are for original condtion copy so may not fit into them correcty. but what exactly is preventing the update there?
I dont have custom rom or recovery and my ota failed.
Sent from my Galaxy Nexus using xda premium
@rbiter said:
I dont have custom rom or recovery and my ota failed.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
after root?
OTA updates install via recovery, so they fail with custom recovery (ClockworkMod). They should install with stock recovery. This is assuming the stock ROM (even rooted), not a custom ROM since as you said that definitely won't work at all, since the update is meant for the stock ROM.
If an OTA update fails on the stock ROM (even rooted) with stock recovery, something else is usually wrong. It's definitely possible, but not the normal situation. In two years with my Nexus One and now Galaxy Nexus, I've never had an OTA update fail on a rooted stock ROM (both automatically with stock recovery and re-rooting afterwards, or manually applying the update with custom recovery).
I know with the Nexus One, some OTA updates failed if people had rooted and removed some of the built-in apps or otherwise messed around with /system. If things like that get modified, there's a good chance the update will fail.
Just my experience... hopefully someone else can give some further input.
does rooting make any change to system?
citrix80 said:
does rooting make any change to system?
Click to expand...
Click to collapse
Getting root access only involves two files being placed in the /system partition:
1) the su binary is placed in the /system/bin directory; and,
2) the Superuser.apk file is placed in the /system/app directory.
Other than that, there are no other changes.
As phazerorg said, rooting will not affect getting the OTA.
There are two separate issues here:
1) Receiving the OTA update; and,
2) Having the OTA update install.
Everyone on a stock ROM (and even some custom ROMs) will receive the OTA update (eventually).
As for installing the OTA update, there are again two issues here:
1) Having the OTA update install automatically; or,
2) Installing the OTA update manually.
To have the OTA update install automatically, you need the following:
1) A stock recovery;
2) A stock ROM (and it CANNOT be de-odexed);
3) All the original applications need to be present (like Goggles, Google+, etc.)
4) Root or no root makes no difference; and
5) A stock boot image.
If you have a custom recovery flashed, then you can manually apply the update through the recovery. However, all the other items from the list above still apply.
If you flashed a stock de-odexed ROM, or a boot image (i.e., kernel) that was modified somehow, you need to flash back to the stock version of each or else you cannot apply the update.
Hope this clears up some things.
what is stock recovery? is it same as stock image?
what is de-odexd ?
efrant said:
Getting root access only involves two files being placed in the /system partition:
1) the su binary is placed in the /system/bin directory; and,
2) the Superuser.apk file is placed in the /system/app directory.
Other than that, there are no other changes.
As phazerorg said, rooting will not affect getting the OTA.
There are two separate issues here:
1) Receiving the OTA update; and,
2) Having the OTA update install.
Everyone on a stock ROM (and even some custom ROMs) will receive the OTA update (eventually).
As for installing the OTA update, there are again two issues here:
1) Having the OTA update install automatically; or,
2) Installing the OTA update manually.
To have the OTA update install automatically, you need the following:
1) A stock recovery;
2) A stock ROM (and it CANNOT be de-odexed);
3) All the original applications need to be present (like Goggles, Google+, etc.)
4) Root or no root makes no difference; and
5) A stock boot image.
If you have a custom recovery flashed, then you can manually apply the update through the recovery. However, all the other items from the list above still apply.
If you flashed a stock de-odexed ROM, or a boot image (i.e., kernel) that was modified somehow, you need to flash back to the stock version of each or else you cannot apply the update.
Hope this clears up some things.
Click to expand...
Click to collapse
Thank you for taking the time to clear this up.
I unlocked the bootloader, rooted, and then installed CWM to make a back-up. I am still, and plan on always, running the stock Rom (4.0.2 right now). I was worried about the OTA's but based on what you said, I can still download the update, but I would need to use CWM to actually install the update? Or would I just need to flash the new update via an updated-stock-rom?
citrix80 said:
what is stock recovery? is it same as stock image?
Click to expand...
Click to collapse
Your phone has several different firmwares on it. Radio, bootloader, recovery and the actual OS. Recovery is what lets you "recover" the OS when things are screwed, and also perform other maintenance operations... such as installing OS updates. You can boot your phone into the bootloader or recovery, in addition to the OS.
Custom recoveries such as ClockworkMod let you do even more things, such as flashing updates or custom ROMs of your choice, or taking nandroid backups (which are basically "images" of your current ROM. Restoring a nandroid backup brings your phone back to exactly how it was at the time the backup was taken... very useful when trying new ROMs or messing around! This is reason enough to use a custom recovery in my opinion).
The stock OS only knows how to install OTA updates using the stock recovery. Stock recovery is what comes on your phone (or from Google via an update). Custom recoveries like ClockworkMod are generally based on the stock recovery, but are different and the OTA updates don't work with them automatically. You can definitely install OTA updates using custom recovery, but you have to do it manually. After you get an update notification from the stock ROM, the update zip file should be downloaded and located in /cache and you can use ClockworkMod to flash it. I also keep the Superuser zip on my phone at all times, so I can flash it immediately after flashing an OTA update, which lets me retain root.
To answer your actual question, I would say that stock recovery is one part of the stock image. But most people probably think of the "stock image" as being the OS side of things. You could have the stock image OS, but still use custom recovery. I hope that makes sense.
what is de-odexd ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Glossary#De-Odex
Although I understand what odex/deodex is, I'm not sure I can give a very good explanation. Someone else can comment, or you can do a search as it's been covered a number of times in various forums on xda, and other sites.
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
I used cwm did a full system wipe, the phone went dead, stuck on bootloader screen, then I flashed stock image from beginning.
how to take nandroind back up? i only see backup/restore in cwm.
citrix80 said:
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
I used cwm did a full system wipe, the phone went dead, stuck on bootloader screen, then I flashed stock image from beginning.
how to take nandroind back up? i only see backup/restore in cwm.
Click to expand...
Click to collapse
In CWM go to Recovery (Hit the "power" button to select), then go to "Back Up and Restore" (use the "power" button to select), then go to "Back Up". Make sure you have at least 50% battery when you do this.
After it finishes copy the contents it should be in /sdcard/clockworkmod/backup I back it up to Dropbox, so I can have the files where ever. (PM me if you'd like an invite so we can both get more space on Dropbox. If you do use Dropbox, I'd encrypt the data with something like TrueCrpyt.)
citrix80 said:
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
I used cwm did a full system wipe, the phone went dead, stuck on bootloader screen, then I flashed stock image from beginning.
how to take nandroind back up? i only see backup/restore in cwm.
Click to expand...
Click to collapse
With the phone completely off, holding down both volume up and volume down and then holding the power button will get you into the bootloader. From there you can use volume up/down to scroll through options to boot into recovery. Alternatively, if you're already rooted, you can use apps like Quickboot to just reboot directly into recovery.
I never actually tried the stock recovery on my phone... I unlocked the bootloader and flashed ClockworkMod and rooted as soon as I got the phone home from the store. Normally, selecting "Recovery" from the bootloader menu would get you into recovery. The only time when I saw the android with the X was after trying to apply the first OTA update (just for fun even though I knew it wouldn't work without stock recovery).
If you have ClockworkMod (CWM)... the backup/restore is nandroid. It's called nandroid because it's NAND flash, and the OS is Android... NAND... Android... Nandroid.
But... make sure you backup /sdcard to another place, because if you do a full factory wipe, you'll also lose all that since they're stored on the "sd card", which is really the data partition. Doing wipes in CWM doesn't wipe /sdcard, but factory resets do. I reguarly rsync my /sdcard to another computer over wifi so I'm sure to always have a completely external backup. That's never a bad idea when you're messing around with this stuff. Too many backups never hurt anyone. Too few backups, on the other hand...
citrix80 said:
what is stock recovery? is it same as stock image?
what is de-odexd ?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=what+is+stock+recovery
http://lmgtfy.com/?q=what+is+deodexed
JayBeezy802 said:
Thank you for taking the time to clear this up.
I unlocked the bootloader, rooted, and then installed CWM to make a back-up. I am still, and plan on always, running the stock Rom (4.0.2 right now). I was worried about the OTA's but based on what you said, I can still download the update, but I would need to use CWM to actually install the update? Or would I just need to flash the new update via an updated-stock-rom?
Click to expand...
Click to collapse
Yes, if you have CWM installed, you can use that to install the update. No need to flash an updated stock ROM.
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
citrix80 said:
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
[snip]
Click to expand...
Click to collapse
The Android robot with the X on it is the stock recovery. When you are there, hold the power button and press the volume up key to access the menu.
efrant said:
The Android robot with the X on it is the stock recovery. When you are there, hold the power button and press the volume up key to access the menu.
Click to expand...
Click to collapse
I just tried to access my stock recovery. But I see the Android robot with a triangle with ! inside. Then I can't do anything with it - power button and volume keys have no effect. What does this mean? I'm running stock rom with stock recovery but with bootloader unlocked.
Hey there
I'm currently working through the below process... on my Verizon CDMA LTE Galaxy Nexus runing 4.0.2 Stock.
http://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/
Also watched this Video (but he doesn't get the error)
http://www.youtube.com/watch?v=dQ1HuteSnDE
And when i get to the part about running mempodroid as sh I get an error that says the following:
Segmentation fault See the below screen shot.
Does anyone have any advice on how i can get past this? I have restart phone and desktop many times and happens every time. I have the PDAnet drivers installed and everything else adb seems to be working.
Would love some help,thanks in advance. Really want to get this working tonight if possible.
Conty
You are not developing anything
Moved to Q&A
FNM
Sent from my PantechP4100 using xda premium
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
imnuts said:
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
Click to expand...
Click to collapse
I'm just following the process for the 4.0.4 install. How else can i do what i need? I'm quite new to my Nexus, i had a bionic before.
Thanks
Need the temp root to run mempodroid i think, can i do this another way? i honestly don't know
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
imnuts said:
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
Click to expand...
Click to collapse
Which CWM version do i want and will this include the radios if i do it this way, sorry kinda newb at this phone. very different to my bionic.
Thanks so much for your help tho
Eidt
I got into stock recovery and saw the android with the explanation point but when i click Volume up + power i get no menu...
I'm off to bed will check back in the morning and see if you have any ideas, thanks again for the help
Finally got the stock recovery to work, however it only allows flashing from ./cache and i cant get my update.zip to cache without root right?
So decided to just unlock bootloader and then it let me root and push to ./cache and then i flashed the update.zip
All seems to be working now.
Thanks for all the help
I love the fact its so easy to unlock and lock the bootloader. very happy with that lol
is there a way to re root the phone once its on 4.0.4 IMM76K ? as the Galaxy Nexus toolkit stops at IMM30B...
Thanks
Nevermind
Adrynalyne saved the day once again
http://www.droid-life.com/2012/02/06/how-to-root-android-4-0-4-on-the-galaxy-nexus/
Thanks Adrynalyne