Related
Official A16 ozip was released yesterday:
realme.com/support/software-update
My working flow is as follows:
1. Extract boot.img and vbmeta.img from the converted zip
2. Use Magisk to patch the boot.img , we got magisk_patched.img
3. fastboot flash boot magisk_patched.img and reboot. However, in this method it says
the current image (boot/recovery) have benn destroyed and can not boot
4. I asked others, they said I have to flash vbmeta.img too. So I used ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. This time, when booting, it just turns black (Under normal circantance, it will show a yellow REALME logo, however not appearing in this method)
_____________________________________
What should I do? Does this vbmeta.img in the official zip work? Thanks for your help!
cocoon_zz said:
Official A16 ozip was released yesterday:
realme.com/support/software-update
My working flow is as follows:
1. Extract boot.img and vbmeta.img from the converted zip
2. Use Magisk to patch the boot.img , we got magisk_patched.img
3. fastboot flash boot magisk_patched.img and reboot. However, in this method it says
the current image (boot/recovery) have benn destroyed and can not boot
4. I asked others, they said I have to flash vbmeta.img too. So I used ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. This time, when booting, it just turns black (Under normal circantance, it will show a yellow REALME logo, however not appearing in this method)
_____________________________________
What should I do? Does this vbmeta.img in the official zip work? Thanks for your help!
Click to expand...
Click to collapse
Upload a video
Hi, I have twrp on the rmx1901cn (Chinese version), can I use the converted zip to image my phone back to its original state using twrp? I don't mind getting back to Chinese stock ROM anymore.
Also, I only have access to TWRP and boot loader now.
Please provide some more hints. I'm stuck at the same spot.
LovemyRealme said:
Hi, I have twrp on the rmx1901cn (Chinese version), can I use the converted zip to image my phone back to its original state using twrp? I don't mind getting back to Chinese stock ROM anymore.
Also, I only have access to TWRP and boot loader now.
Click to expand...
Click to collapse
I've got a little further. I converted the ozip to zip. Extracted the boot.img from the converted file. Flashed boot.img to the phone. and flashed vbmeta.img using the same commands as cocoon_zz.
I'm getting the same black screen as cocoon_zz. I haven't use Magisk but the stock rom is okay by me. Can you guys please give some hints on how to get pass the black screen after the realme logo?
So I have tried to flash a GSI on my Nord N100 and while it boots the phone gets stuck at the boot animation for a good long while. The steps I have taken to flash the GSI were to oem unlock the phone, boot into the bootloader,fastboot reboot fastboot, flash the gsi system image,flash the stock vbmeta image, flash the stock vbmeta system image I also have and then finally rebooting the device after using the fastboot -w command. Did I maybe do something wrong in the steps I took or use a wrong file?
Hi, I think you have to disable AVB, not try to use vbmeta from stock
Here are instructions from Oneplus Nord, you can try again with those vbmeta files
How to: Run an GSI on NORD
To run an GSI on your Nord: Unlock bootloader Toogle oem unlock in Developer options Reboot to fastboot (turn of phone, press volume down and start) Run -fastboot oem unlock Install GSI (check...
forum.xda-developers.com
Wouldn’t using vbmeta files made for a different phone mess up my phone?
svaethier said:
Wouldn’t using vbmeta files made for a different phone mess up my phone?
Click to expand...
Click to collapse
I'd guess it's an empty image created as described here: https://wiki.postmarketos.org/wiki/Android_Verified_Boot_(AVB) section disable verrified boot. And an empty image should be universal I would think
well i tried using that vbmeta file and the phone still gets stuck at the boot animation so maybe it's not the vbmeta file that's not working
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro.
This message was removed on OOS 12 which was one great thing by OP other than the other broken parts.
So this guide is for OOS 13 not 12 as the message was removed on 12.
But OnePlus brought the message back on OOS 13.
IMPORTANT:
*I am not responsible for bricked devices, damage to your device*
I am here to post my method for anyone who is interested.
The methods have been tested
Prerequisities:
You need a unlocked bootloader
YOU NEED TO HAVE THE STOCK RECOVERY INSTALLED
If you're on a custom ROM that'll be the ROM recovery
This is XDA thread and abl.img is only for the OnePlus 8 Pro, but this method has worked for 8 series devices.
You need to be on OOS 13 and have your bootloader unlocked.
The abl.img doesn't rely on the region so it can be used on any OP8 Pro
The abl.img can be extracted using payload dumper, but download the full zip version.
I have added abl.img from OOS 13 F.10 as this is the newest abl.img that has the message removed and is from @bowow
It is recommended to backup your data before modifying anything on your system
Follow one method and stick to that method
Each method is different where one is for Stock OOS 13 and the other is for OOS 13 based Custom ROMs
Method:
Download the abl.img
Copy and paste the abl.img to platform-tools
If u don't have platform-tools, download the .zip file from download links and extract it
For Stock OOS 13
This method was tested and is from @MeHigh.G
This is for on Stock OOS 13 users
Reboot to bootloader
Type " fastboot devices " to check if your device is connected
Type " fastboot reboot fastboot "
Once booted into Fastbootd Mode, type " fastboot devices " to check if your device is connected
Then type " fastboot flash --slot=all abl abl_filename.img "
Now reboot device and done
For OOS 13 based Custom ROMs
This method was tested by me and it does work
This is for OOS 13 based ROM users
Reboot to recovery
Enter advanced
Enter fastboot
The recovery should now show fastbootd
Type " fastboot devices " to check if your device is connected
Type " fastboot flash --slot=all abl abl_filename.img
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
MSMDownloadTool for OP8Pro Here
Bowow's OnePlus Firmware Updates abl section Here
OrangeFox Recovery for OP8+OP8 Pro ext4 erofs
OFox Install instructions Here
OrangeFox Community Telegram
Credits:
@HELLBOY017 For the method and using abl.img to remove the bootloader unlocked message
@MeHigh.G For his method on flashing abl.img on stock OOS 13
@bowow For this F.10 abl.img for OP8 and 8 Pro
reserved
Updates
21/11/22 - Released the XDA thread as a guide to remove the ugly "Your device has been unlocked" message for the OP8 Pro
Not sure if this method does work, but I have contacted ROM developers and they say this is the way...
I'm currently not on OOS 13 based ROM, so I can't try and hopefully this does work
21/12/22 - It has been a month and after checking with devs + testers the method does work!
I have tested the method myself
I have updated the method as there's new steps you need like flashing abl.img in both slots
But the method does work on OOS 13 based ROMS! The message can be removed!
22/12/22 - I have found the method that works on Stock OOS 13 thanks to @MeHigh.G
Stock OOS 13 users should be able to remove the bootloader unlocked message
Added new OOS 13 F.10 abl.img file and removed OOS 12 C36 abl.img due to F.10 being newer to ensure users have a newer bootloader
Credited Bowow for giving the F.10 abl.img file for OP8/8 Pro
5/1/23 - Updated methods to flash abl.img in both slots easily instead of flashing abl.img in one slot
Changed "fastboot flash abl abl.img" to " fastboot flash --slot=all abl abl_filename.img " which will flash abl.img in both slots.
For custom ROM method, you will no longer need to reboot and switch slots with the new command
Nice!
Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
gregpilot said:
Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
Click to expand...
Click to collapse
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
ShadoV90 said:
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
Click to expand...
Click to collapse
That's for the OP9 Pro not the OP8 Pro...
I only learned about this from the dev @HELLBOY017 and it worked for him. He never stated u needed a data wipe.
So I did check that it was working otherwise I would never post something that wouldn't work and wasn't tested.
And I did say.... *I am not responsible for bricked devices, damage to your device* I am here to post my method for anyone who is interested.
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
We'll see how it goes as this is new for 8 Pro users and hopefully it does work
Thanks for the reminder of the missing info to include
Extreme_Ninja2099 said:
That's for the OP9 Pro not 8 Pro...
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
Click to expand...
Click to collapse
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
ShadoV90 said:
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
Click to expand...
Click to collapse
Never considered it as an attack, just posting to clarify where I got this info and everything from.
I only found out about this yesterday from Hellboy017 and it worked for him.
I would recommend this only for users on OOS 13 just to be safe
If something does go wrong, follow the link by @ShadoV90
Do a factory reset or use MSMDownload Tool
thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk
Neil_Armstrong_ said:
thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk
Click to expand...
Click to collapse
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
the flashing unlock_critical output is the fastboot help, i guess it's not working
I will try again saturday on Linux to see if it helps
ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.
MeHigh.G said:
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.
Click to expand...
Click to collapse
Nice feedback, can you share what custom recovery you use on OOS 13 ?
so this work or not?
Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
There's no custom recovery currently for OOS 13... Only for custom ROMs
Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
I use oFox or the one provided with Flamingo OS or Pixel Blaster
so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?
STALKER18 said:
so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?
Click to expand...
Click to collapse
I've already extracted it for the 8 pro... Up to u
For step 4 it's fastboot flash abl abl.img
i'm unable to unlock bootloader says command not supported in default implementation.
IN2021 One plus 8 pro.
Hi all,
I would like to flash some GSI roms into our phone ( OP9P ) but several guides I followed doesn't worked....
Is anyone knows a reliable guide to follow ?
Mnay thanks
Jack Droid said:
Hi all,
I would like to flash some GSI roms into our phone ( OP9P ) but several guides I followed doesn't worked....
Is anyone knows a reliable guide to follow ?
Mnay thanks
Click to expand...
Click to collapse
You know that in an gsi not all will work ?
And when you flash the gsi to system Partition have you disabeld vbmeta_system ?
Yes and no.
BTW, I would like to try.
Can you help me with a reliable guide ?
Use this
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
Hmmmm.....
I believe already tried this guide but I'm not really sure.....
In any case, I'll carefully follow all the steps as it seems interesting....Thanks !
One question :
when adivsed to put "fastboot reboot fastboot", it means that you need to be on fastbootD environment and not bootloader environment ( with green written START on top, just to understand ), correct ?
Jack Droid said:
Hmmmm.....
I believe already tried this guide but I'm not really sure.....
In any case, I'll carefully follow all the steps as it seems interesting....Thanks !
One question :
when adivsed to put "fastboot reboot fastboot", it means that you need to be on fastbootD environment and not bootloader environment ( with green written START on top, just to understand ), correct ?
Click to expand...
Click to collapse
Yes fastboot reboot fastboot for reboot to fastbootd
Ok, thanks.
I try and I'll let you know....!
Hi ChrisFeiveel84,
just a fast question :
I have downloaded a GSI rom that is a rar file.
Unpacking it, I obtains a GSI image file but in order to proceed further, I have to put payload.bin into Fastboot Enhance but payload.bin is fused into the image file....
Normally, with all other custom roms, it is enough to drag the relevant zip file on the payload.dumper and you can obtain all inside img files......
How can I extract GSI iso file in order to have payload.bin file ???
Many thanks
Jack Droid said:
Hi ChrisFeiveel84,
just a fast question :
I have downloaded a GSI rom that is a rar file.
Unpacking it, I obtains a GSI image file but in order to proceed further, I have to put payload.bin into Fastboot Enhance but payload.bin is fused into the image file....
Normally, with all other custom roms, it is enough to drag the relevant zip file on the payload.dumper and you can obtain all inside img files......
How can I extract GSI iso file in order to have payload.bin file ???
Many thanks
Click to expand...
Click to collapse
a gsi have no payload bin
than a gsi is only a system image
(gsi gerneric system image and this is not a rom)
and the gsi you flash (the image ) to system partition (end the rest you use from your rom what you have on your phone )
Here is reported :
Gathering your assetsOn your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Now go to payload dumper and open your version zip : when you try to put zip file, it advise you that you need to put payload.....
Jack Droid said:
Here is reported :
Gathering your assetsOn your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Now go to payload dumper and open your version zip : when you try to put zip file, it advise you that you need to put payload.....
Click to expand...
Click to collapse
you get the data from the full rom packet (the rom you currently have on your cellphone) you have to download it (or make a backup of the partitions with the msm tool like vbmeta vbmeta_system)
mmmmmmm......no
Simply, I tried with Win10 i.o. Win7 and Fastboot Enhance is now checking for payload AND zip file so that I can proceed with GSI ZIP extraction and so on...
Anyway, thanks for your kind replies !
you only need the vbmeta and vbmeta_system image and the gsi
and flash this
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase system
fastboot flash system Gsi.img
So yesterday I acquired a TMobile Revvl V 4G (model TMRVL4G, Newcastle I think?) and started playing with it to gain root. Well after going into developer options and unlocking the bootloader I got a dm verity corruption error and was in a boot loop! After trying `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img` to no avail I held both volume buttons and plugged into mtkclient. I used that to erase all vbmeta, vbmeta_vendor and I think another vbmeta partition. After that I was able to flash vbmeta from fastboot and boot the phone though I get an orange state warning for the unlocked bootloader. So now I'm trying to use mtkclient to pull boot.img since I can't find firmware online for this phone. I see the following partitions: boot_a, boot_b, vendor_boot, and possibly another boot partition, I'll have to check when I can look. My question is does anyone have any idea which of these I need to patch with magisk? I'm going to guess boot_a/b? Any tips or advice is much appreciated. Thanks in advance!
P.S. - Sorry for posting this in this forum but it's pretty close to the phone I have so I figure it would fly, if not can the mods put me in the right spot? Thanks!
Edit: I got root yesterday after patching and flashing boot_a and boot_b. Since there is not system partition I bricked my device trying to flash the super partition to install a gsi for lineageOS. I recovered but would love some advice from anyone who has been down this road.