Database Users

[ROM] Deodexed rom with root

Thanks to anomalous3 over on the vibrant forum he was nice enough to port over his rom to our side based off of the new source code released by samsung
"If you feel like being a guinea pig, or know anyone who does, the deodexed build is here:
http://getyourboneon.com/CaptivateDeodexed.zip
Since I don't have a captivate I can't really test it, but it should work fine. It's based off that UCJH2 build. I didn't include any lag fixes since they've proliferated out of control, but I did include ext manipulation libraries and e2fsck to make life easier for people who want to use one of the lag fixes."
Please note I have NOT tested this rom yet, I don't have my captivate. Please somebody could test this and let us know if there's any problem so we can let him help us fix it.
Again, not responsible for whatever happens to your phone.
Here is the original thread I posted for reference.
http://forum.xda-developers.com/showthread.php?t=746466
EDIT: I'm going to assume you would install this like any other rom via update
EDIT2: anomalous3 has updated the link with corrections. Let us know how it works

Well... since I can't seem to get enough of abusing my phone, guess I'll give this a whirl =P
And I have JH2, So I suppose that makes me a good candidate

Zilch25 said:
Well... since I can't seem to get enough of abusing my phone, guess I'll give this a whirl =P
And I have JH2, So I suppose that makes me a good candidate
Click to expand...
Click to collapse
let us know how it goes

Do I just rename this to update.zip and go recovery and reinstall packages?

And when I try it and my phone crashes I'll blame Zilch because it's convenient.
Sent from my SAMSUNG-SGH-I897 using XDA App

Will do, flashing back to a stock JH2 while I download! I've been waiting for something like this

Clienterror said:
And when I try it and my phone crashes I'll blame Zilch because it's convenient.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It probably was my fault anyway =P

Wait a sec, what does deodexed mean? I looked it up and it means no oxded files, but i don't know what those files are...

damn it, wish this was around 2 hours ago when i was bored! its too late now to ruin my phone haha.. tomo sometime maybe i'll try..

Question...Do I have to install the stock Captivate ROM first as it states in the linked post? I have the stock ROM that is rooted with the AT&T bloatware removed. The only other mod is the lagfix version 2.3...Can I just flash this over that?

you should be able to, according to his original thread on the vibrant forums, the directions were to put on internal sd card and load via clockwork best method. or via recovery mode works too

nammyczc said:
you should be able to, according to his original thread on the vibrant forums, the directions were to put on internal sd card and load via clockwork best method. or via recovery mode works too
Click to expand...
Click to collapse
That's what's taking me so long... seems like JH2 is having some issues with update.zips... namely it's getting to the "Opening installer" then "Install Aborted". The(not new) update.zip for root still works, so I'm tossing on clockwork to see if I can get this thing crammed on here with that.

Installing from Clockwork:
Hoses up during the copying files stage
E:Can't symlink /system/bin/bugreport
E:Failure at line 5:
symlink dumpstate SYSTEM:bin/bugreport
Then install aborts

Zilch25 said:
Installing from Clockwork:
Hoses up during the copying files stage
E:Can't symlink /system/bin/bugreport
E:Failure at line 5:
symlink dumpstate SYSTEM:bin/bugreport
Then install aborts
Click to expand...
Click to collapse
That's because the capitvate uses a different independent bugreport that is not a symlink of dumpstate.
Simply edit the update script in the meta folder and remove that line.
I deodexed the actual captivate files the other day, just havnt tested/posted them, way too busy with school

BuglessPete said:
That's because the capitvate uses a different independent bugreport that is not a symlink of dumpstate.
Simply edit the update script in the meta folder and remove that line.
I deodexed the actual captivate files the other day, just havnt tested/posted them, way too busy with school
Click to expand...
Click to collapse
I'll pm him about this

nammyczc said:
I'll pm him about this
Click to expand...
Click to collapse
Also ask him why superuser.apk is in the xbin folder.

