Redmi K20/ Mi 9T Bricked? - Redmi K20 / Xiaomi Mi 9T Questions & Answers

So I was trying to rollback to stock rom from Pixel Experience since it was still buggy and not complete imo. So I tried flashing the stock Indian rom ( miui_DAVINCIININGlobal_V10.3.8.0.PFJINXM_207eaee662_9.0 ). But was stuck on boot screen. Although I could start fastboot mode. So I installed TWRP again & thought it must be a firmware issue & tried installing firmware from this post from Indian archive ( https://forum.xda-developers.com/mi-9t/development/firmware-xiaomi-mi-9t-redmi-k20-t3955314 ). But now I'm still stuck and cant possibly install twrp back. I tried flashing all the image files from the .tgz file as it had soled my earlier similar issue i had while installing twrp. But now while flashing dummy.img, dummy_devinfo.img, dummy_fsc.img, dummy_modemst.img, system.img & persist.img it shows an error in cmd. Which previously flashed successfully. And now I'm stuck with just the fastboot screen without any recovery. I also tried using MiFlash Tool but it ends up on Antirollback Check error although I have installed it in C:\MiFlash.
It'd be great if someone would help me out from here. TIA!
EDIT-
SOLVED!
Flash TWRP after manually flashing the files. To install persist incase you get an error like me saying persist is write protected/Unable to mount persist, try flashing persist.img from twrp in "Install Image". Might have to flash the rom again after that (I had to for some reason). Works fine then.

L:\K20 root\New folder (3)>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (131072 KB)...
OKAY [ 2.835s]
writing 'boot'...
OKAY [ 0.657s]
finished. total time: 3.492s
L:\K20 root\New folder (3)>fastboot flash cache cache.img
target reported max download size of 805306368 bytes
erasing 'cache'...
OKAY [ 0.016s]
sending 'cache' (128 KB)...
OKAY [ 0.015s]
writing 'cache'...
OKAY [ -0.000s]
finished. total time: 0.031s
L:\K20 root\New folder (3)>fastboot flash cust cust.img
target reported max download size of 805306368 bytes
sending 'cust' (213156 KB)...
OKAY [ 4.618s]
writing 'cust'...
OKAY [ 0.000s]
finished. total time: 4.618s
L:\K20 root\New folder (3)>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (32768 KB)...
OKAY [ 0.704s]
writing 'dtbo'...
OKAY [ 0.157s]
finished. total time: 0.861s
L:\K20 root\New folder (3)>fastboot flash dummy dummy.img
target reported max download size of 805306368 bytes
sending 'dummy' (8 KB)...
OKAY [ 0.000s]
writing 'dummy'...
FAILED (remote: (dummy) No such partition)
finished. total time: 0.000s
L:\K20 root\New folder (3)>fastboot flash dummy_devinf dummy_devinfo.img
target reported max download size of 805306368 bytes
sending 'dummy_devinf' (4 KB)...
OKAY [ 0.016s]
writing 'dummy_devinf'...
FAILED (remote: (dummy_devinf) No such partition)
finished. total time: 0.016s
L:\K20 root\New folder (3)>fastboot flash dummy_fsc dummy_fsc.img
target reported max download size of 805306368 bytes
sending 'dummy_fsc' (4 KB)...
OKAY [ 0.016s]
writing 'dummy_fsc'...
FAILED (remote: (dummy_fsc) No such partition)
finished. total time: 0.016s
L:\K20 root\New folder (3)>fastboot flash dummy_modemst dummy_modemst.img
target reported max download size of 805306368 bytes
sending 'dummy_modemst' (8192 KB)...
OKAY [ 0.188s]
writing 'dummy_modemst'...
FAILED (remote: (dummy_modemst) No such partition)
finished. total time: 0.188s
L:\K20 root\New folder (3)>fastboot flash logo logo.img
target reported max download size of 805306368 bytes
sending 'logo' (26980 KB)...
OKAY [ 0.588s]
writing 'logo'...
OKAY [ 0.144s]
finished. total time: 0.733s
L:\K20 root\New folder (3)>fastboot flash misc misc.img
target reported max download size of 805306368 bytes
sending 'misc' (4096 KB)...
OKAY [ 0.094s]
writing 'misc'...
OKAY [ 0.031s]
finished. total time: 0.125s
L:\K20 root\New folder (3)>fastboot flash persist persist.img
target reported max download size of 805306368 bytes
sending 'persist' (65536 KB)...
OKAY [ 1.406s]
writing 'persist'...
FAILED (remote: Partition is write protected)
finished. total time: 1.421s
L:\K20 root\New folder (3)>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.421s]
writing 'recovery'...
OKAY [ 0.336s]
finished. total time: 1.757s
L:\K20 root\New folder (3)>fastboot flash system system.img
error: cannot load 'system.img'
L:\K20 root\New folder (3)>fastboot flash userdata userdata.img
target reported max download size of 805306368 bytes
sending 'userdata' (198244 KB)...
OKAY [ 4.278s]
writing 'userdata'...
OKAY [ 0.000s]
finished. total time: 4.278s
L:\K20 root\New folder (3)>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.016s]
writing 'vbmeta'...
OKAY [ 0.000s]
finished. total time: 0.016s
L:\K20 root\New folder (3)>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
sending sparse 'vendor' (786428 KB)...
OKAY [ 18.024s]
writing 'vendor'...
OKAY [ -0.000s]
sending sparse 'vendor' (558016 KB)...
OKAY [ 13.004s]
writing 'vendor'...
OKAY [ -0.000s]
finished. total time: 31.043s

