Related
Hello! So I have rooted a few devices before while looking at guides on this website. This time it did not work out very well. I am using a Moto Z2 Force from T-Mobile. When I followed this guide: https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933 , I ended up locking up my phone in bootloop with the Tmobile logo. I have tried flashing back the backup I made and using a few different roms I found on this site. Some of the guides I tried to use to fix my phone were:
https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
https://forum.xda-developers.com/z2...m-stock-november-hybrid-rom-t-mobile-t3712795
https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932
None of them are working.
Bootloader is unlocked. After using the flashall from these links I had to unlock it again or I was stuck on a screen telling me "Your device is corrupt. It can't be trusted and will not boot". When it is locked it just goes between that quoted black screen and reboots itself every 10 or so seconds back into that screen. Once I unlock the bootloader, It quickly shows the white T-Mobile screen. Goes to a black screen that says "Your devices software can't be checked for corruption. Please lock the bootloader". It will let me pause on the screen if I click the power button or it will continue to the T-Mobile screen. On that screen it will vibrate for a half second and then after 5 seconds or so will restart.
At this current moment I have gotten it so I can get into the recovery mode screen. At some points in my adventure today that option would have a bootloop as well. I have tried "Wipe data/factory reset". But that puts me in a even shorter bootloop that does not even vibrate on the T-Mobile screen. It is just a quick flash of white, black, then white again.
Not sure what other information I can give. I am going to leave the phone where it is until someone replies to this.
Go into bootloader. Let us know the bootloader version. It should have a message in bootloader with the end looking like a date, that is what we need to know. It seems you're on Oreo by your symptoms. If so, flash the flash all in development section thread on "update to Oreo [T-Mobile]" nougat flash all's will not work if you're on the Oreo bootloader.
edit: https://drive.google.com/open?id=1CAFz1yIdnqE13ATSoYJKp2R17Q3bVo6A
Thank you so much. That flashall worked. I tried another one from Oreo but it did not work. Glad this one did.
Uzephi said:
Go into bootloader. Let us know the bootloader version. It should have a message in bootloader with the end looking like a date, that is what we need to know. It seems you're on Oreo by your symptoms. If so, flash the flash all in development section thread on "update to Oreo [T-Mobile]" nougat flash all's will not work if you're on the Oreo bootloader.
edit: https://drive.google.com/open?id=1CAFz1yIdnqE13ATSoYJKp2R17Q3bVo6A
Click to expand...
Click to collapse
I wasn't to know if the Oreo flash all skips the need for the magisk manager apk that nougat required.
And is twrp for Oreo like any other twrp from the past can you boot it from fastboot menu or power button combo and works ok? Not exactly getting the current working status of twrp for this device hence why I haven't flashed any recovery
Sent from my [device_name] using XDA-Developers Legacy app
androidddaaron said:
I wasn't to know if the Oreo flash all skips the need for the magisk manager apk that nougat required.
And is twrp for Oreo like any other twrp from the past can you boot it from fastboot menu or power button combo and works ok? Not exactly getting the current working status of twrp for this device hence why I haven't flashed any recovery
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
For Root, Magisk Manager will always be required. You need an app to manage root access to apps or things would be terribly insecure. After you update to Oreo, use the below TWRP, it works flawlessly. Credits to @joemossjr and @invisiblek for it.
https://drive.google.com/file/d/1nEp8EWDye3BE7p0yjugUWRw0-OkePCRz/view?usp=sharing
Uzephi said:
For Root, Magisk Manager will always be required. You need an app to manage root access to apps or things would be terribly insecure. After you update to Oreo, use the below TWRP, it works flawlessly. Credits to @joemossjr and @invisiblek for it.
https://drive.google.com/file/d/1nEp8EWDye3BE7p0yjugUWRw0-OkePCRz/view?usp=sharing
Click to expand...
Click to collapse
Link to the magisk manager needed by chance ? ... Or is it the same one from the nougat root thread?
And can you possibly be the 2nd one to confirm/acknowledge we indeed can edit build prop to enable MHL Mirracast on the z2 force ? So I heard ... I'm trying to mirror my z2 to my pioneer touch screen and it's got to be done via mhl adapter.
Some say Moto and Lenovo just blocked this but it still exists with simply editing a value in build prop ?
Sent from my [device_name] using XDA-Developers Legacy app
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 for more information on magisk. Do not flash anything from the nougat thread. Oreo is different. download the 15.3.zip and flash it in TWRP. download Magisk Manager apk from the official thread and you'll be good to go.
Yes, a build.prop edit should make it work
Uzephi said:
For Root, Magisk Manager will always be required. You need an app to manage root access to apps or things would be terribly insecure. After you update to Oreo, use the below TWRP, it works flawlessly. Credits to @joemossjr and @invisiblek for it.
https://drive.google.com/file/d/1nEp8EWDye3BE7p0yjugUWRw0-OkePCRz/view?usp=sharing
Click to expand...
Click to collapse
Is this TWRP image bootable only or is it safe to flash/replace stock recovery?
Shiro12 said:
Is this TWRP image bootable only or is it safe to flash/replace stock recovery?
Click to expand...
Click to collapse
It is flashable
flashing Twrp V6 moto z2 force is this 100% functional
Uzephi said:
It is flashable
Click to expand...
Click to collapse
so OreoV6 twrp is 100% functional can flash it permanently and boot from fastboot recovery at any point? any other steps or flashing ? decryption neccesary after flashing twrp or is that an optional?
androidddaaron said:
so OreoV6 twrp is 100% functional can flash it permanently and boot from fastboot recovery at any point? any other steps or flashing ? decryption neccesary after flashing twrp or is that an optional?
Click to expand...
Click to collapse
Encryption works thanks to @invisiblek. Just "fastboot flash boot path/to/twrp" and you're golden.
Uzephi said:
Go into bootloader. Let us know the bootloader version. It should have a message in bootloader with the end looking like a date, that is what we need to know. It seems you're on Oreo by your symptoms. If so, flash the flash all in development section thread on "update to Oreo [T-Mobile]" nougat flash all's will not work if you're on the Oreo bootloader.
Click to expand...
Click to collapse
Same as Moto people did on old Griffin (Moto Z) with MM -》N...
Does Oreo works fine on Nougat BL?
(On Griffin you could use fine N on MM BL...)
I too got a bootloop after unlocking the bootloader, installing TWRP, and then Magisk from the TWRP forum. I got it back working after formatting data again luckily. I am on 3.1 right now, do I need to update to 3.2 before flashing Magisk? I'm on 7.1 now, BL: MBM-3.0-nash_tmo-e7b4c60-171017
Thanks for any help, its been many years since I had an upgrade, been stuck on the S6 for a while and glad to get back in the game
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...
Did the new flashall 27.1.3 work if not I may can help
Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?
After using this phone for a while I decided to root it.
I unlocked bootloader, installed TWRP and flashed Magisk, but all I get is bootloop or stuck on bootlogo (your device has been unlocked.....)
SOLUTION
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
Applicable also for moto Z2 Play, just with appropriate recovery, of course
Please note the updates to the first post. It may be necessary to do the procedure twice.
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks
Klen2 said:
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks
Click to expand...
Click to collapse
I did 3.2.3-0 TWRP method (by Junior Passos) on my XT1710-06 device with 8.0 on August 1 security patch (purposefully neglected updating any further cause method was tested exactly up to August patch according to Passos) and everything seems working pretty fine for a month now. Think I've installed no Magisk modules other than Xposed systemless yet and I've no interest in SafetyNet as well, so not deeply tested either. Don't know for sure, but I guess there's a good chance for such method to work on October patch too. Just be sure to perform every step as it is now in the 3.2.3-0 OP. One word of advice: after performing TWRP backup, look for it in /system/media and move it to both external and internal SDcards just in case something goes wrong (usually because of a missed step, I can say)... Also: I recommend to install Magisk v17.1 first time; then, if you want, update to v18 but right from the installer...
Sent from my Moto Z2 Play using XDA Labs
Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).
Have these steps worked for me...
1.)Flash TWRP using Fastboot
2.)Go to TWRP/Settings and open Terminal.
3.)Run both of following commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
Click to expand...
Click to collapse
4.)Flash Magisk-v17.1.zip
5.)Repeat step 2 and 3 dont wipe.
6.)Start
NOTE: before Reinstall stock or uninstall Magisk.
I did the Junior Passos method of doing the backup, and everything is working like a charm.
Cupcake 1.5 said:
Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).
Click to expand...
Click to collapse
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop
OldUncle said:
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop
Click to expand...
Click to collapse
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Perfect!
Thank you very much!
The only solution which worked!
Finally I got full control on my Z2 Play.
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Regarding backup, this is done through the stock ROM correct (Settings --> System --> Backup to Google Drive).
Thanks,
smithmal
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
This worked perfectly on my Moto Z2 XT1710-06 with Oreo 8.0 when no other options worked.
Flash or Boot into TWRP
Backup System and Boot partitions in TWRP
Restore System and Boot Partitions in TWRP (note I had to enable R/W access in TWRP to restore the system partition)
Flash Magisk-v19.3.zip
Reboot
That is it. Now Rooted and passes all SafteyNet test. No more restricted apps. Even Google Pay now works.
Thank You.
sick
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
your method worked like charm, thanks alot man
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Bootloop in logo S9
RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up
Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me
S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
it stucks for me on the samsung logo
aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?
Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img
sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?
Search for recovery.img and boot.img in stock rom and flash in fastboot mode.
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,
regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.
try this n give us the result