Easiest way to "clone" locked device to a dev edition? - Moto X Q&A

So I picked up a Dev Edition XT1060 on swappa so I can get ARUnchained running on it, and was wondering what's the easiest way to clone my current locked, stock, unrooted XT1060 to the new one? I've had varying levels of success in the past with the Moto "Migrate" app, ADB backup/restore from the command line, and Helium, but was wondering if there is anything better out there now.

Don't think so, not on an unrooted device. Best you can do is helium for user apps and data.
And in my opinion....that's as far as you want to go. Restoring anything system related to a new device is asking for problems. ?

Wade-0 said:
So I picked up a Dev Edition XT1060 on swappa so I can get ARUnchained running on it, and was wondering what's the easiest way to clone my current locked, stock, unrooted XT1060 to the new one? I've had varying levels of success in the past with the Moto "Migrate" app, ADB backup/restore from the command line, and Helium, but was wondering if there is anything better out there now.
Click to expand...
Click to collapse
KJ is right if you are going to a different phone.
But if rooted only & going to the same phone, as in a boot unlock which wipes data. You can (I have not tested) use "Online back up" apk with root only. At least on paper it should work .
See my links below.

aviwdoowks said:
KJ is right if you are going to a different phone.
But if rooted only & going to the same phone, as in a boot unlock which wipes data. You can (I have not tested) use "Online back up" apk with root only. At least on paper it should work .
See my links below.
Click to expand...
Click to collapse
They are identical system images, AFAIK, so there shouldn't be anything different in the system files, and the DevEd has already been unlocked by the previous owner. So I don't think I need any of that stuff transferred anyway, which should cut down on the time involved. I haven't played around with trying to restore an ADB backup from a different device, so I'm not sure if there's going to be any issues there. The only time I've used that method was to backup my device before using RSD to flash a different factory image, and even then it wasn't a very smooth operation. I guess I'll just have to try it and find out

Wade-0 said:
They are identical system images, AFAIK, so there shouldn't be anything different in the system files, and the DevEd has already been unlocked by the previous owner. So I don't think I need any of that stuff transferred anyway, which should cut down on the time involved. I haven't played around with trying to restore an ADB backup from a different device, so I'm not sure if there's going to be any issues there. The only time I've used that method was to backup my device before using RSD to flash a different factory image, and even then it wasn't a very smooth operation. I guess I'll just have to try it and find out
Click to expand...
Click to collapse
You cannot nandroid data from one phone to another!! See my post in the x Philz thread.

aviwdoowks said:
You cannot nandroid data from one phone to another!! See my post in the x Philz thread.
Click to expand...
Click to collapse
Wasn't aware I could even nandroid an unrooted phone.
Edit: I'm wondering if maybe you misunderstood what I was talking about with the ADB backup/restore. Here's more information: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
From my early experience with Carbon (which is now called Helium) it was basically the same thing as the ADB backup/restore function, Carbon was just a user friendly wrapper for it. But I could be way off on that point, it just seemed like it was doing exactly the same thing in the background.

Wade-0 said:
Wasn't aware I could even nandroid an unrooted phone.
Click to expand...
Click to collapse
I only figure that on "paper" the online BACKUP should work with root only. Not restore, mind you, that needs custom recovery. Which one would have after the obligatory data wipe which moto enforces to unlock.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382

OP is not rooted. So why confuse the matter. ?

aviwdoowks said:
I only figure that on "paper" the online BACKUP should work with root only. Not restore, mind you, that needs custom recovery. Which one would have after the obligatory data wipe which moto enforces to unlock.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
Click to expand...
Click to collapse
See my edited reply above. Also, the phone is already unlocked by the previous owner (bought it used on Swappa) so I only need to put custom recovery on it and root it, and whatever data transfer method I decide to use.

I thought I would post this also for those wanting a way to backup, while rooted, and then restore their nandroid when unlocked.

Related

I'd like to root but.. I need advice on whether or not I should

