I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img
Related
I was running the 8/3 update of Cyanogenmod 13 just fine on my L24. I downloaded the 8/13 nightly from the CM website and tried to flash it, but for some reason it returned error 7, which shouldn't happen because I already updated to EMUI4/MM firmware two weeks ago (as evidenced by me running the 8/3 version with no problems). However, when I then tried to boot back into system, the phone instead booted back into TWRP. Trying to boot into system in any way (from TWRP menu, through bootloader --> fastboot reboot, et cetera) just reboots the phone right into TWRP again. -_-
Now, I can access only TWRP and bootloader, but whenever I try to flash a .zip in TWRP it immediately reboots back into TWRP. I've tried reflashing TWRP (newest version and older versions), flashing the Cyanogenmod recovery for kiwi, factory resetting, and even reflashing the stock recovery and trying to return to stock EMUI. None of these have worked. (And yes, of course I've tried clearing cache/dalvik.)
At this point I'm just looking to actually boot into system...If anyone has any idea how I might be able to fix this, it would be great.
EDIT: to clarify, when I try to flash the ROM in TWRP, I get the following:
updating partition details
full selinux support is present
MTP enabled
and then an immediate reboot. This is very fast - I had to take a video of it and then freeze the frame to see what the message was.
Boot in fastboot and install your crap? Turn phone off connect to your PC hold Power and volume down until it boots.
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
radiobacter said:
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
clsA said:
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
Click to expand...
Click to collapse
Again, the issue is that I can't install any ROM through TWRP, because trying to instantly reboots the phone and brings me back into TWRP. I've tried reflashing TWRP, but it doesn't do anything.
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
radiobacter said:
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
Click to expand...
Click to collapse
The phone is known to be finicky about sd cards. Try formatting it with TWRP
Sent from my SM-N920T using Tapatalk
Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.
Hi,
After running out of patience i unlocked boot loader on my RN 3 (SD VERSION), and flashed lineage OS, but i did not get VOLTE on it.
To fix that i flashed some files again (and probably forgot to enable developer options), then i rebooted to the phone, and now the bootloader has locked again. I tried booting into EDL mode/TWRP recovery, but the device booted back to lineage OS.
I did not even flash GAPPS just to check if VOLTE is working(basically i booted into the system), now i cannot go to the EDL mode and also not into TWRP recovery. Please guide me on how to get out of this situtaion. I had unlocked bootloader by flashing MIUI 7 through EDL (replaced emmc, and then unlocked it in CMD through unlock-go command)
I am only left with lineage OS with no apps (Tried installing Play store and Play services, that also force closes).
Please help me out with this. I know i messed it up by probably not turning on the developer options before flashing the files.
Please let me know where exactly i messed up so that i do not repeat the mistake. And please guide me on how to unlock bootloader and flash stuff again. Thanks.
Hey just try to find advance restart option in developer options and from their you know what to do
N.G. said:
Hey just try to find advance restart option in developer options and from their you know what to do
Click to expand...
Click to collapse
Yes i found it, I can now boot into the TWRP recovery, but now that the bootloader is locked, i dont think i will be able to wipe or flash any rom. If i wipe i will be in bootloop.
I cant go to EDL. Is it possible to restore MIUI backup with bootloader locked??
Maheshnotani said:
Hi,
After running out of patience i unlocked boot loader on my RN 3 (SD VERSION), and flashed lineage OS, but i did not get VOLTE on it.
To fix that i flashed some files again (and probably forgot to enable developer options), then i rebooted to the phone, and now the bootloader has locked again. I tried booting into EDL mode/TWRP recovery, but the device booted back to lineage OS.
I did not even flash GAPPS just to check if VOLTE is working(basically i booted into the system), now i cannot go to the EDL mode and also not into TWRP recovery. Please guide me on how to get out of this situtaion. I had unlocked bootloader by flashing MIUI 7 through EDL (replaced emmc, and then unlocked it in CMD through unlock-go command)
I am only left with lineage OS with no apps (Tried installing Play store and Play services, that also force closes).
which twrp?
Please help me out with this. I know i messed it up by probably not turning on the developer options before flashing the files.
Please let me know where exactly i messed up so that i do not repeat the mistake. And please guide me on how to unlock bootloader and flash stuff again. Thanks.
Click to expand...
Click to collapse
phone booting or not?...u said gapps force closing...??
which twrp
Maheshnotani said:
Yes i found it, I can now boot into the TWRP recovery, but now that the bootloader is locked, i dont think i will be able to wipe or flash any rom. If i wipe i will be in bootloop.
I cant go to EDL. Is it possible to restore MIUI backup with bootloader locked??
Click to expand...
Click to collapse
What twrp you have have if it is zcx then just flash any rom and if you are wondering check this https://forum.xda-developers.com/re...ide-install-lineage-os-locked-t3546154/page39
And yes don't even try to flash your backup zip from miui backup but if it's twrp backup then you are good to go
ajeshmanu said:
phone booting or not?...u said gapps force closing...??
which twrp
Click to expand...
Click to collapse
Phone is booting. Running lineage 14.1, gapps also flashed now using TWRP.
So basically i can go to TWRP, not to EDL.
N.G. said:
What twrp you have have if it is zcx then just flash any rom and if you are wondering check this https://forum.xda-developers.com/re...ide-install-lineage-os-locked-t3546154/page39
And yes don't even try to flash your backup zip from miui backup but if it's twrp backup then you are good to go
Click to expand...
Click to collapse
I have TWRP 3.1.0.0 and not ZCX. BOOTLOADER IS LOCKED INDEED.
The backup is twrp backup, not MIUI.
So what you are saying is that i should UPDATE THE Current recovery to ZCX through flash image option(IN TWRP) right? And then flash SUPERSU?
And after that CAN I Wipe the currently installed Lineage OS, and then install it again along with CM firmware and VOLTE Patch??? (As mentioned here, https://forum.xda-developers.com/re...t/volte-patches-nougat-based-cm-roms-t3509257)
Please confirm, and if yes, please confirm the order of flashing of above three files.
The main issue is VOLTE.
Also, the backup that i took with 3.1.0.0 can be restored using ZCX Right???
I am not sure but to be on safer side just flash the miui backup first boot in the ROM , set it up ,then try to other stuff and after that try to install zcx twrp if you dont want the unlock your bootloader again
---------- Post added at 02:06 PM ---------- Previous post was at 02:02 PM ----------
Just have a problem that my network goes on and off automatically I am on RR if you face something like this in your ROM
Plz reply
How did u find ur bootloader is locked?
Hi all people,
first of all, I want excuse me for not my perfect English.
I have Honor 9 from few days. And I think to have bricked it.
I have unlocked bootloader correctly.
I have flashed recovery this TWRP recovery with the intention to proceed to root with Magisk or SuperSu. I accidentally and unconsiuosly do factory reset then the phone goes bootloop. (it power off and power on continuously) with the alert "your device has been unlocked and..etc".
Yesterday, reading this thread, I flashed, from fastboot console, boot, recovery and system, the phone resets two/three times then goes to eRecovery where I do a factory reset.
After a factory reset the phone works correctly and seems successfully unbricked. So I re-flash TWRP recovery.
But this morning, during the attempt to install from TWRP one between Magisk or SuperSu (I don't succeed to do it beacuse the phone was crypted and I don't see zip files from TWRP). I have reset the phone but goes bootloop again.
I tried to re-flash boot, recovery, system and cust more (that I don't have flashed yesterday). Now the phone goes eRecovery and ask me to connect to download latest version and recovery, but don't ask me to do a factory reset.
Now I don't know what I can do.
How I can solve this situation? I want only unlock bootloader (done!), install TWRP and have root permission. Now I don't think to change rom.
Something similar happened to me. It seems like the TWRP provided has some issue..... After installing TWRP I had a bootloop problem. I have resolved installing Magisk. It seems that Magisk patchs something. If you can access TWRP try to install Magisk (put the zip file on external sd). In other words: copy magisk zip on sd card - during the bootloop you have the chance to power off phone - Power off - Power on in recovery mode. If you have TWRP correctly installed Honor should go in recovery using TWRP . Install Magisk and see what happens...
unvisigoth said:
Something similar happened to me. It seems like the TWRP provided has some issue..... After installing TWRP I had a bootloop problem. I have resolved installing Magisk. It seems that Magisk patchs something. If you can access TWRP try to install Magisk (put the zip file on external sd). In other words: copy magisk zip on sd card - during the bootloop you have the chance to power off phone - Power off - Power on in recovery mode. If you have TWRP correctly installed Honor should go in recovery using TWRP . Install Magisk and see what happens...
Click to expand...
Click to collapse
I have tried to flash TWRP recovery again to do install Magisk from sd card. I have done it but the phone doesn't work fine.
So I have put rommco05 TWRP Backup into sd card then restored it from TWRP restore (boot and vendor img). Now the phone seems have bootloader locked, in fact I don't have bootloader warning at the power on. Now in fastboot mode the phone says me that I have Phone locked and FRP unlocked.
How can I exit from this situation?
Try this
Killus3 said:
Hi all people,
first of all, I want excuse me for not my perfect English.
I have Honor 9 from few days. And I think to have bricked it.
I have unlocked bootloader correctly.
I have flashed recovery this TWRP recovery with the intention to proceed to root with Magisk or SuperSu. I accidentally and unconsiuosly do factory reset then the phone goes bootloop. (it power off and power on continuously) with the alert "your device has been unlocked and..etc".
Yesterday, reading this thread, I flashed, from fastboot console, boot, recovery and system, the phone resets two/three times then goes to eRecovery where I do a factory reset.
After a factory reset the phone works correctly and seems successfully unbricked. So I re-flash TWRP recovery.
But this morning, during the attempt to install from TWRP one between Magisk or SuperSu (I don't succeed to do it beacuse the phone was crypted and I don't see zip files from TWRP). I have reset the phone but goes bootloop again.
I tried to re-flash boot, recovery, system and cust more (that I don't have flashed yesterday). Now the phone goes eRecovery and ask me to connect to download latest version and recovery, but don't ask me to do a factory reset.
Now I don't know what I can do.
How I can solve this situation? I want only unlock bootloader (done!), install TWRP and have root permission. Now I don't think to change rom.
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-9/help/bootloader-locked-help-to-enable-usb-t3683145
Rommco05 said:
Again unlock bootloader
Click to expand...
Click to collapse
I have unlocked bootloader again and do a factory reset from TWRP recovery, now the phone seems works correctly!!!:good:
Now I should try to root the phone with Magisk or SuperSu, right?
I have a question about TWRP. From TWRP's file manager I don't see the files that I put in the internal memory. It's because I have used finger print to lock the phone that encryptes files?
raw_jay said:
https://forum.xda-developers.com/honor-9/help/bootloader-locked-help-to-enable-usb-t3683145
Click to expand...
Click to collapse
This is to re-brand the phone from Chinese to EU version...I don't think is my case.
Rommco05 said:
Take a backup before make root. You don't see files because is some issue with decryption in TWRP. I achieved root with Magisk but I don't remember exactly steps
Click to expand...
Click to collapse
I think it's too late
Anyway I can re-flash all thing from begin.
Then I can't use TWRP with the phone encrypted ( PIN, password, fingerprint, etc...) ?
Rommco05 said:
I'm not sure about thatz Huawei roms are encrypted somehow by default
Click to expand...
Click to collapse
After I have installed Magisk (v14.0) now I have problem with google play services which don't download and do updates apps.
If I do a factory reset again I can solve it?
Update:
After I done a factory reset from TWRP recovery
and formatting data partition the phone seems working perfectly (I don't know why, but before format data the phone says me that I have only 150mb of memory space)
I say "seems" because there's something getting me in trouble, for example, I don't have anymore ringtones in the settings menu.
And I don't know if I have lost something else.
Exists a possibilty to restore all contents of the phone?
You could try this and flash your phone back to stock. But then you would need to unlock your bootloader and install TWRP again. Another way would be to unpack an image of your ROM and flash system and other parts via fastboot. Of course this could be risky and you could brick the device.
Meranico said:
You could try this and flash your phone back to stock. But then you would need to unlock your bootloader and install TWRP again. Another way would be to unpack an image of your ROM and flash system and other parts via fastboot. Of course this could be risky and you could brick the device.
Click to expand...
Click to collapse
If I understand it well...
I have 2 options:
1) Rebrand the phone and flashin, then at end I have back the phone stock.
2) Unpack the image of ROM (what it means?) and flash system and other parts via fastboot. (Which are those parts? How?) But this procedure is more hazardous then rebrand procedure?
I have understand right?
1. Yes, correct. I would recommend that. Everything is explained in the thread I linked. Of course everything you do could potentially harm your phone, but you should know that already.
2. Get an update.app file for your specific phone model (there are threads already here, just search a bit, or use Firmware Finder), open it with the Huawei Update Extractor and extract the parts you want to flash (like system or recovery). Then flash them via fastboot. I tried this because I was in a situation like yours, but it didn't work for me. But in theory it could, because you would replace the faulty parts of your firmware.
Killus3 said:
I have understand right?
Click to expand...
Click to collapse
Could you solve your problem?
Meranico said:
Could you solve your problem?
Click to expand...
Click to collapse
Hi, I don't say it because I have replaced the phone with another same.
Now I'm starting to unlock bootloader, installing recovery TWRP and rooting the phone.
I hope to avoid bootloop this time.
Goodmorning everyone!
Yesterday I have:
- Unlocked bootloader correctly!
- Installed TWRP correctly!
- Make a TWRP Backup of all partitions of the device, except data partition because TWRP gives me an error during backup attempt.
- Then I start the device.
- After start the device I go to recovery TWRP to install Magisk, but the phone goes bootloop.
After reboot 2-3 times on the screen appears for a few moments a message of eRecovery that have restored something but I don't know. Then the device shows me the eRecovery that asks me to make a factory reset.
At this point I shutdown the device, go in TWRP to flash Magisk unistaller and the device goes out bootloop and works fine but without root.
How I can solve this problem and install Magisk and have root finally?
Some question:
-When I flashed TWRP (via fastboot) and I configurate it, example language, hours, etc... TWRP don't save the settings, in fact when I go in TWRP again I do remake the settings. Why?
-Then I go in sdcard I don't navigate files, I see folders with casual characters. This is an effect of encryption of the device?
Killus3 said:
Goodmorning everyone!
Yesterday I have:
- Unlocked bootloader correctly!
- Installed TWRP correctly!
- Make a TWRP Backup of all partitions of the device, except data partition because TWRP gives me an error during backup attempt.
- Then I start the device.
- After start the device I go to recovery TWRP to install Magisk, but the phone goes bootloop.
After reboot 2-3 times on the screen appears for a few moments a message of eRecovery that have restored something but I don't know. Then the device shows me the eRecovery that asks me to make a factory reset.
At this point I shutdown the device, go in TWRP to flash Magisk unistaller and the device goes out bootloop and works fine but without root.
How I can solve this problem and install Magisk and have root finally?
Some question:
-When I flashed TWRP (via fastboot) and I configurate it, example language, hours, etc... TWRP don't save the settings, in fact when I go in TWRP again I do remake the settings. Why?
-Then I go in sdcard I don't navigate files, I see folders with casual characters. This is an effect of encryption of the device?
Click to expand...
Click to collapse
Answers to all your concerns go here mate---> TWRP doesn't decrypt data. Done.
Hence: weird folders in there, nowhere to store its settings prefs, about Magisk it's another story, if you want root go SuperSU latest beta.
Regards.
a basically did what that guy did, got root installed via TWRP but my google apps are all busted.
I tried flashing the update_data_full_public.zip and update_full_hw_usa.zip I found using the russian device lookup link switching trick but I the HW errored when I tried to flash it in TWRP and my play store still broken.
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Do following, instead of flashing your recovery.
Use this method boot and flash Magisk. Reboot back to your system and install Flashify and install your choosen Recovery with it
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
in stock rom you need to flash magisk right after flashing twrp else it will get replaced by stock
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
What the post above says is correct. However, if you don't want Magisk, after flashing TWRP, reboot into recovery and then into system. You may retain TWRP. However, this doesn't work for everyone.
Hi all, I fixed the issue by completely wiping my phone via TWRP and clean flashing pixel experience ROM. After rebooting on pixel rom TWRP persists.
It appears that MIUI rom has something that keeps reverting it to stock MI-recovery.
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP once more. That's it! You have just overwritten the stock recovery and are now on TWRP!! Now you can reboot to system and TWRP will remain on your device. There's no need to flash Magisk etc if you want just TWRP and nothing else.
Rowdyy Ronnie said:
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP again. That's it! You have just overwritten the stock recovery and are now on TWRP!! There's no need to flash Magisk etc if you just want TWRP and nothing else.
Click to expand...
Click to collapse
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
jonske said:
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
Click to expand...
Click to collapse
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Rowdyy Ronnie said:
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Click to expand...
Click to collapse
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
jonske said:
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
Click to expand...
Click to collapse
How did you fix it?