HI everybody.
It does many years that I wanted to try to root my phone: I love new technology but I become old : perhaps is it the reason for which root my phone finally doesn't seem as easy as it is said everywhere !
As we are at home due to the COVID-19, I thougt that is was the perfect moment to try this week (I began last tuesday).
As i'm a newbie, I read many tutos, pages to understand and to be "sure" not to do mistakes.
I've installed TWRP and it works fine.
I did a backup in TWRP (data, system, manufacturer, modem, EFS and boot).
The only problem, after TWRP installation, was that the smartphone never booted in recovery mode with TWRP: I always had stock root.
To have twrp recovery, I always had to use adb in fastboot.
I searched a long time and never managed to fix this.
I considered it was not a real problem because it was easy to have TWRP with adb.
At this moment, I wanted to install LineageOS but after many searches, I realized that there was no LineageOS rom for the Mi Max 3.
I decided to install the last issue of magisk to really root my phone since the TWRP doesn't root itself the phone.
I installed Magisk v20.4 and troubles began.
I had a bootllop...
It does hours and hours (night and day) I spend to find a fix but without success.
Most of tutos refers to "old" issues of uninstaller or uninmod.
I think I've done many things as:
- Re-install Magisk v20.4
- Install "officiel" Magsisk V20.4 uninstaller (I got an error 1)
- Install different modules remover (I always got errors 1): uninmod_Magisk_v4
- Install Magisk Manager for Recovery v5 202004170 which is very recent (I always got error 1)
- I obviously tried to restore my backup with no success
- I read the page of katterpanne to fix the bootloop, but the mentionned tools refer to "obsolete" versions of magisk manager and uninstaller
The only zip package which didn't cause an error 1 was the magisk_module_remover of edzamber (for magisk 19 and higher) but it is a little old and surely doesn't "fit" to magisk v 20.4 and it didn't work. At least, if i reboot, TWRP warns that there is no installed OS.
I feel desperate and my knowledges are limited.
I don't know how to uninstall manually, if I don't find any suitable uninstaller/remover zip package, this magisk.
Perhaps that all I done has really uninstall/remove magisk but how can I check that ?
Why so many error 1 in TWRP ?
Haw can I check, from TWRP, if my phone is rooted ?
According to you, what should I do: install a version of Magisk lower than V20.4 (even v19.x) or try to install a rom ?
I suppose that I had to install a custom ROM since I've no OS but my phone seems no rooted since Magisk caused a bootloop.
Finally, if there is no suitable LineageOS for the Mi Max 3, which custom ROM can I use (I have no particular expectations: just remove the xiaomi apps).
I apologize for all these questions and this long topic but I hope having replies and help to fix my issue.
I can't believe thet my phone is condemned, dead... I really appreciate this Mi Max 3.
Thanks by advance for your lights.
Best regards.
You can flash back to stock ROM with MiFlash.
Download the fastboot ROM from here:
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503
How to flash with MiFlash:
https://www.the***********.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
Edit: Somehow i can't post the link, just Google "Install MIUI fastboot ROM".
Related
First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly
Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.
Maybe this has something to do with Keymaster?
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.
New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks
Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!
Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.
Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.
So, I got an A50, and I'm really happy that I did. However, switching from a phone that had TWRP and Magisk is something I am not finding easy, even if the phone is much faster than my old one. So, of course, after thoroughly reading my warranty, which had no mention of not covering software device damage, I decided to to go ahead and try to flash TWRP and then install Magisk. I went ahead and easily figured out that my model is SM-A505FN (which would have been all that I needed for my old phone). Seeing that there were successful attempts at installing TWRP and Magisk on this model, I decided to try it out, but quickly found myself with a soft bricked phone, so off to finding a Stock ROM I went. After booting it up again I did more digging, but that yielded no result, however, I decided to try using Magisk manager to patch the AP file and then tried patching that. Sadly, no luck. I even went as far as trying a few of those programs that would root your phone from your PC, but that proved to be a waste of time as even that didn't work (which I suspected would happen, but whatever).
While fondling with the phone, I noticed something in the recovery. It wrote a50xx and then I realized that that must have been the reason for nothing working. And now we get to the title of this post. Has anybody been successful at rooting or flashing TWRP on an a50xx device, and, if so, would you be so kind as to elaborate on how you did it?
If not, I guess I should either wait, or look into trying to port TWRP to a50xx myself.
Edit: In case I do decide to port TWRP, any help or pointers are welcome.
Hello @BrainReader,
Same problem here! I tried rooting my device (sm-a505fn as well) by flashing the ap-file using magisk manager. I kept ending in a bootloop. I tried the latest version v20.x and even tried v19.3 which should work stable according to this thread: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271.
I hope this thread gets more attention and someone finds a solution for rooting the a50!
Kind regards,
Shademaster639
I have a rooted a505fn twrp is not working but rooting with magisk works fine. Every magisk version above 19.3 is giving problems. The latest magisk give very much reboots. What I did I first installed the newest software with Odin. Then install magisk 19.3 after that I set in magisk the update channel to get no further then 19.3.
That patch the AP file and reflash everything with the patched version.
It works without problems.
You must flash complete firmware stock
Then reflash complete firmware with mm agisk ap
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Ms0206 said:
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Click to expand...
Click to collapse
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
kurtn said:
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
Click to expand...
Click to collapse
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Ms0206 said:
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Click to expand...
Click to collapse
Your data Partition is encrypted. Sideload does not touch data partition. Follow the guide
As if I didn't know it before, following the official guides producing the same errors as using Twrp.
I tried so many things...using official recovery does not install OTA automatically.
Sideload producing the same errors as using Twrp - "Magisk addond.d failed, cannot find Magisk binaries, reflash OTA Form decrypted recovery or reflash Magisk".
Howdy!
Please forgive me if this is the wrong place / my google-skills are insufficient!
This is my first post to this forum, because I can't resolve what part is important in rooting (w Magisk?) my RN8P.
First about myself (and my abilities): I did flash some phones (S4 mini, Zenphone2, Yoga Tab 3 plus) with TWRP and Lineage, so basic knowledge should be present, but nothing "in depth"!...
What I did to my RN8P (begonia, global, EU):
OTA-Updated to MIUI A10
Unlocked Bootloader
Reflashed MIUI A9 (because reasons )
Fastboot flashed lk & preloader from CFW MEGATHREAD & non-CFW TWRP
Flashed crDroid (with CFW and TWRP batch) and the crDroid Rom itself w. openGapps via TWRP
What I want to achieve:
Limit my battery charging to a certain percentage
Maybe use the often praised camera app praised with magisk
Let the rest of the system "as is", so have AntiBrick, TWRP and "invisible" Root
Maybe use other magisk-goodies
Versions used:
CFW A10 20200530
TWRP from crDroid-pkg (3.3.1-0)
crDroid 10 20200721 begonia
open gapps arm64 / 10 / pico / 20200730
My question:
I've read about installing MAGISK can trip the AVB, which is to avoid at all costs(?!?), so where is my starting-point for MAGISK?
So what are the pitfalls I have to avoid / consider? / Which guide to follow on how to do it proper?
Forgive my ignorance, any help / bump in the right direction is highly appreciated!
Thoughts so far
Hey!
I think my understanding has grown a little bit...
There is only one Version (no A - A/B) of MAGISK any more, so no fuss about picking the right tool. And being brought via zip-file for flashing within TWRP seems very convenient.
There seem to be TWRP-versions out there, which can mitigate the AVB-tripping for our RN8P, are they CFW compatible? (and which is recommended?)
So basically these questions remain:
Which exact TWRP-version is recommended?
Shall I completely reflash CFW, crDroid, openGapps, when I flash MAGISK? Or just wipe cache / davlik and reset to factory?
Are there other pitfalls or downsides of using MAGISK in my combination of Hard & Software?
Cheers, Mecky85
Not using CFW (Stock MIUI with Magisk benefits), but here is some advice:
0. Make sure you follow every step on TWRP site (especially the vbmeta flashing part). It can save you from headache. I don't say you have to use TWRP, tho. Also make sure you do this step if you return to stock boot image. Do it once, and you are fine.
1. Use CFW-compliance recovery, as recovery has it's own firmware.
2. In my case (I'm doing update with this procedure: MIUI+Magisk>vanillafy>update MIUI>Mod), no need to reset anything. But resetting dalvik+cache is not bad either.
3. Out of question.
Hope that help.
Thanks for the headsup with vbmeta, will have time to look (and hopefolly have a got at it) after the weekend!
Will post my experiences in here.
After a good batch of reading into the topic... I'm not convinced any more I'll cope with it...
Not worth for me to figure everything out, if reading into this is such a hassle... :silly:
Hello xda,
I've had the Pad 5 for a year now. Since I needed it to be multi-user capable, I originally installed a phh gsi on it, which has been working alright except for a few unwanted reboots from time to time.
Still, I believe it is more than time to update this thing, if only for security patches. Since I saw there's now a device specific custom rom with arrowos, I thought I was in luck.
However, I need to back all of the data up before doing so, if I don't want to get shout at by my children. I kind of understood that the best way to back this thing up was to first get root.
Since I had not done it originally, I set out to install the magisk app (v. 25.2), found the boot.img of my original firmware, patched it in the app, flashed it with fastboot and happily rebooted.
The happiness was short-lived, though, as the magisk app displayed a pop-up saying that it doesn't support magisk versions older than v22.0
What may I have done wrong to get that message ?
Thanks for your time and help !