Database Users

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

Can't flash twrp (error flashing partition)

Hey guys,
I received my Essential Phone recently. First of all I unlocked the bootloader with fastboot flash unlock and fastboot flash unlock_critical. All went smoothly but now I'm stuck on the installation of TWRP.
Everytime I get the following error:
C:\Program Files (x86)\Essential\ADB>fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.070s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.171s
I tried 3 different PCs and different USB cables. Unfortunately the first cable was with a Micro-USB to USB-C adapter. Could it help if I sideload the ota zip from here: https://essential-live.herokuapp.com/developer/current-builds?
I appreciate any help! Thanks in advance!
Cheers, Andi

illuminatex said:
Hey guys,
I received my Essential Phone recently. First of all I unlocked the bootloader with fastboot flash unlock and fastboot flash unlock_critical. All went smoothly but now I'm stuck on the installation of TWRP.
Everytime I get the following error:
C:\Program Files (x86)\Essential\ADB>fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.070s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.171s
I tried 3 different PCs and different USB cables. Unfortunately the first cable was with a Micro-USB to USB-C adapter. Could it help if I sideload the ota zip from here: https://essential-live.herokuapp.com/developer/current-builds?
I appreciate any help! Thanks in advance!
Cheers, Andi
Click to expand...
Click to collapse
I ran into that same problem a few times. I think a fastboot -w fixed it (wipe). Seems like once or twice it would fail and I had to run it again? I was using an adaptor too.

Thanks for your reply. I will try to do a wipe. Hopefully the installation of twrp succeeds afterwards.

v_2ryann said:
I ran into that same problem a few times. I think a fastboot -w fixed it (wipe). Seems like once or twice it would fail and I had to run it again? I was using an adaptor too.
Click to expand...
Click to collapse
got a new problem
C:\Program Files (x86)\Essential\ADB>fastboot -w
wiping userdata...
Creating filesystem with parameters:
Size: 109634220032
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 26766167
Block groups: 817
Reserved block group size: 1024
Created filesystem with 11/6692864 inodes and 468189/26766167 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: Check device console.)
finished. total time: 1.204s
C:\Program Files (x86)\Essential\ADB>fastboot -w
wiping userdata...
Creating filesystem with parameters:
Size: 109634220032
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 26766167
Block groups: 817
Reserved block group size: 1024
Created filesystem with 11/6692864 inodes and 468189/26766167 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.877s]
sending 'userdata' (144263 KB)...
OKAY [ 3.272s]
writing 'userdata'...
FAILED (remote: Flash Write Failure)
finished. total time: 4.353s
any other ideas?

illuminatex said:
Hey guys,
I received my Essential Phone recently. First of all I unlocked the bootloader with fastboot flash unlock and fastboot flash unlock_critical. All went smoothly but now I'm stuck on the installation of TWRP.
Everytime I get the following error:
C:\Program Files (x86)\Essential\ADB>fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.070s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.171s
I tried 3 different PCs and different USB cables. Unfortunately the first cable was with a Micro-USB to USB-C adapter. Could it help if I sideload the ota zip from here: https://essential-live.herokuapp.com/developer/current-builds?
I appreciate any help! Thanks in advance!
Cheers, Andi
Click to expand...
Click to collapse
Use fastboot flash boot_a twrp.img or fastboot flash boot_b twrp.img as per the error you get with fastboot flash boot twrp.img.

supercfc said:
Use fastboot flash boot_a twrp.img or fastboot flash boot_b twrp.img as per the error you get with fastboot flash boot twrp.img.
Click to expand...
Click to collapse
Also I could only get it to flash using essentials USB/fastboot drivers here:
https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
I did have your problem several times though. And was eventually able to get it to flash.

supercfc said:
Use fastboot flash boot_a twrp.img or fastboot flash boot_b twrp.img as per the error you get with fastboot flash boot twrp.img.
Click to expand...
Click to collapse
also not working
C:\Program Files (x86)\Essential\ADB>fastboot getvar current-slot
current-slot: _b
finished. total time: 0.003s
C:\Program Files (x86)\Essential\ADB>fastboot set_active other
Setting current slot to 'a'...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Program Files (x86)\Essential\ADB>fastboot getvar current-slot
current-slot: _a
finished. total time: 0.002s
C:\Program Files (x86)\Essential\ADB>fastboot flash boot_a twrp.img
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.083s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.247s

