Database Info

[Q] recovery.img and recovery-from-boot.p

Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron

I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R

Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.

Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.

Was going to ask a dumb question but I figured it out

i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss

recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.

jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..

Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?

I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?

I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?

well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.

Android rescue.zip project..

So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.

I generally do a backup before doing any modding and just reflash from the start and do a restore.

projectsome said:
I generally do a backup before doing any modding and just reflash from the start and do a restore.
Click to expand...
Click to collapse
yup most of the time restoring just boot.img fixes a bootloop

Usually you can just reflash the rom .zip without wiping user data and your data will remain intact and your phone will continue functioning normally if the problem is due to corrupted system files or kernel.
Sent from my LG-P920 using Tapatalk 2

Thread will be locked until, there is further progress made.
@OP PM me when when there is an update.

workaround for crashing links (build.prop)

Hello,
as many may have noticed with the new stock ICS ROM there are some issues regarding links, e.g. WhatsApp crashes if you click on a link etc. and there is a quick fix/workaround for it (you need write access to /system however).
Investigating the crash report it became clear that the issue is related to the Htc Linkify Dispatcher which was (as I understand it) implemented by HTC to comply with some apple patent-related stuff and to strip the device of Android's original abilities regarding the handling of links (more info e.g. on [1] )
So normally the device will have a running Htclinkifydispatcher.apk and in addition a build.prop setting indicating this "feature". With the ICS ROM however the build.prop says that the feature is enabled but a quick check in /system shows that the Htclinkifydispatcher.apk is not installed, so consequently this means that apps relying on build.prop will fail when handling links (as the dispatcher is not active).
The logical solution seems to be to adapt the build.prop accordingly. After a quick search I found the necessary steps to be the following (Source: [2]):
In the /system/build.prop file search for ro.da1.enable=true and set it to ro.da1.enable=false
Add ro.da1.method=false directly under it
Reboot
I performed these steps and now am able to click on links in WhatsApp again without crashes. Maybe this will help someone else as well.
Cheers
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
[2] androidcentral.com / how-restore-functionality-apple-v-htc-war-has-taken-away-root
Sorry for the awkwardly typed web URLs but I do not yet have the privilege to post outside links, so maybe some mod can fix it

some moderator should make this sticky.

yes this is the exact problem i encountered, in every apps except internet.. -.-
thanks!

nice guide everything ok now! :victory:

Thanks for this workaround. However I noticed that I no longer have an option called something like "Aplications associations" under Settings menu. It was just below "Applications"... Do you think is related to the modification?

I think yes...
From what I have understood reading
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
the Apple patent is that when you click on a link (or something recognised usefull data...) a popup menu appear letting you choose what to do.
HTC removes that ability and using Htclinkifydispatcher.apk with "Application Association" gives you the choice (but only one...) of what to do on a specific type of link.
Since the workaround we are talking here needs rootted phones, could be also another solution to put in /system/app the Htclinkifydispatcher.apk and leaves build.prop as it is (to stop crash on link) ?

fblasot said:
I think yes...
From what I have understood reading
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
the Apple patent is that when you click on a link (or something recognised usefull data...) a popup menu appear letting you choose what to do.
HTC removes that ability and using Htclinkifydispatcher.apk with "Application Association" gives you the choice (but only one...) of what to do on a specific type of link.
Since the workaround we are talking here needs rootted phones, could be also another solution to put in /system/app the Htclinkifydispatcher.apk and leaves build.prop as it is (to stop crash on link) ?
Click to expand...
Click to collapse
thanks for this, it works
where can we get the correct htclinkifydisptcher.apk that will work on the stock desire s ics rom?
can you post a link please

I don't have a link but you could try to extract the apk from any HTC ICS sense 4 original rom.
Anyway, I read in an other discussion that also with this apk there are some limits and then the mod of build.prop it is the better solution.

