[ROM][CM11][SM-G355HN][CyanogenMod 11.0][UNOFFICIAL] - Samsung Galaxy Core

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
#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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Click to expand...
Click to collapse
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Downloads
Latest builds: https://www.mediafire.com/folder/cwzwh1c90stij/SM-G355HN
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Installation
1. TWRP Recovery required:
http://forum.xda-developers.com/galaxy-core/development/samsung-galaxy-core-2-sm-g355h-m-t2998094
2. Copy ROM on your ExtSdCard
3. Reboot into Recovery using 3-button-combo (home + volume up + power)
4. Do a Nandroid backup!!!
5. WIPE (wipe data/factory reset/wipe cache partition/internal storage)
6. Install the ROM from extarnal SD card using TWRP Recovery
7. Install Root from here:
http://forum.xda-developers.com/galaxy-core/help/root-galaxy-core-2-t2966445
8. Optionally install the Google Addon
Known Issues
Please do not report bugs if it is already listen in the list of known issues
* Some CyanogenMod features a missing - please do not file bug reports for those.
* Cannot set value via custom brightness "Edit" menu
* No account selected for Backup (gapps problem?)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
* Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
* If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
* If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved
Known issues of current build :
* GPS not working. Will be soon.
* root doesn't work trough developers options
* What you report.
This ROM wouldn't be possible without:
* CyanogenMod
* Samsung Open Source Center
@ngoquang2708
@doesntexits
@cleverior.ipul
Sorry if I forgot someone
XDA:DevDB Information
kanas3gnfcxx (SM-G355HN), ROM for the Samsung Galaxy Core
Contributors
Y300-0100
Source Code: https://github.com/Y300-0100?tab=repositories
ROM OS Version: 4.4.x KitKat
Version Information
Status: Alpha
Created 2016-04-13
Last Updated 2016-04-13

changelog
20160415
* Fixed low volume while using headphones and playing music
2016 04 23
* Fixed NFC (not all tags can be detected )
2016 04 27
* Fixed freeze phone when try to turn of developer options, add Torch thanks to @doesntexits
And when you recording videos first change setting's of audio codes in camera settings.

@Y300-0100
Great work
I got one Q: Did this phone support dual-SIM? I see only one signal there
Also, the correct device codename is kanas3gnfc, not the xx suffix. You can get the right codename in the rootdir folder

How to install in SM-G355M?
Amazing work, i have a noob question, how can i install in SM-G355M?
Thank u , n sorry for my bad english

doesntexits said:
@Y300-0100
Great work
I got one Q: Did this phone support dual-SIM? I see only one signal there
Also, the correct device codename is kanas3gnfc, not the xx suffix. You can get the right codename in the rootdir folder
Click to expand...
Click to collapse
No. HN is single sim model only and code name is kanas3gnfcxx from stock build prop and https://androiddevice.info/submission/29929/show
I realize that when I get asserts prop error with kanas3gnfc when I tried to install rom.

Marco123V said:
Amazing work, i have a noob question, how can i install in SM-G355M?
Thank u , n sorry for my bad english
Click to expand...
Click to collapse
later today when I upload it...
for testing because i don't have M

Y300-0100 said:
No. HN is single sim model only and code name is kanas3gnfcxx from stock build prop and https://androiddevice.info/submission/29929/show
I realize that when I get asserts prop error with kanas3gnfc when I tried to install rom.
Click to expand...
Click to collapse
That's the recovery's fault, since it only get the .name instead of .device
If you say so, the codename in cm is cm_kanas3gnfc than the xx suffix (just like the .name in stock). Also, you can add kanas3gnfcxx in TARGET_OTA_ASSERT_DEVICE flag, so no installation error is produced
Y300-0100 said:
7. Install Root from here:
Click to expand...
Click to collapse
No need for this, since userdebug builds already rooted

Vv

What about the SM-G355H ? will it work or no ?

update-script not working for variant M
Detele is assert for working
Not Working:
-MTP
-Disable Developer Option or Debugging caused bootlop

Joaquin Scala said:
update-script not working for variant M
Detele is assert for working
Not Working:
-MTP
-Disable Developer Option or Debugging caused bootlop
Click to expand...
Click to collapse
1. you are using twrp for kanas3gnfc
2. to fix mtp I need stock boot.img for H and M because of ramdisk files
3. that I don't know. Don't have that issue. if phone reboots when you disable or enable Developer Option or Debugging use grab /proc/last_kmsg
as I mentioned in first post.
4. currently I trying to fix low volume issue!!
5. As you all know I own only SM-G355HN and as I mentioned before there has to be maintainer for each device.
6. What I did regarding twrp for H and M, fix wifi and build roms for them it's because I wanted to encourage other devs (or user enthusiasts )who own devices to include themselves to build. Because I can see here on xda some folks started with development from scratch
7. end
and PS.
All my sources are up to date so anyone can use them and with detailed instruction how to build
https://github.com/Y300-0100/android_device_samsung_kanas3g
https://github.com/Y300-0100/android_device_samsung_kanas3gub
https://github.com/Y300-0100/android_device_samsung_kanas3gnfcxx/blob/master/README.md

