Database Users

Nexus 7 boot.img flash fails with FileWriteFailed

Device: Nexus 7 (2012) WIFI only
After 4.3 update device started locking up and had to repeatedly long-press power to reboot. Factory defaut fixed first time, Second time (because it started happening again) could not recover from factory default. boot.img will not install and returns a (remote: FileWriteFailed) error.
I've tried multiple cables, PCs, and toolkits with no luck.
I can load bootloaders without issue.
I can format and load system, userdata, recovery (have loaded stock, TWRP, CWM recoveries) all appear to load without issue and work fine but haven't been able to fix this issue.
Once the boot.img flash is attempted, the device locks up hard and a long-press of power is needed to bring it back.
I can boot to Google screen with (Start, Power off, Recovery mode, Restart bootloader options) or directly to bootloader without issue.
First tried restoring 4.3 factory, but have since been trying 4.2.2 factory using Nexus Root Toolkit, Nexus 7 Toolkit, and a lot of SDK command line of fastboot commands. I can run ADB commands if I first get into recovery.
Is there a option I can tickle or something else anyone knows I can try? I'm beginning to think the boot sector of the flash is defective (if this makes sense).
Here's an example of a fastboot update. It hasn't mattered the method, the outcome is always identical. It fails at boot.img flash write failure.
>fastboot devices
015d490651281e0e fastboot
>fastboot erase boot
erasing 'boot'...
OKAY [ 1.186s]
finished. total time: 1.186s
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.998s]
finished. total time: 0.998s
>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.796s]
finished. total time: 0.796s
>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.649s]
finished. total time: 4.649s
>fastboot flash bootloader bootloader-grouper-4.18.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.312s]
writing 'bootloader'...
OKAY [ 9.875s]
finished. total time: 10.202s
>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
>fastboot -w update image-nakasi-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d490651281e0e
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.686s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 5.210s
>

This issue has been resolved. The Nexus 7 was returned to Asus support and the motherboard was replaced under warranty.

FTM Mode and Bricked?? LS980

Hey guys, I've tried to hold off posting as long as possible and don't know what to search for to answer the question. I'll start from the beginning. I tried to flash a custom recovery after taking the OTA update to KK. I then rooted with IORoot and everything worked great. I used that Freegee app to try to flash TWRP 2.7 and it went into recovery, started flashing and then immediately rebooted. The Freegee app and other apps kept saying that I had the stock recovery even after multiple flash attemps. I then used the KK AutoRec tool because I thought that would allow for the custom recovery. After doing that, the phone was soft bricked and I was stuck in Fastboot. I used this: http://forum.xda-developers.com/show....php?t=2477595 to reflash everything except PrimaryGTP because I couldn't figure out how to do the PrimaryGTP portion. That worked great and my phone would reboot, but it rebooted into FTM mode with NO software buttons on it. After multiple reboots FTM mode will not exit. Here is the log of the adb terminal commands
Quote:
C:\>fastboot erase recovery
erasing 'recovery'... OKAY
C:\>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY
writing 'recovery'... OKAY
C:\>fastboot erase aboot
erasing 'aboot'... OKAY
C:\>fastboot flash aboot aboot.img
sending 'aboot' (1024 KB)... OKAY
writing 'aboot'... OKAY
C:\>fastboot reboot
rebooting...
C:\>fastboot erase modem
erasing 'modem'... OKAY
C:\>fastboot flash modem 1-modem
error: cannot load '1-modem'
C:\>fastboot flash modem modem.img
sending 'modem' (57856 KB)... OKAY
writing 'modem'... OKAY
C:\>fastboot erase boot
erasing 'boot'... OKAY
C:\>fastboot flash boot 6-boot.img
sending 'boot' (11264 KB)... OKAY
writing 'boot'... OKAY
C:\>fastboot erase PrimaryGPT
erasing 'PrimaryGPT'... FAILED (remote: Partition table doesn't exist
)
C:\>fastboot erase primarygpt
erasing 'primarygpt'... FAILED (remote: Partition table doesn't exist
)
C:\>fastboot erase sbl1
erasing 'sbl1'... OKAY
C:\>fastboot flash sbl1 2-sbl1.img
sending 'sbl1' (512 KB)... OKAY
writing 'sbl1'... OKAY
C:\>fastboot erase dbi
erasing 'dbi'... OKAY
C:\>fastboot flash dbi 3-dbi.img
sending 'dbi' (512 KB)... OKAY
writing 'dbi'... OKAY
C:\>fastboot erase aboot
erasing 'aboot'... OKAY
C:\>fastboot flash aboot aboot.img
sending 'aboot' (1024 KB)... OKAY
writing 'aboot'... OKAY
C:\>fastboot erase rpm
erasing 'rpm'... OKAY
C:\>fastboot flash rpm 5-rpm.img
sending 'rpm' (512 KB)... OKAY
writing 'rpm'... OKAY
C:\>fastboot erase boot
erasing 'boot'... OKAY
C:\>fastboot flash boot 6-boot.img
sending 'boot' (11264 KB)... OKAY
writing 'boot'... OKAY
C:\>fastboot erase tz
erasing 'tz'... OKAY
C:\>fastboot flash tz 7-tz.img
sending 'tz' (512 KB)... OKAY
writing 'tz'... OKAY
C:\>fastboot erase misc
erasing 'misc'... OKAY
C:\>fastboot flash misc 8-misc.img
sending 'misc' (8192 KB)... OKAY
writing 'misc'... OKAY
C:\>fastboot erase persist
erasing 'persist'... OKAY
C:\>fastboot flash persist persist.img
sending 'persist' (5120 KB)... OKAY
writing 'persist'... OKAY
C:\>fastboot reboot
rebooting...
C:\>adb devices
List of devices attached
C:\>^A
I then tried to flash stock TOT to start completely over because I thought that would work. This is the error I keep getting: (Picture below)
I then thought a factory reset would do the trick. I did that and it worked using the power button + Volume down method. It rebooted like normal as if it was completely stock yet the FTM mode is still on there. When I get into download mode and attach it into the LG Flash tool and that Firmware Update screen comes onto my phone, the box says:
Quote:
910K S0.0 AS0.0 B99 UHS
S U LG-LS980 04.4.2 Hrev_10
LS980ZVC_12
ROOTED
I have no clue where to go from here. Please Help

