Database Info

[DEV] OnePlus 6, no luck with Treble, seeking help

So me and Phhusson spent a good part of yesterday and today trying to get the Treble GSI to boot on the OnePlus 6 but no luck.
Only got the device recognised as Qualcomm HS-USB Diagnostics 900E (COM3), no ADB so no logcat
Which means no /system boot at all, black screen after the bootloader unlocked warning.
there are some dm-verity/fec errors, but using a modified vbmeta image did not change anything
If any other dev out here has any ideas you are welcome, me and phh are out of ideas.
PS, find here stock vendor, system and boot images, plus the dump of /sys/fs/pstore
https://drive.google.com/open?id=1J_sROd5AYVmvVTOGfMBuazoVWx4bSkTe

Update 1:
The black screen and no boot issue seems to be much more widespread and it's not specific to the Treble GSI, I have seen a lot of users experiencing the same exact behaviour when flashing other images too, even some stock images from OnePlus.
No clue yet about the exact cause, waiting for more devs to join in on this.

I assume you guys have contacted 1+?
Fingers crossed they could help

Same problem here.. No idea why OP6 boots into EDL mode when You try to boot Phh GSI. I noticed that sometimes when I boot into TWRP, it freezes and boots into EDL too.
Edit: And just like Exelios said, even with stock OP6 system.img it refuses to boot and boots into EDL instead.

ProtoDeVNan0 said:
Same problem here.. No idea why OP6 boots into EDL mode when You try to boot Phh GSI. I noticed that sometimes when I boot into TWRP, it freezes and boots into EDL too.
Edit: And just like Exelios said, even with stock OP6 system.img it refuses to boot and boots into EDL instead.
Click to expand...
Click to collapse
Yeah, you might have to re-flash the entire device with fastboot -w flashall, only way I got back to stock.
https://forum.xda-developers.com/showpost.php?p=76620386&postcount=60

Interesting...who knows what kind of weird stuff OnePlus did when implementing Treble. Did you try Updating to OnePlus Android P beta and going from there?

Exelios said:
Yeah, you might have to re-flash the entire device with fastboot -w flashall, only way I got back to stock.
https://forum.xda-developers.com/showpost.php?p=76620386&postcount=60
Click to expand...
Click to collapse
Managed to get it to boot after I used those commands (Thanks for telling me though )
fastboot flash boot_a
fastboot flash boot_b
fastboot flash system_a
fastboot flash system_b
fastboot flash vendor
fastboot -w flash vbmeta
And I used latest OOS zip from OP website. Just had to extract payload etc.
My guess is that we either need a different vbmeta or ramdisk is not compatible with our OP6. I never worked on A/B so it's all new to me. But I will do some "reverse engineering" soon. I'm surprised to see OP mess up Treble though, they are very developer friendly so why did they mess it up?

ProtoDeVNan0 said:
Managed to get it to boot after I used those commands (Thanks for telling me though )
fastboot flash boot_a
fastboot flash boot_b
fastboot flash system_a
fastboot flash system_b
fastboot flash vendor
fastboot -w flash vbmeta
And I used latest OOS zip from OP website. Just had to extract payload etc.
My guess is that we either need a different vbmeta or ramdisk is not compatible with our OP6. I never worked on A/B so it's all new to me. But I will do some "reverse engineering" soon. I'm surprised to see OP mess up Treble though, they are very developer friendly so why did they mess it up?
Click to expand...
Click to collapse
What I suspect is that the software is just unfinished, not messed up.
Here is the VBMETA.img that made it possible to boot on the pixel 2 xl, but causes the OP6 not to boot at all, not even stock system.
https://drive.google.com/open?id=1ifnXCIdkqKnk_a1HII9RqQd5CVFWz1xR

Bought and shipped a OP6 to Phhusson, hopefully he manages to figure out something with the device in his hands.
Are there really no other devs interested in getting this working? Just me and Phhusson?

Little update
Different OP6 devices are failing to boot differently, some go to EDL and some in PDL, when flashed the same files in the same way.
(Emergency Download Mode
Primary Download Mode)
Sent from my OnePlus 6 using XDA Labs

Hey buddy,
Not sure if you have seen this thread:
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-flash-treble-roms-oneplus-6-t3797858
Is this what you're talking about?
Regards,
Ravi
Sent from my OnePlus6 using XDA Labs

See, I really wish I knew how to get started learning about Android Development like this, I would love to help lol.
I've tried dabbling in Custom ROMs but I don't know enough Java to add useful features lol, and even understanding the build system is kind of hard lol.
Like where would one go to learn how to make Treble ROMs boot and fix errors like this, and just dev stuff like this in general haha.

