fastboot command - One (M8) Q&A, Help & Troubleshooting

hello i try to flash a rom and i see in some web
that i can to do this with this command :
fastboot flash boot boot.img
but i confused and write
fastboot boot boot.img
now i try to enter to recovery of twrp and i cant it just show me black screen :crying:
someone help me plz.

You flashed boot.img in the recovery partition.
Download your preferred recovery and flash it with the command:
fastboot flash recovery recovery.img
you will be good to go
tamir20121 said:
hello i try to flash a rom and i see in some web
that i can to do this with this command :
fastboot flash boot boot.img
but i confused and write
fastboot boot boot.img
now i try to enter to recovery of twrp and i cant it just show me black screen :crying:
someone help me plz.
Click to expand...
Click to collapse

stathis95194 said:
You flashed boot.img in the recovery partition.
Download your preferred recovery and flash it with the command:
fastboot flash recovery recovery.img
you will be good to go
Click to expand...
Click to collapse
i succed to flash recovery but now all i try to do its write:
E:Unable to mount '/cache'

tamir20121 said:
i succed to flash recovery but now all i try to do its write:
E:Unable to mount '/cache'
Click to expand...
Click to collapse
Try to fastboot erase cache and reboot

stathis95194 said:
You flashed boot.img in the recovery partition.
Download your preferred recovery and flash it with the command:
fastboot flash recovery recovery.img
you will be good to go
Click to expand...
Click to collapse
I didn't see him mention anything about recovery. He booted the boot.img there by he would only "simulate" a boot so to speak, not?
Kinda like:
Building and booting Nexus 5 kernel
Excerpt from posted link:
Code:
$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ adb reboot bootloader
$ sudo fastboot boot boot.img
During this commands your phone will reboot to bootloader mode, next using fastboot command you'll copy the new boot image to RAM of the phone and then boot it. YOUR FLASH IS NOT TOUCHED IT'S 100% SAFE! Now just check in settings, what is version of your kernel. When you've done with hacking, and want to have the original just reboot your phone.
Click to expand...
Click to collapse
He could have just restarted the phone and flashed it properly. Maybe doing that is like booting a "virtual" copy of the Kernel on the device for testing purposes?
Either way though, it's just for the sake of interest/education, if anything else. :good:

thx for the help i succed

Related

[Q] Hardest Soft-Bricked ever seen!!! (Help me plz)

hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---

assert failed: getprop("ro.build.asus.sku") == "WW" on ZE551ml

So I flashed Euphoria OS in my Zenfone 2 ZE551ML 16GB variant but now I wanna go back to stock rom. So I downloaded a full stock rom version WW-2.19.40.22. I booted into TWRP recovery, wiped data and all and then flashed the stock rom and then this assert failed get prop error appears. I can't flash the stock rom and I'm stuck with Euphoria. Any info on how I can get back to stock rom?
hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck
knoneNull said:
hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck
Click to expand...
Click to collapse
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.
caveat13 said:
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.
Click to expand...
Click to collapse
try to charge it first , then try again, if not work i think the best is send to service center or try to message shakalaca may be he can help you

Lost Recovery mode!!!???

I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?
wisdomlight said:
I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?
Click to expand...
Click to collapse
normally I just do
Code:
fastboot flash recovery <recovery-image-file>
Also how do you attempt to boot recovery?
- VolDn+Pwr ?
- adb reboot recovery ?
What if you flash stock recovery or twrp?
do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh
wisdomlight said:
do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh
Click to expand...
Click to collapse
if you unpack cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip from cyngn.com you may try to flash stock COS 13.0 as follows:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img

can't get into recovery mode after flashing LineageOS

after flashing LineageOS when i try to get into recovery mode the phone just reboot the bootloader
DarkshadoW99 said:
after flashing LineageOS when i try to get into recovery mode the phone just reboot the bootloader
Click to expand...
Click to collapse
download latest twrp.img from official website. place it in adb fastboot tool folder. then open command prompt widows in same folder. reboot you device into fastboot mode and connect to pc now run the following command
fastboot erase recovery
fastboot flash recovery "recovery file name"
then reboot recovery mode
sukhwant717 said:
download latest twrp.img from official website. place it in adb fastboot tool folder. then open command prompt widows in same folder. reboot you device into fastboot mode and connect to pc now run the following command
fastboot erase recovery
fastboot flash recovery "recovery file name"
then reboot recovery mode
Click to expand...
Click to collapse
i got an error "Failed(Remote: Unable to format)"
DarkshadoW99 said:
i got an error "Failed(Remote: Unable to format)"
Click to expand...
Click to collapse
this show up when i try to erease recovery
DarkshadoW99 said:
this show up when i try to erease recovery
Click to expand...
Click to collapse
try flash command
sukhwant717 said:
try flash command
Click to expand...
Click to collapse
i did it but still cant get into recovery , the phone just reboot the bootloader
DarkshadoW99 said:
i did it but still cant get into recovery , the phone just reboot the bootloader
Click to expand...
Click to collapse
if you are rooted and able to boot into system. try flashing via terminal. if you are unable to boot into system report back

Phone now boot into fastboot but not system

Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)

Categories

Resources