Joyeuse: Phone stuck in "the system has been destroyed" after recovery flash
Hi,
I've messed up my global Redmi Note 9 Pro (Joyeuse).
I had various issues updating to Xiaomi.EU 110.0.5 because of the dynamic storage while using PBRP 2.9.1 and 3.0 unofficial builds which I found on XDA.
So I ended up using the TWRP referenced here: https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ The multi-language version.
This finally installed the ROM, But it never passed the boot animation.
I tried various things with deleting data/reset which can be found when googling for that state, but they did not help.
So I though maybe this TWRP build is the culprit and let's check what happens if I go back to PBRP.
Big Mistake.
After flashing PBRP I received a "the system has been destroyed" message when trying to reboot.
I used the fastboot install batch file for stock 11.0.4 to get back to a working system which of course has the system recovery.
But now every time I try to flash a custom recovery, no matter which one I try (and they all installed fine before) I get the system destroyed message at reboot (no matter if to system or recovery)
Any ideas how to fix this so I can get a decent recovery?
Smuggle a PBRP recovery into the stock flash process?
thx
afx
a.f.x. said:
Hi,
I've messed up my global Redmi Note 9 Pro (Joyeuse).
I had various issues updating to Xiaomi.EU 110.0.5 because of the dynamic storage while using PBRP 2.9.1 and 3.0 unofficial builds which I found on XDA.
So I ended up using the TWRP referenced here: https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ The multi-language version.
This finally installed the ROM, But it never passed the boot animation.
I tried various things with deleting data/reset which can be found when googling for that state, but they did not help.
So I though maybe this TWRP build is the culprit and let's check what happens if I go back to PBRP.
Big Mistake.
After flashing PBRP I received a "the system has been destroyed" message when trying to reboot.
I used the fastboot install batch file for stock 11.0.4 to get back to a working system which of course has the system recovery.
But now every time I try to flash a custom recovery, no matter which one I try (and they all installed fine before) I get the system destroyed message at reboot (no matter if to system or recovery)
Any ideas how to fix this so I can get a decent recovery?
Smuggle a PBRP recovery into the stock flash process?
thx
afx
Click to expand...
Click to collapse
You've posted in the wrong section.
I'd suggest flashing the vbmeta.img with fastboot before flashing recovery to disable verified boot.
lalibm said:
You've posted in the wrong section.
Click to expand...
Click to collapse
Which one would be the right one?
I'd suggest flashing the vbmeta.img with fastboot before flashing recovery to disable verified boot.
Click to expand...
Click to collapse
The stock install script already does that. So me thinks that would not change anything as I tried stock and then flash custom recovery several times.
fastboot.exe $* flash vbmeta `dirname $0`/images/vbmeta.img
if [ $? -ne 0 ] ; then echo "Flash vbmeta error"; exit 1; fi
fastboot.exe $* flash vbmetabak `dirname $0`/images/vbmeta.img
if [ $? -ne 0 ] ; then echo "Flash vbmetabak error"; exit 1; fi
fastboot.exe $* flash recovery `dirname $0`/images/recovery.img
Click to expand...
Click to collapse
cheers
afx
a.f.x. said:
Which one would be the right one?
The stock install script already does that. So me thinks that would not change anything as I tried stock and then flash custom recovery several times.
cheers
afx
Click to expand...
Click to collapse
Try other recovery with te recovery from rr Telegram group Will work
Los recovery also Will work
canteo said:
Try other recovery with te recovery from rr Telegram group Will work
Click to expand...
Click to collapse
I am unfortunately not on Telegram;-(
Someone sent me this, but the link s recursive ;-(
https://t.me/pbrp_testers/9182
cheers
afx
a.f.x. said:
I am unfortunately not on Telegram;-(
Someone sent me this, but the link s recursive ;-(
https://t.me/pbrp_testers/9182
cheers
afx
Click to expand...
Click to collapse
https://www.dropbox.com/s/6k9w18cwof5w7yx/recovery.img?dl=0
flash with fastboot and will work, it is pbrp miatoll
canteo said:
https://www.dropbox.com/s/6k9w18cwof5w7yx/recovery.img?dl=0
flash with fastboot and will work, it is pbrp miatoll
Click to expand...
Click to collapse
Thanks, that worked.
I did try integrating it into the stock update script, just in case, still had stock recovery after that. Strange.
Explicitly flashed it afterwards and got PBRP. Great!
Immediately flashed xiaomi.eu 11.0.5.
Tried to sideload Magisk, but that seems to be wonky in this recovery (when I switch PBRP to sideload adb no longer sees the device).
Now I can only get to PBRP, no system boot and PBRP while it worked on the first start now has problems decrypting the device ;-(
thx
afx
a.f.x. said:
Thanks, that worked.
I did try integrating it into the stock update script, just in case, still had stock recovery after that. Strange.
Explicitly flashed it afterwards and got PBRP. Great!
Immediately flashed xiaomi.eu 11.0.5.
Tried to sideload Magisk, but that seems to be wonky in this recovery (when I switch PBRP to sideload adb no longer sees the device).
Now I can only get to PBRP, no system boot and PBRP while it worked on the first start now has problems decrypting the device ;-(
thx
afx
Click to expand...
Click to collapse
remember to unmount system and vendor before flash a rom, also i use to flash magisk with the recovery without issues, iḿ with eu rom on joyeuse
flash magisk after boot the rom, will be better
a.f.x. said:
Which one would be the right one?
The stock install script already does that. So me thinks that would not change anything as I tried stock and then flash custom recovery several times.
cheers
afx
Click to expand...
Click to collapse
The correct section would have been the Q&A as you've posted in ROMs and Kernels.
What I meant was to flash the modified vbmeta to force disable avb (android verified boot) which could have been easily found on the telegram group, the purpose of which is to prevent the "system destroyed" scenario from happening as the stock vbmeta img has avb enabled. You flashing pbrp somehow kept triggering the flag which resulted in system destroyed repeatedly on each attempt.
Additionally, I have read about pbrp giving some joyuse users trouble with encryption. I'd highly suggest that you join the telegram group for help regarding this. I would have gladly helped you with each step but I own curtana. Hope you get the device up and running again soon. Cheers!
lalibm said:
The correct section would have been the Q&A as you've posted in ROMs and Kernels.
Click to expand...
Click to collapse
Ok, me thought this is a recovery issue and as there is currently only alpha software.
What I meant was to flash the modified vbmeta to force disable avb (android verified boot) which could have been easily found on the telegram group, the purpose of which is to prevent the "system destroyed" scenario from happening as the stock vbmeta img has avb enabled. You flashing pbrp somehow kept triggering the flag which resulted in system destroyed repeatedly on each attempt.
Click to expand...
Click to collapse
I do not think that this is the issue in this case. By now I can install the PBRP that was kindly provided via dropbox.
Me thinks something was weird in the TWRP I installed that triggered this.
Since I tried the PBRP provided here, I no longer see this message.
Additionally, I have read about pbrp giving some joyuse users trouble with encryption.
Click to expand...
Click to collapse
I can get into PBRP after flashing stock, before setting the encryption password in stock,
At that time this is all with some default or null key and PBRP seems to be ok with it.
I'd highly suggest that you join the telegram group for help regarding this.
Click to expand...
Click to collapse
Let's just put it that way, Telegram is thanks to some analysis I did in a previous job, definitely not something I am keen on.
thx
afx
If Bootloader is unlocked, flash fastboot rom
Otherwise EDL
https://github.com/Szaki/XiaomiADBFastbootTools try this
You guys are responding to posts made on 5th September! I think the OP moved on long ago (on 5th September, actually) ...
Related
I was read https://topjohnwu.github.io/Magisk/install.html. That link describe how to install Magisk in our device in few ways. I was interested "Boot Image Patching" section that tell us about rooting device without TWRP.
Before this, I have 5 redmi devices and 3 of it were rooted-well via TWRP. 1 bricked (totally bricked) :laugh: and 1 still un-rooted (Redmi 6A-cactus).
My spec of Redmi 6A are:
Security Level Patch: 2019-03-01
MIUI Version: Global Stable 10.2.8.0 (oCBMIXM)
Unlocked: False (i know that i should unlocked it later, i still waiting my 360 hours )
RAM: 2GB
Storage: 16GB
Since i found that link, i still wondering and keep searching about: "is anybody succesfull root their device (especially Redmi 6A with same spec above) with "Boot Image Patching" way?
if any, please let me know. i just want to hear their review and (of course) their experience.
thanks
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
Nice... i'll try that soon when my 360 hours run out..
thanks.
Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?
adista said:
Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?
Click to expand...
Click to collapse
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:
adista said:
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:
Click to expand...
Click to collapse
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk
ahhl said:
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk
Click to expand...
Click to collapse
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.
adista said:
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.
Click to expand...
Click to collapse
Use the TWRP-1020 instead, it works much better.
hi, i followed this video and i succes for install twrp https://www.youtube.com/watch?v=522RzZ7_uRM&t=254s
jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Someone said to encrypt the data on settings, i don't know how though, if you fix it, next time, don't disable the forceencrypt.
Can you post questions in the questions and answers section next time?
i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk
ahhl said:
i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk
Click to expand...
Click to collapse
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.
I have a similar problem
I was rooting my redmi 6a and now its bricked
First i intall the twrp, then i flash the Magisk with DisableEncryption, the first boot work fine, i update the magisk app and the new version isnt compatible with the magisk installed
Well i repeat the steps and then i lost the signal, in that moment i didnt know it is the IMEI lost, then i try to install Lineage OS 15.1 GSI for Redmi6a cause i think that is the solution
but the system dont boot, only boot the Xiaomi Tittle with "unlocked" (I unlock the phone before) and then get me to TWRP
Im only one with this problem?
I try use the MiFlashTool for flash the stock rom but not work, now im trying with MiFlashTool flash the MIUI9 and MIUI10.2 and other versions
I think, the problem maybe is the Boot.img
(Sorry for my bad English)
Edit-
I dont have any backup lol
---------- Post added at 02:23 AM ---------- Previous post was at 02:01 AM ----------
jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
¿Can you share your correct steps to have the Lineage OS 15.1 in Redmi6A Please?
ahhl said:
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.
Click to expand...
Click to collapse
This "contact manufacturer" error happens when you disable dm-verity, you can install Magisk without disabling it.
whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Sorry for late post
Just make sure that you flash Fastboot ROM, not just STOCK ROM. I did that last time when my IMEI/Baseband are gone. Of course it will wipe all of your data. Just be prepare for it.. :laugh:
davidhozic said:
Can you post questions in the questions and answers section next time?
Click to expand...
Click to collapse
Ups sorry.. i didnt notice that is exists :silly:
No, it wasnt like that :laugh:,, actually i did confused where should i put this question, because in Question & Answers (for me) the topic just too general and i was thinking that my question (maybe) still in development because i didnt found that in Question & Answer...
All my fault, Sorry again,
jonaaa said:
Use the TWRP-1020 instead, it works much better.
Click to expand...
Click to collapse
that just un-official TWRP, right??
i will try that in this weekend. Last time i remember that i can not boot into twrp. Till now, my devices still unrooted. I flash it back to stock ROM. But, when OTA update notification comes and reboot for installing, it give me bootloop into twrp (not to system), and that's mean my TWRP still inside i just cannot boot into.
so, i'll try that TWRP-1020 this weekend. Thanks.
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
I unlocked the device bootloader thanks to Narender, and tried to flash Lineage OS 18.1. After flashing the ROM and vendor zip files, I switched the current slot and restarted to fastboot mode. Then I flashed the vbmeta image. Then I rebooted to recovery to check the current slot. Slot was as expected, so I rebooted the system.
Then, TWRP gave me an alert saying "No OS is installed" before rebooting. I was unsure what was the reason for it because the ROM was just installed, so I rebooted the system.
After that, device went straight into fastboot mode after "Android One" screen. No matter which option I choose from there, it keeps restarting the bootloader. I tried using "fastboot reboot recovery" but that did not work either. Then I tried to change the active slot of the device using fastboot commands. That did not help either.
Now I'm stuck with a Nokia 7.2 that can only be turned off or start in fastboot mode. Is it bricked beyond saving? I just want to install TWRP in any of the slots and install any usable ROM. Any help is deeply appreciated.
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Chevindu said:
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Click to expand...
Click to collapse
Follow this and DM if you have doubts
Edit: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
Follow this and DM if you have doubts
Click to expand...
Click to collapse
I actually installed few ROMs after my previous reply. But none of them had working WiFi, which is a deal breaker. Went back to stock ROM.
If you are interested I could help you
Ujwal2000 said:
If you are interested I could help you
Click to expand...
Click to collapse
Hey, thanks. But I thought it's not possible due how the signatures in security patches work. So I gave up. Maybe I misunderstood. Linking to Raghu's reply below.
Post in thread '[OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |'
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Ujwal2000 said:
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Click to expand...
Click to collapse
Yup, pretty much what I experienced too.
I haven't tried extracting boot image and flashing it manually. At this point to be honest, I'm reluctant to put my hands on it again without having a clear step-by-step guide about it.
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I realize I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I relaise I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Click to expand...
Click to collapse
Thanks Ujwal, appreciate it. I'll have a look.
Hello XDA developers, I'm in urgent and I have a really big problem. It sounds funny but, I deleted my realme ui recovery ,_,
I was trying to install PPUI 4.1 on my Realme 7 but I saw a tutorial that you have to erase the recovery to install TWRP. Please, I need a solution of how can I get it back. I also tried flashing a lot of recoveries and their vbmeta but nothing works. Sadly.
Edit: I'm on RMX2151_11_C.17 | Realme UI 2.0 Latest version
Here is the stock recovery
Chenes said:
Here is the stock recovery
Click to expand...
Click to collapse
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Click to expand...
Click to collapse
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, your data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Chenes said:
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, you're data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Click to expand...
Click to collapse
Can I have that Telegram group invite?
iOussamato_ said:
Can I have that Telegram group invite?
Click to expand...
Click to collapse
Realme 7 • Narzo 20 Pro • Global
Welcome To Realme 7 | Narzo 20 Pro Group • RM6785_updates(official-A12/A13)- @RM6785 / https://t.me/realme7updater • RM6785_Gaming- @RM6785Gaming • Realme 7 Cloud: @realme_7_cloud
t.me
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
Click to expand...
Click to collapse
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
SubwayChamp said:
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
Click to expand...
Click to collapse
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
SubwayChamp said:
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
Click to expand...
Click to collapse
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Chenes said:
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
Click to expand...
Click to collapse
Yes my bootloader is already unlocked
iOussamato_ said:
Yes my bootloader is already unlocked
Click to expand...
Click to collapse
Then you can root your phone 1st then backup your files to a computer and use migrate backup to backup app data. Note that migrate backup is limited to 4gb. Then do the fastboot flash i mentioned before
iOussamato_ said:
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Click to expand...
Click to collapse
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
SubwayChamp said:
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
Click to expand...
Click to collapse
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
iOussamato_ said:
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
Click to expand...
Click to collapse
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
SubwayChamp said:
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
Click to expand...
Click to collapse
Do you know a tutorial of how to use SPFlashTool?
iOussamato_ said:
Do you know a tutorial of how to use SPFlashTool?
Click to expand...
Click to collapse
How to use SP Flash Tool
This is a step-by-step tutorial on how to flash stock rom to a Mediatek device using Smart Phone Flash tool. SP Flash tool is one application you could find very useful in fixing extreme cases of a br
www.hovatek.com
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
iOussamato_ said:
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
Click to expand...
Click to collapse
You have to boot to recovery using hardware buttons (PWR + vol. down), in regard to orange state, this is absolutely normal when bootloader was unlocked, it's not an issue but a cosmetic thing.
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do