Database Info

I need Help with Rooting OP6 stable not beta 9.0.2, bootloader is unlocked

So, i have used my whole saturday on unlocking the booloader which was the easiest and quickest and then trying to root, but that has failed every time. I first flashed the stock firmware zip 9.0.2 then I go back I dont reboot and flash the twrp and magisk zip and then it wont boot up,
when I try rebooting after flashing the firmware back to the system it sends me to the firmware,
when I try flashing a new firmware and then boot into fastboot then twrp and flash magisk it wont boot up,
and when I do the same only with twrp it wont neither.
I have tried sevel magisk versions, 17.1,17.2,17.3 none of them worked
as for the twrp blu spark or the one from the twrp website, i was always able to boot into twrp but not really to flash it as that would end in a twrp loop
can PLEASE anyone, someone, with a good heart and patience help me ? im really loosing my ****s over this
:fingers-crossed::fingers-crossed:

Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)

Faaris Ansari said:
Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)
Click to expand...
Click to collapse
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?

galaxyss8 said:
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?
Click to expand...
Click to collapse
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.

Faaris Ansari said:
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.
Click to expand...
Click to collapse
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now

galaxyss8 said:
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now
Click to expand...
Click to collapse
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1

yldlj said:
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1
Click to expand...
Click to collapse
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?

galaxyss8 said:
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?
Click to expand...
Click to collapse
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.

yldlj said:
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.
Click to expand...
Click to collapse
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.

galaxyss8 said:
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.
Click to expand...
Click to collapse
Just press back button in Recovery/ reboot / choose recovery.

ROM Flashing Sequence

I've successfully unlocked bootloader, rooted (Magisk) and installed TWRP Blu Spark on my Oneplus 6.
The next step is to flash a custom ROM, but I keep running into the instruction "Flash Rom and TWRP Installer (blu_spark)", no matter what custom ROM I'm looking at.
Is it really necessary to reflash TWRP right after the ROM, or can I skip that step since Blu Spark TWRP is already on my phone?

Borat38 said:
I've successfully unlocked bootloader, rooted (Magisk) and installed TWRP Blu Spark on my Oneplus 6.
The next step is to flash a custom ROM, but I keep running into the instruction "Flash Rom and TWRP Installer (blu_spark)", no matter what custom ROM I'm looking at.
Is it really necessary to reflash TWRP right after the ROM, or can I skip that step since Blu Spark TWRP is already on my phone?
Click to expand...
Click to collapse
You need to reflash TWRP everytime you flash a rom becuase recovery partition does not more exist and recovery is integrated in boot.img

1. Wipe everything except internal storage in TWRP.
2. Flash OOS 9.0.X in twrp and flash twrp zip
3. Now reboot to twrp and repeat step 2.
4. Now flash your rom + twrp zip and reboot to twrp.
5. Flash Gapps, magisk or any other zip you want.
You should be good now.

Apachyx said:
1. Wipe everything except internal storage in TWRP.
2. Flash OOS 9.0.X in twrp and flash twrp zip
3. Now reboot to twrp and repeat step 2.
4. Now flash your rom + twrp zip and reboot to twrp.
5. Flash Gapps, magisk or any other zip you want.
You should be good now.
Click to expand...
Click to collapse
AH! Now that's the secret sauce--flashing 2x. The guides just indicate once, which is probably why when I restart, there's no OS and I get kicked back to TWRP. Thank you sir!! :good:

Can someone explain why I have to format internal data? My guess is the encryption key is changing. And I have no pin or password when I flash.

RUNNERX said:
Can someone explain why I have to format internal data? My guess is the encryption key is changing. And I have no pin or password when I flash.
Click to expand...
Click to collapse
Your guess is correct. Encryption. It has nothing to do with FP, or code. It's Googles securety patches basically. If you don't want to format look in the decrypt guide and run in decrypted.

phone has lost root issue

I used magisk on my phone for roots right but it has lost roots. I tried to go into recovery to reinstall magisk but recovery isnt booting, when it select advanced it gives me fastboot or recovery options but when I select recovery its goes back to the start again. I have tried to reinstall TWRP using this method
https://www.xda-developers.com/official-twrp-oneplus-6-huawei-p20-pro/
but I then get a crash dump window.
Please can I get some advice how to proceed?
Thanks

Make sure you're using 3.2.3, anything prior to that is not for Android Pie. If you updated your OS that is more than likely the reason you lost root. Make sure that you download TWRP.img and fastboot through the image before you try to install TWRP permanently