fixed low volume issue!!
YES
I fixes low volume during typing stupid post above in 5 min.
So if you want me to commit it to my github I want to see 1000 thanks click by tonight
PS.
No 1000 more like 10 000

Y300-0100 said:
YES
I fixes low volume during typing stupid post above in 5 min.
So if you want me to commit it to my github I want to see 1000 thanks click by tonight
PS.
No 1000 more like 10 000
Click to expand...
Click to collapse
Well, if mods see this, your account will be... you know
Btw, good job. It's good to see more SPRD devices get CM

doesntexits said:
Well, if mods see this, your account will be... you know
Btw, good job. It's good to see more SPRD devices get CM
Click to expand...
Click to collapse
Thanks for info. But I didn't use any offensive word and if you are referring to 10 000 it's joke ended with
If they think that something should be "done" with my account so be it.
BTW it's already up to date. You know what

Y300-0100 said:
Thanks for info. But I didn't use any offensive word and if you are referring to 10 000 it's joke ended with
If they think that something should be "done" with my account so be it.
BTW it's already up to date. You know what
Click to expand...
Click to collapse
OK, the "10000" is what i referenced
Btw, seems you're missing some libs to get NFC working. Did you tried with any tags/devices?
If it doesn't work then, take a look at this: https://github.com/TheNikiz/android...fc3g/blob/cm-11.0/device_vivaltonfc3g.mk#L101
Some extras configs/packages for NFC are included there. See if any of them works with you

asser19 said:
What about the SM-G355H ? will it work or no ?
Click to expand...
Click to collapse
Sound fix will be but as I mentioned before MTP wont be fixed unless someone provide me stock boot.img for SM-G355H and SM-G355M.
and for a notice I have slow PC so for each build I need aprox 8 hours.
Build for SM-G355HN is uploading right now in SM-G355HN folder on mediafire.

doesntexits said:
OK, the "10000" is what i referenced
Btw, seems you're missing some libs to get NFC working. Did you tried with any tags/devices?
If it doesn't work then, take a look at this: https://github.com/TheNikiz/android...fc3g/blob/cm-11.0/device_vivaltonfc3g.mk#L101
Some extras configs/packages for NFC are included there. See if any of them works with you
Click to expand...
Click to collapse
I'm lazy. I will add packages and files for NFC. I did it before for some other devices, will tray to add FM and screen recording if hardware support it.

Y300-0100 said:
I'm lazy. I will add packages and files for NFC. I did it before for some other devices, will tray to add FM and screen recording if hardware support it.
Click to expand...
Click to collapse
FM is not supported by CM, so you've to implement your own
Also screen recording too. But, screen recording will lag like sh*t on these such devices

Y300-0100 said:
Sound fix will be but as I mentioned before MTP wont be fixed unless someone provide me stock boot.img for SM-G355H and SM-G355M.
and for a notice I have slow PC so for each build I need aprox 8 hours.
Build for SM-G355HN is uploading right now in SM-G355HN folder on mediafire.
Click to expand...
Click to collapse
Here is the stock boot.img form SM-G355M, it's from the last Samsung Update
boot.img

Hello, you can install the rom with TWRP-3.0.2-0-kanas3gnfc.img normally. Now I work MTP. Thank you very much, hoping for a newer version of android L or M.

Related