illuminatex said:
also not working
C:\Program Files (x86)\Essential\ADB>fastboot getvar current-slot
current-slot: _b
finished. total time: 0.003s
C:\Program Files (x86)\Essential\ADB>fastboot set_active other
Setting current slot to 'a'...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Program Files (x86)\Essential\ADB>fastboot getvar current-slot
current-slot: _a
finished. total time: 0.002s
C:\Program Files (x86)\Essential\ADB>fastboot flash boot_a twrp.img
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.083s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.247s
Click to expand...
Click to collapse
First do 'fastboot flash boot twrp.img'.
It will fail but it will give you 'sending 'boot_a' (45048 KB)...' or 'sending 'boot_b' (45048 KB)...' in the logs.
The do 'fastboot flash boot_a twrp.img'. or 'fastboot flash boot_b twrp.img'. according to the 'sending' partition you get. If you get 'sending 'boot_b' . do the same 'fastboot flash boot_b twrp.img'. Don't do the opposite 'fastboot flash boot_a twrp.img'.

supercfc said:
First do 'fastboot flash boot twrp.img'.
It will fail but it will give you 'sending 'boot_a' (45048 KB)...' or 'sending 'boot_b' (45048 KB)...' in the logs.
The do 'fastboot flash boot_a twrp.img'. or 'fastboot flash boot_b twrp.img'. according to the 'sending' partition you get. If you get 'sending 'boot_b' . do the same 'fastboot flash boot_b twrp.img'. Don't do the opposite 'fastboot flash boot_a twrp.img'.
Click to expand...
Click to collapse
Wiping the partition again and again did the trick ... now I'm in TWRP but unfortunately next error occurs. I flashed stockboot.img and magisk.zip and rebooted. Now the phone is stuck on loading Android (moving points). boot_b works still fine!

Hi,
I'm trying to boot to TWRP (the PH-1 'mata' TWRP) but even after wiping partition i still have "No Such Partition" on Writing...
I use the PH-1 USB cable on my laptop... restarted, rewiped, nothing...
Am I doing something wrong?
EDIT : ok, tried with Essential's ADB and it worked.

supercfc said:
First do 'fastboot flash boot twrp.img'.
It will fail but it will give you 'sending 'boot_a' (45048 KB)...' or 'sending 'boot_b' (45048 KB)...' in the logs.
The do 'fastboot flash boot_a twrp.img'. or 'fastboot flash boot_b twrp.img'. according to the 'sending' partition you get. If you get 'sending 'boot_b' . do the same 'fastboot flash boot_b twrp.img'. Don't do the opposite 'fastboot flash boot_a twrp.img'.
Click to expand...
Click to collapse
Thanks, it did the JOB

nvm.

supercfc said:
First do 'fastboot flash boot twrp.img'.
It will fail but it will give you 'sending 'boot_a' (45048 KB)...' or 'sending 'boot_b' (45048 KB)...' in the logs.
The do 'fastboot flash boot_a twrp.img'. or 'fastboot flash boot_b twrp.img'. according to the 'sending' partition you get. If you get 'sending 'boot_b' . do the same 'fastboot flash boot_b twrp.img'. Don't do the opposite 'fastboot flash boot_a twrp.img'.
Click to expand...
Click to collapse
C:\adb>fastboot flash boot_b twrp.img
target reported max download size of 805306368 bytes
sending 'boot_b' (31060 KB)...
OKAY [ 0.824s]
writing 'boot_b'...
FAILED (remote: (boot_b) No such partition)
finished. total time: 0.828s
How do I fix this?

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

Razer phone 2 MR3 build posted on dev site

MR3 build as posted
https://developer.razer.com/razer-phone-dev-tools/factory-images/

These instructions assumes that you have platform tools and the Google ADB drivers installed. If you need instructions for that, look here:
Google ADB Drivers & Androind SDK Platform Tools instructions
To do an upgrade/dirty flash do the following:
Extract the Zip, If you dont want root, skip to step 8
Copy boot.img to you phone
Open Magisk Manager app and Install > Patch Image
Copy "magisk_patch.img" from your phone's Downloads to the folder you extracted the ROM to.
Edit/Copy the flash_all.bat (or .sh on Linux/Mac)
Find the lines 54 & 55 with:
Code:
%fastboot_cmd% flash boot_a boot.img
%fastboot_cmd% flash boot_b boot.img
Change them to:
Code:
rem %fastboot_cmd% flash boot_a boot.img
rem %fastboot_cmd% flash boot_b boot.img
%fastboot_cmd% flash boot_a magisk_patched.img
%fastboot_cmd% flash boot_b magisk_patched.img
Find line 71(73 if you did the steps above) with:
Code:
%fastboot_cmd% erase userdata
Change it to:
Code:
rem %fastboot_cmd% erase userdata
Save the batch script file
Reboot your phone and hold the 'Volume Down' button until your phone boots into "Fastboot Mode"
Run flash_all.bat or what ever you named it, It will reboot your phone twice, the second is when it is done and booting into android.