As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? I got confused with that.
Afterwards, I dl safestrap once I'm rooted? or should I just dl it and put it onto my phone all at once?
Apologies for the noobness. I'd rather be a noob asking questions than a retard who goes ahead and does things and finds out he screwed up too late.
Rooting is done to get superuser permissions within Android so you can install some advanced apps and modify system files which can all be done from within the stock ROM. Rooting then flashing an unofficial ROM is a little more advanced and something I haven't done yet so I can't help you much there. I'm waiting for something a little more stable since my Droid 3 is my main phone. You can read Hash of Codes site (the developer of ICS/JB for the Droid 3) on how to safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
To root use Motofail. I know it says its for the Droid 4 but the original Droid 3 root exploit was patched with the latest OTA so we have to use the Droid 4 method called Motofail:
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
DróidScìon said:
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
.
Click to expand...
Click to collapse
My D3 has Maverick as non-safe for daily driver and the latest Hashcode for fun. I find that to be the best combination. Once Hash finishes the camera and JB is working reasonable well, JB will be my DD.
I also have an SGS3, TF300T, and a Spica, all of them rooted.
once rooted, make sure you use safe strap. It makes roms easy to try out before having to settle
Sent from my DROID3 using Tapatalk
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
DróidScìon said:
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
Click to expand...
Click to collapse
Safestrap 1.08 is the 'normal' ssafestrap
Safestrap 1.08e/f/g is an advanced safestrap with extra features like touch etc but not by hashcode
Safestrap 2.10 is the latest which allows the new kernel with the kexec ICS/JB to be used.
2.10 It appears to also work fine with normal roms so i'd use that
DróidScìon said:
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? .
Click to expand...
Click to collapse
If you were stock 906, there was no reason to run the 1-click.exe - that's only for people who rooted their phones and deleted bloatware to get the phone back to stock, or people whose phones are bricked somehow. Coming from stock, just running Motofail was enough to root.
I will concur with everyone here that running rooting, installing and running Safestrap, and installing a custom ROM - and leaving your rooted stock alone - is the best way to go. It will be a lot easier to unroot later on if you want to sell the phone, etc.
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It doesn't matter. Choose which has enough space.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It's asking where to backup TO, like the post above me, choose wherever has space. Backups are about 1GB. You may wish to move it to your computer after if you don't have much space on your device. You can always stick it back on your external sd via card reader if needed, but it's really hard to brick while using safestrap
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Sent from my XT860 using xda premium
I saw that, and before I rooted, I did a Factory Reset on the phone and formatted my SD card. So I have 11+gig free on Internal and 15+gigs on External.
Now, I just need to learn to Flash RoMs (probably more to it than just hitting a button that says flash .zip) and find some info on the "must-have" apps for a rooted phone.
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
DróidScìon said:
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
Click to expand...
Click to collapse
If your contacts are on your google account they will show up.
What other account info do you mean?
You should go ahead and restore contacts. just go to Settings>Accounts and Sync>Google, then turn contacts sync on.
Endoroid said:
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Click to expand...
Click to collapse
I must have made another noob mistake. Everything went well, up until my first startup with the new OS (cyanogenmod9). It has been at the startup screen for over 15minutes right now. I must say, it is one awesome startup screen, with the blue effects and all, but I would love to get to the desktop/homescreen, haha.
If you guys have any advice I would greatly appreciate it. This is a Droid 3, it was rooted a couple hours ago, I did the safestrap as described, created a backup file, etc. My only guess is I jumped the gun by trying this OS on my Droid3 and it may still be under development? FWIW to you, this is the first I've rooted or modded a smartphone in my life, from 0-full speed in a couple hours is what I was shooting for using everyone elses experience.
thanks
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Phibernaut said:
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
thanks. since my last post I used a more detailed how-to, and wiped 3 different areas for data. Now, i had only a black screen (with power, barely lit) and it never even got to the cool blue screen.
I'm currently in safestrap after pulling my battery again, just trying to figure out how to revert back to my standard OS (rooted) and try a ROM like MavRom since it's suppoedly fully capable and stable. I'd love ICS, but I just want a working phone right now
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
good news is, I did enough steps correctly, that I was able to startup in my unsafe mode, and my normal rooted system is functioning fine. That makes me very happy.
This duel boot thing is pretty cool, reminds me of having bootable thumb drives on my old linux system with different OS's. I hope i can get a seperate OS working, however, that fits my needs for a day to day functional phone, without all of Verizon's crap on it
Once rooted use titanium backup to back up apps and data.
Only restore with the same ROM though, the following is in increasing order of risk
restore app only to exact same ROM+version
restore app+data to same ROM+ver
restore app only to update of same ROM
restore app+data to updated ROM version
play chicken with a bus on a highway
restore apps to different kernel e.g. CM7 backup => restore to CM9
check to see what a gun firing looks like down the barrel
restore app+data to different kernel
restore app+data to an older ROM or kernel
do anything at all with system apps+data if you don't know what you're doing

[Q]Can someone help a beginner root to get rid of ATT bloatware?

