Related
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Click to expand...
Click to collapse
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
SubwayChamp said:
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
Click to expand...
Click to collapse
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
bob_bricoleur said:
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
Click to expand...
Click to collapse
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
SubwayChamp said:
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
Click to expand...
Click to collapse
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
bob_bricoleur said:
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
Click to expand...
Click to collapse
Some times causes different results flashing the fastboot full image through EDL mode (download mode) instead of through fastboot mode.
It could be the issue the TWRP version if there is other available.
And you could try deleting the recovery partition with fastboot erase recovery, then boot (don´t flash yet) to recovery using fastboot boot whateveriscalled.img, then in TWRP flash the TWRP image or the installer zip, then reboot for first time to TWRP and try again.
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Arnavzz said:
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Click to expand...
Click to collapse
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Kaleshwar said:
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Arnavzz said:
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Click to expand...
Click to collapse
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
chintu1234 said:
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
Click to expand...
Click to collapse
This doesn't work. It flashes successfully but when I select Reboot Recovery and press the power button, it boots back to the bootloader.
Maybe wrong twrp img
Try the older 3.3.1-12 twrp.img and then try
Also try the following as well
Fastboot flash boot_a twrp.img
Fastboot flash boot_b twrp.img
And try just reboot not reboot to recovery
Kaleshwar said:
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Arnavzz said:
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Click to expand...
Click to collapse
You can try it . Looks pretty solid.
Sent from my ONEPLUS A6003 using Tapatalk
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
I had similar situation last evening.
I made the mistake of having a factory reset on rooted 9.0.8 and then trying to flash the 10.0.1
I got the same error, so I had to connect my mobile to my laptop, fastboot to the newest TWRP, flash the TWRP, flash the 9.0.9, flash the 10.0.1, flash magisk 20.x and then everything was working.
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules
Update through local update 10.3 or current ROM
Reboot
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img - ( https://androidfilehost.com/?fid=4349826312261678088 )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP ( https://androidfilehost.com/?fid=4349826312261678087 ) or Blu zip (https://github.com/engstk/op6/releases/download/r112/blu_spark_r112-oos_op6-op6t_0dd5f9228.zip)
5. Reboot to recovery
6. Flash Magisk 20.1 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://drive.google.com/file/d/1w44cUg815g-H1h_6gObUVPLDTc_dtiMX/view
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
This worked for me.. Finally. PS - I did in a slightly different order. I installed twrp first, booted into twrp, made sure I was in slot A. If I wasnt, I rebooted to recovery. If I still wasnt I set slot to A manually then rebooted to recovery again. Flashed the stock boot img you linked to boot, then rebooted to recovery slot b (same process I did to get to slot a) then flashed the stock boot img to boot again THEN finally installed magisk. Booted to system, where it hanged a bit, rebooted before getting into android, but booted in just fine after that..
For some reason if you don't flash stock img to slot A (and maybe slot B too, I did this for good measure) before installing magisk everything dies a horrible death and breaks, which can't even be recovered from /boot /system backups..
EDIT: Tried to reboot into recovery, which reverted back to stock for some reason after doing the above steps. So I proceeded to install the bluspark recovery, rebooted into recovery, made sure I was in slot b, made a back up of the boot image, then flashed bluspark kernel. Got stuck at the unlocked bootloader screen. Rebooted into recovery, restored my /boot back. Still stuck when I try to boot into system. Fixed it by booting back into recovery in slot A flashing stock boot img, then into slot b stock boot, then magisk, but also installed bluspark kernel here because I had a feeling I would lose twrp from flashing to stock boot img, and that the issue was caused by twrp (both twrp-3.3.1-16-enchilada-installer-mauronofrio and twrp-3.3.1-x_blu_spark_v9.108_op6 have this issue). Guess what? Turns out I was right. Having twrp breaks everything after you install magisk, so you need to flash the stock boot img before flashing magisk for some reason.. and cant install twrp again unless you dont mind bricking your phone.
EDIT2: F2FS works, just boot into recovery via fastboot (this should be slot b), change /data to f2fs, boot back into fastboot then into recovery again by fastboot (slot b again), flash stock boot img > magisk > bluspark kernel > f2fs_fstab.zip > f2fs_optimize.zip > factory reset/wipe (from twrp before rebooting), done just reboot into system. You of course lose twrp because magisk doesnt like twrp on oos 10.x for some reason, and will need to set everything up again to cause of the wipe. If you dont factory reset/wipe from twrp before booting into system your system will crash and reboot every time you boot into android, then have to do all the steps I listed again.
EDIT3: Never mind, I was wrong, f2fs makes almost all your apps and storage unusable. Not sure if it's cause of the rom (OOS10.3.0) or because we have to flash stock boot.img and get rid of twrp before booting into system. Either way, f2fs has never really been stable or fun to get working so better to stick to ext4.. that few percent performance boost isnt worth it.
EDIT4: This is my last update. After experimenting with different things, bricking my phone, restoring it via fastboot rom, many many times, I've verified the simplest and cleanest way to install magisk.. Do note you wont be able to keep twrp.
Method A - If you already have twrp
Boot recovery into slot a, flash your rom's stock boot.img, then boot into your recovery in slot b (dont boot into slot a recovery because slot a wont have twrp anymore), flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot boot into system. That's it.
Method B - If you don't have twrp
Boot into fastboot, and from your cmd/terminal run fastboot flash boot yourtwrp.img (I suggest Mauronofrio's twrp-3.3.1-16-enchilada-Q-mauronofrio.img or newer). Use your volume buttons to select boot into recovery. Make sure your active slot is B, (if it isnt, install twrp (bluspark and Mauronofrio's twrp both work great) by zip, then follow the steps above in method A). Once you've verified you're in slot B flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot into system. That's it.
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
not working
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
gauravkapoor99150 said:
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
Click to expand...
Click to collapse
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
RASTAVIPER said:
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
sir can you send me a link
lemon07r said:
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
Click to expand...
Click to collapse
@mauronofrio wrote the following in his TWRP thread a while ago:
So little update, after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now.
There are not problems on Android Pie, if you need of the twrp on android Q just flash in boot partition the Q .img (fastboot flash boot twrp.img) and then reboot from fastboot in recovery. Before publishing the twrp I had not tested magisk and twrp together.
On Android 10 use only magisk 19.4
Click to expand...
Click to collapse
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
Basically worked for me, too, with 2 exceptions:
- this tool to remove magisk modules etc. wouldn't be flashed, always ended in an unnamed error; probably the cause for some other problems?
- flashing boot.img (V 10.3.4 from this thread) didn't work for me, I always ended up in twrp's splash screen
- got it solved by dirty flashing the full V 10.3.4 ROM (again from the above thread)
Many thanks once again!
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2
Hi,
sorry to take your time
I'm french so also sorry for my english
I have installed TWRP 3.51 on my poco x3 pro using ADB
fastboot flash recovery twrp.img
sending
writing
finish
fastboot boot twrp.img
After install phone boot in twrp.
I then use the option booting system and the phone boot again in TWRP
Then i used a boot.img from a rom stock
fastboot flash boot boot.img
I also tried fastboot flash vbmeta vbmeta.img
without success
Each time the phone boot in TWRP
regards
alain
Ps I'm not an expert to please explain as much as you can
Dude what?
Fastboot Flash recovery recovery.img
That's it!
Hold Volume Up+ Power to boot the device to boot into Recovery.
Go to install and select customRomFileOfYourChoice.zip to install it.
Maybe needs a format Data to wipe failed encryption.
Reboot to system.
Done
Haldi4803 said:
Dude what?
Fastboot Flash recovery recovery.img
That's it!
Hold Volume Up+ Power to boot the device to boot into Recovery.
Go to install and select customRomFileOfYourChoice.zip to install it.
Maybe needs a format Data to wipe failed encryption.
Reboot to system.
Done
Click to expand...
Click to collapse
thank you
a stock rom or a custom rom ?
custom ROM.
Stock rom has to be flashed differently.
alix264 said:
Hi,
sorry to take your time
I'm french so also sorry for my english
I have installed TWRP 3.51 on my poco x3 pro using ADB
fastboot flash recovery twrp.img
sending
writing
finish
fastboot boot twrp.img
After install phone boot in twrp.
I then use the option booting system and the phone boot again in TWRP
Then i used a boot.img from a rom stock
fastboot flash boot boot.img
I also tried fastboot flash vbmeta vbmeta.img
without success
Each time the phone boot in TWRP
regards
alain
Ps I'm not an expert to please explain as much as you can
Click to expand...
Click to collapse
You need to install a custom ROM and format the data. If you are using an Android 12 or 13 ROM the data partition is encrypted that's why you're phone is boot looping
its working... I had to format data
thank you very much
All is working now. magisk installed (with trwp), lsposed install
But If i'm going in trwrp backup option, I don't see "system"
?
you have to mount the system partition first and set it via terminal to read/write i think.
But i am also not professional mhh..
Try mount it and when u cant Backup it ask again for help
You Want Video turorial ?
Cheack This Out;- https://forum.xda-developers.com/t/...stom-rom-installation-video-tutorial.4583503/
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
{
"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"
}
not working in my device
fastboot flash boot twrp.img
my device went in bootloop
i have also tried
Fastboot boot twrp.img
this is throwing " status read failed (too many links)
(also tried with downgrading to MIUI-12 but no success)
Then i tried to boot into fastbootD mode.
with command "Fastboot reboot fastboot"
Now my device is in the infinite boot loop.
Please help
Is that Redmi 10 Selene ?
And Which twrp you used ?
Neelthegamer007 said:
Is that Redmi 10 Selene ?
And Which twrp you used ?
Click to expand...
Click to collapse
is its redmi 10 selene
and i have used twrp you placed here
NOOBOHOLIC said:
is its redmi 10 selene
and i have used twrp you placed here
Click to expand...
Click to collapse
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Neelthegamer007 said:
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Click to expand...
Click to collapse
But nothing is working now its just stucked in the bootloop
not booting into recovery
not booting into fastboot
how i do it further
You need SP flash tool, and mtk auth bypass just download it, bypass mtk auth and go to sp flash tool, on auth file section select mtk scatter file from miui fastboot rom/images folder, and on sp flash tool un select every file except boot or boot.img
And click the download button [ must be sure that you need to only download the boot.img file,no other file.]
After download,you can go fastboot
If you can't understand
Get help from YouTube.
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
Downgrade is not nessesery with only root
Neelthegamer007 said:
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Click to expand...
Click to collapse
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Tawsif999 said:
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Click to expand...
Click to collapse
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Neelthegamer007 said:
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Click to expand...
Click to collapse
Thank you very much. I thought I have to flash using fastboot flash vbmeta vbmeta.img. But now I can understand, the command is not for flashing. It's for disabling verification.
Tawsif999 said:
You are most welcome
Click to expand...
Click to collapse
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Teaykhuad said:
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Click to expand...
Click to collapse
Sure,are you active right now ? Reply again,i eill give you my telegram..
yes i trying to booting now i dm you
Teaykhuad said:
yes i trying to booting now i dm you
Click to expand...
Click to collapse
How's your experience?
Neelthegamer007 said:
How's your experience?
Click to expand...
Click to collapse
Good bro You teach me to flash custom rom and pixel expirence is not bad but im go to miui and install https://forum.xda-developers.com/t/ultra-rooted-miui-package.4487967/ this for speed and fast animation
Neelthegamer007 said:
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
View attachment 5793645
Click to expand...
Click to collapse
How do I restore WiFi and Bluetooth after flashing