i was able to boot flashing boot_a, boot_b, system_a, system_b, vbmeta and vendor. i didn't used any dm-verify commands....
ps: it feels really smoother and snappier.... dont know why yet..... lol.....
TURBO

TURBO2012 said:
i was able to boot flashing boot_a, boot_b, system_a, system_b, vbmeta and vendor. i didn't used any dm-verify commands....
ps: it feels really smoother and snappier.... dont know why yet..... lol.....
TURBO
Click to expand...
Click to collapse
What are you talking about? Your screenshot shows stock ROM, not any of the GSI

Exelios said:
What are you talking about? Your screenshot shows stock ROM, not any of the GSI
Click to expand...
Click to collapse
My bad.... I flashed the files in OP. Thinking those were a gsi rom. Lol... My apologies.....
this is the correct one:
TURBO

This thread is almost 3 years old but leaving this here since it is the top google search for OnePlus 6 HS-USB Diagnostics 900E hopefully my solution in the link below helps someone else in the future.
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 6
Similar to the previous threads for OnePlus 5 or OnePlus 5T, here are the necessary packages to unbrick/revive a hard bricked OnePlus 6. Download: https://www.androidfilehost.com/?w=files&flid=271466 OnePlus 6_180513_氢OS线刷包.rar After using it...
forum.xda-developers.com

[GUIDE] Install GSI on Xiaomi Mi 10