New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/showthread.php?t=2182792) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
jumi1174 said:
New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/show...182792&page=21) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
Click to expand...
Click to collapse
i would ike many of the same answers
experts help us!
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Im still very new to all of this as well, but i wanted to share this toolkit with you just encase you havent seen it yet. http://forum.xda-developers.com/showthread.php?t=2183942 Its been a tremendous help to me, hopefully it will be to you.
As far as the AT&T bloatware is concerned, It was very easy to remove once i was rooted and had flashed a new ROM. Ive used both Titanium Backup, and Rom Toolkit Pro to remove the junk.
Best of luck with your devices, Ive had a great time learning with mine so far.
jumi1174 said:
New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/show...182792&page=21) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
Click to expand...
Click to collapse
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
2. This is 100% normal. It is strongly advised you backup everything before unlocking due to this.
3. The link in your post to that tutorial is broken so there is no way to see what you mean. Sorry.
4. You cannot receive OTA while the bootloader is unlocked. You would need to relock your bootloader to continue with an OTA update.
5. As of now, no due to having to unlock your bootloader. Please see answer 4.
6. You would need to flash a zip file in a custom recovery to debloat your phone. There are other ways but this is the best way for a very new user. Link to debloat zip: http://forum.xda-developers.com/showthread.php?t=2250403
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
9. Odexed is the default state of the stock ROM. What it means is that a separate .odex cache file is stored away from a system app. It allows the app to load faster as upon boot your phone loads these cache files into the Dalvik VM. When a developer De-Odexes a ROM it means they have taken away those cache files and instead compiled them within the system app. This, in theory is a bit slower, but only when you clear your Dalvik and cache from recovery, otherwise you will notice no difference. The reason a developer does this is it makes the system app easily modifiable and themable. In summary, Deodex equals easily modifiable, whereas odex means the app is more locked down.
Sent from my HTC One using xda app-developers app
Thanks RPelham,
I hate to piggyback on someone else's thread, but they may want the answer to my question as well.
Is it a good idea to clear system and Dalvik cache from within recovery every now and then? Im used to the PC world, where clearing cache from time to time helps keep things in order.
Snakemanc6 said:
Thanks RPelham,
I hate to piggyback on someone else's thread, but they may want the answer to my question as well.
Is it a good idea to clear system and Dalvik cache from within recovery every now and then? Im used to the PC world, where clearing cache from time to time helps keep things in order.
Click to expand...
Click to collapse
No. You only need to clear Dalvik and Cache when flashing a new ROM, Kernel or basically any ZIP package. It won't serve any good purpose to randomly clear it. =)
Android has a great built in way of keeping your phone running great and killing any app that has not been recently used to keep everything running smooth.
Sent from my HTC One using xda app-developers app
behrouz said:
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Awesome videos, thanks!
RPelham said:
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
2. This is 100% normal. It is strongly advised you backup everything before unlocking due to this.
3. The link in your post to that tutorial is broken so there is no way to see what you mean. Sorry.
4. You cannot receive OTA while the bootloader is unlocked. You would need to relock your bootloader to continue with an OTA update.
5. As of now, no due to having to unlock your bootloader. Please see answer 4.
6. You would need to flash a zip file in a custom recovery to debloat your phone. There are other ways but this is the best way for a very new user. Link to debloat zip: http://forum.xda-developers.com/showthread.php?t=2250403
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
9. Odexed is the default state of the stock ROM. What it means is that a separate .odex cache file is stored away from a system app. It allows the app to load faster as upon boot your phone loads these cache files into the Dalvik VM. When a developer De-Odexes a ROM it means they have taken away those cache files and instead compiled them within the system app. This, in theory is a bit slower, but only when you clear your Dalvik and cache from recovery, otherwise you will notice no difference. The reason a developer does this is it makes the system app easily modifiable and themable. In summary, Deodex equals easily modifiable, whereas odex means the app is more locked down.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the awesome reply!
This is the link: http://forum.xda-developers.com/showthread.php?t=2182792
Sorry it was dead, I'll edit my original post.
Another question if you don't mind (may be a stupid question), if I root, will I still be able to purchase apps from the play store without any trouble?
behrouz said:
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
These videos are an absolute perfect example of how to unlock and root. Step by step. If you are new, this will be the perfect go to for help.
Sent from my HTC One using xda app-developers app
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
jumi1174 said:
Another question if you don't mind (may be a stupid question), if I root, will I still be able to purchase apps from the play store without any trouble?
Click to expand...
Click to collapse
Yes, you absolutely can. The only thing Root is giving you is administration level access to your phone. Obtaining root gives you the ability to modify, remove or add core system files and gives apps a lot more functionality as they can integrate themselves into the system.
And to answer question 3:
Yes the phone resets after you unlock your bootloader and it boots back into your phone. Simply reboot back to your bootloader and enter fastboot mode to continue flashing your recovery.
After you flash the recovery, it will boot back into your phone again (once you select recovery from the bootloader menu for the first time after the flash). Don't be alarmed by this, just reboot once more, select your recovery option again and this time it will truely take you to recovery.
Sent from my HTC One using xda app-developers app
RPelham said:
Yes, you absolutely can. The only thing Root is giving you is administration level access to your phone. Obtaining root gives you the ability to modify, remove or add core system files and gives apps a lot more functionality as they can integrate themselves into the system.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for all the help. One more if you don't mind (I appreciate your patience with helping a beginner like myself), will my phone be reset again when I root?
jumi1174 said:
Thanks for all the help. One more if you don't mind (I appreciate your patience with helping a beginner like myself), will my phone be reset again when I root?
Click to expand...
Click to collapse
No. Once you unlocked your bootloader your phone will not reset unless you flash a custom ROM or specifically wipe your device. Rooting will retain all settings and apps.
P.s. I'm heading off for the night. I hope I answered everything for you and helped you obtain a better understanding over this whole process. Ill follow up tomorrow to see if everything worked out for you and answer any additional questions. =)
Sent from my HTC One using xda app-developers app
RPelham said:
No. Once you unlocked your bootloader your phone will not reset unless you flash a custom ROM or specifically wipe your device. Rooting will retain all settings and apps.
P.s. I'm heading off for the night. I hope I answered everything for you and helped you obtain a better understanding over this whole process. Ill follow up tomorrow to see if everything worked out for you and answer any additional questions. =)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them and will I ever need to use them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
(3) The instructions for this ROM: http://forum.xda-developers.com/showthread.php?t=2192324
-Download ROM
-Copy ROM to your sdcard
-Fullwipe in AROMA if you come from another ROM or base
-Flash the ROM
-Let the ROM boot (After a Fullwipe this takes some time)
-Enjoy TrickDroid
I understand the first 2 steps, but what does "Fullwipe in AROMA" mean?
(4) Difference between a ROM and a KERNEL?
(5) Are you familiar with Titanium Backup? I've tried reading their wiki, but I'm still not 100% sure what exactly it backs up and how that is different than the TWRP back up.
jumi1174 said:
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
Click to expand...
Click to collapse
Hi.
1) they are just ruu for many different carriers, countries, etc. There is a specific ruu for your device. That's why so many ruu there
2) no need for that. Just install titanium backup pro from play store after rooting and you can delete all bloatwares or freeze them. Which will also get rid of those unwanted apps from your phone.
---------- Post added at 03:06 AM ---------- Previous post was at 03:03 AM ----------
RPelham said:
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hello mate
I have 2 questions.
Number 7, how do I make backup of your rom if you still haven't installed custom recovery?
Number 8 to unroot my phone I can also use the nandroid backup instead of ruu right?
Edit: 1 more Lol. Sorry.
I asked many places but didn't get an answer for it.
Let's say I have custom ROM, and I need to relock boot loader and flash stock ruu to go back to stock in order to receive ota update. Does the ruu contains the stock recovery? Cuz I read somewhere that in order to get ota update I also needed to flash stock recovery?
Thanks a lot! I think I'm all set after this kkk
If anyone has an answer to this question I'd appreciate it very much. I've rooted many phones but all of them have had SD cards. The HTC One is lacking an SD Card so when I back up data/apks etc is there a spot on the phone's storage that doesn't get wiped when wiping from recovery to install new roms?
gotrandom said:
If anyone has an answer to this question I'd appreciate it very much. I've rooted many phones but all of them have had SD cards. The HTC One is lacking an SD Card so when I back up data/apks etc is there a spot on the phone's storage that doesn't get wiped when wiping from recovery to install new roms?
Click to expand...
Click to collapse
Nope. All gets wiped. Backup on ur PC.
Uh oh. I just told him the opposite in another thread. I could swear I read that selecting a "wipe userdata" option in recovery would erase everything in the /data partition *except* whatever is below /data/media?
Did I get this wrong?
Sent from my PC36100 using xda app-developers app
Ive flashed a couple of different ROMs, and my media has not been erased when selecting "wipe user data". Im using CWM, if that's of any consequence.
Snakemanc6 said:
Ive flashed a couple of different ROMs, and my media has not been erased when selecting "wipe user data". Im using CWM, if that's of any consequence.
Click to expand...
Click to collapse
Sorry then. I saw a video on yt saying all would be deleted. I will try to find and post it here.
Edit. https://www.youtube.com/watch?v=7hvbwWTbZOU&feature=youtube_gdata_player
He was using TWRP, no idea if that makes a difference. Just passing on my experience, Im by no means well versed in all of this lol
Its great having such an active forum to learn from though :good:
ksarius said:
Hi.
1) they are just ruu for many different carriers, countries, etc. There is a specific ruu for your device. That's why so many ruu there
2) no need for that. Just install titanium backup pro from play store after rooting and you can delete all bloatwares or freeze them. Which will also get rid of those unwanted apps from your phone.
---------- Post added at 03:06 AM ---------- Previous post was at 03:03 AM ----------
Hello mate
I have 2 questions.
Number 7, how do I make backup of your rom if you still haven't installed custom recovery?
Number 8 to unroot my phone I can also use the nandroid backup instead of ruu right?
Edit: 1 more Lol. Sorry.
I asked many places but didn't get an answer for it.
Let's say I have custom ROM, and I need to relock boot loader and flash stock ruu to go back to stock in order to receive ota update. Does the ruu contains the stock recovery? Cuz I read somewhere that in order to get ota update I also needed to flash stock recovery?
Thanks a lot! I think I'm all set after this kkk
Click to expand...
Click to collapse
Im not 100% sure as I do not use Titanium, if someone could check that would be great, but I don't think titanium can permanently remove bloat yet. Freeze, yes, remove I'm unsure.
Our device has not achieved s-off which means that the partition the system apps sit on is not accessible to be altered from within the ROM, only by recovery / adb.
7. To my knowledge you must have a custom recovery to make a nandroid. You can't make a complete one without it. And once you nandroid, that backup is specifically for that recovery. I.e. you fly use a cwm nandroid in twrp
8. As long as your nandroid was created before installing the root package, yes.
RUUs will reflash stock recovery.
Sent from my HTC One using xda app-developers app
---------- Post added at 07:56 AM ---------- Previous post was at 07:52 AM ----------
jumi1174 said:
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them and will I ever need to use them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
(3) The instructions for this ROM: http://forum.xda-developers.com/showthread.php?t=2192324
-Download ROM
-Copy ROM to your sdcard
-Fullwipe in AROMA if you come from another ROM or base
-Flash the ROM
-Let the ROM boot (After a Fullwipe this takes some time)
-Enjoy TrickDroid
I understand the first 2 steps, but what does "Fullwipe in AROMA" mean?
(4) Difference between a ROM and a KERNEL?
(5) Are you familiar with Titanium Backup? I've tried reading their wiki, but I'm still not 100% sure what exactly it backs up and how that is different than the TWRP back up.
Click to expand...
Click to collapse
1 and 2 were answered above. I also elaborated on 2 above.
3. Aroma is an installation software made for recovery. It's a wizard that walks you through the ROM setup. You'll see an option for it while setting up the ROM
4. Kernel is the software that allows your hardware to communicate with your ROM as well as control boot screens, splash screens and overclocking and undervolting.
ROM is the phones operating system.
5. TWRP is a FULL backup, titanium is just an app, it can't backup 100% of everything like a recovery can. Titanium backs up your app and user data. Basically your settings and apps.
Sent from my HTC One using xda app-developers app

