Hi
i have a HTC A9s, some weeks/month bevore i had installed Magisk to the phone. It works fine, sone updates from magisk all fine, but yesterday i updated my phone from V14 to V15, installation all fine, but after reboot the phone don't encrytion work. Ask to pin, but don't encrypt. Only reset i can do, but after next reboot the same (loop).
OK, i flash RUU file from other forum-task, the phone start up and works. yeh, i'm lucky.
I need Magisk for Xposted/XPrivacy and i flash the boot.img, after that the phone starts and ask me to my pin für decryption, but i don't have after flash RUU file encrytion activat.
I had have flash old v14 patched image and new patched boot.img with V15 of Magisk.
Can you help me?
linuxdep said:
Hi
i have a HTC A9s, some weeks/month bevore i had installed Magisk to the phone. It works fine, sone updates from magisk all fine, but yesterday i updated my phone from V14 to V15, installation all fine, but after reboot the phone don't encrytion work. Ask to pin, but don't encrypt. Only reset i can do, but after next reboot the same (loop).
OK, i flash RUU file from other forum-task, the phone start up and works. yeh, i'm lucky.
I need Magisk for Xposted/XPrivacy and i flash the boot.img, after that the phone starts and ask me to my pin für decryption, but i don't have after flash RUU file encrytion activat.
I had have flash old v14 patched image and new patched boot.img with V15 of Magisk.
Can you help me?
Click to expand...
Click to collapse
I had the same problem. I'm thinking if you can get stock boot.img and patch it with v15.0 and then patch phone it might work.
Btw can you tell me where did you get ruu files for stock rom?
Wysłane z mojego HTC One A9s przy użyciu Tapatalka
no, i had patched with new version 15 and i have the same problem. on magisk thread thausends of posts with problems, but i don't have read all, only the last, but HTC was not insight.
tomorror i restore again und install v14, i hope this work fine, a pity that TWRP not work on this phone. That would make testing easier.
linuxdep said:
no, i had patched with new version 15 and i have the same problem. on magisk thread thausends of posts with problems, but i don't have read all, only the last, but HTC was not insight.
tomorror i restore again und install v14, i hope this work fine, a pity that TWRP not work on this phone. That would make testing easier.
Click to expand...
Click to collapse
But be careful. I did this and SafetyNet got triggered. And I ended up with working on get rid of magisk or fix this.
Wysłane z mojego HTC One A9s przy użyciu Tapatalka
see post on other thread
Hi,
i have installed old RUU and then flash patched boot.img with V14 and this works fine. Maybe it would have been enough to flash the boot.img V14 without lose data?
Since TWRP does not work on the phone unfortunately, it remains to be hoped that the next update works.
I have this same issue if you want there is working TWRP for our phone, so you can install it
Hi, update 15.2 from magisk is online, has somebody test it? Work it?
Hi I just installed magisk v16 and it works
Related
Hi,
I hope this is the correct forum. If not then pls move it where it should be.
(I also couldnt find a similiar thread for especially sony)
I have an Xperia z5 with root on Android 6.
Since the latest updates i cant play Pokemon anymore because of root check. For other devices there is a solution with Magisk but this doesnt support Sony Devices.
Has anyone a solution to hide root on Sony Devices? Or a way to play Pokemon?
Thanks,
Magisk works with sony devices, im usign Magisk and can play pokemon go with no problem, have you tried to install Magisk?
ZiTrOz said:
Magisk works with sony devices, im usign Magisk and can play pokemon go with no problem, have you tried to install Magisk?
Click to expand...
Click to collapse
No i havent tried because i dont wanted to make something wrong.
In the Magisk-Thread in this forum stands that Sony Devices are not supported. After asking i got the answer that this ist till a problem.
What Sony do you have?
utbf said:
No i havent tried because i dont wanted to make something wrong.
In the Magisk-Thread in this forum stands that Sony Devices are not supported. After asking i got the answer that this ist till a problem.
What Sony do you have?
Click to expand...
Click to collapse
Sony Z5 with Xperia X ROM 3.0
utbf said:
No i havent tried because i dont wanted to make something wrong.
In the Magisk-Thread in this forum stands that Sony Devices are not supported. After asking i got the answer that this ist till a problem.
What Sony do you have?
Click to expand...
Click to collapse
I can assure you that Magisk works with the Z5. I am using the stock firmware (6.0.1), with the AndroPlus kernel v36, and Magisk with root and Xposed installed. SafetyNet passes the checks and AndroidPay works. This means that PokemonGo should work as well.
Before you can use Magisk on the E6653, you're going to need to:
Backup your TA keys so you can restore DRM if you ever go back to stock for warranty purposes
Unlock the bootloader
Flash the AndroPlus kernel
Flash the TWRP 3.0.2 custom recovery
Flash Magisk, SuperSU, and Xposed in a particular order to ensure that SafetyNet passes.
Once you do all that you should have no problems playing PokemonGo with root and Xposed. This is the first Sony phone I've owned and the hardest part for me backing up my TA keys because Flashtool kept failing to flash the downgraded firmware. Once I got my TA keys backed up, the rest of the steps took me less than 30 minutes. It's really not that bad as long as you follow all of the instructions exactly as written.
Hello,
i can also say that Magisk is working on Z5.
I tried it yesterday and everything was fine. For anyone who is also thniking about the Problem here my steps:
Sony was already root and has Supersu installed.
1. complete un-root with supersu
2. flash Magisk_v6.zip with twrp
3. reboot
4. flash phh_SuperSU Magisk version
5. reboot
6. install phh_SuperSU from playstore
7. install magiskmanager from APK
8. install automagsik
Everything is working now.
Thanks for your help
utbf said:
Hello,
i can also say that Magisk is working on Z5.
I tried it yesterday and everything was fine. For anyone who is also thniking about the Problem here my steps:
Sony was already root and has Supersu installed.
1. complete un-root with supersu
2. flash Magisk_v6.zip with twrp
3. reboot
4. flash phh_SuperSU Magisk version
5. reboot
6. install phh_SuperSU from playstore
7. install magiskmanager from APK
8. install automagsik
Everything is working now.
Thanks for your help
Click to expand...
Click to collapse
Hey thanks for the tips mate, I too have a Sony Z5 (but Compact model), and would like to apply Magisk to play Pokemon !
My situation : bootloader unlocked, rooted, rom Xpower V4.0 with SmarTemperatureX, TWRP recovery, supersu installed
My problem : i can't do your 1st step "complete unroot with supersu", this fails in the app and when i select not to replace recovery etc, phone reboot and root is still there... any help please ?
polux400 said:
Hey thanks for the tips mate, I too have a Sony Z5 (but Compact model), and would like to apply Magisk to play Pokemon !
My situation : bootloader unlocked, rooted, rom Xpower V4.0 with SmarTemperatureX, TWRP recovery, supersu installed
My problem : i can't do your 1st step "complete unroot with supersu", this fails in the app and when i select not to replace recovery etc, phone reboot and root is still there... any help please ?
Click to expand...
Click to collapse
From what I understand, Pokemon Go uses SafetyNet to verify the system. SafetyNet will only pass it's checks if it detects a stock ROM without root or Xposed. So while there are methods to hide root and Xposed, I don't think there's any way to spoof a stock ROM.
Bottom line, I don't think it'll work with a custom ROM. Somebody please correct me if I'm wrong.
Devo7v said:
From what I understand, Pokemon Go uses SafetyNet to verify the system. SafetyNet will only pass it's checks if it detects a stock ROM without root or Xposed. So while there are methods to hide root and Xposed, I don't think there's any way to spoof a stock ROM.
Bottom line, I don't think it'll work with a custom ROM. Somebody please correct me if I'm wrong.
Click to expand...
Click to collapse
The guy two posts up says he's usinga custom rom Xperia XZ Rom 3.0 so I think it can be used in a custom rom... Gonna try and will reply back!
On my Z5 compact I use SuperSU 2.78SR1 and suhide 0.53
Here you can find more information: http://forum.xda-developers.com/apps/supersu
Safetynet passed and I can use Android Pay and my banking apps
I think it is more easyer than magisk.
blue4you said:
On my Z5 compact I use SuperSU 2.78SR1 and suhide 0.53
Here you can find more information: http://forum.xda-developers.com/apps/supersu
Safetynet passed and I can use Android Pay and my banking apps
I think it is more easyer than magisk.
Click to expand...
Click to collapse
Hey thanks!! will check your post !
Edit : install of the requirements were OK, but I still fail to connect to my account in Pokemon Go with message "Unable to authenticate"
polux400 said:
Hey thanks!! will check your post !
Edit : install of the requirements were OK, but I still fail to connect to my account in Pokemon Go with message "Unable to authenticate"
Click to expand...
Click to collapse
I got the Same problem
Gesendet von meinem E6653 mit Tapatalk
Read and ask in the thread of suhide.
There are many people who use suhide for PO-GO.
My device is failing and as a result I am unable to setup Android Pay. Is anyone else seeing this on their phone?
Same issue
I'm rooted with Magisk and I pass.... so that's very odd
Just got an OTA that fixed it.
tw1tch175 said:
Just got an OTA that fixed it.
Click to expand...
Click to collapse
Sprint or unlocked U11 ?
I guess unlocked to get an OTA this fast...
Howling Wolf said:
Sprint or unlocked U11 ?
I guess unlocked to get an OTA this fast...
Click to expand...
Click to collapse
Yeah, unlocked. It seemed like a day zero ota that rolled out a bit late, it didn't update my monthly security but after it I had an update to my headphone dac and Assistant app.
heslo.rb26 said:
I'm rooted with Magisk and I pass.... so that's very odd
Click to expand...
Click to collapse
How did you do it? I flashed TWRP and Magisk, and then flashed the stock recovery, and I am failing safety net...
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
heslo.rb26 said:
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
Click to expand...
Click to collapse
Let us know
ticklemepinks said:
Let us know
Click to expand...
Click to collapse
Currently not working for me but I didn't flash the stock boot.img before I flashed the new Magisk so that is probably my issue there. Don't really have the time to mess with it currently so it will have to wait. If anyone else manages to get it working, feel free to update us
EDIT: Got off my ass and uninstalled Magisk, flashed the original boot.img and removed the Magisk Manager. Then I restarted the handset and flashed the Magisk v13 beta.... Pass SafetyNet checks no worries!
heslo.rb26 said:
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
Click to expand...
Click to collapse
I figured that out last night too after spending an hour wondering what I did wrong. Enabling Core-only mode on v12 also works, but you get no modules which is kind of pointless. I will try flashing V13.
EDIT:
Just flashed V13, and it still doesn't work.
@heslo.rb26 How did you get it to work?
ryanyz10 said:
I figured that out last night too after spending an hour wondering what I did wrong. Enabling Core-only mode on v12 also works, but you get no modules which is kind of pointless. I will try flashing V13.
EDIT:
Just flashed V13, and it still doesn't work.
@heslo.rb26 How did you get it to work?
Click to expand...
Click to collapse
Uninstalled Magisk
Flashed the stock boot.img
Rebooted and uninstalled Magisk Manager
Back to Recovery and flashed the new Magisk
.....
Profit
heslo.rb26 said:
Uninstalled Magisk
Flashed the stock boot.img
Rebooted and uninstalled Magisk Manager
Back to Recovery and flashed the new Magisk
.....
Profit
Click to expand...
Click to collapse
I think it might have failed because I flashed a module. Don't think you can do that in the current beta and still pass the new safety net.
That could very well be the issue, currently only using Magisk for root, no modules
I had SafetyNet working with v12 but then on the next reboot it failed. I upgraded to Magisk v13 and again it worked for one reboot. Also looks like the OTA is for unlocked models only (not Sprint)... anyone got any others ideas?
Hi all,
Just tried to flash the latest Magisk (16.0) from TWRP on my honor 8 running B360 and am now in a a bootloop.. Nothing new fixing this but does anyone know what version of magisk will work or why this could have happened? I'm keen to get it working!
Cheers
So I've tried to flash back to an unrooted rom and must've broken something because I now cannot get into TWRP at all. I fastboot flash version 3.1.1-1 which has worked for me countless times and fastboot says it flashes fine but when I try and boot into it with power+vol up the phone goes off for a second, vibrates, pauses for another second before vibrating again and then showing the device cannot be trusted screen. Has anyone ever had this? I'm not sure what else to try here (I also tried flash stock recovery and it does the same thing)
Edit: Got TWRP back, I think my device must be on an earlier version (even though it's corrupt). In case anyone else finds this, this thread helped me https://forum.xda-developers.com/honor-8/help/please-help-boot-enter-recovery-t3660408/page3
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Mumtaz77 said:
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Click to expand...
Click to collapse
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
JoshSnitz said:
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
Click to expand...
Click to collapse
Unfortunately it didn't work - resulted in the bootloop again
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
xuso77 said:
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
Click to expand...
Click to collapse
Yeah, using twrp-3.1.1-1-frd.img. Phone is EMUI 5.0, android 7.0 FRD-L09C432B360
Edit: I have the AL version with dual sim that I've re-branded. Could this be causing an issue?
I don't think so, but I don't know.
Can you try to flash the last magisk developer version, or wait for another user that rebranded the honor.
Good luck!
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
hackslash said:
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
Click to expand...
Click to collapse
Oh, I'll give it a go. Is it more reliable to just flash through fastboot or the zip through twrp?
Edit: Both v14 and 13 gives boot loop when flashed from twrp
Hi,
I'm looking for a solution to root Huawei Mate 20. I couldn't find much on web search about this topic.
I am also not able to find a way to install TWRP or unlock boot loader.
Any ideas?
Sent from my HMA-L29 using Tapatalk
My phone got an update about a week ago. The details didn't mention Anything about boot loader unlocking but when I checked after the update, there was the ability to unlock the bootloader.
I have already opened the developed settings since november but the bootloader unlock option was greyed out and could not be turned on. I read a post from a different thread that his phone recently got an update with the option to turn on the bootloader unlock option. I have been regularly checking for update since I read that post and so last week I finally got it. I am now able to toggle the switch but I did not finish the process because I want to make sure it doesn't cause any warranty issues. I have been a Samsung user and I am very familia with the "warranty void 0x1" issue so I always waited until my warranty was over before rooting my phone. That way everythung has been tried and tested before I take a leap. If you do get the update please post your experience in unlocking the bootloader and eventually rooting your phone.
Sent from my HMA-L29 using Tapatalk
Maybe try kingroot? If it gets the job done on the pro version it might do it here as well.
Found it: https://www.techdroidtips.com/install-custom-rom-huawei-mate-20-cwm-twrp/ https://www.techdroidtips.com/root-huawei-mate-20/
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Hi please create a new thread how to root the phoneee?
Oem unlock is back :cyclops:
Hi, I can't find Twrp for huwaei Mate 20 can you help me?
Wysłane z mojego HMA-L09 przy użyciu Tapatalka
OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Mate please help us.
EDIT:
sorry, now found your post: https://forum.xda-developers.com/mate-20/how-to/guide-manual-updating-firmware-t3892686
so only way to get root it's paying for bootloader code?
OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?
JazonX said:
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?
Click to expand...
Click to collapse
nope, my international mate 20 didn't receive 9.1 yet.
Regards
There is info about root EMUI 9.1 for mate 20X on XDA. "[GUIDE] Root AL00 EMUI 9.1"- https://forum.xda-developers.com/mate-20-x/how-to/guide-root-al00-emui-9-1-t3938483. You need Ramdisk for your device and patche it. Also it is possible to extract Ramdisk from full firmware. Now i have a problem to download full firmware for my phone - HMA-L29 9.1.0.310(C10E10R2P1). I tried https://support.halabtech.com/index.php?a=downloads&b=folder&id=35991 but it is impossible to download zip file. Is there another way to get this firmware?
Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6
ZTNL said:
Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6
Click to expand...
Click to collapse
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.
Need Unlocked Bootloader?
vstrglv said:
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.
Click to expand...
Click to collapse
Could you give a short tutorial of how you did that? Did you have to unlock bootloader?
I guess that unlocked bootloader is required to flash boot image, but I hope to be wrong
Yes, I have unlocked bootloader.
vstrglv said:
Yes, I have unlocked bootloader.
Click to expand...
Click to collapse
Where did you get the bootloader unlock codes? HW no longer support to release it...
I got unlock code on this forum from Crys18 on 30.03.2019 for $6.
Root on EMUI 10
Has anyone rooted the new EMUI 10? Can you give me a how to?
vstrglv said:
I got unlock code on this forum from Crys18 on 30.03.2019 for $6.
Click to expand...
Click to collapse
How can I contact him?
So i have installed android Q beta 3 but when i try to flash latest bluespark twrp via Fastboot its showing this everytime.
FAILED (remote: unknown command)
Though i am typing correct command
Fastboot boot twrp.img
Any help
Flash VIA fastboot mode.
Wysłane z mojego Redmi K20 Pro przy użyciu Tapatalka
jumis said:
Flash VIA fastboot mode.
Wysłane z mojego Redmi K20 Pro przy użyciu Tapatalka
Click to expand...
Click to collapse
Command i have mentioned is already Fastboot method
Do you have the latest version of the SDK Platform Tools on your computer?
makeyourself said:
Do you have the latest version of the SDK Platform Tools on your computer?
Click to expand...
Click to collapse
Give link. But previously there is no such problems
I am experiencing exactly the same problem.
pankspoo said:
Give link. But previously there is no such problems
Click to expand...
Click to collapse
Perhaps but you've installed a new version of the Android Bootloader which interfaces with fastboot. Possibly the Q upgrade also changes your partition layout, I don't know.
The link can be easily found on google but here it is anyway.
makeyourself said:
Perhaps but you've installed a new version of the Android Bootloader which interfaces with fastboot. Possibly the Q upgrade also changes your partition layout, I don't know.
The link can be easily found on google but here it is anyway.
Click to expand...
Click to collapse
Yes i think so, but how can be this problem person specific as u told its working for you?
Anybody who solved this problem? Having the same problems here
It's a known issue. For now, you could try flashing fastboot Pie ROMs. Next time you flash any ROM, flash TWRP afterwards.
If flashing fastboot ROMs also give you problems, then your only remaining chance is to use MSM download tool.
mideg said:
I am experiencing exactly the same problem.
Click to expand...
Click to collapse
Same but in 9.0.8
fastboot boot twrp.img just doesn't seem to work under Android Q anymore. I have the TEST version of TWRP and that doesn't flash with fastboot boot either :/
So I also experienced this problem last night. Had to forego sleeping just to get it to work. Thankfully it's a Sunday.
Anyway, after extensive searching, I have concluded that it is indeed caused by an updated bootloader that disables the "fastboot boot" commands. The OP7 Pro also has this problem.
Unfortunately, flashing stock Pie fastboot ROMs don't fix the problem. I tried flashing all the way back to OOS 9.0.5, but it seems like the bootloader didn't revert and is still unable to accept "fastboot boot" commands.
In my case, I needed TWRP to flash Magisk. Fortunately, we can install Magisk without flashing via TWRP. It's as simple as installing the Magisk Manager APK from topjohnwu's github, and patching the OOS 10 boot.img. I believe there's already a thread somewhere here that provided the patched boot.img. all we need to do is just fastboot flash boot magisk-boot.img, and we should be rooted. I can even install some mods.
For the fastboot issue though, I don't think we're gonna find a fix any time soon.
I have the same Issue.
Went back from Q Beta to 9.0.9 Stable and also flashed the original bootloader.
It's still not possible to fastboot boot TWRP. I'll hope this will be fixed soon...