I have a Verizon DE moto x that has twrp recovery. My active display keeps getting stuck when I get a notification, so I think I need to flash (or however it must be done) a fresh rooted stock copy. Where can I find info on how to do this?
Sent from my XT1060
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
mastarifla said:
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
Click to expand...
Click to collapse
What is the difference between flashing firmware and flashing factory images?
Cozume said:
What is the difference between flashing firmware and flashing factory images?
Click to expand...
Click to collapse
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
mastarifla said:
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
Click to expand...
Click to collapse
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Swimboy46163 said:
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Click to expand...
Click to collapse
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
piccit said:
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
Click to expand...
Click to collapse
Will this work? http://www.youtube.com/watch?v=gDJvZe7_s0E
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
mastarifla said:
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
Click to expand...
Click to collapse
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Click to expand...
Click to collapse
I have a Windows 7 machine and I can never get adb to run in a command prompt, either. I have a driver problem.
I can only use mfastboot to do anything unless I can fix my driver problem.
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Click to expand...
Click to collapse
There are a few tutorials for setting it up correctly, I'm not sure that you need the full SDK in order to do this, but I guess it's nice to have anyways. Try reading up a bit about it, I'm sure you can get it running in no time , after that you'll be much more familiar with these kinds of things.
OP, are you on 4.4? if so, then you don't have to worry about the bootloader. Just download the most current factory image from Motorola. The instructions for flashing the factory images are on their website. Go to www.motorola.com, go to the bottom of the page and click on "Developers". Its the same page you went to in order to get the bootloader unlock code. You have to request the factory image, and Motorola will email you a link, or there's several links to it floating around here.
The factory image will have the same bootlaoder version as you have installed as long as your are flashing the same OS version. It won't relock your bootloader, but you will lose root until you flash TWRP recovery. as far as the media partition, just back up your sdcard partition to your computer before flashing the factory image.
Here's the steps:
1. Plug your MX into the computer and back up all files you want to keep (photos, music, videos, downloads, etc...)
2. Download the 4.4 factory image from the source of your choice (If you don't get it from Motorola, make 100% sure you are downloading the correct file)
3. Make sure you have ADB and fastboot set up properly (and make sure you use the motorola fastboot (mfastboot.exe), bot the Google version)
4. Unzip the factory image and place all the files into the same folder as your adb and fastboot files.
5. Boot your MX into fastboot mode (power off, then hold all three buttons for approx 5 seconds and release)
6. Flash the files using mfastboot, and following the order provided in the included xml file.
7. Reboot.
8. Set your phone up and then restore the files you backed up to your computer
9. If you want root, then you will have to go back to fastboot and flash the TWRP recovery and let it install SuperSU.
10. Finally, PLEASE, make a nandroid back up once you have everything set up and before you make any alterations to it.
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Swimboy46163 said:
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy for ruining it for everybody. If you would stop being on your rag and complaining like a girl none if this would have happened. Look at what you did little girl.
MOTO X Slapped
Related
So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.
Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk
zeer.row said:
So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.
Click to expand...
Click to collapse
Do you have any experience with fastboot? If not, google how to download it for whatever type of computer you have. I'm on a linux machine so its pretty straight forward, but I think its easy on any machine. If you're on windows you'll need the motorola drivers as well. You'll also need a factory stock image for at&t moto x.
After that it's just a matter of flashing the image to your phone and starting over.
I'm sorry, forgot about the locked bootloader. Listen to the guy before me.
If there are any pictures or stuff like that on your phone, i'm afraid those will probably be lost.
I will try to find helpful links for all this stuff, but I just wanted to give you something to look for while I did that.
Anthony04x said:
Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
lnstalling rsdlite now. will update. thanks a ton.
Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.
thank you sooo much!
Hey no problem, we've all been there at some point. Did you get it working?
ps. Don't forget about that thank you button.
Sent from my XT1060
You can use the moto x toolkit here in this forum too. Install, open as administrator, install drivers from main menu, pick back to stock from main menu. Follow on screen instructions and it will do the rest from there
http://forum.xda-developers.com/showthread.php?t=2477132
This is in the completely wrong section. Needs to be moved to Q&A. Questions and help posts don't belong in a Development section.
Sent from my Nexus 5
Moto X was Bricked - Fixed - Thanks for the help
Thank you - it worked -
For some reason VZW wouldn't update my Moto X from 4.2.2 to Kit Kat. I bricked it trying. RSDLite fixed it with your instructions and now I'm on 4.4 Kit Kat.
Thanks!
JetOhmNet said:
Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.
Click to expand...
Click to collapse
OP - you can use my script here:
http://forum.xda-developers.com/showthread.php?t=2603051
choose Advanced Menu and then #2 - Flash Binaries (no wipe)
it uses the mfastboot method and may be able to save your data.
I'm at work right now and I sold a customer a Moto X (Verizon) and he somehow managed to shut the phone down in the middle of the update. I don't know anything about these phones but can someone please tell me how to restore the firmware? I need a full restore and I've looked for the firmware files online and they all say file not found so is there something else i can/should do?
You will need the firmware and rsdlite to try reflashing it. Here is the info you need:
http://forum.xda-developers.com/showthread.php?t=2446515
Thanks man I just have little time and I'm at work so I couldn't research it i appreciate it.
If I were you I would use the second option by manually flashing it, if you haven't done this yet. More and more people are bricking their devices using RSD. (So, the manual option is just safer.)
RSDlist is just calling the commands used to flash the phone, it also means people aren't skipping steps in the flashing process which has the most potential to brick the phone. There is no reason at all to not sure rsdlite unless the program just won't work with your OS.
Steve-x said:
RSDlist is just calling the commands used to flash the phone, it also means people aren't skipping steps in the flashing process which has the most potential to brick the phone. There is no reason at all to not sure rsdlite unless the program just won't work with your OS.
Click to expand...
Click to collapse
Some people had been reporting that RSD bricked their phone because it hiccuped and skiped a step. But yes, make sure not to skip a step if manually doing it.
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 this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app
flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class
zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app
if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.
TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...
Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.
miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Download factory image, extract, flash each img file separately except for userdata.
Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM
Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.
Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing
nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.
Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..
simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?
Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.
I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.