Who's awesome? You are
Worked for me! Thanks dude!
hahnbanach said:
Hello,
as many may have noticed with the new stock ICS ROM there are some issues regarding links, e.g. WhatsApp crashes if you click on a link etc. and there is a quick fix/workaround for it (you need write access to /system however).
Investigating the crash report it became clear that the issue is related to the Htc Linkify Dispatcher which was (as I understand it) implemented by HTC to comply with some apple patent-related stuff and to strip the device of Android's original abilities regarding the handling of links (more info e.g. on [1] )
So normally the device will have a running Htclinkifydispatcher.apk and in addition a build.prop setting indicating this "feature". With the ICS ROM however the build.prop says that the feature is enabled but a quick check in /system shows that the Htclinkifydispatcher.apk is not installed, so consequently this means that apps relying on build.prop will fail when handling links (as the dispatcher is not active).
The logical solution seems to be to adapt the build.prop accordingly. After a quick search I found the necessary steps to be the following (Source: [2]):
In the /system/build.prop file search for ro.da1.enable=true and set it to ro.da1.enable=false
Add ro.da1.method=false directly under it
Reboot
I performed these steps and now am able to click on links in WhatsApp again without crashes. Maybe this will help someone else as well.
Cheers
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
[2] androidcentral.com / how-restore-functionality-apple-v-htc-war-has-taken-away-root
Sorry for the awkwardly typed web URLs but I do not yet have the privilege to post outside links, so maybe some mod can fix it
Click to expand...
Click to collapse

I specifically rooted and unlocked my phone to do this as it was annoying as hell!
Thanks! :good:

You have unlocked the bootloader via HTC? If yes, after that what Guide for rooting have you used? I'm in the same situation as you are, I'm doing this only for the links. Stupid Apple patent! Also, if I un-root / re-lock the bootloader, the change remains? If I re-lock, would it show "Locked" or "Re-locked"?

Yes, unlocked via HTC-Dev. Can't remember the guide I used as I looked at a few for it to make sense to me.
In short, Unlocked boot loader, flashed ClockWorkMod recovery, then flashed super user. - You will have to find the guide that works best for you.
I have left it unlocked, but if you do re-lock it will say - Re-Locked, SECURITY WARNING. Nothing to worry about, just that HTC will know you have unlocked your device if you ever send it in for repair, not a problem for me as my phone is over a year old now.
I did notice though that if you DO re-lock the bootloader and try to edit the Build-Prop, it will always revert back to what it was before.
I had to leave it unlocked to edit it, and I haven't re-locked it.

MalekoUK said:
In short, Unlocked boot loader, flashed ClockWorkMod recovery, then flashed super user. - You will have to find the guide that works best for you.
.
Click to expand...
Click to collapse
... this is my big problem! 4ext / clockworkmod / superoneclick ... mount SDcard... don't mount SDcard... install HTCsync, uninstall HTCSync... Help?

Spiry0r said:
... this is my big problem! 4ext / clockworkmod / superoneclick ... mount SDcard... don't mount SDcard... install HTCsync, uninstall HTCSync... Help?
Click to expand...
Click to collapse
All I did was put superuser on the SD card, then installed the superuser zip via clockworkmod recovery, worked a charm. Anything else you will have to search the forum as I just jumped through a few threads to get the best method for me.
All the answers are in the forums

Thanks man.
For them, who doesn't know what is this all about.
After this fix>
o-> links in facebook work again - automatically open webrowser by clicking on link
o-> you can click on number in SMS message and this number automatically get transfered to dialer, so you can call it, or store to your contacts
o-> moar and moar, i have tried these two, because it was quite serious bug for me

thank you. Htc evo 3d with coolsense rom here had same problem that fixed it

Thx! this solved my problem!

