Related
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
Hi guys, I'm facing a problem with my OPO. Last week I lost my Idea, Wi-Fi and mobile network but yesterday I managed to restore them. The problem is that now I'm on oxygen os and when I try to change rom (like nightly or cos 12), my phone get stuck in bootloop. I've tried to flash via twrp and via fastboot. What can I do to solve this problem?
Thanks in advance
Exactly what have you flashed with fastboot?
Solid-Dado said:
Hi guys, I'm facing a problem with my OPO. Last week I lost my Idea, Wi-Fi and mobile network but yesterday I managed to restore them. The problem is that now I'm on oxygen os and when I try to change rom (like nightly or cos 12), my phone get stuck in bootloop. I've tried to flash via twrp and via fastboot. What can I do to solve this problem?
Thanks in advance
Click to expand...
Click to collapse
Do a full wipe in TWRP (make sure it's TWRP and not OxygenOS's recovery) and you're good to go ahead and flash other ROM
Bobbi lim said:
Do a full wipe in TWRP (make sure it's TWRP and not OxygenOS's recovery) and you're good to go ahead and flash other ROM
Click to expand...
Click to collapse
That isn't the best option, the best option is using fastboot to flash the stock images. Especially considering the IMEI issues he's had, and the issues with ROMs not booting.
Heisenberg said:
That isn't the best option, the best option is using fastboot to flash the stock images. Especially considering the IMEI issues he's had, and the issues with ROMs not booting.
Click to expand...
Click to collapse
Yes I did thought of that but I took into consideration that he might have some data (like pictures) that are important to him so the best way is to at least get the phone up and running before I recommend a fastboot wipe with factory images.
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
Yes I did thought of that but I took into consideration that he might have some data (like pictures) that are important to him so the best way is to at least get the phone up and running before I recommend a fastboot wipe with factory images.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
His data is perfectly safe, I'd just advise him not to flash the userdata.img and his internal storage won't be wiped. No doubt about it, the right option for him is flashing the stock images.
Heisenberg said:
His data is perfectly safe, I'd just advise him not to flash the userdata.img and his internal storage won't be wiped. No doubt about it, the right option for him is flashing the stock images.
Click to expand...
Click to collapse
The last time I got into a similar situation as him, I didn't flash userdata.IMG but everything wouldn't boot so I tried out flashing another ROM, extract out all the data and used factory images. But no point debating on which method works. Since we both have the common goal of helping the user get his phone working again but to each his own I would say regarding how to address this issue and I respect your opinions [emoji106]
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
The last time I got into a similar situation as him, I didn't flash userdata.IMG but everything wouldn't boot so I tried out flashing another ROM, extract out all the data and used factory images. But no point debating on which method works. Since we both have the common goal of helping the user get his phone working again but to each his own I would say regarding how to address this issue and I respect your opinions [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It isn't really a matter of opinion though. In a situation like this where the user is experiencing compounded problems, the only way to wipe the slate clean and start fresh (so any errors are removed) is by flashing the stock images. And your own experience isn't necessarily the best benchmark because I've guided dozens of people through flashing the stock images and not a single one has had an issue like you had.
So after 2 weeks of debugging and trying to figure out why Treble GSI were not booting, then booting only for some users the final answer has been found.
This bootloader is way too stateful.
So if you try directly with proper vbmeta & system.img, you won't notice anything, it will just work, that's why some people say it works.
If you try system first without doing vbmeta, then it will mark the slot as not bootable. Flashing vbmeta afterwards will NOT mark it as bootable.
it also requires the latest fastboot with --disable-verity and --disable-verification, don't know why yet exactly.
Now if you bootloop to mark it as bootable again, you need to flash the boot partition of the slot.
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
This same issue also applies to users trying to restore to stock sometimes.
This means that the One Plus 6 will require proper documentation on how to do things, and people will have to stick to it, see official instructions in post 2.
Now that we know what the exact cause is, and how to deal with it, let the development begin.
PS
Doesn't seem to be OP fault, just stock Qualcomm bootloader.
Credits to Phhusson and me for making this possible, providing phh a device, documenting the findings and all.
WARNING This is still ALPHA
OFFICIAL INSTRUCTIONS
Correct installation procedure of a GSI on the One Plus 6, determined together with @phhusson
Make sure you unlocked the bootloader and that you have the absolute latest ADB and Fastboot from Google, none of the minimal packages we know of will work!
Then in fastboot flash the following, WITHOUT rebooting in between! this needs to be done all in one go!
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Use the STOCK boot image!
Then flash the GSI system image of your choice
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
Then flash STOCK vbmeta image with the specific commands!
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then just fastboot reboot or select start on the phone.
---------------------------------------------------------------------------------------------------------------------------------------------------
If the above fails and you get a bootloop you will have to repeat all the steps above.
---------------------------------------------------------------------------------------------------------------------------------------------------
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
@Exelios
Thank you for sharing.
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Great work man,
I had held off trying as I didn't know if it would work for me or not. Looking forward to trying this out!!!
Sent from my OnePlus6 using XDA Labs
joemossjr said:
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
Click to expand...
Click to collapse
Yeah you can do that once, but to get your first slot back you will need to re flash boot also at some point.
And remember once you flash boot you need to root and TWRP again.
Sent from my OnePlus 6 using XDA Labs
CertifiedBlyndGuy said:
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Click to expand...
Click to collapse
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
Give it a day, phh is trying to implement fixes to the findings in a more elegant and easier way for the end user, this thread was more intended to share our findings with other devs.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
I've booted multiple roms comsic aosp aosip they boot just gotta get it right the first time
Exelios said:
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Ok. Just PM me and I'll move the thread when it happens
Still investigating, there is probably still something to this I'm missing
Exelios said:
Still investigating, there is probably still something to this I'm missing
Click to expand...
Click to collapse
What is the findings so far?
DocRambone said:
What is the findings so far?
Click to expand...
Click to collapse
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Exelios said:
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Click to expand...
Click to collapse
I couldn't get v19 of phh's AOSP to boot for the longest time until I tried this! Thanks man!! :good:
I have cleaned up the OP and added clear instructions in post 2.
Tho LOS still doesn't boot for now, but that's because of a bug specific to the GSI, not a bootloader issue.
Delete
CertifiedBlyndGuy said:
Ok. Just PM me and I'll move the thread when it happens
Click to expand...
Click to collapse
Might I ask to make this a sticky?
Because every developer needs to be aware of it, this doesn't affect just GSI, one can run in the same issue even if flashing TWRP or restoring to stock or anything.
And every user should know about the official way to do things on the One Plus 6, which is slightly different then all other phones.
Thanks
The instructions in post 2 is the same as in the treble thread, still no boot other than aosp v18
I am not loving android 11 so far so i want to go back to 10
Your guide is right here on the factory images page.
The bug ok touchscreen still present on 11?
I find no real difference. Battery is phenomenal on either.
Pixel 4a 9/4/20 (100 to 10)
08h 40m (a10)
09h 12m
09h 09m
09h 08m
09h 06m (a11)
09h 42m
09h 08m
08h 06m (rooted 9/14/20)
08h 46m
08h 48m
09h 34m
Sent from my Pixel 4a using XDA Labs
I took an Android 11 upgrade by accident. How do I downgrade to Android 10 without wiping data?
digger16309 said:
I took an Android 11 upgrade by accident. How do I downgrade to Android 10 without wiping data?
Click to expand...
Click to collapse
I believe you should be able to, but you'd have to do a dirty flash. This guide should be as good as any if you want to give that a try. Though you should definitely back up everything you can in case it goes wrong or if I'm mistaken about being able to flash an older image in this way.
Couldn't you just force the other partition as active?
That might also work, I suppose. Didn't think about that.
The command for that is "fastboot --set-active=x" btw. Where x is either a or b, depending on which partition is the non-active one.
Thanks for the quick reply and both options. I have TiBackup and can pull over everything onto a PC first.
I wasn't aware the updates alternated slots on Pixels.
I'm hopeful the upgrade pushed to the open slot and I can go back, but I didn't know the command.
OK - setting the boot partition didn't work because...my phone came with the factory image on slot b, nothing on slot a, and the Android 11 update wrote over slot b. Thanks, Google.
Is it possible to clean flash the Android 10 factory image directly to slot a, removing -w from flash all.bat, then set to slot a and have it back as it was?
Sorry, I'm a noob without TWRP... what fastboot command would do that?
Why would anybody want to downgrade ?
AstroDigital said:
Why would anybody want to downgrade ?
Click to expand...
Click to collapse
Because I had Magisk modules and EdXposed modules that only worked with Android 10.
digger16309 said:
OK - setting the boot partition didn't work because...my phone came with the factory image on slot b, nothing on slot a, and the Android 11 update wrote over slot b. Thanks, Google.
Is it possible to clean flash the Android 10 factory image directly to slot a, removing -w from flash all.bat, then set to slot a and have it back as it was?
Sorry, I'm a noob without TWRP... what fastboot command would do that?
Click to expand...
Click to collapse
I'm not really sure I understand what you're trying to accomplish with the different partition slots. If all you're concerned about is getting back on Android 10, I wouldn't worry about the partitions at this point. The main thing is that you need to remove the -w because that's the argument that essentially does a factory reset. Once you made that change you can run the bat file.
CoryCoolguy said:
I'm not really sure I understand what you're trying to accomplish with the different partition slots. If all you're concerned about is getting back on Android 10, I wouldn't worry about the partitions at this point. The main thing is that you need to remove the -w because that's the argument that essentially does a factory reset. Once you made that change you can run the bat file.
Click to expand...
Click to collapse
Well, I can't find much if any online description of dirty flashing a previous version of android over a current one, without TWRP. Fastboot commands are not my strength. My thinking is, if I flash A10 onto slot a, but mess it up, I still have a well-working A11 I can boot to onto slot b, and I live to tackle it again. If overwriting A11 with A10 on slot b doesn't work or messes it up so that it's not bootable at all, then what am I left with?
Oh, I see what you're saying. The -w is for a clean flash. Removing it is how you do a dirty flash. And I suppose you could flash to the inactive partition to try and preserve your A11 install. My assumption was that in the event of a failed dirty flash of A10, you'd probably want to cut your losses and do a clean A10 install next. In that case what you'd be left with is a fresh install of Android 10 and you'd restore everything you backed up earlier with Titanium.
At this point, if I could root A11, I may just stay on it and live with it, but I can't get a patched boot image to take. So it may be that I do a full wipe and start over.
Like it won't boot a patched boot image? Did you try on the latest Magisk?
CoryCoolguy said:
Like it won't boot a patched boot image? Did you try on the latest Magisk?
Click to expand...
Click to collapse
I tried everything (latest Magisk, beta, canary). I think the OTA install of A11, which I never wanted, was corrupted. Since I couldn't root, I pulled off all the backups and just did a factory reset. Thankfully, that did work so I'm back on A10, but now have to restore everything .
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.