Develop Bugs

SU BiNARY NEEDS UPDATE, STUCK IN BOOT LOOP

Hello People
I have a problem with an update. (My phone is S-off and rooted.)
Everything works fine until it prompts me that the SU BINARY needs to be updated.
When I follow the instructions, and as far as all I have found on goole/youtube, I get stuck in when rebooting. All I see is the HTC logo.
I have even tried to dowload the SU.zip update to my computer, then drag it to external SD card, go into recovery mode then update from there.
But still, my HTC 10 gets stuck when the HTC logo is on screen.
To fix it out of that state I have to reinstall Viper Venom.
Please any suggestions?
Am I missing something?????
Thanks from Sweden

DeluxeSpade said:
Hello People
I have a problem with an update. (My phone is S-off and rooted.)
Everything works fine until it prompts me that the SU BINARY needs to be updated.
When I follow the instructions, and as far as all I have found on goole/youtube, I get stuck in when rebooting. All I see is the HTC logo.
I have even tried to dowload the SU.zip update to my computer, then drag it to external SD card, go into recovery mode then update from there.
But still, my HTC 10 gets stuck when the HTC logo is on screen.
To fix it out of that state I have to reinstall Viper Venom.
Please any suggestions?
Am I missing something?????
Thanks from Sweden
Click to expand...
Click to collapse
Are you on Nougat or MM?

donkeykong1 said:
Are you on Nougat or MM?
Click to expand...
Click to collapse
Hi
I have 7.0 nougat

You can't flash SuperSu on Nougat. You need Magisk to root your phone. I learned that the hard way ?

donkeykong1 said:
You can't flash SuperSu on Nougat. You need Magisk to root your phone. I learned that the hard way
Click to expand...
Click to collapse
I'm on Nougat and rooted with Supersu without Magisk.

benzo said:
I'm on Nougat and rooted with Supersu without Magisk.
Click to expand...
Click to collapse
Please share. I tried SuperSU, and ended in bootloop every time

donkeykong1 said:
You can't flash SuperSu on Nougat. You need Magisk to root your phone. I learned that the hard way
Click to expand...
Click to collapse
oh... haha I understand..
So you know if there any way to change the root? Since I didnt use magisk..

DeluxeSpade said:
oh... haha I understand..
So you know if there any way to change the root? Since I didnt use magisk..
Click to expand...
Click to collapse
Let's wait for @benzo's reply. He says he rooted without Magisk. I really want to know the procedure too

