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.
I'm having issues with certain "secure" apps not working on Pie with Magisk after updating from Oreo (Google Pay in stores, Zelle, Chase, etc.) even though safetynet and everything else checks out perfectly. I'm thinking about doing a clean install but I'm not sure what's causing the issue and I'd like to avoid it again if at all possible... I followed a guide on XDA and everything works right except for this issues and the only things different from when I was on Oreo are:
* Installed TWRP instead of just fastbooting into it for flashing
* Installed Sultan's kernel, per the guide (not 100% sure how to get back to stock on that either, unless it'll happen when flashing the update from Google)
I think everything else was the same, other than updating Magisk from 16.1 to 18.0 (and later downgrading to 17.2 after reading that 18 had some issues with hiding). Anyone have a similar issue and found a solution or have advice on troubleshooting? I'm planning on trying a fresh install and only fastbooting into TWRP to install Magisk instead of installing it, and staying on the stock kernel to see if that helps but trying to avoid bricking my phone too.
Thanks
Join the crowd... It's been a few weeks since this started. There are a few work around methods but they don't seem to be consistent or permanent. Most are just waiting until magisk gets updated to fix whatever Google did to detect modified systems.
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 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".
Has anyone been offered the Global version by their phone and updated ?
If Yes - what is your experience with MIUI 14 and does Dark mode work for individual apps listed separately in dark mode options?
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Today monring i make an update, it is super. System is faster, but Leica cam app is not possible instal, have anybody newer version of leiaca cam app fo A13? THX
thecumbackkid said:
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Click to expand...
Click to collapse
@thecumbackkid - Please tell me in settings - display - more dark mode options - does it list all the individual apps to choose dark mode for each app ? (it may take a second or 2 to list them)
This is what it shows for me.
Thanks for the info thecumbackkid
Looks like its time to upgrade I was stuck on Miui 12.5 as when I updated to 13 all individual dark mode apps options disappered.
Someone stole my phone on holiday so I bought a new one and stuck on 12.5 as Dark mode for individual apps is essential for my over sensitive eyes!
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
snyfear said:
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
Click to expand...
Click to collapse
@snyfear
Thanks for the info - if you notice anything else let us know
Awful battery drain here. Charged to 100% barely did some basic browsing and half is already gone in a short amount of time. Noticed whenever I have it charged to 100% at night and by the middle of the next day where I barely use it for nothing but just to check for notifications on stuff it's already down to 80%...
AFAIK, this appears to be some pilot program build? I never asked to participate in it so how did I get this update?
Does any one know how to Facemoji keyboard in MIUI 14 for Lisa ?
I am not rooted. its plain stock MIUI.
Tried ADB shell uninstall, it gave me failure.
Also tried Xioami debloater tool. That also didnt work.
I still haven't received the update for some reason and i tried to update it manually but it didn't work what should I do
Updated to 14.0.4 EUXM and can't get root to work anymore.
Patched the boot image via Magisk 25.2 and then tested via fastboot, as always.
I run directly into a bootloop, which after a while sometimes returns to the bootloader or automatically deletes the temporary boot and boots with the normal image.
It's also strange that during the bootloop the device vibrates once every 3-5 seconds briefly. I've never had that before either.
Update:
I found a solution without wiping my device.
I remembered that I had a problem during the last update with shamiko and I didn't uninstalled magisk or removed any modules before the update. So in order to remove the modules without access to /data/adb and wihtout root rights you need to do the following, maybe it's interesting for you folks.
1. Open shell with command: "adb wait-for-device shell magisk --remove-modules"
2. Open second shell and boot with patched boot.img: "fastboot boot boot_patched.img"
The short time at boot, where root is present, was enough to remove the modules via the CLI during the boot loop.
Lessons learned:
Before the next major update definitely remove all Magisk modules before, if not root entirely.
Saves the work afterwards.
Btw:
Update is running smoothly so far. No battery drain noticed.
can anyone link me to a tutorial on how to rollback from custom rom (currently AOSPA) to stock MIUI ROM? want to move to MIUI 14 eventually. greatly appreciate it!
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
telefoongids said:
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
Click to expand...
Click to collapse
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
theanik said:
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
Click to expand...
Click to collapse
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash the rom with fastboot first, to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Just search for mi11le in the downloads.
telefoongids said:
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash it first with fastboot to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Just search for mi11le in the downloads.
Click to expand...
Click to collapse
thank you!
any one from Philippines received the update?