This is how it works for me.
If someone knows a better way let me know.
What you need
Xiaomi Mi 10 (UMI) with unlocked bootloader and latest Xiaomi.eu ROM installed
A/B GSI
PC with ADB & Fastboot installed
USB Cable
Mi 10 stock recovery installed or img for installation
TWRP.img for Mi 10 (If you want to install anything else like Magisk or something)
Boot to fastboot
(Skip this part if you're using stock recovery)
Power off your phone
Hold Volume down + Power until you see fastboot screen
Flash stock recovery found in latest firmware
Code:
fastboot flash recovery recovery.img
Boot to recovery
Power off your phone
Hold Volume up + Power until you see recovery screen
Wipe data
Select option Connect with MiAssistant
Reboot into fastbootd (Fastboot User Space)
Code:
adb reboot fastboot
Erase system partition
Code:
fastboot erase system
Flash your GSI
Code:
fastboot flash system system.img
If you're done here and doesn't want to install anything else
Just reboot and enjoy!
Code:
fastboot reboot
If you want to install anything else
Reboot to fastboot
Code:
fastboot reboot bootloader
Boot TWRP
Code:
fastboot boot TWRP.img
Use MTP to transfer your zip files to internal storage
Install them
Reboot
Enjoy!
Working Images (Need to be A/B)
Quack Phh-Treble
AOSP Q Mod //CAOS
Maybe any image with phhusson treble_experimentations included
At this time (Patch v222) there are some issues (Nothing compared to MIUI's bugs )
Audio issues (Most of them can be fixed by disabling audio effetcs in phh's Settings)
BT audio doesn't work
Fingerprint doesn't work
90 Hz Display doesn't work (Limited to 60 Hz)
Tell me if you found any other working GSI (Please provide forum link)

Which vendor and firmware did you used? Latest one 20.9.4 or specific one?
https://xiaomifirmwareupdater.com/vendor/umi/
https://xiaomifirmwareupdater.com/firmware/umi/

sceryavuz said:
Which vendor and firmware did you used? Latest one 20.9.4 or specific one?
https://xiaomifirmwareupdater.com/vendor/umi/
https://xiaomifirmwareupdater.com/firmware/umi/
Click to expand...
Click to collapse
My Mi 10 was on latest xiaomi.eu stable.

you can write what system images you managed to run on mi10

Kabanoska said:
you can write what system images you managed to run on mi10
Click to expand...
Click to collapse
Sorry I dont understand
Edit: Now I got it...

Is it same guide for Mi 10 Pro?

henkka22 said:
Is it same guide for Mi 10 Pro?
Click to expand...
Click to collapse
I think it'll be the same. As long as you can go to fastbootd with this guide it should be fine.

Basecatcherz said:
I think it'll be the same. As long as you can go to fastbootd with this guide it should be fine.
Click to expand...
Click to collapse
I can confirm that this tutorial works for cmi too. Phhs treble is running but same bugs. Andy yans lineage didn't work If you want this tutorial could be copied to mi 10 pro forums too since there is no roms for it

henkka22 said:
I can confirm that this tutorial works for cmi too. Phhs treble is running but same bugs. Andy yans lineage didn't work If you want this tutorial could be copied to mi 10 pro forums too since there is no roms for it
Click to expand...
Click to collapse
There is something weird here...
I tried some other GSI and ended up soft bricked. Flashed latest stock (boots up) and then flashed CAOS GSI again.
It goes to boot splash and restarts all the time.
Are you on xiaomi.eu?

Basecatcherz said:
There is something weird here...
I tried some other GSI and ended up soft bricked. Flashed latest stock (boots up) and then flashed CAOS GSI again.
It goes to boot splash and restarts all the time.
Are you on xiaomi.eu?
Click to expand...
Click to collapse
I flashed latest stable xiaomi.eu (was on weekly) and then flashed phhs treble. Can't flash over weekly android 11. Didn't try caos

henkka22 said:
I flashed latest stable xiaomi.eu (was on weekly) and then flashed phhs treble. Can't flash over weekly android 11. Didn't try caos
Click to expand...
Click to collapse
Alright. I flashed latest stable xiaomi.eu ROM and now CAOS boots up. Looks like they made some relevant changes.

And btw you don't need stock recovery. I have twrp which have userspace fastboot aka fastbootd so I can leave it installed

henkka22 said:
And btw you don't need stock recovery. I have twrp which have userspace fastboot aka fastbootd so I can leave it installed
Click to expand...
Click to collapse
I tried that, too (LR Team). But Windows was unable to find the right driver and I was unable to use it. Even on Ubuntu it wasn't working.

Basecatcherz said:
I tried that, too (LR Team). But Windows was unable to find the right driver and I was unable to use it. Even on Ubuntu it wasn't working.
Click to expand...
Click to collapse
I just used newest platform tools directly from google site on ubuntu

henkka22 said:
I just used newest platform tools directly from google site on ubuntu
Click to expand...
Click to collapse
On ubuntu I used them, too. In the windows package there are no drivers included.
I tried many drivers flying around in the www...

Does caos gsi pass safetynet for you?

henkka22 said:
Does caos gsi pass safetynet for you?
Click to expand...
Click to collapse
The non-rooted variant with magisk, yes.
Phh's got the problem thats it's pre-rooted.

Basecatcherz said:
On ubuntu I used them, too. In the windows package there are no drivers included.
I tried many drivers flying around in the www...
Click to expand...
Click to collapse
I used Windows originally, you'll have to manually install the Xiaomi drivers from Xiaomi cn website through computer mangement, on this link: https://www.xiaomi.cn/post/18464849. Since these are not signed, you will have to disable signature enforcement on Windows 10! Here is an article on doing that, method 1 works: https://windowsloop.com/disable-driver-signature-enforcement-on-windows/.
Or you can try Mi Flash Tool and look for the install driver option, I haven't tried that method. Let us know how it goes .

xda-jimjongs said:
I used Windows originally, you'll have to manually install the Xiaomi drivers from Xiaomi cn website through computer mangement, on this link: https://www.xiaomi.cn/post/18464849. Since these are not signed, you will have to disable signature enforcement on Windows 10! Here is an article on doing that, method 1 works: https://windowsloop.com/disable-driver-signature-enforcement-on-windows/.
Or you can try Mi Flash Tool and look for the install driver option, I haven't tried that method. Let us know how it goes .
Click to expand...
Click to collapse
I will try that. Maybe tomorrow
Unsigned drivers are not the way I like...

I have MIUI 11 Xiaomi.eu Android 10 stable, can I flash this ROM and Gapps, and maybe some progress to remove in existing issues?

Root Android 12 BETA on 3a XL (And Others...)

Rooting these is easier than some people make it out to be on other Pixel forums, so I figured I'd write up a simplified Root guide for Android 12 here as I don't see one for the 3a XL, but this does apply to all Pixel's that can upgrade to Android 12. Every other tutorial I see tells you go go through and flash Android 11 with Google Chrome, then unlock the bootloader and flash 12, then use the chrome browser flashing to disable verification. Disabling verification is 1 line of code and flashing vbmeta.img. No reason to do all that extra work when it can be done in a few minutes.
I'm not responsible for bricked devices or lost data, do this at your own risk. This tutorial is assuming your Bootloader is ALREADY UNLOCKED. If not, its fairly simple and there's tons of guides on it
This Tutorial was originally written for the Android 12 BETA. Google themselves stated to disable verification and verity with the BETA, but the official Android 12, this step MAY NOT BE NEEDED. Simply try it honestly. if it doesn't bootloop, you don't have to disable verity with vbmeta
What's needed:
- Magisk Manager (here: https://github.com/topjohnwu/Magisk/releases/)
- Fastboot ZIP from Google (here: https://developer.android.com/about/versions/12/download)
- ADB/Fastboot and Drivers installed (new installer: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/)
- Unlocked Bootloader
Instructions
1.) Make sure your bootloader is unlocked, and USB Debugging is enabled.
Download the Fastboot ZIP from google for your device. Open it with 7Zip (or your preferred program), then open the Zip file found in that extracted in 7Zip and pull out boot.img and vbmeta.img
2.) Install Magisk Manager on Device and put the boot.img on your internal storage
3.) Use Magisk Manager to patch the Boot.img file
4.) Drag and drop the magisk-patched.img somewhere on your computer. This is the rooted boot.img
5.) Reboot device to Bootloader and first disable boot verification with the code below
-- To get vbmeta.img, you can pull it out of that Fastboot Zip from Google for Android 12. Simply open the image-xxxxx-xxxxxxx.zip and extract it from there
Code:
fastboot --disable-verity --disable-verification flash vbmeta <drag your vbmeta.img to CMD window>
6.) Once that's done, flash your patched boot image
Code:
fastboot flash boot <drag your magisk-patched.img to CMD Window>
7.) You're rooted!
Update Oct 29, 2021 added above about official android 12 vs beta android 12 (when this was originally written)

