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 tried installing the OTA update on my phone, but it didn't take. It didn't even reboot. The phone is rooted, but I had everything else stock. The problem is that in order for me to manually install it on my phone, i have to flash a custom recovery. The stock won't help me much cause I get the blank screen. So if I flash a custom recovery, and then install the update manually, won't it unroot my phone which would keep me from flashing back to the stock recovery? Anyone know how I can get around this? Seems like a vicious circle to me. Maybe I am just not understanding it.
Thanks!
That depends....I will assume you have S-off with unrevoked, correct?
If you have that you should always be able to re-flash the recovery.
There are a couple different ways I was able to make it work.
1) You can reflash the stock recovery to your phone, then apply the update. The reason it stalls on reboot is that it's looking for the stock recovery.
2) Or you can go to androidcentral and download the zip file linked in the thread:
http://forum.androidcentral.com/droid-incredible/43198-nov-8-2010-maintenance-update.html
rename the file to update.zip/put it on your sdcard/boot into recovery.
That's the method I used, and it ran through the update process without a flaw.
yeah, s-off with unrevoked. Not unrevoked forever though.
I had the stock recovery on the phone at the time i tried installing the OTA.
If I flash the stock recovery to my phone, I can't use it to flash anything because i get the black screen with the white lines down the side. Something to do with the new screens and the drivers. Anyway, only a custom recovery works on my phone.
I usually fall back on the 2.2 RUU when I get stuck...that will clear all data off of your phone, as well as fixing bootloader and recovery.
I think there's a thread buried here somewhere with the file hosted in case you don't have it saved.
Soopafly Incredible said:
That depends....I will assume you have S-off with unrevoked, correct?
If you have that you should always be able to re-flash the recovery.
There are a couple different ways I was able to make it work.
1) You can reflash the stock recovery to your phone, then apply the update. The reason it stalls on reboot is that it's looking for the stock recovery.
2) Or you can go to androidcentral and download the zip file linked in the thread:
http://forum.androidcentral.com/droid-incredible/43198-nov-8-2010-maintenance-update.html
rename the file to update.zip/put it on your sdcard/boot into recovery.
That's the method I used, and it ran through the update process without a flaw.
Click to expand...
Click to collapse
After you ran your update manually, were you able to re-flash a custom recovery?
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.
I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?
RyanGN2 said:
I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?
Click to expand...
Click to collapse
Did your restore boot?
Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.
RyanGN2 said:
Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.
Click to expand...
Click to collapse
Try this.
From Zen Arcade's [ROM][4.3][Dec-2013] AT&T I317-UCUBMK6/MJ4 *Stock* Rooted Odex/De-Odex/Odin thread
After flashing one of the stock packages, you may need to flash the MK6 tz.img and optionally the param.bin from the MJ4 leak. The zip below contains two Odin packages.
Try flashing the tz only package first (in Odin), then the tz+param package to see if this gets your phone to boot. You may also need to boot recovery and do a factory reset.
AT&T i317 ODIN 4.3 UCUBMK6 TZ.IMG & UCUBMJ4 (Leak) PARAM.BIN (AT&T Note 2 ONLY)
I317UCUBMK6-TZ-PARAM.zip
http://d-h.st/CDK
- Run Odin3 v3.07.exe
Download Link http://www.mediafire.com/download/77...x2/Odin307.zip
Unzip to where you can run it.
- Put your Note 2 in Download Mode
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Plug into a RELIABLE usb port and a RELIABLE usb cable (preferably the white Samsung cable) and wait for it to show up in Odin (COM5 or something like that)
Unzip the I317UCUBMK6-TZ-PARAM.zip file you downloaded
- Click the PDA slot in Odin and locate the I317UCUBMK6-TZ.tar.md5 that you downloaded and unzipped
The filename that goes into the PDA Slot is I317UCUBMK6-TZ.tar.md5
MAKE SURE IN THE OPTION AREA ONLY AUTO REBOOT AND F.RESET TIME ARE CHECKED!!!
- Click START and wait. It will complete and reboot.
Try flashing the tz only package first. See if it boots.
If not, repeat the above steps using I317UCUBMK6-TZ-PARAM.tar.md5.
You may also need to boot recovery and do a factory reset. Do this after second ODIN flash.
If your phone still hangs after second flash, pull the battery, and boot into recovery mode.Just hold down UP volume button and power button until recovery screen pops up.
Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.
RyanGN2 said:
Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.
Click to expand...
Click to collapse
Since you tried everything above and it didn't HELP..
I'm wondering have you tired the kies emergency firmware recover. I taught I screwed my phone up flashing a Odin file. Then the phone was stuck not doing anything. Couldn't boot up, nada.
But after running it thru that set up, the phone was back to completely stock...
Look HERE»»»http://goo.gl/J0P1ZX
Not sure if it'll help but worth a try right. It helped me when I was in need.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.
RyanGN2 said:
I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.
Click to expand...
Click to collapse
I'm beyond lost of what you have done and where you're at.
Appears after doing the stuff in my post #4, your phone is booting past ATT screen ???? Understand it booted into OMNI, but at least it booted.
That's all I was trying to do was to get it past the ATT screen.
If I would have know you wanted to go back to stock 4.3, you could have done this....
http://forum.xda-developers.com/showthread.php?t=2618447
You may still have too, if the OTA does not work from the CWM stock 4.1.2 ROM.
Whenever you flash ROMs rule of thumb is back up apps and anything else you want to save, with Titanium Backup or MyBackup, etc. etc. Then restore apps after new ROM is installed.
Doing a wipe/factory rest prevents residual crap from the previous ROM leftover.
Unless its an update to a ROM you already have running, and the OP says no worries, dirty flash.
69%+ of problems with ROM flashes is the flasher didn't follow instructions or half-a$$ed it and didn't wipe or factory reset.
I've been guilty of that also, so not trying to be combative or accusatory.
Good luck with OTA.
When I did the steps in post #4 it never did anything it stayed in omnirom, which I have not had a problem getting to boot. It doesn't boot when I restore from my backup created before I installed Omni with CWM. I don't like Omni and I am tired of everything root. I'm a heavy jail breaker and thought I could do this however its more learning than I wanted and want to be done with root entirely. The OTA update did fail. Should I still use the 4.3 rom above or is there something else I should that will also remove root? I did backup apps with titanium and I also backed up everything with Kies.