Develop Bugs

Cannot root my S9

Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?

Nairozed said:
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Click to expand...
Click to collapse
Try use magisk 16.6 for root issues, ofc when you use custom rom you dont get full camera potential and these green flickers are just minor cosmic bugs.

"Myth" might want to read up more.
You need to flash twrp and flash the no verity file then flash the custom rom
Or even better, flash soldiers rom instead of the resurrection remix. Didnt you read that theres a camera problem?
Better use magisk for rooting btw, use the 16.6

Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?

Nairozed said:
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Click to expand...
Click to collapse
try flash rom + gapps and boot system after that boot recovery and flash magisk 16.6 and boot system

Thanks for the advice. I flashed back to stock firmware to have the zerocam mod working perfectly. But now my lockscreen freezes after a few minutes. So I tried to deactivate my phone going into lockscreen. I get the Black screen of Death now instead when the display turns off into sleep mode. Only way out is rebootingby hard reset, power button+volume down.
What can I do?.... Thanks for Any further advice.

not have logo to sharj

I'm root my A2lite(ptchboot and install Magisk)
but i turn off my phone and connect to sharj
is turn down,no go logo to sharj!!!

hosseinj2 said:
I'm root my A2lite(ptchboot and install Magisk)
but i turn off my phone and connect to sharj
is turn down,no go logo to sharj!!!
Click to expand...
Click to collapse
You turned off the phone, and while off, you connected a charger.
You expect to see something on the screen...
I'm not sure if this works because I never have my phone off
It could be the unlocked bootloader rather than Magisk that has caused this?
I'll do some tests tonight.

yes, turn off your phone and connect to charge,you see logo to charge battery!
but I don't have,
I think i flash patchboot this happen

