I unlocked my bootloader. Installed TWRP and when I was on stock I updated my moto z play to 7.1.1. I know never update through OTA when custom recovery is installed. But I didn't know that earlier. Device got rebooted and directly booted into TWRP and nothing happened. I then rebooted to bootloader and started the device and it booted up!
The problem is each time the phone is rebooted it goes into recovery and i have to reboot it to bootloader to start!
How can I solve this?
I'm currently on Resurrection remix Rom!
Thanks!
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Nikepel said:
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks!
I'll try this tomorrow.
Will update after I'm done!
Got the same problem - unlocked bootloader, installed TWRP, did dual sim mod for a friend and then the "idiot" did an ota - now phone is stuck into booting to TWRP.
I tried the fastboot commands and they went through fine, but phone is still only booting into twrp - with fastboot and "start" its booting up though.
There must still be some "do-ota" flag enabled somewhere.. ?!
---
EDIT: ok well **** it - after i booted it up once normal over the fastboot start it boots normal again!
+1 with same problem.
zroice said:
EDIT: ok well **** it - after i booted it up once normal over the fastboot start it boots normal again!
Click to expand...
Click to collapse
Can you give some more details on how you managed to fix it?
I have the same problem was on stock with root and tried OTA :silly:
These fastboot commands don't work for me, does anyone have another solution?
Nikepel said:
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Perfect !!!
After flashing the android 8 version, my phone could not start normally (directly into the bootloader.)
The command lines saved my Moto lol ?
Thank you very much !
Related
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
---
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly
Hi, i need help M8 got stuck !! i was trying to follow these commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip fw_x.xx.xxx.x.zip
fastboot flash zip fw_x.xx.xxx.x.zip
fastboot reboot-bootloader
but i forget to type fastboot oem rebootRUU !!so i flashed the new firmware fw_6.20.709.2.zip now its stuck
now when i type fastboot oem rebootRUU it gets stuck at the blackscreen with the new htc logo
my M8 rom ViperOne 3.2.1 | 4.4.4
please how to solve it
Coldz0 said:
now when i type fastboot oem rebootRUU it gets stuck at the blackscreen with the new htc logo
Click to expand...
Click to collapse
That is RUU mode. Flash the firmware now (twice).
Since you weren't in RUU mode before, the firmware would have just failed to flash, which means nothing changed, no harm done.
redpoint73 said:
That is RUU mode. Flash the firmware now (twice).
Since you weren't in RUU mode before, the firmware would have just failed to flash, which means nothing changed, no harm done.
Click to expand...
Click to collapse
Fixed it by myself, unlocked bootloader, relock it and install firmware again and all good now
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Saumitraa said:
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Click to expand...
Click to collapse
if no boot loader you have to use unbrick threads.
If you had a flashed back a stock recovery and boot.img if on rooted mm bl with giovix modder tool , you could've downgraded via sd card and stock recovery ..in my link below
There were 2 different cm 13s , one with mm bl and one based on 5.
.
Unbricked
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Saumitraa said:
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Click to expand...
Click to collapse
did you get any error in any command. if you got bootloader it must work
flash xfstk again and and run these commands after extracting raw.. tell me if any of the command fails or give error
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
No errors
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
Which build number raw file you use ?
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
send me log of cmd when you run commands
timbernot said:
Which build number raw file you use ?
Click to expand...
Click to collapse
This one : WW_ZE551ML_2.20.40.194_20160713
Hi there,
I've got a problem with my Moto Z Play. It is unlocked with lastest unofficial TWRP, bootloader unlocked and running lastest Lineage OS ROM.
I already checked these type of threads:
https://forum.xda-developers.com/moto-z-play/help/booting-recovery-automatically-t3654698$
which gives a solution (doing some fastboot commands) but it doesn't work for me.
So I tried to do this in fastboot mode
" adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot "
But it didn't change anything. I need to boot on fastboot mode and then push power button while selecting start to get it runs on ROM.
Is anyone has a solution?
paknex said:
Hi there,
I've got a problem with my Moto Z Play. It is unlocked with lastest unofficial TWRP, bootloader unlocked and running lastest Lineage OS ROM.
I already checked these type of threads:
https://forum.xda-developers.com/moto-z-play/help/booting-recovery-automatically-t3654698$
which gives a solution (doing some fastboot commands) but it doesn't work for me.
So I tried to do this in fastboot mode
" adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot "
But it didn't change anything. I need to boot on fastboot mode and then push power button while selecting start to get it runs on ROM.
Is anyone has a solution?
Click to expand...
Click to collapse
I faced the same issue ... Tried many things but simple solution worked like a charm
Flash twrp ... Re boot phone ... Don't boot to system instead boot to recovery ..then shutdown from recovery ... That's it twrp is permeant and phone boots to system normally
Tried this but still boots to recovery. Thanks for the idea.