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
Related
Hey,
i've got a few problems with my HTC One S, running Cyanogenmod 11 (4.4.4) with TWRP as recovery.
Since a few days nearly every app crashes, ca. 3 minutes after I start the phone. In these minutes everything is working. After that there are only messages that "android.process.acore", "com.google.process.gapps" and nearly every other app has been closed. When I press OK, the message appears again.
So I tried to flash another ROM, which isn't possible because I first can't copy anything to the phone, the copying process stops after the half. I also couldn't download a ROM directly to the phone. Then I tried to flash again my actual ROM which is still on the phone, I selected the .zip in TWRP, but then the phone is restarting and nothing happened.
There are also other problems:
1. I tried a soft reset in the settings, isn't possible because nothing happens when i press the "Confirm" button
2. Clear storage and Factory reset in the boot loader isn't possible, when I select one of that the phone only starts into the recovery, without anything has been resetted
3. Pushing a zip with ADB doesn't work, it says I don't have permissions to copy anything on the storage
4. The ADB sideload mode doesn't start in TWRP
5. I tried to flash CWM as recovery, it says "successful", but when I start into recovery there is still TWRP..
6. Relocking the bootloader doesn't work, it also says "successful" but in the bootloader appears "*** unlocked ***" After that I tried to turn back to stock ROM with the RUU exe by HTC, but when the process starts, the phone just turns off.
Does anyone have a idea? Do I maybe have a virus? Sometimes it appears to me that there are problems with the storage or anything like that..
I really tried to do everything, and also searched in this forum and in other but I didn't find anyone with the same problem..
Thank you!
Give the Mount option a try in TRWP and see if you can copy a ROM over to the phone.
Okay I had to install the right driver for adb..
Then adb push worked, I could select the .zip in the Install option in TWRP, but the phone again just restarts without installing the rom..
ADB Sideload also worked with the driver, but after I tried to ADB sideload the ROM it said "* failed to write data 'protocol fault (no status)' *"..
I searched the forums before posting. 73 results came up and I read through and followed instructions of 7 different posts that seemed similar to mine (including the ones that appear when making a new thread), but nothing has worked or I haven't found a situation like mine.
Hi.
I have a HUGE problem and need help.
I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed the zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that according to someone in Oneplus forums. Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!
Thanks for any advice.
note: I used the signed flashable zip from here.
EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.
EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!
EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready). After that, I got the "Android is starting" "Optimizing app xx of xxx" message again, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!
EDIT 4: I remembered that I did a nandroid backup last February so I restored it with "restore" in TWRP. My phone has been stuck on the "Cyanogen" boot screen for about 40 minutes. I'm lost.
To recap everything:
1. I was trying to manually upgrade from COS 12.1 to COS 13.1
2. My phone was rooted, had TWRP recovery and ADB debugging was enabled in dev options. I can enter fastboot mode using hardware keys. I cannot enter recovery using hardware keys (shows a blank screen), but I can enter recovery using "fastboot boot recovery.img.
3. After I flashed COS 13.1, I was asked (in TWRP) if I wanted to install SU and I said yes and flashed it. This is when I was in a loop of being stuck on COS 13.1 splash screen for about 5-10 minutes and then my phone was "optimizing app xx of xxx" for 15 minutes and then rebooted and did everything all over again.
4. I tried to restored a nandroid backup using "restore" in TWRP, but phone is stuck in "cyanogen" splash screen for more than 40 minutes.
No replies...
Not sure what to do at this point.
I ended up wiping data and performing a factory reset through TWRP. Might try to upgrade again in the future.
Android Marshmallow
Shield update 4.4.0 WIFI
Rooted with SuperSU 2.78 SR5 (Also tried 2.79)
About a month ago, my tablet got into this bootloop and a wipe worked... For a while.
Now it is doing it again, wiping my cache can get me back into the OS, but it just happens again. I've tried all sorts of different versions of SuperSU, and the OTA updates, but the issue just persists. I've also tried removing the SD card to no avail.
Here's the process I've been doing:
1. wipe Dalvik, Cache, and System in TWRP (TWRP booted using Fastboot boot command)
2. Flash Blob, Stock Recovery, Boot, and system images
3. Boot to Android (Just in case)
4. Shutdown, go back to TWRP and sideload SuperSU
5. Boot back to OS
6. Run "am start -n com.google.android.setupwizard/.SetupWizardTestActivity" in terminal emulator in SU mode to fix missing home and recent apps buttons, as well as the notification menu
7. And then it bootloops again shortly after. Usually around 177 apps optimize when it is looping, ~146 when it gets into the OS.
Sometimes the process I tried would be slightly different, such as not booting back to the OS before flashing SuperSU.
MrFastZombie said:
Android Marshmallow
Shield update 4.4.0 WIFI
Rooted with SuperSU 2.78 SR5 (Also tried 2.79)
About a month ago, my tablet got into this bootloop and a wipe worked... For a while.
Now it is doing it again, wiping my cache can get me back into the OS, but it just happens again. I've tried all sorts of different versions of SuperSU, and the OTA updates, but the issue just persists. I've also tried removing the SD card to no avail.
Here's the process I've been doing:
1. wipe Dalvik, Cache, and System in TWRP (TWRP booted using Fastboot boot command)
2. Flash Blob, Stock Recovery, Boot, and system images
3. Boot to Android (Just in case)
4. Shutdown, go back to TWRP and sideload SuperSU
5. Boot back to OS
6. Run "am start -n com.google.android.setupwizard/.SetupWizardTestActivity" in terminal emulator in SU mode to fix missing home and recent apps buttons, as well as the notification menu
7. And then it bootloops again shortly after. Usually around 177 apps optimize when it is looping, ~146 when it gets into the OS.
Sometimes the process I tried would be slightly different, such as not booting back to the OS before flashing SuperSU.
Click to expand...
Click to collapse
Missout number 6 for a while and see what happens if you leave it stock setup for a while
madasahat said:
Missout number 6 for a while and see what happens if you leave it stock setup for a while
Click to expand...
Click to collapse
I actually just found one of your threads with a boot loop saying the bootloader stated UNDEF_BUILD, and mine does too. I am also going to try flashing that .dtb file if it is in the recovery files. EDIT: That seems to just cause it to hang on the boot screen now. EDIT2: Flashing boot.img and blob fixes the non-booting though.
Also, for some reason my nav bar and notifications did not break this time.
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
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.