I am just glad it wasn't my everyday phone..I am new to the whole "rooting" process, i was trying it on my old moto g(7) play XT1952-6, and i wasn't have very much luck, i finally was able to fash it and tried to install a custom rom, when my phone rebooted it is now stuck on fastboot mode and my bootloader is now locked again...It is showing different specs on the device now also, when i looked it up it in reading as an M92 Desktop (ThinkCenter) type 2119ABF...I can no longer turn the device on and with the bootloader locked i can not flash again..the (LMSA) is not able to rescue it either...is there anything i can do to fix it?
can you enter fastboot?
wojtess said:
can you enter fastboot?
Click to expand...
Click to collapse
the phone itself is stuck in fastboot, it doesnt go into anything else...i had already unlocked the bootloader and enabled the usb settings but it locked everything up again..
Try this
Code:
mfastboot devices
mfastboot reboot
to exit Fastboot mode.
http://downloadmirror.co/android/29Sh/mfastboot-v2.zip
jwoegerbauer said:
Try this
Code:
mfastboot devices
mfastboot reboot
to exit Fastboot mode.
http://downloadmirror.co/android/29Sh/mfastboot-v2.zip
Click to expand...
Click to collapse
i tried this and didnt work...my phone does say "fastboot reason: failed to initialize partition table..
Related
Flashed Build HWI69 for US Retail on a Canadian wifi MZ604 xoom..tired of
waiting for 3.1 update.
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
It is stuck on Starting RSD mode 2.
I can not get it to fastboot protocol...device does not turn off.
Any solutions?
Fastboot OEM lock is where you went wrong. Anyway see this thread.
OK I did this procedure yesterday but did not relock (I know it says to on the moto site but the guide I read said not to).
Anyway, pressing power and vol up will force a reboot. Unsure what will happen when it boots back up though...!
You should be fine. Only trying to relock will cause this error.
To get back to fastboot after a bad lock do this.
Power button and volume up, this will reboot the device.
As soon as the screen turns back on holds down power and volume down. In about 60 seconds your device should go to fastboot. Do not let go until it gets there.
Sent From My Evo
Thanks for the reply . It now says Failed to boot LNX 0X0004
Starting Fastboot protocol support
However it will not connect to xoom.
<wait for device> when issue fastboot command.
What the hell is going on?
you need to read this thread
http://forum.xda-developers.com/showthread.php?t=1108518
The exact thread I linked to...(-__-)'
I followed instruction from motorla dev support site.
"h**p://developer.motorola.com/products/software/?pubid=987654"
It uses command "fastboot oem lock"! So why did locking brick the device?
here it is:
Device Software Images
Select the appropriate device software image to download and re-lock your device. If you need to find your build number on your Motorola device go to Settings and About Phone or About Tablet.
The commands to flash and re-lock your device are as follows:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata
The Moto instructions are for locking the device back to it's own image. You are not using your device's own image. Every guide I've seen on here tells you not to relock, regardless of what Moto say. Believe the devs.
Thanxs
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
tfx1 said:
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
Click to expand...
Click to collapse
Try making or obtaining a factory cable which its different from an OTG cable. Start with the two links below. This might save the day.
http://forum.xda-developers.com/showthread.php?t=1077414
http://forum.xda-developers.com/showthread.php?t=1108518
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
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Ferguson35000 said:
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Click to expand...
Click to collapse
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Ferguson35000 said:
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Click to expand...
Click to collapse
I got this problem when installing CWM too. I believed the problem is in this line:
fastboot flash recovery CWM-6.0.5.0-peregrine.img
Click to expand...
Click to collapse
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
UncolourTV said:
I got this problem when installing CWM too. I believed the problem is in this line:
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
Click to expand...
Click to collapse
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Ferguson35000 said:
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Click to expand...
Click to collapse
I have the same issue with this program under linux or windows, it doesn't recognize my device. I have activated USB debug, tried under bootloader or with the phone normally started but nothing better.
only fastboot boot recovery.img works.
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
hacktrix2006 said:
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
Click to expand...
Click to collapse
Thank you for answering.
I will try this then come back.
Ferguson35000 said:
Thank you for answering.
I will try this then come back.
Click to expand...
Click to collapse
Same error :
I still have the mismatch thing with mfastboot ...
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
hacktrix2006 said:
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
Click to expand...
Click to collapse
Hello, I have bought the phone less than one month ago.
It was directly on 4.4.4 after unpacking.
Have you tried renaming the CWM file? Maybe the "-" are a problem although I highly doubt it. Did you try re downloading the file? Running the command window as an administrator? Last resort, you could use TWRP, I'm running on this currently and haven't had any problems installing/flashing ROMs with it and imo prefer it over CWM.
Click to expand...
Click to collapse
I have tried both and they both have the same problem :/ CWM as well as TWRP...
Still no idea what happens.
same problem
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
kosamuky said:
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
Click to expand...
Click to collapse
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Back to stock
Ferguson35000 said:
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Click to expand...
Click to collapse
Yes its normal if you have unlocked your bootloader
To get back to stock, download a stock Fw for your device model and region, you can find a link for one if you enter the moto g section of this site and head to moto 4g lte android development section (only section specifically for peregrine model) unpack the fw files into your fastboot directory (windows) reboot your phone to fastboot mode (where u saw the status code) then press control + shift + right click to launch a command prompt window here (from within fastboot directory in windows) then copy and paste these fastboot commands 1 by 1 pressing enter each time until compete.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
So you mean, it is compulsory to have stock ROM in order to install the recovery ?
Because my problem is not to return to stock, it is to install a proper recovery (CWM or TWRP) in order to boot on it without my computer.
Thanks for your help
No but I think your problem is you have corrupt the recovery partition size maybe through bad flash or something so ur unable now to flash a recovery as the partition size is for different device or damaged and flashing cwm will no longer work as the cwm image is too big or too small for the allocation assigned to it as the devices core partition table has changed (can happen when u flash something for the falcon when you have a peregrine), I would flash back to stock via that method to restore to stock partition sizes and then reroot and flash cwm again after, just a guess from my own understanding.
Sent from my XT1039 using XDA Free mobile app
Guys I had the same trouble installing the recovery with the mismatched partition size message. This message is normal and the recovery is already installed on your device. The problem i had when selecting the recovery with the following black screen was that I used the Power Button instead of the up Button.
5) using volume down scroll to recovery and then use volume up to select
Long story short I bricked my phone when trying to flash recovery using toolkit. Now my phone won't turn on and recovery is gone as well. Somehow my PC can recognize the phone in fastboot mode although there's nothing showing on the screen.
So I tried the method in this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
It shows I flashed everything and it shows green color in the tool but when I checked the partitions, boot.img, recovery.img, userdata.img, system.img, etc are still broken. At that time the bootloader was still unlocked.
Since my computer can still see the phone in fastboot so I tried to flash the original image in fastboot. Again everything went through with no error but the phone still wouldn't turn on and the partitions are still same broken/corrupted. However the bootloader became locked after this. So now I end up with no more solutions. Since bootloader says locked(although boot.img is actually corrupted) I can't flash or do anything in fastboot command.
So I guess I'm really SOL right now... My only hope right now is maybe there will be USB JTAG or Nand flasher but I don't know if anyone can repair that right now.
Any suggestions?
fastboot oem unlock
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
Now use twrp or cwm or whatever
fastboot boot recovery nameofrecovery.img
If your phone boots to recovery you may consider running e2fsck against data and cache partitions through adb shell
Best of luck
Hi all,
I bricked my phone trying to install TWRP, and then I double F-d up when stopping the MSM Download Tool after some minutes of not working. Now nothing works... except that I tinkered a bit and miraculously Fastboot works!
But, when I try to install one by one the .img files, some of them can't be installed as it says that it cannot install on a protected partition. Trying fastboot flashing unlock_critical or fastboot flashing unlock is not recognised by fastboot...
Where do I go from here? Thanks all in advance!
massa said:
Hi all,
I bricked my phone trying to install TWRP, and then I double F-d up when stopping the MSM Download Tool after some minutes of not working. Now nothing works... except that I tinkered a bit and miraculously Fastboot works!
But, when I try to install one by one the .img files, some of them can't be installed as it says that it cannot install on a protected partition. Trying fastboot flashing unlock_critical or fastboot flashing unlock is not recognised by fastboot...
Where do I go from here? Thanks all in advance!
Click to expand...
Click to collapse
You will get fastboot errors about unlocking critical partitions if you try to flash partitions other than boot, recovery and a few others while you're in bootloader mode.
For the rest you must be in fastbootd mode.
You need to enter one more command , "fastboot reboot fastboot" , you will be in fastbootd then you can enter you following flashing or earsing commands