[Q] OS Backup Question - Asus Transformer TF701

Hi, I am sure this is answered somewhere here, but there is so much cumulative information and half-answers to go through.
First the short version then some additional info.
Short;
How can I do a complete backup of a new TF701 so that I could restore it to the state it arrived in before I would unlock the bootloader, root, and install a recovery?
Info;
Although I am not an expert, I have rooted/put clockwork recovery on a few different phones and tablets. I am familiar with adb and know there are techniques to use that to do a backup.
A bit more info;
I have another TF701 that is rooted and works reasonably well, but I did something at some point that now it randomly reboots, as well as it will not install the update to go from JB to KK (I get a "not enough space" error that I assume is really a misleading error based on having encrypted the device).
On the new TF701, after turning it on, all I have done is apply the various system updates. I would like to capture the device in this state so that in the future I can restore to it. IE, that I would both be able to restore to this clean KK as well as stock recovery, and anything else (if there is) software-wise that might cause the device to misbehave. Having a re-locked bootloader isn't necessarily a requirement, as I'm not sure how hard that is, but if possible I would like the state captured to be with the device as it currently is with the locked bootloader.
If possible, I don't want to root, install a recovery, and only then be able to do a backup and have to rely on someone's post of a "Stock recovery" or image.
My main concern is not around returning the device and getting support or things like that; it is being able to return the device to a known, pristine state, since most backup methods don't seem to backup everything; they either only backup apks, or only backup the system rom, or only the "sdcard", etc.

SocketTumi said:
Hi, I am sure this is answered somewhere here, but there is so much cumulative information and half-answers to go through.
First the short version then some additional info.
Short;
How can I do a complete backup of a new TF701 so that I could restore it to the state it arrived in before I would unlock the bootloader, root, and install a recovery?
Info;
Although I am not an expert, I have rooted/put clockwork recovery on a few different phones and tablets. I am familiar with adb and know there are techniques to use that to do a backup.
A bit more info;
I have another TF701 that is rooted and works reasonably well, but I did something at some point that now it randomly reboots, as well as it will not install the update to go from JB to KK (I get a "not enough space" error that I assume is really a misleading error based on having encrypted the device).
On the new TF701, after turning it on, all I have done is apply the various system updates. I would like to capture the device in this state so that in the future I can restore to it. IE, that I would both be able to restore to this clean KK as well as stock recovery, and anything else (if there is) software-wise that might cause the device to misbehave. Having a re-locked bootloader isn't necessarily a requirement, as I'm not sure how hard that is, but if possible I would like the state captured to be with the device as it currently is with the locked bootloader.
If possible, I don't want to root, install a recovery, and only then be able to do a backup and have to rely on someone's post of a "Stock recovery" or image.
My main concern is not around returning the device and getting support or things like that; it is being able to return the device to a known, pristine state, since most backup methods don't seem to backup everything; they either only backup apks, or only backup the system rom, or only the "sdcard", etc.
Click to expand...
Click to collapse
The short answer is: You can't.
You can't do anything in terms of backing up anything system related with a locked bootloader
You cannot relock the bootloader
You cannot make a nandroid without a custom recovery installed.
What's wrong with the stock recovery image and the stock rom you can find on Droidbasement????
They are just that: Pure stock. If you flash those you're tablet is back to factory specs except for the BL unlock.
Try formatting /data on your old tablet, then reflash the rom. Most likely your problems are related to the encryption....

berndblb said:
You can't do anything in terms of backing up anything system related with a locked bootloader.
Click to expand...
Click to collapse
Well, I said I understand I might need to unlock the bootloader.
I don't understand why, for example;
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
after an adb restore;
"You're back to normal, short of possibly some widgets on the home screen. [...] I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. [...] this will not back up SMS messages"
Why??? Is this a bug in adb? something about not being able to lock the file system? Those questions are rhetorical, but I don't understand why everything with Android seems to be "it works, ... except ..."
berndblb said:
What's wrong with the stock recovery image and the stock rom you can find on Droidbasement????.
Click to expand...
Click to collapse
Probably nothing, but what is it's provenance? It was not posted by Asus, right? How do I know it was not posted by some hacker who has added three lines of code that captures every "keystroke" I make? Most of the posted tutorials just say "go here ..,. download this ..., type this ... and there is no explanation of what is going on or why I should trust that download. If I can't get a purely stock rom, how did the person who posted that one?

