[Help] Bootloop after flash Magisk with TWRP - Xiaomi Mi 9 SE Questions & Answers

Hi!
I was about to end this tutorial to root my MI 9 se (https://forum.xda-developers.com/t/...er-flashing-recovery-rooting-process.4286597/) and when I restart after install Magisk, I get a boot loop. Since then I tried this so far:
-Run uninstall.zip (from magisk apk). Resulting on "Updater process ended with error: 1"
-Install a previous versions (23 and 25). After install each version, I rebooted without success. Trying the uninstall.zip of each version result in the same previous error.
-Flash a boot.img. Doesn't seems to work
-Try the Magisk Manager tool. Running mm says that No magisk is installed, althought installing any verision of Magisk doesnt seems to fail (just the uninstall.zip part)
Since the begginning i had to figure some things by myself because adb not recognizes the device. Fastboot in other hand works perfectly (My computer only detects the device when on fastboot, no the other way. Seems to be something related to encryption by Xiaomi)
Some thoughts?
Thanks!
UPDATE: I had to go back to Stock MIUI through MiFlash Utility. After that, y tried another method with Lineage OS UNOFFICIAL, from this same forum, but I reached the same point, with a TWRP recovery bootLoop. I tried version 3.6 and 3.7 of TWRP and the result was the same.
UPDATE 2: Tried SHRP Recovery, but once flashed, pressing volume up + power button wont boot into recovery, just fastboot again (same behaviour as volume down + power). Its so strange but, well, another one more to the bag of problems.. In this try, I was able to boot again normally if just power on the device normally.

Related

Android 8 update with FlashFire breaks TWRP or TWRP boot-loop

Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.

Previous Root on Stock + TWRP + Magisk + OTA update needed + Stupidity + Sultan

OK, so I've been getting the August OTA nagging for a bit, and I finally decided I needed to read some instructions on things and get it on my already rooted phone.
I started with...
1. Unlocked bootloader
2. Root on the stock ROM
3. TWRP 3.3.0-0 recovery installed
4. Magisk 19.3 (19300) installed
5. Windows installed platform tools/drivers/etc
What I did...
1. Downloaded the factory image
2. Removed the "-w" from the fastboot update image line in the batch file
3. Ran that batch file... the 1st bootloader bit went fine, but the reboot seemed to not reconnect the phone via usb
4. Unplugging the usb and replugging it successfully seemed to trigger the 2nd radio update bit, and again the reboot left the batch file hanging
5. Unplugged and replugged and the final fastboot update for the image fails saying something about memory (I didn't save what was on screen because CMD.exe closed when I pressed a key).
6. I try to reboot and it gets in a boot loop. Bootloader unlocked screen to all white G screen and back again.
I figured I'm screwed. Might as well give up and do the Sultan ROM...
7. Launch recovery and get into TWRP
8. ADB Push the most recent Sultan Kernel to the phone from my PC
9. Flash Sultan in TWRP
10. Flash TWRP in TWRP
11. Flash Magisk in TWRP
12. Reboot
And here I am looking at my original setup, with all my apps and data. I still have root. No August patch installed, but my Kernel is 4.4.169-Sultan. So....
I have so many questions.
What went wrong?
What went right?
Sultan doesn't seem any different at all... is that part not right?
What do I do now?
boneriffic said:
What do I do now?
Click to expand...
Click to collapse
You can try using a different cable or USB port to see if that takes care of the flashing issue. Sometimes that's all it takes.
I would also double check your fastboot/adb files to make sure they are the latest from Google.

Honor 7x bricked

model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Click to expand...
Click to collapse
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.
AlexLebul said:
model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.
Click to expand...
Click to collapse
I had the same error "error: partition length get error" with my BND-L24. What I did, I found the stock rom from the firmware finder application. Unloaded the boot.img and flashed it without any issues.
I used the guide in the OpenKirin webpage to find the correct rom (you can check the info of your phone using fastboot commands or download multitool and read the phone info there) and to extract the .img files (go to Openkirin webpage and press support for the guides).
Good luck!
i, I have an issue with my phone and would need your help in recovering it back to life.
I have rebranded mate SE to Indian version few months back. so far so good. I have unlocked bootloader and started playing with it by downgrading etc.
the current situation is the phone is bricked with a android pie erecovery and no boot. tried using all the roms visiting various threads here with no luck (including service rom, multi-tool flashing etc)
multi-tool says Orio version 8.0.0.375. I am not able to flash any Oreo images since multitool says partition mismatch (boot, recovery etc) but when I flash 9.0.XX versions or Nougat versions, system is flashed successfully, yet, boot loops and back to latest erecovery.
don't have twrp (despite multitool flashing is successful) all I get is phone boots only to erecovery (latest)
unable to flash any stock recovery or kernels - as multitools says, partition mismatch.
I tried above method of boot.img flashing but multitool says partition error. tried various boot.img (EMUI 5 / 8 / 9) with no luck.
any help? suggestions?
I had a similar issue the last two days. The only thing that worked was rebooting to fastboot. I tried to get back to Oreo but used a method, that bricked my phone since it flashed an older kernel.img. I got it back running by detecting the version of the bootloader with Multitool and fastboot-flashing recovery, kernel and system that have been aligned with that version.
Be aware: You will have two recovery partitions:
- Huawei has renamed the partitions from "recovery"/"recovery2" to "recovery_ramdisk"/""erecovery_ramdisk"
- unlocking the bootloader does only let you flash recovery_ramdisk
- if you boot into recovery (Pwr & Vol+), the image from erecovery_ramdisk gets loaded
- To boot into recovery you are able to flash, it requires three buttons to be pressed (Pwr & Vol+ & Vol-)
- To flash erecovery_ramdisk, you have to flash TWRP into recovery_ramdisk and from there you can install an image into erecovery_ramdisk.
After having flashed back everything to 9.1.0.162, it was possible to format damaged /data and to setup the device via erecovery and WIFI.

LG F400S/K Kitkat unable to install TWRP recovery / unable to install Gapps (solved)

Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.

TWRP logo bootloop and inability to install system

Hello,
I have a strange problem with Galaxy A5 2017 after installing twrp + lineage 18.1. I will explain the problem in sub points.
1) in January on stock software I installed (according to instructions from XDA forum) root, twrp (via ODIN) and bypass with memory decryption. Then I installed Lineage 18.1, Gapps, Magisk and debloater on it to remove unnecessary apps.
2) The phone worked fine until mid-April. Some update was installed and the phone died.
3) The phone wouldn't boot up after the update and only the TWRP logo was looping (logo kept flashing).
4) the phone couldn't boot up, but after I found the only way to get the system to boot up was to enter command "adb reboot bootloader" from windows console. The system booted, but after another reboot unfortunately it was the same thing - the TWRP logo was looping.
5) I managed to upload Lineage Recovery via ODIN, but unfortunately this didn't change anything. Phone was booting to recovery only (but it was working). I tried to update via ADB Sideload from recovery - also without success. Interestingly, the only way to fix it was to fully format with the system partition from recovery and re-upload the system. This worked, and Lineage booted into the android interface, but on the next reboot I unfortunately only had the Lineage loading logo visible for 10-15 minutes - then a reboot into recovery. I had to repeat the formatting and re-upload the system.
6) Interestingly, when I used the combination - lineage recovery, full format, twrp 3.6.1 (via ODIN) - TWRP booted normally and I could install LineageOS. The system would only boot once, and after the next reboot the TWRP logo would loop again.
7) The last problem I noticed is that if I load Lineage system, gaaps package and magiska via TWRP or Lineage Recovery, the system will never boot - either it will loop the logo (if using Lineage Recovery) or the phone will not load the system, it will reset and loop the TWRP logo indefinitely (if using TWRP recovery).
Does anyone know a solution how to restore the phone? Will it still work or for example NAND memory is dead and nothing can be done? Best regards

Categories

Resources