For the last couple years I've been following this process to retain root using the TWRP A/B Retention Script and installing Magisk to the inactive slot after OTA and everything been fine and dandy. However, after the last time I performed this process Magisk would immediately crash when I tried to launch its app. Upon investigating I noticed that the file it downloaded for flashing was suspiciously small, so I suspect it flashed a corrupted file. I had already successfully rebooted my phone several times after the OTA, so I figured it was just Magisk that got corrupted and TWRP must be fine. I recently tried to reboot into recovery and discovered that TWRP is broken too. My phone briefly flashes the TWRP logo before the screen goes black and it tries to reboot into recovery again.
I've been able to get into fastboot by simultaneously holding down the power button and both volume buttons. However, none of the options in fastboot actually get my anywhere. Choosing start, recovery mode, or power off just get me back into the TWRP bootloop, and restart bootloader obviously just keeps me in fastboot.
I assume I need to reflash TWRP and Magisk, but I'm not sure how to go about that. Can someone point me in the right direction? Thanks.
This is how I proceeded:
Downloaded the latest TWRP image (twrp-3.6.2_11-0-guacamole.img) from here: https://dl.twrp.me/guacamole/
Verified the md5sum to ensure the download wasn't corrupted.
fastboot boot twrp-3.6.2_11-0-guacamole.img
In TWRP, Advanced > Flash Current TWRP
Now I have a working recovery, but I still can't boot into my system. When I go to Reboot > System in TWRP it just boots back into recovery.
I enabled MTP in TWRP and copied off all the data I cared about, then used the "Flash Factory Images" option in the TOOL ALL IN ONE to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip. I tried it without checking the box to erase everything, hoping I could keep my data, but that didn't work. With that box checked though I was able to boot again, but I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue. Does anyone know how to get WiFi working again or why it may have stopped working?
altayh said:
I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue.
Click to expand...
Click to collapse
Fortunately enough the first OTA did indeed solve the WiFi issue. Now I've applied all of the OTAs and finally have my phone in a proper working state again.
Related
Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
eracet said:
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
Click to expand...
Click to collapse
UPDATE: When booting into TWRP 3.2.2.0 it gives me encrypted files. When booting into TWRP 3.2.3.0 it gives me non-encyrpted files and asks for password.
Booting anything to slot A gives me a load error. failed to authenticate.
Update2: Now I cannot get Bluspark TWRP or stock recovery to load VIA Fastboot. Only TWRP 3.2.3.0 works and loads correctly
Update 3: Keep having to do different versions of TWRP to get anything going, even tried OTA and did not work.
Update 4: Phone wants to boot into Qualcomm HS-USB Diagnostics mode when light is on.
Found you
Next time tag me
I'm the same guy on the oneplus forums
Send me a private message here or on the oneplus forums and I'll take it from there
Update: I have resolved the issue. Please do not post any further comments on this because
The issue is already resolved, duh
I just purchased a new OnePlus 7 Pro yesterday and immediately set about rooting it. This is the process I followed:
fastboot oem unlock
fastboot flash boot twrp-3.3.1-4-guacamole.img
TWRP: Install > Select Storage > Internal Storage > Magisk-v20.3.zip
TWRP: Wipe > Format Data
I rebooted and was confused when I wasn't rooted. It seemed the last step had undone my root, so I went back into TWRP and installed Magisk again this time without formatting data. When I rebooted I had root and all was well.
However, there was an OEM update available that warned me it would remove root if I installed it. I found this guide to install an OEM update without losing root, which basically says to download the update via Oxygen Updater and then install it from TWRP. On step 6 is says to select the "Inject TWRP after install" option, but this didn't exist in my TWRP. I went ahead without it, thinking maybe it was enabled by default in my newer version of TWRP. The installation seemed to go without a hitch, but when I rebooted after I was stuck in fastboot. I couldn't boot my phone, nor could I get back into TWRP or regular recovery, only fastboot.
I tried flashing TWRP again using fastboot, but to no avail. I also tried running fastboot -w, but was still stuck in fastboot. I did some more research and found this comment which made it seem like all I had to do was download 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT from here and then run flash-all.bat. Once I did so I ended up stuck on the following screen:
Code:
QUALCOMM CrashDump Mode
--------------------------
dm-verify device corrupted Force Dump
kernel_restart
I can't seem to do anything at all with my device; not even turn it off. I tried holding the power button down for nearly a minute and no response from the phone. Is there any hope at all for my phone or have I properly destroyed it?
https://forum.xda-developers.com/oneplus-7-pro/help/mistake-kernel-error-t4029743
Same thing happened to me and I searched around a bit and found resolution. You can try what I did or try msm tool but search first as crashdump error is becoming common issue it seems
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed
Thank you so much! I thought I'd corrupted fastboot and permanently bricked the phone.
Once I was in fastboot I used tool all in one to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip onto my phone by picking Flash Factory Images, and now it's back up and running.
jasons1004 said:
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed
Click to expand...
Click to collapse
This was the magic trick I needed to know. Holding both volume buttons didn't quite work for me. I held them both down for over a minute and nothing happened. Then I tried holding down the power button and that seemed to work after several seconds. I didn't hold down volume down quickly enough the first time, so I had to do it again. I held both volume buttons and the power button for over a minute, but again, nothing. I tried a couple more times and got it to work. Haven't been able to figure out exactly what causes it to exit the CrashDump mode, but the volume buttons together seems to be the important part.
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
Just use tool to flash 9 then after first boot fasboot flash whatever 10 build you can find. Then after first boot of 10 try boot twrp and install twrp.
Honestly I just used the tool to root and flash recovery. There is a button for that and just pick your files. Good luck
altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.
redpoint73 said:
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Click to expand...
Click to collapse
Ah, I was using the Official TWRP App to get the images so I was under the impression that twrp-3.3.1-4-guacamole.img was the latest. I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
redpoint73 said:
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.
Click to expand...
Click to collapse
This is good to know. Thanks.
Just to follow up, I applied the available OTAs through the phone settings (up to bulid 10.3.0.GM21AA) and then followed the More articulated but fully functional instructions to install TWRP 3.3.1-74 Unified Unofficial Q. Everything went well and I'm now up to date and rooted. Thanks again to both of you!
altayh said:
I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
Click to expand...
Click to collapse
That is the correct TWRP to use ("Unofficial" version -74), as it appears you have already determined.
I don't know why the "official" versions have fallen so far behind. It's been months stuck on version -4, so it seems that they have stopped going "official" for some reason. No matter, the unofficial versions are working fine (and in fact required for Android 10 as you now know), so the "official" tag seems like a technicality.
On these OnePlus phones I don't know why they love Qualcomm Crashdump mode. I fixed it sort of like you, but this worked 100%. You hold all 3 buttons (power, vol up, vol down) and you bypass the crashdump (takes several seconds 5 maybe 10), just quickly let go so you'll be in fastboot mode and can work your magic to fix the damn thing....
I even contacted OnePlus on an 8 they had no idea what to do...
Fastboot flash boot recovery.img <-- bad idea
Fastboot boot recovery.img <-- provit
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Probably an encryption issue. As twrp doesn't support encryption in A11. I don't know what's causing the black screen. The best way out is using msmdownload tool, I believe.
CodeRida said:
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Click to expand...
Click to collapse
in that case reflash twrp,root and the os you were using(in the order you did it the first time and, when you get your next ota update
extract it and edit to remove code which makes it look for stock recovery
select all the decompressed files and compress to ota zip file again
then in update area choose local update and use the file you just edited