dgunn said:
Make sure you're using 3.2.3..............
Click to expand...
Click to collapse
Aha! I did wonder but I followed the guide to the letter as I thought I might brick the phone if I risked the other imgs. I did sort it by using a different TWP file.
Regards

Westindieman said:
Aha! I did wonder but I followed the guide to the letter as I thought I might brick the phone if I risked the other imgs. I did sort it by using a different TWP file.
Regards
Click to expand...
Click to collapse
Good deal glad you got everything working.

I'm on stock android 10 and I have accepted an update I was offered yesterday. It seems everytime I update I have an issue rooting and installing TWRP (last month I was bricked), maybe because I use the last TWRP version I have before the update (currently twrp-3.3.1-1-enchilada). What is the correct process for installing TWRP and rooting again with Magisk? Do I need to get a TWRP update each time?

You have to install the latest one (3.3.18).
Reboot fastboot, type fastboot boot 'recoveryname'.img, once time you are in twrp flash the installer from the inside. Reboot to recovery again and flash magisk.
When you need to update you have two ways:
1 download the full ROM zip and place it in your main storage folder (sd card);
Update via local update but don't reboot;
Open magisk and download and install twrp a/b retention script and don't reboot yet;
Go in the magisk main page and install it as installation in the inactive slot (after OTA);
Reboot and enjoy.
2 download the full zip;
Reboot in twrp;
Flash rom + twrp installer;
Reboot to recovery;
Flash magisk;
Reboot and done.

°Washy said:
You have to install the latest one (3.3.18).
Reboot fastboot, type fastboot boot 'recoveryname'.img, once time you are in twrp flash the installer from the inside. Reboot to recovery again and flash magisk.
When you need to update you have two ways:
1 download the full ROM zip and place it in your main storage folder (sd card);
Update via local update but don't reboot;
Open magisk and download and install twrp a/b retention script and don't reboot yet;
Go in the magisk main page and install it as installation in the inactive slot (after OTA);
Reboot and enjoy.
2 download the full zip;
Reboot in twrp;
Flash rom + twrp installer;
Reboot to recovery;
Flash magisk;
Reboot and done.
Click to expand...
Click to collapse
Some good news, it all went smoothly this time and thanks for your help. Really helpfull into there about updating too. Many Thanks

Westindieman said:
Some good news, it all went smoothly this time and thanks for your help. Really helpfull into there about updating too. Many Thanks
Click to expand...
Click to collapse
Np man. If you wanna make me happy press like button

You know, sometimes its too easy to forget to do that.

What's New(?) procedure to install Custom ROMs coming from OOS 9.0.5?

Hello guys,
I'm having trouble trying to install a Custom ROM (Tresk Mod, but I get it with others too)
So basically some days ago my whole Internal Storage got encrypted so I had to a full wipe.
From there I decided to use Msmtools just in case, so I got back to OOS 5.1.5 from there I updated to OOS 9.0.5 via OTA and unlock the bootloader and install TWRP everything works fine.
But when I tried to install any custom ROM I either cannot boot and just boots to Bootloader (Not even the recovery works) and I get "Failed to load/authenticate boot image: Load Error" which I can fix fastboot flashing all the partitions...
Or I straight get a black screen with the White Notifications LED whenever I try to boot either to system or recovery and from there I can only recover using Msmtools...
So I'm now asking, what are the steps for flashing Custom ROMs now?? Because seems like I'm doing something wrong since I'm ending having a Bricked device...

try to flash rom with bluespark recovery

Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.

Mdknight said:
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Click to expand...
Click to collapse
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?

Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk

Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.

Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Mdknight said:
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Click to expand...
Click to collapse
I finally figured it out
The problem was that as I was updating via OTA OOS 9.0.5 was only installed in one Slot so I need to install it in the other as well.
Did the following process:
1. Boot to Bootloader and do "fastboot boot TWRP.img"
2. From there flash TWRP.zip and Reboot back to it (Recovery)
3. Flash OOS Latest (9.0.5)
4. Flash TWRP
5. Reboot to TWRP
6. Flash OOS Latest (9.0.5)
7. Flash TWRP
8. Reboot to TWRP
9. Wipe data, dalvik cache
10. Flash ROM
11. Flash TWRP
12. Reboot to TWRP
13. Flash gapps + Misc (Magisk, etc)
14. Boot system
Technically just one 1 installation should do as the other slot was already populated but the twice just to be safe.

Android 10 & Custom ROM & Slot A + B

Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.

roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.

When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.

Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?

So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).

remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.

harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.

remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?

harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly

GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.​