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.
Related
Hello,
I just ordered my X820 for dirt cheap (€136). I wanted to ask you about the routine of getting custom ROMs up and running.
From what I understand the procedure is the following:
1. Activate USB debugging and OEM unlocking
2. Go to fastboot and use OEM unlock
3. Fastboot flash recovery TWRP.img
4. Boot into TWRP and format data????
5. Wipe system, caches, data, blah blah
6. Sideload lineage.zip, gapps.zip and magisk.zip eventually
7. Profit
Is this procedure correct? On my other (Xiaomi Redmi Note 3) phone I skipped formatting data and it still worked.
I don't need the stock ROM backup, lineage is the main reason I purchased this device.
I would fastboot TWRP before flashing it and do a full backup. You may need it at some point to fix fingerprint sensor or camera or return the phone to factory state in case of a warranty claim.
The procedure you describe is right, but no need to format data.
popoyaya said:
I would fastboot TWRP before flashing it and do a full backup. You may need it at some point to fix fingerprint sensor or camera or return the phone to factory state in case of a warranty claim.
The procedure you describe is right, but no need to format data.
Click to expand...
Click to collapse
I saw a guide where it says I should boot into TWRP (yes, boot into TWRP, via fastboot) and do a backup from there... Than actually install TWRP and other zips. So I'll do that, thanks.
Heyyo, formatting data is a good step because EUI ROM does some odd data partitioning and prevents custom ROMs from fully utilizing the data partition unless they do format data (it could show up as only 30GB available instead of closer to 54GB since the system partition takes a chunk of the 64GB and so on).
Also, I'd recommend OmniROM over LineageOS. LOS 14.1 is pretty good but OmniROM is more stable and has SafetyNet Google Certification without the need for Magisk hide and potentially Universal SafetyNet fix module.
If you want a ROM with similar environment to LOS 14.1 but with further enhancements to EAS, vendor and device tree? I'd recommend SlimRoms as it has a lot of good tweaks. SlimRoms does require Magisk Hide and for some they also require Universal SafetyNet fix module.
Ps. For some sideloading doesn't work but this does:
adp push nameoffile.zip /sdcard
Which copies the zip to the root of the sdcard folder.
Psps. once you flash a custom ROM you will want to flash an updated modem firmware as it fixes the fingerprint reader when the device sleeps for Nougat and experimental Oreo ROMs.
I recommend either the Chinese 26s 05.09 stable one here
https://yadi.sk/d/woKdrlRrv8yhr/Китай
And some also say developer 466D works better for them so experiment as you wish
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
ThE_MarD said:
Heyyo, formatting data is a good step because EUI ROM does some odd data partitioning and prevents custom ROMs from fully utilizing the data partition unless they do format data (it could show up as only 30GB available instead of closer to 54GB since the system partition takes a chunk of the 64GB and so on).
Also, I'd recommend OmniROM over LineageOS. LOS 14.1 is pretty good but OmniROM is more stable and has SafetyNet Google Certification without the need for Magisk hide and potentially Universal SafetyNet fix module.
If you want a ROM with similar environment to LOS 14.1 but with further enhancements to EAS, vendor and device tree? I'd recommend SlimRoms as it has a lot of good tweaks. SlimRoms does require Magisk Hide and for some they also require Universal SafetyNet fix module.
Ps. For some sideloading doesn't work but this does:
adp push nameoffile.zip /sdcard
Which copies the zip to the root of the sdcard folder.
Click to expand...
Click to collapse
Thanks for the valuable info. I appreciate OmniROM, and SlimRom, and basically everyone that has contributed with a line of code. But I'm more of a LineageOS guy, I like the official Lineage stuff.
You say that on the official TWRP adb sideload doesn't work??? Edit: Oh I see, I will try, if that fails I will use push, thanks again.
ThE_MarD said:
I recommend either the Chinese 26s 05.09 stable one here
https://yadi.sk/d/woKdrlRrv8yhr/Китай
And some also say developer 466D works better for them so experiment as you wish
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
Click to expand...
Click to collapse
After I get the device out of the box I will update to the latest available update from the EUI updater, then I will proceed to install custom ROMs. On my other device doing that update updates the firmware as well, is this the case with this device?
Happy Hepatitis said:
After I get the device out of the box I will update to the latest available update from the EUI updater, then I will proceed to install custom ROMs. On my other device doing that update updates the firmware as well, is this the case with this device?
Click to expand...
Click to collapse
Heyyo, yes they do as they include the firmware files.
Updating to one of the latest EUI versions requires upgrading to the same locale version.
If your phone is an x820 (it'll say on the back of the device) then Chinese 26s is the official latest but there is a leaked 28s.
If your device is a x829 like mine? They come with EUI 5.8.016s which is a modified vendor version that blocks updating even via the update.zip method... So that one you would be screwed and would need to unlock bootloader and then try either fastboot or TWRP flashing a different version of EUI ROM.
Sadly the LeEco official servers were down last I checked but there is a thread in the guides section that has links to the latest versions and I think Google drive backup links too.
I think x821 might be the India model but I could be wrong. If so then their latest is EUI 19s
ThE_MarD said:
Heyyo, yes they do as they include the firmware files.
Updating to one of the latest EUI versions requires upgrading to the same locale version.
If your phone is an x820 (it'll say on the back of the device) then Chinese 26s is the official latest but there is a leaked 28s.
If your device is a x829 like mine? They come with EUI 5.8.016s which is a modified vendor version that blocks updating even via the update.zip method... So that one you would be screwed and would need to unlock bootloader and then try either fastboot or TWRP flashing a different version of EUI ROM.
Sadly the LeEco official servers were down last I checked but there is a thread in the guides section that has links to the latest versions and I think Google drive backup links too.
I think x821 might be the India model but I could be wrong. If so then their latest is EUI 19s
Click to expand...
Click to collapse
It's a X820 4GB RAM 32GB storage version, I ordered it from geekbuying.
Happy Hepatitis said:
It's a X820 4GB RAM 32GB storage version, I ordered it from geekbuying.
Click to expand...
Click to collapse
Ah cool! You should be lucky then and not be stuck on one of those vendor ones like my x829.
The easy way to tell is in your settings you will have an update checker. My x829 did not and wouldn't let me try the recovery update.zip method.
So you'll want to get the EUI ROM latest for your phone and then rename it to update.zip and place it into the root of your sdcard (/sdcard) and then boot to recovery and there should be a selection for "update from file".
https://forum.xda-developers.com/le-max-2/how-to/le-max-2-official-stock-firmware-links-t3433761/
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.
So, since there is not alot of development going on for our device, i thought we could maybe work together to get something done four our Mi Note 10.
Android Q (10) Guide
1) Flash Miui 12 beta
2) Flash Latest OrangeFox Recovery
3) Format Data
4) Wipe dalvik and cache
5) Reboot to Recovery
6) Flash an GSI of your choice (Arm64-AB)
7)Resize the system partition
8) Optional: Flash Opengapps
9) Optional: Flash Magisk
Restart system
Enjoy
(Big thanks to deathhall)
For me Havoc Q works really well, also face unlock works with Havoc
Havoc specific bugs: SMS doesnt work with 4G, Gcam works only with the main lens and frontfacing lens
Havoc 3.6
Android Pie (9) Guide
How to flash these on the Mi Note 10?
1) Flash Orange Fox TWRP
2) Factory reset in TWRP / format Data!
4) Fastboot: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5) Download the ARM64-AB version of your desired rom
6) Flash AB system.img of your GSI in TWRP
7) Flash magisk
8) reboot
That worked for me with both GSIs
Lineage OS 16.0
HAVOC OS 2.9
Whats not working?
- Fingerprint (Needs custom overlay)
- Automatic Brightness (Needs custom overlay)
- Camera works fine, but Video seems a little bit weird
- NFC, but this can be fixed with a magisk module
NFC FIX
Kind of a fix for automatic brightness
Video fix
If you have weird notification sounds delete the SoundFX folder from /Vendor/lib and /Vendor/lib64
Framework-res.apk (Provided by ChriZer)
Great work my friend, hopefully these will be the stepping stones to development and we can get the ball rolling on more in the future!
Sent from my MI CC9 Pro using Tapatalk
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
ztocker said:
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
Click to expand...
Click to collapse
Try with 11.0.12
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
deathhall said:
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
Click to expand...
Click to collapse
Maybe try 11.0.1. since its alot bigger than 12 and 11
Android 11 GSi is out can you give it a shot?
Status?
Is anybody using the LOS GSI as a daily driver?
If there is just the small amount of bugs like in the description, it might be fine for now. At least for me.
Or are there other small bugs 'not worth mentioning' ?
In another parallel thread 'Will there be a custom ROM?', two heros decided to work on our phone... I wish them the best!
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include LineageOS, CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github). With regards to LineageOS, once rooted with magisk it will NOT boot.
Under Display Fingerprint does NOT work on any GSIs currently and Face Unlock only works on specific GSIs.
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
LDP12 said:
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github).
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
Click to expand...
Click to collapse
No fingerprint right?
Fingerprint on GSIs
iSonik said:
No fingerprint right?
Click to expand...
Click to collapse
Unfortunately no fingerprint on any GSIs currently
LDP12 said:
Unfortunately no fingerprint on any GSIs currently
Click to expand...
Click to collapse
Thats not a minor bug imo
iSonik said:
Thats not a minor bug imo
Click to expand...
Click to collapse
Completely opinion based; I can live without it.
I have edited my original post to include this.
LDP12 said:
Completely opinion based; I can live without it.
I have edited my original post to include this.
Click to expand...
Click to collapse
Yeah thats why i said "imo". But that also means no autobrightness
iSonik said:
Yeah thats why i said "imo". But that also means no autobrightness
Click to expand...
Click to collapse
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
LDP12 said:
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
Click to expand...
Click to collapse
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
iSonik said:
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
Click to expand...
Click to collapse
Yes, I am using Q GSIs
Interesting, i cant get GSIs to boot, did you do something different?
Are you wiping Dalvik, System, Data and Cache, and then flashing the preferred GSI?
If the above method is not working, search "Download the MIUI 12 Closed Beta for Xiaomi and Redmi devices XDA" on google, download MIUI 12 beta for tucana/Mi Note 10 (our device) and flash it in TWRP. Then perform a wipe as usual and flash preferred GSI.
iSonik said:
Interesting, i cant get GSIs to boot, did you do something different?
Click to expand...
Click to collapse
I was on MIUI 20.6.11 -MiRoom when I flashed the Bliss GSI, my exact steps where:
Flash Latest OrangeFox Recovery
Formata Data
Format dalvik and cache
Reboot to Recovery
Flash GSI -Arm64-AB or BvN depending on the owner
Go to Data in the manage partition menu and resize partition
Flash Opengapps, I used 10.0 Pico
Restart system
Admittedly, I flashed the GSI but not the gapps first, just to see if it would boot, which it did. then I formatted only cache and dalvik, then resized and flashed Gapps. and it booted and took me right into the setup from the notification that came up when it booted.
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.