SocketTumi said:
Well, I said I understand I might need to unlock the bootloader.
I don't understand why, for example;
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
after an adb restore;
"You're back to normal, short of possibly some widgets on the home screen. [...] I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. [...] this will not back up SMS messages"
Why??? Is this a bug in adb? something about not being able to lock the file system? Those questions are rhetorical, but I don't understand why everything with Android seems to be "it works, ... except ..."
Click to expand...
Click to collapse
Why should something titled as experimental developed for a Samsung Nexus on ICS from 2011 not work on your current tablet?
I don't even know where to begin.......
And anyway, that post is about backing up apps and data. Doesn't backup the rom....
Probably nothing, but what is it's provenance? It was not posted by Asus, right? How do I know it was not posted by some hacker who has added three lines of code that captures every "keystroke" I make? Most of the posted tutorials just say "go here ..,. download this ..., type this ... and there is no explanation of what is going on or why I should trust that download. If I can't get a purely stock rom, how did the person who posted that one?
Click to expand...
Click to collapse
Yes, you should only download from reputable sources. How do you find out if they are reputable? Google is your friend.
How could they do it? Because they know a whole lot more than you do.... or I for that matter.
But it's totally up to you to benefit or not from a boatload of work done for free in the spirit of sharing.

berndblb said:
Try formatting /data on your old tablet, then reflash the rom. Most likely your problems are related to the encryption....
Click to expand...
Click to collapse
Thank you. I was trying to avoid starting over on that tablet, but that worked.

Related

Some questions for my LG 4X HD

