Related
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
Hey guys,
Back in the days when I had my HTC m7 and OP3T.
I saw some threads that people flashed 2 roms on 1 device.
Maybe like old windows that u can pick whichever u wanna boot from when u start the phone.
Is there a way I can do that on my Oneplus 6 ?
I want to flash the Android DP3 rom on a "second" slot for example (I am really curious about it)
R3VX said:
Hey guys,
Back in the days when I had my HTC m7 and OP3T.
I saw some threads that people flashed 2 roms on 1 device.
Maybe like old windows that u can pick whichever u wanna boot from when u start the phone.
Is there a way I can do that on my Oneplus 6 ?
I want to flash the Android DP3 rom on a "second" slot for example (I am really curious about it)
Click to expand...
Click to collapse
You can try to flash a rom on slot A and another on B (i did not try this method) but you can't flash oos and P dp3 because oos is encrypted and beta dp3 is decrypted
R3VX said:
Is there a way I can do that on my Oneplus 6 ?
I want to flash the Android DP3 rom on a "second" slot for example (I am really curious about it)
Click to expand...
Click to collapse
Not going to work, even with OOS roms.
The A/B system is designed for seamless updates, not completely separate OSs. Not all partitions are duplicated. The two slots share some things that will cause conflicts.
is there a different way then? i've definitely seen some people do it smh
R3VX said:
is there a different way then? i've definitely seen some people do it smh
Click to expand...
Click to collapse
no, there is no way yet.
Didn't past dual boot methods use the recovery partition and a modified twrp? That's not going to work on an A/B phone since there is no recovery partition anymore.
Maybe you could hack A/B to create truly separate slots, but I'm not aware of anyone doing it.
Hitman478™ said:
You can try to flash a rom on slot A and another on B (i did not try this method) but you can't flash oos and P dp3 because oos is encrypted and beta dp3 is decrypted
Click to expand...
Click to collapse
This has changed since the recent beta 3. Beta is now encrypted
vijai2011 said:
This has changed since the recent beta 3. Beta is now encrypted
Click to expand...
Click to collapse
You mean that I can try it without format userdata? This could be a great info
Sent from my OnePlus6 using XDA Labs
Hitman478™ said:
You mean that I can try it without format userdata? This could be a great info
Click to expand...
Click to collapse
I moved to beta 3 from 5.1.9 rooted without any reset. Your mileage may vary ofc.
vijai2011 said:
I moved to beta 3 from 5.1.9 rooted without any reset. Your mileage may vary ofc.
Click to expand...
Click to collapse
This sounds good :good: thank you, i can finally try beta 3 without format userdata
Hi, I just rooted my 7 Pro with the official guide video ( https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/ ). I've done all the steps correctly but when I try to boot into system on partition B, my phone goes straight back into TWRP Recovery.
The A partition works fine.
Am I supposed to use the A partition?
Mine does the same, I had to reflash twrp from fastboot on slot b to make it work.
JedixJarf said:
Mine does the same, I had to reflash twrp from fastboot on slot b to make it work.
Click to expand...
Click to collapse
How do you do that?
I'm not too keen with rooting
Xpelazus said:
How do you do that?
I'm not too keen with rooting
Click to expand...
Click to collapse
If it's anything like the pixel it's really only made to boot the active slot. So I'm going to say it's pretty normal that you can only boot one slot they both share the same data.
mac796 said:
If it's anything like the pixel it's really only made to boot the active slot. So I'm going to say it's pretty normal that you can only boot one slot they both share the same data.
Click to expand...
Click to collapse
I read somewhere that if you use the B partition, then you can save the A partition for system updates and not delete your rooting in the process
Xpelazus said:
I read somewhere that if you use the B partition, then you can save the A partition for system updates and not delete your rooting in the process
Click to expand...
Click to collapse
Every time you flash the OTA it's going to go to the other slot. Really all its for is fast seamless updates
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.