Develop Bugs

Desire won't boot

Hi
Messed up my desire a while back. It won't boot. When I turn it on I get this screen
When I plug it in to PC then unplug it I get this screen
Can't flash any RUU. Can't access recovery. Just nothing. Anyone any ideas what I can do?
Sent from my GalaxyS2 with CM9

Hm, no fastboot. Does it recognize it if you connect the phone to your pc? Your PC may see a USB serial console that accepts commands.
Google for "HbootAnalysis" to get a list of commands.
The gotofastboot commands looks worth a shot. Once in fastboot you should be able to flash anything you want.

The phone reacts, and the computer knows there is something there. Just not a phone...
Sent from my GalaxyS2 with CM9

So you cannot even access fastboot?

No
Sent from my GalaxyS2 with CM9

This is probably extremely unhelpful so I apologise but what did you do/what happened to the Desire to make it (what seems to be) stuck in a loop?

this is a partition/radio brick
it usually happens when you try and RUU a device when its using the new alpharev hboots that do not have the right sizes (hes using the sense hboot which doesnt use stock sizes)
so basically it kills the partitions. this is because alpharev put that "annoying" hboot protection on to stop RUU's from overwriting it. i love the alpharev team but that really isnt needed
I dont think its possible to fix this without being able to get to fastboot as we need to get the hboot flashed with stock sizes

Stuck on the way RRU
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper

fxjumper said:
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
Click to expand...
Click to collapse
indeed this should work
he said he cant boot to fastboot though, are you saying you can use fastboot in the RUU screen?

yes i can enter fastboot command
but after these stuff, i loosed my name/serial_number in adb but not in fastboot
my new adb username/serial_number is 1234567890ABCDEF

Htc m9 corruted bootloader blue screen,Please HELP

When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?

are you soff?

blue screen error
plz some one help..
htc m9 asia tw
s-on
firmware update to 5.1 sudden mobile reset and now when it on after gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error plz someone help. what to do.

You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.

philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
please someone help to solve this problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This screen comes every time and reset htc logo and then same blue screen

Maybe try fastboot boot recovery.img and see if that works??

philicibine said:
Maybe try fastboot boot recovery.img and see if that works??
Click to expand...
Click to collapse
FAILED (remote: Not allow when s-on)

mnhs1010 said:
When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?
Click to expand...
Click to collapse
Is your error solved or are you still stuck with the blue screen as I am also the effected

LineArc said:
Is your error solved or are you still stuck with the blue screen as I am also the effected
Click to expand...
Click to collapse
Still same problem dear blue screen...

mnhs1010 said:
Still same problem dear blue screen...
Click to expand...
Click to collapse
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money

sa3d12 said:
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money
Click to expand...
Click to collapse
did your problem solved >>>>>

mnhs1010 said:
did your problem solved >>>>>
Click to expand...
Click to collapse
U mean you solved your problem or you are asking me? ..
Anyway i dont have problems with my device

hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
Click to expand...
Click to collapse
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again

I think you only need to flash the hosd

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
Thanks a lot! You have been avoided a heart attack hehe!

You my friend are a star... I thought my HTC M9 was a brick for sure.
Just to add people, remember do not try and copy through ADB installer (As I did to begin with)... It will not detect your phone... Use the Fastboot application within CMD.
VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
does anyone have for m9 verizon ?

@VashSV, I already pressed thanks button but want to write and say thanks to you. You save my phone. Happy new year 2017

Many many many thanks to you!!! I what in this blue screen loop, thanks to your commande list I managed to write .img by .img, you are the boss.

Exact same problem
philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
Hello, a bit late but I have the exact same problem with my HTC one M9, can you please help me? I am s-off, unlocked and my phone is T-MOB010 with N7 corrupted firmware :/ pleaseeee

Serious problem in the Moto G5 Cedric xt 1672! (Help me please!!)

friends, how are you?
It's the following .. I have a serious problem with my Moto G5.
When he went to do the update for Oreo he gave a problem ... Of which I can not leave.
It starts in fastboot mode or attempts to initialize Android but stops on screen (M) as picture.
The bootloader is locked, I tried to unlock by cmd and put the key sent by the motorola, signaled as if it worked and continues as (oem_locked).
I do not have root, my bootloader is locked, and I can not access recovery despite entering fastboot mode.
I tried installing several roms by adb, but I could not succeed with any (Always giving FAILED REMOTE).
Yesterday until it managed to enter the initial configuration of the android (where it places the wifi) but then restarted and never again.
I've tried everything a little bit, and I could not succeed with anything.
Help me, please, I do not know what else to do!
Thank you
:confuso:

You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!

.....
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
TheFixItMan said:
You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!
Click to expand...
Click to collapse

sonmota said:
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
Click to expand...
Click to collapse
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

....
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
TheFixItMan said:
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse

sonmota said:
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
Click to expand...
Click to collapse
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone

I saw there was an October update in the ROM. I will try here in the community this ROM and try to blink and bring the result here ..

friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
TheFixItMan said:
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone
Click to expand...
Click to collapse

sonmota said:
friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
Click to expand...
Click to collapse
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used

I can not get into recovery. Would not it be a problem with the motherboard?
TheFixItMan said:
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used
Click to expand...
Click to collapse

sonmota said:
I can not get into recovery. Would not it be a problem with the motherboard?
Click to expand...
Click to collapse
Could well be
As long as gpt flashed successfully without giving a downgrade warning which will call it to fail then the recovery part of the firmware should flash and you should have access to recovery mode via entering recovery from bootloader then holding power button and volume up at the picture of the android screen
It could be a motherboard issue but since you have no problem getting into bootloader it's more likely a firmware issue/user error

Rooting Motorola G6 Play gone wrong

Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke

Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.

Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.

Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.

How to flash stock firmware on my XT2045-2?

Recently I rooted my Moto G8 (XT2045-2) phone, booted up TWRP and tried to install LineageOS. But somethign went wrong (I don't know what exactly) and my phone only booted into bootloader mode.
So now I am unsuccessfully trying to restore the stock firmware.
I downloaded the firmware (version RAV_RETAIL_10_QPJS30.63-35-1-15_subsidy-DEFAULT_regulatory-DEFAULT_CFC) and tried flashing it by doing the following commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
Every single one of those commands completed successfully, but booting the phone still only gets me to the bootloader screen.
Trying to boot into recovery mode also just gets me to the bootloader.
Next I tried to just flash TWRP by doing:
Code:
fastboot flash recovery twrp-3.4.0-0-rav-test6.img
.
Command completes successfully, but booting into recovery mode afterwards still only gets me to the bootloader screen.
I can boot into TWRP via
Code:
fastboot boot twrp-3.4.0-0-rav-test6.img
.
Any idea what the problem is with my phone?
Or what my next step could be to salvage this phone?

You have to be in fastbootd mode when you flash firmware. Try this out from the bootloader...
Code:
fastboot reboot fastboot
That should switch you to fastbootd mode. If it doesn't, then boot up twrp, and from the menu select reboot>fastboot.

Thanks.
When I try
Code:
fastboot reboot fastboot
I just get
Code:
fastboot: usage: unknown reboot target fastboot
TWRP also doesn't show me fastboot option.
The only reboot options I have are:
- System
- Power Off
- Recovery
- Bootloader
- Edl
- Slot A
- Slot B
Any other ideas?

Try updating fastboot/adb.

Spaceminer said:
Try updating fastboot/adb.
Click to expand...
Click to collapse
Thanks, I got one step further with that.
The command actually went through but the phone just booted in normal bootloader mode again and i got the following error:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Chaos156 said:
Thanks, I got one step further with that.
The command actually went through but the phone just booted in normal bootloader mode again and i got the following error:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
That sounds promising. Try this... Flash your stock recovery then rerun that command.

.

Spaceminer said:
That sounds promising. Try this... Flash your stock recovery then rerun that command.
Click to expand...
Click to collapse
Flashing the stock recovery did not work. it said the flashing process was successfull, but the phone still only boots into bootloader mode when I try to boot recovery after flashing.
The following got me into fastbootd though:
Code:
fastboot boot recovery.img
Where recovery.img is the stock recovery.
I tried flashing the stock ROM in fastbootd mode and at first it seemed to be successfull. No error messages.
But rebooting afterwards just gets me back into bootloader mode. Neither system nor recovery are booting.

I think that I have an idea that will work. Boot up twrp. Unzip this and copy the entire folder to /sdcard/TWRP. Then use twrp to restore this recovery image. (The backup name is "z") After that reboot to recovery and see if it works. If it does, then use stock recovery to switch to fastbootd, and try flashing your firmware again.

I unzipped and copied the BACKUP to /sdcard/TWRP.
But sadly I encountered the next problem almost immediately.
My TWRP restore screen looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only "package" to restore was the empty cache folder.
I tried to switch the storage, but the Micro SD card option and the USB Storage option were not selectable at all.
Next I used TWRPs file manager to copy the BACKUP from sdcard to /cache. Had no luck with that though either.
The cache folder on the Restore screen was still empty.
I selected the cache package just to see what would happen if I try to restore it.
The following happened:
The stuff below [RESTORE STARTED] are the error messages for the restore process.
All the error messages above happen every time i boot into TWRP.

@Chaos156
I'm not sure what to make of that but I have a few ideas. It looks like /data is trashed in some way.
Idea #1
Boot twrp, then wipe>format>type "yes" to continue. Then reboot directly to the bootloader, and from there, boot up twrp again and try restoring that recovery image.
Idea #2
Boot twrp. Rename recovery.emmc.win to recovery.img and try directly flashing it using twrp's install image option.
Idea #3
Also grab the latest twrp from Vache and try using that. I believe we're up to twrp 3.5.0. It should be posted in the development threads.

I got the newest TWRP and did the format/wipe. I think that fixed 50% of my problem!
I no longer get the "failed to mount /data" errors. But the "Failed to mount /metadata" errors continue.
Any idea on how to fix the metadata partition too?
Installing that image didn't work. The installation went well, but after rebooting I was just back in bootloader mode.

Chaos156 said:
I got the newest TWRP and did the format/wipe. I think that fixed 50% of my problem!
I no longer get the "failed to mount /data" errors. But the "Failed to mount /metadata" errors continue.
Any idea on how to fix the metadata partition too?
Installing that image didn't work. The installation went well, but after rebooting I was just back in bootloader mode.
Click to expand...
Click to collapse
From the bootloader try,
Code:
fastboot erase metadata
Edit: If that doesn't work, try it with twrp using fasbootd.

I erased the metadata, but even after flashing an image it just boots into bootloader mode still.
I tried it twice; once from bootloader and once from TWRP fastbootd.
It says your image was flashed successfully but it still doesn't boot afterwards.
The metadata partition errors also still persist.
I can also no longer boot the stock recovery via "fastboot boot stock_recovery.img". It just shows the "No command" error. Same if I try to boot your recovery.img directly via "fastboot boot recovery.img".

You can try to run BlankFlash to fix it

Chaos156 said:
I erased the metadata, but even after flashing an image it just boots into bootloader mode still.
I tried it twice; once from bootloader and once from TWRP fastbootd.
View attachment 5212679
It says your image was flashed successfully but it still doesn't boot afterwards.
The metadata partition errors also still persist.
I can also no longer boot the stock recovery via "fastboot boot stock_recovery.img". It just shows the "No command" error. Same if I try to boot your recovery.img directly via "fastboot boot recovery.img".
Click to expand...
Click to collapse
This is probably your best bet at this point. In order for fastbootd to work, you need either twrp or the stock recovery to flash properly to the recovery partition. You should be able to install the stock recovery from the bootloader since it's not a dynamic partition. Then just reboot into fastbootd and get it fixed up. For some reason, that doesn't seem possible. So I'm not sure what's going on with your phone at this point. Scope out lolinet. They probably have a blank flash for our device. If not, let me know and I'll trying digging one up from some folks on the gsmhosting forums. If you need QPST utilities to run the blank flash, also let me know and I'll link it.

lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

I found the blank flash on lolinet and it included the qboot utility version 3.86.
I tried using the bash script :
Code:
./blank-flash.sh
But it just just said "< waiting for device >" without ever detecting my phone.
Calling "./qboot devices" directly did not list my device where both "fastboot devices" and "adb devices" found my phone.
I tried searching for qboot to see if a newer version than 3.86 might exist, but I can't find any source for qboot at all.

Did you run from bootloader, fastboot oem blanklash

Chaos156 said:
I found the blank flash on lolinet and it included the qboot utility version 3.86.
I tried using the bash script :
Code:
./blank-flash.sh
But it just just said "< waiting for device >" without ever detecting my phone.
Calling "./qboot devices" directly did not list my device where both "fastboot devices" and "adb devices" found my phone.
I tried searching for qboot to see if a newer version than 3.86 might exist, but I can't find any source for qboot at all.
Click to expand...
Click to collapse
You need to be in EDL (emergency download mode) to use a blank flash. Try booting twrp and check the reboot options. It should be there. I'm just not sure if it'll work. If it does work, it might not look like anything is going on. My G7 play in EDL mode, just had a black screen and looked like it was turned off, but the backlight was on. When connected to my PC, it appeared as something like QHUSB in my device manager.