I have the LG 4x for some time now and i am wondering how to go about with it. I have certain questions, maybe knowledgeable people can answer them.
-I bought the phone with the German 10c firmware. I am now thinking of applying the European 10h one. When i click "software update" from the phone, it says no update available. When i click it from the LG pc suite, it says, the 10h is available, but does not give more information on which 10h it is. I also have downloaded the firmware from the internet, so i am wondering which is the safest, easiest, most certain procedure, to apply the updated firmware. I still have not rooted my phone. And what i have not figured out yet, is, DOES UPDATING THE FIRMWARE MEAN FACTORY RESET? Or is it more like a software update, where it just updates things needed to be updated, not touching anything else?
-Is it possible, if i root the phone, to unroot it, using a reverse procedure? You know, if the need for using the warranty arises.
-It really bothers me, the new type of file system with this android version. I ve been using the 2.3 before i got the phone, which requires, just a backup with clockworkmod and a copy of the external sd and you re done. Now, i don't know which is the best method to backup my phone. ALL apps, except for a couply of offline maps apps, install in the INTERNAL memory of the phone, all game data, etc, which has nearly filled half my phones internal memory so far. I understand that the only solutions to this, are root, and Directory Bind, and one other app i don't recall the name now. So, thats two reasons to root the phone, moving apps to sd, and using Titanium Backup with root, for backup. So the question is, what other option do i have for backup, WITHOUT root?
Everything else works great, good hardware on this phone!
ZTEBlade0 said:
I have the LG 4x for some time now and i am wondering how to go about with it. I have certain questions, maybe knowledgeable people can answer them.
-I bought the phone with the German 10c firmware. I am now thinking of applying the European 10h one. When i click "software update" from the phone, it says no update available. When i click it from the LG pc suite, it says, the 10h is available, but does not give more information on which 10h it is. I also have downloaded the firmware from the internet, so i am wondering which is the safest, easiest, most certain procedure, to apply the updated firmware. I still have not rooted my phone. And what i have not figured out yet, is, DOES UPDATING THE FIRMWARE MEAN FACTORY RESET? Or is it more like a software update, where it just updates things needed to be updated, not touching anything else?
-Is it possible, if i root the phone, to unroot it, using a reverse procedure? You know, if the need for using the warranty arises.
-It really bothers me, the new type of file system with this android version. I ve been using the 2.3 before i got the phone, which requires, just a backup with clockworkmod and a copy of the external sd and you re done. Now, i don't know which is the best method to backup my phone. ALL apps, except for a couply of offline maps apps, install in the INTERNAL memory of the phone, all game data, etc, which has bearly filled half my phones internal memory so far. I understand that the only solutions to this, are root, and Directory Bind, and one other app i don't recall the name now. So, thats two reasons to root the phone, moving apps to sd, and using Titanium Backup with root, for backup. So the question is, what other option do i have for backup, WITHOUT root?
Everything else works great, good hardware on this phone!
Click to expand...
Click to collapse
All of your question was answered. don't be lazy
L2Deliver said:
All of your question was answered. don't be lazy
Click to expand...
Click to collapse
Maybe they have been answered at some post in some thread, but i have no way of finding the exact post!
Why dont you help a fellow smartphoner and answer me here, if you know the answer?
1 - if you update via official SW it maybe leave data untouched and only update system
2- to unroot just reflash SW (via lgflashtool for example)
3- LGs backup app...
Maybe they have been answered at some post in some thread, but i have no way of finding the exact post!
Why dont you help a fellow smartphoner and answer me here, if you know the answer?
Click to expand...
Click to collapse
You have a search feature in the forum, which you can use.
And the reason some of us don't answer questions that have been repeatedly asked and answered is that, if we do, we say that it's OK to open a thread to ask a question that's easilly answered.
But I'll do you a bit of a favor: I'll tell you WHERE you can find the information, and I'll even answer one of the questions (the last) since, regardless of having seen it asked and answered a few times before, I'm not able to direct you to the right place where this sort of question has been asked and answered.
ZTEBlade0 said:
I have the LG 4x for some time now and i am wondering how to go about with it. I have certain questions, maybe knowledgeable people can answer them.
-I bought the phone with the German 10c firmware. I am now thinking of applying the European 10h one. When i click "software update" from the phone, it says no update available. When i click it from the LG pc suite, it says, the 10h is available, but does not give more information on which 10h it is. I also have downloaded the firmware from the internet, so i am wondering which is the safest, easiest, most certain procedure, to apply the updated firmware. I still have not rooted my phone. And what i have not figured out yet, is, DOES UPDATING THE FIRMWARE MEAN FACTORY RESET? Or is it more like a software update, where it just updates things needed to be updated, not touching anything else?
Click to expand...
Click to collapse
If you want to update it through flashing the .kdz, you should find that information in the respective thread, as it not only refers the correct method, but also the consequences.
ZTEBlade0 said:
-Is it possible, if i root the phone, to unroot it, using a reverse procedure? You know, if the need for using the warranty arises.
Click to expand...
Click to collapse
This information can be found, as it turns out, in the two possible threads for rooting the LG 4X (one for ICS and one for JB). I'll give you a bit more help, as the threads aren't in the same sub-forum - the one for JB is in the General Forum, the one for ICS is in the Development Forum.
ZTEBlade0 said:
-It really bothers me, the new type of file system with this android version. I ve been using the 2.3 before i got the phone, which requires, just a backup with clockworkmod and a copy of the external sd and you re done. Now, i don't know which is the best method to backup my phone. ALL apps, except for a couply of offline maps apps, install in the INTERNAL memory of the phone, all game data, etc, which has nearly filled half my phones internal memory so far. I understand that the only solutions to this, are root, and Directory Bind, and one other app i don't recall the name now. So, thats two reasons to root the phone, moving apps to sd, and using Titanium Backup with root, for backup. So the question is, what other option do i have for backup, WITHOUT root?
Everything else works great, good hardware on this phone!
Click to expand...
Click to collapse
Most backup programs don't care where you've installed your apps. That said, if you don't want to root your mobile, the only option you have is the LG Backup app. I'm not sure if it saves and recovers every bit of data (meaning the saves of your games and other information you may have configured into your apps), but it's your best bet for a root-less 4X.
mmm273 said:
1 - if you update via official SW it maybe leave data untouched and only update system
Click to expand...
Click to collapse
It "MAY" leave data untouched??? In computers, this word is not supposed to be used, either it WILL, or it will NOT. So you re telling me it will be an unstable procedure if i update via the official Software?
skryptus said:
Most backup programs don't care where you've installed your apps. That said, if you don't want to root your mobile, the only option you have is the LG Backup app. I'm not sure if it saves and recovers every bit of data (meaning the saves of your games and other information you may have configured into your apps), but it's your best bet for a root-less 4X.
Click to expand...
Click to collapse
Great. So you re saying too, that the only backup option a non rooted user has is not even to be trusted. If it will not save apps data, its useless then. What am i supposed to do, play all games over again?
No, i used maybe , because i only flashing via LG flash tool and it erase all data ... but i THINK official update MAY leave data ( like on xperias phones)
its hard to root it, make complete backup and then flash it ? if answer is yes, dont go to upgrade...
mmm273 said:
No, i used maybe , because i only flashing via LG flash tool and it erase all data ... but i THINK official update MAY leave data ( like on xperias phones)
its hard to root it, make complete backup and then flash it ? if answer is yes, dont go to upgrade...
Click to expand...
Click to collapse
No, if there is a procedure, i ll follow it and root it, i am just thinking, that i read that 4.1 will have a DIFFERENT rooting procedure, so i was thinking to wait, upgrade to 4.1 and THEN root it.
I am now backing up for the first time from within the phone app, see how it goes.
ZTEBlade0 said:
I am now backing up for the first time from within the phone app, see how it goes.
Click to expand...
Click to collapse
Well, the backup is over, just about 1.3gb. Strange, the internal memory is full up to about 6.5gb. I don't understand WHAT exactly it backed up! It said it will back up "app data", along with other stuff (contacts, call log, etc.). I have no idea what it backed up from the Apps. Left more confused than before!
maybe that backup is justl ike you backup via CWM - backup system and data, and this lg backup tool make data backup... so you backup all of your internal storage to PC (before that make backup of contants and messages) try update , and after that run restore ...
or you can root, backup, flash, root again, restore...
ZTEBlade0 said:
It "MAY" leave data untouched??? In computers, this word is not supposed to be used, either it WILL, or it will NOT. So you re telling me it will be an unstable procedure if i update via the official Software?
Click to expand...
Click to collapse
Official method leaves stuff untouched. It warns you it will erase the data, but from what I've heard, it doesn't. Although, everyone is advising for you to do a factory format after you update it, as it solves a lot of slowdowns and other possible incompatibility problems.
Great. So you re saying too, that the only backup option a non rooted user has is not even to be trusted. If it will not save apps data, its useless then. What am i supposed to do, play all games over again?
Click to expand...
Click to collapse
Please stop putting words into other people's mouths. I said I'm not sure. I myself haven't used the app. Other users have been mentioned having used it (but then again you'd know that if you went to the trouble of looking around a bit), so I think it would be a viable alternative, but I won't vouch for it and/or its abilities because I have no experience with it.
Point is, if you don't want to use root, you lose the ability of writing into the /data folders (and some times even correctly reading from it). If LG, by some bending of those rules, made it so you can, count yourself lucky. If they didn't, you can't really blame them - it's Google's OS (who IMO should have come up with a decent Backup solution a long time ago).
mmm273 said:
maybe that backup is justl ike you backup via CWM - backup system and data, and this lg backup tool make data backup... so you backup all of your internal storage to PC (before that make backup of contants and messages) try update , and after that run restore ...
or you can root, backup, flash, root again, restore...
Click to expand...
Click to collapse
I did a backup using the LG app. So it said it backs up "application data, contacts, etc". Ok. The size is just 1.8gb. The used space in internal memory is 9gb. So i don't understand WHAT exactly it backed up from the applications. Everything EXCEPT for the "sd data" of games?
So i would do a firmware update, then a factory reset, to have the new firmware installed, CLEAN, then restore my backup. Right? So after the factory reset, it will have wiped ALL applications, deleted them from the internal memory? Is that correct? So i would use the 1.8gb restore, and what will it give me from my 9+gb applications (games, etc) that i have now?
Or, do i have to COPY all "sd data" files from the internal memory to PC, and restore the 1.8gb backup AND re-copy the "sd data" files of games and applications, back to internal memory?

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] Please help, oh wise & experienced ones of XDA