this should be stickied or put in the INDEX thread.. thanks a lot for this, OP!
Spiry0r said:
... this is my big problem! 4ext / clockworkmod / superoneclick ... mount SDcard... don't mount SDcard... install HTCsync, uninstall HTCSync... Help?
Click to expand...
Click to collapse
before you do anything, back up everything that can be backed up, such as contact, smses, APN settings and apps if possible.
after that, change the sd card with a blank one (this isn't necessary, but just to ensure that you will not erase your current sd card and the files inside it)
1. unlock the bootloader (follow the steps closely and also install all necessary files as mentioned in the instructions)
2. download necessary custom recovery (4EXT is what i recommend) and SU zip files, put in the root of the blank SD card (that is, not inside any folder, for the sake of convenience)
3. boot into recovery (can be done in several ways, easiest one is power+vol down and get to recovery from bootloader screen, but remember to turn off fastboot in settings)
4. flash the custom recovery first. Once finished, my suggestion is turn off the phone
5. boot into recovery again, it should now be the custom one
6. flash the SU zip..
7. done, you are now rooted with stock ROM
experts please feel free to add on or correct any mistakes..
sorry if I got off track a little, just want to offer some help because I'm in a good mood today..

hahnbanach said:
(you need write access to /system however).
Click to expand...
Click to collapse
I tried frm es note editor in es file explorer but got error saving the file how do I get write access to /system ?

urmish101 said:
I tried frm es note editor in es file explorer but got error saving the file how do I get write access to /system ?
Click to expand...
Click to collapse
In es file Explorer options. And remember you'll need to enable "browse as root" or something similar as well.

[Q] 100% Original Stock ROM backup before root?

Hi there,
I am new to xda and new to Android hacking.
What I wanna ask is, (I guess it's of most newbies concern as well), can we have a 100% backup of our system (stock ROM)? Obviously, it is important because:
If we perform an official (OTA) update to a new Android version. And we don't like it. It is possible to get back to the old original one which we are used to. (not everybody likes new things, and/or not every new thing is good)
If our phones are having some problems. And we have to give it back to the company for a fix. In most cases they will flash a new ROM for us. If we wanna keep using the old one (explained in #1), we have to keep a copy of it by ourselves.
If we want to try new custom ROMs, we may want to switch it back after trying.
Whenever we do any modifications, it's always better to keep a backup/roll-back point. In case anything goes wrong, we have a safeguard.
For the official warranty issue.
Yup I do see there are some official stock ROMs downloads for some particular phones. But those are not really a backup of our original ROMs. And it's always hard to verify if those downloads are the original official releases. And, if those downloads are 100% stock ROMs, this means some guys out there could make it, so what is the way to do so?
Or, how those mobile phone companies do it in their labs?
I have been doing researches on this topic for a few days. Some posts claim that their methods are "backup stock ROM" or "backup before rooting". But after digging into it, they requires rooting and/or flashing CWM. Here comes a few questions:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
In addition, I have found some related pieces. which could be useful to anyone viewing this post, and might be useful for you to solve this (my) question. :fingers-crossed:
* as I'm a new user, I can't post links directly. Please delete the blank spaces in between.
ht tp://www .modaco .com/topic/351269-backup-original-rom/
In reply #5, user C3C0 raised a method of backing up the original stock ROM without root. But it seems he is flashing CWM and that method is only for ZTE Skate.
adb backup tool of Android SDK
At the first sight i came across this approach, I thought it is the official method to do whole system (ROM) backup (WOW - how nice!). But after studying for a few more posts, I think adb backup can only backup app+app_data, and possibly some system settings only. Am I correct? And also, adb backup is only for ICS (Android 4.0), isn't it?
adb backup usage: ht tp://forum.xda-developers .com/showthread.php?t=1420351
(But mentioned in the bottom of #1 the poster is having some issues on using adb backup. Perhaps there are some bugs and not reliable(?)
One more question on adb backup: Can it backup just one app+app_data, and restore just one app+app_data, without affecting other things? If yes, we don't need to root and don't need Titanium Backup (which requires root) for backup app+app_data. Isn't it?
** In case I have said anything or any terms wrongly in this thread, please DO correct me, for helping me and helping others.
P.S. i am using LG Optimus 3D.
Thanks a lot, wholeheartedly,
midnite_

Backup phone before root
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er

ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse
Hi ya,
It's so nice that you are having the same concern as I do.
As far as i know, the approaches of rooting differ from phones to phones. So we may have to find our own specific rooting method in the phone model sub-forums. It won't be hard for your popular S3
I would like to have a look at that Mr. Robinson's thread. If he can backup the stock ROM, those app+app_data wont a big issue (i guess).
cheers,
midnite_

midnite_ said:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
Click to expand...
Click to collapse
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, http://www.android.com is a good place to start, and to learn more about adb check out http://developer.android.com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: http://developer.android.com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.

wildstang83 said:
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, ht tp://www .android .com is a good place to start, and to learn more about adb check out ht tp://developer .android .com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: ht tp://developer .android .com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.
Click to expand...
Click to collapse
Hi Wildstang,
Thanks very much for your warm welcome and very informative reply. So are you a Flashaholics or Crackflashers yet?
As I am a newbie, please forgive me if I am asking dumb questions.
As far as I understand,
The steps of root is
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
** does "flash a custom recovery" means "flash Superuser binary & Superuser.apk"?
"Flash Superuser binary & Superuser.apk" is just "add SU binary to system/bin" and "add Superuser.apk to system/app". Then why not just copy them into place?
I just found on the web that "flashing" means replacing the OS of the phone with a new ROM. Would that still keeping the stock ROM?
To have a backup of the original stock ROM, can I
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
3. Perform the backup
And later, after I have flashed a new ROM, or whatever I do, as long as I didn't brick it, when I want to rollback my phone to its original, I can
1. Restore the backup
2. Delete "SU binary in system/bin" and "Superuser.apk in system/app"
3. re-lock the bootloader
Is this correct?
I don't mean to challenge you. But does adb pull \ really backup the system, or just all the files?
Thanks very much again!
midnite_

Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.

bump... midnite_ r u still around?

Hi Descent2,
Yes i am still around but i am busy with other stuffs at this moment. Thanks very much for your reply. You have studied a lot and you really did good summarisations. Very informative and I learnt a lot from it. Hope some of the masters or experienced ones would come by and bring us out of the mist
cheers,
midnite_
Descent2 said:
Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.
Click to expand...
Click to collapse

check here
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse

Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
mf2112 said:
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
Click to expand...
Click to collapse

You must unlock your bootloader then flash a custom recovery. You will then use that custom recovery to make a backup of your rom. That backup will be stored on your sd card.
Now, I have tried to help you and so have a couple other folks. You expect us to just give you answers step by step. I am sorry but this is simply not how XDA works. XDA is set up in a way which makes it for any users to find quickly what they want to know. Use the search feature on the site and you will find many answers. I tell you to go do your own research now and be proud of what you learn on your own. And if you cannot, please do not try to modify your phone further, you may just brick it if you aren't careful.

midnite_ said:
Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
Click to expand...
Click to collapse
I put in the GS3 links since the OP was using that phone. Every phone will be different so I don't think a general way or guide would be practical.
Sent from my HTC Sensation 4G using xda premium

[GUIDE] Fix BOOTLOOP with CWM zip !!! For All Phone

First of all,
Sometimes we facing BOOTLOOP, but we rarely make a backup so DATA in that backup already out to date.
And i found a method which can FIX BOOTLOOP WITHOUT RESTORING OLD BACKUP !
CAUTION !
THIS METHOD ONLY FOR ANYONE WHO FACING BOOTLOOP AFTER INSTALLING APPS, MODS, ETC
AND THAT APP IS NOT IMPORTANT FOR YOUR ROM
Things you will need
PC or Laptop
USB Cable (For connecting SD-CARD)
SD-CARD Reader (If your CWM Recovery can't mount SD-CARD)
WinRAR or WinZip
Notepad++
Patience!
Click to expand...
Click to collapse
So, lets begin..
STEP 1
If you facing bootloop after installing apps, mods, etc.
YOU MUST REMEMBER THE NAME AND LOCATION OF APPS/MODS YOU'VE PREVIOUSLY INSTALLED
Click to expand...
Click to collapse
STEP 2
Download my CWM zip HERE
Click to expand...
Click to collapse
STEP 3
In PC, after download, extract zip, open META-INF > com > google > android
Open updater-script with Notepad++
Click to expand...
Click to collapse
STEP 4
Edit this line
Code:
delete("/system/app/Home.apk","/system/etc/permissions/com.sonyericsson.uxpres.xml");
with name and location of apps/mods you've previously installed
Ex.
Code:
[CENTER]delete("/system/app/Crap.apk");[/CENTER]
And if you installed more than 1 app, you can insert another name and location in 1 line
Ex.
Code:
delete("/system/app/Crap.apk","/system/etc/permissions/com.bluesky.nxp-resolution.xml");
Click to expand...
Click to collapse
STEP 5
Save your modified updater-script and zipped the META-INF and system folder
Click to expand...
Click to collapse
STEP 6
Put your modified zip to your SD-CARD with mount sdcard option in CWM (with USB Cable) or using SD-CARD Reader
Click to expand...
Click to collapse
STEP 7
Flash It !
DONE !
Click to expand...
Click to collapse

Thanks, its is a lot easier to do with adb file manager thingy software I found online, connecting to pc via usb gives full access to phone file system partitions with root access, just deleting the files with it also works. :thumbup:
Why are SMARTphones soo... Freaking Dumb?

Or via adb
Connect phone/tablet to pc
In adb type:
adb delete("/system/app/Whatever.apk")
Done...
Disadv: USB Debugging must be enabled...

You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data

Bert98 said:
You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data
Click to expand...
Click to collapse
You're welcome

Before I tried the tutorial you or even try out all of the tutorials available on the internet, please help me to conclude my problem.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward

hey the link isn't working anymore? can you please reupload?
Do you have to get into recovery? as i have no recovery on my phone Xperia z3