Hello
I have big problem.
After patching img over Magisk and flash this new patched img, can not start system / boot loop to POCO logo, or boot loop to MIUI logo - here system starting, but every restart and boot loop
Help please
Thanks
Hi!
Which boot-img did you patch and where did it come from?
How did you flash it?
So:
I received an update 12.5.8.0.RKHEUXM
After the update, I always have to root the phone again.
So I took boot.img from the original 12.5.8.0.RKHEUXM and patched it via Magisk.
I flashed the patched boot.img via ADB.
Well, after the restart, my phone will boot only after the MIUI logo and a bit of a melody, and the phone will restart again. This restart is performed about 4 times and remains/stops in fastboot mode,or it will return to TWRP after clearing dalvik and cache and restarting.
He does what he wants
I've had a problem with that before, but it was enough to delete Dalvik and the cache via temporary TWRP.
Then the system booted up normally, but now it doesn't work even after deleting Dalvik and the cache.
Here is a link to the thread where I solved it. Nobody actually advised me there, I just tried to clear dalvik and cache via TWRP and it was after the problem. Unfortunately, now the problem persists.
Poco F3 - Boot Loop to POCO logo / Please help
Hello. I have a big problem after updating the firmware. Poco F3 root over magisk. After updating from 12.5.6.0 RKHEUXM, I updated to 12.5.7.0 RKHEUXM. After the restart, both the phone and the system booted up. I patched the original boot.img...
forum.xda-developers.com
Thats what I did also with 12.5.8.0.RKHEUXM and everything is working fine.
Updated to 12.5.8.0 via the MIUI updater, but downloading the full rom, as the updater told me that the incremental update (~58MB) wouldn't work.
Then downloaded the the recovery file here: https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.8.0.RKHEUXM/
Unzipped it and extracted the boot.img with payload-dumper-go on my Mac: https://github.com/ssut/payload-dumper-go
Patched the boot.img with Magisk on the phone.
Copied the patched_boot.img file back to the Mac.
Flashed the patched_boot.img from the mac with fastboot to both partitions:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Friend, I did exactly what you were writing, and unfortunately my system won't start
The only thing I did differently was to download the big rom 6gb update so I didn't have to extract boot.img. I didn't have to use a payload dumper.
Any other solution?
But I don't want to lose data and applications!
Did you try wiping data partition?
takichiman said:
Did you try wiping data partition?
Click to expand...
Click to collapse
Where should I do it?
But I don't want to lose data and applications!!!!!
I have bootloop to MIUI logo 4times - 5times and then stop in fastboot mode , It stops in fastboot mode and after pressing and holding the power button, the mobile starts only in fastboot mode, it no longer starts booting to the MIUI log
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
takichiman said:
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
Click to expand...
Click to collapse
You didn't give me much advice, my friend
I don't want to lose any data, or applications, pictures, just anything.
If it went after deleting the dalvik / cache last time, then why shouldn't it go now?
The system boots only to the miui logo, then the boot loop.
I don't understand why this is so.
And can't you somehow refresh the whole rom without losing data, applications and files?
Boot temp recovery, backup boot, patch backed boot and flash patched boot ... Just rename the boot backed image of twrp in boot.img, patch and flash ...
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Dark-Yox said:
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Click to expand...
Click to collapse
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
snx413 said:
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
When you boot, you have access normally
snx413 said:
When you boot, you have access normally
Click to expand...
Click to collapse
And how do I remove them? instructions please
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
You can remove them in TWRP
jkmaxfli said:
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Click to expand...
Click to collapse
Dirty flash the whole ROM then
Adb shell
then
magisk --remove-modules
Dark-Yox said:
You can remove them in TWRP
Dirty flash the whole ROM then
Click to expand...
Click to collapse
How it dirty flash ?
I used it over TWRP recovery ROM zip file, and not work flashing
Related
my flashing history:
i was on audax (oos based nougat rom) with blu spark kernel before, then went to official ob1, then back to audax, then back to stock oos nougat and now i flashed audax and after clean flashing it, it just wont boot up.
when i try to boot up i see the 1+ logo but then it reboots to recovery. i also tried flashing stock nougat again and also flashed stock kernel manually but it also doesnt work.
i always do:
1. wipe system/dalvic/cache/data
2. install ROM
3. wipe dalvik/cache
4. flash magisk (also tried without flashing magisk)
5. reboot
i've been looking on the interwebs all day but nothing worked.. help pls :/
EDIT: problem was blu spark twrp. Maybe installing Oreo ****ed it up. I flashed codeworkx newest twrp universal build and now Im able to boot again!! Btw: I also found that magisk 15.0 prohibits a proper boot up and results in a boot loop. version 15.2, however, does the trick!
when it auto reboot to recovery, formate data
When s**t happens, it is wise to start everything from scratch:
-boot in fastboot mode and flash stock recovery with "fastboot flash recovery recovery.img" (rename recovery.img with your recovery filename), then reboot recovery and select english, advanced, adb sideload;
-flash stock OS with "adb sideload rom.zip" (rename rom.zip with your Oxygen OS filename).
Procedure will require some minute because of the large file size. Remember to save all your data on internal storage first!
I advice you to flash original recovery because often sideloading in TWRP leads to some error.
Your phone will boot again... after that you may reflash TWRP, Magisk etc
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
redatak said:
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
Click to expand...
Click to collapse
He says that it occurs even without Magisk... I had a similar trouble once, and the only way to solve it was the procedure I wrote above...
I dont know if you can boot it w/o root
redatak said:
I dont know if you can boot it w/o root
Click to expand...
Click to collapse
Why not? Stock OS is not rooted.
jonsat said:
Why not? Stock OS is not rooted.
Click to expand...
Click to collapse
He said audrax not stock oos
SOLVED! TWRP was the only variable left that I didn't think of. See initial post for solution. thx for help!
Goodmorning, I've a strange problem with flashing recovery.
I used lastest fastboot
I've flashed the recovery (fastboot flash...) Then booted into it directly (fastboot boot recovery...) And obviously problems with mounting data.
The real problem is that when I reboot system , twrp is automatically erased and stock recovery is mounted.
I've tried everything, new recovery,new fastboot...
Please help me
That's standard with a lot of OEM ROMS on many different phones. You can flash magisk or SuperSU to preserve your flashed twrp.
sbeaber4 said:
That's standard with a lot of OEM ROMS on many different phones. You can flash magisk or SuperSU to preserve your flashed twrp.
Click to expand...
Click to collapse
That won't work, the no-verity-opt zip is needed to preserve twrp or it will always revert back to the stock one.
Go here
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
And DL the TWRP & no-verity-opt-encrypt 1.6
follow the directions starting with
Open a command prompt and verify your device appears in fastboot
Then run
Code:
fastboot flash recovery C:\Twrp__chinese_Android8.img
Click to expand...
Click to collapse
Pitrino said:
Goodmorning, I've a strange problem with flashing recovery.
I used lastest fastboot
I've flashed the recovery (fastboot flash...) Then booted into it directly (fastboot boot recovery...) And obviously problems with mounting data.
The real problem is that when I reboot system , twrp is automatically erased and stock recovery is mounted.
I've tried everything, new recovery,new fastboot...
Please help me
Click to expand...
Click to collapse
- flash latest twrp https://twrp.me/xiaomi/xiaomimimix2.html
- reboot to recovery with hardware keys (volume-up + power) immediately after flashing
That solved the problem for me.
RECOVERY information:
Name Version: Xiaomi Mi 8 Lite Multilanguage TWRP
Download:
DOWNLOAD
MOD EDIT: Link removed, side is containing warez
How to install:
Fastboot just run .bat file to install it from fastboot mode
TWRP.img can be flashed manually from fastboot
all credits goes to @wzsx150, and poison-74 (4pda)
U know if this is compatible with latest Miui EU rom?
Is data decryptable?
Not entire related to Platina but Mi8 SE users are having trouble with twrp and miui eu.
Thanks.
Have downloaded and installed file recovery.img with twrp, works ok with xiaomi.eu rom.
I have MIUI 10 xiaomi.eu 9.1.10 android 9
lucainno said:
Have downloaded and installed file recovery.img with twrp, works ok with xiaomi.eu rom.
I have MIUI 10 xiaomi.eu 9.1.10 android 9
Click to expand...
Click to collapse
Can you enter in twrp and see if data folder is avalable?
Or it ask a password?
Go recovery no enter password, press cancell .
Before wipe Save All data to PC
(this action wipe All data and internal Memory) Wipe data factory reset and reboot phone
install update recovery.img multilanguage
Please help me, how enter to twrp recovery on Mi8 Lite ? I try all buttons combinations and nothing.
Power of phone
Press Vol + and Power for 5 seconds for enter recovery
Hi guys, I just went from Redmi5 Plus to Mi8 lite, unfortunately I have to wait for the famous 360 hours in the meantime I'm downloading what I need on the R5Plus was available Orange Fox recovery, which automatically decrypted the partitions without having to install lazy Flasch later, here how does this TWRP mod do this?
I would like to install the Xiaomi Eu as soon as I unlock the bootloader I am currently on last Global Stable 10.2.2.0 a help thanks.
It's work on android pie beta global 9.3.1?
this should be a new one:
MOD EDIT: Link removed, side is containing warez
This build does not work with Pie - can someone update the initial post?
excuse me sir, ust want to ask, after flashing twrp 1003 version why after reboot always revert to stock recovery, is there any to fix it, thanks
edit : i already fix it
falqon said:
excuse me sir, ust want to ask, after flashing twrp 1003 version why after reboot always revert to stock recovery, is there any to fix it, thanks
edit : i already fix it
Click to expand...
Click to collapse
Could you please share how you fixed it?
Just upgraded the ROM to 10.3.2.0 and now TWRP recovery always reverted to stock recovery after reboot.
reflash your twrp via adb and when u type "fastboot reboot" press and hold Volume Up until enter twrp, and then try to reboot recovery via twrp. i can't share youtube link, afk right now
falqon said:
reflash your twrp via adb and when u type "fastboot reboot" press and hold Volume Up until enter twrp, and then try to reboot recovery via twrp. i can't share youtube link, afk right now
Click to expand...
Click to collapse
Done this several times, but I didn't use hard buttons, instead i used fastboot boot recovery.img command to reboot to recovery after flashing recovery. I also tried rebooting to recovery from twrp without problem, but after rebooted to system, twrp reverted to stock recovery, everytime.
I didn't have this problem with MIUI 10.3.1.0 with the same TWRP.
edit : I'm using TWRP 0330 btw, and somehow there was no swipe to allow modification confirmation when the phone rebooted to twrp for the 1st time after flashing twrp.
Wonder why.
ne0t said:
Done this several times, but I didn't use hard buttons, instead i used fastboot boot recovery.img command to reboot to recovery after flashing recovery. I also tried rebooting to recovery from twrp without problem, but after rebooted to system, twrp reverted to stock recovery, everytime.
I didn't have this problem with MIUI 10.3.1.0 with the same TWRP.
edit : I'm using TWRP 0330 btw, and somehow there was no swipe to allow modification confirmation when the phone rebooted to twrp for the 1st time after flashing twrp.
Wonder why.
Click to expand...
Click to collapse
check your display panel via device hardware info on playstore, mine is synaptic, not all twrp version work on this panel, i'm using twrp 3.2.3-1003 btw
https://www.youtube.com/watch?v=7eeiSm7rzZY
falqon said:
check your display panel via device hardware info on playstore, mine is synaptic, not all twrp version work on this panel, i'm using twrp 3.2.3-1003 btw
https://www.youtube.com/watch?v=7eeiSm7rzZY
Click to expand...
Click to collapse
Tks, but I don't have problem with TWRP 0330, it works fine, including touch screen, the problem is TWRP get replaced by Stock Recovery everytime I boot my my phone to system.
I don't want to root my phone, just like to have TWRP recovery around so I can use it to flash hosts file for ads blocking and some other things.
Someone told me i need to flash lazyflasher...I'm going to do it later ..
ne0t said:
Tks, but I don't have problem with TWRP 0330, it works fine, including touch screen, the problem is TWRP get replaced by Stock Recovery everytime I boot my my phone to system.
I don't want to root my phone, just like to have TWRP recovery around so I can use it to flash hosts file for ads blocking and some other things.
Someone told me i need to flash lazyflasher...I'm going to do it later ..
Click to expand...
Click to collapse
Boot to recovery through fastboot and then flash the image or the zip through TWRP, then to flash it reboot again to TWRP before to boot up to system.
SubwayChamp said:
Boot to recovery through fastboot and then flash the image or the zip through TWRP, then to flash it reboot again to TWRP before to boot up to system.
Click to expand...
Click to collapse
Tried that too, actually more, boot to recovery from fastboot with fastboot boot recovery.img command and also hard button, boot to recovery from twrp recovery, flash recovery.img, boot to twrp recovery again twice, but stock recovery still came back.
ne0t said:
Tried that too, actually more, boot to recovery from fastboot with fastboot boot recovery.img command and also hard button, boot to recovery from twrp recovery, flash recovery.img, boot to twrp recovery again twice, but stock recovery still came back.
Click to expand...
Click to collapse
No. don´t try to boot to recovery from fastboot after to flash it, don´t flash it through fastboot.
Do the next three steps and see what happens but do it exactly the same or won´t worth the try:
- In fastboot delete recovery partition by typing fastboot erase recovery
- Then reboot to recovery (don´t flash it yet) by typing fastboot boot twrp.img (rename recovery image firstly to twrp)
- Now once in TWRP flash the zip or image to the recovery partition, when you finish go to Reboot options within TWRP and choose recovery to boot to it before to boot up to system. If you boot at this instance to TWRP then the issue have to be solved, reboot normally to system.
Edit: If this way the problem is not solved then after to install TWRP flash Magisk that can prevent it to be overwritten.
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
killer23d said:
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
Click to expand...
Click to collapse
already done, if i flash it again will it work? because im still stuck in the bootloop
Nicster205 said:
already done, if i flash it again will it work? because im still stuck in the bootloop
Click to expand...
Click to collapse
if you reflash the factory boot.img then you'll get out of bootloop.
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse
reflashing the factory boot.img seems useless. you can long-press the power button to force power down. then power up to the fastboot mode,and reflash the full factory image(11 or 10). the nomal methon working on 10 seems dizzy in 11 now.
fwiw, heres the path i used...i hate making it more steps than needed (tranferring boot image to device and back again for magisk patching for example)...
1) flash-all.bat (with wipe enabled - because clean install)
2) Immediately on reboot from 1 and before it gets anywhere near to beginning of setup: fastboot boot twrp-3.4.0-1-taimen.img
3) adb push Magisk-e66b0bf3(20425).zip /tmp
4) adb shell twrp install /tmp/Magisk-e66b0bf3(20425).zip
5) adb reboot
6) after reboot, install canary magisk manager (for whatever reason doesnt install from TWRP flash)
7) open canary magisk manager and enable magiskhide
This is caused by twrp
Use android toolbox, just boot twrp, flash magisk
boot into twrp go to advanced fix bootloop option reboot
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse
Hello.
How can I please reinstall the stock rom via TWRP recovery without data loss, or how can I reinstall it via the Miflash tool?
I have a bootloop and would like to try reinstalling rom. Thanks
basically what u can do is flash stock rom using mi flash tool. ensure that down to the bottom u click save user data. and i think u should be fine flashing the stock rom and preserving your data in that sense. after flashing wait and let the device reboot for itself it usually takes a couple mins
TormentedHeart said:
basically what u can do is flash stock rom using mi flash tool. ensure that down to the bottom u click save user data. and i think u should be fine flashing the stock rom and preserving your data in that sense. after flashing wait and let the device reboot for itself it usually takes a couple mins
Click to expand...
Click to collapse
I have already managed to boot into the system, in TWRP Recovery I wipe dalvik.
But I need root and I must to patch the boot.img again via Magisk. And then I must flash patched boot.img via ADB back to the mobile, but I'm afraid I'll go back to the bootloop.
Any other options to do root or avoid bootloop?
Thanks
jkmaxfli said:
I have already managed to boot into the system, in TWRP Recovery I wipe dalvik.
But I need root and I must to patch the boot.img again via Magisk. And then I must flash patched boot.img via ADB back to the mobile, but I'm afraid I'll go back to the bootloop.
Any other options to do root or avoid bootloop?
Thanks
Click to expand...
Click to collapse
Stupid question but did you extracted boot.img before or after update? Maybe you flashed patched boot.img from previous update to last update? That would cause bootloop
Greenspoof said:
Stupid question but did you extracted boot.img before or after update? Maybe you flashed patched boot.img from previous update to last update? That would cause bootloop
Click to expand...
Click to collapse
It's not a stupid question.
The update was displayed on my phone, downloaded, installed, restarted and booted into the system, everything is fine.
Then I had to download the update manually from the Internet and extract the boot.img. and I then patched it via Magisk and flashed it back to the mobile via ADB, and then a bootloop occurred.
jkmaxfli said:
I have already managed to boot into the system, in TWRP Recovery I wipe dalvik.
But I need root and I must to patch the boot.img again via Magisk. And then I must flash patched boot.img via ADB back to the mobile, but I'm afraid I'll go back to the bootloop.
Any other options to do root or avoid bootloop?
Thanks
Click to expand...
Click to collapse
basically to root its just best to flash the official magisk zip via twrp. it patches the boot img during the process. and u wont get bootloop