Database Develop

Boot loop on a HTC M9 (with 6.0), which was fine with systemless root in the past

My HTC M9 (with Android 6.0, HTC version number is 3.36.709.3) was working fine with Magisk(systemless framework)V3 + SuperSU v2.76 (mod by @topjohnwu) before last Friday. After a power shortage (running out of battery) of the device, the UI keep crashing and reboot. I can't do anything, therefore, I planned to backup and full-reset my device and start from beginning. But I found that I can't make any root work again. I had tried several combinations of flashable zip packages:
MagiskV3+SuperSUv2.76(mod, filename SuperSU-v2.76-magisk.zip )<=I use exact same package on my local storage, which was working in the past, therefore it can't be the issue of these archives
MagiskV3+SuperSUv2.76(mod, newer than file above, filename UPDATE-SuperSU-v2.76-magisk.zip)
UPDATE-SuperSU-v2.76-20160630161323.zip
SuperSU-v2.78-201609011115.zip
Once I flashed anyone of these zip combinations in TWRP (with no error message in screen) and reboot, the system will start boot looping, with no adb capability at all, therefore I don't know how to debug here.
(I believe that launch_daemonsu.sh had been ran since SuperSU.apk had been installed correctly and SuperSU.apk no longer in /data/ after reboot)
(And I've also tried to confirm patch status by extracting boot partition with sukernel and check if the boot partition is patched/fstab had been modified/scripts are added, they are)
But once I restore the boot.img from backup (no matter TWRP restore or fastboot flash boot), the system will boot correctly again.
I did restore TWRP backup between each test, and I even tried to restore RUU between each of test, no success.
Can anyone help to guide me how to debug in such situation?
Does it matter if my device is still S-ON?
I attache the log of SuperSU installer in TWRP for reference.

Is the systemless supersu from www.supersuroot.com/ even legit? On this kind of things my trust is all in XDA

cbroeter said:
Is the systemless supersu from www.supersuroot.com/ even legit? On this kind of things my trust is all in XDA
Click to expand...
Click to collapse
It is not.
There are people taking a number of my apps, registering domains, and putting them up without my consent. That site is one of the fakers (the guy behind it has many).
The APK and ZIPs they serve may be the originals, they might be modified. I don't know.
I've tried taking them down in the past, but it's a never-ending story. Can't even get Google to stop serving ads to these pages
For my stuff, only trust links from my own site (chainfire.eu) and the Play store.

Magic v11 installation question

Hi, do i need install systemless SuperSU always in twrp before install magisk v11 if I want use new MagiskSU instead??
If I try install Magisk v11 with superSU uninstalled and phone unrooted TWRP give me error and installation fails and if I install superSU and after Magisk v11, Magisk manager say system is using SuperSU instead MagiskSU. How do I install Magisk with MagiskSU??
I have Samsung Galaxy S4 with optimized LineageOS 14.1

Read the pinned Magisk thread...
Unroot again using unSu by osm0sis (Google) before flashing magisk

Installation Instructions
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
Click to expand...
Click to collapse
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Code:
! SU image mount failed...
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
[B]Updater process ended with ERROR: 1
Error installing zip file 'sdcard/Download/Magisk v11.1/Magisk-v11.1.zip[/B]

dhaern said:
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Click to expand...
Click to collapse
You need to FULLY unflash superSU using the zip that the other person told you to google.

PartyPlease said:
You need to FULLY unflash superSU using the zip that the other person told you to google.
Click to expand...
Click to collapse
Ok I will try unflash with the zip, I was using unroot inside superSU menu but installation instructions dont say nothing about the unflash with an extrenal script

dhaern said:
Ok I will try unflash with the zip, I was using unroot inside superSU menu.
Click to expand...
Click to collapse
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.

Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.

PartyPlease said:
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.
Click to expand...
Click to collapse
ahh, this would explain why my boot.img was not the same after "unrooting"! thanks for clearing this up for me...

dhaern said:
Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.
Click to expand...
Click to collapse
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.

vicky_ag said:
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.
Click to expand...
Click to collapse
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.

dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks but doesn't seem to work for me.

dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks for this hint; got my build "passed" now appreciate it

What settings are you guys using in Magisk? I have disabled BusyBox, enabled Magisk Hide and systemless hosts. Superuser options are Access to "Apps and ADB" and Automatic Response set to prompt

I'm still having an issue installing Magisk on my phone with RAMROM V10. It gives me an ERROR 1.
It has been suggested that I should re-flash my boot.img with TWRP following the instruction:
Place your BOOT.img on your sdcard
Reboot into TWRP recovery
Tap "Install"
In the bottom right corner tap "Install Image"
Select your BOOT.img
Select the Boot Partition, then swipe to confirm Flash
However, when I follow the step, my TWRP cannot seem to find BOOT.IMG in my SD Card (I know it is there). What did I do wrong? Can anyone help?

i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files

sm00th4f3 said:
i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files
Click to expand...
Click to collapse
FIY: Flashing regular boot.img files works just fine with "Install Image" in TWRP (of course, YMMV, depending on your device).

Best way to update? 148 SP1

Can anyone help and tell me the best or easiest way to update my BLA-L29 8.0.0.142 (C432)
It is unlocked bootloader and rooted with twrp.
I tried to download the 148.SP1 and Install it with Twrp and an installerfile i read that you should place with the update.zip file.
But in the end i never got it to Install the 148 version =(
So please can anyone help and guide me?

You can use huru updater https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Also you should check your xloader version before installing new rom here https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241

lopusina said:
You can use huru updater https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Also you should check your xloader version before installing new rom here https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
Click to expand...
Click to collapse
The huru updater is the one i tried to use. Since i Come from 142 i dont have any xloader version right?
Sp1 is The 01 version from what i read. But i did not get it to work with the huru updater.

HazeTaze said:
The huru updater is the one i tried to use. Since i Come from 142 i dont have any xloader version right?
Sp1 is The 01 version from what i read. But i did not get it to work with the huru updater.
Click to expand...
Click to collapse
B142 is 01 xloader, B148-SP1 is 01. (B148 is 02).
But B148-SP1 is not passing SafetyNet, if you're relying on that.
You can flash Magisk and install the MagiskHide Props Config module, there you can spoof your device fingerprint to B137 and it will pass safetynet.
First make sure you are using a supported recovery. Official TWRP is not supported as it lacks many things needed.
TWRP by Pretoriano80 works fine, found here: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Place HuRUpdater_0.4.zip, update.zip, update_data_public.zip and update_all_hw.zip (Public and hw zips renamed) in the same folder. Place twrp named recovery.img if you want to keep it after flashing, else you get stock recovery.
Flash HuRUpdater using the install button.
If it still fails, post recovery log here (Advanced -> Copy Log, log is copied to /sdcard/recovery.log).

ante0 said:
B142 is 01 xloader, B148-SP1 is 01. (B148 is 02).
But B148-SP1 is not passing SafetyNet, if you're relying on that.
You can flash Magisk and install the MagiskHide Props Config module, there you can spoof your device fingerprint to B137 and it will pass safetynet.
First make sure you are using a supported recovery. Official TWRP is not supported as it lacks many things needed.
TWRP by Pretoriano80 works fine, found here: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Place HuRUpdater_0.4.zip, update.zip, update_data_public.zip and update_all_hw.zip (Public and hw zips renamed) in the same folder. Place twrp named recovery.img if you want to keep it after flashing, else you get stock recovery.
Flash HuRUpdater using the install button.
If it still fails, post recovery log here (Advanced -> Copy Log, log is copied to /sdcard/recovery.log).
Click to expand...
Click to collapse
What i did wrong was that i forgot to completly rename the new files to the right name, now it worked and I guess i can withstand safetynet for now. Dont know how it will affect me?
Thanks a lot for The help anyway!

HazeTaze said:
What i did wrong was that i forgot to completly rename the new files to the right name, now it worked and I guess i can withstand safetynet for now. Dont know how it will affect me?
Thanks a lot for The help anyway!
Click to expand...
Click to collapse
It affects a handful of apps, Android Pay and snapchat to name a couple. Some banking apps use it too.

and Fortnite...
ante0 said:
It affects a handful of apps, Android Pay and snapchat to name a couple. Some banking apps use it too.
Click to expand...
Click to collapse
...if you are so inclined

rbt001 said:
...if you are so inclined
Click to expand...
Click to collapse
That too. But I'm not sure if it needs both basic and CTS profile to pass or just checks for root... I tried getting it running with Note 8 props but it refused, kept coming to the "Android Beta" request page.

ante0 said:
That too. But I'm not sure if it needs both basic and CTS profile to pass or just checks for root... I tried getting it running with Note 8 props but it refused, kept coming to the "Android Beta" request page.
Click to expand...
Click to collapse
Well... I got it running but eventually got this message...
EDIT: hmmm... not sure if my screenshot got attached. The text says: Unable to run Fortnite on a device that has been rooted, has an unlocked bootloader, has the Android Debug Bridge active, or has failed the SafetyNet check.

The root permission request is no longer displayed

I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?

@rovo89

@topjohnwu

https://www.didgeridoohan.com/magisk/MagiskHelp

I have added much more information.

Reinstall firmware???

LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?

535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe

Question Step by step help to modify Redmi 9T

Hello everyone and my apologies for my terrible English (I did this with the help of Google Translator) since I cannot find reliable information in my language (Spanish).
I just bought a Redmi 9T model M2010J19SG (4/64 GB, Android v10, MIUI v12.0.5, unmodified) and I would like to be able to restore some applications, as they were configured on my previous mobile (Galaxy S4 GT-I9500 Android v4.4.2 , rooted), for this I tried to use Titanium Backup Pro that I have been using for a long time for my backups and restorations but the Redmi does not allow it because I am not a root user on that phone.
Someone could help me, step by step, on how to install the appropriate TWRP on my Redmi 9T, to then be able to install and use the Magisk to root the phone and be able, using the Titanium, to restore those applications that interest me so much.
Thanks

First, unlock the bootloader by following this guide: https://romprovider.com/unlock-bootloader-redmi-9-power/?amp
Wait for 7 days max, and then try going to the fastboot mode and unlock it again. Do not log out your MIUI account on the device otherwise the timer would reset. Feel free to use the device while waiting, you wouldn't want to wait in the fastboot mode, do you? Hahaha jkkk
And then go to this post to download OrangeFox recovery: https://forum.xda-developers.com/t/...dmi-9-power-redmi-note-9-4g-redmi-9t.4263407/
And here, look for the fastboot instruction, follow that to flash OrangeFox to Redmi (DO NOT do the zip instruction, it wouldnt work on the stock MIUI recovery): https://wiki.orangefox.tech/en/guides/installing_orangefox
STAY ON THE RECOVERY ONCE YOU HAVE FLASHED IT!!!
Do not reboot to the system, if you accidentally do, just reflash the OrangeFox recovery as MIUI have already replaced it with the stock recovery.
Anyways after that, you should have a working recovery, now using a computer go to Magisk github release page, download the version 23 zip file: https://github.com/topjohnwu/Magisk/releases
While still on recovery, connect your Redmi 9T to the computer using cable, it will show up as MTP device. Just copy over the magisk file I mentioned to the Redmi. I forgot you can actually download this and copy before unlocking your bootloader so you won't have to later.
Locate the magisk file in OrangeFox and then flash it. VOILA you're done! Reboot to system.
==
BACKUP YOUR FILES AND APP DATA!!! In case something goes wrong. I do not guarantee this would work. Feel free to get help though...
To uninstall magisk, duplicate the magisk zip then rename it to uninstall.zip - flash in the recovery as usual.
I know a simple thing but, use a pin code or a password so you would be able to unlock the /data partition in OrangeFox. You would see the unlock screen right away after booting to the recovery, just enter your code or password and you're good to go.
Sorry that no one answered you, i don't know perhaps right now you could have already figured out how to, but nonetheless this would be a reference to those who are about to do the same thing as you wanted.

I forgot you said TWRP, im sorry.
Anyway the TWRP link: https://forum.xda-developers.com/t/recovery-3-5-a10-twrp-unnoficial-for-lime-redmi9t-beta.4233045/
The general steps are more or less the same. That post also contains instructions how to flash TWRP. Feel free to ask questions if you need help.

AJPuzon​Thank you, thank you and thank you very much for the explanation. I will follow your recommendations and when I finish I will report the results.

Also gonna put this here while I still remember:
It's very likely that the phone will fail SafetyNet once Magisk is installed. Hence no banking apps will work and you cant install apps that require Safetynet (they will be hidden) So here's what I did on mine to pass it again:
1. Go to Magisk settings (should be at the top right cog icon), turn on MagiskHide.
Now go back, tap the shield icon below (Superuser requests) MagiskHide is now visible, go to that. Tap Google Services and it will expand, check all the additional items under it.
- do this for all the other google apps that you have installed.
2. Go to Magisk settings again and the turn on Hide Magisk. Name it to whatever you want. Reopen Magisk using the new program name that you assigned it to. Reboot.
3. And then go ahead and clear the App Data of both Google Play Services and Google Play Store. Reboot
Additional steps for custom roms:
1. Go to modules (4th option below) and then install MagiskHide Props Config. Now reboot.
2. Go to Play Store and then install a terminal application. (Material Terminal is what I use in this case).
3. Open the terminal app, type props then press enter, after follow the instructions to find your device in the list, change your device fingerprint to that. Reboot once done.
4. Again clear the app data of Google Play Services and Google Play Store, and reboot.