Assuming this works as it's supposed to, and my bootloader is already unlocked, will this wipe my data? (Pixel 4a)

tails618 said:
Assuming this works as it's supposed to, and my bootloader is already unlocked, will this wipe my data? (Pixel 4a)
Click to expand...
Click to collapse
Since your bootloader is unlocked, it shouldn't wipe anything

tails618 said:
Assuming this works as it's supposed to, and my bootloader is already unlocked, will this wipe my data? (Pixel 4a)
Click to expand...
Click to collapse
Hey did this work for you on Pixel 4a? I just flashed beta 4 and I haven't tried rooting yet.

Makishima said:
Hey did this work for you on Pixel 4a? I just flashed beta 4 and I haven't tried rooting yet.
Click to expand...
Click to collapse
Sorry it took so long to reply - yes, it did.

KaptinBoxxi said:
Rooting these is easier than some people make it out to be on other Pixel forums, so I figured I'd write up a simplified Root guide for Android 12 here as I don't see one for the 3a XL, but this does apply to all Pixel's that can upgrade to Android 12. Every other tutorial I see tells you go go through and flash Android 11 with Google Chrome, then unlock the bootloader and flash 12, then use the chrome browser flashing to disable verification. Disabling verification is 1 line of code and flashing vbmeta.img. No reason to do all that extra work when it can be done in a few minutes.
I'm not responsible for bricked devices or lost data, do this at your own risk. This tutorial is assuming your Bootloader is ALREADY UNLOCKED. If not, its fairly simple and there's tons of guides on it
What's needed:
- Magisk Manager (here: https://github.com/topjohnwu/Magisk/releases/)
- Fastboot ZIP from Google (here: https://developer.android.com/about/versions/12/download)
- ADB/Fastboot and Drivers installed (new installer: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/)
- Unlocked Bootloader
Instructions
1.) Make sure your bootloader is unlocked, and USB Debugging is enabled.
Download the Fastboot ZIP from google for your device. Open it with 7Zip (or your preferred program), then open the Zip file found in that extracted in 7Zip and pull out boot.img and vbmeta.img
2.) Install Magisk Manager on Device and put the boot.img on your internal storage
3.) Use Magisk Manager to patch the Boot.img file
4.) Drag and drop the magisk-patched.img somewhere on your computer. This is the rooted boot.img
5.) Reboot device to Bootloader and first disable boot verification with the code below
Code:
fastboot --disable-verity --disable-verification flash vbmeta <drag your vbmeta.img to CMD window>
6.) Once that's done, flash your patched boot image
Code:
fastboot flash boot <drag your magisk-patched.img to CMD Window>
7.) You're rooted!
Click to expand...
Click to collapse
What you seemed to have missed the whole part about the vbmeta.img part? Where you you get that??

prot- said:
What you seemed to have missed the whole part about the vbmeta.img part? Where you you get that??
Click to expand...
Click to collapse
You get vbmeta from the Fastboot zip file in the image-xxxxxxxxx.zip that you extract. I'll add it to original post. I didn't realize I forgot