Hi folks. So I haven't been on this site in a good while, but I've come across an issue that requires the help of someone with wisdom about the issue at hand. Up front, you should know that I'm not familiar with the whole rooting thing and even the technical terminology of most of it.
A little back story...I've recently purchased a Sprint HTC One M8 from someone. Everything works fine with the phone, there's nothing wrong with it at all. It's rooted and has s-off. I bought it that way. I asked the seller if he could unroot and take the phone back to full stock before the deal, but turns out he had someone else root and soff for him so he wasn't able to take it back to full stock. But he put the stock ROM back on it for me, though it's still rooted and has s off. I've provided pictures for those who are in the know to see for yourself, because I don't know what any of that software info means on those screens.
Here are my questions, and I'll put them in numerical format so there won't be any confusion in replying back:
1. From what you see in the pictures provided, are you able to to tell if it is in fact on the stock ROM or not?
2. I am receiving notifications that an official OTA update is available from Sprint/HTC:
A. What are the consequences of downloading and installing the OTA update(s)?
B. Will s-off be effected?
C. Will the root block the update from happening, or will it work fine since it's on stock ROM and has s-off?
D. Will it brick my phone if I update, or is there a chance at all that my phone will get bricked or stuck?
3. If I want to revert my Sprint M8 back to full stock (unroot and s-on), or maybe even put on a different ROM, how can I go about doing it?
4. What benefits do I have in keeping my phone in the state that it is currently in, that is, having rooted and s-off? And how can I take advantage of those benefits?
5. If I want to flash a different ROM or revert back to full stock (unroot and s-on), will it delete everything off my phone, including specifically my synced Gmail accounts?
6. As you can see in the picture with the 3 Android figures, at the top it says "tampered" and "unlocked." Does the "unlocked" mean that the phone is fully unlocked and can be used on any other service provider network, domestically and internationally?
Sorry about the length of this message, but I know there are some knowledgeable people on here who have wisdom and experience on the issue, so I would greatly appreciate any productive and helpful replies to my questions. If you have any questions for clarification please feel free to ask. Thanks!
If you choose recovery from the menu option in your first screenshot, what happens?
Captain_Throwback said:
If you choose recovery from the menu option in your first screenshot, what happens?
Click to expand...
Click to collapse
Hi Captain. I haven't tried anything because I wanted to seek help first and get answers to my questions before doing anything. That would be much appreciated. I also didn't want to risk bricking since I don't know anything about this stuff. What is recovery, what is it supposed to do?
1. Yes, it appears to be a stock rooted ROM. Appears to be the first update. There have been two since, including the most recent one from this past week.
2.Your software & firmware version will be updated. S-off won't be affected. You simply have to have the stock recovery installed to take the OTA. Taking the OTA won't brick your phone.
3. You can revert to S-on but I'm not even sure why you'd want to. If you want to unroot simply take the OTA after installing the stock recovery.
4. Hit the second link in my sig for more info.
5. If you flash a different ROM yes, your phone will get wiped and you'll need to set up your accounts again. If you take a OTA update your data won't be affected.
6. "Unlocked" means your bootloader is unlocked, plain and simple. See my answer to question #4 for more info.
As far as what recovery is, think of it as a very small and separate OS from the Android OS. It allows for the flashing of .zip files (ROM's, kernels, mods, etc.). It also allows you to back up your entire phone to either the internal storage or micro-SD card, among other things.
Take a look at this thread if you haven't already.
Magnum_Enforcer said:
1. Yes, it appears to be a stock rooted ROM. Appears to be the first update. There have been two since, including the most recent one from this past week.
2.Your software & firmware version will be updated. S-off won't be affected. You simply have to have the stock recovery installed to take the OTA. Taking the OTA won't brick your phone.
3. You can revert to S-on but I'm not even sure why you'd want to. If you want to unroot simply take the OTA after installing the stock recovery.
4. Hit the second link in my sig for more info.
5. If you flash a different ROM yes, your phone will get wiped and you'll need to set up your accounts again. If you take a OTA update your data won't be affected.
6. "Unlocked" means your bootloader is unlocked, plain and simple. See my answer to question #4 for more info.
As far as what recovery is, think of it as a very small and separate OS from the Android OS. It allows for the flashing of .zip files (ROM's, kernels, mods, etc.). It also allows you to back up your entire phone to either the internal storage or micro-SD card, among other things.
Take a look at this thread if you haven't already.
Click to expand...
Click to collapse
Thank you very much Magnum_Enforcer for the detailed and organized response. I will definitely be looking into the links you've mentioned/provided. Ideally, it would be great if I can somehow keep it rooted and have s-off while being able to take OTA updates. From that point I clean learn about and use the benefits from it being rooted with s-off, although I need to keep my Google accounts synced, so no flashing of ROMs for me.
So after reading your reply, I went ahead and tried taking the OTA, and after it turned off, it loaded up in the screen in the pic I've attached to this message. I'm assuming it doesn't seem I have the stock recovery as you said is required to take the OTA. How do I get the stock recovery on my phone in place of this "Team Win Recovery Project" recovery so that I can be able to take the OTA update properly? And will removing the current recovery and putting on the stock recovery effect s-off, root, or my synced accounts in any way?
P.S. I see you're in Birmingham. I actually grew up all over B'ham. Which part of town are you from?
L A Z I Z A said:
Thank you very much Magnum_Enforcer for the detailed and organized response. I will definitely be looking into the links you've mentioned/provided. Ideally, it would be great if I can somehow keep it rooted and have s-off while being able to take OTA updates. From that point I clean learn about and use the benefits from it being rooted with s-off, although I need to keep my Google accounts synced, so no flashing of ROMs for me.
So after reading your reply, I went ahead and tried taking the OTA, and after it turned off, it loaded up in the screen in the pic I've attached to this message. I'm assuming it doesn't seem I have the stock recovery as you said is required to take the OTA. How do I get the stock recovery on my phone in place of this "Team Win Recovery Project" recovery so that I can be able to take the OTA update properly? And will removing the current recovery and putting on the stock recovery effect s-off, root, or my synced accounts in any way?
P.S. I see you're in Birmingham. I actually grew up all over B'ham. Which part of town are you from?
Click to expand...
Click to collapse
That's why I asked you to select recovery in the first place. I could've told you whether it would've worked based on that.
I recognize you wanted answers to your questions, but in order to give you the most complete and accurate answer, all I asked was for you to check your recovery.
Captain_Throwback said:
That's why I asked you to select recovery in the first place. I could've told you whether it would've worked based on that.
I recognize you wanted answers to your questions, but in order to give you the most complete and accurate answer, all I asked was for you to check your recovery.
Click to expand...
Click to collapse
There's no need for quarrel or to take anything personal. It's not as if I ignored you, I replied back to you. I'm here to seek answers and help, I've no interest in disagreements. Sorry if you feel that way. I'm sure you're quite knowledgeable and experienced enough to have been able to tell me the same, if not more. The response I received from Magnum just happened to be complete and informative enough to me to let me know it was ok to try it out. I like to know at least a little about what I'm doing before jumping into something. That's just the way I am, people are different.
I sought help again in my last response though, and if you're still interested in helping, it would be appreciated. If not, I would understand, no worries or hard feelings.
You won't be able to take the OTA with TWRP installed. You can find the stock recovery in the first post of the link below. There are also instructions on how to install it. Once installed you can boot back to the OS and take the OTA.
Stock Backups + OTA's
To answer your other question, I've lived in several different places all over the state over the years but now live in the northern part of Jefferson county, outside of the city of Birmingham (you couldn't pay me to live in the city limits of B'ham).
Sent from my HTC M8

HELP! Nexus 6 Encryption Unsuccessful - Can't grab TWRP backup or any other data

Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
wizard5007 said:
Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
Click to expand...
Click to collapse
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
zelendel said:
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
Click to expand...
Click to collapse
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
wizard5007 said:
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
Click to expand...
Click to collapse
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
How did you fix the issue?
zelendel said:
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
Click to expand...
Click to collapse
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
scryan said:
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
Click to expand...
Click to collapse
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
zelendel said:
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
Click to expand...
Click to collapse
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
lol!
ok, both @zelendel and @scryan are right..
its highly not recommended to restore a nandroid onto a different phone if it contains system apps. that said, theres also a chance that it would be fine as well. its just that the system apps could not be supported(or could be) by the 2nd device. but even if they arent supported, it wont really harm your device, as you can fix whatever issues by just switching out the apps that are causing issues(then reboot).
scryan said:
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
Click to expand...
Click to collapse
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
zelendel said:
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
Click to expand...
Click to collapse
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
simms22 said:
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
Click to expand...
Click to collapse
I wouldn't say most. But it was close indeed. I had them both but focused on the hd2 mostly. God I miss truly open bootloader lol.
zelendel said:
....focused on the hd2 mostly.
Click to expand...
Click to collapse
I remember the HD2 as one of the best phone ever made.
zelendel said:
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
Click to expand...
Click to collapse
Just wanted to chime in here and say, I agree 1000% that I would never restore a backup from one phone to another, unless I knew for a fact I could "rescue" the phone if it locked up/got fried/ruined from the restore..
And, I have been playing with cell phones since November 1983, the first day cell service became widely available in Chicagoland, and I have been modding/tweaking/hacking them pretty much since then, so I too have "extensive" experience about what may or may not work when doing something like this..
To each his own, but I would never do this..

Boot-loader Flashing vs. using Flashfire

(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.

Categories

Resources