Database Develop

I think I soft bricked my phone. flashing "no command"

I've got a moto x '14 verizon XT1096. Tried to use fastboot to load twrp to eventually get to install Cm13. However, it threw this message:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.006s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.024s
Dumbass me thought it would be a good idea to unplug the device and simply try again. Well, what a bad decision. The phone now flashes the "no command" robot on it's back. yes, flashes. i can get back to fastboot, but after this i'm not sure what to do.
Thanks in advance. I'm fairly new at this, be easy on me.

Try this. This is my mini guide I wrote in another thread.
Well, at first I tried to flash twrp through fastboot but the original recovery override the twrp recovery.
So, what I did, instead of flashing, I just temporary booted into twrp.
adb reboot bootloader
fastboot boot twrp.img (and not fastboot flash recovery twrp.img)
Then phone booted into twrp, I flash supersu 2.46.
Then I easily downloaded twrp manager from google play and installed twrp recovery to my xt1096.
Have fun
Use this https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse

Fastboot Recovery? Getting g.co/ABH Error On Boot

I flashed the Android Wear 2.0 OTA update and now the watch won't boot. I get the "Device Software Can't Be Checked For Corruption" error and it's telling me to go to g.com/ABH.
It won't go into recovery mode, but will go into fastboot mode. I grabbed the stock images from here, and flashed the stock boot, system, and recovery imgs, but the error persists.
https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Am I screwed? Or is there something I could do to recover?
Thanks.

Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk

Wait for about 10 seconds when the warning appears. The watch will continue it's boot after 10 secs.

TonySuperPony said:
Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk
Click to expand...
Click to collapse
I thought I had initially. I hadn't turned the watch on for a while, but decided to get it set up yesterday when I saw news of the 2.0 update hit. It originally had the first firmware on it and wouldn't update to 2.0 (adb would fail to find the watch).
So, I flashed MWF76 from the link in my earlier post. And that worked properly -- the watch booted normally, set up the apps, the right build number was showing, etc.
When that was done I tried to flash the 2.0 update again. And this time the watch was being recognized properly with adb. The flash procedure seemed to go without a hitch, but I got the g.co/ABH error on first boot.
And if you let the watch sit for 10 seconds, it only boots into Fastboot mode. You can't enter recovery. If you try to enter recovery with the vol-down+power button combo, you see recovery for a split second and then it goes right to fastboot.
At the moment it appears the bootloader is locked again.

Still experimenting. Hoping someone with more knowledge may be able to help.
Fastboot oem unlock reports that the bootloader is already unlocked.
Tried flashing all of the IMGs in MFW76 and these flash successfully:
boot
system
recovery
modem
asusfw
But when trying to flash these, the flash fails because it says the bootloader is locked. Trying fastboot oem unlock again reports the bootloader is unlocked, but still can not flash these...
devinfo
factory
misc
modemst1
modemst2
oem
splash
Tried fastboot flashing unlock_critical, and the watch shows part of a message, but I can't see if there's anything to do on...pressing the top or bottom buttons changes the color of the bg.

Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.

yilun said:
Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.
Click to expand...
Click to collapse
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?

re: flashable AW 2.0 zip file
BigWopHH said:
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?
Click to expand...
Click to collapse
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!

Misterjunky said:
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!
Click to expand...
Click to collapse
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"

re: adb sideload
BigWopHH said:
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"
Click to expand...
Click to collapse
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!

Misterjunky said:
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!
Click to expand...
Click to collapse
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.

BigWopHH said:
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.
Click to expand...
Click to collapse
I'd try to get the watch running 1.5 first via fastboot.

See my post in the other thread linked here, specifically my edits.
I did boot, recovery, then system, and did "fastboot format userdata" instead of "fastboot erase userdata"

I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?

re: not booting properly
AndyKir said:
I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?
Click to expand...
Click to collapse
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!

Misterjunky said:
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!
Click to expand...
Click to collapse
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.

AndyKir said:
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.
Click to expand...
Click to collapse
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.

Misterjunky said:
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.
Click to expand...
Click to collapse
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?

