Hello, guys. Because there are some ROM's for Poco F1 and, due to our lack of OEM ports (such as OxygenOS v11, MIUI 13 S and MyUI v4 S) on Mi 8, I have made some patches which fix almost all the bugs.
Which of them are not fixed
-> NFC
-> Dual GPS, but normal one works fine
-> AOD, because developers for Poco F1 have removed it from system
What does this patch do
Based on proprietary-files.txt from dipper's device tree, these patches replace some vendor files, which are responsible for bugs, such as camera, sound and sensors issues.
OK, then. So, how to flash a Poco ROM on Mi 8?
The steps are quite simple:
1) We download and we unpack a ROM made for Poco F1
2) We flash system.img, vendor.img, cust.img (or system_ext.img as cust) and boot.img as images
3) We flash DFE (optional), beryllium2dipper-patch (for Ignition 4.0 the specific one, otherwise the common one), permissiver and a custom kernel (personally, I prefer either No Gravity or LawRun) which does not support system_ext
And we are done
Possible questions:
1) I cannot flash cust.img from my custom recovery
OrangeFox stable recovery supports cust/system_ext, so this image can be flashed by using this recovery. Otherwise, we can use fastboot (fastboot flash cust cust-or-system_ext.img)
2) Sudden reboot after flashing the patch
Only after the first time, there will be no sudden reboots after the second reboot
3) There are no ROM's which can be booted by following this guide
Well, if coming either from an encrypted ROM or from a ROM which supports system_ext (or both), formatting data is required
4) Can this guide and patch be used on every ROM made for Poco F1?
Sure, if they are not AOSP ROM's and if custom kernels are supported
I hope it helps
hello dear developer, we are doing everything smoothly for dipper, but there is constant reboot, how can we solve this
Are you on Ignition 4.0/5.0 or on MIUI Mind?
If so, these ROM's cannot be booted, anymore (there are bootloops on Poco F1, too). This happens due to Google's security patch, so I don't know whether there is a solution for this or not. Other more advanced developers are trying to fix it without promising anything.
If not, I will make another patch without proprietary files for NFC.
Related
First question is the title basically, wanna flash miui if i happen to not like PE. Can i flash it with twrp?
Second question, If I flash PE without any custom kernels. And flash miui after that. Will i have my original kernel? Or does flashing custom roms change to a custom kernel?
Sorry a bit new to this. Thanks for your time.
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
csleo17 said:
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
Click to expand...
Click to collapse
What is rom recovery package?
thanks for your time man
ParsaMrrelax said:
What is rom recovery package?
thanks for your time man
Click to expand...
Click to collapse
Android devices predominantly followed by following partitions!
/system
/boot
/recovery
/vendor
/storage
/persist
/ta (in xperia)
/overlay (optional)
now RECOVERY (beside parition name) refers to a operating system DESIGNED ONLY to change size of these partitions (ADVANCE) and basic need to spread out(FLASH) operating system according to command by package in certain partitions. -- TWRP is one OUTSTANDING Recovery project over the years. back in old days Philztouch recovery was also popular for Xperia models-
the term "rom recovery package" means, READ ONLY MEMORY ( a android operating system File ) Designed for RECOVERY TO READ and spead the data in /system + / boot & /data partitions for your Poco (or any android based) for boot in to android operating system.
MIUI mainly releases TWO filetypes of SAME ROMS , for example miui10.3.6 has
1. RECOVERY ROM (1.6gb) (to be flashed by TWRP
2. FASTBOOT ROM (2.8gb) which can be flashed by FLASHER running on WINDOWS based System (some times iMac too)
3. Android devices uses many types of processor, SNAPDRAGON processors are famouss (poco uses Snapdragon or SD845) hence Two type of Flashers can be USED to FLASH POCO, 1 MI FLASH (RECOMENDED) (supports Two Mods, on fastboot rom, fastboot & EDL) or QUALCOMS QLOADER flasher (ADVANCE and NOT RECOMENDED)
coming back to twrp,
all custom roms are designed keeping in mind that RECOVERY (such as TWRP) will be FLASHING it on ANDROID DEVICE. so the sequence of flashing such roms are like
1. flashing vendor firmware , from a. vendor firmware , download from https://mirror.akhilnarang.me/MIUI/b...r-firmware.zip
b. flashing pixel experience ROM ( you should also try Crdroid and Havoc)
c. flashing google apps from openapps.org (take arm64>android9.0>MICRO package and hit download) 250+mb filesize
d. (optional) optimus drunk kernel (check development forum for post)
e. flashing magisk18.3.zip (if you want your Device to WAKEUP ROOTED)
now answering you question
1. YES YOU CAN TOGGLE BETWEEN MIUI AND CUSTOM ROMS, but don't make it habit! there is always chance for you to BRICK your device. also you will loose all your data if MIUI uses Encryption method which TWRP cannot READ to operate /data partition. then you must RE FORMATE /data partition via twrp in order to make it accesable for custom rom(s)
2.ANY TIME WHEN TWRP FLASH ANY ROM, MIUI OR ANY CUSTOM ROM, THE OLD KERNEL IS OBSOLETE AND NEW ONE IS PLACED thats why you need to flash magisk everytime you clean flash any rom in order to get root access
please do ask if you need any clarification
might be a old thread.
but i installed a custom rom on my moms phone but i thinking going back to stock. the custom rom is old and has scroll problems...
but i see stable miui has no updates. but can i flash official miui rom from twrp over the custom lingeos rom?
or is it better to update her phone to a more recent custom rom.
either way she will lose her data. plus camera has bugs but i never had the time with work and she working to put it back in a mint working state. cause the scrolling being broking is fuking stupid
tought about miui stable. just to flash it true trwp.
or update it to a more recent custom rom.
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
nasos_Gr said:
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Click to expand...
Click to collapse
Miui decided to use MODIFIED VENDOR IMAGE hence POCO F1 gets a modified vendor image for Android Pie-based Project Treble GSIs
what was the impact?
custom roms couldn't be flashed (booted) if you don't flash the modified vendor image from twrp
even today when most of the roms have their own vendor you still need to flash the vendor+firmware (atleast)
Developer Akhil Narang started collecting all releases at
https://mirror.akhilnarang.me/MIUI/beryllium/
currently I am using 9.6.27-9.0 which is working best for me, 10.3.6 image made my batter drainage high (atleast i noticed)
I am on HAVOC2.8 and this is how i did it
1. flashed TWRP 3.3.1 unofficial (download it from HERE ) ref Reference - as official twrp has TOUCH driver issues. this one worked with me very well
2. I wiped /data, /system then
3. flashed VENDOR.zip from HERE
4. FLASHED CUSTOM ROM (i use HAVOC2.8)
5. FLASHED DFE HERE - REFERENCE
6. FLASHED GOOGLE APPS ( GAPPS.ORG) ( ARM64>9.0MicroPackage)
7. Flash Kernel ( OPTIONAL- havoc uses shadow kernel , i feel optimus drunk kernel is better, battery and 4g connectivity) even Franco Kernel is very good
8. FLASHING MAGISK19.3
9. when i was on havoc2.7, by using MIGRATE, it made flashable zip of my APPS+DATA, stored in internalStorage, and now I will FLASH that file., Mine size goes to 2gb you can get it from HERE
10. WIPE CACHE/DELVIK
11. REBOOT
fire reboot may go in to bootloop and then second reboot may take a while and finally you should see Pixel Setup asking google accounts and info etc
-----------------------
extraa
once after you finish setup! don't RESTORE APPS from PLAYSTORE, (download only license apk, in my case I have purchases many apps from playstore and saperate license info is always appear in intial setup! SELECT THOSE ONLY)
ONCE playstore is DONE downloading all your selected (fewer) apps, and MAGISK ROOT is working...... put device on AIRPLANE MODE
FROM DROP DOWN Notification panel, CLICK MIGRATE, and it will prompt you what do you wana restore from your previouce ROM to newly flashed HAVOC ..APPS+SETTINGS+PERMISSION+DATA etc - migrate restoration may take upto 30 mins,
once done, uninstall from system and reboot device!
REMEMBER I DONOT RECOMEND MIGRATE TRICK FOR WHATSAPP, it doesn't work properly and NOTIFICATION ISSUES with BLANK DP observed by me whenever I forcely re-instated whatsapp by migrate!
Martensite said:
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
Click to expand...
Click to collapse
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
nasos_Gr said:
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
Click to expand...
Click to collapse
Flashing custom roms will not wipe anything, so the vendor is still there. And firmwares too.
Hi devs ...
I had a small question which was bothering me. I wanted to know that , if I flash custom roms and custom kernels frequently will it exhaust the hardware and battery ?
Sincerely,
A pocophone user .
Seriously, no. But do read up on what you need to do to flash custom roms and custom kernels.
htramas said:
Hi devs ...
I had a small question which was bothering me. I wanted to know that , if I flash custom roms and custom kernels frequently will it exhaust the hardware and battery ?
Sincerely,
A pocophone user .
Click to expand...
Click to collapse
depends which custom kernel you are using? if you see a novoice developer experimenting with certain stuff in the kernel of your device, you should not be trying. or atleast proceeding with cautions!
however poco f1 is old device now, and we have definate winners where custom kernels are concerns!
Franco / Twisted loop / malakas / Optimus Drunk / Arter (no sound mod) / and shadow kernel are good ones!
i usually stick to Optimus Drunk
but if you feel touch issues then Try Twisted kernel as developer keeps 3 versions updated based on touch drivers
YasuHamed said:
depends which custom kernel you are using? if you see a novoice developer experimenting with certain stuff in the kernel of your device, you should not be trying. or atleast proceeding with cautions!
however poco f1 is old device now, and we have definate winners where custom kernels are concerns!
Franco / Twisted loop / malakas / Optimus Drunk / Arter (no sound mod) / and shadow kernel are good ones!
i usually stick to Optimus Drunk
but if you feel touch issues then Try Twisted kernel as developer keeps 3 versions updated based on touch drivers
Click to expand...
Click to collapse
I more into gaming so I was thinking of flashing seshtation kernel
guhvanoh said:
Seriously, no. But do read up on what you need to do to flash custom roms and custom kernels.
Click to expand...
Click to collapse
Okay thanks for letting me know but yeah I'm aware of flashing lil bit .
htramas said:
I more into gaming so I was thinking of flashing seshtation kernel
Click to expand...
Click to collapse
yes but double check which Screen Refresh rate performs well for u
there are 3 versions! some users reports screen hanging on 66hz
also keep in mind,
Kernel <---> your choice of CUSTOM ROM <------> vendor+ Firmware combination
has different results for two different users using SAME kernel version/type
vendor+fw of 9.6.27-90 is very stable of last old days from miui9.6 and uptill now supported by final version of android9 roms!
however since every custom rom has now their own VENDOR embeded, so whats left is Firmware
for me (OD kernel + crdroid5.10 (android9) + fw miui10.3.8) gives higher battery drain as compare to fw9.6.27-90 but if i remove OD kernel to Twisted Loop, same vendor works just fine, this mean OD kernel has hight batter drain.
and if on OD kernel i switch to fw9.6.27-9.0, i get better temperature and SOT..
so you try your combination and you will come to know only with time! no one can assure which combo or trio will work for u!
REMEMBER always flash DFE (disable Force Encryption Global, Poco f1 (Treble) IF you ever later change vendor/fw OVER the installed/flashed ROM in Twrp because this way encryption keys in vendor will change and device will loose access to storage and you will get bootloops and later you will have to format your ALL partitions (data lost) in order to gain access of internal storrage on NEW keys of Flashed vendor by you...
however remember DFE is unsafe because it means your deice is no more encrypted and if ever lostor stolen , a well known android user may gain access to your data... so keeping security on screen lock, (finger print or pattern) is recomended but you need to remove pattern if you ever wana flash anything again in next boot ... as Twrp can ask pin but cannot ask pattern (not to my knowledge)
useful links
https://mirror.akhilnarang.me/MIUI/beryllium/ (no updates since aug19)
MOD EDIT: Link Removed (latest fw and/or vendor and/or fw+vendor combine zips found here)
YasuHamed said:
yes but double check which Screen Refresh rate performs well for u
there are 3 versions! some users reports screen hanging on 66hz
also keep in mind,
Kernel <---> your choice of CUSTOM ROM <------> vendor+ Firmware combination
has different results for two different users using SAME kernel version/type
vendor+fw of 9.6.27-90 is very stable of last old days from miui9.6 and uptill now supported by final version of android9 roms!
however since every custom rom has now their own VENDOR embeded, so whats left is Firmware
for me (OD kernel + crdroid5.10 (android9) + fw miui10.3.8) gives higher battery drain as compare to fw9.6.27-90 but if i remove OD kernel to Twisted Loop, same vendor works just fine, this mean OD kernel has hight batter drain.
and if on OD kernel i switch to fw9.6.27-9.0, i get better temperature and SOT..
so you try your combination and you will come to know only with time! no one can assure which combo or trio will work for u!
REMEMBER always flash DFE (disable Force Encryption Global, Poco f1 (Treble) IF you ever later change vendor/fw OVER the installed/flashed ROM in Twrp because this way encryption keys in vendor will change and device will loose access to storage and you will get bootloops and later you will have to format your ALL partitions (data lost) in order to gain access of internal storrage on NEW keys of Flashed vendor by you...
however remember DFE is unsafe because it means your deice is no more encrypted and if ever lostor stolen , a well known android user may gain access to your data... so keeping security on screen lock, (finger print or pattern) is recomended but you need to remove pattern if you ever wana flash anything again in next boot ... as Twrp can ask pin but cannot ask pattern (not to my knowledge)
useful links
https://mirror.akhilnarang.me/MIUI/beryllium/ (no updates since aug19)
MOD EDIT: Link Removed (latest fw and/or vendor and/or fw+vendor combine zips found here)
Click to expand...
Click to collapse
Do you have any suggestions for gaming kernels and roms because i want extract the full potential of poco without putting much pressure on battery .
htramas said:
Do you have any suggestions for gaming kernels and roms because i want extract the full potential of poco without putting much pressure on battery .
Click to expand...
Click to collapse
to my knowledge Malakas kernel is recomended by some users in Telegram groups but seshtation is popular,
I think you should try both on two+ custom roms! , Carbon ROM i would say! its very clean! no VENDOR embeded! so u need to flash your vendor+fw
YasuHamed said:
to my knowledge Malakas kernel is recomended by some users in Telegram groups but seshtation is popular,
I think you should try both on two+ custom roms! , Carbon ROM i would say! its very clean! no VENDOR embeded! so u need to flash your vendor+fw
Click to expand...
Click to collapse
What do you mean by vendor and fw can you explain and tell me how to flash ? Btw i was thinking of flashing pixel experience + or crdroid with seshstation for gaming and yeah i want to try carbon rom after you tell me how to flash.
htramas said:
What do you mean by vendor and fw can you explain and tell me how to flash ? Btw i was thinking of flashing pixel experience + or crdroid with seshstation for gaming and yeah i want to try carbon rom after you tell me how to flash.
Click to expand...
Click to collapse
this is what i understood
in android there are following partitions (to my knowledge)
/oem
/data
/system
/boot
/recovery
/storage
/vendor
oem paritition has binaries library to read and translate android and execute command. since android 8.1 these binaries changed to different language. what you flash in poco in this partition is called firmware its usually 100mb of binaries to be flashed either by fastboot or better via twrp if its in flashable zip
/vendor parition has standard format and information about device's hardware for android to access device hardware
in all other mobiles in xaiomi tree, Poco was the FIRST ONE to be released with MODIFIED VENDOR IMAGE from Xiaomi, this means
-while flashing custom rom if you didn't flash vendor (400mb zip file do be downloaded from the links i gave above) , your device will bootloop only! because custom roms arent carrying standard android vendor format file to support device hardware for POCO. so all custom roms depending on users to download and flash vendor saperately!
however since JULY2019, almost all android 9 custom roms started carrying atleast one supported MODIFIED version of Vendor embeded in the zip file of of Pixel Experience, crdroid, havoc, mokee, lineage, xtended, Aosip etc etc, where PE carries Google Apps also so the PE is 1.3gb zip file! where all others are 800mb. (which used to be 400+mb pre july2019)
Carbon rom still don't carry vendor and expect user to flash vendor saperately
PROs /CONS
- when vendor was saperate, jumping from Crdroid to havoc to xtended to aosip to mokee to linage was easier becuase ONCE you flash vendor 9.6.27-9.0 (for say) any custom rom never touches that, and you never get encyption error at boot and you never LOOSE your data
-but when you flash different vendor lets say 10.3.8 version, it will definately change your encryption keys in vendor and you will be locked out in your next boot - if you didnt flash DFE
- post july2019, all roms have some vendor image embeded to everytime you flash or jump from crdroid to havoc to xtended etc etc, your vendor parition will be flashed prior to system partition and you MUST flash DFE now (as explained above)
now why xiaomi did this? well all i read to support Project treble (i don't know much about it )
when i had Redmi note 5pro, the vendor image was standard and i used to change sound files for max boost! but on poco i need kernel auiditor to increase volume which for me its still low for me to enjoy music
YasuHamed said:
this is what i understood
in android there are following partitions (to my knowledge)
/oem
/data
/system
/boot
/recovery
/storage
/vendor
oem paritition has binaries library to read and translate android and execute command. since android 8.1 these binaries changed to different language. what you flash in poco in this partition is called firmware its usually 100mb of binaries to be flashed either by fastboot or better via twrp if its in flashable zip
/vendor parition has standard format and information about device's hardware for android to access device hardware
in all other mobiles in xaiomi tree, Poco was the FIRST ONE to be released with MODIFIED VENDOR IMAGE from Xiaomi, this means
-while flashing custom rom if you didn't flash vendor (400mb zip file do be downloaded from the links i gave above) , your device will bootloop only! because custom roms arent carrying standard android vendor format file to support device hardware for POCO. so all custom roms depending on users to download and flash vendor saperately!
however since JULY2019, almost all android 9 custom roms started carrying atleast one supported MODIFIED version of Vendor embeded in the zip file of of Pixel Experience, crdroid, havoc, mokee, lineage, xtended, Aosip etc etc, where PE carries Google Apps also so the PE is 1.3gb zip file! where all others are 800mb. (which used to be 400+mb pre july2019)
Carbon rom still don't carry vendor and expect user to flash vendor saperately
PROs /CONS
- when vendor was saperate, jumping from Crdroid to havoc to xtended to aosip to mokee to linage was easier becuase ONCE you flash vendor 9.6.27-9.0 (for say) any custom rom never touches that, and you never get encyption error at boot and you never LOOSE your data
-but when you flash different vendor lets say 10.3.8 version, it will definately change your encryption keys in vendor and you will be locked out in your next boot - if you didnt flash DFE
- post july2019, all roms have some vendor image embeded to everytime you flash or jump from crdroid to havoc to xtended etc etc, your vendor parition will be flashed prior to system partition and you MUST flash DFE now (as explained above)
now why xiaomi did this? well all i read to support Project treble (i don't know much about it )
when i had Redmi note 5pro, the vendor image was standard and i used to change sound files for max boost! but on poco i need kernel auiditor to increase volume which for me its still low for me to enjoy music
Click to expand...
Click to collapse
Thanks for the info btw can I uninstall kernel manager after setting the CPU and GPU frequencies?
htramas said:
Thanks for the info btw can I uninstall kernel manager after setting the CPU and GPU frequencies?
Click to expand...
Click to collapse
only if you set boot.sh script otherwise you need to keep it so that on eveyr boot it applies the values
i recomend smart pack kernal manager
https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
YasuHamed said:
only if you set boot.sh script otherwise you need to keep it so that on eveyr boot it applies the values
i recomend smart pack kernal manager
https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
Click to expand...
Click to collapse
I installed smart pack but it was stuck on white screen.
htramas said:
I installed smart pack but it was stuck on white screen.
Click to expand...
Click to collapse
when was that? two days ago got new update , you should try! i am using it for many months now! its best!
another option its to buy Franco.app
YasuHamed said:
when was that? two days ago got new update , you should try! i am using it for many months now! its best!
another option its to buy Franco.app
Click to expand...
Click to collapse
I tried it today
It just shows this
htramas said:
It just shows this
Click to expand...
Click to collapse
THIs probably means magisk is not allowing it (supersu rights)
can you check magisk is properly installed? and you have root access ?
YasuHamed said:
THIs probably means magisk is not allowing it (supersu rights)
can you check magisk is properly installed? and you have root access ?
Click to expand...
Click to collapse
Yes it does have rootaccess and magisk is properly installed . Sidenote : I installed Franco kernel app.
In the developer options I have started uploading the GSI ARM64 dynamic system.
I was quite surprised by the possibility.
I'm on Miui Global 12.5.2.0 and AOSP Android 12 was loaded into the second slot automatically and without selection.
Starting the function started the upload and after the upload the prompt to reboot into the other system remained in the top bar.
The reboot went without problems and loaded the AOSP ROM Android 12 in a clean basic environment.
The top bar continued to hold a link to reboot back into Miui.
I returned to a pristine and fully functional Miui system (including settings and data).
The top bar still held a link to reboot into AOSP or remove it. I removed it.
This means that our phone can run two independent systems, one in slot "A" and one in slot "B". These are not virtual slots, but physical slots.
This could be relevant to building recovery.
I can confirm that. figured that's before.
Steps on booting the Android 12 on DSU? I'm using pixel experience and I tried to load the PB4 on DSU but it boots me into an android 11 environment. Does it only work on stock rom?
It could be related to the 12.5.2.0 update.
Presumably the vendor and others will be ready for Android 12.
The firmware package does not include the vendor file, it is obtained by installing the entire Miui ROM or by extraction. Firmware is therefore not enough for change.
StaryMuz said:
It could be related to the 12.5.2.0 update.
Presumably the vendor and others will be ready for Android 12.
The firmware package does not include the vendor file, it is obtained by installing the entire Miui ROM or by extraction. Firmware is therefore not enough for change.
Click to expand...
Click to collapse
i think it only works on stock rom. I installed 12.0.11 and used the DSU loader there. worked fine but the side mounted fingerprint sensor gets treated as a touch input. Could be the custom rom doesn't have the proper dsu config and stuff? Havent tried yet on xiaomi.eu
A little experiment:
I switched in Miui 12.5.2.0 using DSU Loader to GSI ROM. From developer.android.com I downloaded the Android 11 GSI ZIP and took the vbmeta.img from it. Then he downloaded IMG for Lineage OS 18.1 GSI from XDA. I switched the phone to fastboot and flash files (fastboot flash vbmeta vbmeta.img); (fastboot -w flash system system.img); fastbootD is required for system.img. Without deleting anything, I booted the system and Lineage OS 18.1 Treble works.
It's GSI so it's not fine-tuned for our phone, but it works for the vast majority of what's possible. Including fast charging, which detects after a while. For now, the camera is working as well.
A bit complicated, but Lineage OS 18.1 GSI was possible to install. The flash system.img (GSI) itself is not functional. I suppose any GSI system could be run this way.
Generic System Image releases | Platform | Android Developers
developer.android.com
Reverting to the default Miui is no longer available. It would have to be re-flashed.
inn000 said:
Steps on booting the Android 12 on DSU? I'm using pixel experience and I tried to load the PB4 on DSU but it boots me into an android 11 environment. Does it only work on stock rom?
Click to expand...
Click to collapse
Going now to crDroid and I tried running the DSU Loader.
After downloading and selecting reboot to GSI, I reloaded crDroid in the version with android 11.
But the GSI download was version SPB4.210715.014, which is Android 12.
As I found out, it's a GSI version of Android supplied by the Android developer to test and validate new apps.
The fact that Android 12 was not loaded, but again only crDroid Android 11 is related to the fact that our custom ROMs cannot work with the activation of the second slot (A/B).
This is also why OTA updates (running on the system) do not work properly.
For this update you need to automatically switch the active slot, which will not happen! This will cause the OTA update to fail.
Resolving the ability of custom boot.img to work with fastbootD commands can probably fix the problem with the broken OTA.
So far, switching to GSI only works on Miui.
StaryMuz said:
Going now to crDroid and I tried running the DSU Loader.
After downloading and selecting reboot to GSI, I reloaded crDroid in the version with android 11.
But the GSI download was version SPB4.210715.014, which is Android 12.
As I found out, it's a GSI version of Android supplied by the Android developer to test and validate new apps.
The fact that Android 12 was not loaded, but again only crDroid Android 11 is related to the fact that our custom ROMs cannot work with the activation of the second slot (A/B).
This is also why OTA updates (running on the system) do not work properly.
For this update you need to automatically switch the active slot, which will not happen! This will cause the OTA update to fail.
Resolving the ability of custom boot.img to work with fastbootD commands can probably fix the problem with the broken OTA.
So far, switching to GSI only works on Miui.
Click to expand...
Click to collapse
yep only works on stock miui loader. sgsi systems works too, I used pixel 5 pb4 sgsi and it works better than the one on stock miui dsu. the same problems still exists. Audio, power button, etc.
inn000 said:
yep only works on stock miui loader. sgsi systems works too, I used pixel 5 pb4 sgsi and it works better than the one on stock miui dsu. the same problems still exists. Audio, power button, etc.
Click to expand...
Click to collapse
Sorry to bring this up again, but what is SGSI ? What does the "S" stand for
Tested on my Mi Pad 5 Pro 12.4"(dagu) using elish's ROM.
Step to install:
1. Download FastbootEnhance.
2. Download ArrowOS ROM (Xiaomi/elish), and unzip it. There should be a payload.bin inside.
As elish (Mi Pad 5 Pro) and dagu (Mi Pad 5 Pro 12.4") uses the same SoC, it should be fine. But still, unverified if further problems occurs.
3. Either backup the boot and vendor_boot, or download a stock firmware and extract from it.
小米社区
web.vip.miui.com
4. Under fastbootd (fastboot boot fastboot), use FastbootEnhance to flash the payload.bin.
5. Re-enter to fastbootd, use
Code:
fastboot flash boot boot_stock.img
to flash the boot img back to the vendor one.
6. fastboot reboot, and then unplug the cable.
Then, fastboot reboot. And the ArrowOS should boot.
Current issue:
camera not working
NOTE:
not sure if
fastboot --disable-verity --disable-verification flash vbmeta_ab vbmeta.img
is needed
What do you think are the major changes now with the ArrowOS?
CauAguiar said:
What do you think are the major changes now with the ArrowOS?
Click to expand...
Click to collapse
I just found that the UI and overall experience is better than LineageOS.
And also the Pad is on the official support list of ArrowOS.
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
spacezmonkey said:
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
Click to expand...
Click to collapse
Same for me. Tried TrebleApp, using
Code:
am start -n me.phh.treble.app/.TopLevelSettingsActivity
to call at adb shell, but still not working.
does this work for enuma as well?
Does the Xiaomi Pen work on this Rom?
niveZz said:
does this work for enuma as well?
Click to expand...
Click to collapse
I am also very much interested using this on my: Mi Pad 5 Pro 5G "Enuma".
@All If this doens´t work on "Enuma" - can this be adapted?
@kokomicat
Really interested in this. Any news? Also I dont quiete understand, "no system sounds" means no notification sounds etc. or no sound at all like from youtube spotify etc...?
Thx
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
I Tried the steps, No Errors, but after Last fastbook reboot it just Boots to normal MIUI?
Any Tips?
siamese007 said:
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
Click to expand...
Click to collapse
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
spacezmonkey said:
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
Click to expand...
Click to collapse
It means this ROM is modified to suit elish device. So you need to use some apps to modify the system settings manually to fix the audio effects that are not compatible with the stock firmware.
I am using A13 Arrow GSI ROM. Everything works fine after disabling all the audio effect features of the ROM system. Except Xiaomi peripherals are not compatible.
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
spacezmonkey said:
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
Click to expand...
Click to collapse
You may try to flash the new Stock ROM that is compatible with the custom ROM. It seems the firmware you installed has sound conflicts with the installed firmware. Try the stable version of the firmware. The dev versions are still under development.
If the sound issues persist, I think you may wanna try the new custom ROM.