anyone know whats going on?

Just an update if this helps. I can make calls with the "Q-Slide" feature, but I still don't have software buttons. The phone activated just like it should have and it shows everything great and I have LTE but after multiple restarts it still goes into FTM mode and I can't exit the mode when the phone is off. I just so happen to get lucky and get into the setting menu and hit update PRL and activate, which activated LTE. So thats one step forward I guess. Does anyone know whats going on?? In the LG flash tools both the PID and IMEI read: NULL.

Motorol Moto G 2nd edition XT1608 UK - STUCK ON BLACK BACKLIT SCREEN

Hi all.
Had a moto g for a while and had no problems at all, until yesterday: WhatsApp crashed and said do I want to restore the history - I chose yes, and then it looked as if the app crashed, a black screen appeared
Turn the phone on/off and after the boot process has finished (android/motorola logo) the phone is once again stuck on the black screen -
Tried clearing the cache from the recovery mode , I've tried using fastboot and flashing the ROM back to 4.4.4 - but had absolutely no success
It was suggested to install ClockWordMod recovery or TWM, and I did this using fastboot, fastboot says it's complete and ok, but then everytime I go to recovery mode I have the lying down android saying no command, and the only place I can get too from there is the normal android recovery screen , I've tried reseting the factory defaults, clearing cache , but I can'#t get anything to work
Any help/advice is really appreciated - does anyone know why I cant boot into clockwork recovery after having flashed it successfully according to fastboot?
Thanks
Mark

You just can flash the factory firmware (stock) and relock the bootloader using mfastboot v2. It will fix this, I had this problem two times and the process above got me out of it. Also if first flash gives errors like partition and fallthrough, you will have to flash the commands once again. It will completely restore your device to normal.
Press thanks if this helps.

ArtRahul said:
You just can flash the factory firmware (stock) and relock the bootloader using mfastboot v2. It will fix this, I had this problem two times and the process above got me out of it. Also if first flash gives errors like partition and fallthrough, you will have to flash the commands once again. It will completely restore your device to normal.
Press thanks if this helps.
Click to expand...
Click to collapse
Thanks for the reply
Ive been looking at fastboot/adb -I had tried flshing back to 4.4.4 using fastboot also tried recovery roms like twrm
I'm not really sure how to do what you describe above , I cant find the stock firmware....I need UK 4.4.4 -- the links i come across are always dead
iyou got a link?
thanks!

You don't need the files for UK. Files for any other country will also work. Here's a tool how to restore to 4.4.4, and there are the images for UK too, I just checked, the link is working. http://forum.xda-developers.com/showthread.php?t=2983295

mapito said:
Thanks for the reply
Ive been looking at fastboot/adb -I had tried flshing back to 4.4.4 using fastboot also tried recovery roms like twrm
I'm not really sure how to do what you describe above , I cant find the stock firmware....I need UK 4.4.4 -- the links i come across are always dead
iyou got a link?
thanks!
Click to expand...
Click to collapse
But why you want 4.4.4 firmware, haven't you yet updated it to 5.0.2??
And if you want the factory firmware image for stock 5.0.2, it's here -> https://drive.google.com/open?id=0Bzr0qvz6uRerOGRfOEptU2p0ZkU
and
also you'll first need to update your bootloader to lollipop then you're ready to go.