Ok, so first some disclaimers...
1) I am running 10.0.10.0 with an unlocked bootloader.
2) I have both TWRP (3.3.1-dees_troy) and Magisk (19.3) installed.
3) I have a custom splash screen (https://forum.xda-developers.com/mi-a2-lite/themes/splash-image-maker-t3914702).
I turned off my phone and plugged it into the charger.
I saw the Android one logo for a bit.
I saw a battery indicator briefly.
The screen turned off.
I unplugged the phone and tried to turn it on... I'm not sure what was going on but the power button wasn't working, probably the phone was "turning off" after charging?
I plugged the phone into the charger again and it showed the battery indicator, but the screen was flickering on and off. I seem to recall discussion of this on these forums back when I first got the phone. As I said, I don't normally turn my phone off so I don't see this issue.
I did a bit of digging and found this old thread, which suggests that both TWRP and Magisk cause the charging animation to break, and that the phone won't charge while in this state. https://forum.xda-developers.com/mi-a2-lite/help/battery-animation-charge-power-off-t3875783
Both TWRP and Magisk modify the boot partition. I guess they do something that interferes with the charger animation. If I'm reading this right, /init looks at /init.rc and there's a case for running /charger -> /sbin/charger -> /root/charger, which is I guess what is responsible for doing the charging animation.
I found a page where someone describes bypassing this state and just booting the phone when the charger is connected. If I turned my phone off more often, I might be interested in doing this... https://appdictive.dk/blog/android/how-to/2017/04/20/disabeling_offline_charge_on_android/

a1291762 said:
Both TWRP and Magisk modify the boot partition. I guess they do something that interferes with the charger animation.
Click to expand...
Click to collapse
I feel like I'm going to sink a bunch of time into this...
I compared my vanilla and Magisk-patched boot images. It looks like Magisk changes both the kernel (zImage) and init, but not init.rc or charger. The patched image has a backup of the original init on it, so maybe the modified init just does Magisk stuff before restoring the original init and booting normally...
I kind of curious now and interested in trying to poke at this but it's going to be very slow going. Making changes, repacking the boot image, fastboot flashing then powering off and booting with the charger. And it'll be even slower if I can't figure out a way to start adb from that state (or save logs somewhere persistent, not sure if this happens before /data has been mounted).
I wish this phone had a serial port in the headphone Jack like Asus/Nexus devices do... but I couldn't find any information suggesting it has and I'm not about to put voltage into the microphone pin in the hope that it does.

thank you to answer.but I don't understand good
if i flash this file which fastboot my logo charge is come back?and root is working?(my build is v 10.0.9 Android 9)

hosseinj2 said:
thank you to answer.but I don't understand good
if i flash this file which fastboot my logo charge is come back?and root is working?(my build is v 10.0.9 Android 9)
Click to expand...
Click to collapse
No, that does not seem to be the case.
Based on the old thread, you need to go back to stock boot image (no twrp or Magisk) to get charging while off to work again.
I plan to try some tests of custom boot images to see if I can get it to work right, but it may take some time.

a1291762 said:
No, that does not seem to be the case.
Based on the old thread, you need to go back to stock boot image (no twrp or Magisk) to get charging while off to work again.
I plan to try some tests of custom boot images to see if I can get it to work right, but it may take some time.
Click to expand...
Click to collapse
ok , I'm waiting than you

I did a bit of digging...
charger is the binary that runs when you boot with the charger plugged in. It's in AOSP (code for Mi A2 Lite is probably different and probably not open sourced): https://android.googlesource.com/platform/system/core/+/jb-mr1-dev-plus-aosp/charger
I unpacked a few images and looked at the charger binaries. I found that there seems to be many versions of this binary. One for each of Oreo, Pie, TWRP (dees_troy), TWRP (offain).
I found a reference to the MIUI charger binary being used for the Mi A2 Lite Linage build (because it works?)...
https://github.com/33bca/android_device_xiaomi_daisy/commit/47fd114e0062659a840e6bebaf57f4fb77b976c1
I downloaded both the Lineage ROM and a Redmi 6 Pro boot.img and confirmed that Lineage is using the Redmi 6 Pro's chargeonlymode binary.
Alas, when I attempted to pack this into a boot.img and flash it, both twrp and the system failed to start. But that could just be because I can't actually pack a working boot.img...
I was able to copy the binaries onto the phone and run them from TWRP (I use 3.3.1-dees_troy). The binaries fought with the recovery for control of the screen occasionally, but I was able to observe at least some of the binaries apparently working correctly.
- oreo - screen lit but black
- pie - screen lit but black
- twrp 3.3.1-dees_troy - displayed as numbers and text
- twrp 3.3.1-offain - screen lit but black
- lineage - graphical display
I also noticed that when the binary worked, it fairly aggressively turned off the display. I had to press the power button, sometimes several times, to get the display to come on briefly showing the charging image before it turned off again.
When I unpacked my actual boot.img (extracted from the phone), it had TWRP's charger binary (ie. installing TWRP replaces your charger binary?) but when I actually boot the phone, that's not the binary I see. Instead, /sbin/charger is a link to /root/charger, which is the Pie binary. When I boot to TWRP, I see the TWRP charger binary. I wonder if this is something to do with Magisk?
I'm not yet sure what all this means... When I flashed a vanilla image and plugged my phone into a charger, it sort-of seemed to work but the screen turned off quickly. But maybe that's just the "aggressive" screen turning off I noted when I ran the binaries from TWRP?
I'll try to confirm this, plus any difference between having only TWRP, only Magisk or both.
And there's always that Lineage binary, if I can get it packed into a boot.img...

Applying Magisk to OnePlus 3 on Android Pie results in a soft-brick

Yesterday I took some time to attempt to upgrade my OnePlus to Android Pie after finding out earlier that it's not as simple as just installing an update when your boot loader is unlocked. After a bit of searching I found this guide which I followed to upgrade OxygenOS to version 9.0.5. After some initial problems (I didn't pay enough attention and TWRP was set to auto-reboot which complicated matters a little) I managed to finish the upgrade and the device booted.
After confirming everything worked well I figured I should flash Magisk back onto the device so that I would have root access again. I flashed Magisk 19.3 and tried to boot the phone but it got stuck on the spinning OnePlus logo during boot. Left it running for over an hour, nothing happened so eventually I decided to flash the OTA update and the BL/KM patch again, which made my phone boot again but without Magisk, obviously.
After that I tried flashing Magisk 19.2 and Canary (19.4), both with the same results: a spinning logo, nothing more.
I'm not sure what else I can try. In a particular braindead moment I thought I should just try to take a look at Magisk's log file but of course that's not accessible without root access. I've got a feeling that the patch to the bootloader is causing issues with Magisk's firmware patch but I'm not familiar enough with this kind of problem to figure out what is going on exactly.
Does anyone recognize this problem or can one of you tell me what I could try to get Magisk running again?

I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot

dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot
Click to expand...
Click to collapse
Thanks, I'll give it a go later tonight!

dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Click to expand...
Click to collapse
I tried it just now. Sadly I get the same end result. Thanks anyway though.
I have an ADB log of the crash that happens that causes the phone not to boot, maybe that's familiar to someone around here? I uploaded it here.

Hello can I ask a question why do you need root

OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6. I flashed Magisk with no issue. Here are the steps I took:
Starting with unlocked BL
Boot into the newest official version of TWRP via fastboot.
Flash OOS 9.0.5 and boot into it, completing device setup.
Reboot into OnePlus recovery, then from within, reboot into fastboot
Flash TWRP to recovery in fastboot, then shut down device (do not attempt to fastboot reboot recovery, it will boot into OOS and overwrite TWRP)
Boot device, use volume key to interrupt startup, boot into recovery (TWRP)
Follow installation instructions from Havoc thread, do not wipe cache/dalvik after flashing, do not boot before flashing all zips (I flashed ROM -> gapps -> Magisk in that order)
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.

kallum7 said:
Hello can I ask a question why do you need root
Click to expand...
Click to collapse
I work on an app that uses location data and it's pretty convenient to be able to test it on a real device but with a joystick instead of real location data. To make matters more complicated it's my personal phone and I use that to play Pokémon Go too. Without cheating I might add, the root is not for PG but because I do want to be able to play it on the same phone that I use to test my app I need Magisk to hide the fact that it's rooted or the game won't start.
LunarisDream said:
OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6.
Click to expand...
Click to collapse
Thanks for the suggestion but I'd rather keep using OOS on this phone as long as I don't have a new phone for daily use. I don't really want to modify this thing too much without having a replacement ready in the likely case that I screw something up.
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.
Click to expand...
Click to collapse
I tried both flashing the OTA, the modded firmware and Magisk in one go and separately after confirming that the OTA/FW were working. Sadly both methods resulted in the same problem.