KaptinBoxxi said:
You get vbmeta from the Fastboot zip file in the image-xxxxxxxxx.zip that you extract. I'll add it to original post. I didn't realize I forgot
Click to expand...
Click to collapse
Awesome thanks!
For Android 11 I always need a custom kernel to avoid freeze cause of the systemless hosts file. Do U do the same in 12? What kernel?

prot- said:
Awesome thanks!
For Android 11 I always need a custom kernel to avoid freeze cause of the systemless hosts file. Do U do the same in 12? What kernel?
Click to expand...
Click to collapse
Honestly, when I flashed this, I didn't do anything except the vbmeta and the android 12. If its a GSI, I would think maybe a custom kernel is needed, but this isn't a GSI if you're doing it right to a pixel. My 3A XL is still running 12 just fine with root, no custom kernel

KaptinBoxxi said:
Honestly, when I flashed this, I didn't do anything except the vbmeta and the android 12. If its a GSI, I would think maybe a custom kernel is needed, but this isn't a GSI if you're doing it right to a pixel. My 3A XL is still running 12 just fine with root, no custom kernel
Click to expand...
Click to collapse
With systemless hosts enabled?

prot- said:
With systemless hosts enabled?
Click to expand...
Click to collapse
yep, enable it with every device i root

KaptinBoxxi said:
You get vbmeta from the Fastboot zip file in the image-xxxxxxxxx.zip that you extract. I'll add it to original post. I didn't realize I forgot
Click to expand...
Click to collapse
Does vbmeta.img change with each new monthly release? If so, then flashing vbmeta.img with the --disable-verity and --disable-verification flags will need to be done as part of the update process. Correct?

Can someone confirm whether disabling verity and verification is absolutely necessary on the Pixel 3? I believe this issue is specific to the 4a 5g, 5, 5a, and 6 series, and should not affect the 3/3XL/3a/4/4XL/4a.
Try this: Reflash vbmeta without the flags
Code:
fastboot flash vbmeta vbmeta.img
Leave your patched boot image alone and see if you boot. If you end up in bootloader with
failed to load/verify boot images
this confirms that disabling verity/verification is necessary.

V0latyle said:
Can someone confirm whether disabling verity and verification is absolutely necessary on the Pixel 3? I believe this issue is specific to the 4a 5g, 5, 5a, and 6 series, and should not affect the 3/3XL/3a/4/4XL/4a.
Try this: Reflash vbmeta without the flags
Code:
fastboot flash vbmeta vbmeta.img
Leave your patched boot image alone and see if you boot. If you end up in bootloader with
failed to load/verify boot images
this confirms that disabling verity/verification is necessary.
Click to expand...
Click to collapse
I've had hit or miss results to be 100% honest. I never do anything differently. I've rooted dozens upon dozens of Pixel's. Sometimes its needed, sometimes it isn't.
In this case its needed because of Android 12 BETA GSI was being used. Since Android 12 Official is out, it may not be needed

KaptinBoxxi said:
I've had hit or miss results to be 100% honest. I never do anything differently. I've rooted dozens upon dozens of Pixel's. Sometimes its needed, sometimes it isn't.
In this case its needed because of Android 12 BETA GSI was being used. Since Android 12 Official is out, it may not be needed
Click to expand...
Click to collapse
I believe this has more to do with Boot Image Header v4, not GSI. I could be wrong.

V0latyle said:
I believe this has more to do with Boot Image Header v4, not GSI. I could be wrong.
Click to expand...
Click to collapse
Well even google stated to disable it during the beta. They didn't provide avb_keys at first with the beta, which was strange which is why i said to do it on this tutorial

V0latyle said:
Can someone confirm whether disabling verity and verification is absolutely necessary on the Pixel 3? I believe this issue is specific to the 4a 5g, 5, 5a, and 6 series, and should not affect the 3/3XL/3a/4/4XL/4a.
Click to expand...
Click to collapse
I have the 3a and was able to root normally without disabling verity and flashing vbmeta.

mulperi said:
I have the 3a and was able to root normally without disabling verity and flashing vbmeta.
Click to expand...
Click to collapse
This issue only affects 765G and Tensor devices - the 4a 5g, 5, 5a, 6, and 6 Pro. All other devices are NOT affected.

Will this method work on a pixel 3a XL on Android 10

[Guide] How to flash custom rom (gsi) in infinix hot 11s (X6812/X6812B)

