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.
Related
I have a razr m. It came with stock JB. I safestrapped it. I later had an issue so i tried to fastboot it using DROID_RAZR_M_Utility1.10. It worked but then i got an error in fastboot. I tried RSD. I get an error failed flashing process. 1/19 flash partition "gpt_main0.bin" -> PHONE returned FAIL. When using the razr m utility i get "writing 'system'... INFOProtocol error (multiflash unexpected).
mamismo said:
I have a razr m. It came with stock JB. I safestrapped it. I later had an issue so i tried to fastboot it using DROID_RAZR_M_Utility1.10. It worked but then i got an error in fastboot. I tried RSD. I get an error failed flashing process. 1/19 flash partition "gpt_main0.bin" -> PHONE returned FAIL. When using the razr m utility i get "writing 'system'... INFOProtocol error (multiflash unexpected).
Click to expand...
Click to collapse
Any help? stuck in the same situation
bootloader is unblocked?
U have to decompress first with rsd and then extract happened to me but u r gonna need the fast boot files
Sent from my XT907 using xda app-developers app
Yep, if you can't get the utility to work, do through RSD itself. I've used the Utility three times in the last week, and have had no problems. Not sure why you're having issues.
i found a solution - my fastboot was outdated. This created a requirement for the windows version of the Razr M utility. RSD never worked for me
mamismo said:
i found a solution - my fastboot was outdated. This created a requirement for the windows version of the Razr M utility. RSD never worked for me
Click to expand...
Click to collapse
hi, can you tell me how you fixed this problem, im getting the error in rsd and when i use matt's razr m utility.
i cd'ed into the utility folder and ran the utility. If that doesn't work you can try opening the fastboot update file and manually sending the commands through fastboot.
mamismo said:
i cd'ed into the utility folder and ran the utility. If that doesn't work you can try opening the fastboot update file and manually sending the commands through fastboot.
Click to expand...
Click to collapse
I'm when you say cd'ed, u mean open the windowsutility.bat using a cmd prompt? i did that and im still geting preflash verication failure at the end of the process and the same gpt_main0.bin error on the phone.
sirccchar said:
I'm when you say cd'ed, u mean open the windowsutility.bat using a cmd prompt? i did that and im still geting preflash verication failure at the end of the process and the same gpt_main0.bin error on the phone.
Click to expand...
Click to collapse
From what I understand, you can edit the XML file inside the zip file and remove the line with got_main0.bin. Save it and it should install. No guarantees, that's just what I read.
Sent from my XT907 using xda premium
netizenmt said:
From what I understand, you can edit the XML file inside the zip file and remove the line with got_main0.bin. Save it and it should install. No guarantees, that's just what I read.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
i did that and it still gets the failure and same result, it reboots and i see the red M and it just goes black. a lil bit more info, I was getting fail on the maintance update, so i tried rebloated my phone, and it was still failing, so i did a restore using twrp from a backup, but the camera was force closing, so i did a system wipe using twrp and now i think i'm bricked. safe strap shows up but is disabled and gets no input. anyone can help?
Try manually flashing everything based on the files in the XML file and see where you get an error. Use the fastboot flash and erase commands based on lines in the XML file
mamismo said:
Try manually flashing everything based on the files in the XML file and see where you get an error. Use the fastboot flash and erase commands based on lines in the XML file
Click to expand...
Click to collapse
so i did that using the following lines, phone reboots to the red M and blacks out, according to this site, i think im brick??? http://teamuscellular.com/Forum/topic/3916-electrify-m-cannot-downgrade-via-rsd-lite/ ((
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash devtree device_tree.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
fastboot continue
from here
http://forum.xda-developers.com/showthread.php?t=2172537
and i get
E:\DROID_RAZR_M_Utility1.10>fastboot flash partition gpt_main0.bin
sending 'partition' (32 KB)...
OKAY [ 0.076s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.344s
E:\DROID_RAZR_M_Utility1.10>fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (100 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.514s]
finished. total time: 0.534s
E:\DROID_RAZR_M_Utility1.10>fastboot flash sbl2 sbl2.mbn
sending 'sbl2' (126 KB)...
OKAY [ 0.020s]
writing 'sbl2'...
OKAY [ 1.079s]
finished. total time: 1.099s
E:\DROID_RAZR_M_Utility1.10>fastboot flash sbl3 sbl3.mbn
sending 'sbl3' (512 KB)...
OKAY [ 0.050s]
writing 'sbl3'...
OKAY [ 1.074s]
finished. total time: 1.125s
E:\DROID_RAZR_M_Utility1.10>fastboot flash rpm rpm.mbn
sending 'rpm' (140 KB)...
OKAY [ 0.021s]
writing 'rpm'...
OKAY [ 0.495s]
finished. total time: 0.516s
E:\DROID_RAZR_M_Utility1.10>fastboot flash tz tz.mbn
sending 'tz' (192 KB)...
OKAY [ 0.025s]
writing 'tz'...
OKAY [ 1.091s]
finished. total time: 1.125s
E:\DROID_RAZR_M_Utility1.10>fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (256 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 1.612s]
finished. total time: 1.652s
E:\DROID_RAZR_M_Utility1.10>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.014s
E:\DROID_RAZR_M_Utility1.10>
E:\DROID_RAZR_M_Utility1.10>fastboot flash modem NON-HLOS.bin
< waiting for device >
sending 'modem' (30720 KB)...
OKAY [ 2.374s]
writing 'modem'...
OKAY [ 1.426s]
sending 'modem' (17576 KB)...
OKAY [ 5.200s]
writing 'modem'...
OKAY [ 2.447s]
finished. total time: 11.468s
E:\DROID_RAZR_M_Utility1.10>fastboot flash fsg fsg.mbn
sending 'fsg' (2794 KB)...
OKAY [ 0.226s]
writing 'fsg'...
OKAY [ 2.066s]
finished. total time: 2.302s
E:\DROID_RAZR_M_Utility1.10>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.838s]
finished. total time: 0.843s
E:\DROID_RAZR_M_Utility1.10>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 1.248s]
finished. total time: 1.254s
E:\DROID_RAZR_M_Utility1.10>fastboot flash logo logo.bin
error: cannot load 'logo.bin'
E:\DROID_RAZR_M_Utility1.10>fastboot flash devtree device_tree.bin
sending 'devtree' (512 KB)...
OKAY [ 0.050s]
writing 'devtree'...
OKAY [ 0.553s]
finished. total time: 0.613s
E:\DROID_RAZR_M_Utility1.10>fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.799s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.084s
E:\DROID_RAZR_M_Utility1.10>fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.799s]
writing 'recovery'...
OKAY [ 5.358s]
finished. total time: 6.167s
E:\DROID_RAZR_M_Utility1.10>fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.444s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.761s
E:\DROID_RAZR_M_Utility1.10>fastboot flash cdrom cdrom
error: cannot load 'cdrom'
E:\DROID_RAZR_M_Utility1.10>fastboot erase tombstones
erasing 'tombstones'...
OKAY [ 1.371s]
finished. total time: 1.377s
E:\DROID_RAZR_M_Utility1.10>fastboot erase cache
erasing 'cache'...
OKAY [ 1.655s]
finished. total time: 1.661s
E:\DROID_RAZR_M_Utility1.10>fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.102s]
finished. total time: 3.102s
E:\DROID_RAZR_M_Utility1.10> fastboot continue
resuming boot...
OKAY [ 0.010s]
finished. total time: 0.015s
sirccchar said:
so i did that using the following lines, phone reboots to the red M and blacks out, according to this site, i think im brick??? http://teamuscellular.com/Forum/topic/3916-electrify-m-cannot-downgrade-via-rsd-lite/ ((
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash devtree device_tree.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
fastboot continue
from here
http://forum.xda-developers.com/showthread.php?t=2172537
and i get
E:\DROID_RAZR_M_Utility1.10>fastboot flash partition gpt_main0.bin
sending 'partition' (32 KB)...
OKAY [ 0.076s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.344s
E:\DROID_RAZR_M_Utility1.10>fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (100 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.514s]
finished. total time: 0.534s
E:\DROID_RAZR_M_Utility1.10>fastboot flash sbl2 sbl2.mbn
sending 'sbl2' (126 KB)...
OKAY [ 0.020s]
writing 'sbl2'...
OKAY [ 1.079s]
finished. total time: 1.099s
E:\DROID_RAZR_M_Utility1.10>fastboot flash sbl3 sbl3.mbn
sending 'sbl3' (512 KB)...
OKAY [ 0.050s]
writing 'sbl3'...
OKAY [ 1.074s]
finished. total time: 1.125s
E:\DROID_RAZR_M_Utility1.10>fastboot flash rpm rpm.mbn
sending 'rpm' (140 KB)...
OKAY [ 0.021s]
writing 'rpm'...
OKAY [ 0.495s]
finished. total time: 0.516s
E:\DROID_RAZR_M_Utility1.10>fastboot flash tz tz.mbn
sending 'tz' (192 KB)...
OKAY [ 0.025s]
writing 'tz'...
OKAY [ 1.091s]
finished. total time: 1.125s
E:\DROID_RAZR_M_Utility1.10>fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (256 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 1.612s]
finished. total time: 1.652s
E:\DROID_RAZR_M_Utility1.10>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.014s
E:\DROID_RAZR_M_Utility1.10>
E:\DROID_RAZR_M_Utility1.10>fastboot flash modem NON-HLOS.bin
< waiting for device >
sending 'modem' (30720 KB)...
OKAY [ 2.374s]
writing 'modem'...
OKAY [ 1.426s]
sending 'modem' (17576 KB)...
OKAY [ 5.200s]
writing 'modem'...
OKAY [ 2.447s]
finished. total time: 11.468s
E:\DROID_RAZR_M_Utility1.10>fastboot flash fsg fsg.mbn
sending 'fsg' (2794 KB)...
OKAY [ 0.226s]
writing 'fsg'...
OKAY [ 2.066s]
finished. total time: 2.302s
E:\DROID_RAZR_M_Utility1.10>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.838s]
finished. total time: 0.843s
E:\DROID_RAZR_M_Utility1.10>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 1.248s]
finished. total time: 1.254s
E:\DROID_RAZR_M_Utility1.10>fastboot flash logo logo.bin
error: cannot load 'logo.bin'
E:\DROID_RAZR_M_Utility1.10>fastboot flash devtree device_tree.bin
sending 'devtree' (512 KB)...
OKAY [ 0.050s]
writing 'devtree'...
OKAY [ 0.553s]
finished. total time: 0.613s
E:\DROID_RAZR_M_Utility1.10>fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.799s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.084s
E:\DROID_RAZR_M_Utility1.10>fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.799s]
writing 'recovery'...
OKAY [ 5.358s]
finished. total time: 6.167s
E:\DROID_RAZR_M_Utility1.10>fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.444s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.761s
E:\DROID_RAZR_M_Utility1.10>fastboot flash cdrom cdrom
error: cannot load 'cdrom'
E:\DROID_RAZR_M_Utility1.10>fastboot erase tombstones
erasing 'tombstones'...
OKAY [ 1.371s]
finished. total time: 1.377s
E:\DROID_RAZR_M_Utility1.10>fastboot erase cache
erasing 'cache'...
OKAY [ 1.655s]
finished. total time: 1.661s
E:\DROID_RAZR_M_Utility1.10>fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.102s]
finished. total time: 3.102s
E:\DROID_RAZR_M_Utility1.10> fastboot continue
resuming boot...
OKAY [ 0.010s]
finished. total time: 0.015s
Click to expand...
Click to collapse
im having the same issue bricked and cannot boot and bootloader is locked:crying:
What OS are you using on your computer to run the utility? Are you using the Motorola charging/usb cable? Have you tried a different USB port on your computer? Is your battery charged.
RikRong said:
What OS are you using on your computer to run the utility? Are you using the Motorola charging/usb cable? Have you tried a different USB port on your computer? Is your battery charged.
Click to expand...
Click to collapse
i tried on 2 different computers and battery was fully charged
one comp running windows 7 one running windows vista
bigrob1015 said:
i tried on 2 different computers and battery was fully charged
one comp running windows 7 one running windows vista
Click to expand...
Click to collapse
I also tried it on a couple of PCs, with different cables, changing the xml, everything i could find to do. are we dead in the water? does this phone have a year warranty? the safe strap screen is still coming out, will that make the phone out of warranty?
sirccchar said:
I also tried it on a couple of PCs, with different cables, changing the xml, everything i could find to do. are we dead in the water? does this phone have a year warranty? the safe strap screen is still coming out, will that make the phone out of warranty?
Click to expand...
Click to collapse
matt has a new utility out for 4.1.2 and a new set of tools I just used it and it works flawlessly!!!!! no longer bricked
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
look for his post with the new utility
sirccchar said:
I'm when you say cd'ed, u mean open the windowsutility.bat using a cmd prompt? i did that and im still geting preflash verication failure at the end of the process and the same gpt_main0.bin error on the phone.
Click to expand...
Click to collapse
maybe your download file is corrupted ，try download it again , the toolbox should work under cmd mode, it's better than RSD
way.
hey guys. just wanted to come here to say that i had previously soft-bricked my 907, and using RSDlite in conjunction with the pertinent files from matt's utility (seems to need to be 1.20 ; 1.10 absolutely did not work) got my handset working again in like 10 minutes. additional details available on request, but essentially it was a matter of having the phone turned on in AP fastboot mode, plugged into a USB port, at roughly 90% power, and clicking "start" in RSD lite 6.14. JB 4.1.2 stock (i used the fb files from matt's 1.20 file, haven't really investigated whether or not this is a crucial detail). i was dealing with a totally useless phone during the moments leading up to this process having worked.
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
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
I successfully unlocked my bootloader last night. I went through the process of patching the img file through magisk to root and flashed it via fastbooot. I have been stuck in a loop since. I can still get into fastboot. I have tried Smart Assistant and RSD but they wont detect my phone.
I tried a using different firmware as others have posted and i'm still stuck.
here is my process on powershell:
PS C:\Android> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.002s]
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.092s]
finished. total time: 0.095s
PS C:\Android> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.179s]
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_30.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64_30.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster64.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.317s]
finished. total time: 0.497s
PS C:\Android> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Android> fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (65900 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 0.512s]
finished. total time: 2.040s
PS C:\Android> fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (11612 KB)...
OKAY [ 0.270s]
writing 'fsg'...
OKAY [ 0.089s]
finished. total time: 0.361s
PS C:\Android> fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android> fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.016s
PS C:\Android> fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin'
PS C:\Android> fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin'
PS C:\Android> fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin'
PS C:\Android> fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.380s]
writing 'dsp'...
OKAY [ 0.104s]
finished. total time: 0.486s
PS C:\Android> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2633 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.044s]
finished. total time: 0.107s
PS C:\Android> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.789s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.641s]
finished. total time: 1.431s
PS C:\Android> fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (256852 KB)...
OKAY [ 5.933s]
writing 'system'...
OKAY [ 1.093s]
finished. total time: 7.028s
PS C:\Android> fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
OKAY [ 6.062s]
writing 'system'...
OKAY [ 1.102s]
finished. total time: 7.166s
PS C:\Android> fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (234600 KB)...
OKAY [ 5.424s]
writing 'system'...
OKAY [ 0.955s]
finished. total time: 6.379s
PS C:\Android> fastboot flash system system.img_sparsechunk.3 target reported max download size of 536870912 bytes
sending 'system' (259529 KB)...
OKAY [ 5.998s]
writing 'system'...
OKAY [ 1.075s]
finished. total time: 7.075s
PS C:\Android> fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
OKAY [ 6.061s]
writing 'system'...
OKAY [ 1.114s]
finished. total time: 7.177s
PS C:\Android> fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (252895 KB)...
OKAY [ 5.852s]
writing 'system'...
OKAY [ 1.144s]
finished. total time: 6.997s
PS C:\Android> fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 6.070s]
writing 'system'...
OKAY [ 1.092s]
finished. total time: 7.163s
PS C:\Android> fastboot flash system system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system' (260863 KB)...
OKAY [ 6.071s]
writing 'system'...
OKAY [ 1.883s]
finished. total time: 7.955s
PS C:\Android> fastboot flash system_b system_other.img
error: cannot load 'system_other.img'
PS C:\Android> fastboot flash oem oem_other.img
target reported max download size of 536870912 bytes
sending 'oem' (43696 KB)...
OKAY [ 1.012s]
writing 'oem'...
OKAY [ 0.219s]
finished. total time: 1.233s
PS C:\Android> fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (68308 KB)...
OKAY [ 1.584s]
writing 'oem'...
OKAY [ 0.300s]
finished. total time: 1.887s
PS C:\Android> fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.032s]
finished. total time: 0.033s
PS C:\Android> fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.082s]
finished. total time: 0.083s
PS C:\Android> fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
PS C:\Android> fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
PS C:\Android> fastboot reboot
rebooting...
finished. total time: 0.001s
You need to wipe everything with fastboot commands. Then flash stock again. Also there's no need to do any of that anymore to get root. Just flash the latest magisk in TWRP next time.
Phalanx7621 said:
You need to wipe everything with fastboot commands. Then flash stock again. Also there's no need to do any of that anymore to get root. Just flash the latest magisk in TWRP next time.
Click to expand...
Click to collapse
Thank you for the reply
Should "Fastboot erase" wipe it all out?
do you know where I can the correct stock room for XT1962-1?
Sent from my SM-N975U using Tapatalk
Extract all files from stock zip and run flashall.bat file at command prompt with phone connected in bootloader mode. This will flash and erase all to correct retail stock at Lolinet mirror
https://mirrors.lolinet.com/firmware/moto/river/official/RETAIL/
Flashall.bat file
Extract into adb folder (same as all files in stock zip file)
HueyT said:
Extract into adb folder (same as all files in stock zip file)
Click to expand...
Click to collapse
Thank you for your help!! I'll let you know how it goes
Sent from my SM-N975U using Tapatalk
HueyT said:
Extract into adb folder (same as all files in stock zip file)
Click to expand...
Click to collapse
Update: I'm back up and running! I really appreciate the help! my bootloader is still unlocked, what is the best way to root this device?
dnsource said:
Update: I'm back up and running! I really appreciate the help! my bootloader is still unlocked, what is the best way to root this device?
Click to expand...
Click to collapse
Install TWRP and then flash Magisk 20.2 and Magisk Manager APK
While patching the boot.img for your first installation, did you choose "Preserve force encryption" in "Advanced Settings"?
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
dladz said:
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
Click to expand...
Click to collapse
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
reppinrengar said:
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
Click to expand...
Click to collapse
You don't flash using fastboot just stick with the installer.bat file, it's in the ROM zip
If that doesn't work then your system is borked, in which case like I said just use the MSM tool.
You're done in several steps.
You should never need to unlock critical
reppinrengar said:
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
Click to expand...
Click to collapse
Use the original OnePlus cable.