Bootloop after supersu binary update - Xperia Z1 Q&A, Help & Troubleshooting

Pretty much as in the title. I believe it was on the dualrecovery root for 5.1.1 and the latest supersu binary update just dropped it into a bootloop. What do I do now?

Same issue here... Don't know what to do!

Welp factory reset in both recoveries didn't do anything.

Seems that manually flashing the 2.81 supersu zip worked for me.

Yep I posted a workaround in the superSU thread a couple of days ago. Flashing the zip version from TWRP works and fixes the bootloop.

i have the same issue and i am not know with this flash stuff
what should i do can some one explain to me

same problem anyone plz post the step to fix this

s2nabil said:
same problem anyone plz post the step to fix this
Click to expand...
Click to collapse
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019

The last SuperSU 2.82 from 28.05.2017 working fine ... at last

Rebel2k said:
Same issue here... Don't know what to do!
Click to expand...
Click to collapse
Same problem but my computer wont recognise my phone & will only charge my phone I bought a new cable aswell still will only charge, Someone if any idea please help be appreciated.

Did you try to start in recovery with your phone, run the TWRP file manager and plug your phone? Don't you get access to the phone file system?

EQ2000 said:
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019
Click to expand...
Click to collapse
https://download.chainfire.eu/1113/S...0528234214.zip
v2.82 updated work fine for me, thank u

EQ2000 said:
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019
Click to expand...
Click to collapse
I was able to solve the boot loop problem with your advice but now the SuperSU icon is disappeared
Any idea how to bring it back?

so I had the exact same problem......supersu asked for an update and that caused a boot loop on my Z1c
I reflashed supersu using recovery,
First v2.82 << that did NOT fix the boot loop
Then v2.79 << this fixed the boot loop.
However, I left the phone to charge for a few minutes and supersu auto updated. Now it says it is v2.82 inside the supersu app. The app still keeps nagging about an update.......which I am not installing, fearing it will cause the boot loop again

Fix
Try to flash supersu.zip in twrp it's works on me

I also as many other users here have updated the library of super Su (got the
notification). And after the installation and rebooting got into the booting loop.
I have wiped cache and dalvick cashe with TWRP but it didn't help. I installed the
2.82 Update-SuperSu via TWRP. And after the long time of apps optimization I was
able to boot into the Android (Lollipop 5.1). However, I found the root was lost.
The RootChecker saying: "Root access is not properly installed on this device".
So, basically my question is how to restore the root and keep the bootloader locked
(important!)
Here I see several scenarios:
1. Restore using TWRP backup.
Should I wipe cache, dalvik cache and data before and after the restore?
2. install Update_SuperSU 2.79 or 2.76 (originally I have version 2.76)
Should I wipe cache, dalvik cache and data before and after the installation?
3. Flash with pre-rooted ROM.
Should I wipe cache, dalvik cache and data before and after the installation?
4. Start from zero, i.e to follow the procedure I have rooted the phone at time
I've purchased it. Namely:
4.1 Downgrade to KitKat
4.2 Root with FlashTool.
4.3 Flash prerooted Lollipop rom with TWRP
4.4 Flash with customized Lollipop rom
Xperia Z3c (compact)
Lollipop 5.1.1
I would appreciate for your suggestions.

Related

Stuck at Mi logo after SuperSU 2.46 flash on latest MIUI 6. Sys 2 working.

