Hi everyone, I make this thread because even with all others threads in this forum, we still get the same questions all the day. How boot this gsi ?
So here it is, I'll try to keep it up-to-date. I don't have time to try every gsi out there, you can help me if you have other informations
OFFICIALS GSIs
PHH-Treble by Phhusson [08.01.2019] BRIGHTNESS FIXED
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Resurrection Remix
by Mracar [20.01.2019] Do not try 14th Feb build - Random Reboots
With Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
From Pie Vendor (Thanks to Lecterr)
I am on Xiaomi.eu 9.1.24 and this TWRP: https://www.androidfilehost.com/?fid...63190603912779
wipe only system, cache, dalvik-cache
flash RR-image
Reboot to system - it boots about a few minutes and reboots to recovery
Reboot to system - it boots into system...thats it!
AOSP Extendedby EnesSatim [19.12.2018]
Can't make boot latest versions (since December)
Older use the normal way to install Gsi (Thanks to Opasha)
VIPER OS by peaktogoo [31.01.2019]
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bug : Vendor error message on boot
ARROW OS
by ArrowOs Team [15.01.2019]
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
PIXEL DUST by amarbajpai [28.12.2018]
Latest [28.12.19]
With Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Older builds
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bootleggers by Dil3mm4
Not booted yet
AOSDP by EchelonTeam
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Descendant OS
by Dil3mm4
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
AOSIP by AOSIP team [24.02.19]
Very Stable (Recommend Pie stable vendor 10.2.1)
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
UNOFFICIALS GSIs
AOSP Extended unofficial
by Nfound (4pda) [13.01.2019] [15.02.19]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Pixel Experience Unofficial
by EnesSatim [12.01.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Xenon HD unofficial
by Nfound (4pda) [28.01.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bugs : 28.01.19 can't edit qs tiles
Nitrogen OS Unofficial by Nfound (4pda) [25.01.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
LiquidRemix Unofficial by king1990
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/sh...er button wait 5 min and retry untill it boot
AICP Mordiford Pie by Technical Pie builds here [01.12.2018]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
DirtyUnicorns Unofficial by Peaktogoo [09.01.2019]
Pie Vendor (Thanks to Opasha) / Vendor error on boot.
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
GZOSP Unofficial by Nfound (4PDA) [01.02.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
MSM Xtended
By Nfound (4PDA) [02.02.2019]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Don't forget to flash Dialer fix after system.img
Bug : No sound over headphones, sound goes to speakers.
SuperiorOS by Nfound [14.02.19]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Bug : No sound over headphones, sound goes to speakers.
BAIKAL OS
By Nfound [MEDIUM]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
CrDroid By Peaktogoo [OPTIONS]
RR method Oreo Vendor (Thanks to Nikita) (you can try without Post gsi)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
OmniRom
by King1990
Pir Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Havoc OS by Nfound
Issue : No headphone sound
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bootleggers by Nfound
Vendor : Oreo
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
ION by Nfound
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bliss OS by Nfound
Oreo Vendor (Thanks to Nikita) = long boot without Post or use it but no LED
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Dot OS by Nfound
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Aquarios by Nfound
Oreo Vendor (Thanks to Nikita) = long boot without Post or use it but no LED
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Syberia OS, LEAN OS, BEAST OS and FRED OS don't boot.
05.03.19 : DU from Nfound not booting too (crash on PIN)
BRIGHTNESS | BLUETOOTH | SOUND | VOLTE | LTE SMS | ETC .. FIXES
A HUGE THANKS to theses people https://forum.xda-developers.com/mi-max-3/how-to/treble-experience-t3856333
PHH Fixes + VOLTE Fix by @MrColdbird
- Brightness
- Bt (Phh way, maybe not working on every gsi, if not, flash Bt fix or replace vendor files)
- Flickering Sound (clean libs)
- Camera API
- VOLTE Fix
- SMS sending fix on 4G
Go here > https://forum.xda-developers.com/showpost.php?p=79039299&postcount=43
All-In-One fix by @lkmnArief
- Bt (Replace Files Vendor)
- Brightness (by Fingerprint)
- Camera API
View attachment MiMax3_Bt_Britghness_gsi_fixes_v1.1.zip
PHH Fixes thanks to @btvbtv
https://forum.xda-developers.com/mi-max-3/how-to/guide-android-9-pie-aosp-phh-treble-rom-t3862708
V110
View attachment phh-treble-pie-fixes-v110.zip
BRIGHTNESS
Install a terminal app
Into it
Type "su" and enter then allow root
? (if you don't have go flash magisk)
Type "setprop persist.sys.qcom-brightness 4095" press enter
BLUETOOTH
NEW* Flashable ZIP with TWRP
thanks to Telegram user @lkmnArief
Download FixGsiBTSound.zip View attachment FixGsiBTSound.zip
_____________________
Old Manual Way
Download file "Vendor-Etc-2018-11-09" Here or attached file
?Need ROOT explorer (if you don't have root go flash magisk)
??Unzip the file
??Copy or Cut and Paste every files in Root directory /vendor/ect some files go on /ect some on /ect/audio. Replace files if already existing. Then set every files to 0644 permission (Rw R -R) and reboot.
? If this technique don't work (can't copy on root directory of missing files after reboot) you'll need to do this changes through TWRP in file manager move every files one by one and one by one set chmod to 0644 for EVERY files. This technique can't fail.
A HUGE THANKS TO :highfive:
Devs mentionned for making Gsi for us
People mentionned for their guides or tips or workarounds or everything else
@Nikitel and Adnan for testing and helping me on Telegram Channel
History of Editions :
02.02.19 : Added AICP Mordiford, Dirty Unicorns Unofficial
08.02.19 : LEAN, BEAST and FRED OS don't boot.
13.02.19 : Added MSM Xtended, New BT flashable fix, Way to boot latest PixelDust, Corrections, Added a picture
15.02.19 : AEX unoff updated [Ok], RR updated [RandomReboots], Added SuperiorOS [HP issue]
17.02.19 : Added Baikal OS, Crdroid and Descendant Os.
19.02.19 : Added OmniRom thanks to @Lecterr + Phh Fixes V110 thanks to @btvbtv
25.02.19 : Added AOSIP (very good gsi) and Bootleggers, New Visual tab
05.03.19 : Added Ion, Dotos, Du, Auqarios, Bliss, and Two new all-in-one fixes for Gsis !
Won't update often the thread because of my exams soon...
Great guide! Thanks Skyllery
Nikitel said:
Great guide! Thanks Skyllery
Click to expand...
Click to collapse
Just forget AICP Mordiford, will add it later. Thx
Sent from my MI MAX 3 using XDA Labs
Very good. Thanks your work helping noobies[emoji1787]
Enviado desde mi MI MAX 3 mediante Tapatalk
Tks very much
Hi,
Thanks for this... But how is this a guide to boot a GSI image ?
Unless I've missed something, it's only a list of GSI ROM with a comment if they boot or not
As far as I am concerned, I tried to install Resurrection Remix following the "How to install RR on mi Max 3".
I sticked to the guide step by step...
In the end, it did not boot and got stuck on RR bootanim...
So my experience : being able to boot a mi Max 3 with a GSI ROM is like the lottery : sometimes you win, but more often you loose
My conclusion ? Treble is a nice idea. Support from manufacturers is terrible...
My question : why are manufacturers so eager to protect their own **** ? What does Xiaomi have to loose if a customer uninstalls MIUI ? Same goes for Huawei. Especially for HUAWEI. They got such a nice feature called eRecovery. In case your device doesn't reboot because you did something wrong, you can always reboot into "eRecovery" and download the latest version of eMUI from there... Evey manufacturer should do that and allow to unlock the bootloader and install a GSI ROM...
I've tested all (all the same) listed here. Most have problems when the device restarts (at least in my case). Any version of October and November work well with either the Oreo or Pie vendor. The only one that worked well now being released in January is NitrogenOS. By the way I used this rom to boot the Havoc released in January and it worked. But by successive installations, in the TWRP appears the message that the system partition needs cleaning. Overall, the idea of GSI is fantastic, but there are so many devices that hardly a rom of these will work perfectly. There will always be a bug here, another bug and nothing working as it needs to. I even cleaned the system partition, but it gave brick and I had to reinstall the miui by fastboot. What we needed was a proper rom for the Mi Max 3, but I find it difficult. I have tried a lot to use some GSI because this miui is more disappointing than the Huawei emui.
NexusPenguin said:
Hi,
Thanks for this... But how is this a guide to boot a GSI image ?
Unless I've missed something, it's only a list of GSI ROM with a comment if they boot or not
As far as I am concerned, I tried to install Resurrection Remix following the "How to install RR on mi Max 3".
I sticked to the guide step by step...
In the end, it did not boot and got stuck on RR bootanim...
So my experience : being able to boot a mi Max 3 with a GSI ROM is like the lottery : sometimes you win, but more often you loose
My conclusion ? Treble is a nice idea. Support from manufacturers is terrible...
My question : why are manufacturers so eager to protect their own **** ? What does Xiaomi have to loose if a customer uninstalls MIUI ? Same goes for Huawei. Especially for HUAWEI. They got such a nice feature called eRecovery. In case your device doesn't reboot because you did something wrong, you can always reboot into "eRecovery" and download the latest version of eMUI from there... Evey manufacturer should do that and allow to unlock the bootloader and install a GSI ROM...
Click to expand...
Click to collapse
1. Under each rom you've the way we get it to boot. It's not a guide but each rom use one way or most to boot. So that's why I get them all together here. And we can update this list when gsi testers on mi max 3 tell me if they boot or not.
2. If you missed to boot RR, consider to change your recovery to Nigel TWRP as we using it. Because with Oreo vendor's way on stable eu 10.2.1. I flash it everytime without problem and already did it 6 or 7 times.
3. We don't have choice to use Gsi until, Nigel make a booting LOS, but pie kernel sources are not out for our phone, we need to wait Miui Pie stable on my opinion.
Germano1980 said:
I've tested all (all the same) listed here. Most have problems when the device restarts (at least in my case). Any version of October and November work well with either the Oreo or Pie vendor. The only one that worked well now being released in January is NitrogenOS. By the way I used this rom to boot the Havoc released in January and it worked. But by successive installations, in the TWRP appears the message that the system partition needs cleaning. Overall, the idea of GSI is fantastic, but there are so many devices that hardly a rom of these will work perfectly. There will always be a bug here, another bug and nothing working as it needs to. I even cleaned the system partition, but it gave brick and I had to reinstall the miui by fastboot. What we needed was a proper rom for the Mi Max 3, but I find it difficult. I have tried a lot to use some GSI because this miui is more disappointing than the Huawei emui.
Click to expand...
Click to collapse
What kind of problems ? Something changed between Oct/November and December/January, don't know why. But with nigel recovery we boot them (listed here). Only LiquidRemix is a bit tricky. But others boot fine.
You tell you boot Havoc latest build with NitrogenOs installed ? Can you explain the way ?
I always wipe everything, flash eu, factory reset and reboot into recovery to continue the installation maybe that's why I never faced this problem in system partition.
Gsi is a solution not THE solution. But at least we've got correct battery life and fixes for bluetooth and brightness. The more annoying.
What twrp are you using ?
Most stable are full stocks, like PE, AOSDP. I use AICP, RR or AEX on my side with a way better SOT on RR. Nitrogen is a good one too.
Regards
question is. do you get much better battery life on these roms compare to EU?
Skyllery said:
1
What kind of problems ? Something changed between Oct/November and December/January, don't know why. But with nigel recovery we boot them (listed here). Only LiquidRemix is a bit tricky. But others boot fine.
You tell you boot Havoc latest build with NitrogenOs installed ? Can you explain the way ?
I always wipe everything, flash eu, factory reset and reboot into recovery to continue the installation maybe that's why I never faced this problem in system partition.
Gsi is a solution not THE solution. But at least we've got correct battery life and fixes for bluetooth and brightness. The more annoying.
What twrp are you using ?
Most stable are full stocks, like PE, AOSDP. I use AICP, RR or AEX on my side with a way better SOT on RR. Nitrogen is a good one too.
Regards
Click to expand...
Click to collapse
At all times I have fc messages on almost everything (system, systemUI and downloaded apps). I always make the installations clean and I always faithfully follow every step to install and I always have these problems. As for Havoc, I installed over nitrogenOS without cleaning anything, and it worked, but it all started to fail continuously. But before that, the Havoc released in January was bootloop. The liquid remix started normally, but when I needed to reboot, it came into bootloop, as well as all roms of December and January. The only ROM that worked well and I was able to reboot the device was nitrogenOS, but when I tried to edit the build.prop in the vendor, when I rebooted the device, the screen did not turn on. And I'm using nijel's TWRP to install the roms. As I said before, there are so many different gadgets that it is impossible for a single rom to work well for everyone.
pakudaboy said:
question is. do you get much better battery life on these roms compare to EU?
Click to expand...
Click to collapse
about the same for me when I used havoc
Germano1980 said:
At all times I have fc messages on almost everything (system, systemUI and downloaded apps). I always make the installations clean and I always faithfully follow every step to install and I always have these problems. As for Havoc, I installed over nitrogenOS without cleaning anything, and it worked, but it all started to fail continuously. But before that, the Havoc released in January was bootloop. The liquid remix started normally, but when I needed to reboot, it came into bootloop, as well as all roms of December and January. The only ROM that worked well and I was able to reboot the device was nitrogenOS, but when I tried to edit the build.prop in the vendor, when I rebooted the device, the screen did not turn on. And I'm using nijel's TWRP to install the roms. As I said before, there are so many different gadgets that it is impossible for a single rom to work well for everyone.
Click to expand...
Click to collapse
What you saying is strange, never facing these issues (system crash or ui or any downloaded app). I think you miss something (wipe data ?) or you don't use eu vendor as base. With bittgapps or opengapps no problem with eu and nigel for any of them. Except Liquid Remix which go easily into bootloop.
Havoc over Nitrogen is interressting, I'll see after my exams. Or if @Nikitel want to try ?
What did you changed in build.prop ?
Btw I'm agree with your last sentence, and we're not many to test them, hard to say what need or don't need to be done. As I'm not a dev, just go forward, blind.
Here's how I install almost every builds. Wipes (cache, dalvik, data, system, sometimes internal) install eu 10.2.1 or 9.1.24 depends, directly reboot into recovery, factory reset, flash mtp fix if needed, system.img and reboot. Sometimes install magisk too before reboot if I use pie gsi over oreo vendor.
Regards
Skyllery said:
Hi everyone, I make this thread because even with all others threads in this forum, we still get the same questions all the day. How boot this gsi ?
So here it is, I'll try to keep it up-to-date. I don't have time to try every gsi out there, you can help me if you have other informations
Click to expand...
Click to collapse
Thanks Skyllery! If you (or other GSI users) could answer this it would be much appreciated, there are so many options that it's become confusing. I've flashed Nijel's TWRP and Xiaomi.eu 10.2.1 today so I'm ready to choose a GSI and have a play around. I don't really care about having a lot of added features and customizations, I just want everything to work. So my question:
Can any of the GSI's currently be made 'complete' and free of bugs with patches and workarounds? As in every feature working correctly including bluetooth audio streaming, brightness control, etc? Which is the best GSI to install from that point of view?
Many thanks
chongo_au said:
Thanks Skyllery! If you (or other GSI users) could answer this it would be much appreciated, there are so many options that it's become confusing. I've flashed Nijel's TWRP and Xiaomi.eu 10.2.1 today so I'm ready to choose a GSI and have a play around. I don't really care about having a lot of added features and customizations, I just want everything to work. So my question:
Can any of the GSI's currently be made 'complete' and free of bugs with patches and workarounds? As in every feature working correctly including bluetooth audio streaming, brightness control, etc? Which is the best GSI to install from that point of view?
Many thanks
Click to expand...
Click to collapse
As you are on 10.2.1 eu try RR. Except AEX, other need to run a pie vendor. Everything working if you apply correctly patches.
If you want stock google experience, flash 9.1.24 eu and try Pixel Experience or Phh-Treble
Regards
Sent from my MI MAX 3 using XDA Labs
Skyllery said:
As you are on 10.2.1 eu try RR. Except AEX, other need to run a pie vendor. Everything working if you apply correctly patches.
If you want stock google experience, flash 9.1.24 eu and try Pixel Experience or Phh-Treble
Regards
Sent from my MI MAX 3 using XDA Labs
Click to expand...
Click to collapse
Everything went fine until I tried to flash the RR system.img. I followed the steps exactly. I chose Install Image, had System Image selected for where to flash, and chose the image file. It starts to install then says:
Error opening: '/external_sd/system-190120-arm64-aonly-vanilla-nosu.img' (I/O error)
Any idea where I might be going wrong? I might try to download the RR image again
thanks for this guide sir.
chongo_au said:
Everything went fine until I tried to flash the RR system.img. I followed the steps exactly. I chose Install Image, had System Image selected for where to flash, and chose the image file. It starts to install then says:
Error opening: '/external_sd/system-190120-arm64-aonly-vanilla-nosu.img' (I/O error)
Any idea where I might be going wrong? I might try to download the RR image again
Click to expand...
Click to collapse
Sorry, was in exams last days, you fix your problem ? seems to be a image problem yes.
gunzgunz said:
thanks for this guide sir.
Click to expand...
Click to collapse
You're welcome, will update it soon
- beast
- lean
- Fred os
Regards
Sent from my MI MAX 3 using XDA Labs
Skyllery said:
Sorry, was in exams last days, you fix your problem ? seems to be a image problem yes
Click to expand...
Click to collapse
I did, after re-downloading the image I was able to flash RR. Thanks!
im experiencing a bug that i think is not necessarily related to the gsi in question but i dont know anyway. ive installed descendant 2.0 following the rr method and it works impressingly well, but each time i reboot, it boots into nijels twrp and it asks for a password for data decryption. to solve it, ive found that if i reboot via fastboot, i doesnt happen, but this needs a computer so its not very helpful. any idea?
btw awesome work, pretty big from u to help us beginner users this much. thank you very much.
Related
Most anticipated news. At last Treble Support for our Redmi 3 (Ido) devices.
Ariafan and WinKarbik made this project for us. What they did - he shared the HALs (Hardware Abstraction Layers simpler - vendor) from the Android Framework, used the cust section (which is useless on custom), moved HALs (vendor) into it. Now we can use this project, there are assemblies from official teams.
Xposed and Substratum work fine, magisk modules are not everything, usual modules and patches look rebuilt under treble, the ways of mounting have changed.
This is from Ariafan
crDroid Treble
On top of it (with standard wipes) you can put GSI firmware (I tested AOSP 8.1 from phhuson). I (Redmi 3 2/16) from the "iron" did not work only taking photos in the stock camera (the video shoots, and they say in Cameringo there is a photo shoot, but I did not check it). Installation through any Recovery with Project Treble support
Download rom: https://yadi.sk/d/EKRUczm33aD7VU
Rom description: CrDroid v4.5, Oreo 8.1
Build date: 2018-08-13.
Our Device is A only. Flash A only gsi.
Credit: Ariafan, Winkarbik from 4pda
Enjoy and hit Thanks below.
Use this thread for Treble discussion for Our Ido.
Reserved
thanks for the great work. i prefer to wait for solved camera issue. because i'm too handsome without camera and i like waiting :laugh:
regards.
iwingmusic said:
thanks for the great work. i prefer to wait for solved camera issue. because i'm too handsome without camera and i like waiting :laugh:
regards.
Click to expand...
Click to collapse
just use cameringo
mesandman said:
just use cameringo
Click to expand...
Click to collapse
i always use cameringo for long time. it is already said problem with camera and only photo shoot and haven't tested either for cameringo so i'm not going to test it. i'm currently enjoying RR without any matter. i've tested RR with treble one and it didn't boot.
iwingmusic said:
i always use cameringo for long time. it is already said problem with camera and only photo shoot and haven't tested either for cameringo so i'm not going to test it. i'm currently enjoying RR without any matter. i've tested RR with treble one and it didn't boot.
Click to expand...
Click to collapse
but i've downloaded though :laugh:
Hi,
Great news and good job. I have twrp.3.2.3.0 for ido, is it compatible with this rom/treble? Can you put here a tutorial to flash treble? I'm a noob on this but I would like to give my ido a new live. Thks and good job.
aftrindade said:
Hi,
Great news and good job. I have twrp.3.2.3.0 for ido, is it compatible with this rom/treble? Can you put here a tutorial to flash treble? I'm a noob on this but I would like to give my ido a new live. Thks and good job.
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-3/development/unofficial-orangefox-recovery-project-t3804923
Now that I have orange fox, how do I flash this treble cr Droid rom? Thks
aftrindade said:
Now that I have orange fox, how do I flash this treble cr Droid rom? Thks
Click to expand...
Click to collapse
Don't know about OrangeWolf because I'm using RedWolf cust version
-Wipe everything
-Install ROM +Gapp +magisk 16.7
-reboot
aftrindade said:
Now that I have orange fox, how do I flash this treble cr Droid rom? Thks
Click to expand...
Click to collapse
-install your rom treble (cr Droid-8.1-v4.5 20180813 or RR-O-v6.1.0-20180811) reboot system
-back to twrp orangewolf
-wipe : system, data, cache
-mount : data, vendor, cache, microsd
-install image : choose arm64 A - I tested : RR (pphusson), RR (official), Pixel Experience (official) from 4pda
-reboot system
good luck
aftrindade said:
Now that I have orange fox, how do I flash this treble cr Droid rom? Thks
Click to expand...
Click to collapse
i haven't used orange fox either but i always do clean install in every flashing to make sure everything goes well by wiping dalvik, system, data, internal storage & cache then getting rom + gapps into install queue then wiping dalvik again. don't forget to backup internal storage first.
ghue2311 said:
-install your rom treble (cr Droid-8.1-v4.5 20180813 or RR-O-v6.1.0-20180811) reboot system
-back to twrp orangewolf
-wipe : system, data, cache
-mount : data, vendor, cache, microsd
-install image : choose arm64 A - I tested : RR (pphusson), RR (official), Pixel Experience (official) from 4pda
-reboot system
good luck
Click to expand...
Click to collapse
Thank you for the info!
Are the treble roms you tried good for daily usage?
Which one would you recommend?
SciG said:
Thank you for the info!
Are the treble roms you tried good for daily usage?
Which one would you recommend?
Click to expand...
Click to collapse
yes, i have tried both... i think cd droid 20180813 better than rr 20180811
ghue2311 said:
yes, i have tried both... i think cd droid 20180813 better than rr 20180811
Click to expand...
Click to collapse
how did you get rr 20180811 working? failed to finish pixel setup on me.
any working screenshots?
Last crdroid rom boots on my Redmi 3, but Camera app not working. RR still buggy, stuck in boot after installation.
Rdeniro67 said:
Last crdroid rom boots on my Redmi 3, but Camera app not working. RR still buggy, stuck in boot after installation.
Click to expand...
Click to collapse
i don't know much about treble, but if you have flashed treble system image, maybe included when you flashed crdroid that has unworking camera, it means that you could flash/change to rom from any official GSIs from crdroid or rr after, doesn't it?
iwingmusic said:
i don't know much about treble, but if you have flashed treble system image, maybe included when you flashed crdroid that has unworking camera, it means that you could flash/change to rom from any official GSIs from crdroid or rr after, doesn't it?
Click to expand...
Click to collapse
Only Crdroid rom boots, even after I installed it any ohter 8.1 rom (rr , pixel exp.) not booting. I went back to Lineage, it is still 7.1.2 but working without problems for me.
Hello everyone. Today or tomorrow I will push rr treble after fixing some bugs
What is this topic about?
I've spent quite some time writing fixes for GSIs to work properly on our Mi Max 3.
As part of that, we now have a list of easily flashable fully working Mi Max 3 ROMs to pick from.
This topic will be used to keep track of all fully working ROMs and of course to host the latest set of GSI patches / flash templates.
Available ROMs:
These have been tested and confirmed fully working (sans ROM-specific bugs).
AOSiP
Build date: 2019-05-14
Patch date: 2019-05-17
Flashing guide:
Unlock your device's bootloader.
Flash nijel8's modded TWRP recovery.
Pick and download one of the available ROMs.
Reboot into TWRP recovery and flash your ROM of choice.
Go into TWRP's wipe menu and "factory reset" your device (aka. slide the bar).
Flash Gapps (Opengapps / Bitgapps) if your ROM of choice requires / you want it.
Reboot your phone and set it up to your liking.
How can I get my ROM of choice listed here?
Download the TWRP package template from here!
Grab a GSI of your choice and unpack the system image (if it is compressed).
Rename the unpacked system image to system.img and place it inside the system folder inside the template zip file.
Rename the resulting zip file accordingly, flash it, test it, and after you've confirmed everything's working fine, upload and share it.
How do I enable DT2W (double-tap to wake)?
Create a file named "enable_dt2w" (without the quotes) in your device's internal storage.
Reboot your device.
Changelog:
2019-05-17
Changed cpusets to 0-7 (UX gains)
Set rendering thread to schedule as FIFO (UX gains)
Updated AOSiP to its latest (2019-05-14) build
2019-05-10
Swapped firmware & vendor base to stable 10.3.1.0
Updated AOSiP to its latest (2019-05-07) build
2019-05-01
Added two touchscreen-related properties to build.prop
2019-04-30
Updated the kernel to ResurrectedKernel 5.0 (brings a whole bunch of new governors)
Changed default little core governor to alucard
Changed default big core governor to darknessv5
Updated AOSiP to its latest (2019-04-29) build
2019-04-22
Fixed a mistake on my end that made the screen flicker on brightness changes (sorry guys)
Updated the kernel to ResurrectedKernel 4.1 (kcal support!)
Updated AOSiP to its latest (2019-04-22) build
2019-04-21
Fixed the device fingerprint issue (Magisk users should now be CTS-verified by default again)
Added AptX & AptX HD Bluetooth support
Removed DotOS & PixelExperience from the rooster because the WiFi HotSpot function wasn't working properly in them
2019-04-12
Added addon.d support (which means dirty-flashes won't lose their Gapps, Magisk, etc. anymore)
Tested and added Pixel Experience to the roster
2019-04-10
Added ResurrectedKernel (Unlocks 1.8GHz on Little Core / 2.0GHz on Big Core)
Tweaked Governor to utilize ResurrectedKernel's frequency range fully
Updated DotOS bundle to latest build
Repacked all bundles with latest patch
Dropped "Minimal Package" support as its no longer maintainable in tandem with ResurrectedKernel
It ended up with the lags (AOSIP).
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Germano1980 said:
It ended up with the lags (AOSIP).
Click to expand...
Click to collapse
Where's the lag Germano? Works fine for me.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
Stuck how? If you have "unlock" trouble, as in, your PIN won't let you in, use the "Remove lockscreen" option inside TWRP to remove your previous lockscreen data.
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
MrColdbird said:
Where's the lag Germano? Works fine for me.
Click to expand...
Click to collapse
Before installing their zip, they had some lags in screen transitions and to slide and open apps. Now, everything got more fluid and faster. It was great ... until voLTE is working (and my operator informed me that my device was not compatible with haha).
---------- Post added at 19:14 ---------- Previous post was at 19:07 ----------
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
What vendor is your device on? Many GSI's only start at a particular vendor (Oreo or Pie).
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
Make sure the GSI you picked supports Pie vendors.
Not every GSI does... and the ones that are still stuck on Oreo vendors are... troublesome, to say the least.
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
The last time I had problems in booting the GSI roms I did the following:
1- I reinstalled the latest global version of Miui Oreo via miflash (Beware of ARB)
2- Logged in the Mi account, enabled the USB debugging and installation by ADB settings to install the TWRP
3- I installed TWRP (nijel8's modded), formatted the data and then installed xiaomi.eu
4- I configured the device and made a backup of xiaomi.eu
5- As I already had the files, I installed AOSIP, without deleting the system, just cleaning the data of xiaomi.eu
6- After the boot, I installed the gapps and magisk.
I never had any problems installing GSI's on my device.
When I was in Miui Oreo, I tested some roms that only boot the Oreo vendor (Bootleggers, PixelDust among others), but I think with the Oreo vendor they spend a little more battery life.
(hope this helps you)
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Masacci0 said:
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Click to expand...
Click to collapse
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Skyllery said:
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Click to expand...
Click to collapse
So if i install this rom https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ i'm ok and without arb? I get confused because on the image they say mi max 3 has arb, if they mean the official 10.2 has arb, why even put the image in the .eu version? It just confuses people.
So i go with this rom reach setup screen, recovery and install the gsi rom?
Jesenican said:
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Click to expand...
Click to collapse
Try the xiaomi.eu versions from last month based on installing AOSiP. Today I tried with the versions of this month and did not boot.
I am having the exact same issue. I followed the guide and installed the latest xiaomi.eu 9.3.7 beta and boot no problem then i flash gsi .img and it gets stuck at MI Logo and wont go any further. I have tried latest xiaomi.eu beta, stable, last months, month before that. All xiaomi.eu boot fine without issue but as soon as I flash any gsi .img it gets stuck at MI Logo screen? Am I doing something wrong?
Also the gsi i am using is latest pixel experience arm64 A only.
Any help would be greatly appreciated.
Same. I tried 3 different GSI roms and kept being stuck on the mi logo... :'(
only aosp gsi works, still getting android.process.media and bluetooth crashes
Edit: instead of com.android.media it was android.process.media
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
jngiag said:
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
Click to expand...
Click to collapse
You're my hero! That did the trick. ;D
So can i normaly flash older xiaomi.eu version without fear of ARB?
OP post updated with a new package.
Changelog:
Tweaked the governor to boost properly and use the 1.6 / 1.8GHz maximum little / big frequencies. (Everything's even smoother now~)
In-Call Volume and Cracking sound Fix For Xiaomi Mi Max 2 (oxygen) Thanks To snekkill
Hello guys in this post I am going to tell you to step by step method to fix in call volume issue in all pie Roms for our Xiaomi MI Max 2 device. So guy's special thanks to @snekkill who done a great job for our device. I used his boot & vendor source and created a flashable zip file.
Credits :
Special thanks to :
snekkill for updated boot and vendor.
@MaheshTechnicals For Patch File.
Working on: Pie ROMs (Android 9.0) ONLY. NOT WORKING ON MIUI ROMS
How to flash :
CLEAN FLASH RECOMMENDED.
1. Flash any pie rom.
2. Flash fix zip then reboot your phone.
3. Again go to recovery.
4. Flash Gapps
5. Flash magisk (if u want).
6. Reboot system. Done. the in-call volume will fix.
I personally tested on
AOSP BASED ROMS:
ArrowOS,
pixel Experience plus,
BootleggersROM (no need),
AOSIP
AOSMP
AICP
AOSP Extended.
LINEAGE BASED ROMS:
Lineage os
Resurrection Remix
Not Working On :
YOU TELL ME
Downloads :
AOSP BASED
In-Call Volume and Cracking sound Fix Zip File. (use latest one).
29 Oct 2019: in-call volume fix zip.
Changbg :
in call volume fix.
30 Oct 2019: in-call volume fix zip v2
Changlog:
• update vendor
• fixes for sound reduced headphone and speaker volume.
LINEAGE BASED (Works on LineageOS, RR, etc).
09 Nov 2019: in-call volume fix zip v3 (Lineage based)
Changlog:
• supported for lineage based ROM's.
• update vendor
• updated boot.
XDA:DevDB Information
In-Call Volume Fix For Android Pie ROMs, Tool/Utility for the Xiaomi Mi Max 2
Contributors
MaheshTechnicals
Version Information
Status: Stable
Current Stable Version: V2
Stable Release Date: 2019-10-30
Created 2019-10-30
Last Updated 2019-10-30
Great... New update available... a huge thanks to @snekkill
[email protected] said:
Great... New update available... a huge thanks to @snekkill
Click to expand...
Click to collapse
Yup ?
Great job guys, you're on fire! Thanks for your efforts.
Awesome! Finally, we have the long awaited solution to make our beloved MM2 one of the best budget phone out there!
Big thanks to snekkill to find the solution and generously sharing his sources with Mahesh. And big thanks also to Mahesh for his time and effort in offering us so many updated ROMs.
Looking forward to trying this on Havoc 2.9. Would I still need to flash the echo fix of BeingTejas?
EyeBalos said:
Awesome! Finally, we have the long awaited solution to make our beloved MM2 one of the best budget phone out there!
Big thanks to snekkill to find the solution and generously sharing his sources with Mahesh. And big thanks also to Mahesh for his time and effort in offering us so many updated ROMs.
Looking forward to trying this on Havoc 2.9. Would I still need to flash the echo fix of BeingTejas?
Click to expand...
Click to collapse
Echo is fixed already.
Also the sound is Good like MIUI Stock 7.1.
You can use Graphic drivers though.
Havoc OS 2.9 works best, snekkill made a complete rom for that. You can use any pie rom, mostly are working with fix zip.
Tip: QC works best when you put phone in charger , wait few seconds and reboot.
Just a dumb question.. How to flash this fix along with v385 graphics driver? I couldn't get both of them working together. After doing all the steps, AIDA64 shows v269 driver. Could anyone make a step by step?
Moresche said:
Great job guys, you're on fire! Thanks for your efforts.
Click to expand...
Click to collapse
Thanks ?
Moresche said:
Just a dumb question.. How to flash this fix along with v385 graphics driver? I couldn't get both of them working together. After doing all the steps, AIDA64 shows v269 driver. Could anyone make a step by step?
Click to expand...
Click to collapse
First flash rom+fix +graphics drivers
Hi, your LOS16 rom (https://androidfilehost.com/?fid=4349826312261606268) is not booting in system. Stuck at boot animation with these both fixes.
Can you pls check and resolve.
I already tried the following steps mentioned in your Arrow thread:
After flashing rom if you are stuck on boot logo (MI logo) then follow this steps :
A. Boot your phone into fastboot mode using volume down + power key.
B. Wait 5 sec on fastboot mode then long press on power key to restart your phone. It will fix that stuck MI logo error.
Note : after flashing a rom if you stuck on bootanimation then follow this steps :
A. Boot your phone into recovery mode. Go to wipe section turn wipe dalvik +chdches.
B. GO back to home page on recovery. Go to reboot/fastboot (bootloader).
C. Wait 5 sec on fastboot mode then long press on power key to restart your phone. It will fix that stuck bootanimation error.
on dirty rom havoc os 2.9 is ok great
@sebastianos80: did you mean you just dirty flashed the In-call Volume Fix .zip file onto your existing Havoc 2.9?
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
[/COLOR @sebastianos80: did you mean you just dirty flashed the In-call Volume Fix .zip file onto your existing Havoc 2.9?
Tak,yes
not working on miui11 pie based rom
MaheshTechnicals said:
In-Call Volume and Cracking sound Fix For Xiaomi Mi Max 2 (oxygen) Thanks To snekkill
Hello guys in this post I am going to tell you to step by step method to fix in call volume issue in all pie Roms for our Xiaomi MI Max 2 device. So guy's special thanks to @snekkill who done a great job for our device. I used his boot & vendor source and created a flashable zip file.
Credits :
Special thanks to :
snekkill for updated boot and vendor.
@MaheshTechnicals For Patch File.
Working on: Pie ROMs (Android 9.0) ONLY.
How to flash :
CLEAN FLASH RECOMMENDED.
1. Flash any pie rom.
2. Flash fix zip then reboot your phone.
3. Again go to recovery.
4. Flash Gapps
5. Flash magisk (if u want).
6. Reboot system. Done. the in-call volume will fix.
I personally tested on
AOSP BASED ROMS:
ArrowOS,
pixel Experience plus,
BootleggersROM (no need),
AOSIP
AOSMP
AICP
AOSP Extended.
LINEAGE BASED ROMS:
Lineage os
Resurrection Remix
Not Working On :
YOU TELL ME
Downloads :
AOSP BASED
In-Call Volume and Cracking sound Fix Zip File. (use latest one).
29 Oct 2019: in-call volume fix zip.
Changbg :
in call volume fix.
30 Oct 2019: in-call volume fix zip v2
Changlog:
• update vendor
• fixes for sound reduced headphone and speaker volume.
LINEAGE BASED (Works on LineageOS, RR, etc).
09 Nov 2019: in-call volume fix zip v3 (Lineage based)
Changlog:
• supported for lineage based ROM's.
• update vendor
• updated boot.
XDA:DevDB Information
In-Call Volume Fix For Android Pie ROMs, Tool/Utility for the Xiaomi Mi Max 2
Contributors
MaheshTechnicals
Version Information
Status: Stable
Current Stable Version: V2
Stable Release Date: 2019-10-30
Created 2019-10-30
Last Updated 2019-10-30
Click to expand...
Click to collapse
NOT WORKING ON MIUI11 pie BASED ROM
kaleemk32 said:
NOT WORKING ON MIUI11 pie BASED ROM
Click to expand...
Click to collapse
It will work only on AOSP and lineage based Roms.
does this fix the echo?
JimmyEatFood said:
does this fix the echo?
Click to expand...
Click to collapse
yes
[email protected] said:
yes
Click to expand...
Click to collapse
thanks
My phone no longer boots after flashing this so-called fix
fryslanboppe said:
My phone no longer boots after flashing this so-called fix
Click to expand...
Click to collapse
You did something wrong? Which fix you flashed on which ROM?
My LuisROM based on cdDroid V6.x for Xiaomi Redmi 4x (santoni)
Code:
*** Disclamer
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is my personal custom rom. LuisROM based on the crDroid, LineageOS and other...
This is a ROM that works on Xiaomi Redmi 4x (santoni) snapdrgon only! This ROM comes with a highly-customized kernel, as well as some other very custom modifications.
I will NOT provide support if you install a custom kernel!
Changelogs: http://luis-builds.de/downloads/lineageos/cr/Xiaomi_Redmi_4X_(santoni)/changelog_santoni.txt
Introduction
Hello Friends!
I had troubles to find current builds for my devices so I decided to make regular builds for my devices. When my friends told me about similar problems, I extended the builds to include their devices as well. So these builds were and are mainly for my friends and me, but I finally decided to provide them also for public download.
My ROMs
My LuisROM an awesome combination of performance, customization, power and the most new features, brought directly to your device. The LuisROM build server generates automaticly every 2nd days new builds directly from the sources.
Notice
Sometimes I get a lot of help or feature requests from users of my LuisROMs. My dog Luis and I try to fulfill most of the wishes, but that is not always possible. I do that as a little hobby and Luis does not always want to build ROMs . Please understand if I can not always answer directly.
ROM features:
Based on the latest cdDroid V6.x (Android 10), LineageOS and AOSP sources
Latest security patches and sources
OTA Updater
Compatible with EX Kernel Manager
Many other misc. performance and stability improvements under the hood
Kernel: Linux 3.18.x Kernel with many mods other devs and me (thanks for your incredible work!)
Removed lots of excessive bloat (improves security and performance)
Improved stability (several bugs not listed here have been fixed)
Boeffla Wakelock blocker driver V1.1.0
More I/O-Schedulers (fiops, sio, zen, maple)
Optimized for performance and battery life
Compatible with systemless root (recommend Magisk 20.x !!!)
Many other misc. improvements not listed here
Installation instructions:
Pre-installation:
OrangeFox Recovery of course (download here)
Tested with "V11.0.2.0.NAMMIXM" firmware. (download here)
Magisk 20.x and above (Link) can also be used just make sure you flash it after a first successful boot (after passed setup screen)
First time installation:
Unlock your bootloader
Install lates MIUI firmware (tested V11.0.2.0.NAMMIXM)
Flash recovery zip (TWRP)
Flash my latest LuisROM (download here)
Optional: Flash Open GApps and Magisk 20.x and above
Reboot and enjoy
OTA App update installation (auto):
Go to crDroid > About cdDroid > Updates
Press reload button (right corner)
Select download on the new build list
After download select update/flash new build
Optional: Installed gapps and magisk will be moved into new system automaticaly !
TWRP update installation (manual):
Download latest LuisROM build (download here)
Boot into Recovery TWRP
Flash my updated LuisROM (download here)
Reboot and enjoy
Download
Latest builds: (http://luis-builds.de/downloads/lineageos/cr/Xiaomi_Redmi_4X_(santoni)/)
Latest MIUI firmware: (download)
My other devices/ROMs: (http://luis-builds.de/downloads/lineageos/)
Download OpenGapps: (http://opengapps.org)
Flash latest OrangeFox Recovery: (download here)
Donate for my dog Luis, he is looking forward to an extra bone:
https://bw2.link/LuisDonation
Changelog
Developer: http://luis-builds.de/downloads/lineageos/cr/Xiaomi_Redmi_4X_(santoni)/changelog_santoni.txt
Known Issus
..
Telegram group:
https://t.me/rr_luisrom
Thanks To/Credits
Special thanks to Teams:
LineageOS team: https://www.lineageos.org
crDroid Team: https://crdroid.net/
OMNI team https://omnirom.org/about/
SLIMROMS https://slimroms.org/#/about
topjohnwu (Magisk) https://forum.xda-developers.com/apps/magisk
Thanks to the best devs on earth:
LuK1337 (https://forum.xda-developers.com/member.php?u=5075128)
PeterCxy (https://forum.xda-developers.com/member.php?u=5351691)
francokernel (https://forum.xda-developers.com/member.php?u=3292224)
sultanxda (https://forum.xda-developers.com/member.php?u=4800121)
flar2 (https://forum.xda-developers.com/member.php?u=4684315)
nathanchance (https://forum.xda-developers.com/member.php?u=6842057)
zx2c4 for the wireguard vpn ROM Integration (https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635)
phhusson for some blobs (https://github.com/phhusson)
and of course to all the supporters.
Thanks for the Sources/Blobs/Tweaks
ProtoDump (https://github.com/LineageOS)
Omnirom (https://github.com/omnirom)
TheMuppets (https://github.com/TheMuppets)
ryan-andri (https://github.com/ryan-andri)
AliHasan7671 (https://github.com/AliHasan7671)
zeelog (https://github.com/zeelog)
My Sources/Blobs/Tweaks
DEVICE (https://github.com/FraEgg/android_device_xiaomi_santoni_ra)
KERNEL (https://github.com/FraEgg/android_kernel_xiaomi_msm8937)
XDA:DevDB Information
[ROM][SANTONI][10]LuisROM Android 10 based on crDroid V6.x, ROM for the Xiaomi Redmi 4X
Contributors
8224Freak
Source Code: https://github.com/FraEgg
ROM OS Version: Android 10
ROM Firmware Required: V11.0.2.0.NAMMIXM
Based On: LineageOS, crDroid, AOSP
Version Information
Status: Beta
Beta Release Date: 2020-03-24
Created 2020-03-24
Last Updated 2020-03-24
Reserved
Great rom. Only one bug, the speaker is silence unless the headphone is plugged.
crDroidAndroid-10.0-20200321-santoni-v6.4-LuisROM
is normal.
Stuck at fastboot...
Hello,
I've a little problem. I've used LuisROM RR for a long time. Now I want to switch to LuisROM CR.
I did a clean install with the newest crDroidAndroid-10.0-20200331-santoni-v6.4-LuisROM.zip, the newest FW and newest OrangeFox.
During the installation of the ROM, there was a message "Cannot mount the storage".
Now it reboots only into fastboot.
An installation with the old LuisROM RR works without a problem.
Any ideas?
Thx,
wayne
---------- Post added at 12:50 PM ---------- Previous post was at 12:38 PM ----------
OK.
The old version crDroidAndroid-10.0-20200215-santoni-v6.3-LuisROM-ota.zip works...
An the Upgrade from crDroidAndroid-10.0-20200215-santoni-v6.3-LuisROM-ota.zip to
crDroidAndroid-10.0-20200331-santoni-v6.4-LuisROM.zip didn't work, same problem, stuck at fastboot...
:crying:
Maybe you should clear the internal storge.
However, the newer roms have bugs.
@wayne5de try to install magisk after installing rom. The phone will start, but there will be no sound from the main speaker. The last working version is probably 20200319.
doopek said:
@wayne5de try to install magisk after installing rom. The phone will start, but there will be no sound from the main speaker. The last working version is probably 20200319.
Click to expand...
Click to collapse
What do you mean with "no sound". My phone rings, I can talk and hear the other person.
At the moment 20200215-santoni-v6.3-LuisROM is installed with magisk.
There have been some bug since a few versions, which results in the lack of sound from the main speaker. You don't hear ringtones or music. Calls are working correctly. If this speaker works for you, I will have to try the latest version again. This morning I tried dirty flashing and the sounds didn't work.
I also can verify that sounds does not come from the main speaker on a fresh install. Just tried it and work's from the main speaker only if headphones are plugged
In this latest version, the phone's sound does not work
@8224Freak there has been a problem with your builds for several versions.
After a dirty flash, the system boots up but there is no sound from the main speaker. The talk speaker works.
After clean flash the phone starts in fastboot mode. Installing magisk fixes startups but no sounds yet.
Logs attached after installation with recovery and already running system.
The last good is probably 20200319 or the first next.
Stuck on fastboot
When I flash and reboot my phone the phone got stuck in fastboot mode.
Please fix this issue
Thanks for rom,
crDroidAndroid-10.0-20200319-santoni-v6.4-LuisROM
but is slowly and I' reporting what doesn't work:
- for a dark colour scheme backround of phone calls is not dark
- why on upper belt is max 6 icon/shortcuts ? rest of roms usually has 8
- why system (990+149+121 +101+85 MB !) uses up 1446 MB of memory ?
- why system has up 31 aplications ? Roms has usually 22-26
- level of corrections to producer protection is very old, but from 01.10.2018 !?!?!
- system doesn't has advanced restart
When could You reparing ? I saw new version but could You cofirmed that is free of those bugs ?
Speaker not working.!?
(drive.google.com/file/d/1-svW-RFpG8YzFsan3U9iOuF0zbpHYW6E/view?usp=drivesdk) - remove brackets
(drive.google.com/file/d/1-sfP88RdHSvjs-3dx2QnLrz-WAxErQ8C/view?usp=drivesdk) also remove brackets (new member stuff, sorry)
I can't download it rom,gps does not catch well,only 3-5 satellites
Fixed: stuck on fastboot and no sound...
FYI:
These two problems are fixed: stuck on fastboot and no sound...:good:
I did a dirty flash from the old crDroidAndroid-10.0-20200215 to the newest crDroidAndroid-10.0-20200427.
Thx for your good work! :highfive:
No camera works...
With the newest update crDroidAndroid-10.0-20200504 no camera works... :crying:
wayne5de said:
With the newest update crDroidAndroid-10.0-20200504 no camera works... :crying:
Click to expand...
Click to collapse
But does the phone work well ?
Are there any other bugs?
Do you have the sound good now?
For the camera, I recommend 2 apk that I use:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera
https://play.google.com/store/apps/details?id=com.caddish_hedgehog.hedgecam2
As I said before: These two problems are fixed: stuck on fastboot and no sound...
I also use open camera, but this, the standard camera, HD-camera, ... didn't work!
After dirty flash (from build 20200429 to 20200501) my phone stuck on cr logo but after clean install everything is ok.
Same situation after dirty flash from build 20200501 to 20200504.
On 20200504 build ...... no camera (open camera, gcam) is working. Back to 20200501.
Hello everyone!
This is a dotOS port from the Galaxy J3 2016 (made by @lucas000br) to the J2 2016.
Working:
My (basic) testings all seemed to work quite well
Added features and patched bugs:
Patched lock button in boot.img
Pre-rooted the ROM
Added FM-Radio from ViperOS (microG variant only)
Optimized features
Signature spoofing patched on microG variant
[See post #2 for further information]
Known problems:
Gapps variant is laggy (nothing I can do - Google sucks)
Your J2 shows up as a J3 (it's a port that's why)
Download links and installation instructions can be found in post #2
Credits:
Nanolx for Signature Spoofing
PixelBoot for base
lucas000br for modified base
Me for everything else
Obligatory Links:
Kernel Source: Github
Original Build (Abandoned by PixelBoot): XDA Developers (No source code)
Port of Port (by lucas000br): Thread seems to have disappeared?
Variant information (Which one is which?)
GAPPS: This one has most of the stock Google apps (Drive, YouTube, etc) + GSF present. Recommend for most users. RAM usage 640mb on idle
microG: All Google apps have been replaced with FOSS software. Google Services Framework has been replaced with microG. Signature spoofing is also present. RAM usage 560mb on idle
DIY: Want to build your own ROM? This one's for you! Everything except the bare minimum has been stripped out, so that you can decide what to pick for your ROM. (For power users only).
Stock dotOS: The stock dotOS compiled by PixelBoot for J3 2016; with Wi-Fi, Bluetooth, Signature spoofing and Power Button patched. Most stable out of all. You will need to flash additional GAPPS to get Google Services. RAM Usage 500mb.
Download Links:Stock dotOS (Recommended): MEGA
GAPPS: Oreo-Themed dotOS
microG: Oreo-Themed dotOS
DIY: Oreo-Themed dotOS
Installation Instructions:[If you don't have TWRP, get an image and install it from here]
GAPPS:
Boot to TWRP
[Do make sure to backup your data]
Wipe Dalvik, Data, System, Cache
Flash the ROM
Reboot. Done!
microG:
Boot to TWRP
[Do make sure to backup your data]
Wipe Dalvik, Data, System, Cache
Flash the ROM
After rebooting, open microG settings.
Go to self-check and tick the check boxes that are unticked (that will initialize microG)
Go back, and enable Device Registration, Cloud Messaging and Device Attestation
Then go to Location backends, and configure the DejaVu and Nominatim backends.
Done!
DIY and Stock dotOS will be the same as GAPPS variant
Changelog:
v1.2: Initial release06/05/2021: After lucas' comment, I realized that this wasn't the stock dotOS. So I have ported the stock dotOS created by PixelBoot. Try it out!
lucas000br said:
well done!
Also, PixelBoot did the DotOs base rom, i just modified it to be more like Android Oreo
(dont worry because i credited PixelBoot in the original j3 thread)
Click to expand...
Click to collapse
oops I need to credit him
Thanks for informing!
good soon try it out
i have flashed stock rom provided by u of dot os but my phone stuck at samsung logo pls look into it .....i am sure i have flashed it n follow all steps correctly
Uniqueshiva said:
i have flashed stock rom provided by u of dot os but my phone stuck at samsung logo pls look into it .....i am sure i have flashed it n follow all steps correctly
Click to expand...
Click to collapse
okay I'll try flashing it again. wait
NullCode said:
okay I'll try flashing it again. wait
Click to expand...
Click to collapse
btw i don't have stock rom installed before i flash it......I am on viper os....then i boot to twrp wipe sytem cache data n flash your provided dot os stock rom then i reboot but stuck at Samsung logo
@Uniqueshiva thank you for the information. I had made a typo in the updater script that caused the boot image to fail.
Please download the new ROM and flash it. I've confirmed it to work
NullCode said:
@Uniqueshiva thank you for the information. I had made a typo in the updater script that caused the boot image to fail.
Please download the new ROM and flash it. I've confirmed it to work
Click to expand...
Click to collapse
thx for responding so fast btw i will try it tomorrow as my data got finished today sorry for it...i will surely give feedback
edit- I tried stock dos os rom n flash arm 7.1 Pico gapps...boot animation appears but after sometimes black-brown screen appears after 5 min phone started but its written setup wizard failed i am not able to go ahead as setup wizard failed written every time so i turn off the phone maybe it can be the gapps problem now i will try dot os magisk gapps version provided by u btw i am curious that what is DIY dot os u give is all bugs fixed in it just asking..
Uniqueshiva said:
thx for responding so fast btw i will try it tomorrow as my data got finished today sorry for it...i will surely give feedback
edit- I tried stock dos os rom n flash arm 7.1 Pico gapps...boot animation appears but after sometimes black-brown screen appears after 5 min phone started but its written setup wizard failed i am not able to go ahead as setup wizard failed written every time so i turn off the phone maybe it can be the gapps problem now i will try dot os magisk gapps version provided by u btw i am curious that what is DIY dot os u give is all bugs fixed in it just asking..
Click to expand...
Click to collapse
hmm it could be flashing gapps causes problem with the rom...
yes try the gapps version i provided
the diy one is mainly for rom porters. it has many features removed so that rom porters can think about what features to add in the rom
only basic feature available in rom is phone and messaging support
I can't access internal storage after flashing. Stock file manager crashes if i open it. Stock browser says "no sd card, usb storage is required to download the file". There's no internal storage even after connecting the phone to pc. It only shows memory card.
Edit: Just wiped the internal storage and re-flashed it. Works fine now
Thanks for porting this amazing rom
@NullCode, thanks for your work for device j210f...I like the ui of dot os..but i must say your previous build i.e viper os was more stable n amazing atleast for me....btw thanks a lot for keeping this device alive...
Dark theme not working in settings and other apps.Any help?
shayara said:
Dark theme not working in settings and other apps.Any help?
Click to expand...
Click to collapse
there's a theming option in settings > display > scroll to the end
from there figure out what to do (I've confirmed its working)
Uniqueshiva said:
@NullCode, thanks for your work for device j210f...I like the ui of dot os..but i must say your previous build i.e viper os was more stable n amazing atleast for me....btw thanks a lot for keeping this device alive...
Click to expand...
Click to collapse
I know, viperOS was much more stable because I took 1 entire year to port and test the rom (i started testing January 2020 )
however, dotOS was ported in only 1 month
so it is not as polished
but im glad you liked it
NullCode said:
Hello everyone!
This is a dotOS port from the Galaxy J3 2016 (made by @lucas000br) to the J2 2016.
Working:
My (basic) testings all seemed to work quite well
Added features and patched bugs:
Patched lock button in boot.img
Pre-rooted the ROM
Added FM-Radio from ViperOS (microG variant only)
Optimized features
Signature spoofing patched on microG variant
[New] 2 more ROM options to choose from (with varying features)
[See post #2 for further information]
Known problems:
Gapps variant is laggy (nothing I can do - Google sucks)
Your J2 shows up as a J3 (it's a port that's why)
Download links and installation instructions can be found in post #2
Credits:
Nanolx for Signature Spoofing
PixelBoot for base
lucas000br for modified base
Me for everything else
Note: You might've noticed how I didn't put [PORT] in the thread title. It is mainly because this ROM varies from J3's dotOS so much, I don't think it is fair to call this one a port.
Click to expand...
Click to collapse
Hey.
I am using this ROM since 6th May (stock variant) and it is very great but has lots of bugs.
1. Bluetooth Audio stutters really bad (problem in every Android N rom for this phone)
2. Google Meet doesn't work (just shows the logo and then crashes) I am using Open GAPPS
3. Many system app crash randomly (sometimes even the launcher and system ui) requiring me to take out the battery and restarting the phone.
4. Camera quality is significantly bad compared to stock 6.0
But still a great project.
Thank you for keeping this phone updated.
NullCode said:
there's a theming option in settings > display > scroll to the end
from there figure out what to do (I've confirmed its working)
Click to expand...
Click to collapse
Okay.Thnx.
NullCode said:
I know, viperOS was much more stable because I took 1 entire year to port and test the rom (i started testing January 2020 )
however, dotOS was ported in only 1 month
so it is not as polished
but im glad you liked it
Click to expand...
Click to collapse
Omg 1 year......that's y it feels so smooth in viper os i get nearly 900 mb free ram with gapps again thanks for your hardwork.....I know that u may be bored now for working on j210f that is old device but still hoping for more
Uniqueshiva said:
Omg 1 year......that's y it feels so smooth in viper os i get nearly 900 mb free ram with gapps again thanks for your hardwork.....I know that u may be bored now for working on j210f that is old device but still hoping for more
Click to expand...
Click to collapse
My build has more free ram and battery btw.