NOTE
This is an UNOFFICIAL build of CyanogenMod 10 for the galaxy fame S6810P it should also work for the S6810 but i don´t know for sure since i don´t own this device and don´t want to brick your device so.
If you know that s6810p roms works with s6810 say it in the thread here and i wil edit the asserts later on the sourcecode.
This is only for testers who know how to report an logcat so we find out the problems why it won´t boot and can fix those problems.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, or dead SD cards,
* nuclear war, pinguin invasions or that you are getting fired because the alarm app failed.
* before flashing it! YOU are choosing to make these modifications, and if
* If you point your finger at me for messing up your device, I will laugh at you. Hard
*/
First Time Installing an custom rom if you have an custom recovery proceed to step download zip and continue.
Install an good custom recovery:http://forum.xda-developers.com/showthread.php?t=2656949
Download the zip
WIPE DATA/FACTORY RESET
Format/System
flash the rom zip from recovery
Flash the kernel from recovery
Reboot
Connect your phone to your pc and use adb to logcat and report it here.
Download Site: TEST VERSION 1.0
https://drive.google.com/file/d/0B1u3mnq0nstfSkdnUVp1YkhPZVU/
Kernel
https://drive.google.com/file/d/0B1u3mnq0nstfVGNsVnFNSDVIVnc/edit?usp=sharing
FAQ/KNOWN ISSUES
Click to expand...
Click to collapse
Wifi doesnt work
Audio doesnt work
Bluetooth works but internal sd isnt mounted good so you cant receive files.
nfc i dont know.
simcard doesnt work
camera doesnt work related to internal sd not being mounted well or wrong permissions
sdcard mounting doesnt work
EVERYTHING RELATED TO RIL
Don´t blame me that it doesnt work fully since there is no official or unofficial sourcecode on github except mine now.
And i don´t own that device.
Credits:
adytzu33 for the cm10 sourcecode
Corsicanu for providing the sourcecode and helping to finalize cm10.
Cyanogenmod for providing their own system
Corsicanu,faizauthar12 and Toshiro71 for being Betatesters.
XDA:DevDB Information
Cyanogenmod 10, ROM for the Samsung Galaxy Fame
Contributors
wulsic
ROM OS Version: 4.1.x Jelly Bean
Based On: Cyanogenmod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2014-05-30
Created 2014-05-19
Last Updated 2014-05-31
Reserved for Later use
I'd like to test but i dont know how to get logcat. if u give instruction here.i'll try
Thank You
Hi, thanks but the link doesn`t work
Sent from my Meeb[]x-1 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1726238 Here's a way, I don't know if it is outdated. I gonna try to post a logcat after a download the rom.
@wulsic you forgot about gapps - http://goo.im/gapps/gapps-jb-20121011-signed.zip
To provide logcat - install the rom and gapps, make a full wipe, reboot and connect the phone to usb cable and open a cmd where you will type 'adb logcat'. Copy the output-there will be a loop-and paste it here.
You will need sdk installed and configured and proper drivers.. Note that the phone might not boot-will remain on Samsung Galaxy Fame logo. I will test it in an hour or two maybe..
Sent from my Nameless phone
Ohyeah i totally forget i will check it after school i cant do anything now cause i need to go to school.
Hakets sorry but i cant make an mirror now. Next Time i will upload to mega and mediafire or google drive. Or inform me if you guys know a beter website.
If you guys post an logcat attach it in your post instead of quoting it @corsicanu thankyou for making an detailed post i was tired so i couldt finish it.
I will make after school another mirror, make the platform-tools and drivers in one package so people dont need to download the whole sdk. If we Get the phone booted up then i will also post in the op my light gapps i think the fame will also be smoother then with unneccesary bloatware.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
I use google drive without any problems..
Mirrored the zip... You will find also gapps-jb-20121011 for 4.1.x. Cheers!
Removed the link
Update 1: Edited the zip because i received status 7 and reuploaded. Status 7 is because the recovery is built with s6810 kernel and the zip tries to get assert for s6810p. @wulsic you may need to remove manually on every build from updater-script so it won`t request asserts.
Update 2: Something is wrong with init.rc.. @adytzu33 fixed this once but idk how. It`s related to the mountpoints and permissions.
Code:
[email protected] ~/Desktop $ adb devices
List of devices attached
94363000479004F6 device
[email protected] ~/Desktop $ adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
I am wait until beta version or final version
Sent from my GT-S6810 using XDA Premium 4 mobile app
aserted failed: getprop........................................
installation aborted ( status 7)
i guess i'll also wait for next release
Question
I am download from corsicanu link
After instalation
It still bootloop
And I try to use stock boot.img,and it's same
Can corsicanu or wulsic fix this
I am use S6810
Sent from my GT-S6810 using XDA Premium 4 mobile app
corsicanu said:
I use google drive without any problems..
Mirrored the zip... You will find also gapps-jb-20121011 for 4.1.x. Cheers!
https://drive.google.com/folderview?id=0B-zMfsAgHdrxUjFDellHaXJrNlk#list
Update 1: Edited the zip because i received status 7 and reuploaded. Status 7 is because the recovery is built with s6810 kernel and the zip tries to get assert for s6810p. @wulsic you may need to remove manually on every build from updater-script so it won`t request asserts.
Update 2: Something is wrong with init.rc.. @adytzu33 fixed this once but idk how. It`s related to the mountpoints and permissions.
Code:
[email protected] ~/Desktop $ adb devices
List of devices attached
94363000479004F6device
[email protected] ~/Desktop $ adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Corsicanu i will remove the line
TARGET_OTA_ASSERT_DEVICE := nevisp,s6810p,GT-S6810P from the boardconfig.mk i will look into init.RC after school. But i just need to know or the ROM is compatible with Every device so i can mention it.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
toshiro71 said:
aserted failed: getprop........................................
installation aborted ( status 7)
i guess i'll also wait for next release
Click to expand...
Click to collapse
Try to download from corsicanu,he fixed it
Sent from my GT-S6810 using XDA Premium 4 mobile app
Need to point out some things:
@wulsic you need to remove manually from updater script every time as the compiler still inserts an assert.. Was tested with @adytzu33 and came up to same conclusion. The other solution would be to make another cwm for all devices based on s6810p kernel.
And the rom will be compatible with all version of single sim Fame as they work with custom stock. Only problems that may appear could be 'no sim' errors like on stock rom for different zone.
@faizauthar12 there is no point to download again as we are sure something is wrong there.
For all here, these builds are debug builds. The only purpose of these builds is to patch existing bugs and make it work. If you are not sure of what you`re doing, the best will be to stay away. It may not boot, may brick your phone or you may lose your data. You are the only one responsable for any damage that you do to your phone.
corsicanu said:
Need to point out some things:
@wulsic you need to remove manually from updater script every time as the compiler still inserts an assert.. Was tested with @adytzu33 and came up to same conclusion. The other solution would be to make another cwm for all devices based on s6810p kernel.
And the rom will be compatible with all version of single sim Fame as they work with custom stock. Only problems that may appear could be 'no sim' errors like on stock rom for different zone.
@faizauthar12 there is no point to download again as we are sure something is wrong there.
For all here, these builds are debug builds. The only purpose of these builds is to patch existing bugs and make it work. If you are not sure of what you`re doing, the best will be to stay away. It may not boot, may brick your phone or you may lose your data. You are the only one responsable for any damage that you do to your phone.
Click to expand...
Click to collapse
Sorry for my mistake
Sent from my S6810 using XDA Mobile app
I just wanna say, I'm glad that finally someone built CM for galaxy fame
Thanks for all your works guys..
I'm ready to be your tester
But, just out of curiosity..
why don't you guys compile CM11 instead?
I mean, someone has making effort to do it, but also stuck in somewhere..
maybe you guys could team up or something
here's the link:
http://forum.cyanogenmod.com/topic/91390-compiling-cm11-to-the-galaxy-fame/
and
http://forum.xda-developers.com/showthread.php?t=2713973
regards,,
cheers
and keep famous
midoen said:
I just wanna say, I'm glad that finally someone built CM for galaxy fame
Thanks for all your works guys..
I'm ready to be your tester
But, just out of curiosity..
why don't you guys compile CM11 instead?
I mean, someone has making effort to do it, but also stuck in somewhere..
maybe you guys could team up or something
here's the link:
http://forum.cyanogenmod.com/topic/91390-compiling-cm11-to-the-galaxy-fame/
and
http://forum.xda-developers.com/showthread.php?t=2713973
regards,,
cheers
and keep famous
Click to expand...
Click to collapse
because, as i said, other version of android different than stock (4.1.2) needs porting of drivers.. and when you end up with errors you don't really know wich is the problem - incomplete device tree or incompatible drivers.. will try to reach him and see if we can team up.. cheers!
Sent from my Nameless phone
Stuck in bootsplash, please tell me how to solving this ?
Ikhsan_novindri said:
Stuck in bootsplash, please tell me how to solving this ?
Click to expand...
Click to collapse
Wait man,it's under maintaince cause all device stuck on boot
Sent from my GT-S6810 using XDA Premium 4 mobile app
Ikhsan_novindri said:
Stuck in bootsplash, please tell me how to solving this ?
Click to expand...
Click to collapse
Flash stock rom via odin or restore a previous backup if you have.
I will say it one more time. This isn`t a working cyanogenmod, it doesn`t boot, and the only purpose of releasing it is for debug. If you don`t know what this is about stay away from this thread. Also please read the whole thread before flashing. Was that much 2 pages?
We will keep it low until a working version. If there is anyone who would like to help us with tests and debugging PM me or @wulsic and maybe we`ll cooperate. Thanks!
Also http://github.com/wulsic & http://github.com/corsicanu for those who want to help on this project.
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of CyanogenMod 10.2
Sauce: https://github.com/CyanogenMod
Downloads
Firmware: http://get.cm/?device=p1 (Grab the builds that start with "cm-10.2-")
Google Apps: 1 (Make sure you grab the correct version, for CyanogenMod 10.2 / Android 4.3.0)
Installation
Note: this firmware uses the same partition layout as CyanogenMod 10.1 nightly builds.
Do a Nandroid Backup!
Install the firmware using ClockworkMod Recovery
Optionally install the Google Addon
Known Issues
Bootanimation looks weird for the first few seconds.
Still image capture from the front camera doesn't work.
Change Log
20130814
Initial release
Reporting Bugs
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. 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)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Use these commands to get a logcat and dmesg
Code:
adb root
adb logcat > logcat.txt (wait for a few seconds then press Ctrl + C)
adb shell dmesg > dmesg.txt
Credits
humberos, sbradymobile, jt1134, pawitp and everyone else involved in coding and debugging.
Works perfectly so far. Everything works. Battery backup is good too. The option to disable hardware keys is missing I guess but that's alright. Thanks for your hard work.
Sent from my GT-P1000 using Tapatalk 4
Any chance we get some p1c love
Sent from my SCH-I800 using xda premium
Nicklag said:
Any chance we get some p1c love
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I don't remember where, but at some point it was advised that CM10.0 and subsequent ROMS are the same for P1000, P1000L and P1000C.
@cdesai, can you please correct me if wrong?
Thank you, Desai!!! It looks decent! You are the great coder.
When push the power button, the screen always switches to landscape from portrait (or
vice versa) before it goes off. And lockscreen is always portrait.
Yue_Iohikzu said:
I don't remember where, but at some point it was advised that CM10.0 and subsequent ROMS are the same for P1000, P1000L and P1000C.
@cdesai, can you please correct me if wrong?
Click to expand...
Click to collapse
P1000, P1000L and P1000N - the C version is a different beast.
Mjoelnir77 said:
P1000, P1000L and P1000N - the C version is a different beast.
Click to expand...
Click to collapse
I just verified, indeed it is a device for a different region.
Thank for the heads up.
Most likely the only requirements are the drivers for the region specific hardware, besides that it should be the same.
Hi!
First of all, thanks for this great new rom. Its feel like faster than 10.1 (maybe because of the factory reset)
My only problem i cant take PicSphere photos with Focal. The logcat is attached.
Thanks again!
As far as I know Focal is still in a very early stage. It has bugs on every 10.2 rom.
Sent from my GT-P1000 using xda app-developers app
cdesai is always the earliest bird My question is how to enable root permission, I think this is critical to all fans!
bravokylee said:
cdesai is always the earliest bird My question is how to enable root permission, I think this is critical to all fans!
Click to expand...
Click to collapse
Go to Setting -> About tablet -> Click 7 times on Build Number to enable developer options, then set Root access there...
bravokylee said:
cdesai is always the earliest bird My question is how to enable root permission, I think this is critical to all fans!
Click to expand...
Click to collapse
Try to flash superSU 1.5.1
send from my Nexus
Installed this in my P1000. Working fine. Flashed this over 4.2.2 by alroger's and then flashed gapps for 4.3. Awesome. Thanks for the developer.
Sent from my GT-P1000 using xda premium
I can't connect to home WiFi network, even after several attempts it still reports only:
The problem with the verification
Thanks in advance for any help
Wiped Dalvik and formatted cache and system and then installed that directly over the Alroger from 10th of August with the march gapps (there are newer ones - loading them now). Everything works and no bugs so far (only missing the tweaks from the alroger rom).
You only get root after becoming a delevoper like described above. But it works then without any third party stuff or any problems.
Wow! Just installed this to test for the weekend, but I don't think I have to go back I also flashed over alrogers last build (full wipe), and it's working very stable ever since. What is experimental about it?
Just one question, what governor and scheduler do you prefer cdesai (or others)? Is the standard on demand and row advisable, because it's pre-configured like that, or is that a misunderstanding?
TRIM Support?
Hi, Thanks for this. Does anyone know if TRIM Support is enabled in this version? Does it help out?
Thanks.
why not p1c?looking forward.....
polycentric said:
why not p1c?looking forward.....
Click to expand...
Click to collapse
+1 , If I'm not interested in connecting it to the Sprint CDMA network and only use it as a WiFi tablet is it OK to use the GSM ROM anyway if i only use the wifi? I always wondered that.
If by "bootup screen looks weird for a few seconds" you mean that the Cyanogenmod logo is stretched horizontally and you can only see the word "Cyanogen", I've been having that since I first flashed CM10, even the stable builds.
As for the ROM itself, it's nice and fast, but battery life is a *****. I know it'll get better, of course, so I'll just stick with this.
For 4 weeks ive been looking at KK and playing with source... 4.4 images Build (ota zip fails)
4.4 images are building im coming here for developers help on getting this rom working
i will continually post here my sources (this is an awesome forum) and my progress as i go on.. been at this for over 4 weeks developing my first rom...
this post will get more colorful and easier to read over time:
Below is a quote from my google+ post on Xoom Community (join it.. its a great place)
STATUS UPDATE:
Xoom Wifi - LIFESTREAM ROM by LOGMD
Build 17 - Failed BUT we have:
-boot.img
-system.img
-kernel (supposedly)
I have managed to extract the system.img into a flashable Zip... but i KNOW the permissions are F*%#ked
I installed boot.img manually using fastboot but its left me in bootloops (not actually getting to the boot animation, looping on the moto logo)
i flashed the 4.2.2 EOS4 BigPart image because its compatible with the new partition layout and it doesnt bootloop... but it also doesnt get to bootanimation either...
BUT it did respond to ADB devices and came up as unauthorized device so obviously when i ADB SHELL it says device unauthorized...
I THINK that i need to build the boot.img with the BigPart patch but im not sure even if the kernel is just not working properly. if ive built it properly or whatever...
IF ANYONE knows any xoom developers or you are a xoom developer and know how to build kernels on a version of android thats not supported officially or if you think you could help me out then im all ears
Click to expand...
Click to collapse
BIG THANKS to the BigPart & 4.3/4.4 dev thread (will add links later) would have been stuck at one of the many roadblocks if it wasnt for these people!
we are getting closer to getting a rom working i can feel it! lets make it happen! loving how live the threads are in this forum for the xoom!
PROGRESS
I will update here the overall progress towards a working rom WHEN i get time as work can get very busy. I will not be selfish and steal peoples ideas if they are the ones who invented it then i will give credit where it is due, and it is possible that this rom could never be built or someone beats me to it. I may end up collaborating with someone with more experience on thier rom but ill do my best to get an edition of my own working.. IF all fails for now with 4.4 i will spend time on a 4.2 rom/kernel
DISCLAIMER
I (LOGMD) 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software. In saying that Enjoy a respectful development environment, expect no ETA's and help me where necessary
REPARTITION
SYSTEM.IMG
BOOT.IMG (kernel, ramdisk etc)
THREADS OF LIFE (words stolen from Shadows Fall Album)
This is where you and I should use as a starting point for homework using the communities are a great way to learn the newest up to date developments! I do not read fiction books but I sure as hell read technology!
GOOGLE+
+LOGMD | +XDADevelopers | +XoomOwners
XDA-Forums
BLOG
OTHER (follow me)
Twitter | Facebook
I wish you luck. As your skill and luck is our luck.
Sent from my Xoom using XDA Premium HD app
subbed! anticipating great things!
way to be!! Super excited. Need guinea pigs? I'll help
sbeaber4 said:
way to be!! Super excited. Need guinea pigs? I'll help
Click to expand...
Click to collapse
ill start uploading some system img zips soon. see if i can take anything more out of android that is not essential to makeing it work i.e. NO BROWSER NO PLAY STORE everything gone, i was told by another developer they have managed to get the rom small enough for fastboot (~251MB) so ill try the same so it will be easier to flash!
I stupidly did not reserve posts so heres one more
boot.img
For the kernel, why don't ask to ElementalX ?
If we have a system.img but it's to large to flash through fastboot,
thinking out loud but could we get it connected via adb in recovery and do the dd if=/location/of/system/img of=/dev/block/mmcblkpXXX
would that work?
---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------
Another thought on trying to get the img into a flashable zip, not sure if you've heard of dsixda kitchen! http://forum.xda-developers.com/showthread.php?t=633246
I've used it before in regard to the Xperia T and it's compatible with many devices and can turn system imgs into zips I believe
If using bigPart Kernel than you can not use fastboot as fastboot does not know the new partition layout.
Incredible news!!
Love to see KitKat on Motorola Xoom!
Sent from my Xoom using Tapatalk 4
Have you tried using Motorola's mfastboot.exe? I've had to use that instead of the regular fastboot to flash large system images to my Moto X, I'm curious if it would work for the repartitioned Xoom. Apparently it breaks the image down into two parts to get around size limitations with the regular fastboot.
I uploaded it here if you'd like to test it out
TWRP
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
pots22 said:
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
Click to expand...
Click to collapse
I managed to shrink to 209 MB which flashes =] it may not have anything but core android but thats all we care about right now i dont care about FC... next is kernel follow this link will be more active about kernel updates. im gonna post some nvidia drivers i just found
Elemental-X seems to have updated to beta with support for big partition.
4.4
hawkstorm said:
Elemental-X seems to have updated to beta with support for big partition.
Click to expand...
Click to collapse
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
pots22 said:
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
Click to expand...
Click to collapse
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Cameron581 said:
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
hawkstorm said:
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
Click to expand...
Click to collapse
That makes no sense he removed apps and was on a parted kernel
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Experimental X was just updated to support Bigpart. It is not the update that Logmd is looking for to support KK 4.4. The new kernel needs a lot more upgrading involving drivers for the Tegra Chip.
They are probably trying to see if they can get KK 4.4 working without bigpart first. And if successful it can blossom from there with ROM developers taking advantage of BigPart to create more custimized ROMS.
4.4
Cyanogenmod launch from yesterday and today a lot of ROM CM11 4.4.2
http://download.cyanogenmod.org/
All ROM don't exceed 200 Mo, so i'm really not sure about the necessity of Bigpart.
Introduction
Temasek is based on Cyanogen Mod rom ,and added more feature than Cyanogen Mod
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, or dead SD cards,
* nuclear war, penguin invasions or that you are getting fired because the alarm app failed.
* before flashing it! YOU are choosing to make these modifications, and
* If you point your finger at me for messing up your device, I will laugh at you. Hard
*/
Samsung Galaxy Fame device-specific source code :
Devicehttps://github.com/wulsic/android_device_samsung_nevisp
Kernel: Vendor: [/COLOR][URL="https://github.com/wulsic/android_vendor_samsung_nevisp"]https://github.com/wulsic/android_vendor_samsung_nevisp
Patches :
Most patches by pawitp: https://gist.github.com/pawitp/88a1d4514a0734c866c7(replace each time it says CAPRI with RHEA)
Icu4c compat for working rhea EGL driver: https://gist.github.com/Flex1911/47a9515fc482d5551a85
audioflinger patch for support old API https://gist.github.com/Flex1911/79969e4bfe06cf91b647, https://gist.github.com/Alonso1398/9eede1c631c2a88ec2fc and https://gist.github.com/Alonso1398/5d9dbb0f0eb5cc9cf25a
Not Working:
Same like CM12.1
Working:
everything is working except at Not Working list
Installation instructions
first,u need CWMR 6.0.4.9(by corsicanu or wuilsic) / TWRP 2.8.7.0
Download the zip
WIPE DATA/FACTORY RESET
Format/System
flash the rom zip from recovery
Flash gapps package or light gapps.
Reboot
Connect your phone to your pc and use adb to logcat and report it here.
Downloads
Please don't mirror to any site ,cuz everyone must see this thread and read the discussion
Please give a proper credit and thread link if you are publishing any article, video or anything related to this ROM
don't use adfly or shorten link to made money from our hard works
ROM
Android File Host
Gapps
you can use Open Gapps or any gapps ,choose PICO <because it's just include Play Store and Google Framework
How do I logcat?
See this thread how to logcat it's very easy, I suggest to be also newb friendly to use the logcat apps.
http://forum.xda-developers.com/showthread.php?t=1726238
How do I enable Dual SIM?
To enable or disable, run the following command from adb or terminal emulator and then reboot. SIM Settings can then be found in Settings -> Multi Sim Settings
Option 2 which is the fastest one is to check out this app made by @xenon92 it also has a nice UI, I hope it works on the fame else I will remove the link again:
https://github.com/xenon92/multisim-toggle/releases
Enable:
Code:
su
setprop persist.radio.multisim.config dsds
Disable:
Code:
su
setprop persist.radio.multisim.config none
Note that Dual SIM mode currently has the following limitations:
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
The QuickSettings tile will display the status for the currently selected SIM for data
There is no arrow activity indicator in the status bar.
Changing 2G/3G network mode using the QuickSettings toggle is not supported, only do it from Settings.
Changing 2G/3G mode in Settings may show too many options if the language used is not English. If more than 3 options is shown, only use the 3 top options (which will be WCDMA only/GSM only/WCDMA preferred regardless of the actual label shown).
3G may not work properly if Dual SIM mode is enabled with only 1 SIM inserted
Cannot set different ringtone for each SIM
Baseband version not displayed in Settings
Credits:
Google for Android before Cyanogenmod will slice them off.
The Android community for their contributions
Cyanogenmod for their Branch
@wulsic for his works! for this device to make a good device tree based on
@dhinesh77 for his Corsica source which I use as base.
@pawitp for Patches
@xenon92 for collection and patch apply script
karthick mostwanted for some kernel tweaks/other stuff.
@corsicanu
Ramsudharsan
@happyhere :*
@Alonso1398 for the patches
@flex1911 for the patches
@citrusb for fixing build kernel problem
@temasek who make temasek rom
@arter97 of course,he help temasek to made the best one
And all the betatesters and the fame community peope which are just too many to mention.
XDA:DevDB Information
Temasek 5.1.1, ROM for the Samsung Galaxy Fame
Contributors
faizauthar12, Wulsic, Karthick Mostwanted
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: latest firmware
Based On: Temasek
Version Information
Status: Beta
Current Beta Version: 20151207
Beta Release Date: 2015-12-07
Created 2015-12-07
Last Updated 2015-12-07
reserved
I'm trying to flash now, but it seems to be going much slower than usual (tried on cwm and twrp latest versions). Stuck at "detected filesystem ext4 for dev/block/mmcblk0p9". Any solutions? (same issue with both recoveries)
Update: It takes really really long, but suddenly it boots Its really smooth, thank you @faizauthar12
It has more applications is nice and soft
it does not work
the browser goes black
The camera records but the videos come in green
Sound Recorder does not work
the gapps take a long the phone
It's a great job thank you very much for your effort
U know ,the size of temasek ,500 mb : v ,so yeah it will take longer than usual
Please do something for dual sim
bhkparmar said:
Please do something for dual sim
Click to expand...
Click to collapse
give me ur RILD from stock
system/bin
faizauthar12 said:
give me ur RILD from stock
system/bin
Click to expand...
Click to collapse
I have already uploaded System/Bin from my stock rom in Cm12.1 threads, link: http://forum.xda-developers.com/showpost.php?p=63851534&postcount=123
deepakpop said:
I have already uploaded System/Bin from my stock rom in Cm12.1 threads, link: http://forum.xda-developers.com/showpost.php?p=63851534&postcount=123
Click to expand...
Click to collapse
lol xD
forget that
SIM is not working what to do???
torgashkin said:
SIM is not working what to do???
Click to expand...
Click to collapse
Not sure what model you have, but on my phone (s6810), I simply changed to single sim and voila, it works
there is a possibility of
Slim ROM 5.1.1
CARBON ROM
as has the Pocket Neo?
can't flash this rom
I try to flash this on my fame with cwmr 6.0.4.9, but while i flash this rom, i always got "error at extsdcard/rom.zip
instalation aborted
(Status 7)"
Can you help me.
Sorry for my bad english
YDroid521 said:
I try to flash this on my fame with cwmr 6.0.4.9, but while i flash this rom, i always got "error at extsdcard/rom.zip
instalation aborted
(Status 7)"
Can you help me.
Sorry for my bad english
Click to expand...
Click to collapse
Already tried CWMR 6.0.5.1 / TWRP?
Sent from my ferrari using XDA Labs
faizauthar12 said:
Already tried CWMR 6.0.5.1 / TWRP?
Sent from my ferrari using XDA Labs
Click to expand...
Click to collapse
I also use TWRP 2.8.7.0 but after I flash this rom and reboot, my phone do not want to boot, then i open twrp again and flash another rom Then reboot, its fine.
Can you tell me whats wrong with this, because i really want use this rom or tell me correct way flash with twrp.
YDroid521 said:
I also use TWRP 2.8.7.0 but after I flash this rom and reboot, my phone do not want to boot, then i open twrp again and flash another rom Then reboot, its fine.
Can you tell me whats wrong with this, because i really want use this rom or tell me correct way flash with twrp.
Click to expand...
Click to collapse
how long u wait it ??
it takes more than 30 minutes
faizauthar12 said:
how long u wait it ??
it takes more than 30 minutes
Click to expand...
Click to collapse
I wait 30 minutes or more. Can you tell me step by step flash this rom with twrp because this is first im using twrp
YDroid521 said:
I wait 30 minutes or more. Can you tell me step by step flash this rom with twrp because this is first im using twrp
Click to expand...
Click to collapse
i think
u already read the first post bro
wipe>advance wipe
ROM download page says :
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access
waheka said:
ROM download page says :
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65918888&postcount=345
CyanogenMod 11 for the Samsung Galaxy Ace II x (GT-S7560M) and Galaxy Trend (GT-S7560)
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.
*/
Not working:
FM Radio
Bugs:
*Camera only 3.2 megapixels (2048x1536)
*Uploading/sending videos via Instagram,Facebook and Facebook Messenger fails
Downloads:
Latest Build CM11 April 23th 2017
CHANGELOG
*Optimized dalvik
*Switched to my kernel test branch
*Miscellaneous fixes
Latest EXPERIMENTAL build: ExperimentalCM11 April 26th 2017 (by @motoralbi)
EXPERIMENTAL-CHANGELOG
*Work on bionic
*Switching to faster math functions
XposedFix
Download XposedFix.zip and flash it to get xposed working.
I have to tell you that this fix is a pretty much a big security breach,and this hack will never be incorporated in to my builds.
Flashing this fix WILL REGRESS ALL THE DALVIK CHANGES we've done so far.I do not provide support for issues regarding xposed.
Installation Instructions & Requirements:
1. Copy zip packages (ROM) to an SD Card
2. Enter recovery mode
3. Choose "install zip from sdcard"
4. Select "choose zip from sdcard" and locate the ROM zip package
5. Confirm the installation by choosing "yes"
Recoveries:
I recommend you use TWRP 3.0.2 by @kengnatural
You can also flash by codename13s TWRP 2.8.0.1
If you do not have one installed, please install one of them prior to installing the ROM!
IF YOU WANT TO USE GAPPS WITH ANY OF MY BUILD,FORMAT /SYSTEM PARTITION,FLASH ROM,BOOT IT AND THEN GO BACK TO RECOVERY AND FLASH GAPPS YOU WANT!(DONT FLASH GAPPS BEFORE FIRST BOOT!!!!)
IF YOU DONT DO THIS YOULL GET THE MESSAGE THAT SETUP WIZARD STOPPED WORKING!
THIS GOES FOR EVERYONE!
I recommend you always do a CLEAN FLASH of all my builds
Little notice:
This rom is ported version of CM11 for s7562.
I would like to say thank you to all people that are/were working on this rom:
@jonypx09
@Codename13
@m4jonez
@KlinkOnE
@kengnatural (not only for work you are doing but for mentoring me too!!)
@oF2pks (for making patches and allowing us easily to add wakelock blocker to CM11!)
guys who test my builds and report everything:
@noobcoder
@F4uzan (providing moral support)
@GreekDragon (providing moral support,thanks my giros brate)
Cyanogenmod Team
Google
Maintainers:
@pavlepiramida
@motoralbi
If you find any new bugs please report and try to make a logcat of it or at least provide a detailed explanation (what happend,what were you doing,how was the phone behaving) so I can recreate that bug myself and try to fix it!
My Github account: https://github.com/pavlepiramida
FrankenKernel repo: https://github.com/pavlepiramida/FrankenKernel
Tips for usage
For best experience I suggest you:
*set your CPU Governor to lulzactive
*set your I/O Governor to zen or CFQ
*If you dont use memory hungry apps disable KSM (it will improve your battery life just a little bit and performance)
*go to Settings/Developer options and reduce all animations to 0.5
*disable all touch sounds
*turn off Daydream in Settings/Display & lights
*turn off profiles if you do not use them
*go to Settings/Privacy and disable CyanogenMod statistics reporting
*also while you are there if you are not using Blacklist disable it
Flashable Samsung stock ICS sounds : https://www.androidfilehost.com/?fid=745425885120704205
All my builds will support @microg patch for signature spoofing
To learn more about this and why its in this rom check out his thread
[APP] microG GmsCore - lightweight free software clone of Google Play Services
"Setting up Microg" on kylessopen devices by @Zeroblood
Here you can get help for setting up Microg.
my androidfilehost folder with all build so far: https://www.androidfilehost.com/?w=files&flid=156391
Hey Pavle,
Why do you suggest turning CM stat reporting off ? I understand it's not very useful, but is there a real performance gain, or just a marginal one ?
breversa said:
Hey Pavle,
Why do you suggest turning CM stat reporting off ? I understand it's not very useful, but is there a real performance gain, or just a marginal one ?
Click to expand...
Click to collapse
For me that is always off as it is pinging their servers on every boot and sometimes causes a wakelock.
I did notice a small boost in performance but that could very well be a placebo.
Disabling does not harm you,so why not turn it off
Haha, alright, I did not know about that potential wakelock.
BTW, I'll have my friend try out one these builds tomorrow to try and make that wifi work again. I'll keep you informed !
breversa said:
Haha, alright, I did not know about that potential wakelock.
BTW, I'll have my friend try out one these builds tomorrow to try and make that wifi work again. I'll keep you informed !
Click to expand...
Click to collapse
Im sure it was just a corrupt download.
If not we'll think of something!
can i install it with cwm 5.6?
tomyjeje said:
can i install it with cwm 5.6?
Click to expand...
Click to collapse
nope
flash TWRP (as I recommended TWRP 3.0.2 by kengnatural)
Hi! A couple days ago I saw there was a link in this thread to a version of this ROM with the Omni kernel, which would fix the wifi problem in Latin American devices. Now it's gone.
What happened? Did that fix not work out? I was planning to try it this weekend...
Thanks!
mincem said:
Hi! A couple days ago I saw there was a link in this thread to a version of this ROM with the Omni kernel, which would fix the wifi problem in Latin American devices. Now it's gone.
What happened? Did that fix not work out? I was planning to try it this weekend...
Thanks!
Click to expand...
Click to collapse
I had to remove it as it was going into bootloop after flash on new build.
I have to test it a bit more.
It works for my July build but in September I changed few things that apparently dont play well with codebame13 kernel.
If I dont sort it out,Ill upload whole July rom with his kernel packed in it!
Thanks for your work. I'm looking forward to it.
By the way, in case it's relevant, a while ago I tried your "fixWifi.zip" from an old release, and it wasn't working for me. (It disabled bluetooth like you said it would, but it didn't restore wifi.) I don't know if that has anything to do with how the new release will work, but I'm telling you just in case.
mincem said:
Thanks for your work. I'm looking forward to it.
By the way, in case it's relevant, a while ago I tried your "fixWifi.zip" from an old release, and it wasn't working for me. (It disabled bluetooth like you said it would, but it didn't restore wifi.) I don't know if that has anything to do with how the new release will work, but I'm telling you just in case.
Click to expand...
Click to collapse
Hah it wasn't working for anyone,few important files were missing but I was to lazy to remove it from androidhost :/
hey pavle, did you try to fix wifi on this build or just camera?
the wifi still not work, i take a logcat but there is no error about wifi.
https://drive.google.com/open?id=0B8oAXWJSnBcvZ2xMczloT3M3cTg
do you know why?
noobcoder said:
hey pavle, did you try to fix wifi on this build or just camera?
the wifi still not work, i take a logcat but there is no error about wifi.
https://drive.google.com/open?id=0B8oAXWJSnBcvZ2xMczloT3M3cTg
do you know why?
Click to expand...
Click to collapse
Thx for Logcat,Ill see if there's something new in it!
Just a quick question,did you logcat while turning wifi on?
EDIT
Dude your logcat is an empty .txt file....
Did you remove it from Drive?
Process error, on my gt s7560.. how to fix? pls
metodding said:
Process error, on my gt s7560.. how to fix? pls
Click to expand...
Click to collapse
redownload rom
pavlepiramida said:
redownload rom
Click to expand...
Click to collapse
is not resolved
metodding said:
is not resolved
Click to expand...
Click to collapse
Strange,Im having trouble downloading it myself....
Seems that its a issue on androidfileshost side,sadly nothing I can do.
I'd suggest,if you are downloading it via phone,to try and download it via PC (Firefox,Chromium,Chrome......etc) and manually move ROM to SD Card,as sometimes theres an issue with browsers for phone.
Refresh few times download page and try again,meanwhile Ill send an email to androidfiles staff to see if they are doing anything on servers (maintenance or something else).
Thanks for report and I hope it gets sorted out soon!
pavlepiramida said:
Strange,Im having trouble downloading it myself....
Seems that its a issue on androidfileshost side,sadly nothing I can do.
I'd suggest,if you are downloading it via phone,to try and download it via PC (Firefox,Chromium,Chrome......etc) and manually move ROM to SD Card,as sometimes theres an issue with browsers for phone.
Refresh few times download page and try again,meanwhile Ill send an email to androidfiles staff to see if they are doing anything on servers (maintenance or something else).
Thanks for report and I hope it gets sorted out soon!
Click to expand...
Click to collapse
Always run the download from PC, tried several times .. the error is present equally
metodding said:
Always run the download from PC, tried several times .. the error is present equally
Click to expand...
Click to collapse
Are you using any ADBlocker on browser?(If you are disable it)
Are you using a VPN?(If you are disable it)
Have you tried other mirrors to download from?(Try other mirrors that are available,I suggest Quebec mirror )
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is an unofficial TWRP 3.x build for the Huawei Honor 3C (h30u10/H30-U10)
This project is abandoned! I'll reopen the thread if I have any progress in the future... If you want anything from me you can contact me in my email address, in Telegram (@iamnotstanley) or in private message.
Only use this binary with your own responsibility, and please read the "known issues" list.
Working:
Everything, except the things in the "known issues" list.
TWRP functional checklist, but in this list not everything applies for our device
Known issues:
flash/restore image (boot&recovery) (installing with a zip [if you're using codelover's fixed update-binary] and backup working correctly) **need help **
Download:
Latest and older versions: See the DevDB Downloads page or click here. (Mirror)
Install:
You can install this recovery in 4 way:
Using an another version of TWRP: install the downloaded zip
Using an another version of TWRP: extract the zip and flash the image
Using SP Flash Tools: extract the zip and flash the image
Using Flashify or other flashing app: extract the zip and flash the image
Revert easily to codelover's TWRP:
Download from here the UPDATE-TWRP-2.8.6.0_H30-U10.zip or the UPDATE-TWRP-2.8.6.0_V2_H30-U10_EU.zip and install it inside the TWRP, after that if you reboot to recovery, you will see the old version.
Changelog:
TWRP changelog: here
Device changelog:
3.1.1-0:
Updated to the latest version.
We still have the the "image flash" problem!
3.1.0-0:
First release for Huawei Honor 3C (h30u10)
Built with omnirom android-5.1 tree
Prebuilt kernel: EU B306 (3.4.67)
Screenshots: See the DevDB Screenshots page or click here.
Credits:
iamnotstanley
codelover
carliv for his bootimg module
MSF-Jarvis for his initial device tree
TeamWin team
omnirom team
XDA:DevDB Information
TWRP for Huawei Honor 3C, Device Specific App for the Honor 3C
Contributors
iamnotstanley, codelover, carliv, MSF-Jarvis, TeamWin team & omnirom team
Source Code: https://github.com/iamnotstanley/android_device_huawei_h30u10/tree/android-5.1
Version Information
Status: Abandoned
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-05-13
Created 2017-04-01
Last Updated 2018-01-29
Reserved
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
hassanjavaid8181 said:
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
Click to expand...
Click to collapse
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
iamnotstanley said:
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
Click to expand...
Click to collapse
really appreciate your efforts:good:
good luck
Bro can we flash magisk by this version.
mnumaher said:
Bro can we flash magisk by this version.
Click to expand...
Click to collapse
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
iamnotstanley said:
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Click to expand...
Click to collapse
Thanks.
Is touch working correctly in this version?
mnumaher said:
Thanks.
Is touch working correctly in this version?
Click to expand...
Click to collapse
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Rayquaza said:
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
Click to expand...
Click to collapse
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
iamnotstanley said:
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
Click to expand...
Click to collapse
Ty bro it's working absolutely fine.
When we will be able to flash img.
mnumaher said:
Ty bro it's working absolutely fine.
When we will be able to flash img.
Click to expand...
Click to collapse
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
working fine cheers!
iamnotstanley said:
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
Click to expand...
Click to collapse
hi and great work, thanks for that
codelover maybe have a patch for that, past time he say i forget it, but can help you to know how solve that
Hi @iamnotstanley, to answer your question:
If i recall correctly i did explained about the problem in my thread earlier - the problem lies on 3C KK kernels. (MTK variant only)
H30-U10 stock KK kernels do not permit writing to the boot partition (/dev/bootimg) directly, the partition is mounted as read only.
Interestingly, there are some ported recoveries out there that doesn't work, and user doesn't even know about it. (eg: ROM appeared to be flashed successfuly but failed to boot because boot.img didn't get through, missing assert() to stop)
If you find a working H30-U10 recovery that can write to boot for 3C, it's likely using JB kernel or KK kernel from other 6582 compatible KK kernel, not sure if someone has compiled a fully working 3C kernel.
With JB kernel, you will be missing SELinux & some other features, while KK kernel from other device is dangerous IMHO, unless you are 100% sure it's compatible, sometimes i wonder whether those permanently bricked 3C with partition error were using these 'patched' recoveries...
My TWRP 2.8.6.0 has been customized to deal with this, i wrote a few C custom functions for twrp, it works like this;
1) read the partition table while flashing, loop through until you find the details for target partition that you need to write.
2) calculate the size and offset to write (you will need to convert the hex to int, then some math again to get the bs, skip, etc value for dd)
3) use 'dd' to write directly to mmcblock0, instead of C fwrite to the specific built-in partition mount point, eg: /dev/bootimg
Wish i could help more, unfortunately i don't have 3C data with me anymore (hdd crashed), and my work is killing me.
Good luck with that!
codelover said:
Hi @iamnotstanley, to answer your question:
...
Click to expand...
Click to collapse
Hi!
Thanks for your answer, I really appreciate your help.
So the problem is mainly in the kernel. I don't think I can fix this, but I'll try after my exams.
TWRP updated to 3.1.1-0
Hello guys!
I updated the TWRP to 3.1.1-0 yesterday. Unfortunately it still have the image flash issue. If you're interested you can download from the DevDB Downloads page or the Github mirror.
Huawei Honor 3C H30-U10
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
SHBhatti said:
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
Click to expand...
Click to collapse
Try rooting with root applications such as Baidu root and etc.
TamaziAce said:
Try rooting with root applications such as Baidu root and etc.
Click to expand...
Click to collapse
I was Try to root with king root, king root said that your device is rooted successfully but root checker said no root???? what should i do now..?