Develop Bugs

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

jUST BOOTLOADER SCREEN JUST

NO RECOVERY JUST BLUE SCREEN NO DOWNLOAD MODE JUST BLUE SCREEN
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
{
"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"
}

What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?

iElvis said:
What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?
Click to expand...
Click to collapse
htc m9 asia tw
s-on
firmware update to 5.1 (2.10.709.1) through RUU mode sudden mobile reset and now when it on after that 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.

We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?

iElvis said:
We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?
Click to expand...
Click to collapse
HTC m9 asia tw it was with firmware 1.40.709.8 then i unlocked bootloader from htcdev.com and used venom rom...
after that i started to update to 5.1 i used following commands,
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
fastboot oem rebootRUU
fastboot flash zip firmware-2.10.709.1.zip
fastboot reboot-bootloader
firmware updated successfully but it stuck at htc logo.
then i flash again firmware.zip sudden mobile reset and this blue screen appears. now when going to RUU, download, recovery mode this blue screen appears.
bootloader screen come while pressing vol + and vol - and power button but can't flash anything. while using command on bootloader screen fastboot gives error FAILED (remote: cannot flash this partition in s-on state)
FAILED (remote: Not allow when s-on)

solve this problem
please reply

how can you solve the problem ???

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
not solved yet....

mnhs1010 said:
not solved yet....
Click to expand...
Click to collapse
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least

clsA said:
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least
Click to expand...
Click to collapse
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...

mnhs1010 said:
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...
Click to expand...
Click to collapse
any solution please tell

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
please u have any solution please tell me.

https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#
inset Firmware Packs
"WARNING: HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Because of that it's not recommended (especially to S-ON Users) to relock the Bootloader and flash these files if you want to update to Firmware 2.XX.XXX.X or newer. You better use a RUU and the Update Function in "Settings>About" for that purpose."
Flash stock rom, RUU.exe

finally replacement of mainboard

Possible Solution!
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
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
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
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
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work

I Did say S-OFF only but thanks for your input - I know a few people who were stuck with S-OFF too.
Arthas92 said:
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work
Click to expand...
Click to collapse

I'm stuck at same problem. Does anyone can help?
Is XTC an option?

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
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
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
Hi. I have the same problem which is blue screen on download mode. I tried this method but nothing happen. My HTC is verizon version. I tried to flash all the img from 3.37.605.7 firmware but still the same.

Found a way to recover hard brick bootloader

Hello guys,
I have found a way to restore hard brick "flashing led", but the problem is that now i have device with erased system and locked bootloader, cant flash anything due to "(bootloader) Preflash validation failed", tryed to download few firmware files to try but nothing can be flashed so far.
Do you guys know how to flash kernel and stock recovery img files with locked bootloader.
Note*: Cant unlock bootloader since "Oem unlocking" is not enabled and cant enable it since it cant boot, fastboot oem unlock gives "(bootloader) feature disabled".
So to summarize this, got bootloader back, cant boot, cant unlock bootloader, need official signed latest boot.img and recovery.img.
{
"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"
}

magix01 said:
Hello guys,
I have found a way to restore hard brick "flashing led", but the problem is that now i have device with erased system and locked bootloader, cant flash anything due to "(bootloader) Preflash validation failed", tryed to download few firmware files to try but nothing can be flashed so far.
Do you guys know how to flash kernel and stock recovery img files with locked bootloader.
Note*: Cant unlock bootloader since "Oem unlocking" is not enabled and cant enable it since it cant boot, fastboot oem unlock gives "(bootloader) feature disabled".
So to summarize this, got bootloader back, cant boot, cant unlock bootloader, need official signed latest boot.img and recovery.img.
Click to expand...
Click to collapse
How have you managed to enter the "bootloader" mode?

You don't need an unlocked bootloader to flash stock firmware via fastboot
Just download the firmware and use fastboot to flash it (all parts)
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
Plus what did you use to re-image the bootloader?

I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.

magix01 said:
I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.
Click to expand...
Click to collapse
try rewrite bootloader, I don't know if it will work, but try.

magix01 said:
I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.
Click to expand...
Click to collapse
Pls. provide the method to unbrick we will try flash firmware other versions.
Please give full info how to unbrick. Thanks.

if you share the method
ASHDCBZ said:
Pls. provide the method to unbrick we will try flash firmware other versions.
Please give full info how to unbrick. Thanks.
Click to expand...
Click to collapse
if you share the method, so faster we can find a way to revive the g5 and you would help us all
si comparte el metodo, asi mas rapido podremos buscar la forma de revivir el moto g5 y nos ayudarias a todos

This method is derived from reverse engeneering an exploit from a hardware box released on gsm forums i cant share it now, not until i have full method with system booting then i will share.

magix01 said:
This method is derived from reverse engeneering an exploit from a hardware box released on gsm forums i cant share it now, not until i have full method with system booting then i will share.
Click to expand...
Click to collapse
You have to flash the entire firmware in order - not just boot.img (which is the kernel)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?

