Related
Hi! This is an index and guide about the Samsung Galaxy S4 mini plus i9195i
Rooting guide:
I downloaded Kingroot and rooted it there (even though it said not supported, it still worked). I then downloaded Super me and let it do it's magic (delete Kingroot apps and install SuperSU apps). It takes about 10 minutes. After 10 minutes, you can get your refund from the Play Store.
Xposed guide:
I downloaded the Xposed installer, went to install/update, and it all went smoothly for me. Other users reported boot loop, but my phone was fine, so don't blame me if you get boot loop.
Custom Roms:
KitKat ROMS:
CyanogenMod 11
Lollipop ROMS:
CyanogenMod 12.1
Marshmallow ROMS:
CyanogenMod 13
Nougat ROMS:
LineageOS 14.1
Oreo ROMS:
LineageOS 15.1
dotOS 2.4
Resurrection Remix 6.0.0
Pie ROMS:
LineageOS 16
Pixel Experience
Credits to @Danil_e71 for the development on our device
As far as my testing went, all these ROM's are pretty stable and that includes LOS 16. This device is not my primary device though, so I don't test as well as I used to. LOS 16 doesn't seem to have any major bugs. (I didn't even find minor bugs either, but again, I don't test properly.). You need the latest TWRP to flash it though.
Custom Kernels:
Custom kernel by alexax66 for stock ROM 4.4
.zip file (v 0.1.7)(Flash via recovery)
.tar file(v 0.1.7)(Flash via odin)
(v 0.1.7) Disc image file
Source
It works well, normal features work and it seems to make the phone work faster. I found that all kernel features do work, while there are a few bugs (I've come across 2: the alarm clock doesn't work and I can't search for mobile networks/ put new apns in). To make sweep2sleep work, you must insert
Code:
su
echo 1 > /sys/sweep2sleep/sweep2sleep
into the terminal after adding code to the build prop (this worked for me, but after a reboot it stopped). I installed first via TWRP official and then via Odin. I'm not sure if you have to do it that way, but I can assure you that if you do do it that way, it will work.
I would not recommend this kernel, due to its instability, although I did used to use it daily.
Custom kernel for stock ROM 4.4 by Danil_e71
https://forum.xda-developers.com/attachment.php?attachmentid=3778847&d=1465586157
I could not get WiFi working on this kernel.
Custom kernel for CM 11 by Danil_e71
https://forum.xda-developers.com/attachment.php?attachmentid=3778501&d=1465562842
Overclocks to 1.4 Ghz, and works well.
Custom Recoveries:
I am only listing the most recent versions:
CWM
flash via recovery (v 6.0.5.1) by @alexax66
flash via odin (v 6.0.5.1) by @alexax66
Disc image file (v 6.0.5.1) by @alexax66
Philz
flash via odin (v 6.59.0) by @alexax66
flash via recovery (v 6.59.0) by @alexax66
Source
TWRP
flash via recovery (v 3.1.0-0) by @Danil_e71
Stock ROM:
Here
Stock Kernel:
Latest stock kernel (Disc image file)
Stock Recovery:
Stock recovery (Disc image file)
Anyone else tryed this metod and can confirm that them devices is rooted ?
Zakariasz said:
Anyone else tryed this metod and can confirm that them devices is rooted ?
Click to expand...
Click to collapse
yeah I just rooted my device by installing the linked KingRoot apk. It failed the first try but I tried a second time and now it works
I don't have custom recovery, nor kernel nor Xposed framework yet though.
Stagefright-Official Rom
Hello,
just to say that I upgrade (odin flash) to last Official rom yesterday, find on sammobile:
Model GT-I9195I
Model name GALAXY S4 mini LTE
Country Netherlands
Version Android 4.4.4
Changelist 5332500
Build date Mon, 11 Jan 2016 11:42:16 +0000
Product code PHN
PDA I9195IXXU1APA1
CSC I9195IPHN1APA1
good news : all Stagefright detector are green !
exzemat said:
good news : all Stagefright detector are green !
Click to expand...
Click to collapse
What is Stagefright?
LoScienzo said:
What is Stagefright?
Click to expand...
Click to collapse
wikipêdia:
Stagefright is the collective name for a group of software bugs (or more specifically backdoors), that affect versions 2.2 ("Froyo") and newer of the Android operating system, allowing an attacker to perform arbitrary operations on the victim device through remote code execution and privilege escalation.[1] Security researchers demonstrate the bugs with a proof of concept that sends specially crafted MMS messages to the victim device and in most cases requires no end-user actions upon message reception to succeed, while using the phone number as the only target information.[2][3][4][5]
Sorry, but I have a stupid question:
Can I use the Netherlands-version also on devices that are used in other countries / with other carriers?
Bibabuzzel said:
Sorry, but I have a stupid question:
Can I use the Netherlands-version also on devices that are used in other countries / with other carriers?
Click to expand...
Click to collapse
Yes, you can, but I think if you wait, your country might come. They just (50 minutes ago) released one for region TPD here. I think I'm going to wait.
I use method described in the first post but with Super Sume v 9.1.9 and xposed installer from the first post and everything work like charm for the moment.
I've done it via same route, it was bit of a hassle for trying to find information about this exact phone. Nice compilation here. Thumbs up.
exzemat said:
Hello,
just to say that I upgrade (odin flash) to last Official rom yesterday, find on sammobile:
Model GT-I9195I
Model name GALAXY S4 mini LTE
Country Netherlands
Version Android 4.4.4
Changelist 5332500
Build date Mon, 11 Jan 2016 11:42:16 +0000
Product code PHN
PDA I9195IXXU1APA1
CSC I9195IPHN1APA1
good news : all Stagefright detector are green !
Click to expand...
Click to collapse
Are there any noticable differences in this update?
no other than more recent kernel build (11/01/2016) : more secure ...
I added a bunch of disc images of kernels and recoveries (no new releases ) I also added the newest stock kernel if anyone needs it. (Released 11 Jan 2016) Also, TWRP 3.0.0-0 is out for our device, links are there. Is anyone working on CM by the way?
Anyone flashed any of the stock firmware in the original post?
Mine came with the stock firmware from another country, and I would like to flash the one for my country to see if the cell phone signal is any better.
Should I bother?
BTW, will doing that trip the knox meter?
I tried to change Kingroot with SuperSUMe but can't do this, course can't brake Knox. I try to install SuperSU it also can't brake Knox. Wtf?
I need custom kernel without bugs for our i9195i.
I also can mention that the Rom for each country has special BB (baseband - drivers for radio module). But there is no any Rom for my country... So i have unstable signal...
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
How to disable Knox?
There's a new official TWRP release (3.0.0-2) here , enjoy
Sent from my GT-I9195I
Update: Got a custom ROM fully working (with small bus where and there). Check the first post
DroidKing18 said:
Update: Got a custom ROM fully working (with small bus where and there). Check the first post
Click to expand...
Click to collapse
You've got a interesting thread here to stay up-to-date on info about our phone, but shouldn't you mention some credits to the guy(s) that found the cm11?
I think it's Chrisled2 talking about it on cyanogenmod-forum (i see he's active here also by the name of chrisled):
https://forum.cyanogenmod.org/topic/110203-gt-i9195i-supported/?page=2#comment-591554
There are mentions about problems with play store, and playing video files in browser.
But thanks again for keeping us up-to-date!
Could you maybe try and test the infrared-functions with the custom rom? I use it for my television and decoder.
bartiest said:
You've got a interesting thread here to stay up-to-date on info about our phone, but shouldn't you mention some credits to the guy(s) that found the cm11?
I think it's Chrisled2 talking about it on cyanogenmod-forum (i see he's active here also by the name of chrisled):
https://forum.cyanogenmod.org/topic/110203-gt-i9195i-supported/?page=2#comment-591554
There are mentions about problems with play store, and playing video files in browser.
But thanks again for keeping us up-to-date!
Could you maybe try and test the infrared-functions with the custom rom? I use it for my television and decoder.
Click to expand...
Click to collapse
I thought OyyO found it first but I wasn't sure. I would've given creds to the devs but they don't seem to be on this site, if they are, tell me, but I've only seen them on 4pda, a Russian site. The truth is that I didn't test it enough to notice all the bugs. I lost a lot of interest when I found that I couldn't put Xposed on
Sent from my GT-I9195I using XDA-Developers mobile app
Btw, there is a also TWRP 3.0.2 now so your links to the official builds are outdated - you may want to link directly to https://dl.twrp.me/serranoveltexx/
According to ciwrl from the LineageOS Team, "Look for [official Lineage OS] builds to start rolling out this weekend" January 21st & 22nd, 2017
If you are not familiar with the builds download page, when an official LineageOS build is available it will be listed on that page. To find the build for your device, into the left side "Devices" column, click on the appropriate horizontal tab for your device brand name. Then click on the appropriate horizontal sub-tab model name. If your device is not yet listed it means that build is not yet released, please re-visit again later.
There are no estimated time of arrival (ETA) for all builds. If you want builds to be release faster you are welcome to love back your LineageOS community by contributing a code review. Either yourself as volunteer or by paying someone to contribute on your behalf.
Two types of builds:
1. Nightly: For clean fresh install. LineageOS Team recommends that users wipe when switching to LineageOS, and reinstall their gapps.
2. Experimental: For data migration/upgrade from CyanogenMod (CM) 13.0 or 14.1 to LineageOS 14.1. That data migration may or may not work. If it does not work you can always try the Nightly build. Experimental build may wipe permissions. In that case you will have to re-allow app permissions, but should retain all user data. Experimental build is watermarked with an ugly banner to ensure that you do not permanently run that Experimental build, and upgrade to a Nightly build after. Experimental build will be available for two months after January 20th, 2017. Read more.
Bugs and feature requests
Report bugs and make feature requests in that tracker. The LineageOS team are not accepting bug or regression reports until builds are available here. If you have any questions please check the instructions in that wiki or ask in #lineageOS on freenode.
Links
• Present Builds/Downloads available
• Verifying builds authenticity
• Update & build prep
• Bug and feature request tracker
• Wiki
• Status page
• Statistics
Enjoy
Why not a link to their official blog?
And when?
We all are waiting for official lineage-14.1 builds.
Good idea
RockyTV said:
Why not a link to their official blog?
Click to expand...
Click to collapse
RockyTV Good idea. Done I just added all the official links related to the coming soon official builds at https://forum.xda-developers.com/li...january-21-t3542405/post70658000#post70658000
waiting it like a child wait xmas
I think tomorrow will be available.
EvilHowl said:
I think tomorrow will be available.
Click to expand...
Click to collapse
I hope it does.. Well all the best!!
Seems like Lineage 14.1 builds have started.
https://review.lineageos.org/#/c/155809/
First build for Nexus 5x is up!
Enviado desde mi Nexus 6P mediante Tapatalk
Nexus nightly ready ... I wait for lg d802 ?
zifnab himself said it may take an hour for builds to be available in the download portal because of the hourly update interval on the mirrors; so it could take up to an hour for device builds to show up in the portal.
There's a ROM for Galaxy J2 (J200BT...)? If not, please do one, we're stuck on 5.1.1, and it's a horrible thing.
Do we know anything about lg g2 d802? I would like to know if it will get launched on los 13 or los 14.1 and when , thank you for your great work and for your time
pananoydakis said:
Do we know anything about lg g2 d802? I would like to know if it will get launched on los 13 or los 14.1 and when , thank you for your great work and for your time
Click to expand...
Click to collapse
pananoydakis The LineageOS Team said that the builds will be release periodically starting on January 21st & 22nd, 2017. When a build is available it will be listed on that page. Into the right side "Devices" column, click on the appropriate horizontal tab for your device brand and model. If your device is not yet listed, please re-visit again later.
There are no estimated time of arrival (ETA) for all builds. If you want builds to be release faster you are welcome to love back your LineageOS community by contributing a code review. Either yourself or by paying someone to contribute on your behalf.
For S5 klte pls
Enviado desde mi SM-G900F mediante Tapatalk
Why Cynogenmod and lineageOS does not make ROMs for meizu devices?
Why Cynogenmod and lineageOS does not make ROMs for meizu devices?
tank4k said:
will LOS get substratum compatibility?
Click to expand...
Click to collapse
I hope so... It sucks to have to reapply all of your themes whenever you update.
Ouch. I tried flashing the experimental OnePlus One (bacon) over CM14.1/LineageOS unofficial 20170117. The ZIP signature failed to verify. I (probably foolishly) tried it without ZIP signature verification, and it corrupted the partitions. Back to a few months ago CM14 TWRP backup...
So I highly DON'T recommend trying to flash the 20170123 bacon build if it fails ZIP signature verification.
(Going a touch deeper, there had been problems a couple of major generations of CM ago on the OnePlus One where the ZIPs were fine but the exact signing simply didn't work, and it was appropriate at that time to skip ZIP signature verification, but... oops).
libove said:
Ouch. I tried flashing the experimental OnePlus One (bacon) over CM14.1/LineageOS unofficial 20170117. The ZIP signature failed to verify. I (probably foolishly) tried it without ZIP signature verification, and it corrupted the partitions. Back to a few months ago CM14 TWRP backup...
So I highly DON'T recommend trying to flash the 20170123 bacon build if it fails ZIP signature verification.
(Going a touch deeper, there had been problems a couple of major generations of CM ago on the OnePlus One where the ZIPs were fine but the exact signing simply didn't work, and it was appropriate at that time to skip ZIP signature verification, but... oops).
Click to expand...
Click to collapse
If you flashed the actual nightly (and did a clean install), you shouldn't have this problem. I think.
RockyTV said:
If you flashed the actual nightly (and did a clean install), you shouldn't have this problem. I think.
Click to expand...
Click to collapse
It's possible that I caused the damage myself. The not-ZIP-signature-verified Experimental flash was taking far longer than usual; after about 30 minutes I cold re-started. After the restart, the /system file system was gone.
Two concerns remain:
1. That TWRP 3.0.2.0 fails the ZIP signature verification on BOTH the Experimental and the Nightly.
2. That the flash took 30+ minutes and hadn't completed, when a normal flash on the OnePlus One (including LineageOS unofficial just a few days earlier) takes perhaps 5 minutes, or less.
Hi all !
As I did not find a similar thread yet for the OnePlus 3T, I am starting one now.
I put some flashable zips together, which contain the modem and firmwares (NOT the complete rom, only other parts like bootloader etc.) of several OOS versions.
This allows you to change modems and firmware quickly and easily without flashing the full roms.
Why would you need this?
For instance if you are on OOS 4.0.3 and want to get rid of the nasty dm-verity message during every start.
Then you can flash this 4.0.2 firmware in recovery, boot into fastboot mode, enter the commands to get rid of dm-verity message ("fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity"), reboot straight back into recovery, flash 4.0.3 firmware again and bamm - done.
Installation
1. Download a Firmware+Modem package from below
2. Go into Recovery (TWRP recommended)
3. Flash the downloaded .zip file
4. Reboot
5. Enjoy
Notes
These packages are ONLY FOR THE ONEPLUS3 T, no other phone !!!
Under normal circumstances, you cannot flash this zips on a wrong device as the flash zip checks for the device and will fail if you are not on an OnePlus 3 T.
However, if you are unsure and have adb debug connection, try
Code:
adb shell grep Hardware /proc/cpuinfo
On a OnePlus3T, this gives you "Hardware : Qualcomm Technologies, Inc MSM8996pro" back.
Alternatively you can also check in a local terminal app by entering the following command:
Code:
grep Hardware /proc/cpuinfo
DO NOT flash this package on a OnePlus 3 !!!
All packages are assembled by me from original OOS stock roms only.
Disclaimer
As always - Flash on your own risk !!
Make sure you flash the correct version depending on your device!
I can and will not take any responsibility for bricked phones or lost data.
I will not give any support as the content of the packages come from OnePlus and not from me.
Downloads
OOS 5.0.2 - DOWNLOAD LINK
OOS 5.0.1 - DOWNLOAD LINK
OOS 5.0.0 - DOWNLOAD LINK
OOS 4.5.1 - DOWNLOAD LINK
OOS 4.5.0 - DOWNLOAD LINK
OOS 4.1.7 - DOWNLOAD LINK
OOS Open Beta 11 - DOWNLOAD LINK
OOS 4.1.6 - DOWNLOAD LINK
OOS 4.1.5 - DOWNLOAD LINK
OOS 4.1.3 - DOWNLOAD LINK
OOS 4.1.1 - DOWNLOAD LINK
OOS 4.1.0 - DOWNLOAD LINK
Open Beta 3 - DOWNLOAD LINK
OOS 4.0.3 - DOWNLOAD LINK
OOS 4.0.2 - DOWNLOAD LINK
OOS 3.5.4 - DOWNLOAD LINK
Hi @Lord Boeffla,
I have a question about dm-verity: does fastboot commands used while under 4.0.2 firmware have same result has flashing this zip (from @jcadduono) ?
If yes, why do we simply just flash this zip while under 4.0.3 firmware ?
casual_kikoo said:
Hi @Lord Boeffla,
I have a question about dm-verity: does fastboot commands used while under 4.0.2 firmware have same result has flashing this zip (from @jcadduono) ?
If yes, why do we simply just flash this zip while under 4.0.3 firmware ?
Click to expand...
Click to collapse
Good question. Without analyzing what the zip you refer to does exactly, I cannot answer that.
And I will probably not do that as I personally prefer to work with OnePlus original methods only (flashing their firmware, using official commands is my preferred choice).
So - I cannot say. Up to you how you remove dm-verity best for you.
Andi
Hey andi, there is a similar thread i think
https://forum.xda-developers.com/showthread.php?t=3468628
My bad sorry. This is for OP3
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Crazy_Oni said:
Hey andi, there is a similar thread i think
https://forum.xda-developers.com/showthread.php?t=3468628
My bad sorry. This is for OP3
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Exactly, it is for the OP3. And the firmwares are NOT the same.
Andi
Firmware/Modem of Open Beta 3 added, as this is required to install latest LineageOS version of 9th of March 2017.
Andi
Firmware of todays OOS 4.1.5 added.
Enjoy
Andi
Firmware of todays OOS 4.1.6 added.
Enjoy
Andi
Firmware of Open Beta 11 added, so latest LineageOS can be flashed again properly.
Andi
Firmware of yesterdays OOS 4.1.7 added.
Enjoy
Andi
Firmware of yesterdays OOS 4.5.0 added.
Enjoy
Andi
Firmware of yesterdays OOS 4.5.1 added.
Enjoy
Andi
Firmware of OOS 5.0.0 added.
Enjoy
Andi
Firmware of OOS 5.0.1 and OOS 5.0.2 added.
Enjoy
Andi
Here's a build of TWRP Recovery 3.3.0-0 for the VK810: twrp-3.3.0-0-vk810.img
To install for the first time, follow the same instructions as for the other LG G Pad 8.3 models here: https://twrp.me/lg/lggpad83.html
If already rooted, just download the file and from a local terminal window type:
Code:
su
dd if=/sdcard/Download/twrp-3.3.0-0-vk810.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or on a device that already has an older version of TWRP installed, select Install, tap Install Image, pick the .img file, select Recovery partition, and swipe to install.
I built this from the official TWRP project for the V500, but used the kernel from the unofficial LineageOS 14.1 build available here.
If you want to make modifications or updates, my device configuration project for the VK810 (and V500) are available here: https://github.com/Magendanz/android_device_lge
Note that I just updated the build to TWRP 3.2.1-0. I've also switched to the LineageOS 14.1 prebuilt kernel.
Just updated the build to TWRP v3.2.2-0. Release notes are here.
Magendanz said:
Just updated the build to TWRP v3.2.2-0. Release notes are here.
Click to expand...
Click to collapse
Do you have any custom roms planned? Or do you know of any good ones available now? Thanks for the new TWRP btw!
JTruj1ll0923 said:
Do you have any custom roms planned? Or do you know of any good ones available now? Thanks for the new TWRP btw!
Click to expand...
Click to collapse
I've been using the LineageOS 14.1 builds from @invisiblek (Dan) available here. However, it does have a problem accessing the device sensors, so you can't rotate the screen to change orientation or play many games. I'm anxiously awaiting a LOS 15.1 build.
Magendanz said:
I've been using the LineageOS 14.1 builds from @invisiblek (Dan) available here. However, it does have a problem accessing the device sensors, so you can't rotate the screen to change orientation or play many games. I'm anxiously awaiting a LOS 15.1 build.
Click to expand...
Click to collapse
I tried it and i kept having the screen flicker. Do you have that? I know there is a 8.1 rom for v500... Wonder if there is a way to build off of that? I just barely got this device working again after losing it from a move.
JTruj1ll0923 said:
I tried it and i kept having the screen flicker. Do you have that? I know there is a 8.1 rom for v500.. Wonder if there is a way to build off of that?
Click to expand...
Click to collapse
No, I haven't had a problem with screen flicker. The only OREO 8.1 build for v500 that I've seen is this crDroid one from @beroid. If we can find a nice clean LineageOS 15.1 project for v500 like we have for LineageOS 14.1, I can make the modifications to build for vk810. I did it for LineageOS 14.1 using these instructions, but ran into the same problem with the device sensors.
Magendanz said:
No, I haven't had a problem with screen flicker. The only OREO 8.1 build for v500 that I've seen is this crDroid one from @beroid. If we can find a nice clean LineageOS 15.1 project for v500 like we have for LineageOS 14.1, I can make the modifications to build for vk810. I did it for LineageOS 14.1 using these instructions, but ran into the same problem with the device sensors.
Click to expand...
Click to collapse
If I had a computer I could try and be of use, but sadly mine is out of service until I start my new job here soon.
Just updated the build to TWRP v3.2.3-0. Release notes are here. We're now building using the twrp-6.0 branch, just like the official v500 device tree.
Thanks for the updates!
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~)