It's AOSP time ..
Android Pie ..
manta-Classic_Pie_08-2019_AOSP_9.0.0_r46_followmsi.zip --> DISCONTINUED
AospExtended-v6.7-manta-20191018-1203-UNOFFICIAL.zip --> DISCONTINUED
Known issues:
- NavBar works good, but no icons visible. (AospExtended only)
- NFC may not work correctly and drains a lof of battery - Pls disable thru settings menu.
- HWC (hardware composer) is partly broken (icons are not shown correctly and black home screen)
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
Oreo ..
manta-Classic_01-2019_AOSP_8.1.0_r60_followmsi.zip --> DISCONTINUED
Known issues:
- Headphone jack is not fully working (Pls use the "AudioJack" kernel -> 3.4.67 - current standard kernel for all Oreo ROMs)
- If you install Magisk, pls disable Magisk "Hide" feature. (3.4.113 kernel issue)
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
Nougat ..
AOSP_7.1.2_r28_N2G48C_manta-ota-eng.followmsi-v1.zip --> DISCONTINUED
Known Issues:
- Camera is not working (broken HAL1 camera and unsupported HAL2 camera)
- Bluetooth is not working - fixed
- Audio jack is not working - fixed (still "old" kernel - 2017-05-09)
System and Cache repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system and cache partitions .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 800mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 800mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
For manual repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77759823&postcount=953
https://forum.xda-developers.com/showpost.php?p=77762148&postcount=954
For automatic repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77764246&postcount=957
https://forum.xda-developers.com/showpost.php?p=77770425&postcount=960
@ipdev - Thanks for your TWRP flashable repartitioning package !
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (Not required if you upgrade from previous build)
3. Install ROM.zip from above
4. install opengapps or beansgapps (arm) (optional)
5. install SuperSU.zip and/or Magisk.zip
6. Reboot into system
- Please install Magisk.zip and/or SuperSu.zip yourself.
- Due to systemless rooting - if you have installed magisk and/or supersu before you need to install it again !
- If you install SuperSu.zip it will boot twice - no panic, it's normal !
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- If you face any strange issues, pls do a factory reset via TWRP first.
Gapps:
The AOSP installer does not support "/system/addon.d/" scripts !
For this reason Gapps are not persistent like in LineageOS or in other custom ROMs.
I have modified the installer script to add this functionality.
You should be able to keep your gapps installation when you upgrade the ROM.
SuperSU and/or Magisk:
SuperSU.zip and/or Magisk.zip has always to be installed after ROM installation/upgrade - because of systemless rooting.
If you install SuperSu.zip it will boot twice - no panic, it's normal !
SOURCES:
If you want to build your own ROM ..
https://github.com/followmsi/manifests/tree/manta-aex-pie
https://github.com/followmsi/manifests/tree/manta-aosp-pie
https://github.com/followmsi/manifests/tree/manta-aosp-oreo
https://github.com/followmsi/manifests/tree/manta-aosp-nougat
DOWNLOAD:
https://androidfilehost.com/?w=files&flid=289294
https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk
Thanks to @sooti and @Khaon !
Enjoy
Is this "Pixel C" version with new tablet recents?
stunned said:
Is this "Pixel C" version with new tablet recents?
Click to expand...
Click to collapse
Most probably not .. it seems they are not part of AOSP yet - they are included in stock firmware.
Tested the new "stuff" on my Pixel C running AOSP as well .. the "new" mutil windows view did not work as in stock firmware.
Maybe it's related to the new Pixel Launcher .. maybe they are "hidden" and not activated in AOSP.
Also the battery usage alerts were not working on Pixel C ASOP build.
Need to check this ..
Maybe I need to do a complete wipe and start from scratch to get all the new nice stuff working ? .. )
You may have test yourself on manta ...
Cheers
followmsi said:
Most probably not .. it seems they are not part of AOSP yet - they are included in stock firmware.
Tested the new "stuff" on my Pixel C running AOSP as well .. the "new" mutil windows view did not work as in stock firmware.
Maybe it's related to the new Pixel Launcher .. maybe they are "hidden" and not activated in AOSP.
Also the battery usage alerts were not working on Pixel C ASOP build.
Need to check this ..
Maybe I need to do a complete wipe and start from scratch to get all the new nice stuff working ? .. )
You may have test yourself on manta ...
Cheers
Click to expand...
Click to collapse
Pixel c has its own Aosp tree or branch or whatever it is called. We already have the different navkey layout which is not available on phone aosp.
stunned said:
Pixel c has its own Aosp tree or branch or whatever it is called. We already have the different navkey layout which is not available on phone aosp.
Click to expand...
Click to collapse
For the pixel c AOSP version I have used the pixel c branch.
Still not working ..
Just installing new pixel c launcher on the pixel c to see the difference .. if at all.
We will see if and how we can "enable" those features .. on manta hopefully too.
Sent from my AOSP on dragon using Tapatalk
Keep getting error Bluetooth share keeps stopping, flashed with gapps, and without, same error
dnp77 said:
Keep getting error Bluetooth share keeps stopping, flashed with gapps, and without, same error
Click to expand...
Click to collapse
Yep .. will have a look.
Plenty of Bluetooth changes in 7.1.2.
Thanks for the info.
SetupWizard
If you do a clean install and install opengapps there are issues with the gapps "SetupWizard" on 7.1.2 !
Have a look here ...
https://forum.xda-developers.com/showpost.php?p=71740178&postcount=267
You can also mount system (RW) and type:
Code:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
in TWRP terminal. This will allow you to bypass the SetupWizard altogether on a clean flash.
As it looks like the gapps team is working on an replacement SetupWizard for 7.1.2 ..
Cheers
New version ..
AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v2.zip
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (no need to wipe system if you upgrade from previous build)
3. Install AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v2.zip
4. Install open_gapps-arm-7.1-xxxx-2017xxxx.zip (optional)
5. Install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- The SetupWizard from gapps is still buggy on 7.1.2
- Camera is not working
Changes:
- Bluetooth is working now !
Enjoy
Audio jack not working
Nicholas1994 said:
Audio jack not working
Click to expand...
Click to collapse
Thanks for the info .. same/similar problem like in LOS 14.1
Have updated the know issues now ..
Known Issues:
- Camera is not working
- Audio jack is not working
- Bluetooth is not working - fixed in v2
Not sure when the Audio jack issue will be fixed ..
Cheers
followmsi said:
Thanks for the info .. same/similar problem like in LOS 14.1
Have updated the know issues now ..
Known Issues:
- Camera is not working
- Audio jack is not working
- Bluetooth is not working - fixed in v2
Not sure when the Audio jack issue will be fixed ..
Cheers
Click to expand...
Click to collapse
What kernel are you using? this is what you should be using. the issue has something to do with changes in merges beyond 3.4.67, try mine if you want a working kernel with headphone support
sooti said:
What kernel are you using? this is what you should be using. the issue has something to do with changes in merges beyond 3.4.67, try mine if you want a working kernel with headphone support
Click to expand...
Click to collapse
Cool .. This works well
Compiled a new kernel using your sources .. really nice.
Thanks a lot !
New manta kernel .. fixing Audio jack !
manta-kernel_kernel-flasher-5.1-20170409.zip
manta-kernel_kernel-flasher-5.1-20170409.zip.sha1
Installation:
1. Boot into latest TWRP
2. Install manta-kernel_kernel-flasher-5.1-20170409.zip
3. Reboot into system
No need for SuperSU ... or anything else.
The installer will take care.
Thanks to @sooti for the information.
Enjoy
Audio jack Works fine now , thanks for a super rom ?
AOSP - Music.apk
The current Music AOSP app is not working .. google did forget to implement a patch
https://groups.google.com/forum/#!topic/android-rpi/LNUCjXXvn2U
This problem occurs on all 7.1.2 AOSP ROMs.
Here is the patch:
https://android.googlesource.com/pl...+/6036ce6127022880a3d9c99bd15db4c968f3e6a3^!/
Have cherry-picked this patch now and compiled the Music.apk again.
You still need to manually grant access to "storage" for the app.
Made a quick installer to replace the broken apk ..
AOSP_7.1.2_r2_Music.apk_fixed-for-Android-N_manta.zip
Maybe I will remove the app next release completely.
Cheers
Grid view
Google has activated the "grid" view of your recent apps for a few devices in 7.1.2.
It's part of AOSP already.
If you would like to use this feature .. just activate it
Pls type inside terminal app as root ..
mount system RW:
Code:
mount -o rw,remount /system
activate grid:
Code:
echo "ro.recents.grid=true" >> /system/build.prop
Reboot into system ...
I am not sure if we should activate this view per default in the next release.
Some comments please
followmsi said:
Grid view
Click to expand...
Click to collapse
For tablet layout and a 10" screen size I prefer recents grid view, thanks for the hint. :good:
Now all the fresh changes are included ...
AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v3.zip
Changes:
- Added new kernel to fix Audio jack
- Enabled "Grid View" per default
- Fixed Music.apk
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (no need to wipe system if you upgrade from previous build)
3. Install AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v3.zip
4. Install open_gapps-arm-7.1-xxxx-2017xxxx.zip (optional)
5. Install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- The SetupWizard from gapps is still buggy on 7.1.2
- Camera is not working
Enjoy
To finalize the manta kernel testing I have made a last version ..
Activated 1 more governor .. and used a cherry-pick to speedup AC charging.
manta-kernel-aosp_kernel-flasher-5.1-20170413.zip
Changes:
- ONDEMAND CPU governor activated
- The kernel has included changes to speed up AC charging
Installation:
1. Boot into latest TWRP
2. Install manta-kernel-aosp_kernel-flasher-5.1-20170413.zip
3. Reboot into system
No need for SuperSU ... or anything else.
The installer will take care.
If you face any strange issues, pls let me know.
Enjoy
Related
CyanogenMod 11 with crDroid additions for Xiaomi MiPad
!! IMPORTANT !!
xep.8800.org will be temporarely down from 29.03.15 for couple of weeks so it would be great if somebody do mirror of latest buld and post link here. Thx!
About:
Source built CM except proprietary blobs and binary kernel from stock MIUI rom.
This is not a port from another binary rom.
Click to expand...
Click to collapse
What's working:
It seems everything working for now..
Click to expand...
Click to collapse
Not working/Bugs:
"Wi-Fi region code" setting is broken. Do not touch it or it will break your wi-fi.
you tell me.. testing in progess..
Click to expand...
Click to collapse
Instructions:
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
Multirom Instructions:
1. Install TWRP Multirom Recovery
2. Reboot into TWRP and install multirom-20150205-v30-UNOFFICIAL-mocha.zip
3. Click "Advanced->Multirom" and flash your desired second rom.
4. Return to the installed roms listing, click fresh installed rom and click "Remove boot.img" (Due to closed kernel sources kexec-hardboot is not implemented so we need to remove boot.img)
5. Reboot. Select your desired rom from multirom menu
Click to expand...
Click to collapse
Downloads:
cm-11-20150327-UNOFFICIAL-mocha.zip
CWM
Multirom:
TWRP_multirom-v2.8.4-mocha.zip
multirom-20150205-v30-UNOFFICIAL-mocha.zip
I don't know if it is actually compiled with TEGRA optimizations but have created CWM flashable zip with stock bionic libraries. You can flash it on top of CM installation:
tegra_bionic.zip
Changelog:
15.02.15
* apply qcom bionic optimization
* build.prop dalvik etc tweaks
02.02.15
* Reboot to recovery fixed
* Recents view proportion fixed
26.01.15
* Synced with CM repo
* have enabled Display mirroring (miracast) though it does not work with my EZ dongle, sound is ok but screen is black. May be it'll work with another dongles...
21.01.15
* Update to the latest kernel from stock MIUI
20.01.15
* Sleep issue fixed
* Adopt nvcplsvc for CM & implement Performance Profile selection
18.01.15
* Synced up with CM repo.
* Added USB Mass Storage mode for external sd. Though it does not work along with ADB Debug enabled, need to be switched off when using UMS mode.
17.01.15
* Switch to CM's audio_effects and make Dirac plugin work. Equalizer crash fixed.
Click to expand...
Click to collapse
Links:
http://github.com/cyanogenmod
http://github.com/cristianomatos
https://github.com/faust93
Click to expand...
Click to collapse
I take no responsibility for what this may or may not do to your device.
Do not forget to click Donate button! It makes me work harder!
Thanks Pumbaster for your work!
My device doesn't seem to go to sleep...
WakeLockDetector shows Android System --> ConnectivityService as the main issue. BetterBatteryStats shows the same...
I tried turning location services off, froze Mobile Data and Mobile Network Configuration in Titanium Backup but that doesn't help. No checking if the same wakelock appears with wifi off...
Anyone with any clue? Or the same problem?
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Krystanos said:
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Click to expand...
Click to collapse
I used pico gapps myself and the june version is way smaller then the december version, then again I actually did try the december version as well and it seemed to work fine. So not sure, apart from the size...
About TWRP vs CWM, not sure. Guess it also should work with TWRP but haven't tried... CWM is needed for True Dual Boot, but that seems bugged anyway.
By me too. Battery drain is to much, device don't go to sleep...
zolikaDB said:
By me too. Battery drain is to much, device don't go to sleep...
Click to expand...
Click to collapse
Yeah, seems to be a common issue.
My device only goes to sleep when wifi is turned completely off. When I have it set to turn off when display is off I still get the wakelocks. I also have set the scanning for open wifi to off, location services turned off, etc.
For now I flashed back to the 0114 version as that one is working fine here...
If I can share some logs or anything, I'd be more then happy to!
@dagrim1: I hope, Pumbaster make new, fixed build
I Encounter Graphical Glitches with 3rd Party Browsers (Opera and UC Browser)
Chrome works fine so far. Also heavy Battery drain an 17/1
@faust93: what is with battery drain?
Did a very dirty try or replacing frameworks.jar but that didn't work...
Saw some wifiStateTracker errors and that and ConnectivityService seemed to be part of the framework, that's why I gave it a shot. 0118 still has the deespleep/wakelock issue btw...
I don't really care about dual boot. MIUI has so much limits. Once I go to CM, I don't think I'll be able to come back to MIUI...
But I'll stick to CWM, just in case...
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
dagrim1 said:
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
Click to expand...
Click to collapse
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
zolikaDB said:
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
Click to expand...
Click to collapse
I don't believe it's integrated in 0118, think that fixes some sd stuff...
I am currently running the 0118 build (with the wpa_supplicant.bin file replaced manually) and seems to be working pretty fine. Had some video issues with a certain app (video jumping a bit, stuttering) but think I fixed that with 'disable hardware overlay' in developer options.
Without the replaced .bin I also had a problem with turning off and on wifi. It would work when booting, but if I turned it off I couldn't turn it on again... The replaced .bin also fixes that. Now checking if antutu finishes it's run...
@dagrim1: hope, Pumbaster fix this problem!
Just another small question: full wipe will delete the /data partition too right ? So the ROM zip file will be deleted too ? Or am I missing something ?
Thanks.
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
jastonas said:
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
Click to expand...
Click to collapse
Unfortunately I tried to install CWM with fastboot and it failed to install... No specific error message.
I have seen a port of TWRP for MiPad. Have you tried this one, or the standard one?
How I wish I could just flash CM on my MiPad...
Rom updated to LP 5.1.1 on June 17. All latest features included:
My Changes:
1. Thermanager values fixed to prevent flickering and low charging. There is ZERO flickering.
2. Camcoder mike low recording sound fixed
3. VOLTE enabled (if and when your carrier implements it). If you go to Network, you'll see Volte enabled; also in phone test menu, you will see VOLTE flag enabled
4. WIFI background scanning disabled - better battery life
5. GSM Network is handled by System, as opposed to Modem
6. Shady IPs cleaned thought the rom
7. Kernel with Overclock, Voltage, Screen Color and TWRP integrated.
9. All usual hardened features in kernel (see original description below)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=13068
Do a clean flash, since this is LP 5.1.1
_______________________________________________________________________________________________________
Rom updated March 20. Over 800 downloads in 8 days and 6 "thanks you". Thanks...
Some changes: sound control in kernel which allows to compensate for low camera mike recording (use Trickster mode or similar app); wifi background scanning is disabled - better battery life; latest validus and cm changes
DOWNLOAD LINK: http://forum.xda-developers.com/devdb/project/dl/?id=11628
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is the latest Validus LP compiled from sources on March 11. Latest CM changes including FM Radio
Changes:
1. Kernel with all ciphers, hashes, random number generation enabled
2. SeLinux disabled, Tomoyo security enabled
3. 256 bit encryption with increased key length and 5000 iteration, as opposed to weak 2000
4. Latest CM and Validus changes including black interface and changing keyboard theme based on app color
5. Black Contacts fixed (now white text on black background)
6. Led lights normal brightness fixed
7. TWRP 2.8.X integrated into kernel
DOWNLOAD LINK: http://forum.xda-developers.com/devdb/project/?id=8646#downloads
Install:
1. Be on Kitkat at least, rooted and with recovery
2. Enter recovery, wipe System/Cache/Data
3. Flash the rom
4. Flash data from your previously saved Lollipop rom (optional, but works on my device)
5. Reboot and enjoy
Credit: Validus Team, Slimroms, AOSP, Cyanogenmod, Omniroms
Warning: I am not responsible for death and destruction resulting from flashing this rom. You are on your own.
Kernel Source: https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Validus Lollipop Unofficial, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/Team-Validus/android
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP Cyanogenmod
Version Information
Status: Testing
Created 2015-03-12
Last Updated 2015-06-17
Screen Shots
Screen shots added.
For those who are interested in encrypting the data partition. Remember, there is no longer any visible slowdown. What you need to do before or after encryption is to enable "Disable HW overlay" in Developer Options. There is a catch, though: this won't stick after reboot unless you implement an init.d script that will take care of this.
Here is the script : http://d-h.st/QIiE
Download the script by using the blue button (unless you want their ridiculous exe. download manager)
Put the script into /system/etc/init.d with at least 750 permission and reboot. You will see that Disable HW overlay option is ticked by default.
Also, I recommend ADB shell encrypting, as opposed to doing it from Security menu for several reasons: first with ADB you are not limited by 16 characters, you can use a passphrase that you can remember and no one can break; second, in Security menu, encryption will use your pin password (which is short) to encrypt. Remember, you only need a long passphrase to boot, and if your rom has "soft reboot", you don't need to enter password at all. Here is how to do it:
1. Go to Security menu and enable Pin/Password/Pattern or None. Your screen password could be short, as it is independent from boot password.
2. Next, pick a long boot password. You need to convert it into hex: just use this site https://www.online-toolz.com/tools/text-hex-convertor.php for conversion. Now, copy your hexed password (for future pasting).
3. Next, go to Developer Options and enable ADB; Root for ADB + APPS
4. Connect your phone to your computer
5. Open Terminal and type "adb shell" without quotes and press enter
6 Then type "su" also no quotes and press enter
7. Now type the following without quotes: vdc cryptfs enablecrypto inplace password HERE PASTE YOUR ACTUAL HEXED PASSWORD and press enter. Remember, don't type HERE PASTE YOUR PASSWORD, instead paste your hexed password there.
8. After you press enter, your phone will reboot and start encrypting. In a few minutes, you will get another reboot and a prompt for boot password. Here, enter your actual password (not the hexed one). Your phone will boot and you can check in the Security options that your phone is encrypted.
Enjoy.
Can u tell what the bugs?
Sent from my C6903 using XDA Premium 4 mobile app
meliacentrum said:
Can u tell what the bugs?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CM bugs....
Do Google Services work on this build?
Gonna try it but I assume they might crash as with the other hardened builds
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
Has this got the landscape rotation sys ui crash bug
shingers5 said:
Gonna try it but I assume they might crash as with the other hardened builds
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
Has this got the landscape rotation sys ui crash bug
Click to expand...
Click to collapse
Encryption has nothing to do with gapps crashing. The only thing that could be related is android_logger=n in kernel. I guess gsf can't log your every key stroke without that function in kernel. So, any other lp kernel would do. I may recompile the kernel with that option on.
Good compilation
My previos ROM was RR. Trying this. Data was restored from RR is normal.
I like this Validus ROM
All what I want is included + Black Theme (Default)
Xprivacy works? Can't nmake it work on cm12( asks kernel modification)
Sent from my TegraNote-P1640
Instruction for Encrypting Data Partition
See post #3 on how to encrypt your data partition without any visible slowdown.
http://forum.xda-developers.com/showpost.php?p=59392722&postcount=3
ggs2 said:
Xprivacy works? Can't nmake it work on cm12( asks kernel modification)
Sent from my TegraNote-P1640
Click to expand...
Click to collapse
The only two roms that work with Xposed Xprivacy from start are my versions of Resurection Remixed and Slim LP (remember, I have SElinux disabled in my kernels). So, if you want those, flash Resurection, then install your favorite apps including Xposed and Xprivacy, then backup the data. Then do a clean flash of Validus, then flash Xposed binary (before rebooting), then restore Data from Resurection and reboot. It works. If you look at screenshots I posted, you will see I have Xprivacy working.
I actually like thia ROm and the default theme too. Been using since flashing and gapps work. Had a few issues but flashed banks gapps and they worked fine
Does this have low LED bug? Can't see LED... tried xposed that works though:
optimumpro said:
The only two roms that work with Xposed Xprivacy from start are my versions of Resurection Remixed and Slim LP (remember, I have SElinux disabled in my kernels). So, if you want those, flash Resurection, then install your favorite apps including Xposed and Xprivacy, then backup the data. Then do a clean flash of Validus, then flash Xposed binary (before rebooting), then restore Data from Resurection and reboot. It works. If you look at screenshots I posted, you will see I have Xprivacy working.
Click to expand...
Click to collapse
ggs2 said:
Does this have low LED bug? Can't see LED... tried xposed that works though:
Click to expand...
Click to collapse
Led is fixed, unless you use a different kernel.
optimumpro said:
Encryption has nothing to do with gapps crashing. The only thing that could be related is android_logger=n in kernel. I guess gsf can't log your every key stroke without that function in kernel. So, any other lp kernel would do. I may recompile the kernel with that option on.
Click to expand...
Click to collapse
Do I understand correctly that gapps will not work here? Could the missing module be shipped and downloaded as 'ko' file or does it have to be compiled in?
steveeJ said:
Do I understand correctly that gapps will not work here? Could the missing module be shipped and downloaded as 'ko' file or does it have to be compiled in?
Click to expand...
Click to collapse
I don't use Gapps, but another user a few posts above said they worked...
optimumpro said:
Led is fixed, unless you use a different kernel.
Click to expand...
Click to collapse
Doesn't work. if i restore data from RR in validus, i end up in bootloop even though I have only installed Xposed/Xprivacy in RR..
Can't use RR because LED is tooo low.
Would keep an eye, till the time validus by itself can support Xprivacy (if it does !)
Thanks...
ggs2 said:
Doesn't work. if i restore data from RR in validus, i end up in bootloop even though I have only installed Xposed/Xprivacy in RR..
Can't use RR because LED is tooo low.
Would keep an eye, till the time validus by itself can support Xprivacy (if it does !)
Thanks...
Click to expand...
Click to collapse
Did you follow directions in my other post? Did you install xposed and xprivacy in Resurection? I have validus with data restored from Resurection and xposed and xprivacy work fine.
optimumpro said:
I don't use Gapps, but another user a few posts above said they worked...
Click to expand...
Click to collapse
gapps seem to work so far!
I'm currently trying to mount the sdcard which is ext4 formatted. I can mount it manually via the shell, but vold won't notice any of that. I guess I need to figure out how to persistently change /fstab.qcom file.
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !
https://twrp.me/google/googlepixelc.html
I would like to continue this thread for publishing test builds and other troubleshooting.
Once the changes are stable and tested I will merge them into TeamWin github for the next official build.
Known issues:
- FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.
fwtool
The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
Installation:
Please install the new version from your current TWRP.
Pls make a "reboot to recovery" once you have installed the new version.
Of course you can install it via fastboot too.
Sources:
https://github.com/TeamWin/android_device_google_dragon
https://github.com/omnirom/android_bootable_recovery
DOWNLOAD:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
Have fun!
XDA:DevDB Information
[TWRP][dragon], Tool/Utility for the Google Pixel C
Contributors
followmsi
Version Information
Status: Stable
Current Stable Version: 3.3.1-2
Stable Release Date: 2017-04-01
Created 2016-06-17
Last Updated 2023-01-11
Changes:
Official 3.7.0_9-1 (2023-03-25)
- Exclude MTP
- Restore stock values for init.recovery.dragon.rc
- Enable Screen Timeout
https://dl.twrp.me/dragon/twrp-3.7.0_9-1-dragon.img.html
Official 3.7.0 (2022-10-10)
- New official version -> https://twrp.me/site/update/2022/10/10/3.7.0-released.html
Official 3.6.2 (2022-06-01)
- New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
Official 3.6.1 (2022-03-10)
- New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
Official 3.6.0 (2021-11-28)
- New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
Official 3.5.2 (2021-04-07)
- New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html
Official 3.5.1 (2021-03-17)
- New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Official 3.5.0 (2020-12-31)
- New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html
Official 3.4.0-0 (2020-06-22)
- New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Official 3.3.1-2 (2020-03-01)
- Script updates to improve encryption -> Thanks to updateing from Team Mokee !
Official 3.3.1-1 (2020-01-27)
- Script updates for Android 10
- Added more languages
- Fixed build issues
- New Kernel
Official 3.3.1-0 (2019-05-19)
- New official version
Official 3.3.0-0 (2019-04-10)
- New official version
Official 3.2.3-0 (2018-07-29)
- New official version
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Official 3.2.2-0 (2018-06-30)
- New official version
* DRM changes
Official 3.2.1-0 (2017-12-18)
- New official version
Official 3.2.0-0 (2017-11-29)
- New official version
Official 3.1.1-1 (2017-09-15)
- Including all changes for Oreo and for better en/decryption from unofficial V1 and V2
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
- New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
- Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)
Official 3.1.1-0 (2017-05-17)
- Upgrade to 3.1.1-0
Unofficial 3.1.1-0 (2017-05-14)
- Latest TWRP changes (3.1.1)
- Latest kernel sources (2017-05-12)
- Latest LineageOS changes (Android 7.1.2)
Official 3.1.0-0 (2017-04-01)
- Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.
3.1.0-2
- Custom installer script problems should be fixed now.
3.1.0-1
- Removed all the FBE changes - will take longer to get it running on dragon
- Added NTFS-3G support for NTFS R/W -> USB-OTG
- Used new kernel binary with changed F2FS config
3.1.0-0
- @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
- Added some more config changes for FBE.
3.0.3-4
- Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.
3.0.3-3
- Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
- fstab modification (usb-otg -> auto)
3.0.3-2
- F2FS enabled
- tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)
3.0.3-1
- Based on Android 7.1.1 AOSP -> android-7.1.1_r14
- Based on TWRP branch for Android 7.1
- tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)
v23
- Based on Android 7 AOSP -> android-7.0.0_r3
- Based on TWRP branch for Android 7
- tegra-3.18 kernel -> v160907
v22
- Based on Android 7 AOSP -> android-7.0.0_r1
- Based on TWRP branch for Android 7
- chromeos-3.18 kernel -> v160823
- Maybe not fully working as v21 due to new sources.
v21
- Added BRIGHTNESS PATH ... Thx to @ggow
v20
- Added Battery PATH ... Thx to @ggow
v19
- "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now
- New versioning
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
v17
- "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
- chromeos-3.18 kernel -> v160618
v16
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
DarthDestroyeis said:
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the feedback ..
Did you install something before .. maybe still mounted from before ?
Or you just made the backup only ?
Which partitions did you backup ? .. system as well .. or just data ?
Pls post recovery.log on pastebin.com .. helps a lot !
Thanks
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
DarthDestroyeis said:
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It´s always system which is complaining .. no other partitions, correct ?
Thanks ... will have a look.
Yup... just the system partition.
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
ilpolpi65 said:
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
Click to expand...
Click to collapse
You did flash system-vendor update.zip via fastboot ?
No good idea.
The kernel and the TWRP are fine to flash via fastboot, but not the system.img and vendor.img.
Like written on first page of the updatr.zip thread.
Pls install the package via TWRP.
Or use unmodified stock image from Google for fastboot.
For recovery bootloop I know only "fastboot reboot".
I had the bootloop once myself, as I still was on M, but the command did help me.
YevOmega said:
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
Click to expand...
Click to collapse
I am not the OTA User
As I know, the tool "flashfire" from Chainfire should handle the whole OTA process smoothly.
The Update.zip packages I do anyway, because I am used to it .. over the years.
Did this for Nexus Flo ... Nexus 10 as well.
For Pixel C I just publish them, because nobody as else is doing it.
Look in Flo and manta xda .. They have these packages too, done by others.
Because of all the problems with OTA .. in the past ..and still today.
Today we have systemless root and regular OTA...times are changing.
Maybe it's time for something like flashfire in the next time ..
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
ilpolpi65 said:
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
Click to expand...
Click to collapse
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
followmsi said:
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
Click to expand...
Click to collapse
True... It's really strange..but..pixel c too is a strange device...
anyway thanks for your help !
DarthDestroyeis said:
Yup... just the system partition.
Click to expand...
Click to collapse
v17
- "Failed to unmount `/system `(Device or resource busy)" - fixed now
- chromeos-3.18 kernel -> v160618
Please have a try with v17.
My problems are gone .. no more warning messages while doing backup or restore.
"Failed to unmount `/system `(Device or resource busy)"
Pls test as well !
Thanks
sorry for all this quick releases today .. this is the last one for now !
but when something new is working .. I would like to share it with you ...
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
Enjoy !
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
redukt said:
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
Click to expand...
Click to collapse
Today I have made 3 backups and restores
No problems or messages so far ..
But pls test on your device as well .... On Pixel C you never know
Cheers
Ok, will test it now without wipes
redukt said:
Ok, will test it now without wipes
Click to expand...
Click to collapse
Hopefully
Here is one more ROM for Mi PAD. This one I consider as stable daily driver.
What working:
audio
sensors (autorotation)
wifi
3D graphics
hardware accelerated video playback
camera
SD card and USB mounting
gapps
Known problems:
not enough space to install gapps in /system
microphone doesnt work
you have to merge 2 system partitions in one to install 2017-02-25 and newer builds
2017-02-21
Initial release
download: lineage-13.0-20170221-UNOFFICIAL-mocha.zip
2017-02-25
changelog:
whole new audio based on opensource tinyhal (microphone should work both builtin and headset). Please report any regression.
new libwvm means widevine drm should work now
big system partition (1.2Gb). You have to install it on merged system1 and system2, if you have already merged just install.
SD card mount fix included (previosly avaliable as boot.img)
Wifi uses unique device MAC addres from /BKB partition
cleaned some useless blobs like powerservice daemon
download:lineage-13.0-20170225-UNOFFICIAL-mocha.zip
2017-03-07
changelog::
Added settings for enable Navigation bar ( check in Settings -> Buttons). Hardware keys disables when nav bar switched on.
Vibration intensity setting (check in Settings -> Sound)
Settings for notification and battery LED (color, intensity)
Settings for buttons backlight intensity
Added ffmpeg codecs for format unsupported by hardware or google, like flac
Download: lineage-13.0-20170307-UNOFFICIAL-mocha.zip
2017-04-18
battery animation on offline charging
userspace cpquiet governor by default (resolves all lags in video)
updated hwui props in build.prop (improve screen stability, less black pixels in chrome)
bigger shader cache (seems to little improved graphic perfomance)
updated wifi driver and firmware
hope finally resolved wifi disconnection issue by disabling IpReachability monitor
Download: lineage-13.0-20170418-UNOFFICIAL-mocha.zip
Fix for 2017-04-18 build
fixed boot.imgboot-20170420.img
MAC address loading fixed
Resolved issue with wifi Switch On
Added hardboot exec patch for work as main rom for MultiROM
gihub source code links:
Device tree (cm-13.0 branch)
Kernel (cm-13.0 branch)
Vendor blobs (cm-13.0 branch)
Thanks for author of this repository for building custom webview.apk manumanfred/android_external_chromium-webview
Merge partitions
Mi Pad by default has 2 /syetm partition, each 640Mb. It is not enogh to install LineageOS and Gapps. To install 2017-02-25 build and newer you have to merge 2 system partition in one 1.2Gb system partition. To dod this follow instruction http://en.miui.com/thread-118294-1-1.html
Root Access
If you want root acces flash SuperSU zip https://forum.xda-developers.com/apps/supersu
XDA:DevDB Information
LineageOS 13.0 for Xiaomi MiPad (mocha), ROM for the Xiaomi Mi Pad
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_device_xiaomi_mocha
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod, LineageOS
Version Information
Status: Beta
Created 2017-02-21
Last Updated 2017-04-20
Reserved
so no way to flash gapps via twrp ? how to do this merge thing ? pls make a tutorial...
love this rom, better than cm12.1.
smooth as butter! highly recommended!
thank you highwaystar
OoSTARTERoO said:
love this rom, better than cm12.1.
smooth as butter! highly recommended!
thank you highwaystar
Click to expand...
Click to collapse
Any bugs u encountered so far. Video playback/some lags/restarts?
I have no words to describe except what @OoSTARTERoO said.
I am starting to really love my mipad.
Kudos to @highwaystar_ru
Camera is working fine.
I will check with Antutu after some time.
Anyway, I cannot seem to use sd card as internal storage .. is this a bug ?
@highwaystar_ru omg i cant believe this ur literally One Man Army
Thanks a lot Highwaystar.. Real thanks for keeping the MiPad alive.
darryl1234 said:
@highwaystar_ru omg i cant believe this ur literally One Man Army
Click to expand...
Click to collapse
HighwayStar is one-man army:good:
hell1134 said:
I have no words to describe except what @OoSTARTERoO said.
I am starting to really love my mipad.
Kudos to @highwaystar_ru
Camera is working fine.
I will check with Antutu after some time.
Anyway, I cannot seem to use sd card as internal storage .. is this a bug ?
Click to expand...
Click to collapse
This from myfriend
AnKiT ([email protected]):For all who were searching for Extsdcard... its in /mnt/media_rw/9016-4EF8Go to the directory and from options add shortcut to Desktop.. and access External Sdcard from desktop... ?
Click to expand...
Click to collapse
thanks @highwaystar_ru!!! You are the best one!!
VALRCIEL said:
This from myfriend
Click to expand...
Click to collapse
I think I mis-explained. I can access SD card from file manager, but, I cannot set it as Internal Storage - adoptable storage feature of MM roms.
---------- Post added at 08:51 PM ---------- Previous post was at 08:33 PM ----------
OK ... found a solution to gapps installation.
1) Install the rom
2) Boot
3) Reboot to recovery
4) Backup the ROM in SD Card (internal will be erased)
5) Wipe - advanced - select all except SD card & OTG
6) Reboot to recovery
7) Restore the backup from SD card
8) Reboot to recovery (again)
9) Install gapps (I use pico)
10) Reboot.
I used this ROM and almost everything is OK except HW decoding in MX Player / VLC.
There're some lags when I watch movie with MX / VLC.
Otherwise, very good ROM, thx.
Here's an easier and quicker way to install gapps:
-> Repartition /system
-> Install the ROM
-> From the TWRP main menu, select Wipe -> Select Advanced -> Select the system partition and click on Repair or change file system
-> Click on resize
-> After the process is done, flash gapps.
This would mean no waiting for twrp to backup and restore the entire partition. Fair warning though, I have tested this on one of my other devices, not the Mi Pad. Though I am pretty sure it'll work, it'll help if someone tried it and reported so that it can be added to the OP.
As is said before. saver and god of mipad(MOCHA) @highwaystar_ru.
Is this really good for daily use?
@highwaystar_ru can't we install gapps pico version without merging the memory.
Navin9 said:
@highwaystar_ru can't we install gapps pico version without merging the memory.
Click to expand...
Click to collapse
Nope. Partition is too small and free space after installing ROM is about 73mb. Pico gapps requires about 140 mb.
(Guide) How to merge system1 & system2. And how to flash CM13.
1. Download the bin file from : here
2. Place it in /sbin folder in root using any root file explorer, set permissions 755 (check image in attachments)
3. Download Repartition zip from : here
4. Reboot into recovery.
5. Flash Repartition zip (downloaded in step 3). After flashing this recovery will reboot automatically.
6. Now Wipe everything except internal and external storage. (Create backup of your current ROM just in case, if you want.)
7. Flash latest Lineage OS 13 zip.
8. Go to Wipe > Advance > Select 'System' > Repair and Resize Filesystem > Resize file system.
9. Go back and flash gapps zip + superuser zip.
10. Reboot now
Guys you won't believe it this ROM is amazing. This is smoothest ROM on mi pad . I'm sharing some screen shots . Thisron worth a shot folks.
Welcome to MIUI sGSI For Galaxy J7 2017
TESTED ON J730X
Some information you should know..
This is a fully working MIUI sGSI with Android version 9.0
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
I don't own any files here, except patch files.
So, we are here with sGSI. It's normally called "unstable" and "not for daily usage" so users are recommended to go for GSI. But GSI lacks features and has AOSP-like design that some users may be bored of that. And now we finally break that law. sGSI can now be used as daily drivers.
As the nature of these sGSI go, it was a non stop battle for almost 3 weeks straight to get it to this point where all features are working as expected. if you appreacite this work Hit the Thanks button
RULES OF POSTING : READ everything before commenting, And especially the instlal steps, the rom has been tested throughly for a long time, so if you have an critical issue like not booting or no sim, you missed the instructions, posts that are irrelevant to this project will be ignored(Constructive criticism is welcomed). If you do face a new bug however, dont just say "hey bug here" provide more information, and a LOGCAT, bug reports without logcats will most likely be ignored.
FEATURES:
Based on MiuiMiX 11 by MMX Team 9.12.26 using ErfanTools
Android 9.0
MIUII 11 Features
Semi-SIM support (Currently one SIM only)
Heavily debloated
Zipaligned
Very Optimised
Battery and performance focused
Full MIUI without missing vital apps
Rootable with Magisk
RMM/KnoxGuard/Defex Free
And many more
Kernel:
You can choose either latest CronosKernel by @ananjaser1211, or KRAKEN kernel by @SPARTANICUS
Install steps:
ensure you have LATEST TWRP from Here
Download all the files in the DOWNLOAD section
Wipe everything (SYSTEM,DATA,CACHE,DALVIK and preferably Internal storage all together)
Flash Project Spaget 3.0 (not X!) here and follow the steps there.
Flash MIUI-Aonly-9-20191230-ErfanGSI.img to SYSTEM
Flash your desired kernel, either Cronos or KRAKEN (must be using Treble version)
[IMPORTANT] Flash Magisk in order to have patch working
Flash sGSI-Patch.zip
Flash NFC Patch
After the boot animation is on for 30~60 Seconds. Hold VolumeDown+power until the device reboots
Install Google Play Services apk in Downloads section in order to get setup working
Setup your rom and READ the F.A.Q for more information.
BUGS:
Signal bar doesn't work (always empty) but it's acturally working
FM Radio (No FM Radio app in image)
Only one SIM is working at the moment
VoLTE not working (need another fixes)
SCREENSHOTS:
Imgur
CREDITS:
IF you helped in this GSI and i forgot you, tell me in a PM or in a reply
@ananjaser1211 for his Project Spaget, CronosKernel and HUGE contribution for Exy7870
@SPARTANICUS for KRAKEN Kernel
@SrCDA for his NFC patch
@erfanoabdi for his tools to port GSIs
And the rest of EliteTeam
DOWNLOADS ARE IN POST 2
DOWNLOADS:
Official Treble support Group : Telegram
----------------------------------------------------------------
All files are uploaded here: Google Drive
GSI: Here (My Google Drive acted up and does not let me upload any more files)
FAQ:
Good idea to read this F.A.Q While the rom is installing
Notes:
Q : Brightness bar not working / Camera doesn't work
A : You have flashed Spaget X instead of Spaget 3.0. Reinstall again
Q : Phone doesn't detect any SIM cards
A : Flash latest Cronos/KRAKEN kernel
Q : Everything on my screen is so small [J730 only]
A : Go to Settings > Developer settings > Set screen density to 411
Q : I got front camera stretch
A : Change resolution from 16:9 to 4:3
Q : Can I use front flashlight?
A : No, Samsung has their own libs, for now no apps can use front flashlight. Back flashlight still works
Q : How is battery Life ?
A : With some tests and some cycles, it will be better than stock due to optimzations
Q : the phone wont install any apps
A : Reboot
One more
does the rom have some type of error for daily use
VoLTE : Not work, need flash Magisk Module and using Phone App to VoLTE work
All work normal, just a Android Pie but like Android Q MIUI :good:
Great work
The first boot is so longer? I've waiting more than 10 minutes and don't boot. Or is bootloop?
And i've not found the MIUI-Patch.zip, only sGSI-Patch.zip
What android version is this? Can i flash the official magisk? There's no camera stretch bug? Like other gsi rom?
gabriel.oliveira.brito said:
The first boot is so longer? I've waiting more than 10 minutes and don't boot. Or is bootloop?
Click to expand...
Click to collapse
After the boot animation is on for 30~60 Seconds. Hold VolumeDown+power until the device reboots
gabriel.oliveira.brito said:
And i've not found the MIUI-Patch.zip, only sGSI-Patch.zip
Click to expand...
Click to collapse
Thanks for noticing, I forgot to rename the file.
NindoS said:
VoLTE : Not work, need flash Magisk Module and using Phone App to VoLTE work
Click to expand...
Click to collapse
I don't use VoLTE, so I couldn't test if it works. Can you tell me which Magisk module you used?
NindoS said:
All work normal, just a Android Pie but like Android Q MIUI :good:
Great work
Click to expand...
Click to collapse
Nice
Updated FAQ and sGSI patch. I forgot to add an important fix in patch, so anyone using this MIUI, reflash the new patch right now :good:
I tried again, followed all the steps as requested. On the first boot, I restarted the phone after approximately 30 seconds. But I still bootloop. I'm using Project Spaget 3.0, but I can't find a topic in the forum. Could you send me your Project Spaget zip file?
My logcat is on attachments
nfc not working. I installed the fix on the twrp and it failed, I had to install the fix when I started the cell phone so that it did not give me an error and it appears as a module installed in magisk but it does not work
Working fine but having bug
I have a bug with the WhatsApp application when viewing the stories that contain videos are not played and the app freezes.
I attach my log Cat about the error
I have problems with external storage, the system does recognize it but with third-party apps such as file explorer or streaming apps like spotify they don't detect external storage, I've tried to modify the vold.fstab and nothing. some fix they have
dani_hedz said:
I have problems with external storage, the system does recognize it but with third-party apps such as file explorer or streaming apps like spotify they don't detect external storage, I've tried to modify the vold.fstab and nothing. some fix they have
Click to expand...
Click to collapse
It's sGSI related problem, don't know why it happens
argenmu09 said:
nfc not working. I installed the fix on the twrp and it failed, I had to install the fix when I started the cell phone so that it did not give me an error and it appears as a module installed in magisk but it does not work
Click to expand...
Click to collapse
It works for me
Wi-Fi not working