ArtRahul said:
But why you want 4.4.4 firmware, haven't you yet updated it to 5.0.2??
And if you want the factory firmware image for stock 5.0.2, it's here -> https://drive.google.com/open?id=0Bzr0qvz6uRerOGRfOEptU2p0ZkU
and
also you'll first need to update your bootloader to lollipop then you're ready to go.
Click to expand...
Click to collapse
I was on Lollipop yea, but I was havng issues as above so thought id downgrade
how do i update the bootloader?!
I'm a bit confused by what I'm reading everywhere
do I need to go back to 4,4,4 or stay on Lollipop?! and also why would i need to update the bootloader

mapito said:
I was on Lollipop yea, but I was havng issues as above so thought id downgrade
how do i update the bootloader?!
I'm a bit confused by what I'm reading everywhere
do I need to go back to 4,4,4 or stay on Lollipop?! and also why would i need to update the bootloader
Click to expand...
Click to collapse
any chance you could put that stock firmware somewhere else? EVERY time i try and dl off google drive it NEVER ever finishes gets near and then says download interrupted
I did try 4.4.4.
and i got the following;
MOTO G 2nd GEN Kitkat 4.4.4 FIRMWARE Flasher
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.360s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.045s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.130s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.370s]
writing 'boot'...
OKAY [ 0.235s]
finished. total time: 0.610s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.380s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 0.585s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257527 KB)...
OKAY [ 8.376s]
writing 'system'...
OKAY [ 4.691s]
finished. total time: 13.072s
target max-sparse-size: 256MB
sending 'system' (260629 KB)...
OKAY [ 8.502s]
writing 'system'...
OKAY [ 4.423s]
finished. total time: 12.931s
target max-sparse-size: 256MB
sending 'system' (255304 KB)...
OKAY [ 8.312s]
writing 'system'...
OKAY [ 4.786s]
finished. total time: 13.109s
target max-sparse-size: 256MB
sending 'system' (76792 KB)...
OKAY [ 2.531s]
writing 'system'...
OKAY [ 1.273s]
finished. total time: 3.804s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49252 KB)...
OKAY [ 1.641s]
writing 'modem'...
OKAY [ 0.827s]
finished. total time: 2.478s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.015s
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.015s
target max-sparse-size: 256MB
sending 'fsg' (650 KB)...
OKAY [ 0.095s]
writing 'fsg'...
OKAY [ 0.075s]
finished. total time: 0.170s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
DONE!.........PRESS ANY KEY TO REBOOT
which is because the firmware isnt suitable for the device?
also bootloader is 48.82 - thats ok? dont need to update it , right?

I just tried the easy installer for lollipop and while it looked like it had worked (see below)
it STILL stuck on the black creen after boot logos
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.028s]
finished. total time: 0.135s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
OKAY [ 0.310s]
finished. total time: 0.354s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.969s]
finished. total time: 1.088s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.051s]
finished. total time: 0.136s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.615s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.211s]
finished. total time: 0.625s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.879s]
writing 'system'...
OKAY [ 4.770s]
finished. total time: 17.575s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.729s]
writing 'system'...
OKAY [ 5.009s]
finished. total time: 13.750s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 9.289s]
writing 'system'...
OKAY [ 4.744s]
finished. total time: 14.039s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.650s]
writing 'system'...
OKAY [ 4.390s]
finished. total time: 13.044s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.126s]
writing 'system'...
OKAY [ 0.553s]
finished. total time: 1.687s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.738s]
writing 'modem'...
OKAY [ 0.835s]
finished. total time: 2.578s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.019s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.150s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.031s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.043s
DONE!.........PRESS ANY KEY TO REBOOT
rebooting...
finished. total time: 0.005s
Press any key to exit

mapito said:
I just tried the easy installer for lollipop and while it looked like it had worked (see below)
it STILL stuck on the black creen after boot logos
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.028s]
finished. total time: 0.135s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
OKAY [ 0.310s]
finished. total time: 0.354s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.969s]
finished. total time: 1.088s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.051s]
finished. total time: 0.136s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.615s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.211s]
finished. total time: 0.625s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.879s]
writing 'system'...
OKAY [ 4.770s]
finished. total time: 17.575s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.729s]
writing 'system'...
OKAY [ 5.009s]
finished. total time: 13.750s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 9.289s]
writing 'system'...
OKAY [ 4.744s]
finished. total time: 14.039s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.650s]
writing 'system'...
OKAY [ 4.390s]
finished. total time: 13.044s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.126s]
writing 'system'...
OKAY [ 0.553s]
finished. total time: 1.687s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.738s]
writing 'modem'...
OKAY [ 0.835s]
finished. total time: 2.578s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.019s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.150s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.031s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.043s
DONE!.........PRESS ANY KEY TO REBOOT
rebooting...
finished. total time: 0.005s
Press any key to exit
Click to expand...
Click to collapse
It's because your bootloader is updated and it cannot accept kitkat now and you will have to flash the 5.0.2 over this bootloader else you'll get these errors(black screen) again. Atlast what you need to do is to flash the stock 5.0.2 firmware via mfastboot v2 and you'll get back your device fully working.
These are the commands ->
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
And if the link I provided doesn't work then try searching for these two files
1. Motorola Moto G 2014 Stock 5.0.2 Factory Firmware
2. mfastboot v2
You can easily get that on XDA, after you download, just unzip the firmware file in the mfastboot's folder and then in cmd flash above commands.

