I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol
Related
10.3.2.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.3.2.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=6006931924117882402
10.3.1.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.3.1.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=1395089523397934131
10.2.2.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.2.2.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=1395089523397908184
10.2.1.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.2.1.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=11410963190603887317
10.0.7.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.0.7.0.PDGCNFH_v10-9.zip/download
https://androidfilehost.com/?fid=11410963190603845043
New links will be posted here.
10.0.4.0 bootloops for me
Coming from Pixel 3 Experience GSI ROM by EnesSastim. I can fastboot flash the official MIUI 10 Global which works but every time I flash this ROM via TWRP I just get bootloop.
Full wipe doesn't seem to help so I guess I'm sticking on the official Global ROM for now. Any ideas?
10.2.1.0 added in OP.
mike freegan said:
10.0.4.0 bootloops for me
Coming from Pixel 3 Experience GSI ROM by EnesSastim. I can fastboot flash the official MIUI 10 Global which works but every time I flash this ROM via TWRP I just get bootloop.
Full wipe doesn't seem to help so I guess I'm sticking on the official Global ROM for now. Any ideas?
Click to expand...
Click to collapse
Not sure if you ever figured it out but the instructions on EU's site are terrible and not very descriptive.
When they mean when they say "Wipe /Data" is to hit Wipe > Format Data > Type Yes (and swipe to confirm I believe) You will then have to copy over the zip to your phone and flash (That's why the instructions are written that way)
Keep in mind, that this will wipe your internal storage so make a back up. It also takes a long time to boot, longer than clean miui install.
is it possible to flash from one MIUI 10 rom to another? mine is on stock chinese 10 rom now, and can't see any files on the root folder of the phone under recovery. may need to use the rom's flash function.
Hello friends, I hope and can help me, it turns out I have the ROM installed but not let me have permissive the seLinux with the kernel stock, just let me if I put a modified kernel, the problem is that for me none of all the modified kernel gives me the autonomy that gives me and L kernel stock, I want to have the permissive ROM of seLinux with the kernel stock, someone knows how? Thank You for your help
10.2.2.0 added in OP.
Might sound like a silly question, but when the phone was first launched and people applied xiaomi.eu roms, some reported that installing magisk would brick their phones for whatever reason. Is this still the case? I just want to pass my safetynet
10.3.1.0 added in OP.
10.3.1.0 reuploaded: https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-10-3-stable-release.47170/post-480558
10.3.2.0 added in OP.
10.3.2.0 reuploaded.
Hey OP6 users
i thought of something. that might have been obvious for some people but maybe not for everyone.
when doing a clean flash for a custom ROM it is often needed that we flash a required base. Either OOS stable or a OOS beta version.. which ever is needed by the custom ROM.
we don't need to flash the base again when we're just updating the custom ROM (unless the custom ROM needs a newer version of the base
knowing that, is it still needed to flash the base when changing to a custom ROM that needs the exact same base?
correct me if I'm wrong, but it would save some time for us to not have to flash the same required base for another custom ROM which needs the same one we previously flashed.
it would save: two OOS + TWRP flashes every time and two TWRP reboots, which would be pretty nice?
it would also be nice to save that time if we just wanted to re flash the current ROM I/you/we were using for any reason.
then a clean flash of a current custom ROM in use or changing to another ROM with the requirement of the same base would just be as simple/fast as
Format Data !!!!(optiona)!!!!
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash GApps.zip + Magisk
Reboot System
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
How much time do you think you are wasting out of your life when you have to flash a base file (give me seconds and % of HP)? ROFL...?
If I am flashing a new ROM, usually I clean flash, test the ROM... IF I LIKE --> clean flash again, and set it up proper.
Feels good coming fresh out of the box, knowing everything is working optimized.
Anways, with xXx.NoLimits and how smooth OOS is, personally I don't really see any point on flashing custom ROMs anyways anymore.
castrum_doloris said:
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
Click to expand...
Click to collapse
Aight yeah it thougt so. Ofc I wipe data before flashing a new rom. But thanks for your input/confirmation feels good to have other opinions and experiences then there's also the fact you also have to wait until your rom supports the new base, so u don't flash a new base then switch to your custom Rom and stuff won't work correctly hehe
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
kewinhw said:
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
Click to expand...
Click to collapse
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
castrum_doloris said:
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
Click to expand...
Click to collapse
okey I'm using the disable dm-verity, forceencrypt script btw. but okey i see now hehe. thanks for your answer
I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?
Hi, hoping a kind soul out there will help to confirm a few things about moving to Android 10 from Android 9
I haven't bothered keeping my phone up to date for around a year, and I'm just looking into updating to stock OOS 10 for now.
I'm currently rooted with TWRP & Magisk running an old Android 9 custom ROM, and there seems to be a bit of confusion around TWRP and updating to android 10. I'm looking to completely format the phone, not worried about loss of data as I'll just restore titanium backups, so my plan is this to get a clean install with TWRP + Magisk+Gapps:
1) Reboot to current bluspark TWRP, Flash OOS 10.3.0, Flash twrp-3.3.1-16 mauronofrio installer.zip, Reboot to recovery
2) Flash OOS 10.3.0, Flash twrp-3.3.1-16 mauronofrio installer, flash Magisk 20.3, flash GApps arm64 10.0 nano, reboot to system & enjoy.
This was always my normal update process so i'm pretty comfortable with this way if it will work.
Can anyone confirm if this will cause issues due to TWRP not working properly with android 10 when i preform my first reboot to recovery? My thinking is that if I flash it after installing android 10 then any issues caused by android 10 should be fixed, is this correct?
Thanks!
There is no confusion at all.
Everything is clear since months ago that 10.3 was released.
Upgrade firstly to the latest 9.x Rom, then flash the latest TWRP and then u are ready for flashing 10.3 and latest magisk.
Sent from my ONEPLUS A6003 using Tapatalk
ok, so I have to go to OOS 9.09 with twrp-3.3.1-16-enchilada-Pie-mauronofrio, before upgrading to 10..3.0 & twrp-3.3.1-16-enchilada-Q-mauronofrio, even if I want to just do a full wipe and start fresh on 10.3.0?
Paratax said:
ok, so I have to go to OOS 9.09 with twrp-3.3.1-16-enchilada-Pie-mauronofrio, before upgrading to 10..3.0 & twrp-3.3.1-16-enchilada-Q-mauronofrio, even if I want to just do a full wipe and start fresh on 10.3.0?
Click to expand...
Click to collapse
This is the latest TWRP: twrp-3.3.1-x_blu_spark_v9.108_op6
The rest has already been discussed.
Sent from my ONEPLUS A6003 using Tapatalk
Hello all,
My phone came with ColorOS OOS 12 and I hate it. As soon as I rooted it it started crashing daily, I even reflashed a fresh oos12 image using the local update tool and only granted superuser to one app (solid explorer so I could access user files) and it still crashes. Not to mention all the apps i want to use don't work on android 12 (call recorder, busy box) and no custom recovery.
I've been reading through the forum and I found a downgrade package that looks like its hosted by oneplus: https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_059624cc7298428b.zip
I just wanted to make sure I am doing this correctly...
Do I use the OP Local Update app to flash?
Will I be able to flash TWRP for android 11 afterwards?
Will i need to relock the bootloader?
Should i re-root using the magisk slot b method or wait until its flashed and use TWRP?
Will it try to OTA back to android 12? If so, what's the best method to get on the latest version of android 11?
Thanks for the help.
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
EtherealRemnant said:
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
Click to expand...
Click to collapse
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
aaronbaird1 said:
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
Click to expand...
Click to collapse
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
EtherealRemnant said:
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
Click to expand...
Click to collapse
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
aaronbaird1 said:
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
Click to expand...
Click to collapse
You would need to back to 11 because OnePlus hasn't released working sources for 12. Just use the downgrade package, factory reset, then upgrade to 11.2.10.10 and you'll be good to go for custom ROMs. TWRP isn't used for flashing them, they all generally post their own recovery. StagOS was the best one I used (plus the dev is really responsive when there are issues) and people seem to really be enjoying Nameless but that came out after I went back to stock so I haven't tried it yet.
Before you mess with custom ROMs, make sure that you download the global MSM Tool and make sure you can connect it. Honestly since you have to go back anyway, might as well download and use the MSM Tool to get the device back to 11 anyway.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
Easiest way to get it into EDL is adb reboot edl but if you want to practice the key combination in case you can't get into the OS, I found if you open the MSM, check use lite firehose, and click Start before you connect the phone, it has less connection errors because it's waiting for the phone so as soon as you connect the cable, it pops up.
EtherealRemnant said:
TWRP isn't used for flashing them, they all generally post their own recovery.
Click to expand...
Click to collapse
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
aaronbaird1 said:
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
Click to expand...
Click to collapse
Yeah TWRP has issues. I soft bricked last time I tried to do anything with it and had to use MSM Tool to get back to working order.