Recovery Image Errors - G1 General

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

Related

All I want to do is use nandroid backup.

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.

Noobie Question about ICS

I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
I used the version available on Rootzwiki... not sure if thats the answer you wanted. I'm running 4.0.3 ICS on my wifi XOOM OC to 1.54. No FC's, reboots or anything of the sort. You'll need to be sure that you have su-install.zip, and other img files needed. As I said, you'll find them all on the rootzwiki website under xoom hope this helps, if not good luck.
You are talking about two different things here. I don't know where to start here you're all mixed up. There are several ways to flash a ROM, you can fastboot flash the .img files such as what you are referencing to. Or you can flash an update .zip file from recovery. The way you flash the ROM depends on the source, if its a bunch of *.img files you use fastboot, if it's a *.zip file you use recovery. Just follow the directions given for installation that are provided with the ROM you are downloading.
sboehler said:
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
Click to expand...
Click to collapse
Hello, and welcome to XDA! =] Anyways on with your question. There are two ways to flash a ROM to your xoom. One being fastboot/adb, where you use the command line on your computer to send commands to your device and make it do stuff. This is where you use system.img, boot.img, recovery.img.
The second, is CWM (ClockWorkMod recovery) This, as far as im aware, is the most common way. This is where the .zip's come in. Because you take the .zip you put it on your external SD card. boot into recovery (after flashing CWM of course) and flash the rom. CWM is nice because you can also make a 100% snapshot of your internal memory state via making a nanodroid back up. That way if anything messes up you have a 100% backup you can restore at anytime if you need it.
In a nutshell, You use *.img files with fastboot and .zip files with CWM.
Anyways. If you're new to rooting. Please check out these two threads, They'll help you get started. =]
Xoom Heaven: Root+Non Root Users Are Welcome!
[Guide] Setting up and using adb/fastboot-unlock, flash custom recovery & root
The second guide I did use to flash my own zoom so I can assure you it does work.

MOTOACTV ROMs

Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.

[Q]OTA KitKat Update Failed, won't complete boot process now.

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/

HELP: Problems with factory reset