If anyone's wondering I did a clean flash and factory reset, then installed Magisk again after that. Everything's working again now. Thanks for trying to help!

[Help] Oneplus 7T Qualcomm CrashDump Mode

Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
dm-verity device corrupted Force Dump
Kernel_restart
Click to expand...
Click to collapse
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?

Which specific model do you have, region? Which twrp was used?

Werchio said:
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Click to expand...
Click to collapse
TWRP?! There are no working twrps for 7T series.

gpz1100 said:
Which specific model do you have, region? Which twrp was used?
Click to expand...
Click to collapse
Oneplus 7, EU region (guacamoleb). TWRP that I have managed to boot into is 3.3.1-70.

Aswin08 said:
TWRP?! There are no working twrps for 7T series.
Click to expand...
Click to collapse
My bad. It is a Oneplus 7 Guacamoleb, TWRP version is 3.3.1-70

Oneplus 7T Qualcomm CrashDump Mode
Hi Everyone,
My OnePlus 7T got stuck in QUALCOMM CRASHDUMP MODE.
First, i wanted to know the reason why this crash is happening as i can see many users reporting the same in many forums.
Note : It is my brand new phone purchased 2 days back.
Thanks !!

Restor your firmware with the msmtool

Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" .
Now ADB,Fastbootd and Windows 10 / Mac OSx do not see my device, let alone recognize

It's possible that your phone is corrupted. Double freezer bag phone, express all excess air out from bag, zip both bags tightly, stick phone in freezer for 1 hr to deplete battery, then try buttons and msmtool

Question Battery percentage broken since installing a custom rom (Poco F3)

Hi all,
first, i have installed LoS and followed the instructions from their website. i was stuck at LoS boot logo then.
After that, i've installed Arrow OS (Android 12) from the XDA thread and followed the guide. it worked and runs smooth but i've got a problem:
Since i've installed arrowOS, my battery percentage is stuck at 93%. I've tried things to fix it, like installing LoS again. Same problem there.
I went back to stock global rom with XiaoMiFlash and got the same problem at stock os now. i dont know, how is the percentage calculated and why it is stuck forever now. even if my phone is off and i plug in the charging cable, same problem with 93%. maybe the poco f3 has an hardware detection for battery percentage and i did something wrong while flashing custom roms ? is there any way to fix it ?
would be nice if anyone can help me
thanks in advance

Hi, Sorry its not related to your issue but just wanted to know how easy is it to flash the stock ROM and do you have the steps or YouTube video which you can share?

sickestbreed said:
Hi all,
first, i have installed LoS and followed the instructions from their website. i was stuck at LoS boot logo then.
After that, i've installed Arrow OS (Android 12) from the XDA thread and followed the guide. it worked and runs smooth but i've got a problem:
Since i've installed arrowOS, my battery percentage is stuck at 93%. I've tried things to fix it, like installing LoS again. Same problem there.
I went back to stock global rom with XiaoMiFlash and got the same problem at stock os now. i dont know, how is the percentage calculated and why it is stuck forever now. even if my phone is off and i plug in the charging cable, same problem with 93%. maybe the poco f3 has an hardware detection for battery percentage and i did something wrong while flashing custom roms ? is there any way to fix it ?
would be nice if anyone can help me
thanks in advance
Click to expand...
Click to collapse
I'm having the same problem and tried flashing stock but battery percentage didn't change, did u find a fix yet ? i didn't try waiting for the phone to be drained completely

Younes_bfd said:
I'm having the same problem and tried flashing stock but battery percentage didn't change, did u find a fix yet ? i didn't try waiting for the phone to be drained completely
Click to expand...
Click to collapse
Nope, I didnt solve the problem yet. Can you please explain since when you got this problem ? was it after flashing a custom rom or after unlocking the bootloader ?

sickestbreed said:
Nope, I didnt solve the problem yet. Can you please explain since when you got this problem ? was it after flashing a custom rom or after unlocking the bootloader ?
Click to expand...
Click to collapse
After flashing a custom kernel
It's fixed now after flashing fastboot stock ROM twice, then I went to stock recovery and wiped data
Update: after rebooting the device i see different percentage, will drain it then charge to 100 and calibrate

I found that after you changed from Custom ROM, sometimes the speed of the SoC stuck on 2.7Ghz instead of 3.2Ghz. Flash (DONT LOCK) with Stock Chinese ROM (Redmi K40) will fix the stuck, maybe this problem also like that. And after Flashing with Chinese ROM, flash again to your wish Stock ROM (Global, EEA, ID, etc.).

Younes_bfd said:
After flashing a custom kernel
It's fixed now after flashing fastboot stock ROM twice, then I went to stock recovery and wiped data
Update: after rebooting the device i see different percentage, will drain it then charge to 100 and calibrate
Click to expand...
Click to collapse
Hello, could you tell me what kernel you used