Related
As we(in the TG group) have tested a bunch of Pie9.0 (s)GSI Roms on the XDA forum (https://forum.xda-developers.com/project-treble/trebleenabled-device-development) I was asked to make a guide/summary of what there was already been tested and in our opinion the better ones out of the Pie-list.
It’s not to be intented to be ‘the’list but only to give you a guidance to what there is at the moment. And most of, it’s very easy to install
The ones that I will list are the ones WITHOUT call bugs on our Axon 7. As you wish you can vote for your favorite of the listed ones above.
Note : the LOS16 PPR2 is not the same as the one under ROM section (Ordenkrieger)
LIST AVAILABLE : (not in a specific order and more to come)
1. HavocOS : based on https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Latest stable : https://sourceforge.net/projects/havoc-os/files/arm64aonly/
2. BenzoROM : based on https://forum.xda-developers.com/pr...device-development/gsi-benzo-rom-9-0-t3837127
Latest stable : https://forum.xda-developers.com/showpost.php?p=78312149&postcount=284
3. PixelExperience : based on https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Latest stable : https://github.com/EnesSastim/Downloads/releases/tag/PE-A-2018-09-05
4. LOS16.0 PPR2 : based on https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
Latest stable : https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ!DD4z0AhA . More info.
5. ArrowOS : based on https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
Latest stable : https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/7_sep_2018/
6. DescendantOS : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578
7. PixelDust : https://forum.xda-developers.com/showpost.php?p=78184921&postcount=212
8. AEX 6.0 OFFICIAL : https://forum.xda-developers.com/showpost.php?p=78245997&postcount=254
Pre Requisitions :
Unlocked BL, Bootstack B12 NFound or your preferred one
Vendor partition by @djkuz or your preferred one
TWRP3218-treble under the hood @NFound or your preferred one
Installation : or your own preferred method as this is just an example
Wipe System. Data, Vendor, cache dalvik (although data does the job)
Flash the v1.1 NFound
Flash the .img that you have extracted and if needed renamed to system.img
And just….reboot
After installation there can be applied some fixes :
a* Use the aroma COMBIFIX v3.1 to fix the NFC/HS general lag, choose button reverse, flash new kran framework overlay, magisk and gapps
update : for magisk 18.1 use the latest Combifix v5.1 or with Magisk 19.0 you can use Combifix v6.0 or the latest one with magisk 19.1 and latest MHPC : COMBIFIX 6.1
a. NFC when laggy or not working combined with Hotspot : Pie_NFC /Hotspot fix by @kountry83
On ArrowOS and Benzo they both work after applying the fix although the Hotspot works on ArrowOS and Benzo die to v105 phh
b. GCAM when default one isn’t working
c. Camera fix if you have a settings bug
d. Reverse BACK/RECENT (mount system / vendor) or A2017X_softkey_reverse_module
e. System settings color accents
f. DarkMode & SettingsColorAccents thnx @kountry83
g. safetynet issues
Misc :
* A2017X-MoKee_vendor_boot_combo
* AEX bootanimation
* Havoc bootanimation
* There is no need to an incall fix as all of the listed are free of the bug.
* Also no problems with SD card or booting the roms.
* In some cases the package provided by the dev is GAPPS included. If no gapps provided you can simply flash the OFFICIAL GAPPS.
* All roms have NFC working. Hotspot isn’t reliable and mostly not working.
* Some Pie Roms do have more customization as to the other. Up to you to vote which one you do prefer. When voting it would be good when you make your vote based on ‘most stable/most customs/best battery life’
* Substratum works (tested on Benzo and NOS...)
I’m not going get into detail about each rom. I’ll leave that up to you to discuss further on. Perhaps if voting leads us to a one of a kind, we can focus on that in the future.
It would be much appreciated as you add your input even with your fixes or additions you want to point out.
This is something that is growing on XDA and all the input is welcome to improve what we have.
ENJOY !
@Oki, thnx for your guidance on flashing back and forth between (treble) roms
Credits to all mentioned in the thread and to all members for testing and improving it on TG !
Feel free to join us too on Axon7-trebleshoot
-----
Havoc P seems to be a good option. Im voting for havoc.
nays_pl said:
Havoc P seems to be a good option. Im voting for havoc.
Click to expand...
Click to collapse
A good one. As for me the Benzo, Los16PPR2 and Havoc are the best to this point.
Especially smoothness, battery life and customization are more then ok atm.
Updates will follow and improve things where needed.
Thanks @raystef66 ! Took some time away from flashing and was a bit lost of where to go on my axon after moving to aex5.8 and how to do. Good that you also have the instructions
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Axebladewarrior said:
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Click to expand...
Click to collapse
Thnx for the input !
True, as for me too, the AEX Oreo has a bunch of customs that Benzo still hasnt. But out of all GSI's Benzo and a couple others have the most.
Even on some Pie GSI's the displayed features aren't even working.
Batterylife as on NOS gave me 4-5 SOT on average use.
Anyway, like you said, still building up....
raystef66 said:
@Oki, if you want to guide the users on your method to flash a (s)GSI from scratch with your PartyTool, be our guest
Click to expand...
Click to collapse
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Awesome :highfive:
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
That would be great and much appreciated as you have followed your own guideline next to NFounds ! That's why I asked
I follow what you're trying to achieve and in fact I'm waiting to test the LabMods. Thnx !
As said, I come along with many people asking how to go back and forth between N,O and Pie. I know what to do in such occasions but many don't.
Because of your tools I'll leave the full guide on that up to you
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Thx. How about adb and encryption for TWRP2. 3.2-0L?
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
Read his OP in the thread he linked.
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
I have not developed new kernels but I have taken care of both situations. Just go to the TWRP Labs Mod thread, the info is in the OP and you can ask there too. This thread is all about the Pie implementations, Let's try to keep on topic as much as possible.
really hope MIUI 10 will be stable enough, miss MIUI
HOW TO...
Round Trip from NOUGAT or OREO to PIE GSI
OK, the full instructions to go from Nougat or Oreo to Pie, and back, would be:
Prerequisite
Bootloader Unlocked Axon 7
Install tools and configuration
1. Install TWRP Labs Mod Custom Recovery. Use the B12 version in case you are currently using Oreo encryption. Reboot to recovery.
2. Open the PARTY tool under Advanced > Oki Labs. If you do not have vendor partition you need to create one. Use the default configuration (System, 512MiB, at the end). Accept to reboot recovery. If the vendor partition is there, then just leave PARTY tool and continue with the next step.
Backup your daily driver config:
3. Go to the EDL Backup tool under Advanced > Oki Labs and create the Backup zip choosing FULL. If something goes wrong you will be able to restore your device using TWRP or MiFlash
4. From the Main Menu, backup your Data partition to the External SD.
5. Backup your Internal Storage using the option under Advanced > Oki Labs (Check the available space, the tool is not yet checking for available space, I will add it this weekend)
Prepare Treble configuration:
6. From TWRP Install the special B12 Bootloader with enabled EDL key combo support (The Universal Bootstack leads to DFU mode) and the modem for your region.
7. From the Main Menu, Wipe Vendor
8. Flash Axon 7 Treble ROM v1.1
Flash GSI package:
9. From the Main Menu, Wipe Dalvik / Cache / System / Data
10. From here you have to follow the installation instruction for the Generic System Image (GSI). Usually it is a single img file. So go to Install, press Install_Image button and navigate to the GSI file to flash it. Then just reboot. Some images would require additional ZIPs such as GApps or recommended patches.
Here you test the Pie ROM. If you want to test another Pie ROM you can try just going back to step 9. However, to ensure everything is clean you should start in step 7.
Return to your Daily Driver Config
11. Boot Recovery and flash the backup EDL ZIP you created in step 4. If you bricked your device just extract the contents of the file in your HD, Boot your phone into EDL mode, and use MiFlash. This step restore your original bootstack, modem and OS.
12. From main menu restore your Data partition
13. Go to Advanced > Oki Labs and restore Storage.
14. If you had to create the vendor partition in step 2, just run the PARTY tool again to remove the vendor partition.
15. From the Main Menu, Wipe Dalvik / Cache and reboot to system.
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Misc
Magisk Camera Module (MI A2 stock camera for Pie) - tested and works very good. Even flash is synchronised as well.
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
raystef66 said:
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Click to expand...
Click to collapse
How about hotspot? Is it working now?
privatedoodle said:
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
Click to expand...
Click to collapse
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Oki said:
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Click to expand...
Click to collapse
This new version works. Thanks!
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup.
Notes
The idea of this project treble is to separate the device-dependent part and the system.
The project treble requires a separate /vendor partition for device-dependent part. But unfortunately we do not have it. But we have a /cache partition, which takes about 200mb and there is a /hidden partition, which takes 50-60mb. 200mb is not enough for us, our vendor is about 450mb.
In the first edition I maded for the 825 tablet, I implement an original solution using separate files for the system and the vendor. But this solution was very difficult to understand. Now my good friend @bonuzzz suggested an idea to me using a compressed partition (squashfs with lz4 compression). With this method, our vendor takes 190-195mb and it is possible to write it to the /cache partition. And use the /hidden partition as a /cache.
Now the installation has become much easier, almost like installing the usual lineage.
Installation
1. install twrp version with treble support (this is my special twrp, based on 9.0 with my latest caf kernel with squashfs support)
2. download treble zip and flash it as usual zip. It will flash boot.img and /vendor partition (in /cache)
3. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble
extract, you should get .img file, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
4. if you wanna back to stock firmware or lineage - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Links
Firmware
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1hOPdO9UajY7AlJ5lE859Tr6Y7sEpwhTf/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1DokV37D8f2s9OtoAJTCURfdx88tNW788/view?usp=sharing
TWRP
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1gJ50Sg75Vh7PKyiWfejiCPSD0SYCL5p2/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1x_MKQ1PDM6eEbSPsDyFk0DABjXnZfyB4/view?usp=sharing
System images
You can use almost any system image from https://forum.xda-developers.com/project-treble
Our version is: arm64 and a-only image
Magisk
You should use only latest 19.0 beta version from: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do not use 18.1 or early version - it's dnw, it will corrupt firmware or may be even corrupt recovery (need flash recovery again via odin)
Almost all firmware say about wrong vendor version. This is normal, just press OK.
let's experiment together!
Version for SM-T825 hope will come soon too. I have some ril issues.
Update boot.img
Wow! Thank you for the amazing work. I seriously can't believe no one hasn't gone crazy over this already.
How would I go about adding some libraries to my /vendor partiton now? I want to try a Samsung OneUI GSI image on my tablet but it requires additional libraries.
The files I want to add are in here: https://mega.nz/#!oi52TSTY!2Qy3WU7DjVmafs4zENPF6dlOsbY06JG5NuvsNeDTRn4
How did you build this file in the first place?
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
cephasara said:
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
Click to expand...
Click to collapse
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
GSIs
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Maybe my /hidden & /cache partitions got corrupt somehow. I tried several GSIs and had the same issue. Thanks for confirming though.
Have you tried an GSIs from non AOSP-based images? Like OneUI or Xperia? I had trouble with those.
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Could you let us know which treble rom you used, as I have the same issues with video playback on youtube.
I also want to throw out there I was on the Nougat bootloader when I tried this and had video playback issues. I have not tried it out on Oreo. I would imagine that could make a big difference.
deleted (it sucks none of the sensors function properly)
just installed RR but i think gps not working
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
This is great!
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Mhh.. I get constantly soft reboots if i try to install third party apps or restore my titanium backup on Havoc for treble. Fingerprint is also not working. Seems to be very unstable...
How could I go about adding files to this treblized /vendor partition? Presumably through the zip? If this is the case, how could I do that?
Fair warning to those wanting to try this: treble roms do install and run, but sensor support appears to be lacking. I can't get any input from gps, accelerometer, gyro, or light sensor.
@Valera1978 If anybody has any idea on how to add support for these to the (I'm assuming) vendor partition, I'd love any hint or direction.
usb otg not working
alegru said:
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Click to expand...
Click to collapse
Does Netflix work?
I get a bootloop after installing image and reboot to system. I have followed the instructions and got an error "Updater process ended with ERROR:7" installing the treble-16.0.zip. I flashed the custom TWRP using odin and using stock Pie. Did I do something wrong?
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
ianrobbie said:
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
Click to expand...
Click to collapse
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Looking dangerous. I'd like to try it but uncertain procedures
NullCode said:
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Click to expand...
Click to collapse
would some of the issues seen by others be fixed if one started with non-rooted stock 9.0 and 9.0 bootloader (if it is different from that for Oreo)? thanks anyone
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
deleted
What version of RR Pie did you test? The May Release?
JDBS30 said:
What version of RR Pie did you test? The May Release?
Click to expand...
Click to collapse
all of them.
this link i used and choose one of them from your choice arm a only of course: https://get.resurrectionremix.com/?dir=gsi
I can't install Resurrection Remix
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
elfennani said:
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
Click to expand...
Click to collapse
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
rudi021 said:
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
Click to expand...
Click to collapse
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
elfennani said:
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
Click to expand...
Click to collapse
like i wrote your device must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
rudi021 said:
like i wrote you must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
Click to expand...
Click to collapse
How did you downgrade your firmware?
elfennani said:
How did you downgrade your firmware?
Click to expand...
Click to collapse
i found oreo firmware. if you want you can download from my google drive. here is link: https://drive.google.com/file/d/1KnqHZ8_EVTstJP5AMsMy_8Uc1QV-vMHe/view?usp=sharing
Please help
rudi021 said:
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
Click to expand...
Click to collapse
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Maxmiliano Coelho said:
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Click to expand...
Click to collapse
my dear friend just ask i will help you. this patched boot.img is made by ashyx. i will be bad member if i share his works without permissions.so i share with you his link. here is link for oreo patched boot.img https://androidfilehost.com/?fid=1395089523397921797
please follow instructions carefully. read twice and try to understand.enjoy.if you have any doubt please ask. thank you.
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
why not.i am not star just ask and if i can help i will please to do that.you can always send me personal message(PM) on xda
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
rudi021 said:
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
Click to expand...
Click to collapse
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Maxmiliano Coelho said:
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Click to expand...
Click to collapse
once you perform flashing gsi,no need repeat every time this steps,just (at least i do like that) format data,reboot to recovery,flash gsi(as system.image) and flash magisk then mount system and reboot.about audio volume install viper fx audio apk(Magisk module),and then fix volume as your own.
kapmino269 said:
If anyone faced problems with booting some roms on
ROM LOGO NOT SAMSUNG .
use this :
https://www.androidfilehost.com/?fid=6006931924117925309
Tested on j415f
RR
AOSP
DESCENDANT ZERO .
Click to expand...
Click to collapse
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
rudi021 said:
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
Click to expand...
Click to collapse
me i have not a network on aex extended but on dot os i have
Envoyé de mon Phh-Treble vanilla en utilisant Tapatalk
kapmino269 said:
Guys , sorry I found error in my script and I fixed it I tested it on AEX official , I will test it in others then post it .
@rudi021
---------- Post added at 09:15 AM ---------- Previous post was at 08:29 AM ----------
v2 : https://www.androidfilehost.com/?fid=6006931924117930007
tested : work with rom logo bootloop 100%
Click to expand...
Click to collapse
thank you bro. i definetly try this on pie upgrade and inform you.thank you for your hard work. i am on vacation and when i come home i will try this.thank you and greetings from Croatia.:good:
also i stop build gsi roms for j4+ because my pc is old so i need little upgrade of same( RAM(have only 4 gb,need for pie at least 8 gb ,my motherboard can have 32 gb,), my processor is i3 but i will upgrade on i5 and after that i will continue work on it. but now i am on vacation with my wife and children and when i come hom ei will continue to work it.thank you once more.
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.
Disclaimer:
The use and installation of this software product is at the exclusive responsibility of the user.I am not responsible for any damage that may occur to your device resulting from the use of this software.This software product is "as is". Its first goal is to allow the xiaomi.eu Rom be installed via recovery.If you have any doubts regarding the above lines, you should not use or install it.
Recovery:
Unofficial release 3.7.0 for Xiaomi Mi 10T Lite and Redmi Note 9 Pro 5G devices. Status : StableVersion : 3.7.0.4GRelease Date : 2022.12.26Features:
Android 12 decryptionAndroid 13 decryption (Not tested by myself)FlashingAdbOtg (Not tested by myself)MtpBackup / Restore to / from microSDBackup / Restore through adbSideloadDevice boot Logo changerMagisk tools and theme from @ Brigudav (Not tested by myself)
Notes:
I concluded that custom roms (without Miui) are unable to decrypt /data with this recovery.Checking LineageOS and ArrowOS, it seems that they use a different encryption mode than Miui.I haven't found how to check on Twrp booting what encryption mode /data uses and adjust to it.Therefore, I have uploaded another release for non Miui devices.Can't tested by myself, I don't know if it decrypts fine.However, it is likely the Miui variant will work correctly on the rest.
About official TWRP: The current official release https://twrp.me/xiaomi/xiaomimi10i.html does not work anymore since Miui 13. Use instead this TWRP.
Twrp not decryping on miui 14: Please, read this post
Downloads:
Last release from Xda (Post #2)
Older releases from androidfilehost
Release 3.7.0.3F for CUSTOM NOT Miui rom from Xda (Post #2)
Installation:
Updating this Twrp release:Downloaded to phone:Click on Install and locate the .zip file.Downloaded to PC (no need to copy it to the phone): On phone: start install via ADB (sideload). On PC execute: adb sideload file_name.zip
Try without installing: (does not alter the phone unless you want to do)Extract recovery.img from .zip file downloadedEnter fastboot mode.Execute: fastboot boot recovery.img
Installing this for the first time:
Your bootloader must be open. Extract recovery.img from downloaded .zip file. Enter fastboot mode Execute: fastboot flash recovery recovery.imgCredits:
Team Win RecoveryMinimal Manifest PlatformAlexander Brigudav
Latest release 3.7.0.4G for MIUI rom
Release 3.7.0.3F for CUSTOM Non Miui rom
Nice work
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
kacskrz said:
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
Click to expand...
Click to collapse
Hello. I'm Spanish xiaomi.eu translator and user.
I don't understand how is possible your issue...
When I boot TWRP it asks me for the PIN to decrypt.
I would not have uploaded the image without testing it first.
Also the reboot buttons do what they say..
I have so far tested it without installing, because I have not yet dumped the Stock Recovery partition.
In theory, it is supposed to work exactly the same in boot mode as in flash mode.
Can you try it without installing?
As stated in the third disclaimer lines:
"Its intention is to allow the Rom xiaomi.eu be installed via recovery."
I retired here due to lack of free time and have only become involved now for this reason.
Best regards
tuxafgmur said:
Can you try it without installing?
Click to expand...
Click to collapse
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
kacskrz said:
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Click to expand...
Click to collapse
Your logs do not seem to give relevant information about the issue.
It is clear that booting are completely ignoring the security lockout..
During the night I dumped and unpacked the stock recovery.
After studying it, I found nothing significant except that the kernel is not exactly the same as in boot.img.
I'm now downloading the latest weekly release to unpack it and compare vs stable release.
kacskrz said:
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
Click to expand...
Click to collapse
I'm not sure I understand what this paragraph means..
Regards.
Pixel Experience 12 data decrypted successfully.
Thanks
Lineage os data decrypted successfully.
Unfortunately, the weekly xiaomi.eu does not decipher the date.
For @kacskrz , @nolan2112 and anyone else using weekly xiaomi.eu:
I would appreciate the test of the new Release 3 I just uploaded.
Thanks in advance.
@tuxafgmur Unfortunately, nothing changed. I've posted logs on the xiaomi.eu thread.
The latest version also cannot decode the date. firmware weekly 22.7.21
New release 3.6.2.1B uploaded
In addition to some other minor changes,
fixed decryption on xiaomi.eu weekly.
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Tested to flash xiaomi.eu from storage and sideload.
tuxafgmur said:
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Click to expand...
Click to collapse
Everything is fine, the recovery is fully working. Thanks Amigo!
New release 3.6.2.1B-R3 uploaded
Revision
New release 3.6.2.1C uploaded
Format: Zip file to install from TWRP.
Some reviews.
Since xiaomi.eu rom replaces boot Logo on global devices, showing "Redmi"
this release includes options to switch logo between "MI" and "Redmi".
Each has two versions to choose from:
1 - Factory stock.2 - Like stock but hiding the padlock shown when bootloader is open.
The only recovery that works (and decrypts) on the newest MIUI 13 Android 12. Thank you!
Fantastic work, congratulations!