I had 6.3.2.0 rooted via SuperSU. I updated it to the latest 6.3.9.0 MIUI6 versiom this morning.
I did not have Survival Mode enabled on SuperSU. After the OS update, I had no CWM or SuperSU or root.
So I installed CWM r8. Then through it, I installed r11. Rebooted after each zip install.
Then I went on to install the SuperSU 2.46 zip via CWM. Now the phone was stuck at the white Mi boot logo.
I have now switched to the secondary System (System 2 -- 6.3.9.0) via CWM and am able to use the phone.
1. What should I do in order to fix the boot issue on the non-working system?
2. This working system has root but no SuperSU. Installing SuperSU from the Play Store says it needs the binary. I am afraid to install any SuperSU zip at this point on the working system. What should I do?
*Another user on the miui.com forum also has the same issue with the new update (can't post link):
i am having the same prob too. same after updating the su. now stuck on mi3 booting icon. and i changede from system 1 and 2 both cant be boot up. how to do mounting so i can transfer new dl rom and install?
Click to expand...
Click to collapse
Please help.
same problem
I m facing the same problem.. If u have found a solution pls share

[Q] Phone won't boot after root

Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
after root do you have flashed superSU?
RotesMeerJogger said:
after root do you have flashed superSU?
Click to expand...
Click to collapse
Well I flashed superSU to root the phone!
But when I do it, it won't boot.
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Daman5202 said:
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Click to expand...
Click to collapse
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
gigaboss said:
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
Click to expand...
Click to collapse
As you said "it stucks on boot", many times the phone gets stuck on boot when the image is corrupted , its called soft brick. Try downloading the zip file of os, flash it through recovery. The img is probably facing some errors while booting with root access. Are you nougat user? 7.1? And are you using default recovery?
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
donny110 said:
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
Click to expand...
Click to collapse
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
gigaboss said:
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
Click to expand...
Click to collapse
Have you cleared caches before the flash? And are you using the Full OOS 3.5.4? And I assume the most recent Supersu? I did exactly that 2 days ago. Using the full OOS zip that is in one of the threads here on XDA (can't link on phone right now).
Btw. It can bootloop a few times and take awhile once you flash both.. If that doesn't work I guess it's beyond my knowledge. You might want to try if the same thing happens with 3.5.3
gigaboss said:
Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
Click to expand...
Click to collapse
I don't have my 3T yet to verify, but did you flash the zip which disables encryption and dm-verity?
EDIT: From the TWRP thread, step 10: http://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
__McB__ said:
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
Click to expand...
Click to collapse
I got to the bottom of my problem (but did not solve it somehow) by formatting and trying every possibility. I lost all my data :crying:
So here is what happens:
-I start with a clean ROM, root it, install kernel, everything works fine EXCEPT for safetynet that won't pass even with root switch
-I try to install suhide 0.55, the phone won't start anymore (stays on boot animation, tried to wait all night)
AND HERE IS THE WEIRD THING.
-If I dirty flash the rom to start over, it boots, if then I flash SuperSU, it won't boot!! As if suhide was still in the data partition and preventing the phone from booting!!
So it means that if I try to install suhide once, I am not able to boot with root anymore... I need to format my data partition and start all over again.
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
__McB__ said:
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
Click to expand...
Click to collapse
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I had a similar issue with my op3t after root it, I wipe data but it won't start, I just flash the zip 5.1 no verity opt encrypt and should be work fine without flashing supersu:good:
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
No, never got it working. Upgraded to 4.0.2 and never looked back.
Maybe you already tried this version.. Otherwise...

Can't install TWRP after updating to Nougat

I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.
Gutito said:
I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.
Click to expand...
Click to collapse
that would be because the TWRP in SRK Tools is only for android 6 (EMUI 4.1 - 4.1.1) and not for android 7 (EMUI 5 - 5.1)
the recovery that you need to use in order for twrp to be installed is this one https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.0/twrp-3.1.0-0-eva.img
then once its installed boot up your phone and then type in "adb reboot recovery" and that will then boot your device into TWRP 3.1.0.0
Thank you, it worked!
Another question, but now related to SuperSU.
I am with the 2.79 version of SuperSU and I downloaded the binary .zip of this version and flashed it by twrp. The problem is that it keeps saying ""There is no SU binary installed and SuperSU cannot install it. This is a problem!".
I already got it to work. Thanks btw
Gutito said:
I already got it to work. Thanks btw
Click to expand...
Click to collapse
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!
kzip said:
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!
Click to expand...
Click to collapse
I solved it by this post https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
I ended up not using super su but If you want you can use it instead of the one suggested there
By flashing the file provided in the post, I managed to automatically get access to super user (root)

Unrooting does not work..phone doesnt boot

I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
TMG1961 said:
I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
Click to expand...
Click to collapse
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
ktmom said:
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
Click to expand...
Click to collapse
Thanks, that did the trick. Rooted with Magisk now.

absolute cluster**** after attempting to move from 4.5.0 to 5.0

So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?
I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...
Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0

Categories

Resources