My device (Redmi 8) is Treble supported & A-only Arm64 system.
Can I flash any A-only ARM64 GSI rom ?
I tried couple of A-only Arm64 GSI's, those flash successfully but my device start and Redmi logo appears and its restart again & again.
+1
ahmd gom3aa said:
+1
Click to expand...
Click to collapse
??
Tauseef786 said:
My device (Redmi 8) is Treble supported & A-only Arm64 system.
Can I flash any A-only ARM64 GSI rom ?
I tried couple of A-only Arm64 GSI's, those flash successfully but my device start and Redmi logo appears and its restart again & again.
Click to expand...
Click to collapse
Does the device have encryption disabled?
Do you use patch files to start / force the start?
Do you have the boot or recovery in permissive mode?
@Tauseef786
Did make a wipe of the userdata after flashing the GSI?
Did you try to flash the vbmeta linked from phh in his quack thread before flashing the GSI?
dhacke said:
@Tauseef786
Did make a wipe of the userdata after flashing the GSI?
Did you try to flash the vbmeta linked from phh in his quack thread before flashing the GSI?
Click to expand...
Click to collapse
Excuse me, I went to phh thread to see where is this vbmeta but I didn't find it...where is it & what does it do?
Magdy Doze said:
Excuse me, I went to phh thread to see where is this vbmeta but I didn't find it...where is it & what does it do?
Click to expand...
Click to collapse
That's the link to the vbmeta which phh suggests:
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Some devices need it to allow a GSI boot.
dhacke said:
That's the link to the vbmeta which phh suggests:
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Some devices need it to allow a GSI boot.
Click to expand...
Click to collapse
so its flashed before the system image right?
& the order would be (fastboot flash system vbmeta.img)?
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
Tauseef786 said:
??
Click to expand...
Click to collapse
he meant to say (same) as he has the same problem...it came from the like button on social media when it shows the (+1) to endorse a certain comment/post
Magdy Doze said:
so its flashed before the system image right?
& the order would be (fastboot flash system vbmeta.img)?
Click to expand...
Click to collapse
Yes first vbmeta and then system.
But the command you wrote is wrong. You need to execute one command for the vbmeta and one for the system.
So the commands would be:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot flash system 'name of the system img'
If you have a device which comes with Android 10 out of the box you can only flash the system.img in fastbootd mode probably. This means you need one extra command between the ones i wrote. In this case it would show as follows:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot reboot fastboot
3. fastboot flash system 'name of the system img'
dhacke said:
Yes first vbmeta and then system.
But the command you wrote is wrong. You need to execute one command for the vbmeta and one for the system.
So the commands would be:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot flash system 'name of the system img'
If you have a device which comes with Android 10 out of the box you can only flash the system.img in fastbootd mode probably. This means you need one extra command between the ones i wrote. In this case it would show as follows:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot reboot fastboot
3. fastboot flash system 'name of the system img'
Click to expand...
Click to collapse
Got it now..thanks a lot
Tauseef786 said:
My device (Redmi 8) is Treble supported & A-only Arm64 system.
Can I flash any A-only ARM64 GSI rom ?
I tried couple of A-only Arm64 GSI's, those flash successfully but my device start and Redmi logo appears and its restart again & again.
Click to expand...
Click to collapse
I have a Redmi 8 and i remember flashing an A-only rom resulting in bootloop too. I also had problems with A/B roms but i fixed it by formatting (not just wiping) /data, after you do that it will reboot once in the Redmi logo then all the next boots will work. Currently running A/B Lineage 17 while before i was running Pixel Experience 10 A/B just fine. I know technically it's an A/B rom but it works.
Please try formatting /data first with the A-Only image. You can do so by going in TWRP>Wipe>Format Data. Let me know if this worked. If it didn't, flash an A/B image then format data with the instructions above. I know that the Redmi 8 technically is A-Only, but this worked fine for me soo feel free to try. Remember to format data for A/B images too, or they will bootloop!
EDIT:
Why should I use GSI for A/B devices to some A-only devices? : On Android 9, Google changed the requirements and all devices shipped with Android 9 must use "system-as-root". Before this change, only A/B devices were system-as-root and GSI name was separated by A-only and A/B. For this historical reasons, you have to use GSI for A/B on the devices shipped with Android 9+. (source: https://github.com/phhusson/treble_experimentations/wiki)
Click to expand...
Click to collapse
Redmi 8 comes with Android 9, thus it needs A/B GSIs as the above and the device list on the article says.
While the issue for the OP was solved, I still wanted to repeat the question: Can I flash any A/B/AB Treble ROM (according to my device) onto my phone? So basically all Treble ROMs will be compatible to my treble-enabled device?
I already understood the general principle of Treble, I just am thankful for a last bit of comfirmation about this.
Thanks in advance.
BenjyTec said:
While the issue for the OP was solved, I still wanted to repeat the question: Can I flash any A/B/AB Treble ROM (according to my device) onto my phone? So basically all Treble ROMs will be compatible to my treble-enabled device?
I already understood the general principle of Treble, I just am thankful for a last bit of comfirmation about this.
Thanks in advance.
Click to expand...
Click to collapse
B-Only doesn't exist
But as long as it has a fitting variant (in this case AOnly Arm64)
Everything should be fine
0
Related
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (WARNING : According to 5m4r7ph0n36uru, you can't flash vbmeta via fastboot if your device isn't S-OFF, you have to use TWRP, but I don't know how, so ask someone who knows! I will update my tutorial once I see instructions.)
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello, which GSI did you tried from the list? If you tried more then one, which is the one that runs better?
Thank you
Hi!
I have tried AOSP 10.0 v206 system-quack-arm64-ab-gapps.img. v208 is out now.
I still have to try others.
Let us know if you find one working better than others!
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
mientus25 said:
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
Click to expand...
Click to collapse
Hi mientus25! I'm sorry if you bricked your smartphone trying to flash it. I think the --disable-verity option not working was a matter of platform tools (adb) version.
My htc have actually hard brick. I will try to send it to the service(warranty). Will tell you what comes of it.
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
xreeman said:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
Click to expand...
Click to collapse
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
5m4r7ph0n36uru said:
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
Click to expand...
Click to collapse
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
GaetanoS.89 said:
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
Click to expand...
Click to collapse
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
5m4r7ph0n36uru said:
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
Click to expand...
Click to collapse
All right, would you please write a message over with all the steps here? Thank you
GaetanoS.89 said:
All right, would you please write a message over with all the steps here? Thank you
Click to expand...
Click to collapse
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Code:
adb reboot bootloader
Delete the system and data partition by
Code:
fastboot erase data
and
Code:
fastboot erase system
Flash the nonverity vbmeta image via
Code:
fastboot flash vbmeta nameofvbmeta.img
(the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via
Code:
fastboot flasch system nameofgsi.img
(the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
https://www.xda-developers.com/goog...al&utm_source=twitter.com&utm_campaign=buffer
Wiil this work with the U12+???
It may work for GSIs with a fixed verity status. Thus it doesn't work for some Android 10 GSIs without flashing a noverity vbmeta as. Thus I decided long ago, to never recommend such tools, and not to help people who used one, as those using such tools most of the time didn't even care learn the basics of adb and fastboot. I can't remember anyone, who used a tool, who's ever been fully capable to identify potential problems and errors, let alone how to solve them. And the latter is the baseline to start modding a device.
Sent from my Pixel 4 XL using XDA Labs
5m4r7ph0n36uru said:
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Delete the system and data partition by and
Flash the nonverity vbmeta image via (the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via (the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
Click to expand...
Click to collapse
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello I am trying to follow all the steps on the guode, but when I have to flash the vbmeta file from Bootloader Mode I am getting this:
C:\Users\User\Desktop\ADB2>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Not allowed on PRODUCTION device')
fastboot: error: Command failed
If I try to install the vbmeta from Download Mode I am getting this error
GaetanoS.89 said:
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Click to expand...
Click to collapse
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
5m4r7ph0n36uru said:
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
Click to expand...
Click to collapse
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
GaetanoS.89 said:
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
Click to expand...
Click to collapse
Which software version are you running!?
Sent from my Pixel 4 XL using XDA Labs
5m4r7ph0n36uru said:
Which software version are you running!?
Click to expand...
Click to collapse
I was running Android 9 stock. After a few trials I have been able to install and boot the Pixel Experience and the permessiver and everything seems to work without flashing the vbmeta file
Moderator Information
This project is not under active development, take precautions when you are installing it.
Click to expand...
Click to collapse
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 Pro in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8 Pro
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Can you please do this for OnePlus 8 (non pro)
This is awesome, my OP8P is not even here yet and development is moving forward nicely.
Tx mauronofrio, donation sent!
---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------
As I understand this, this is for the European version so far and not the US version, correct?
Poloasis said:
This is awesome, my OP8P is not even here yet and development is moving forward nicely.
Tx mauronofrio, donation sent!
---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------
As I understand this, this is for the European version so far and not the US version, correct?
Click to expand...
Click to collapse
desiresiscool said:
Can you please do this for OnePlus 8 (non pro)
Click to expand...
Click to collapse
For now yes, I need of the others normal roms to make the fastboot roms and for sure this will come also for OnePlus 8
Hey! Nice to see you again. I just got my 8 pro today. Nice work!! Is there a telegram group I can join to help with development?
mauronofrio said:
For now yes, I need of the others normal roms to make the fastboot roms and for sure this will come also for OnePlus 8
Click to expand...
Click to collapse
@mauronofrio , you might want to head to my mirrors thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233 https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315/
Some_Random_Username said:
@mauronofrio , you might want to head to my mirrors thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233 https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315/
Click to expand...
Click to collapse
Thanks, i'm downloading the others roms just now
This might be a stupid question, but will twrp recovery ever be available to flash custom ROMs down the road, or is it just not possible on the OP8Pro?
Gordietm said:
This might be a stupid question, but will twrp recovery ever be available to flash custom ROMs down the road, or is it just not possible on the OP8Pro?
Click to expand...
Click to collapse
I think that will be needed a bit of time
If I substituted a magisk patched boot.img in the fastboot rom and flashed it via flash-all command, will it flash the stock rom and root it at the same time?
Sent from my OnePlus 8 Pro using XDA Labs
Where is this flash all.bat people are using?
I got it. It's in the file you download.
So I'm really screwed here. I flashed a substartum theme that caused my phone to boot into fastboot mode. I cant delete the theme witha an adb command because its not recognizing my device.
Now I fastbooted the stock rom with flash all.bat and Im getting failed error commands. I just realized that Ive already updated to 10.0.55 and its not working. What do I do?
Can you flash it with the MSM tool?
Gordietm said:
So I'm really screwed here. I flashed a substartum theme that caused my phone to boot into fastboot mode. I cant delete the theme witha an adb command because its not recognizing my device.
Now I fastbooted the stock rom with flash all.bat and Im getting failed error commands. I just realized that Ive already updated to 10.0.55 and its not working. What do I do?
Click to expand...
Click to collapse
Try
fastboot -w
On fastboot
---------- Post added at 01:38 PM ---------- Previous post was at 01:32 PM ----------
cultofluna said:
Try
fastboot -w
On fastboot
Click to expand...
Click to collapse
Also, on flash all bat
Ignore, invalid sparse error....
Guitarfreak26 said:
Can you flash it with the MSM tool?
Click to expand...
Click to collapse
Have you fixed the FP issue?.
cultofluna said:
Try
fastboot -w
On fastboot
---------- Post added at 01:38 PM ---------- Previous post was at 01:32 PM ----------
Also, on flash all bat
Ignore, invalid sparse error....
Click to expand...
Click to collapse
Hey thanks. Everything finally worked and back to normal. I'm staying away from certain substratum themes from now on until we have twrp. ?
Sent from my OnePlus 8 Pro using XDA Labs
Gordietm said:
Hey thanks. Everything finally worked and back to normal. I'm staying away from certain substratum themes from now on until we have twrp. ?
Click to expand...
Click to collapse
TWRP probably not coming on dynamic partitions
( Oneplus 7Tpro , Pixel4/ 4xl still don't have a fully working twrp)
cultofluna said:
TWRP probably not coming on dynamic partitions
( Oneplus 7Tpro , Pixel4/ 4xl still don't have a fully working twrp)
Click to expand...
Click to collapse
Supposedly there are some working on 7's, and a private 8 one in China that can't be put on XDA.
cultofluna said:
TWRP probably not coming on dynamic partitions
( Oneplus 7Tpro , Pixel4/ 4xl still don't have a fully working twrp)
Click to expand...
Click to collapse
Wrong.
Its not ready yet but they posted update on Twitter this month that they made a lot of progress on Pixel 4 now it can decrypt data and install. So it will be coming to Android 10 only devices once they made changes.
Nekromantik said:
Wrong.
Its not ready yet but they posted update on Twitter this month that they made a lot of progress on Pixel 4 now it can decrypt data and install. So it will be coming to Android 10 only devices once they made changes.
Click to expand...
Click to collapse
Decrypt data only without pin/password/pattern and rom, magisk, gapps flashing wasn't tested yet
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
niaboc79 said:
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
Click to expand...
Click to collapse
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Miustone said:
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Click to expand...
Click to collapse
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations ?
niaboc79 said:
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations
Click to expand...
Click to collapse
Nice to know! Fingerprints are the worst on Xperia 1 and 5. Hope it will be better on the Mark 2...
Just made an Overlay over Night for GSIs, after experimenting around with them again. Finally got some essential Features working like AoD. Still missing is VoLTE and wifi calling which is a common Android 10 GSI bug i think. Double Touch to work does also not work on My Xperia 5 (Dunno why).
Thread; https://forum.xda-developers.com/xp...eriment-mars-vendor-overlay-gsi-roms-t4128449
which AOSP Vendor Package from Sony can be use on xperia 1 ii
I was wondering, is this device Xperia 1ii is able to recieved GSI 13?
I have the previous model Xperia 1 running GSI 13 really well, and was wondering if this device is similar to do the same?
Kind of a dumb question, because I would assume yes?... But would like to know just the same, as I saw a bargain price for a new Xperia 1ii, and hoping it to be similar.
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
I imagine this will be ported to our device once the P5 version is working properly. It's still in "testing" according to @bigbiff. I'd just be patient for that since he's been working on it since I had my Pixel 3 XL. Lots of hurdles to overcome unfortunately.
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
Yes, but it is for Android 10 (Q): TWRP 3.5.0_10-0 -
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
-Try a GSI 10(Q) in activeslot=a
-reboot-bootloader
-./fastboot --set-active=b
-reboot-bootloader
-./fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
-reboot-bootloader
-./fastboot -w boot xxx.img
v.garne said:
-Try a GSI 10(Q) in activeslot=a
-reboot-bootloader
-./fastboot --set-active=b
-reboot-bootloader
-./fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
-reboot-bootloader
-./fastboot -w boot xxx.img
Click to expand...
Click to collapse
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal android runs on slot b, don't know if that makes a difference for these specific steps.
rspkt said:
I imagine this will be ported to our device once the P5 version is working properly. It's still in "testing" according to @bigbiff. I'd just be patient for that since he's been working on it since I had my Pixel 3 XL. Lots of hurdles to overcome unfortunately.
Click to expand...
Click to collapse
Sounds like it's already able to make backups on the P5, which is the main function I'm interested in, even if can't decrypt /system yet.
I'd like to help him as much as possible. I posted on his thread and he said he needs dmesg to see what's not working. Any idea how to provide that?
mistermojorizin said:
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal android runs on slot b, don't know if that makes a difference for these specific steps.
Click to expand...
Click to collapse
mistermojorizin said:
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list runs on slot b, don't know if that makes a difference for these specific steps.
Click to expand...
Click to collapse
Generic system image,
mistermojorizin said:
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal android runs on slot b, don't know if that makes a difference for these specific steps.
Click to expand...
Click to collapse
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
I was able to get touchscreen working in TWRP by flashing it to the boot partition, then booting the proton kernel installer (which flashes the proton kernel to the boot partition). no ADB though. Can't get the dev a dmesg/catlog, unless someone knows how to get one without ADB from inside TWRP.
v.garne said:
-Try a GSI 10(Q) in activeslot=a
-reboot-bootloader
-./fastboot --set-active=b
-reboot-bootloader
-./fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
-reboot-bootloader
-./fastboot -w boot xxx.img
Click to expand...
Click to collapse
Is there a GSI 10(Q) available for redfin or bramble? I can't find any.
mistermojorizin said:
I was able to get touchscreen working in TWRP by flashing it to the boot partition, then booting the proton kernel installer (which flashes the proton kernel to the boot partition). no ADB though. Can't get the dev a dmesg/catlog, unless someone knows how to get one without ADB from inside TWRP.
Click to expand...
Click to collapse
I could not mount /data or /storage so I couldn't make a backup.
Master Cylinder said:
Is there a GSI 10(Q) available for redfin or bramble? I can't find any.
I could not mount /data or /storage so I couldn't make a backup.
Click to expand...
Click to collapse
yes, it was mentioned that it doesn't decrypt yet.
We got TWRP now!
[RECOVERY][UNOFFICIAL] - (1/16/22) TeamWin Recovery Project [BRAMBLE]
Essentially copy/paste from the official TWRP for redfin thread, except I've made my own unofficial build for the Pixel 4a5G that in my own testing appears to be on feature parity with the official build for the Pixel 5! There are reports of the...
forum.xda-developers.com
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.