Hi, I am relatively familiar with fastboot commands having had many android devices on which I had unlocked the bootloader but I haven't really found clarification on the difference between these commands.
I understand that boot and bootloader are different but how and will wiping one wipe the other as well, I also know that the command fastboot erase bootloader should NEVER be used.
So what is different between boot and bootloader.
Never mind I think I have resolved the issue if anyone else is confused.
Boot is where the kernel and files that the system has to boot are stored whereas bootloader is where the file that boots the boot.img files is.
Once again NEVER use the command fastboot erase bootloader
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 a Motorola Xoom from Verizon, and this is the issue.
When I turn on, the tablet it's stuck in M logo screen, I already read almost any information about this issue, but still I can't use my xoom.
I already done this: the bootloader is already unlock
a) Files From MZ600 HRI39
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
b) used RSD method
c) used recovery method too
I had used every method on this forum to recover my Xoom, and nothing seems to work, at this time I don't know what else do.
adb commands doesn't work for me, only with fastboot and RSD is visible my device.
At this time I accept any sugestions, Since apply a factory reset, or install a new Android version
I have a serious problem: my device's partitions are all erased and formatted and the boot loader is locked which is why I can't install a recovery or anything else. fastboot oem unlock doesn't work for any reason. It just boots and does nothing. After entering fastboot again it says it's locked.
The alternative method with adb doesn't work as I don't have a recovery nor do I have a system.img on the device. I can only enter fastboot now and flash the radio. How can I flash stock CM11S now? I need to unlock the bootloader and fastboot won't let me!
h**p://forum.xda-developers.com/showpost.php?p=55952004&postcount=457
Guy with a similar problem, who found a solution... Give it a try!
How on earth did you manage to erase all the partitions?
Transmitted via Bacon
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
Ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img"
When trying install TWRP for the first time on a new (to me) Pixel 3, after unlocking the bootloader I ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img". Can still enter the bootloader, but anything else gives a black screen.
What is the best method to recover from this? I still have access while in the bootloader through fastboot. Should I reflash stock google images or is something else better to recover? If I should reflash the stock google images what is the best method to do so?
Yes after reading more I realize this was the wrong thing to do. "fastboot boot twrp.img" was not working so I figured to try flashing instead, but afterwards realized that was obviously wrong.
Thanks for any help.
OK, It looks that I am soft bricked and a factory image reset is the only way to recover.
The steps I've seen mostly commonly referenced are to run the following
Code:
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
flash-all.bat (using the factory images)
The issue seems to be that Android 10 which was on the phone doesn't work with fastboot erase. Is it necessary to run this or is it OK to go straight to flash-all.bat? (BTW I finally figured out that my issue above was TRWP doesn't support android 10 yet, but the guides I saw were older and didn't mention that. )
twfry said:
When trying install TWRP for the first time on a new (to me) Pixel 3, after unlocking the bootloader I ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img". Can still enter the bootloader, but anything else gives a black screen.
What is the best method to recover from this? I still have access while in the bootloader through fastboot. Should I reflash stock google images or is something else better to recover? If I should reflash the stock google images what is the best method to do so?
Yes after reading more I realize this was the wrong thing to do. "fastboot boot twrp.img" was not working so I figured to try flashing instead, but afterwards realized that was obviously wrong.
Thanks for any help.
Click to expand...
Click to collapse
First things first. TWRP does not work at all on a Pixel with Android 10. Flash-all should be all you need to do to recover from your issue.
sliding_billy said:
First things first. TWRP does not work at all on a Pixel with Android 10. Flash-all should be all you need to do to recover from your issue.
Click to expand...
Click to collapse
The 3 top guides from google all had steps for android 9 apparently and so I didn't catch that 10 is different..... flash-all.sh worked and we're back. Thanks!