Related
Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4
cw18306 said:
Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4
Click to expand...
Click to collapse
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way
danger2u said:
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way
Click to expand...
Click to collapse
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X
flashallthetime said:
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X
Click to expand...
Click to collapse
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
look alot of people are having this issue it is a simple fix follow the directions step by step
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
as soon as you type the above command to flash TWRP we need to boot the phone into recovery before we let it boot to android we can do that via the command below.
Code:
adb reboot recovery
MAKE SURE THAT AFTER YOU TYPE THE FIRST COMMAND DO NOT LET THE PHONE BOOT TO ANDROID.
right after you hit enter for the mfastboot command type the reboot command it will boot into recovery. if not i would redownload the correct TWRP recovery for 4.4
there is a link here
http://forum.xda-developers.com/showthread.php?t=2603358
cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
If recovery flashes but is not available, your best bet is to flash the sbf firmware and flash recovery, its worked for numerous folks including me
Sent on my Moto X
cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.
xawen said:
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.
Click to expand...
Click to collapse
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
Like I said previously ,flash the kitkat firmware, forget jb. You can not flash back to the pre camera ota, gpt.bin is the bootloader which if is incompatible will fail, saving you from hard bricking your device
Sent on my Moto X
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
What errors are the RSD and fastboot actually failing with?
When you're trying to do the fastboot flash, does "fastboot devices" actually show your device as connected?
-----Edit----
Are you sure that is the right version of the firmware? I'm waiting for access to the files from the moto site right now so I can compare the full file name, but I'm pretty sure you have the Maxx Dev Edition firmware file there.
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
fastboot reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted
@cw18306 just got turnt up
SuperSU.ZIP Move to Phone?
dray_jr said:
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
adb reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted
Click to expand...
Click to collapse
You are THE MAN! Quick question regarding SuperSU.zip...Do I unzip it in windows and MOVE the 4 folders to the phone, OR do I only need to move the UNZIPPED SuperSU file to the phone? I am about to flash recovery and want to be sure. Thanks so much!!!
Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.
nhizzat said:
Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.
Click to expand...
Click to collapse
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android.
cw18306 said:
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android. I rebooted to bootloader again, reflashed TWRP, highlighted Recovery, hit UP, and the screen goes black and does not boot. If I press the power button, the phone will boot to Android. That is where I am now. Something must be up with my Recovery file?
Click to expand...
Click to collapse
@dray_jr
cw18306 said:
@dray_jr
Click to expand...
Click to collapse
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:
cw18306 said:
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:
Click to expand...
Click to collapse
no problem glad everything worked out for you enjoy
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
alexhdkn said:
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
Click to expand...
Click to collapse
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Why would you want to relock the bootloader just to get back to close as stock as possible?
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
TechSavvy2 said:
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Device: VZW Moto X
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
KidJoe said:
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Click to expand...
Click to collapse
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
nhizzat said:
Why would you want to relock the bootloader just to get back to close as stock as possible?
Click to expand...
Click to collapse
So i can get Lollipop official!
TheBoiledDogs said:
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Already done this but it won't relock the bootloader.
alexhdkn said:
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
Click to expand...
Click to collapse
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
alexhdkn said:
So i can get Lollipop official!
Click to expand...
Click to collapse
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
edit:canceled
KidJoe said:
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
Click to expand...
Click to collapse
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
alexhdkn said:
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
Click to expand...
Click to collapse
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
KidJoe said:
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
Click to expand...
Click to collapse
I know it's an entire process and I did it last night to go back to stock 4.4.4. But I just feel safer (thieves) with the bootloader locked.
Thieves? How will having a locked bootloader protect you from thieves?
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
simms22 said:
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
Click to expand...
Click to collapse
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Click to expand...
Click to collapse
it is easy, enjoy
simms22 said:
it is easy, enjoy
Click to expand...
Click to collapse
So to reassure, the process I listed is good to use for updates?
Forerunner326 said:
So to reassure, the process I listed is good to use for updates?
Click to expand...
Click to collapse
yea, its fine, but you dont have to reboot the bootloader after each flash.
simms22 said:
yea, its fine, but you dont have to reboot the bootloader after each flash.
Click to expand...
Click to collapse
Rebooting the bootloader like this doesn't hurt correct?
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
i wouldnt think so
simms22 said:
i wouldnt think so
Click to expand...
Click to collapse
What does rebooting the bootloader do?
Forerunner326 said:
What does rebooting the bootloader do?
Click to expand...
Click to collapse
just that, reboot the bootloader, nothing else. its been too long since i flashed a factory img! good thing too
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked?
Click to expand...
Click to collapse
You don't.
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
efrant said:
You don't.
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
Click to expand...
Click to collapse
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Forerunner326 said:
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Click to expand...
Click to collapse
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
efrant said:
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
Click to expand...
Click to collapse
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Forerunner326 said:
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Click to expand...
Click to collapse
Yes.
This is my method verified with 5.1.0 D and E variants, this will not wipe your device.
Download images from: https://developers.google.com/android/nexus/images#shamu
Extract all files to your comp including the main .tgz and the .zip inside that
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img (optional if keeping TWRP or you can flash the latest TWRP here)
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot (Or enter recovery and re-root if you kept TWRP)
efrant said:
Yes.
Click to expand...
Click to collapse
Is there anything else I should know before I flash any update files onto the device?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
gee2012 said:
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
Click to expand...
Click to collapse
What about the cache image? Would it go after boot.img gets flashed? Or do I not worry about it?
This is what I have so far.
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. Connect to pc and load platform tools command window
4. fastboot flash bootloader {bootloader-shamu-xxx.img}
5. fastboot reboot-bootloader
6. fastboot flash radio {radio-shamu-xxx.img}
7. fastboot reboot-bootloader
8. fastboot flash system system.img
9 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
10. Boot into TWRP by selecting Recovery Mode on device and pressing power button
11. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm)
12. Reboot (Main menu > reboot)
You can do that after boot:
fastboot erase cache
fastboot flash cache cache.img
11, 12, 13.
Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?
touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!
If you have some difficulties finding fastboot rom for some G5S+ variant, I suggest using Lenovo Moto Smart Assistant (LMSA). You can download it from here and install on your PC.
How to download latest specific stock fastboot rom for your G5S+
You must:
Using stock rom (locked or unlocked bootloader).
Install Lenovo Moto Smart Assistant on your PC.
Restore stock firmware, recovery, and boot image (if you changed it before).
Steps:
Reboot your phone to bootloader.
Open "Lenovo Moto Smart Assistant".
Connect your phone to PC using the USB cable.
Choose "Flash" menu on LMSA.
Choose "Moto Phone".
Choose "Moto G Plus (5th Gen S)".
Choose your phone models.
Wait for a minute while LMSA checking your phone, and then choose "Rescue". It will download the latest 1.5+ GB stock fastboot rom based on your phone model. You can find it on "C:\ProgramData\LMSA\Download\RomFiles".
Click "Rescue" to flash latest rom and accept some confirmations. Your phone will be rebooted after flashing process completed.
Now your phone is back to stock rom. Of course, if you have unlocked it before, those steps wouldn't lock your bootloader. If you want to lock it, I suggest you do it immediately after flashing process completed.
Here to lock your phone after successful stock rom restoration.
You must:
Have ADB fastboot driver installed.
Get extracted fastboot rom from "C:\ProgramData\LMSA\Download\RomFiles".
Steps
Reboot to bootloader.
Open "Command Prompt" on your PC, and go to the location of extracted fastboot rom.
Connect your phone to PC using the USB cable.
Check first that your phone is connected using "fastboot devices" command.
Do all below commands in sequence:
Code:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
Your phone will be restarted. There will be no unlocked bootloader message anymore. And you'll have your phone locked. Ta-da .
Note:
Check "system.img_sparsechunk.x" files (where "x" is sequential numbers) in extracted fastboot rom folder. Newer rom may have more files than the older one. You must flash ALL those "system.img_sparsechunk.x" files in sequence.
If you have issues, please share here. Thanks are appreciated.
I did all above steps but my G5 plus is still saying it has an unlocked bootloader with a ID: Invalid key error.
My phone simply avoids the bootloader to be relocked... it's just pure garbage...
What is the reason for relocking the bootloader? You don't get the warranty back...
should i setup my devices and come back to bootloader or without setup please clear this
thanks in advance
Will Moto Smart Assistant also work for the G7 (Play)?
Motorola support sais no (and that there is no way at all to restore the images after unlocking the bootloader)... will try to find out myself later today.
And another question, do people have experience with updating Motos via Moto Smart Assistant? Reason is that latest models (G7) do not allow for OTA updates with bootloader unlocked. Am wondering if it will still be possible via the Smart Assistant - provided that works at all
Does it require only stock rom?
Can i flash the stock rom using lenovo smart assistant when the phone is with custom rom?
Tried it all, but no good news.
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Install Pixel Experience ROM
voliveira92 said:
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Click to expand...
Click to collapse
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Abhimlv12345 said:
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Click to expand...
Click to collapse
hello i was looking around to fix my revvl xt-1952-t ( motola g 7)
its stuck in boot loop flashing bad key ( always had bad key since unlocking the phone. )
i have done a couple roms on samsung devices and never on any thing else .
fast boot is some what new to me. i love it vr oden installs . so i went to reinstall
stock rom on a extra phone
and didnt not get it to load i have whipped and reinstalled 4 tines checked the models var etc seems like it is all correct . is there any ideas or tricks i could be missing
I think i did it without flashing the sparsechunk