re: fastboot bootup
AndyKir said:
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?
Click to expand...
Click to collapse
You must have flashed the wrong boot.img (which is the kernel)
Make 100% sure that you are flashing the correct kernel and
don't issue the command "fastboot format userdata".
All you need is:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
then oem lock bootloader
What was the exact filename of the ziip file
which had the 3 IMG files in it?
Here is the link for the zip file which contains the correct IMG files in it:
https://www.dropbox.com/s/tz9bg5fggpfn2q6/swift_partition_dump_part1_MWG68.zip?dl=1
unlock bootloader, flash the three img files, lock bootloader
and issue this fastboot command: " fastboot reboot "
Don't flash anything else and don't format anything...
Good luck, have a great day!

Misterjunky, thank you for your replies!
I`ve downloaded your files from Dropbox, put it in c:\adb\correct\ folder, and run next commands in PowerShell
PS C:\adb> fastboot oem unlock
...
(bootloader) The bootloader is already unlocked!
OKAY [ 0.006s]
finished. total time: 0.007s
PS C:\adb> fastboot flash boot C:\adb\correct\boot.img
target reported max download size of 262144000 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.038s]
writing 'boot'...
OKAY [ 3.222s]
finished. total time: 4.263s
PS C:\adb> fastboot flash recovery C:\adb\correct\recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.043s]
writing 'recovery'...
OKAY [ 3.150s]
finished. total time: 4.195s
PS C:\adb> fastboot flash system C:\adb\correct\system.img
target reported max download size of 262144000 bytes
erasing 'system'...
OKAY [ 1.134s]
sending sparse 'system' (254201 KB)...
OKAY [ 8.468s]
writing 'system'...
OKAY [ 26.695s]
sending sparse 'system' (149469 KB)...
OKAY [ 5.016s]
writing 'system'...
OKAY [114.570s]
finished. total time: 155.890s
PS C:\adb> fastboot oem lock
...
(bootloader) Locking bootloader...
(bootloader) Device Locked!
(bootloader) Locking bootloader done!
OKAY [ 0.023s]
finished. total time: 0.024s
PS C:\adb> fastboot reboot
rebooting...
finished. total time: 0.008s
PS C:\adb>
After reboot, I still in Fastboot mode - nothing is changed.

[Stock ROM][Applied 1 October OTA Update]Trying to get TWRP custom recovery flashed

Hello. So, I got my Moto G5s Plus around the last week of October or beginning of November. It is a great device, but I learned about the camera flaws by Motorola and unlocked the bootloader to fix it by following this XDA thread here for camera fixing and the Chromatix mod. I learned that I could edit build.prop without flashing the TWRP recovery but using it temporarily following the guide here. build.prop edit would enable cam2api for third party cam apps. The Chromatix mod threads/posts were for the G5 Plus, which I didn't realize at the time and didn't backup original Chromatix files. However, That went successfully and I could still use my phone with better camera quality. Note that prior to doing this fix and before unlocking the bootloader (I believe) I had updated my device from Nougat to Oreo. My bootloader is indeed unlocked.
Now, when the 1 October OTA Update came I was hesitent because I had came across some rooting/custom rom/custom recovery/mod articles while learning about unlocking the bootloader. Yet and before reading more to get educated on this, I applied the update to my phone. I was hoping it wouldn't brick it or that it would fail if it didn't work. It failed (because of the modification on the stock ROM) at the last bit of the update and rebooted my phone. My phone worked and it let me know nothing was changed by the failed update. However, my phone since then has shown as if it is up-to-date in system updates.
So, basically I have been trying to flash TWRP for my Moto G5s Plus after that was done. I want to see about backing up my stock ROM (or the most important parts) possibly getting a good custom ROM installed (which I believe they have their own official Android security updates from Google?). However flashing TWRP hasn't worked. I get the following in PowerShell (cmd):
PS C:\Android SDK\platform-tools> fastboot flash recovery twrp.img
Sending 'recovery' (10236 KB) OKAY [ 0.407s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.172s]
Finished. Total time: 0.594s
Note that I renamed twrp-3.1.1-sanders.img to twrp.img as it was a suggestion I followed at the time. This I heard is normal, but when I go to Recovery Mode on my phone I see this:
Start Up Failed:
Repair message stuff
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
~~~
Error: failed to load kernel!
~~~
I also tried to find the latest stock ROM to flash because I believe I read I may need to do that. I found SANDERS_RETAIL_8.1.0_OPSS28.65-36-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and tried to use "Apply update from ADB" from the stock Recovery (when it was working normally after powering off and not with kernel errors because of this). It failed.
I couldn't find the right answer(s). Thank you to anyone that can help me or others who have done the same!!
EDIT (11/19/2018):
So, last night I tried wiping my data in stock recovery and then I tried to do this again. It still didn't work. I also tried to apply the same stock zip as well as boot_magisk.img from this thread here https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301.
PS C:\Android SDK\platform-tools> fastboot flash boot boot_magisk.img
Sending 'boot' (10702 KB) OKAY [ 0.391s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.141s]
Finished. Total time: 0.563s
It all still fails. However, now when I boot up my phone it goes straight to the bootloader instead of loading the OS right away. I can select START to start the phone normally from there.

I got all this resolved through XDA's Telegram group (& specific group for G5s Plus/sanders)! I have TWRP (Treble) and custom rom working after getting an official stock rom from them flashed using fastboot commands!
I don't know if I should or a mod can close/erase this thread now?

Try typing fastboot oem fb_mode_clear while in bootloader

Coala990 said:
Try typing fastboot oem fb_mode_clear while in bootloader
Click to expand...
Click to collapse
Thanks for the suggestion/tip. I will probably try that if I reflash twrp treble (or another version of twrp for Sanders) again. This has been resolved.

Can't flash vendor.img but i have TWRP [What to do ?]

Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much

I need help :'(

I had that.
Phone was completely dead, needed a new board.

chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?

benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.

benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!

You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.

benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??

Fashing Locked e Unlock OEM At Developer Option.. Moto G7 Plus

How to unlock the OEM when I could not activate the developer options, because the device does not turn on?
It is not possible to flash a ROM because it says: flashing_locked
In short, the device only goes to Fastboot.
------------------
I manage to do the following. I did a temporary boot via Fastboot.
fastboot boot "Original ROM file or Boot.img Patched with Root"

More information I have I will be putting it here.

An application to use adb and fastboot without a computer.
Bugjaeger or Bugjaeger Premium
ps: requires otg support on the device you are going to control.

I'm out of results at the moment, I couldn't recover my Moto G7 Plus.
I've already lost almost 100% of the hopes that I can manage.
I think I will have to send it to a Motorola Official Technician or buy another device, as it is not worth me to have it fixed. because the stores are far from my city.

I was able to start the device, but I still can't activate oem unlock.
it is already a progress.
I used a modified boot.img and started the device using:
fastboot boot boot.img
the problem I have to use this command to turn on the device without...

if i get more news i will talk here.

Anrito Kun said:
if i get more news i will talk here.
Click to expand...
Click to collapse
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?

wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
------------------
I don't know how to send files here.
I have no new results, but I will try to send the boot.img that could connect the device.

wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img

I haven't been able to do anything new yet.
I think that only specialist technicians will know how to fix the device.

Anrito Kun said:
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
Click to expand...
Click to collapse
------------------
After downloading use the command: fastboot boot file.img
This managed to start the device, but I couldn't get into Recovery ... At least I couldn't.

Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.

Anrito Kun said:
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Click to expand...
Click to collapse
------------------
I think it may be possible to join TWRP with the system's Boot.img. As if it were a magched patched, only instead of magisk it is TWRP.

delete

delete

poog said:
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....tried 2 things that fail
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.510s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
Click to expand...
Click to collapse
------------------
You're using the Moto G7 plus, right?
the command has to be this to use the file:
fastboot boot "file name".img

poog said:
I can boot to fastboot, but I cannot flash anything. I cannot get a proper return with "fastboot devices"
I cannot get RSD LITE to recognize my device. (win 10). I have read to try win7
Device Manager (windows 10) can only show the device as "Motorola ADB Device". I have not figured out how to force it to show as Qualcom ..............if that will make a difference or not. qualcom drivers are installed.
Before I messed it up I was able to load the device as a qualcom device on the right port and blankflashed after I hardbricked with nothing on screen.
Ability to boot to fastboot but not flash anything seems it is effectively dead for now.
Click to expand...
Click to collapse
------------------
There is no point in trying Flash on the device when the device is Flashing Locked.

My phone is in the same situation after I tried to re-lock the bootloader. Please do follow up on your progress.

hey I have the same problem have you found a solution?

Unfortunately, no.