Database Users

Stuck at FASTBOOT Zenfone Selfie/Zenfone Laser (Z00U/Z00T)

Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s

https://www.androidfilehost.com/?fid=24671318762849134 you need to flash this fisrt before flash custom rom

Same Problem XDA devs Pl Help
Kabeesh said:
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
Click to expand...
Click to collapse
:fingers-crossed:

YotaPhone2 206 stuck on Powered by Android logo SOLVED

Since yesterday my YotaPhone 2 bricked. It is YD206, bought from China. I did nothing special - AlwaysOnDisplay kind of hanged up (with some artefacts on it ) and after I went to reboot it just went into boot loop. It was with marshmallow (I bought it that way - used). I tried power and vol+ - it just continues to restart and shows Powered by Android pic. Now I can only put it in download mode (power and vol-). Tried to flash it with yota-flash and 4.4.3-S01-003-CN1.0.3.32a.zip firmware - no success. Everything went just fine, but it reboots again shows powered by Android and in some time phone reboots and shows the same. I succeeded to load TWRP Recovery (twrp-v5.img). I wiped it out - no change at all. I tried to flash the system.img with different sizes - still no luck.
Guys, I'm really stuck here, so any help is appreciated! Cheers

I think, I'm experiencing the exact same issue with my YotaPhone YD206. It was on the 5.0.0-RU-1.1.134 firmware before the blackout happened.
This is a description of the issue on my side. Could you please confirm if it is the case with yours? I read many threads but found no solution.
The EPD display is stuck on the same screen from the weather widget.
After powering off the device, it shows the "Powered by android" logo and ends in an endless bootloop (auto-restarting each 10 minutes).
The phone can be put into the "Downloading Mode" without problem, and fastboot can also detect it:
Code:
C:\Program Files (x86)\yotaphone_flasher\fastboot devices
55554735 fastboot
Flashing the original CN firmware succeed, no errors to see
Code:
target reported max download size of 2147483648 bytes
sending 'aboot' (892 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.063s
target reported max download size of 2147483648 bytes
sending 'boot' (12760 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.281s]
finished. total time: 0.688s
target reported max download size of 2147483648 bytes
erasing 'system'...
OKAY [ 0.281s]
sending 'system' (846110 KB)...
OKAY [ 27.410s]
writing 'system'...
OKAY [ 25.646s]
finished. total time: 53.337s
target reported max download size of 2147483648 bytes
sending 'recovery' (13308 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.297s]
finished. total time: 0.734s
target reported max download size of 2147483648 bytes
erasing 'cache'...
OKAY [ 0.031s]
sending 'cache' (18800 KB)...
OKAY [ 0.594s]
writing 'cache'...
OKAY [ 0.484s]
finished. total time: 1.109s
target reported max download size of 2147483648 bytes
sending 'modem' (57545 KB)...
OKAY [ 1.847s]
writing 'modem'...
OKAY [ 1.250s]
finished. total time: 3.097s
target reported max download size of 2147483648 bytes
sending 'sbl1' (280 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.047s
target reported max download size of 2147483648 bytes
sending 'rpm' (191 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 2147483648 bytes
sending 'tz' (325 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.031s
target reported max download size of 2147483648 bytes
sending 'aboot' (892 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.063s
Would you like to flash userdata[Y/N]:

First of all 10x for your reply!
1>>> AlwaysOnDisplay of my phone stuck on a page of a book I was reading.
2>>> Same here: After powering off the device, it shows the "Powered by android" logo and ends in an endless bootloop
3>>> Yes, the phone can be put into the "Downloading Mode" without problem, and fastboot can also detect it:
4>>> All flashing attempts went without any error. I tried with CN, RU and APC fimwares. Tonight Im gonna try with HK. I even tried manually to flash every partition with fastboot (https://forum.xda-developers.com/yotaphone-one/help/y2-bootloop-to-recovery-t3509883) - still the same result. Tried to install the official Marshmallow through TWRP - no luck at all. Tomorrow gonna open the phone and disconnect the battery for a while - will post here what the result is.
The interesting part is that installing TWRP is not possible on all firmwares uploaded on a phone. It works for sure with 4.4.3-S01-003-CN1.0.3.01a
Cheers!

Hi and thanks for your reply!
By the way: Are you able to boot it into recovery? Mine can't.
angelll123 said:
First of all 10x for your reply!
1>>> AlwaysOnDisplay of my phone stuck on a page of a book I was reading.
2>>> Same here: After powering off the device, it shows the "Powered by android" logo and ends in an endless bootloop
3>>> Yes, the phone can be put into the "Downloading Mode" without problem, and fastboot can also detect it:
4>>> All flashing attempts went without any error. I tried with CN, RU and APC fimwares. Tonight Im gonna try with HK. I even tried manually to flash every partition with fastboot (https://forum.xda-developers.com/yotaphone-one/help/y2-bootloop-to-recovery-t3509883) - still the same result. Tried to install the official Marshmallow through TWRP - no luck at all. Tomorrow gonna open the phone and disconnect the battery for a while - will post here what the result is.
The interesting part is that installing TWRP is not possible on all firmwares uploaded on a phone. It works for sure with 4.4.3-S01-003-CN1.0.3.01a
Cheers!
Click to expand...
Click to collapse

veeblefetzer said:
Hi and thanks for your reply!
By the way: Are you able to boot it into recovery? Mine can't.
Click to expand...
Click to collapse
I can't boot into its custom recovery - pwr & vol+ do nothing. But I am able to do it with twrp (put it in Downloading... mode and then <<fastboot boot twrp-v5.img>>) (for twrp image look here: https://forum.xda-developers.com/yotaphone-one/help/guide-everything-to-yotaphone2-t3547194.
Code:
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe boot twrp-v5.img
downloading 'boot.img'...
OKAY [ 0.497s]
booting...
OKAY [ 0.020s]
finished. total time: 0.517s
After that it loads TWRP 3.2.0 by itself.
Note that with my phone it works only with CN firmwares. Right now with 4.4.3-S01-003-CN1.0.3.32a). Best regards!

No luck again - I disconnected YP2's battery for some time, but the phone still acts as before. I plan to test all available CN firmwares and to use 'fastboot -S' command for system.img with 512M chunks and 256M chunks. Will let you know if there is any progress. Cheers!

I've run out of ideas and I'm thinking about to return it to GearBest.
Thanks anyway for the updates and the work!
angelll123 said:
No luck again - I disconnected YP2's battery for some time, but the phone still acts as before. I plan to test all available CN firmwares and to use 'fastboot -S' command for system.img with 512M chunks and 256M chunks. Will let you know if there is any progress. Cheers!
Click to expand...
Click to collapse

Hi guys, as far as I remember when playing around with flashing my yotaphone is that sometimes it makes a difference if you first erase and also that the yotaflasher tool does not always do this completely correctly.
So sadly it is better to understand what is going on, then do it yourself and tweak it until it works.
I used my own scripts so I could control what was being flashed instead of having to always flash everything.
So try extracting the firmware yourself and then flashing every part with an executable bat file.
Userdata should be erased also to make it work, so try to get a backup for that first if you can.
here are the scripts that I used:
To make this work, you need to extract the zip file manually to the firmware folder of your yota_flasher folder and put the bat script also in the yota_flasher folder.
Code:
fastboot.exe flash modem firmware\radio\NON-HLOS.bin
fastboot.exe flash modem firmware\radio\NON-HLOS.bin
fastboot.exe flash rpm firmware\radio\rpm.mbn
fastboot.exe flash rpm firmware\radio\rpm.mbn
fastboot.exe flash tz firmware\radio\tz.mbn
fastboot.exe flash tz firmware\radio\tz.mbn
fastboot.exe flash sbl1 firmware\radio\sbl1.mbn
fastboot.exe flash sbl1 firmware\radio\sbl1.mbn
fastboot.exe flash aboot firmware\emmc_appsboot.mbn
fastboot.exe flash aboot firmware\emmc_appsboot.mbn
fastboot.exe flash recovery firmware\recovery.img
fastboot.exe flash recovery firmware\recovery.img
fastboot.exe flash boot firmware\boot.img
fastboot.exe flash boot firmware\boot.img
fastboot.exe erase system
fastboot.exe flash system firmware\system.img
fastboot.exe erase userdata
fastboot.exe flash userdata firmware\userdata.img
fastboot.exe flash persist firmware\persist.img
fastboot.exe flash persist firmware\persist.img
fastboot.exe flash cache firmware\cache.img
fastboot.exe flash cache firmware\cache.img
pause
Edit: fixed some badly copy pasted edited code
Edit: Changed code to flash most files 2 times just to be sure.

tomgaga said:
Hi guys, as far as I remember when playing around with flashing my yotaphone is that sometimes it makes a difference if you first erase and also that the yotaflasher tool does not always do this completely correctly.
So sadly it is better to understand what is going on, then do it yourself and tweak it until it works.
I used my own scripts so I could control what was being flashed instead of having to always flash everything.
So try extracting the firmware yourself and then flashing every part with an executable bat file.
Userdata should be erased also to make it work, so try to get a backup for that first if you can.
here are the scripts that I used:
To make this work, you need to extract the zip file manually to the firmware folder of your yota_flasher folder and put the bat script also in the yota_flasher folder.
fastboot.exe flash modem firmware\radio\NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg firmware\radio\fsg.mbn
fastboot.exe flash tz firmware\radio\tz.mbn
fastboot.exe flash sbl1 firmware\radio\sbl1.mbn
fastboot.exe erase aboot
fastboot.exe flash aboot firmware\emmc_appsboot.mbn
fastboot.exe erase recovery
fastboot.exe flash aboot firmware\recovery.img
fastboot.exe flash boot firmware\boot.img
fastboot.exe erase system
fastboot.exe flash system firmware\system.img
fastboot.exe erase userdata
fastboot.exe flash userdata firmware\userdata.img
pause
Click to expand...
Click to collapse
10x for the reply, but I still have no luck. YotaPhone continues to act like a brick. All of bat file commands end with status OKAY, still phone goes into boot loop. Just one little correction:
Code:
fastboot.exe flash aboot firmware\recovery.img
should be:
Code:
fastboot.exe flash recovery firmware\recovery.img
Cheers mate!

[/COLOR]
angelll123 said:
10x for the reply, but I still have no luck. YotaPhone continues to act like a brick. All of bat file commands end with status OKAY, still phone goes into boot loop. Just one little correction:
Code:
fastboot.exe flash aboot firmware\recovery.img
should be:
Code:
fastboot.exe flash recovery firmware\recovery.img
Cheers mate!
Click to expand...
Click to collapse
Which firmware have you tried and where did you get it?
and I also added a line to erase the cache
Code:
fastboot.exe erase cache
you did that too right?
And regarding recovery, with marshmellow with twrp ( found here: https://forum.xda-developers.com/showpost.php?p=70206915&postcount=49), i noticed that you have to release the power button when the phone shows the android logo while still holding the vol-up until it goes into recovery. So procedure is to reboot the phone by or while holding power+vol-up buttons and then release the power button when the android - text shows but keep holding vol-up.

Thanks guys!
Same here. All of fastboot commands end with status OKAY (including erase cache), but the phone still stuck at boot.
I tried with the Chinese firmware, version: 4.4.3-S01-003-CN1.0.3.32a, which I downloaded from ftp://fw.ydevices.com/ while the site was still alive.
The content of the firmware:
Code:
C:\Program Files (x86)\yotaphone_flasher\firmware>tree /F
Folder PATH listing
Volume serial number is 0000008B 09A6:99FE
C:.
¶ boot.img
¶ cache.img
¶ dt.img
¶ emmc_appsboot.mbn
¶ emmc_appsboot.raw
¶ persist.img
¶ ramdisk-recovery.img
¶ ramdisk.img
¶ recovery.img
¶ system.img
¶ userdata.img
¶
+---radio
NON-HLOS.bin
rpm.mbn
sbl1.mbn
tz.mbn
And I had to change this:
Code:
fastboot.exe flash fsg firmware\radio\fsg.mbn
To:
Code:
fastboot.exe flash rpm firmware\radio\rpm.mbn
since firmware\radio\fsg.mbn does not exist in 4.4.3-S01-003-CN1.0.3.32a.
Complete batch output:
Code:
C:\Program Files (x86)\yotaphone_flasher>flash_yota.bat
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash modem firmware\radio\NON-HLOS.bin
target reported max download size of 2147483648 bytes
sending 'modem' (57545 KB)...
OKAY [ 1.813s]
writing 'modem'...
OKAY [ 1.234s]
finished. total time: 3.047s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 2.610s]
finished. total time: 2.610s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 2.594s]
finished. total time: 2.594s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash rpm firmware\radio\rpm.mbn
target reported max download size of 2147483648 bytes
sending 'rpm' (191 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash tz firmware\radio\tz.mbn
target reported max download size of 2147483648 bytes
sending 'tz' (325 KB)...
OKAY [ 0.031s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.047s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash sbl1 firmware\radio\sbl1.mbn
target reported max download size of 2147483648 bytes
sending 'sbl1' (280 KB)...
OKAY [ 0.000s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase aboot
erasing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash aboot firmware\emmc_appsboot.mbn
target reported max download size of 2147483648 bytes
sending 'aboot' (892 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.063s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash recovery firmware\recovery.img
target reported max download size of 2147483648 bytes
sending 'recovery' (13308 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 0.797s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash boot firmware\boot.img
target reported max download size of 2147483648 bytes
sending 'boot' (12760 KB)...
OKAY [ 0.453s]
writing 'boot'...
OKAY [ 0.281s]
finished. total time: 0.734s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.281s]
finished. total time: 0.281s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash system firmware\system.img
target reported max download size of 2147483648 bytes
erasing 'system'...
OKAY [ 0.031s]
sending 'system' (846110 KB)...
OKAY [ 26.798s]
writing 'system'...
OKAY [ 25.611s]
finished. total time: 52.440s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.469s]
finished. total time: 0.469s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash userdata firmware\userdata.img
target reported max download size of 2147483648 bytes
erasing 'userdata'...
OKAY [ 0.188s]
sending 'userdata' (141162 KB)...
OKAY [ 4.453s]
writing 'userdata'...
OKAY [ 3.828s]
finished. total time: 8.469s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
C:\Program Files (x86)\yotaphone_flasher>pause
Press any key to continue . . .
tomgaga said:
[/COLOR]
Which firmware have you tried and where did you get it?
and I also added a line to erase the cache
Code:
fastboot.exe erase cache
you did that too right?
And regarding recovery, with marshmellow with twrp ( found here: https://forum.xda-developers.com/showpost.php?p=70206915&postcount=49), i notice that it is not so easy to get it into recovery sometimes using the button-combination, sometimes I have to wait till the android logo appears to press and hold power+volup.
Click to expand...
Click to collapse

veeblefetzer said:
Thanks guys!
Same here. All of fastboot commands end with status OKAY (including erase cache), but the phone still stuck at boot.
I tried with the Chinese firmware, version: 4.4.3-S01-003-CN1.0.3.32a, which I downloaded from ftp://fw.ydevices.com/ while the site was still alive.
The content of the firmware:
Code:
C:\Program Files (x86)\yotaphone_flasher\firmware>tree /F
Folder PATH listing
Volume serial number is 0000008B 09A6:99FE
C:.
¶ boot.img
¶ cache.img
¶ dt.img
¶ emmc_appsboot.mbn
¶ emmc_appsboot.raw
¶ persist.img
¶ ramdisk-recovery.img
¶ ramdisk.img
¶ recovery.img
¶ system.img
¶ userdata.img
¶
+---radio
NON-HLOS.bin
rpm.mbn
sbl1.mbn
tz.mbn
And I had to change this:
Code:
fastboot.exe flash fsg firmware\radio\fsg.mbn
To:
Code:
fastboot.exe flash rpm firmware\radio\rpm.mbn
since firmware\radio\fsg.mbn does not exist in 4.4.3-S01-003-CN1.0.3.32a.
Complete batch output:
Code:
C:\Program Files (x86)\yotaphone_flasher>flash_yota.bat
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash modem firmware\radio\NON-HLOS.bin
target reported max download size of 2147483648 bytes
sending 'modem' (57545 KB)...
OKAY [ 1.813s]
writing 'modem'...
OKAY [ 1.234s]
finished. total time: 3.047s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 2.610s]
finished. total time: 2.610s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 2.594s]
finished. total time: 2.594s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash rpm firmware\radio\rpm.mbn
target reported max download size of 2147483648 bytes
sending 'rpm' (191 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash tz firmware\radio\tz.mbn
target reported max download size of 2147483648 bytes
sending 'tz' (325 KB)...
OKAY [ 0.031s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.047s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash sbl1 firmware\radio\sbl1.mbn
target reported max download size of 2147483648 bytes
sending 'sbl1' (280 KB)...
OKAY [ 0.000s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase aboot
erasing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash aboot firmware\emmc_appsboot.mbn
target reported max download size of 2147483648 bytes
sending 'aboot' (892 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.063s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash recovery firmware\recovery.img
target reported max download size of 2147483648 bytes
sending 'recovery' (13308 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 0.797s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash boot firmware\boot.img
target reported max download size of 2147483648 bytes
sending 'boot' (12760 KB)...
OKAY [ 0.453s]
writing 'boot'...
OKAY [ 0.281s]
finished. total time: 0.734s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.281s]
finished. total time: 0.281s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash system firmware\system.img
target reported max download size of 2147483648 bytes
erasing 'system'...
OKAY [ 0.031s]
sending 'system' (846110 KB)...
OKAY [ 26.798s]
writing 'system'...
OKAY [ 25.611s]
finished. total time: 52.440s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.469s]
finished. total time: 0.469s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe flash userdata firmware\userdata.img
target reported max download size of 2147483648 bytes
erasing 'userdata'...
OKAY [ 0.188s]
sending 'userdata' (141162 KB)...
OKAY [ 4.453s]
writing 'userdata'...
OKAY [ 3.828s]
finished. total time: 8.469s
C:\Program Files (x86)\yotaphone_flasher>fastboot.exe erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
C:\Program Files (x86)\yotaphone_flasher>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Well I think the only option is to try another one.
Here is one link with all roms: https://forum.xda-developers.com/yotaphone-one/general/firrmware-files-one-files-onedrive-t3633138
unfortunately you have to download them all together :/.
Here I uploaded the chinese firmware files that are working for me(, i just tested):
https://drive.google.com/open?id=0B_Z57M1pKWRubG1ycDk1aVJuWXM

One more important thing. Try doing:
Code:
fastboot.exe oem unlock
It seems that the phone gets relocked when flashing probably the boot.img(not sure about that).
AND try running every flash command twice! For twrp recovery for example, it did not work until I ran it twice without restarting. Strange stuff.

Still no luck - I tried with tomgaga's firmware, erased the cache, replaced script for flashing tsg with a one that flashed rpm. The phone still goes into boot loop. I tried tomgaga's advice about pressing vol+ & pow and when 'Powered by Android' logo appears to let go pow - all that in order to enter recovery mode. It jsut keeps rebooting with 'Powered by Android' logo. Still with all CN firmwares I can load twrp recovery image.
I have to say how happy I am that you guys participate in that thread and keep it alive. I have no doubts that in the end we will succeed unbricking this wonderfull phone. Cheers

One more thing - when I try with command:
Code:
fastboot.exe oem unlock
phone just reboots in that well known 'Powered by Android' bootloop. I guess it have to do something - maybe show 'Your OEM is now unlocked' or something. Best regards guys!

angelll123 said:
Still no luck - I tried with tomgaga's firmware, erased the cache, replaced script for flashing tsg with a one that flashed rpm. The phone still goes into boot loop. I tried tomgaga's advice about pressing vol+ & pow and when 'Powered by Android' logo appears to let go pow - all that in order to enter recovery mode. It jsut keeps rebooting with 'Powered by Android' logo. Still with all CN firmwares I can load twrp recovery image.
I have to say how happy I am that you guys participate in that thread and keep it alive. I have no doubts that in the end we will succeed unbricking this wonderfull phone. Cheers
Click to expand...
Click to collapse
Ok this might sound stupid, but could you for certainty check that your buttons are functioning correctly by booting some normal recovery using fastboot and then see if vol up, down, and power work consistently as expected.
And when you say it goes into bootloop, do you mean that it shows the yotaphone animation for a while first?

Hi guys,
same behaviour here for:
Code:
fastboot.exe oem unlock
It reboots and nothing happens after 'Powered by Android" logo.
Ok this might sound stupid, but could you for certainty check that your buttons are functioning correctly by booting some normal recovery using fastboot and then see if vol up, down, and power work consistently as expected.
Click to expand...
Click to collapse
Booting into recovery via fastboot also not possible. I don't think that the buttons are defect. At least booting into "Downloading mode" is possible.
And when you say it goes into bootloop, do you mean that it shows the yotaphone animation for a while first?
Click to expand...
Click to collapse
For my device, it means that it shows the very first "powered by android" logo, no Yotaphone animation. After 5-10 minutes it reboots and this happens continuously, till battery runs out.

veeblefetzer said:
Hi guys,
same behaviour here for:
Code:
fastboot.exe oem unlock
It reboots and nothing happens after 'Powered by Android" logo.
Booting into recovery via fastboot also not possible. I don't think that the buttons are defect. At least booting into "Downloading mode" is possible.
For my device, it means that it shows the very first "powered by android" logo, no Yotaphone animation. After 5-10 minutes it reboots and this happens continuously, till battery runs out.
Click to expand...
Click to collapse
How to you try to get into recovery using fastboot? And what happens then?
And you can also try flashing the russian lollipop firmware:
I uploaded it here:
https://drive.google.com/open?id=0B_Z57M1pKWRuSm5LTXhBYzJfS00
it includes the hybrid modem by default, but the russian and chines radio files are included too.

And one more thing, it seems I did not include a line to flash the persist partition, for me it worked without, but you could to try that too:
Code:
fastboot.exe flash persist firmware\persist.img
fastboot.exe flash persist firmware\persist.img

Hello,
did you solved this problem?
I have the same problem as you. Only "powered by android" and restart. Power and - button ->downloading, power and +button -> nothing
The EPD display is stuck on the same screen from the yota reader, bootloap every 10 seconds. Between every restart lcd display flash with blue color.
I didnt make any firmware upgrades or anything else with software, phone didnt fall down...
Thanks for help
Dalibor

Moto X Play XT1562 Having Network Problem (NO SIGNAL)

Please suggest me what i do ? i am not having network in my moto x play xt1562 from yesterday, i tried to turn off/on aeroplan mode and change SIM card but even then no signal, sim card working fine in other mobile.
i also tried to select network manually , and switch from 4g lte to 3g or 2g but not working.

Do you have IMEI?

Issued Solved
ziom5510 said:
Do you have IMEI?
Click to expand...
Click to collapse
I have solved the issue, not its 6.0, but got update of 7.1.1, NOW ITS Not comming

Hi. M having same problem in my x play what to do
Should I roll back to marshmallow
Plz provide twrp flasable room of lollipop or marshmallow
Vodafone slot2 - 358967063233173
Jio slot1 - 358967063233165

even i am having the same issue

Moto x play . No service status
Unable to register on network . Signal comes goes .
In low
Coverage area unable to register ..
Device is nougat version.
What to sumbody help me ..

techeligible3322 said:
Please suggest me what i do ? i am not having network in my moto x play xt1562 from yesterday, i tried to turn off/on aeroplan mode and change SIM card but even then no signal, sim card working fine in other mobile.
i also tried to select network manually , and switch from 4g lte to 3g or 2g but not working.
Click to expand...
Click to collapse
Facing same issue.. sim1jio4g.. and sim2airtel
Tried different sim. But problem persists.. moto xplay india android nougat
---------- Post added at 05:02 AM ---------- Previous post was at 04:58 AM ----------
Sim1jio sim2airtel.. tried sim change
Changed sim slot, tried netwrok reset, and factory reset too
Problem still persists
Moto xplay india
Nougat android ( ota ver.)

techeligible3322 said:
Hey i have foxed this issue, before i was having this issue, just go to google, and type there
" moto x play network issue techeligible ". Open that site and follow all steps from there
Click to expand...
Click to collapse
Thanks alot ,brother. Hope there will b a permanent solution for this problem
---------- Post added at 04:21 PM ---------- Previous post was at 04:01 PM ----------
Is there any permanent solution via root(i.e. on rooted moto xplay. Apps/mods o)

shivm500 said:
Thanks alot ,brother. Hope there will b a permanent solution for this problem
---------- Post added at 04:21 PM ---------- Previous post was at 04:01 PM ----------
Is there any permanent solution via root(i.e. on rooted moto xplay. Apps/mods o)
Click to expand...
Click to collapse
Try this one first then let me know

techeligible3322 said:
Try this one first then let me know
Click to expand...
Click to collapse
Thought it worked but itsnt . Both netwrks emergency calls only

shivm500 said:
Thought it worked but itsnt . Both netwrks emergency calls only
Click to expand...
Click to collapse
Did u reboot in fastboot ? And then download adb bypass tool in computer?

techeligible3322 said:
Did u reboot in fastboot ? And then download adb bypass tool in computer?
Click to expand...
Click to collapse
I followed the whole process via adb and the commands ..
Network just keep on droping and most of the time its emergency calls only..

shivm500 said:
I followed the whole process via adb and the commands ..
Network just keep on droping and most of the time its emergency calls only..[/QUOTE
Ah, that actually worked fine with me when i use commands okay, dis you also download firmware ??? I guess i downloaded 1gb file
Click to expand...
Click to collapse

techeligible3322 said:
shivm500 said:
I followed the whole process via adb and the commands ..
Network just keep on droping and most of the time its emergency calls only..[/QUOTE
Ah, that actually worked fine with me when i use commands okay, dis you also download firmware ??? I guess i downloaded 1gb file
Click to expand...
Click to collapse
I did adb fastboot
Nd thay commands
Dont know about firmware
Pls guide
(Iam on nougat)
Click to expand...
Click to collapse

Ok today i will search that firmware as well ok

Download Firmware
shivm500 said:
techeligible3322 said:
I did adb fastboot
Nd thay commands
Dont know about firmware
Pls guide
(Iam on nougat)
Click to expand...
Click to collapse
Go to Device Settings > About > check what's written with "BUILD NUMBER", mine is MPDS24-11..., this is to make sure you are downloading right firmware from below site. just match detail with build number firmware.
You can download your device Android 7.1 Firmware from below link
https://github.com/motoxplay/stock
-after downloading finish, just flash your device with this firmware.
Flash With Firmware:
-Extract the downloaded firmware to somewhere you can use adb.exe.
-Reboot device in "Bootloader Mode" by pressing "Volume Down + Power Key".
-Copy and past "ADB Commands Prompt" where you have "Downloaded extracted firmware".
-Press "Control + Shift + Mouse Right click", then open "Windows Command Prompt here".
-Connect device to computer.
Note: Make sure, "Moto X Play Firmare", and "ADB" both are in same folder.
Copy & Past below commands in to adb command prompt window, to flash with firmware:
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 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 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
Best of luck
Click to expand...
Click to collapse

After flash with firmware, soft reset your device and then I hope this would fix your network issue

thnx

shivm500 said:
techeligible3322 said:
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
D:\New folder>adb reboot bootloader
D:\New folder>fastboot oem fb_mode_set
...
OKAY [ 0.009s]
finished. total time: 0.009s
D:\New folder>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.803s]
finished. total time: 0.811s
D:\New folder>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.093s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.796s]
finished. total time: 1.891s
D:\New folder>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (3080 KB)...
OKAY [ 0.109s]
writing 'logo'...
OKAY [ 0.151s]
finished. total time: 0.261s
D:\New folder>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.188s]
writing 'boot'...
OKAY [ 1.388s]
finished. total time: 2.579s
D:\New folder>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.174s]
writing 'recovery'...
OKAY [ 1.397s]
finished. total time: 2.572s
D:\New folder>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (255439 KB)...
OKAY [ 8.619s]
writing 'system'...
OKAY [ 9.509s]
finished. total time: 18.129s
D:\New folder>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (261106 KB)...
OKAY [ 8.810s]
writing 'system'...
OKAY [ 7.097s]
finished. total time: 15.908s
D:\New folder>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (248342 KB)...
OKAY [ 8.364s]
writing 'system'...
OKAY [ 8.959s]
finished. total time: 17.323s
D:\New folder>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257578 KB)...
OKAY [ 8.682s]
writing 'system'...
OKAY [ 10.331s]
finished. total time: 19.012s
D:\New folder>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (254106 KB)...
OKAY [ 8.567s]
writing 'system'...
OKAY [ 6.541s]
finished. total time: 15.107s
D:\New folder>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (262050 KB)...
OKAY [ 8.822s]
writing 'system'...
OKAY [ 7.905s]
finished. total time: 16.727s
D:\New folder>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (236003 KB)...
OKAY [ 7.942s]
writing 'system'...
OKAY [ 9.900s]
finished. total time: 17.842s
D:\New folder>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.7': No error
D:\New folder>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.7': No error
D:\New folder>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.7': No error
D:\New folder>fastboot flash system system.img_sparsechunk.8
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.8': No error
D:\New folder>fastboot flash system system.img_sparsechunk.9
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.9': No error
D:\New folder>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (37377 KB)...
OKAY [ 1.260s]
writing 'modem'...
OKAY [ 0.703s]
finished. total time: 1.963s
D:\New folder>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
D:\New folder>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
D:\New folder>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1314 KB)...
OKAY [ 0.062s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.109s
D:\New folder>fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
D:\New folder>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
D:\New folder>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.031s
D:\New folder>fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
D:\New folder>fastboot reboot
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse
after 6 the 7th 8th and 9th sparse chunk
didnt happened
Click to expand...
Click to collapse

shivm500 said:
shivm500 said:
after 6 the 7th 8th and 9th sparse chunk
didnt happened
Click to expand...
Click to collapse
hey no problem, I also did same like this and got failed but even then after I reboot my device in bootloader, and then again restart my drive normal after I got my Singal issue solved
Click to expand...
Click to collapse

OnePlus 6T always boot on Bootloader, cant flash TWRP or Stock Recovery...

What about friends, it happens that I wanted to install TWRP to my OP6T, but it did not go well ... I followed the steps and when I gave "Reboot Recovery", I entered the fastboot mode, and it did not happen there, it did not allow me to flash the rom, the stock recovery, or the TWRP, tells me the following ...
This happens when wanting to boot the twrp.img:
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
PS C:\Users\vhr07\Desktop>
--------------------------------------------------------------------------------------------
This happens when you want to install the recovery stock:
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.518s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.536s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
I install the recovery by means of "boot" and it says OK, but when wanting to boot I get error:
PS C:\Users\vhr07\Desktop> fastboot flash boot recovery.img
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.518s]
writing 'boot'...
OKAY [ 0.271s]
finished. total time: 1.794s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.506s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.547s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
These were my last attempts ...:
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (30948 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.734s
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.508s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.525s
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16849 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.406s
PS C:\Users\vhr07\Desktop> fastboot flash recovery_b recovery.img
target reported max download size of 536870912 bytes
sending 'recovery_b' (65536 KB)...
OKAY [ 1.523s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 1.538s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b recovery.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.517s]
writing 'boot_b'...
OKAY [ 0.301s]
finished. total time: 1.824s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.511s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.549s
PS C:\Users\vhr07\Desktop> fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot' (30948 KB)...
OKAY [ 0.714s]
writing 'boot'...
OKAY [ 0.154s]
finished. total time: 0.874s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30948 KB)...
OKAY [ 0.717s]
writing 'boot_b'...
OKAY [ 0.181s]
finished. total time: 0.904s
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.716s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
----------------------------------------------------------------------------
Please, I need your help I promise not to ROOT again the hahaha team
I would pay if necessary
PD: already tried with bootloader unlocked and blocked
UPDATE: MSMTools, stuck on "PARAM PREPROCESSING"
https://imgur.com/qiaF8oh

First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.

foobar66 said:
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
Click to expand...
Click to collapse
Same situation
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.500s]
writing 'boot_a'...
OKAY [ 0.308s]
finished. total time: 1.814s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.498s]
writing 'boot_b'...
OKAY [ 0.345s]
finished. total time: 1.849s
PS C:\Users\vhr07\Desktop> fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.505s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.537s
PS C:\Users\vhr07\Desktop>

Seem look like usb debug not authorize pc

i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!

efebe said:
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
Click to expand...
Click to collapse
MSMTools stuck on this
https://imgur.com/qiaF8oh

Vlodayax said:
MSMTools stuck on this
https://imgur.com/qiaF8oh
Click to expand...
Click to collapse
Click "stop" then "exit" and kill the program and start over. Keep trying. I was down a whole day and a half after trying to flash a Rom. I made it worst after wiping the system and the MSM tool saved my a$$.
Sent from my OnePlus6T using XDA Labs

Oneplus 6T McLaren complete brick

I have had the OP6T for about 1.5 years now and immediately installed TWRP after the purchase. I have never changed or updated the software (Android 9.0). Now I recently experienced some small bugs and wanted to perform a factory reset via TWRP. This one just did not allow it and I got an error message. Backing up was also not possible because of a mount error. The internal partition was still available. Yesterday I downloaded the official and stable update to Android 10 via the Oneplus site. This was the next step to solve the problems.
Step-by-step plan:
1. Boot to TWRP and flash new rom.
2. Install TWRP again to overwrite system recovery.
3. Reboot to recovery again and reinstall Magisk.
4. Reboot device.
All problems started at step 1. When flashing the full zip I got an 'Error code 1'. My TWRP turned out not to be up to date. I immediately updated TWRP and rebooted it. At that moment TWRP reported that there was no OS installed. No disaster, I could still overwrite everything and install Android 10 I thought. Again an 'Error code 1'. Then I wiped the system partition via TWRP. After this the error code stayed. When I restarting TWRP, TWRP suddenly disappeared as well. Now I have the default menu of an empty Oneplus device which only allows me to go to fastboot/ADB. In tried to reinstall TWRP trought fastboot/ADB but it failed. Below the error code from the command prompt:
PS C:\Users\yoeri\Downloads\img> fastboot devices
1b6ccb35 fastboot
PS C:\Users\yoeri\Downloads\img>
PS C:\Users\yoeri\Downloads\img> fastboot boot twrp.img
downloading "boot.img"...
OKAY [ 0.699s]
...booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.724s
The MSM tool (hard-brick tool) does not work either. My device doesn't show up but it can still boot up to nowhere. Fastboot/ADB is the only way to connect the device but doesn't work. I suspect that there were errors in the disk partitions from the beginning. Does anyone have any idea how I can fix my OP6T?

Generally wiping system is a bad idea on these devices. Generally once I've had problem in fastboot, I've had to use the fastboot ROM to fix the device. Either reload the problem "partition" or the whole ROM, doesn't matter.
Since you have fastboot, the MSM tool is never what I jump since it locks the bootloader. MSM Tool is always my last resort. Key combinations are (from another post I did recently):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Just to make sure you do know that when you using the MSM tool, you won't be in Fastboot correct? There is a driver as well for this.
Once you get this up and running, make sure you are using an up to date TWRP from here.

OhioYJ said:
Generally wiping system is a bad idea on these devices. Generally once I've had problem in fastboot, I've had to use the fastboot ROM to fix the device. Either reload the problem "partition" or the whole ROM, doesn't matter.
Since you have fastboot, the MSM tool is never what I jump since it locks the bootloader. MSM Tool is always my last resort. Key combinations are (from another post I did recently):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Just to make sure you do know that when you using the MSM tool, you won't be in Fastboot correct? There is a driver as well for this.
Once you get this up and running, make sure you are using an up to date TWRP from here.
Click to expand...
Click to collapse
I can only enter fastboot mode. Download mode doesn't show up with that button combination. Is there no way to recover it with fastboot mode?

yoeri058 said:
I can only enter fastboot mode. Download mode doesn't show up with that button combination. Is there no way to recover it with fastboot mode?
Click to expand...
Click to collapse
Nothing will show up on the screen while in download. MSMTool will recognize it though if the drivers are properly installed.
If fastboot works, I always use that before the MSMTool. MSMTool is always and always should be the last resort, as it relocks the bootloader.
You can flash ROMs from Fastboot, that's how I normally recover my phone when I've messed it up, and typically what I do in this situation: Stock Fastboot ROMs for OnePlus 6T Thread
I made a script* that has all that stuff in it that so I can flash everything I need from a single command (I use Linux all this stuff just goes in a .sh file, Windows would be a little different):
Code:
sudo fastboot flash aop_a aop.img
sudo fastboot flash aop_b aop.img
sudo fastboot flash bluetooth_a bluetooth.img
sudo fastboot flash bluetooth_b bluetooth.img
sudo fastboot flash boot_a boot.img
sudo fastboot flash boot_b boot.img
sudo fastboot flash dsp_a dsp.img
sudo fastboot flash dsp_b dsp.img
sudo fastboot flash dtbo_a dtbo.img
sudo fastboot flash dtbo_b dtbo.img
sudo fastboot flash fw_4j1ed_a fw_4j1ed.img
sudo fastboot flash fw_4j1ed_b fw_4j1ed.img
sudo fastboot flash fw_4u1ea_a fw_4u1ea.img
sudo fastboot flash fw_4u1ea_b fw_4u1ea.img
sudo fastboot flash modem_a modem.img
sudo fastboot flash modem_b modem.img
sudo fastboot flash oem_stanvbk oem_stanvbk.img
sudo fastboot flash qupfw_a qupfw.img
sudo fastboot flash qupfw_b qupfw.img
sudo fastboot flash storsec_a storsec.img
sudo fastboot flash storsec_b storsec.img
sudo fastboot flash system_a system.img
sudo fastboot flash system_b system.img
sudo fastboot flash vbmeta_a vbmeta.img
sudo fastboot flash vbmeta_b vbmeta.img
sudo fastboot flash vendor_a vendor.img
sudo fastboot flash vendor_b vendor.img
sudo fastboot flash LOGO_a LOGO.img
sudo fastboot flash LOGO_b LOGO.img
*I just took all that information from the thread, definitely give all the credit to mauronofrio for taking the time to develop TWRP for our device and others, and put these things together for us. Mainly just pointing out, which so did he I believe you don't need type all that stuff in one by one.

OhioYJ said:
Nothing will show up on the screen while in download. MSMTool will recognize it though if the drivers are properly installed.
If fastboot works, I always use that before the MSMTool. MSMTool is always and always should be the last resort, as it relocks the bootloader.
You can flash ROMs from Fastboot, that's how I normally recover my phone when I've messed it up, and typically what I do in this situation: Stock Fastboot ROMs for OnePlus 6T Thread
I made a script* that has all that stuff in it that so I can flash everything I need from a single command (I use Linux all this stuff just goes in a .sh file, Windows would be a little different):
Code:
sudo fastboot flash aop_a aop.img
sudo fastboot flash aop_b aop.img
sudo fastboot flash bluetooth_a bluetooth.img
sudo fastboot flash bluetooth_b bluetooth.img
sudo fastboot flash boot_a boot.img
sudo fastboot flash boot_b boot.img
sudo fastboot flash dsp_a dsp.img
sudo fastboot flash dsp_b dsp.img
sudo fastboot flash dtbo_a dtbo.img
sudo fastboot flash dtbo_b dtbo.img
sudo fastboot flash fw_4j1ed_a fw_4j1ed.img
sudo fastboot flash fw_4j1ed_b fw_4j1ed.img
sudo fastboot flash fw_4u1ea_a fw_4u1ea.img
sudo fastboot flash fw_4u1ea_b fw_4u1ea.img
sudo fastboot flash modem_a modem.img
sudo fastboot flash modem_b modem.img
sudo fastboot flash oem_stanvbk oem_stanvbk.img
sudo fastboot flash qupfw_a qupfw.img
sudo fastboot flash qupfw_b qupfw.img
sudo fastboot flash storsec_a storsec.img
sudo fastboot flash storsec_b storsec.img
sudo fastboot flash system_a system.img
sudo fastboot flash system_b system.img
sudo fastboot flash vbmeta_a vbmeta.img
sudo fastboot flash vbmeta_b vbmeta.img
sudo fastboot flash vendor_a vendor.img
sudo fastboot flash vendor_b vendor.img
sudo fastboot flash LOGO_a LOGO.img
sudo fastboot flash LOGO_b LOGO.img
*I just took all that information from the thread, definitely give all the credit to mauronofrio for taking the time to develop TWRP for our device and others, and put these things together for us. Mainly just pointing out, which so did he I believe you don't need type all that stuff in one by one.
Click to expand...
Click to collapse
I followed the article but it doesn't work for me. I receive this error codes:
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot devices
1b6ccb35 fastboot
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot boot flash-all.bat
creating boot image...
creating boot image - 4096 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.030s
Click to expand...
Click to collapse
These are the logs from the manual try which also didn't change anything:
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot boot flash-all-partitions.bat
cannot load 'flash-all-partitions.bat': No such file or directory
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot flash aop_a aop.img
>> fastboot flash aop_b aop.img
>> fastboot flash bluetooth_a bluetooth.img
>> fastboot flash bluetooth_b bluetooth.img
>> fastboot flash boot_a boot.img
>> fastboot flash boot_b boot.img
>> fastboot flash dsp_a dsp.img
>> fastboot flash dsp_b dsp.img
>> fastboot flash dtbo_a dtbo.img
>> fastboot flash dtbo_b dtbo.img
>> fastboot flash fw_4j1ed_a fw_4j1ed.img
>> fastboot flash fw_4j1ed_b fw_4j1ed.img
>> fastboot flash fw_4u1ea_a fw_4u1ea.img
>> fastboot flash fw_4u1ea_b fw_4u1ea.img
>> fastboot flash modem_a modem.img
>> fastboot flash modem_b modem.img
>> fastboot flash oem_stanvbk oem_stanvbk.img
>> fastboot flash qupfw_a qupfw.img
>> fastboot flash qupfw_b qupfw.img
>> fastboot flash storsec_a storsec.img
>> fastboot flash storsec_b storsec.img
>> fastboot flash system_a system.img
>> fastboot flash system_b system.img
>> fastboot flash vbmeta_a vbmeta.img
>> fastboot flash vbmeta_b vbmeta.img
>> fastboot flash vendor_a vendor.img
>> fastboot flash vendor_b vendor.img
>> fastboot flash LOGO_a LOGO.img
>> fastboot flash LOGO_b LOGO.img
target reported max download size of 536870912 bytes
sending 'aop_a' (180 KB)...
OKAY [ 0.011s]
writing 'aop_a'...
OKAY [ 0.029s]
finished. total time: 0.072s
target reported max download size of 536870912 bytes
sending 'aop_b' (180 KB)...
OKAY [ 0.027s]
writing 'aop_b'...
OKAY [ 0.035s]
finished. total time: 0.102s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (748 KB)...
OKAY [ 0.026s]
writing 'bluetooth_a'...
OKAY [ 0.021s]
finished. total time: 0.071s
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (748 KB)...
OKAY [ 0.024s]
writing 'bluetooth_b'...
OKAY [ 0.024s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.421s]
writing 'boot_a'...
OKAY [ 0.311s]
finished. total time: 1.735s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.423s]
writing 'boot_b'...
OKAY [ 0.311s]
finished. total time: 1.737s
target reported max download size of 536870912 bytes
sending 'dsp_a' (32768 KB)...
OKAY [ 0.713s]
writing 'dsp_a'...
OKAY [ 0.324s]
finished. total time: 1.039s
target reported max download size of 536870912 bytes
sending 'dsp_b' (32768 KB)...
OKAY [ 0.715s]
writing 'dsp_b'...
OKAY [ 0.344s]
finished. total time: 1.062s
target reported max download size of 536870912 bytes
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.189s]
writing 'dtbo_a'...
OKAY [ 0.072s]
finished. total time: 0.264s
target reported max download size of 536870912 bytes
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.191s]
writing 'dtbo_b'...
OKAY [ 0.080s]
finished. total time: 0.275s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_a' (344 KB)...
OKAY [ 0.020s]
writing 'fw_4j1ed_a'...
OKAY [ 0.027s]
finished. total time: 0.073s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_b' (344 KB)...
OKAY [ 0.028s]
writing 'fw_4j1ed_b'...
OKAY [ 0.032s]
finished. total time: 0.100s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_a' (344 KB)...
OKAY [ 0.020s]
writing 'fw_4u1ea_a'...
OKAY [ 0.028s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4u1ea_b'...
OKAY [ 0.036s]
finished. total time: 0.099s
target reported max download size of 536870912 bytes
sending 'modem_a' (118228 KB)...
OKAY [ 2.596s]
writing 'modem_a'...
OKAY [ 0.683s]
finished. total time: 3.282s
target reported max download size of 536870912 bytes
sending 'modem_b' (118228 KB)...
OKAY [ 2.596s]
writing 'modem_b'...
OKAY [ 0.523s]
finished. total time: 3.123s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (432 KB)...
OKAY [ 0.031s]
writing 'oem_stanvbk'...
OKAY [ 0.038s]
finished. total time: 0.102s
target reported max download size of 536870912 bytes
sending 'qupfw_a' (64 KB)...
OKAY [ 0.005s]
writing 'qupfw_a'...
OKAY [ 0.025s]
finished. total time: 0.070s
target reported max download size of 536870912 bytes
sending 'qupfw_b' (64 KB)...
OKAY [ 0.008s]
writing 'qupfw_b'...
OKAY [ 0.025s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'storsec_a' (24 KB)...
OKAY [ 0.012s]
writing 'storsec_a'...
OKAY [ 0.028s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'storsec_b' (24 KB)...
OKAY [ 0.008s]
writing 'storsec_b'...
OKAY [ 0.032s]
finished. total time: 0.072s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system_b'...
OKAY [ 0.033s]
sending sparse 'system_b' (498465 KB)...
OKAY [ 11.469s]
writing 'system_b'...
OKAY [ 0.002s]
sending sparse 'system_b' (515995 KB)...
OKAY [ 17.766s]
writing 'system_b'...
OKAY [ 0.002s]
sending sparse 'system_b' (504323 KB)...
OKAY [ 17.175s]
writing 'system_b'...
OKAY [ 0.003s]
sending sparse 'system_b' (524294 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 47.659s
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (8 KB)...
OKAY [ 0.012s]
writing 'vbmeta_a'...
OKAY [ 0.041s]
finished. total time: 0.070s
target reported max download size of 536870912 bytes
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.009s]
writing 'vbmeta_b'...
OKAY [ 0.047s]
finished. total time: 0.070s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' (513884 KB)...
OKAY [ 12.133s]
writing 'vendor_a'...
OKAY [ 0.003s]
sending sparse 'vendor_a' (315106 KB)...
OKAY [ 14.075s]
writing 'vendor_a'...
OKAY [ 0.002s]
finished. total time: 26.218s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
target reported max download size of 536870912 bytes
sending 'LOGO_a' (3204 KB)...
OKAY [ 0.082s]
writing 'LOGO_a'...
OKAY [ 0.014s]
finished. total time: 0.099s
target reported max download size of 536870912 bytes
sending 'LOGO_b' (3204 KB)...
OKAY [ 0.084s]
writing 'LOGO_b'...
OKAY [ 0.025s]
finished. total time: 0.113s
Click to expand...
Click to collapse
I am sure that I have al drivers correctly installed. Do you know which MSM-tool is should use? Last OS was Android 9 but now there is nothing installed.

OhioYJ said:
Nothing will show up on the screen while in download. MSMTool will recognize it though if the drivers are properly installed.
If fastboot works, I always use that before the MSMTool. MSMTool is always and always should be the last resort, as it relocks the bootloader.
You can flash ROMs from Fastboot, that's how I normally recover my phone when I've messed it up, and typically what I do in this situation: Stock Fastboot ROMs for OnePlus 6T Thread
I made a script* that has all that stuff in it that so I can flash everything I need from a single command (I use Linux all this stuff just goes in a .sh file, Windows would be a little different):
Code:
sudo fastboot flash aop_a aop.img
sudo fastboot flash aop_b aop.img
sudo fastboot flash bluetooth_a bluetooth.img
sudo fastboot flash bluetooth_b bluetooth.img
sudo fastboot flash boot_a boot.img
sudo fastboot flash boot_b boot.img
sudo fastboot flash dsp_a dsp.img
sudo fastboot flash dsp_b dsp.img
sudo fastboot flash dtbo_a dtbo.img
sudo fastboot flash dtbo_b dtbo.img
sudo fastboot flash fw_4j1ed_a fw_4j1ed.img
sudo fastboot flash fw_4j1ed_b fw_4j1ed.img
sudo fastboot flash fw_4u1ea_a fw_4u1ea.img
sudo fastboot flash fw_4u1ea_b fw_4u1ea.img
sudo fastboot flash modem_a modem.img
sudo fastboot flash modem_b modem.img
sudo fastboot flash oem_stanvbk oem_stanvbk.img
sudo fastboot flash qupfw_a qupfw.img
sudo fastboot flash qupfw_b qupfw.img
sudo fastboot flash storsec_a storsec.img
sudo fastboot flash storsec_b storsec.img
sudo fastboot flash system_a system.img
sudo fastboot flash system_b system.img
sudo fastboot flash vbmeta_a vbmeta.img
sudo fastboot flash vbmeta_b vbmeta.img
sudo fastboot flash vendor_a vendor.img
sudo fastboot flash vendor_b vendor.img
sudo fastboot flash LOGO_a LOGO.img
sudo fastboot flash LOGO_b LOGO.img
*I just took all that information from the thread, definitely give all the credit to mauronofrio for taking the time to develop TWRP for our device and others, and put these things together for us. Mainly just pointing out, which so did he I believe you don't need type all that stuff in one by one.
Click to expand...
Click to collapse
I fixed it using Mauronofrio all-in-one tool. I am now running Android 10. Thanks for pointing me in the right direction!

yoeri058 said:
I am sure that I have al drivers correctly installed. Do you know which MSM-tool is should use? Last OS was Android 9 but now there is nothing installed.
Click to expand...
Click to collapse
On the MSMTool it won't matter what version, pick one and run it.
Since you were on Android 9 you may actually want to try using an Android 9 fastboot ROM.