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
Related
Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.
Maybe THIS can help you?
Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes
Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John
Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.
Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John
Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.
Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.
firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk
But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged
What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.
Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain
Fixed!
Now I'll write a guide for those in the same situation.
franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI
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.