[Q] Swapping nandroid from one Moto X VZW Dev Ed to another

So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
etc6849 said:
So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
Click to expand...
Click to collapse
I would use Philz @hachamacha edition. See the RAZR HD section. If an OTA is needed YES do it first.
The problem is the data partition not the system. Due to your ESN and such.
Hachamacha may help you with some issues.
He is about to do a unified build to include his new X!
---------- Post added at 01:50 PM ---------- Previous post was at 01:26 PM ----------
He just posted the unified
http://forum.xda-developers.com/showpost.php?p=52414440&postcount=78
Thanks, the ESN/IMEI is normally stored in the radio's firmware? Or are you saying there's some file somewhere that also contains that data?
etc6849 said:
Thanks, the ESN/IMEI is normally stored in the radio's firmware? Or are you saying there's some file somewhere that also contains that data?
Click to expand...
Click to collapse
Right data contains phone data. But you may find a way to patch those IDs. Not via *228, as that is for 3g only. Try a complete restore & if you have to wipe data you can.
I do not know what happens when data is loaded from another phone.
aviwdoowks said:
I would use Philz @hachamacha edition. See the RAZR HD section. If an OTA is needed YES do it first.
The problem is the data partition not the system. Due to your ESN and such.
Hachamacha may help you with some issues.
He is about to do a unified build to include his new X!
---------- Post added at 01:50 PM ---------- Previous post was at 01:26 PM ----------
He just posted the unified
http://forum.xda-developers.com/showpost.php?p=52414440&postcount=78
Click to expand...
Click to collapse
Hi aviwdoowks,
I haven't yet posted anything but an intention to post something (how convoluted is that?) ; I have some builds that're up to date, unified, etc, for the *dt versions, but since I can't test until I get one, I hate to dump it on people. If someone doesn't care, then PM me. I'll be around for a few hours today and tomorrow to respond. Just make sure you tell me what device you've got since I just started dev for about 9 or 10 devices today.
Cheers.
hachamacha said:
Hi aviwdoowks,
I haven't yet posted anything but an intention to post something (how convoluted is that?) ; I have some builds that're up to date, unified, etc, for the *dt versions, but since I can't test until I get one, I hate to dump it on people. If someone doesn't care, then PM me. I'll be around for a few hours today and tomorrow to respond. Just make sure you tell me what device you've got since I just started dev for about 9 or 10 devices today.
Cheers.
Click to expand...
Click to collapse
I cannot get multi quote to work.
What do you think of the Op's restore question.
I thought you might come up with a way to restore data to a different X phone.
aviwdoowks said:
I cannot get multi quote to work.
What do you think of the Op's restore question.
I thought you might come up with a way to restore data to a different X phone.
Click to expand...
Click to collapse
Near as I can see (and I just tried multi-q for the first time), it is a myth I copied the original question down below and will look and see.
etc6849 said:
So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
Click to expand...
Click to collapse
Not sure I'm understanding. Was the first phone not a DE, rather an xt1060 or something like that? If so, which model was it? I'm also awaiting (few days) delivery of my first Moto X DE but have had no other one. Any factory unlockable phone I've had in the past is returned to a somewhat blank condition (/system and /data) as soon as you either a) lock or b) unlock using the Moto website so you'll of course, have to do that much and then slap on SuperSU (or whatever you like for root), busybox, etc.
Minimal amount of work? Stick to one recovery type because making backups is easy. If you want to use TWRP (which is a good recovery) to restore to the new phone, then do it. The easiest part of everything is changing recoveries once unlocked and rooted and you "KNOW" that TWRP can restore TWRP. Yes, Philz Touch can also restore TWRP, but when we build for phones new to us, sometimes, the git is in a state where maybe something isn't working, so why bother taking a chance on wasting all that time.
I've got Philz Touch latest version built for the msm8960dt (the motos/ultra/maxx/and others) but haven't looked into it since I've got no phone yet. My other possible suggestion would be to switch to Philz Touch as soon as I put up a pointer on it (or use an older one if you get your phone before). Stick it on your phone and make a new backup in CWM/Philz format. I'll go through the code and enable the /persist partition so you can get a backup of that. When you get the new DE, goto website, unlock, (which will probably just git rid of /data and /system), and if you want the least amount of guessing what is needed and not needed , just install the DE 4.4.2 image from the site so you'll have the firmware that is desired for that model phone. (radio and /firmware / persist stuff). Then boot to recovery and do the restore of the usual partitions. Use the .xml file in the .zip to figure out the order of the partition flashing for /firmware and radios and any other bits you want to flash. I would just create a batch file with 'fastboot flash 'partitionname' '{name}.img' statements in the exact order as in the .XML file and run it.
I don't know which (if anything but stock) ROM you've used and I'm not sure it matters which flavor it is, but it matters which version it was built from on the Moto so be sure it's apples to apples, since most the ROMs I've looked at seem to require the kernel from whatever was installed before. (the /lib/modules are also built to match that kernel as well and are a part of the /system of that ROM).
Everytime I've gone into a new phone situation and decided I was going to get away with a nandroid restore and voila , it always takes a bit of touch-up work, so pick one recovery, make the backups doing it, and do the restores to the DE using it rather than adding yet another variable. I can't think of one situation where I didn't have to at least use say Titanium Backup to restore the apps (I don't bother with data) because things rarely work out the same way. The other not-so-intuitive thing is that moving things from one phone to another (especially a nonDE to a DE) often bring up a new issue or more so expect to have to do a bit of work. Just be sure to make a good copy of the /sdcard/.. stuff that you need to keep (TitaniumBackup), and other data you need that nandroids don't care about, and back it up to your PC using adb. After you unlock, you can copy it to the target phone, and try the recovery. I really like Philz and I like TWRP as well, but I'd never tell someone they could move for sure from one phone to another without any problem. Best bet is using same recovery type on both ends though. Don't restore /persist or /firmware unless you're certain it's wiped. I mean that 4.4.2 image (.xml.zip) from the website has all the firmware you really want in it at it takes about 2 simple statements from adb to get it on the phone. That's pretty easy. Also, you never know. Might get lucky and a nandroid could be all you need but I'm not holding my breath on that.
Good luck.

