I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?
hash02 said:
I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?
Click to expand...
Click to collapse
Can you send me the link of the thread where you saw your rom?. Pretty sure theres a tutorial in it.. You are missing some important step like flashing create vendor.zip or repartitioner.zip and some other stuff.. Give me the link...
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.
hash02 said:
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.
Click to expand...
Click to collapse
Redo the process and try to flash the gsi only without gaps then boot..
r
ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot.. You can check this out also maybe it will help? https://forum.xda-developers.com/t/zuk-z2-pro-project-treble-android-10-11-12-gsi-ab.4197355/
Click to expand...
Click to collapse
to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot
prc.kailas said:
to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot
Click to expand...
Click to collapse
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn
ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot..
Click to expand...
Click to collapse
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity
hash02 said:
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity
Click to expand...
Click to collapse
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..
ivanjudge said:
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..
Click to expand...
Click to collapse
Well, Ok but where do i find android 11 opengapps ?
I didn't find any other gapps for Android 11.
However I tried your method even if it makes absolutely no sense at all. This device is a-only not a/b. Can you explain that or is that an elephant in the room that you dont want to talk about ?
In any case, the device does not bootloop anymore, it just sits in fastboot mode.
These are the steps to flash a gsi on zuk z2 pro correctly:
Wipe clean all partitions excluding user data
Then flash https://forum.xda-developers.com/t/radio-modem-basebands-for-zuk-z2-pro-only.3715835/ latest baseband
Flash boot image [ linked below - it is the boot image extracted from a mokee 9.0 rom ]
flash vendor image [ copied from another thread ]
flash gsi image [which ever you want]
reboot to recovery again [ sometimes it doesnt work unless you do ]
reboot to system
https://mega.nz/folder/E55iTZQJ#jNsa9d7WxLKr-9q_LFPS1A saved here for anyone else's convenience.
hash02 said:
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn
Click to expand...
Click to collapse
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.
prc.kailas said:
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.
Click to expand...
Click to collapse
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx
hash02 said:
superior-arm64-bvN-userdebug.img with AEX 7.3 works awesome and stable enough.
Click to expand...
Click to collapse
havoc-arm64-bvN-vndklite.img with AEX 7.3 works
hash02 said:
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx
Click to expand...
Click to collapse
for me AEX 8.1 is awesome, but none of custom support Uhealth with Sp02 sensor. its very usefull at this time.
Related
We already know this phone is arm64,
the GSI rom AOSP v112 has support for this phone.
But how is the rom behave? What works and doesn't?
How are other GSI flavours doing? Like RR, AEX, HAVOC,....
[NOTE: For those who are interested i'll change this post to some GSI guide cepheus,
as soon as i recieve my Mi 9. But until then i'll hope for some of your feedback]
See this: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
and these two: https://forum.xda-developers.com/showpost.php?p=79284072&postcount=46, https://forum.xda-developers.com/showpost.php?p=79295919&postcount=53
It shoudn't be needed to write a guide
a video guide would be interesting
I usually used twrp to flash the Gsi file but now I didn't understand what steps should be taken
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
update: since Phh was ultra vanilla with literally 2 extra settings, tried RR, same greeting, no fp, and no swipe to apps there, i don't really beg for their modifications as i have Xposed Edge for this. Finally went back to Floko knowing how to fix gapps problem, it's got best navbar solution, although with tons of bugs (contradicting navbar user actions, non responsive gestures, nonresponsive buttons), no tap2wake, AOD sucks, fp sucks too, produces blinking screen.
Looks like trebles are unusable, time to go back to XIAOMI EU... so much for "don't need device specific ROMs".
doggydog2 said:
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
Click to expand...
Click to collapse
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
dear mod please close this one, there seems to be already a conversation about this
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
tried to do that, tried to install arm64 Gapps, I'd get an error saying my system is arm, so i install arm gapps, they do get "installed", but when i reboot, there is no gapps at all.
edit: arm64 gapps worked when used LR.Team/wzsx150 twrp.
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
doggydog2 said:
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
Click to expand...
Click to collapse
You can find fastboot image here:
https://en.miui.com/a-234.html
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
thanks but both links redirect me to http://www.miui.com/ in chinese where i can browse to quasi-full roms again. strange.
btw i'm a fan of your kernel except it causes "can't connect to camera".. after many combinations of flashing i tried skipping the kernel (v01, or v02 or any kernel), and camera is back. however without Night mode this time...
update: found stable ROM at least https://c.mi.com/thread-1907373-1-0.html
update: somehow i trust this is the legit link to develop ROM http://bigota.d.miui.com/9.3.1/ceph....1_20190301.0000.00_9.0_global_cdb3885bac.tgz
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
Hey,
Could you make your magisk patch to not require pressing FP scanner twice for FP to register?
Without the patch, works fine from first try, but with it, two presses at least are needed Everytime.
Thank you!
Please help me. I can't seem to understand what exactly I need to do in order to install a custom ROM on my K20 Pro (Global 10.3.5.0.) I have tried following this (https://forum.xda-developers.com/k20...0-pro-t3953844) post thoroughly and others as well, but can't seem to exactly understand what I am required to do. Most custom ROM's state [Raphael], but as I purchased this device in India, it would most probably be [Raphaelin], after unlocking the Bootloader and installing TWRP, am I supposed to flash a Custom ROM (for ex. Lineage OS) directly or would I have to install a ROM which would make my device [Raphael]? Vendor and Firmware have gone over my head, I do not understand what I need to di. If someone could help me out, It would be mean a lot. Thank you.
Platinum_Pyth0n said:
Please help me. I can't seem to understand what exactly I need to do in order to install a custom ROM on my K20 Pro (Global 10.3.5.0.) I have tried following this (https://forum.xda-developers.com/k20...0-pro-t3953844) post thoroughly and others as well, but can't seem to exactly understand what I am required to do. Most custom ROM's state [Raphael], but as I purchased this device in India, it would most probably be [Raphaelin], after unlocking the Bootloader and installing TWRP, am I supposed to flash a Custom ROM (for ex. Lineage OS) directly or would I have to install a ROM which would make my device [Raphael]? Vendor and Firmware have gone over my head, I do not understand what I need to di. If someone could help me out, It would be mean a lot. Thank you.
Click to expand...
Click to collapse
If you're running stock MIUI and haven't moved to any custom MIUI's till date then you can straight away flash LOS. Moreover, most of the custom roms work on multiple vendors irrespective of whether it is a China Vendor or India or Global. It doesn't matter till the time the developer specifically asks you to be on a particular vendor.
Vendor isn't a dreaded thing. It's just the drivers needed to run the various components in the device (BT, WiFi etc). Till the time you don't wipe the vendor partion in twrp, you would always be good to go. You could carry on flashing custom roms w/o careing about the vendor.
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
If you're running stock MIUI and haven't moved to any custom MIUI's till date then you can straight away flash LOS. Moreover, most of the custom roms work on multiple vendors irrespective of whether it is a China Vendor or India or Global. It doesn't matter till the time the developer specifically asks you to be on a particular vendor.
Vendor isn't a dreaded thing. It's just the drivers needed to run the various components in the device (BT, WiFi etc). Till the time you don't wipe the vendor partion in twrp, you would always be good to go. You could carry on flashing custom roms w/o careing about the vendor.
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Platinum_Pyth0n said:
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Click to expand...
Click to collapse
Go back to the Lineage instructions and read immediately below that. It starts P.S.
It explains exactly proper vendor and firmware means.
No you won't need to install anything for this step
Platinum_Pyth0n said:
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Click to expand...
Click to collapse
Nope ! You don't need to flash vendor + firmware as you already running an untouched stock MIUI build. That is for people who are coming from either modified MIUI builds (EU, Miroom etc) or custom roms with a different vendor (India device running on China Vendor)
Custom roms don't carry the Vendor Firmware files and you can only modify the existing Vendor when you move to other region stock or custom MIUI roms.
Back up your data on Internal storage to a safe place either on a PC or OTG. Skip this step if you have nothing important.
Boot In TWRP
Wipe System, Data , Cache , Dalvik
(Don't reboot at this point, Not Even a Recovery reboot)
Flash LOS
Flash GApps
Go to Advanced Wipe and Format Data by typing Yes
Reboot
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
Nope ! You don't need to flash vendor + firmware as you already running an untouched stock MIUI build. That is for people who are coming from either modified MIUI builds (EU, Miroom etc) or custom roms with a different vendor (India device running on China Vendor)
Custom roms don't carry the Vendor Firmware files and you can only modify the existing Vendor when you move to other region stock or custom MIUI roms.
Back up your data on Internal storage to a safe place either on a PC or OTG. Skip this step if you have nothing important.
Boot In TWRP
Wipe System, Data , Cache , Dalvik
(Don't reboot at this point, Not Even a Recovery reboot)
Flash LOS
Flash GApps
Go to Advanced Wipe and Format Data by typing Yes
Reboot
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I'm trying to install a custom rom in K20 pro raphaelin. But it is getting stucked at recovery. Then I have to install stock ROM using MIFlash. Any help on this issue?
Custom ROM is successfully flashed in TWRP.
MyNameIsAbey said:
I'm trying to install a custom rom in K20 pro raphaelin. But it is getting stucked at recovery. Then I have to install stock ROM using MIFlash. Any help on this issue?
Custom ROM is successfully flashed in TWRP.
Click to expand...
Click to collapse
Did you do FORMAT Data (not just Wipe) when you installed your custom ROM, and before rebooting?
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
sternje said:
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
Click to expand...
Click to collapse
Restore MIUI by flashing a MIUI fastboot ROM.
Get the fastboot ROM from here
https://xiaomifirmwareupdater.com/miui/raphael/
Choose the fastboot ROM for the phone you have (European or Global). Make sure it is a fastboot ROM, not a recovery ROM.
Use this guide to flash it
https://c.mi.com/oc/miuidownload/detail?guide=2
View the page in desktop mode if viewing on a phone.
In step 5 make sure you change flash option to 'clean all' before hitting flash. This is three radio button options at the bottom of the flash tool. The default locks the bootloader, so you need to change it to keep the bootloader unlocked.
After doing this boot into MIUI at least once before trying to install something again.
When flashing a custom ROM over MIUI you need to format data in TWRP.
After installing TWRP, boot into it a do the following.
Perform a factory reset.
Format data - make sure you format, not wipe, need to type 'yes' to confirm.
Reboot back into TWRP - this makes sure the data partition is properly mounted after formatting.
Now flash the ROM you want and GApps if needed.
Reboot to system and it should be good.
Flash Magisk if needed.
Do not wipe anything else in TWRP. It's not needed.
sternje said:
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
Click to expand...
Click to collapse
First Learn Basics while messing with your device.
Kernel is a part of ROM's Zip,
So even if you wiped kernel(so called boot), it will again gets re flashed with new ROM.
Second your problem is,
You are booting into wrong partition.
I am not sure , what you did.
But Mi9TPro has two partitions, Google's new A/B partition table for Android.
And you may have wiped both Flashed A(example) and booting into B.
Therefore it is not booting properly.
Ask in Telegram group for faster solution.
Or wait here for better solution in reply.
OR
Simply flash Fastboot,
And then try everything again.
Ans from next time, read everything step carefully and then proceed.
Sent from my Redmi K20 Pro using Tapatalk
itspdp said:
First Learn Basics while messing with your device.
Kernel is a part of ROM's Zip,
So even if you wiped kernel(so called boot), it will again gets re flashed with new ROM.
Second your problem is,
You are booting into wrong partition.
I am not sure , what you did.
But Mi9TPro has two partitions, Google's new A/B partition table for Android.
And you may have wiped both Flashed A(example) and booting into B.
Therefore it is not booting properly.
Ask in Telegram group for faster solution.
Or wait here for better solution in reply.
OR
Simply flash Fastboot,
And then try everything again.
Ans from next time, read everything step carefully and then proceed.
Click to expand...
Click to collapse
This phone does not have A/B partitions.
Robbo.5000 said:
This phone does not have A/B partitions.
Click to expand...
Click to collapse
It has, but you can't see then normally in twrp.
Ask in telegram group for fast solution.
And please do read about android partition tables feom android oreo.
Sent from my Redmi K20 Pro using Tapatalk
itspdp said:
It has, but you can't see then normally in twrp.
Ask in telegram group for fast solution.
And please do read about android partition tables feom android oreo.
Click to expand...
Click to collapse
It's an A only, system as root device. It is not an A/B device.
This is why MIUI updates need to be installed in system recovery. It does not install updates when the system is live.
if it's booting back into twrp. It's usually one of the three mistakes.
1. wrong vendor
2. didnt flash dfe
3. flashed dfe for stock rom
4. encrypted, so format data partition.
you can follow the guide: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, k20p is A partition only, not dual.
kernel is included with rom.
ask in telegram group for faster replies.
Sandeeep Kiran said:
if it's booting back into twrp. It's usually one of the three mistakes.
1. wrong vendor
2. didnt flash dfe
3. flashed dfe for stock rom
4. encrypted, so format data partition.
you can follow the guide: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, k20p is A partition only, not dual.
ask in telegram group for faster replies.
Click to expand...
Click to collapse
You don't need to flash dfe. I've not yet come across a situation where it is required. Flashing dfe will make life easier, at the cost of greatly reduced security, but there are always options to do what you want without flashing dfe.
Robbo.5000 said:
You don't need to flash dfe. I've not yet come across a situation where it is required. Flashing dfe will make life easier, at the cost of greatly reduced security, but there are always options to do what you want without flashing dfe.
Click to expand...
Click to collapse
It's required for oss based builds now.
I was using pixel experience ROM for some time and I tried to update to the latest plus edition. The installation guide recommended full format data and flashing. I did as instructed. Now I'm stuck in booting into TWRP recovery. I looked up a few kinds of stuff and none of them worked. Is anyone else facing the same problem? has anyone got a working fix? I tried removing the TWRP folder, re-flashing TWRP with TWRP and orange fox recover, and then flashing ROM. non helped. got a broken phone now any help is appreciated.
basukala said:
I was using pixel experience ROM for some time and I tried to update to the latest plus edition. The installation guide recommended full format data and flashing. I did as instructed. Now I'm stuck in booting into TWRP recovery. I looked up a few kinds of stuff and none of them worked. Is anyone else facing the same problem? has anyone got a working fix? I tried removing the TWRP folder, re-flashing TWRP with TWRP and orange fox recover, and then flashing ROM. non helped. got a broken phone now any help is appreciated.
Click to expand...
Click to collapse
Use the correct TWRP if the rom is in A11 use A11 TWRP etc..
https://androidfilehost.com/?w=files&flid=318260
Twrp/wipe/format data write yes reboot Twrp/flash rom.
what do you mean by rom is in A11? I have redmi k20 pro raphael phone. I am using twrp for raphael code name.
basukala said:
what do you mean by rom is in A11? I have redmi k20 pro raphael phone. I am using twrp for raphael code name.
Click to expand...
Click to collapse
AOSP roms can be under ANDROID 11 or 12 or 13.
PixelExperience
Android OS version: 11.0.0_r40
The first version is in A11 and since August in A12
Version: 12
File name: PixelExperience_raphael-12.1-20220820-1826-OFFICIAL.zip
I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.
basukala said:
I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.
Click to expand...
Click to collapse
Do you use this TWRP?
twrp-3.6.2_9-0-raphael-TeamWin.imgTwrp
wipe/format data write yes reboot twrp
flash the rom
Use this O.F https://androidfilehost.com/?fid=15664248565197208249
basukala said:
I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.
NOSS8 said:
Do you use this TWRP?
twrp-3.6.2_9-0-raphael-TeamWin.imgTwrp
wipe/format data write yes reboot twrp
flash the rom
Click to expand...
Click to collapse
Wipe everything, system, vendor, internal storage, dalvik, cache via advanced wipe, then flash firmware and vendor or if your rom has included firmware then just flash the rom directly. Try to boot into OS if it still bring back to twrp then again repeat the above steps and this time flash stock vendor and firmware from mi website and try to boot into OS.
Click to expand...
Click to collapse
All the best
yes using the team win version of TWRP. Used Orange Fox recovery. ( nice look and feel and features btw). But they didn't work either. What could I try more? Could I be able to revert back to MIUI stock ROM ? let me know if you have good resources. Thank you very much for your time and efforts
basukala said:
yes using the team win version of TWRP. Used Orange Fox recovery. ( nice look and feel and features btw). But they didn't work either. What could I try more? Could I be able to revert back to MIUI stock ROM ? let me know if you have good resources. Thank you very much for your time and efforts
Click to expand...
Click to collapse
Back to MIUI
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
flashed stock miui rom for now. Will tap into pixel rom in few days.
now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?
basukala said:
now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?
Click to expand...
Click to collapse
Xiaomi has stopped updating on Android version 11.
Which rom do you want to install?
basukala said:
now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?
Click to expand...
Click to collapse
Why bothering to manually search here and there for official ROMs
Install the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
and the app will show you links to download the latest Global, EEA, etc, zip/recovery or tgz/fastboot, or you can scroll through the older versions and pick an older if you wish
Btw, latest are MIUI 12.5, A11 - there are no official A12 ROMs for Mi 9/Redmi K20 line of models
Even if they receive MIUI 13, it will be (for some already released, but eg China only, etc) it will be A11
Same issue, I guess this is it for me. Time to buy a new phone rather than accidentally losing data from time to time with custom ROMs. I wonder if they didn't know such issue exists before releasing it to the public.
Im on my A605FN right now and i have installed AOSP v222 (treble_a64_bvS-userdebug 10 QQ3A.200805.001 200805 test-keys) as my system. Can someone send me a working android 8 GSI? Android 10 is too much for this device and my 3gb of ram cant take it. I dont have time searching for well working GSI's to this phone. I need well optimized system that will use minimum ammount of resources. Thanks.
MDN2137 said:
Im on my A605FN right now and i have installed AOSP v222 (treble_a64_bvS-userdebug 10 QQ3A.200805.001 200805 test-keys) as my system. Can someone send me a working android 8 GSI? Android 10 is too much for this device and my 3gb of ram cant take it. I dont have time searching for well working GSI's to this phone. I need well optimized system that will use minimum ammount of resources. Thanks.
Click to expand...
Click to collapse
Just try that Lineage R mod - it should work fine. However if you want so old builds, then there is best list with Android 8 Oreo section:
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
When i try to install lower android version than 10 my phone boots in download mode... Yes, regular odin mode, no errors, etc. Please help, i want to get rid of that android 10 no matter what version it is, even LineageOs or AOSP, its still android 10 that use a lot of resources to work smoothly
1. Download this and extract.
2. Go to TWRP.
3. Follow this guide (flash this in TWRP, not in Odin).
It should work well. Older Android versions may require older kernel versions to run or you just chosen wrong builds (it needs to be A/B arm32_binder64 (A64 - not arm64) vndklite).
In case that Lineage R mod is not smooth enough do the same with other GSI's from the list from my previous post (always choose arm32_binder64 vndklite (A/B) builds). Some will be lightweight enough for your needs.
Ye i know build for my phone . I will try the GSI you linked but which gapps should i use to this system?
And i have another great idea, what if i just not install the gapps and run clear CLEAR android
Hmm... Also i can install the most important gapps, I didnt think about that, that should use very small ammount of ram, cpu, etc.
MDN2137 said:
Ye i know build for my phone . I will try the GSI you linked but which gapps should i use to this system?
Click to expand...
Click to collapse
Just use build I linked above. It has integrated Gapps and passes needed certfications out of the box. You can also download vanilla build and flash pico gapps yourself. However option with integrated gapps is just fine and sufficient. Read whole thread - author had the same problem as you and solved it by flashing Lineage R mod with integrated gapps - it's the most simple way.
Idk why but when i flash this GSI with no error and then i try to boot to the system it goes download mode. I think i know how to flash GSI's, I'm doing it 100% right. I flashed it in every possible way. It is getting boring
MDN2137 said:
Idk why but when i flash this GSI with no error and then i try to boot to the system it goes download mode. I think i know how to flash GSI's, I'm doing it 100% right. I flashed it in every possible way. It is getting boring
Click to expand...
Click to collapse
Well, flash maybe at first stock firmware via Odin to ensure that kernel and vendor partiton are untouched. And then flash GSI in TWRP two times like it was said in guide.
However the most common cause of such effect (booting to download mode) is just wrong build (wrong architecture - you need to always download arm32_binder64 (A64) builds).
I already tried to flash GSI after flashing ROM via Odin3. Still booting to download mode. Im 420% sure i downloaded right build.
Well, I'm out of ideas. However you can still try to resize system partition in TWRP to make it a bit bigger and then try to flash GSI image (two times). You can also just try to play with different GSI's from the GSI list - just look for the smallest images and try to flash them. If some will properly boot then just go back to TWRP and flash rest of your needs (pico gapps, Magisk, etc.).
I will try that in future