So I'm pretty much a noob when it comes to flashing custom ROM's and such stuff, and always follow written tutorials where available.
Yesterday I managed to flash Revolution OS to my Mi 9 (with unlocked Bootloader) and using Twrp it worked perfectly.
Now today I tried to reset the device due to some Issues, and I must've accidentally deleted the ROM itself somehow, because now the phone just Bootloops all the time.
Recovery is not accessible, or I'm unsure if there is even a recovery still on it, but I can access fastboot.
I tried different commands like flashing ROM to the device via Fastboot or Mi Flash tool, but it either fails with unknown error or it doesn't progress the command.
So I wanted to ask, if there is any hope for my Mi 9 or if I just made a expensive mistake.
Any answers, tips and possible solutions are appreciated, thank you!
Goatfreak99 said:
So I'm pretty much a noob when it comes to flashing custom ROM's and such stuff, and always follow written tutorials where available.
Yesterday I managed to flash Revolution OS to my Mi 9 (with unlocked Bootloader) and using Twrp it worked perfectly.
Now today I tried to reset the device due to some Issues, and I must've accidentally deleted the ROM itself somehow, because now the phone just Bootloops all the time.
Recovery is not accessible, or I'm unsure if there is even a recovery still on it, but I can access fastboot.
I tried different commands like flashing ROM to the device via Fastboot or Mi Flash tool, but it either fails with unknown error or it doesn't progress the command.
So I wanted to ask, if there is any hope for my Mi 9 or if I just made a expensive mistake.
Any answers, tips and possible solutions are appreciated, thank you!
Click to expand...
Click to collapse
Did you've tried to flash system (download an unzip your first miui rom e.g. Global, eu...) and twrp via adb?
For me it was fine in a same situation.
You can download the fastboot ROM from xiaomi side, extract following from tgz file
-boot
-recovery
-vendor
-system
And flash it manually via fastboot. Welcome back to Miui world....
Laptapper said:
Did you've tried to flash system (download an unzip your first miui rom e.g. Global, eu...) and twrp via adb?
For me it was fine in a same situation.
Click to expand...
Click to collapse
Hey thank you very much for your reply.
I was able to flash TWRP via Fastboot but when entering the command fastboot boot recovery.img it still bootlooped again and I still couldn't acess Recovery through button combination.
Is there anything I might be doing wrong or so?
The only option you have now is to flash the full rom via fastboot
gogoffm said:
You can download the fastboot ROM from xiaomi side, extract following from tgz file
-boot
-recovery
-vendor
-system
And flash it manually via fastboot. Welcome back to Miui world....
Click to expand...
Click to collapse
Just spend the last couple hours following your advice, but I still get abootloop and no recovery option on the phone itself.
Flashing all the parts worked but it seems like it's not really applying them?
I used the stock cepherus ROM
Puhh, then I am really don't know. This method always worked for me. Can you make a sc of the fastboot commands you are using to flash the files ?
Goatfreak99 said:
Just spend the last couple hours following your advice, but I still get abootloop and no recovery option on the phone itself.
Flashing all the parts worked but it seems like it's not really applying them?
I used the stock cepherus ROM
Click to expand...
Click to collapse
And which twrp?
- Download XiaomiADBFastbootTools.
- Connect through Fastboot
- Download a stable official rom via the program
- Flash the Rom via the program
- Voila, you're back on stock
Laptapper said:
And which twrp?
Click to expand...
Click to collapse
for TWRP I use Twrp_3.3.0_Cepheus.
KaiseRRUby said:
- Download XiaomiADBFastbootTools.
- Connect through Fastboot
- Download a stable official rom via the program
- Flash the Rom via the program
- Voila, you're back on stock
Click to expand...
Click to collapse
Thank you for the reply, I've downloaded that program and aam currently tring to flash the official global developer ROM with it.
Last log however is :
C:\Users\\xaft_tmp>fastboot getvar product 2>&1 | findstr /r /c:"^product: *cepheus" || echo Missmatching image and device
Is that supposed to be like that, or do I need a different ROM?
I have the Mi 9 Global Version if that's of use
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>set CURRENT_ANTI_VER=1
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>(set version=1 )
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>if [1] EQU [] set version=0
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>set anticheck="antirollback check pass"
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot getvar product 2>&1 | findstr /r /c:"^product: *cepheus" || echo Missmatching image and device
Missmatching image and device
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot getvar product 2>&1 | findstr /r /c:"^product: *cepheus" || exit /B 1
product: cepheus
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot erase boot ||
Erasing 'boot' OKAY [ 0.008s]
Finished. Total time: 0.040s
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot flash crclist C:\Users\Win8Pro.GAMINGPC.000\Documents\cepheus_global_images_9.5.30_20190530.0000.00_9.0_global\images\crclist.txt ||
Sending 'crclist' (0 KB) OKAY [ 0.012s]
Writing 'crclist' FAILED (remote: 'update crc list failed')
fastboot: error: Command failed
"Flash crclist error"
Done!
this was the last log after it failed
Try using MiFlashPro tool. You can download the rom directly from the app. I had this issue before and that is the only way I fixed it. Make sure you download the rom that is labeled as fastboot.
Goatfreak99 said:
for TWRP I use Twrp_3.3.0_Cepheus.
Click to expand...
Click to collapse
For me this one
https://forum.xda-developers.com/Mi-9/how-to/recovery-unofficial-twrp-recovery-3-2-3-t3912118
Was working with the system flash to start twrp.
Also I've found in this twrp more usefull options and also more partitions of the phone could be backup.
I'm now on v17 but I've didn't got the link right now.
But don't reboot after flashing twrp and system with adb command, use instead the hardware keys to boot in twrp.
If you've got a backup then you can restore it, may be you've got to flash then also magisk again.
This was the way which was working for me.
Laptapper said:
For me this one
https://forum.xda-developers.com/Mi-9/how-to/recovery-unofficial-twrp-recovery-3-2-3-t3912118
Was working with the system flash to start twrp.
Also I've found in this twrp more usefull options and also more partitions of the phone could be backup.
I'm now on v17 but I've didn't got the link right now.
But don't reboot after flashing twrp and system with adb command, use instead the hardware keys to boot in twrp.
If you've got a backup then you can restore it, may be you've got to flash then also magisk again.
This was the way which was working for me.
Click to expand...
Click to collapse
You Sir,are a true legend.
I was immediatly able to flash that TWRP onto my Mi 9 and from there I could flash the stock ROm.
Thank you very, very much!
I already was afraid of bricking my 450 $ purchase but thanks to you it is back up and running again ^^
Goatfreak99 said:
You Sir,are a true legend.
I was immediatly able to flash that TWRP onto my Mi 9 and from there I could flash the stock ROm.
Thank you very, very much!
I already was afraid of bricking my 450 $ purchase but thanks to you it is back up and running again ^^
Click to expand...
Click to collapse
Well done bro, you've flashed it and it's your work.
I don't know why the others mostly don't use this twrp.
Goatfreak99 said:
You Sir,are a true legend.
I was immediatly able to flash that TWRP onto my Mi 9 and from there I could flash the stock ROm.
Thank you very, very much!
I already was afraid of bricking my 450 $ purchase but thanks to you it is back up and running again ^^
Click to expand...
Click to collapse
I tried flashing that TWRP. But once I boot to recovery, it still goes back to fastboot.
RebornCheiko said:
I tried flashing that TWRP. But once I boot to recovery, it still goes back to fastboot.
Click to expand...
Click to collapse
when you flashed TWRP using fastboot, dont using reboot recovery command but use key combo, volume up/power.
in that way recovery sticks
marcel112 said:
when you flashed TWRP using fastboot, dont using reboot recovery command but use key combo, volume up/power.
in that way recovery sticks
Click to expand...
Click to collapse
It still doesn't work.
I have no choice but to flash the stock ROM using MiFlash Tool, thankfully it worked.
Bricked Mi 9 Lite
Hello. I know this may not be the right topic for which I am sorry. I need your help!
At night my mother's phone caught a bootloop (MI 9 Lite) This is a factory phone used for a month. I was looking for ways to solve the problem. The phone sticks to the MI logo and restart. MI flash sees the phone but there is an error during flash. The program sees the device but does not want flash. I have no idea how to solve the problem. Please help.
Regards
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ps.
If you have links to programs / drivers that can be useful for phone repair. I will be very grateful.
Related
Hi everyone,
I have an HTC One (m7), carrier H3G Italy, unlocked, tampered, S-ON, wtih TWRP 3.0 installed. I had CyanogenMod installed (version 12.x). Recently my phone stopped working without any reason and when I tried to reboot it simply didin't work.
Following some guides I found in this site, I tried to flash a new recovery (the update of TWRP) and the stock recovery, I also tried to flash a new ROM with adb sideload, but nothing worked.
Please help me :angel:.
Thank you a lot
TRenghia said:
Hi everyone,
I have an HTC One (m7), carrier H3G Italy, unlocked, tampered, S-ON, wtih TWRP 3.0 installed. I had CyanogenMod installed (version 12.x). Recently my phone stopped working without any reason and when I tried to reboot it simply didin't work.
Following some guides I found in this site, I tried to flash a new recovery (the update of TWRP) and the stock recovery, I also tried to flash a new ROM with adb sideload, but nothing worked.
Please help me :angel:.
Thank you a lot
Click to expand...
Click to collapse
can you please post the output of "fastboot getvar all" (hide your imei and sn)?
What do you mean by "stopped working" and "tried to reboot it simply didn't work"
The phone doesn't boot in the ROM or it doesn't boot at all (i.e not even in bootloader) ?
Please post a link to the rom you are trying to flash and to the twrp version you are using.
Also you don't need to use sideload anymore when using recent twrp version. TWRP now support MTP so you can simply boot in twrp with your phone connected to your computer and you'll see your phone internal storage from your computer (like a usb thumb drive). Simply drag and drop the rom.zip from you computer to your phone then use the "install" menu of twrp to flash it. From my experience, adb sideload isn't always reliable...
alray said:
can you please post the output of "fastboot getvar all" (hide your imei and sn)?
What do you mean by "stopped working" and "tried to reboot it simply didn't work"
The phone doesn't boot in the ROM or it doesn't boot at all (i.e not even in bootloader) ?
Please post a link to the rom you are trying to flash and to the twrp version you are using.
Also you don't need to use sideload anymore when using recent twrp version. TWRP now support MTP so you can simply boot in twrp with your phone connected to your computer and you'll see your phone internal storage from your computer (like a usb thumb drive). Simply drag and drop the rom.zip from you computer to your phone then use the "install" menu of twrp to flash it. From my experience, adb sideload isn't always reliable...
Click to expand...
Click to collapse
Hi alray,
Thank you for your help. With "stopped wroking", I mean that the phone doesn't boot in the ROM, and when I said "reboot", I mean just switch off and on. I can boot in the bootloader and the recovery .
Now I am using TWRP version 3.0.0-0 and I'd like to flash this ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TRenghia said:
Hi alray,
Thank you for your help. With "stopped wroking", I mean that the phone doesn't boot in the ROM, and when I said "reboot", I mean just switch off and on. I can boot in the bootloader and the recovery .
Now I am using TWRP version 3.0.0-0 and I'd like to flash this ROM.
Click to expand...
Click to collapse
Are you sure your phone wasn't running a newer version than 7.19.771.1? Like maybe 7.19.771.21, 7.19.771.31 or 7.19.771.51? Hard to know since your version-main is blank
Better to edit your version-main to 7.19.771.1 to be 100% sure the RUU will work.
Boot in twrp main menu then open a command window on your computer and type:
Code:
adb shell
echo -ne "7.19.771.1\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
Make sure there is no typo in the long command (copy/paste if needed)
When back in bootloader mode check your version-main is now 7.19.771.1
Code:
fastboot getvar all
Then re-lock your bootloader
Code:
fastboot oem lock
and flash the 7.19.771.1 ruu (make sure the RUU zip file is in the same folder where you have fastboot on your computer. You MUST use the fastboot version linked in the OP of the ruu collection thread to flash the RUU https://androidfilehost.com/?fid=95916177934539737. The "regular" fastboot from the android sdk tool won't work.
Code:
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed.zip
fastboot reboot
alray said:
Are you sure your phone wasn't running a newer version than 7.19.771.1? Like maybe 7.19.771.21, 7.19.771.31 or 7.19.771.51? Hard to know since your version-main is blank
Better to edit your version-main to 7.19.771.1 to be 100% sure the RUU will work.
Boot in twrp main menu then open a command window on your computer and type:
Code:
adb shell
echo -ne "7.19.771.1\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
Make sure there is no typo in the long command (copy/paste if needed)
When back in bootloader mode check your version-main is now 7.19.771.1
Code:
fastboot getvar all
Then re-lock your bootloader
Code:
fastboot oem lock
and flash the 7.19.771.1 ruu (make sure the RUU zip file is in the same folder where you have fastboot on your computer. You MUST use the fastboot version linked in the OP of the ruu collection thread to flash the RUU https://androidfilehost.com/?fid=95916177934539737. The "regular" fastboot from the android sdk tool won't work.
Code:
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed.zip
fastboot reboot
Click to expand...
Click to collapse
Hi alray,
I've done what you suggested, but I couldn't change my version-main (I copied the command) and, when I tried ti flash the new ROM this is what I got
TRenghia said:
Hi alray,
I've done what you suggested, but I couldn't change my version-main (I copied the command) and, when I tried ti flash the new ROM this is what I got
Click to expand...
Click to collapse
I don't really understand why you jumped to step 3 if step 1 didn't worked... Now that the bootloader is relocked you can't boot in twrp anymore to write the correct version-main (might be problematic). What was the problem when changing the version-main? Why not posting it and waiting for help instead of jumping to step #3?
After doing "fastboot oem rebootRUU" did your phone rebooted in ruu mode (a black screen with silver HTC logo on it)?
After much thinking, I decided to root my new phone, but things did not go well. I unlocked the bootloader and everything went well, but at the time of installing twrp everything went to hell. Now I try to install the official ROM via miFlash and via Fastboot but I always get errors.
In myFlash tool I get: error: FAILED (remote: GetVar Variable not Found)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In fastboot I get: sending system_a
FAILED
"Flash system_a error".
I have bootloop and I can not turn off the device. Can somebody help me?
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
minnuss said:
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
Click to expand...
Click to collapse
Hi, I followed the steps but I can't flash system. I got the same error: "Flash system_a error" in "a" and in "b" FAILED (remote: GetVar Variable not Found)
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Yes something strange with the latest fastboot rom. I could flash it but tried a LOT.
use ./fastboot flashing unlock_critical
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
djmitza222 said:
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
Click to expand...
Click to collapse
I tried, flash some images well, but in boot.img just shows flashing but doesn´t continue. I had waiting long time.
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
djmitza222 said:
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
Click to expand...
Click to collapse
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Doesn't work! :/ i got the same error in slot a and b. I tried flash handly, but the problem continues just in system.img. other images flashed well.
Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
meltbanana said:
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
Click to expand...
Click to collapse
:crying: Seriously? your warranty was avoid?
Antolinetz said:
:crying: Seriously? your warranty was avoid?
Click to expand...
Click to collapse
after 2 hours playing with that faulty phone I clearly decided not to open it and sent it back. I suspect there's hardware (RAM?) issues with some Mi A2 devices. as I wrote I wasn't even able to load a kernel. it did weird things and gave me strange fastboot feedback. atm I'll stick with tissot but I'm unsure about xiaomi's latest smartphones .
Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
same occured with me. Try this:
./fastboot flash system_a system.img
./fastboot flash system_b system.img
Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
download the 1.0.2 version, it has an unbrick option that takes care of most softbricks
YOU MUST RUN the unlock oem unlock, flashing, and unlock flashing_critical options (options 1 2 and 3) before trying the unbrick option. If the unbrick option does not work, try the revert to stock option.
For any others getting in a bootloop from TWRP, download the 1.0.1 version and run the Launch TWRP option it will overwrite the boot.img to a usable one. TWRP is really buggy right now so FOLLOW THE INSTRUCTIONS.
And for those who have a bootloop because they tried to install xposed, run the revert to stock option. Unfortunately ATM there is no way to keep your data unless you put the https://magiskroot.net/uninstall-magisk-module-twrp/ zip on your device.
Hi guys, finally whith EDL mode, after hours and hours flashed well!
fastboot oem edl
or
fastboot-edl-v2
I have reviewed each .img file and I also found that apparently the system.img file was not decompressed correctly. Then I went to the always reliable Total commander and was decompressed fine.
Thank you all!
people try:
1- Another usb port
2- Another usb cable
3- Another PC
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
woofwoof75 said:
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
but how?
Hi Guys !
Since today I have a Mi Mix with the MIUI 10 Global Stable Rom.
MIUI Version 10.0.1.0 (OAHMIFH)
Now my question: Which is the right TWRP version and which Magisk version to use.
2. It suffices, if you only want to boot boats TWRP only via fastboot and to flash Magisk
3. no-verity-opt-encrypt not necessary?
4. Last but not the least Which encryption password must be entered in TWRP.
Exact step by step instructions would not be wrong, because I'm not quite sure from the read here
Thank you in advance for your help
this : www.mediafire.com/file/lv7sncx1np9d41u
and this : https://github.com/topjohnwu/Magisk/releases/download/v17.3/Magisk-v17.3.zip
Thanks first of all,
Flashing over Fastboot and if so direct flashing with "Flash twrp" or first twrp boot and then TWRP.img flashing
or something else to consider?
no-verity-opt-encrypt not necessary?
Need password after boot in TWRP or not?
Solved
Self solved !!!
Flash TWRP via Fastboot
fastboot flash recovery C: \ adb \ twrp.img (adapt path to your path on the computer))
fastboot format userdata (because this way is not asked for PW or pin)
If you just want to start #TWRP, you enter the following.
fastboot boot C: \ adb \ twrp.img
To start TWRP, hold the following keys for a few seconds: VOL + & Power
Then copy your Roms and or Magisk from the PC to the phone and flash, alternatively flashing with OTG
Sorry for my bad English
rudiratlos57 said:
Self solved !!!
Flash TWRP via Fastboot
fastboot flash recovery C: \ adb \ twrp.img (adapt path to your path on the computer))
fastboot format userdata (because this way is not asked for PW or pin)
If you just want to start #TWRP, you enter the following.
fastboot boot C: \ adb \ twrp.img
To start TWRP, hold the following keys for a few seconds: VOL + & Power
Then copy your Roms and or Magisk from the PC to the phone and flash, alternatively flashing with OTG
Sorry for my bad English
Click to expand...
Click to collapse
Hi,
I'm on chinese MIUI 10 10.0.1.0 (OAHCNFH). Unlocked bootloader and fastboot flashed TWRP (lithium) 3.2.1.0. Also rooted with Magisk Manager v17. Had to also flash from twrp the no-verity-opt-encrypt to avoid twrp being replaced by the stock miui flash tool. All running smoothly. For now just used root access to install Goolge camera (editing camera2prop); also installed Kernel auditor but did not play with the settings yet.
Marcelocohenarg said:
Hi,
I'm on chinese MIUI 10 10.0.1.0 (OAHCNFH). Unlocked bootloader and fastboot flashed TWRP (lithium) 3.2.1.0. Also rooted with Magisk Manager v17. Had to also flash from twrp the no-verity-opt-encrypt to avoid twrp being replaced by the stock miui flash tool. All running smoothly. For now just used root access to install Goolge camera (editing camera2prop); also installed Kernel auditor but did not play with the settings yet.
Click to expand...
Click to collapse
Hi, where did you get a copy of miui 10? I got a copy from xiaomi website, http://en.miui.com/download-317.html#471. I got boot loop after flashing it. Can you point me to the right direction to get a working copy? thanks
tiunilohmu said:
Hi, where did you get a copy of miui 10? I got a copy from xiaomi website, http://en.miui.com/download-317.html#471. I got boot loop after flashing it. Can you point me to the right direction to get a working copy? thanks
Click to expand...
Click to collapse
if you can't even boot miui10 that you got from official site, then maybe you shouldn't modify anything in your phone, stop it and using it like normal user. good day.
heindrix said:
if you can't even boot miui10 that you got from official site, then maybe you shouldn't modify anything in your phone, stop it and using it like normal user. good day.
Click to expand...
Click to collapse
Is that a joke?
I have been flashing rom and modified many phones. Just feeling missing something. That's why asked.
I was in RR rom before. Wanna try new miui 10. I got other miui 10 worked from rombuilder.com. But missing some features. That's why wanna try the official one. Anyway, next time If you don't have good answer, you don't have to say anything. Good day.
tiunilohmu said:
Hi, where did you get a copy of miui 10? I got a copy from xiaomi website, http://en.miui.com/download-317.html#471. I got boot loop after flashing it. Can you point me to the right direction to get a working copy? thanks
Click to expand...
Click to collapse
If flashing an official recovery ROM doesn't work, usually you must flash a official fastboot ROM to restore everything, i.e. via USB from a Windows computer.
tiunilohmu said:
Hi, where did you get a copy of miui 10? I got a copy from xiaomi website, http://en.miui.com/download-317.html#471. I got boot loop after flashing it. Can you point me to the right direction to get a working copy? thanks
Click to expand...
Click to collapse
Sorry, I received my MIUI 10 via OTA before unlocking mi device. But I know the official MIUI 10 can be downloaded from the MIUI forum (check here http://en.miui.com/a-234.html), there is a fastboot method to flash it but you will probably lose al data and applications (is not like an OTA)
Marcelocohenarg said:
Sorry, I received my MIUI 10 via OTA before unlocking mi device. But I know the official MIUI 10 can be downloaded from the MIUI forum (check here http://en.miui.com/a-234.html), there is a fastboot method to flash it but you will probably lose al data and applications (is not like an OTA)
Click to expand...
Click to collapse
Thanks for the info. Just tried to flash with fastboot. I got "Mismatched image error". After did some reading deleted these lines,
"fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8996_A8" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8996_A8" || exit /B 1"
Then got a "command write failed" error. Why Xiaomi has to make it so complicated? Any other suggestion?
tiunilohmu said:
Thanks for the info. Just tried to flash with fastboot. I got "Mismatched image error". After did some reading deleted these lines,
"fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8996_A8" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8996_A8" || exit /B 1"
Then got a "command write failed" error. Why Xiaomi has to make it so complicated? Any other suggestion?
Click to expand...
Click to collapse
Did you check this https://forum.xda-developers.com/android/software-hacking/devices-xiaomi-firmware-updater-t3741446 ? I think these can be flashed using twrp. There is also a discusion here about the correct twrp version to be used.
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk
zencooler said:
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for replying. I've just tried that and it says 'Your system is not supported for recovery'.
Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka
cielik said:
Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....
androidyeah... said:
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....
Click to expand...
Click to collapse
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:
Try to use the Flash TOOL of this post, it always works with me.
https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964
androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Try to use OTG dload method.
If you need firmware and help tell me!
I had this problem on my EML-L29, tjis helped me:
factory reset
wipe cache
fastboot erase system
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
Yeah, similar to what I had to do. Factory reset wasn't possible for me, but flashing partitions worked.
Bricked P20 Pro
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.
Wrong section. Can this be moved please.
I thought there was a new ROM thread..
Rustyrobotguy said:
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.
Click to expand...
Click to collapse
You can always go into fastboot mode in emergency mode.
Just connect the phone to PC via USB cable and then press power key + Volume Down.
It will bring you into Fastboot Emergency.
Then you can play with fastboot commands.
I recommend you to extract RECOVERY_RAMDIS.img from UPDATE.APP (you can get it from update.zip file for your firmware) into a folder that keeps your fastboot exe file. Then do following command on your PC:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
It will give you stock recovery.
Then you can do command:
fastboot reboot
Immediately after this command disconnect USB cable and press Volume Up key.
On recovery you can do wiping your data partition and don't he factory reset.
If it not help and you are still on boot loop you can go again into fastboot emergency mode and do fastboot command:
fastboot -w
This will reformat your data partition and after this your phone will boot into erecovery to do factory reset again. It should help you to bring your phone into live.
Regards.
Sent from my SM-N960F via Tapatalk
androidyeah... said:
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:
Click to expand...
Click to collapse
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s
thoughtless22 said:
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s
Click to expand...
Click to collapse
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk
zencooler said:
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Same Problem for me. cant find any way to get this to work.. my Phone is bricked 2 month now i miss it lol
does anyone have a Solution for this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Try thoes command in fastboot:
HTML:
fastboot getvar rescue_phoneinfo
fastboot oem get-product-model
fastboot oem get-psid
fastboot getvar vendorcountry
fastboot oem get-build-number
if it returns something weird, then you are fvcked up.
mine messed up once, I had to get to Service Center to replace the motherboard.
Maybe, now there is some 3rd party way can save you phone, I don't know.
so here how i bricked my phone.
i wanted to try new miui 12 on my k20 pro .so i download the latest beta release from official sources, then what i did next is change the device name in update script of miui 12 zip file ,i replaced 'Raphael' by 'Raphaelin' as i am using Indian variant after tring it for some time i decided to go back to my previous version as i had an backup.
After i restored my back up and reboot it went into boot loop , keeps booting till logo.(restore was 100%ok)
so next i took it to just install a custom rom ,i decided upon pixel rom and installation went successfully but on reboot option it showed me no os installed .
So i decided what the **** lets just go to stock rom using 'mi flash tool' (i have used this method as last resource many time before in case if all went to ****) but in this time it showed my an error of mismatching image and device . i don't know why this happened as i have done it many times before and every time it went pretty ok.
then i tried to boot to recovery but to no avail it was not happening i keep booting into bootloader next what i did is try to reflash my recovery
fastboot flash recovery twrp.img
it went ok
then
fastboot boot twrp.img
it showed me an error
creating boot image...
creating boot image - 38807552 bytes
Sending 'boot.img' (37898 KB) OKAY [ 0.836s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed.
so my current situation is i can't boot into recovery and i install stock miui with mi flash .
so Guys any idea why this all is happening.
Are you able to boot into recovery by using 'volume+' and power button combination?
pankajgulia111 said:
so here how i bricked my phone.
i wanted to try new miui 12 on my k20 pro .so i download the latest beta release from official sources, then what i did next is change the device name in update script of miui 12 zip file ,i replaced 'Raphael' by 'Raphaelin' as i am using Indian variant after tring it for some time i decided to go back to my previous version as i had an backup.
After i restored my back up and reboot it went into boot loop , keeps booting till logo.(restore was 100%ok)
so next i took it to just install a custom rom ,i decided upon pixel rom and installation went successfully but on reboot option it showed me no os installed .
So i decided what the **** lets just go to stock rom using 'mi flash tool' (i have used this method as last resource many time before in case if all went to ****) but in this time it showed my an error of mismatching image and device . i don't know why this happened as i have done it many times before and every time it went pretty ok.
then i tried to boot to recovery but to no avail it was not happening i keep booting into bootloader next what i did is try to reflash my recovery
fastboot flash recovery twrp.img
it went ok
then
fastboot boot twrp.img
it showed me an error
creating boot image...
creating boot image - 38807552 bytes
Sending 'boot.img' (37898 KB) OKAY [ 0.836s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed.
so my current situation is i can't boot into recovery and i install stock miui with mi flash .
so Guys any idea why this all is happening.
Click to expand...
Click to collapse
What ROM did you try and restore in the Mi Flash Tool?
If you tried an Indian ROM, then try to flash a Chinese ROM instead.
pankajgulia111 said:
so here how i bricked my phone.
i wanted to try new miui 12 on my k20 pro .so i download the latest beta release from official sources, then what i did next is change the device name in update script of miui 12 zip file ,i replaced 'Raphael' by 'Raphaelin' as i am using Indian variant after tring it for some time i decided to go back to my previous version as i had an backup.
After i restored my back up and reboot it went into boot loop , keeps booting till logo.(restore was 100%ok)
so next i took it to just install a custom rom ,i decided upon pixel rom and installation went successfully but on reboot option it showed me no os installed .
So i decided what the **** lets just go to stock rom using 'mi flash tool' (i have used this method as last resource many time before in case if all went to ****) but in this time it showed my an error of mismatching image and device . i don't know why this happened as i have done it many times before and every time it went pretty ok.
then i tried to boot to recovery but to no avail it was not happening i keep booting into bootloader next what i did is try to reflash my recovery
fastboot flash recovery twrp.img
it went ok
then
fastboot boot twrp.img
it showed me an error
creating boot image...
creating boot image - 38807552 bytes
Sending 'boot.img' (37898 KB) OKAY [ 0.836s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed.
so my current situation is i can't boot into recovery and i install stock miui with mi flash .
so Guys any idea why this all is happening.
Click to expand...
Click to collapse
You need to remove these lines from .bat files within fastboot ROM folder. or if you are on Linux then corresponding lines from .sh files.
Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *raphaelin" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *raphaelin" || exit /B 1
Robbo.5000 said:
What ROM did you try and restore in the Mi Flash Tool?
If you tried an Indian ROM, then try to flash a Chinese ROM instead.
Click to expand...
Click to collapse
It worked , I have indian variant but it showed mismatched image and device.
But it worked well with global variant , I flashed mi 9t pro global version.
Thanks
pankajgulia111 said:
It worked , I have indian variant but it showed mismatched image and device.
But it worked well with global variant , I flashed mi 9t pro global version.
Thanks
Click to expand...
Click to collapse
I got into the same issue, just go into the flash_all file of the indian stock rom and change it into raphael and it will work as charm.
Senior_Pj said:
I got into the same issue, just go into the flash_all file of the indian stock rom and change it into raphael and it will work as charm.
Click to expand...
Click to collapse
How to modify flash_all file on Windows 10
toufik_d said:
How to modify flash_all file on Windows 10
Click to expand...
Click to collapse
Notepad++
Senior_Pj said:
Notepad++
Click to expand...
Click to collapse
I tried and could not change it
toufik_d said:
I tried and could not change it
Click to expand...
Click to collapse
I did it last week
Senior_Pj said:
I did it last week
Click to expand...
Click to collapse
thank you very much
It has been modified with another program and transferred to the Indian version