They finally did it LOL.
Hope Android 10 or even 11 on their update roadmap.

ah! finally I can upgrade without losing all my data.

I see a bunch of errors like:
"Flashing is not allowed for Critical Partitions"
or
"Erase is not allowed for Critical Partitions"
are those normal errors?
Code:
D:\aura-p-release-3141>fastboot flash xbl_b xbl.img
Sending 'xbl_b' (3279 KB) OKAY [ 0.094s]
Writing 'xbl_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash xbl_config_a xbl_config.img
Sending 'xbl_config_a' (95 KB) OKAY [ 0.013s]
Writing 'xbl_config_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash xbl_config_b xbl_config.img
Sending 'xbl_config_b' (95 KB) OKAY [ 0.005s]
Writing 'xbl_config_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash tz_a tz.img
Sending 'tz_a' (2008 KB) OKAY [ 0.065s]
Writing 'tz_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash tz_b tz.img
Sending 'tz_b' (2008 KB) OKAY [ 0.060s]
Writing 'tz_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash hyp_a hyp.img
Sending 'hyp_a' (376 KB) OKAY [ 0.012s]
Writing 'hyp_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash hyp_b hyp.img
Sending 'hyp_b' (376 KB) OKAY [ 0.019s]
Writing 'hyp_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash aop_a aop.img
Sending 'aop_a' (180 KB) OKAY [ 0.015s]
Writing 'aop_a' OKAY [ 0.003s]
Finished. Total time: 0.028s
D:\aura-p-release-3141>fastboot flash aop_b aop.img
Sending 'aop_b' (180 KB) OKAY [ 0.009s]
Writing 'aop_b' OKAY [ 0.002s]
Finished. Total time: 0.022s
D:\aura-p-release-3141>fastboot flash keymaster_a keymaster.img
Sending 'keymaster_a' (227 KB) OKAY [ 0.008s]
Writing 'keymaster_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash keymaster_b keymaster.img
Sending 'keymaster_b' (227 KB) OKAY [ 0.016s]
Writing 'keymaster_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash cmnlib_a cmnlib.img
Sending 'cmnlib_a' (367 KB) OKAY [ 0.019s]
Writing 'cmnlib_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash cmnlib_b cmnlib.img
Sending 'cmnlib_b' (367 KB) OKAY [ 0.021s]
Writing 'cmnlib_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash cmnlib64_a cmnlib64.img
Sending 'cmnlib64_a' (484 KB) OKAY [ 0.020s]
Writing 'cmnlib64_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash cmnlib64_b cmnlib64.img
Sending 'cmnlib64_b' (484 KB) OKAY [ 0.015s]
Writing 'cmnlib64_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash devcfg_a devcfg.img
Sending 'devcfg_a' (39 KB) OKAY [ 0.010s]
Writing 'devcfg_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash devcfg_b devcfg.img
Sending 'devcfg_b' (39 KB) OKAY [ 0.007s]
Writing 'devcfg_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash ImageFv_a ImageFv.img
Sending 'ImageFv_a' (20 KB) OKAY [ 0.010s]
Writing 'ImageFv_a' OKAY [ 0.001s]
Finished. Total time: 0.020s
D:\aura-p-release-3141>fastboot flash ImageFv_b ImageFv.img
Sending 'ImageFv_b' (20 KB) OKAY [ 0.006s]
Writing 'ImageFv_b' OKAY [ 0.001s]
Finished. Total time: 0.017s
D:\aura-p-release-3141>fastboot flash qupfw_a qupfw.img
Sending 'qupfw_a' (63 KB) OKAY [ 0.005s]
Writing 'qupfw_a' OKAY [ 0.002s]
Finished. Total time: 0.015s
D:\aura-p-release-3141>fastboot flash qupfw_b qupfw.img
Sending 'qupfw_b' (63 KB) OKAY [ 0.012s]
Writing 'qupfw_b' OKAY [ 0.001s]
Finished. Total time: 0.024s
D:\aura-p-release-3141>fastboot flash abl_a abl.img
Sending 'abl_a' (1024 KB) OKAY [ 0.038s]
Writing 'abl_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.002s
D:\aura-p-release-3141>timeout /t 10
Waiting for 0 seconds, press a key to continue ...
D:\aura-p-release-3141>fastboot oem simconfig set SS
OKAY [ 0.001s]
Finished. Total time: 0.001s
D:\aura-p-release-3141>fastboot flash avb_custom_key pkmd.bin
fastboot: error: cannot load 'pkmd.bin': No such file or directory
D:\aura-p-release-3141>fastboot flash abl_b abl.img
Sending 'abl_b' (1024 KB) OKAY [ 0.036s]
Writing 'abl_b' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot erase ddr
Erasing 'ddr' FAILED (remote: 'Erase is not allowed for Critical Partitions
')
fastboot: error: Command failed
D:\aura-p-release-3141>fastboot flash persist persist.img
Sending 'persist' (32768 KB) OKAY [ 0.923s]
Writing 'persist' OKAY [ 0.411s]
Finished. Total time: 1.345s
D:\aura-p-release-3141>fastboot flash modem_a modem.img
Sending 'modem_a' (116444 KB) OKAY [ 3.292s]
Writing 'modem_a' OKAY [ 0.916s]
Finished. Total time: 4.218s
D:\aura-p-release-3141>fastboot flash modem_b modem.img
Sending 'modem_b' (116444 KB) OKAY [ 3.296s]
Writing 'modem_b' OKAY [ 0.884s]
Finished. Total time: 4.197s
D:\aura-p-release-3141>fastboot flash dsp_a dsp.img
Sending 'dsp_a' (32768 KB) OKAY [ 0.925s]
Writing 'dsp_a' OKAY [ 0.232s]
Finished. Total time: 1.166s
D:\aura-p-release-3141>fastboot flash dsp_b dsp.img
Sending 'dsp_b' (32768 KB) OKAY [ 0.925s]
Writing 'dsp_b' OKAY [ 0.246s]
Finished. Total time: 1.202s
D:\aura-p-release-3141>fastboot flash boot_a magisk_patched.img
Sending 'boot_a' (20772 KB) OKAY [ 0.594s]
Writing 'boot_a' OKAY [ 0.165s]
Finished. Total time: 0.768s
D:\aura-p-release-3141>fastboot flash boot_b magisk_patched.img
Sending 'boot_b' (20772 KB) OKAY [ 0.592s]
Writing 'boot_b' OKAY [ 0.299s]
Finished. Total time: 0.907s
D:\aura-p-release-3141>fastboot flash dtbo_a dtbo.img
Sending 'dtbo_a' (8192 KB) OKAY [ 0.238s]
Writing 'dtbo_a' OKAY [ 0.066s]
Finished. Total time: 0.312s
D:\aura-p-release-3141>fastboot flash dtbo_b dtbo.img
Sending 'dtbo_b' (8192 KB) OKAY [ 0.239s]
Writing 'dtbo_b' OKAY [ 0.066s]
Finished. Total time: 0.333s
D:\aura-p-release-3141>fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (748 KB) OKAY [ 0.026s]
Writing 'bluetooth_a' OKAY [ 0.005s]
Finished. Total time: 0.042s
D:\aura-p-release-3141>fastboot flash bluetooth_b bluetooth.img
Sending 'bluetooth_b' (748 KB) OKAY [ 0.028s]
Writing 'bluetooth_b' OKAY [ 0.008s]
Finished. Total time: 0.054s
D:\aura-p-release-3141>fastboot flash logfs logfs_ufs_8mb.bin
Sending 'logfs' (16 KB) OKAY [ 0.010s]
Writing 'logfs' OKAY [ 0.001s]
Finished. Total time: 0.021s
D:\aura-p-release-3141>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (515468 KB) OKAY [ 15.415s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 2/6 (514448 KB) OKAY [ 19.345s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 3/6 (515328 KB) OKAY [ 19.086s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 4/6 (516208 KB) OKAY [ 19.555s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 5/6 (516208 KB) OKAY [ 19.726s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 6/6 (367560 KB) OKAY [ 15.416s]
Writing 'system_a' OKAY [ 0.000s]
Finished. Total time: 114.098s
D:\aura-p-release-3141>fastboot flash system_b system_other.img
Sending 'system_b' (335964 KB) OKAY [ 9.455s]
Writing 'system_b' OKAY [ 0.001s]
Finished. Total time: 9.615s
D:\aura-p-release-3141>fastboot flash vendor_a vendor.img
Sending 'vendor_a' (493676 KB) OKAY [ 13.896s]
Writing 'vendor_a' OKAY [ 0.001s]
Finished. Total time: 14.120s
D:\aura-p-release-3141>fastboot flash vendor_b vendor.img
Sending 'vendor_b' (493676 KB) OKAY [ 13.900s]
Writing 'vendor_b' OKAY [ 0.000s]
Finished. Total time: 14.129s
D:\aura-p-release-3141>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_a' OKAY [ 0.001s]
Finished. Total time: 0.019s
D:\aura-p-release-3141>fastboot flash vbmeta_b vbmeta.img
Sending 'vbmeta_b' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_b' OKAY [ 0.001s]
Finished. Total time: 0.019s
D:\aura-p-release-3141>fastboot flash systeminfo_a systeminfo.img
fastboot: error: cannot load 'systeminfo.img': No such file or directory
D:\aura-p-release-3141>fastboot flash systeminfo_b systeminfo.img
fastboot: error: cannot load 'systeminfo.img': No such file or directory
D:\aura-p-release-3141>fastboot flash nvdef_a nvdef.img
Sending 'nvdef_a' (1380 KB) OKAY [ 0.046s]
Writing 'nvdef_a' OKAY [ 0.021s]
Finished. Total time: 0.077s
D:\aura-p-release-3141>fastboot flash nvdef_b nvdef.img
Sending 'nvdef_b' (1380 KB) OKAY [ 0.049s]
Writing 'nvdef_b' OKAY [ 0.018s]
Finished. Total time: 0.084s
D:\aura-p-release-3141>rem fastboot erase userdata
D:\aura-p-release-3141>fastboot erase box
Erasing 'box' OKAY [ 0.086s]
Finished. Total time: 0.092s
D:\aura-p-release-3141>fastboot flash splash splash.img
Sending 'splash' (10816 KB) OKAY [ 0.312s]
Writing 'splash' OKAY [ 0.090s]
Finished. Total time: 0.412s
D:\aura-p-release-3141>fastboot flash storsec storsec.mbn
Sending 'storsec' (20 KB) OKAY [ 0.006s]
Writing 'storsec' OKAY [ 0.002s]
Finished. Total time: 0.017s
D:\aura-p-release-3141>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
*** waiting for boot... 30 min later... ***
No luck...
seems like it didn't like the replacement for the magisk_patched.img
went back to fastboot mode, flashed MR3 without root, basically skipped to step 8 directly, that worked well.
booted into OS in like 15 sec.
it kept all my data, nice.
Now I need to figure out how to root it again, so i can keep using Titanium Backup and many other Apps that only works with root.
*** after a while ... ***
Alright
flashed latest R14 arter97 (https://forum.xda-developers.com/razer-phone-2/development/arter97-kernel-razer-phone-2-t3914996) kernel img to boot a and boot b
this gives me access to TWRP
picked up latest version of Magisk https://******************/
booted to TWRP
flashed Magisk root.
now I'm back in business with Titanium Backup, etc...

Hi!
I just wanted to share my experience performing this steps.
I dirty Flashed. In short, everthing worked, with a minor hiccup. After rebooting the first time, it said encryption unsuccessful, so I rebooted to TWRP and flashed f2fs_fstab.zip and vold_mod_arter97.zip that I had copied before to the phone (not being sure if I'd need them), rebooted and everything worked!
AllGamer said:
I see a bunch of errors like:
"Flashing is not allowed for Critical Partitions"
or
"Erase is not allowed for Critical Partitions"
are those normal errors?
Click to expand...
Click to collapse
Yes, it happends when the partitions are locked for flashing, you should be able to unlock them with the following command.
Code:
fastboot flashing unlock_critical
I didn't had to do this for these steps to work for me though.
Cheers.

is there a changelog for the new mr3 build?

Link to the patched Global MR3 boot image with Magisk
Patched boot.img
omega552003 said:
These instructions assumes that you have platform tools and the Google ADB drivers installed. If you need instructions for that, look here:
Google ADB Drivers & Androind SDK Platform Tools instructions
To do an upgrade/dirty flash do the following:
Extract the Zip, If you dont want root, skip to step 8
Copy boot.img to you phone
Open Magisk Manager app and Install > Patch Image
Copy "magisk_patch.img" from your phone's Downloads to the folder you extracted the ROM to.
Edit/Copy the flash_all.bat (or .sh on Linux/Mac)
Find the lines 54 & 55 with:
Code:
%fastboot_cmd% flash boot_a boot.img
%fastboot_cmd% flash boot_b boot.img
Change them to:
Code:
rem %fastboot_cmd% flash boot_a boot.img
rem %fastboot_cmd% flash boot_b boot.img
%fastboot_cmd% flash boot_a magisk_patched.img
%fastboot_cmd% flash boot_b magisk_patched.img
Find line 71(73 if you did the steps above) with:
Code:
%fastboot_cmd% erase userdata
Change it to:
Code:
rem %fastboot_cmd% erase userdata
Save the batch script file
Reboot your phone and hold the 'Volume Down' button until your phone boots into "Fastboot Mode"
Run flash_all.bat or what ever you named it, It will reboot your phone twice, the second is when it is done and booting into android.
Click to expand...
Click to collapse

Hello everyone,
I tried to dirty flash it easily through fastboot (flash_all) as per razer instructions and now I seem to be stuck in a quasi-boot loop.
Devices reaches system and after two seconds it pops the window "Power off - shutting down" and it reboots. After rebooting, I get a similar to bootloader interaction saying that boot failed and that i should wipe userdata, which I do, with no effect.
Sometimes, after I tried flashing MSR2 and 1, i get an interaction saying that android.process.acore stopped working and then it powers off.
Safe mode didn't help either. Any suggestion? I need to RMA this one for a screen issue and I wanted to wipe everything installing the system from scratch, I don't think that they will accept it as is.
Thank you for your help!

Makyura said:
Hello everyone,
I tried to dirty flash it easily through fastboot (flash_all) as per razer instructions and now I seem to be stuck in a quasi-boot loop.
Devices reaches system and after two seconds it pops the window "Power off - shutting down" and it reboots. After rebooting, I get a similar to bootloader interaction saying that boot failed and that i should wipe userdata, which I do, with no effect.
Sometimes, after I tried flashing MSR2 and 1, i get an interaction saying that android.process.acore stopped working and then it powers off.
Safe mode didn't help either. Any suggestion? I need to RMA this one for a screen issue and I wanted to wipe everything installing the system from scratch, I don't think that they will accept it as is.
Thank you for your help!
Click to expand...
Click to collapse
Dont dirty flash
Make sure both your bootloader and bootloader critical are unlock
just flash as usual and download the rom from
https://developer.razer.com/razer-phone-dev-tools/factory-images/
general instruction from below
https://developer.razer.com/razer-p...70.285929881.1593019602-1360853609.1593019602

hoodred said:
Dont dirty flash
Make sure both your bootloader and bootloader critical are unlock
just flash as usual and download the rom from
https://developer.razer.com/razer-phone-dev-tools/factory-images/
general instruction from below
https://developer.razer.com/razer-p...70.285929881.1593019602-1360853609.1593019602
Click to expand...
Click to collapse
I was flashing those, but none of the recent ones worked. I had to flash the very first release, 8.1 MR0 (litterally tried all of them backwards).

Unable to get to fast boot
If not in the right location please direct me. I'm at quite aloss I've been extensively reading the forums to root my razer phone 2. I cannot get windows 10 to recognize the phone in fastboot in cmd prompt while in bootloader, it will recognize the phone while it's on and adb works. Once I give the command for adb reboot bootloader it has the phone reboot to boot loader but fastboot won't detect. I've tried updating the drivers and it still shows android with the question mark circle. I know it must be something simple I'm overlooking. Please can anyone assist?

I've had this same issue. I think it's something with Windows 10 Update 2004. What I ended up doing was getting a usb drive and making a boot disk with FWUL on it. Which makes a live linux disk with all the tools you need.

NO COMMAND when booting system. TWRP has no storage, cache, etc.

Hello I've messed up and didn't flash with fastboot correctly. I try to flash a stock oreo rom via fastboot with the commands at the end of the post and it boots "NO COMMAND". Then I flashed TWRP to flash a zip with it and phone has no STORAGE or memory or anything, so it keeps failing.
Is there any way via fastboot or anything to fresh start?
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
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse

The last version of software for the G5 plus (potter:8.1.0/OPS28 .85-17-6-2) only shows 8 sparsechunk.x files - your batch file shows 10 sparsechunks - did you flash the proper firmware for your unit ?
Whats the model number of the phone and the file name of the firmware you used ?

I downloaded two OREO roms and tried both. Followed this post https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 but maybe I messed up when choosing the rom: selected one first, and after it failed, did a -w in fastboot and tried the next one. My phone is a g5 potter
This is the other ROM I tried: https://qc5.androidfilehost.com/dl/...er-twrp-flashable-OPSS28.85-17-6-2-aroma.zip?

https://mirrors.lolinet.com/firmware/moto/potter/official/
potter Moto G5 Plus firmware last update August 2019
XT1680(LATAM/Argentina/Chile,2GB)
XT1681(LATAM/Colombia/Mexico,2GB)
XT1683(Brazil,DS,DTV,2GB)
XT1684(Europe,3GB)
XT1685(Australia/Europe/NewZealand,3GB)
XT1686(India,3/4GB)
XT1687(USA,2GB/4GB)
==========
AMXBR
XT1683_POTTER_AMXBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMXCL
XT1680_POTTER_AMXLA_8.1.0_OPSS28.85-13-3_cid50_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
==========
AMXCO
XT1680_POTTER_AMXLA_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMXLA
XT1680_POTTER_AMXLA_8.1.0_OPS28.85-17-6-2_cid50_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
==========
AMXMX
XT1680_POTTER_AMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMXPE
XT1680_POTTER_AMXLA_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMZ
XT1687_POTTER_AMZ_8.1.0_OPSS28.85-17-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
ATTMX
XT1680_POTTER_ATTMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-IUSMXLA_regulatory-DEFAULT_CFC.xml.zip
==========
CC
XT1687_POTTER_CCAWS_8.1.0_OPSS28.85-17-6_cid50_subsidy-CCAWS_regulatory-DEFAULT_CFC.xml.zip
==========
LRA
XT1687_LRA_8.1.0_OPSS28.85-13-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETAIL
POTTER_RETAIL_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETAPAC
XT1684_POTTER_RETEU_SS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1685_POTTER_RETEU_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETAR
XT1680_POTTER_RETAR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETBR
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETEU
XT1684_POTTER_RETEU_SS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1685_POTTER_RETEU_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETGB
XT1684_POTTER_RETEU_SS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1685_POTTER_RETEU_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETIN
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETLA
XT1681_POTTER_RETLA_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETLA1ST
XT1680_POTTER_RETLA1ST_8.1.0_OPSS28.85-13-5_cid50_subsidy-LATAM_SELFPERSO_regulatory-DEFAULT_CFC.xml.zip
==========
RETMX
XT1681_POTTER_RETMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETUS
XT1687_POTTER_RETUS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFBR
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFCO
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFES
XT1685_POTTER_TEFES_8.1.0_OPSS28.85-17-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFMX
XT1681_POTTER_TEFMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-MOVSTLA_regulatory-DEFAULT_CFC.xml.zip
==========
TIGCO
XT1681_POTTER_TEFCO_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TIMBR
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
---------- Post added at 05:07 AM ---------- Previous post was at 04:45 AM ----------
your fastboot commands for OPS28.85-17-6-2 should have been;
Fastboot flash partition gpt.bin
Fastboot flash bootloader bootloader.img
Fastboot flash modem NON-HLOS.bin
Fastboot flash fsg fsg.mbn
Fastboot flash dsp adspso.bin
Fastboot flash 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 oem oem.img
Fastboot erase cache
Fastboot erase userdata
Fastboot erase DDR
Fastboot reboot
if you have a backup of your EFS and PERSIST:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
whats the model of the phone and the country your in ?

Its the 2gb model. I live in Argentina. I didn't back up EFS or PERSIST sadly

I'm not an expert on the firmware, but I know which US versions to use. I believe that your phone is the XT1680, and the firmware would be XT1680_POTTER_RETAR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip under the RETAR directory at https://mirrors.lolinet.com/firmware/moto/potter/official/
In my past experience, no command was missing the recovery program TWRP. I would just fastboot it again, onto my phone, and then go back to recovery, and TWRP would be there.
It sounds like in your case the partitions may be missing, and TWRP would not see anything.
I try would fastboot the firmware listed at the lolinet mirror (use the batch file listed above that does not erase the modems and EFS/Persist) and see if it comes back. I would first delete the ADB folder and all software in it, it appears you may have had the wrong firmware. Put a new copy of the ADB software, a new copy of the extracted firmware from the mirror. See if it comes back,
If it does not work and fastboot appears to work, sounds like you would have to recover or recreate linux partitions on the phone. If there is no response from the phone, its probably bricked.
Hope that helps and thats all I can suggest.

Nivead said:
I'm not an expert on the firmware, but I know which US versions to use. I believe that your phone is the XT1680, and the firmware would be XT1680_POTTER_RETAR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip under the RETAR directory at https://mirrors.lolinet.com/firmware/moto/potter/official/
In my past experience, no command was missing the recovery program TWRP. I would just fastboot it again, onto my phone, and then go back to recovery, and TWRP would be there.
It sounds like in your case the partitions may be missing, and TWRP would not see anything.
I try would fastboot the firmware listed at the lolinet mirror (use the batch file listed above that does not erase the modems and EFS/Persist) and see if it comes back. I would first delete the ADB folder and all software in it, it appears you may have had the wrong firmware. Put a new copy of the ADB software, a new copy of the extracted firmware from the mirror. See if it comes back,
If it does not work and fastboot appears to work, sounds like you would have to recover or recreate linux partitions on the phone. If there is no response from the phone, its probably bricked.
Hope that helps and thats all I can suggest.
Click to expand...
Click to collapse
Thank you for your help. Sadly, it doesnt work - it still says No Command. I'll quote the CMD Log down here, if anyone finds it informative.
If anyone can point me about recreating linux partitions on the android, I'd be glad. I have no idea what that is, although I'm going to look for it right now.
Bumping this post to see if anyone has an idea. Thank you Nivead.
C:\Users\Fresco\Desktop\asd>Fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.077s]
Finished. Total time: 0.257s
C:\Users\Fresco\Desktop\asd>Fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.284s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.548s]
Finished. Total time: 0.861s
C:\Users\Fresco\Desktop\asd>Fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (71921 KB) OKAY [ 1.737s]
Writing 'modem' OKAY [ 1.109s]
Finished. Total time: 2.892s
C:\Users\Fresco\Desktop\asd>Fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (3012 KB) OKAY [ 0.234s]
Writing 'fsg' OKAY [ 0.119s]
Finished. Total time: 0.363s
C:\Users\Fresco\Desktop\asd>Fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.525s]
Writing 'dsp' OKAY [ 0.298s]
Finished. Total time: 0.835s
C:\Users\Fresco\Desktop\asd>Fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2186 KB) OKAY [ 0.216s]
Writing 'logo' OKAY [ 0.102s]
Finished. Total time: 0.330s
C:\Users\Fresco\Desktop\asd>Fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.549s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.376s]
Finished. Total time: 0.935s
C:\Users\Fresco\Desktop\asd>Fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.628s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.481s]
Finished. Total time: 1.124s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (258396 KB) OKAY [ 5.877s]
Writing 'system' OKAY [ 3.773s]
Finished. Total time: 9.797s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256514 KB) OKAY [ 5.857s]
Writing 'system' OKAY [ 3.344s]
Finished. Total time: 9.337s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (246302 KB) OKAY [ 5.557s]
Writing 'system' OKAY [ 3.662s]
Finished. Total time: 9.355s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 5.863s]
Writing 'system' OKAY [ 3.378s]
Finished. Total time: 9.384s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 5.862s]
Writing 'system' OKAY [ 3.482s]
Finished. Total time: 9.481s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 5.928s]
Writing 'system' OKAY [ 3.369s]
Finished. Total time: 9.433s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (250531 KB) OKAY [ 5.631s]
Writing 'system' OKAY [ 3.717s]
Finished. Total time: 9.484s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (262059 KB) OKAY [ 5.870s]
Writing 'system' OKAY [ 3.786s]
Finished. Total time: 9.799s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (254142 KB) OKAY [ 5.677s]
Writing 'system' OKAY [ 3.338s]
Finished. Total time: 9.163s
C:\Users\Fresco\Desktop\asd>Fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (104608 KB) OKAY [ 2.437s]
Writing 'oem' OKAY [ 1.391s]
Finished. Total time: 3.892s
C:\Users\Fresco\Desktop\asd>Fastboot erase cache
Erasing 'cache' OKAY [ 0.012s]
Finished. Total time: 0.014s
C:\Users\Fresco\Desktop\asd>Fastboot erase userdata
Erasing 'userdata' OKAY [ 0.175s]
Finished. Total time: 0.177s
C:\Users\Fresco\Desktop\asd>Fastboot erase DDR
Erasing 'DDR' OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\Users\Fresco\Desktop\asd>Fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
Click to expand...
Click to collapse

bump

crata said:
I downloaded two OREO roms and tried both. Followed this post https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 but maybe I messed up when choosing the rom: selected one first, and after it failed, did a -w in fastboot and tried the next one. My phone is a g5 potter
This is the other ROM I tried: https://qc5.androidfilehost.com/dl/...er-twrp-flashable-OPSS28.85-17-6-2-aroma.zip?
Click to expand...
Click to collapse
The second ROM seems to be (by name) a TWRP flashable which means it's not possible to flash it by fastboot, only by TWRP.
Maybe that should be the way to go for you. If you can't flash any fastboot firmware maybe try a TWRP flashable.
Versions and tutorials are here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482

Wolfcity said:
The second ROM seems to be (by name) a TWRP flashable which means it's not possible to flash it by fastboot, only by TWRP.
Maybe that should be the way to go for you. If you can't flash any fastboot firmware maybe try a TWRP flashable.
Versions and tutorials are here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Click to expand...
Click to collapse
Thanks for the effort but I can't flash via TWRP because it doesn't recognize any storage