Hi all,
Is anyone rooted on global hardware global ROM 10.3.1.0? I've been getting the update notifications for a while but have been hesitant to update in case I loose root, I've never updated with an OTA on a rooted device before. To update, can I just download the OTA then reflash TWRP and Magisk and be good to go? Has anyone tried this? If so, what version of TWRP and Magisk did you use successfully?
Thanks in advance for any input/advice!
Download the OTA, install it via TWRP, boot into the system and flashing TWRP via ADB again. Boot into the TWRP and flash again magisk. That's how it worked for me. At least with my mix 2 [emoji1360]
Gesendet von meinem MIX 3 mit Tapatalk
Related
Hi guys,
I am using a rooted HTC e8 (european/german version with 1 sim only) with TWRP.
Software Infos from the about sceen: android version 5.0.2, HTC Sense 6.0, Software number 2.34.401.6 ...
I do want to upgrade to android 6 (have the notification sitting on my phone for months now) but I am not really sure how. I can't just do the ota update with my custom recovery (right?!).
Here are the steps I used to get root on the last android 5 update:
then follow these instructions
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
Run the following commands from your adb folder:
6.fastboot oem rebootRUU
7.fastboot flash zip RUU.zip
8.fastboot reboot
Click to expand...
Click to collapse
Can I just do the same again? What would be the right RUU for me?
Afterwards how do I get the right version of twrp back and how do I root again?
Sorry for all these questions but most of this is new to me, so thanks for any helpful answer
Someone?
ILastSamuraiI said:
Someone?
Click to expand...
Click to collapse
Read on snoopy-haeckers.jimdo.com
Gesendet von meinem HTC One_E8 mit Tapatalk
snoopyhaeckers said:
Read on snoopy-haeckers.jimdo.com
Gesendet von meinem HTC One_E8 mit Tapatalk
Click to expand...
Click to collapse
Hey, thanks for the link! Great site (and even german ).
So am I right, that I need to do this to get my updates:
get the Android_5.0.2_M8_ACE_2.34.401.5 RUU from your site and flash it
start the phone and let it do its normal update to android 6
Get the latest version of twrp and flash it
Install/flash the superSU from your post here to get root again (is that one still the right one?)
If anyone can confirm this I will try it soon. Thanks :good:
I guess I do not need the whole ruu but just to flash the stock recovery from your site. Rest should still be right?!
Edit: Or not, afaik that only works if nothing else has been changed and I have superSU installed and might have changed something.
best and easiest way is twrp backup.just you must download latest twrp from snoopy-haeckers.jimdo.com and restore it from twrp recovery .with this way you never need to flash ruu or lock bootloder or flash stock recovery and........
restore it
https://docs.google.com/uc?id=0B0QMeWRH_17FQ0t5SWluSHpQTVE&export=download
I did just that (restored the twrp backup from your link) and after that my phone was stuck at the start screen (htc one, the white one). Any idea whats wrong or how to fix it?
Restoring my own backup from before worked and is running again atm. Might it be a problem to restore a backup with a newer version of android?
Whats your android version?and check your Hboot version
I did try it again after unzipping and copying the files to my phone again and updating to the newest twrp version. This time it worked. Thanks for the help!
So i flashed twrp on top of the stock rom and it just keeps bootlooping it not even getting to the samsung logo just the galaxy s6 splash screen
Heres a odin screenshot http://prntscr.com/h13jdx
Flash Magisk. It' s dm-verity
arkasha17 said:
Flash Magisk. It' s dm-verity
Click to expand...
Click to collapse
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
paul222008 said:
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
Click to expand...
Click to collapse
Just search. From twrp flash Magisk.
Inviato dal mio SM-G920F utilizzando Tapatalk
DON'T FLASH MAGISK v14.0
Like the others said, you need to flash magisk but don't flash magisk v14.0. I had huge issues with my SM-G920F with magisk v14.0 (I kept on losing root, modules didn't work correctly...) so I just went back to the last working version, which was v13.3. You can still install the same modules (by manually flashing them through apps like flashify), but you will never lose root (or at least I haven't). I lost root after 3 minutes of use on average on v14.0 and never lost it once on v13.3. However, the best way to do so it to run the uninstall script in twrp if you had magisk previously installed and then flash the older versions. The older versions can be found on the original magisk developer section right at the bottom where it says downloads.
Previsouly, I used TWRP v8 and EU MIUI 8.7.19 and today I updated EU MIUI 8.8.3.
After ROM installation, my system is booted to TWRP mode.
I successfully reinstalled EU MIUI ROM, and worked well until TWRP work.
After using TWRP, my system is booted to TWRP mode..
How can I fix this TWRP loop problem.
Please help me.
Thank you.
Format data and working.
Gesendet von meinem MIX 2S mit Tapatalk
I'm running Android 10 and OOS 10.0.2 GM21AA.
I'v clean flashed the OOS 10.0.2 and rooted the phone by flashing Magisk through TWRP Latest build. Initially the root was going well.
After installing youtube vanced module from magisk, i rebooted the phone and it doesn't rebooted. It got stuck in OEM Unlock Warning screen for a while then automatically shifted to fastboot mode.
Then i flashed the stock boot.img and phone became good to go.
I flashed the stock boot.img patched with magisk. But the phone doesn't get any signal(SIM UNKNOWN) after reboot.
I tried changing magisk and twrp versions also, but it didn't work.
I need help of you guys. Please suggest me.
Use the following thread!
It works fine!
https://forum.xda-developers.com/showthread.php?t=3940368
Gesendet von meinem GM1913 mit Tapatalk
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
I flash magisk 20.1 after every eu update.
First i flash the eu update. After that i boot in recovery again. Then i flash magisk and clean dalvik and cache. Then i boot system.
If you flash into the recovery magisk after the eu update without restarting, it ends in the bootloop.
At least it was with me like that.
Gesendet von meinem MIX 3 mit Tapatalk
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
I'm running Magisk 19.4 (the one for Xiaomi devices obviously) on Xiaomi.eu beta 9.12.12. No initial issues or any since
You should always reboot first, otherwise magisk will bootloop
Giuskiller said:
You should always reboot first, otherwise magisk will bootloop
Click to expand...
Click to collapse
A reboot into twrp is enough
Gesendet von meinem MIX 3 mit Tapatalk
I can confirm that magisk 19.3 work fine on lastest eu stable 11.0.1.0 android 10.
i have the last xiaomi.eu beta and the last magisk and all work good
kiwan955 said:
i have the last xiaomi.eu beta and the last magisk and all work good
Click to expand...
Click to collapse
I too [emoji1360]
Gesendet von meinem MIX 3 mit Tapatalk
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
From my experience in mix 2s. If i have a MIUI with magisk modules active, then flash new rom, restart, flash magisk, then wipe dalvik, i get bootlooped. The solution was to disable all magisk modules before updating and then flash magisk, wipe dalvik and restart. After getting into the OS, reactivate the modules.
If you have a twrp based recovery that allows you to disable magisk modules from the recovery (like orange fox) that may help you get out of the bootloop.
Give it a try