CONTEXT: My phone no longer charges (USB port doesn't work), but I have insurance. VZW sent me a replacement phone and I need to send back the old phone after doing a factory reset. The phone won't factory reset and I need your help. I think this will be an easy one for you guys. Here is my sense of the problem. I rooted the phone when I got it right away right after it was released aprox 2.5 years ago. I downloaded the classic root files like Clockworkmod, Wanam Xposed, Titanium Backup, Busy Box Pro, ROM Manager, ROM Installer, ROM Toolbox Pro, Root Explorer, Super SU, ...etc. After that I never changed the ROM. So I still have OEM ROM with lots of app updates. I did change the recovery.img in order to use one of those apps. I think it was to use Clockworkmod. Anyways now when I go to factory reset the phone it says it is missing the recover.img file. My sense is if I put back that file on my phone in the right spot it will then allow me reset to stock. Does that sound right? If so how do I do that? If not what else should I try consider? Grateful for any help I can get! THANK YOU in advance.
Things are really dead around here as you can tell by the lack of responses, but to answer your question the only way to restore unrooted stock is by downloading the stock firmware and using ODIN. The recovery img file is in that firmware too. I suggest getting your USB port fixed or you are screwed. If you do that, then follow these steps:
Download stock firmware here: http://www.sammobile.com/firmwares/database/SM-N900V/
Download ODIN here: https://mega.nz/#!nZoThZ5a!TrPzLGDrtQJSmJfH8UkOFAkfc9wSLl_lPhrVusQoRJ8
After you unpack the zip files, turn off your phone. Then hit the power, home and volume down buttons all at the same time for download mode. Confirm by hitting volume up as instructed. Plug the phone into your PC and open ODIN. You should see the COM port open. Next select the AP option, then browse to the file you unzipped the firmware to. Double click and wait until the md5 is done being verified. Hit start and wait, it takes about 4 or 5 minutes. Once it's finished and the phone starts rebooting, unplug the phone and pull the battery (you don't want to let it boot all the way or you'll get FCs out the ying yang). Now replace the battery, boot into stock recovery by hitting power, home and volume up all at the same time. Recovery will come up and then do your factory reset. You should be good to go after that.
ArtfulDodger said:
Things are really dead around here as you can tell by the lack of responses, but to answer your question the only way to restore unrooted stock is by downloading the stock firmware and using ODIN. The recovery img file is in that firmware too. I suggest getting your USB port fixed or you are screwed. If you do that, then follow these steps:
After you unpack the zip files, turn off your phone. Then hit the power, home and volume down buttons all at the same time for download mode. Confirm by hitting volume up as instructed. Plug the phone into your PC and open ODIN. You should see the COM port open. Next select the AP option, then browse to the file you unzipped the firmware to. Double click and wait until the md5 is done being verified. Hit start and wait, it takes about 4 or 5 minutes. Once it's finished and the phone starts rebooting, unplug the phone and pull the battery (you don't want to let it boot all the way or you'll get FCs out the ying yang). Now replace the battery, boot into stock recovery by hitting power, home and volume up all at the same time. Recovery will come up and then do your factory reset. You should be good to go after that.
Click to expand...
Click to collapse
Thanks - is there any way to do this without the USB port? I can still get new files to the phone via the MicroSD card. Or use Root explorer to mess with all the files on the phone.
mozenter said:
Thanks - is there any way to do this without the USB port? I can still get new files to the phone via the MicroSD card. Or use Root explorer to mess with all the files on the phone.
Click to expand...
Click to collapse
Refer to this thread: http://forum.xda-developers.com/showthread.php?t=2426162. But keep in mind, your bootloader MUST be unlocked to use mobile ODIN. If you are on KK 4.3 & up, I think you might be SOL.
ArtfulDodger said:
Refer to this thread: http://forum.xda-developers.com/showthread.php?t=2426162. But keep in mind, your bootloader MUST be unlocked to use mobile ODIN. If you are on KK 4.3 & up, I think you might be SOL.
Click to expand...
Click to collapse
Thanks I apprecaite the effort! I tried Mobile Odin. I purchased Mobile Odin Pro, but it doesn't work with VZW variant of Galaxy Note 3. Any other ideas? Thanks again for all the help!
mozenter said:
Thanks I apprecaite the effort! I tried Mobile Odin. I purchased Mobile Odin Pro, but it doesn't work with VZW variant of Galaxy Note 3. Any other ideas? Thanks again for all the help!
Click to expand...
Click to collapse
Sorry, sounds like without that USB port you are stuck with that phone then unless you can get it repaired. Thanks for the update, I kind of wondered if anything got resolved. Good luck!
ArtfulDodger said:
Sorry, sounds like without that USB port you are stuck with that phone then unless you can get it repaired. Thanks for the update, I kind of wondered if anything got resolved. Good luck!
Click to expand...
Click to collapse
One last attempt to get this fixed. I really just need to know where the recovery imagine is located in the note 3. Here again is a quick summary of the issue. I also just posted in the CWD thread.
"I have a Galaxy Note 3. I successfully put CWD on it when I purchased it several years ago. The USB port no longer charges the phone. I have insurance with VZW, but I need to send the phone back in stock. I can't put the phone back in stock because I have the CWD recovery image is in there. I recall I left the old recovery image on the phone and just changed the extension. So all I need to do to fix the phone is go back into the folder where the recovery image is and delete the CWD image and change original image extension back to its original form (which I think is IMG). The problem is I don't where on the phone these recovery images are. Can anyone help me with this situation? Thanks!!!"
mozenter said:
One last attempt to get this fixed. I really just need to know where the recovery imagine is located in the note 3. Here again is a quick summary of the issue. I also just posted in the CWD thread.
"I have a Galaxy Note 3. I successfully put CWD on it when I purchased it several years ago. The USB port no longer charges the phone. I have insurance with VZW, but I need to send the phone back in stock. I can't put the phone back in stock because I have the CWD recovery image is in there. I recall I left the old recovery image on the phone and just changed the extension. So all I need to do to fix the phone is go back into the folder where the recovery image is and delete the CWD image and change original image extension back to its original form (which I think is IMG). The problem is I don't where on the phone these recovery images are. Can anyone help me with this situation? Thanks!!!"
Click to expand...
Click to collapse
The recovery image is the recovery partition and you have overwritten it. You MAY be able to dig an image out of a firmware such as founf on sammobile but you still need a way to flash it. Without an unlocked bootloader or USB port.. I believe you're out of luck. You should simply send the phone back to VZW... I seriously doubt the shop it really goes to cares if it's stock or not.
Sent from my SM-N900V using Tapatalk
I'm sorta confused.
If it was rooted a few years ago & it was a retail device, a "true" replacement recovery (e.g. CWM) wouldn't boot because of the Samsung signing checks. This isn't a Developer Edition device, is it?
If it had SafeStrap installed, then:
- that already comes with a pseudo-recovery which is a mod of TWRP.
- the whole thing boots out of /system using the stock boot partition, and all it's magic happens inside of /system (with some loopback blobs for the non-stock slots stored in /data)
Does the OP know that a "factory reset" is an Android misnomer? There is no "resetting" back to factory of a device which has had customization of the /system partition. That has to be done either manually or through restoration of backups. The android "Factory Reset" only wipes the /data file system. It doesn't magically repair random customizations to /system, and that's what causes the "Custom" icon during boot.
About the only way I can think that the OP can resolve this is if he happens to have a Safestrap (pseudo-) TWRP backup of the stock slot. I guess the approach would be to:
- get the correct release "recovery.img" file out of the Odin Stock tarball, and "dd" it to the recovery partition ( mmcblk0p15 on the SM-N900V)
- restore the original, virginal "stock slot" backup onto the stock slot from the Safestrap+TWRP backup
- make sure to set the active slot to the stock slot
- reboot, go back into Safestrap recovery and:
- delete all other slots
- uninstall Safestrap.
This of course would only be feasible if the stock slot backup was taken immediately after installation of SafeStrap, so it's uninstall would restore /system to approximately the same condition as Stock. Maybe after running that ROM for a little bit the TIMA attribution would revert the "Custom" status indicator. It might even allow a download of an OTA.
There is another method of restoring to stock without USB that I can think of, but it would involve the bootloader unlock and booting a real (true) custom recovery, which would blow the Knox Warranty bit, so - given the OP's desires - I don't see much point in it.
donc113's comments should be considered as well: what is the chance that the warranty returns department is going to "go all CSI" on your returned phone? They probably have to deal with hundreds of dead phones per day. I suppose it depends a bit on luck and who is doing the warranty returns, but there have been more than one person on XDA report "I just returned the phone in it's trashed state and didn't bother to clean anything up, and no complaints."
good luck
donc113 said:
The recovery image is the recovery partition and you have overwritten it. You MAY be able to dig an image out of a firmware such as founf on sammobile but you still need a way to flash it. Without an unlocked bootloader or USB port.. I believe you're out of luck. You should simply send the phone back to VZW... I seriously doubt the shop it really goes to cares if it's stock or not. Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I have an unlocked bootloader, but no USB port. So any ideas you have would greatly be apprecaited. VZW cares a lot. It will cost me $300 if I can't fix it.
mozenter said:
I have an unlocked bootloader, but no USB port. So any ideas you have would greatly be apprecaited. VZW cares a lot. It will cost me $300 if I can't fix it.
Click to expand...
Click to collapse
Did you unlock the bootloader or is that the way it came? Since you put CWM on it a long time ago... I would think that it's a developer edition and if so... It will be engraved inside with "Developer Edition" under the battery.
If it is a developer edition.... To the best of MY knowledge (i certainly could be wrong) Verizon never sold them... Only Samsung did... Thus Verizon never had a warranty on it.
But, no matter what version it is, since you loaded a non VZW recovery...you can not put back 100% to stock because the "warranty fuse" is blown and can not be reset.
I presume you have tried Odin to flash a stock firmware load that includes stock recovery but that requires the USB port be working (but doesn't require the charge circuit to work).
Beyond Odin... I have no other ideas.
Sent from my SM-N900V using Tapatalk
mozenter said:
I have an unlocked bootloader, but no USB port. So any ideas you have would greatly be apprecaited. VZW cares a lot. It will cost me $300 if I can't fix it.
Click to expand...
Click to collapse
Read this all the way through - twice at a minimum. You should understand how and why every step works before you begin. You should also verify md5 signatures of any files transferred around from place to place. (busybox and twrp both have "md5sum" command). You know - compute the MD5's after extracting them from the Odin archives, and then verify the same md5 sigs after you move/copy them to the phone /sdcard
Your idea that a "factory reset" with the stock recovery alone is going to return your phone back to factory stock is not sound.
You can rewrite the /system partition by booting into a custom recovery and using one other small trick*. If you were to then also overwrite the recovery partition with the stock recovery in the same (custom recovery boot) session, you would be able to:
1) boot into the stock recovery and
2) use the stock recovery (and a stock /system) to perform a factory reset.
This would give you a completely stock phone that has been factory reset, but with one small flaw: that your Knox warranty flag was blown to 0x1. (From everything you've said we think it is already blown, though)
twrp-3.0.2-0-hltevzw-4.3.img dd'ed into the recovery partition will let you do these operations via a terminal command session from the screen of the phone. No USB port needed, no ADB needed. All you will need to do is get the .img files onto the phone, either with a SDcard or wirelessly on a LAN/dropbox, etc.
0) Get the Stock Odin Tarball corresponding to your (rooted) ROM release (e.g. sammobile.com) ; use "tar" or 7-zip to extract "recovery.img" and "system.img" from this tarball.
1) Download twrp-3.0.2-0-hltevzw-4.3.img from twrp.me and get it onto your /sdcard (internal)
2) Get the stock "recovery.img" file (from the Odin tarball) onto your phone's /sdcard
*3) Convert the "system.img" file (from the Odin tarball) into a non-sparse system image file via the "simg2img" command, e.g.
<Unix-prompt>$ simg2img system.img system-nonsparse.img
I don't know if the Windows version of Google/Android developer tools has the "simg2img" tool; if not you are going to have to do this in a Linux VM (e.g. Ubuntu).
4) Get the latter file ("system-nonsparse.img") onto your phone /sdcard
5) From a root shell (in your current rooted ROM, use a terminal emulator and type "su" to get a root prompt)
dd if=/sdcard/twrp-3.0.2-0-hltevzw-4.3.img bs=2048 of=/dev/block/mmcblk0p15
this installs the custom TWRP recovery to your recovery partition
6) Boot into the TWRP recovery. Using Advanced->Terminal in TWRP, then:
7) dd if=/sdcard/recovery.img bs=2048 of=/dev/block/mmcblk0p15
(this step puts the stock recovery back onto the phone)
8) dd if=/sdcard/system-nonsparse.img bs=2048 of=/dev/block/mmcblk0p23
(this step puts the full stock /system back onto the phone)
9) Do a "reboot recovery" in TWRP. This will put you into the stock recovery, from which you can do a full factory wipe.
Voila! Factory Firmware and wiped - but with a blown Knox Warranty flag.
* the "one other small trick" is to convert the "system.img" file found in the stock Odin tarball to a non-sparse image using the Android tool "simg2img". Normally this unpacking job is handled by the bootloader when Odin is uploading the (sparse) system.img file to the phone, but you would be putting system.img back onto the phone by raw-writing it with "dd" the same way you would manually flash a recovery image to the recovery partition (using "dd").
The thing is, based on everything you have said so far, your phone already has a blown Knox Warranty flag. (Either that or you had a Developer Edition phone, or are confused about the difference between a true custom recovery and a fake one that lives inside safestrap). But what the heck, if that's the case, at least the phone will look fully stock if it is booted normally, and that's at least a little bit of an improvement.
This won't fix the Knox Warranty fuse; the only thing it will fix is the appearance of the "Custom" icon during booting. (Getting this to go away might even require booting the fully reset stock ROM and letting it run for a while as well so that the stock attribution processes can complete).
If you do this, you have to understand the whole process all the way through, as you will only have one chance at it. As soon as you have re-written the /system partition and put the stock recovery back on the phone, root is gone at that point. (Additionally note that step 8 CAN NOT be accomplished with the normal ROM booted - it can only be done from a custom recovery. You will lock up the system and the write will fail if you try it from the "regular" ROM.)
good luck.
bftb0 said:
Read this all the way through - twice at a minimum. You should understand how and why every step works before you begin. You should also verify md5 signatures of any files transferred around from place to place. (busybox and twrp both have "md5sum" command). You know - compute the MD5's after extracting them from the Odin archives, and then verify the same md5 sigs after you move/copy them to the phone /sdcard
Your idea that a "factory reset" with the stock recovery alone is going to return your phone back to factory stock is not sound.
You can rewrite the /system partition by booting into a custom recovery and using one other small trick*. If you were to then also overwrite the recovery partition with the stock recovery in the same (custom recovery boot) session, you would be able to:
1) boot into the stock recovery and
2) use the stock recovery (and a stock /system) to perform a factory reset.
This would give you a completely stock phone that has been factory reset, but with one small flaw: that your Knox warranty flag was blown to 0x1. (From everything you've said we think it is already blown, though)
twrp-3.0.2-0-hltevzw-4.3.img dd'ed into the recovery partition will let you do these operations via a terminal command session from the screen of the phone. No USB port needed, no ADB needed. All you will need to do is get the .img files onto the phone, either with a SDcard or wirelessly on a LAN/dropbox, etc.
0) Get the Stock Odin Tarball corresponding to your (rooted) ROM release (e.g. sammobile.com) ; use "tar" or 7-zip to extract "recovery.img" and "system.img" from this tarball.
1) Download twrp-3.0.2-0-hltevzw-4.3.img from twrp.me and get it onto your /sdcard (internal)
2) Get the stock "recovery.img" file (from the Odin tarball) onto your phone's /sdcard
*3) Convert the "system.img" file (from the Odin tarball) into a non-sparse system image file via the "simg2img" command, e.g.
<Unix-prompt>$ simg2img system.img system-nonsparse.img
I don't know if the Windows version of Google/Android developer tools has the "simg2img" tool; if not you are going to have to do this in a Linux VM (e.g. Ubuntu).
4) Get the latter file ("system-nonsparse.img") onto your phone /sdcard
5) From a root shell (in your current rooted ROM, use a terminal emulator and type "su" to get a root prompt)
dd if=/sdcard/twrp-3.0.2-0-hltevzw-4.3.img bs=2048 of=/dev/block/mmcblk0p15
this installs the custom TWRP recovery to your recovery partition
6) Boot into the TWRP recovery. Using Advanced->Terminal in TWRP, then:
7) dd if=/sdcard/recovery.img bs=2048 of=/dev/block/mmcblk0p15
(this step puts the stock recovery back onto the phone)
8) dd if=/sdcard/system-nonsparse.img bs=2048 of=/dev/block/mmcblk0p23
(this step puts the full stock /system back onto the phone)
9) Do a "reboot recovery" in TWRP. This will put you into the stock recovery, from which you can do a full factory wipe.
Voila! Factory Firmware and wiped - but with a blown Knox Warranty flag.
* the "one other small trick" is to convert the "system.img" file found in the stock Odin tarball to a non-sparse image using the Android tool "simg2img". Normally this unpacking job is handled by the bootloader when Odin is uploading the (sparse) system.img file to the phone, but you would be putting system.img back onto the phone by raw-writing it with "dd" the same way you would manually flash a recovery image to the recovery partition (using "dd").
The thing is, based on everything you have said so far, your phone already has a blown Knox Warranty flag. (Either that or you had a Developer Edition phone, or are confused about the difference between a true custom recovery and a fake one that lives inside safestrap). But what the heck, if that's the case, at least the phone will look fully stock if it is booted normally, and that's at least a little bit of an improvement.
This won't fix the Knox Warranty fuse; the only thing it will fix is the appearance of the "Custom" icon during booting. (Getting this to go away might even require booting the fully reset stock ROM and letting it run for a while as well so that the stock attribution processes can complete).
If you do this, you have to understand the whole process all the way through, as you will only have one chance at it. As soon as you have re-written the /system partition and put the stock recovery back on the phone, root is gone at that point. (Additionally note that step 8 CAN NOT be accomplished with the normal ROM booted - it can only be done from a custom recovery. You will lock up the system and the write will fail if you try it from the "regular" ROM.)
good luck.
Click to expand...
Click to collapse
Thanks you rock. I REALLY appreciate the effort. I fully realize that Knox won't be fixed. This is NOT a developer phone. These instructions a little over my head as I'm not that experienced with custom ROMs. I have really only dabbled a little bit with my last few phones.
mozenter said:
Thanks you rock. I REALLY appreciate the effort. I fully realize that Knox won't be fixed. This is NOT a developer phone. These instructions a little over my head as I'm not that experienced with custom ROMs. I have really only dabbled a little bit with my last few phones.
Click to expand...
Click to collapse
There is a possibility... That there is a script called install_recovery.sh or install_original_recovery.sh in your /system/etc directory. You must have root to execute them IF they even exist.
It depends on when and how CWD was installed.
Sent from my SM-N900V using Tapatalk

Categories

Resources