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!!!!
I rooted my EVO 4G yesterday. Everything was going fine until I uninstalled some of Sprint's factory software. This caused my system to behave very weird so I decided to flash it back to the OTA software.
I followed the instructions on android central, but unfortunately the PC36IMG.zip file they tell you to download and install is Android 2.1. I'm now stuck on 2.1, and the OTA update doesn't work. I am new to this and accept that this is my fault, but I was wondering if anyone had instructions on how to update to 2.2?
I tried downloading and installing HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed from this site, but the bootloader screen won't let me install this file. Any help would be greatly appreciated. THANKS!
What root method did you use?
Also, you can't flash ROMs from bootloader, you need to be in recovery -- when you get to the bootloader screen, go to recovery, press power. Also, make sure that you have a recovery installed (ClockworkMod or Amon_Ra).
From recovery, you should be able to flash to any 2.2 ROM you want (assuming that you have full root/nand unlocked/s-off/whatever else people want to call it).
Also, be prepared to be flamed for posting this in the development section (as opposed to the Q&A).
Yeah, should have done it in Q&A. Sorry for that. Again, noob
I initially used Unrevoked. I had ClockworkMod installed before reverting back to 2.1. It's gone now. Should I just use Unrevoked again to reinstall it?
chadz70 said:
Yeah, should have done it in Q&A. Sorry for that. Again, noob
I initially used Unrevoked. I had ClockworkMod installed before reverting back to 2.1. It's gone now. Should I just use Unrevoked again to reinstall it?
Click to expand...
Click to collapse
Go to the market, and download ROM manager. If you already have root, you will be able to flash either Clockwork or (if you scroll down to the bottom of the options when you open the ROM manager app, you will see the option to flash an alternate recovery) Amon recovery via ROM manager. Once the recovery is flashed, you can boot directly into recovery using the ROM manager app. Place the rom file on the root of the SD card, and when you boot into recovery, find "install zip from card" and flash it. Make sure you wipe everything twice before you flash a new rom.
Before you do anything, make a nandroid back-up. If anything goes wrong with the rom, you can always download ROM manager again and revert back to how your phone is now. (providing that whatever went wrong didn't break your root)
Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.
fisheric1 said:
Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.
Click to expand...
Click to collapse
Need any and all information about your phone. I also notice that you are new. The dev section isnt for Q/A there is an entire section dedicated to solving these issues. Please remember that next time. Keeps things cleaner. So please gather anything you can about your phone. Method, Hboot, Version, Radio, Anything that can help anyone here identify something.
Do you have the rom in the root of the usb card? If so try full data wipe and installing the room see if it boots up.
Thanks for the quick reply. Will remember. Desperation has gotten the better of me. I will move over to Q/A if you prefer.
HBOOT-2.10 0001
RADIO - 2.15
Initially rooted via Unrevoked 3 beta RC2 yesterday.
if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)
T3hPWN said:
if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)
Click to expand...
Click to collapse
I agree with this method... the best way to determine the recovery to use would be to go into the terminal and type
Code:
cat /proc/mtd
if you see "400000" then you need to get the clockwork v3.0.0.2 that supports this phone partion layout. If you see "20000" then you should get amon_ra 1,8 from here:
http://forum.xda-developers.com/showthread.php?t=705026
The information I gathered was from this post:
http://forum.xda-developers.com/showthread.php?t=894331
Making sure you have the correct recovery is the first step. Once that is done create a nandroid and save it somewhere to ensure that the wimax partition is saved.
You have to flash the modified version of Amon_ra found in Zikronix thread. You can find my thread that points to it or just search for hboot 2.10 and follow the instructions in that rooting thread. It seems you're already rooted so just flashing the recovery is probably all you will need.
I haven't used unrevoked, and I know there are several versions. But I have seen others who have used unrevoked and couldn't flash anything bc evidently the method they used to root didn't install the flash_image file on their phone.
I know that installing flash_image fixed being able to flash for some people who rooted with unrevoked.
This issue came up and I was able to help some people, if you check near the end of fastRX8 thread. But I was only able help point the right direction, they figured out the rest of the way. The OP there has the flash_image file and tells you what terminal commands to install it.
I don't know how for you to check if you gave it or not, as I can see mine on sd card cuz I put it there when I rooted.
Beyond this suggestion, lithid can probably help much better than I.
But def post your hardware version, root method, and hboot version (you see that when you go into bootloader and read the top line.
Sent from my PC36100 using XDA App
Wow, sorry, theres been several posts since I started tying. Looks like these guys got it for ya
Sent from my PC36100 using XDA App
Was there a resolution for your problem? If so please post so anyone searching in the future can resolve there problem quickly.
you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.
dkdude36 said:
you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.
Click to expand...
Click to collapse
You mean the modified amon ra recovery image?
exactly...
dkdude36 said:
exactly...
Click to expand...
Click to collapse
Ya it worked for someone else in the Amon_Ra Clockwork thread here is the link.
zikronix said:
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to.
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
Click to expand...
Click to collapse
OP flash the PC36IMG in the bootloader to load this new recovery, then you can go into your new recovery and flash a new rom.
i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?
defjef123 said:
i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?
Click to expand...
Click to collapse
Were you restoring a backup or did you stuck on loop on a new rom flash?
i wasnt even trying to flash a rom yet. i was doing the very first nand backup so i could check some roms out. after the backup was complete it gave the option to power off so i did and when i turned my phone back on it was in the bootloader loop. so i went back to recovery, wiped everything, restored nand and i said it restored but when i rebooted it was back in the bootloader loop.so i just search around trying to get help but couldnt find much so i put sprintlovers since it boots up right when you turn your phone on. now it wouldnt even nand backup it said some error and was in the bootloader loop again so i just reinstalled sprintlovers, again
Try downloading an actual rom in zip format (not sprintlovers pc36img) and see if you can flash a new rom fresh. Make sure to wipe everything.
Try using Caulkings format all zip in recovery to wipe your caches.
http://www.mediafire.com/file/ikylelx99c49133/Calkulin's_FORMAT_ALL.zip
put in on my sd card turned my phone off to go into recovery and now my phone wont even turn on
it came on now. gonna try to wipe and flash that rom
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).
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.