Hi, how can i install a treble GSI without bootloop on this phone? THX
Have you unlocked the bootloader? If yes, then just go to the Developer Options & Select DSU Loader. You will be automatically offer the latest Android 12 DP2 with & w/o GMS bundle.
aimsjahan said:
Have you unlocked the bootloader? If yes, then just go to the Developer Options & Select DSU Loader. You will be automatically offer the latest Android 12 DP2 with & w/o GMS bundle.
Click to expand...
Click to collapse
yes but i want something installed, not emulated, also with 144hz enabled, even if i don't have the triggers
ASUS only validated GSI for Zenphone 8 so far. I think we have to wait for our turn.
aimsjahan said:
ASUS only validated GSI for Zenphone 8 so far. I think we have to wait for our turn.
Click to expand...
Click to collapse
No, i dont want A12 GSI, I want something like Lineage and stuff
Therazorsedge said:
No, i dont want A12 GSI, I want something like Lineage and stuff
Click to expand...
Click to collapse
Are you seeking a custom ROM based on LineageOS?
He mean gsi (not the dsu loader and not a custom rom )
aimsjahan said:
Are you seeking a custom ROM based on LineageOS?
Click to expand...
Click to collapse
Yes! i think it's not too complicated to make it boot on dtock recovery from Asus, anyone tried?
you have to erase system and from there, install via fastboot, i only need the command to try a PHH gsi
Rog 5is android 11 devices .
can be the system can only be flashed via fastbootd.
Use the comand
Fastboot -w
Fastboot flash system_a "name from the gsi.img"
Fastboot flash system_b "name from the gsi.img"
But I think that these two must also be flashed so that the gsi boots.
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity flash vbmeta_b vbmeta.img
fastboot --disable-verity flash vbmeta_system_b vbmeta_system.img
Vbmeta and vbmeta sytem use from the stock rom
ChrisFeiveel said:
Rog 5is android 11 devices .
can be the system can only be flashed via fastbootd.
Use the comand
Fastboot -w
Fastboot flash system_a "name from the gsi.img"
Fastboot flash system_b "name from the gsi.img"
But I think that these two must also be flashed so that the gsi boots.
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity flash vbmeta_b vbmeta.img
fastboot --disable-verity flash vbmeta_system_b vbmeta_system.img
Vbmeta and vbmeta sytem use from the stock rom
Click to expand...
Click to collapse
Haha, i will have a bootloop? hahahaha
Anyone can try?
Hello guys my phone is stuck in a bootloop because I tried to install twrp from fastboot.
I unlocked bootloader and started Fastboot.
Then I connected my phone to my mac via USB.
Then I ran this commands:
./fastboot flash recovery recovery.img
./fastboot flash vbmeta vbmeta.img
(The mistake I think I made was that I flashed recovery before vbmeta).
Then I restarted my phone and I could not get into android or fastboot.
Please I need help.
This is the tutorial which I used.
Thanks in advance.
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)
jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
Please do you know how to get the build number of my bricked phone?
mikkyboy said:
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)
Click to expand...
Click to collapse
It's not hard to install TWRP to this device
Now that I have my IMEI numbers restored, I am going to again attempt to flash LineageOS over my stock Android 9.
Let's say I want the latest revision of LineageOS 18, I understand that this is the required system image;
lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img.xz
I also know a vbmeta file is required. This is where I get confused and suspect it's the reason I always get bootloop when flashing.
Do I need a stock vbmeta, a modified vbmeta or a blank vbmeta? I have quite the collection.
Also do I add flags;
--disable-verity
and / or
--disable-verification
Now last, but not least, is my sequence of flashing correct?
fastboot flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot erase userdata
fastboot reboot
I appreciate your time and help.
probably stock vbmeta will work, or get the one in TWRP page for Nokia 2.2
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
What device are you talking about ?
f1tm0t said:
What device are you talking about ?
Click to expand...
Click to collapse
Tab p11 4gig
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
f1tm0t said:
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
Click to expand...
Click to collapse
Threr is no twrp sadly
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
mingkee said:
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
Click to expand...
Click to collapse
I tried it i flashed patched boot.img only in fastbootd still boots me in to the bootloader
LSS4181 said:
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
blocky3321 said:
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
Click to expand...
Click to collapse
Which Magisk version did you use? From what I can tell any official Magisk version should work.
I haven't really tested the recent builds of vvb2060's Alpha or huskydg's Delta... so if you're using these versions I can't really help you much...
Additionally, you need to check which slot you are now, and through fastbootd check which slot actually has system, vendor and such. Normally the super partition only has enough size for one slot. You may have entered a wrong slot that doesn't have usable system.
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
Getting Started: What's Your Device ?
Tab p11 4gig
Device->settings->About : Model & Hardware -> Lenovo ??? (Tb-j606f,TB-J616F...) In your case stiker on box or on back.
mingkee said:
who told you to flash vbmeta.img?
Click to expand...
Click to collapse
???
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
doveman said:
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
Click to expand...
Click to collapse
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
NOSS8 said:
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
Click to expand...
Click to collapse
Yeah, I downloaded the correct ROM (miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip) and extracted the boot.img from that.
Renaming magisk.apk to magisk.zip and flashing it just installs the app doesn't it, it doesn't root the phone as far as I'm aware.
I followed the instructions here, which say that you should only tick the "Patch vbmeta in boot image” option when patching the boot.img in Magisk if the device does NOT have a separate vbmeta partition. The Poco X3 does have a separate vbmeta partition,, so I didn't tick that option.
Installation
The Magic Mask for Android
topjohnwu.github.io
I've tried the "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" command with four different versions of fastboot that I've got, dating from 2016 to 2020, and they all reject the "--disable" switches as an "unknown option".
I tried it without those options, so I flashed the patched boot.img and then did "fastboot flash vbmeta vbmeta.img" but after rebooting Magisk still shows that root is not installed.
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
NOSS8 said:
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
Click to expand...
Click to collapse
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
doveman said:
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
Click to expand...
Click to collapse
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Check:
https://forum.xda-developers.com/t/...n-vendor-dynamic-partition-enable-rw.4238807/
https://forum.xda-developers.com/t/q-h-safety-way-to-unlock-bootloader-flash-recovery-root.4198719/
NOSS8 said:
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
doveman said:
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
Click to expand...
Click to collapse
What happens if you try to root from the Magisk app?
NOSS8 said:
What happens if you try to root from the Magisk app?
Click to expand...
Click to collapse
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
doveman said:
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
Click to expand...
Click to collapse
No functional TWRP for this device.?
NOSS8 said:
No functional TWRP for this device.?
Click to expand...
Click to collapse
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
doveman said:
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
Click to expand...
Click to collapse
Strange case as strange as the number of threads has this subject for this device.
NOSS8 said:
Strange case as strange as the number of threads has this subject for this device.
Click to expand...
Click to collapse
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
doveman said:
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
Click to expand...
Click to collapse
This phone is rootable, surely an oversight or an error somewhere.
NOSS8 said:
This phone is rootable, surely an oversight or an error somewhere.
Click to expand...
Click to collapse
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
doveman said:
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
Click to expand...
Click to collapse
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
NOSS8 said:
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
Click to expand...
Click to collapse
I've already got TWRP recovery flashed. I guess I'll have to flash the ROM again and start from scratch.
I tried flashing super.img but that didn't fix it. In the end, going into ADB Sideload mode in TWRP and flashing the 2.7GB recovery version of the ROM with
"adb sideload miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" fixed it without losing any data.
I still can't root it though. I've tried the "install Magisk (root)" option in TWRP and renaming magisk.apk to magisk.zip and installing that in TWRP, but it still shows "Installed N/A" in Magisk and Root Verifier says "Root permission not granted or Superuser App Missing" but then it says "Superuser App: 25.25:MAGISKSU", so it's the root permission that isn't granted.
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
NOSS8 said:
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
Click to expand...
Click to collapse
I thought so but I've reflashed the patched boot.img and done
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
and
"fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img"
in case it needed that too, but Magisk still shiows "Installed N/A"
I tried installed SR5-SuperSU-2.82 zip from TWRP to see if that would get it rooted,, but it couldn't even install that, it just gave some error.