Related
WWARNING:You must Have The Correct Radio and Latest SPL! You can find them here (RADIO MUST BE INSTALLED FIRST) You can find it here
PLEASE DO YOUR RESEARCH BEFORE FLASHING ANY ROM INCLUDING MINE!!!
Please give credit if you use my work
This ROM is built from the WWE HTC Hero leak.
As with any other ROM there is a risk involved in the process, I'f you have any doubts you should just leave it alone or do some more research and get comfortable with what you are actually doing before proceeding!
Me and Drizzy will be teaming up to bring you new releases from now on. Soon 2.4 with alot more modifications, new kernel etc but untill then its BT time
DrizzyJAC r2.3.6
-Drizzy/JAC collab
-Pretty much the same as 2.3.5 but with framework/.apk's optimized
-Changed a2sd config to try and decrease loops
-/system/media moved to sdcard
JACHero r2.3.5
-app_s now moved to the sdcard @ system/sd/data/app_s
-Modified Rosie from coolbho3000 (thanks)
-CPU freq modifications in init.rc thanks to Cyanogen
-No longer overclocked by default set @ 384
-SMSReceiver service set to Highest priority
-Busybox only @ /sbin now
-apns-conf.xml update
-AudioFilter changes (should slightly increase volume and lower mic sensitivity)
-Added userinit.sh run support
-3G icon instead of H for Data
-App setup reverted to WWE format, only 3rd part apps in /data/app
-Cleaned up a2sd.sh script to prevent mounting and parsing redundancy and removed unneeded code for Hero builds
-Cleaned up update-script
***KNOWN ISSUE - use 3G/Edge to accept TOS for Market no WiFi, also first browser page on Wifi doesnt want to load at first on WiFi, go to any other site and you should be good
***Also swapper at 32/60 seems to be a sweet spot
JACHero r2.3.3
-Modified Rosie.apk
-db.hates.you custom wallpaper for JACHero
JACHero r2.3.2 - Had to pull the modified Rosie before releasing 2.3.2 it will be done soon.
-Removed cache_pressure from sysctl.conf
-Reverted AudioMOD
-updated contributors.html
JACHero r2.3.1
-replaced BT firmware in system/etc/firmware
-Max CPU set to 528
-APN changes in system/etc
-sysctl.conf changes system
-cleaned up unused/unneeded files in system/etc
-AudioMOD in /system/etc
-BT changes to enable pramods BT fix
-HCItool added to /system/bin to enable pramods BT fix
-Boot.img changes to conform to pramods BT fix
-removed launcher.apk/.odex
-removed learnmore.apk/.odex
-removed footprints/footprintswidget .apk/.odex
-removed HTCsync
JACHero r2.3
-Auto APPS2SD w/EXT2/EXT3 included script @ /system/bin/a2sd.sh
-2.6.27 Kernel - will be moving back to 2.6.29 eventually
-RAMDISK modifications
~auto mount for EXT2/3 partitions with noatime, nodirtime
~Updated sbin
~updated Trigger Binary
~calls to /data/init/rc system/init/rc
~PATH changes
~BlueTooth changes from Hero init.hero.rc and init.rc imported
-DalvikVM optimized
-Superuser Binary
-SD card placeholder
-BusyBox
-Added APN's for T-mobile users (SMS fix inlcuded in apn-conf.xml Thanks Horrorwolf)
-Trout keymappings
-Camera replaced with working Hero camera (still has rotate issue)
-Updated trout gps
-Multi-Touch
-Working WiFi
-Flash 9
-Audio libs updated (working audio and HTCMusic.apk)
-build.prop modifications to reflect proper device
-Sensor updates for Auto-Rotate (TouchFlo still won't rotate of course)
-sysctl.conf added to /system/etc
-auto backlight turned off by default in build.prop
-Wifi tether
-Swapper included
-changes to /data/app removed any .odex'd apps due to upgrade issues
-/system/lib files updated
PLEASE SUBMIT BUGS HERE http://code.google.com/p/jacheroplus
**********PLEASE READ BEFORE INSTALLING*********
Please use Cyanogen's recovery image!
Make sure you have a partitioned SD card with a FAT32 partition and a EXT3 partition. (EXT2 is supported also) If you do not this ROM will install but you will have little space left due to APPS2SD not running. I personally like the clean slate location for Hero and then i use the widgets i need if any.
When I install I check the ext filesystems first, if it tells you to go to console to manually check do it! After I've repaired the EXT partition or if it didn't need repair I will now wipe and then apply the update and reboot.
A walkthrough by forum member sxfx is posted one post below for install.
ALSO run as few widgets as possible folks!
DOWNLOADS
JACHero r2.3.6 SYM/BIND APPS2SD - MD5: 2A64747A1048FD175B1C1667D17E50FA
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.6.zip
JACHero r2.3.5 SYM/BIND APPS2SD - MD5: D80155D128ECCD3010768B52D9FB8EC0
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.5.zip
JACHero r2.3.3 SYM/BIND APPS2SD - MD5: 417ADE957153FD0BE5F3C7C9816B276F
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.3.zip
JACHero r2.3.2 SYM/BIND APPS2SD - MD5: a05c4d8d5abccd19c416b6febe40d6d2
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.2.zip
JACHero r2.3.1 SYM/BIND APPS2SD - MD5: 28f0afcc47d7766c71ecdb71e74e332a
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.1.zip
JACHero r2.3 SYM/BIND APPS2SD - MD5: D40A33ED2B1DED9181E1EA7B0AA96CC4
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.zip
JACHero r2.2.1 SYM/BIND APPS2SD - MD5: 35ad30f844862fb559ffcddadd4d49d2
http://www.justanotherdev.slackdev.com
JACHeror2.2.1 Fatality Merge SYM/BIND APPS2SD - MD5:87b22fc0baf6fc4138c48114388990b5
http://www.justanotherdev.slackdev.com
Thanks to daproy, JesusFreke, Cyanogen, Haykuro , xDan, Sangeet.003, Twisted Umbrella, and everyone else in the android community helping out.
If you like my work visit me at my Twitter.
No Off-Topic Posts!!!!!! This is not a general support thread!!!!
CREDIT:sxfx
Ok Guys.
I created this thread cause in the JACHero thread on at least every page everyone asks how to install it, what am I doing wrong, and why is it broken.
So let me give you step by steps of what exactly I have done for me and others to run Hero with out a problem. I will also create a thread with step by step on how to use Ubuntu Linux Live distro to partition your card.
Things you will need to make this work.
Your Brain
G1 Phone
SD Card reader
And the files I included in this thread.
My phone right now is running.
JACHero 2.3
NEW SPL
cyanogens recovery 1.2
8gb class 6sd with Swapper(Swap file on ext2 sd)
setCPU slightly overclock.
Results.
Ever since I did my new Buttons, and the SPL I included in this write up, I have not had one problem flashing any hero rom at all on my phone, nor did I ever have problem actually running hero roms.
So here goes.
First before you partition your card or do anything make sure your card is at least portioned to fat32, don't worry about any other partitions yet.
OK once you do that go ahead and take the radio zip file I am including in this thread and flash it on your phone.
But first make sure you don't already have new radio installed which is 2.22.19.26I THIS IS VERY IMPORTANT. To check what radio you have, power off your phone, and power it on while holding the camera button.
If you do have new radio you can continue on to flashing the new SPL.
Flashing your SPL. (PLEASE MAKE SURE YOU HAVE THE NEW BUTTONS INSTALLED)
Ok this is where it might get a little tricky, and you might require a SD card reader I know I did and frankly I think this is the best way to do it and I recommend every time you do put a new update on your sd card to update your phone do it through a card reader.
Now after you flash your SPL you might or I should say more then likely will get stuck at the T-Mobile G1 screen, this also might happen after new radio flash in the previous step. If this is the case do not freak out it's normal and your phone is not bricked, but this is why having a sd card reader is important.
Ok so Here is what you do after you have flashed new Radio and SPL(Note:The steps on running Linux live distro and using it to partition your card is coming up). Boot up Live distro of Ubuntu, when its done booting, go ahead and go into the partitioning program while your sd card is hooked up in the computer.
Go ahead and set up two partitions at this time. One EXT3, and of course the other one Fat32. Your ext3 partition doesn't have to be all that big. I actually have mine set up to 512.
Once you are done creating partitions, go ahead and put the latest JACHero on the FAT32 portion and flash away (don't forget to rename to update.zip).
At this point if you follow all of these steps there is no way possible that your phone should not boot right into the system to run the initial setup.
These steps pretty much walk you through steps as if you were starting with a phone that has completly nothing on it.
Also the first boot up after flashing the new ROM, might take a few mins at the HTC screen.
Once your phone loads up and you go through the setup process go ahead and run swapper, it should be an APP that's already pre-installed.
Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp
Here is the reason why. The default location is your FAT32 partition. If you all of a sudden mount your phone to the computer with the swap file running on FAT32 you will corrupt your sd card, and then you will have to wipe and reinstall everything.
If you set the location of your swap file on /system/sd/ that's actually your ext2/3 partition and never gets mounted and you never have to turn swapper off.
Well I hope this helps some of you out. I will be writing the walk through on loading up live distro of Linux and partitioning your card sometime today.
I have used this method on a couple different phones and it has worked each time. Also I really recommend installing cyanogens recovery 1.2, as its an excellent way of making a back up of your phone and doing future flashing.
If there is anything anyone thinks that could be done better feel free to post in here.
Remember different people have different ways. I have posted this way cause it has worked for me on my phone and two other phones I setup, and each time there was no hicups.
FILES:
Radio 2_22_19_26I
NEW SPL
CM-Recovery-1.2
Ubuntu Linux Download
DISCLAIMER:
I am not responsible for anything that you might have done to your phone by following these directions. Like I mentioned before so far every time I have used this method, I have had nothing but success.
================================================== =============================
XDA Users, KEEP THIS THREAD ON TOPIC OR IT TOO WILL GOTO THE TRASH!!!
================================================== =============================[/CENTER]
ArmandHammer said:
old one is on this site and on the market,
the new one is also on this site and on the market,
just search
Click to expand...
Click to collapse
at least u can tell me what should i search for in the market....?
ArmandHammer said:
CHMOD didnt work for me,
chmod did,
ill report back on the apps to sd
After using the old apps2sd app i got an infinite loop.
Click to expand...
Click to collapse
Yeep I was running into the same problem. It wasn't working for me in upper case either. It started working once I did it as
su <enter>
chmod 777 /data/app <enter>
exit <enter>
exit <enter>
I think it should be noted on the first pase that chmod 777 should be in lowercase.
zgmf-x322a said:
at least u can tell me what should i search for in the market....?
Click to expand...
Click to collapse
AppsToSd search that in the market(old version)
I didnt buy the new one, its in the new and improved apps to sd thread
Alright back on topic
Okay so 1.4 is out now. He says Apps2Sd is included. I've never used Apps2sd and really don't know how to. So do I have to do anything with the 1.4 build to move it onto my sd card or will it automatically do it for me?
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
EXT3 support is next on the list.
justanothercrowd said:
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
Click to expand...
Click to collapse
Perfect thanks! Is this the only difference in 1.4? So I have to create the partition myself first correct? I thought Apps2sd created the partition for me. Oh well let me go create the partitions lol.
PS: the CHMOD command doesnt seem to work in upper case. Lower case only.
So will this new Rom with the app2sd app move everything but leave rosie.apk & launcher on the phone memory? Or is there something else that needs to be done?
justanothercrowd said:
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
EXT3 support is next on the list.
Click to expand...
Click to collapse
thanks a lot, you are doing it just right
question, if my apps are already in ext2 (system/sd/app) will it work? or they will now be located in : system/sd/app_s ?
thank you
Somebody respond with how much available space they have left after running the APPS2SD.apk
i've chmod 777'd the hell outta my system/app folder and I still can't download apps. I've run the command from terminal on phone from ADB Shell, from inside the folder, from the root, as root every possible way and I still can't download anything.
Would it make a difference if I had tried downloading from market before applying commands?
I did a lot of testing and left all the files needed to keep this ROM stable and FAST under /data/app_s
Somethings work better under the app_s directory un-linked.
Everything else is under /data/app like a normal ROM so normal APPS2SD methods work. Since Marcus already has the app up I just included it...its only 18kb anyways.
This isnt off topic but an inquery to the EXT3 comming soon
Here is a question. Everyone is head over heels about using ext3 which is understandable. But why when i create and use an ext3 partition, why does everything running from my sd slow down by far?
i have 2 partitions on my sd ones an ext2 ones ext3 if i switch my link to m ext partition everything is fine.. if i switch it to my ext3 it gets about .5x slower
rahduke said:
i've chmod 777'd the hell outta my system/app folder and I still can't download apps. I've run the command from terminal on phone from ADB Shell, from inside the folder, from the root, as root every possible way and I still can't download anything.
Would it make a difference if I had tried downloading from market before applying commands?
Click to expand...
Click to collapse
If it means anything i tried to download an app then forgot about the commands, typed the commands and it worked.
I've posted this before, but got no response.
Is anyone else having trouble getting wifi turned on? I can actually use the Wifi tether app, but just trying to turn it on myself, it fails.
Thoughts?
Bryan
TheGeekNextDoor said:
I've posted this before, but got no response.
Is anyone else having trouble getting wifi turned on? I can actually use the Wifi tether app, but just trying to turn it on myself, it fails.
Thoughts?
Bryan
Click to expand...
Click to collapse
i tried moving and linking the local file once and that made my wifi never be able to turn it on until i deleted the link and moved it back
ArmandHammer said:
If it means anything i tried to download an app then forgot about the commands, typed the commands and it worked.
Click to expand...
Click to collapse
did you reset after commands?
fleshdeep said:
Somebody respond with how much available space they have left after running the APPS2SD.apk
Click to expand...
Click to collapse
43 mb AWESOME!!! the apps to sd works now in v1.4 great job.
did you reset after commands?
Click to expand...
Click to collapse
i just ran the commands and then pressed exit twice.
pentace said:
i tried moving and linking the local file once and that made my wifi never be able to turn it on until i deleted the link and moved it back
Click to expand...
Click to collapse
I've learned a lot about linking, but I am not sure what local file you are refering to that would make my wifi work for me. Any help is appreciated.
Bryan
Download link: MT3GV1.5_NBN1.5.zip
MD5:
1c962a4767659f86776fe6daf3052cf7 MT3GV1.5_NBN1.5.zip
This is the result of the work/messing around I did in this thread.
I started with the T-Mobile OTA stock ROM available here:
signed-opal-ota-150449.95700137.zip
I then:
1. Rebuilt the kernel with the same config as the ROM, except with the addition of the netfilter features required for tethering. (Kernel source is slightly newer than in the ROM as yesterday there were a few security related patches added to the repo.) The wlan.ko driver was rebuilt to match the new kernel as well.
2. Added the Superuser app and the Tethering app.
3. Removed the T-Mobile recovery and radio images. They are redundant at best, bricks waiting to happen at worst.
4. Re-packed and re-signed the ROM. (Only the ROM zip was signed so it would install via our recovery images. The internal apks were left alone.)
The result should be an experience identical to the stock software you had out of the box, but with the possibility of running apps that require root as well as tethering. Speed is the same, features are the same, apps are the same, etc.
There are plenty of great custom ROMs here if you're looking for more, but this will work if you're going for simple with no surprises.
UPDATE: Donut /1.6 update is on page 3.
UPDATE: Donut /1.6 DMD64 update is on page 4.
Is this for 32B or 32A?
This is for 32B.
awesome
hey man great job this is exactly what i want!!! great job!!!
atomtom, thank you for doing that. It's been working great the last 24 hours, no hidden gotchas or surprises from the updated kernel/wifi driver.
Thank you!!!...This is EXACTLY what I was looking for ..expecially for my friends who want root for wifi tether!!
Clean and Stock
Thanks for this ROM. I like clean and simple builts and this fullfill my tethering needs with my Viliv S5. I installed it today on MyTouch 3G.
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
atomtom said:
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Click to expand...
Click to collapse
Hi there
I am running SPL 2005 (aman_ra mytouch root guide)
32B radio from htc site for google ion 2.22.19.26I
recovery 1.2.0G (aman_ra)
I have been going back and forth trying to find the rom that works best for me so yes i have done the format/wipe. Also since i want to be sure i might even run the following ontop of the format/wipe
fastboot erase system -w
fastboot erase boot
I dont erase recovery since i dont think i need to.
Please let me know.
Also - I would LOVE it if you could provide the same rom but with HTC keyboard/dialer.
flamingblue8z said:
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
Click to expand...
Click to collapse
Yeah, the one that is available stand-alone is older than the one that comes with other ROMs. When I tried installing the newer apk pulled from Cyanogen 4.0.1 it would fail due to the key used to sign the ROM internals.
adb install Superuser.apk:
Code:
159 KB/s (14979 bytes in 0.091s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
adb logcat:
Code:
E/PackageManager( 58): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 58): Package couldn't be installed in /data/app/org.zenthought.android.su.apk
If anyone knows how to sort this out let me know and I'll update it.
That said, su still worked perfectly when I installed Better Terminal Emulator. (Of course, Better Terminal Emulator doesn't work to begin with. Try typing in a number.)
hmm interesting. when I was using just the stock ROM, then used 1click root, went into CM-recovery, followed by your directions, adb mount -a, then adb push the SU in reference, zenthought's, I had no issue. I then pushed the wlan.ko you put up, and flashed boot.img, rebooted, and finally installed the Superuser.apk, and I had NO issues whatsoever. i've got a nandroid backup of that system setup, in case there is anything of interest in there. I would have to boot back into it and remove my txts/mms/contacts, but i'd gladly share it for analysis.
I noticed the myTouch NBH appeared earlier, im going to try downloading that on my WinMo Wing (it connects to the wifi at the college im at but my G1 and myTouch won't.) i'll try flashing the NBH then your ROM, see what happens... oh and yes, I obviously wiped before installing ur ROM.
ROM has Superuser Permissions and Superuser Whitelist? Whats the difference and are they both needed?
Superuser Whitelist is the name of the apk that manages which app gets root access, su is the command line tool that actually performs the actions requested as root.
speedyls91 said:
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Click to expand...
Click to collapse
After last night and today of normal use, and leaving it on overnight, I haven't seen any behavior out of the ordinary.
I spent the last hour or so playing around with the donut update, but there are problems.
I downloaded the COC10 to DRC92 update zip and looked through it. Appears to be a new boot.img, a handful of files, and a bunch of binary patches. I made the following changes:
1. New kernel with the netfilter features enabled, but otherwise same sources and config.
2. Replaced the wlan.ko patch with the full file that goes with the new kernel since the one we're upgrading isn't the original and the patch won't apply.
3. Changed the update script to not try to patch the wlan.ko and skip over the version/key checks.
The update (applied manually via the recovery image) went fine, but there are problems with one of or both of WiFi Tether and Superuser. When attempting to start tethering there is just a general failure error but nothing bad in the log screen. In addition the Superuser app no longer honors the "always yes" setting. There are newer versions of both apps so I'll check those out later tonight/tomorrow.
Wow, doesn't sound good. Maybe leave out Wifi tether? I have been using a better su whitelist app, I think u may want to use it. I am using stock Donut at the moment, runs GREAT, so if I can help this would be great. What I am going to do is load my nandroid backup, clear out some garbage, and if you want I can send u my system.img and u can pick it apart appropriately to take a look at the SU I have along with the whitelist app. Perhaps that will solve the problems.
Wifi Tether is kinda the whole point so leaving it out isn't an option (or rather, having the user install it manually won't help). I think getting the new Superuser app working is a higher priority though. Unfortunately a system image of a stock ROM won't do any good. The problem is that the Superuser app ties in to the system in a way that requires them to be signed with the same key (or a shared key, something I haven't looked in to yet.)
Code:
I/PackageManager( 78): /system/app/Superuser.apk changed; collecting certs
E/PackageManager( 78): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
My guess that the system is signed with T-Mobile's production key but Superuser is signed with a test key that is used on the fully custom builds. So it works fine with stock Android, Cyanogen, etc., but not here since I only changed the kernel, not the keys.
Obviously I can't re-sign Superuser.apk with T-Mobile's key so I have to re-sign the system with the test key. Unfortunately I have no idea 1) which file this is specifically, or 2) how to do it even if I knew.
Any suggestions are of course appreciated.
You mentioned that before. But even on the stock COC10 ROM, I pushed THAT su (from the last JF ROM,1.51) into /system/bin and then installed the apk into /data/app and it worked previously. If you wouldn't mind, plz send the new boot.img and I'll try flashing it through fastboot, as well as cm-recovery so I can use the root access adb to push the su into the stock donut. Which spl has fastboot enabled? I'll PM u my email.
here it is:
Froyo (Android 2.2) w/HTC Sense based on Gratia Release version ROM
FR008 Repaired Bluetooth/FM Radio for HTC Sense in Cyanogen OC custom kernel
FR008 Stable Release with new kernel enabled
---------------------------------------------------------------------------------
FR008 RC2 Backed out to FR007 kernel to repair bluetooth & FM Radio
FR008 RC2 Cleanup permissions
FR008 RC2 Added Ladios Chinese customization routine for "-CHT" or "-CHS" carriers
---------------------------------------------------------------------------------
FR008 RC1 Fixed Superuser permissions causing problems with programs requiring root (a2ext, Titianium, Rom Manager)
FR008 RC1 Added ext4 fs support
FR008 RC1 Added nls_utf8 module support for cifs
---------------------------------------------------------------------------------
FR008 RC0 Reworked from a Gratia Release ROM (thanks grmpf for sharing)
FR008 RC0 New Custom Kernel (Based on CM6 kernel from cyanogen)
FR008 RC0 Trackpad wake working
FR008 RC0 IPV6 enabled
FR008 RC0 TUN enabled
FR008 RC0 CIFS module included
FR008 RC0 Overclock enabled (stock speeds unless enabled with SetCpu, 864 MAX, 806 Recommended)
FR008 RC0 Froyo WIFI Hotspot Tether working
---------------------------------------------------------------------------------
FR0X Add-on to enable Asian Handwriting keyboard - flash after ROM, wipe data first
FR007 Added Japanese, Korean, Portuguese (Brazil) and Hebrew (Wipe data required) - I cannot test these - feedback please.
---------------------------------------------------------------------------------
FR006 Added Chinese language support (zh_CN and zh_TW) Properly (Data wipe needed to enable)
FR006 Set supplemental apns_conf.xml from cyanogenMod to updated version
---------------------------------------------------------------------------------
FR005 Added Voice Dial (Thanks Gene Poole)
FR005 removed chinese Language - was fouling up default keyboard mic
---------------------------------------------------------------------------------
FR004 A couple of smaller bug fixes
RF004 MMDDYYYY Date format default - changeable in settings
RF004 Chinese language added
RF004 apns-conf.xml from CM6 added - may not work as override
---------------------------------------------------------------------------------
FR003 Numerous bug fixes
RF003 Fahrenheit default weather temp
RF003 Normal MIC on HTC_IME keyboard
---------------------------------------------------------------------------------
FR002 Added de-odexed version
FR002 Updated fingerprint for Market
---------------------------------------------------------------------------------
FR001 aps2ext (Cyanogen/Darktremor)
FR001 ap2sd (standard Froyo garbage')
FR001 Astro filemanager (cause *I* like it)
FR001 Terminal (cause *I* like it)
FR001 US english default (cause that's where *I* live)
FR001 No boot noises (cause *I* hate them)
FR001 Tons of locales (cause not everyone lives where I do)
FR001 Working Market (just cause)
FR001 No Gomarket (just cause all over again)
Notes:
Brand New LA Release candidate ROM - built from actual Gratia ROM and not a pre-release leak. This is the latest.
New Kernel (thanks go to cyanogen)
Use interactive governor with SetCPU for best OC Results (806mhz is Max Recommended speed)
Please discuss issues in this thread
Instructions:
Always do nandroid backups
WIPE DATA is highly recommended; required if coming from any other ROM, including liberated aria 2.1.
To add Asia Handwriting input support, wipe data, flash rom, then immediately flash the handwriting add-on.
Download:
LA_FROX_handwriting_signed.zip
md5: 7bcd9d855dc1b671af4ddc8bdd76a64a (Not a ROM - add-on for Handwriting keyboard)
liberated_aria_FR008_signed.zip
md5: 9bdc6527f67b545d9a388bc022555c49
liberated_aria_ddx_FR008_signed.zip (De-odexed)
md5: 0cb19faf0697af54615cfb040777d923
Kernel Options - Updated 12/17/2010 (Repair Superuser access)
FR008 Default:
http://droid.neolobster.com/roms/htc-kern-cm-a2ext-v2-signed.zip
a2ext enabled
Suitable for any FR00* ROM or other stock 2.2 Liberty ROM
Overclocking to 864 (806mhz max recommended) with SetCPU
Trackpad wake
CIFS support with nls_utf8
ext4 enabled
Hong Kong Shipping 2.2 Kernel:
http://droid.neolobster.com/roms/htc-kern-hk-a2ext-v2-signed.zip
Suitable for any FR00* ROM or other stock 2.2 Liberty ROM
a2ext enabled (ext2/ext3)
No Overclocking
No Trackpad wake
No CIFS support with nls_utf8
No ext4 enabled
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Linux GPL information:
Kernel config and source for custom kernels used in the FR liberated_aria ROMs located at:
http://github.com/attn1/htc-kernel-msm7227
ReadMe Is contained within the source package
Kernel Credits are posted in the readme and changelogs.
Many thanks to Cyanogen for his ongoing support and help
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Non-standard disclaimer:
In order to use this ROM, you must have already installed clockwork recovery. If you manage to brick your phone with this ROM from there, you are a dumb ass of unimaginable proportions, and I absolve myself of any responsibility whatsoever. Further, any damage done to your phone with this ALPHA ROM is your fault and no one else's.
FAQ
Q. I bricked my phone/my signal sucks/my cat exploded since installing this ROM.
A. See the Non-standard disclaimer above.
Q. I can't seem to flash the rom successfully, and my Nandroid backups don't restore.
A. Do NOT start Clockwork recovery by powering down the phone with the USB port plugged in. Clockwork WILL NOT operate reliably that way. Power down the phone with the USB cord disconnected so that the phone powers off properly. Then start the phone by pressing and holding the vol-down button while pressing the power button to start. After diagnostics complete, you can enter Clockwork the proper way.
Q. I lost my 3g connection after I flashed Liberated Aria FR Series, now the icon just says "H".
A. You didn't lose 3g - the H is for HSDPA, which is enhanced 3g, sometimes referred to as 3.5g. It's a good thing, if you see an "H" where the "G" used to display - don't worry about it. Print this out for next time you head to the can: http://en.wikipedia.org/wiki/High-Speed_Downlink_Packet_Access
Q. How do I keep my wifi from going to sleep every time the screen shuts off?
A. There is a hidden feature that disables wifi sleep.
menu > Settings > Wireless & networks > wifi settings > menu (again) > advanced > Wi-Fi Sleep policy > Never > menu > Save
However: although you can keep the wifi service from sleeping, the wifi driver will still sleep on it's own after detecting no bus activity for a period of time. It doesn't wake reliably, so you are better off just letting the service sleep.
Q. Will this ROM support over or under clocking with Set CPU?
A. Yes! As of FR008, we have a stable, fully functioning OC kernel.
Q. Hey, what's a de-odexed ROM and what's it for?
A. Read this: http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/ and this: http://forum.xda-developers.com/showpost.php?p=7435131&postcount=8
Q. I can't get flash to work. What's going on?
A. Flash 10 is not supported by this CPU, but HTC's Flash Lite is in there.
Q. Where's the FroYo wireless hotspot?
A. It's in there!
menu > Wireless & networks > tethering and portable hotspot
Q. What's wrong with bluetooth? It doesn't work with my floozengadget.
A. Nothing. All bluetooth functions have been confirmed *WORKING* with compatible devices.
Q. But my floozengadget device is bluetooth compatible. What's wrong with bluetooth?
A. Nothing. Android bluetooth on the broadcom chipset is not compatible with every bluetooth device. Consistent compatibility issues have been noted with devices using certain parrott chipsets, certain automobiles with factory bluetooth including most Nissans, Volkswagons and an assortment of other devices and autos.
Q. Can you fix bluetooth so it will work with my floozengadget device?
A. No.
Q. Does the FM Radio work?
A. Yes.
Q. Is this an HTC Sense ROM?
A. Yes.
Q. My widgets don't load or I am missing icons on the desktop or in folders.
A. The sdcard mounts late in the startup process - later than when desktop icons and widgets are loaded. This is a problem inherent in Android 2.2 and manifests itself when an application/widget is moved to the sdcard that has a presence on the Desktop. This is not a bug in this ROM, it's apps2sd in FroYo. For better apps2sd performance, use the ap2ext version (enabled by default when an ext2 or ext3 partition exists as the second partition - after FAT - on the SDCARD).
Q. If this is Froyo, then how come it doesn't work exactly like it does on xyzphone?
A. The Aria is not xyzphone, and probably has a different feature set.
Q. May I use your work and customize it and republish it?
A. Sure, but if you start with this ROM as a base for your own, please note it.
Q. May I mirror these ROMs?
A. Please don't, as I updated them periodically, and I can't update mirrors I can't control. If you want to do you own build based on these, then fine, mirror away.
Help
Install either ROM from Clockwork Recovery.
If you aren't rooted and dont have Clockwork installed, Go here: Unrevoked reflash Root/Recovery flash tool
If you are rooted and haven't yet installed clockwork, then do that. See this thread: Unrevoked reflash Root/Recovery flash tool
if you are running windows and are having difficulties with drivers for proper operation of Unrevoked Reflash, then look here for solution: Shadowf0x's custom LiveCD spin for rooting the Aria
Once clockwork is loaded:
Do a nandroid backup to preserve your current rom
Wipe Data (if coming from another rom, including CM6 or liberated_aria non-deodexed version, or to enable additional languages from previous version)
Wipe Cache
Wipe dalvik cache (advanced > wipe dalvik cache)
Install liberated_aria_*FR00*_signed.zip from sdcard
To Enable A2SD:
Backup your applications
Backup your sdcard
Partition your sdcard with ROM Manager with an ext partition option. (ROM manager is in Market)
This should start a special mode of clockwork recovery, which will partition the sdcard.
Yay moar romz!!!
Nice! Gonna try this out and compare it to the speed of cm6.
Sent from my Liberty using XDA App
This has got me very excited. Thank you.
Sent from my Liberty using XDA App
will be giving this a flash and run as i'm heading up to Atlanta this morning
Thanks alot attn1! I am flashing this as I type!
Liberated FroYo
You R the man!
Thanks you very very much on all of your priceless work.
I have this up and running right now. No issues at all so far. I'll post if I encounter anything strange.
Thanks attn1!
drumist said:
I have this up and running right now. No issues at all so far. I'll post if I encounter anything strange.
Thanks attn1!
Click to expand...
Click to collapse
Rock on! You are the man!
Oops...didn't mean to quote. Doh!
I think I'm going to switch to this rom since that new Gratia ROM has some chinese characters here and there and those chinese market apps. I'll be watching this thread for any future revisions. Thanks for this!
Impossible to move some programs on an SD-card, unlike CyanogenMod...
Froyo apps2sd sux anyway. Partition and use a2sd method included in this Rom.
Does this one have the voice dialer, or would the seperate app I downloaded a couple o weeks ago that you whipped up for us work fine with Froyo?
Sent from my HTC Liberty using XDA App
Yes I must say since flashing my Aria with this, it is very snappy and the market is working great, thanks again attn1!
Just thought I'd post again and say everything is working great. No issues so far (then again I've only been playing with it for about half an hour now). Only thing with all the roms I've tried though is why can't ONE of them for ONCE not put apps on that we can't uninstall.. such as Astro - I never use it, my explorer of choice is rootexplorer, but now that it's integrated into the ROM i can't uninstall it. I can see where this makes sense for certain apps such as superuser or busybox, but astro and other apps? I just really dislike it when roms do that. This particular rom doesn't include a lot of item(s) but I'd love it if you put out a "clean" version that didn't include items such as astro (which I think is the only item you included). Anyway I digress, thanks again for this.
I have two questions about this ROM:
1.-Is it possible to hide the clock from status bar? and,
2.-How to enable wake system from trackball?
Thanks for your answers
lasertits said:
Just thought I'd post again and say everything is working great. No issues so far (then again I've only been playing with it for about half an hour now). Only thing with all the roms I've tried though is why can't ONE of them for ONCE not put apps on that we can't uninstall.. such as Astro - I never use it, my explorer of choice is rootexplorer, but now that it's integrated into the ROM i can't uninstall it. I can see where this makes sense for certain apps such as superuser or busybox, but astro and other apps? I just really dislike it when roms do that. This particular rom doesn't include a lot of item(s) but I'd love it if you put out a "clean" version that didn't include items such as astro (which I think is the only item you included). Anyway I digress, thanks again for this.
Click to expand...
Click to collapse
This can certainly be done. Keep in mind that this is just the first release, you can't expect everything on the first go.
@attn1 Check your PM... ;-)
Installation error. I tried to install this ROM from clockwork (rebooting into this via plugging in the power and reboodting) and then it gave me an error saying the following... please help
Can’t symlink /system/bin/bugreport
E: failure at line 10: symlink dumpstate system:bin/bugreport installation aborted
what should I do??
READ ME FIRST! This is beta. Some things may not work properly. If you find a problem, please either respond to this thread, or add a bug on the issue tracker on github. Thanks!
Introduction
This kernel is built from Samsung's T959VUVKJ6 Kernel source drop with some slight modifications.
There are plans for this kernel to have voodoo sound, bln, and optimizations in the future.
But for now, stability and code cleanliness are top priority.
The thread title will update as I do. I don't have any scheduled plans, so don't ask for ETAs.
Changes
My code is hosted on GitHub. You can find the latest changes there.
Btw... I actually tag my releases
Plans
I sorta did a little brain dump on what I'm thinking here.
Initramfs
We are now on a new version of CWM: v5.0.2.7
Old backups from previous nandroid's WILL NOT restore with this version, as the nandroid backup format changed.
Also, if you're updater-script and update-binary that are using amend instead of edify, please switch to edify. Amend is no longer supported.
New recovery fixes backup & restore, adds the ability to restart adbd and restart to download mode.
Current Support
AFAIKT, this kernel is basically just like stock, but adds ext4(and jbd2), tun, cifs, fuse, and si4709 modules.
Debug info was recently disabled, which should also speed things up a bit.
ChainDD's Free Superuser.apk and /system/xbin/su are automatically installed/updated if needed.
Same with RaverX3X's bootanimation binary.
Download
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+:
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
Flashing
Either flash from CWM or:
Install Heimdall
Extract the zImage from the CWM zip file
Change your directory to where the zImage is
Put your phone in download mode
Run the following:
Code:
heimdall flash --kernel zImage --recovery zImage
Credits
drhonk (cwm+voodoo initramfs)
krylon360
RaverX3X (moral support, testing, bootanimation binary)
SeafoodExpert(aka ericmpanda), FBis251, and zargeus (for testing)
pawitp (thanks again for your help earlier)
supercurio (for voodoo lagfix and everything else!)
ChainsDD (for Superuser.apk and su)
Benjamin Dobell (for Heimdall, my current favorite program)
Last, but not least...
Samsung (for the source, of course)
Release History
Beta 3.1 (an RC): sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
Disable broken DMA Acceleration and Deep Idle.
Nothing else updated. Another kernel update will happen soon
Beta 3 (tagged in git): sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Update CWM to v5.0.2.7
Fix backup & restore
More kernel cleanup
Beta 2d (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2d-unsigned-update.zip
Add bootanimation as a voodoo extension. This will install /system/bin/bootanimation just like su and Superuser.apk.
Updated to ChainsDD's Superuser.apk to build v3.0.7 (41). 'su' is still 3.0.3
Beta 2c (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2c-unsigned-update.zip
Basically reverted back to v0.0.2
Double checked that su and superuser are updated
Worked with Krylon360 and RaverX3X to finally get initramfs bootanimation working. Now the rom just needs the right /system/bin/bootanimation (and it needs to be executable! yea. I ran into that one... :sigh: )
Beta 2b (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2b-unsigned-update.zip
Removed 'disabled' from bootanimation service, as suggested by Krylon360
Updated Superuser.apk and su
Beta 2a (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2a-unsigned-update.zip
Removed 'disabled' from samsungani service, as suggested by Krylon360
Beta 2 (tagged in git): sms-T959V-KJ6-v0.0.2-unsigned-update.zip
More build clean-up
Disabled Debug Info and a few other debug options for performance
Made ext4 and tun as modules, now also packing cifs, fuse, and si4709
Initial Beta (tagged in git): sms-T959V-unsigned-update.zip
For more details, check out github... really. Everything I do, there is source for!
Changes to the kernel can be found here.
The bug tracker for the kernel is here.
awesome work! I am very excited to try this. Downloading now and will update as soon as I have a few minutes to spare.
jigglynuts said:
awesome work! I am very excited to try this. Downloading now and will update as soon as I have a few minutes to spare.
Click to expand...
Click to collapse
Great! I'm about to pass out... lol.
As the Title says/warns... this is beta2.
I am running this on my phone, as well as a few other people, and we haven't ran into any major issues... yet.
If you actually find a bug, please submit a new bug to the issue tracker on github.
:sleeps:
:happydance
Thanks for your work!
Mind I ask, i know rfs and ext4, but what is the mtd+yaffs 2 you mentioned adding?
Will ext4 voodoo conversions take place in the same manner as before?
Sent from my SGH-T959V using XDA App
Updated op with an update to remove disabled from samsungani in init.rc.
Thanks for the tip, Krylon360!
Finally a KJ6 kernel compiled form source! Thanks so much, will try it shortly!
Caligula36 said:
:happydance
Thanks for your work! Mind I ask, i know rfs and ext4, but what is the mtd+yaffs 2 you mentioned adding? Will ext4 voodoo conversions take place in the same manner as before?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Basically, the internal storage on your phone is a flash device.
BML and FSR (aka XSR) acts as a software-based FTL (Flash Translation Layer).
This allows you to put filesystems like fat or ext4 on a flash device.
Hardware FTLs are everywhere. Look at your memory stick for instance. There is an FTL between the usb device controller and the nand flash chips that actually store the data. You can format your memory stick with ext4, btrfs, ntfs, whatever...
Samsung decided to go further down the rabbit hole with RFS, which is basically a modified version of FAT(32?) with ACLs and Journalling. IMO, silly.
BUT, fsr/rfs are proprietary modules and are built with a kernel that has a set of symbols exposed. If I disabled debugging (like I did) and something in one of those fsr/rfs modules depended on it, then the fsr/rfs modules wouldn't load (unless you trick it).
Moving to controlling the flash on the phone (in which the flash type on this phone isn't nand, but OneNAND-Flex) with MTD gets us away from the proprietary modules, but introduces a new problem. Can't use ext4 for /system, /data, and /cache anymore. Instead you have to use a flash filesystem, like yaffs2 (which is what the CM supported Samsung phones use). I would like to see a test on this phone with UBI/UBIFS though. I think that might have better performance then yaffs2 or jffs2 (but almost everything, including my grandma is faster then jffs2... seriously).
It's subtly modified stock, and I'm using the same initramfs (minus kernel modules, of course) that kj1 with voodoo lagfix had (now with boot animation support with the latest update). Lagfix and all should work just as it did before.
Ask, and ye shall receive... (or better, get a whole page about how flash works)
Just what I've been waiting for... I've missed CWM, but wanted to keep the kj6 kernel.
I'll push this later this morning as time permits and see how it goes.
Thanks!
How fast is boot with this?
I am using it with the simply simple rom right now, perfect combination!!!
Sent from my SGH-T959V using XDA App
Will it work with init.d scripts ? lockscreens and thundervolt...
itzik2sh said:
Will it work with init.d scripts ? lockscreens and thundervolt...
Click to expand...
Click to collapse
It's just a kernel it has init-d support and boot animation support.
lockscreens are framework dependant not kernel dependant.
Sent from my HTC Glacier using xda premium
I've been using this for a few hours now on top of Valhalla o/c'd to 1.3ghz and it's been running great so far. Good job man.
Sent from my SGH-T959V using xda premium
how long does it take to boot. Normal or voodoo kernel time.
airfluip1 said:
how long does it take to boot. Normal or voodoo kernel time.
Click to expand...
Click to collapse
Shaved 4-5 seconds off my boot, on Octane 2.x
Sent from my SGH-T959V using xda premium
Running great on icbinb kj6.
Many thanks for this.
Just flashed, no issues so far
Sent from my SGH-T959V using XDA App
Okay, user error... got it flashed with Heimdall after all... we'll see how she plays...
Working well with ICBINB Official KJ6. Nice work. Glad to see some developers are back in action with this phone.
Hi guys,
for those of us who are waiting for at least the M1 of CM12 before switching lanes, I did a build of Carbon (and a few of CM11, previously) for our Photons.
This is an odexed ("user", not "userdbg") build, running on the cm-12.1 kernel branch and using the latest available f2fs_tools. It also features a modified init which can use either f2fs or ext4 for /cache and /data - so switching to f2fs is highly recommended, but not mandatory. Superuser is included.
This is esentially for those who switched to CM12 just for f2fs; it's miles faster than cm12, and a bit more responsive that the old official cm11 nightlies.
A word of warning. TWRP's "change filesystem" function formats the partition (PhilZ does too, but at least it makes that explicit).
So what you want to do when switching from an ext4 ROM is,
before you begin: copy everything in the internal sdcard somewhere on the external sdcard; this is needed, since the "internal sdcard" is actually a folder in /data;
in TWRP, begin by creating a backup of /data (that saves everything except the "internal sdcard" and /cache - that's why you need step #1);
do the FS change for both /data and /cache
restore the /data backup, on the freshly formatted /data partition; ignore the "different filesystem" warning, it's inconsequential;
install the ROM;
once you booted the phone, copy back the old contents of the internal sdcard
You only need to do this when you change filesystems, which will be exactly once if you like my ROMs And obviously, if you don't, you have to use the exact same procedure before flashing an ext4 ROM, if you don't want to lose data.
Though, in all fairness, I'd recommend flashing this cleanly - unless you're upgrading from an ext4 Carbon build.
A note on the radio
I have included a tool called radio-tool (of my own design) that allows people to enable/disable the US GSM lock and individual network bands;
if you're having the SIM mod, and are from, or have business in, the US, you can use it to kill the CDMA and Sprint LTE bands altogether, as well as to enable US GSM bands and disable the US GSM lock;
the source code is here
Use (as superuser)
Code:
radio-tool [dbg] [{+|-}opt [...]]
where opt is one of
uslock - US GSM lockout
cdma - CDMA bands (CDMA800 / CDMA1800 / CDMA2000 1xEV-DO)
usgsm - US GSM/HSPA bands (GSM850, GSM1900, WCDMA850, WCDMA1900)
eugsm - EU GSM/HSPA bands (GSM900, GSM1800, WCDMA900, WCDMA2100)
sprlte - Sprint LTE (LTE25, 1900)
vzwlte - Verizon LTE (LTE13, 700)
Download:
ROM: CARBON-KK-UNOFFICIAL_f2fs-20150526-moto_msm8960.zip
Recoveries: TWRP-2.8.6.0-20150526-f2fs-moto_msm8960_jbbl-xt897.img, PhilZ-6.59.0-20150520-crkk_f2fs-moto_msm8960_jbbl-xt897.
You do not need to use a su app with this; but if you want to, please use the latest SuperSU. Attempting to use a different, or older, su app could result in no radio.
Changes from stock Carbon:
alternative mount points support - this enables the ROM to work with either f2fs or ext4 for /data and /cache
tuned mount settings - kickass speed with both ext4 and f2fs
256MB of lz4-compressed swap space (zram0)
built on gcc-4.8-sabermod
build.prop tweaks - this defaults to GSM/WCDMA - plus a few radio and network tweaks;
added a few goodies that are present in CM builds (Term, Apollo, Calendar, CMWallpapers, VideoEditor, plus the cmdline utils);
removed the stats and the update apps (for obvious reasons)
added Romanian (programmers) keyboard support in Asanti Keypad
built with: twrp 2.8.6.0, cm12.1 kernel, cm12.1 f2fs-tools, cm12.1 e2fsprogs, cm12.1 exfat, cm12.1 fuse.
(this will allow me to pick up any improvements in kernel, file systems, and recovery, with great ease )
Quirks:
MTP doesn't start by default in TWRP, despite the fact that it claims to be enabled; disable and re-enable MTP, and it will work
in PhilZ' mount menu, entries for cache and data are duplicated; this is cosmetic - mounting and umounting works just fine, regarless which of the two entries for each partition you choose
.
Older, CM11 vanilla builds:
Download:
cm-11-20150427-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip - repo syncs, builds with TWRP, uses branch cm-12.1 of the kernel, uses latest available f2fs-tools
Use latest SuperSU with any of the CM ROMs - older, or different, su apps might make the radio not work.
NOTE. These ROMs are actually moto_msm8960_jbbl, so they should work on all devices for which official moto_msm8960_jbbl builds did, as long as they're still on the JB bootloader (jbbl) and you have a device-specific recovery that supports f2fs. A suitable PhilZ touch for non-xt897's can be found on the AtrixHD thread, courtesy of @palmbeach05, or you could use PhilZ-6.59.0-20150506-crkk_f2fs-moto_msm8960_jbbl-mb866 (note, despite the -mb866 suffix, it should work on any moto_msm8960_jbbl device except xt897).
The current repo is available here. To use,
repo init -u https://github.com/mionica/android.git -b cr_kk_gcc-4.8
repo sync
. build/envsetup.sh
breakfast carbon_moto_msm8960_jbbl
edit the .repo/local_manifests/roomservice.xml, changing the device project for android_device_motorola_moto_msm8960_jbbl to
Code:
<project path="android" name="mionica/android_device_motorola_moto_msm8960_jbbl" remote="mionica" revision="cr_kk_xt897" />
repo sync again
finally, (cd vendor/carbon && ./get-prebuilts).
After you do that, you're good to go - (optional) configure ccache (if it's your first build), (optional) enable ccache, choosecombo, then mka carbon 2>&1 | tee BUILD.LOG.
If you're not sure how to do any of these, either just use the provided ROM, or search on youtube for "building CyanogenMod" - that should help, I know it helped me Anyway, this thread is not the right place for learning how to build Android.
Mirrored for archival purposes.
This server WILL BE SLOW. You've been warned.
http://lionspaws.net/cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl/
98e652a97965ba5d88cb9068fe7d4dbe *cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
Using it for the last few days, seems good so far. Thanks
taking a break
Quick one. I'll take a break from this for now - my little sister's phone broke down, so she got my Photon. I just ordered one from the States today, but between that arriving and cornholiogsm doing the SIM mod, it might take a while (US to Ireland to Czech Republic to Ireland - and Tomas is pretty busy in my experience).
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Wait what wiki told you to use CWM for xt926!? CM's wiki?
enigma9o7 said:
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Click to expand...
Click to collapse
I agree with @arrrghhh you should use what your device maintainers recommend you use. I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section. Odexed is like what you get from the manufacturer. It has .apk and odex files in it. odex assist the apk files. 6.0.4.4 is outdated, as 6.0.5.1 is the most recent. The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well. Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore. Lollipop is able to be used on your device, as it currently has official builds. 5.0 had issues, 5.1 just got its official release yesterday. As far as unofficial builds go, I refer you to epinter and krystianp who both took an older device and provided unofficial updates that were very stable, despite the neverending work on a custom kernel. Furthermore, you can go talk to Quarx about unofficial builds, since his builds has been running the Defy for years. So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item. Battery life will always be an issue if you have a bad setup (wifi and bt on all the time, max bright screen, hrs of listening to music or streaming, etc.)
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
mionica said:
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
Click to expand...
Click to collapse
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Click to expand...
Click to collapse
Mmm will have to check. For me it's working in the EU using GSM/HSPA on the xt897 with the SIM mod.
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Another possibility is that it wouldn't work because of SElinux mismatches between kernel and userland. The following has to be in the fstab:
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,noatime,nodiratime,barrier=1,[b]context=u:object_r:radio_efs_file:s0[/b] wait,check
If it doesn't, on the xt897 you get no WiFi, but I expect results might vary by device
All I'm saying is, it might or might not be a kernel config, would have to check when I get to my PC.
mionica said:
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Click to expand...
Click to collapse
I reviewed the entire changelog from cm-11.0 to HEAD, and couldn't find anything that looked even remotely radio-related, so I reckon it's most likely the SElinux thing. And now that I built a TWRP that has a chance of running on AHD, I guess you could tell me whether that's the case
arrrghhh said:
Wait what wiki told you to use CWM for xt926!? CM's wiki?
Click to expand...
Click to collapse
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
palmbeach05 said:
I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section
....
The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well.
...
Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore.
...
So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item.
Click to expand...
Click to collapse
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
enigma9o7 said:
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
Click to expand...
Click to collapse
Yes, you can dirty flash this ontop of an existing CM11 after switching /data and /cache from ext4 to f2fs. Gapps will be fine since they install on the /system partition.
Sent from my ATRIX HD using XDA Free mobile app
Switched to Carbon, but preserved most of the goodies from CM; links in the first post.
Also added a note on how to hack your radio to disable CDMA/LTE - so you could go with this phone in the US and never register on Sprint's network (unless they have a GSM/WCDMA network in place too, which should be fine).
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
enigma9o7 said:
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
Click to expand...
Click to collapse
There should be an option to wipe things, go there
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There should be an option to wipe things, go there
Click to expand...
Click to collapse
Thanks, found it.
And now I'm stuck. But I bet it's an easy solution.
I changed filesystems, restored data & cache, installed cm (04/27), installed superuser (wasnt sure if needed, but figured it couldnt hurt), and I booted.
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
I thought maybe I'd try command line, but I'm no expert there... I su'd and tried similar things as in EX but similar results.
I thought I'd try to copy it back with TWRPs file manager, but I couldn't figure out where to put it, there was no /storage directory, so I tried putting it in / and that started copying for a while but before it was done it rebooted and just hung at the TeamWin screen until I powered off...
So yeah. Dunno how to restore sdcard0. Help please....
edit: maybe superuser doesn't work? I tried to use default "file manager" and it wont let me switch to root mode. Then I noticed that while trying ES File Manager again I didnt see the popup about "root granted" or something like that that I normally see. But superuser is installed, its in the apps menu and runs and a quick look thru the settings seems okay to me, but I don't recall ever setting anything before.
edit2: I'm giving up and going to try to go back to last cm11 nightly and hope my phone starts working again. I tried reflashing multiple times, eventually tried supersu instead of superuser and that worked to get root explorer working, but I still couldn't copy over sdcard0 using ES anyway, but using default filemanager I could start (although I hate that filemanager cuz I dont know how to change directories, usually have to tap about 15 times before it opens a folder), but it would always start then reboot before it finished. So I still dunno how to copy that back.
enigma9o7 said:
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
Click to expand...
Click to collapse
Superuser is probably not a smart choice on KK. Use SuperSU instead.
The very first boot is somehow handled differently - I discovered this when I worked on integrating SuperSU into a catch-all zip of mine (alongside Windows Mobile ringtones, Midnight Commander, patched hosts, and a few other goodies). I got no radio with my package, but if I flased SuperSU instead, it worked.
It took me a coupe of tries to find the culprit - a flag file in /etc that SuperSU created after the first boot (and I attempted to create that from my zip). Made my zip not create that, and bang! everything worked just fine. Btw, removing that file after the first boot had no effect, the phone'd be screwed until you wiped /data.
Now, the fact that SuperSU handles the first boot differently kinda makes me think that older su's might very well not work (properly) on KK - and what you're reporting seems to confirm that.
I would strongly suggest going Carbon instead; that includes a working su. It's essentially CM with a different boot logo and a good few extra customization options (which you can safely ignore if you're not into that sort of thing).
So if you didn't go back yet, try either
flashing carbon and being done with it, everything will work;
flash the cm rom alongside supersu, not any other root app,
Either way, root will work, phone will work, and you'll be able to copy stuff around to your heart's desire.
As for a FM, I strongly suggest an app called Total Commander. The UI is atrocious as of late (the author is obviously better at coding than designing icons ), but it' probably the most complete FM solution for Android, bar none. And it's free, without adds; wait til you try it in landscape
I'm sorry for you inconvenience, but I also somehow feel it's earned - the OP said SuperSU back before Carbon replaced CM; because that's what I was using, and it worked for me - no guarantees if you went your own way. I've re-added the limitation and made it bold+orange in the CM part of the post (Carbon has its own, fully working, su).
Added the 2015.05.03 build of Carbon; links to 2015.04.30 removed.
At this stage, CM users should have everything they liked about CM, already compiled in (except for WhisperPush, the point of which I don't quite see).
Changelog from 2015.04.30:
added Calendar (!!!) - why on earth would the Carbon guys build an ROM without this?!
built on gcc-4.8.x-sabermod-20150429
added CMWallpapers, Video Editor
added the previously-missed vim, unrar, zip and gdbserver
synced with upstream; in particular, there was a noteworthy GPU memory allocation improvement in the kernel
Todo:
add an app for messing with the NV settings (enable/disable bands, enable/disable US GSM lockdown)
enable zram.
Added the 2015.05.05 build of Carbon; links to 2015.05.03/04 removed.
Changelog from 2015.05.04:
set default governor to msm-dcvs - better out-of-box performance
imported the cm-12.1 init support (including swap enabling)
Changelog from 2015.05.03:
support for fstab alternatives, cm12-style (my own code in fs_mgr); now you can use the ROM with either f2fs or ext4 for /cache and /data
massively improved FS performance for both ext4 and f2fs - tuned the fstab settings for best performance;
added radio-tool to enable/disable US GSM lock and groups of radio bands (CDMAs, US GSM/HSPA, EU GSM/HSPA, Sprint LTE, Verizon LTE) - see spoiler in first post
Todo:
figure out why swapping doesn't want to start, despite the device being there and mkswap succeeding (error -16).
Updating the recovery to a 20150505 build is highly recommended.