This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll notice updates come without it for Global or on their Global support site, the firmware is outdated.
- On T-Mobile have full 5G. I don't know about AT&T and Verizon. Should be same.
If you are on Global and you just received your phone. Do all the updates from the incremental through device. If you want root, you can flash with the EU patched boot.img and everything will work as normal
**** but once you do this, you will need to wait for Global full OTA to update next time, unless you managed to have a backup copy of the unpatched boot.img
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
- Topjohn provides full instructions on how to do this yourself as well.
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
Go into Magisk app and install via direct install and all done.
Return to stock
- Restore boot.img from Magisk
- Uninstall Magisk
- Flash the stock boot.img
- Relock the bootloader, will wipe and return to factory reset.
Stock 11.2.33 Boot.img
boot11233_stock.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Magisk Patched 11.2.33 boot.img
boot11233_patched.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Spoiler: Previous Boot Images
Patched Boot.img for Europe (11.2.2.2.LE25DA)
boot93.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Stock Boot.img for Europe (11.2.2.2.LE25DA)
boot.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Future Full OTA Updates
- Update as usual
- Go into Magisk and choose direct install and then install to inactive slot after OTA
- This will retain root
How to do it yourself:
Download full OTA, usually Oxygen Updater App, XDA has links or from https://www.oneplus.com/support/softwareupgrade
Download Payload Dumper
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
Extract and place payload.bin in input folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Run the payload_dumper.exe
In the output folder will be boot.img, move that onto your phone, folder of your choice
Go to Magisk app, click install
Choose Select and Patch a File
Choose the file and it will patch it, Magisk will say where the file is located.
That is your patched boot.img file. Use that to flash / root your phone.
Remember only have do this once, you don't have to do this again with subsequent updates.
zymphad said:
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Go into Magisk app and install via direct install and all done.
Click to expand...
Click to collapse
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.
Slikkster2k said:
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.
Click to expand...
Click to collapse
So there seems to be confusion about version. The boot image doesn't matter. When you flash a custom rom, there isn't a EU or US version. The only difference I can think of if it's T-Mobile, so when you flash, then it would just be an international/global. This is from XDA.
Honestly I would bet the Indian version is same as well.
This is the EU, which is the same boot.img for US unlocked.
If the future you should be able to do this yourself once OnePlus adds the 9 series to their global firmware downloads list.
Good to know, thanks! I'm not planning to flash a custom rom, I just want root. So I just have to make sure the bootloader is unlocked, and then follow the steps for Magisk.
Yep, working great here. Mobile payments working fine. Using energized for adblock.
So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Edit: From what I've found, factory reset doesn't touch the boot partition. So that won't help.
This method worked for me, though I'm now running the same issue as Slikkster2k, since I don't have an unpatched boot.img, I can't uninstall magisk to update via OTA.
I would suggest, for those wanting to be able to update in the future (until we get a custom recovery), that instead of /fastboot flash boot boot.img, use /fastboot boot boot.img and then let Magisk finish the install. When Magisk patches the boot image, it will take a backup of the stock one to be used for uninstallation.
Slikkster2k said:
So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Click to expand...
Click to collapse
Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.
[email protected] said:
Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.
Click to expand...
Click to collapse
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.
@zymphad
Do you also have a copy of the unpatched boot.img file?
Slikkster2k said:
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.
Click to expand...
Click to collapse
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.
zymphad said:
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.
Click to expand...
Click to collapse
The issue is that even if we wanted to do this, Slikkster2k and I (and possibly others), don't have the stock boot.img, since we flashed the magisk patched boot.img directly. Since you provided the patched boot.img originally, do you have the unpatched version available?
That way if anyone still on the original version that came pre-loaded wants to flash back to fully stock (and maybe re-lock bootloader) they can.
Those of us on the Global/US variant (AA) don't have the full zip available, and since we can't flash incremental while rooted, we currently have no way of actually reverting to stock until OnePlus publishes the full ROM zip.
Will post the stock.
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
And the to root again would factory reset again...
The March security update is already out for Nord and 8 series. Would just wait.
The incremental is still the Feb security update which you are already on.
Thanks, I mostly just wanted to redo the root process, but use /fastboot boot boot.img instead of /fastboot flash boot boot.img, so that magisk has a backup of the stock bootloader. That way, if for some reason I need to flash back to stock before the March Security update comes out, I can do so from my phone without needing my PC.
zymphad said:
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
Click to expand...
Click to collapse
Ah, was not aware of that. In that case we'll just have to wait, hopefully OnePlus posts it soon.
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.
Slikkster2k said:
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.
Click to expand...
Click to collapse
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it
reffu said:
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it
Click to expand...
Click to collapse
Actually I tested it using fastboot boot boot.img before I flashed it, just to make sure it would work (I didn't know it was from 11.2.1.1 at the time, but I'm paranoid).
Seems the rest of the world is getting the March update except US again. Still no full package, and this time not even partial. Dunno what is going on with OnePlus and US, but it's annoying.
Will update for EU AB firmware in the OP. And then put disclaimer for Global to do all their updates prior to rooting.
Related
A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.
Now I wish I can unroot my phone, lol
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?
You can extract recovery.img from the ColorOS zip.
If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you
MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)
Deleted
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota
wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?
Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader
wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23
How to re install the original recovery :crying:
Hi everyone
Xiaomi added Anti roll-back to latest Stable/Beta ROMs and many users bricked their phones because of it, i unlocked my bootloader yesterdays and started testing everything about Anti, and here is what i found so far:
As of right now, anything Beta 8.7.6 and above has it, and for Stable 9.5.19.0 and above, check Xiaomi announcement about it, in 2nd post you will find the last Miui builds without Anti Roll-back
you can flash TWRP again
you can Root Anti ROMs with Magisk or Disable Encryption
you can switch from CN builds to Global builds or vise versa
you can switch between all anti 4 builds just fine, like from 8.7.12 to 9.5.19.0 or anything with anti 4
you can flash any AOSP/LOS based ROM
you can flash anti 4 fastboot ROMs
based on fastboot script we might get anti 5 in the future
how to bypass anti roll back lock in fastboot and flash/run anything
1- TWRP flashing method:
Boot Twrp or Redwolf using “fastboot boot XYZ.img”
Copy img to device then flash Image file of XYZ.img again from recovery.
Flash Lazyflasher Or Magisk
Or you can just flash any AOSP/LOS based ROM
or check #6 to unlock bootloader commands
2- Switching from CN Beta to Global Beta
Download Global Beta 8.7.12 Fastboot Here or Global Stable 9.5.19.0 Fastboot Here
Make sure to backup your data first
Run flash_all.bat to flash Global build and wipe everything
Wait for system to boot up, and everything should be fine
3- Flashing Custom ROMs
Flashing AOSP/LOS ROMs should be easy, flash twrp, wipe data & flash ROM
Flashing Miui based ROMs is a bit tricky, you have to make sure they didnt include bootloader inside the Zip, check for firmware-update inside Zip's before flashing or just ask other users
4- based on fastboot new script we might get anti 5 in the future, so dont keep flashing newer bootloader/modem unless ROM developer tell you to do so
here is how the new script works:
it check for Anti vlaue
if Anti is smaller than 4, then it flashes normally, but your device will be anti 4 also
if Anti is 4, it flashes dummy to anti roll-back pass, then proceed to flash ROM, after flashing is done you will have the same Anti 4 vlaues
if Anit is bigger than 4, like 5 or something else, the script will abort and tell you to get Anti 4 ROM
5- Unlocking Fastboot:
This method let you flash twrp or run fastboot commands again
Download fastboot-unlock-anti-4-whyred from attachments or Drive
Flash from fastboot running this command
fastboot flash antirbpass dummy.img
Now flash twrp, run any fastboot command
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you have to flash dummy/unlock every time you go into fastboot, or ARB will block your commands
ill keep this thread updated, make sure to follow up with updates
The Last builds without Anti Roll-back
The last builds without anti roll-back
Recovery/TWRP builds
Stable is Miui 9 9.5.17.0
Beta is Miui 10 8.7.5
Fastboot Builds
Stable is Miui 9 9.5.17.0
Beta is Miui 10 8.7.5
and this just in case
K cool Abdul?
You are legendary.. Keep it up
So, I'm on 8.7.5 right now with twrp and magisk and I'd like to keep updating as new builds come out. Can I just do what I always do? Download 8.7.12 rom, flash with twrp, flash lazyflasher and magisk?
Also would flashing other stuff risk bricking, like camera2 API zip, or YouTube vanced?
jmartinho said:
So, I'm on 8.7.5 right now with twrp and magisk and I'd like to keep updating as new builds come out. Can I just do what I always do? Download 8.7.12 rom, flash with twrp, flash lazyflasher and magisk?
Also would flashing other stuff risk bricking, like camera2 API zip, or YouTube vanced?
Click to expand...
Click to collapse
8.7.5 doesn't have Anti-rollback feature while 8.7.12 (All roms with 8.7.6 n above) has it
So u better dont update to newer versions of Official MIUI firmware to avoid issues
UCFour said:
8.7.5 doesn't have Anti-rollback feature while 8.7.12 (All roms with 8.7.6 n above) has it
So u better dont update to newer versions of Official MIUI firmware to avoid issues
Click to expand...
Click to collapse
Yes I know, but I don't want to be stuck in 8.7.5 forever because I doubt Xiaomi will go back on this. I like Miui and I don't have any intention of downgrading either, I just want to be able to keep TWRP and root.
[Index] Everything About Anti Roll-back [Whyred]
Have you tried it yet? It works?
.
AL_IRAQI said:
Flashing Miui based ROMs is a bit tricky, you have to make sure they didnt include bootloader inside the Zip, check for firmware-update inside Zip's before flashing or just ask other users
Click to expand...
Click to collapse
One question:
So if i want to update to the newest version of MIUI10 will it be okay if i just replace the files inside firmware-update of the zip with the one from 8.7.5?
Forgive my english if it make you confused:laugh:
2- Switching from CN Beta to Global Beta
this method also need to unlock bootloader right ??
Thank you very much for sharing.
I'm on 8.7.12 and my bootloader is still locked.
am I still able to. unlock bootloader and install twrp?
thanks
AL_IRAQI said:
Flashing AOSP/LOS ROMs should be easy, flash twrp, wipe data & flash ROM
Flashing Miui based ROMs is a bit tricky, you have to make sure they didnt include bootloader inside the Zip, check for firmware-update inside Zip's before flashing or just ask other users
Click to expand...
Click to collapse
What file is the bootloader in rom or firmware zips?
DedeDocil said:
One question:
So if i want to update to the newest version of MIUI10 will it be okay if i just replace the files inside firmware-update of the zip with the one from 8.7.5?
Forgive my english if it make you confused:laugh:
Click to expand...
Click to collapse
Nope, just remove it, and edit the script
azwina said:
2- Switching from CN Beta to Global Beta
this method also need to unlock bootloader right ??
Click to expand...
Click to collapse
Yeah, fastboot ROM is needed
nelsonmenon said:
I'm on 8.7.12 and my bootloader is still locked.
am I still able to. unlock bootloader and install twrp?
thanks
Click to expand...
Click to collapse
Yeah it should be fine, i unlocked on 8.7.12 then flashed twrp & AOSiP
corkiejp said:
What file is the bootloader in rom or firmware zips?
Click to expand...
Click to collapse
More than one file, so just remove the fw folder
jmartinho said:
So, I'm on 8.7.5 right now with twrp and magisk and I'd like to keep updating as new builds come out. Can I just do what I always do? Download 8.7.12 rom, flash with twrp, flash lazyflasher and magisk?
Also would flashing other stuff risk bricking, like camera2 API zip, or YouTube vanced?
Click to expand...
Click to collapse
Mods should be perfectly fine, just make sure not to flash bootloader from twrp
Let me clear a thing... 9.5.19 will be anti roll back enabled... When xiaomi release update next to 9.5.19 whatever it will... Can i roll back from that buil to 9.5.19... I mean to say can i roll back an anti roll back rom to it previous version of anti roll back rom... Waitting for your ans...
AL_IRAQI said:
Mods should be perfectly fine, just make sure not to flash bootloader from twrp
Click to expand...
Click to collapse
Do I still need to remove the firmware-update folder if I just want to update to official MIUI 10 builds (like 8.7.5 to 8.7.12, etc) or is it only other third party MIUI roms?
orion.30 said:
Let me clear a thing... 9.5.19 will be anti roll back enabled... When xiaomi release update next to 9.5.19 whatever it will... Can i roll back from that buil to 9.5.19... I mean to say can i roll back an anti roll back rom to it previous version of anti roll back rom... Waitting for your ans...
Click to expand...
Click to collapse
You can't roll back to older bootloader after flashing 9.5.19.0 bootloader
jmartinho said:
Do I still need to remove the firmware-update folder if I just want to update to official MIUI 10 builds (like 8.7.5 to 8.7.12, etc) or is it only other third party MIUI roms?
Click to expand...
Click to collapse
Yeah for the most part, check my other thread for modded Miui ROMs
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-redmi-note-5-pro-miui-roms-t3816343
I am in miui 8.7.5 global beta now with unlocked bootloader and twrp installed. If I will flash 8.7.12 global beta and then flash lazyflasher zip, will it remove my twrp ??
Team Win Recovery Project 3.6.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904
Reserved
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.
costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!
costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data
Everything working!
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:
Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.
Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?
toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733
ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)
xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?
ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The August update is 11.0.10.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.10.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz
Can you tell how to to update I have only magisk Installed I want to keep magisk.
Aadil Gillani said:
Can you tell how to to update I have only magisk Installed I want to keep magisk.
Click to expand...
Click to collapse
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?
elvinguitar said:
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?
Click to expand...
Click to collapse
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.
a1291762 said:
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.
Click to expand...
Click to collapse
Will I lose my data by flashing the vanilla image?
elvinguitar said:
Will I lose my data by flashing the vanilla image?
Click to expand...
Click to collapse
Flashing a boot image won't lose data unless you use the wrong version and get unlucky.
Flashing any of the partitions that the OTA touches won't lose data.
a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.
RyanCM said:
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.
Click to expand...
Click to collapse
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.
a1291762 said:
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.
Click to expand...
Click to collapse
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
---------- Post added at 05:02 AM ---------- Previous post was at 04:24 AM ----------
RyanCM said:
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
Click to expand...
Click to collapse
I successfully flashed the patched boot.img and installed Magisk Manager and the only options I have are to flash a zip in recovery (I don't have recovery, hindsight) and "select and patch a file". I don't know how to proceed with either of those options.
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.
RyanCM said:
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.
Click to expand...
Click to collapse
That's why the standard way is to BOOT the patched image and use Magisk Manager to install.
If you want to flash partitions, you need to use the correct set (a or b). Fastboot can tell you (getvar current-slot). Flashing both is useless, since the inactive set of partitions is only used when doing OTA (or dual boot, for some brave souls).
If you're coming from phones without a/b partitions you should definitely read about them. Several things are quite different.
Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat
Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat hai mara pass pc nahe ha bootsign.img file link=https://drive.google.com/file/d/1Q172DYs7t7bIo0K_LENCO1OAo6tg0FTz/view?usp=drivesdk and video how to boot sign.img unsing img link=https://youtu.be/ZWphK23KLew
a1291762 said:
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz
Click to expand...
Click to collapse
Offline ... can you please reup?
networxpsc said:
Offline ... can you please reup?
Click to expand...
Click to collapse
It's hosted on Google drive. It just loaded for me (private window to simulate anon user). The preview won't work because it's not that kind of file. Just click download.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. This is a straightforward port of the device tree for flame (Pixel 4) to sunfish (Pixel 4a).
Downloads:
sunfish (Pixel 4a) rom (v2): https://mega.nz/file/zG4UVTQB#ZXLw_qULzC8-an-MEdxdAvUMhmIa5qLI6YG54Feh2z0
410b3f523795d9d1481d183309adb170 lineage_sunfish-qd3a.200805.001-rel-v2.zip
sunfish (Pixel 4a) rom (v1, broken, do not install): https://mega.nz/file/jXRB2a4B#a5Dcf9T6emWAwvAj3oFvofkI0la0zf7vj5KIMn-yQaM
MD5: 86743134c3032a030d35195d44f02e1b lineage_sunfish-qq3a.200805.001.zip
This is not a recovery-installable zip! Please read below for how to install this image
Prerequisites:
Like the TWRP build for this device, this ROM build is only known to be compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
Instructions:
1. Flash the vbmeta.img file in the included zip (fastboot flash vbmeta vbmeta.img)
2. Reboot into fastbootd (fastboot reboot fastboot)
3. Run fastboot update -w lineage_sunfish-qd3a.200805.001-v2.zip
(If you do not have a working fastbootd, extract boot.img from the update zip and flash it from the bootloader first)
Working:
- Camera
- Fingerprint
- Wi-Fi
- Bluetooth
- Sound
- Mobile data (tested with T-Mobile only)
Not tested:
- Google apps (should work fine, but you never know)
Changelog/Source Code:
sunfish device tree: https://github.com/liamwhite/android_device_google_sunfish
sunfish kernel tree: https://github.com/liamwhite/android_kernel_google_sunfish
Credits:
Many thanks to all LineageOS team members and all the contributors out there in the community.
Android version: 10
Kernel version: 4.14.117
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
Edmontonchef said:
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.
Click to expand...
Click to collapse
posıtıve said:
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
Click to expand...
Click to collapse
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
liamwhite said:
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
Click to expand...
Click to collapse
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
TheSayaMan said:
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
Click to expand...
Click to collapse
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
TheSayaMan said:
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
Click to expand...
Click to collapse
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.
liamwhite said:
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.
Click to expand...
Click to collapse
I'm sure it's not broken. Probably a issue with my phone. I'm getting a error in the bootloader about debug policy enabled, not in list. I know that's not normal because my wife has the same phone and hers doesn't say that. And I have no idea what or how to change verity. My bootloader is unlocked.
Same error here, getting corrupt error then it sticks to google logo
nixromancer said:
Same error here, getting corrupt error then it sticks to google logo
Click to expand...
Click to collapse
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
TheSayaMan said:
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
Click to expand...
Click to collapse
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Board: sunfish MP1.0(NA)
Bootloader: s5-0.2-6539975
Baseband: g7150-00018-200701-B-6643937
Secure boot: PRODUCTION
NOS production: yes
liamwhite said:
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Click to expand...
Click to collapse
any idea how to check if verity is enforcing and how to change it. Did a search, can't find anything.
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.
liamwhite said:
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.
Click to expand...
Click to collapse
Your going completly around what I asked. I'm done with this. Moving to another thread.
Stay away from this, it changes your file system to raw and is a complete waste of time.
I rebuilt my entire source tree, reflashed the Pixel system images and reproduced the corrupt device warning. Picking through the changes, it didn't work because I had inadvertently flashed vbmeta.img on my build but not included it in the zip. I've posted an updated version of the zip and provided new instructions for how to flash this, because Lineage's fastboot does not allow flashing the vbmeta partition (you have to first flash it from the bootloader).
I tested again with a clean wipe, reset to Pixel factory image QD4A.200805.003 and this time it worked without a problem. The android-info.txt will now ensure that you are using the right bootloader when flashing, so that issue should go away too.
Cool I'll give it a try tomorrow
TheSayaMan said:
Stay away from this, it changes your file system to raw and is a complete waste of time.
Click to expand...
Click to collapse
What does this mean
nixromancer said:
Cool I'll give it a try tomorrow
What does this mean
Click to expand...
Click to collapse
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.
TheSayaMan said:
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.
Click to expand...
Click to collapse
The fact that I messed up and didn't realize I had to include the vbmeta.img file in the first zip is my fault, and I totally own that. It isn't able to be flashed in Lineage's fastbootd ("file not found", presumably it's missing a devfs node) so I accidentally excluded it from the image I shipped, not realizing it was mandatory.
Yes, I'm new to this forum, but I'm not new to building Lineage and I've done it many times before. I have serial UARTs for my phones. I'm posting this build here because I'm excited to be the first to get stable lineage running on the 4a, with the full list of vendor blobs and such (see my posted device tree), and this is the first time I've ported Lineage to a new board. It took me a week of tiring work bootstrapping the board, getting the first serial output, getting into recovery, and then finally figuring out that the kernel modules were missing before getting a full boot.
I was annoyed that the flashable zip generated by mka bacon doesn't include the required modules, and in my testing applying it never worked (they were always excluded from the vendor parition, even after multiple makefile changes), which is why I decided to make an ad-hoc flash method using a fastboot update zip, which reliably worked. That was the primary source of the error here. I won't make that mistake again.
I know you're frustrated that the first image I provided didn't work, but I have looked into it, reproduced your issue, and fixed it (and it ironically was only missing one 4K file needed to make it work).