Related
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
A friend of mine bought an Alcatel OT895, which is a not so famous phone, and I don't know how can I root it, is it even possible?
And if rooting is possible, can I install a custom ROM (especially CM7.2) on it? I couldn't find anything useful anywhere.
Someone has to find out what hardware it has and what Android version it has. If you have the technical inclination, you could:
* Connect the phone via USB (with debugging enabled on the device) and access the internal filesystem via ADB (a tool from the Android SDK)
* Extract the relevant information, located in files named like 'build.prop', as well read /proc/cpuinfo
But even without those info (they just help in getting to know the hardware), you could jump straight into running an exploit to see if it works. If the Android version the vendor shipped with the device still has the particular vulnerability, the exploit will work.
Else, you need to extract the boot image and edit files, then repack and flash it. This is only possible if you have access to a safe flashing environment, i.e. custom recovery, so that you can first back up the partition.
There may be other ways, but that depends a lot on who else has posted information related to your device on the Internet or elsewhere.
Thanks, but I'm too noob for this, so I rather leave it on stock.
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
I bought a chinese phone Telsda/TSD A198 . The firmware reports it as an MT6589 CPU but the computer reports it as a spreadtrum phone. I need to root the phone to get rid of some apps on this to make space. Also without rooting is there anyway to backup the stock rom on my phone before I mess up to root? I have seen a method on XDA but that requires root. Now I am trying to backup to get to rooot !!!! Also I have also researched researchdownload but without a ROM backup and not knowing which CPU model to flash its impossible to it right. I also looked into mtkdroidtools and it tells me "unstructured rom backup not possible" , so I am guessing its a fake MTK CPU that is being reported by tweaking the firmware.
This is the link to the phone
http://www.aliexpress.com/item/New-...3-MTK6589-4-0-INCH-smart-phone/879312434.html
Any help is appreciated.
Thanks
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Villis1251 said:
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Click to expand...
Click to collapse
Ok, first my honest suggestion dont buy this phone it has pathetic performance. For the same price go for a real MTK6577 dual core. ANyways below are the answers to your question
> Real CPU frequence seems to be 1GHZ
>Mali 300 GPU
>no 3G
>no GPS
>256MB RAM and 256 MB ROM
>I am not sure if its real JB and I cant figure it out but it says JB 4.2.1 and the kernel is 2.6.35.7 and hence I guess its a fake JB. The funny part is under baseband version it says "MT6589 1.5GHZ quad cores" !!!! offcourse it means the firmware/build.prop has been tweaked and is reporting false values. Also when I ran Antutu it gives a score of about 3500 which is useless when compared to what is required to run games ..etc. I hope I have helped.
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
custom recovery
Villis1251 said:
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
Click to expand...
Click to collapse
Finally I was able to stitch a ROM, using bits and pieces from different sources and its perfectly working. I only need to build a CWM recovery image based on the recovery image I have attached. Can someone help me do that? so that I can do a nandroid and ump my rom in case someone needs to recover their telsda A198
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
aspirus said:
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
Click to expand...
Click to collapse
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
hel me please!!!
braindia said:
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
Click to expand...
Click to collapse
braindia hello ... I bought the same phone and I have problems with the sims do not have to call or receive coverage ..... could you explain you did and how you did it?
there say that you put android 4.0 not work quite right? ... greetings from chile
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
aspirus said:
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
Click to expand...
Click to collapse
ok looks like lot of people have issues with this phone. Its a junk phone, all fake stuff on it. ANyways I will upload the firmware images and then you guys can use those to flash on your phones. Below is what I have done
1> Patched a 4.0.4 ROM which works perfectly
2>Removed useless preinstalled apps
3>rooted
4>Perfectly working dual sim,GPRS,WIFI,Camera,Camcorder .,..etc etc
4>The issue is with the IMEI, because of the way its stored you guys will need to use your own NV files.
The only thing I havent been able to do is get a working CWM, but you dont need it as you can flash the firmware images using researchdownload.
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
working firmware files
aspirus said:
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
Click to expand...
Click to collapse
Here you go, you flash at your own risk. If there are bricks/issues you are responsible for your own device.(Standard disclaimer) . I have uploaded all the files except system and NV, system image is kind of big and I am trying to figure it out where to upload it.. You dont need to worry about NV unless you completely erased the flash(never erase the complete flash or format it). If you havent done so then you are good to go.
Please google to find researchdownload and use it to flash the attached files. I wont be able to write the tutorial on using researchdownload so google is your friend.
I have also uploaded the gapps zip which will get you up and running with google play store. You need root to copy these files directly into system/apps folder.
I will be able to upload a system file which works, not the patched one with google play store, root ...etc etc . You do that on your own, I will help you do it.
Thanks !
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
aspirus said:
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
Click to expand...
Click to collapse
your phone is probably not detected due to 2 reasons
1> windows disabling non signed driver.. if thats the issue while you start the PC keep hitting F8 you will be shown various options
Select disable windows driver signature enforcement
2> Second reason is you need to add an entry in adb_usb.ini file I think its 0x1782 which is for SPRD enumerator. There are tons of links for this one of which is
http://forum.xda-developers.com/showthread.php?p=37271476
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
aspirus said:
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
Click to expand...
Click to collapse
getting root is simple, flash a CWM I have attached one, please note this does not work but it works enough to get you root. follow the below steps
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
4> perform mount /system and then exit shell
5> push su binary & busybox directly to /system/bin (from the command prompt using adb push)
6>change permissions for su & busybox to make them runnable
7> exit from the shell and reboot
8> do adb install superuser.apk(optional this can be done later)
thats it you have su, and then you can sideload the superuser apk or you can do step 8 as above. Once you have rebooted and verified that you indeed have superuser you can flash the stock recovery back on the phone.
Note note note : The CWM recovery image is only for you to get root and it doesnt work and doesnt show the normal CWM options... you have been warned. You should flash your old recovery/stock recovery after you have achieved root.
Also can you give me the stock recovery image so that I can build a working CWM out of it. I overwrote mine and now stuck with another recovery which works but is not for this phone.
Thanks
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
aspirus said:
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
Click to expand...
Click to collapse
Hmm... I am not sure what is the issue please try attached drivers and pray that they work . use either 64bit or 32bit depending on your OS.
Also you said you have the firmware can you upload it ? I can do something more with the stock/original firmware, so please upload it
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
aspirus said:
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
Click to expand...
Click to collapse
Thanks ... I know this phone is a waste of time and money both. I am just using this phone as an experiment platform knowing fully well that this piece of junk will die anytime.
Hello to all,
Please some help/advice, I'm new in this.
I have more than a week trying to find a way to install Google Services on a Huawei P40 Lite. version JNY-LX2 (JNY-LGRP2-OVS 10.1.0.297 - C25E5R2P1).
I found some methods failed with (Using LZPlay app) then I found that is needed to do a downgrade and use the Googlefier method or dload method but I'm currently stuck with the following 2 issues
1-) I found a firmware in pro-teammt.ru that is minor to 10.1.0.150 but I cannot find the way to download it.
2-) Before to proceed I´d like to make a backup of the stock firmware that the device has now (if something goes wrong), but I don´t find yet a way to make the stock ROM backup.
Then,
1-) May someone help me out in how to make a stock rom backup. Maybe some written guide that I haven´t found yet.
The device is not rooted but I'm confused, since I see in some sites they say that only can be done in rooted devices and in others sites they say is no needed be rooted.
2-) How to download the firmware from pro-teammt.ru since when I do click on links always appears server connection errors or that maybe have been removed.
3-) The C25 region I found that is for Latam, but C605 is for Latam too I think. So, If only possible to find and download C605 firmware would be work on this device?
Thanks in advance for any help.
Regards
Device's Android must be rooted ( temporarily or permanent ) to fully backup its Stock ROM ( what consists of boot.img, system.img, recovery.img, metadata, etc.pp ): Reason is that Android must get mounted as RW what requires superuser rights.
Once rooted a full backup easily can be done by means of ADB.
Example:
Code:
adb devices
adb exec-out dd if=/dev/block/mmcblk0p7/boot.img > C:\boot.img
adb exec-out dd if=/dev/block/mmcblk0p20/system.img > C:\system.img
...
If you have an eMMC internal storage you can see names and partitions at same time running
Code:
adb shell "ls -l /dev/block/platform/msm_sdcc.1/by-name/"
jwoegerbauer said:
Device's Android must be rooted ( temporarily or permanent ) to fully backup its Stock ROM...
Click to expand...
Click to collapse
Thanks for your answer. Then first step should be roote the device.
Do you know a good guide to root this Huawei model (or guide that works for any device)?
I can search on google, but there is many results and some noise since some are old or different procedures and I'm not sure which would be safer to choose in order to avoid damage the device.
Regards
Because your phone is running Android 10 ( EMUI 10 ) and based on Kinn 810 chipset I guess all the so-called One-Click-ROOT tools aren't working at all.
I don't own this phone, hence I can't guide you further. Thanks for your understanding.
jwoegerbauer said:
Because your phone is running Android 10 ( EMUI 10 ) and based on Kinn 810 chipset I guess all the so-called One-Click-ROOT tools aren't working at all.
I don't own this phone, hence I can't guide you further. Thanks for your understanding.
Click to expand...
Click to collapse
I understand. Thanks for your help anyway.
Regards