I am still trying to fully wrap my head around Android moving to Slot partitions. I am reading as much as I can and feel I have a better understanding of it but have tried to flash lineageOS with microg but ended up with a bricked device maybe due to not doing the proper steps to switch to the active slot? My question is if I have TWRP installed and currently on OOS 11, can I just flash the zip file for lineage OS or so I need to do something additional? The TWRP script states you have to boot into Recovery to switch active slots and flash additional items. I know if I flash lineage I will end up with their Recovery as well which I obviously dont want. Can I flash the TWRP installer after flashing lineageOS zip or no? Please help confirm or deny what needs to be done given my current setup.
Thank you all in advance for any help/experiences you can share about this.
Related
Some background: I'm coming from an OP3 which did not have this Slot A/B thing and you could easily just flash firmware going forward. I'm currently confused as to how custom roms will update firmware and such going forward.
I noticed there's 'systemless' roms now (like NoLimits), I don't really understand what the advantages/disadvantages vs something like Havoc OS are.
If I go with a custom rom, will I need to flash to OOS to update firmware then reflash back to the custom rom in the future?
I apologize if these are really newb questions, trying to find specific details with some of these keywords makes it really hard to find relevant information (and I've tried).
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Link above is some info on A/B partitioning.
The benefit of systemless ROMs are that they are just Magisk Modules so installing and uninstalling is very easy. You don't need to boot into recovery or wipe anything.
Havoc is a full ROM and based on AOSP so wiping is needed, especially when security patches are different. Some people are decrypting their phones with the no verity zip but I won't say too much about that to keep things as simple as possible.
You don't need to flash any OOS firmware when on Havoc, and I think it's because custom ROMs have their own vendor image. More advanced users feel free to correct me if I'm wrong about this.
Flashing isn't really too different and I personally don't even think about A/B slots. You just need to remember to flash the TWRP zip file after a ROM flash to keep TWRP. And you also need to reboot back into recovery to install Google apps, rather than just after the ROM flash.
Custom kernels are now flashed last (after TWRP and Magisk).
This is how I've done it and have been issue-free.
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 (Android 11) on my OP7P and want to boot (or flash) TWRP.
There is a lot of different information about the state of TWRP on Android 11.
I hope someone could clearify the following questions:
1. Does TWRP [3.5.2] support Android 11?
the release notes of 3.5.1 state that they "prepared a mini release before Android-11 support."
The release notes of 3.5.2 don't mention android 11 at all.
There are various people in the LOS18.1 thread that can boot twrp, so I assume there is some kind of (partial) support.
2. What if 'fastboot boot twrp.img' doesn't work?
For me I can't boot (or flash) TWRP (on LOS18.1).
So as the twrp/lineage os guide says I do:
fastboot boot twrp.img
Click to expand...
Click to collapse
It finished succesfull, but my phone stays in fastboot and doesn't reboot.
The TWRP guide says the following:
If fastboot boot command doesn't work you need to root your device and flash the TWRP installer (remember that flashing the TWRP installer you will lose the root).
Click to expand...
Click to collapse
I find this a very vague description; what do they mean with "doesn't work"?
(when I flash twrp it results in an unbootable phone, might be related to a/b partitions, but I have not enough knowledge of that)
3. Does TWRP work on encrypted phones?
I found various posts that suggest that TWRP doesn't work on encrypted phones.
I can't find any reliable source that supports that statement.
Twrp says this, but that doesn't clearify things at all.
I hope someone could give me some answers, or guide me to some reliable source so I can find it myself.
I find the documentation of LineageOS and TWRP lacking in that perspective.
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
lenigma1too said:
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
Click to expand...
Click to collapse
I also think there is no official TWRP for android 11, but twrp doesn't make this very clear in their docs.
Multiple people are claiming they are able to (at least) boot twrp on Android 11.
LineageOS 18.1 is Android 11 (but I will clearify the post).
Thank you for your reply
there is now a working TWRP version for Android 11.
Nebrassy version: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'
It looks like the OP8T OOS recovery doesn't really exist. About the only things it will do is wipe data or reboot to fastboot or system. No sideload.
All of the android devices that I own I have rooted as well as installed new ROMS on them and they had at least a basic recovery. Why doesn't OP8T OOS have a recovery like most any basic android OS? I really don't understand especially since OP has been very user-oriented in dealing with it's fan base. It appears the LOS recovery has these basic features. I expect other ROMS built for OP8T have a working recovery. Is there something unusual about the OP8T?
zzjea said:
It looks like the OP8T OOS recovery doesn't really exist. About the only things it will do is wipe data or reboot to fastboot or system. No sideload.
All of the android devices that I own I have rooted as well as installed new ROMS on them and they had at least a basic recovery. Why doesn't OP8T OOS have a recovery like most any basic android OS? I really don't understand especially since OP has been very user-oriented in dealing with it's fan base. It appears the LOS recovery has these basic features. I expect other ROMS built for OP8T have a working recovery. Is there something unusual about the OP8T?
Click to expand...
Click to collapse
With the move to the A/B model, you now flash updates directly in the running system. So that functionality is no longer required in recovery. Which leaves just factory reset and fastboot as the two functions you can't do while the phone is still running.
Thanks. How do you install a new ROM then?
zzjea said:
Thanks. How do you install a new ROM then?
Click to expand...
Click to collapse
You use the custom ROM's recommended installation process.
You flash images, after unpacking them, with fastbootd.
So if you wanted to go back to OOS stock ROM from a custom ROM, you have to use the MSMtool? Did Android 10 or 11 or OOS change the partition structure for the OP8T? When and why did payload. bin become the container for the img files that used to be directly in the zip file? Is this all about the introduction of the seamless update and the a and b slots?
zzjea said:
So if you wanted to go back to OOS stock ROM from a custom ROM, you have to use the MSMtool? Did Android 10 or 11 or OOS change the partition structure for the OP8T? When and why did payload. bin become the container for the img files that used to be directly in the zip file? Is this all about the introduction of the seamless update and the a and b slots?
Click to expand...
Click to collapse
Have a read of this: https://source.android.com/devices/tech/ota/ab
Note that the OnePlus 8T uses this method - it even gets the updates from Google's servers.
Since oneplus 6 nas no security updates i decide to install custom ROM LineageOS 19.1 the newest build from official website.
Before installing this ROM i do all steps gently from Funky Wizard guide.
I have ADB drivers, unlock bootloader, installed magisk (rootet phone) backup my OOS and EFS, and installed twrp.
All basic stuff. Now i was ready to go to installed lineageOS.
I install lineage and i do all steps by their official website but with twrp. ( only what i dont flash copy partition zip file i wasnt sure if that will be work with twrp ).
After restart to recovery i must install gapps. Unfortunely the recovery was replaced i was assumed istead of twrp.
I installed gapps with their recovery and all work fine until i want to replace to twrp.
Now when i boot temporarly from img to install it perm. I have weird folder names wihtout any possibility to add ZIP file.
With some research i guess that folders are somehow encrypted.
Could you help me to install twrp with lineageOS when i have still access to this files? I need it for ex. recovery to stock if something in future goes wrong.
And i am currently on android 12 for sure.
Thank you from feedback!
first of all, you'd be better of if you posted this in the right area ==> https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/ ==> more chance to get help related to LOS 19 questions (it's pure chance I saw your post here)
second: make sure to follow the instructions given at the LOS instructions pages ==> https://wiki.lineageos.org/devices/enchilada/
Mostly it is important that you have latest OOS 11 firmware installed in both slots before you start with LOS.
For the first steps never mind which recovery you have, just follow the instructions using LOS recovery. Reason is that TWRP is having problems wiping data / performing factory reset, at least it never worked for me. Then later on you can switch to TWRP
Back in May this year I wrote an instruction set here: https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/post-86879331
Interesting for you right now is everything below 1.x
2.x is a separate instructiopn set for OTA updates coming later on
Good luck!
Thank you for response. You have right its better to install it directly from dedicated recovery (lineage) and than replace with twrp. Also i fill missing steps (install recovery again and flash parition integration file) and also wipe all data as instruction says. Now after reinstall lineageos and then install twrp i have all normal structure files as before. Thanks again