idol 3 twrp question - Onetouch Idol 3 Q&A, Help & Troubleshooting

ok reading other threads i see others having issues with flashing twrp also.
i followed the unlock procedure and it was a sucess.
procedure:
in command prompt with files in directory
1: adb reboot-bootloader
2: fastboot -i 0x1bbb oem unlock
3: fastboot -i 0x1bbb oem device-info (bootloader confirmed unlocked)
4: fastboot -i 0x1bbb reboot
5: let deviice reboot
6: adb reboot-bootloader
7: got files from here http://forum.xda-developers.com/idol-3/general/twrp-custom-recovery-idol3-6045-t3162608
8: fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
10: rebooted
11: scratched head as default recovery booted.
so i am assuming i need to apply root before flashing custom recovery?
thanks in advance for any help provided.

I'm not sure there is any difference between the 5.5" & the 4.7" in term of the procedure but here's what I did on my 5.5"
1. Get ADB SDK application installed on PC
2. Download and install the correct USB driver for the phone. Assume you already downloaded the custom TWRP recovery image
3. Enable USB debugging mode on the phone
4. Plugin the phone to the PC, open Command Prompt
a. adb devices // to make sure the phone is recognized and listed
b. adb reboot bootloader
c. fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img // browse to where the .img is located first
Should be it!
You can root it AFTER install the custom recovery.
Hope that help!

deamon1311 said:
ok reading other threads i see others having issues with flashing twrp also.
i followed the unlock procedure and it was a sucess.
procedure:
in command prompt with files in directory
1: adb reboot-bootloader
2: fastboot -i 0x1bbb oem unlock
3: fastboot -i 0x1bbb oem device-info (bootloader confirmed unlocked)
4: fastboot -i 0x1bbb reboot
5: let deviice reboot
6: adb reboot-bootloader
7: got files from here http://forum.xda-developers.com/idol-3/general/twrp-custom-recovery-idol3-6045-t3162608
8: fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
10: rebooted
11: scratched head as default recovery booted.
so i am assuming i need to apply root before flashing custom recovery?
thanks in advance for any help provided.
Click to expand...
Click to collapse
I had to use Flashify to get it to stick on my 60450. Otherwise, I would have to use commands to get it to boot into TWRP rather than stock.

5.5" cricket here.
it boots into twrp till it loads the os wich seems to repair the recovery.
be annoying if it is self repaiiring.

ok root applied.
how do i flashify twrp.

Related

[Q] After erasing the recovery with fastboot my LG p350 don't start