backing up / restoring original firmware

i'm about to root my moto x dev.
i want to keep a backup of the original firmware in case i want to go back.
does it make any difference that it is encrypted? i'm guessing no...
also, any good dumb proof steps? the main info thread only mentions restoring stock by downloading a firmware not using a backed up one.
gcbxda said:
i'm about to root my moto x dev.
i want to keep a backup of the original firmware in case i want to go back.
does it make any difference that it is encrypted? i'm guessing no...
also, any good dumb proof steps? the main info thread only mentions restoring stock by downloading a firmware not using a backed up one.
Click to expand...
Click to collapse
Rooting how? What version of android are you on? These are very important considerations to be able to make a recommendation.
Assuming you intend to unlock your bootloader, you can make a backup with TWRP Custom Recovery BEFORE you root.
If you are using the PIE exploit (only current root method for 4.4.2+), you cannot flash custom recovery. If this is the case, your only option to return to stock will be to flash the official SBF file for your carrier as listed in the "Return to Stock" thread. Not really important since the changes are lost upon reboot anyways.
Regardless, we need more details.
EDIT: Just saw you are using DEV edition.
Very easy!
FIRST: When you unlock your bootloader, it ERASES EVERYTHING. Save anything important first. You cannot make a backup until after you flash twrp, which you can only do AFTER you unlock the BL.
Additionally, according to this thread, it is impossible to backup an encrypted device. So after unlock, you are advised to not choose to encrypt, otherwise no backup can be made: http://forum.xda-developers.com/moto-x/moto-x-qa/twrp-device-encryption-t2711700
Once Unlocked, flash TWRP custom recovery with mfastboot:
mfastboot flash recovery twrpfilename.img
link to download twrp here: http://forum.xda-developers.com/moto-x/development/recovery-twrp-official-support-moto-x-t2779637
then use fastboot to reboot into bootloader:
fastboot reboot-bootloader
now VOL DOWN to "recovery" and VOL UP to open it.
There is a BIG backup button. Use it.
Afterwards, click exit. When you do, it will tell you that you are not rooted and ask if you want to flash SuperSU Installer.
Say yes! Once rebooted, run SuperSU installer and it will root & install SuperSU for you. It will give you 2 options: Choose Play Store Option.
Good Luck
@gcbxda
Keep in mind, since unlocking the bootloader also does a factory reset and puts you back to "fresh out box" the backup you do once you flash TWRP on your phone, will be no different than "Stock Rom" (except TWRP recovery). So why not use the factory firmware to flash the phone back instead of restoring such a backup?
Oh, and keep in mind, if you do backup while in TWRP, you'll want to copy that back up file from the phone to the PC for storage. Future Factory Resets and such will likely wipe the X's internal /SDcard so the backup file would be lost.
Now if your intent is to unlock the bootloader, setup your phone the way you like it before rooting, back up, and then root.... I can see the value in that.
You can also use 'adb pull /sdcard c:\' to backup any files you have
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Also, what if I do a backup of the partitions with ADB? ...man sometimes the android community pisses me off. everything must be packaged in a app or some GUI that hides all the information. ...just wasted 2 days reading xposed source to learn that all i had to do, instead of even installing xposed, was to edit a single sql value from 1 to 0... i'm all for the nice guis, but don't hide the actual steps like it is some black magic.
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Stock
gcbxda said:
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Also, what if I do a backup of the partitions with ADB? ...man sometimes the android community pisses me off. everything must be packaged in a app or some GUI that hides all the information. ...just wasted 2 days reading xposed source to learn that all i had to do, instead of even installing xposed, was to edit a single sql value from 1 to 0... i'm all for the nice guis, but don't hide the actual steps like it is some black magic.
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Click to expand...
Click to collapse
Hello,
You can find all the stock roms here - - > http://sbf.droid-developers.org/phone.php?device=0
MikeNaples said:
Hello,
You can find all the stock roms here - - > http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
thanks. i also saw that motorola offer it themselves.. is this their own repository?
but regardless, it is always nice to already have your own handy
gcbxda said:
thanks. i also saw that motorola offer it themselves.. is this their own repository?
but regardless, it is always nice to already have your own handy
Click to expand...
Click to collapse
Moto officially offers recovery images (full stock rom) for the GSM Dev/GSM Unlocked XT1053 and Verizon XT1060 by request on their web site here -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images They are the most currently released rom only. You wont find older versions there.
SBF.Droid-Developers.org is neither owned, operated nor sponsored by Moto. They keep every version full stock roms (SBF files) they find. I'm not going to speculate how they come across them, but they have many SBF files that Moto hasn't officially released to the public too. i.e. Sprint, ATT, and other carriers.
---------- Post added at 07:27 AM ---------- Previous post was at 07:01 AM ----------
gcbxda said:
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Click to expand...
Click to collapse
There are ways to get back to stock to be able to take an OTA -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
gcbxda said:
Also, what if I do a backup of the partitions with ADB? ...
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
You can certainly back up that way. But I haven't tried backing up that way and restoring, so I don't know.
gcbxda said:
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Click to expand...
Click to collapse
With my HTC Incredible and HTC Thunderbolt and Moto Droid, I did backups in CWM, and restores. It was mainly for when a new upgrade came out. I would backup my current device setup, apps, etc. Apply the update, and if I didn't like the update or had problems, I could revert to my pre-update backup, rather than flash a stock rom and have to set it up all over again, install all my apps, etc. But the HTC devices had S-OFF, so downgrading wasn't an issue.
With my Droid Bionic, the bootloader wasn't unlocked, so it wasn't an option. And there were issues with GPT.Bin and other items preventing downgrading roms, even when flashing official full SBF files.
I haven't really done this with my VZW Dev X, mostly due to the fact that while the bootloader is unlocked, its not unlocked as much as a Nexus device, or an HTC with S-Off, where you can downgrade and flash any parts no matter what. Security issues, things like GPT.BIN, MotoBoot, etc can still get in the way when trying to downgrade. So I never felt it worth the risk. Not to mention the limited space on the X, and time/effort to make the back up and move the file to the PC, and then getting it back on the phone should I ever need to restore it since there is no real SD card.
If your intent of backing up stock roms is so you can revert to stock, having the Moto SBF files available elevates most users concerns. When flashing the same version, there are ways to do it without losing your Apps/Data (like in the case of running 4.4.2 rooted and modded, but wanting to get back to stock to take the 4.4.3 OTA).
If you want to do a backup/restore inside TWRP, you can. I have read many posts from users who were successful. I just advise that you keep track of the version you back up, and only restore if the same Android version is still on your phone (i.e. only restore a 4.4.2 back up if 4.4.2 is on your phone, only restore a 4.4 back up if 4.4 is still on your phone, etc)
wait, what are the limitations i will have with a unlocked Dev device?
with my nexus and touchpad i often tried 4.3 roms and went back to 4 or 2.3 even...
i tried searching the terms you mentioned but it spawn all sort of threads with OP having some flashing problem and then pages of comments starting with "i think..."
I'm extremely confused now
Sent from my XT1053 using XDA Free mobile app
gcbxda said:
wait, what are the limitations i will have with a unlocked Dev device?
with my nexus and touchpad i often tried 4.3 roms and went back to 4 or 2.3 even...
i tried searching the terms you mentioned but it spawn all sort of threads with OP having some flashing problem and then pages of comments starting with "i think..."
I'm extremely confused now
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Unlocked or Locked Moto X... you have to be concerned when flashing backwards. The Security features on the X prevent downgrading certain components. Attempting to do so will brick or set you up to brick in the future.
Please see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm
Short version... once you have 4.4.2 on your phone, do NOT attempt to downgrade.
KidJoe said:
Moto officially offers recovery images (full stock rom) for the GSM Dev/GSM Unlocked XT1053 and Verizon XT1060 by request on their web site here -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images They are the most currently released rom only. You wont find older versions there.
Click to expand...
Click to collapse
Lol. looking back at that thread i whish i had went ahead and did all the backups on all OTA updates before each twrp/root and did not trust motorola to have my back.
I'm a moron. Bumping this as a lesson to others