magix01 said:
I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?
Click to expand...
Click to collapse
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)

006fazer said:
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
Click to expand...
Click to collapse
I think that should work because he is having the bootloader version B8.24 and the rom posted on XDA having B8.23

006fazer said:
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
Click to expand...
Click to collapse
Still cant flash it, however i tried your firmware, flashed bootloader, now version changed from B8.23 to B8.25, but when i get to fastboot flash boot boot.img i still get:
sending 'boot' (16384 KB)...
OKAY [ 20.642s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 20.830s
This happens on B8.25 new version, got anything else to try?
Edit: I flashed B8.23 bootloader and it bricked the phone again to Qcom loader... this time it wont flash bootloader with exploit again so its dead 100% i think.

Obviously don't try and downgrade the bootloader
Can you just flash twrp recovery & access recovery mode to flash a custom rom?

Cant, the bootloader i flashed was locked, and to flash twrp you need to unlock it wich i cant because of no oem unlock.

magix01 said:
Cant, the bootloader i flashed was locked, and to flash twrp you need to unlock it wich i cant because of no oem unlock.
Click to expand...
Click to collapse
You would have to say how you rreimaged the bootloader so those with unlocked bootloaders can try
I take it you used something like z3x or similar software

I used JTAG flasher from GSM forum, but the thing is my bootloader used to be unlocked then after flash it went to locked status and CID was 0xDEAD, basically now i cant every fix it with jtag so its dead totally.

try with RSD Lite, is automated

Tried still same problem just this time it fails with gpt.bin, also the phone is totally bricked again so ...

magix01 said:
I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?
Click to expand...
Click to collapse
Yeah, that's pretty ****ed up

Help Z2 PLAY XT1710-11 + Testing

Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions​
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
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 modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"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"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends

I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .

How To Guide Convert ColorOS to OxygenOS (OFP & OTA | Bootloader reLock & PIN working)

Update: 18th March 2023
**** Give Up ****
I got so fedup and decided to goto HK and get my OnePlus 11, a real CPH2449 GLO. Paid and waiting to collect.
I will not be update and maintaining this post from now on.
Why give up?
Minor issue like auto brightness and things is still something i can live along with.
Some othe rmajor issue are just impossible to make this chiniese converted 1+11 to be my daily driver:
- Auto reboot randomly
- Lagging randomly, screen lag, video recording lag.
- OTA update issue, refreshing/reinstall at every update is just anonying
My advice? just get a proper non chinese version or if you own a Chinese version just stick with colorOS.
**** Flash at your own risk ****
**** Flash at your own risk ****
**** Flash at your own risk ****
*** DO NOT OTA UPDATA Your Phone After Convert. It will brick and only Official MSM Tool can save you ***
A Oneplus user since OnePlus one. Give up Oneplus and swtiched to Nothing phone since Oneplus 10. Decided to try out OnePlus 11 and ColorOS is really pain in the a**
This post tested converting from PHB110 to CPH2447 / CPH2449. I did not test CPH2451.
Model:
CPH2447 - Indian
CPH2449_EEA - EU
CPH2449_GLO - International
CPH2451 - North America
PHB110 - China
Credits：
Thanks for their feedback
[email protected]
wtywtykk
mark332
alexander宇
daxiaamu
Following is the steps to flash the OTA updates:​
Step 1:
Download all the usual tools
Download Fastboot Enhance
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449 Global A07: eea73728a1b945ea8e3ff6b628495af5.zip
ColorOS: Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
Reboot back into bootloader, as in step 2 item 4.
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin
Step 4:
Boot into fastbootd (Phone Screen: The one with language selection)
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is YES
Flash payload.bin
Step 5:
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img exits
Boot into fastbootd (Phone Screen: The one with language selection)
Use Fastboot Enhance or command line
fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
Step 6:
Follow step 6 from "flash the OFP/EDL Packages"
Following is the steps to flash the OFP/EDL Packages:​
Step 1:
Download all the usual tools
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449GDPR_11_A.06_2023010723370128.zip
Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
Reboot back into bootloader, as in step 2 item 4.
Step 3:
fastboot flash --slot=all modem radio/modem.img
fastboot flash --slot=all boot images/boot.img
fastboot flash vbmeta_system_a images/vbmeta_system.img
fastboot flash vbmeta_system_b images/vbmeta_system.img
fastboot flash vbmeta_a images/vbmeta.img
fastboot flash vbmeta_b images/vbmeta.img
fastboot flash vendor_boot_a images/vendor_boot.img
fastboot flash vendor_boot_b images/vendor_boot.img
fastboot flash vbmeta_vendor_a images/vbmeta_vendor.img
fastboot flash vbmeta_vendor_b images/vbmeta_vendor.img
Step 4:
Go into fastbootd (Phone Screen: The one with language selection)
fastboot reboot fastboot
fastboot flash --slot=all init_boot images/init_boot.img
fastboot flash --slot=all abl radio/abl.img
fastboot flash --slot=all aop radio/aop.img
fastboot flash --slot=all aop_config radio/aop_config.img
fastboot flash --slot=all bluetooth radio/bluetooth.img
fastboot flash --slot=all cpucp radio/cpucp.img
fastboot flash --slot=all devcfg radio/devcfg.img
fastboot flash --slot=all dsp radio/dsp.img
fastboot flash --slot=all dtbo images/dtbo.img
fastboot flash --slot=all engineering_cdt images/engineering_cdt.img
fastboot flash --slot=all featenabler radio/featenabler.img
fastboot flash --slot=all hyp radio/hyp.img
fastboot flash --slot=all imagefv radio/imagefv.img
fastboot flash --slot=all keymaster radio/keymaster.img
fastboot flash --slot=all oplus_sec radio/oplus_sec.img
# Flash the ColorOS version A.08 # fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
fastboot flash --slot=all qupfw radio/qupfw.img
fastboot flash --slot=all recovery images/recovery.img
fastboot flash --slot=all shrm radio/shrm.img
fastboot flash --slot=all splash images/splash.img
fastboot flash --slot=all tz radio/tz.img
fastboot flash --slot=all uefi radio/uefi.img
fastboot flash --slot=all uefisecapp radio/uefisecapp.img
fastboot flash --slot=all xbl radio/xbl.img
fastboot flash --slot=all xbl_ramdump radio/xbl_ramdump.img
fastboot flash --slot=all system images/system.img
fastboot flash --slot=all system_ext images/system_ext.img
fastboot flash --slot=all vendor images/vendor.img
fastboot flash --slot=all product images/product.img
fastboot flash --slot=all my_product images/my_product.img
fastboot flash --slot=all odm images/odm.img
fastboot flash --slot=all my_engineering images/my_engineering.img
fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
fastboot flash --slot=all system_dlkm images/system_dlkm.img
fastboot flash --slot=all my_stock images/my_stock.img
fastboot flash --slot=all my_preload images/my_preload.img
fastboot flash --slot=all my_heytap images/my_heytap.img
fastboot flash --slot=all my_carrier images/my_carrier.img
fastboot flash --slot=all my_region images/my_region.img
fastboot flash --slot=all my_bigball images/my_bigball.img
fastboot flash --slot=all my_manifest images/my_manifest.img
Step 5:
From the fastbootd screen (with language selection),
English
Format Data
Step 6:
From daxiaamu blog post,
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Go into bootloader again. follow step 2
Run $ fastboot flashing lock
Again, go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Once passed the setup screen. Goto settings and set the pin
Additional Tips:
If your phone goes into bootloop with oneplus logo. Most likely its not brick. Just need to do a factory reset in fastboot or QLMFlasher.
As mention by mark332 use the free edition. Goto the fastboot tab and unbrick your phone.
I also paid for the commercial edition. Received username/password which can never login to the commercial editon. Commercial edition allows flash in EDL which i wanted to try.
{
"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"
}

Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.

sth_safal said:
Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.
Click to expand...
Click to collapse
i tried to, after locking the bootloader. the system not able to set the screenlock pattern

kaijern said:
i tried to, after locking the bootloader. the system not able to set the screenlock pattern
Click to expand...
Click to collapse
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..

sth_safal said:
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..
Click to expand...
Click to collapse
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
I am the same.
Can I recover with relock?

sth_safal said:
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?
Click to expand...
Click to collapse
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
Since its worling. I will wait for the international version to be avilable after Feb 7 and try to do a complete flash again. By that time is just all about from Oxygen to Oxygen nothing risky.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
I tried to relock it.
fastboot oem lock、fastboot flashing lock、fastboot oem unlock、fastboot flashing unlock
Every command gives me an error.

It seems I brick my phone.
After I typed in "fastboot flash --slot=all abl abl.elf", I got this error:
ERROR: usb_write failed with status e00002ed
fastboot: error: Could not check if partition abl has slot all
In a poor attempt to fix it, I locked BL, and now it stuck in a bootloop to FASTBOOTD
I couldn't get back to FASTBOOT with pressing physical key. Please help!
P.S. I am using mac

if you can give a step by step, or actually a video, that would actually be amazing. i fear for my phone haha

Is this version of package able to receive the OTP update of OOS?

I also bricked my phone last night, got bootloop and only was able to get into bootloader. I unbricked it by fastbootenhanced and flash the F08 payload.bin file

sunxutian said:
I also bricked my phone last night, got bootloop and only was able to get into bootloader. I unbricked it by fastbootenhanced and flash the F08 payload.bin file
Click to expand...
Click to collapse
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
Why can't you boot into fastbood? Did you try fastboot reboot fastboot?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver

sunxutian said:
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver
Click to expand...
Click to collapse
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?

oprocks said:
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?
Click to expand...
Click to collapse
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader

sunxutian said:
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader
Click to expand...
Click to collapse
tried that a few times, something about "userdata" not working right..
platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.063s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
any idea if there is a way to get fastboot to get userdata partition to proper state first? maybe?