Related
Hi everyone.
Just wondering about something :
Everywhere, we see people instructing to reboot the recovery after flashing any ROM, to "switch slots", because it flashes in the inactive slot, and other packages flash in the active one. Until there, no problems, seems legit.
Maybe a stupid question : in TWRP, there is a switch in the "Reboot" section to select the active slot. Why just not use that ?
Is there a reason, or do people don't talk about this to avoid user error ?
Totone56 said:
Hi everyone.
Just wondering about something :
Everywhere, we see people instructing to reboot the recovery after flashing any ROM, to "switch slots", because it flashes in the inactive slot, and other packages flash in the active one. Until there, no problems, seems legit.
Maybe a stupid question : in TWRP, there is a switch in the "Reboot" section to select the active slot. Why just not use that ?
Is there a reason, or do people don't talk about this to avoid user error ?
Click to expand...
Click to collapse
Because you wanna make sure the TWRP you just flashed sticks, switching manually is not recommended
whizeguy said:
Because you wanna make sure the TWRP you just flashed sticks, switching manually is not recommended
Click to expand...
Click to collapse
I see. But if you make sure to flash the TWRP installer last each time you do something, wouldn't this prevent any error ? As it flashes on both slots anyway ?
I mean something like :
- Flash a stable OOS
- Switch slots
- Flash it on the other slot
- Flashing the TWRP installer to keep in in place
This would be way simpler that things we see on this forum with constant reboots, ect, haha !
Totone56 said:
I see. But if you make sure to flash the TWRP installer last each time you do something, wouldn't this prevent any error ? As it flashes on both slots anyway ?
I mean something like :
- Flash a stable OOS
- Switch slots
- Flash it on the other slot
- Flashing the TWRP installer to keep in in place
This would be way simpler that things we see on this forum with constant reboots, ect, haha !
Click to expand...
Click to collapse
Try it your way and let us know
whizeguy said:
Try it your way and let us know
Click to expand...
Click to collapse
Oh i did ! I went back to Stable OOS 9.0.3 yesterday, did it like this, no problems encountered
Check the active slot -> Flash OOS -> Switch to second slot -> Flash again -> Back to first slot -> Flash Magisk and TWRP :good:
when I flash a new build of stock for example, I reboot to recovery, flash rom, flash recovery, reboot recovery, flash magisk, reboot. I dont do the rom twice, never had issues.
gffmac said:
when I flash a new build of stock for example, I reboot to recovery, flash rom, flash recovery, reboot recovery, flash magisk, reboot. I dont do the rom twice, never had issues.
Click to expand...
Click to collapse
Yup, works the same. What i'm wondering is why we all bother rebooting the recovery between ROM and Magisk/TWRP flashing instead of just switching the active slot in TWRP.
It's not such a big dead as rebooting TWRP does switch slots too, but this can but more convoluted for new users as they often don't get why you have to reboot the recovery during the flashing process.
In the end this doesn't change anything, i just wonder why i haven't seen anybody use that feature
Agreed this confuses things as well. I read it was "not recommended" to switch slots within TWRP but no one can confirm "why?". It sounds like the reboot to recovery method just made its way into every ROM flashing instructions and it just isn't necessary as long as you flash the TWRP zip last.
jdgesmlls said:
Agreed this confuses things as well. I read it was "not recommended" to switch slots within TWRP but no one can confirm "why?". It sounds like the reboot to recovery method just made its way into every ROM flashing instructions and it just isn't necessary as long as you flash the TWRP zip last.
Click to expand...
Click to collapse
Let's say you flash OS, magisk, kernel then twrp then reboot to system you will end up with no root, no custom kernel since twrp will replace boot img. That's a good reason to follow it as it tells you why you reboot to twrp instead of swapping slots is because you wanna make sure the twrp you just flashed is actually installed, if not you can fastboot and flash it to see again if it works.
jdgesmlls said:
Agreed this confuses things as well. I read it was "not recommended" to switch slots within TWRP but no one can confirm "why?". It sounds like the reboot to recovery method just made its way into every ROM flashing instructions and it just isn't necessary as long as you flash the TWRP zip last.
Click to expand...
Click to collapse
This approach did not just "make its way into every ROM flashing instruction." There's a very good reason not to: You're short-circuiting safeguards built into the Android updating process. When you reboot to recovery after flashing an update, the system doesn't just "switch slots." It checks whether the slot is bootable, and if it isn't, it marks it as unbootable and switches safely back to the original slot. When you switch manually, you're circumventing that step, and you may be switching to an unbootable slot. Except this time, you may boot to a black screen with no way out except wiping your whole phone with the MSM dowload tool.
You guys are free to continue switching manually, and if you do everything right, you should be okay. But there's a good reason not to, and threads like this just get noobs in trouble for no good reason.
iElvis said:
This approach did not just "make its way into every ROM flashing instruction." There's a very good reason not to: You're short-circuiting safeguards built into the Android updating process. When you reboot to recovery after flashing an update, the system doesn't just "switch slots." It checks whether the slot is bootable, and if it isn't, it marks it as unbootable and switches safely back to the original slot. When you switch manually, you're circumventing that step, and you may be switching to an unbootable slot. Except this time, you may boot to a black screen with no way out except wiping your whole phone with the MSM dowload tool.
You guys are free to continue switching manually, and if you do everything right, you should be okay. But there's a good reason not to, and threads like this just get noobs in trouble for no good reason.
Click to expand...
Click to collapse
Got it. My question was if there was a reason like what you just explained that encouraged not doing things this way.
I see why it's not the way people ar told use the Recovery, if the system isn't capable of switching back, it could indeed brick the phone in case of user error ... Didn't think about this !
Thanks for the clarification.
Interesting thread guys, thanks
Bit confused with A/B slots
Learn about a&b slots here .... Learn first flash later!
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
HIGHLY RECCOMENDED READING ... (If you have not used A&B slots before)
@Neil_Armstrong_
@Totone56
jasonv31 said:
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
HIGHLY RECCOMENDED READING ... (If you have not used A&B slots before)
@Neil_Armstrong_
@Totone56
Click to expand...
Click to collapse
Been flashing from some time, and I know how it works. My original question was about the feature in TWRP and it was answered by iElvis :good:
jasonv31 said:
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
HIGHLY RECCOMENDED READING ... (If you have not used A&B slots before)
@Neil_Armstrong_
@Totone56
Click to expand...
Click to collapse
Very effective guide thanks !
Well... after installing Magisk, I'm now getting asked to type Password to decrypt storage, which would be OK except that no keypad is coming up....
EDIT: all solved; sideloaded 19.4 to TWP and works, rooted etc. Now I need a custom ROM!
Wish I felt on this thread earlier ... Thanks guys now it's clear !
iElvis said:
This approach did not just "make its way into every ROM flashing instruction." There's a very good reason not to: You're short-circuiting safeguards built into the Android updating process. When you reboot to recovery after flashing an update, the system doesn't just "switch slots." It checks whether the slot is bootable, and if it isn't, it marks it as unbootable and switches safely back to the original slot. When you switch manually, you're circumventing that step, and you may be switching to an unbootable slot. Except this time, you may boot to a black screen with no way out except wiping your whole phone with the MSM dowload tool.
You guys are free to continue switching manually, and if you do everything right, you should be okay. But there's a good reason not to, and threads like this just get noobs in trouble for no good reason.
Click to expand...
Click to collapse
Can you please tell me what is the correct way to go?
whizeguy said:
Let's say you flash OS, magisk, kernel then twrp then reboot to system you will end up with no root, no custom kernel since twrp will replace boot img. That's a good reason to follow it as it tells you why you reboot to twrp instead of swapping slots is because you wanna make sure the twrp you just flashed is actually installed, if not you can fastboot and flash it to see again if it works.
Click to expand...
Click to collapse
I think this just happened to me mate. I booted recovery and switch slots to B and now my phone doesnt boot, and there is suddenly no option in recovery to switch back to A... any advice? or did it already flash something and I messed up my phone?
texasslim281 said:
I think this just happened to me mate. I booted recovery and switch slots to B and now my phone doesnt boot, and there is suddenly no option in recovery to switch back to A... any advice? or did it already flash something and I messed up my phone?
Click to expand...
Click to collapse
What phone are you using?
"System update installation failed" while trying to install Q dp3, what did I miss?
I am currently on oxygenOS 9.0.8, both slots completely stock. I have unlocked the bootloader and enabled USB debugging.
I am trying to install Q dp3, but everytime I select Q dp3 zip file and press ok, update manager immediately says "System update installation failed" with no specific error code or any leads.
I have tried:
-Redownloading the Q dp3 file from here (https://oxygenos.oneplus.net/OnePlus6Oxygen_22_OTA_003_all_1907120020_wipe_ae2a3b38959345b1.zip)
-Rebooting and trying again
-Relock and unlock the bootloader
-factory reset within the settings
The strange thing is, I can normally install oxygenos 9.0.8 full update file. So I suspected problem of the dp3 file. But redownloading didn't solve the problem.
Is there something I have missed out? Some settings I have to do? Specific conditions?
Searching haven't helped me much(I searched everywhere, but I think nobody has my problem).
If someone can help me, I will be grateful. Thanks!
Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.
remewer said:
Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.
Click to expand...
Click to collapse
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?
ddaggebi said:
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?
Click to expand...
Click to collapse
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
Thanks you! Now I can flash away~
remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?
ddaggebi said:
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?
Click to expand...
Click to collapse
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.
remewer said:
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.
Click to expand...
Click to collapse
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me
ddaggebi said:
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me
Click to expand...
Click to collapse
No problem. Read more about A/B partitions. It's actually just as easy to mod our phone once you know how A/B partitions work.
Does anyone know where I can find a stock Rom preferably android 10 that I can flash in TWRP? I have the fastboot roms but when flashing vbmeta there is no partition choice to flash it to but the partition exists on both a and b slots after a gdisk print command. And I have no clue on how I would flash the bin files in TWRP. Also the same problem exists for bootloader and a few others just like vbmeta. I need stock because I completely screwed my A11 stock after a faulty magisk install and didn't know I couldn't install customs from A11. I've been away for a little bit and instead of doing homework I acted as if everything was the same from 10 to 11 and well...here I am. No computer access so fastboot is out of the question. Am I screwed until I have computer access? Thanks again,
Rooster
bigrooster88 said:
Does anyone know where I can find a stock Rom preferably android 10 that I can flash in TWRP? I have the fastboot roms but when flashing vbmeta there is no partition choice to flash it to but the partition exists on both a and b slots after a gdisk print command. And I have no clue on how I would flash the bin files in TWRP. Also the same problem exists for bootloader and a few others just like vbmeta. I need stock because I completely screwed my A11 stock after a faulty magisk install and didn't know I couldn't install customs from A11. I've been away for a little bit and instead of doing homework I acted as if everything was the same from 10 to 11 and well...here I am. No computer access so fastboot is out of the question. Am I screwed until I have computer access? Thanks again,
Rooster
Click to expand...
Click to collapse
Hi rooster, have a look at the link below. The rom is from trusted guys who have been doing moto stuff for years. Follow the instructions, and hopefully you have a good result.
Motorola Stock ROM: Sofiap // Pro
telegra.ph
Beetle84 said:
Hi rooster, have a look at the link below. The rom is from trusted guys who have been doing moto stuff for years. Follow the instructions, and hopefully you have a good result.
Motorola Stock ROM: Sofiap // Pro
telegra.ph
Click to expand...
Click to collapse
OK brother I just flashed the Rom following all instructions minus erase userdata, which is a step I usually take but I don't have fastboot right now, and it's still booting up has been for 2-3 minutes but it finally vibrated when I started it up so I'm expecting good things. Thanks so much....and there she is she started lol perfect timing! You have helped me so much as this is my daily now that I've lost my OnePlus.
Edit
everything seems to be working fine except for my calls. They don't come through but they show as missed and when I try to dial out it goes to call but then goes straight to call ended. Everything else is working tho.
One more thing..is there a certain process to root? When I flashed the magisk zip it sent me into a boot loop.
Hello!
I tried the search function but my search-fu isn't strong today. I got a Vortex V22 phone from Standup Wireless. I must have been half asleep, because when i flashed what I assumed was the correct boot.img, I got stuck in a boot loop.
On further investigation, I had flashed the boot for another device called Vortex. I am having incredible difficulty in finding the right boot image. The info I have from the side of the box is:
Vortex V22 4G LTE
Color: Graphite Blue
ROM 32GB
RAM 3GB
OS Android 11
FCC ID 2ADLJ-V22
I deeply appreciate any and all help. Thanks so much!
i was trying to find a phone case for the phone what model number is yours ?
If you're still searching I can try to make a rom dump, I have this phone as well brand new untouched or registered.
I'd just need a tutorial on the proper way to dump and extract the files so I can upload the boot.img
_
I've never used it cause I put the StandUp Wireless sim in my T-Mo InSeeGo 5G HotSpot and prefer to use my Galaxy S8 with Keyboard Cover Case and Unihertz Titan Pocket
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
PicelBoi said:
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
Click to expand...
Click to collapse
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
In fastboot not fastboot d do
Fastboot flash unlocking
And it'll ask ya if u agree bs....
& Click yes.
Mtkclient unlocks bootloader as well
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
PicelBoi said:
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
Click to expand...
Click to collapse
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
mee too
defcondoc said:
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
Click to expand...
Click to collapse
Yea, will post it later this day! Do you need anything else like my super partition?
PicelBoi said:
Yea, will post it later this day!
Click to expand...
Click to collapse
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
PicelBoi said:
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
Click to expand...
Click to collapse
I was able to get a bunch of GSI's that work with it, including the phone you posted, but I was looking to get root and found a couple pre-rooted GSI's that work as well. Newer ones do work as well I has 13 rooted and working. However, I liked the Pixel ROMs the best and would prefer to install those instead and then root. So I need the firmware for that so I can patch a modified boot.img.
PicelBoi said:
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
Click to expand...
Click to collapse
Thank you. I understand and have a lot of experience with this. However, I still never understood why there is two Fastboot's.
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
atsalchenberg said:
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
Click to expand...
Click to collapse
Are you looking for a good GSI ROM?
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
But yes I am indeed looking for a good running a12 rom
atsalchenberg said:
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
Click to expand...
Click to collapse
I completely messed up one messing with partitions and it took many tries trying to get to was able to still get to the bootloader fastboot and then recovery to fastbootD. You should be able to get it booted into fastbootd and flash as it seems you can.
Try the one below. you should be able to find it with a google search. If you can't let me know and I will try to look and see where I downloaded it from as I cannot remember where I found it.
I've tried many GSI ROM's Some boot fully, some only boot to the boot screen and some won't boot at all.
I'm using 13 rooted LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
It is vanilla. I can't remember if there is a GAPPS version or not. But you can load it all after with magisk. But its rooted.
I still would like if picelboi could share the stock rom, so we can have a boot.img. I would like to try other ROM's that are not PRE-Rooted.
atsalchenberg said:
But yes I am indeed looking for a good running a12 rom
Click to expand...
Click to collapse
I can't remember which A12 I had working but I was looking for root and the one A12 that was prerooted I had issues with so I went to A13.
This is an A13. LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
There may be a newer version of it now.
Also, these phones seem have that internet connect issue with some GSI ROMS and this is one of them I think, they connect to wifi but they won't actually connect to internet, but there is a easy fix for it.
Hello everyone, I have the OP9 china varient,
I've flashed custom ROMs in some devices in the past, specially on a Poco F1 and a Mi 11 Ultra (flashed MIUI.EU in it several times). With the OnePlus 9 the process with unlocking the bootloader was a bit different but I got it to work. But when it comes to custom ROMs installation, the end result is always a bricked device and I had to use MSM from OP9 pro to unbrick and then OP9 MSM to get the device back to normal. I've downgraded everytime to OxygenOS 11 but it didn't work. Can someone help me find out what am I doing wrong?
My procedure besides unlocking the bootloader was:
1. Install boot.img
2. From fastboot to recovery
3. Wipe everything (tried not doing it with the same result)
4. Install ROM via ADB (as an update)
5. Wipe everything (tried not doing it with the same result)
6. Reboot
7. Brick..
I've considered it being an ADB drivers problem, but the device is recognized in the computer as an ADB device so I don't think it is.
As I install through ADB, the CMD window keeps the percentage going up but on the device it never shows anything ROM related as it is being installed, just the final message saying steps 2/2 had been completed.
Thanks in advance, and happy flashing guys!
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
EtherealRemnant said:
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
Click to expand...
Click to collapse
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
lleonardocruzz said:
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
Click to expand...
Click to collapse
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
EtherealRemnant said:
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
Click to expand...
Click to collapse
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
It's only mentioned in the Stag thread and I think Lineage too but it should work with every ROM since it's only a recovery script that copies the partitions.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
mattie_49 said:
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
Click to expand...
Click to collapse
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
lleonardocruzz said:
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
Click to expand...
Click to collapse
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
lleonardocruzz said:
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
Click to expand...
Click to collapse
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
mattie_49 said:
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Click to expand...
Click to collapse
EtherealRemnant said:
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.
Click to expand...
Click to collapse
cbrown666 said:
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
Click to expand...
Click to collapse
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
lleonardocruzz said:
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
Click to expand...
Click to collapse
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
EtherealRemnant said:
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
Click to expand...
Click to collapse
I have to agree with both. I'm also a global unit op9 unlocked on C-48 rooted. Anything that is usually still maintained/updated and not deserted is better than custom. Cherry picking and flashing is overrated. Stock isn't bad at all. You guys enjoy your devices.