donkeykong1 said:
Please share. I tried SuperSU, and ended in bootloop every time
Click to expand...
Click to collapse
Status: i'm on Nougat 2.28.401.9 EU leaked with Supersu and TWRP 3.0.2-7_UNOFFICIAL.
My steps:
- Donwloaded the RUU firmware, in my case the EU leaked from here https://forum.xda-developers.com/htc-10/how-to/wwe-htc-10-stock-rom-ruu-2-28-401-9-t3525075
- Put firmware on Sd Card
- Go to donwload mode (adb reboot download mode or Power e Vol-)
- fastboot oem rebootRUU
- fastboot flash zip 2PS6IMG.zip
- fastboot reboot-bootloader
- flashed recovery, twrp-3.0.2-7_UNOFFICIAL-pme.img (https://forum.xda-developers.com/devdb/project/?id=14825#downloads) -> steps: adb reboot download mode or Power e Vol- -> fastboot flash recovery twrp.img (twrp-3.0.2-7_UNOFFICIAL-pme.img renamed)
- fastboot reboot recovery
- adb sideload supersu.zip (in my case i used this: SuperSU-v2.79-201612051815.zip)

benzo said:
Status: i'm on Nougat 2.28.401.9 EU leaked with Supersu and TWRP 3.0.2-7_UNOFFICIAL.
My steps:
- Donwloaded the RUU firmware, in my case the EU leaked from here https://forum.xda-developers.com/htc-10/how-to/wwe-htc-10-stock-rom-ruu-2-28-401-9-t3525075
- Put firmware on Sd Card
- Go to donwload mode (adb reboot download mode or Power e Vol-)
- fastboot oem rebootRUU
- fastboot flash zip 2PS6IMG.zip
- fastboot reboot-bootloader
- flashed recovery, twrp-3.0.2-7_UNOFFICIAL-pme.img (https://forum.xda-developers.com/devdb/project/?id=14825#downloads) -> steps: adb reboot download mode or Power e Vol- -> fastboot flash recovery twrp.img (twrp-3.0.2-7_UNOFFICIAL-pme.img renamed)
- fastboot reboot recovery
- adb sideload supersu.zip (in my case i used this: SuperSU-v2.79-201612051815.zip)
Click to expand...
Click to collapse
Thank you very much! I'll try this as soon as I get home from work
Oh, wait... There's SuperSU 2.79??? I thought 2.76 is the latest... That must be it. I'll report when I try it out

donkeykong1 said:
Thank you very much! I'll try this as soon as I get home from work
Oh, wait... There's SuperSU 2.79??? I thought 2.76 is the latest... That must be it. I'll report when I try it out
Click to expand...
Click to collapse
You can get the latest supersu here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Help please!! OTA with Magisk problem

Hi folks, I've a problem with my Pixel 2 XL. I've installed Magisk 16 (1600) on it and I'm trying to update it (April update) throw official OTA following this guide:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Click to expand...
Click to collapse
Unfortunately I'm at "Security update installing..." "Step 1 of 2" since half an hour without moving to Step 2 of 2.
Can you help me please?
:crying:
screenshot attached

I would strongly recommend downloading the full factory image. Extracting the zip and removing the -w in the fastboot -w update in the flash all script. It's way easier!
More details here -
https://forum.xda-developers.com/showpost.php?p=74772300&postcount=296

last_nooby said:
Hi folks, I've a problem with my Pixel 2 XL. I've installed Magisk 16 (1600) on it and I'm trying to update it (April update) throw official OTA following this guide:
Unfortunately I'm at "Security update installing..." "Step 1 of 2" since half an hour without moving to Step 2 of 2.
Can you help me please?
:crying:
screenshot attached
Click to expand...
Click to collapse
That has never worked for me at anytime.
Sideloading the OTA through TWRP works without issue.
My steps
Boot into twrp
Go to advanced
Adb sideload
Swipe to activate adb sideload
From PC run command adb sideload “file path/filename.zip
Reboot, you lost root and recovery, allow OTA to complete install, takes a while
Power down.
Boot to bootloader
Fastboot boot twrp
Flash twrp
Flash MAGISK ZIP

parakleet said:
That has never worked for me at anytime.
Sideloading the OTA through TWRP works without issue.
My steps
Boot into twrp
Go to advanced
Adb sideload
Swipe to activate adb sideload
From PC run command adb sideload “file path/filename.zip
Reboot, you lost root and recovery, allow OTA to complete install, takes a while
Power down.
Boot to bootloader
Fastboot boot twrp
Flash twrp
Flash MAGISK ZIP
Click to expand...
Click to collapse
random question (my apologies OP, I'm not trying to hijack...)...
what version of TWRP are you / have you been using to do this?
...I had attempted this a while back and wasn't able to get it working correctly...I had to resort to THIS...

simplepinoi177 said:
random question (my apologies OP, I'm not trying to hijack...)...
what version of TWRP are you / have you been using to do this?
...I had attempted this a while back and wasn't able to get it working correctly...I had to resort to THIS...
Click to expand...
Click to collapse
The 3.2.1-2 version. Found here.
https://dl.twrp.me/taimen/

Rooting with Android 10

My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?

buddy the best bet for not hard/soft bricking is to downgrade to android 9 and install preloader and then root/install recovery.
if you want you can search "konah begonia guardian" on YouTube. he has quite nice guides.
regards

david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse
FYI this device is really easy to brick that one single misstep can brick your phone and mostly the only way to restore it is via service center. So you must really pay attention to each instruction on the guides. Most root guide need to flash custom recovery first so I guess its inevitable. In order to flash custom recovery, you need to downgrade to Android 9 or Pie, more higher version than that will brick your phone.
In order to root this phone, you first need to unlock the bootloader, refer to here for the guide. (Warning, just follow the unlock bootloader guide since the flashing twrp and rooting guide from there are kinda outdated and not recommended to follow)
Then you need to flash factory firmware (preloader and lk) so you can unbrick your phone in case you brick it, refer to Megathread for guide how to do it. After that you can flash custom recovery, then you can flash magisk via custom recovery to root your phone.

This guy does a ice job explaining a simple root method for Android 10 on youtube

thanks :good:
one more thing , in all methods , after flashing twrp recovery and booting into it the guides say to delere a file called "recovery-from-boot.p".
i saw on telegram channel describing the same mathod but it also said that if i skip the deletion of that file the original recovery will remain , the phone will be rooted
and be able to OTA update.
does anyone know if its ok to do that?

I rooted from Android 10, and same with you, I only need to root to remove ads and install a few apps only.
I used this guide
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Make sure that the twrp is the one that compatible with android 10, otherwise it won't boot to recovery.
Have mi flash app and android stock rom ready on your PC so that if you find problem you can always flash the stock ROM.
david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse

gaban05 said:
I rooted from Android 10, and same with you, I only need to root to remove ads and install a few apps only.
I used this guide
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Make sure that the twrp is the one that compatible with android 10, otherwise it won't boot to recovery.
Have mi flash app and android stock rom ready on your PC so that if you find problem you can always flash the stock ROM.
Click to expand...
Click to collapse
after reading a bit i think the right recovery version to root with android 10 is in the following thread:
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
and this is the procedure:
1. Download recovery file from this message
2. Open CMD from the dir where you store twrp.img (it's important because you don't need to type whole path of the twrp.img
3. Turn off the device, hold Power button & Vol- to enter fast boot and connect device to USB
4. In CMD type first fastboot devices to ensure that device is in fastboot, this is not important but recommended. Output should be something like this 4l6lsctgskpj4swc fastboot
5. Then it's time to flash recovery file. Type fastboot flash recovery twrp.img
6. This is the most important step now, on the device screen it should write USB Transmission ok if that is there you are ready to go. Remove device from the USB and hold Power button & Vol+, When the device turn off the screen keep holding Vol+ it'll keep screen off for about 5-10 seconds, then it'll show a recovery, still holding vol+ because it will get restarted again, and again still holding vol+ and recovery will show up. Simple words (Keep holding vol+ till recovery not appear for second time)
7. If it asks for a password, it's a password you use on the device it self(one for unlocking the screen or unlock the device after reboot), enter password and wait for Data decrypt.
At the moment there is no root and recovery will be replaced after you try to boot next time. To prevent it from replacing recovery do next (my opinion is skipping step 8. and 9. and having stock recovery because of MIUI updates):
8. Go to mount and tick the /system
9. Go back, tap on advanced, then to File Manager search for system_root dir open it, then find system and on the bottom is file called recovery-from-boot.p Remove that file and recovery wont be replaced
Now how we root it:
10. Go to advanced and tap on Close AVB2.0 and swipe to confirm
11. Go back and tap to Install ROOT, swipe to install and Reboot system
This will install Magisk v19.4, after boot you can update it from the Magisk Manager, my suggestion is to first update the manager then Magisk binary.
can anyone confirm that?

Thisnameisepic said:
This guy does a ice job explaining a simple root method for Android 10 on youtube
Click to expand...
Click to collapse
Yes it was his video I used to flash twrp to my phone,his explanation is amazing

david_z said:
after reading a bit i think the right recovery version to root with android 10 is in the following thread:
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
and this is the procedure:...
can anyone confirm that?
Click to expand...
Click to collapse
Yup, that worked for me on Android 10, global 11.0.5.0 QGGMIXM. The LR Team TWRP is the only one that worked for me, and I tried several.
Do make sure you download the v1210 for Android 10...
- in step 5, the 'twrp.img' you write in the command must match the actual filename you downloaded. Either change the name of the file, or enter the full filename in the command line.
- step 6 is kinda tricky. you might not get it right the first time. before installing twrp, i actually made sure i got the key combination right by going into stock recovery a few times.
When you do get TWRP up and running, the very first step is to set the language to English (unless you want Chinese). It will be the lower right buttton on the very first screen you are presented with (where you are asked for your password, if there is one).
I did not do steps 8 or 9, and TWRP has held. I did, however, reboot right back to recovery immediately after my first successful TWRP load-up. That may have stuck it.
The LR Team TWRP installed Magisk 20.3 for me. 20.4 is the latest, but I'm a little timid about letting it update. I had softbrick issues with trying to install Magisk manually thru this TWRP (instead of using the 'Install Root' button). Let me know if you update yours.
HTH

david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse
You can go follow guide from telegram group

i tried twrp avb2.0 but it gave me bootloop after power off and on again , it's better to get the avbmeta image file from fastboot rom(same miui rom you use) and disable it from fastboot mode.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img

Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?

My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!

Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/

didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on

posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?

i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"

kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.

thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?

posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.

thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.

posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.

thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.

Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you

Question Bootloop after battery died

Yesterday it happend suddenly: Battery 5% left, just a quick newsarticle before bed and it left me.
At first it didn't even take any charge. Booted in recovery and it's at 40% now.
But booting doesn't work.
OP Logo, bootanimation for around 20 seconds, repeat...
What I tried:
Power off, reboot
changed active slot
Flash the boot image what was last downloaded by me a while ago (semed to be Boot 12.C44_BA, not sure)
Flash the magisk image
Flashed a C47 image
no difference at all, same boot pattern.
A little sidenote:
I have magisk on my op9p, worked fine. a recent ota update failed repeatedly installing in defaulkt way. at boot i had to switch active slot in fastboot a few times. then it booted to current firmware.
I am wondering why i get the same issue independent from the boot.img.
Why did the low battery started this problem at all? How can i be sure to have the right boot.img flashed.
And most important: how can i boot into andoird again?
let me know if you need more information.
Thanks in advance!
edit:
is it possible to install twrp and backup/restore later the important data?

use msm tool and make all new

ChrisFeiveel84 said:
use msm tool and make all new
Click to expand...
Click to collapse
thanks for the hint! I read about this tool. But this means a full wipe of system and user data, right? any chance to avoid this and rescue images before setting up new?

I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?

Speaka said:
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Click to expand...
Click to collapse
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?

luckylui said:
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
Click to expand...
Click to collapse
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?

Speaka said:
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Click to expand...
Click to collapse
Google search "Tool ALL IN ONE" download it and install. Download the C.62 firmware from one of the threads in the forum. Open the tool you installed earlier select generic device from the pop-up. Click on "advanced options" in the tool and that'll bring you to "adb sideload". I hope that works for you!

This sounds promising. I will try that later. To be sure: This will keep personal data like an usual ota update?
Edit: I'm still stuck. Heres what i do: Boot twrp (not install) from fastboot. in twrp start adb sideload. open the toolaio, generic device, advanced options, select firmware.zip and click flash under sideload. Than it prompts "phone is not in adb or fastboot mode". In the main window it show the device id and "adb sideload".
what am i missing?