Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is a continuation of the work by Shakalaca. Currently not much will be different. It does have however the latest security Patches. I will be splitting my time between CM 14.1 and Lineage 15. If you have questions please ask. The Z017 should work with both versions, I am running the Z012(KE552KL) and it seems okay.
Prerequisites:
TWRP
Unlock Bootloader
What Works?
- No Major Issues
What's broken ?
You tell me
Download Links
ROM:
https://drive.google.com/drive/folders/0B9R9sRY5L3uiM055Z3ZYeF9MXzA?usp=sharing
TWRP:
https://drive.google.com/drive/folders/0B9R9sRY5L3uidzNmTmpzSWthMTQ
GAPPS:
http://opengapps.org/
Special Thanks @anhenrique @shakalaca
Source Code:
https://github.com/LineageOS-Zenfone3
XDA:DevDB Information
LineageOS 14.1 for ZE552KL and ZE520KL, ROM for the Asus ZenFone 3
Contributors
basenode, basenode
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-08-31
Last Updated 2017-08-30
Changelog:
Aug 30 2017:
- Build Using Latest CM14.1 Sources (Android 7.1.2)
- Includes August Security Updates
I'll try it out sir. Considering I sat across from you for two days while you were dinkin around with it
Nice man Hope you can fix 60fps record bug
Is it 7.1.2?
sontranngoc said:
Is it 7.1.2?
Click to expand...
Click to collapse
Yes it is.
[email protected]
basenode said:
Yes it is.
Click to expand...
Click to collapse
Thank you. I'm installing. But why I cannot install a zip file from internal memory, it has no choice (I can do that with Xperia Z). I have to install by adb sideload instead.
sontranngoc said:
[email protected]
Thank you. I'm installing. But why I cannot install a zip file from internal memory, it has no choice (I can do that with Xperia Z). I have to install by adb sideload instead.
Click to expand...
Click to collapse
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Can you insert ViperOS / ResurrectionRemix functions? How to lock the power menu and block fast access, both with the screen locked? This helps a lot when the cell phone is lost or stolen.
kiq1702 said:
Can you insert ViperOS / ResurrectionRemix functions? How to lock the power menu and block fast access, both with the screen locked? This helps a lot when the cell phone is lost or stolen.
Click to expand...
Click to collapse
I would like to keep this rom as stick as possible. I am open to Updating the existing ViperOS Rom for this device. I am one person so it might be difficult for me to support too many roms especially considering my personal desire to see oreo on this device. I will take a look @ Viper and see what I can do.
basenode said:
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Click to expand...
Click to collapse
I cannot boot to TWRP:
fastboot flash recovery twrp-3.1.0-0-Z012-20170408-N.img
target reported max download size of 536870912 bytes
sending 'recovery' (21080 KB)...
OKAY [ 0.697s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.838s
...
..
fastboot reboot
rebooting...
finished. total time: 0.016s
After this command, the phone start normally, not into TWRP
---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------
basenode said:
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Click to expand...
Click to collapse
I can boot into TWRP, but after wipe cache, system, dalvik, i install the zip file, it shows the error:
Can't install this package on top of incompatible data
Updater process ended with ERROR: 7
Error installing file 'zip ......'
sontranngoc said:
I cannot boot to TWRP:
fastboot flash recovery twrp-3.1.0-0-Z012-20170408-N.img
target reported max download size of 536870912 bytes
sending 'recovery' (21080 KB)...
OKAY [ 0.697s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.838s
...
..
fastboot reboot
rebooting...
finished. total time: 0.016s
After this command, the phone start normally, not into TWRP
---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------
I can boot into TWRP, but after wipe cache, system, dalvik, i install the zip file, it shows the error:
Can't install this package on top of incompatible data
Updater process ended with ERROR: 7
Error installing file 'zip ......'
Click to expand...
Click to collapse
Hi!
This will solve your problem.:
1- Open the ROM with Winrar;
2- Go to: META-INF -> com -> google -> android;
3- Run the "updater-script" file with Notepad ++;
4- Delete the first 1 line, save and update the file in ROM;
Update your TWRP from main Zenfone 3 folder: https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA (twrp-3.1.1-0-Z017-20170826.img)
ToDream said:
Hi!
This will solve your problem.:
1- Open the ROM with Winrar;
2- Go to: META-INF -> com -> google -> android;
3- Run the "updater-script" file with Notepad ++;
4- Delete the first 1 line, save and update the file in ROM;
Update your TWRP from main Zenfone 3 folder: https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA (twrp-3.1.1-0-Z017-20170826.img)
Click to expand...
Click to collapse
Thanks. I have installed successfully.
We have to remove 2 BELOW RED LINE, NOT FIRST 1 LINE:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
The first line will check for products, I saw that line already included Z017 and Z012, it's not a problem.
sontranngoc said:
Thanks. I have installed successfully.
We have to remove 2 BELOW RED LINE, NOT FIRST 1 LINE:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
The first line will check for products, I saw that line already included Z017 and Z012, it's not a problem.
Click to expand...
Click to collapse
Actually it depends on the program that you will use to edit, using Notepad ++ you delete only this line of verification.
Follows attached
RobinRo said:
Nice man Hope you can fix 60fps record bug
Click to expand...
Click to collapse
@kyle_l88 and I are working on it but I can't make and promises
Battery Issues
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
So far everything seems pretty great. Had a couple force close issues. The camera certainly doesn't support 60FPS recording on 1080p yet. But i am working on that part of the code. Otherwise there seems to be few, if any, issues. High five! :good:
jyao6429 said:
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
Click to expand...
Click to collapse
I am running it on a test device and and looking at the battery life. I'll leave it on tonight also to see how it does. I don't think this version has doubletap to wake. I know there is double tap on statusbar for sleep.
I added an issue here for tracking: https://github.com/LineageOS-Zenfone3/android_device_asus_Z017/issues/2
jyao6429 said:
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
Click to expand...
Click to collapse
Did you wipe everything before installing or dirty flash over the shakalaca ROM?
basenode said:
Did you wipe everything before installing or dirty flash over the shakalaca ROM?
Click to expand...
Click to collapse
No, I did not wipe it. This problem was also present in the most recent ROM from shakalaca if that helps.
Related
PREAMBLE
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* 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 recovery image
* [B]before[/B] 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.
*/
I'll keep this thread short and simple. Want a changelog or a list of features? Then visit teamw.in.
Want to see screenshots? They can be found here.
DOWNLOAD
You can always get the latest build from here.
INSTRUCTIONs
The builds can be flashed using an existing recovery. However, should you be unable to flash that ZIP (it seems like CM recovery can't flash it) then do the following:
Download the latest TWRP nightly build and extract the recovery image (recovery.img)
Put the file on the root of your internal storage (e.g. by doing "adb push recovery.img /sdcard")
Use a Terminal Emulator on your phone or connect your device to your PC (type "adb shell" in that case) and run the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It doesn't work... Plox halp, dev?
There's absolutely nothing I can do without logs. Do the following:
Code:
adb pull boot.txt
adb pull tmp/recovery.log
Pull the these two files and post them here (also mention what ROM you currently use!) - otherwise your post will be ignored.
XDA:DevDB Information
TWRP for Sony Xperia Z, Tool/Utility for the Sony Xperia Z
Contributors
Olivier
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2014-12-24
Last Updated 2015-04-11
HALP?
In some cases, TWRP won't work because the buffer for uncompressed ramdisks is too small (in the extract_elf_ramdisk binary) - is this my fault? NO! - Ask your ROM dev to cherry-pick these patches: gerrit.omnirom.org/#/q/topic:fusion3-twrp
Example:
Code:
RECOVERY BOOT
ANDROID! format...
Offset: 6137856
Size: 4961834
gunzip error -- Err:inflate -5
Failed to gunzip
cpio: logo.rle not created: newer or same age file exists
cpio: sbin/busybox not created: newer or same age file exists
8735 blocks
The problem is with the boot.img - I have already fixed that in OmniROM, Slim and my HodorKernel. Plus everyone who has flashed MultiROM isn't affected either.
Should your ROM dev be too lazy or just not willing to fix it in his ROM, flash this hack. It will serve you well for now.
Hi, I cant get this to work with CM 12 by infected. Official twrp 2.8.0.1 works, if I flash this one CM recovery shows up.
This is my boot.txt
Wed Dec 24 12:02:04 GMT 2014
ANDROID BOOT
cpio: logo.rle not created: newer or same age file exists
2354 blocks
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
Wed Dec 24 12:02:07 GMT 2014
I cant find tmp/recovery.log
Is it located somewhere else?
infected_ said:
check your PM box... log is there.
and you really want to go down that road again?
Click to expand...
Click to collapse
Yes, you sent me the log after I had literally begged you to do so. Just wanted to let you know that what you did was wrong.
infected_ said:
check your PM box... log is there.
and you really want to go down that road again?
Click to expand...
Click to collapse
Oliver has got a point. Your messages were rude whilst he was trying to help. Not hard to apologise...
Sent from my Xperia Z using XDA Free mobile app
infected_ said:
Its not working for me on the FOTAKernel, here you have the log: boot.txt, and its better to mention on OP that dd command needs to be run as root ("adb root" before "adb shell" or "su" after "adb shell")
regards..
edit:
trying now;
https://github.com/omnirom/android_...mmit/2c51477bc064e52e4095ecae6df1dbe0dfcb5849
i'll let you know it a bit if it worked.
edit2:
awesome. its working, in the link below is latest infected yuga cm12 boot.img, compatible with TWRP 2.8.3.0 ..
https://www.mediafire.com/?9vnr7t9dmoysqau
thanks to @Olivier for figure it what was wrong.
Click to expand...
Click to collapse
Hi, thank you guys for figuring that out. Where is the difference between oliviers twrp build and the official one? Does the offical twrp build boot with this fix too?
@infected_ taking no prisoners :')
Beans
infected_ said:
you didnt liked that i stated that you toke screenshots of the recovery flashed on "boot" and not FOTAKernel, and saying to everybody that is working?! yes, i did call you a cheater, because exactly what you did
Click to expand...
Click to collapse
Well, look at the date the commit was made - 26 September. This means I had figured this out a good while before I tried building TWRP 2.8.3.0, because that patch was intially needed for MultiROM TWRP. Hence, your argument is invalid, I didn't even need to "cheat" - why would I want to do that? I just didn't know TWRP had become this big as well and because my ROMs and kernels always include that commit, I hadn't noticed, whereas your build lacked it - you therefore assumed my build was broken and started attacking me. Does it make sense now?
hutilicious said:
Hi, thank you guys for figuring that out. Where is the difference between oliviers twrp build and the official one? Does the offical twrp build boot with this fix too?
Click to expand...
Click to collapse
The difference is that my build works. And no, IIRC the official build has another problem.
The recovery worked on his device because all of the kernels he builds have had that commit included since September. When you provided your logs it pointed to the fact that your kernel also needed it. Is there a language barrier here or something?
Also, Olivier can hardly be blamed because of something Team Win are responsible for.
You're obviously an intelligent person, but this is dragging on too far. Take a breath, realise you made a mistake and move on.
Sent from my C6603
I'll explain it as best I can:
Your first mistake was accusing him of cheating everyone by flashing the recovery.img on boot to get screenshots.
The recovery worked properly on his own device, therefore he obviously didn't need to do that.
You then later tried flashing it with commands that don't work on this device and to a location that doesn't even exist and blamed Olivier when it didn't work.
From this post:
Code:
[email protected]:/ # dd if=/sdcard/twrp-2.8.3.0-yuga.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
21680+0 records in
21680+0 records out
11100160 bytes transferred in 0.690 secs (16087188 bytes/sec)
This device doesn't have a recovery partition. Flashing to that location will have no effect.
Proof:
Code:
[email protected] ~/Desktop $ sudo fastboot flash recovery twrp-2.8.3.0-yuga.img
[sudo] password for infected_:
sending 'recovery' (10840 KB)...
OKAY [ 0.354s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
[email protected] ~/Desktop $ sudo fastboot flash FOTAKernel twrp-2.8.3.0-yuga.img
sending 'FOTAKernel' (10840 KB)...
OKAY [ 0.343s]
writing 'FOTAKernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Desktop $
Those fastboot commands aren't allowed on the yuga.
Edited as I read this back today and it was a bit abrupt. Apologies if it seemed so as that wasn't the intent.
Sent from my C6603
See edits to my post above.
Bye.
Sent from my C6603
Please stop all this useless drama...to get back on this thread's use :angel:
Unfortunetly im still on non booting twrp, i indeed applied that twrp-ify and this one too and using latest bootable recovery from omni repos.
yeah i should have brought logs, but i have to leave again; so will bring some overnight or tomorro. Just wanted to know if i forgot something...i don't fell like to revert all commits to 2.0.8.x versions wich back then was working ok if im not mistaken.
thx =)
Looks like I'm a little late to the party
Nothing to see here it seems.....
(if there's any posts you both want deleted, PM me)
MD
Okay some news: As stated above, it's possible to compress the recovery ramdisk using LZMA to make it fit without using my extract_elf_ramdisk hack. As a result, the ramdisk-recovery.cpio file is now 3.6 MB big (TWRP 2.8.3.0).
I have pushed some commits to the OmniROM gerrit - before merging them, I'd like some of our devs to test and confirm it works.
Link: gerrit.omnirom.org/#/q/topic:fusion3-twrp
Thanks man...will give a go overnight or tomorro...and please, "some of our devs" ? lolz only 5 pple work on fusion3 so far x) hahaha
Will report asap.
ok while using latest bootable recovery repo from omni and your latest changes... (this patch is still applied idk if i must take it off)
facing this issue
Code:
----- Making recovery image ------
----- Made recovery image -------- /data1/sources/validus5/out/target/product/yuga/recovery.img
Install: /data1/sources/validus5/out/target/product/yuga/system/priv-app/Telecom/Telecom.apk
Construct recovery from boot
mkdir -p /data1/sources/validus5/out/target/product/yuga/obj/PACKAGING/recovery_patch_intermediates/
PATH=/data1/sources/validus5/out/host/linux-x86/bin:$PATH /data1/sources/validus5/out/host/linux-x86/bin/imgdiff /data1/sources/validus5/out/target/product/yuga/boot.img /data1/sources/validus5/out/target/product/yuga/recovery.img /data1/sources/validus5/out/target/product/yuga/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
Copying: /data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/services_intermediates/classes-jarjar.jar
Copying: /data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/services_intermediates/emma_out/lib/classes-jarjar.jar
Copying: /data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/services_intermediates/classes.jar
source and target don't have same number of chunks!
source chunks:
chunk 0: type 0 start 0 len 18069
chunk 1: type 2 start 18069 len 16081028
chunk 2: type 0 start 6145090 len 968
chunk 3: type 2 start 6146058 len 9553152
chunk 4: type 0 start 11520489 len 1559
target chunks:
chunk 0: type 0 start 0 len 18069
chunk 1: type 2 start 18069 len 16081028
chunk 2: type 0 start 6145090 len 2825150
make: *** [/data1/sources/validus5/out/target/product/yuga/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Error 1
make: *** Waiting for unfinished jobs....
target Java: ethernet-service (/data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/ethernet-service_intermediates/classes)
DroidDoc took 22 sec. to write docs to /data1/sources/validus5/out/target/common/docs/api-stubs
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol '__system_property_get' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/base_base_gyp_intermediates/base_base_gyp.a(sys_info_android.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libcutils.so
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol 'SkBitmap::lockPixels() const' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/skia_skia_library_gyp_intermediates/skia_skia_library_gyp.a(SkBitmap.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libjnigraphics.so
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol 'SkBitmap::unlockPixels() const' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/skia_skia_library_gyp_intermediates/skia_skia_library_gyp.a(SkBitmap.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libjnigraphics.so
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol 'SkBitmap::notifyPixelsChanged() const' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/skia_skia_library_gyp_intermediates/skia_skia_library_gyp.a(SkBitmap.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libjnigraphics.so
#### make failed to build some targets ####
im using arm-linux-androideabi-4.8 from google with refs/tags/android-5.0.1_r1 and with cm cwm...its going ok
Alx31TLse said:
facing this issue
Click to expand...
Click to collapse
That error (wherever it is, I can't find it) doesn't seem to be related to my commit - TWRP 2.8.3.0 builds for me in CM11, Omin 4.4 and Omni 5.0.
Code:
----- Making recovery image ------
----- Made recovery image -------- /data1/sources/validus5/out/target/product/yuga/recovery.img
Means that it worked (possibly another commit causing the build error).
Olivier said:
That error (wherever it is, I can't find it) doesn't seem to be related to my commit - TWRP 2.8.3.0 builds for me in CM11, Omin 4.4 and Omni 5.0.
Code:
----- Making recovery image ------
----- Made recovery image -------- /data1/sources/validus5/out/target/product/yuga/recovery.img
Means that it worked (possibly another commit causing the build error).
Click to expand...
Click to collapse
Omni 5.0? Did you build it? If it is working mind sharing on XDA please?
Sent from my Xperia Z using XDA Free mobile app
Works fine! Just wondering why that the recovery provided by the official site doesn't work =/
Alx31TLse said:
facing this issue
Click to expand...
Click to collapse
Just got the same error while building SlimLP. It seems like it tries to generate a recovery_from_boot.p file when it shouldn't (TARGET_NO_SEPARATE_RECOVERY is set to true in device/sony/common). This commit should fix it: https://github.com/CyanogenMod/android_build/commit/651987c5f2f78207edebdd821d1700a0464fdfb5
EDIT: This commit doesn't fix it either. Strangely, the build only fails with "bacon" as a target, but not with "bootimage".
Gesendet von meinem Xperia Z mit Tapatalk
Code:
** Disclaimer
I am not responsible if flashing this recovery bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
Recovery Information
Target Devices: Samsung Galaxy Grand Prime SM-G530MU | SM-G530M | SM-G530H | SM-G530FZ | SM-G530P | SM-G530T | SM-G530T1 | SM-G530W
Recovery Status: Stable
Maintainers: [ vince2678 ]
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Bug reports: http://grandprime.ddns.net/bugs/
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530M[/B] - [COLOR="DarkSlateBlue"][B]fortunalteub[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530P/T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
Click to expand...
Click to collapse
Download
Builds:
Code:
[B]SM-G530MU:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-gprimeltezt[/url]
[B]SM-G530M:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-fortunalteub[/url]
[B]SM-G530FZ:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-gprimeltexx[/url]
[B]SM-G530P/T/T1/W:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-gprimelte[/url]
Click to expand...
Click to collapse
Instructions
Installation using Odin
Code:
* [B]Enable Developer Mode on your phone and unlock the bootloader from the
Settings, if not done already. [/B]
* Download a recent [B].tar[/B] archive from the links above for your device.
* Reboot into Download Mode [Press Power+Volume Down+Home].
* Flash the [I][B]tar[/B][/I] archive using ODIN by clicking [I][B]AP[/B][/I] and selecting
the [I][B].tar[/B][/I] file you just downloaded.
Click to expand...
Click to collapse
Changelog
Code:
[B][U]29/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated to 3.1.1-0.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created DevDB project. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Mouse cursor is now hidden from recovery screen.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP now has F2FS filesystem support [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP has USB OTG support integrated for external usb peripherals
(should work for vfat, exfat, ext4 or f2fs-format peripherals).[/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
[LIST]
[*] [B][[COLOR="Red"]ALL[/COLOR]][/B] [B] None. [/B]
[/LIST]
FAQ
Q: Are you taking device requests?
A: If you're willing to buy me/donate the device for testing, sure.
Click to expand...
Click to collapse
XDA:DevDB Information
[UNOFFICIAL][RECOVERY]TWRP 3.1.x for Grand Prime SM-G530M/MU/FZ/P/T/T1/W, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
vince2678
Version Information
Status: Stable
Created 2017-05-15
Last Updated 2017-05-29
Vince at the end update it in variant FZ, well for your work, thank you genius
---------- Post added at 06:01 PM ---------- Previous post was at 05:56 PM ----------
Just a question, the backups that I have made with the j6 version serve me now after updating, Thank you very much for the information
Fz: Aroma packages not work
aurelio.9581 said:
Fz: Aroma packages not work
Click to expand...
Click to collapse
Peak and nano if, problem is in device
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Install rom, backup, root zip
docrates1975 said:
Peak and nano if, problem is in device
Click to expand...
Click to collapse
Nano works for me,only aroma not works
aurelio.9581 said:
Nano works for me,only aroma not works
Click to expand...
Click to collapse
Because putting more garbage on your device, I do not get it
What improvements has the new construction j6?
docrates1975 said:
What improvements has the new construction j6?
Click to expand...
Click to collapse
F2FS, as well as whatever the TWRP 3.1.1-0 comes with (not sure).
vince2678 said:
F2FS, as well as whatever the TWRP 3.1.1-0 comes with (not sure).
Click to expand...
Click to collapse
I already tried, I'm back to building j3 , I commented that it does not start the system from the recovery, directly goes out, and press power twice to start, the first time you press power, it only shows the amount of battery you have, And in the second if you start the system, that's why I went back to building j3.
vince Already corrected in j8 the problem that I comment, Thank you
I tell you, because the j3 is no longer to download
vince, Updated to # 8 or 3.1.1, all good, thanks for your work
Vince, when backing up it is normal to have 2 boxes for system, 2 for data, being 1 external data, 2 system, 1 of start, 2 of cache and this is not the one efc and when making the copy say that external data is included, and since the recovery does not start it only goes off and you have to start from the power button
docrates1975 said:
Vince, when backing up it is normal to have 2 boxes for system, 2 for data, being 1 external data, 2 system, 1 of start, 2 of cache and this is not the one efc and when making the copy say that external data is included, and since the recovery does not start it only goes off and you have to start from the power button
Click to expand...
Click to collapse
Yes, it's completely normal.
vince2678 said:
Yes, it's completely normal.
Click to expand...
Click to collapse
And because the system does not start with recovery? And does not modify the partitions of the mobile when you install a backup with 2 copies of the system, 2 data with the same size? And because there is no option to copy the efs? I think it's an important copy too. And sorry for my maybe silly questions
odin says pass but no twrp recovery
Recovery is not taking, downloaded the right one for my phone which is SM-G530P. ODIN gives a pass but no cigar on the recovery just boot loop, have i missed a step in the process...? Also have root running stock with latest update lolipop, usb debug and bootloader unlocked
kitogh said:
Recovery is not taking, downloaded the right one for my phone which is SM-G530P. ODIN gives a pass but no cigar on the recovery just boot loop, have i missed a step in the process...? Also have root running stock with latest update lolipop, usb debug and bootloader unlocked
Click to expand...
Click to collapse
When installing with odin uncheck the box of auto reboot, And when you say odin pass you remove the battery and start with power button, to see if this works for you
docrates1975 said:
When installing with odin uncheck the box of auto reboot, And when you say odin pass you remove the battery and start with power button, to see if this works for you
Click to expand...
Click to collapse
Took out the battery after pass in Odin, disconnected usb cable reinserted battery and tried button combo for recovery samsung grand prime logo comes up with set warranty bit:recovery in left top corner in yellow and loops until i release button combo... No stock recovery now also but i can boot system and phone works ok no recovery at all.
kitogh said:
Took out the battery after pass in Odin, disconnected usb cable reinserted battery and tried button combo for recovery samsung grand prime logo comes up with set warranty bit:recovery in left top corner in yellow and loops until i release button combo... No stock recovery now also but i can boot system and phone works ok no recovery at all.
Click to expand...
Click to collapse
To ignore the yellow letters, After installing the recovery as I said Start the system and then go to recovery, And must enter by pressing volume more, power and home at the same time Pressing the 3 buttons release when the yellow letters come out, Must install since I did so and with the install lineageos 14.1
docrates1975 said:
To ignore the yellow letters, After installing the recovery as I said Start the system and then go to recovery, And must enter by pressing volume more, power and home at the same time Pressing the 3 buttons release when the yellow letters come out, Must install since I did so and with the install lineageos 14.1
Click to expand...
Click to collapse
OK I'll give it another try...
kitogh said:
OK I'll give it another try...
Click to expand...
Click to collapse
Nope no joy... Tried the recovery for the SM-G530P that's posted on this thread but it will not take to my device which is a sprint phone SM-G530P running lollipop 5.1.1. I also downloaded a twrp recovery from lineage for the grand prime called twrp-3.1.1-0-fortuna3g.img.tar this did take to my phone but I've got no touch or way to control this recovery. What next ? Drop kick it into my neighbors garden... Are these tar files posted here?? Why wont they take to my device and the one from lineageos yes. I might need Sherlock to solve this mystery. If anyone can help out thanks in advance.
DisclaimerThis software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_clt_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working (if it pin/password, pattern fails then try by removing them (password, pin, pattern, fingerprint) from Android before booting to TWRP.
MTP and OTG connection = working
Backup&Restore = working
Note: This was tested only by few P20 Pro owners,so if you test it,please report back!There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_clt_0.1.img - Decryption support (you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk not available for backup./vendor not available for backup (use /vendor_image instead)
Glad to see this. Any chance of sources or a pull request on my device tree to get decryption working?
hum.. it seem that decryption working great.
See :
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
a1Pha said:
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
Click to expand...
Click to collapse
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Pretoriano80 said:
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Click to expand...
Click to collapse
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
a1Pha said:
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
Click to expand...
Click to collapse
Yes, no problem! Also have a look at my Github (pretoriano80). My goal is also to make a fully open source version. ?
Quote: Note: This was tested only by few P20 Pro owners,so if you test it,please report back!
Hi Pretoriano80, Hi All,
Great job ! Just installed... I confirm that it works on my CLT-L29 8.1.0.106(C432)
Internal storage decryption, MTP and usb OTG connection, Backup& Restore (incl /vendor_image) : All working !
Many thanks & Cheers
CLT-L09 (C782) all is working as it should, successful backup and mount of my 1tb hard drive.
Absolutely fantastic work
Thanks :good:
Well this is very positive.
Less than 2 calendar weeks from release to TWRP release.
I think we can possibly have pretty high expectations for development on the P20 Pro.
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
andrewglass3 said:
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
Click to expand...
Click to collapse
You have to unlock bootloader first!
Pretoriano80 said:
You have to unlock bootloader first!
Click to expand...
Click to collapse
Yep - I forgot that step - had the code but missed it out lol - Im an idiot lol
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
Have you made sure that the Google Pay app is selected in the Magisk Hide list in the app? It doesn't tick automatically like it used to with Android Pay. You should pass safetynet with Magisk installed. Also, after flashing TWRP still passes safetynet too.
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
TWRP has nothing to do with SafetyNet! Maybe you installed a firmware which didn't passed Google check yet.
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
m00h said:
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
Click to expand...
Click to collapse
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
DJBhardwaj said:
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
Click to expand...
Click to collapse
I did on the other TWRP thread, worked fine.
The page for getting an unlock code seems to 404 for me. Is this happening for anyone else too?
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage OS is available in the LineageOS Github repo. And if you would like to contribute to Lineage OS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
NOTE: This build is unofficial, don't report bugs to the official LineageOS bug tracker.
HOW TO FLASH
Download the ROM from here
Download GAPPS from here
Install TWRP recovery from this thread
Boot to recovery
Wipe Data/Factory reset
Flash LineageOS
Flash GAPPS
Wipe Cache/Dalvik
Boot to system
What works
Audio
Camera
RIL (calls, sms, etc)
GPS
Bluetooth
WiFi
Everything else not listed below
What doesn't work
HDR
WiFi Hotspot
Wireless display
Before asking any question read the FAQ below
Big thanks to @voidzero for letting me use his server to build and for the initial device tree
XDA:DevDB Information
[ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s, ROM for the HTC One (M8)
Contributors
root-expert, voidzero
Source Code: https://github.com/M8s-dev/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M firmware base
Version Information
Status: Stable
Beta Release Date: 2018-06-18
Created 2018-06-18
Last Updated 2018-10-27
Changelog
Code:
[B][U]26 October 2018[/U][/B]
* Instagram videos fixed
Code:
[B][U]18 October 2018[/U][/B]
* August/September/October ASB merged
* Use sdFAT instead of exFAT
* Reduce GPS fix time
* Increased speaker volume
* Increased microphone volume
* Increased upper earpiece volume when in-call
* Enabled HDR
* Fixed wakelock
Code:
[B][U]26 July 2018[/U][/B]
* July Android Security updates
* Kernel updated from tag 3.10.49 to tag 3.10.108
* Bluetooth now recognises the correct bt address
* Use low-latency as primary output for notifications and ringtone
* Switched SELinux to enforcing
* When usb composition is on "charge only" adb works
* Enabled audio offloading
* Added the option to disable Double Tap to wake gesture
* Added option to unlock phone with a gesture (you can find it under gestures tab)
* Used newer WiFi configuration files (hope that fixes WiFi problems)
* The name "HTC One M8s" is shown to your pc when connected instead of "Android Phone"
Code:
[B][U]20 June 2018[/U][/B]
[LIST]
[*]Fixed headphones microphone
[/LIST]
Code:
[B][U]18 June 2018[/U][/B]
[LIST]
[*]Initial commit
[/LIST]
Frequently Asked Questions (FAQ)
Q: I flashed the ROM and I'm getting random reboots and crashes
A: Ensure that before flashing this ROM your last stock rom was Android version 6.0. If not follow the instructions on the post below
Q: I found a bug, what should I do?
A: Describe in this thread the issue as best as you can and include steps to reproduce.
Also include a logcat taken the time that the bug happens.
If you had a random reboot don't bother taking a logcat instead pull /sys/fs/pstore/console-ramoops file and atach it to your post.
Q: I want to root this ROM. Should I flash something?
A: Either download su addon from https://download.lineageos.org/extras or flash Magisk.
If you are coming from CM12.1 (Just like I did) then follow these steps
NOTE: If you do not follow these steps, your final Oreo ROM (LOS 15) will crash, you'll suffer randoms reboots and instability problems due to incompatible radio / HTC firmware. This whole update process to Stock 6.0 can take up to 4 hours! So make sure you have the time to do everything correctly, don't cut corners.
I suffered
1. Create a full backup of your ROM using TWRP (v2.8 or v3.0.2.0), Copy your INTERNAL STORAGE and SD Card contents to PC .
During the upgrade from "CM12.1 > 5.0.1 Stock > 6 Stock > LOS 15" you WILL lose your internal data! (because of bootloader relock & unlock again)
2. Relock your bootloader; (Make sure you are using the htc_fastboot.exe)
Turn off phone
Go into bootloader (Hold down VOL DOWN+Power button
Connect USB and enter Fastboot (Should show as FASTBOOT USB)
Open commandprompt;
Code:
htc_fastboot oem lock
The phone should restart and show up as ***RELOCKED***
3. Get your matching RUU from https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If you dont know which RUU to get, follow this thread; https://forum.xda-developers.com/ht...lp-thread-htc-one-m8s-to-stock-howto-t3190238 (M8sQL_UL > Firmware (Expert)>Firmware Crypted (Original HTC))
If you get the "Device halted due to Large Image update fail" error during installation, just try another RUU - but make sure it matches your CID.
I got it working using a "signed" version. The "combined-signed" version did not work for me. Your mileage may very.
Click to expand...
Click to collapse
4. In Android Stock (5.0.1), continue the setup and after that go to: Settings > Software updates (At the bottom) > Check for updates
At first I only got 2 APP updates: "HTC Sense" and some other app (cant remember). Update both apps and reboot.
After a reboot check again for updates. Now you get a ~400Mb update. Download and install.
After the first update check again for updates. Now you get a ~1.23Gb update (Update to Marshmallow, Part 1 of 2). Download and install.
After that check again, and now you'll get a ~700Mb update (Update to Marshmallow, Part 2 of 2.)
That's it for going back to the most recent stock version. You now have Android 6.0 Stock running.
To install TWRP (if you want to flash LOS 15)
1. Unlock your bootloader again.
Go to https://www.htcdev.com/bootloader/ and follow the instructions.
2. Flash TWRP.
Code:
htc_fastboot flash recovery twrp-recovery-image-name-and-version.img
After that:
Wipe Cache/Dalvik, Data and System
Install LOS15
Wipe Dalvik again
Flash Gapps
Wipe Dalvik
Boot
Say thank you to @root-expert for keeping this phone alive with the development and @voidzero for providing the build-environment / mirrors
- Jeroen
Nice job! Great work on the rom and keeping the one m8s alive!
New build up!
Headphones microphone is now fixed.
Grab it as usual from here
-Chris
For the users who want to remove the"root icon" ( the status bar), there is no setting to disable it.
{
"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"
}
To remove it:
Connect your M8s to PC with USB
Open CMD
Code:
adb shell settings get secure icon_blacklist
The output is:
Code:
[COLOR="Red"]rotate,headset[/COLOR]
Now enter the output + su
Code:
adb shell settings put secure icon_blacklist rotate,headset,[COLOR="red"]su[/COLOR]
And after that:
Code:
adb reboot
Now the "#" icon is gone from the status bar.
- Jeroen
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
brunkonjaa said:
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
Click to expand...
Click to collapse
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
root-expert said:
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
Click to expand...
Click to collapse
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
brunkonjaa said:
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
Click to expand...
Click to collapse
I don't believe you have to do that. The only requirement is that your last stock android version was Android 6.0
Post battery statistics here
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
GeoEgbA said:
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
Click to expand...
Click to collapse
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Problem with google play services
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
Click to expand...
Click to collapse
View attachment recovery.log
Try by twrp-3.0.2-0-m8ql.img
View attachment twrp-3.0.2-0-m8ql.zip
GeoEgbA said:
View attachment 4533829
Try by twrp-3.0.2-0-m8ql.img
View attachment 4533830
Click to expand...
Click to collapse
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
monkyMatys said:
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
Click to expand...
Click to collapse
Hello,
Ensure that you flashed GAPPS straight after flashing the ROM WITHOUT rebooting to system. If you reboot to system and then flash GAPPS you'll have problem and crashes like you do. Also ensure that your previous stock andorid version was android 6.0. If not follow the instructions on this thread to revert back to stock and then try to flash the ROM
-Chris
root-expert said:
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
Click to expand...
Click to collapse
Yes yes that why i wrote that need 3.2.1..0 becouse on 3.0.2.0 get error 7. I flash 3.2.1.0 anf LOS and work great for 15h now sorry for confusion
How long should the first boot take? i followed the instructions, twrp 3.2.1 gave a /persist error but everything else seemed fine. its been 20m and im at the lineage os boot screen.
Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Removed a ton of tracers
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Voice Changer
Chinese Alpha Launcher
High-end icon animations
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
Mirror app doesn't work.
You tell me.
FIXES:
Reverted the MiuiAod for more stability
Added the Backup app back
Added the Mi Sound app back.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: https://t.me/LiteEDevelopmentGroup
Channel: https://t.me/LiteEDevelopmentChannel
Changelog:
- 1.3:
Working Mi Dialer with call recorder
New charging animation
Deodexed
Fixed flasher issue
I forgot
- 1.2.5:
Changelog in telegram
- 1.2:
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Chinese Alpha Launcher
High-end icon animations
- 1.1:
Never published on XDA
Added the vbmeta patcher in flasher script (this fixes that cannot boot into userspace error)
Changed boot sound and boot animation from Redmi Note 9T
MIUI Launcher Mod by Sipollo (removed)
High-end icon animations
Chinese version of Search (removed)
App Vault from MIUI 13 (removed)
Uses the chinese version of Mi Calendar (removed)
- 1.0:
Initial release
Wow nice., Hoping for more upcoming custom rom for our handset. Thanks
J6idot said:
Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
Removed a ton of tracers
More colorful bootanimation
Uses the chinese variant of File Explorer, Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Custom MiuiAod with "always on" function
Voice Changer
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
I have no idea how to test the Voice Changer function. Could anyone try this?
You tell me.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: not yet
Channel: https://t.me/LiteEDevelopmentChannel
Click to expand...
Click to collapse
big big work
Wow, Great work. Thanks. But is genome karnel stable?
Awesome work, might try it later
IamAlaminislam said:
Wow, Great work. Thanks. But is genome karnel stable?
Click to expand...
Click to collapse
yep
I can't seem to find the telegram channel for the genome karnel. Want to know the change log..
Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.
GildroY said:
Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.
Click to expand...
Click to collapse
why not? rom works perfectly fine
J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Thanks. Will try it out tonight
J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?
GildroY said:
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?
Click to expand...
Click to collapse
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Will try again tonight post work. Many thanks.
J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Worked like a charm!!
Thanks a ton.
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer
J6idot said:
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer
Click to expand...
Click to collapse
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)
angel495 said:
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)
Click to expand...
Click to collapse
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
Can you get advise about make a change for in system and vendor folder (its write protect)... I am try edit a build.prop file, but then i save changes file just gone and i need make a reflash.
angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
For call recording you can use axet's call recorder. It's available on fdroid and is working fine so far, for me, with this rom.