[ROM][4.4.4] CyanogenMod 11 for Samsung Galaxy SL - 20160705

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT!
Click to expand...
Click to collapse
* PLEASE READ THE ENTIRE TOPIC BEFORE FLASHING THE ROM.
Bug Reports
Click to expand...
Click to collapse
* REPORT BUGS IN THE TOPIC ONLY.
* DON'T SEND ME PM MESSAGES ABOUT BUGS OR FEATURE REQUESTS.
* ONLY REPORT THE BUGS IN CM11. I DON'T PROVIDE SUPPORT FOR OTHER ROMS. POST IN THEIR RESPECTIVE THREADS.
* IF YOU ARE ON A CUSTOM KERNEL, FIRST CHECK WITH THE STOCK KERNEL AND THEN REPORT THE BUG.
Downloads
Click to expand...
Click to collapse
ROM Downloads
Google Apps
Download the Pico Modular Package to save space on the system partition.
Changelog
Click to expand...
Click to collapse
20160705
Android Security patch level - 1st June 2016
20160421
Android Security patch level - 1st April 2016
Improved multitasking ability
Upstream Changes.
20150713
Upstream changes.
20141008
Upstream changes.
20140902
Updated to 4.4.4
Pull in changes from NamelessROM
Improved Video Recording
Fixed media playback issues.
20140513
Upstream Changes
20140507
Upstream changes.
20140423
Fixed front camera recording issues.
Upstream Changes.
20140324
Optimized CPU speed when screen off
Bluetooth HID support
Upstream updates.
20140318
Fixed issues with Audio and Media Playback
Upstream changes.
20140309
Upstream changes.
20140222
Upstream changes.
20140209
Bought back battery changes from 20140120 build
Fixed Compass
Fixed media playback.
Upstream changes.
20140128
Upstream changes.
20140124
Reverted battery driver changes.
Upstream changes.
20140120
Fixed Battery Drain
Fixed WiFI Tethering
Installation Instructions
Click to expand...
Click to collapse
IMPORTANT! READ BEFORE FLASHING!
1. If you flash this ROM from Stock ROM, it will wipe data due to different partitioning. The device would reboot while flashing and resume again.
2. Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
3. While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
4. Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
5. Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
Stock ROM
1. Flash CWM Compatible Kernel (CF ROOT)
2. Reboot to Recovery.
3. Wipe Data / Factory Reset.
4. Select the ROM zip from your SD Card and flash.
5. The device will reboot and finish flashing.
6. Reboot to Recovery Again.
7. Flash Google Apps.
8. Reboot
Any other AOSP ROM (CM7/MIUI/CM9)
1. Reboot to Recovery.
3. Wipe Data / Factory Reset.
4. Select the ROM zip from your SD Card and flash.
5. The device will reboot and finish flashing.
6. Reboot to Recovery Again.
7. Flash Google Apps.
8. Reboot
Upgrading from previous versions of CM10
1. Reboot to Recovery.
2. Select the ROM zip from your SD Card and flash.
3. Flash Google Apps.
4. Reboot
Sources
Click to expand...
Click to collapse
https://github.com/dhiru1602
Credits
Click to expand...
Click to collapse
codeworkx
sconosciuto
Known Issues
Click to expand...
Click to collapse
None
The Google Apps package doesn't include Google Home, Google+, Hangouts and Face Detection.
Yaay Finally,
>testing,
a preview is coming soon
Thank You Master
Thank you master Dhiru!!! Great job!
Thanks i flash it and Report =)
Gesendet mit meinem Mäusekino =)
Hi Dhiru.. Currently on it and its great work... A big thanks to you bro..
I have two questions.
1. How to SWAP SD Card.
2. How to disable Touchpad lights.
Oh God Dhiru you shocked me again!
But oops! I got stuck at the first boot screen. Previous was your CM10.2 A4. Flashed CM11 and gapps without wiping anything. After rebooting it stucked.
Edit: Tried clean flash from DDLF2 but still stucked after CM11A1 flashing.
First look.. Awesome...
Unable to customize UI.. Seems like brightness is little higher even at the minimal level..
So far so good...
Hit Thanks if I have helped you...
Sent from I9003 XDA App
thanx
thanx dhiru for keepig our device alive samsung ditched our phone but thanks to you devs for keeping our device alive :good::good::good::good:
big thanx Dhiru for your amazing work, finally Kitkat arrived for our device, will try it and subscribe this thread...
best regards,
deDante
CF-ROOT
Hi @dhiru1602
please share the CWM or CF-ROOT you use to flash CM rom from stock.
thanks
chongns said:
Hi @dhiru1602
please share the CWM or CF-ROOT you use to flash CM rom from stock.
thanks
Click to expand...
Click to collapse
And to come to think of it, how did you get 240 likes if you don't know which CF-ROOT to use?
Here, tho. Download.
woooow,it's so smooooth.and the free ram is almost 100+MB.:good:
I installed the googlehome. it works fine.but how to make the Statusbar transparent?
nbrian2012 said:
And to come to think of it, how did you get 240 likes if you don't know which CF-ROOT to use?
Here, tho. Download.
Click to expand...
Click to collapse
Different ROM, different RAMdisk
Downloading now...... Thanks dhiru
Will try to give the review once i have tested it
nbrian2012 said:
And to come to think of it, how did you get 240 likes if you don't know which CF-ROOT to use?
Here, tho. Download.
Click to expand...
Click to collapse
By porting "CF-ROOT" for those CF-ROOT which make people phone boot loop .....funny hah...
well, i just want to ensure, our member are using the cwm or cf-root which Dhiru is using so, we can avoid unnecessary incompatibility between our so old cf-root. and also "why i get status 7 ? "
Downloading now...... Thanks dhiru
Will try to give the review once i have tested it
AWESOME. Amazing. Dhiru you're the best, seriously. Thank you for doing this. I hope you can make a stable ROM out of this. Thank you so much.
EDIT: Waited patiently for this... what are the absolute major bugs which effect everyday stuff? Phone calls/texts/app incompability/battery ... anyone who is using the ROM currently, please answer.

