As some of you have already noticed, a couple of weeks ago @Dinolek and I published a utility, that allows bypassing authentication on MTK devices.
The tool is based on an exploit dubbed kamakiri, which was originally found by @xyz` and released for the Amazon FireTV Stick 4K (mantis)
What does this mean?
You can use this utility to bypass Serial Link Authentication and Download Agent Authentication on supported devices to use software such as SP Flash Tool to unbrick devices that would otherwise require authentication (AUTH-file).
The tool has since been expanded to support more SOCs by contributions from @viperbjk, @Rortiz2 and others.
It currently supports the following SOCs (and their variations):
mt6261
mt6572
mt6580
mt6582
mt6592
mt6595
mt6735
mt6737
mt6739
mt6750
mt6753
mt6755
mt6757
mt6761
mt6763
mt6765
mt6768
mt6771
mt6779
mt6785
mt6795
mt6797
mt6799
mt6833
mt6853
mt6873
mt6885
mt8127
mt8163
mt8167
mt8173
mt8590
mt8695
There are two parts to this project, the Utility itself and the Exploit Collection.
Please refer to the projects README how to set up your environment to use this utility successfully.
Please note, this project has already been incorporated in multiple commercial tools without even a mention.
This software is free to use, but the courtesy of at least mentioning the original authors is expected.
If you like this software and would like to support us, you can donate
reserved #1
reserved #2
Donated, fantastic work!
Nice work!
This will work on MTK devices that misconfigured on preloader, like this one:
Code:
MTK_SEC_CHIP_SUPPORT=yes
MTK_SEC_USBDL=ATTR_SUSBDL_ONLY_ENABLE_ON_SCHIP
MTK_SEC_BOOT=ATTR_SBOOT_ONLY_ENABLE_ON_SCHIP
MTK_SECURITY_SW_SUPPORT=yes
CUSTOM_SEC_AUTH_SUPPORT=no
Which means the phone was secured but no authentication file is generated, and impossible to revive without some sort of programmer back then. An example is Nokia 3.
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Yoss Roness said:
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Click to expand...
Click to collapse
Same! Spent days a few weeks ago trying to get around the authentication. Is it possible for MT6750?
Yoss Roness said:
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Click to expand...
Click to collapse
It depends, if the developers will have a device with the same soc or a device with a similar soc then it is possible that they port it, or even another person who is good at decompilers who wants to port can do it, you can also but you always depend on whether you can do it
Yoss Roness said:
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Click to expand...
Click to collapse
MT6762 should be the same as MT6761, so that should already be supported.
For unsupported devices you can try running the utility in testmode.
Code:
./main.py -t
If you can get a bootrom-dump, we can see what we can do about support.
k4y0z said:
MT6762 should be the same as MT6761, so that should already be supported.
For unsupported devices you can try running the utility in testmode.
Code:
./main.py -t
If you can get a bootrom-dump, we can see what we can do about support.
Click to expand...
Click to collapse
Can you create a guide on how to port (for noobs though)? I also have an unsupported device and would like to try porting.
XRed_CubeX said:
Can you create a guide on how to port (for noobs though)? I also have an unsupported device and would like to try porting.
Click to expand...
Click to collapse
I can't really create a porting guide.
As said, first step is to get a bootrom-dump.
This may be achieved using testmode.
What SOC do you have?
k4y0z said:
I can't really create a porting guide.
As said, first step is to get a bootrom-dump.
This may be achieved using testmode.
What SOC do you have?
Click to expand...
Click to collapse
MT8321
k4y0z said:
MT6762 should be the same as MT6761, so that should already be supported.
For unsupported devices you can try running the utility in testmode.
Code:
./main.py -t
If you can get a bootrom-dump, we can see what we can do about support.
Click to expand...
Click to collapse
I tried, but when I ran your command I recieved this error: Unable to create process using '/bin/python3
XRed_CubeX said:
MT8321
Click to expand...
Click to collapse
Did you try dumping bootrom using testmode?
Yoss Roness said:
I tried, but when I ran your command I recieved this error: Unable to create process using '/bin/python3
Click to expand...
Click to collapse
Please refer to the README how to set up python and libusb or use FireISO
XRed_CubeX said:
MT8321
Click to expand...
Click to collapse
Can't find a lot of info on MT8321, can you give more information what device this is?
k4y0z said:
Can't find a lot of info on MT8321, can you give more information what device this is?
Click to expand...
Click to collapse
Alcatel 3c
XRed_CubeX said:
Alcatel 3c
Click to expand...
Click to collapse
Any luck with testmode?
k4y0z said:
Any luck with testmode?
Click to expand...
Click to collapse
I haven't tried yet
firstly this is huge, soon enough we'll probably get rid of oems' dumb restrictions and paywalls for having permission over your own device but it doesnt work on my redmi note 8 pro global
it's just stuck on waiting for device, i've tried everything like cmd in admin, restarting, all the debug parameters, even class filters. i dont see mtk6785t but 6785 is there so i think that shouldnt be an issue? idk but any help would be great, i have the payloads in the payloads/ folder and the default_config.json5 file in the dir with main.py in it
i'm running it on a pc w ryzen 5 3600 so that could be why? i've checked the code it seems to just not find the serial port. if i should try on an intel cpu, how would i use it with a mac? because i dont have any other pcs. maybe through vm but i doubt that'd work. anyways amazing work just wait for someone to make a gui for it (maybe me but.. cries in tkinter) and it'll be an end to all the stupid oem stuff
again any help would be really appreciated i dont wanna get a realme or something just because i hate miui
wentaas said:
it's just stuck on waiting for device, i've tried everything like cmd in admin, restarting, all the debug parameters, even class filters. i dont see mtk6785t but 6785 is there so i think that shouldnt be an issue?
Click to expand...
Click to collapse
I don't know if mt6785 and mt6785t are the same.
If it doesn't even see your device your issue is something else.
Make sure your device is in bootrom-mode.
Related
SM-G389F Marshmallow Port for SM-G388F
Hello Everyone,
So we all know that the SM-G389F has Marshmallow as it's OS,
But when we look on the side of the SM-G388F, we still have Lollipop as it's OS, So I decided to port the OS version of the SM-G389F to the SM-G388F while configuring it to be compatible with it's hardware! :laugh:
I might need some help....
But we can start by Converting the Firmware Download to a Zip for the Custom Recovery to flash it
(Link to Download)
Thanks for Tuning in,
I will keep you all Updated soon! :fingers-crossed:
Hello Everyone,
I've wasted plenty of time trying to extract the SM-G389F Marshmallow Firmware but it was all for nothing. So now I am asking you all who own this device to flash the ROM link above using odin (https://www.sammobile.com/firmwares/galaxy-xcover3/SM-G389F/BTU/download/G389FXXS1APK1/114774/) and then creating a backup via TWRP including the system.img and the boot.img and sending it to me via Dropbox, Google Drive...
Anyway I would like to forgive myself for failing to do this operation without owning the phone because of the md5 protection, but now I will be leaving this part in your hands
Thanks in Advice,
Diamond26
For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.
Matt07211 said:
For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.
Click to expand...
Click to collapse
Thanks for including yourself in this thread!
But may I ask which device do you own please?
Diamond26 said:
Thanks for including yourself in this thread!
But may I ask which device do you own please?
Click to expand...
Click to collapse
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F
Matt07211 said:
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F
Click to expand...
Click to collapse
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!
Diamond26 said:
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!
Click to expand...
Click to collapse
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)
Matt07211 said:
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)
Click to expand...
Click to collapse
I just want to mess around with the ROM, maybe I could modify something!
PixelBoot said:
I just want to mess around with the ROM, maybe I could modify something!
Click to expand...
Click to collapse
Do what ever you want, you can still mess around a lot, you just can't transplant files from the value edition to the Normal edition.
There is some cool mods you can do if you modify system apks.
https://forum.xda-developers.com/showthread.php?t=2799050
Is this thread still up?
Rrrrrrx404 said:
Is this thread still up?
Click to expand...
Click to collapse
Thinking about it...
I was thinking the same thing… I have an old Xcover, so i just wanted to try…
Did you succeed?
Moderator note:
This is a test build. Flash at your own risk! Many things may not be working and you may encounter bootloop. Please do not flash if you don't know whast you're doing!
This is my first porting of a rom...be understanding
Requirements
- Bootloader Unlocked
- Recovery TWRP
Do a full wipe (data, system, dalvik and cache), flash MIUI 9 (Global Rom porting from Note 4 MTK) and enjoy it!
LINK
Anyone tried this ROM. Any bugs. Screenshots please.
I can t try because dont have this phone
fosseperme said:
This is my first porting of a rom...be understanding
Requirements
- Bootloader Unlocked
- Recovery TWRP
Do a full wipe (data, system, dalvik and cache), flash MIUI 9 (Global Rom porting from Note 4 MTK) and enjoy it!
LINK
Click to expand...
Click to collapse
Keep up tge good work. Im surprised this even happened.
fosseperme said:
This is my first porting of a rom...be understanding
Requirements
- Bootloader Unlocked
- Recovery TWRP
Do a full wipe (data, system, dalvik and cache), flash MIUI 9 (Global Rom porting from Note 4 MTK) and enjoy it!
LINK
Click to expand...
Click to collapse
Nice, i will try it
SkaboXD said:
Nice, i will try it
Click to expand...
Click to collapse
Have you tried it how's it?
Wilson Shrestha said:
Have you tried it how's it?
Click to expand...
Click to collapse
i Just downloaded it in night, didn't tried it yet
IT'S FAKE, GUYS!! He tried some random guide on the internet! He doesn't know what he's doing. He posted the same exact ROM for the Mi A1 and he bricked other people's devices. Please don't try this!
SkaboXD said:
i Just downloaded it in night, didn't tried it yet
Click to expand...
Click to collapse
I thought so since Nokia hasn't released its source codes yet.
I'm looking at the specs of the note4 mtk, and I see that the chipset is Mediatek MT6797 Helio X20.
I'm not sure that would work with the nokia 3
nicolasmart said:
IT'S FAKE, GUYS!! He tried some random guide on the internet! He doesn't know what he's doing. He posted the same exact ROM for the Mi A1 and he bricked other people's devices. Please don't try this!
Click to expand...
Click to collapse
Mi A1 has different partition scheme. The rom should work for Nokia and Mediatek.
Well, we will know is it real rom if someone flash it
SkaboXD said:
Well, we will know is it real rom if someone flash it
Click to expand...
Click to collapse
Someone crazy enough to flash this I'm not. And who cares about MIUI 9 when sweet Oreo is on the way.
fosseperme said:
Mi A1 has different partition scheme. The rom should work for Nokia and Mediatek.
Click to expand...
Click to collapse
Which method you used for porting this ROM?
SkaboXD said:
Which method you used for porting this ROM?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/development/guide-android-6-0-x-marshmallow-rom-t3373520
fosseperme said:
https://forum.xda-developers.com/android/development/guide-android-6-0-x-marshmallow-rom-t3373520
Click to expand...
Click to collapse
This is for 6.0, Nokia 3 have Android 7.0 and Androis 7.1.1. I think that it won't work. And also it is for MT65xx chipsets
fosseperme said:
https://forum.xda-developers.com/android/development/guide-android-6-0-x-marshmallow-rom-t3373520
Click to expand...
Click to collapse
Guys, I just got my hands on NK3(Nokia 3) today, hoping I will be able to do something for it soon.
AND regrading the quoted reply to link(guide) , I wrote that simple guide and it's not and never meant for porting Miui Roms.
FOR now, I have not tested the acclaimed Miui for NK3 , and as some says it's fake it might be true but to clear all doubts, someone should take the risk and try.
If I get free time too, I will try it personally to see.
iykeDROID™ said:
Guys, I just got my hands on NK3(Nokia 3) today, hoping I will be able to do something for it soon.
AND regrading the quoted reply to link(guide) , I wrote that simple guide and it's not and never meant for porting Miui Roms.
FOR now, I have not tested the acclaimed Miui for NK3 , and as some says it's fake it might be true but to clear all doubts, someone should take the risk and try.
If I get free time too, I will try it personally to see.
Click to expand...
Click to collapse
first of all thanks for the guide. I want to clarify that I drew inspiration not only from yours, but also from this http://www.osbusters.net/2015/11/how-to-port-miui-7-rom-to-qualcomm-smartphones.html, which is designed for processors qualcomm but that is fine in general and is based on a comparison of fstab files of the boot.img through the meld software.
fosseperme said:
first of all thanks for the guide. I want to clarify that I drew inspiration not only from yours, but also from this http://www.osbusters.net/2015/11/how-to-port-miui-7-rom-to-qualcomm-smartphones.html, which is designed for processors qualcomm but that is fine in general and is based on a comparison of fstab files of the boot.img through the meld software.
Click to expand...
Click to collapse
Please no matter what you do or can do, its not recommended to do use a number of peoples' device to test a project it your ain't certain.
in the previous replies, someone mentioned that you did same to Mi A1 which you got those devices bricked, please and please , its better you get a tester to test your stuffs for you than to push to publicc for all dudes to bricked thier device.
Remember, they used money to purchase the NK3.
Thanks.
Yeah completely hard bricked my phone I think, have to wait until I can be back with it to see if it is possible to unbrick it.
Seems like when I tried it earlier, it didn't even boot into the preloader....
Can anyone here see if https://forum.hovatek.com/thread-11836.html is possible?
Hi!
I would like to present you Android Boot Manager dualboot solution.
For now we have 4 work in progress devices:
Volla Phone
F(x)tec Pro 1/X
Moto G5
Galaxy S3 neo (nothing done yet)
Our wiki
Why new solution?
There is a lot of them already, such as: efidroid, multirom, dualboot patcher.
Now all of them are dead, because google implemented SAR, A/B, super partition.
We aim to support all that.
How it work?
ABM consists of 2 parts: bootloader and app+ sh scripts.
App with sh scriptes is used to install bootloader and add new roms.
Bootloader is used to display list of roms and load linux kernel with right dtb and optionally initrd.
What is used as BL:
Anything that can boot kernel. It coud be either 2nd stage bl, or in some cases even phones main bl.
For now:
Volla Phone (MTK's lk based bl)
F(x)tec Pro1/X (custom abl + uefi app)
Moto G5 and S3 neo (lk2nd)
Thanks to:
nift4 (Android app dev, co-creator of project)
LVGL team (GUI library)
lk (little kernel, used as bootloader on some platforms)
Fxtec (HW)
Volla (HW)
Reserved
Reserved#1
i am looking forward for your project ,Good work and hope if support come also for xiaomi poco F2 pro
bilalrajput said:
i am looking forward for your project ,Good work and hope if support come also for xiaomi poco F2 pro
Click to expand...
Click to collapse
It is possible, but i dont have that device.
What u need from my phone to do that,i think its very interesting,keep it up.Cheers!!!!
-CALIBAN666- said:
What u need from my phone to do that,i think its very interesting,keep it up.Cheers!!!!
Click to expand...
Click to collapse
What device, what soc?
I have a F(x)tec Pro1 ready for some stunts, I'm happy to serve as a test pilot as soon as I can find some instructions!
You call it Android Boot Manager. Does that mean it is made specifically to boot things that are based on Android, like Stock, AICPQ, LineageOS, or is that true for any ported OS that runs on libhybris with the Android kernel (plus some patches sometimes), like hybris-mobian, ArchARM, SFOS, etc.?
kewbak said:
I have a F(x)tec Pro1 ready for some stunts, I'm happy to serve as a test pilot as soon as I can find some instructions!
You call it Android Boot Manager. Does that mean it is made specifically to boot things that are based on Android, like Stock, AICPQ, LineageOS, or is that true for any ported OS that runs on libhybris with the Android kernel (plus some patches sometimes), like hybris-mobian, ArchARM, SFOS, etc.?
Click to expand...
Click to collapse
Hi!
Android Boot Manager will support Ubuntu touch, SFOS, and other too i hope. Currently i am working on fxtec bringup. I got gui in uefi already, tho lvgl have problems with font.
luka177 said:
What device, what soc?
Click to expand...
Click to collapse
Redmi 9,MTK Helio G80 64bit,Cheers!!!
Hi, now we have work in progress wiki https://www.wiki.abmanager.tech/index.php/Main_Page
We plan to implement no-bootloader-workaround that will work on devices without 2nd or 1st stage opesource bootloader. And we plan support for Das U-boot
Great news! I see that the Pro1 msm8998 is not listed among supported devices, but count me in as a tester as soon as it is. Curious if it would be possible to dualboot mainline + libhybris OSes too, but I reckon this would be difficult.
kewbak said:
Great news! I see that the Pro1 msm8998 is not listed among supported devices, but count me in as a tester as soon as it is. Curious if it would be possible to dualboot mainline + libhybris OSes too, but I reckon this would be difficult.
Click to expand...
Click to collapse
It is not listed as wiki is really WIP. And yes it will be possible to dualboot libhybris based OSes with mainline based.
how is the project going? think that your android boot manager will be a cool thing!!
Phitschhd said:
how is the project going? think that your android boot manager will be a cool thing!!
Click to expand...
Click to collapse
About 7 people have an working tripleboot on the Volla Phone
nift4 said:
About 7 people have an working tripleboot on the Volla Phone
Click to expand...
Click to collapse
that sounds cool...with A11?
Phitschhd said:
that sounds cool...with A11?
Click to expand...
Click to collapse
The Volla Phone has no Android 11 yet.
Strange... there is an post in my inbox that I can't see with the web ui?
oh ok that sounds cool..do you know if they are also working on an „universal“ solution for „all“ phones?
Click to expand...
Click to collapse
I am one of the developers, and well we are working on something easy to port, it isn't totally generic.
nift4 said:
Strange... there is an post in my inbox that I can't see with the web ui?
I am one of the developers, and well we are working on something easy to port, it isn't totally generic.
Click to expand...
Click to collapse
that‘s because i deleted the post. It was logic anyway that it will be (hopefully ) a universal solution, bc its also in the topic android development. But nice that you working on that! I also have Dualboot on my Poco F1 because the dev vasishath brought Multirom to this device.
Hi Luka,
any info on the progress of dualboot for the f(x)tec pro1 x? ABM would definetely be great for this device.
Hello everyone! I have owned this phone for going on 9 months now and I have had it rooted ever since I bought my SM-A315G but have tried countless times to port TWRP or just compile it myself. The outcome is inevitably failure... So I am reaching out to the world for help and any help that is received would be a blessing
Also when setting up the BoardConfig.mk file, how do you get the amounts for the variables BOARD_SUPER_PARTITION_SIZE, BOARD_GOOGLE_DYNAMIC_PARTITIONS_SIZE, BOARD_SUPER_PARTITION_ERROR_LIMIT?!?! I am lost!!
Also when setting up the BoardConfig.mk file, how do you get the amounts for the variables BOARD_SUPER_PARTITION_SIZE, BOARD_GOOGLE_DYNAMIC_PARTITIONS_SIZE, BOARD_SUPER_PARTITION_ERROR_LIMIT?!?! I am lost!!
[/QUOTE]
those thing are optional .. this is what happen if you follow a compiling guide from one source ...
i recommend compiling TWRP without changing parameter just to make sure you have properly setup your working directory
nwhitfield86 said:
Hello everyone! I have owned this phone for going on 9 months now and I have had it rooted ever since I bought my SM-A315G but have tried countless times to port TWRP or just compile it myself. The outcome is inevitably failure... So I am reaching out to the world for help and any help that is received would be a blessing
Click to expand...
Click to collapse
Hey man, this is going to make me sound like a d**k and I know this is where you ask the questions, but how did you root the A315G? I'm not an expert but I got one sitting round and thought I might put it to use, starting by rooting it.
Thread would be nice. Root, twrp.. anything
Bon7 said:
Thread would be nice. Root, twrp.. anything
Click to expand...
Click to collapse
I am hard at work right at this moment on this A31 project. Hopefully soon...
compiling TWRP from source is basically 50% installing TWRP system depedencies 50% reading stack overflow troubleshooting guide
you need to familiarize your self with terminal command like mkdir,ls,apt-get ..etc
ineedroot69 said:
compiling TWRP from source is basically 50% installing TWRP system depedencies 50% reading stack overflow troubleshooting guide
you need to familiarize your self with terminal command like mkdir,ls,apt-get ..etc
Click to expand...
Click to collapse
I'm no stranger to the Linux command line, I ran Ubuntu for nearly 5 years, but I am a stranger to rooting and flashing mobile devices.
6sxtc6 said:
I'm no stranger to the Linux command line, I ran Ubuntu for nearly 5 years, but I am a stranger to rooting and flashing mobile devices.
Click to expand...
Click to collapse
if im not misktaken i think ubuntu has pre installed adb so you can just type " man adb " or " adb -help " for it to show all the possible commands also for rooting Magisk is way togo
6sxtc6 said:
Hey man, this is going to make me sound like a d**k and I know this is where you ask the questions, but how did you root the A315G? I'm not an expert but I got one sitting round and thought I might put it to use, starting by rooting it.
Click to expand...
Click to collapse
Root with magisk
I have rooted my A31 with Magisk. There are lot of guides, you can scull in XDA. As bank and other applications wants none rooted devices. Though it is possible to hide root I do not want that. For. Other uses I have lenovo tab 8 FHD root etc.
hello everyone there is still no twrp for A31???
Gollo99 said:
hello everyone there is still no twrp for A31???
Click to expand...
Click to collapse
I'm trying to do it, but there is no help of anyone
ZModder said:
I'm trying to do it, but there is no help of anyone
Click to expand...
Click to collapse
create a telegram group and expand the community and help each other
ZModder said:
I'm trying to do it, but there is no help of anyone
Click to expand...
Click to collapse
I'll make a telegram group and send the link to join
Gollo99 said:
I'll make a telegram group and send the link to join
Click to expand...
Click to collapse
Better make an Discord One, also XDA doesn't allow external links
ZModder said:
Better make an Discord One, also XDA doesn't allow external links
Click to expand...
Click to collapse
the twrp you did is working now? or what is missing to make it work?
Gollo99 said:
the twrp you did is working now? or what is missing to make it work?
Click to expand...
Click to collapse
Nope, {Mod edit}
I was thinking on making a Device Tree based on the A32x one
ZModder said:
Nope, {Mod edit}
I was thinking on making a Device Tree based on the A32x one
Click to expand...
Click to collapse
A32 already has twrp, only A31 is missing
Gollo99 said:
A32 already has twrp, only A31 is missing
Click to expand...
Click to collapse
Refresh: The most similar Device I found is A41, still searching
Hi! Has anyone tried to flash a GSI rom on Xiaomi 13? If yes how does it work?
Thanks in advance
Currently there is no GSI working on this model AFAIK. Wait for device specific ports instead.
---
EDIT: This is not true. See the replies below.
rikumi said:
Currently there is no GSI working on this model AFAIK. Wait for device specific ports instead.
Click to expand...
Click to collapse
Thank you for answer, I hope they'll arrive soon
what is important is the architecture not the model
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
NOSS8 said:
what is important is the architecture not the model
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Have you tried any of these? Does it works on Xiaomi 13? Thank you in advance
Nope, I don't install gsi rom on my devices.
Snapdragon 8 Gen 1/2 ARM64(V9) - X86.
GSI on Xiaomi 12 Pro
after testing several Treble GSis, I finally found CherishOS. Most of them are not booting, or other issues (no mobile data, only calling, settings are crashing,....). Save your time and choose CherishOS. How I flashed it: 1. clean flash...
forum.xda-developers.com
They may have others with less bugs or updates.
NOSS8 said:
Nope, the does not install gsi rom on my devices.
Snapdragon 8 Gen 1/2 ARM64(V9) - X86.
GSI on Xiaomi 12 Pro
after testing several Treble GSis, I finally found CherishOS. Most of them are not booting, or other issues (no mobile data, only calling, settings are crashing,....). Save your time and choose CherishOS. How I flashed it: 1. clean flash...
forum.xda-developers.com
They may have others with less bugs or updates.
Click to expand...
Click to collapse
It seems that there are a lot of problems unfortunately yet... however thank you very much!
saluzzo997 said:
It seems that there are a lot of problems unfortunately yet... however thank you very much!
Click to expand...
Click to collapse
As written above, do research on devices with the same soc, One plus, Samsung etc.
There are surely some with little or no bug.
NOSS8 said:
As written above, do research on devices with the same soc, One plus, Samsung etc.
There are surely some with little or no bug.
Click to expand...
Click to collapse
Thank you!
I am using Project elixir for almost 2 weeks now. So far so good.
I suggest you dont flash it but instead usi it via DSU. Autobrightness is not working, fingerprint too. There are gcam ports wich are also compatible with our device. Battery life is better than miui. Even adding a card to google wallet works fine, until a reboot.
Lhunar said:
I am using Project elixir for almost 2 weeks now. So far so good.
I suggest you dont flash it but instead usi it via DSU. Autobrightness is not working, fingerprint too. There are gcam ports wich are also compatible with our device. Battery life is better than miui. Even adding a card to google wallet works fine, until a reboot.
Click to expand...
Click to collapse
Sorry but what do you mean with "use it via DSU"? What does DSU mean? Is there a tutorial for it? Thank you in advance!
saluzzo997 said:
Sorry but what do you mean with "use it via DSU"? What does DSU mean? Is there a tutorial for it? Thank you in advance!
Click to expand...
Click to collapse
You shouldve just used google to understand better. But basically its a subsystem method wich was implemented to allow a/b partition devices to be able to run gsis' for testing purposes, without the need of flashing and deleting the original os. Think of it as dualboot for android. The only thing is that if you're using it via dev settings, you dont have the choice of selecting what to boot, but your device will directly download google's official gsi (wich is not very functional and its ugly).
Thats why you just need to download the DSU Sideloader app from PlayStore. The app will do everything with a gsi of your choice if you follow the instructions.
The only thing wich is mandatory is that the BL of your device must be unlocked in order to use dsu.
There are videos on YT showing this. If you want to try the gsi I mentioned, download it from their website.
Lhunar said:
You shouldve just used google to understand better. But basically its a subsystem method wich was implemented to allow a/b partition devices to be able to run gsis' for testing purposes, without the need of flashing and deleting the original os. Think of it as dualboot for android. The only thing is that if you're using it via dev settings, you dont have the choice of selecting what to boot, but your device will directly download google's official gsi (wich is not very functional and its ugly).
Thats why you just need to download the DSU Sideloader app from PlayStore. The app will do everything with a gsi of your choice if you follow the instructions.
The only thing wich is mandatory is that the BL of your device must be unlocked in order to use dsu.
There are videos on YT showing this. If you want to try the gsi I mentioned, download it from their website.
Click to expand...
Click to collapse
Thank you very much for your explanation and sorry to have asked to you what DSU was, I just wanted to be sure that we were talking about the same thing, I'll give it a try!
saluzzo997 said:
Thank you very much for your explanation and sorry to have asked to you what DSU was, I just wanted to be sure that we were talking about the same thing, I'll give it a try!
Click to expand...
Click to collapse
No problem, I dont mind explaining, but there are pretty detailed articles, wich may enlighten you better than I can do it. Anyways, if/when you try it you'll really understand how much MIUI is ruining the experience of that pretty device. I was thinking about selling it 3 days after i got it, only because of that deprecated UI with stupid restrictions. I'm really glad i searched and tried stuff. Good luck!
Lhunar said:
No problem, I dont mind explaining, but there are pretty detailed articles, wich may enlighten you better than I can do it. Anyways, if/when you try it you'll really understand how much MIUI is ruining the experience of that pretty device. I was thinking about selling it 3 days after i got it, only because of that deprecated UI with stupid restrictions. I'm really glad i searched and tried stuff. Good luck!
Click to expand...
Click to collapse
Thank you very much, I hate MIUI too and I was doing the same thing selling this awesome phone because of that, thank you again!
Lhunar said:
No problem, I dont mind explaining, but there are pretty detailed articles, wich may enlighten you better than I can do it. Anyways, if/when you try it you'll really understand how much MIUI is ruining the experience of that pretty device. I was thinking about selling it 3 days after i got it, only because of that deprecated UI with stupid restrictions. I'm really glad i searched and tried stuff. Good luck!
Click to expand...
Click to collapse
Hi, sorry if I bother you, I've just tried with project elixir GSI using DSU sideloader, but I don't know why when I restart by clicking on notification it doesn't even boot on my GSI... I've installed the sideloader as root installation... I don't know why it's not working...
saluzzo997 said:
Hi, sorry if I bother you, I've just tried with project elixir GSI using DSU sideloader, but I don't know why when I restart by clicking on notification it doesn't even boot on my GSI... I've installed the sideloader as root installation... I don't know why it's not working...
Click to expand...
Click to collapse
Well I'm not using root. I gave permissions via adb and i have no problems. What rom chinese or global ? or maybe you're using something custom like xiaomi eu?
Lhunar said:
Well I'm not using root. I gave permissions via adb and i have no problems. What rom chinese or global ? or maybe you're using something custom like xiaomi eu?
Click to expand...
Click to collapse
Yeah, I'm on EU
saluzzo997 said:
Yeah, I'm on EU
Click to expand...
Click to collapse
Thats your problem. When I tried this on eu it wasnt working.
Lhunar said:
Thats your problem. When I tried this on eu it wasnt working.
Click to expand...
Click to collapse
Oh...what a bad luck... thank you very much for your help