ArtRahul said:
It's because your bootloader is updated and it cannot accept kitkat now and you will have to flash the 5.0.2 over this bootloader else you'll get these errors(black screen) again. Atlast what you need to do is to flash the stock 5.0.2 firmware via mfastboot v2 and you'll get back your device fully working.
These are the commands ->
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
And if the link I provided doesn't work then try searching for these two files
1. Motorola Moto G 2014 Stock 5.0.2 Factory Firmware
2. mfastboot v2
You can easily get that on XDA, after you download, just unzip the firmware file in the mfastboot's folder and then in cmd flash above commands.
Click to expand...
Click to collapse
hey thanks
so needs to be mfastboot2 not fastboot?
is there anyway to check exact version of android i had without being able to get in os..i ink it was 5.0.2

mapito said:
hey thanks
so needs to be mfastboot2 not fastboot?
is there anyway to check exact version of android i had without being able to get in os..i ink it was 5.0.2
Click to expand...
Click to collapse
If last time, on your phone, you used Lollipop, then it's 5.0.2 and if KitKat then it's 4.4.4, simple.
And you'll need mfastboot2

turns out the problem could be more than i thought..when i try to wipe user data/clear cache i get failed errors on the phone
..while it says the phone has been flashed successfully it never works
i guess this has something to do with the fact cant erase user data/clear cache
other people have had the same issues and no fix reported beyond getting a replacement

http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587/page4

mapito said:
turns out the problem could be more than i thought..when i try to wipe user data/clear cache i get failed errors on the phone
..while it says the phone has been flashed successfully it never works
i guess this has something to do with the fact cant erase user data/clear cache
other people have had the same issues and no fix reported beyond getting a replacement
Click to expand...
Click to collapse
what errors are you getting now...
are these (failed to validate system image/ fall-through from normal boot)??
If these are the errors you will have to re-flash the commands given above(as I told you in previous post).
I had same problem twice yet, and fixed by this process, so I can make you sure that you too should try again, and report the news here. I am here to help you.

Try using fastboot to boot philz cwm temporarily.
Fastboot boot Phil'srecovery.IMG
(or whatever its named)
Then use philz to format your partitions. Assuming twrp is installed already, Reboot to enter twrp. then use twrp to format partitions. Install ROM.
Sent from my Moto G 2014 using XDA Free mobile app

no TWR installed can i still use this recovery img or wont it work?

mapito said:
no TWR installed can i still use this recovery img or wont it work?
Click to expand...
Click to collapse
Install twrp recovery.
Sent from my Moto G 2014 using XDA Free mobile app

I cant mate, everytime I install it it says successfu;l but when i reboot its not there..I think there's a problem with the motherboard oe eeMC memory as when i try andwipe user data/cache it comes back saying failed
so I guess it cant write to the storage which is why i cant get TWRP to work
any ideas what to do here? fastboot says everythings worked..but clearly hasn't as cant get into TWRP or CWM even tried flashing stock sand nothing..but fastboot - w shows errors
reading on here people suggest its to do with the eeMC, itsa almost like the storage is set to read only

mapito said:
I cant mate, everytime I install it it says successfu;l but when i reboot its not there..I think there's a problem with the motherboard oe eeMC memory as when i try andwipe user data/cache it comes back saying failed
so I guess it cant write to the storage which is why i cant get TWRP to work
any ideas what to do here? fastboot says everythings worked..but clearly hasn't as cant get into TWRP or CWM even tried flashing stock sand nothing..but fastboot - w shows errors
reading on here people suggest its to do with the eeMC, itsa almost like the storage is set to read only
Click to expand...
Click to collapse
Did you try booting into philz with the command I gave you yet? Doesn't install, just boots the recovery image.
Sent from my Moto G 2014 using XDA Free mobile app

hey thanks for replyingI hadn't yet
I'll try that in a minute just grabbing the Philz recovery image
hope this works
thanks!

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

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.