Hello,
I have followed a tutorial for solving the problem of "Fastboot mode started
udc_start()" from this thread http://forum.xda-developers.com/showthread.php?t=2131247 and something was go wrong.
I have done this steps in the sdk platform tools folder:
1- fastboot erase recovery
2- fastboot flash recovery recovery.img ( here i've got an error)
3- fastboot reboot
Everyting was ok until I have tried to write the .img file on the phone. I've got an error that I don't have enough space. I think I have deleted the recovery file and now it's stuck, because it's not booting. The 4 leds from the bottom it's flashing continuously and the screen remains to the LG logo. I have tried to connect the phone to the PC but the device it's not recognized anymore. I get this message in the adb tool "Waiting for device"
I really appreciate if it's someone that can help me
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Logan_M said:
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Click to expand...
Click to collapse
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
catalin11 said:
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
Click to expand...
Click to collapse
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Logan_M said:
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Click to expand...
Click to collapse
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
catalin11 said:
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
Click to expand...
Click to collapse
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
catalin11 said:
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
Click to expand...
Click to collapse
now i'm in the emergency mode
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
some1 pls help me
catalin11 said:
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
Click to expand...
Click to collapse
can u plz elaborate...i too have the same problem....plz..
Logan_M said:
If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located.
Click to expand...
Click to collapse
That is incorrect. The recovery does NOT have to be named recovery to use fastboot to flash it, although it does make life simpler

[Downlad} ADB Essentials Kit By DroidScoop.net

ADB Fastboot Essentials Kit By DroidScoop.net
This kit includes all the files necessary to run the android debug bridge or (ADB) while in Fastboot.
We've taken the time to extract all the files from the android SDK, as well as provide a walk through sheet that provides most of the commands necessary while using the ADB.
This is not a guide on how to use or set up ADB but a compilation of the essential files.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Whats included:
-ADB.exe
-AdbWinApi.dll
-AdbWinUsbApi.dll
-Fastboot.exe
-Read Me Guide.txt
-ADB Commands Cheat Sheet.txt
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[COMMAND LIST]
FASTBOOT DEVICES
FASTBOOT REBOOT
FASTBOOT REBOOT-BOOTLOADER
FASTBOOT REBOOT-RECOVERY
FASTBOOT OEM UNLOCK
FASTBOOT OEM LOCK
FASTBOOT ERASE SYSTEM
FASTBOOT ERASE BOOT
FASTBOOT ERASE DATA
FASTBOOT ERASE CACHE
FASTBOOT ERASE RECOVERY
FASTBOOT FLASH RECOVERY ___.IMG
FASTBOOT FLASH HBOOT ___.IMG
FASTBOOT FLASH RADIO ___.IMG
FASTBOOT FLASH USERDATA ___.IMG
FASTBOOT FLASH SYSTEM ___.IMG
FASTBOOT FLASH BOOT ___.IMG
FASTBOOT UPDATE ___.ZIP
[DOWNLOAD]
Download our Kit at this DEV Host URL: http://d-h.st/oW7
If you have questions about the ADB itself feel free to ask
We hope this tool is a useful and convenient and as always please leave feedback and support our team!
Visit DroidScoop.net
Thank you,
Team Droid Scoop
DO NOT DOWNLOAD! 4 kinds of malware(detected, hopefully not more) in file
DroidScoop said:
ADB Fastboot Essentials Kit By DroidScoop.net
This kit includes all the files necessary to run the android debug bridge or (ADB) while in Fastboot.
We've taken the time to extract all the files from the android SDK, as well as provide a walk through sheet that provides most of the commands necessary while using the ADB.
This is not a guide on how to use or set up ADB but a compilation of the essential files.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Whats included:
-ADB.exe
-AdbWinApi.dll
-AdbWinUsbApi.dll
-Fastboot.exe
-Read Me Guide.txt
-ADB Commands Cheat Sheet.txt
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[COMMAND LIST]
FASTBOOT DEVICES
FASTBOOT REBOOT
FASTBOOT REBOOT-BOOTLOADER
FASTBOOT REBOOT-RECOVERY
FASTBOOT OEM UNLOCK
FASTBOOT OEM LOCK
FASTBOOT ERASE SYSTEM
FASTBOOT ERASE BOOT
FASTBOOT ERASE DATA
FASTBOOT ERASE CACHE
FASTBOOT ERASE RECOVERY
FASTBOOT FLASH RECOVERY ___.IMG
FASTBOOT FLASH HBOOT ___.IMG
FASTBOOT FLASH RADIO ___.IMG
FASTBOOT FLASH USERDATA ___.IMG
FASTBOOT FLASH SYSTEM ___.IMG
FASTBOOT FLASH BOOT ___.IMG
FASTBOOT UPDATE ___.ZIP
[DOWNLOAD]
Download our Kit at this DEV Host URL: http://d-h.st/oW7
If you have questions about the ADB itself feel free to ask
We hope this tool is a useful and convenient and as always please leave feedback and support our team!
Visit DroidScoop.net
Thank you,
Team Droid Scoop
Click to expand...
Click to collapse
Thanks a lot

[Completed] Moto G2 UTAG Flashfail Configured As Fastboot

Hi
I tried to root my Moto G2 running android 5.0.2 following a tutorial I found on technoprotocol.com (can't post link as I am new to forum.)
I booted into fastboot mode as per the instructions (after enabling usb debugging) and tried to root. Unfortunately I got an error (I didn't catch what it said) and now my phone only boots into fastboot and I can't go into any of the sub-menus ("recovery", "factory" etc.)
I downloaded minimal adb and fastboot and tried the command:
Code:
fastboot oem fb_mode_clear
However it still boots into fastboot and wont let me go into submenus or boot into android.
Any help wold be greatly appreciated.
It now seems to be working after I ran these commands through ADB FastBoot.
Code:
fastboot erase userdata
and
Code:
fastboot reboot

Tried to root moto g 2015 indian version with kingroot app now stuck in startup menu

I tried to root my MOTO G 2015 XT1550 using KINGROOT app.At that time it was running marshmallow 6.01 ,after running the kingroot application the phone restarted and stuck in startup menu with fastboot mode.Please help me out of this
Are u able to open stock recivery?
And have unlocked bootloader?
Amirphp said:
Are u able to open stock recivery?
And have unlocked bootloader?
Click to expand...
Click to collapse
No,I have not unlocked the bootloader,what i did was that i installed kingroot app and tried to root from the app.I don't know what it did to my device but now its stuck in fastboot mode.Please tell me how to open stock recovery.
divyandu said:
I tried to root my MOTO G 2015 XT1550 using KINGROOT app.At that time it was running marshmallow 6.01 ,after running the kingroot application the phone restarted and stuck in startup menu with fastboot mode.Please help me out of this
Click to expand...
Click to collapse
1. Stay calm.
1.a You cannot root your phone without unlocking bootloader.
1.b. You will need to do a thorough reading of how to unlock bootloader from threads in this forum or else where. You will also need to read and understand the process of fastboot mode of flashing stock firmware.
2. Since you are able to enter fastboot mode connect your mobile to your PC with your USB chord, open the minimal adb fastboot mode, try to get the unlock key, visit Motorola site and get your bootloader unlock key. There are other threads explaning how to do this. Download the correct stock firmware identified based on the phone model no. Eg xt1550 dual sim and store it onto your PC, you will also need the minimal adb fastboot file, Motorola drivers, twrp3.0., SuperSU 2.62-3 ( no other version of SuperSU works, only this version)
3. Once you unlock your bootloader, flash the stock firmware which you need to download from other thread of this forum using fastboot mode. Note, marshmallow 6.0.1 has 7 sparsechunk files. So be careful about fast boot commands. Do not use the commands you find on the stock firmware thread blindly as these have commands only for 6 sparsechunk files. You may open the flash file from the downloaded firmware to get an idea of all the commands to be typed and their respective partitions too.
4. Flash twrp to replace stock recovery. Enter recovery from fastboot mode using volume keys to navigate and powerkey to select.
5. Once into twrp, press mounts tab and tick to mount USB storage, and copy the SuperSU 2.62-3 file into the external memory card of your phone from pc. Install this SuperSU.zip file without unzipping it by pressing the install tab in twrp home screen and selecting the zip file and sliding the installer.
6. Reboot system. Done! You have your phone rooted the perfect way.
When I switch on my device(moto g3) the following message appears.
Start Up Failed
Your device didn't startup successfully.
Use the Software Repair Assistant on your computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation,backup to fastboot
Boot up failed
Please help with a solution asap??
divyandu said:
When I switch on my device(moto g3) the following message appears.
Start Up Failed
Your device didn't startup successfully.
Use the Software Repair Assistant on your computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation,backup to fastboot
Boot up failed
Please help with a solution asap??
Click to expand...
Click to collapse
Dear friend please have patience...
These things require a cool mind...
Did you try the hardware way of entering the fastboot mode? If not keep the volume down and power button pressed for some time till ulyou enter fastboot mode. Basically there is no info if you have tried to follow what was given earlier...have you tried it?
I am unable to unlock the bootloader from adb.
The problem I think is that my phone's USB debugging is off.Anybody plz tell me how do I turn my bootloader on from fastboot or recovery mode.
divyandu said:
No,I have not unlocked the bootloader,what i did was that i installed kingroot app and tried to root from the app.I don't know what it did to my device but now its stuck in fastboot mode.Please tell me how to open stock recovery.
Click to expand...
Click to collapse
@divyandu follow this and let me know if it works.
http://forum.xda-developers.com/2015...k-6-0-t3349468
you can get the Factory Firmware's on this Link.
http://forum.xda-developers.com/2015...mages-t3169639
divyandu said:
I am unable to unlock the bootloader from adb.
The problem I think is that my phone's USB debugging is off.Anybody plz tell me how do I turn my bootloader on from fastboot or recovery mode.
Click to expand...
Click to collapse
Dear friend,
You need not have your bootloader unlocked to flash factory firmware
Quote from the XDA forum factory firmware link:
"Frequently Asked Questions:
Can I restore Factory Firmware if my Bootloader is locked?
Yes."
And if you are still stuck with a phone stuck at logo or is looping at the boot, either follow steps given elsewhere in this forum or follow the method that I am enumerating below which is what I would have done (which in principle is same as given elsewhere).
Getting your phone revived is your first priority. Unlocking bootloader and rooting is secondary.
You would be needing a pc with administrator privilege, internet connection and of course your phone along with the usb cable.
You would be needing the drivers for your phone, minimal adb and fastboot files, stock firmware for your phone model. All these files are available in the XDA forum as per links provided by others or as per this link
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
1. Correctly install drivers onto your pc using administrator privileges.
2. Unzip and Install the minimal adb and fastboot files onto your pc into some specific directory and click the executable files once. This would ensure that all the files are loaded and dos prompt recognizes the adb and fastboot commands (commands are different for ADB stage and FASTBOOT stage, what you are going to use is directly the fastboot stage commands given below). Install as an administrator. Note this specific directory and file where you unzipped and installed the minimal adb file as you will need it in the below step.
3. Download the stock 6.0.1 mm firmware for XT1550 from the link below store it in you pc.
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Unzip the stock firmware. Now copy all the files of the stock firmware (all of them) into the specific file of the minimal adb and fastboot which you unzipped into and installed earlier and noted the location. You need to copy all the firmware files into the minimal adb and fastboot directory as that way you avoid specifying the location of the files for each flash command which is both simple and saves us from a lot of mistakes.
4. After copying all the unzipped stock firmware files in the minimal adb fastboot directory, press the shift button on keyboard and right click the mouse on the screen where in a dialogue box appears and choose to open the command prompt in this directory. This will open a command prompt with default reference to the current directory.
5. In what ever condition your phone is in (other than the fastboot mode), press simultaneously the volume down key + power button together for about 8-10 secs. This action will automatically lead your phone to enter the fastboot mode. After entering the fastboot mode you can connect the phone to your pc using a usb cable and your pc should ring a note that it has detected the phone. To check if the pc has detected the phone and the link is established, type the following command in the command prompt window which you opened in step 4
fastboot devices
This command displays your device number if all is well in the command prompt window. NOW you are ready to flash the stock firmware I.E. after successful detection of the phone by your pc.
6. Carefully type each and every of the commands in italics or copy and paste them ONE by ONE and wait for each command to be executed. The commands are being given below to help you (these are for flashing the 6.0.1mm onto the XT1550 only) in the opened command prompt window (Ensure that you do not miss any of the commands and follow the order given below) :
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 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 fb_mode_clear
fastboot reboot
If you have done every thing correctly till now you should see the command prompt returning a OKAY afer each command with the time taken for flashing each file. This should revive your device first.
After this you may try unlocking the bootloader and rooting as the next step. But be patient and retain a cool head to read first and think clearly..... you will need it a lot as is necessary for such things... good luck and happy learning!!
Follow the instructions in this thread ...to unlock bootloader and root...
Works 100%.
http://forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113
arunhebbare said:
Dear friend,
You need not have your bootloader unlocked to flash factory firmware
Quote from the XDA forum factory firmware link:
"Frequently Asked Questions:
Can I restore Factory Firmware if my Bootloader is locked?
Yes."
And if you are still stuck with a phone stuck at logo or is looping at the boot, either follow steps given elsewhere in this forum or follow the method that I am enumerating below which is what I would have done (which in principle is same as given elsewhere).
Getting your phone revived is your first priority. Unlocking bootloader and rooting is secondary.
You would be needing a pc with administrator privilege, internet connection and of course your phone along with the usb cable.
You would be needing the drivers for your phone, minimal adb and fastboot files, stock firmware for your phone model. All these files are available in the XDA forum as per links provided by others or as per this link
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
1. Correctly install drivers onto your pc using administrator privileges.
2. Unzip and Install the minimal adb and fastboot files onto your pc into some specific directory and click the executable files once. This would ensure that all the files are loaded and dos prompt recognizes the adb and fastboot commands (commands are different for ADB stage and FASTBOOT stage, what you are going to use is directly the fastboot stage commands given below). Install as an administrator. Note this specific directory and file where you unzipped and installed the minimal adb file as you will need it in the below step.
3. Download the stock 6.0.1 mm firmware for XT1550 from the link below store it in you pc.
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Unzip the stock firmware. Now copy all the files of the stock firmware (all of them) into the specific file of the minimal adb and fastboot which you unzipped into and installed earlier and noted the location. You need to copy all the firmware files into the minimal adb and fastboot directory as that way you avoid specifying the location of the files for each flash command which is both simple and saves us from a lot of mistakes.
4. After copying all the unzipped stock firmware files in the minimal adb fastboot directory, press the shift button on keyboard and right click the mouse on the screen where in a dialogue box appears and choose to open the command prompt in this directory. This will open a command prompt with default reference to the current directory.
5. In what ever condition your phone is in (other than the fastboot mode), press simultaneously the volume down key + power button together for about 8-10 secs. This action will automatically lead your phone to enter the fastboot mode. After entering the fastboot mode you can connect the phone to your pc using a usb cable and your pc should ring a note that it has detected the phone. To check if the pc has detected the phone and the link is established, type the following command in the command prompt window which you opened in step 4
fastboot devices
This command displays your device number if all is well in the command prompt window. NOW you are ready to flash the stock firmware I.E. after successful detection of the phone by your pc.
6. Carefully type each and every of the commands in italics or copy and paste them ONE by ONE and wait for each command to be executed. The commands are being given below to help you (these are for flashing the 6.0.1mm onto the XT1550 only) in the opened command prompt window (Ensure that you do not miss any of the commands and follow the order given below) :
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 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 fb_mode_clear
fastboot reboot
If you have done every thing correctly till now you should see the command prompt returning a OKAY afer each command with the time taken for flashing each file. This should revive your device first.
After this you may try unlocking the bootloader and rooting as the next step. But be patient and retain a cool head to read first and think clearly..... you will need it a lot as is necessary for such things... good luck and happy learning!!
Click to expand...
Click to collapse
Ty everyone for the support and the quick answers.My phone is unbricked and is running 6.0.1
Special thanks arunhebbare your suggestion worked out finally
I tried to root my MOTO G 2015 XT1550 using KINGROOT app.At that time it was running marshmallow 6.01 ,after running the kingroot application the phone restarted and stuck in startup menu with fastboot mode.
:crying: When I switch on my device(moto g3) the following message appears.
Start Up Failed
Your device didn't startup successfully.
Use the Software Repair Assistant on your computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation,backup to fastboot
Boot up failed
plz help me
vidya_sagar said:
I tried to root my MOTO G 2015 XT1550 using KINGROOT app.At that time it was running marshmallow 6.01 ,after running the kingroot application the phone restarted and stuck in startup menu with fastboot mode.
:crying: When I switch on my device(moto g3) the following message appears.
Start Up Failed
Your device didn't startup successfully.
Use the Software Repair Assistant on your computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation,backup to fastboot
Boot up failed
plz help me
Click to expand...
Click to collapse
You tried the above solution a few posts back??
Broadcasted from Zeta Reticuli
Gravemind2015 said:
You tried the above solution a few posts back??
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
i'm not sure about Enabling USB debugging. is that above process will work??when i don't enable usb debugging?
tnx for ur reply
---------- Post added at 10:45 AM ---------- Previous post was at 10:07 AM ----------
vidya_sagar said:
i'm not sure about Enabling USB debugging. is that above process will work??when i don't enable usb debugging?
tnx for ur reply
Click to expand...
Click to collapse
if u dont mind can u post the vedio of this process
bad
iam unlocked my boot loader in my moto g3 running 6.0.1...after i try to flash twrp to root ..but it is no worked ..so i use king root app to root my phone root installed successfully ...but my sims signels are not showing ...so i do hard reset ...after phone is on and stucks at language selection what should i do
vidya_sagar said:
i'm not sure about Enabling USB debugging. is that above process will work??when i don't enable usb debugging?
tnx for ur reply
---------- Post added at 10:45 AM ---------- Previous post was at 10:07 AM ----------
if u dont mind can u post the vedio of this process
Click to expand...
Click to collapse
My internet is not fast enough for a video upload sorry. But if you are not sure about the process you can search lost101's firmware flashing guide in general section. I have flashed it and it works.
Broadcasted from Zeta Reticuli

How To Guide Restore OnePlus 9 to Stock via Fastboot Commands

This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, then hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Final reboot:
Code:
fastboot reboot
7. If everything worked your phone should now boot into OxygenOS.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To check current slot:
Code:
fastboot getvar current-slot
To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. This will wipe your device! Reboot to the bootloader and run:
Code:
fastboot -w
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Edit: script attached. I've (unfortunately) had the opportunity to test it and fix all the bugs. So it works. You will need to have fastboot.exe accessible in your system PATH to run it.
Slikkster2k said:
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. Reboot to the bootloader and run:
Code:
fastboot -w
This will wipe your device!
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot bootloader
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Click to expand...
Click to collapse
That would be helpful indeed. Would this script run on mac as well?
Not unless there's a version of PowerShell for macs (there is for Linux, but I don't know if it's compatible).
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
AxelM said:
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
Click to expand...
Click to collapse
I used 11.2.2.2.LE25AA as I said in the original post (this is the global variant, which matches my device). I am not sure if this works for cross-flashing, or if it's possible to cross-flash an Indian phone to EU. Have you tried restoring the Indian ROM? Does that work?
You're getting an actual boot loop? The error I was getting (and the reason I had to restore) was the phone booting to the bootloader or fastbootd (depending on the slot I tried) instead of Oxygen, because it couldn't mount the user partition due to encryption. In fastbootd an error was reported (I forget the exact one) which made me suspect it was a partition mounting issue. At no point was my phone actually boot looping, even during partial/failed flashes.
I've never encountered the error with fastboot -w, but I only did that on my phone once. From some searching online, it can be caused by an old version of the platform tools, so did you download the latest version?
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
AxelM said:
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
Click to expand...
Click to collapse
Glad to hear you got it working!
PowerShell script added to second post. Totally untested, but I tried to make it as idiot proof as possible.
Slikkster2k said:
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Reboot back into the bootloader:
Code:
fastboot reboot bootloader
7. You should now be able to continue booting normally by pressing the power button.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
Click to expand...
Click to collapse
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
toyanucci said:
That would be helpful indeed. Would this script run on mac as well?
Click to expand...
Click to collapse
Windows offered now to add to MAC - https://support.apple.com/en-us/HT201468
toyanucci said:
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
Click to expand...
Click to collapse
Thanks, updated OP.
ok i kind of bricked my phone using this and i need a little help PLEASE?
Ok i tried the fist 2 steps 1. fastboot -w than the first list of commands using cmd with admin rights it worked...i think but it did load everything without issues...now i go to do the "fastboot reboot fastboot"
and now my phone is stuck on a black screen with nothing and i just hear the chime windows makes when you disconnect and reconnect a device..... and in the Device manager this comes up for 10 seconds than goes away for 5 than comes back NON STOP
i cant adb i cant do anything please help !
I'm not sure if this will help you, but I had a lot of issues initially running this. First off you need to use the Oneplus drivers, I don't think the qualcom driver will work the same way. I could be wrong, but that's what I did. Secondly, you need to force install the driver because Windows doesn't like it.
Here are the steps I took.
1. Uninstall any old drivers.
2. Install the newest Oneplus Drivers from here https://oneplususbdrivers.com/
3. Extract the zip file and run the installer like normal
4. Once the installer finishes, you'll need to reboot your machine and bring up the Startup settings (hold down shift and reboot (keep holding down shift until you get a screen with options)) Then click advanced and startup settings and hit restart after that. Once the machines starts up, on the first boot you will have a bunch of options. Choose option 7 "disabling driver signature enforcement" mode.
5. Once Windows launches and you login, go back into the device manager and follow these steps:
right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.
----------------------------------------
The above should get your drivers working properly in all modes (adb, fastbootd, bootloader, normal)
One other issue that I ran into when I was using the powershell script was that I was seeing intermittent errors. After trial and error I realized that Windows was picking up a different version of fastboot. I was initially using the minimal adb/fastboot files, but if you compare those to the ones listed in the first post in the "SDK Platform Tools", they are very different from each other, so you need to make sure you use the SDK Platform Tools version. The minimal ADB/Fastboot version will NOT work.
After I got those 2 things ironed out, the powershell script ran without a hiccup and my phone is stock and booting without an issue.
I know I'm late to respond to this thread, but I hope someone finds this information helpful!
Mine keeps trying this and it isn't running and or rebooting into Fastbootd when the script is ran. Should I just try and invoke this manually? I've tried that as well an I'm seeming to get errors left and right with no resolve.
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Good work
toyanucci said:
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Click to expand...
Click to collapse
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
ilikepie___ said:
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
Click to expand...
Click to collapse
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
toyanucci said:
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
Click to expand...
Click to collapse
I’ll give it a shot, yeah it doesn’t do anything. Can’t see a display or anything on the screen.

Categories

Resources