So I was on tmobiles firmware rooted and something happened last night. It shut off and wouldn't boot up into system or recovery so after being frantic about it for about an hour and after some googling. I decided I was going to try a dirty flash (I think that's what I did)
I downloaded the latest ota zip from OnePlus 9.5.11 and used the all in 1 tool to boot to twrp and installed the ota zip there and installed twrp. Now the phone booted up to 9.5.11 on the international version and asked me to update to 9.5.13 which I let it. Then I rebooted back to twrp and installed magisk and reboot again. Bootloop happened so I went back to twrp and deleted my modules and rebooted again and it was fine and then reinstalled my modules....
Now for the actual question, should I be worried about corrupt data by doing what I did?
I really didn't want to lose my data, I have titanium backup but I can't get twrp to make any backups because I use OOS parallel apps
Bump
Anyone have an answer or any info to add?
If you didn't lose anything, then you didn't lose anything.
Related
Okay. Saw that CM12.1 came out, downloaded it. Flashed it. Forgot Gapps. So I kept getting the error message the Gapps crashed. Decided to flash back to 12, but still didn't have any Gapps .zip on the phone so it gave me the same error. Loaded my recovery, phone worked even if it was stock android bloated bs. But whatever.
Then I got a notification of an OTA update, figured I'd do that, then make a new backup before trying to reflash CM12.1 with the new Gapps package. Phone reboots, gets stuck booting to TWRP. Got home and downloaded Gapps 5.1, won't load past TWRP. Reflashed it with GL_G3_Flash2FixStuckRecovery.zip from here on XDA. Still no dice. So I queued up that, CM12 and Gapps 5. Still boots to TWRP. Then queued up that fix .zip, CM12.1 and Gapps 5.1, same ****. TWRP.
I'm going on a trip tomorrow, I'd quite like my phone to be operational so I don't have to use my ****ty burner. Any suggestions?
edit:
I can still transfer files to TWRP from my PC and access all of my TWRP functions, but it won't boot past that.
If you have a backup I would just restore to the previously working backup until the trip is over. Then when you come back worry about it. That being said, you said you took the OTA to Lollipop. Did it update successfully because typically it won't go through successfully if your d850 has been rooted. Are you on 20f? I would try flashing a rooted version of stock lollipop there is a few of them on here some are even debloated for you. If it works and you get a succeful boot then redownload the cm12 and Gapps and do a fresh clean install.
adosin said:
If you have a backup I would just restore to the previously working backup until the trip is over. Then when you come back worry about it. That being said, you said you took the OTA to Lollipop. Did it update successfully because typically it won't go through successfully if your d850 has been rooted. Are you on 20f? I would try flashing a rooted version of stock lollipop there is a few of them on here some are even debloated for you. If it works and you get a succeful boot then redownload the cm12 and Gapps and do a fresh clean install.
Click to expand...
Click to collapse
The issue was before booting and my recovery didn't work either. But I found a solution and was on CM12.1 the whole trip, so we're good.
I was on stock rooted 5.1.1 and got the update notification, so i flashed the stock rom again to unroot, partition gpt.bin wouldnt flash, so i skipped it and it still worked, booted into 5.1..1 no trouble, hit the ota install, no trouble, booted up MM, no trouble, flashed twrp, booted into twrp, rooted using when twrp asked, and rebooted system- or tried to. it shows the bootloader is unlocked screen, and stays there indefinitely.
so i booted back into twrp and wiped cache, dalvivk, data, but it still didnt boot into system. i factory reset via twrp, no help, i flashed the supersu zip, thinking it was twrps root that was problematic, but still same problem.
Im going to try flashing cm13 via recovery to see if that works, but whats going on? is it that failed partition flash from earlier?
how can i get back to stock, mm or lp?
EDIT: CM13 works fine, no problems.
I'm having the same problem can u tell me how you solved this problem? Plzz ASAP
Sounds like dm-verity... Reflash your ROM and use systemless root from now on, don't ever touch /system!
Its been posted over and over, DON'T flash SuperSU when asked by TWRP, as Aquous said, use systemless root.
Sent from my SM-T530NU using Tapatalk
Hello everyone, 2 questions:
I have a rooted Oneplus 6 with Official TWRP and Magisk. Yesterday I wanted to update to 5.1.6, so, with a VPN it downloaded the full zip through the update app. As soon as it finished downloading, it started to update directly.. Omg! I restarted immediately in recovery because I wanted to update from there, afraid of losing TWRP.
Question 1: what would have happened if I would had left the update app to finish installing?
From TWRP I updated the ROM, reflashed TWRP, and Magisk. Everything was up and running (slot b).
This morning I woke up and found that root was missing and phone had switched to slot a. I simply reflashed Magisk from recovery (slot a) and everything is good now.
Question 2: What happened? Another mysterious update during the night?
Thank you!
Hurizen said:
Hello everyone, 2 questions:
I have a rooted Oneplus 6 with Official TWRP and Magisk. Yesterday I wanted to update to 5.1.6, so, with a VPN it downloaded the full zip through the update app. As soon as it finished downloading, it started to update directly.. Omg! I restarted immediately in recovery because I wanted to update from there, afraid of losing TWRP.
Question 1: what would have happened if I would had left the update app to finish installing?
From TWRP I updated the ROM, reflashed TWRP, and Magisk. Everything was up and running (slot b).
This morning I woke up and found that root was missing and phone had switched to slot a. I simply reflashed Magisk from recovery (slot a) and everything is good now.
Question 2: What happened? Another mysterious update during the night?
Thank you!
Click to expand...
Click to collapse
1 you would've went completely stock.
2 a/b partitioning is for faster integration of system updates and only flashes on one of the 2 partitions.
mikex8593 said:
2 a/b partitioning is for faster integration of system updates and only flashes on one of the 2 partitions.
Click to expand...
Click to collapse
Hello, thanks for you reply.
I know it flahhes only on one partition, but after I flashed from TWRP I was rooted and on slot B. Then, something happened while I was sleeping and woke up with the phone not rooted and on slot B. This is very strange to me. Can you explain what happened? It updated?
This phone has no recovery partition. The kernel and recovery share the same partition. So when you flashed the full ota in twrp, recovery was overwritten and you lost root.
You should have just let it update, then reinstalled twrp and magisk. You are going to lose twrp and root with every ota anyway, which is how the update process is intended by OP. It gives you a clean stock slot with everything where it belongs. Reinstalling twrp and magisk is really not that hard.
This isn't like other phones where taking an ota w/root can cause a brick. OP has specifically designed the ota process on this phone to accommodate rooted users.
Hurizen said:
Hello, thanks for you reply.
I know it flahhes only on one partition, but after I flashed from TWRP I was rooted and on slot B. Then, something happened while I was sleeping and woke up with the phone not rooted and on slot B. This is very strange to me. Can you explain what happened? It updated?
Click to expand...
Click to collapse
you asked what happened:
if you are in one slot and fash mods, root, or anything else vie twrp it will behave like always, you will stay on that slot, reboot into sustem and all good.
the moment you fash a rom/update it will flash ti the other, non-current slot while your rdcovery zlsession will still show and be in the currently active slot
only upon reboot the device will decide to boot into the new slot.
to avoid loosing root and kernel, you have to manually change the slot and flash kernel and root in the new slot with the new system installed.
need more input? you'd have to pk because i won't come back here very often :highfive:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Bxperiaz3 said:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Click to expand...
Click to collapse
Can you boot in TWRP? if can try changing slot and boot from it
Mervingio said:
Can you boot in TWRP? if can try changing slot and boot from it
Click to expand...
Click to collapse
Hi,yes I can. Its loading the logo now so i'll wait and see what happens. If that works then what should be the next thing I do?
Edit: Slot B seems to be bootlooping on the logo unless its meant to take a few minutes
Is there a way to recover without wiping my data?
So slot A sits on the caution device rooted screen then defaults to the fastboot rescue mode which allows me to select reboot to recovery which is twrp. From there I have full access to the phone but still not booting to system. Slot B passes the fastboot screen and hangs on the one plus logo just circling around. This is my first rooted phone and I haven't had any problems until now so I'm hoping its something simple because I didnt do anything big to cause it. Hopefully someone has some insight.
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Bxperiaz3 said:
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Click to expand...
Click to collapse
Yes
MrSteelX said:
Yes
Click to expand...
Click to collapse
Will I lost root or relock the bootloader? I'm trying to find the least destructive way to get back to what I had which was oos 10 with twrp and magisk.
Uninstalled magisk and was able to reboot. However reflashing it as i want to retain root makes it bootloop again. Any possible fix for this that isn't a factory reset and reroot?
I can't get substratum or substratum themes to work on any rom or stock, nothing happens after reboots.....or everything turns this weird orange theme. Then one time it corrupted the whole OS and I had to wipe.
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
i6rb said:
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
Click to expand...
Click to collapse
Thanks, i'll try this. Will I need to install TWRP again once I do this or is it unaffected?
Tried to dirty flash the same stock rom from TWRP but I don't think it did it properly. Can I dirty flash stock rom, flash magisk then try reboot to system?
Any help greatly appreciated.
Woke up this am to an OOS update and remembered that there's a process to go through to not lose root and magisk, so I look up the thread and follow the simple directions.
Allow the OTA but do not reboot.
Go into Magisk and install again to internal
Stay in Magisk and install to inactive slot
Reboot
I did exactly that and upon reboot, my phone booted to my lockscreen pic and just flashes every second. Even in safe mode it bootloops at a flashing lockscreen.
I followed exactly what I was supposed to do, so is there a step missing? Or was I not supposed to take the OOS update that was being pushed today?
I can access TWRP still, and I do have a full backup available if I need it, but I'd much rather figure out how to move forward.
Thanks for any help you can give me!
OnePlus 7 Pro
stock ROM
TWRP & rooted
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
FlipmodeBG said:
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
Click to expand...
Click to collapse
What exactly did you do to uninstall magisk from TWRP? I don't know how to do this...
Did you go into TWRP file manager and just delete /data/adb/magisk folder?
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
FlipmodeBG said:
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
Click to expand...
Click to collapse
Thanks for that, didn't work for me though. I keep bootlooping at insecure bootloader warning.
I have messed something up pretty bad, after the last reboot, I'm met with the Qualcomm CrashDump mode -- dmverity device corrupted force dump
kernel_restart
Now I'm stuck, because I've tried to recover my backup, it goes through the process at just over 1000 seconds, has no errors or failures but still won't boot.
I need some help here.
Nevermind, I have to have this phone back up and running ASAP, so I used MSM Tool and started over. I figured spending a few hours setting it back up from scratch was the best way forward at this point.
I'm unclear on what caused this problem... maybe I had a magisk module that didn't disable, or maybe I forgot to disable a substratum layer or something, but I really borked myself all because of an OTA update.
Any further advice on what I might have done or what might have corrected it will still be appreciated because I'm sure there will be another OTA someday and I'd really like to avoid this happening again.
Thanks!
What I do when there is a new Ota is
download the update from the updater app
remove any passwords or finger prints
reboot to twrp
install the Ota
do no reboot
install twrp installer
do no reboot
install magisk
wipe dalvick
reboot
check if Magisk is installed and if not reboot back into twrp and install Magisk again
Hi. Magisk 20.4 not working my device. Has anyone managed to get it working?