Related
How To Flash Roms with the Ridiculous Slots... yep. You're a rookie again because these things are going to drive you onto a drunken crazy bender... You'll probably wake up in Mexico married to someone you've never met and tied in with the Chicago Mob in debt for a quarter million. THIS IS WHAT WORKS FOR ME. I do the same thing Every time and have done this wrong so many times I've lost count.
Note number 1...
You have or know how to use adb and fastboot basics... if not... Of not Google the Adb and fastboot set up for your devices and/or PC/Laptop etc... There are a lot of forums and Q&A on setting this up to get fastboot cmds running. You should be familiar regardless and at least have the stock flashall.bat for a Google Stock IMG JUST IN CASE. I am assuming everyone is already at the install for TWRP and is working with 3.2.0-0 only. You cannot flash roms without it. Any other version for 8.1 will NOT work at this time...
Note number 2...
Roms will vary. Some may include the vendor image and you don't need to flash it. Some may include gapps and you don't need to flash those... Some may include everything and have you flash to slot_a and that is all. In other words do what the OP says, they built it. They know what's in it and how it works.
Here's the trick... It doesn't mean you can't do these in any other way but you will NOT get stuck if you follow some simple rules...
Roms only flash while in Slot_A
Gapps only Flash in Slot_B
Kernels only flash in Slot_B
Magisk only flash in Slot_B
IMG Flash to Slot_B
TWRP 3.2.0-0 ONLY
TWRP 3.2.0-0 to either slot
Do NOT EVER Flash anything other then TWRP, Rom Gapps and Vendor until GOING through first boot. Yes you can but it increases your issues.
Always always always double check between every install the status of your Overlays folder. Before every rom install Mount System then Go to File Manager and Delete that folder from Slot B before you boot to Slot A to flash the rom. This can hold Data from Magisk and Mods that get all tore up Everytime... It also happens when you reflash Magisk or dirty flash a rom. I'm going to put together a fresh flash below and I'll get into that a little later.
So from stock Google image...
Clean flash... MAKE SURE YOUR LOCKSCREEN IS OFF... No fingerprint set up... Not a pin set up... No pattern set up. If your more secure than swiping up to open your screen your not getting in to TWRP 3.2.0-0 decrypted.
Either... Reboot recovery (you'll be in slot B) if you already have TWRP installed....
Or....If you're just booting TWRP for the first time...from bootloader you fastboot boot (not flash really the terminology is BOOT) TWRP-3.2.0-0-marlin.img (you'll be in slot B)
Read your bootloader screen or go to TWRP 3.2.0-0 Reboot menu to find out which slot you're in.
FLASHING YOUR FIRST ROM...
note... Most are going to require before flashing your coming from stock. Just do it. At least the initial install... Dirty flash or clean flash after that without going back to stock but you don't have to flash the stock image.
Ready... You're in slot b remember...in order here...
- Wipe Data System Cache
- Flash TWRP 3.2.0-0 the ZIP
This is why you can't have your lockscreen on... If you didn't listen just go back to your bootloader and start over with the flash-all.bat. Sorry but I warned you... You can't get anything to flash at this point because you can't decrypt 3.2.0-0.
- Go to MOUNT then make sure your system box is checked
- Go to ADVANCED and then File Manager and make sure you have no overlay folder. If you do... click on it and hit delete from the options on the bottom portion of TWRP.
- HIT HOME and Go to the actual reboot menu choice (Not the swipe reboot system)
-Click on slot_A and then reboot back into recovery. ...NOTE... I usually don't use the reboot recovery option.(reboot recovery seems wonky and doesnt work for me all the time) I reboot system and just hold volume down until I hit the bootloader and the choose recovery in the bootloader options...
You ARE in Slot A now... Right... You can Double check in the bootloader or TWRP in the reboot menu.
- if you really really really like to wipe you can wipe Data system and cache in Slot_A... I never do from slot_a but to each their own.
- Flash rom and flash TWRP 3.2.0-0. Nothing else.
- Reboot back to recovery again.
You ARE in slot B. Yep automatically... When a rom is flashed it goes to the opposite slot. And reboots you there on the next recovery reboot so DO NOT GO change your slot to B unless an OP actually directs you to do so.
So... We're in slot B
- Flash Gapps and Vendor... nothing else until after you boot up.
Yeah yeah... You want to be rooted... Well boot up first and we'll hopefully be able to walk through that too.
Your booted up. Go to your development options and double check to make sure USB Debugging is enabled... Really whatever, you're really pretty safe if you have Your fastboot drivers and they must be installed because you installed TWRP to get this far so if something goes wrong from here we can still always do the flash-all.bat so your phone shouldn't implode and brick out.
Reboot recovery. Yep you're in slot B... You should now always boot recovery to slot_b unless you mess something up and get stuck in a loop. I've seen it but couldn't duplicate. It was always me flashing out of order.
GAINING ROOT... MAGISK INSTALL
- Choose the zip, flash and reboot.
Nothing further needed, make sure it's compatible with 8.1 and at least 15 to 16 are Oreo compatible. Easy right.
Well even when I'm updating... the wonderful Overlay folder can get jacked. I'm pretty sure I've heard it laugh at me as I stuck in bootloop after bootloop... If you delete the overlay folder anytime BEFORE you update to the next version of Magisk you'll be ok
UPDATING MAGISK...
So if you're on 15.3 and you want to get to 16.0 without getting stuck or having issues on boot.
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
MAGISK AND KERNEL
To get Magisk and a kernel going can give you to madness. It gets a little tricky. But honestly devs have really really improved the process. If you're rooted already most you can flash reboot into the rom reboot to recovery again and then do this again...
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
For the most part the current kernels do not blow out your Recovery anymore however some do. In fact the only one I know that will is Noexezshades. Probably spelled that wrong but you'll catch my drift if you read his OP.
SERIOUSLY YOU BETTER ALREADY HAVE BOOTED INTO YOUR ROM FOR THE FIRST TIME.. You'll hate your life if you set this up during your initial install.
INSTALLING KERNEL WITH MAGISK
- Reboot Recovery (hahaha. Ha. You turned your fingerprint scanner on... Reboot and turn it back off)
- Flash Magisk
- Reboot
I know... right now you're saying WTF... I didn't flash the kernel. This is just a fail safe... Points in Any Kernel need Root to install... I haven't had issues but really probably because I always flash Magisk first.
If you already had Magisk installed start here.
Now we're going to Flash the kernel. It's going to unroot you so we'll just immediately install Magisk I recommend always installing Magisk after a kernel because it also Patches the boot otherwise there are times when patching the boot.img is required however I believe most DEVs have surpassed that FOR MOST KERNELS.
- Reboot recovery (Dang. You forgot to turn off your fingerprint sensor again, sorry life's rough turn off your lockscreen again)
- Flash kernel
- Reboot system
- Reboot recovery (you might lose TWRP however every Newer version I'm using--- unless noted by the OP--- is working at present)
- DON'T flash Magisk... No dont flash Magisk. If you were following along you can see you need to go delete the overlay folder before you flash Magisk it will almost always go bad at this point if you don't delete the overlay folder
- Flash Magisk
- Reboot.
Hopefully you learned what's happening now in the background. I try to explain things from a user level and do this as part of my daily work every day. I don't understand things unless someone tells me what's going on along the way and keeps me partially entertained...
Talk amongst yourselves or don't post Anything. The goal is to take the issues out of the day to day so the devs aren't getting the questions.
I'm gonna have to read this post a couple of times to get the hang of it. I'm kind of a newbie.
Great post. Thank you for the write up. Helps to understand twrp when dealing with two partitions
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Sent from my Pixel XL using Tapatalk
pkelly517 said:
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Click to expand...
Click to collapse
It'd be neat if I could edit my post from the XDA app. My screen and back glass broke... then the earpiece blew out so I was awaiting parts and haven't been online
I need to go away from the option of even flashing TWRP at kernel install. As everyone updates their kernels... I see it starts a looping issue now. Everything else is solid.
overlay folder
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
-Happy Feet- said:
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Mikkey81 said:
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Click to expand...
Click to collapse
Thanks for your help, great explained for an pixel Beginner.
Gesendet von meinem Pixel XL mit Tapatalk
beezza said:
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
Click to expand...
Click to collapse
Go to TWRP.
Open Mount and click to Mount System
Open Advanced and then choose File
If you find a folder in your root named 'overlay' tap on it (select it) and then click on delete.
If it's not there.... great. You've probably never rooted. It'll cause some bootloops once in a while, sometimes it doesn't matter. It's more important to do this at the point of flashing a room because you most likely will not get a fresh install to boot up if you're rooted.
Quick Note: This file carries over Magisk root data and gets messy as you update Magisk or reflash it.
I tried installing latest magisk on android "P" and was on Slot-B and it wouldnt install, error...
changed to slot-A and then it installed..
Magisk v16.3 (1630)
Thanks for info. good stuff i am new to pixel coming for my old friend nexus 6
just fyi I downloaded and flashed twrp-3.2.1-2-marlin before reading this and just happen the passcode thing for me is not a problem. Had to enter it twice the first time using twrp but now just once. works fine.
I don't give nearly enough appreciation where it's due but I gotta hand it to you... By far the best guide ever! Thank you!
Very good details and advice. I'm having far else problems by following these steps. Thanks for all your work.
commenting here to save this for future.
thank you OP!
hoping this thread is still alive. . . is there a recommended factory image to restore to? do i need to flash the factory on both slots? is it best to flash -the factory system.img on a particular slot? In the end which slot to --set_active=?
And how do the SLOTS come into play for doing a TWRP backup and doing a TWRP restore ?
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Joe199799 said:
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Click to expand...
Click to collapse
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
farhan20 said:
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
Click to expand...
Click to collapse
I flashed OOS 9.0.12 yesterday because I switched ROMS with 9.0.11 and it resulted in a msm flash, turns out switching roms from 9.0.11 is a bad idea. But after updating I flashed havoc OS and everything is all good. We appreciate the answer I understand it a little better now
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good.
Click to expand...
Click to collapse
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Nsane457 said:
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Click to expand...
Click to collapse
That was a very well written and insightful answer thank you. The way you wrote makes everything much easier to understand
I think with the new TWRP recovery flashing is about to be less of a d**k. TWRP 3.3.0-0
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Try restoring through the msm tool.
TheRemyx said:
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Click to expand...
Click to collapse
Have you wiped the cache?
It's not a hardware issue.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
Scott said:
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
Click to expand...
Click to collapse
Thanks guys. Using MSM worked.
For those who may have the same issue, I used MSM to go back to 9.0.11 since a few people said they had issues with 9.0.12 such as not being able to unlock it. I restored 9.0.11, unlocked my device, then flashed the 9.0.12 OTA. Issue stayed resolved.
I did try to flash Omnirom again and the issue came back, so I'm curious as to what's happening. I'm going to try another Rom.
Just an update, this seems to happen with any rom I flash now. I tried Omnirom, Pixel Experience, and Syberia OS. They boot up but with no 4g connection. When I use MSM to go back to 9.0.11 or 9.0.12 everything works properly. Not sure what I may be missing?
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
dj_ooms said:
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
Click to expand...
Click to collapse
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
dj_ooms said:
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
Click to expand...
Click to collapse
I had tried flashing GAPPs (ARM64-Nano) and it didn't seem to make a difference. I was skipping that and flashing Magisk just to confirm if I had service first. But would service/signal be dependent on something in GAPPs? I may try your way. I hadn't run into any issues with encrypted storage lately. The last few times I was able to get around it by booting to system first, then rebooting back to recovery.
schmeggy929 said:
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
Click to expand...
Click to collapse
I was installing TWRP because every time I restored or flashed, I was losing my custom recovery.
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
CptUnicorns said:
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
Click to expand...
Click to collapse
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Striatum_bdr said:
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Click to expand...
Click to collapse
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
CptUnicorns said:
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
Click to expand...
Click to collapse
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Striatum_bdr said:
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Click to expand...
Click to collapse
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
CptUnicorns said:
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
Click to expand...
Click to collapse
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
OhioYJ said:
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
Click to expand...
Click to collapse
That does clear up things for me, I've either mis-read or not read that when on slot A you are actually flashing slot B and Visa versa.
I'll be flashing both my slots to 10.3.1 just so they're fully updated. ( A is my main)
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
CptUnicorns said:
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
Click to expand...
Click to collapse
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Great stuff. Thought I understood from how you explained it. I'll check that guide as well and have it to hand just incase.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Something didnt want to play when I was flashing... Got to flashing gapps and magisk, gapps flash gave me a error 64 and i got magisk installed, booted, now I've got no twrp and when I use fastboot it just softbricks then restarts after about 5 minutes, I'm gonna try booting from 3.2.3-2 as that was fine and hope I can boot into recovery and just go lineage I think for something new
EDIT
So I used fastboot --set-active=a, managed to get back to twrp so now its flashed on both again. In the process of flashing lineage now, hopefully this wont chuck another error at me for gapps
For the past 24+ hours I've been trying to flash a few custom roms on my UNLOCKED BOOTLOADER OP6T, but the phone TURNS OFF a few seconds after the boot sequence/animation.
I've read about the A/B slots and tried the Roms' flashing instructions, along with a few suggestions from others, but I cannot get any Custom Rom on my phone...
Here are the steps I've taken to flash (a few times I tried different things that I'll put in parenthesis). Is there anything ya'll see that I'm doing wrong?:
Starting from OOS 10.3.2 Fastboot Recovery and all required files on an OTG USB Drive
fastboot to TWRP....img
Confirmed I'm on Slot A
Wipe Data/Dalvik
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
(Format Data)
Confirmed I'm on Slot B
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot B
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install GAPPS (Arm64 10.0 Nano)
(Format Data)
Reboot System
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
oooscasianooo said:
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
Click to expand...
Click to collapse
Have you tried without Gapps?
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Thanks. I actually gave up and setup stock OOS again, so it took a while to get a TWRP backup, etc. etc.
So after the backup, I installed Xtended + TWRP, reboot to recovery, installed Xtended + TWRP, wiped dalvik, and reboot to system.
Boot animation shut down issue as usual.
Afterwards, I copied the pstore folder (attached zip).
Thanks!
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Anything in the logs I can look for?
This is driving me crazy. I flashed MIUI just fine (because it had the .bat file that does everything for you). Essentially it's doing the same thing as flashing OOS & Rom on A/B, right?
Just tried flashing the newest Xtended Rom (May 11th), same issue. Phone vibrates and completely turns off while the boot animation is running.
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
mrmcshagbag said:
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
Click to expand...
Click to collapse
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
oooscasianooo said:
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
Click to expand...
Click to collapse
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
mrmcshagbag said:
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
Click to expand...
Click to collapse
Thanks! Do you mean the "mauronofrio" version?
oooscasianooo said:
Thanks! Do you mean the "mauronofrio" version?
Click to expand...
Click to collapse
Yes couldn't remember the exact name but I knew you would be able to find it haha
mrmcshagbag said:
Yes couldn't remember the exact name but I knew you would be able to find it haha
Click to expand...
Click to collapse
hahaha thanks! I was thinking, "is there a T-Mobile version of TWRP?!" haha!