[Ics] unofficial cm9 by jokersax 8/23/2012 - Motorola Photon 4G

This Kanged CM9 Alpha build is a free, community built, aftermarket firmware distribution of Android 4.0 (ICS), which is designed to increase performance and reliability over stock Android for your device.
Code:
**[B][COLOR="Red"][SIZE="3"]Disclaimer[/SIZE][/COLOR][/B]** * these are alphas so understand that means things are broken * * I am not part of the Cyanogenmod Team * * 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. * Change Logs Disabled during alpha, please read thread.
[B][U][SIZE="3"]Stages[/SIZE][/U][/B]
* [B]Alpha[/B]- means something major is broken. Goal is to get major stuff working
* [B]Beta[/B]- means little things are still broke but most big stuff is fixed. Goal to clean up code and fix little issues so we can submit to cm to become official
* [B]Stable[/B]- official cm rom.
* [B]After stable[/B]- tweaking, Also adding features.
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.
Instructions:
First time flashing CyanogenMod 9 to the Motorola Photon 4G?, or coming from another ROM?
Root the Photon.
Unlock the Bootloader.
Flash the recovery on my site in cwm
Perform a NANDroid backup of your current ROM.
Flash This ROM.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 9?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod.
Flash gapps.
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
ROM: Link
Latest version: check site
Click to expand...
Click to collapse
Gapps: Link
Latest version: check site
Click to expand...
Click to collapse
Other
New touch based installer at jokersax.com no more confusing wipes or methods of flashing.
Credits:
joxersax11 -King Kollaborator iservin -Wiki Master cybik xboxfanj turl shabbypenguin ebbinger_413 sky24987 DethMetalz69 cougarcougar Focus.lau mrinehart93 Cyanogenmod Team koush/romracer/calkulin - 5027pre3 Recovery shabbypenguin - AIO Root the2dcour - Unlocked bootloader ranmasaotome510 - updated OP
Click to expand...
Click to collapse
The Photon dev team and turl would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

Mighty ambitious but good luck!
I'm sure many will offer their help.

I've been playing with a serious Alpha of cm9 on the thunderbolt. Thanks you Lau

jokersax11 said:
first of all thank focus.lau
http://bbs.189store.com/forum.php?mod=viewthread&tid=15563&page=1&extra=#pid511942
this will start off using his version. eventually i will get source downloaded(hopefully today), and ill begin getting all the bugs worked out.
this version was provided by focus.lau, i modified it to make it semi usable. 99% of the credit to this point is all focus.lau! i simply fixed a few issues preventing boot up using stateside photons. it can be modified in the same way miui was by adding parts from this and that and getting alittle more function.
my plans are to get cm9 source downloaded and find time to bang out all the necessaries to get cm9 fully working. its going to be a long road but we gots the cm9 before 2012!
currently uploading/fixing data/phone
Click to expand...
Click to collapse
Joker, you are da man!

On the ball joker!! Thanks!!
Sent from my MB855 using XDA App

ok i gotta get some sleep, cm9 source issues are now resolved so i should be able to start building in a day or so.
i this modified this build so it wasnt in chinese and so it would flash on our photons with our recoveries.
you guys can tweak and mod and try to get this build going all you want. im uploading so be patient if its not there yet.
have fun.

The op is questionable
Posts by wdl900 edited on 2011-12-27 20:36
Pro: you are still not official 4.0 for the news of trouble? You still waiting for official cm9 it? ? Tell you that from today you do not have to wait, now let you taste the taste of 4.0, because we do a large egg, ha ha, did not ask you served? I was served, and sincerely thank the selfless dedication of the egg show! !
Since there is no official version of the kernel, this release is trial version, not the complete version, but it was enough, because we have taken a historic moment Egg a ~~~~~~~~~~~
Special thanks to XDA here on FXP, CM team, as well as Pharaoh, show video, the child generation to the show, and all who support the show eggs, axes have you even more exciting! ! !
The version of the source code is compiled based on cm9, moto photon official kernel, version experience, as well as imperfections ~ ~ ~ ~
Note: This version of the version to be perfect in CM7, based on the upgrade (7.2 to be a perfect version of the first brush, brush after the first restart, and then transferred to recovery under the brush CM9) brush cm9 card before, do not wipe, otherwise the phone will FC, we remember ah, as to the issue of FC, eggs will be perfect after the show, we can support a ~~~~~

That's really interesing. Going to flash it before 2012.
Can anyone provide info about things that work and that don't?

I have to say, Chinese are great!! LOL, I have flashed this rom, the biggist problema are camera and sd card, and games often fcs, most of the time they cannot be opened at all, but it's a gaint step towards cm9. I appreciate your and those developers' work very much. together we can build our perfect cm9. I am testing it right now.
Sent from my MB855 using XDA App

dxl880517 said:
I have to say, Chinese are great!! LOL, I have flashed this rom, the biggist problema are camera and sd card, and games often fcs, most of the time they cannot be opened at all, but it's a gaint step towards cm9. I appreciate your and those developers' work very much. together we can build our perfect cm9. I am testing it right now.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Whats wrong with the sd card and have you tried a 3rd party camera app?

it doesn't recognize sd card. both internal and external, but the focus solved the problem by adb push the file vold.fstab to system/etc, see
http://bbs.189store.com/forum.php?mod=viewthread&tid=15572&extra=page=1
As for camera, i believe it is driver related.
Sent from my MB855 using XDA App

Looks like I wont be using this till my day off
Posts by editing focus on 2011-12-27 20:22
First to download my attachment. vold.fstab.apk (2.29 KB, Downloads: 42) If there is no ADB tool, prior to your mother and then download a good degree, and then placed in c: \ windows \ system32 under.
After downloading, remove the. Apk suffix.
WIN + R and enter cmd into the command line, execute the following command sequence:
adb push vold.fstab (if not the same level directory, please fill out the complete path, such as c: \ vold.fstab) / mnt / emmc / / push the file you downloaded to the root directory emmc
adb shell / / entering the shell
su / / get root privileges
mount-o remount, rw-t yaffs2 / dev/block/mtdblock3 / system / / mount the file system as read-write
cp / mnt / emmc / vold.fstab / system / etc / / / replace the previous file
exit
exit
adb reboot / / restart
This last statement, the phone automatically restart after you can get.
If you do not know the meaning of the above command a one executive put it. / / .. This is a comment. Meaning to tell you. Command is above the red part! !

mount-o remount, rw-t yaffs2 / dev/block/mtdblock3 / system / / mount the file system as read-write
Click to expand...
Click to collapse
this concerns me... for someone who compiled cm9 how does he think we have yaffs anywhere on this phone? or mtd partitions? this is an emmc device.. :/
and this rather spoils the fun :O i have had cm9 source down
as i said i liked being lazy but i havent been

finally uploaded, commence flashing.

What do the yaffs pertain to and what is a eemc device?
I could google it(and I will) but I'd rather you explain it
jokersax11 said:
finally uploaded, commence flashing.
Click to expand...
Click to collapse
You did not sleep for long lol

i forgot something
wipe wipe wipe wipe wipe
also dont worry about that version on that site. i slightly modified this one, you guys can modify some more while i sleep if you like.

Before you sleep what was modified?
SD card mount and camera or no?
I'd unlock if those 2 were done

AJC9000 said:
Before you sleep what was modified?
SD card mount and camera or no?
I'd unlock if those 2 were done
Click to expand...
Click to collapse
nope i made it english and removed some radio edits. also i made it flash properly on our phones. for a test build that is

shabbypenguin said:
this concerns me... for someone who compiled cm9 how does he think we have yaffs anywhere on this phone? or mtd partitions? this is an emmc device.. :/
and this rather spoils the fun :O i have had cm9 source down
as i said i liked being lazy but i havent been
Click to expand...
Click to collapse
if your site goes down im sorry

AJC9000 said:
Looks like I wont be using this till my day off
Posts by editing focus on 2011-12-27 20:22
First to download my attachment. vold.fstab.apk (2.29 KB, Downloads: 42) If there is no ADB tool, prior to your mother and then download a good degree, and then placed in c: \ windows \ system32 under.
After downloading, remove the. Apk suffix.
WIN + R and enter cmd into the command line, execute the following command sequence:
adb push vold.fstab (if not the same level directory, please fill out the complete path, such as c: \ vold.fstab) / mnt / emmc / / push the file you downloaded to the root directory emmc
adb shell / / entering the shell
su / / get root privileges
mount-o remount, rw-t yaffs2 / dev/block/mtdblock3 / system / / mount the file system as read-write
cp / mnt / emmc / vold.fstab / system / etc / / / replace the previous file
exit
exit
adb reboot / / restart
This last statement, the phone automatically restart after you can get.
If you do not know the meaning of the above command a one executive put it. / / .. This is a comment. Meaning to tell you. Command is above the red part! !
Click to expand...
Click to collapse
wow. umm to everyone else, please just use root explorer/regular adb/unzip add rezip.

Related

[REF][Patch] Malware Exploit for all pre-Gingerbread phones

I'm posting this here for visibility for Fascinate users and ROM developers. In the following thread you can find all the information, as well as how to download and apply the patch files:
http://forum.xda-developers.com/showthread.php?t=977154
I'm sure it will be incorporated into the major ROM's soon. However, if you install apps from unverified sources, or regularly try out new apps from the market, you shouldn't wait.
Patching via CWM:
imnuts said:
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Click to expand...
Click to collapse
Patching via ADB or terminal emulator:
Alternatively, probably the quickest way (and if you copy and paste, the most fool-proof) if you are rooted and know how to use ADB, is to open up a command prompt or a terminal emulator on the phone to access the adb shell. If on a PC, type:
Code:
adb shell su
Then type the following lines, omitting the $ and # (if you are on a terminal emulator, start here):
Code:
$ su
# mount -o rw,remount /dev/block/stl9 /system
# touch /system/bin/profile
# chmod 444 /system/bin/profile
You are now protected from the current iteration of DroidDream Malware. Consider installing a security program like LookOut to protect against future vulnerabilities.​
Original Post:
Rodderik said:
[Patch][Rom]Malware Exploit for all pre-Gingerbread phones
Who is affected? All phones pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post or use one of the alternate methods down there
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Link to publishers apps here. I just randomly stumbled into one of the apps, recognized it and noticed that the publisher wasn’t who it was supposed to be.
Super Guitar Solo for example is originally Guitar Solo Lite. I downloaded two of the apps and extracted the APK’s, they both contain what seems to be the "rageagainstthecage" root exploit – binary contains string "CVE-2010-EASY Android local root exploit (C) 2010 by 743C". Don’t know what the apps actually do, but can’t be good.
I appreciate being able to publish an update to an app and the update going live instantly, but this is a bit scary. Some sort of moderation, or at least quicker reaction to malware complaints would be nice.
EDIT: After some dexing and jaxing, the apps seem to be at least posting the IMEI and IMSI codes to http://184.105.245.17:8080/GMServer/GMServlet, which seems to be located in Fremont, CA.
I asked our resident hacker to take a look at the code himself, and he’s verified it does indeed root the user’s device via rageagainstthecage or exploid. But that’s just the tip of the iceberg: it does more than just yank IMEI and IMSI. There’s another APK hidden inside the code, and it steals nearly everything it can: product ID, model, partner (provider?), language, country, and userID. But that’s all child’s play; the true pièce de résistance is that it has the ability to download more code. In other words, there’s no way to know what the app does after it’s installed, and the possibilities are nearly endless.
Click to expand...
Click to collapse
The offending apps from publisher Myournet:
* Falling Down
* Super Guitar Solo
* Super History Eraser
* Photo Editor
* Super Ringtone Maker
* Super Sex Positions
* Hot Sexy Videos
* Chess
* ????_Falldown
* Hilton Sex Sound
* Screaming Sexy Japanese Girls
* Falling Ball Dodge
* Scientific Calculator
* Dice Roller
* ????
* Advanced Currency Converter
* App Uninstaller
* ????_PewPew
* Funny Paint
* Spider Man
* ???
Click to expand...
Click to collapse
http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
Now, on to some more details of the virus. We should point out that this vulnerability was patched with Gingerbread, meaning any device running Android 2.3+ should be fine. In other words, if you’re looking to play the blame game (which I’m not, but having read all the comments on the original post, many people are), then there’s plenty to go around. The hole was fixed by Google, but it’s relatively useless since many phones aren’t yet running a version of Android that is protected. It’s noteworthy that some manufacturers released updates that patched the exploit for devices without updating to Gingerbread; unfortunately, it appears that minority is quite a small one.
Perhaps most important is the question of what infected users can do about their situation; unfortunately, the answer is not much of anything. Because the virus opens up a backdoor and can bring in new code at any time, the only way to really rid an infected device of any damage is to completely wipe the device – not exactly the optimal solution, but it looks like the only one available, at least for now.
Finally, Justin notes that ROM developers working with pre-Gingerbread versions of Android can prevent the virus from backdooring in code by putting a dummy file at /system/bin/profile.
Click to expand...
Click to collapse
As you can see androidpolice.com reports on this backdoor and roots and steals personal information. The apps are removed from the market but that doesn't mean they got them all. Attached is a flashable fix as suggested by androidpolice.com
So users can flash this .zip or simply create a blank file called profile and place it in /system/bin/ (developers are encouraged to include this file in future releases. A blank file is not going to affect performance at all)
Alternate methods:
Using 'adb shell' or terminal emulator (should work on any ROOTED phone) as suggest by xaueious here
Code:
$ su
su
# remount rw
Remounting /system (/dev/stl9) in read/write mode
# touch /system/bin/profile
# chmod 644 /system/bin/profile
#
Alternate 2:
Download blank profile file from here (or create one and name it profile)
Use a program like Root Explorer to copy it to /system/bin/
Then longpress on it and check the permissions should be read/write for user, read for group, and read for others.
Alternate 3:
cyansmoker has put together an apk for the patch here https://market.android.com/details?id=com.voilaweb.mobile.droiddreamkiller
Thanks for pointing this out photoframd and androidpolice.com for investigating and reporting!
UPDATE: I renamed the .zip file and reuploaded it (350 hits wow). Also in the edify scripted version I added 644 permissions to the file (but if you already flashed it then it should have defaulted to that). I also added a pre-edify version of the patch thanks to xaueious for people using a recovery that does not yet understand edify.
Click to expand...
Click to collapse
Thanks
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
I would also recommend installing the free Lookout Mobile Security app. I find it to be very non-intrusive on my phone, no negligible battery drain or performance issues. Just scans any app you install, looking for bad stuff. Also does weekly full system scans, contact backup, and provides phone lock/alarm/location tracking features in case you lose it. Premium version has even more bells and whistles.
Posted from my EB01 SuperClean Fascinate with Voodoo
This has been stuck for the time being as it seems to be affected a BOATLOAD of users. Thanks for the linkage!
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
sorry delete
jcase said:
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
Click to expand...
Click to collapse
adb shell chmod 644 /system/bin/profile
also?
NOsquid said:
adb shell chmod 644 /system/bin/profile
also?
Click to expand...
Click to collapse
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
lasportsfan said:
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
Click to expand...
Click to collapse
Yes.
All this is is a quick fix that will create a blank file. The current iteration of the malware checks to see if it already exists. This file fools it into thinking it already exists, so it moves on.
As you might guess, the author needs to only update his code to bypass this, in order for this to be an issue again.
And now that this is out, someone else will probably try it. Someone who is a little more thorough.
Moral of the story?
Be careful.
Consider running something like LookOut.
Backup your important data regularly.
As far as CWM goes, is there some kind of connection to the malware thing? Or just in general?
(If just in general, it's better to ask elsewhere as to not derail the thread).
Otherwise, I don't believe the newest (orange) clockwork recovery from ROM manager is fully compatible yet. Last I heard, it still had some bad binaries and 1 bad mounting point. Stick with the Red from JT's thread (which is the same bundled into SuperClean). Other than a couple superficial bugs that don't hurt anything, it works wonderfully and has more features than the orange CWM currently has.
GizmoDroid said:
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
Click to expand...
Click to collapse
I dunno, it was in Rodderik's post but jcase didn't mention it. He's smarter than me, that's why I asked...
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
italysfinest327 said:
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
Click to expand...
Click to collapse
Who should act? Users and developers using pre-gingerbread roms
Click to expand...
Click to collapse
I'd say that means you should be worried. Those apps listed are just the ones that were found on the market with them from one publisher. Just how virus's can get put into any application on a PC, the same can be done on phones.
Remember folks, our phones are just as exploitable as any other computer, so be careful!
good thing the patch came out!
imnuts said:
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
Click to expand...
Click to collapse
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
iofthestorm said:
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
Click to expand...
Click to collapse
This is just another reason why I see this as a quick fix for what will need to have a much better one in the future.
If anyone hears of a more robust solution (besides using LookOut), let us know!
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
SupraLance said:
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
Click to expand...
Click to collapse
It is included in SC2.8. The 0 bytes is the best indicator that you are clean, since this patch is merely an empty file.
If you were infected, that file would actually have code in it.
For CWM 2.5.x.x DJ05, which one do you flash? or both?
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Thanks and sorry for the trouble, just wanted to be sure.

[RECOVERY][ENCORE] TWRP 2.3.1.0 with on-screen keyboard! [2012-10-15]

Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
Oh man. Awesome!
Looks nice...looking forward to trying it out.
This looks very slick!
Sent from space
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Super cool, thanks guys, I am now into Nook Color... HD2, AMAZE 4G...
Jainyankee1993 said:
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
We have a list of supported devices on the main twrp2 page: http://teamw.in/project/twrp2
So I see you got that stuck in recovery bug all worked out ehh? nice work.
eyeballer said:
TeamWin is proud to present TWRP 2.0 for Nook Color!!
Click to expand...
Click to collapse
Congrats TeamWin... this is supercool.
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
hm, anyway to install this on an existing install?
Midnitte said:
hm, anyway to install this on an existing install?
Click to expand...
Click to collapse
Right from their page? Though idk what kernel they are talking about.
Download the above file. Connect your Nook Color to the PC via the USB cable. This assumes you have working ADB.
Execute the following:
adb shell busybox remount / -o rw,remount
adb shell busbbox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push twrp-encore-2.0.0RC0.ub /boot/uRecRam <--- You can change uRecRam to uAltRam for alternate boot.
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Click to expand...
Click to collapse
RileyGrant said:
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
Click to expand...
Click to collapse
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
eyeballer said:
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
Click to expand...
Click to collapse
Actually what I thought, thanks for clarifying man .
Oooh, i look forward to trying this.
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
bobtidey said:
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
Click to expand...
Click to collapse
I had to do the same thing. Kept getting an error that "applet not found" for busybox in adb.
Thanks for the alternate method.
This is a much better implementation of our hardware in backup.
Thanks TeamWin.
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
It wasn't there before! I swear! /thanks
Hm, is usb storage working for anyone?
The only thing I don't really care for is... and I know I am doing things in a unique way....
I have SASD with CM7 on it... verygreen's recovery as alt-boot and replaced CWM with TWRP as recovery mode on the uSD... when in TWRP and reboot... it boots stock on eMMC instead of a normal boot... it should do a normal boot (uSD first)

[ROM] [UNOFFICIAL] CyanogenMod 12.1 INTERNATIONAL 26/8/2014

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, 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!
CHECK KNOWN ISSUES HERE
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Google Apps: Link 1 Link 2
TWRP Recovery: https://www.androidfilehost.com/?fid=24052804347766143
CHANGELOG
Download
GAPPS for CM-12.1
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!!!
source
https://github.com/cyanogenmod/android_device_htc_enrc2b
https://github.com/cyanogenmod/android_kernel_htc_enrc2b
https://github.com/cyanogenmod/android_device_htc_tegra3-common
Contributors
Lloir, Thomy
Source Code: http://github.com/cyanogenmod
Working Not Working: Eventually Change log
This will be edited and updated as I make progress
Working 7/7/15:
Audio
Touch
Display
Vibrator
WIFI
Bluetooth
DATA/GSM/RIL (except for sim pin)
BATTERY
ROTATION
GPS
Not Working 7/7/14:
Device encryption
CHANGELOG
?/05/16 (well it's finally coming out) in 2017
05/05/17 -- FINAL
cgroups fixed
RIL Fixes (GSM/DATA)
3G Mtu changed, should see an increase in speed.
Security patches, fixes loads of security issues
X+ now shows up instead of the ONE (MTP) (pulled from AndyLavr git)
SElinux fix up (pulled from AndyLavr git)
CM main source update
and a load of other stuff.
------------------------------------------------------
27/11/15 ------ MD5 b9ae858d0a881ae6a24958caa067360e
Sdcard symlink is fixed? it's storage/sdcard0 (for me anyway test it for me)
Added more sepolicies for the ril :silly:
Updated main cm source
FULL WIPE
------------------------------------------------------
5/11/15
CM update which includes Security updates from Google https://groups.google.com/forum/#!topic/android-security-updates/GwZn7sixask
Reverted the changes I made to sdcard, which means /sdcard is now able to be accessed again.
------------------------------------------------------
25/10/15
More selinux denial's fixed thanks to @el-Loko logs
Let me know if the sim card issue still arises.
I've made changes to MTP and the /sdcard /storage area's
------------------------------------------------------
24/10/15
Sepolicies updated, hopfully the no sim issue will be fixed now. https://github.com/Lloir/android_device_htc_enrc2b-2/commits/cm-12.1
No more selinux denial's that I could find. All eliminated.
Source update
Kernel update's thanks to @ntemis https://github.com/Lloir/htc_kernel_oxp/commits/cm-12.1
Sim toolkit now show's and works
GPS lock is oh oh so much quicker
If google maps has a hissy fit let it die and reload it.
------------------------------------------------------
28/8/15
Updated source (Which includes the chrome fix)
------------------------------------------------------
26/8/15
Updated source
Revert my bluetooth breakage change, so BT works as it should.
------------------------------------------------------
7/8/15
http://review.cyanogenmod.org/#/c/93232/
http://review.cyanogenmod.org/#/c/105285/ + http://review.cyanogenmod.org/#/c/105284/
http://review.cyanogenmod.org/#/c/105100/ (This is a security fix hence the build today) Issue with this, currently will get sorted for a future build
Mainline cm update ^^ those changes are not merged into CM but I've picked them to go into this rom for my own personal build. I will share this build
------------------------------------------------------
7/7/2015
CM general update
CVE's patched (security) http://review.cyanogenmod.org/#/c/102586/
NFC Update
Low memory killer updated
USB OTG Enabled
Brightness should be brighter (Should)
Re-implemented the powerhal from CM-10.2 (For those of you who have been around here for ages)
Updated the keymaster file based off of the grouper (Security)
A ton of patches from the grouper kernel http://review.cyanogenmod.org/#/c/102546/
VFS/ Compaction changes http://review.cyanogenmod.org/#/c/102597/
------------------------------------------------------
20/6/2015
CM mainrom update
GPS working in permissive only mode
-----------------------------------------------------
9/4/2015
12.1 update
Chrome/Firefox work
Updated with most recent CM source
------------------------------------------------------
6/4/2015
CM-12.1
DO NOT DIRTY FLASH OVER CM-12.0 IT WILL CRASH
gps is still broken
everything below counts
NEEDS KERNEL FLASH as usual
------------------------------------------------------
6/4/2015
New Kernel, not loaded with crap. This kernel is WIP. NO SMARTMAX on it, No S2W (Let the rage begin)
Might have turned the audio up...Sounds like it, need someone to confirm
Button light stays on when it needs to now.
------------------------------------------------------
3/4/2015
Fixed No Data issue FLASH THE NEW ROM AND BOOTIMG
------------------------------------------------------
2/4/2015 or 3/4/2015 depending on where you live
1st actual working release so lets start the change log
Battery WORKING
Source updated to today's released source
SELINUX DISABLED
Rotating working
GPS broken
regretting this...check the post above this one...
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
Sorry man cant use it daily without the battery being fixed! Other than that the camera works? at least for the most part
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
el-Loko said:
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
Click to expand...
Click to collapse
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Lloir said:
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Click to expand...
Click to collapse
I'll jump in as soon as builds with proper battery comes up.
And, thank you for being an awesome dev.
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
reaper90 said:
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
Click to expand...
Click to collapse
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Lloir said:
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Click to expand...
Click to collapse
This device is more than two years old now, i don't think there will be new devs coming to this device. Although i know not everyone wants to buy or can afford a new device every two years, i think this one has done it's job. while htc dropped support after only one year, i think some quite stable 4.4 roms are more than we could have asked for!
first impression on this build:
runs pretty good so far, camera not working here, kickstarting the battery from TWRP does not really work for me (maybe i'm doing something wrong) and when using adb shell, the charging led stays forever on.
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
backb0ne5p1d0r said:
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
Click to expand...
Click to collapse
Pretty much, not tested to see if it doesn't charge though....it will ALWAYS show 66%
Also are you using a 3rd party app for camera??
I don't mind it showing 66 as it's not my main phone.
And No, but I flashed GApps.
All I did was full wipe, Flash boot.img, flash ROM, flash GApps. Then the ROM booted and had a working camera
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
backb0ne5p1d0r said:
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
Click to expand...
Click to collapse
Yeah, there's that.
I have it fixed here, just not happy with the fix at the moment. IF People want to fix it this temp way do the following :
reboot into TWRP
mount system
adb shell
chmod 777 system/bin/htcbatt
reboot
If your not happy with using a 777 chmod then that's understandable, I'm trying out a 2nd fix as we speak, this will also help me to fix the battery issue in TWRP too
Things that are now working on my local build
Device Encryption
Battery + Battery LED
IF I'm happy with the battery fix, I'll do that release today.
Still broken :
GPS --- Kinda borked.
Rotating
Button lights are a little yeah.
This is going to be replaced with omni-L
Stay tuned, Not releasing ANYTHING until I have a nice working build of a ROM, not going to be releasing half-assed builds anymore.
Ok, after 2 days of daily use i can say that this rom is very stable, no reboots or freezes. Only GPS and auto-rotate is not working for me, but (orig)cam does its job.
One tip for the battety sidekick:
Instead of doing the trick via pc do it in a shell on your phone but dont kill the process with ctrl-c.

CM12 / Android TV ROM Development

This thread is for development updates, and an eventual release of testing candidates for the future of dual booting CM12 android roms on the Amazon Fire TV. At this time I am not planing on supporting the Fire TV stick since my development platform is based off USB3 booting.
There currently isn't even a stable branch in CM12 upstream so things are quite tricky right now.
I may eventually setup public nightlies once the core is stable.
IN PROGRESS FORM HERE: https://t.co/TXp9z7htDx
The goals for development are in this order:
Wifi [working]
Bluetooth [crashing]
Stable core [random resets possibly storage related]
Audio [possibly needs hacking to default to hdmi]
Recovery system [rom boots using the recovery partition currently]
Hardware Acceleration [untested]
Android TV addons [require stable core]
USB Formating and install app [apparently not everyone knows what gparted is]
Modified version of Rbox's bootloader [I'd like to add recovery to the loader then have stock and custom boot options]
Also, if you want to be ready for possible nightly testing, I highly recommend going to walmart and buying one of the playstation USB3 hubs. It's about $20 but allows you to plug in a USB3 drive and keyboard and mouse until bluetooth is working.
SETTING UP USB BOOTING:
Code:
#include <std_disclaimer.h>
/* * Your warranty is now void. *
* I am not responsible for bricked devices, dead USB drives,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in these files
* before flashing them! 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. */
PART ONE [Preparing the drive]:
This process will eventually be streamlined but for now I'll explain the process and how it relates to testing builds during development. Since the Fire TV only has an 8gb flash chip and has no hardware recovery trigger, it is quite the unforgiving device to develop on. The current boot method for my CM12 builds involves flashing over the recovery partition and using it as a sort of dualboot partition. The modified recovery partition then searches for ext4 partitions on and external (USB3 preferred) flash drive. Currently each build generates its own boot image to be flashed over recovery, but I'm currently in the process of exploring the possibility of following Rbox's method of loading a boot image from a system folder instead making only one flash to the actual device necessary going forward.
For USB3 booting during the development process I highly recommend using a USB3 hub for a keyboard and mouse while bluetooth pairing and control mapping is being worked on. I also recommend a USB3 drive.
1) Turn on a Linux machine or boot a Live CD
2) Open Gparted
3) Delete any partitions on the usb drive
4) Create three ext4 partitions, the first partion is system and should be about 1GB, the THIRD partition is cache, and should be about 768mb with 0mb following, you should then have the middle portion empty in the display, in this SECOND partition make your data partition fill the rest of the space.
PART TWO [Preparing the bootloader]:
WARNING this process currently involves replacing your recovery partition, remember kids dd and root is like holding a grenade, make sure you don't throw it at something you care about.
Also, if you are testing a build and it does not load using the previous bootloader, try flashing the latest one from the nightlies (and vise versa) as I am still in the process of stream lining the boot process as far as what should take place before system bring up on our device. If a different boot image loads the system with noticeably more stability let me know asap so I can track the causes of my current issues.
Code:
adb connect <STOCK FIRE TV IP>
adb push boot-<DATE>.img /sdcard
adb shell
cd /sdcard
su
dd if=boot-<DATE>.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Next I recommend side loading this apk to make rebooting into USB boot easier.
The three most recent "boot" images have been added to the downloads section, remember these should be flashed to recovery. Although they would work in boot, that would disable Rbox's loader and prevent you from loading stock OS.
PART THREE [Playing with instability]:
Great so now you have a USB3 booting image flashed to your recovery partition and you have an empty flash drive. This is where the tinkering begins. In the download section you will find a .tar.gz archive with a somewhat booting system with the aforementioned issues. Inside this archive is a system.img file which you will use dd to flash to the first partition of the flash drive you formated. After the system image is flashed you can plug your flash drive into your hub and reboot into recovery. Things will be great, wifi will show up and if you're quick enough you can complete setup and make it to the launcher. (the issue I'm currently working on is an odd timed reset that may be kernel or storage related oddly if you make it to the launcher and don't touch anything, it takes longer to reset)
If you made it this far, welcome to development. You can help by "kanging" (replacing system apk's and files with other versions to find more stable matches, or remove apks until things don't die then report back to me) Also if you make it to this point go ahead and fill out the form I mentioned earlier. Eventually any hotfix builds I do between nightly builds will be accessible to those users to play with.
Overhauling the boot system next and working on the reset debugging.
XDA:DevDB Information
TechVendetta ROM Development, ROM for the Amazon Fire TV
Contributors
TechVendetta, rbox
Source Code: https://github.com/TechV/android_device_amazon_bueller
ROM OS Version: 5.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-01-29
Last Updated 2015-01-29
Reserved
UPDATE: I'm pretty much settled in to my new job/home now so I'm going to resume this project shortly. The first order of business is to see what sort of driver improvements we got from Amazon and whether their modifications help resolve the issues I was having. I only have the original FireTV so I'll be only testing on that. Not sure if the new one has an unlocked bootloader or recovery system so that will be up to whichever brave soul wants to test that. Hopefully tomorrow I can resync my repos and get a look at whats changed.
Reserved
Thanks for the update! Looking forward to seeing how this progresses.
Thanks for your work!
It would be nice run a CM12 build in Fire TV
So far the main system seems promising, I feel like the reset issue, which is the primary major roadblock is either in the kernel, or in the storage management/selinux services. Selinux should be disabled in this build so I'm looking into the other two options right now.
TechVendetta said:
So far the main system seems promising, I feel like the reset issue, which is the primary major roadblock is either in the kernel, or in the storage management/selinux services. Selinux should be disabled in this build so I'm looking into the other two options right now.
Click to expand...
Click to collapse
Thank you for keeping us updated!
[email protected] said:
Thank you for keeping us updated!
Click to expand...
Click to collapse
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
TechVendetta said:
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
Click to expand...
Click to collapse
Hey,
i've got one question for the installation:
you use the recovery as boot partition (because you dont want to mess with the actual boot partition where the bootmenu is).
is there a reason we cant use rbox's bootmenu, add another entry "usb boot" which will boot from /system/boot/usbboot.img ?
Or is the only reason that this just hasnt been added by rbox so we have to use another way?
I think this would be the most brick safe version and shouldnt be a big problem for rbox to implement....
Chris
[edit]
i'm really looking forward to this
aHcVolle said:
Hey,
i've got one question for the installation:
you use the recovery as boot partition (because you dont want to mess with the actual boot partition where the bootmenu is).
is there a reason we cant use rbox's bootmenu, add another entry "usb boot" which will boot from /system/boot/usbboot.img ?
Or is the only reason that this just hasnt been added by rbox so we have to use another way?
I think this would be the most brick safe version and shouldnt be a big problem for rbox to implement....
Chris
[edit]
i'm really looking forward to this
Click to expand...
Click to collapse
Thats one of the goals I put up there, just unlike rboxs current loader I know a way to make it remote controlled. ;D I started a bit on it. The "friendly user release" will have a root installer app that will handle multiboot, formating flash drives, recovery options, updates etc.
Really looking forward to a CM12 Android TV ROM. It would be nice to know that Amazon would not be able to kill a rooted Fire TV when this becomes reality. Peace of Mind regarding the Fire TV would be Priceless!
Xposed too http://forum.xda-developers.com/showthread.php?t=3030118
hhairplane said:
Xposed too http://forum.xda-developers.com/showthread.php?t=3030118
Click to expand...
Click to collapse
I'm a big fan of exposed, I'll have to add that to my testing list. I get a bit more free time tonight so I'll be getting back to looking at WiFi and Bluetooth and the installer. I still have two possible routes for both installing and updating i have to consider.
Sent from my LG-VM670 using XDA Free mobile app
TechVendetta said:
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
Click to expand...
Click to collapse
Any luck with the video acceleration, eg for Kodi or others such as Netflix, etc? How about hdmi audio?
Thanks for the update!
Video acceleration appears to be working, haven't got to audio. Had a death in the family this morning so i haven't had time to test my latest build.
Sent from my LG-VM670 using XDA Free mobile app
Sorry to hear that, Family is first! Although, maybe working on this will help take your mind away from that. Feel better!
TechVendetta said:
Video acceleration appears to be working, haven't got to audio. Had a death in the family this morning so i haven't had time to test my latest build.
Sent from my LG-VM670 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry to hear that.
I recently installed CM 12 on a 2012 kfhd and wow!--it really brought that device to life! Performance/OC options are built right into the OS and another Dev made a custom kernel to oc to 1.7 ghz. But I have limited experience with CM and Android TV. Can we expect a similar UI and performance options with this? Or is it different for the set top boxes?
BTW--I think it's really great you're doing this. Lots of people are excited and it's very appreciated!!!
KLit75 said:
I recently installed CM 12 on a 2012 kfhd and wow!--it really brought that device to life! Performance/OC options are built right into the OS and another Dev made a custom kernel to oc to 1.7 ghz. But I have limited experience with CM and Android TV. Can we expect a similar UI and performance options with this? Or is it different for the set top boxes?
BTW--I think it's really great you're doing this. Lots of people are excited and it's very appreciated!!!
Click to expand...
Click to collapse
I can overclock the kernel but I'm not sure if it will be necessary yet. As for the features, CM12 doesn't even have a "stable" build yet. (they call them M builds now) They are still porting customizations like that in. That rom may use some stuff pulled in by the dev from other projects like paranoid, aokp etc. I'm listening to what people are asking for and I'll be taking it into consideration once I get to tweaking release candidates.
TechVendetta said:
I can overclock the kernel but I'm not sure if it will be necessary yet. As for the features, CM12 doesn't even have a "stable" build yet. (they call them M builds now) They are still porting customizations like that in. That rom may use some stuff pulled in by the dev from other projects like paranoid, aokp etc. I'm listening to what people are asking for and I'll be taking it into consideration once I get to tweaking release candidates.
Click to expand...
Click to collapse
Sounds great. Thinking now...an OC kernel probably isn't necessary since it's already real fast. But this rom I have works well on a relatively low end/older device. So I'm super excited about your project. Thanks again!

[ROM][UNOFFICIAL] CyanogenMod 12.1 for Alcatel ONETOUCH IDOL 3 5.5

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). 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. Your changelog is whatever was merged into gerrit.
Download Links
Androidfilehost:
Download: https://www.androidfilehost.com/?fid=24391638059057759
Google Apps Minimal Edition:
Download: http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Installation
1.) You must have twrp installed follow this guide here
2.) Download the ROM and Gapps and place them on internal or external storage (depending on your model you may only have internal storage)
3.) In TWRP navigate to "Wipe" and wipe cache, data, and dalvik
4.) In TWRP navigate to "Install" find the location of the downloaded zips and proceed with installation
5.) Once both ROM and Gapps have been successfully flashed reboot system and wait for the device to boot
XDA:DevDB Information
CyanogenMod 12.1 for Alcatel ONETOUCH IDOL 3 5.5, ROM for the Alcatel Onetouch Idol 3
Contributors
Unjustified Dev
Source Code: http://github.com/TeamRegular
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-10-14
Last Updated 2016-01-28
Status
Working:
Radio (Includes Dual Sim, Data and SMS)
Sound
Camera
BT
Sensors
Wifi
Known Issues:
Please share your bug reports (include a log if possible)
Tap to wake (Works, but disables itself randomly)
Horrendous battery drain
Changelog
20160218
remove unneeded qcom usb script
disable boot freq limit for cluster
20160216
Updated prima driver to LA.BR.1.1.3_rb1.45
Updated kernel to LA.BR.1.1.3_rb1.45
add back various alcatel kernel changes
set usb properties on boot (Fix the usb product model defaulting to Android)
set variant from init and add support for I806 (pivoq)
selinux enforcing (wcnss fixes by pivoq)
add peripheral manager
wcnss: restore stock config
20160128
update storage configuration (fix internal storage access)
don't set tct properties
set taptowake control state to 2
remove window cover support (revisit later)
remove unused zram script
remove tct cmdline garbage
remove unused hdcpService
remove power engine
remove powerup reason
remove unused Tct Daemon
disable secure discard
remove camera wrapper
use half res bootanimation
update WCNSS cfg from firmware bin
Stop the QC-QMI message spam
switch to init.qcom.power and update devfreqs
add script to identify device variants
switch to new cm-12.1 kernel
update adreno blobs
FAQs
Q: Is the device fully reversible on CyanogenMod as well?
A: Unfortunately no, it does allow all rotations but the dialer app currently will not allow you to place calls upside down.
Q: Does Dual Sim work with this ROM?
A: Dual Sim devices are now supported
Q: Why is my device 6045X?
A: The script failed to identify your device the supported model are 6045I, 6045B, 6045K, and 6045Y
Q: How can I get my device supported?
A: Post the model number and stock build.prop
Q: Is the Aero flipcase supported on CyanogenMod?
A:At the current moment it is not supported
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
salzy said:
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
Click to expand...
Click to collapse
No plans at the moment. There's is already someone handling 4.7 variants. Check out the CM port thread for details.
w00t!!!!!
Sent from my 6045I using Tapatalk
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
So close but yet so far.. I was so hyped when saw the thread but got down to earth quickly.. Stay focused my man, you're about to make something that's good into the great..
Just wondering if cm have some incompatibles with root apps like greenify, Viper 4 Android? Thank you
Sent from hell
Did you get the kernel to boot building from source or are you still repacking with stock?
Sent from my 6045I using XDA Premium HD app
brian117 said:
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
Click to expand...
Click to collapse
It's close. Just seeing how fast @Unjustified Dev has progressed to this point has been impressive.
Great Great Great my idol trembles park in the pits ready to receive new engine.
make sure everyone to get the minimal gapps as 5.1 before download
Whoohoo! so excited haha.
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:deleted
masterdex said:
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Click to expand...
Click to collapse
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Unjustified Dev said:
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Click to expand...
Click to collapse
Then I immediately delete the link to avoid problems.
My ADB is ready.
will it be regular flash or aroma installer?
masterdex said:
Then I immediately delete the link to avoid problems.
My ADB is ready.
Click to expand...
Click to collapse
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Unjustified Dev said:
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Click to expand...
Click to collapse
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
masterdex said:
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
Click to expand...
Click to collapse
You can flash gapps before and the boot.img isn't needed flash cm and gapps. Once they are done mount system and use the file manager to remove wlan module and that's it reboot and everything should be fine.

Categories

Resources