[Q] Backup before unlocking / S-OFFing

Hi,
After having looked at tons of theads and many searches, perhaps you can help, please?
I'd like to unlock via HTCdev and go S-OFF.
As I have many apps with their individual settings, an extensive calendar and > 1500 contacts,
I wonder how to backup all that stuff as unlocking wipe everything.
Thank you very much in advance
V
v said:
Hi,
After having looked at tons of theads and many searches, perhaps you can help, please?
I'd like to unlock via HTCdev and go S-OFF.
As I have many apps with their individual settings, an extensive calendar and > 1500 contacts,
I wonder how to backup all that stuff as unlocking wipe everything.
Thank you very much in advance
V
Click to expand...
Click to collapse
you might want to have a look at an app called Helium by koush, download it from playstore, its able to backup without root, don't forget though, unlocking your bootloader will also erase your sdcard, so be sure to copy the backup off your phone once its complete to your computer.
This will however only backup apps and data etc, I use my google account to backup my contacts, as for the rom itself, you will have to create a backup manually after unlocking the bootloader with a custom recovery like twrp.
You may also be interested in doing an adb backup, as this is something you can do on a fully stock unrooted device. Here is a link to a guide here on XDA:
http://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
and you can also just google "adb backup" for a wealth of info on this option.
Seanie280672 said:
...Helium...
Click to expand...
Click to collapse
Thanks! I'll try that.
dougeedug said:
...adb backup...
Click to expand...
Click to collapse
Thanks for the suggestion. I remember to have tried backing up my HTC One S with adb a couple of years ago. At that time it would not restore the backup. However, I'll do the backup just in case...
Just a thought:
I understand it's possible to gain temporary root.
Isn't there a way to pull an image of the whole system and restore exactly that later?
v said:
Just a thought:
I understand it's possible to gain temporary root.
Isn't there a way to pull an image of the whole system and restore exactly that later?
Click to expand...
Click to collapse
You can actually boot cwm recovery from the fastboot folder on your computer, with your phone in the bootloader to do a full system. Data, sdcard backup including the stock recovery to your computer without actually installing the custom recovery, but I'm really sorry, I can't remember how to do it, it's been years since I've done it that way, a bit of googling and you may be able to find it, not to sure either if your bootloader needs to be already unlocked to do it.
Seanie280672 said:
You can actually boot cwm recovery from the fastboot folder on your computer, with your phone in the bootloader to do a full system. Data, sdcard backup including the stock recovery to your computer without actually installing the custom recovery, but I'm really sorry, I can't remember how to do it, it's been years since I've done it that way, a bit of googling and you may be able to find it, not to sure either if your bootloader needs to be already unlocked to do it.
Click to expand...
Click to collapse
it's "fastboot boot <name of recovery>.img"
however, this only works on hboot 1.44, after that (hboot 1.54+ it will just freeze, and not enter recovery)
and I think you need an unlocked bootloader for that anyway
Seanie280672 said:
you might want to have a look at an app called Helium by koush
Click to expand...
Click to collapse
I agree with this too. I've heard about people having trouble applying an adb backup.ab, so it would definitely be a good idea to use helium too. Just make sure to set it to save the .apks too so you wont have to hit the playstore for those. Also, do remember to move whatever backup you make off of the device and as far as contacts, make sure they are set to be backed up to your gmail account. They probably already are judging by the fact that you already have so many, unless you collected them all since you got the phone. I mean, 1500 contacts would mean you have added 5 unique contacts per day since the release of this particular phone which is unlikely.
dougeedug said:
...1500 contacts would mean you have added 5 unique contacts per day...unlikely...
Click to expand...
Click to collapse
You are right.
But I saved my first contacts in an HP-41CX and have migrated data since then.
Some of these phone numbers are still in use.
Since 1984.
Sorry for this off-topic post.

Categories

Resources