noob here
1. do i need to have OxygenOS on the phone before flashing a rom like lineage?
i'm asking because my mobile data isnt working (sim still works fine in my last phone)
2. what is magisk for?
3. I don't have access to windows in order to use MSMtool,
4. so very frustrating, what am i doing wrong?
5.currently have lineage recovery and OS installed
6. Android version 10
Related
Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
balleny said:
Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
Click to expand...
Click to collapse
1. Settings, system, systemupdate
2. Read the big guide
3. Same as above
4. Same as 2
5. Same as above
6. Omni is good, havoc is good... All depends on your usage, you have to try the roms and decide for yourself.
7. After each rom flash you must flash twrp, then reboot to twrp then gapps then magisk if you want to use custom roms. (A/B partitions, read that info in guide section)
8. You don't flash, you install an apk. Many people like it. Up to you if you will like it. Try, just an apk.
9. For me, they worked from first boot.
10. Probably not, Google has made improvements in security and that's why titanium stopped working on bank aps etc.
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
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
I installed LineageOS 18.1 using the official LineageOS installation guide .. How can I revert OnePlus 7 Pro to official stock ROM ?
spacecc said:
I installed LineageOS 18.1 using the official LineageOS installation guide .. How can I revert OnePlus 7 Pro to official stock ROM ?
Click to expand...
Click to collapse
I just did this today. I was coming from Pixel Experience. It's super simple. You will lose all your data.
Download the FULL OTA to your computer: (This is a link to global version)
REMOVE any security settings you have -- pin, etc. (not sure if this is necessary, but i did it anyways)
Reboot to TWRP / Recovery
Wipe system / data
Reboot recovery again (don't worry if you cannot access the internal storage from your computer, that will get fixed after flashing)
Plugin phone to computer
Enable sideloading
Install the OTA zip by sideloading with ADB
Bash:
adb sideload OTAFilename.zip
Reboot after flash and wait several minutes
Done.
slgooding said:
I just did this today. I was coming from Pixel Experience. It's super simple. You will lose all your data.
Download the FULL OTA to your computer: (This is a link to global version)
REMOVE any security settings you have -- pin, etc. (not sure if this is necessary, but i did it anyways)
Reboot to TWRP / Recovery
Wipe system / data
Reboot recovery again (don't worry if you cannot access the internal storage from your computer, that will get fixed after flashing)
Plugin phone to computer
Enable sideloading
Install the OTA zip by sideloading with ADB
Bash:
adb sideload OTAFilename.zip
Reboot after flash and wait several minutes
Done.
Click to expand...
Click to collapse
I am trying now since 5 over 5 hours to get stock OS for my 7T (hotdogb) with LOS 20 back to stock OS cause of safety net not working as well as some other stuff which i want to reset… But i am unable to install neither TWRP nor default stock OS. I am stuck with LOS recovery and cant install stock OS cause LOS is newer, and it would be a downgrade, letting it fail the upgrade via ADB. I tried with payload dumper and there the partitions are locked even tho oem is unlocked. I ran out of ideas, anything I can try?
Regarding TWRP: i tried both stock and other rom version, it did not work.
hypethetime said:
I am trying now since 5 over 5 hours to get stock OS for my 7T (hotdogb) with LOS 20 back to stock OS cause of safety net not working as well as some other stuff which i want to reset… But i am unable to install neither TWRP nor default stock OS. I am stuck with LOS recovery and cant install stock OS cause LOS is newer, and it would be a downgrade, letting it fail the upgrade via ADB. I tried with payload dumper and there the partitions are locked even tho oem is unlocked. I ran out of ideas, anything I can try?
Regarding TWRP: i tried both stock and other rom version, it did not work.
Click to expand...
Click to collapse
I think you need MSM tool,it's pretty straight forward.Why bothering with trwp.