Related
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
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
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.
(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.
Hello! I have a moto x4 bought on CLARO (brazilian) carrier that comes with their official ROM (with non uninstallable apps, etc). It's the XT1900-6 model, with Android 8.0 Oreo installed. Thing is, the moto x4 was updated to Android 9 Pie, the retail devices have started receiving through OTA over a year ago. But as mine is carrier branded, it depends on them to release the updates (motorola gives to them and they do whatever they want, modify and release or do nothing) and they haven't lanuched the update. So I am tired of waiting and want to know if I can just "unbrand" my phone by installing an official retail firmware to receive the update (or just install the Android 9 firmware directly). Can I just get the retail firmware from lolinet and flash it following a guide? Or this is not possible at all?
I think the problem would be in getting the non-Brazilian ROM to access Claro, or whatever carrier you are using down there. But I don't know.
KrisM22 said:
I think the problem would be in getting the non-Brazilian ROM to access Claro, or whatever carrier you are using down there. But I don't know.
Click to expand...
Click to collapse
But the ROM would still be brazilian. Check out this firmware on lolinet.com on /firmware/moto/payton/official/RETBR/XT1900-6_PAYTON_RETBR_9.0_PPWS29.69-26-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (As a new user, I cannot post links yet)
Ah, okay, I understand your question. But of course not having tried it I don't know the answer. Have you tried lmsa (see my sig) to see what if anything it offers you?
KrisM22 said:
Ah, okay, I understand your question. But of course not having tried it I don't know the answer. Have you tried lmsa (see my sig) to see what if anything it offers you?
Click to expand...
Click to collapse
I have not, but I tried to check it out right now, your link is giving 404 not found error.
LOL yes, I screwed up. Thanks. Try it now.
---------- Post added at 10:22 PM ---------- Previous post was at 09:51 PM ----------
I realized another possible prob - the ROM you have on there now is a (maybe) custom ROM made by Claro. Therefore some other ROM like the one you suggested, might not connect to Claro. Dunno...
KrisM22 said:
LOL yes, I screwed up. Thanks. Try it now.
---------- Post added at 10:22 PM ---------- Previous post was at 09:51 PM ----------
I realized another possible prob - the ROM you have on there now is a (maybe) custom ROM made by Claro. Therefore some other ROM like the one you suggested, might not connect to Claro. Dunno...
Click to expand...
Click to collapse
Yes, I think that is the case. But the model is exactly the same as retail, I can't think of why a retail ROM wouldn't work. I think it would be like I had bought the phone in some random store and put a Claro sim card on it, it would work.
Okay, I tried LMSA, it says my ROM version is up to date. But this is expected, as it would check for updates in the Claro channel, which has none. I want to change to retail ROM so it would check for updates in retail channel.
Back in the day, even before Android, I did something like this with an old Nokia phone. Phones used to differ the model number not only by region, but also by carrier. I don't remember the procedure exactly, but I flashed a retail number over the carrier number and used a Nokia support software like the LMSA and it recognised the phone as retail. It had an update to be installed, so I did and the phone "turned" into retail version. Of course none of this applies for modern smartphones, but I think it may be possible to do something similar.
I hear you. Not having the Claro ROM to flash back if it doesn't work, you would be simply taking a chance. And if the new ROM won't connect to Claro, you're stuck. I realize the big reason I am being so cautious here is that in my reading I had recently encountered a Claro phone that now wouldn't work, but of course I forget where I read that and what was done to the phone - maybe a custom ROM? I'll do a search and see if I find it again. Nope, nothing in X4, so I don't know where I saw it.
EDIT: no, I find nothing. it was something about (I think) they were on a custom ROM and it would connect to Claro only and very slowly, or something like that.
EDIT2: I'm advising you not to flash unless you have a clear way back.
You're right, you're being cautious. This is exactly why I registered in the forum in the first place, so I could discuss the matter with people more experienced before I do anything stupid, maybe even found someone who had already done what I'm trying to do. I appreciate your help.
ivooc28 said:
You're right, you're being cautious. This is exactly why I registered in the forum in the first place, so I could discuss the matter with people more experienced before I do anything stupid, maybe even found someone who had already done what I'm trying to do. I appreciate your help.
Click to expand...
Click to collapse
You're welcome! Yeah, caution is something too many folks don't have enough of and wind up with bricked phones. And even used, they're not cheap. Keep searching!!!
I will keep searching! Isn't there a way to just extract the current firmware I'm running to use as a backup?
Theoretically, maybe, but I wouldn't want to trust it(see modems comment below). You could
fastboot boot twrp.img
to temporarily get twrp and then boot to it, and then use it to do a backup, but you must make sure that you back it up to your SDcard since internal storage is often wiped during a flash. Then, theoretically if your new ROM doesn't work you could
fastboot boot twrp.img
back into twrp and restore that backup, but, again, I wouldn't want to trust it. I have used that to back up stock when flashing custom ROMs in the past, but I always had, and often used, RSDlite to flash a stock ROM to get me out of trouble. I believe RSDlite will work on an 8.x ROM on the X4 (I haven't tried it) but I know it will not recognize my phone at all now that it is at 9.0 RSDlite needs to be updated and I have no idea who is running that these days. One question I would have over the above is the particular modems being flashed - are they different in your Claro ROM, and if so, i do not believe they are backed up/replaced if you do a TWRP backup or restore.
"Okay, I tried LMSA, it says my ROM version is up to date."
Does it offer to download that ROM? If so, click the little down arrow and download it and see if you can access that and see if it looks like something that could be saved and flashed later. When I tried it a few days ago it looked like it was offering to download the same thing I had on. If so, that might give you a copy of the ROM you're on that you could flash to get back if need be - IF YOU CAN TRUST IT.
Nite. I'll check in tomorrow PM.
EDIT: of course I don't know if you can go from a partial Treble 9.0 back to a regular 8.x ... even if you have the stock ROM.
KrisM22 said:
Theoretically, maybe, but I wouldn't want to trust it(see modems comment below). You could
fastboot boot twrp.img
to temporarily get twrp and then boot to it, and then use it to do a backup, but you must make sure that you back it up to your SDcard since internal storage is often wiped during a flash. Then, theoretically if your new ROM doesn't work you could
fastboot boot twrp.img
back into twrp and restore that backup, but, again, I wouldn't want to trust it. I have used that to back up stock when flashing custom ROMs in the past, but I always had, and often used, RSDlite to flash a stock ROM to get me out of trouble. I believe RSDlite will work on an 8.x ROM on the X4 (I haven't tried it) but I know it will not recognize my phone at all now that it is at 9.0 RSDlite needs to be updated and I have no idea who is running that these days. One question I would have over the above is the particular modems being flashed - are they different in your Claro ROM, and if so, i do not believe they are backed up/replaced if you do a TWRP backup or restore.
Click to expand...
Click to collapse
You're saying that if the upgrade fails, then I would need to downgrade back to 8.x and that could be a problem, I see.
About the modems being flashed, I don't know if I understand it right. I believe the modems are the same here, regardless if I bought in Claro or retail. What I'm saying is, usually here in Brazil, if you buy a retail or carrier phone, either way you can put any (Brazil) sim card and the carrier would work. Of course that if a phone doesn't support specific LTE frequency bands by hardware, then it wouldn't work, but then it wouldn't matter if it is retail or carrier.
lmsa apparently doesn't give me option to download firmware, or maybe I didn't check it out properly.
ivooc28 said:
You're saying that if the upgrade fails, then I would need to downgrade back to 8.x and that could be a problem, I see.
About the modems being flashed, I don't know if I understand it right. I believe the modems are the same here, regardless if I bought in Claro or retail. What I'm saying is, usually here in Brazil, if you buy a retail or carrier phone, either way you can put any (Brazil) sim card and the carrier would work. Of course that if a phone doesn't support specific LTE frequency bands by hardware, then it wouldn't work, but then it wouldn't matter if it is retail or carrier.
lmsa apparently doesn't give me option to download firmware, or maybe I didn't check it out properly.
Click to expand...
Click to collapse
a) yes, might be a prob. Don't know.
b) if you know that then you can flash any Br ROM you want and connect to any carrier with it.
c) in lmsa, click flash (top tabs), then "go rescue". A box with fill-in-the-blanks pops up: fill in:
moto phone, moto X 4th gen, XT1900-6 (I believe it was in your case)
Hopefully some lines will appear and there will be a little down arrow thing on the right side saying download.
Click that and download the ROM. Once it is downloaded (DO NOT click rescue as that will wipe your phone), but go looking on your PC and see if you can find where it stored that download and grab/save it for yourself for possible future . I suspect it will be in c/users/<name>/local/motorola/"rom name" or something like that, not necessarily in local. It gives you part of the name so you could search your c:/ for some of that name to try to find it.
I wish I could be more specific as to its location but when I tried it with my phone this morning it said "This device is not supported" - I suspect that is because I just took the Nov 1 sec patch and there is no ROM out yet for it (lolinet doesn't have it yet - probably take another 2 or 3 weeks)(pretty lame imho, but it is what it is.
As to b) above if there are really that many folks using different carriers down there it seems that someone should know the answer to your question. Different website maybe, or post blatant "any one from Brazil here?" subject line in x4 , or search xda for Brazil. someone's gotta know! I don't believe LenAsh will swat you for a post like that if you link to this post and make clear your problem. A piece of the problem may be that the xda x4 forum seems very quiet . There may be 80 folks looking in but few are talking. Or, simply no experience in the matter and not wanting to encourage you to do something that will render your phone useless...