Related
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...
Recently got my OP3T, and thought that I should root it, and I do have experience rooting a OPO.
So I pulled up a guide and followed it. after flashing no-verity and SuperSU, I tried to reboot, but it only ended up in playing the animation indefinitely.
I'm scared to **** right now, and would appreciate any help. Even reverting it to factory settings would be good, but I don't really know how to do that right now. Thanks.
You don't flash both. U either flash SuperSU, or if u don't want to use SuperSU and want another firm of your then u flash the DM verity zip. Not both. Flash the version of the room you're on and then flash SuperSU immediately after u go back to twrp
I am having serious battery drain on any OOS 4.x.x rom. I used to have very good battery life in 3.5.2. can anyone give me a proper step by step guide to downgrade? Battery is a huge issue for me.
i have my own steps that i found it by my self but it will earse all ur data so backup ur data to pc.
here are the steps :
1. make sure u have unlocked bootloader, custom recovery (twrp) i prefer use blu_spark twrp latest version
2. pur ur 3.5.x firmware in internal storage
3. boot to twrp recovery and do a clean wipe(dalvik, data, internal, system, cache)
4. flash ur 3.5.x firmware. it will take a long time just wait it
5. reboot to system, ull get a no os installed warning in twrp just reboot it(swipe)
6. when the devices boot up ull get a enter password for decrypt data. just reboot to bootloader
7. when u in fastboot mode connect ur devices to pc
8. use op3/op3t toolkit to flash twrp from fastboot u can find the toolkit here: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
9. then wait when it boot to twrp and when it boot up wipe data, internal storage only
10. reboot to system. done
sorry for my bad english. i hope it works
Ok that sounds easy. Reboot to recovery after flashing ROM retains the recovery I guess. Do you have any suggestion of custom kernel for 3.5.x ? Also i have the latest twrp. Will is allow me to flash 3.5?
arafat_mw said:
Ok that sounds easy. Reboot to recovery after flashing ROM retains the recovery I guess. Do you have any suggestion of custom kernel for 3.5.x ? Also i have the latest twrp. Will is allow me to flash 3.5?
Click to expand...
Click to collapse
u can try this i guess https://forum.xda-developers.com/on...mm-6-0-1-oxygen-3-5-4-kernel-3-18-48-t3567781
Thank you guys. It wasn't really tough. Flashed OOS 3.5.4 full zip. Rebooted to recovery then rebooted to system. However it was bootloop at the start then I restarted and flashed SuperSU zip, it booted up. Don't know why SuperSU is required to boot up. However I am not getting the support for Magisk. I tried cleaning up SuperSU and then flashing the Magisk zip but it didn't work. Any advice ?
arafat_mw said:
Thank you guys. It wasn't really tough. Flashed OOS 3.5.4 full zip. Rebooted to recovery then rebooted to system. However it was bootloop at the start then I restarted and flashed SuperSU zip, it booted up. Don't know why SuperSU is required to boot up. However I am not getting the support for Magisk. I tried cleaning up SuperSU and then flashing the Magisk zip but it didn't work. Any advice ?
Click to expand...
Click to collapse
You have to reflash stock boot image to get Magisk to work
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
ssteward said:
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
Click to expand...
Click to collapse
Try flashing magisk 15.3 + no verity stuff as suggested on that thread...
Sent from my MI 5 using Tapatalk
ssteward said:
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
Click to expand...
Click to collapse
Dont flash unpatched boot images using twrp
flash unpatched boot image or v14 boot image(that you made earlier) using pc ODIN/ any other prefered tool. Just flash the boot.img nothing else or you can use fastboot to only flash boot.img, it works 100% all times,after flashing it should boot normal
then make a new patched boot image for v15.3 from magisk app just as you made for v14 and flash using pc,then it should boot normally
many phones seem to show stuck at boot logo after moving from v14 to v15(especially v15.1 and v15.2) and also some some devices with f2fs storage seems working weirdly with audio mods.
teddy0209 said:
Try flashing magisk 15.3 + no verity stuff as suggested on that thread...
Click to expand...
Click to collapse
I'm pretty sure that's one of the permutations I tried before but having just flashed those two zips again, after making sure any previous Magisk installations had been removed, I get the same result - stuck at the pulsating Samsung logo.
If someone can tell me what parts of the system the problematic in-app upgrade from v14.0 to v15.0 would have affected then I could perhaps have a better idea of what I need to fix to get my phone starting up again.
ssteward said:
I'm pretty sure that's one of the permutations I tried before but having just flashed those two zips again, after making sure any previous Magisk installations had been removed, I get the same result - stuck at the pulsating Samsung logo.
If someone can tell me what parts of the system the problematic in-app upgrade from v14.0 to v15.0 would have affected then I could perhaps have a better idea of what I need to fix to get my phone starting up again.
Click to expand...
Click to collapse
Have you tried flashing your stock boot image or even dirty flashing your entire system with ODIN (as suggested above)? Magisk only edits the boot image, nothing else.
Supreme Genius said:
Dont flash unpatched boot images using twrp
Click to expand...
Click to collapse
Sorry, my mistake. I did flash boot.img via Odin. It was the original boot.img file that I fed into Magisk v14.0 so it could create patched_boot.img.tar that originally worked. I'm going to try that again now.
Didgeridoohan said:
Have you tried flashing your stock boot image or even dirty flashing your entire system with ODIN (as suggested above)? Magisk only edits the boot image, nothing else.
Click to expand...
Click to collapse
That's good to know, thanks. I do have the full system from sammobile from which I extracted boot.img, so could try that if the 'lighter touch' approaches fail.
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
ssteward said:
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
Click to expand...
Click to collapse
Probably try that... Hope it's not a corrupt boot partition...
Sent from my MI 5 using Tapatalk
ssteward said:
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
Click to expand...
Click to collapse
did you flash the previous v14 patched boot image again using ODIN? this should work
same boot loop problem prevailed on my s7 active and lenevo k8 and flashing the v14 patched boot image and then making new v15.3 boot image gave a perfectly working magisk, although my redmi 3 was showing same boot loop problem and i have to flash the stock rom ( used twrp to restore nandroid backup but boot loop was not solved )
It seems your lots of permutations and combinations have damaged post_fs config of the kernel so you have only option left is to dirty flash the ROM.
teddy0209 said:
Probably try that... Hope it's not a corrupt boot partition...
Click to expand...
Click to collapse
Sounds ominous. How would I recognise this and fix it?
Supreme Genius said:
did you flash the previous v14 patched boot image again using ODIN? this should work.
Click to expand...
Click to collapse
I don't seem to be able to find the patched_boot.img.tar that I used originally with Odin. I've checked a few different machines and on various SD cards but I only have the unpatched boot.img.
ssteward said:
Sounds ominous. How would I recognise this and fix it?
I don't seem to be able to find the patched_boot.img.tar that I used originally with Odin. I've checked a few different machines and on various SD cards but I only have the unpatched boot.img.
Click to expand...
Click to collapse
Then you need to flash the ROM , if you got another device then you can make a patched v15.3 image and flash it
I used another phone to created a patched_boot.img.tar for v15.3 and flashed that with Odin but that gave me a boot loop. Trying this again but flashing no-verity-opt-encrypt-6.0 afterwards allowed me to get to the pulsating Samsung logo. So giving up on this approach, I dirty flashed my stock ROM and this worked but I was left looking at a pulsating Samsung logo for a nerve-racking 5 mins or more.
Thank you everyone for your help. I have my phone booting up again!
Now I need to work out install the latest Magisk successfully. If I try using the patched_boot.img.tar method with v15.3 then I'm back to the pulsating Samsung logo. Again. Using TWRP to flash the v15.3 zip gives the pulsating Samsung logo. I did select 'Preserve AVB 2.0/dm-verity. I also tried again with a clean stock ROM install and flashed the v15.3 zip and no-verity-opt-encrypt-6.0, as suggested by someone who'd successfully installed v15.3. I'm at a bit of a loss.
One clue, TWRP couldn't see the internal SD card data (iow /data). I wasn't able to check this option in the 'Mount' menu in TWRP either. I think this points to /data being encrypted. TWRP could see it yesterday, so perhaps I've inadvertently encrypted this. I was careful to uncheck 'Preserve force encryption' in Magisk Manager. I guess now that I've unbricked my phone, I should start another thread for this magisk install issue but any help or pointers to relevant threads that I may have missed would be great.
Thanks again for all your help.
I soft bricked my G930FD when going from v14.0 to v15 using the in-app update but got it back by dirty flashing my stock ROM thanks to the help I got here.
Now I'd like to install the latest Magisk to get root back but despite reading a lot of threads where people solved similar issues going to v15 on Samsung devices and following their suggestions, I can't get Magisk to work and always get stuck on boot, either a boot loop, or more often, the pulsating Samsung logo.
If I try using the patched_boot.img.tar method with v15.3, which is technique I used originally to install v14.0, then I get stuck at the the pulsating Samsung logo. If I use TWRP to flash the v15.3 zip, I get a boot loop. At that point, flashing the stock boot.img allows me to boot or if I flash no-verity-opt-encrypt-6.0 then I get to the pulsating Samsung logo. I did select 'Preserve AVB 2.0/dm-verity' in Magisk Manager.
I also tried again with a clean stock ROM install and flashed the v15.3 zip and immediately flashed no-verity-opt-encrypt-6.0, as suggested by someone who'd successfully installed v15.3 on an S7, but again, stuck at the pulsating Samsung logo.
One clue perhaps, TWRP couldn't see the internal SD card data (iow /data). I wasn't able to check this option in the 'Mount' menu in TWRP either. I think this points to /data being encrypted. TWRP could see it before I dirty flashed the ROM, so perhaps I've inadvertently encrypted this. I was careful to uncheck 'Preserve force encryption' in Magisk Manager , which seemed to default on.
I'm at a bit of a loss so would really appreciate it if you can tell me how to get up and running with Magisk v15 on my Samsung Galaxy S7 if you've managed this yourself.
Can anyone share how they've done this?