Related
Ladies and Gentlemen,
It is my pleasure to present the latest stock Oreo 8.1 (Beta) ROM for Xiaomi Mi A1. Up till now, only a handful of testers were able to use the stock beta 8.1
But now, everyone has the opportunity to use it on their device.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I would not be responsible if anything happens to your device. Your warranty will be void after flashing the ROM. You need to go back to stock stable ROM with a locked bootloader for Warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and unzip it.
2. You will see a folder with name as tissot_images_V9.6.2.0.ODHMIFE_8.1
3. Keep it on C drive
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.2.0.ODHMIFE_8.1 and click on "Flash". Make sure you are doing it in a proper way.
10. Wait until you see a "Flash Done" message on the screen. It may take around 5-10 minutes. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with June security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. A lot of newbees have problem at first, especially when flashing rom on MiFlash tool. That's because of selecting and flashing the rom file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
I have been using the ROM for two days and I am yet to find any bugs except ctsProfile shows as false and Google Play Store shows Uncertified.
*For better battery life, you can try Void kernel (Choose the stock version).
ROM Download Link:
https://www.androidfilehost.com/?fid=818222786056041186
Credit:
Xiaomi, 4PDA, @topjohnwu for Magisk, @flex1911 for Void kernel, @CosmicDan & @mohancm for their work on TWRP.
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.
MiFlash Tool
Screenshots will be added shortly.
Screenshots
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
exodius48 said:
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
Click to expand...
Click to collapse
I can confirm battery drain with this rom.
Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
Did xiaomi give you the permission to share it on xda?
muruu said:
Did xiaomi give you the permission to share it on xda?
Click to expand...
Click to collapse
No, this is leaked beta. He just reshare from displax @ 4pda.ru
after sucessfully flashing using miflash it stucks on andriodone
N1ck474 said:
This update is leaked from weeks, why complaining here and now?
We're getting delayed updates cause Xiaomi is far away from Quick updates (MIUI or Stock, still Xiaomi).
Click to expand...
Click to collapse
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
joeniz said:
when unlock bootloader cause erase all information like may update?
Click to expand...
Click to collapse
Why would they remove a security feature they just recently added?
joeniz said:
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
Click to expand...
Click to collapse
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
dback31 said:
Why would they remove a security feature they just recently added?
Click to expand...
Click to collapse
Cause i found no phone that u can't root !!
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
Rowdyy Ronnie said:
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Click to expand...
Click to collapse
What about messenger fb in any rom i use i get animation lag in messenger when message appear things like that and if someone send me message while i using phone the phone animation lag .... Only in fb messenger i found this problem i hate this app .... Anybody have that issue because iam going mad .
Rowdyy Ronnie said:
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
Click to expand...
Click to collapse
If you just share a rom build by someone else, this is the wrong section of the forum to post it.
Too, you say (in op) you have permission from xiaomi to post it here in xda. This sounds unusual. Do you have any proof for this claim?
Thread cleaned.
Thread moved to the guides section where shared ROMs belong. The redirect from development section will expire in 24 hours.
:good:
Rowdyy Ronnie said:
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
hahahah oh wow
the best joke i ever seen
seriously
copyright to leaked build? hahaha i can't stop
Closed beta ROM, so no point in "allowing" you to share it. They could open beta and do it themselves.
I call fake news on that
You share a rom from another forum. Okay. It was already been shared in XDA by the original poster in 4pda.
I call this reposting in the same forum.
You state that the ROM isn't yours and you "share" it with other people on XDA. And then you say reposting is stealing? Didn't you repost it as well? For you is not stealing but for others is?
Conclusion: Are you that desperate for attention?
Is this the official beta rom?
Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
Click to expand...
Click to collapse
How did you manage to get permission from Xiaomi? Have some proofs?
Hello, I want to install official android 12 GSI ROM on my device (Mi A2). I have stock ROM installed on my device and I want to install it by following the official installation instructions. I doubt my device will work with official installation instructions, but my device is fully treble supported. Will my device work in this case? The only answer to this question will be to do this, but I'm afraid of bricking my device.
Everyone can answer you. Not means that he answer you because he knows the answer since he born !
He had search, read & get knowledge.
It always recommended to read about Gsi carefully before install it on your device if you fear bricking then find out on your responsibility.
Hope you got me.
Regards
Abdullah.Csit said:
Everyone can answer you. Not means that he answer you because he knows the answer since he born !
He had search, read & get knowledge.
It always recommended to read about Gsi carefully before install it on your device if you fear bricking then find out on your responsibility.
Hope you got me.
Regards
Click to expand...
Click to collapse
Thanks. I just want to know if anyone has successfully installed the official method.
LazCoder said:
Thanks. I just want to know if anyone has successfully installed the official method.
Click to expand...
Click to collapse
Every one followed the official method has get successfully installation. most devices has same instructions. sometimes you get stuck on Boot loop or system not booting just change the version of GSI build.
Good luck
Abdullah.Csit said:
Every one followed the official method has get successfully installation. most devices has same instructions. sometimes you get stuck on Boot loop or system not booting just change the version of GSI build.
Good luck
Click to expand...
Click to collapse
Thanks, then I'll have to take the risk. If the GSI does not boot I will install the stock ROM. I haven't reset it to factory reset since I bought it. Or I will buy a Pixel device to avoid dealing with all this, but Google Pixel devices are not sold in Turkey.
LazCoder said:
Hello, I want to install official android 12 GSI ROM on my device (Mi A2). I have stock ROM installed on my device and I want to install it by following the official installation instructions. I doubt my device will work with official installation instructions, but my device is fully treble supported. Will my device work in this case? The only answer to this question will be to do this, but I'm afraid of bricking my device.
Click to expand...
Click to collapse
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
mottaM said:
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
Click to expand...
Click to collapse
Just because your device is treble compatible doesn't mean it supports new Android versions. Did you check if it supports new versions?
mottaM said:
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
Click to expand...
Click to collapse
I have a Nokia 2.2 same chipset (mt6761) and android 12 gsi works
areallydumbperson said:
I have a Nokia 2.2 same chipset (mt6761) and android 12 gsi works
Click to expand...
Click to collapse
It doesn't matter which chip it is. It matters what version the phone was released with and whether it supports future GSI releases.
LazCoder said:
Just because your device is treble compatible doesn't mean it supports new Android versions. Did you check if it supports new versions?
Click to expand...
Click to collapse
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
mottaM said:
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
Click to expand...
Click to collapse
Sad for you.
mottaM said:
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
Click to expand...
Click to collapse
After researching I was wrong but 32 bit vendor just so interesting
@LazCoder
Your phone's SoC is 64-bit.
You will need to recompile your entire ROM as 64 bit, then flash the GSI
GSIs will need the vendor and kernel and well everything else to be 64 bit
jwoegerbauer said:
@LazCoder
Your phone's SoC is 64-bit.
You will need to recompile your entire ROM as 64 bit, then flash the GSI
GSIs will need the vendor and kernel and well everything else to be 64 bit
Click to expand...
Click to collapse
Can I simply flash android 11 then flash android 12 gsi?
aqiluii said:
Can I simply flash android 11 then flash android 12 gsi?
Click to expand...
Click to collapse
Official sources say it's possible. But you should check compatibility first.
Hello everyone, since I have this mobile I have some problems. When paying with the phone, most of the time the NFC gives me an error and I have to try a thousand times. And the worst of all is that when I open the gallery or the camera, the brightness goes down to the minimum. Has anyone had these problems and solved them? Thank you very much.
Don't use stock rom, flash xiaomi.eu. It's way better than what xiaomi ships their phones with.
I had that issue with the stock, theirs a big list of bugs. I'm on xioami.eu 13.0.13 (recent as of this comment)
and all those are gone, except the phone bug where you have to answer in speaker mode once on, and off to fix it.
also the lockscreen video wallpaper doesn't loop, and stops playing after a while.
this is where the rom is,
https://xiaomi.eu/community/threads/22-6-8-6-9.66076/ (super easy to flash)
if you're lost just follow this
Installing MIUI EU ROM and root
Hi all, thought I would post a simple guide for people who are wanting to get some customisation on their ROMs and install root. First off - as of this post there's no working twrp/orangefox for this device and as far as I'm aware android 12...
forum.xda-developers.com
Vincent Foxx said:
Don't use stock rom, flash xiaomi.eu. It's way better than what xiaomi ships their phones with.
I had that issue with the stock, theirs a big list of bugs. I'm on xioami.eu 13.0.13 (recent as of this comment)
and all those are gone, except the phone bug where you have to answer in speaker mode once on, and off to fix it.
also the lockscreen video wallpaper doesn't loop, and stops playing after a while.
this is where the rom is,
https://xiaomi.eu/community/threads/22-6-8-6-9.66076/ (super easy to flash)
if you're lost just follow this
Installing MIUI EU ROM and root
Hi all, thought I would post a simple guide for people who are wanting to get some customisation on their ROMs and install root. First off - as of this post there's no working twrp/orangefox for this device and as far as I'm aware android 12...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much. I forgot to mention that my mobile is Poco x4 pro 5g. I have a Mac, and I don't know how to change the rom, the tools are for Windows.
Jorgelopezortiz74 said:
Thank you very much. I forgot to mention that my mobile is Poco x4 pro 5g. I have a Mac, and I don't know how to change the rom, the tools are for Windows.
Click to expand...
Click to collapse
XiaomiFlashTool V2 exists for all operating systems. You can also just use a vm to do this on your mac. Just pass your phone in after booting to fastboot and ensure you have fastboot drivers installed on your mac.
KHSH01 said:
XiaomiFlashTool V2 exists for all operating systems. You can also just use a vm to do this on your mac. Just pass your phone in after booting to fastboot and ensure you have fastboot drivers installed on your mac.
Click to expand...
Click to collapse
Xiaomi Flash Tool V2 is it safe to flash a rom on a device, or there is a lot of risk of bricking
Jorgelopezortiz74 said:
Xiaomi Flash Tool V2 is it safe to flash a rom on a device, or there is a lot of risk of bricking
Click to expand...
Click to collapse
As long as you get the right rom file it is fine. So triple check and ensure that you downloaded the right rom.
KHSH01 said:
As long as you get the right rom file it is fine. So triple check and ensure that you downloaded the right rom.
Click to expand...
Click to collapse
According to the colleague, the Xiaomi.eu rom has a bug when picking up the call. I don't know if that will be solved with the following updates, that's why I'm afraid to download that rom and that to solve the brightness it could spoil another function of the mobile.
Jorgelopezortiz74 said:
According to the colleague, the Xiaomi.eu rom has a bug when picking up the call. I don't know if that will be solved with the following updates, that's why I'm afraid to download that rom and that to solve the brightness it could spoil another function of the mobile.
Click to expand...
Click to collapse
Upto you whether you want to do or not. I won't be able to flash anything until my bootloader unlocks so I don't know what the differences between the roms are.
Hi,Umm, I have mostly encountered that devices with MTK chipset are going more haywire than SD chipsets could it be that there is no reason for this to be true.I have many MTK devices but now I haven't had them rooted can anyone confirm any method which is less harmful for MTK devices probably one which doesn't destroy motherboard.
P.S Usually I avoid buying MTK based devices also will probably avoid in future as well xD
it is irrelevant which processor is installed in the Android device: Android's version should be 6 and higher
actually, mediatek devices are easier to unlock, raw backup is always possible, porting custom recovery is possible without source code, rooting is therefore always possible, so consider mediatek is less secure than qualcomm or exynos where some devices don't even allow bootloader unlock.
downside, because source code often is not published, development scene has sparely support for mediatek, so often no custom ROM will be available at all.
of course, powerful tools like SP Flash Tool or mtkclient always come with highest risk to brick, it's your responsibility not to blindly trial or follow random people advice without knowing what you're actually doing. read golden rules
- do not flash preloader
- do not format whole eMMC
- do not use foreign scatter file
aIecxs said:
of course, powerful tools like SP Flash Tool or mtkclient always come with highest risk to brick, it's your responsibility not to blindly trial or follow random people advice without knowing what you're actually doing. read golden rules
- do not flash preloader
- do not format whole eMMC
- do not use foreign scatter file
Click to expand...
Click to collapse
Thanks for sharing this, I'll keep that in mind
Also I've never flashed Custom Rom on MTK variants though using Xposed and SU must have caused such issue.
aIecxs said:
do not format whole eMMC
Click to expand...
Click to collapse
what ?
Guan Yu said:
what ?
Click to expand...
Click to collapse
aIecxs said:
Did you actually ran, or did you try to run Format All + Download from SP Flash Tool?
In case you did, that will have erased SECRO which is responsible for verifying DA + auth_sv5.auth. Besides along with other important partitions (IMEI, calibration data, etc.) you lost the availbility to flash.
Click to expand...
Click to collapse
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use this guide to install any GSI as the process should work the same. You can find various projects in Treble-Enabled Device Development.
WARNING: These instructions are intended ONLY for those who are familiar with Android, partitions, Odin, TWRP, ADB tools, etc. If you are a beginner/novice, GO NO FURTHER. I am NOT a developer, and I will NOT provide support. All software linked herein is provided AS IS. If you screw something up with your phone because you're trying to do something you know nothing about, I won't help you fix it.
To check whether you can run a GSI on your device, you can either use Termux or adb shell:
getprop ro.treble.enabled
If this returns TRUE, your device is Treble enabled and can run GSIs.
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
Disconnect USB/power cables and turn your device OFF
Hold both Volume buttons (do not press Power) and plug in the USB cord connected to your PC
The download/unlock screen should come up immediately. Select the option for device unlock mode.
Disable Knox Guard
After unlocking your bootloader, boot your device normally. Skip through setup, but make sure you connect to the Internet.
Enable Developer options again; OEM Unlocking will likely not be visible. To fix this, initiate a check for a firmware update. Do not download the update.
Go back to Developer Options and confirm that OEM Unlocking is visible; it should be grayed out with the message "Bootloader is already unlocked". If you do NOT see OEM Unlocking, do not attempt to flash any custom firmware.
Put your device in Download Mode. Look for a line that says "KG STATUS" - CHECKING or COMPLETE are OK. If this says LOCKED or PRENORMAL, do not attempt to flash custom firmware and go back to step 1 of this section.
Flash TWRP
Download TWRP for your device. You need the file that ends in .tar.
Put your device in download mode and connect to your PC.
Using Odin, flash the TWRP image in the AP slot. Make sure you either uncheck Auto Reboot in the Options tab, or be ready to force recovery mode when the device reboots. If you allow the OEM firmware to boot after flashing TWRP, it will automatically install the OEM recovery.
Install Multidisabler
Download Multidisabler, transfer it to your device, and flash in TWRP. Among other things, this will disable the recovery restoration, although since you won't be using the OEM firmware this doesn't matter.
Format /data.
Install GSI
Download the Android Preview GSI from Google
These builds are similar to what Pixel devices are running, although they lag behind in updates, and the GMS flavor includes Google Apps. If you want the pure AOSP source, check out Android Continuous Integration for the "master" builds.
If you prefer, you can install the vanilla version, and flash the GApps package of your choice. I highly recommend LiteGapps or NikGapps
Extract system.img from the above archive and transfer to your device
Wipe /system in TWRP. Do not wipe /boot as this will erase your kernel!
Install GSI in TWRP: Install > Install Image > Select GSI image > Select /system and flash.
Important: If you need to flash a GApps package, do this immediately after installing the GSI. You may need to resize /system if you get an error.
Root/Pass Play Integrity
If you want root, just flash Magisk in TWRP. No need to rename it to .zip. If you choose not to root, be aware that the device will not pass Play Integrity, so many banking/DRM apps will not work.
If you do want to be able to use banking/DRM apps, root with Magisk and install the Universal SafetyNet Fix Displax mod to pass BASIC_INTEGRITY and DEVICE_INTEGRITY attestation.
Notes:
If your device does not have TWRP available, you can try patching your own recovery to enable fastbootd; this will allow you to flash partitions directly from a fastboot command line.
If you're feeling really brave, you can try running a Generic Kernel Image, which you'd flash to /boot. This may not boot properly.
Thanks for the tutorial
I have a Galaxy Note 9 (snapdragon) and Galaxy Tab S8+, wich doesn't have (almost) any roms.
Do you think Samsung hardware like s pen and camera will work fine on GSI ?
Do KVM is enabled on GSI ?
shim80 said:
Thanks for the tutorial
I have a Galaxy Note 9 (snapdragon) and Galaxy Tab S8+, wich doesn't have (almost) any roms.
Do you think Samsung hardware like s pen and camera will work fine on GSI ?
Click to expand...
Click to collapse
The idea behind GSIs, specifically Project Treble, is that the system image can change, while the hardware drivers and kernels will remain the same. So, in theory, yes - since you'd be using the original kernel, all hardware features should work. YMMV though, and I have no idea how to make them work if they don't. I'm not a developer.
shim80 said:
Do KVM is enabled on GSI ?
Click to expand...
Click to collapse
What is KVM? If it is Samsung specific, then likely not, unless it's built into the kernel.
V0latyle said:
What is KVM? If it is Samsung specific, then likely not, unless it's built into the kernel.
Click to expand...
Click to collapse
KVM (for Kernel-based Virtual Machine) is a feature that allow hardware virtualization on recent ARM chips.
It's enabled by default on Exynos and Tensor (Google), but Qualcomm is using it for protecting the kernel, so it's can't be enabled unless using modified custom kernel...
shim80 said:
KVM (for Kernel-based Virtual Machine) is a feature that allow hardware virtualization on recent ARM chips.
It's enabled by default on Exynos and Tensor (Google), but Qualcomm is using it for protecting the kernel, so it's can't be enabled unless using modified custom kernel...
Click to expand...
Click to collapse
Ah. Well, as I explained above, a Generic System Image is designed to be used with a separate kernel, most often the OEM kernel, so you could potentially flash a custom kernel and use a GSI with it. More to your point though, I have no idea - if KVM is implemented in the kernel, it should work on a GSI, provided you install the necessary framework to use it.
can you send any screenshot??
amirabbas mm said:
can you send any screenshot??
Click to expand...
Click to collapse
It's just AOSP, it's not custom. Looks like the Pixel interface. I don't have any screenshots.
Suggestion, you can add https://github.com/Johx22/Patch-Recovery
for devices without twrp. I and other ppl have already tested on galaxy tab A7 Lite and it works fine
V0latyle said:
The idea behind GSIs, specifically Project Treble, is that the system image can change, while the hardware drivers and kernels will remain the same. So, in theory, yes - since you'd be using the original kernel, all hardware features should work. YMMV though, and I have no idea how to make them work if they don't. I'm not a developer.
What is KVM? If it is Samsung specific, then likely not, unless it's built into the kernel.
Click to expand...
Click to collapse
What’s the catch? In other words, how is this different then the pixel experience rom?
Skorpion96 said:
Suggestion, you can add https://github.com/Johx22/Patch-Recovery
for devices without twrp. I and other ppl have already tested on galaxy tab A7 Lite and it works fine
Click to expand...
Click to collapse
I've never used that, can you describe how it works? I don't really intend this guide for beginners so I won't write detailed instructions but I can cover the basics. It sounds as though this can be used to flash system images via fastboot?
Arealhooman said:
What’s the catch? In other words, how is this different then the pixel experience rom?
Click to expand...
Click to collapse
I'll be honest, I've never used Pixel Experience, but from what I can see, the major difference is that it is based on AOSP and has a lot of Pixel stuff included. You can absolutely use this guide to install any GSI, they should all work the same since they're designed to work with a separate kernel. That being said, it appears that Pixel Experience is provided in a sideloadable ZIP, so you'd simply install the ZIP in TWRP.
What I have linked in this thread is the official Android Developer GSI which is intended to be used as a Compatibility Test Suite platform for Android apps, so it isn't really fine tuned for daily use, but in my experience it's been quite stable and usable. You can also use the master AOSP builds if you want the pure source.
V0latyle said:
I've never used that, can you describe how it works? I don't really intend this guide for beginners so I won't write detailed instructions but I can cover the basics. It sounds as though this can be used to flash system images via fastboot?
I'll be honest, I've never used Pixel Experience, but from what I can see, the major difference is that it is based on AOSP and has a lot of Pixel stuff included. You can absolutely use this guide to install any GSI, they should all work the same since they're designed to work with a separate kernel. That being said, it appears that Pixel Experience is provided in a sideloadable ZIP, so you'd simply install the ZIP in TWRP.
What I have linked in this thread is the official Android Developer GSI which is intended to be used as a Compatibility Test Suite platform for Android apps, so it isn't really fine tuned for daily use, but in my experience it's been quite stable and usable. You can also use the master AOSP builds if you want the pure source.
Click to expand...
Click to collapse
Would this have everything Google pixels have? Is this Google pixel firmware?
Arealhooman said:
Would this have everything Google pixels have? Is this Google pixel firmware?
Click to expand...
Click to collapse
This is just AOSP - plain Jane vanilla Android, optionally with Google apps. As such, it doesn't include any of the device specific customizations that Pixels may have. Pixel firmware is very close to AOSP and I'm not sure what all is different but the Pixels are marketed as Google's "Android Showcase" devices that demonstrate what Android is capable of.
What the Pixel series does is use a generic kernel and system image - meaning that you could, in theory, use the same system image on any GSI capable device - but they also have a product partition that contains the various customizations for that particular device. This is done to make software updates much simpler; on the Pixel series, Google basically uses one system build across all its active devices, meaning they don't have to rebuild for every update, while the product partitions are what hold the device specific software.
Long story short, Pixels are indeed running the AOSP GSI that I've shared here, but the GSI itself does not contain anything specific to the Pixels.
Tysm, and thsi has no chance of a brick if I do it right and am supported by project treble?
Arealhooman said:
Tysm, and thsi has no chance of a brick if I do it right and am supported by project treble?
Click to expand...
Click to collapse
It depends on your definition of "brick". To me, "bricked" means the device is completely unusable and unrecoverable with the software and tools that are available to the average user - for example, if the screen doesn't come on, the bootloader is corrupted, something like that.
Using a GSI won't cause this to happen, if you do everything properly. At the very worst, it may be unstable, and you may have to go back to your last known good configuration to be able to get your device working again, but that's just a matter of either flashing different firmware or going back to OEM firmware.
It's entirely possible that this may not work properly on your device, and since I am not a developer, I am not providing any support whatsoever. Use at your own risk.
V0latyle said:
I've never used that, can you describe how it works? I don't really intend this guide for beginners so I won't write detailed instructions but I can cover the basics. It sounds as though this can be used to flash system images via fastboot?
I'll be honest, I've never used Pixel Experience, but from what I can see, the major difference is that it is based on AOSP and has a lot of Pixel stuff included. You can absolutely use this guide to install any GSI, they should all work the same since they're designed to work with a separate kernel. That being said, it appears that Pixel Experience is provided in a sideloadable ZIP, so you'd simply install the ZIP in TWRP.
What I have linked in this thread is the official Android Developer GSI which is intended to be used as a Compatibility Test Suite platform for Android apps, so it isn't really fine tuned for daily use, but in my experience it's been quite stable and usable. You can also use the master AOSP builds if you want the pure source.
Click to expand...
Click to collapse
It decompile stock recovery, add fastboot and recompile, I'll show you a photo as attachment
Skorpion96 said:
It decompile stock recovery, add fastboot and recompile, I'll show you a photo as attachment
Click to expand...
Click to collapse
Ah ok, so when you're in fastbootd mode, you can just flash the partitions directly?
Skorpion96 said:
It decompile stock recovery, add fastboot and recompile, I'll show you a photo as attachment
Click to expand...
Click to collapse
In this picture, is this how fast boot d look like? Im scared flashing too good to be true stuff on my device, and even more scared that it works, and then when I try to flash soemthign thru it it break connection and gives me a hard brick
Arealhooman said:
In this picture, is this how fast boot d look like? Im scared flashing too good to be true stuff on my device, and even more scared that it works, and then when I try to flash soemthign thru it it break connection and gives me a hard brick
Click to expand...
Click to collapse
It is fastboot on my galaxy tab A7 Lite, you can enter by recovery, it will add the option
V0latyle said:
Ah ok, so when you're in fastbootd mode, you can just flash the partitions directly?
Click to expand...
Click to collapse
Yep
can i install on costume rom??