There is probably problem with the official ROM. I have managed to get to the same situation with EU version. I have tried some beta and end up with barely working twrp. Sideload didn't work etc.
So I bought USB-C flash disk and instaled custom ROM LineageOS and everything is working fine so far.
Non of the official ROM have worked, so for some time I will have to function LineageOS and wait for some properly working recovery and ROM...

Reep1324 said:
There is probably problem with the official ROM. I have managed to get to the same situation with EU version. I have tried some beta and end up with barely working twrp. Sideload didn't work etc.
So I bought USB-C flash disk and instaled custom ROM LineageOS and everything is working fine so far.
Non of the official ROM have worked, so for some time I will have to function LineageOS and wait for some properly working recovery and ROM...
Click to expand...
Click to collapse
Do u get an error saying "Failed to mount '/persist' (Invalid Argument)?

No. Everything looks ok, but then I got Bootloop or it goes straight to Recovery. Using the russian and greek one. Oficial ROM, EU rom and Lineage. Nothing works now...

Have you tried flashing magisk? Had the same problem where I couldn't launch official rom (I was coming back from xiaomi.eu). Flashing magisk in TWRP resolved the problem. You can OTA after that to get back to stock rom (as without TWRP or magisk).

nega_tive said:
So I was trying to rollback to stock rom from Pixel Experience since it was still buggy and not complete imo. So I tried flashing the stock Indian rom ( miui_DAVINCIININGlobal_V10.3.8.0.PFJINXM_207eaee662_9.0 ). But was stuck on boot screen. Although I could start fastboot mode. So I installed TWRP again & thought it must be a firmware issue & tried installing firmware from this post from Indian archive ( https://forum.xda-developers.com/mi-9t/development/firmware-xiaomi-mi-9t-redmi-k20-t3955314 ). But now I'm still stuck and cant possibly install twrp back. I tried flashing all the image files from the .tgz file as it had soled my earlier similar issue i had while installing twrp. But now while flashing dummy.img, dummy_devinfo.img, dummy_fsc.img, dummy_modemst.img, system.img & persist.img it shows an error in cmd. Which previously flashed successfully. And now I'm stuck with just the fastboot screen without any recovery. I also tried using MiFlash Tool but it ends up on Antirollback Check error although I have installed it in C:\MiFlash.
It'd be great if someone would help me out from here. TIA!
EDIT-
SOLVED!
Flash TWRP after manually flashing the files. To install persist incase you get an error like me saying persist is write protected/Unable to mount persist, try flashing persist.img from twrp in "Install Image". Might have to flash the rom again after that (I had to for some reason). Works fine then.
Click to expand...
Click to collapse
Hi,
I cant boot in to stock Indian ROM. But, i was able to flash 10.3.9 global.I have tried ll methods. flash tool, recovery nothing works. Everytime i do something it will break on to bootloop, cant get the stock indian ROM back. Always come back to global stable.

Matthas said:
Have you tried flashing magisk? Had the same problem where I couldn't launch official rom (I was coming back from xiaomi.eu). Flashing magisk in TWRP resolved the problem. You can OTA after that to get back to stock rom (as without TWRP or magisk).
Click to expand...
Click to collapse
It's already solved. And yes, I have tried all combinations possible.
In the end I have decompressed .tgz file (6,5GB) and flash it thru 2017 version of MiFlasher.

Related

Unable to mount storage, Internal memory 0

First noticed encryption failed on A6000 Plus. After that it's not booting up only stuck on boot logo/splash screen. Tried several way using fastboot rom, QFIL. Looking for help.
Last fastboot status:
Code:
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash partition gpt_bo
th0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.006s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.043s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash tz tz.mbn
target reported max download size of 268435456 bytes
sending 'tz' (399 KB)...
OKAY [ 0.018s]
writing 'tz'...
OKAY [ 0.011s]
finished. total time: 0.029s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash sbl1 sbl1.mbn
target reported max download size of 268435456 bytes
sending 'sbl1' (246 KB)...
OKAY [ 0.012s]
writing 'sbl1'...
OKAY [ 0.010s]
finished. total time: 0.022s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash rpm rpm.mbn
target reported max download size of 268435456 bytes
sending 'rpm' (145 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.009s]
finished. total time: 0.018s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash aboot emmc_appsb
oot.mbn
target reported max download size of 268435456 bytes
sending 'aboot' (419 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.012s]
finished. total time: 0.033s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot erase boot
erasing 'boot'...
OKAY [ 0.033s]
finished. total time: 0.033s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash modem NON-HLOS.b
in
target reported max download size of 268435456 bytes
sending 'modem' (45681 KB)...
OKAY [ 1.742s]
writing 'modem'...
OKAY [ 0.521s]
finished. total time: 2.265s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash system system.im
g
error: cannot open 'system.img'
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash cache cache.img
error: cannot open 'cache.img'
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash userdata userdat
a.img
error: cannot open 'userdata.img'
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash recovery recover
y.img
target reported max download size of 268435456 bytes
sending 'recovery' (10130 KB)...
OKAY [ 0.392s]
writing 'recovery'...
OKAY [ 0.122s]
finished. total time: 0.515s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (9576 KB)...
OKAY [ 0.364s]
writing 'boot'...
OKAY [ 0.115s]
finished. total time: 0.480s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash persist persist.
img
error: cannot open 'persist.img'
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash sec sec.dat
target reported max download size of 268435456 bytes
sending 'sec' (0 KB)...
OKAY [ 0.005s]
writing 'sec'...
FAILED (remote: flash write failure)
finished. total time: 0.026s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>fastboot flash splash splash.im
g
target reported max download size of 268435456 bytes
sending 'splash' (5401 KB)...
OKAY [ 0.209s]
writing 'splash'...
OKAY [ 0.068s]
finished. total time: 0.278s
C:\adb\Lenovo_A6000_S035_150507_8G_ROW\Firmware>
install twrp by pc
Install twrp as per your KitKat or lolipop version after wipe data cache and system and flash lolipop lenovo a6000 plus stock rom.if not flash than extract zip and only flash system folder and India it's as per your country.if also not start than only one solution flash stock rom by pc.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Please give full information regarding your problem.i am not any dev but I know some type of errors which I have faced.
lathiyamayur789 said:
Install twrp as per your KitKat or lolipop version after wipe data cache and system and flash lolipop lenovo a6000 plus stock rom.if not flash than extract zip and only flash system folder and India it's as per your country.if also not start than only one solution flash stock rom by pc.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Please give full information regarding your problem.i am not any dev but I know some type of errors which I have faced.
Click to expand...
Click to collapse
Phone is dead as of now, only fastboot mode and boot recovery thorugh fastboot are working.
unbrick method follow
Unbrick device method use.
lathiyamayur789 said:
Unbrick device method use.
Click to expand...
Click to collapse
Explain please
Anyone there to here?

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

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

What about friends, it happens that I wanted to install TWRP to my OP6T, but it did not go well ... I followed the steps and when I gave "Reboot Recovery", I entered the fastboot mode, and it did not happen there, it did not allow me to flash the rom, the stock recovery, or the TWRP, tells me the following ...
This happens when wanting to boot the twrp.img:
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
PS C:\Users\vhr07\Desktop>
--------------------------------------------------------------------------------------------
This happens when you want to install the recovery stock:
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.518s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.536s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
I install the recovery by means of "boot" and it says OK, but when wanting to boot I get error:
PS C:\Users\vhr07\Desktop> fastboot flash boot recovery.img
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.518s]
writing 'boot'...
OKAY [ 0.271s]
finished. total time: 1.794s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.506s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.547s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
These were my last attempts ...:
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (30948 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.734s
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.508s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.525s
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16849 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.406s
PS C:\Users\vhr07\Desktop> fastboot flash recovery_b recovery.img
target reported max download size of 536870912 bytes
sending 'recovery_b' (65536 KB)...
OKAY [ 1.523s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 1.538s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b recovery.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.517s]
writing 'boot_b'...
OKAY [ 0.301s]
finished. total time: 1.824s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.511s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.549s
PS C:\Users\vhr07\Desktop> fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot' (30948 KB)...
OKAY [ 0.714s]
writing 'boot'...
OKAY [ 0.154s]
finished. total time: 0.874s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30948 KB)...
OKAY [ 0.717s]
writing 'boot_b'...
OKAY [ 0.181s]
finished. total time: 0.904s
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.716s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
----------------------------------------------------------------------------
Please, I need your help I promise not to ROOT again the hahaha team
I would pay if necessary
PD: already tried with bootloader unlocked and blocked
UPDATE: MSMTools, stuck on "PARAM PREPROCESSING"
https://imgur.com/qiaF8oh
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
foobar66 said:
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
Click to expand...
Click to collapse
Same situation
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.500s]
writing 'boot_a'...
OKAY [ 0.308s]
finished. total time: 1.814s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.498s]
writing 'boot_b'...
OKAY [ 0.345s]
finished. total time: 1.849s
PS C:\Users\vhr07\Desktop> fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.505s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.537s
PS C:\Users\vhr07\Desktop>
Seem look like usb debug not authorize pc
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
efebe said:
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
Click to expand...
Click to collapse
MSMTools stuck on this
https://imgur.com/qiaF8oh
Vlodayax said:
MSMTools stuck on this
https://imgur.com/qiaF8oh
Click to expand...
Click to collapse
Click "stop" then "exit" and kill the program and start over. Keep trying. I was down a whole day and a half after trying to flash a Rom. I made it worst after wiping the system and the MSM tool saved my a$$.
Sent from my OnePlus6T using XDA Labs

Unlocked bootloader Phone stuck in bootloop

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"?

i need help (my phone smells softbrick or hardbrick and have bootloop) I have a p8 lite 2015 (ALE-L23)

This phone have probably softbrick or hardbrick and bootloop and intro to recovery (no erecovery) gets a rescue mode screen
I have tried with the "potatonv" tool and trying to flash a stock rom and a custom recovery but none work and I have the bootloader unlocked but I get these following results:
>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 471859200 bytes
sending 'RECOVERY' (36118 KB)...
OKAY [ 0.986s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 1.012s
>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (36118 KB)...
OKAY [ 1.000s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.468s

Categories

Resources