Related
I have to think I'm not the first to be in this situation but my searches didn't turn up anything that looked familiar.
I rooted the stock phone and installed TWRP 2.6xx a month or two ago with no issues. Everything's been running great and I decided it was time to make another backup using TWRP.
After a successful backup I wiped dalvik and cache out of habit and went to reboot -- TWRP said I was not rooted and wanted to know if I wanted to install SuperSU? This question was unexpected since I'd been rooted for a long time, and I decided to just say yes. The phone rebooted and stopped at the Samsung Galaxy S4 boot screen. I did up-volume reboot to recovery, but it seemed to hang at the TWRP blue screen -- I later discovered it will eventually get to the menu after a minute or two of the blue screen. I tried wiping cache and dalvik again and rebooting -- every time I try to reboot now it asks if I want to install SuperSU -- whether I say yes or no seems to make no difference -- I've tried both several times. Every time it hangs at the Samsung boot screen, or it takes forever to get to TWRP if I'm booting to recovery.
I've tried wiping cache, dalvik and data with no improvement. I finally tried formatting data, but again no improvement. I also tried restoring my backup several times and wiping cache and dalvik but still stuck.
I prior to today's problems I'd used TWRP a number of times and I don't recall it asking the SuperSU question, so I am thinking that is the key to this problem, and I'm wondering if anyone knows what it means?
You need to go to 2502 twrp, 26+ has hanging problems and possible Partition issues, also what rom are you on? Do you need to flash super su along with the rom /gapps?
Here's the twrp forum for us SPH-L720
The last page has a download link for the most stable build for us good luck!
http://forum.xda-developers.com/showthread.php?t=2262999
I'm running what came on the phone, just unlocked, rooted, and installed TWRP.
I ran CM10.1 on my previous phone and currently on my tablet, but my impression from running it previously is CM is a downgrade in voicemail functionality (you get these annoying text messages and have to call the voicemail), and I'm assuming it doesn't support the special GS4 hardware features like being able to hover your finger.
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Nerva said:
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Click to expand...
Click to collapse
How did you root? CF auto root also installs SuperSU
Do you have a back up from when you were rooted? IF twrp keeps giving you problems, use cwm, are you able to get past the Samsung boot..
Yeah that's what I did back when I rooted it months ago. I tried running CF auto root again today and it didn't work, so I ran it from Odin and it did work that time, but there was no change -- still hangs on the Samsung boot screen, although now I'm back to the stock recovery. So I tried installing the stock MF9 firmware from Odin -- still hangs on the boot screen. I don't know what to do at this point...
After mf9 install avd stock recovery did you factory reset
Yes, I did a factory reset -- followed the video instructions by qbking77. Still hangs on the boot screen.
Take out battery.. Put back in. Go to stock recovery, holding all 3 buttons volume up factory reset.. If you used odin abd flashed mf9 it should fix you?
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Well I guess I tried man, someone who has more knowledge should chime in now
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
This
http://forum.xda-developers.com/showthread.php?t=2400192
Im also stucked with the same problem!! After flashing my rom succesfully it just ask ur device is not rooted swipe to install!! I tried all the posiblities!! but i stuck with the boot image!! pls help me!!
From experience it sounds like you should head over to sammobile and Odin back to stock and start fresh.
1. Odin to stock
2. Root phone
3. Put desired recovery
4. Flash ROM (be sure to read dev install instructions some require reboot of recovery after wipe)
5.try to restore backup (best if you flash ROM that is backup then restore backup)
6.if you went into nae or ng2 you cannot downgrade to me
7.google has many solutions
Sent from my SCH-I545 using XDA Free mobile app
Sorry for necro, but did anyone figure out a solution to this? This just happened to me.
Just Reflash it
We have the same issue, tried to install supersu binary, after installing through twrp recover, my phone went bootloop, as i've tried to search the internet, the issue doesn't fix by by most of the users unless they reflash their device. though its a bit hassle starting from zero, but atleast, you got ur device back
This helps me:
1. Run Odin on your computer and, after entering download mode on your phone, establish a connection between your devices with the help of the USB cable.
2.Note: for download mode – power off your smartphone and then press and hold, at the same time, the Power, Volume Down and Home buttons.
3.Odin will try to recognize your device; if everything works as expected, on the program the “added” message will be displayed and the ID:COM field will be turned yellow, or blue. (Note: if that’s not happening, unplug the USB connection, close Odin, force restart your phone and reinstall the USB drivers on your computer before retrying the steps from above)
4.From the program click on the “PA” button and load the custom recovery image; don’t check Re Partition and Auto Reboot options.
5.When done, click on “start” and wait while TWRP recovery is being added on your phone
6.In the end, Odin will display the “pass” message and the ID:COM filed will be turned green (or other color) with message - RESTART; you can then remove the USB cord and reboot your smartphone.
I have had this prob on a few things , if you have a backup,flash any mod that will go to the device will do then run the backup and reflash should work .and if you have twrp try to reformat all but the system and see if that helps.
Good luck.
Hi to everyone.
Today, I installed the TWRP and the ROM and both were installed correctly on a Le Pro3 X722. The problem started when the Google services were updating. Suddenly, the phone restarted and entered in a bootloop. I was not even able to enter the TWRP. The page freeze on LE-Recovery logo and then crashed (fill full of lines). I disconnected the battery for a while and then, I was able to enter the TWRP for 2 time but recovery crashes in few seconds. I wanted to wipe and install a clean rom but I cannot enter TWRP anymore.
Please, Is there someone that could help me?
Thank you very much in advance
PS. My phone is not recognized via ADB. I tried with the AIO Tool but my device is not detected.
Hi, I followed the whole process for Qfil explained here:
Leeco Le Pro3 x720 Hard Brick
So the phone was running lineageos 15.1 nightly from 22.08 which i guess was kind of really unstable (even opening twitter in the morning could turn off the device. It could be turned back on right away though), xposed framework v90 w/yt...
forum.xda-developers.com
Installation was correct but nothing change in my phone:
- same start page and bootloop
- Same problem trying to access the recovery.
Now, i can connect via fastboot and I would like to install a fastboot rom (preferable EUI stock 20) but I cannot find one. All links are dead.
Thank you very much in advance
So, my stupid completely stock A2017U started bootlooping (hey, did LG make these?). cache wipe, factory reset all didn't help, so I'm down to trying to do the full SD upgrade. However, the phone won't stay booted long enough for me to get into settings to enable OEM unlocking. Is there a way to do it from adb in recovery? The phone stays booted perfectly fine in recovery, so I'm guessing something got corrupted in a system partition somehow (emmc cell failure maybe?).
If not, I'll have to EDL it first, but I'd rather stay official if possible.
adb sideload is giving me problems, but it maybe that I don't have enough memory for that.
I take it you are not rooted? Reason I ask is I just experienced a boot loop after updating SuperSU. The solution was to install the previous version of SuperSU from recovery.
MyronAz said:
I take it you are not rooted? Reason I ask is I just experienced a boot loop after updating SuperSU. The solution was to install the previous version of SuperSU from recovery.
Click to expand...
Click to collapse
No, I'm stock everything. If I could get the damn thing to boot up enough again to get into settings, I could enable OEM Unlocking and then use the sd card method. But it won't stay up that long through the setup wizard.
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.
Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?
I was wiping my Cache in TWRP on Pixel Experience 10 and I accidentally wiped data as well. Despite this, I figured the worst thing that would happen is I would have install my apps again.... Instead my phone would directly boot to recovery, and the internal storage directory was now a bunch of folders with unrecognizable filenames. ****.. I figured if I format data I would at least get it to boot again. Nope still straight to recovery. So I thought I would reinstall the ROM by flashing miui_DAVINCI_V11.0.2.0.QFJCNXM_f6f375d6c4_10.0, formating it again then installing PixelExperience_davinci-10.0-20191225-0807-OFFICIAL. Still going straight to recovery....
I am worried I've permanently bricked it somehow by wrecking the system partition or something along those lines. Has anyone experienced this have some suggestion on what I could try. Would fastbooting davinci_global_images_V11.0.1.0.PFJMIXM_20191028.0000.00_9.0_global_156b6de73d.tgz possibly fix this? Any help would be greatly appreciated, I really hope I don't need to buy a new phone after this mishap
You're phone is encrypted because it cannot boot probably, but you should be able to enter your password in recovery.. but if you have a bootloop while encryption is enabled sometimes it doesn't recognize the password (in my experience). i know you want to keep some stuff, but what i would do is dirty flash custom rom (and gapps if that is needed for the rom). If that still doesn't want to boot you should clean flash the rom.
I used TWRP from LR team, but the official should also work. If the phone is still not booting you'll have to return to stock i think... Thats what i did.
---------- Post added at 08:10 PM ---------- Previous post was at 08:07 PM ----------
Btw forgot to mention, reverting to stock doesn't really work well with a custom recovery sometimes. I flashed an xiaomi.eu rom from xda which did not work for me. But i downloaded an official full update from Xiaomi and installed it with twrp. I lost twrp, but back at my pc a did not fastboot flash it again, but just only booted so i could flash magisk and go on that road
its the peanut said:
You're phone is encrypted because it cannot boot probably, but you should be able to enter your password in recovery.. but if you have a bootloop while encryption is enabled sometimes it doesn't recognize the password (in my experience). i know you want to keep some stuff, but what i would do is dirty flash custom rom (and gapps if that is needed for the rom). If that still doesn't want to boot you should clean flash the rom.
I used TWRP from LR team, but the official should also work. If the phone is still not booting you'll have to return to stock i think... Thats what i did.
---------- Post added at 08:10 PM ---------- Previous post was at 08:07 PM ----------
Btw forgot to mention, reverting to stock doesn't really work well with a custom recovery sometimes. I flashed an xiaomi.eu rom from xda which did not work for me. But i downloaded an official full update from Xiaomi and installed it with twrp. I lost twrp, but back at my pc a did not fastboot flash it again, but just only booted so i could flash magisk and go on that road
Click to expand...
Click to collapse
I never encrypted it and there is no password prompt from what I can tell. The phone just boots into the main menu of TWRP even after I format and install custom rom.... If I could just get it to boot it would be a success. If I Fastboot to V11.0.1.0.PFJMIXM from V11.0.2.0.QFJCNXM could that pose any problems you think?
rickbos said:
I never encrypted it and there is no password prompt from what I can tell. The phone just boots into the main menu of TWRP even after I format and install custom rom.... If I could just get it to boot it would be a success. If I go from V11.0.2.0.QFJCNXM to V11.0.1.0.PFJMIXM could that pose any problems you think?
Click to expand...
Click to collapse
Well yes.
In these times almost every device has been encrypted straight out of the box... Most of them (correct me if i am wrong). My oneplus 6 is encrypted, and same for my Mi 9T. You don't have to do it cause it's already done by Xiaomi in case of theft or when you lose it. Handy for those situations but a pain when you brick your phone because twrp wont be able to read the data. Now i don't need encryption because i always have my hands in my pockets so I'll know when it gets stolen.
I don't know what recovery you are using but i read that some of them can't read encryption properly. But what i do know is that the latest TWRP by LR team does read it good and can also disable the encryption and have backup working. There is an thread on xda for all available recoverys where its included, you can try the one from LR and maybe it can read it or ask for a password.
You can also try to stick in a USB via OTG (cable or adapter), redownload the files (as i guess the rom and stuff is stored on your phone?) And put them on the usb, mount it in twrp and flash it that way because a usb otg is not encrypted and can be read. I always put my files and backups on the usb otg so i dont screw myself.
Before going to stock just try the LR team TWRP and/or the OTG method, if you can boot the phone properly and unlock it then you should be good. After that you can backup everything and maybe if you want proceed to decrypt the phone.
For decrypting, there is also an xda thread about it using the LR teams twrp, but i will warn you! Back up everything because decrypting requires to format data so you'll probably wipe everything. It's all in those threads
---------- Post added at 09:16 PM ---------- Previous post was at 08:32 PM ----------
I used this website for my stock rom, if you can boot anything try from here (I don't know if it's official, but it worked)
I could not boot my phone, it got in bootloop or back to recovery. I flashed the zip file with twrp from LR and also official version and both worked but for some reason i cannot change my region, its stuck on china and i want it to the Netherlands... But it is not a big deal.
Now be careful, you'll have to choose your device. But when you choose the Mi9T series it also combines the Mi 9, Mi 9T and the 9T Pro... And also region specific.
In my case it was the Mi 9T EEA (europe) and miui V11.0.3 (miui 10). Check it to be sure!
https://c.mi.com/miuidownload/index
I can't remember how to post URL's
(Edit) seems URL's get fixed when posted on auto
its the peanut said:
Well yes.
In these times almost every device has been encrypted straight out of the box... Most of them (correct me if i am wrong). My oneplus 6 is encrypted, and same for my Mi 9T. You don't have to do it cause it's already done by Xiaomi in case of theft or when you lose it. Handy for those situations but a pain when you brick your phone because twrp wont be able to read the data. Now i don't need encryption because i always have my hands in my pockets so I'll know when it gets stolen.
I don't know what recovery you are using but i read that some of them can't read encryption properly. But what i do know is that the latest TWRP by LR team does read it good and can also disable the encryption and have backup working. There is an thread on xda for all available recoverys where its included, you can try the one from LR and maybe it can read it or ask for a password.
You can also try to stick in a USB via OTG (cable or adapter), redownload the files (as i guess the rom and stuff is stored on your phone?) And put them on the usb, mount it in twrp and flash it that way because a usb otg is not encrypted and can be read. I always put my files and backups on the usb otg so i dont screw myself.
Before going to stock just try the LR team TWRP and/or the OTG method, if you can boot the phone properly and unlock it then you should be good. After that you can backup everything and maybe if you want proceed to decrypt the phone.
For decrypting, there is also an xda thread about it using the LR teams twrp, but i will warn you! Back up everything because decrypting requires to format data so you'll probably wipe everything. It's all in those threads
---------- Post added at 09:16 PM ---------- Previous post was at 08:32 PM ----------
I used this website for my stock rom, if you can boot anything try from here (I don't know if it's official, but it worked)
I could not boot my phone, it got in bootloop or back to recovery. I flashed the zip file with twrp from LR and also official version and both worked but for some reason i cannot change my region, its stuck on china and i want it to the Netherlands... But it is not a big deal.
Now be careful, you'll have to choose your device. But when you choose the Mi9T series it also combines the Mi 9, Mi 9T and the 9T Pro... And also region specific.
In my case it was the Mi 9T EEA (europe) and miui V11.0.3 (miui 10). Check it to be sure!
https://c.mi.com/miuidownload/index
I can't remember how to post URL's
(Edit) seems URL's get fixed when posted on auto
Click to expand...
Click to collapse
Thank you for your help. It seems the only way around this is to decrypt it but I am not sure how that is done. I am on the official twrp-3.3.1-0-davinci from teamwin. When I try to reinstall a custom rom it says "E:Unable to decrypt FBE device" before running the rest of the commands. This is still after I have formated data...
rickbos said:
Thank you for your help. It seems the only way around this is to decrypt it but I am not sure how that is done. I am on the official twrp-3.3.1-0-davinci from teamwin. When I try to reinstall a custom rom it says "E:Unable to decrypt FBE device" before running the rest of the commands. This is still after I have formated data...
Click to expand...
Click to collapse
I ran into that FBE message yeah, but i was able to flash. I have decrypted before doing anything. Btw i am not sure but i think the twrp you are using is older then available now, marionofro (correct is misspelled) made a newer i think. But i have had no problems with LR. Seems that people say you can ignore that fbe message if you can proceed.
I'll post the links below that i used. The first one will be the thread for twrp by LR (its combined with a few others to choose from and also a linked thread to how to install) but if twrp is working and you have an usb on the go you could install that version through that way and install as recovery img. Or you have to fastboot flash it. Btw if you flash miui via twrp you will loose twrp and get stock recovery. With twrp the rom didnt seem to want to boot
The other link is for decrypting, but before this try to dirty flash your rom... Or clean flash via LR twrp so you might save the storage (do not wipe internal or format data yet). If that didn't work, then try to decrypt following those instructions, flash the rom you want and then i thing was change something in the extra options with forceencrypt.
Thread collection of multiple twrp versions, recommend the one from LR
https://forum.xda-developers.com/mi-9t/how-to/twrp-versions-xiaomi-mi-9t-t3955946
Tutorial for decrypting, READ IT CAREFULLY and do exactly as said as if you do it wrong you can make it worse. The required and fully working twrp is also linked there i think.
https://forum.xda-developers.com/Mi-9/how-to/tutorial-howto-decrypt-phone-backup-t3930946
Here is also a handy tool for pc to flash certain things, and our device is supported, i used it to temporarily boot twrp to flash certain zips without flashing the recovery. Might be handy for flashing fastboot stuff too.
https://forum.xda-developers.com/mi-9t/development/tool-tool-one-driverstwrpfactory-t4009871
Thank you so much this really helped me out. Unfortunately it seems as though I will have decrypt everytime I load a ROM and I lost my data since I had to format but at least I am having it boot up again. Many thanks from Canada!!!
rickbos said:
Thank you so much this really helped me out. Unfortunately it seems as though I will have decrypt everytime I load a ROM and I lost my data since I had to format but at least I am having it boot up again. Many thanks from Canada!!!
Click to expand...
Click to collapse
Happy to help.
Thats the down part of encryption/decryption... You have to take in account that you will loose data. That is why i back everything up on an external device that i can plug into the phone by OTG method.
Greetings from Holland
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
Harshadd30 said:
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
Click to expand...
Click to collapse
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
zgfg said:
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
Click to expand...
Click to collapse
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
Make sure you use the latest official TWRP for davinci
Which "notifications" - it's about Passwords and Security in Android. You can try by removing Android unlock pin/pass, reboot to Android and set it again and then try with TWRP.
Again, make sure you use up-to-date TWRP, best the official
twrp-3.5.2_9-0-davinci.img (if you were not familiar with and TWRP does not ask, maybe you are on an ancient and maybe some unofficial TWRP)
HI, I updated to V12.1.4.0.RFJMIXM and tried to install the latest TWRP but booting into recovery mode TWRP is in this like read only mode and dosnt bring up the usual thing to decrypt your files. It says unmodified system partition. Keep system read only? TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root your device. Then it says keep read only or swipe to allow modifications. Any suggestions? Tried removing and adding security pin but didnt work
I need it to install magisk. I tried patching a recovery image with magisk which worked. But trying to boot to magisk with recovery dosnt work. I hold the keys and then when it vibrates let go but it always goes to stock recovery. Not system with magisk as it talks about.
Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
This seems like a bootloop. Did you change any roms before this happened? You might have to format (not wipe) your data partition which unfortunately will also delete all your files from the phone's internal storage.