vietphunguyen said:
Wait a sec, what does deodexed mean? I looked it up and it means no oxded files, but i don't know what those files are...
Click to expand...
Click to collapse
-From googling, found on XDA:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.

golemaw said:
-From googling, found on XDA:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
This is correct. Deodexed ROMs can be themed...

BuglessPete said:
Also ask him why superuser.apk is in the xbin folder.
Click to expand...
Click to collapse
Good catch on that one Yeah, it surprised me that a lot of the stuff in the captivate doesn't rely on toolbox either. I might even port that over to the Vibrant since I think that toolbox is a stupid vestigial substitute for busybox anyways. Link updated, let me know if it works.

anomalous3 said:
Good catch on that one Yeah, it surprised me that a lot of the stuff in the captivate doesn't rely on toolbox either. I might even port that over to the Vibrant since I think that toolbox is a stupid vestigial substitute for busybox anyways. Link updated, let me know if it works.
Click to expand...
Click to collapse
updated original post with info

pre-rooted stock 6.2.1 update

See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?

AndrewTL said:
See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?
Click to expand...
Click to collapse
You need to go through all the lines of code for that and I believe some of them are binary files as well. Possible but will take much time. For now we must wait until someone finds a better solution.
Sent from my Kindle Fire using Tapatalk

signature issues.

6.2.1 experiment?
transfuntioner said:
signature issues.
Click to expand...
Click to collapse
Maybe I don't follow the process.. but I'm guessing no signatures..
not a signed bootloader.. no signatures required...
Get beyond compare and look at the differences between the OTA updates and the zip that Eldarerathis put together.
The ".bin" files are just ".zip" files renamed.
Look at
META-INF/com/google/android/updater-script in the bin files they release.
It is just a script.
And to do the things that it is doing, it has to be getting root permissions while it is running.
I don't know how to recover if it doesn't work, but I half wonder if you were to take the zip that fellow created, change the extension to ".bin" and just dump it into the update folder if the fire would install it for you?
He took out the image files from the script. He's just updating the system tree directly. He doesn't update the bootloader, recovery or backup trees.
For that matter if those contained something nasty, they could probably be pulled from an earlier update.
== cut ===
package_extract_file("recovery.img", "/dev/block/platform/mmci-omap-hs.1/by-name/recovery");
show_progress(0.100000, 10);
package_extract_file("u-boot.bin", "/dev/block/platform/mmci-omap-hs.1/by-name/bootloader");
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup", "/backup");
package_extract_file("backup_userdata.zip", "/backup/backup_userdata.zip");
== cut ===
Please nobody try this idea that doesn't know enough to recover if it doesn't work, because I've not a clue how.
But could someone explain why wouldn't it work?
Worst case the rev might need to be manually edited to bump it one for the script.
Seems like it might be an easy way to get around headaches with OTA updates.

Andrew,
Are you having issues with getting into recovery so that you can test this? The Devolopers have a copy of TWRP 2 working perfectly on the device so you can get a clean backup of the OS before you test.
You sound like you may know what to do to fix the issue and I just want to help you get a good recovery in case it doesn't pan out or for testing.
~enjoy.

Actually I'm just afraid of messing up what I have working now.
I've got TWRP 2 running with the 6.2.1 image.
I'm setting these up as gifts. I spent a good 12 hours yesterday fighting the darn things. Guess I'm getting gun shy. Had a lot of issues with adb. Kudos to the new utility and setting the second ports up. I'm learning.
The OTA install wipes the system directory. It's in the script.
I was tempted to just comment that line out and see if it would leave the rest alone.
If I brick the thing its going to be painful for me to sort out.
I also didn't want to risk losing root. I also haven't tried loading an older OTA version.
At the time, I couldn't ask the fellow that developed the rooted 6.2.1 zip the question in his thread as I didn't have enough posts.
I'm going to be out of pocket for quite some time. I'm not going to have time to spend like this again for at least a few days.
But I was checking the zip he made versus the .bin/.zip files that the OTA releases using beyond compare. I wanted to see what files had actually changed.
That's when I found that script. It is manipulating permissions directly. It has to be running at a root level. I don't see anything like a signature on it, so why couldn't their own update system be used to tweak their own updates to allow for root?

