{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all,
this is the thread for a custom kernel i made for Samsung Galaxy A10 based on android pie (9).
The custom kernel has been named Eureka which is a greek work which means "I have found the solution". This kernel is the solution for both gaming and performance on our cheap A10.
Compatibility:
This kernel has 2 versions. One version works only on ONE UI (can be stock or debloated ONE UI) and the other version works on GSIs and custom roms (GSIs built specifically for A10). So, please download the correct version.
FEATURES:
* Disabled Samsung security features
* Enabled all governors except Schedutils governor.
* Overclocked CPU as follows:
BIG Cores: from 1560 MHz to 2080 MHz.
LIL Cores: from 1352 MHz to 1690 MHz.* Underclocked CPU as follows:
BIG Cores: from 728 MHz to 312 MHz.
LIL Cores: from 449 MHz to 208 MHz.* Added GPU thermal and voltage control
* Added latest boeffla_wl_blocker V 1.1.0 and disabled some wakelocks
* Network speed improvement
* Enable zram support.
* Switch to a lower charging voltage more quickly.
* GPU max frequency overclocked from 676 MHz to 1300 MHz
* Implemented Dynamic FSync 2.0
* Has Spectrum support
* Pre-rooted with magisk 20.4
* Built with Linaro V4.9.4 toolchain. Reason: Better performance
* FOR GSI:
* Fixed ADB and MTP.
* Set SElinux as permissive
Please read the changelog for full list of changes.
KNOWN ISSUES:
* None
SOME MINOR TWEAKS FOR BEST GPU PERFORMANCE:
* Set GPU power policy to "always on"
* Set GPU governor to "static"
* Set min and max GPU frequency to 1300 MHz
* Disable GPU thermal manager to prevent GPU frequency from dropping
* If you are on ONE UI and GPU keeps on changing when u force it at 1300 MHz, disable/remove devicehealthmanagerservice and gameoptimizingservice apps
* Games don't require high CPU frequency because they depend more on GPU. You can therefore decrease CPU max frequencies to reduce heating of the device.
Best kernel manager for Samsung A series devices is HkTweaks:
LINK: https://drive.google.com/file/d/1LeFWtpBJJEpoU9eT6NH2lImem8yTf_na/view?usp=sharing
My contact info:
Developper:
* Telegram: @Chatur27
Channel for Eureka future updates:
* Telegram: https://t.me/eureka_kernel
Official discussion group for A10:
* Telegram: https://t.me/a10grp
I'm grateful to KineSight for designing the logo.
* Telegram: @Kinesight
Download link for my kernels for A10:
EurekaR4.0 for A105 using GSI or custom rom:
https://github.com/Chatur27/Eureka-kernel-for-SM-A105-Pie/releases/download/rev4.0/Eureka.R4.0_A105.GSI.Pie.zip
EurekaR4.0 for A105 using ONE UI based roms:
https://github.com/Chatur27/Eureka-kernel-for-SM-A105-Pie/releases/download/rev4.0/Eureka.R4.0_A105.ONEUI.Pie.zip
Source code for my kernels:
https://github.com/Chatur27/Eureka-kernel-for-SM-A105-Pie
Can I flash this kernel with Fk Kernel Manager or Ex Kernel apps? I do not have twrp installed, but I have magisk and root on my stock rom. And if I flash it will I lose magisk or root on phone?
sifonaru said:
Can I flash this kernel with Fk Kernel Manager or Ex Kernel apps? I do not have twrp installed, but I have magisk and root on my stock rom. And if I flash it will I lose magisk or root on phone?
Click to expand...
Click to collapse
Hi, I never tried to flash using those apps but you can try if u want.
My kernel is pre-rooted with magisk 20.4, so you won't lose root.
Its a good practice to have TWRP on a rooted device, because it can backup and restore data or system.
I really want to try your kernel but just afraid that if I install twrp on my magisk rooted device I can lose all my data. It's enough to flash twrp from Odin? Is there any patch or step required (before or after the twrp flash process)?
sifonaru said:
I really want to try your kernel but just afraid that if I install twrp on my magisk rooted device I can lose all my data. It's enough to flash twrp from Odin? Is there any patch or step required (before or after the twrp flash process)?
Click to expand...
Click to collapse
After u flash TWRP, u will have to go to wipe→format data→type "yes"
This is done so as to remove the fbe error in twrp.
So u should backup your data first.
Since your phone is already rooted, you can use titanium backup pro to backup your app/game data
When u launch the app for the first time, you have to go it's preferences and scroll down till you find "Backup app external data" and choose "Enabled (always)
Just backup your desired apps and move the TitaniumBackup folder found on your internal storage to your pc or SD card.
To restore, install titanium backup Pro again and copy the TitaniumBackup folder to your internal storage.
Link to titanium backup:
https://drive.google.com/file/d/1MHvWowC6ygCWFKGpOBavkOZCiPtz7OJs/view?usp=drivesdk
sifonaru said:
I really want to try your kernel but just afraid that if I install twrp on my magisk rooted device I can lose all my data. It's enough to flash twrp from Odin? Is there any patch or step required (before or after the twrp flash process)?
Click to expand...
Click to collapse
You don't have to wipe all your data, just wipe cache and dalvik
Primeaqua02 said:
You don't have to wipe all your data, just wipe cache and dalvik
Click to expand...
Click to collapse
Bro, that won't solve fbe error.
2080 MHz frequency does not work
Hello, I have a maximum frequency of large cores of only 1768 MHz but in settings EX Kernel the manager has the ability to choose 2080 MHz, what may be the problem?
i did flash the kernel and i got an issue, the phone bricks when i power on with the charger connected and i cant run the phone, but when i disconnect the charger from the phone and power on it runs perfect with the kernel, idk why, when i shut down my phone and i put the charger the charging icon got a freeze for forever. whay i can do?
Zloemoloko1998 said:
Hello, I have a maximum frequency of large cores of only 1768 MHz but in settings EX Kernel the manager has the ability to choose 2080 MHz, what may be the problem?
Click to expand...
Click to collapse
Yeah,that's a limit of Exynos Kernels.
No fix has been found for that yet.
I recommend using HkTweaks and go to CPU tab. Change governor to userspace and min and max Frequency to max frequency (2080 and 1690)
This has high battery drain. So use it only if u need max performance
Hello, I have a question, is this modified kernel useful for the Pixel Experience custom ROM with Android 10? I wait your answer.
Is it android 10 compatible ?
Maroon2609 said:
Hello, I have a question, is this modified kernel useful for the Pixel Experience custom ROM with Android 10? I wait your answer.
Click to expand...
Click to collapse
First of all, the thread title says it's for Android 9
If you want Eureka for Android 10 , Search XDA more
There is another version for Android 10
A kernel makes any ROM/GSI better. Just try it
You can always go back to stock Kernel later
dornz said:
Is it android 10 compatible ?
Click to expand...
Click to collapse
If you want Eureka for Android 10 , Search XDA more
There is another version for Android 10
Please
How to flash this kernel, some body got the bricks phone, please give me the method to flash, thank you.
IneedFiveMore said:
How to flash this kernel, some body got the bricks phone, please give me the method to flash, thank you.
Click to expand...
Click to collapse
It's not easy to brick a Samsung phone
God knows where u get this information.
This kernel is 100% working.
Just flash the kernel in twrp and reboot.
This kernel version already has magisk root.
If you get stuck on A10 logo, force restart and let it boot normally
I have rebooted into "Download Mode" and have successfully flashed TWRP 3.3.1-0. Now, after rebooting and accessing the recovery, I have done a "Format Data", to then flash Eureka Kernel 4.0, then I did a "Wipe Dalvik and Cache" and then "Reboot System", but the device falls into bootloop... I then rebooted into TWRP to flash Magisk 20.3 to see if that way the device would bootloop, but it remains the same. Ultimately I proceeded to flash magisk-uninstaller and it didn't work. The only way is to reinstall the firmware.
*What is the correct way to install this kernel?
*Does it actually work for Android 9?
When flashing the kernel it says: "FOR ANDROID VERSION 10 (Q)"
PS: I clarify that I have flashed "Eureka.R4.0_A105.ONEUI.Pie.zip" which is supposed to be the proper kernel for Android 9 Pie.
Chatur27 said:
Hi all,
this is the thread for a custom kernel i made for Samsung Galaxy A10 based on android pie (9).
The custom kernel has been named Eureka which is a greek work which means "I have found the solution". This kernel is the solution for both gaming and performance on our cheap A10.
Click to expand...
Click to collapse
I managed to install your kernel correctly, thanks really, it works great… It cost me a little at first but it already remained…
I have seen that in the kernel you developed for Android 10 you added «double tap to wake» and «double tap to sleep». Could you add it in a future update in this version for Android Pie?
try to install this kernel on android stock 9, with twrp but it left me on galaxy a10 frozen
I tried with the two files one by one repairing the system
JuCeNM2496 said:
I managed to install your kernel correctly, thanks really, it works great… It cost me a little at first but it already remained…
I have seen that in the kernel you developed for Android 10 you added «double tap to wake» and «double tap to sleep». Could you add it in a future update in this version for Android Pie?
Click to expand...
Click to collapse
how did you do it?
sgh-t599n said:
how did you do it?
Click to expand...
Click to collapse
You have to follow a few steps:
1- Start in TWRP and in "Backup and Restore" choose only the "Boot" partition into SD Card or Internal Storage…
2- Install "Eureka-4.0" and Wipe /Cache and /Dalvik and then restart.
3- Wait until the system starts (that takes about 10 minutes) if the device gets stuck on the boot logo, force the shutdown by pressing the keys: "Power" & "Vol +" & "Vol -" after this it should start correctly.
4- If it still doesn't turn on you will have to force it off once more and start in "Recovery Mode" and flash Magisk "20.3" or Magisk "20.4" (you shouldn't install a newer version of Magisk or there will be bootloop problems)
5- Reboot and enjoy…
P.S: If the bootloop still persists (somewhat unlikely) then go to "Backup and Restore" and choose to restore the "Boot" partition that they had previously backed up and everything is fine again, as if nothing happened. Good Luck!!!
Related
Hi,
I found a link for Liquid Smooth unofficial build for our note on their google+ community.
http://dl.niimdroid.com/LiquidSmooth/n7000/
I just want to share. [emoji6]
Greetings from Germany
scoute-dich
really smooth perhaps the best I have tried (and I've tried many rom) thanks
wow that's awesome! are you the one building these?? I am going to try this asap
thank you very much for the link
REVENGE SOLVES EVERYTHING
tysonraylee said:
wow that's awesome! are you the one building these?? I am going to try this asap
thank you very much for the link
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
No, I didn't build it, I just found the link. But I also think that this is a good rom. I didn't found a xda-thread, so I posted it here...
Greetings from Germany
scoute-dich
flahsed the 18-10-2014 release
multi-user works
hover is included
seems very stable
Theme engine needs some updating but i guess should be included in the future updates
what else can i ask for
thank you very very much
Hope there would be an official thread for this
scoute-dich said:
No, I didn't build it, I just found the link. But I also think that this is a good rom. I didn't found a xda-thread, so I posted it here...
Greetings from Germany
scoute-dich
Click to expand...
Click to collapse
Its being made by the Great dev for the asylum omni "Bosko Trkulja" aka chasmodo
follow the link here...by the way,these are the blind builds of his,,,
https://plus.google.com/103683575509787472991/posts/GBdaA3FuKDp?cfem=1
DrNinjaa said:
Its being made by the Great dev for the asylum omni "Bosko Trkulja" aka chasmodo
follow the link here...by the way,these are the blind builds of his,,,
https://plus.google.com/103683575509787472991/posts/GBdaA3FuKDp?cfem=1
Click to expand...
Click to collapse
wow!!! chas is the man an awesome and talented dev indeed
REVENGE SOLVES EVERYTHING
Hi mates,
I've not seen any instructions about installing that ROM. With only 170GB probably it is not a full rom.
I haven't seen the kernel in it and also SecPhone.apk; SecContacts.apk; SecSetings.apk etc. . . . . even SystemUI.apk
Could somebody post any guidelines about installation, which kernel should be used etc. :fingers-crossed:
Should SNote apps etc. from Note3 works on it without any changes?
Thanks.
Avitohol said:
Hi mates,
I've not seen any instructions about installing that ROM. With only 170GB probably it is not a full rom.
I haven't seen the kernel in it and also SecPhone.apk; SecContacts.apk; SecSetings.apk etc. . . . . even SystemUI.apk
Could somebody post any guidelines about installation, which kernel should be used etc. :fingers-crossed:
Should SNote apps etc. from Note3 works on it without any changes?
Thanks.
Click to expand...
Click to collapse
This is an AOSP rom which is like a Google stock firmware found in nexus devices that's why the size is 170-200mb and yes this is a full rom though you have to download gapps separately
The firmware you are thinking about is the Samsung bloated firmware filled with unnecessary junk making it around 1 - 1.5GB and so we call it Crapsung
Sorry I despise Samsung firmware, never used it and never will
Also note since this is not a Samsung firmware you will not able to use Snote or any Samsung related application as they are not compatible with AOSP framework
The instructions to flash this firmware are as follows
1) download ROM (the kernel is included in the ROM itself )
2) download PA Gapps
3) make sure your device is ROOTED and if not rooted already, please ROOT your device. (This is a mandatory and important step)
4) download RAW kernel for KK ROMs. (we have to use this kernel as KK ROMs require SE Linux compatible recovery otherwise you will not be able to flash it)
Note : raw kernel doesn't becomes your device kernel. The kernel is bundled with the ROM which will get flashed along with it
5) move all downloaded files to internal or external SD.
6) Now on a ROOTED device, reboot it to recovery by pressing home key + power key + volume up key simultaneously.
7) Since you are already rooted I expect might also have flashed a custom recovery. If so take a nandroid backup with that recovery [ DO NOT SKIP THIS STEP ]
7) Once nandroid backup is done do the following
-wipe data factory reset
-wipe cache
-go to mounts and storage and format system
-go to advance and wipe dalvik cache
8) back to the main menu choose install zip and first install RAW kernel and once done navigate to advance and select "reboot recovery" [ do not skip this step]
9) assuming that everything went correctly you should now be booted into TWRP recovery. You could do a factory reset here too if you want
10)Now choose install and select the ROM file first and queue the Gapps file too and flash
11) once the process is complete reboot and setup your device accordingly
12) and if not already Welcome to real world of android (Aosp/cm11)
Simple right
Raw kernel can found in the development section of N7000 forum with a simple search make sure to download the one for KK ROMs.
As for Gapps just go to Google and type pa gapps and the first link will take you to PA Gapps xda thread. Choose your pick from there
hope that helps
thank you very much
REVENGE SOLVES EVERYTHING
tysonraylee said:
This is an AOSP rom which is like a Google stock firmware found in nexus devices that's why the size is 170-200mb and yes this is a full rom though you have to download gapps separately
The firmware you are thinking about is the Samsung bloated firmware filled with unnecessary junk making it around 1 - 1.5GB and so we call it Crapsung
Sorry I despise Samsung firmware, never used it and never will
Also note since this is not a Samsung firmware you will not able to use Snote or any Samsung related application as they are not compatible with AOSP framework
The instructions to flash this firmware are as follows
1) download ROM (the kernel is included in the ROM itself )
2) download PA Gapps
3) make sure your device is ROOTED and if not rooted already, please ROOT your device. (This is a mandatory and important step)
4) download RAW kernel for KK ROMs. (we have to use this kernel as KK ROMs require SE Linux compatible recovery otherwise you will not be able to flash it)
Note : raw kernel doesn't becomes your device kernel. The kernel is bundled with the ROM which will get flashed along with it
5) move all downloaded files to internal or external SD.
6) Now on a ROOTED device, reboot it to recovery by pressing home key + power key + volume up key simultaneously.
7) Since you are already rooted I expect might also have flashed a custom recovery. If so take a nandroid backup with that recovery [ DO NOT SKIP THIS STEP ]
7) Once nandroid backup is done do the following
-wipe data factory reset
-wipe cache
-go to mounts and storage and format system
-go to advance and wipe dalvik cache
8) back to the main menu choose install zip and first install RAW kernel and once done navigate to advance and select "reboot recovery" [ do not skip this step]
9) assuming that everything went correctly you should now be booted into TWRP recovery. You could do a factory reset here too if you want
10) Now choose install and select the ROM file first and queue the Gapps file too and flash
11) once the process is complete reboot and setup your device accordingly
12) and if not already Welcome to real world of android (Aosp/cm11)
Simple right
Raw kernel can found in the development section of N7000 forum with a simple search make sure to download the one for KK ROMs.
As for Gapps just go to Google and type pa gapps and the first link will take you to PA Gapps xda thread. Choose your pick from there
hope that helps
thank you very much
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thanks. This is fully thorough instruction. Thanks :good:
My Liquid Smooth with Bauner Kernel, really fast! Thanks mythical chasmodo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7000 using Tapatalk
panamera2011 said:
My Liquid Smooth with Bauner Kernel, really fast! Thanks mythical chasmodo
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Made the switch to LS and Bauner kernel, very good combo ?
Ls 20142024
https://plus.google.com/103683575509787472991/posts/bRVf12Uec8Z
chasmodo said:
https://plus.google.com/103683575509787472991/posts/bRVf12Uec8Z
Click to expand...
Click to collapse
awesome!! will flash this when I get home
thank you very much
REVENGE SOLVES EVERYTHING
I am getting the error "unfortunately ui system process has stopped"
I have tried full wipe and also without gapps but still the same error.
is it just me or is anybody else getting it too??
REVENGE SOLVES EVERYTHING
Hi bro try with clean install there is no problem here....
yes the build is fine works perfectly
its my sim that was causing the FC's changing my sim solved the problem
REVENGE SOLVES EVERYTHING
Is that normal or battery draining could someone guide me what is causing my battery drain fast..
Ls 20141026
https://plus.google.com/103683575509787472991/posts/a7sBzu6JQJy
LS-KK-v3.2-2014-10-26-n7000 [emoji4]
Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Reserved
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app
rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?
Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.
Everything went smooth! Thank you so much!
rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.
No problems at all... Everything went perfect!
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.
need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921
ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"
Unofficial release -TWRP recovery for the Galaxy J3 2017 - SM-J330F/FN/FZ/G/DS EXYNOS 7570
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance
UPDATE 10/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status: Beta
Update 15/9/2018
TWRP 3.2.3-1 OO build released.
Current status: Stable
Update 27/1/2018
TWRP 3.2.1-1NN build released
Current status: Stable
Update 23/11/2017
TWRP 3.1.1-1 NN build released.
Current status: Stable
Features:
TOUCHSCREEN working
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.[/B]
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1)
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1, THE DEVICE WILL AUTO BOOT TO RECOVERY)
5. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
DOWNLOAD:
twrp_3.3.1-1_sm-j330x_13819
twrp_3.2.3-1_j330_13918
twrp_3.2.1-1_sm-j330f_270117
twrp_3.1.1-1_sm-j330f_231117
Nougat Root instructions:
Install latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, disable dmverity and mount internal storage:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install the boot image patch.
Boot image patch
no-verity-no-encrypt_ashyx
5. Install Magisk(if root is required)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Reboot
OREO ONLY ROOT INSTRUCTIONS:
1. Install the Root patch kernel with TWRP.
J330F-FN_root_no_sim_patch
NOTE:This is a custom Oreo J330F/FN XXU3BRG3 permissive/enforcing kernel and patch built from source. It makes changes to the system partition also.
What does it do?:
*It installs a custom kernel to fix the no SIM issue when rooting.
*Patches the system to fix WIFI and Bluetooth not turning on when using custom kernels.
*Patches DM-Verity.
*Removes forced encryption and patches /data not able to be mounted (after formatting).
*Removes the SecurityLogAgent nag when using a custom kernel.
2. If you wish to mount /DATA for access to internal storage then FORMAT the /DATA partition.
3. To root install the latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
PIE ONLY ROOT INSTRUCTIONS:
To root install latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable encryption (mount DATA in TWRP) install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
Finally FORMAT /DATA in TWRP.
Reboot.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @lemlis, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
UPDATE: Touchscreen fixed
.
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
Click to expand...
Click to collapse
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Click to expand...
Click to collapse
Probably the version of SuperSu you flashed.
ashyx said:
twrp_3.1.1-1_sm-j330f_231117
Click to expand...
Click to collapse
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
lemlis said:
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
View attachment 4340464View attachment 4340476
Click to expand...
Click to collapse
Seems I didn't include my updated FSTAB in the new build. Corrected, thanks for pointing it out.
ashyx said:
Probably the version of SuperSu you flashed.
Click to expand...
Click to collapse
Yeaa you right..i use super su which remain in my memory card almost 2 years ago ???
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
BlackDragonz said:
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
Click to expand...
Click to collapse
updato.com
i cant flash super su twrp didn't show the file to flash
File to flash have to be on sd card ?
Help Me
azhar960225 said:
Help Me
Click to expand...
Click to collapse
Police. Fire or ambulance?
I Want root j3 pro 2017..but how
azhar960225 said:
I Want root j3 pro 2017..but how
Click to expand...
Click to collapse
Flash SuperSU or Magisk.
How? To Flash How? Cannot root j3 How to Flash?
7.11 Android...
arabarabow said:
twrp didn't show the file to flash
Click to expand...
Click to collapse
put zip file inside any folder.File to flash have to be in folder
Just done flashing latest build and flashed magisk, all are running fine. Tysm @ashyx !
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
arabarabow said:
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
Click to expand...
Click to collapse
Boot to TWRP and flash Supersu or Magisk. Use the three button combo.
Can i just use cf auto root to root my phone without installing a recovery? Or it's better to root using this method?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads :
DO NOT USE TWRP OR ANY OTHER CUSTOM RECOVERY. READ INSTALLATION INSTRUCTIONS BEFORE INSTALLING
SourceForge folder (includes rom, LineageOS recovery image)
OpenGapps
Magisk
Installation :
You MUST have unlocked botloader and running latest stock android 11 on your phone
You can find information about installing and using adb here
1) Flash LineageOS recovery via fastboot using command
fastboot flash boot <name of the file>
2) Reboot to recovery
3) Download copy-partitions-20200903_1329.zip (this script makes sure both slots on your phone uses same firmware by copying it from active to inactive slot and was created by official LineageOS maintainers)
4) Navigate Apply update -> apply from ADB
5) Sideload copy-partitions-20200903_1329.zip using command
adb sideload copy-partitions-20200903_1329.zip
Tap 'continue' on your phone when prompted
6) Perform factory reset
7) Navigate Apply update -> apply from ADB
8) Sideload rom .zip
adb sideload <rom zip name>
9) Reboot recovery (Advanced -> Reboot to recovery)
Now you can sideload gapps or magisk if you need them (recovery might give you a warning about flashing unsigned files, just click second option and installation process will continue)
10) Navigate Apply update -> apply from ADB
11) Sideload rom .zip
adb sideload <zip name>
* For new Magisk versions change file extension to zip to be able to sideload it
12) Tap 'Reboot system now'
Updating to a new version:
1) Reboot recovery
2) Navigate Apply update -> apply from ADB
3) Sideload rom .zip using
adb sideload <rom zip name>
4) Reboot recovery (Advanced -> Reboot to recovery)
Now you need to sideload gapps or magisk if had them installed (recovery might give you a warning about flashing unsigned files, just click second option and installation process will continue)
5) Navigate Apply update -> apply from ADB
6) Sideload .zip package
adb sideload <zip name>
* For new Magisk versions change file extension to zip to be able to sideload it
7) Tap 'Reboot system now'
Notes :
- This is personal build for my own usage, I'm just sharing it
- Custom recoveries, kernels, mods are not supported
Trees :
Common tree: https://github.com/HarukeyUA/android_device_xiaomi_sm6125-common
Device tree: https://github.com/HarukeyUA/android_device_xiaomi_laurel_sprout
Kernel: https://github.com/HarukeyUA/android_kernel_xiaomi_laurel_sprout
Vendor: https://github.com/HarukeyUA/proprietary_vendor_xiaomi
Reserved
What is the difference between this lineageOS and the other android11 firmware one?
antoine62 said:
What is the difference between this lineageOS and the other android11 firmware one?
Click to expand...
Click to collapse
This is OSS build.
@HarukeyUA
Since it's your personal build can you add smart charging feature (cherry pick) please (for battery health) , hope you release next build with smart charging feature plox
1. Bugs?
2. Plans for going official?
Sairagav said:
1. Bugs?
2. Plans for going official?
Click to expand...
Click to collapse
All major features (including, but not limited to wfd, selinux enforcing, L1 drm) are working fine. But there still can be bugs I didn't discover because of my usage pattern and/or availability in my region.
I don't have any plans for official status.
i flashed this rom ... now my phone is dead and will not turn on. :-(
(happened at point 6: "Reboot recovery (Advanced -> Reboot to recovery)")
any tipps for de-bricking anyone?
//edit:
i managed to flash the service-rom via MiFlash... the phone is okay again, and this ROM does also work now.
Typhoon_Master said:
i flashed this rom ... now my phone is dead and will not turn on. :-(
(happened at point 6: "Reboot recovery (Advanced -> Reboot to recovery)")
any tipps for de-bricking anyone?
//edit:
i managed to flash the service-rom via MiFlash... the phone is okay again.
Click to expand...
Click to collapse
Are you sure you had latest Android 11 Firmware in both slots? Which device version do you have (Global, EU)?
Rom boots fine on my global Mi A3 (128/4) upgraded to Android 11 firmware via fastboot flash
Harukey said:
Are you sure you had latest Android 11 Firmware in both slots? Which device version do you have (Global, EU)?
Rom boots fine on my global Mi A3 (128/4) upgraded to Android 11 firmware via fastboot flash
Click to expand...
Click to collapse
Yes. I had the latest official EU Version 12.0.4.0 (Android 11) on my device.
//edit:
however: i then flashed the service-rom from here via MiFlash. The Phone bootet again and i just flashed this rom now and it is working.
New build is up
Changelog:
- LineageOS source sync
- Merged LA.UM.9.1.r1-09100-SMxxx0.0 into kernel
- Kernel version 4.14.223
- Switch to source built perf interface
- Init script upstream from caf
- Updated carrier config from LA.UM.9.11.r1-02800-NICOBAR.0
- Imported dpm properties from stock
Download: SourceForge
Harukey said:
- This is personal build for my own usage, I'm just sharing it
Click to expand...
Click to collapse
Thanks for your work...
- Any screen-shots?
- How is the SOT & overall battery life?
Typhoon_Master said:
The Phone bootet again and i just flashed this rom now and it is working.
Click to expand...
Click to collapse
Did you identify what went wrong at your first try?
XDAnewone said:
Thanks for your work...
- Any screen-shots?
- How is the SOT & overall battery life?
Click to expand...
Click to collapse
XDAnewone said:
Did you identify what went wrong at your first try?
Click to expand...
Click to collapse
Screenshots
Battery life is subjective and depends on your usage pattern
As for second post, I guess they had Android 11 firmware in one slot and Android 10 firmware in another, so when device switched slots it refused to boot due to firmware incompatibility.
XDAnewone said:
Did you identify what went wrong at your first try?
Click to expand...
Click to collapse
I have no idea.
Harukey said:
As for second post, I guess they had Android 11 firmware in one slot and Android 10 firmware in another, so when device switched slots it refused to boot due to firmware incompatibility.
Click to expand...
Click to collapse
Yes could be, but again: I have no idea.
Hi, I would like to know if it is possible to update the system from an old version of your rom without needing to reflash the rom and lose its data ?
Excuse me if my english is bad.
(I flashed the rom yesterday)
Dabrico said:
Hi, I would like to know if it is possible to update the system from an old version of your rom without needing to reflash the rom and lose its data ?
Excuse me if my english is bad.
(I flashed the rom tomorrow)
Click to expand...
Click to collapse
If you coming from 17.1 you must format data.
If you coming from my older 18.1 build you can follow instruction from this thread skipping recovery fastboot flashing and format data steps
Harukey said:
If you coming from 17.1 you must format data.
If you coming from my older 18.1 build you can follow instruction from this thread skipping recovery fastboot flashing and format data steps
Click to expand...
Click to collapse
Thank you
[Edit :] I reinstalled your rom because my phone didn't want to boot after I followed your instructions.
ok if we want to install with twrp
Brand new phone, had 9 so did the OTAa to 10 and 11, then I'm guessing this happened:
Harukey said:
As for second post, I guess they had Android 11 firmware in one slot and Android 10 firmware in another, so when device switched slots it refused to boot due to firmware incompatibility.
Click to expand...
Click to collapse
If your instructions have a decent chance of resulting in a bricked device, it might be helpful to include steps to check or correct that before leading slot-noobs such as myself down the path to no-no-more-bootey-boot-land.
Thanks asshole for my new EDL cable, and the sweet ROM. It's nice, so far I've noticed:
- Phone... Settings... Calling accounts... does not persist between reboots with one SIM and a SIP account; choosing the SIP account as default reverts to the SIM every time. Curiously, with two SIMs inserted, this will persist on any of the three settings between reboots.
- Phone... call recording does not appear to work, blank audio files are created, although this was only tested with a SIP account so may just be a limitation. Also tried Call Recorder by SKVALEX v2.1.0 via Magisk module, same blank audio files.
- fingerprint reader doesn't work, but that's possibly due to my EDL adventure as it booted up after rawprogram4+patch4 and I couldn't get it back into EDL to do 5... so now I'm not really sure what state my device is in, joy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 7.1 for the Xiaomi Mi Note 10 Lite [toco]
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
- Have the latest Global stable MIUI v13.0.2.0 installed
- Make sure you're running TWRP or OrangeFox for Android 13
- Boot into recovery
- Copy Rom
- Flash Rom
- Format data
- Reboot to system & #KeepEvolving
Update / Dirty Flash
- Boot into recovery
- Flash Rom
- Wipe Dalvik Cache & Cache
- Reboot to system & #KeepEvolving
Download
Donate me! / Official Chat / Device Support
Android version: 13.0.0_r6
Evolution version: 7.1
Security patch level: September 2022
Build Author: AndroidHQ254
ROM Source: [URL]https://github.com/Evolution-X[/URL]
Kernel Source:: VantomKernel
ROM Developer: Joeyhuab
XDA:DevDB Information
Evolution X, ROM for the Xiaomi Mi Note 10 Lite
Contributors
AndroidHQ254, @NeoArian
Source Code: https://github.com/Evolution-X
ROM OS Version: Android 13
ROM Kernel: Linux 4.14.292
ROM Firmware Required: Latest Stable MiUI v13.0.2.0 (Android 12)
Based On: AOSP
Version Information
Status: Stable
Created 2020-09-22
Last Updated 2022-09-22
Dirty flash is available/possible when I'm update from A.12.1 of evoX?
kavillock said:
Dirty flash is available/possible when I'm update from A.12.1 of evoX?
Click to expand...
Click to collapse
NO. This requires a clean flash
i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience
I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?
i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening
Alenett said:
I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?
Click to expand...
Click to collapse
You need Global MIUI 13.0.2.0 and this is specified in the post
Fox_it3 said:
i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience
Click to expand...
Click to collapse
It would not be shared here if it were not stable
Fox_it3 said:
i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening
Click to expand...
Click to collapse
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13
AndroidHQ254 said:
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13
Click to expand...
Click to collapse
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom
Fox_it3 said:
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom
Click to expand...
Click to collapse
If you are on Android 13, you should not have any mounting issues unless you have something messed up. Keep in mind that the recoveries are tested extensively before posting
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
AndroidHQ254 said:
You need Global MIUI 13.0.2.0 and this is specified in the post
Click to expand...
Click to collapse
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.
Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
There is a separate recovery for each Android version. So I don't understand why you are using an OrangeFox for Android 13 on Android 12. Stick to the specifications and follow instructions
Alenett said:
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.
Click to expand...
Click to collapse
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom
AndroidHQ254 said:
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom
Click to expand...
Click to collapse
It is what i did.
Alenett said:
It is what i did.
Click to expand...
Click to collapse
All working great I hope
Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!
Alenett said:
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!
Click to expand...
Click to collapse
Thanks i must have missed this for sure , im pretty basic at this custom rom stuff thanks a lot
Double tap to wake does not work after ~5 seconds after screen off (after the always on display dims down)
* Might be related to a broken screen replacement.
* I DID verify that the problem is a software problem - flashed xiaomi.eu rom and it DOES work there.
* I'm NOT at all sure it worked even with original screen (screen was fully functional, just a few cracks in the glass)
Update:
Tried derpfest and project elixir, same problem.
also found this on pixel-experience github issue tracker...
exactly the same issue - AOD becomes too dim and tap to wake stops working.
seems it's a known problem.