Related
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Try to install the stock recovery and ramdisk.
+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.
After I flashed a treble gsi, I need to flash stock recovery?
Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3
Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.
Here I bring to you the official Havoc-os 4.X ROM Android 11 and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
Remember I am not a developer, if you are presenting any bugs let us know and you can contact the Havoc team on Telegram
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32, the version that i tested Havoc-OS-v4.5-20210208-Official-arm64-ab.img.xz
Bugs
videos recorded with the default camera do not play
Update: Install the NGCam_7.4.104-v1.8-fix.apk Once the application is installed open it take a photo close the application, this will create a folder in the SD called Gcam, inside the Gcam folder create a folder and call it Config7 and inside this place the XML file Redmi 8 GCam 7.4.104.314953318 G_Modder.xml restart the application and you're done
the only bugs that have is slow motion record not work for now
Automatic brightness does not work
Update: to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 ( use root explorer ) and reboot ..... problem solved
the necessary files are at the end of the tutorial
Steps
Note: I did the installation coming from Mui 12.EU, and there was no problem in the installation process or in the boot process
If you come from Miui12 .EU or any other GSI Rom go to step 4, if you come from the Rom stock follow the this steps
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Install a custon recovery, if you dont know how to, follow this post: https://c.mi.com/thread-2850424-1-0.html
4- Make wipe only to Cache, Dalvik, System, Data and Internal SD
5- Format data,( if it doesn't format the data you will have bootloop) then Reboot into Recovery
6- Copy all the files to the phone (Havoc-OS-v4.X-20200522-Official-arm64-ab.img you can find it by unpacking the zip), Magisk,Magisk Path Fix, Permisiver, Certification Patch.zip, opengapp (recommended nano or pico)
7- Install system image to system partition (on TWRP go to install-Install image-System) .
8- Flash Permisiver v5 (on TWRP go to install selec permisver_v5.zip)
9- Resize system partition to flash opengapps (on TWRP go to Wipe-Advanced Wipe-Select System on the list-Repair or Change File System-Resize)
To Root
once you have installed an resized the system
10- Flash the Magisk path fix (on TWRP go to install selec MagiskA11_PATH_fix.zip)
11- Flash Magisk (on TWRP go to install selec Magisk-v23.0.zip)
12- Flash Opengapps
1-Flash Certification Patch
1 - Make a wipe to Cache and Dalvik
1- Reboot
The boot process takes 5 to 10 minutes the first boot, in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
Download link Rom image:
arm64-ab • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGapss Android 11: https://sourceforge.net/projects/opengapps/files/arm64/test/20210130/
Magisk:
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
Don't mind it, I haven't read all the article....
letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
D
letouvetpierre said:
Don't mind it, I haven't read all the article....
Click to expand...
Click to collapse
Dont worry
Darth Inferno said:
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
Click to expand...
Click to collapse
Okay thanks I think I will try this in the few days. Thanks for your guide !
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
letouvetpierre said:
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
Click to expand...
Click to collapse
Hi, I need to know some things to help you, what ROM did you have before flashing Havoc? do you have the bootloader unlocked? When did you use My flashtool, what method did you use?
letouvetpierre said:
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
Click to expand...
Click to collapse
In my particular case it was not necessary to flash vbmmeta as I comment in the OP I come from Miui12.eu, but it is necessary to avoid problems whatever the ROM you have before installing Havoc is to have the latest version of TWRP and have configured a lock pattern security in ROM access and in the flashing process I didn´t have problems
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
letouvetpierre said:
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
Click to expand...
Click to collapse
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Darth Inferno said:
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Click to expand...
Click to collapse
Hey!
I thought about something this afternoon : if I flash HavocOS with adb and fastboot, we also haven't any problems with TWRP installation ! But the problem is that I haven't found any wiki to do that and i won't transform my phone to a beta tester....
Thanks a lot for your help but I think i will wait until a custom rom of LineageOs or HavocOs...
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Dragonnuu said:
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Click to expand...
Click to collapse
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can help.
letouvetpierre said:
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can hel
Click to expand...
Click to collapse
Thanks for replying and trying to help but last night I managed to get havoc 4.1 is installed by flashing lineage first (using another guide from this category). I will try again to get havoc 4.1 working without flashing lineage as soon as posible because I am curious .
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
mwaseem851 said:
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
Click to expand...
Click to collapse
Magisk doesn't work on Android 11
letouvetpierre said:
Magisk doesn't work on Android 11
Click to expand...
Click to collapse
Finally managed to flash Magisk on Havoc 4.1 with the help of youtuberking (telegram and YouTube).
How: just flash Magisk path fix before magisk and it's good to go.
Hello all. first post here as i only recently found this great site. So ive been wanting a rooted phoje for a long time now as i iswd to jailbreak my uphone back when i used apple and hadnt learned of Androida greatness. I got a pixel 5a and i love it! Its different and i just love it. Maybe more than my s21ultra even. Anyways I updated to android 12 beta and then tried to root my device. I've never done this before so i tried to learn as much as possible. Anyways I followed the magisk tutorials and unlocked my boot loader and downloaded the boot.IMG for Android 12 and patched the image then did the fastboot and adb stuff only to end up with my phone not working. Clearly I did something wrong. It originally said on the fastboot menu failed to load or verify boot image. And was stuck on that menu. Tried to recover reboot and it stayed the same. Somehow I got it to restart then it was in a bootloop going to google to the unlocked bootloader warning screen over and over. I got frustrated and left it. It died and put it on the charger and it was in rescue or recovery mode saying no command. I got it into recovery menu and tried to factory reset and now it boot to the white google screen. I wanna flash it back to android 11 that it came with so I can eventually try and root it again as that seems much more successful then Android 12. ANy help is very appreciated and I am a SUPER noob at this and don't know about any of it so please keep that in mind when replying. Thanks
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
bobpiesz said:
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help I really appreciate it! I'm gonna give it an attempt right now.
I am facing the same type of problems for so long now.
Seems Magisk breaks booting when on the 12 S bootloaders :c even with disable-verity and disable verification in any step of the process
Disabling verity and verification is no longer required with Magisk 23016.
Follow my guide here, use the Factory Image method.
Hello to all,
I tried 1 year ago to root my POCO M3 Pro 5G but could not succeed to install TWRP unofficial for this model because of the problem of non-existent recovery partition (see https://forum.xda-developers.com/t/...oco-m3-pro-5g-redmi-note-10-5g.4474375/page-2) In short I bricked my device several times and then I had a boot with a weird screen that disappeared when I updated to MIUI 13.
Today I am on Android 12 MIUI global 13.0.3 and I would like to install magisk manager without the help of TWRP and I have the default recovery of MIUI with which I can not install anything.
I had also followed the procedure described https://forum.xda-developers.com/t/...urself-and-optionnal-debloat-privacy.4337693/ but without success impossible to flash on A or B : error messages : too many links, the partition does not exist (see screen shot in PJ), no emulator etc
The bootloader is still unlocked
I would like to root my phone and use Magisk manager modules such as Skvalex without damage or install root apk with spyware and trojan.
Do you have any solutions for me?
Thank you very much for your answers.
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
Ok tx I'll try this method and let you know
install magisk via fastboot is the easiest way for rooting. and more safe than using custom recovery. follow the guides with more attention. bad twrp can damage bootloader. bad flash of stock can damege device
i think the twrp have broked your boot, and i suppose u have flashed a wrong stock rom.
before made other damage, if can enter into fastboot: be sure to download right firmware. and flash it without relock option. if u dont do this, the risk is a serious hard brick. for who is not able to do a simply procedure like rooting, an hard brick is impossible to repair . be carefull
I have rooted my phone with magisk without any recovery, you just have to modify boot.img and flash it using fastboot.
I followed this method- https://www.getdroidtips.com/root-poco-m3-pro-5g/
Good evening
Thanks for your 2 answers.
I finally succeeded in laboriously rooting and patching on A and B but the modops on https://www.getdroidtips.com/root-poco-m3-pro-5g/ are incomplete and/or inaccurate. For example it is necessary to specify that it is necessary to download not the recovery version of the ROM but the fastboot version which is not underlined in the text of the link and other details of this type which avoid wasting time other example to find in the repertory the file of the patch.img even not hidden difficult to find even with the way and invisible via the directory of windows.
I have the root and I have installed modules on Magisk manager finally after the first attempt 12 months ago.
Cheers