Ive been reading post after post after post and im confused as all hell.
All I want to do is be able to take a image of my phone once I have everything setup and take new images about once a week in case the phone is ever replaced. I want to be able to get all my ringtone associations apps and app settings like the settings from my k-9 setup etc... phone settings EVERYTHING. I understand the mybackpro and sprite will not do this detailed of a backup. So thats what lead me here.
I have the sprint hero. I have already updated to the newest OTA firmware.
I would like step by step what i need to do. Here is what i think is the correct way from my searches. PLEASE CORRECT ME IF IM WRONG.
1. download ruu from http://forum.xda-developers.com/showthread.php?t=586258 insatll htc sync and run ruu and follow directions. That should bring the phone back to the stock image. Unless I can root from the new OTA firmware which I dont know. Someone lmk if I can.
2. Root the phone following this link http://forum.xda-developers.com/showthread.php?t=583291 or this link http://theunlockr.com/2009/11/18/how-to-root-your-sprint-hero-in-one-click/ or this link http://theunlockr.com/2009/11/07/how-to-root-your-cdma-htc-hero-sprint-verizon/ Which link is best to follow?
3. I setup my phone then turn off then home key power will get to the green menu with nandroid backup as a option. Run that and I have a image of EVERYTHING on my phone?
One last ? Can I ever update to the latest firmware or am I stuck with the stock firmware.
Thank you for your time.
It looks like you have answered your whole question. Yes, you have the process down to a science.
About which links to follow:
Folow the first link to root your phone. That's a thorough, easy to follow, minutes-to-root, fool-proof method. It also contains the download links and everything you need to do EXACTLY what you want.
So yeah,
1. RUU to stock
2. Root by following guide
3. Home/Power and select Make Nandroid Backup
4. (if you want) install rom like fresh .4 (most stable release) that includes the Sprint MR (maintenance release) and application tweaks etc.
Thank you for your response. Though I had it but wanted to make sure
Can I do the OTA update after I have rooted and made my backup? Will this cause any issues with the root or the backup?
also does fresh .4 use the htc sense ui? Ive come to really like that compared to my buddies droid UI.
Actually, if all you want to do is take a nandroid backup, there's no reason to root your phone at all.
Just install the latest flashrec here
Get the Amon-Ra recovery image for the Hero here
Install flashrec, run flashrec, BACKUP RECOVERY IMAGE, then apply the Amon-Ra recovery image.
Now, you can boot to recovery and do a nandroid backup.
If you want to apply the Sprint update, you must restore your backup recovery image (see above in bold) before the update will apply. Once you've rebooted a few times with the Sprint update, you can then apply the Amon-Ra recovery image again (no need to re-backup the recovery image). Reboot into recovery and you can make a nandroid backup.
While it's true that the first link you provided will indeed give you the recovery image to be able to do a nandroid backup, if that is all you want to do, there's really no reason to go through all the steps of rooting your phone (this may change in the future if flashrec stops working with an update from Sprint/HTC - we may even be forced to do a goldcard method at some point in the future if they do something like they did to the gsm Android phones).
jmanley69 said:
Actually, if all you want to do is take a nandroid backup, there's no reason to root your phone at all.
Just install the latest flashrec here
Get the Amon-Ra recovery image for the Hero here
Install flashrec, run flashrec, BACKUP RECOVERY IMAGE, then apply the Amon-Ra recovery image.
Now, you can boot to recovery and do a nandroid backup.
If you want to apply the Sprint update, you must restore your backup recovery image (see above in bold) before the update will apply. Once you've rebooted a few times with the Sprint update, you can then apply the Amon-Ra recovery image again (no need to re-backup the recovery image). Reboot into recovery and you can make a nandroid backup.
While it's true that the first link you provided will indeed give you the recovery image to be able to do a nandroid backup, if that is all you want to do, there's really no reason to go through all the steps of rooting your phone (this may change in the future if flashrec stops working with an update from Sprint/HTC - we may even be forced to do a goldcard method at some point in the future if they do something like they did to the gsm Android phones).
Click to expand...
Click to collapse
So, how do I install flashrec and "apply" the Amon-Ra recovery image? Sorry, but I just got my first Android phone this morning. LOL! And I want to explore all possibilities of what my new toy can do. But I'm not quite sure how to do either of those things.
You Can Root the New O.T.A. Update manually only.
I have a Sprint Hero and to get the OTA Update I had to get the Original RUU file and install it. Then I did the OTA update but the key thing is Amon Ra image and flashrec WILL NOT WORK.
What Does work is:
1. From the home Screen Go to Settings>Applications>Development Check your USB Debugging Mode and Stay awake boxes
(This is just getting set up to use the Android SDK. Im sorry for all the experience folks Im just going step by step for thoroughness)
2) From the Desktop Computer Get to your command prompt and Follow the steps Below:
3. Open the Command Prompt and type the following (hitting enter at the end of every line):
cd\
cd AndroidSDK\Tools\
adb devices
And make sure your phones’s serial number pops up (if not redo section I).
4. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
5. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
Thats It..After you get the message "ENJOY THE SHELL and get the # sign, IF YOU ENTER EVERYTHING CORRECTLY EXACTLY WHAT YOU TYPED WELL SHOWS UP BELOW WHERE YOU TYPED IT!!)
ROOT USER Programs seem to work but the (PowerButton/ Home Button pressing combination still hangs at "HTC") which is where somehow the Green menu screen is supposed to be. And the NANDROID Backup is supposed to be. If anyone knows how to get this to work or to prevent the Hero from hanging please let us know.
Related
Hello. I'm really new to the g1, I got it just two weeks ago, and right now I have JFv1.50 ADP1.5 installed right now. I'm not familiar with many of the technical terms, but I'm starting to understand everything.
I went through the root process, trying to follow some guide using a root.apk application to download/ install the right files, but it bricked my phone. I was able to manually get it to JFv1.50 ADP1.5 later on though.
Now my problem is that I believe I still have the normal recovery image on the phone. In recovery mode there is a picture of an exclamation mark in a triangle.
So I figured I'd go try to use JF's 1.43 recovery image. I put the zip on my SD card and renamed it update.zip. When I go into recovery mode now, though, and press ALT+S, I see the installation/ update bar pop up for like 3 seconds, enough for the orange progress bar to move a few millimeters, and then it just stops. No error message or anything.
I tried installing the test keys recovery image also, but it didn't work at all.
I really need JF's recovery image though, so I can make backups etc.
I've searched for this, but the closest problem I can see is this one:
http://forum.xda-developers.com/archive/index.php/t-505950.html
But for me, I don't even get an error message when using the update.zip...
Sorry for my lack of technical knowledge here, but try to bear with me
Thanks for any help you can give me!
The cooked roms are signed with testkeys, so the original recovery mode will refuse to flash them. You'll have to get the recovery image modified by JF and flash it. The latest version is included in JF v1.43. You can find recovery.img in a folder called data in that zip.
Copy it to your sdcard or adb push it to somewhere on the phone. Then type these commands on the phone:
su
flash_image recovery /path/to/recovery.img
You must have root in order to do this. Alternatively, you can push the file to /system and the init script will flash it for you the next time you boot.
billc.cn said:
The cooked roms are signed with testkeys, so the original recovery mode will refuse to flash them. You'll have to get the recovery image modified by JF and flash it. The latest version is included in JF v1.43. You can find recovery.img in a folder called data in that zip.
Copy it to your sdcard or adb push it to somewhere on the phone. Then type these commands on the phone:
su
flash_image recovery /path/to/recovery.img
You must have root in order to do this. Alternatively, you can push the file to /system and the init script will flash it for you the next time you boot.
Click to expand...
Click to collapse
Thanks so much! I couldn't figure this out until now. It's working perfectly now.
Feel free to close this thread. Thanks again
Been reading lots of guides and forum posts in preparation to getting my stock G1 all did up, just wanted to clear a couple things up
I'll probably be installing the jf 1.5 firmware,
Just to be sure:
1) once I have a rooted RC29 installed, I can install hardspl, and then install the JF firmware version I want?
2) What's the difference between the jf 1.5 US rom and the jf 1.5 ADP rom, I assume the ADP is the dev phone version, but can it be/is it worth it to install it on a normal G1?
3) In the wiki it says this about rooting:
On RC29 phones and lower, a huge exploit existed where anything you typed into your keyboard was also being run in a hidden console with root permissions.
1. Download recovery.img and copy it to your SD card (see the previous section on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
If I'm just going to be installing the JF firmware immediately, do I really need to do step 8? - what does that get you?
Thanks for the help, I suspect probably these questions have been answered before, so if you've got links to those answers, please do post.
1- Never installed hardspl :-S Haykuro's wipes your ROM, as in, you have to boot in to recovery and reinstall your ROM, but hardspl is probably different. Hard SPL is an optional step really, I never installed it. If you're not going to use fastboot, you don't need it, and you can always install it later when you find out more about it and actually need it.
2- Yeah ADP is the dev phone version. There are hardly any themes for the US version but loads for ADP. Not really sure of the other differences, I don't think ADP has the amazon mp3 store.
3- Step 8 is what installs your custom recovery image, so when you hold down home+power it will give you the options to wipe and flash your phone. Without the recovery image, you can't install a ROM.
hospadar said:
Been reading lots of guides and forum posts in preparation to getting my stock G1 all did up, just wanted to clear a couple things up
I'll probably be installing the jf 1.5 firmware,
Just to be sure:
Click to expand...
Click to collapse
1) once I have a rooted RC29 installed, I can install hardspl, and then install the JF firmware version I want?
Yes
2) What's the difference between the jf 1.5 US rom and the jf 1.5 ADP rom, I assume the ADP is the dev phone version, but can it be/is it worth it to install it on a normal G1?
ADP is the developers version and US has MyFaves. ADP takes up less system space.
3) If I'm just going to be installing the JF firmware immediately, do I really need to do step 8? - what does that get you?
You DEFINITLY want the SPL. In fact, use my signature to acquire the 1.4 recovery so you can install any zip from the sdcard, create backups with Nandroid and restore in case you mess something up later on. Without it, it's a hassle and time consuming.
I am running a 1839 US 0089 Thinkpad Tablet w/Clockwork Recovery and want to restore back to my stock recovery to allow my ICS upgrades to go off w/o a hitch.
Since Lenovo sucks in that it does incremental patches/updates vs a full updates.zip build, can we extract this from an update build and push to our devices?
i have not seen much info on this on the interwebz. i have several nandroid backups but of course those where taken using CWR, ie vicious circle..
if i find out any info, i'll post updates here too. :good:
TIA!
UPDATE: on ICS! see notes below and link to thread that helped me get there!
this post: http://forum.xda-developers.com/showthread.php?t=1741623
resolved all of my issues! power button replaced and the new button looks much more beefier (reinstalled my gobi card after getting back from lenovo).
they did reset software BUT they did not restore the stock recovery image. grr.. anywho, for anyone interested i made notes on what i did to finally get on ICS. i recommend doing a factory reset after updating to ics too. helped w/my inital lag issues.
(my notes from in that post )
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again.
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip
close but not there yet..
Noticed on this thread an uninstall actions given you backed up the install-recovery.sh (which of course i didn't, doh!)
http://forum.xda-developers.com/showpost.php?p=21962380&postcount=1
I am running CWR 64gb version (US) and ran these commands via commandline and adb:
adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
the "cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh " action came back with a file does not exist but i continued but now seem to have NO recovery. I am able to boot into Honeycomb no probs and can do any adb task i need. i have since repushed the cwr recovery.
any thoughts my TPT geeks?
i have a totally new approach on this. i have a work TPT (same exact model and build) that is 100% stock. i plan to try to temp boot to CWR on it w/o installing it and capturing a nandroid of it.
once i have a full 100% stock 0089 US nandroid and can confirm it updates to ICS, i will post a link to it (if that is kosher w/xda, i'll have to re-read the forum rules again)
seamonkey420 said:
Noticed on this thread an uninstall actions given you backed up the install-recovery.sh (which of course i didn't, doh!)
http://forum.xda-developers.com/showpost.php?p=21962380&postcount=1
I am running CWR 64gb version (US) and ran these commands via commandline and adb:
adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
the "cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh " action came back with a file does not exist but i continued but now seem to have NO recovery. I am able to boot into Honeycomb no probs and can do any adb task i need. i have since repushed the cwr recovery.
any thoughts my TPT geeks?
Click to expand...
Click to collapse
If you download the 89 update from the lenovo download site, you can pull the files you need from it.
However, I just updated to ICS with CWR on my tablet and now have ICS (with stock recovery).
no luck here on my end. i have a nandroid backup from after applying 89 updates and made sure not to remove any items. however my power button my tpt just broke and i think i even have a working update.zip i resigned (removed the indigo checks) but now can't test.
guess i'm waiting for ICS until i get my tpt fixed up.
UPDATE:
called lenovo support about power button and also inquired on reloading software/if i get same motherboard in tablet (which i do). Lenovo will be reloading my tpts rom to the stock rom after button fixing. gotta send it in but i got it through work so i have the awesome ez-warranty so perhaps (if you can wait and don't mind losing all data) others that are having upgrades may be able to send in their tpts. i honestly wish lenovo would just create a full/stock ICS rom that us w/issues updating can push via adb. i'll see if i can get that nandroid made of a stock ICS USA TPT (1839) w/o having to put on cwr but temp unrooted once mine's back.
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.
planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.
Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.
Going well so far...had an issue but figured it out.
Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.
Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?
Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/
I plan to make a complete backup of the device so I can restore to stock and receive OTAs in the future. I would like to outline my intended process and hope a more seasoned community member will QC.
Step 1: Boot TWRP and perform a full backup
While in fastboot, run:
Code:
fastboot boot <twrp.img>
Navigate TWRP and perform full backup
Step 2: Root the Device via Magisk (or superSU if you desire):
See other threads for rooting
Step 3: Determine what partition recovery is located on:
Using ADB -> shell, run:
Code:
su
Grant root access and run:
Code:
ls -l /dev/block/*/by-name
Find the partition labelled recovery, note the path
Step 4: Extract the recovery and package into an image file:
Using ADB -> shell, run:
Code:
dd if='/dev/block/mmcblk0p<#>' of='/sdcard/stock_reco.img'
With this, if I want to go back to stock, I can restore the unrooted factory ROM with TWRP and flash the stock recovery with fastboot.
What is the communities thoughts?
I would love this ability too, sadly found nothing on forum that's even close, stock available once you have worked out at which update your bootloader is at.
Why lenovo/motorola decided on different model versions around the world seems crazy, surely easier for production and marketing to make international, especially supplying updates for OS.
Rant over.
sednafx said:
I plan to make a complete backup of the device so I can restore to stock and receive OTAs in the future. I would like to outline my intended process and hope a more seasoned community member will QC.
Step 1: Boot TWRP and perform a full backup
While in fastboot, run:
Code:
fastboot boot <twrp.img>
Navigate TWRP and perform full backup
Click to expand...
Click to collapse
Hi,
If you like "restore to stock and receive OTAs"...
Please, advise that you need to backup all of these partitions: BOOT, SYSTEM, OEM and RECOVERY. Not all TWRP versions will backup all!
Futhermore, if you will like to do a downgrade, then you need to backup all other parts.
I hope this helps to newbies!
manos78 said:
Hi,
If you like "restore to stock and receive OTAs"...
Please, advise that you need to backup all of these partitions: BOOT, SYSTEM, OEM and RECOVERY. Not all TWRP versions will backup all!
Futhermore, if you will like to do a downgrade, then you need to backup all other parts.
I hope this helps to newbies!
Click to expand...
Click to collapse
I would like to backup the full partition table. Please let me know what steps I am missing. TWRP should backup boot, and system. I understand recovery may need done separately.
sednafx said:
I plan to make a complete backup of the device so I can restore to stock and receive OTAs in the future. I would like to outline my intended process and hope a more seasoned community member will QC.
Step 1: Boot TWRP and perform a full backup
While in fastboot, run:
Code:
fastboot boot <twrp.img>
Navigate TWRP and perform full backup
Step 2: Root the Device via Magisk (or superSU if you desire):
See other threads for rooting
Step 3: Determine what partition recovery is located on:
Using ADB -> shell, run:
Code:
su
Grant root access and run:
Code:
ls -l /dev/block/*/by-name
Find the partition labelled recovery, note the path
Step 4: Extract the recovery and package into an image file:
Using ADB -> shell, run:
Code:
dd if='/dev/block/mmcblk0p<#>' of='/sdcard/stock_reco.img'
With this, if I want to go back to stock, I can restore the unrooted factory ROM with TWRP and flash the stock recovery with fastboot.
What is the communities thoughts?
Click to expand...
Click to collapse
OP, did you ever get an answer on this? I'm interested in using block copy as well to pull down a complete stock image.
I have researched this topic and from what I can gather, you have to be rooted to pull the block level data on system etc. I haven’t found a full tutorial to complete what I am trying to do.
sednafx said:
I have researched this topic and from what I can gather, you have to be rooted to pull the block level data on system etc. I haven’t found a full tutorial to complete what I am trying to do.
Click to expand...
Click to collapse
There was an option in TWRP to backup recovery. I haven’t tested if I restore everything... Can I get back OTAs.
I'm interested in doing the same thing. It seems there are no stock images for my XT1683 on NPN25.127.33 and I don't want to risk bricking it by eventually flashing the wrong image and taking a OTA. So the obvious solution would be to backup my own stock image. I've looked around and found the following thread and command:
https://forum.xda-developers.com/showthread.php?t=1758326
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
I can't be sure, but it would seem this could be used to backup the entire partition set (including OEM as well as the stock recovery and bootloader). Even if there's no root access, one could boot into TWRP from fastboot and issue the command (exactly like OP's step 1). Do you think it would be possible to take this backup, restore it at a later date and still be able to take an OTA with no issues?
I also would like to know this. Or if a stock ROM is available for XT1684 NPNS25.137-33-11 as I've searched and had no luck.
Thanks.