[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project

[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project
CyanogenMod is a free, community built distribution of Android 5.1 which greatly extends the capabilities of your phone.
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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
XDA:DevDB Information
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project, ROM for the Sony Xperia Z3 Compact
Contributors
jerpelea
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-12-02
Last Updated 2015-04-13
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
Homepage
www.freexperiaproject.net
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
the build should be here soon: http://fxpblog.co/cyanogenmod/cyanogenmod-12/
we have enabled daily builds
if your device is not yet in the list will appear soon (1 day,1 week, 1 month) no ETA please
but you have to remember that is an early alpha build
Thread closed until there is a build available
Thread cleaned
 @jerpelea, please PM a mod or report this post to get the thread re-opened immediately.
Now that the daily builds are continued, have you or any other dev worked on CM12 for our device?
I am currently able to compile, but there seems to be a couple of issues that users are reporting,
Problems with com.qualcomm.location.apk
Updater script errors in recognizing proper device
System bootloops after 'starting apps'
Code:
E/installd( 269): DexInv: --- END '/system/priv-app/com.qualcomm.location/com.qualcomm.location.apk' --- status=0x0100, process failed
D/AndroidRuntime( 4634): Shutting down VM
E/AndroidRuntime( 4634): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
It might be that I am not importing all the necessary repositories or the wrong ones (in my local manifests),
I would be grateful if device specific repos can be mentioned in the OP or second post
Thank you
Merry Christmas!
Can't wait for my Z3C build to be available.
AlexBurnout77 said:
Can't wait for my Z3C build to be available.
Click to expand...
Click to collapse
On that topic -- why has this been re-opened if there are still no builds?
 @jerpelea can we get at least a vague explanation of what's halting the builds from being made/uploaded?
Exactly. If they wanted to give us a full working built they can. I dont understand why theyre dragging thier boots, unless they want to release lollipop stock first.
someone755 said:
On that topic -- why has this been re-opened if there are still no builds?
@jerpelea can we get at least a vague explanation of what's halting the builds from being made/uploaded?
Click to expand...
Click to collapse
g0ldenchild562 said:
Exactly. If they wanted to give us a full working built they can. I dont understand why theyre dragging thier boots, unless they want to release lollipop stock first.
Click to expand...
Click to collapse
The builds weren't being uploaded because the build server was down for a couple of weeks. Now that it's back up things should be getting back to normal.
They can't give us a full working build because the builds aren't fully working. Even with Sony sources and binaries the modem still isn't working, CM12 isn't fairing much better.
Gairtial said:
The builds weren't being uploaded because the build server was down for a couple of weeks. Now that it's back up things should be getting back to normal.
They can't give us a full working build because the builds aren't fully working. Even with Sony sources and binaries the modem still isn't working, CM12 isn't fairing much better.
Click to expand...
Click to collapse
Well then the thread sbouldnt have been reopened. If theres nk available builds yet...
Yeah I'm not sure why they reopened it when they're not doing CM12 builds.
Did anyone flashed first release? What's working and not working.
Using the build from the 28th
Confirmed not working & issues:
*cell service
*camera
*Brightness slider is finicky
*device gets VERY hot
*massive battery drain
Things that work on this CM rom but not the latest AOSP build:
*NFC
*sd Card Support
*USB mounting to a PC
* Location
Notes:
This installs the stock CM recovery so make sure to get rom and gapps installed via TWRP the first go.
I had to edit the updater-script to flash. Removed the first line of device checks as it saw mine as a aries and would not flash
PS, for the love of all things holy, please setup a mirror. The current provider is just shy of torture.
finally we get one build,will flash.wait for my report
edit:lol,saw it,plan is over
edit2:still flashed it,it seems we have baseband at least(not display unknown),on its first boot,i noticed it's searching signal,then disappeared,checked baseband not unknown,tried to search for carrier but it never ends.
did a logcat,before logcat I turned on airplane mode,after its beginning i disabled airplane mode,tried to search for operator,then turned it to lte mode then tried to search again.
https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0
I don't understand why two built on 28 december ? One 280Mo and an other 285Mo .
http://uploaded.net/f/4bbo69
You can see to the bottom one this page .
Thanks i'm very happy to see CM12 on this device
mick711 said:
I don't understand why two built on 28 december ? One 280Mo and an other 285Mo .
http://uploaded.net/f/4bbo69
You can see to the bottom one this page .
Thanks i'm very happy to see CM12 on this device
Click to expand...
Click to collapse
the other one is for z3.I think I didn't see more builds..
Just tried the latest renamed nightly for (z3c instead of aries)-
FXP-cm-12-20141228-UNOFFICIAL-z3c.zip
The WIFI radio seems to work - but the LTE and voice radio connects
right at boot and then disconnects and goes away.
On shutdown/restart the same thing happens - LTE/Voice connects at first
and then it goes away.
I saw funky radio issues when testing the pure AOSP aries builds-
so it may not be just the CM12 ROMS.
I also had to edit the z3c zip file to allow the aries product name
so I could install it from doomlord's stock CWM kernel recovery image-
but that was minor compared to the radio issues.

[ROM] OFFICIAL CM-12.1 SnapTo (G620-A2) NIGHTLIES

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, we will laugh at you, all, at the same time.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Download
https://github.com/cyanogenmod/android_device_huawei_g620_a2
https://github.com/cyanogenmod/android_kernel_huawei_msm8226
change log
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
OFFICIAL CM-12.1 SnapTo (G620-A2), ROM for all devices (see above for details)
Contributors
Lloir, Lloir, Thömy
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-08-30
Last Updated 2015-08-30
ChangeLog
31/8/15 (Next Nightly)
Add in missing CVE -- 2015-1534
Remove 1080p from video record (device doesn't support it)
Add in Selinux policies to stop log spam
Add in correct lunfile path to enable SDcard mounting
Fixed Loudspeaker (Let me know how this is)
------------------------------------------------------------------------------------
30/8/15
Add in all the latest CVE patches too many to list (approx 20)
Fix LED
Known Issues
Loudspeaker doesn't work in calls currently
LED pulse length and speed still isn't working. Also noticed loudspeaker in calls is still broken in 8/30 nightly build.
USHAM2 said:
LED pulse length and speed still isn't working. Also noticed loudspeaker in calls is still broken in 8/30 nightly build.
Click to expand...
Click to collapse
Umm you sure? It's working perfectly fine here.....
and I already said loudspeaker is broken
Yes.. If you set the pulse length to long or very long, the LED should fade in out vs. continuous flashing when you receive a new notification. I did a clean flash to 8/30 build.
USHAM2 said:
Yes.. If you set the pulse length to long or very long, the LED should fade in out vs. continuous flashing when you receive a new notification. I did a clean flash to 8/30 build.
Click to expand...
Click to collapse
I just set it manually to long sent my self a text and it's pulsing green correctly.....
Uploading a video to show you what I have, to see if it's the same....
or if you don't have flash http://youtu.be/QLDaW86rGa0
Hmm. I guess an easier way to describe it... When I change the pulse length to very short then to very long, the pulse length stays the same. There's no noticeable difference.
USHAM2 said:
Hmm. I guess an easier way to describe it... When I change the pulse length to very short then to very long, the pulse length stays the same. There's no noticeable difference.
Click to expand...
Click to collapse
AHH now that's worded better, ok. I'll check it out properly once everything else is sorted.
Good afternoon all!
This phone is currently on sale and I'm debating whether to get it or now. it's around $100 USD, so not terribly expensive.
Lloir, will you continue support for this device past CM12.1? If you do, I think I'll buy it as a back up phone...as if I didn't have enough haha.
After installing via the provided insrtructions I show only 4gb instead of the 8gb that i should have in total storage capacity. Anyone else getting this or know how to fix it?
Thanks
edxmon said:
Good afternoon all!
This phone is currently on sale and I'm debating whether to get it or now. it's around $100 USD, so not terribly expensive.
Lloir, will you continue support for this device past CM12.1? If you do, I think I'll buy it as a back up phone...as if I didn't have enough haha.
Click to expand...
Click to collapse
need help.
hello... i´m a beginer.... i have tried to install a twrp recovery on my huawei g620-a2 but cellphone can´t start.... when i press start button just apear recovery system.... i can acces the bootloader too selectin reboot to bootloader.
i have tried to wipe data/factory reset and install this rom through "apply update option" (i don´t have other option), it finish succefully but when i reboot system.... it doen´t start. HELP ME... What can i do??
i´m trying to use roms and recoverys downloaded from url that apears in one picture of my attachments.
no have The key by my bootloader, Speak Spanish :v
Hello, I have a problem when getting the code to unlock my bootloader says I should write well the model of my phone or imei, someone could send me a screenshot of how I should correctly write the form ???:crying:

[ROM][7.1.2][FINAL] CodeOfHonor's OmniROM 7.1 for Huawei P8 Lite 2017

OmniROM is our Android custom ROM variant, feature-packed but always with stability as #1 priority in mind.
Based on the Android Open Source Project (AOSP) and enriched by our developers with lots of custom enhancements, OmniROM has set out to give you a great Android experience on your mobile.
Code:
* 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.
Compatible device?:
Code:
[LIST]
[*]P8 Lite 2017.
[*]P9 Lite 2017.
[*]P10 Lite.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP, flash my latest build to avoid error 7 from here.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
tell me.
Downloads:
Code:
[B][I]**21/05/2018**[/I][/B]
[LIST]
[*][URL="https://www.haky86.com/2018/05/21/omnirom-nougat-hi6250/"]From Haky's Blog[/URL]
[/LIST]
Changelogs:
Code:
[B][I]**21/05/2018**[/I][/B]
[LIST]
[*]re-works
[/LIST]
Source Code:
Device Tree:
https://github.com/hak86/android_device_huawei_hi6250
Kernel GPL:
https://github.com/hak86/android_kernel_huawei_prague
Vendors:
https://github.com/hak86/android_vendor_huawei_hi6250
XDA:DevDB Information
OmniROM for PRA-LX1, ROM for the Huawei P8lite/P8 Lite
Contributors
haky 86, Meticulus
Source Code: https://github.com/hak86?tab=repositories
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 5.x "C432B161"
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-01-17
Created 2018-01-17
Last Updated 2018-01-17
ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.
*reserved v2*
Download Link is not working
Edit: There is a " in the end of the link that shouldn't be there.. Maybe you should edit the link
Zillinda said:
Download Link is not working
Edit: There is a " in the end of the link that shouldn't be there.. Maybe you should edit the link
Click to expand...
Click to collapse
fixed
I have a totally weird issue on this ROM. I don't have this issue on any of your ROMs except this one.
When i use your vendor my SIM Card is not detected (even if i disable Dual Sim and reboot)
But the weird thing is, when i flash my stock vendor from P10 Lite the Sim is working BUT the sound is not working.
I flashed this one like every ROM from you, and every ROM worked but not this one :/
Are you using the latest Code of Meticulus? Because i had this issues with earlier builds of Meticulus' ROMs
Except that everything works fine. I will go back to your fully working SlimROM until you release AOSPExtended.
Zillinda said:
I have a totally weird issue on this ROM. I don't have this issue on any of your ROMs except this one.
When i use your vendor my SIM Card is not detected (even if i disable Dual Sim and reboot)
But the weird thing is, when i flash my stock vendor from P10 Lite the Sim is working BUT the sound is not working.
I flashed this one like every ROM from you, and every ROM worked but not this one :/
Are you using the latest Code of Meticulus? Because i had this issues with earlier builds of Meticulus' ROMs
Except that everything works fine. I will go back to your fully working SlimROM until you release AOSPExtended.
Click to expand...
Click to collapse
In your case you must edit the /vendor/phone.prop file
* search for [0X3B412000]
* and make sure to set the following string.
persist.radio.multisim.config=single
persist.dsds.enabled=false
* save and reboot.
you get this problem because my vendor.img is designed to run with single sim devices only.
AOSPE will be available after AOSPA Paranoid, isn't available on any hi6250 device as I see.
Edit: remove persist.radio.multisim.config=single, save and reboot.
haky 86 said:
In your case you must edit the /vendor/phone.prop file
* search for [0X3B412000]
* and make sure to set the following string.
persist.radio.multisim.config=single
persist.dsds.enabled=false
* save and reboot.
you get this problem because my vendor.img is designed to run with single sim devices only.
AOSPE will be available after AOSPA Paranoid, isn't available on any hi6250 device as I see.
Edit: remove persist.radio.multisim.config=single, save and reboot.
Click to expand...
Click to collapse
Thanks, i will try it now.
But why don't i have this issue with your other ROMs?
Zillinda said:
Thanks, i will try it now.
But why don't i have this issue with your other ROMs?
Click to expand...
Click to collapse
it's releated to vendor.img partition since it's designed to run on single sim.. just fix the flags I wrote and will get fixed.
a thing you should do manually on dual sim phones.
haky 86 said:
it's releated to vendor.img partition since it's designed to run on single sim.. just fix the flags I wrote and will get fixed.
a thing you should do manually on dual sim phones.
Click to expand...
Click to collapse
I get error, that it's Read-Only File system and if i want to change the permission of the file with Root Browser it says Changing permissions was not successful. Both the Editor and the Root Browser have root permissions.
Edit: i see the file is symlinked to /hwvendor/phone.prop so i edited it inside there but it's still not working
Zillinda said:
I get error, that it's Read-Only File system and if i want to change the permission of the file with Root Browser it says Changing permissions was not successful. Both the Editor and the Root Browser have root permissions.
Edit: i see the file is symlinked to /hwvendor/phone.prop so i edited it inside there but it's still not working
Click to expand...
Click to collapse
set via adb shell and tell us if fixed
setprop persist.radio.multisim.config single
setprop persist.dsds.enabled false
haky 86 said:
set via adb shell and tell us if fixed
setprop persist.radio.multisim.config single
setprop persist.dsds.enabled false
Click to expand...
Click to collapse
nope, i don't know if i am too stupid or if it's really not working, but none of this methodes is working.
Zillinda said:
nope, i don't know if i am too stupid or if it's really not working, but none of this methodes is working.
Click to expand...
Click to collapse
well, as you see it's working for me in screenshots.
I finally got it working by replacing the /hwvendor/phone.prop file from my STOCK vendor into the vendor of @haky 86.
@haky 86
Intalled the C432B161 firmware, then proceed to flash this rom with your instructions, everything works except video recording on camera, also for whatsapp, facebook, messenger, etc
Any hints ? Maybe I missed something
rubentkato77 said:
@haky 86
Intalled the C432B161 firmware, then proceed to flash this rom with your instructions, everything works except video recording on camera, also for whatsapp, facebook, messenger, etc
Any hints ? Maybe I missed something
Click to expand...
Click to collapse
Enable Google H264 in Settings -> Extra
Sent from my hi6250 using XDA Labs
Zillinda said:
Enable Google H264 in Settings -> Extra
Sent from my hi6250 using XDA Labs
Click to expand...
Click to collapse
Already did that and reboot the phone, but the problem persist.
[/ATTACH]
rubentkato77 said:
Already did that and reboot the phone, but the problem persist.
[/ATTACH]
Click to expand...
Click to collapse
what is your device?also did you flash my vendor partition?
haky 86 said:
what is your device?also did you flash my vendor partition?
Click to expand...
Click to collapse
I bought it as P9 Lite 2017 PRA-LX3C69B110 branded from Telcel Mexico, then converted PRA-LX1C432B110 dual sim unbranded and got updated to B170.
Then unlock bootloader, instal your latest TWRP, follow your unbrick guide fro C432B161.
Then flash omni ROM + pico gapps.
In some point I didn flash your vendor img (how did I miss that !#@$!) do I needto flash it again before omni rom or after?
Regards. :good:
rubentkato77 said:
I bought it as P9 Lite 2017 PRA-LX3C69B110 branded from Telcel Mexico, then converted PRA-LX1C432B110 dual sim unbranded and got updated to B170.
Then unlock bootloader, instal your latest TWRP, follow your unbrick guide fro C432B161.
Then flash omni ROM + pico gapps.
In some point I didn flash your vendor img (how did I miss that !#@$!) do I needto flash it again before omni rom or after?
Regards. :good:
Click to expand...
Click to collapse
well yes, you have to flash my own vendor from unbrick guide!
but before doing that pull /vendor/phone.prop from converted firmware and paste into system/vendor/ to avoid sim problems.
as you see my screenshot the camera is fully works without enable google codecs.

[ROM][7.1.2][12/05/2018] CodeOfHonor's AOSPA Paranoid v7.3.1 for Huawei P8 Lite 2017

Paranoid Android is a custom ROM aiming to extend the system, working on enhancing the already existing beauty of Android and following the same design philosophies that were set forward by Google for Android Open Source Project.
Code:
* 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.
Compatible device?:
Code:
[LIST]
[*]All devices that use hi6250 chipset and use kernel 4.1.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
Installation Guide:
Make sure to the stock backup saved on pc, I'm not responsible for any bricked or damage.
Reboot to TWRP.
Go to Wipe.
Choose Advance Wipe.
Check on Data and change file system to EXT4, will not ever boot with F2FS.
Wipe cache, data, dalvik and system.
Flash the rom.
Reboot and have fun then.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
Dual sim might will not work all variants, so don't waste your time by asking me to fix it.
You don't like it?, easy revert to Emui 5.x.
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Source Code:
Device Tree:
https://github.com/codeofhonor-dev/android_device_huawei_hi6250
Kernel GPL:
https://github.com/codeofhonor-dev/android_kernel_huawei_hi6250
Vendors:
https://github.com/hak86/android_vendor_huawei_hi6250
XDA:DevDB Information
AOSPA Paranoid for Hi6250, ROM for the Huawei P8lite/P8 Lite
Contributors
haky 86, Meticulus
Source Code: https://github.com/hak86/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emiui 5.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.3.1
Stable Release Date: 2018-02-09
Created 2018-02-09
Last Updated 2018-02-08
ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.
Thank you for your awesome work! AOSPA is my fking favorite ROM.
NetfariousIntent said:
Thank you for your awesome work! AOSPA is my fking favorite ROM.
Click to expand...
Click to collapse
glad to hear that
I'll post in p9 lite and honor 6x sections later
here a screenshot of my friend that run on his p10lite and have almost 19%..
it is stable? can i try it?
---------- Post added at 09:44 AM ---------- Previous post was at 09:05 AM ----------
stuck at installing the rom. it says tested fir you p8 lite 2017 by haky86....... and it doesnt move at all
karasoulas said:
it is stable? can i try it?
---------- Post added at 09:44 AM ---------- Previous post was at 09:05 AM ----------
stuck at installing the rom. it says tested fir you p8 lite 2017 by haky86....... and it doesnt move at all
Click to expand...
Click to collapse
sounds like you didn't use my recovery.
https://basketbuild.com/devs/haky86/HuaweiP8Lite2017/TWRP
haky 86 said:
sounds like you didn't use my recovery.
https://basketbuild.com/devs/haky86/HuaweiP8Lite2017/TWRP
Click to expand...
Click to collapse
yup. works. i dont know why man. but the stock rom is faaaaar faster than ur roms. Not trying to be rude i love ur work but i dont know. maybe iim doing something wrong?
** Note **
**11/02/2018**
pa_hi6250-7.3.1-EOL-20180210.zip
Changelogs:
**11/02/2018**
possible fix for ril crashes
Hello, the Rom is running smoothly. Thank you. but the network is coming After 30 second going . What is the solution?
atsmurat said:
Hello, the Rom is running smoothly. Thank you. but the network is coming After 30 second going . What is the solution?
Click to expand...
Click to collapse
This is happening also to me, probably due to newer blobs on emui5.0.1 (I came from that version to AOSPA)
Also why permessive? I think debug it's done as everything works! Better enforcing
Thanks for your hardwork btw, very appreciated
sys01 said:
This is happening also to me, probably due to newer blobs on emui5.0.1 (I came from that version to AOSPA)
Also why permessive? I think debug it's done as everything works! Better enforcing
Thanks for your hardwork btw, very appreciated
Click to expand...
Click to collapse
Was happening to me until I flashed Gapps aroma with the new dialer and stuff. now everything works smoothly :/
atsmurat said:
Hello, the Rom is running smoothly. Thank you. but the network is coming After 30 second going . What is the solution?
Click to expand...
Click to collapse
sys01 said:
This is happening also to me, probably due to newer blobs on emui5.0.1 (I came from that version to AOSPA)
Also why permessive? I think debug it's done as everything works! Better enforcing
Thanks for your hardwork btw, very appreciated
Click to expand...
Click to collapse
some devices require the following flags in build.prop ;
ro.config.client_number=2
rild.libargs1=-m modem1
rild.libpath1=/vendor/lib64/libbalong-ril-1.so
rild.libpath=/vendor/lib64/libbalong-ril.so
rild.libargs=-m modem0
save and reboot, should fix the problem then.
NetfariousIntent said:
Was happening to me until I flashed Gapps aroma with the new dialer and stuff. now everything works smoothly :/
Click to expand...
Click to collapse
I use pico, always.
Sim keep disconnecting itself
It gives error while saving the finger print, both in this and the slim rom
atsmurat said:
It gives error while saving the finger print, both in this and the slim rom
Click to expand...
Click to collapse
Did you erase all of your fingerprints in stock ROM before flashing?
If not, flash elite ROM, erase fingerprints, and then flash this/slim back
CarlosAG10 said:
Did you erase all of your fingerprints in stock ROM before flashing?
If not, flash elite ROM, erase fingerprints, and then flash this/slim back
Click to expand...
Click to collapse
İ didnt erase fingerprints in Omni ROM . From that ?
Where is Elite Rom ?
haky 86 said:
some devices require the following flags in build.prop ;
ro.config.client_number=2
rild.libargs1=-m modem1
rild.libpath1=/vendor/lib64/libbalong-ril-1.so
rild.libpath=/vendor/lib64/libbalong-ril.so
rild.libargs=-m modem0
save and reboot, should fix the problem then.
I use pico, always.
Click to expand...
Click to collapse
Noto solve the SIM from disconnecting itself
Wire1122 said:
Noto solve the SIM from disconnecting itself
Click to expand...
Click to collapse
I will do a test-build post dinner, I fix the problems around here a few weeks ago on some roms!
Have You found the bug? I really want use your rom for Daily use.
** Note **
**13/02/2018**
pa_hi6250-7.3.1-EOL-20180213.zip
**13/02/2018**
Fix RIL crashes.
How to fix RIL Crashes?
Follow this post

Categories

Resources