Related
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
So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked
Megadarkwood said:
So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked
Click to expand...
Click to collapse
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
http://waynekent.com/page6.html
NWKENT said:
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
Click to expand...
Click to collapse
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version
Megadarkwood said:
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version
Click to expand...
Click to collapse
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >> http://sbf.droid-developers.org/phone.php?device=14
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >>
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.
Megadarkwood said:
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.
Click to expand...
Click to collapse
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #
Click to expand...
Click to collapse
I am not concerned about any data, just need to get it working. I will flash TWRP as soon as I get back to my computer
Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app
NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
nArdow said:
Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, how am I supposed to sideload the .img for TWRP?
Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk
Clarkiieh said:
Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Won't work, says "Waiting for Device"
Megadarkwood said:
Won't work, says "Waiting for Device"
Click to expand...
Click to collapse
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
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
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.
The Closet Candian said:
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
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
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.
Click to expand...
Click to collapse
Alright, but do I need a OS file or something in the folder before I do this?
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"
Megadarkwood said:
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"
Click to expand...
Click to collapse
Since you are in fastboot mode you should use "fastboot devices".
meekrawb said:
Since you are in fastboot mode you should use "fastboot devices".
Click to expand...
Click to collapse
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
Only thing I can think of is to re-install the drivers or try different USB ports.
Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.
eg0097 said:
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.
Click to expand...
Click to collapse
Got TWRP on and everything flashed but carbon is still in a boot loop.
Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk
Clarkiieh said:
Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yeah I hear the beep.
Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.
Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk
Go to bootloader and run "fastboot devices" and see whether your device gets detected or not? If it does, then flash the factory images. System and boot img files would do the job.
If it doesn't then you need to fix the adb, fastboot issues first. Follow these threads:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
If you have an OTG cable with you, you can directly flash the rom from a usb stick!
tangosierra_ said:
Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
You havent got fastboot installed.
Go to teh link in my signature.... Then go to section 1b, 1
usb/otg
Dixi1801 said:
Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.[/QUOT
Download any compatible rom to a usb/otg..mount from TRWP and your good to go..Happens to me once..Just download any compatible roms just to bring up your phone..
Click to expand...
Click to collapse
Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
remove all old drivers and restart
install http://forum.xda-developers.com/showthread.php?p=42407269&__utma=248941774.1031819907.1403635167.1403781687.1403790944.7&__utmb=248941774.1.10.1403790944&__utmc=248941774&__utmx=-&__utmz=248941774.1403790944.7.7.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m
shhbz said:
remove all old drivers and restart
install http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m
Click to expand...
Click to collapse
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk
rootSU said:
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great and flash-all.bat script does not work evrytime so just wanted the guy to be sure the he type the commands in right direction instead getting error cant find and stuff
shhbz said:
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great
Click to expand...
Click to collapse
1b1 in the link in my signature.
Minimal is fine but you have to manually add to environment variables or cd to the directory but that's all done with the 15 seconds one.
Sent from my Nexus 5 using Tapatalk
Thanks for the help guys.
RootSU, you saved me haha, was sat at work stressing trying to sort the mess I made out!
I'm all stock now... But the screen keeps going off because of the proximity sensor haha -_-
Thanks again though. Can always count on a Yorkshireman
The important thing is to remain calm and know it can be fixed
Sent from my Nexus 5 using Tapatalk
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
It's very, very, unfortunate that this happened so early in the life of my new Pixel 2. Here's what I did:
fastboot oem unlock
Device erases and boots normally, power off and boot into bootloader using volume and power.
Flash Android 8.1 beta using flash-all.bat
<Device is stuck in bootloader>
Flash factory Android 8.0 image, same thing
Try "fastboot --set-active=a" followed by "fastboot continue" and "fastboot --set-active b" followed by "fastboot continue", neither worked.
Try entering recovery or download mode from bootloader, neither worked.
I contacted Google support, and they didn't have any suggestions other than an RMA, so a new device should be on the way soon. Given the comments in this thread about using the wrong version of fastboot, I'll point out that I do have the latest version of platform-tools, and my fastboot version is:
Code:
C:\>fastboot --version
fastboot version 3db08f2c6889-android
Installed as C:\android-platform-tools\fastboot.exe
Anyone else have this experience? (I hope not.)
Edit: Okay, thanks to this post, I learned that I flash-all.bat, which uses "fastboot -w update image-*.zip", leads to this condition. However, flashing each img file in the zip archive individually gets the device back to health. Phew.
can you share the .bat file please?
I didn't use a bat script to recover the device, I typed each "fastboot flash <partition> <partition>.img" command by hand. Not the most efficient, but I wasn't expecting to do this more than once.
It's possible you had a bad download, did you attempt to redownload the stock image?