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...
Related
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.
Question for those you you way smarter than I'll ever hope to be. I randomly lost root and TWRP on my 3T and I have no idea how this happened.
Quick (or not so quick) background - I was stock rooted OOS 4.1.6. I disabled AdAway for a bit yesterday to gain access to something it was blocking (done it many times) and when I re-enabled it my phone was stuck in a boot loop afterwards. Weird, but not concerning. I booted into TWRP and restored a backup. OOS 4.1.3 was my latest backup, so after successfully loading that up, I flashed the full 4.1.6 OTA and SuperSu as I've done before to update. Worked fine. Was adding my preferred mods via Substratum and Magisk and I messed up. Couldn't get Substratum to work properly and couldn't get Magisk to update to 13.1. I verified I had root, which I did. Went back to TWRP and reflashed 4.1.6 and SuperSU. When my phone was up and running again I didn't have root. Weird, so I tried again, still couldn't get SuperSU to flash properly. Got frustrated and figured I haven't had a clean install since getting the device in January. Every update I've flashed via TWRP has been dirty. So, factory reset, blah, blah, blah. Done it plenty of times with many devices. Flashed the OTA and SuperSu again, but noticed SuperSu failed. Rebooted recovery to try again, but it went to the stock recovery. My phone is working fine now, but I'm without root and I no longer have TWRP.
What might have caused this to happen? And how can I avoid it in the future? I know how to get it back (I'll do it after work) but it's frustrating.
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Anova's Origin said:
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Click to expand...
Click to collapse
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Rodeojones said:
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Click to expand...
Click to collapse
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Anova's Origin said:
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Click to expand...
Click to collapse
I was using version 2.8.2. Regardless, you answered my question as to how it happened in the first place, so thanks.
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
I had the same problem so I flashed it TWRP again then flashed another ROM and it stuck. I have no idea why it does that either.
chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
Flash SuperSU or magisk before booting to system...and it Will stick...
Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.
roger.hernandez91 said:
Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.
Click to expand...
Click to collapse
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.
beany23 said:
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.
Click to expand...
Click to collapse
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?
roger.hernandez91 said:
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?
Click to expand...
Click to collapse
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.
beany23 said:
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.
Click to expand...
Click to collapse
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?
roger.hernandez91 said:
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?
Click to expand...
Click to collapse
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Yes quick question, did you use Magisk uninstaller package from thread or just uninstall Magisk directly from the app?
Confused on how to uninstall Magisk without encrypting my device or loosing my boot or messing anything like that up
Also, wipe Dalvik cache and cache or just cache only?
Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully
Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?
roger.hernandez91 said:
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?
Click to expand...
Click to collapse
Sure you can. Magisk doesn't root the system so all of the files you need to discard are in /data and /cache. You need a copy of the stock kernel in image format, if Magisk didn't make a back up. I gotta say bro, I haven't uninstalled Magisk or tried, so I don't know what's going to happen when you do this.
If your phone force encrypts after flashing the kernel, you may be screwed and have to format data and lose everything. This could possibly also brick your device beyond help. Since you can't mount your system in TWRP, if for some reason it fails encryption or DM-Verify into a bootloop, from the LAF or recocery modification, it won't boot. At least, not until you find a way to mount the system, which I think will be near impossible.
With that being said, if you decide to move forward you can either wipe data and cache or remove the files one by one. Your choice.
Well I gotta say, I've had a hell of a day fixing this thing. System partition got wiped somehow and had to fight to get my backup restored, thankfully I had one. Basically came back from the dead. Ended up wiping my entire internal storage to get TWRP to shut the hell up about decrypting, flashed new recovery again, flashed Magisk v16.4 beta, and now I'm good to go. Didn't have any of the issues mentioned above. And now I'm not having /system mounting problems or the force quits upon flashing a new mod. Everything seems good.
Appreciate y'all. You guys are awesome for taking the time to help.
roger.hernandez91 said:
Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully
Click to expand...
Click to collapse
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted
beany23 said:
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted
Click to expand...
Click to collapse
Nah man I actually did have to do it from laf recovery because it wasn't working from regular recovery. Had to flash it from both and also formatted data and I was good to go. I got it all figured out.
Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.
This might go without saying but after flashing Magisk are you also wiping Dalvik?
Nuzzlet said:
Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.
Click to expand...
Click to collapse
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.
TLX317 said:
This might go without saying but after flashing Magisk are you also wiping Dalvik?
Click to expand...
Click to collapse
Yes I am
mixlex said:
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.
Click to expand...
Click to collapse
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.
Nuzzlet said:
Yes I am
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.
Click to expand...
Click to collapse
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help
a4abbas said:
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help
Click to expand...
Click to collapse
At the moment I'm just using regular TWRP actually. Havnt used blue since I switched the beta builds. I actually remember having trouble finding a download for Blu spark. What are your issues?