[SCRIPT] No-lag solution to CM7/9 "low memory" notifications (STEP BY STEP,FIXED TB)

[SCRIPT] No-lag solution to CM7/9 "low memory" notifications (STEP BY STEP,FIXED TB)
23/01/12 - Now with Titanium Backup support!
The Titanium Backup team is awesome. I contacted them and within 3 days they had a working fix. To make sure that titanium backup works properly all you need to do is download the latest version from the market, go into 'preferences' and select 'follow all symbolic links' in the 'Troubleshooting' section at the bottom. That's it. Now you'll be able to backup normally and then restore your apps in any other rom. Neat!
Click to expand...
Click to collapse
Okay, I've found a rather excellent solution to the low storage problem that plagues the CM7 and CM9 roms - without causing the lagginess of the ".nodatadata" approach. It's not my work but was posted by drefnel on the Cyanogenmod forum. It's very smart: instead of moving the whole of /datadata (fast yaffs2) to /data (slower ext4) and so introducing lag it keeps most apps' non-performance critical data on /data and moves performance critical sqlite databases and xml preference files to the fast /datadata.
Installing this fix is a two step process:
Phase 1 - some prep, takes around 10 minutes to complete. Only has to be done once.
Phase 2 - running the script whenever you've installed new apps and used them once or twice. this just involves hitting a shortcut on your home screen. boom!
The original guide can be found here we need to make a few alterations and I've done a step-by-step below:
Step by step guide
I take no responsibility if using these instructions messes up your phone. They worked for me and you should always be able to restore using the clockworkmod backup. But you can't say you haven't been warned.
Make sure you're running CM7 or TeamHacksung's CM9 or Onecosmic ICS.
This will NOT work on encrypted phones.
DO A NANDROID BACKUP BEFORE YOU BEGIN.
Phase 1 - (if you've already used the ".nodatadata" method then start at step 4)
1. Download Terminal Emulator
2. Open terminal emulator and then enter each of the following followed by return:
su
touch /datadata/.nodatadata
3. Reboot (this might take a while as the OS will be making changes to your filesystem).
4. Open terminal emulator and then enter each of the following followed by return:
su
rm /data/data/.nodatadata
5. Reboot into recovery, go to "mounts & storage" and then select "format datadata". Reboot normally.
6. Go to the market and download GScript Lite. Open it and close it again - this should create a folder called "gscript" in your sdcard. Unzip the file attached in this post and place the script in it in that folder.
7. Open up GScript Lite, press menu and add script. Click load file, select the script file, make sure that "needs SU" is selected and click save.
8. Run the script by tapping it. You should see GScript report its progress and finally the script should finish. Press close and gscript will crash out (can't have it all ).
Phase 2
Add a shortcut to this script on your desktop.
CM7 - long-press and hold a blank area of your home screen, select 'add shortcut', and then select 'gscript lite'. select the script you've just added.
CM9 - go into your app drawer, select the 'widgets' tab, find 'gscript lite', press and hold it and move it onto your home screen. select the script you've just added.
You should use the shortcut after you've installed new apps and used them a few times. There's no harm in not using the script for a while, all that will happen is that app may become a bit laggy until you use the script to move its data to /datadata.
That's it. Congratualtions!
You can flash new CM roms and the script will carry on working fine, but if you wipe data in recovery then you'll have to start from the beginning
You won't be able to easily go back to the original configuration or use the ".nodatadata" method (you'll need to Titanium Backup, wipe everything and then restore), but you'll never miss them.
Good luck
I hope this helps people out. We should find a way of better automating the steps to make it more noob friendly and maybe Team Hacksung and One Cosmic could incorporate it into their ROMs. (Essentially the script needs to be run periodically to make sure that the performance critical /data/data elements of new apps are copied across to /datadata - apart from that it's not too different from the ".nodatadata" approach).

Personally using the much simpler .nodatadata approach, i found that after a rom (cm9) install, most lag goes away after using it for a few hours, although I have heard the speed of the flash memory is not equal on all devices... so could be laggy for some regardles of usage.

Yup I've tried both and the script approach is definitely much quicker in my case. I'm going to see if I can simplify this procedure somewhat.

Sorry for being a noob.. I am not sure how to apply the script to my Android device... Should I use Terminal Emulator on my Galaxy S and type the script in there? Would you mind to guide me through the process? Thanks a lot

Now with a step-by-step guide.

Man you are awesome! Thanks for your guide!

Wouldn't it be an idea tu use scriptmanager (free or pro) instead of gscript? it can run scripts on boot.
Maybe later, when the standard kernel for cm9 will support init.d, it can be an init.d script?
And oh, I will put a link to this thread in the wiki, you can edit the wiki yourself also if you ask for acces.

seem like there is no one try on OneCosmic, and im going it a shot!
will report later~

Zatta said:
Wouldn't it be an idea tu use scriptmanager (free or pro) instead of gscript? it can run scripts on boot.
Maybe later, when the standard kernel for cm9 will support init.d, it can be an init.d script?
And oh, I will put a link to this thread in the wiki, you can edit the wiki yourself also if you ask for acces.
Click to expand...
Click to collapse
Good points. The reason I chose GScript was its user friendliness and simplicity. There are define advantages in running this script at boot. (I'd much prefer to have things run automatically before the GUI appears (as in init.d) rather than clog up GUI boottime as Script Manager would require.)
The phenomenal uptime I get with Android means that I don't reboot very often. Ideally we'd want something that monitored the data/data folder and ran the script on the appearance of new folders. I'm not sure how you'd automate that without resorting to Tasker. Maybe init.d is the best we can do when it's supported. In the meantime a GScript shortcut on the desktop that I hit once every couple of days feels like the best option so far!
Sent from my GT-I9000 using XDA App

Code124Y said:
seem like there is no one try on OneCosmic, and im going it a shot!
will report later~
Click to expand...
Click to collapse
Tested on OneCosmic and it working good for all but picture/gallery gone...
what i mean is it scan no photo nor any image on my phone~
using gallery+ giving me the same view(nothing in gallery)
but other then this 2 gallery, im try with quickpic also and yup it show pic~
but i want the original picture gallery from the 4.0.3... any help?

There are more advantages in scriptmanager. You are not bound to a specific location on the scared for example, with gscript it has to be in /sdcsrd/gscript folder. And you can make a widget with this script in it, making it a one-click operation but I believe that is a paid feature (and gscript can do something similar, no?)
On the other hand, it is as you say, a bit more complicated.
Also making it a init.d isn't a full solution. Every update from the ROM will wipe the /system/etc/init.d so the script needs to be reinstalled.
Maybe a cwm-flashable would be needed than, everybody here can flash. In that case also the initial commands could be run during flashing.
Taptalked u see

Zatta said:
...Maybe a cwm-flashable would be needed than, everybody here can flash. In that case also the initial commands could be run during flash
Click to expand...
Click to collapse
Yup, a flashable zip which runs initial commands and then appends on an init.d script seems like the way to go. Once the CM9 kernel supports I'll learn how to make these (essentially lazy, me)
BTW, making a one click operation from GScript is easy. Just add the GScript shortcut to your home screen and it will prompt you which script you want to run on click (remember that shortcuts are now grouped with widgets in ICS)
Sent by airmail.

Code124Y said:
Tested on OneCosmic and it working good for all but picture/gallery gone...
what i mean is it scan no photo nor any image on my phone~
using gallery+ giving me the same view(nothing in gallery)
but other then this 2 gallery, im try with quickpic also and yup it show pic~
but i want the original picture gallery from the 4.0.3... any help?
Click to expand...
Click to collapse
Have you tried clearing the data for the gallery app? Worth a shot.
Sent by airmail.

revthanki said:
Have you tried clearing the data for the gallery app? Worth a shot.
Sent by airmail.
Click to expand...
Click to collapse
not needed already, becoz reboot seem to be fixed...
Samsung galaxy S GT-I9000 miui.us latest rom

I just have a question popped up in my mind, after applying this script,when I update my teamhacksung ROM in the future(i.e the future build15), will it causes any problem / break my phone?

leolee0209 said:
I just have a question popped up in my mind, after applying this script,when I update my teamhacksung ROM in the future(i.e the future build15), will it causes any problem / break my phone?
Click to expand...
Click to collapse
Absolutely shouldn't, as long as pawitp doesn't ask you to wipe data. If he does then you'll have to start again
Flash away!
Sent by airmail.

People, beware that this will break your TitaniumBackup, I was tested myself

Funnnny said:
People, beware that this will break your TitaniumBackup, I was tested myself
Click to expand...
Click to collapse
How do you mean? A bit more detail please. It really shouldn't, as Titanium Backup does respect symbolic links...
Sent by carrier pigeon.

mispost
10 char

Originally Posted by Funnnny<br />
People, beware that this will break your TitaniumBackup, I was tested myself
Click to expand...
Click to collapse
<br />
<br />
How do you mean? A bit more detail please. It really shouldn't, as Titanium Backup does respect symbolic links...<br />
<br />
<br />
Sent by carrier pigeon.
Click to expand...
Click to collapse
When I backup, wipe and restore, titaniumbackup just restore the symlink, not the actual data
Sent from my GT-I9000 using Tapatalk

[ROM][KANG] CherryKANG 0.9.4 1512max 384min [CM9] synced [11/04] Now supports goo.im!

Hi guys..
I just want to say thanks to the cm team for bringing ics to our touchpads. None of the work in this rom is my own.. I have just used the great tutorials and stuff I've picked up before to compile this. All credit to everyone who put work into this!
This rom includes cherry-picks from http://review.cyanogenmod.com such as the fixes below
A wifi fix -- review.cyanogenmod.com (Although some people are reporting wifi issues still. I recommend a full wipe)
I have also compiled my own kernel into this.. which I set the default CPU speed to 1.5ghz and the default governor to ondemand. I also added HAVS support. Although I don't know if we really need it on a tab. Maybe it will help slightly with battery life?
These are settings that I like and normally run. So don't flame me!
I am looking for pointers too.. for what to do next. I would like to add the webOS style recent apps mod next. Also ROMControl would be nice from here .. some pointers on how to include would be helpful. Any help greatly appreciated
So.. please remember.. I made this for myself... to teach me something.. someone just said I should post it!All credit goes to the people that contribute to cyanogenmod.
Cheers and enjoy
Buy me a beer if your a fan! Hit donate!
IN THIS BUILD
0.9.4 --- UPLOADING AS WE SPEAK!! Check back in an hour
Hopefully now has Goo.im app support for ease of updates
Not much else (synced 11/04)
managed to put this quick one together in the midst of everything.. so not had much chance to test. let me know how it is.
DOWNLOADS
http://goo-inside.me/devs/philicibine/ Thanks for hosting! Loving the download numbers here guys .. thanks for the support
http://www.cherrykang.mythreed.com/CherryKANG/ Big thanks to @Jedipottsy for this one.
Thanks for all the support from everyone!
Gapps are not included
My antutu benchmarks have been over 6000 btw
Hit the thanks button!
Previous Builds
0.9.3
Now with 4.0.4 inside!!
New Cyanogenmod boot animation!! I left this in coz it looks cooool
Min CPU clock is 384 (No more SoD's!)
Synced 31/03
Lots of new commits so YOU MUST FLASH GAPPS AGAIN!
0.9.2
Min CPU clock is 245 now.
Synced 10/03
Lots of new commits so YOU MUST FLASH GAPPS AGAIN!
0.9.1
Synced 08/03
Netflix and YouTube HD FIXED -- Thanks to wtogami for his cherry-pick script.
0.9
Synced 07/03
Now has stylus input merged
unsure if netflix works yet (please test) and.. nope! It doesn't :'-(
CherryKANG-Bricked
AS REQUESTED -- No changes.. just a bricked kernel thanks to show-p1984
0.8.9
At last it works! Lol
Synced 28/02 should have Netflix - edit - doesn't
Wifi fix
120 dpi - see post 2 for market fix
CherryKANG wallpaper - awesome!
0.4.8a
Kernel rebaked into it. should be lots smoother now
0.4.4a
kernel and wifi fixed
nothing else changed just wanted to get back to a working state
0.4.1a
re-done kernel as last build compiled with standard cm kernel
0.4a
Removed 270 degree rotation coz it derped the bootup :-/
Recompiled the kernel and increased min cpu to 245 (sleep issues)
0.3a First CherryKANG named build! lol =D
270 degree rotation
dpi set to 132 (Requires fixed market apk)
wifi scan interval increased
0.2a
Novalauncher - hope its OK?!
Scrolling cache fix - for smoother scrolling in the browser and other apps. (Kanged from aokp github) credits to them
And a pretty tasty boot animation! From MindSplit - thanks!
Hope you likey

REMEMBER ... This is now 120 dpi. You will either need to download LCD Density Pro from the market, or see below for a free alternative!
Posted by Hockey4life0099 thanks!
or you can use the free version (or dpi changer) to modify the dpi back to 160
---------- Post added at 02:15 AM ---------- Previous post was at 02:03 AM ----------
I wrote this. It looks more complicated than it is cause i broke it down step by step. Ignore my cracked out numbering scheme, i didnt feel like shifting all the numbers down when i added more info.
1. If you dont already have it, download es file explorer
1b. go to the application settings and clear the data for the market
1c. download dpi changer and change dpi to 135(dont reboot yet)
2. go into the options on there and check the root explorer option and the mount option
3. download to TP
http://www.sundergaming.com/downloads/tabletmarketdpiunlocked.apk
4. rename the file Vending.apk
5. long press to copy the file (in ES file explorer)
6. click the star in top right corner (favorites)
7. Choose the phone (/)
8. navigate to system/app
9. paste the app
10. find the app in there called marketupdater.apk or something similar and rename it marketupdater.apk.bak
11. reboot
12. see if you can download an app like flash player. If you cant go to next step
12b. get back to system/app and click the Vending.apk and let it install.
You can mess around with the dpi if you want, but also remember that if the text is small, you can change the default text size in the settings.
The issue i encountered with this method is sometimes the fix stops working, but all you need to do to get the apps to download once again is clear your market data in the application settings. It is obviously much easier to download the app mentioned in the op, but this is for the cheapskates. your only other option is download dpi changer and just switch the dpi back to 160. That is painless but you loose out on some app compatibility and some screen real estate. I myself change the dpi to 138 and change the font size to large. Everything seems to be perfect. Best balance out there IMO.
nevertells2 said:
Do not install CM9 over CM7. Some have gotten away with it and others like yourself run into trouble. Do a clean install, that means running ACMEUninstaller. Here are some instructions I created just for an occasion such as this:
Since the release of CM9, it has become abundantly clear to me that one
needs to do a clean install of the rom to avoid all the little
nagging issues that so many folks are reporting. Whether you are
installing for the first time, upgrading from CM7 or installing
an update of CM9, one really needs to do a clean install.
Since the advent of the official CM9 nightlies, installing
the rom and the Gapps files via CWM seems to be much more
reliable. You still need to wipe the cache and Dalvik cache
before you reboot after installing any rom. If you run into
trouble after an install via CWM, then read on.
Those who know how to do it otherwise and are comfortable with that
feel free to deviate from this document.
For first time installers, you can skip this part. First thing
you need to do is a nandroid backup of your current install and
copy it over to your PC for safe keeping. Next you should backup
your apps using either Titanium Backup or My Backup Root. This will
allow you to restore all your apps after you are done with this
update. If the install goes South, you can always restore your
nandroid backup.
For the first time installers, if you have not already prepared
your PC for this project, you need to download the following:
1. ACMEInstaller2
2. ACMEUninstaller
3. Moboot 0.3.5.zip
4. ClockworkMod.zip(CWM)
5. update-cm-9.0.0-RC0-Touchpad-alpha2-fullofbugs.zip
6. UniversalNovacomInstaller.jar
7. The latest Gapps.zip
The ACME files, Moboot, CWM and the Alpha2.zip can all be found
on the OP for Alpha2 at:
http://rootzwiki.com/topic/18843-releasealpha2-cyanogenmod-9-touchpad/
The universal novacom installer and Gapps files can be found by doing a Google
search on the names above and you will find the download page. I found
the novacom installer here:
http://universal-novacom-installer.googlecode.com/files/UniversalNovacomInstaller.jar
You should download the latest Gapps.zip which
the last time I checked at the link below was 20120317:
http://wiki.rootzwiki.com/Google_Apps
First thing, open the run box on your PC and browse to the novacomInstaller
file. This is a Java executable, so treat it just like any .exe file.
However, since it does not end in .exe, when you browse to find it,
you will have to tell the browser to show "All Files." Once it is in
the run box, click on OK and the Novacomd drivers will be installed,
the Palm,inc folder will be created and the novacom.exe will be placed
in that folder. Next if the ACME files you downloaded are zips, unzip
them both into the Palm, Inc folder which you will find in the Program
files folder. If not zipped, copy both into the Palm, Inc folder. Now
your PC is prepared for installing CM9, so everything applies to first
installers and upgraders from this point forward.
First timers boot into WebOS, upgraders can do the same or boot into
your current install of Android. Connect your TouchPad to your PC
with the usb cable and open Windows Explorer on your PC. You should
see either the TouchPad as a drive, or cm_tenderloin if you are already
running a version of CM9. If you have not already created a cminstall
folder on your TouchPad do so now. Also create a folder named ICS
Install.
Next you need to copy Moboot 0.3.5 and ClockworkMod(CWM) into the
cminstall folder on your TouchPad. Now copy the rom.zip and the
Gapps.zip file into the folder you created named ICS Install. It's up
to you which rom and Gapps file you use if you are installing something
different from what is listed above. If you are copying files to the
Touchpad drive, you now need to right click the drive letter and eject
the drive when you are done. If you are copying files to cm_tenderloin,
you can just close Windows Explorer and both of you disconnect the usb cable.
Upgraders, now you need to run ACMEUninstaller and when it is done, your
TouchPad will reboot back into WebOS. Now both of you need to reboot while
holding down up volume to put the TouchPad into WebOS recovery or bootie
mode. You will know you succeeded if you see a large white usb symbol.
Now plug the usb cable back in and you should hear the PC beep indicating
the TouchPad is connected. You will not be able to see the TouchPad in
Windows Explorer, so don't try. On your PC click "RUN" and type in CMD.
This opens the command window. First timers type in the following in the
command window:
cd/ and press enter. You will see C:\
Now type cd program files and press enter. You will see C:\program files
Now type cd Palm, Inc and press enter. You will see C:\ program files\Palm, Inc
Upgraders, your novacom.exe may be in a different folder, so go browse to that folder.
Both of you enter novacom boot mem:// < ACMEInstaller2 in the command window and
hit enter. After a few seconds, you should see what is fondly called the "Double Penguin" on
the Touchpad. When the install is done, the TouchPad will boot to Moboot. Tap
the volume on the TouchPad to stop the 5 second countdown if you see one. Now
select CWM using the Home button, then Install zip file from SD card and use the
volume rocker to move down to the ICS Install folder. Select that and move to the
Alpha2.zip and select that. Start the install. When it is done, use the go back
selection to go back to the main CWM screen and select reboot.
Once Android is booted up(be patient, it takes a couple of minutes the first time),
play around with the browser, set up wifi, just to make sure your install was
successful. Now reboot back to CWM and do the same procedure to install the Gapps.zip
you copied to the ICS Install folder earlier. You're done with a clean install.
Upgraders, you know what to do, first timers, I hope you have friend around to show
you the ropes or you own an Android phone and already know the ropes. Good Luck!
P.S. I strongly suggest you make a nandroid backup of your new installation right now.
First timers, one makes a nandroid backup using CWM. Boot to CWM, select "Backup and
Restore" and select "Backup".
Click to expand...
Click to collapse
Sent from my cm_tenderloin using xda premium

what's the wifi fix ?

This one http://review.cyanogenmod.com/12342
Sent from my cm_tenderloin using xda premium

Does this have Gapps cooked into it?

No sorry... I'm using v11 though
Sent from my cm_tenderloin using xda premium

Ok thanks...

If we have CM7 installed do we do a factory reset/wipe of the caches and then install the zip directly?

dtwconsulting said:
If we have CM7 installed do we do a factory reset/wipe of the caches and then install the zip directly?
Click to expand...
Click to collapse
Yep.. I think so. I think you can also flash without a wipe.. but wouldn't recommend.. and if you do.. flash the latest gapps
Sent from my cm_tenderloin using xda premium

Cheers mate

hi, whats the webOS style recent apps mod you mention in the OP?

Drop Box link already dead
Any one have a mirror?
Thanks!

MatthewYiu said:
Any one have a mirror?
Thanks!
Click to expand...
Click to collapse
Still working for me as of 10:40am. But.... here's a mirror just in case.
http://www.mediafire.com/?q60g82098q1vh16
Gapps v11:
http://goo.gl/u9s8g
For additional related files and mods, see sprice's thread here:
http://forum.xda-developers.com/showthread.php?t=1452324

f_padia said:
hi, whats the webOS style recent apps mod you mention in the OP?
Click to expand...
Click to collapse
When u hold home.. the apps come across the screen horizontally. Looks like the card feature of webOS.
Its in AOKP so I might have a look at their github later.
Sent from my HTC Vision using xda premium

tapout27 said:
Does this have Gapps cooked into it?
Click to expand...
Click to collapse
Read much?

how about hw acceleration?

mercado79 said:
Still working for me as of 10:40am. But.... here's a mirror just in case.
http://www.mediafire.com/?q60g82098q1vh16
Gapps v11:
http://goo.gl/u9s8g
For additional related files and mods, see sprice's thread here:
http://forum.xda-developers.com/showthread.php?t=1452324
Click to expand...
Click to collapse
flashing now! =)

Hello,
is the wifi fix included in the kernel? if so, is it possible to make a only a kernel-package to flash with CWM over the standard CM9-0.6?
Thanks

Not quite sure how to do that just yet. Will look at some other kernels tomorrow
Sent from my cm_tenderloin using xda premium

coolineho said:
how about hw acceleration?
Click to expand...
Click to collapse
This is just a kang. I lack the knowledge to even attempt looking into that!
Its working the same as cm
Sent from my cm_tenderloin using xda premium

[RECOVERY][CWM] JCSullins CWM Recovery 6.0.1.9 [2012-12-04]

Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**

menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2

menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:

"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.

chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .

*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.

I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.

Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app

It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.

I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.

Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.

jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.

jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T

New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob

RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T

.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:

Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app

Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:

jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.

Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery