Related
*********************************************
CM10 is now available.
Requirements: Root
From rooted stock or a custom rom, just download and install updated Rom Manager from the Play Store and download CM10 Nightly and GAPPS. Reboot into ClockWorkMod, factory wipe, disable signature check, flash CM10 twice. The first time partitions our tabs and reboots. Flashing a second time is for good measure. Then flash GAPPS. Done.
Note: I am not sure if Rom Manager can flash ClockworkMod directly. I personally updated from ICS > CM10 by downloading CM10 and GAPPS through GooManager and flashing manually in ClockWorkMod.
Its been reported that you can go directly from rooted stock to CM10. I've actually completed everything below to get to ICS first (Stock > ICS > CM10 JB).
CM10 is a much better experience. The tab works much better, doesn't freak out, lasts longer, plays better.
*********************************************
Wow. Lots of different, confusing, and scattered information about how to go from stock Gingerbread to the latest CM9 build. It is all very confusing and honestly most of the useful information isn't even on this site. So I figured I would help myself (and others) in creating a very detailed walkthrough of the process required to successfully get from GB to CM9 Build 7.
**This specifically outlines the methods to take a COMPLETELY STOCK Sprint Galaxy Tab 7" SPH-P100, unrooted, to a ICE CREAM SANDWICH rom. I "think" it might also work for the Verizon CDMA and a few others. I think the ROM itself is a general overall generic build for all 7" Gtabs. So heads up that if you have a different version, you might want to use this as a guide rather then a step-by-step.**
BACKUP EVERYTHING YOU MAY NEED BECAUSE OBVIOUSLY THIS PROCESS WILL FORMAT YOUR GALAXY TAB
GET CONNECTED!
We need to download Heimdall's App and his Drivers (Main URL). This is the first confusing steps as everyone suggests using an older version, but the included drivers don't work on newer Windows OS's. So you have to mix and match a few different versions to get it working. I've already compiled an archive with everything you need: Heimhall Mixture /w zImage & ClockWorkMod 5.0.2.7
1. Extract everything to a simple folder [ex. C:\GTABICS ]
2. Turn off Gtab. Hold VolDown+Power until you get to a downloading screen
3. C:\GTABICS\Drivers\zadiag.exe to load drivers [try running as Administrator]
4. C:\GTABICS\heimdall-frontend.exe to start the process
5. Kind of confusing. Focus on the "BROWSE" buttons. Look for "Kernel(zImage)" on the left and "Recovery" on the right. Hit browse for each one and select the appropriate file from C:\GTABICS. Obviously "Kernel(zImage)" = "zImage" and "Recovery" = "recovery.bin".
6. Make sure Kernel(zImage) and Recovery both have files selected and a checked box. While GTAB is at the black Downloading screen: Hit "START".
7. The process is pretty fast. Don't rush. At this point your tab will probably just bootloop anyway.
LET'S GET THIS SHOW ON THE ROAD
Now you have ClockWorkMod installed and a proper kernel, most flashers will feel really at ease right now. But there are a few little quirks that will cause this to go bad. You have to install 2 versions of ICS to get to the latest; One using the existing partition table, and a second that will update to a newer format. You obviously have to install GAPPS like always with a CM rom, but not so fast, you have to manually "MOUNT /SYSTEM" in CWM before it will even take. And there is the fact that you have to manually open and edit the CM9 Build7 update and remove code....[holy crap].
But it is pretty easy once you go through it once.
REQUIRED FILES
JT1136 CM9 V5
JT1136 CM9 V7 UPDATE
GAPPS
Prepare CM9 v7 Update
1. On your PC, open "update-cm-9.0.0-RC0-galaxytab7c-KANG-BUILD7.zip" and browse to META-INF\com\google\android
2. Copy "updater-script" to your desktop and open with Notepad and remove the first 3 lines or just Download it.
3. Drag and drop the update-script back into the META-INF\com\google\android folder, overwriting the existing one.
If all goes well, you are now done with the PC.
COPY FILES AND FLASH
1. Copy Build5, the new Build7, and GAPPS to your microSD card.
2. Boot into ClockWorkMod: Power off. Hold VOLUP + POWER
3. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
4. Flash zip from SDCard: locate Build5 and Flash
5. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
5.5 [OPTIONAL] You should be able to boot into ICS at this point if you want to make sure build5 flashed properly before upgrading to build7
6. Flash zip from SDCard: locate Build7 and Flash
At this step, my GTab rebooted in the middle of the process the first time. It freaked me out but I assume (now) that since it changed the partition tables, it needed to reset. So I did it a second time just to be safe:
7. Flash zip from SDCard: locate Build7 and Flash
8. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
Congrats. You should have a working bootable CM9 build. But lets flash GAPPS so we have our Google services. This is tricky.
9. Mounts and Storage > Mount /System
10. Flash zip from SDCard: locate GAPPS and Flash.
11. Finally [!] reset device and prepare for boot.
Now you are on the latest CM9 build [7] and have the latest GAPPS installed. Hopefully you are booting now and see the famous ICS Boot Animation. Have fun. In the future you should be able to simply download new roms as they are available and flash normally like you would any other device.
RECAP:
Drivers and Flash Tool
Pre-Edited updater-script
UPDATES
Convert to Sprint
The above procedure will set your Tab as a Verizon version. If you plan on using the Sprint cellular service or just want everything to match, then flash this via ClockWorkMod.
****************************************
I didn't do any development work. All credit goes to Heimdall for his fantastic Recovery Flasher and jt1136 for his great stills porting this awesome rom over to our Galaxy Tabs. All I did was bump and grind my way through to see a successful working flash. I figured if I didn't post a walkthrough here, I would hate myself in 6 months when I boink something up and have to do this all over again. I would recommend you keeping all of the files safe somewhere to prevent this headache again.
DONATE TO JT1134
DONATE TO HEIMDALL
MAIN HEIMDALL URL
MAIN ROM URL
player911
i have been thinking about moving up to ICS with my sprint sph-p100
just not sure if i should jump now or wait till more things are working ?
do the things working out number those not , is it ready to be a daily driver yet?
Camera fully works but is flaky sometimes. Video out isn't working yet but he's working on it.
Other then that, its golden. Very fast and works well. Really worth it. Feels much better... like an actual tablet vs a large phone.
Iffy Camera and video out aren't worth holding back. One of the benefits is now Wiimotes and PS3 controllers will pair up using their respective apps now.
Sent from my Galaxy Nexus using xda premium
Thanks for the input ill be movin up to ICS soon
Sent from my SPH-P100 using Tapatalk
flashed sprint Tab
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!
Great Thanks! The first complete step-to-step instruction for installing ICS on Sprint p100.
One note- if you have Error 12 - delete all SAMSUNG USB drivers on PC, rebut and instal drivers from first archive.
At least!!! Thanks a lot!
I don't use the cellular network (sprint) but it does come up and show signal. I don't use it as a phone or anything like some people (supposedly you can install phone.apk and make calls over a voice plan).
I just use the tab as a tab. I just wanted to confirm that it appears to see the cellular network fine.
Sent from my Galaxy Nexus using xda premium
just made the plunge had some issues with the drivers for heimdall and after that i got a fail when flashing hit start again and it flashed
followed all the steps and im on cloud 9 now wow
gonna take a few to get used to ICS
Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2
LivnDream said:
Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2
Click to expand...
Click to collapse
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium
scabrerautexas said:
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!
Click to expand...
Click to collapse
you have nothing to worry about, 3g will still work.. i have flashed many roms on mine including ics ones and 3g still worked.
well i shouldn't say many roms...i've flashed it many times to ics and back to gb.
player911 said:
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its a sprint patch on the rootzwiki fourm for this rom ill get you a link
i got a post there with a link to the patch someone there posted
it changes the wireless from showing veirson to sprint and the tab to sph-p100
wasnt tryin to cause any confusion
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build7-0304/page__st__1040#entry613901
Do I need to be on stock gb or could I do this while rooted? Sorry I'm noob with hiemdall.
Sent from my SPH-P100 using xda premium
As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?
dog44 said:
As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?
Click to expand...
Click to collapse
Try re-downloading the version 5 zip again. Make sure you don't edit anything within the zip before you put it on your SD card. This happened to me when I edited the version 7 zip as instructed above.
Ok. Got it working. What is the newest ver.? I'm on 4.03
Sent from my SPH-D700 using XDA
I think 4.0.3 is the latest ported over. I have a Galaxy Nexus and 4.0.4 was just released... so I would expect delays in porting that over to unofficial devices.
The patch, I've found, is just cosmetic. Once you upgrade to ICS using this method, the build.prop has everything setup as a Verizon Device (name, settings, etc). They can all be manually changed but there is a patch that you can flash via ClockWorkMod that does everything for you.
The link was posted a few posts up.
What is DTI? I may just leave it as verizon since I get more signal. LOL
Hey what's up guys I just threw this on my sprint tab... I had a few quirks with it early... when I first flashed the clockwork mod on it, the screen was discombobulated... the capacitive touch orientation was in landscape mode while the actual screen was in portrait.
So when I had to put the files back on the tab after modifying build 7 zip. I had to figure how to unlock the screen and then and also to choose "connect USB to storage"
Then I got a little nervous while doing the wipe because it took long. I thought it froze..
Just a heads up of what could happen to other guys .
Also now after full install, I find that my ram is usually pretty low and my CPU usage is almost always @ 100 percent .
Taking away from the fluidity... any suggestions ?
I restored my email from titanium back up and also my browser bookmarks, now they don't open up or close immediately. This happens with a lot with system data restored things....
Sent from my SPH-P100 using Tapatalk
Whenever my tab starts it says encryption unsucessful, how can I get past this screen?
NEW KERNEL IS CHARGING. OS DOESN'T SHOW THE CHARGING ICON.
Make sure when you plug in to check the Settings -> Battery screen and see "Charging"
06-28: KERNEL.ZIP #13 IS NOW READY HERE (FLASH IN RECOVERY): REMOVED TEMP
(Recompiling w/o Linaro for compatibility)
md5sum: a16c281fa3dbe0962c6dc2c03e6df5bc
Full ROM: http://bit.ly/NaD2vW
md5sum: d9dfe6f5f97eadbeaecc86d0314cb80e
- Mainline Linux 3.0.31 updates
- TI kernel 3.0.21 branch updates
- [ROM-Only] Now w/ "OtterParts where the touchscreen filter setting can be set (0 as default, but 30 is very usable) -- (Scott Brady)
- Built using Linaro toolchain
- Added KRAIT optimizations (not sure how effective yet) (twa_priv)
NOTE: I haven't adjusted the nightly server to use the 3.0.31 kernel OR Linaro yet. This is the only ROM link I've built with it in it.
[06-27-2012] UNOFFICIAL NIGHTLY SERVER IS RUNNING:
DOWNLOAD HERE
GApps: http://goo.im/gapps (4/29 is the latest in the CM9 row)
These builds are using a stock framework which includes the volume slider mod. It's kept up-to-date by twa_priv.
STEPS FOR UPDATING:
1. Download .zip file from the nightly server and place on your device
2. Reboot into recovery and apply .zip
3. If coming from any ROM which is not CM9 please wipe data/cache/Dalvik Cache
4. Reboot and enjoy
LATEST CHANGES:
[06-26-2012] Added sbradymobile's touch filter patch + OtterParts for controlling the filter level (30 recommended, default as 0 for now) (under Settings -> Advanced) [THANKS!]
SOLO KERNEL NOTES:
06-08: KERNEL.ZIP #12 IS NOW READY HERE (FLASH IN RECOVERY): http://bit.ly/KPbDVm
md5sum: e7476ff785b2dfbdb062e1cc036c14ac
- Touchscreen driver changes (event optimization, ICS friendly)
- Updated the WLAN driver to R5.00.18 (up from R5.00.5)
- Cleaned up the charger code some more (part of on-going charger work)
- Added more support for PPTP and L2TP connections
- [NEW 06/08] Added CCMP support used in 802.11i for EAPOL/WPA2/IPSEC connections using 4-way handshakes (Will fix some users who can't connect to wifi at certain locations)
TROUBLESHOOTING FOR USB not being recognized in Windows 7 (while the Kindle is *NOT* plugged into computer):
- Open Device Manager
- Right-click your computer name and select "Show Hidden Devices"
- The top device group should be: Android device(or phone): under it "Android ADB Composite device"
- Right-click on that and select uninstall
- Now plug the Kindle back into the computer and let driver re-install
IF FOR SOME REASON WIFI DOESN'T WORK ON THE FIRST BOOTUP DO THE FOLLOWING:
Enter Terminal Emulator
Type: su
Type: fix-mac.sh
Exit Terminal Emulator
Reboot
THIS ROM SHOWS OFF HOW WELL ICS CAN RUN ON THE KINDLE FIRE.
** READY FOR DAILY USE **
If I had just installed this ROM and I wanted to see something that might not work in the stock-kernel based ICS ROM, then I'd try the following:
- Install "Chrome Beta" from the market and test it out.
- Audio is more stable.
- Launcher is smoother due to full PVR graphic support
- Try YouTube!
For user support, look to this thread! Please keep discussion here as to what works and what doesn't, etc.
Thanks so much for putting this out there!
I will definitely give it a go once my internet connection stops being so wonky.
Time to play, thanks Hashcode!
Sent from my Kindle Fire using Tapatalk 2 Beta-5
Thanks Hashcode!
btw, I can't get the screen on and it shows
D/SurfaceFlinger( 115): About to give-up screen, flinger = 0x1b5c918
E/libEGL ( 115): validate_display:188 error 3008 (EGL_BAD_DISPLAY)
It's strange!
Awesome work Hash, thank for all the time and hard work your putting into this.
WOOHOO!!!
Ha Ha, my coworkers think I'm retarded. Can't wait.
soupmagnet said:
WOOHOO!!!
Ha Ha, my coworkers think I'm retarded. Can't wait.
Click to expand...
Click to collapse
Lol for buying a kindle? People around me are the same way, thanks hash for all the hard work, can't wait for a stable release
Sent from my Kindle Fire using XDA
Amazing work Hashcode. Simply Amazing.
I cant wait till this kernel is stable.
once again, nice job, i really envy your tallent.
Oddly enough I get bootloops on this right AT the bootanimation. Was running CM9 earlier (which worked fine), but for some odd reason this rom always bootloops on a different part of the bootanimation.
Wiped every single option under CWM. Will probably try TWRP to see if it's any different. The only option I don't see under CWM is "/format boot" so I'm assuming that maybe there are some remnants that are keeping it from booting. I recall from the Nexus S forums that a proper wipe involves formatting system and boot.
I decided to give "fastboot erase boot" a try. I thought that this was going to just wipe out the boot partition. I was then going to flash the boot partition with your boot.img from your zip file, but somehow I still wasn't able to get back into the recovery after doing so. After flashing recovery again, it finally loaded back up. But, at that point I just flashed a nandroided boot.img just to be safe.
I'm not even sure if this line of thinking is correct though, haha. If it is I'll goof with it some more tomorrow.
Or would it be possible to include a line in your installation script to wipe boot as well?
I simply cannot seem to be able to get the screen working. The backlight does start, and sometimes I can see different colours in various lines of pixels, but no picture shows no matter how many times I try the power button. Very strange.
Thank you for outstanding job.
My kindle Fire recycled to boot loop during booting using this ROM. It recycled back to boot at CM animation where it remained for a few second at CM boot animation then boot to boot partition.
Sent from my Amazon Kindle Fire using Tapatalk
Anyone successfully flashed this using TWRP? Can't get it to boot...
Had absolutely no problems booting this on my KF. Works flawlessly so far.
Only thing was the CM9 boot animation was in portrait and cut off.
Oh, and I flashed using TWRP.
Oh, and guess what?! Google Chrome Beta now works!!!!
Some of my other findings...
The audio driver works very, very well! Amazon doesn't seem to have it implemented very well in their stock builds. Notably in apps like Audiotool Sketch which would crash on the first ICS builds because of the original driver and then Squids which soundtrack would simply stutter on both stock and CM9 and now plays beautifully on this kernel.
Sims FreePlay no longer throws the error and you can now download and play it. Looks great on the KF too!
I'm not having any booting issues, that's after now having rebooted twice. I'm having the screen not work when you turn it off and on, ut like you said, just pressing it multiple times fixes it.
Not having anymore issues with the reboot button after a few restarts...
Flash works beautifully.
If you have it plugged in, it'll keep the charge. I've been messing with it for a hour and it hasn't went down anyway.
Hmm, I don't even see a boot anim. This is after wiping everything possible using TWRP.
Strange, what ROM did you come from?
treUse said:
Hmm, I don't even see a boot anim. This is after wiping everything possible using TWRP.
Strange, what ROM did you come from?
Click to expand...
Click to collapse
MoDaCo. Do a wipe of your caches.
I did, I wiped everything, including cache. Came from cm9 tho, maybe, as another user said, boot isn't wiped correctly.
treUse said:
I did, I wiped everything, including cache. Came from cm9 tho, maybe, as another user said, boot isn't wiped correctly.
Click to expand...
Click to collapse
Try factory restore then.
I did a factory reset and cleared both the cache and dalvik cache, prior to installing the FW. It just refuses to show a picture, and there is also no boot animation.
Once, though, I waited for it to boot and then I tapped around on the screen. Somehow I heard dial tones, and a distinct button press "click"
Hello, Im new to this and was able to root my TF101 build .27 with oneclickrecovery V0.4, which installed SUPERUSER v3.0.7
Wanted to install the EOS 4 JB because I read this is very Fast and Stable. This is what is important to me, hence the root.
Now how do I use this and install the ROM?
Is there a youtube or link that someone can direct me to?
Have a look here:
http://www.transformerforums.com/forum/showthread.php?t=33773
You will need to update to TWRP 2.3.2.3 (highly recommended) via GooManager
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I'll alleviate some of your confusion lol, Rouge XM etc are recoveries (that are accessed via holding vol down and power) Easyflasher is a program that runs off your pc and allows you to install a recovery (like Rouge, TWRP or CWM). Easyflasher also works as an unbrick tool (if you do something wrong and mess up your tf101 easyflasher will restore it back to stock)
When using a recovery you need to place the rom on your sd card (some recoveries will only allow flashing from internal or external sd card's not both, but in the case of rouge it access both) then wipe the device (this will get rid of data etc, so if your going to make a back up this is the time) and then wipe everything except for battery stats (it isnt necessary to wipe everything but im not using the same recovery so i cant remember what the options say on rouge so just wipe everything for now) then flash the rom with "install for .zip"(and anything that goes with it i.e gapps or another kernel----- depends on the rom your using) and then just to be safe wipe the devlik cache again and reboot.
hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I would STRONGLY suggest switching to TWRP. Rogue will work for now, but if you flash updates to this ROM, the new file structure for 4.2 will cause your /sdcard/ to end up in the /sdcard/0/ directory, and after another flash it will be /sdcard/0/0/. You can move the files, but IMO TWRP is much better anyway (it can flash from internal and external storage).
You can install GooManager and choose to install open recoveryscript from the menu, or you can use the dd command and a terminal emulator to install TWRP:
First, download the twrp blob from here: http://techerrata.com/browse/twrp2/tf101
Rename the 2.3.2.3 blob to TWRP.blob
Method 1
Open a terminal emulator.
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
It is important to just do a reboot, if you reboot to recovery immediately it WILL NOT update the recovery. Upon reboot, you should see a progress indicator at the Eee Pad screen. Feel free to reboot to recovery after this (even before it boots).
I strongly recommend reading the post by Fredurco in the link he provided. As a matter of fact, read the first three posts. These are the most detailed instructions for any ROM I've ever seen and believe me, I've seen more than a few. Take your time and just follow those directions to the letter and you will be fine.
frederuco said:
IMO TWRP is much better anyway (it can flash from internal and external storage).
Click to expand...
Click to collapse
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...
Thing O Doom said:
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...
Click to expand...
Click to collapse
Yeah, get crackin!
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.
hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
JoinTheRealms said:
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.
Click to expand...
Click to collapse
I agree! EOS 4 IMO is the most usable and stable 4.2 build. My biggest complaint with the CM10.1 build was the touchpad disable was not working. It is still a great ROM otherwise and pretty stable.
As far as 4.1 ROMs, EOS 3 is solid, and so is the CM10/PananoidAndroid hybrid.
I am definitely itching for some cornerstone love!
I use liquidsmooth currently, and it's my new favorite, since everything works. I haven't found or noticed any bugs, which is rare.
EOS4 is also good, but I just don't like the feel of it oddly. Very well built and worth a shot though.
Hi Fred! Dug my TF101 out of moth balls and put on EOS4.
Had some trouble with the drivers, So I ended up using 1 from column A, 2 from column B:silly:
end result, got my drivers, APX mode going, (cross between oneclickrecovery, easyflash, nvFlash, Universal Naked Drivers),
Finally got twrp on and flashed superuser
got twrp-goo manager to update it, Flashed EOS4- saw updated recovery did not stick, finished the flash, updated twrp again, reflashed eos4- saw twrp update did stick this time, and now get to play with the TF 101 all over again!
Everything old is new again!
Thanks Fred! Your post on the TF forum was great, and XDA supplemented what wasn't working for me!! Great teamwork:victory:
Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!
LongbowFoSho said:
Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!
Click to expand...
Click to collapse
I guess I am not sure what is causing your WiFi stability issues. I have no problems with the EOS 4 ROM and WiFi. It never drops out on me. It is perfectly stable, and I can play 720p H264 23.94 FPS mkv files with no issues using MX player.
Before I ran EOS 4, I was running the ParanoidAndroid/CM10 Hybrid ROM and it was just as stable and fast.
If you are having WiFi issues, did you do all the wipes (Cache, Davlik, System, Factory Reset) before flashing the ROM? If not, then that is probably where the WiFi issue is (settings from your previous ICS ROM still present on the data partition).
Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!
LongbowFoSho said:
Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!
Click to expand...
Click to collapse
EOS4 and the CM10.1 No-Name are the only ones getting regular updates.
Thanks for the quick responses. EOS 4 is installed and process of redownloading all my apps. Now I just need to test out some video. I'm testing it without the OC kernel first, just for fun.
If you wanna see more in-depth which rom is better, I recommend a little app called Antutu benchmark, it'll give your current setup a score depending on how fast it does things like 3d renderind, sd card reading and battery performance
I might be in the minority with this opinion, but after some tinkering I'm not all that convinced that EOS is any faster than the stock ROM from a general usability standpoint (even with the latest KAT kernel), but the video is definitely improved, so I'll keep it as my "daily driver".
Thanks for the help, guys!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
Latest build: http://download.cyanogenmod.org/?device=captivatemtd
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Installation
- First time flashing CM11 to your Captivate (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
You will finally see a "set_metadata_recursive" status 7 error. That is normal.
Reboot back into recovery (the reboot is required)
Install the ROM again from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
See here
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
See here
IRC
Join us on #teamhacksung-support (user channel) or #teamhacksung (developer channel)
Changelog
A rough changelog is (will be) available here:
http://changelog.bbqdroid.org/#/captivatemtd/next or http://www.cmxlog.com/11/captivatemtd
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
First!!
Good work mate :good:
Nice :good::good:
how awesome is this! thank you pawitp!
Nice Work Pawitp! Finally Official
Thanks for keeping our outdated device alive. We appreciate all the work you put into it.
Thank you !!
I attempted to try it. I did use the new recommended Gapps. AT&T Captivate coming from CM 10.2 (4.3) stable. It would boot and then gave my a choice of two launchers. The first on I tried gave me intro screens but in about 30 seconds it would go into a soft reboot which it did not recover. I then did a reboot with the power and volume buttons and chose the second launcher. Same intro screen but it went a bit further and showed a few icons (which I did not recognize) and then in went into a soft reboot which again I had to do a reset. This time I wiped the caches and tried another reboot. I decided to wait a while when it rebooted to see if that made any difference. After about 45 seconds it went into another soft reboot. This time I did a restore and I am back to CM 10.2. I am going on vacation so I won't be able to try anything for 10 days.
Same here; not booting.
Mine is stuck at the CM logo and the arrow going round and round the logo.
This has been going on for more than 2 hours now.
Going to pull the battery and try again.
hirent said:
Same here; not booting.
Mine is stuck at the CM logo and the arrow going round and round the logo.
This has been going on for more than 2 hours now.
Going to pull the battery and try again.
Click to expand...
Click to collapse
Please get a logcat
Sent from my Nexus 4 using xda app-developers app
pawitp said:
Please get a logcat
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, I just pulled the battery and booted into recovery.
Wiped everything twice (did it before too) and installed CM11. Rebooted recovery and reinstalled CM11 again.
Rebooted device and voila, it booted up.
Don't know what changed but it booted up this time. I'd wiped everything the first time too.
Anyway, thanks for the work that you have put in. And also for responding above.
hirent said:
Well, I just pulled the battery and booted into recovery.
Wiped everything twice (did it before too) and installed CM11. Rebooted recovery and reinstalled CM11 again.
Rebooted device and voila, it booted up.
Don't know what changed but it booted up this time. I'd wiped everything the first time too.
Anyway, thanks for the work that you have put in. And also for responding above.
Click to expand...
Click to collapse
I believe I did the same thing as you but I kept getting a soft reboot (which it did not recover from) in about 45 seconds to a minute after it booted up. I'll try again when I get back from vacation.
This may or may not be a dumb question lol. Any need for a bootloader flash? I ask because it was required from 4.3 to 4.4 on my nexus 4. Thanks for keeping this captivate alive!
murph187 said:
This may or may not be a dumb question lol. Any need for a bootloader flash? I ask because it was required from 4.3 to 4.4 on my nexus 4. Thanks for keeping this captivate alive!
Click to expand...
Click to collapse
There hasn't been any bootloader updates since 2.3
Sent from my Nexus 4 using xda app-developers app
Wow, wait for a long time. Thanks so much
Sent from my SGH-I897 using XDA Premium 4 mobile app
Should I 4.4? or not yet?
I'm now on hellybean 4.3.1... do you recommend to flash the new 4.4 CM?
Thanks for your help
J o s e p h said:
I'm now on hellybean 4.3.1... do you recommend to flash the new 4.4 CM?
Thanks for your help
Click to expand...
Click to collapse
CM10.2 has now stable release, CM11 is in alpha stage. It's your choice.
Just to say thanks to pawitp for the excellent work!
I'm running Android 4.4.1 on a >3y old device and with the apps I use it's stable enough for a daily driver, no single FC. :good:
P.S. Wow! Fresh start, 190MB free RAM! And it runs smoother than JB! Must taste KitKat...
Val D. said:
Just to say thanks to pawitp for the excellent work!
I'm running Android 4.4.1 on a >3y old device and with the apps I use it's stable enough for a daily driver, no single FC. :good:
P.S. Wow! Fresh start, 190MB free RAM! And it runs smoother than JB! Must taste KitKat...
Click to expand...
Click to collapse
yeah, i'm happy with this rom, but i hope "Cannot send SMS to "premium" number (wait for fix from CM core)" will be fixed soon. I can not send right now
Xperia Z3 Compact, CyanogenMod 12 - official nightly
Since 2015-01-21 CM12 nightly available.
Working:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- GPS
- Compass
- NFC
- OTA update
Reported bugs:
- Audio calls work over loudspeaker, it's usable, but uncomfortable.
- Calling app somebody is a bit laggy - Try turning off "Phone number lookup" in dialer settings
- built in Audio Fx seems to be buggy on BT
- USB OTG
Solved bugs:
- auto brightness is buggy - SOLVED 2015-01-27
- the recovery is _EXTREMELY_ hard to read. It looks like a black screen but if you look closer the brightness is set to minimum or something. - SOLVED 2015-01-27
Download Links:
CyanogenMod 12:
Nightly: link
Changelog:
http://www.cmxlog.com/12/z3c/
Instalation:
- backup current ROM
- download and put cm12 ROM on external SD
- extract kernel from this cm12 zip (boot.img) and flash in fastboot / fastboot flash boot boot.img
- power up phone, go to recovery mode
- do a full wipe
- select Aplly Update -> chose from sdcard1 -> select cm12 nightly zip
- after finish reboot phone
Google Apps i got from here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900 I pick "micro version of gapps"
Click to expand...
Click to collapse
Thanks to veimus for instalation help
crimpy1 said:
Since 2015-01-21 CM12 nightly available.
Download Links:
CyanogenMod 12:
Nightly: link
Click to expand...
Click to collapse
Great, is there a rls log? Or gerrit which shows wants not working?
Sent from my D5803 using XDA Free mobile app
shafiq01 said:
Great, is there a rls log? Or gerrit which shows wants not working?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Changelog:
http://www.cmxlog.com/12/z3c/
Should this thread be posted ?
Does cyanogenmod installer work with z3c
Is it possible to flash it through twrp?
I have kitkat rom now with 23.0.1.A.5.77
Does it require lollipop as base OS before I can flash this *.zip
Sent from my D5803 using XDA Free mobile app
No, you have to flash kernel first from CM12 zip to have a recovery that can handle Android 5
My Easy way is:
- backup current ROM
- download and put cm12 ROM on external SD
- extract kernel from this cm12 zip (boot.img) and flash in fastboot
- power up phone, go to recovery mode
- do a full wipe
- select Aplly Update -> chose from sdcard1 -> select cm12 nightly zip
- after finish reboot phone
Google Apps i got from here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900 I pick "micro version of gapps"
shafiq01 said:
Is it possible to flash it through twrp?
I have kitkat rom now with 23.0.1.A.5.77
Does it require lollipop as base OS before I can flash this *.zip
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
You have TWRP? Where'd you get that?
I have androplus kernel v19c on top of rEctiFy ROM which has the DRM fix baked into the ROM. Awesomeness.
But androplus kernel supports multiROM. Whether it can take the app https://play.google.com/store/apps/details?id=com.tassadar.multirommgr i don't know. But if it could then it would perhaps be possible to have both my current ROM (Kitkat) and the CM12 ROM. In that manner I would have a daily driver and CM12 to boot between. But first I will try the instructions given with the kernel from CM12, I guess it's inside this nightly build?
Sent from my D5803 using XDA Free mobile app
@op, a bunch more info would be cool, what does work, what does not, known bugs and so on...
tapatalked from lollipopped i9300
flashing fails in cyanogen recovery, and i can't use the adb shell to un dim the recovery screen.
im pretty sure i had adb enabled in dev mode before i started.
is there a fix for that?
I saw this on xperiablog, already downloaded the latest build but didn't try and install it yet. It would be great if someone who tried it posted here what works and what doesn't.
I had it for day, and what works:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- and almost all was fine for me..
And now problems:
- auto brightness is buggy
- high battery consumption when my phone was paired to bluetooth car speaker
- from power menu option Reboot = power off
- LED notification are working but you can`t force to different colours (i.e. if i want setup blue color for SMS its always ~amber), charging/battery LED are OK red/orange/green
Anyone able to confirm that the magnetic charger works?
veimus said:
I had it for day, and what works:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- and almost all was fine for me..
And now problems:
- auto brightness is buggy
- high battery consumption when my phone was paired to bluetooth car speaker
- from power menu option Reboot = power off
- LED notification are working but you can`t force to different colours (i.e. if i want setup blue color for SMS its always ~amber), charging/battery LED are OK red/orange/green
Click to expand...
Click to collapse
wow, sounds nice, i would indeed like to have it as well
but i'm failing on flasing part through cyanogen recovery twice now
first i did the way as mentioned in the thread, then i tried the jerpelea thread method by adding the aries in the script
no success, maybe it could be that my external sd card is formated as exFat32, so i could get larger files than 4GB.
meaning cyanogen recovery can't read, perhaps?
now i i've restored my kitkat nandroid backup twice through twrp(nut) after fastbooting androplus kernel.
I've installed it as well now, so far everything seems to work. Auto brightness is indeed buggy.
To get it installed I had to do a few things:
- Extract boot.img from the cm12 zip and flash it with fastboot
- boot into recovery (power up) , the recovery is _EXTREMELY_ hard to read. It looks like a black screen but if you look closer the brightness is set to minimum or something. Turn off all lights (LOL) and flash cm12 followed by gapps.
- unlock developer options to enable root
shafiq01 said:
I have androplus kernel v19c on top of rEctiFy ROM which has the DRM fix baked into the ROM. Awesomeness.
But androplus kernel supports multiROM. Whether it can take the app https://play.google.com/store/apps/details?id=com.tassadar.multirommgr i don't know. But if it could then it would perhaps be possible to have both my current ROM (Kitkat) and the CM12 ROM. In that manner I would have a daily driver and CM12 to boot between. But first I will try the instructions given with the kernel from CM12, I guess it's inside this nightly build?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
MultiROM support requires some work to make the z3c a compatible device - androplus kernel (v19c) has the required kexec-hardboot support for multirom, but multirom manager doesn't support the z3c and no multirom custom TWRP... I would have a go at porting Multirom, but I don't know coding with C very well.... If anybody can code in C, there is a porting guide by the dev here: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
---------- Post added at 10:39 AM ---------- Previous post was at 10:28 AM ----------
shafiq01 said:
wow, sounds nice, i would indeed like to have it as well
but i'm failing on flasing part through cyanogen recovery twice now
first i did the way as mentioned in the thread, then i tried the jerpelea thread method by adding the aries in the script
no success, maybe it could be that my external sd card is formated as exFat32, so i could get larger files than 4GB.
meaning cyanogen recovery can't read, perhaps?
now i i've restored my kitkat nandroid backup twice through twrp(nut) after fastbooting androplus kernel.
Click to expand...
Click to collapse
I had the same problem, tried three times (even shut myself in a really dark room to see if i could read the recovery logs!) - I started thinking the issues must be with accessing my external sd card (mount issues?), so I moved the cm rom zip to internal/sdcard0 and flashed again, it worked perfectly! Done the same thing with Gaaps, worked!
We really need TWRP (or CWM) as the cm recovery is a bit pants (no offence intended to CM), no nandroid backup/restore, mount tools etc).
I have spent about six hours playing with and "customising" the rom - I'll post my experiences/issues soon...
Translate
Thanks
A lot of big update on next nightly , I
I would like to know how translate CM12 ?
I find this for CM11 : https://crowdin.com/project/cyanogenmod
but nothing for CM12 and no files strings.xml here : https://github.com/CyanogenMod/android_device_sony_z3c
Thanks
mick711 said:
Thanks
A lot of big update on next nightly , I
I would like to know how translate CM12 ?
I find this for CM11 : https://crowdin.com/project/cyanogenmod
but nothing for CM12 and no files strings.xml here : https://github.com/CyanogenMod/android_device_sony_z3c
Thanks
Click to expand...
Click to collapse
Looking forward to all those changes. I'm tempted to try this as a daily driver for a few days, but the brightness is driving me a bit nuts having to set it manually. Don't see any fixes listed for it in the next nightly.
I installed and seens all fine. Couldn´t install using TWRP from AndroPlus Kernel. Needed to flash the CM boot.img and than try to read the recovery menu lo/
But all seens fine, so far
For next, nights, all i need is wipe cache/dal and apply update like now?