In this Guide i will explain you how you can flash GSI rom in infinix hot 11s
Warning - this can brick your device if not done properly use this guide only if you know how to recover to stock rom using spflash tool
NOTE- I am assuming you have unlocked the bootloader and enabled usb debugging if you haven't done that you can learn to do that from the other guide i made
First you need to download a working gsi for this device you can download the ones we have tested below
Now download and install platform tools using this Tutorial you can skip this if you have already done this
You need to get the vbmeta.img and vbmeta_system.img from stock firmware which you can download and extract using 7zip and then take the both the files from it or ask in our Telegram group
After downloading gsi image make sure to extract it to .img format using 7-zip as
I advice you to move all required files for flashing into platform tool folders in root directory to make it easier or atleast move it to same folder
Product.gsi has been attached (it's same for both NFC and non NFC version)
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you are stuck at "waiting for devices" output at this step you will have to follow this video
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot (you should enter fastbootd after this command make sure before continuing)
fastboot flash product product_gsi.img
fastboot flash system <gsiname>.img
IF YOU ARE GETTING UNABLE TO RESIZE PARTITION ERROR MAKE SURE TO FLASH YOU FLASHED Product_gsi.img
Now select recovery from volume down button and power button >> go to wipe data and factory reset now reboot to system
~~End of guide!~~
Tested roms -
Ancient os Android 12 vndklite ( best rom if you want to play games on this phone codm runs buttery smooth on 90fps! has a lots of customisation )
Pixel experience Android 12 vndklite (is more stable and bug free than ancient os better memory management and a lot better battery life than stock and even ancient os best rom if you want to use it for daily driving)
For future development and questions join our telegram group https://t.me/infinixhot11s_dev
Edit - I was able to fix all the audio and performance issues by making a magisk module for it download Here (if you don't know how to root this device I have made a guide on that too)
Low call volume problem is also fixed by the module
Edit 2 - stock camera has been ported to gsi and the 50mp camera works now join telegram for more information
Edit 3 - newer versions of gcam bsg supports 50 mp camera
Edit 4 - Android 13 GSI works good and the Bluetooth issues are fixed in latest patches (you can daily drive it)
Quick fixes for GSI you will need after flashing :-
Enable the settings highlighted in the screenshot below by going to settings/phh settings/misc features
For VoLTE to work go to settings/phh settings/IMS Features and enable all 4 options (make sure you are connected to internet so that you can download ims apk)
Reboot
Non nfc stock rom - Link
nfc stock rom -

Ansh, Zypher here. I'll DM you on XDA regarding to Ancient OS. I cannot use my main phone and no telegram so I'll DM you here. Please accept me, thank you.

Zypher Kim said:
Ansh, Zypher here. I'll DM you on XDA regarding to Ancient OS. I cannot use my main phone and no telegram so I'll DM you here. Please accept me, thank you.
Click to expand...
Click to collapse
Sure

Thx for the awesome step by step guide bro

The volume increases but cannot reduce it and is only on loud speaker

kelvinchinedu said:
The volume increases but cannot reduce it and is only on loud speaker
Click to expand...
Click to collapse
Working to fix it

Better

i tried to do "fastboot reboot fastboot" command, But "fastboot: usage: unknown reboot target fastboot". How to enter fastbootd?

aryornug said:
i tried to do "fastboot reboot fastboot" command, But "fastboot: usage: unknown reboot target fastboot". How to enter fastbootd?
Click to expand...
Click to collapse
Try to download a newer platform tool verson

also works on standard infinix hot 11! except for the gcam patch which i didnt try

Fggevhy said:
also works on standard infinix hot 11! except for the gcam patch which i didnt try
Click to expand...
Click to collapse
That's good to know

Fggevhy said:
also works on standard infinix hot 11! except for the gcam patch which i didnt try
Click to expand...
Click to collapse
Can you tell me what did you do to get it running on the standard hot 11 x662
I tried but ended up bricking my device
(Restored later with sp flash tool)

Yahiaxe said:
Can you tell me what did you do to get it running on the standard hot 11 x662
I tried but ended up bricking my device
(Restored later with sp flash tool)
Click to expand...
Click to collapse
Try following same tutorial but take vbmeta.img and vbmetasystem fr your firmware...also see if hot11 also has same architecture (for gsi)

Uniqueshiva said:
Try following same tutorial but take vbmeta.img and vbmetasystem fr your firmware...also see if hot11 also has same architecture (for gsi)
Click to expand...
Click to collapse
Is the product.gsi the same for the standard hot 11?

Yahiaxe said:
Is the product.gsi the same for the standard hot 11?
Click to expand...
Click to collapse
It should work fine for all android including yours

ansh_/ said:
It should work fine for all android including yours
Click to expand...
Click to collapse
I tried again but I got an error "dm-verify is corrupt your device will boot in 5 seconds" and it just bootloops

Yahiaxe said:
I tried again but I got an error "dm-verify is corrupt your device will boot in 5 seconds" and it just bootloops
Click to expand...
Click to collapse
I got it to finally work thanks to everyone for your help and thanks ansh_/ for the wonderful guide
ps: Switching to a non-vndklite gsi did the trick

the gsi flashing is easier then i thought
I tested pixel experience plus (june update), it was laggy, crashing and slow
currently on ancient os 6.4 and its a-m-a-z-i-n-g smooth, fast, no crashes, good game performance and extremely customizable, I highly recommend it
update; ancient started getting a little laggy for some reason and randomly rebooted a few times
so, i switched to crdroid 8.8, it's great nice clean customizable and stable android, with great battery management and performance

hello need help. after following your tutorial ang flashing crdroid 8.8 i got a device corrupted then proceeds to bootloop.
after that i tried flashing stock firmware using sp flash tool with this tutorial
[Guide] Flashing stock rom for Mediatek devices using spflash tool
In this guide i will explain you how to flash stock ROM using spflash for your Mediatek devices in the simplest way possible Requirements - a phone with Mediatek SoC Stock rom which you may or may not find on your vendor official website ( a...
forum.xda-developers.com
but no luck bypass tool give me some kind of error and wont bypassed the protection. now the phone is stuck on charging light. power button does nothing.
i hope anyone have ideas to fix this
thanks

SlothYano said:
hello need help. after following your tutorial ang flashing crdroid 8.8 i got a device corrupted then proceeds to bootloop.
after that i tried flashing stock firmware using sp flash tool with this tutorial
[Guide] Flashing stock rom for Mediatek devices using spflash tool
In this guide i will explain you how to flash stock ROM using spflash for your Mediatek devices in the simplest way possible Requirements - a phone with Mediatek SoC Stock rom which you may or may not find on your vendor official website ( a...
forum.xda-developers.com
but no luck bypass tool give me some kind of error and wont bypassed the protection. now the phone is stuck on charging light. power button does nothing.
i hope anyone have ideas to fix this
thanks
Click to expand...
Click to collapse
Well, your actually might have just hard bricked this device I am afraid.
But I can tell you the steps to flash the stock firmware
1- Download the firmware for your device make sure its the correct one (If it's incorrect then you will hard brick the device)
2- Make sure you have mtk vcom drivers
3- use spflashtool and load the firmware (no need for the bypass tool)
4- make sure you set it to Firmware Upgrade (This is important)
5- make sure your phone is off
6- click on "Download" in the flashtool
7- Hold both volume buttons and plug in the device
8- If your device is still alive it should start the flashing process
Note: You did something that was incorrect when you started to follow this guide and you most likely hard bricked your device. Your phone is gone I think
Please note that I am not an expert on the subject tho

How To Guide Unlock the bootloader and install GSI ROM

So if anyone is interested in booting a GSI Image Here is the guide: also thanks to @Dollscythe I just updated it as he forget to write me a step for flashing the vbmeta.img..
1. you need to download the firmware file for your model
2. you need to open it with your zipping software of choice (i use 7zip) And after it unzips you need to unzip AP file to get to the recovery.img.lz4
3. you extract the recovery.img and you patch it to enable fastbootd https://github.com/Johx22/Patch-Recovery you will also find the info how to patch it on the link, it is easy if you know how to follow it) - Currently is NOT working, the dev said to me that he will fix this once his exams are over. (If you know how to Decompress the Iz4.img to get just the .img it will probably work - didn't try tho.
4. this step will wipe your device so make sure to back up (unlocking the bootloader) And it will also trigger your Knox!
To unlock the bootloader you need to go to settings, about phone - software info and press on the build number like 7times to enable developer options. After that go to developer options and enable OEM unlock.
Turn off the phone, put the USB C cable into the phone (but not into the computer yet!) Then hold the volume + and volume - button at the same time and put the cable into the phone.
When you are in the download mod you will see the instructions on how to unlock the bootloader.
5. Boot into the system and do the first time setup (make sure to connect to wifi, but skip any prompts to register or login to accounts)
6. double check if the oem unlock toggle is still on, then reboot to download mode
7. you need to flash the patched bootloader using odin - you flash your patched recovery in AP window in Odin. Then you immediately boot into the recovery (you gotta boot to your new recovery immediately after the flash is complete, make sure to hold the key combination for recovery immediately after pressing start in odin to get it right. otherwise, the system will wipe your newly flashed recovery and you'll have to do step 7 again)
8. You will now notice that your recovery has a new option: fastbootd mode (yes there's a d in there, it's not a typo, it stands for fastbootdynamic mode) 9. once you're in, your device now officially supports fastboot. you just do "fastboot flash system *the_name_of_the_system_image_you_downloaded.img", RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group) and once that is done flashing just exit fastbootd mode back to the recovery, then format data and then then reboot for system images, i recommend pixel experience https://github.com/ponces/treble_bu...4-ab-vndklite-12.1-20220518-UNOFFICIAL.img.xz 10. you'll be greeted by a google bootlogo and thats a success.
Good luck!

Bucika said:
RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group)
Click to expand...
Click to collapse
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.

One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website

jdg007 said:
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
Click to expand...
Click to collapse
The purpose of XDA "Developers" was actually to share knowledge between developers, you know, people who actually know how the most basic stuff works. It's open up for the public, sure, but most of the stuff you can find here are not meant for the average noob that doesn't know how to unlock a bootloader.
The instructions are pretty clear for people who can use a google search. Don't expect everything to be spoon fed, put in a little effort.
There's a difference between saying "OMG this is too complicated why don't you explain it with a video or why don't you tell me step by step on how to flash custom firmware on my phone" and saying "Hey I'm stuck in step 3, I don't understand the part here. This is what I've tried so far..."
I bet for the most part, the first person would be ignored while the second person would more likely get a response.

That means to offend you in any way or whatever I just wished people would give more explanations on what they post because you know I don't make no sense on how you patch the recovery I'm new at this it's my it's my fault I do know how to unlock bootloaders not bootleggers and I do know how to install TWRP and Flash zip balls but as when it comes to patching something the only thing I know how to pack is using magisk That's the boot image I'm sorry hope Hope you can help me out

If you don't mind email me a copy of that recovery image that you got Text I sure would appreciate it Just looking forward For your reply

Thanks @Bucika, here's a guide that might be a bit more noob friendly. Also a big thanks to @Dollscythe for their help.
Files can be found here.
These are the latest GSIs.
1. Unlock bootloader by opening developer options and flipping the "unlock bootloader" switch.
2. Boot into download mode (press and hold vol + and - while plugging into computer).
Press and hold vol + to enter unlock mode. Accept and click enter. Your phone will reset.
3. Using Odin, flash fastbootd through AP. (recovery.img).
4. Press and hold volume + key as the phone reboots, as when you restart again it will reverse this step. You should be in recovery now.
Click on fastboot.
5. Get fastboot working on your computer. Test connection by using the command "fastboot devices" to see if your device is there.
6. Run the command fastboot flash system [name of gsi file]. (without square brackets)
7. When you're done, run ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. Go back to recovery and wipe your phone.
9. Go back into fastboot, flash magisk file if you would like root: fastboot flash boot magisk
10. Wipe again, reboot.
11. Once you are fully booted in, open settings > phh settings (first entry) > misc settings > then scroll down until you find "force fps"
Change that to the @120fps option.
Hope this helps! Note that this is unofficial and WiFi hotspot doesn't work, Samsung Health has issues too. I couldn't get my watch 4 working with GSI.
This will blow your Knox bit fuse!

Ivan Fuentes Hagar said:
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
Click to expand...
Click to collapse
I find myself in a bootloop too after this step, how did you get out of the bootloop?
edit, answer to my own question in case it helps someone in the future: plug phone into a pc and then hold `volume up + volume down` buttons to enter download mode.
edit 2 if after flashing a GSI rom your device wont boot, plug it into power and wait a few minutes.

I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?

ActuallyJammy said:
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
Click to expand...
Click to collapse
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12

TringQuack said:
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
Click to expand...
Click to collapse
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.

ActuallyJammy said:
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
Click to expand...
Click to collapse
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13

TringQuack said:
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
Click to expand...
Click to collapse
Could you give me a GSI rom with a patch and similar to PE?

@TringQuack What's your current state with A53?
Running GSI? Stock?

ThugMaster said:
@TringQuack What's your current state with A53?
Running GSI? Stock?
Click to expand...
Click to collapse
Stock

@TringQuack How do I know if the build is compatible with A13?