Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
I totally know that feeling. I started with a tmo op7p, flashed international, unlocked bootloader, try to boot TWRP, and nope. Switch slot, it works. Flash it, great. Make a backup with TWRP of my working system, flash ROMaur, won't do anything but boot to TWRP. Open TWRP file manager and every file on internal storage is a ton of folders with jumbled strings of letters and numbers for names. MSM tool back to intl stock, try lineage... Nope. Keeps telling me to do a factory reset. I did, but I do another and still boot loop. MSM to intl, try other roms, same outcome.
I can unlock my bootloader and root it and run intl stock but that's it.
oxadedzn said:
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
Click to expand...
Click to collapse
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
tech_head said:
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
Click to expand...
Click to collapse
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
JhinCuatro said:
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
Click to expand...
Click to collapse
If you install TWRP on a 7 Pro without installing Magisk you will absolutely boot loop. If you wipe the system in one slot and have a differing ROM from the active slot you can in fact boot loop. Although the systems are different, the settings between the systems are shared.
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Arden144 said:
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Click to expand...
Click to collapse
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
You can also install TWRP if you like.
No computer needed.
This works.
tech_head said:
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
This works.
Click to expand...
Click to collapse
That's completely unnecessary and just avoiding the purpose of the a/b system.
All it would take is:
1. Local install
2. Install magisk to inactive slot
Related
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
sapalot said:
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
Click to expand...
Click to collapse
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
reaper000 said:
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
Click to expand...
Click to collapse
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
sapalot said:
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
Click to expand...
Click to collapse
Don't mess with stock recovery if you already have TWRP and Magisk aboard.
Here's how to update to 9.5.9 (or whatever) when it arrives:
- download your 3 zips: the latest full ota ROM, the latest Magisk, and the latest TWRP installer.
- boot to TWRP recovery
flash the ROM and TWRP installer
- reboot to TWRP recovery
flash Magisk
wipe dalvik
- reboot to system
There's a possibility after these steps and you're happily on the ROM, you might find that you're not rooted (it's more likely on a custom ROM than OOS). In which case you just reboot to recovery and flash Magisk, and then reboot to system. Done.
Discussion:
If you want a clean flash, you'd simply do a TWRP factory reset (standard wipe) instead of wiping dalvik.
Consider flashing both slots (A and B) whenever you update OOS, for two reasons. First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base. The second reason is more compelling: the way the data partition changes encryption every update has obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck
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.
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
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Did you also FORMAT your data?
Use MSM Tool
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Wrong order. First flash LOS, then TWRP Installer and then Magisk. When you flash LOS after TWRP and Magisk, your TWRP and root will be gone.
n2851991m said:
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
Click to expand...
Click to collapse
crap... my link is old.. may not work.. i'll try yours.... fingers crossed
csmooth2001 said:
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
Click to expand...
Click to collapse
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
razorshiv said:
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
Click to expand...
Click to collapse
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
im guessing big time
is there a forum just for GM1915 ??? anywhere in the world...
csmooth2001 said:
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?.
Click to expand...
Click to collapse
yes.
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
Click to expand...
Click to collapse
flash rom, flash twrp, reboot recovery, flash magisk.
is there a forum just for GM1915 ??? anywhere in the world..
Click to expand...
Click to collapse
They are scattered around the op7pro forum. Just do a search for tmo or tmobile.
boot to other slot & sim will work
Hey
My phone dont detected sim card in custom rom Havoc 3.0.
My phone: OnePlus
Guide install ROM:
https://forum.xda-developers.com/oneplus-7-pro/development/rom-havoc-os-2-6-t3942337
Hope this can help
I had similar issues flashing the rom in slot b instead of slot a fixed it for me
Kreiden_123 said:
I had similar issues flashing the rom in slot b instead of slot a fixed it for me
Click to expand...
Click to collapse
How do you choose slot b while flashing on TWRP?
This seems really convoluted to me, but it totally worked:
Boot TWRP (from fastboot)
Install TWRP from phone storage
Reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into system and wait for something like 5 minutes while it sat on the "Your bootloader is unlocked!" screen.
I believe that installed into both slots for me.
I also had to ADB push the install files after the first ROM install because my encrypted data all got lost. This was all SUPER inconvenient, but it ended up working for me.
jfsat said:
This seems really convoluted to me, but it totally worked:
Boot TWRP (from fastboot)
Install TWRP from phone storage
Reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into system and wait for something like 5 minutes while it sat on the "Your bootloader is unlocked!" screen.
I believe that installed into both slots for me.
I also had to ADB push the install files after the first ROM install because my encrypted data all got lost. This was all SUPER inconvenient, but it ended up working for me.
Click to expand...
Click to collapse
Love it, I'm going to try it tonight