Related
February 4: Rom updated to include February security patches.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16643
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
January 14. Rom updated to include Google's January 2016 security patches. Also, selinux not only disabled, but completely removed: the rom compiled without selinux sources/binaries.
Kernel does NOT include recovery, so use TWRP for Fota/Recovery partition.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16217
_________________________________________________________________________________
For those who prefer to stick to bugless kitkat: Rom updated to include all "shields up" features including cleaning creepy Ips and dns defaults. Compiled just a few days ago.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13001
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is Slimkat 10 unofficial built from sources on March 2. Built using JDK-7, which turned out to be beneficial for the rom. Slim, fast, smooth and stable. For those of you who have been using Lollipop for a while, you will see how much faster, smoother and more stable kitkat is. Everything works: no reboots, no freezing, no overheating, no screen light flickering, no video recording/play problems, great battery life and abundance of features. This taken together with improved security makes a pretty darn good rom. I tried it and got rid of Lollipop.
Changes:
1. New Iptables binaries which allow to stop kernel communicating (if used with Afwall) with Google home.
2. Changes in Vold to enable 256 bit AES encryption, as opposed to default 128 bit
3. Key length increased for multiple keys
3. Kernel with disabled Selinux and enabled Tomoyo together with all ciphers/hushes/digests/random number generation tools
4. Latest changes from Google code (I was surprised finding changes pushed for kitkat while synching Google source)
5. TWRP 2.8.x integrated in boot image
Install:
1. Be on Kitkat, rooted with recovery
2. Enter recovery and wipe Cache/System/Data
3. Flash the rom and reboot
4. Enjoy and say thank you or perhaps donate
Rom is in Download section above
Credit: Slimroms
Warning: I am not responsible for your device exploding and killing everybody around. You are on your own. :laugh:
Source: https://github.com/SlimRoms/platform_manifest/tree/kk4.4-caf
Source with changes: https://github.com/HonamiZ1
XDA:DevDB Information
Slimkat 10 Final Edition, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2015-03-02
Created 2015-03-03
Last Updated 2016-02-04
Reserved
Believe me I have no interest in being in any of "your threads" {That's why I'm editing this post instead of posting a new one xD},
I'll leave this thread from any further discussion.... for now at least
Regards,
Omar.
OmarEinea said:
Cool, can you give us changelog of what's new between build 9.0 and build 10?
cuz latest kk build by Slim Team is 9.0 : https://github.com/SlimRoms/vendor_slim/blob/kk4.4/config/common.mk#L154
so you must have made some major changes to call it build 10, right?
Regards,
Omar.
Click to expand...
Click to collapse
Thanks. Reading the OP might help...
" you didn't get my point, did you!!"
Oh, I did get your point alright. :fingers-crossed:
Could you please do me a favor? Kindly stay away from my threads. If you feel that you need to continue to report me, that's your right, but again, stay away from my threads.
Best regards
Gonna give this a try as sounds like Kk on steroids well stable steroids.....LP still too buggy for me.
I tried it. But play store doesn't work. What is the problem...?
Rom Updated
See OP for description and download link...
thanks
the best option is in that forum for the Z1 now
First download
Thanks for all your awesome roms
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Xecu said:
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Click to expand...
Click to collapse
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
optimumpro said:
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
Click to expand...
Click to collapse
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Xecu said:
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Click to expand...
Click to collapse
Xperias don't have recovery partition. Fota is used by stock firmware only, so it is available in custom roms, hence recovery image could be installed there. However, the normal way for custom roms is to incorporate recovery into boot image, which is faster. This was until lollipop, when the not so smart folks at Cyanogen, gave up on CWM (which was always in boot image) and came up with their own recovery. CM recovery does not work, so TWRP guys figured out a way to install their recovery in Fota, instead of having users/developers decompiling boot image, replacing CM recovery with TWRP and recompiling the image again. That's what I do in CM based kernels, but Slimrom folks use TWRP in boot by default.
So, when you did fastboot erase recovery, you got rid of recovery in fota partition. Now, you have TWRP in boot image.
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Running this Rom, these issues are gone. I am again at 2 days runtime and I can finally write longer messages without beeing bothered by an unresponsive screen. The system feels reliable again.
Only issue i found so far, is that my headphones are sometimes not recognized. In these cases, I have to unplug and plug them in again until the system recognizes them. I had the same issue when I was on KitSlim_AMG, but not on stock. So this might be a bug in the SlimBean / CM Code-Base.
Xecu said:
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Click to expand...
Click to collapse
You are forgetting the heat issue, which requires RECALL. I am not a huge gamer, but CPU can easily get to 75-80 degrees after using Firefox/Fennec for about 10 minutes. Then flickering and other heat protection kick in. Note, that most users won't notice overheat, because glass is not a very good heat conduit. They just complain of backlight flickering. However, if you enable CPU stats in developer options, you can see the temperature on screen. This is a shame (overheating), especially that LP has been around for about 7 months to no avail. You can't blame the processor, since there is no heat issue on kitkat and jb.
Lollipop, in my view, is the worst ever android version: linux (which is great) + google poop (google does what it does best) = lollipop. Really, the name should be Lollipoop.
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Xecu said:
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Click to expand...
Click to collapse
Logging is disabled in kernel for security. You can get a few apps on f-droid for logcat...
New build
Rom updated to include January 2016 security patches. See OP for download and description.
optimumpro said:
Rom updated to include January 2016 security patches. See OP for download and description.
Click to expand...
Click to collapse
Thank you for continuing to support KitKat I'll try the new build tomorrow
So the boot image doesn't have a kernel? Do I have to fastboot flash recovery recovery.img if I don't have the bootloader update?
Hello everyone! Just want to share this little gem I've put together.
So as some of you might know, CM13 and other ROMs based on it do not yet support the new LCD on OPPO Find 7s (R63419). I use to have the first version of the panel, but got drunk one night and cracked the screen. Bought a new one and suprise suprise, everything looked messed up as I was running CM. I didn't want to start over so I put this build together using latest CM13 nightly + Pojiku's patched kernel.
WHAT IS IT?
- It is the latest nightly (will try to update) with already patched kernel for LVM + NEW LCD from Pojiku (his thread here: http://forum.xda-developers.com/find-7/orig-development/rom-cyanogenmod-nameless-builds-lcd-t3327530)
WHAT WORKS:
- New LCD
- Supports LVM (Wuxianlin LVM patch)
- Sound works on this version (didn't work on latest version from Pojiku)
- Gestures (Circle for camera, V for flashlight, double tap to wake)
- Actually, everything works except 4K video recording
This build IS EXPERIMENTAL! ALWAYS BACKUP!
If you want GAPPS, I'm using OPENGAPPS's pico version. I think you need to fully boot once, then install GAPPS, then boot again. I'm not sure exactly as I'm coming from CM12 dirty flash. Did a system install, first boot + setup, then restore data partition.
PLEASE NOTE: You might need to change permissions for the Google SetupWizard in Settings! Go into Settings -> Apps -> SetupWizard and grant all permissions. OR else gapps might not work!
You need to be unified by flashing ColorOS 2.1.5 using Alexander Tashi's method.
Please use this recovery (UNIFIED TWRP 3.0.0: https://drive.google.com/open?id=0B0IQuS71Z8k2WmVnTGVrdFJTZVU)
Please use this script if UNIFY don't work: https://drive.google.com/open?id=0B0IQuS71Z8k2eXVXNlMtSU9wNGc
DOWNLOAD
Latest version: cm-13.0-20160402-NIGHTLY-find7
Link : https://drive.google.com/open?id=0B0IQuS71Z8k2Q3dCMFhFdlp1amM
Hi, this works perfect for me! Thank you man, and thanks also to Wuxianlin and Pojiku. You got it, works fine, everything. Only one bsod at first start, no more bugs.
I will try the rom for a week, if its stable sure i'll use it as daily rom.
Thanks again for your job
Cheers
I will try soon when I have time.
Hope this ROM keep update.
Thank you very much.
sugarsweetcandy said:
Hello everyone! Just want to share this little gem I've put together.
So as some of you might know, CM13 and other ROMs based on it do not yet support the new LCD on OPPO Find 7s (R63419). I use to have the first version of the panel, but got drunk one night and cracked the screen. Bought a new one and suprise suprise, everything looked messed up as I was running CM. I didn't want to start over so I put this build together using latest CM13 nightly + Pojiku's patched kernel.
WHAT IS IT?
- It is the latest nightly (will try to update) with already patched kernel for LVM + NEW LCD from Pojiku (his thread here: http://forum.xda-developers.com/find-7/orig-development/rom-cyanogenmod-nameless-builds-lcd-t3327530)
WHAT WORKS:
- New LCD
- Supports LVM (Wuxianlin LVM patch)
- Sound works on this version (didn't work on latest version from Pojiku)
- Gestures (Circle for camera, V for flashlight, double tap to wake)
- Actually, everything works except 4K video recording
This build is stable for me, BUT IT IS EXPERIMENTAL! ALWAYS BACKUP! Battery life is good, no crashes after a modest amount of testing.
If you want GAPPS, I'm using OPENGAPPS's pico version. I think you need to fully boot once, then install GAPPS, then boot again. I'm not sure exactly as I'm coming from CM12 dirty flash. Did a system install, first boot + setup, then restore data partition.
DOWNLOAD
Latest version: cm-13.0-20160402-NIGHTLY-find7
Link : https://drive.google.com/open?id=0B0IQuS71Z8k2Q3dCMFhFdlp1amM
Let me know if it works for you
Click to expand...
Click to collapse
Hi, I have tried flashing this and every now and then after locking the screen, it does not show up.
EDIT: It happens when you turn on Ambient Display
Many thanks.
I'm going to try this immediatly.
I hope you will continue to update and if no, it will be great if you can explain how did you do to make that possible like that we souhld continu the work.
Thanks again and hope you'll continue.
Have a nice day.
I don't know if i did something wrong . I m familiar with flashing etc... I flashed the rom(clean install. full wipe) 3 times and i always have the same issue. when i open the file explorer integrated in the rom, i can see my external sd and can open it but there is no internal storage listed. I tried with sd maid (explorer) and same, no inernal storage listed. when i go in system settings under storage, i see the internal storage (i'm on lvm) and i see 2 sd cards : one wich is corrupted and a second which is my external sd and i can open it. when i plug the phone to my pc, i see only my external sd card partition (iternal storage doesn't appear) and when i click on it my data are not visible. it seems to be empty but in reality no. In TWRP the phone plugged to the pc, i can see internal and external storage and all data are there.
I will try another time maybe i will find the problem.
I had similar issue. Try going to settings in file manager and then to storage settings I think, and enable root access mode. Worked for me. However I have installed the arm 6.0 pico gapps and just get everything crashing (google services, etc) so I'm not sure what I'm doing wrong.
I stand corrected.......I see what you mean now. Thought I actually had valuable input but spoke too soon lol. Can't download anything now due to "no sdcard" issue ;(
ok i have some news.
I think lvm is not supported. Let me explain.
The 3 first times, i maked a full wipe, flashed lvm setup package, flashed the rom and open gapps (tried stock and nano) and after the reboot and setup, issues i've related appears.
I've decided to read a new time the op and my english is not very good. So i've read : "...already patched kernel for LVM...". I've decided to make a new clean install but this time without flashing the lvm setup. after a reboot and setup, all is good but i have the 2 partitions. once for install app (2.93go), and once for data. Clearly no lvm.
Please sugarsweetcandy, give us new build with complete lvm compatibility as quickly as you can.
Thanks for your work.
p.s : i read on oppo forum a comment saying that this build is not for x9076. is that right. I hope no because my find 7s is a x9076 model
---------- Post added at 03:50 AM ---------- Previous post was at 03:44 AM ----------
thecell_2007 said:
I had similar issue. Try going to settings in file manager and then to storage settings I think, and enable root access mode. Worked for me. However I have installed the arm 6.0 pico gapps and just get everything crashing (google services, etc) so I'm not sure what I'm doing wrong.
I stand corrected.......I see what you mean now. Thought I actually had valuable input but spoke too soon lol. Can't download anything now due to "no sdcard" issue ;(
Click to expand...
Click to collapse
Thank you for your help thecell. I've already did this but it did'nt work for me. the internal storafe doen t appear if i flash lvm setup package.
For your problem, i figure that you've followed the installation instructions on op. Maybe i'm wrong but i think you flashed the rom and reboot then setup and reboot to recovery then flashed gapps....
when i did the this manipulation i had the same issue.
So what you have to do is in twrp : select all packages you want to flash (rom, gapps, supersu, hal mod, xposed....) and reboot then setup, reboot system and all will done
.
I am not too sure what's causing problems with LVM. I actually have unified chinese method, and this is what I get: i.imgur.com/34KSCBP.jpg
Although there seems to be a "corrupted" SD card, everything works and I can download correctly. I will try looking into it!
sugarsweetcandy said:
I am not too sure what's causing problems with LVM. I actually have unified chinese method, and this is what I get: i.imgur.com/34KSCBP.jpg
Although there seems to be a "corrupted" SD card, everything works and I can download correctly. I will try looking into it!
Click to expand...
Click to collapse
Thanks for your response.
I have exactly what you have when i flash "setuplvm_find7_FULL_WIPE_09012014.zip" (http://forum.xda-developers.com/showpost.php?p=55187001&postcount=558). but in the file explorer my sdcard 0 doesn't appear. I tried with flashing the wuxianlin lvm patch for cm 13 and then i have no the corrupted issue that we can see in your screen but my internal storage doesn't show 25go it shows 2.93go only and the 22go doesn't appear. i didn't sleep all the night testing many methods lol. I will try a last time flashing this "twrp_find7_lvm_09012014.img" (http://forum.xda-developers.com/showpost.php?p=55187001&postcount=558). Maybe there will be in this twrp versio some option for lvm.
Thanks for your invest. I and many find 7 owners i think are waiting for this since a long time. I really want to own this rom. Please bring us some great news. Of course you have a life and we will be patients.
thanks again
I'm on x9077 so it might be different for you, but my install pattern went like this:
1. Was using CM12 fine with old LCD.
2. Did full backup, unified with Chinese ColorOS install method (see CM thread on OPPO forum), and then restored data
2. Broke screen, installed new LCD, and then CM12 didn't work anymore.
3. Did a full backup, wiped everything, installed CM13 + pico apps
4. Booted and did setup.
NOTE: You might need to change permissions for the Google Setupwizard in Settings. Go into Settings -> Apps -> SetupWizard and grant all permissions
5. Some apps will need reinstalling because they will have wrong permissions.
Hope this helps!
CM13 20160406 snapshot is release.
is this version support new X9077 LCD ?
zw963 said:
CM13 20160406 snapshot is release.
is this version support new X9077 LCD ?
Click to expand...
Click to collapse
Yes, the new LCD is supported!
proazy said:
Yes, the new LCD is supported!
Click to expand...
Click to collapse
I tried the CM13 20160406 snapshot from cyanogen official downloads, in my x9076 with panel r63419 and not works, blanck screen, the same ever
roi_xordo said:
I tried the CM13 20160406 snapshot from cyanogen official downloads, in my x9076 with panel r63419 and not works, blanck screen, the same ever
Click to expand...
Click to collapse
Try the one that is mentioned in this thread, it works for me! The official ones are not supported.
Cm13 20160406 nightly
proazy said:
Yes, the new LCD is supported!
Click to expand...
Click to collapse
I tried the CM13 20160406 NIGHTLY in my x9076 with panel r63419 it not works...
Keukul said:
I tried the CM13 20160406 NIGHTLY in my x9076 with panel r63419 it not works...
Click to expand...
Click to collapse
Me too, X9077, when start up, panel is keep black, not work.
this hacked version is work fine for me for now.
I am in the process of redownloading sources and updating to ROM to latest. I lost everything!
Thanks for merging LVM into CM13, I switched today from Nameless and unified storage works for me, however I'm experiencing a lot of random reboots during the day. Is there any log I can catch, so you can help me identify the source? Thx (also posting this on OPPO forums).
I am an oppo find 7 user, if I flash this rom will vocc fast charge works in my oppo. Pls let me.know
Thread update 15.04.2022, fixed some links, removed others, added RR 5.8.8 and did some formatting.
So since there were many users who had questions for roms,root,firmware and stuff like that which was already available but only in small posts,I finally decided to make a big official thread for the HTC Desire 310 and 320. Why 1 thread for 2 phones? Well,they are practically the same phone but desire 320 is running on stock kitkat and has flash.
Port guys and developers: @MaRtYy01 aka Martin Dimitrov @HTC Desire 310 aka 69techur aka Alija Huskic (Team N3GG3)
@Swoopae (deserves to be here lel) and users in 4PDA Desire 310 and 320 threads
New facebook group (tnx Swoopae) click
1.ROOTFlashable SuperSU zip: in firmware flashing video
<Moderator Edit>: Files removed due to 15 different antivirus services detecting the APKs as Trojans.
2.RECOVERIES
Spoiler: For firmware 4.2.2 only
Recommended-CWM 5(you dont need anything else,everything on 4.2.2 can be flashed with it): click
CWM 6 click
TWRP click
Stock recovery(if something messes up with other recovery and you get into bootloop flash it with sp flash tools) click
OTA - for android 4.2.2 click
Steps:
1.Put the OTA (named as update.zip) and the CWM on your SDCard
2.Reboot to Recovery (Volume UP + Power)
3.Select "apply update from sdcard"
4.Choose our update.zip (OTA)
5.It will return an error(if it doesnt then you should flash the stock rom with sp flash tools)(as our device is already updated) and it will let you choose two options. SELECT REBOOT SYSTEM NOW
6.After the phone is fully booted up, proceed to install the recovery as you wish!!!RENAME THE RECOVERY TO RECOVERY.IMG OR YOU WILL END IN BOOTLOOP!!!(You can use Rashr or MobileUncle MTK Tools or whatever you want)
7.After install, reboot to recovery
4.4.2+These don't work if you are with the jellybean firmware(kernel 3.4.5), only for desire 320 firmware. Required to flash roms with version higher than 4.2.2
- Philz Touch click in this archive you have all stuff required for the rooting and installing the recovery on the d320 kitkat rom. Password is amogus
- Philz Touch mirror link without any other stuff coming with it: click mirror
- Flash the OTA click mirror with the stock recovery and reboot, go to mobile uncle tools and flash the recovery (new recovery.img)
btw OTA for android 4.4.2 is different from the jellybean one
3.ROMS
Spoiler: 4.2.2
These roms are usually bugless or with minor bugs that dont interrupt the work. All ported from 4PDA users
XPERIA C click (sometimes gives errors while installing apps)
Lenovo(vibe ui) click
MIUI 5 click (one of the best 4.2.2 roms)
Lollifox click
Moonmod click
CyanogenMod 10.1 click (google play doesnt work)
4.4.2/4.4.4
WARNING:YOU NEED THE DESIRE 320 FIRMWARE TO FLASH ROMS WITH NEWER VERSION THAN 4.2.2
[07.11.2016]MIUI 8 click (bugless) [ported by @Swoopae]
Spoiler: 5.1.1
[01.11.2016] AICP 10 click
gapps(for AICP only) click [ported by @MilkyPL]
[26.8.2016]CyanogenMod 12.1 click bugfixed version by @Swoopae
Flyme OS 4.5 link in kk firmware flashing video (google play doesnt work,I will try to fix it soon;gapps built in) [ported by me]
Spoiler: 6.0.1
Not 100% of the roms are well tested, so have a working rom as backup in case the rom you try doesnt work properly, also report back if you experience this.
IMPORTANT-If you own desire 320 flash this patch right after the rom or you will face wifi issue-click
Its made for marshmallow roms,so work for lollipop and kitkat isnt guaranteed. Tbh it doesn't always work on marshmallow too lmao
For mounting the sdcard as internal storage,here is @Swoopae 's patch click
It's made for cm13 but will probably work on other marshmallow roms too.
[14.11.2016]Mokee 3 click (bugless,vpn also works,just 2g switch bugged) [ported by @Swoopae]
[01.11.2016]AICP 11 click (gotta be almost bugless as all new mm based roms) [ported by @MilkyPL ]
[12.10.2016]TemastekPLUS click (improved and tweaked temastek cm13,bugless,vpn also should work) [ported by @Swoopae]
[02.10.2016]SwoopaeOS r01 click (based on slim6,fixed lag and minor bugs plus a sexy theme) [yes its by @Swoopae]
[04.9.2016]Paranoid Android 6.0.3(aospa) click (vpn and audio from headphones doesnt work) [ported by @Swoopae]
[17.8.2016]CyanogenMod 13 click ( very stable, gps, google play work,just fm radio doesnt work) [ported by @Swoopae]
[15.8.2016]Slim Marshmallow click (everything except fm radio works) [ported by @Swoopae]
7.1.2|27.09.2017| Resurrection Remix N 5.8.4 by Swoopae: click
(should work well,needs some testing)
|15.04.2022| Resurrection Remix N 5.8.8 by me: post download
Steps:
1.Make sure the rom is on the sdcard
2.If you wish you can make a backup of your current rom
3.Wipe cache,data,system;dont mount anything/wipe for a new rom on philz recovery
4.Select update from sdcard/zip from sdcard/whatever is it from sdcard
5.Choose the rom zip and flash it
6.Flash gapps if the rom requires it(pico gapps are strongly recommended)
7.Reboot,first boot takes 3-8 minutes depending on the rom
GAPPS: http://opengapps.org/
Choose arm - whatever android version rom you are flashing - pico are recommended,if you have problems with gapps try with pico,flashing after rom and after 1 boot and then report if still doesnt work
4.Firmwares
- Have any problems with the gps? Try this: click and this: click
- Desire 310 stock roms:
single sim: click mirror mirror 2
dual sim: click mirror
- Desire 320 stock rom(works for both d310 single and dualsim): click ; When installed on desire 310 bugs of that firmware are little while line on top of the screen and auto rotation(screen flickering too but doesn't happen on 5.0+ roms)
- SP Flash tools: click
- Driver: click
- Fix for driver signature error on windows 8/8.1: click
- Stuff for fixing imei(including toolhero): click mirror
- If you don't want to flash the desire 320 firmware and just want to unbrick this tutorial will be more helpful(also works if you have desire 320 and want to unbrick): click
HTC Desire 310 aka 69techur reported that Lenovo A328 firmware also works without flickering on and white line,but volume buttons,camera,rotation and a lot of other things dont work.
- Instructions for flashing D320 firmware on D310:
1.Backup imei with toolhero on 4.2.2
2.Install the driver on the pc,if it cant install them because they arent signed-disable signature verification(test mode) or try on other pc
3.Run the sp flash tool with compatiblity mode windows 7(only if you are on newer os) and set everything on it like in the video, connect the phone to the pc without battery and holding volume down;da dl with cheksum,high speed,no battery in the options,select firmware upgrade and start to flash
4.Root with the pc software,make sure you have enabled usb debugging in developer settings
5.Flash the OTA with the stock recovery and reboot, go to mobile uncle tools and flash the recovery(new recovery.img)
5.Now you have recovery.Wipe system,data and cache and flash the rom you wanna flash(the 4.2.2 roms dont work anymore) after that flash gapps if the rom requires it and reboot.
KERNEL BUGS:Screen flickering(kitkat roms only),screen rotation,little white line on the top of the screen
5.YOUTUBE
Kitkat firmware,recovery and roms installation: click
CyanogenMod 13: click
How to fix imei: click
CyanogenMod 12.1: click
CyanogenMod 10.1: click
MIUI 5: click
Galaxy S5 mod: click
The HTC Desire 320 rom: click
AICP 6.0.1: click
CyanPOP 5.1.1: click
CleanKat 4.4.4: click
Wanna port a rom on your own? Here is a video guide for android 5 and 6: click
and written tutorial: click
Credits:
-The users of 4PDA for all 4.2.2 roms and all recoveries, cm12.1, guides, etc.
-Me for translating the guides, youtube videos and ported roms
-HTC Desire 310 aka 69techur for helping me test stuff, his porting tutorial, ported roms and youtube videos
-Swoopae and Tomi Sudi for ported roms
-other guys that I havent mentioned
If you have questions, reports about bugs, requests or something feel free to ask.
Don't forget to hit thanks
Nice thread
#Proud_To_Be_Team_N33G3!
Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?
Immortel.CZ said:
Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?
Click to expand...
Click to collapse
in 5.x.x roms flash rom, boot, then flash
in 6.0.1 roms flash rom and then flash gapps
Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes
Immortel.CZ said:
Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes
Click to expand...
Click to collapse
Broken os is for the 4.4.2 firmware (kernel 3.4.67),not the stock 4.2.2(kernel 3.4.5) .You need to flash the d320 firmware first,get philz recovery on it then flash the rom and the gapps.
And here my explanation:
7b) I will add that later in the firmware section
9 ''(You can use Rashr or MobileUncle MTK Tools or whatever you want)'' Rashr is in the google play
11.-14. Well,I guess I will have to add instructions how to flash roms
BTW The kitkat firmware installation+installation of recovery and roms video is complete gotta upload today
Edit:video uploaded https://www.youtube.com/watch?v=QRpw5sQA0rs
and thread finished
Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
Last two bugs above (GPS and data) still occuring but not every time. Looks like switch is bugged.
EDIT: Did full wipe, format SD, reflashed G5 mod and now works without those bugs. Probably my fault flash. Yay!
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too
Immortel.CZ said:
Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too
Click to expand...
Click to collapse
I would recommend you broken os over cm13,I havent updated it from a month(since I currently dont have the phone to test it) and broken os is super stable and almost bugless.
BTW if you have the 512mb ram version,I highly recommend the s6 mod or cleankat(69techur still hasnt uploaded it tho,lazy bastard XD).Kitkat uses less ram and its faster.I actually think that cleankat must be the fastest rom after all.
For the s5 mod:
-Keyboard works by default,just swipe the status bar and choose aoso keyboard
-Weird,dialer worked fine for me.And its not for s5 after all,the dialer looks like jellybean touchwiz,not kitkat,probably ported from s4/s5 chinese clone.
-The unlock screen looks like that because of the navigation bar,if you remove it(find qemu.hw.mainkeys=0 in the build.prop and change it to qemu.hw.mainkeys=1) and add pie controls instead,it will be fine.
-The pop up about the back cover aoso appears in the original s5,but this isnt real touchwiz rom so I suggest you not to touch it/backup the rom and try to remove it.
-Idk,probably sh1tty touchscreen,I think I faced the same issue when I was with the rom
-I dont know about solution of the last problems,the russians have ported the rom not me,checked the forum and they havent even reported these issues XD
BTW,if you have problem with random reboots put the fingerorint unlock.Its not real fingerprint of course,you just have to swipe down on the finger icon.The russians reported that this fixed the random reboots.
Anyway,thanks for the bugs report
Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.
Reading this comments makes me feel like my IQ decreasing
Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!
Immortel.CZ said:
Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.
Click to expand...
Click to collapse
Just to start from something,6),thats most likely software fault.And indeed I think the tutorials are fine,since you managed to flash s5 mod you are smart enough and for the videos-they are more to see how it happens,if i wanted I could put a song in the background instead of talking,my english sounds like **** tho(sometimes even I dont know what Im saying XD).So if you look at the instructions carefully,then follow what Im doing in the video you will be fine.Just if you dont know,you need to flash the desire 320 stock rom before s6 mod,broken os or other roms with version newer than 4.2.2 which might seem a bit hard for you(its actually easy tho,try to flash roms on htc one x and you will see what is hard ).The desire 320 rom also has a few issues like the rotation and white line.And dont get me wrong,Id choose broken os every day over s6 mod since its wayy better,s6 mod isnt bugless too.Also,your ram seems to be 1gb which is fine.
If you want the fastest solution-flash miui 5,its the stablest and the awesomest rom so far,ive been using it for a month and really loved it.You dont need to flash the desire 320 rom for it.
In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot
Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?
Aconcerneduser said:
Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?
Click to expand...
Click to collapse
Hey Aconcerneduser.
If you have stock room then no, you cant install/move apps to SD. I´ve tried lot of things (like App2SD, Link2SD) and nothing works.
Try flash Galaxy S5 Mod, it is not hard and then you can move apps to SD!
I can make you noob proof walkthrough (how I flashed it), it takes you 15 minutes tops and it works.
EDIT: Updated my bug report about S5 mod!
Immortel.CZ said:
In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot
Click to expand...
Click to collapse
'' 2) Go to recovery and flash 320 rom.'' XDXDXDXDXDXDXDXDXDXDXDXDXDXDXD
Lollll no.You need to flash it with sp flash tools;before that backup imei with toolhero
After that root it with the pc root program,flash the ota with STOCK recovery,do the ''build.prop thing'' and then flash recovery with mobile mtk tools.And new_recovery.img IS philz touch.
The rest is right.
Also,watch my last video for the kitkat firmware.recovery.You dont need to understand what I say,just look what Im doing.
Immortel.CZ said:
Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!
Click to expand...
Click to collapse
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-
HTC Desire 310 said:
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-
Click to expand...
Click to collapse
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.
MaRtYy01 said:
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.
Click to expand...
Click to collapse
Mine MLG ports are bugless
And that's your problem, HTC DESIRE 310. Not everyone is like you, not everyone have everything like you. And lol you are not speaking fluidly English.
If you don't want contribute this conversation, please step aside.
Thanks MaRtYy01 for advices. Few hours back I've refreshed my bug reports. Data and gps problems are gone, probably faulty flash or cause of not wiping.
And thanks for correcting me, as you can see I'm still little bit confused Will look it up tomorrow, now is bed time.
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
When does the development starts?
I don't know the procedure of ROM development. Are devs waiting for the oreo update from HTC?
Some devs already work on Oreo aosp, but it's not that easy to get it working on the 10 so that everything works. Maybe even stock will be earlier here than custom Roms like aosp and los
Sent from my HTC 10 using XDA Labs
Don't really know about LOS but AOSP based is already here...
https://forum.xda-developers.com/htc-10/development/rom-official-pure-fusion-os-oreo-t3694203/page2
P.S why is there a Dev in the Title?
Is there any news?
kingfared said:
Is there any news?
Click to expand...
Click to collapse
Lineage has a whole site with news and downloads and everything: https://www.lineageos.org/
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
Honestly Annoying said:
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
Click to expand...
Click to collapse
You can't start a "Dev thread" if you aren't a dev on the project; you can only start a "Nag thread".
Sorry for unqualified question. I know the new site but I don't know where to find dev threads. If you can help me I'll be glad.
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Ndaoud360 said:
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Click to expand...
Click to collapse
That device still has an active developer working on it. crpalmer, the user who brought 14.X to HTC 10 seems to have moved on to newer devices.
hope it will have LOS15.1
Even though Raymon left development does this mean there are no los 15 for us?
As already stated by fagyi, once he solves all bugs on aosip 8.1 he will build los.
15.1 Running flawless albeit hot sometimes!
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
heyChristo said:
Ladies and Gentleman,
I have been extremely pissed off lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
If you are so frustrated about stuff you get for free than just stay stock and stop being frustrated.......mwuhahaha funny how the world works these days......oh and by the way, you don't downgrade your kernel, you downgrade your firmware.
Cheers, have an absolutely fabulous Sunday
heyChristo said:
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Musthafa-Noor said:
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Click to expand...
Click to collapse
Nougat.
heyChristo said:
Nougat.
Click to expand...
Click to collapse
Maybe was wrong. Maybe was Oreo firmware. Switched to this and had to go the other one. Sometimes I just go into a flashing rage and can't rememember what happened after.
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Click to expand...
Click to collapse
I'm using that ROM build of 15.1 on my HTC 10 (Android 8.1), and it works pretty good actually. besides a few minor issues.
Unlocked Bootloader from HTCDev, Running latest TWRP Recovery, S-On (for me at least was not needed to turn this off), Latest Magisk (which seems to pass the Safetynet check) / Busybox.
I changed the Kernel afterwards to "kernel_htc_pme_aosp_tabp0le_eas_4.02-O" (from tabp0le) because it has the "performance" cpu governor that i can enable using Kernel Adiutor.
The bugs i encountered so far :
- Camera apps open slowly, except for "Open Camera" , not a big issue.
- HTC Sense Launcher doesn't seem to work, just get the famous (app has stopped) message, but maybe it's a conflict with my GAPPS installation
- Only 1 speaker works, HTC10 has Boomsound with 2 speakers on stock rom, 1 is a treble speaker, the other one is kinda like a small subwoofer for the low frequencies.
Is there any soundmod that would enable both speakers again?
There is not any mod to do that. But the dev of this ROM is working on getting the bottom speaker working.
I just saw that a new build-version is released for HTC10.
lineage-15.1-20180624-UNOFFICIAL-pme.zip
The below is a guide to installing GSI images on the Mi 8 Pro. I specifically have experience with the PixelExperience 9.0 (Unofficial) but have had other GSI ROMs booting and working. I hope this is useful for some.
GSI (Generic System Image) ROMS can be flashed to any Project Treble enabled device. These devices have either an A/B partition layout (these allow for seamless updating as the system can boot from A or B partition) or just an A only partition layout. The Mi 8 Pro is an arm64 a only device and support project treble ROMs. You can choose from suitable ROMs listed here and here.
The instructions given below are for Android Pie (9.0). The same basic setup can be used for Android Oreo (8.0, 8.1) ROMs, but the Mi 8 Pro should be flashed with the appropriate Xiaomi base ROM first before flashing any 8 based GSI ROM
As the ROM development for the Mi 8 Pro is basically dead, I decided to buy a OnePlus 6T and sell my Mi 8 Pro. However, due to having my new OnePlus 6T stolen, and due to a lack of funds to buy a new device, I have revived my Mi 8 Pro to try to get something other than MIUI working on it. I now have The PixelExperience (Unofficial) GSI ROM running very smoothly on my Mi 8 Pro.
As the PixelExperience team has stated they will be delivering GSI images again, if there are enough of us asking, we could get better support for things like the fingerprint sensor, for a more complete experience.
Some of the below steps may be unnecessary, but are there for a complete beginner's guide to doing this and getting the right results.
Working:
WiFi
Bluetooth (with APTX)
NFC (Including Google Pay)
RIL
Mobile data (LTE / HSPDA / 3G / EDGE)
GPS
Camera (with camera built in to ROM, as well as some GCAM implementations)
Video Camera (not working on GCAM implementations tested so far - only working on Camer built in to ROM)
Flashlight
Sound / Vibrations
Face Unlock
Hotspot
Not Working:
VoLTE (I have had it working, but unable to end phone calls and problems receiving SMS messages, so reverted)
Fingerprint (There is some support. The fingerprint area of the screen lights up when trying to enrol a new fingerprint. The screen dims when a finger is placed on the sensor, and a green light us emitted from the sensor area, but it does not register the fingerprint and this is not currently working.)
Notification LED
You Tell Me
How to install
Flash the latest Fastboot Global Stable Android PIE (9.0) ROM for the Mi 8 Pro. (eg. equuleus_global_images_V10.3.4.0.PECMIXM_20190712.0000.00_9.0_global_9a181f79c1.tgz) using the Xiaomi Tool.
Update: Use the latest MIUI system. The contents of the vendor partition are important. The most compatible vendor partition as of 2019-08-19 is from equuleus_global_V10.3.5.0.PECMIXM. You can download and flash that vendor independantly, if you have already set up your GSI image.
Reboot and finish basic MIUI setup.
Reboot to recovery.
[*]Format data (Wipe - Advanced - format data - confirm by typing yes)
DO NOT FORMAT DATA. Just perform a factory reset. Formatting data can cause issues and prevent booting.
Wipe Cache - Dalvik Cache and System
Reboot recovery
Use adb to push PixelExperience GSI image (img file extracted from download) and latest version of Magisk to root of SDCard. (Empty due to formatting data).
("adb push c:\path\system.img /sdcard/" and then "adb push c:\path\Magiskv19.3.apk /sdcard/")
Flash the image to system partition by taping INSTALL and then on the "Install Image" button (to toggle between flashing zip and img files). Do not reboot yet.
Flash magisk zip in the normal way (hit the same button as in previous step to show zip files to flash. (This is necessary to avoid bootloops)
Reboot, and enjoy.
You can now set up your "PixelExperience" device with your apps and settings, including registering a face for face unlock.
To pass cts validation for the safetynet and to allow service such as Google Pay to work
In Magisk, under settings - Find “Magisk Hide” and toggle the switch on
Magisk restarts. Go to Magisk Hide from the Magisk menu and ensure that...
Google Pay
Google Play
Google Play Services
Google Service Framework
Any Banking Apps
...are checked so that they cannot see Magisk (canont see phone as rooted).
Now go to downloads and install the SafetyPatch v3 module (created by hackintosh5).
Reboot.
Open settings - go to apps and notifications - and find the above apps to clear all data.
Enjoy your rooted safetynet compliant, as close to stock as possible Xiaomi Mi 8 Pro.
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
axelgrox said:
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
Click to expand...
Click to collapse
Face unlock works fine. I have it paired with Pick to wake phone - so when I pick it up it wakes up to allow face unlock.
However, be prepared for some investment of time (not for face unlock).... I am a bit stuck now and cannot reproduce the above to get this working. Sometimes the results are different depending on base ROM etc.
Share how you get on and anything you may need to do to get this working.
Thanks
Nice work, i will try it .
The mi8 pro 's fingerprint is so bad which can be ignored, and the face unlock is the mostly used, hahahah
thank you very much for your work
Hi, I am waiting to unlock bootloader. Need 148hrs. Will install this. Thanks for sharing.
Quick update: There are some issues with GSI ROMs and the Mi 8 Pro. SOe of these relate to the SIMcard settings - and selection of preferred SIM for data, calls etc.
My experience shows that the vendor image from equuleus_global_V10.3.5.0.PECMIXM fixes many of these. The vendor image from the original MIUI ROM is used with the GSI system image to make the whole Project treble stuff work. I advise flashing this latest vendor image for maximum compatibility.
Do you know what issues remain after flashing the latest vendor image?
Does the face unlock on Pixel Experience work with IR camera or front cam?
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
eremeya said:
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
Click to expand...
Click to collapse
Have experienced this on occasion also.
What GSI image have you tried? after my multiple efforts, I would recommend... in this order: Omni. HavocOS, Descendant(no future updates), PIxelExperience. I am hopeful about the PixelExperience team who have made an announcement that as of August they will no longer produce CAF versions of PixelExperience, and that they will maintain regular GSI builds also. PE official GSI - I am full of hope.
Anyway, back on topic: Try this.
Follow the instructions - a few precisions:
Use XiaoMiFlash to flash the equuleus_global_images_V10.3.4.0 as a base. You can update the vendor partition once you have GSI up and running, but don't let the MIUI update to 10.3.5. Ensure you define a PIN to make sure that data partition is encrypted. (everyone should use encryption nowadays, and besides, I have had bad experiences whn using a xiaomi eu or mi-globe ROM (unencrypted) as the base
Reboot and finish basic MIUI setup. - What I mean here is to let the ROM boot, don't have to sign in to Google or Mi, but get to the home screen after the initial setup.
Then reboot fastboot and flash TWRP 3.3.0. Search for TWRP-3.3.0-0504-XIAOMI8UD-CN-wzsx150.zip.
Boot to TWRP. Make sure that you are able to decrypt the data partition with the PIN you set earlier. If TWRP does not ask you for the passcode / PIN - something is wrong. Try again. ONce all is OK in TWRP, perform factory reset. (DO NOT FORMAT DATA for the aforementioned encryption reason).
adb push the img file.
adb push the Magisk 19.3 zip.
Flash both in TWRP
Reboot TWRP
Reboot system. If it appears to hang, after 5 minutes you can force restart with the power button. I have had the ROM boot OK after second boot only?
Pretty sure that if you strictly follow the above you should get a working GSI image on Mi 8 Pro. Let me know...
It's a bit flaky to set up, but once set up, apart from fingerprint sensor not working, very stable and lovely to have the stock ish android system on a MIUI phone!
Be careful with preferred network type for mobile network as some selections have messed up incoming SMS messages for me... a dealbreaker.
What happens when you flash Magisk? What does TWRP say? Have you tried flashing Magisk, rebooting TWRP, and flahing Magisk again? It may be a TWRP version issue?
Thanks for your reply!
The version of twrp you mention is what I have used. I have not tried installing then rebooting to twrp so I try that.
When flashing magisk it usually flashes fine (I have had a couple times where it just throws an error) then when I reboot the phone will boot past the Mi logo the the Android boot logo then after 10-15 sec. it just reboots to twrp.
I was finally able to get the twrp to stick across boots by flashing twrp, signing boot image, removing twrp then reboot to Miui.
Do I need to adb push the GSI image or should it be fine to install from a USB drive?
The SMS issue isn't really a big deal for me as I use Google Fi routed through hangouts for one sim and a local sim where I'm living for mostly data and a few phone calls for the second one
Thanks so much for this post. I was completely oblivious to the fact that the Mi 8 Pro would actually be different to the Mi 8 when it comes to custom roms. When I decided on my next phone, I read the positive reviews and saw enough Mi 8 roms to be willing to make a switch to Xiaomi. Until I read your post I was close to despairing as I don't want a Xiaomi rom on my phone for various reasons (among them is the fact that I don't trust them and the way they have decided to collect user data).
I've tried to follow your guide in every step (I've also flashed the updated vendor.img), but unfortunately I have not been able to install the Pixel Experience rom on my device. I do see the boot animation but it never stops, I'm forever stuck with the Google-G and the progress bar below it. Has anyone else managed to install the Pixel Experience rom on the Mi 8 Pro? If yes, did you follow the guide here or did you do something else?
Also, in your initial post you write that we should wipe the system in TWRP but as far as I can tell GSI roms need you to wipe data, cache and dalvik cache but not the system partition (if you do it, you also don't get asked for your PIN code in TWRP any more, which - as you said - indicates that something went wrong).
Did you install a particular version of the Pixel Experience rom? Maybe that might be part of my issue?
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
tllim73 said:
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
Click to expand...
Click to collapse
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
eremeya said:
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
Click to expand...
Click to collapse
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
tllim73 said:
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
Click to expand...
Click to collapse
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
eremeya said:
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
Click to expand...
Click to collapse
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
I try rooting it with magisk but unable to boot up. That's why I turn to Miroom Rom. They have done something which can boot it up.
tllim73 said:
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
Click to expand...
Click to collapse
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
Might be the developer version is only for the Chinese Rom. Anyway I am happy now running with GSI Rom.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
What version of TWRP are you using?