Database Develop

[Release] HTC Sense Transparent LockScreen

Very old mod. Probably no longer works. Use at own risk. No longer supported by me.
ROOT REQUIRED
ONLY works on ROMS that include HtcLockScreen.odex.
So it wont work if you've flashed lwp patches, Sprint ROMS or anything that removes the .odex file.
-------
Originally created by JsChiSurf over in the Hero forums via my encouragement This version is made for the Eris, it is not the same as the Hero version (which doesn't work properly for us).
This is a modification of the STOCK HTC Sense lockscreen that removes the background so you can see your homescreen behind it.
*Users need to already be comfortable with using 'adb' I won't be providing support on that since there are numerous threads with instructions all around.*
**Before** pushing the apk into that folder, you'll need to FIRST perform the following steps to remove the stock lock wallpapers from loading, as well as any cached custom wallpaper you have applied. You can perform these via adb as listed, or if you have Root Explorer (on the marketplace), you can navigate to the folders listed and delete the items that way.
Code:
adb remount
adb shell
cd /data/misc/lockscreen
rm *
cd /system/customize/resource
rm htc_wallpaper*
exit
Note: You may or may not have anything to delete in /system/customize/resource, so if you get an error message while using adb, don't worry.
HtcLockScreen.zip MD5: 9423D8C3D6CBBF3E084CD185130F9649
*APK NOTE: APKs are case sensitive, be sure you install this without renaming it, or it wont overwrite your original APK*
After you extract the zip to your sdk/tools directory perform the following (case sensitive):
Code:
adb push HtcLockScreen.apk /system/app
adb reboot
If you get "read-only" errors, try "adb remount" OR "adb shell", then, "su", then "mount -o rw,remount /dev/block/mtdblock3 /system" and then the other commands.
EDIT: Clock-less version now available for download! Same instructions apply.
Clock-less Info: **Since some users may have performed the 'experienced users' steps below, an Android image has been added to 'lockscreen_topedge.png' so that it isn't 100% transparent.
If you want to remove this image: First, download the ZIP below with the PNGs, take any one of those and rename it to 'lockscreen_topedge.png, open the lock apk in your favorite zip file manager (winzip, winrar, 7-zip), navigate to "res\drawable-normal-mdpi" and drag your newly-renamed PNG in there. If a dialog pops up, be sure you select the option that has NO compression, this is usually called "Store."**
Make a post if you have any problems NOT related to 'adb.' Again, support is not provided for that.
Clockless Lock.zip MD5: B604B530E02C47DA81AD8B4563BE71D2
__________________
Now some optional additional steps for **experienced users only** (I suck at tech support so if you ask something, I'll try to answer, but no guarantees):
If you put the PNGs included in the zip below into 'com.htc.resources.apk\res\drawable-mdpi', it will remove the HTC "Arc" on the lockscreen. Now, to create your own Arc replacement, all you'll need to do is go into 'HtcLockScreen.apk\res\drawable-normal-mdpi' and change the lockscreen_topedge.png to your liking A much easier change than fiddling with your resources apk everytime and its only 1 image to change, instead of trying to line up three. Of course, if you remove the Arc and do not change your lockscreen_topedge.png, you will have a completely invisible lockscreen, so don't freak yourself out, just make something for that PNG.
*Does not seem to work with Hero or Legend ROMs*

I've used adb push (to change my boot animation) but I can't say I know how to use it.
Can you specify which commands to use?
EDIT: do you have to have root for this?

Yes you have to have root. You would do 'adb install HtcLockScreen.apk'.

wshuman3 said:
You would do 'adb install HtcLockScreen.apk'.
Click to expand...
Click to collapse
waahhh no X_X this isn't an app to be installed. you are overwritting the old one (after youve backed up!) the "install" command installs to data/app, which isn't what we want (but thanks for keepin an eye on the thread for me wshuman3 )
if you put the apk in your sdk\tools directory, then the command would be
Code:
adb push HtcLockScreen.apk system/app
you were correct about needing root tho

oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?

Lemcott said:
oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?
Click to expand...
Click to collapse
please read the first post again before you post. your question is answered in both the thread title as well as the second line.
thanks!

no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?

Lemcott said:
no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?
Click to expand...
Click to collapse
i believe it should still show you the home screen, considering with the normal lock app by htc in order to unlock it with the dot pattern, you have to pull the slider down, then it shows you the pattern. so going off of that, then it should still do the same thing, but instead of showing a pic on the lock screen, it shows the home screen, then you slide it down to unlock, which i would assume that it would then pop up the dot pattern.

ECLIPS3's explanation is entirely correct. locking will not hide your homescreen. but then, if someone wanted to see your homescreen with the normal lockscreen, they would just have to slide down the Arc most of the way and they'd see most of it. not secure either way.
but i dont think thats what you were even worried about Lemcott. but explained it anyway

yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?

Lemcott said:
yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
it will look like the normal lock screen, just transparent. but you could edit the transparent lock screen to look like jameselles, just transparent. im sure someone would be willing to do that for you. i might, just dont have time right now.

I'll give it a whirl, but if anyone wants to race me be my guest, I'm pretty noobish when it comes to android/linux, but I'll give it my best.

Lemcott said:
if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
99.9% sure your senseable lock would be in-tact, just transparent. since your senseable lock's graphics are stored in com.htc.resources.apk and this is only a change to your HtcLockScreen.apk

Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot
and when your phone boots back up, you'll be looking at a shiny new transparent lockscreen.

Arcalyth said:
Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Click to expand...
Click to collapse
NOTE!: the code is case sensitive, make sure you capitalize as follows:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot

When I try this I always get the nexus 1 lock screen. I'm running Ivan's latest build.
I will try again on a fresh flash since I have been messing with stuff.
Edit: OK, fresh flash without wiping allowed me to change to the Transparent Lock Screen. Thanks gohamstergo.
btw, I have no idea what I changed to not allow this mod.

@silver: not sure but youre not the only one with the issue. no idea what causes it. seems rare tho

AWW, I thought I was special.
But, If anyone ever needs any "rare issues or bugs" found....

Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!

TheAtheistReverend said:
Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!
Click to expand...
Click to collapse
If read the "advanced" directions in the OP, it basically explains how to do this, even though he was trying to tell you how to AVOID doing that. but I agree, I'd like it too. It would almost be like a security feature cuz only you would know where to swipe to unlock

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.

This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions

Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.

Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html

elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you

Yes this method definitely works. I have market working now and can search for protected apps etc.

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.

he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.

I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/

Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.

LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.

Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?

Yes, it requires an edit to a file that you can only be edited when rooted

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!

OP has been updated with original build.prop

Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input

will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.

Thanks for the reply.

Change Screen Resolution on legend ???

is it possible to change the resolution of htc legend..........i tried lcd density but no use ...i am using azure cyanogen mod 6.....
i tried to edit the build pro..but no use
some one help me.......
Change Your Screen Resolution on HTC Evo 4g

I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time

@TheGrammarFreak
What is the resoultion of your screen now?

qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
I dunno how I'd work it out, sorry.

Ah...
I think I've found the first of many flaws with this, and it was mentioned in the EVO 4G post. Some apps ignore this and use the old resolution, and thus don't fill the screen (see attachment)
As you can the the status bar goes a lot wider than the app. The status bar is the full width of the screen.
Other problems arise too, a reinstall of the app doesn't help, and some apps just end up completely screwed...

qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.

grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Cool, thanks grandioso
On a slightly different note I've found that changing the value to 130, and using the 5 icon rows feature of launcher pro, is quite nice.

grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Thanks for clearing that .

There are some problems, but if you want to try it out, you can flash the update.zip I've just made.
160lcd.zip takes you back to default and 120lcd.zip makes your screen resolution higher.

@Briix
Can you make update for 130, like TheGrammarFreak suggested

I'd make one but I'm currently struggling to sign my .zip
EDIT:
Done it, just testing then I'll upload. I also notice that ROM Manager is one of the apps that ends up being screwed by this mod...
EDIT 2:
Wow, lots of edits. Anyhoo, 130lcd right here:

really nice

TheGrammarFreak said:
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
Click to expand...
Click to collapse
thanks man its working...........

Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?

Explicitly my zip? Or any of the zip's in this thread?
No wipe is needed.
Also, this method is inherently flawed. Some apps just don't use the edited resolution. Unless a way can be found to force these apps to scale up then there will always be ugly moments.
One of the things that I've found to not work is the HTC-IME mod. So is it worth it? That for you to decide... Lol
Sent from my Legend using XDA App

I mean yours or Briix' - are there any others ?
I don't want to edit the file manually if I don't have to

grandioso said:
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Click to expand...
Click to collapse
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..

whitetigerdk said:
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
Click to expand...
Click to collapse
I'd love to, but I can't at the moment, I'm at school and didn't bring my laptop. Unless someone beats me to it I'll make one in about an hour and a half; when I'm home.
I did try 140 myself but I didn't think it was worth it. I use 5 icon rows in launcher pro and the widgets started overlapping again. Like they did in the default resolution.
Sent from my Legend using XDA App

I'll wait..
Would be great though if WF & Clock Widget (The Sense look Clock) would adapt to new screen and fill it out..
Totally sweet indeed..

Yeah, if I knew more about android I'd look into forcing apps to scale up. I'm not sure if it's even possible, but hey.
Sent from my Legend using XDA App

[ROM][CWM]KhasMek Stock Deodexed plus! For Tab 10.1

As normal, it's not my fault if you fubar your tab by flashing this or if zombies come and speedhump your cat. You've been warned.
Well, hello there, some of you may know me from my vzwtab (7") work, but I'm sure most of you don't.
No matter, I just finished deodexing my framework and app folders, so I decided to share with you.
This isn't anything special, just you're stock system that's been deodexed, I did not remove any programs, there are really only three or so 'bloatware' apps on here, so I didn't bother.
If you would like to, just use root file explorer (or your preferred method) to remove them.
In addition to the stock items I have added pershoot's SU/Busybox/misc package (SOURCE) All credit goes to him for that.
If there's anything else, just let me know. I have tested this on my own rooted tab and everything seems to work fine and be stable.
If you notice any issues, please format/clear both Dalvik & normal Cache. It's probably the cause.
Features
Deodexed flashable system
Pershoot's SU/Busybox/misc pacakage (nano, VIM, all kinds of other goodies)
Changelog
06212011- r1 - Initial Release
Known Issues
You may have to go through and manually delete your odex's in /system/app/ and /system/framework/ but the apk's and jar's no longer call them. (I can't get the amend format command working right. if you want to tell me how, please!)
Installation
Reboot into CWM either via ROM Manager or via power off, volume down + power, volume down to CWM icon and volume up to select.
Select Install Zip from SD Card
Navigate to location of zip and select okay
Clear Cache and Dalvik Cache (in advanced)
Reboot
Make themes for me
Download
HERE
Lastly, if you like my work, donate to me so I can donate money to devs that make my world easier (and therefore yours).

awesome finally someone to break ground for the Samsung Galaxy tab! Thanks will try it out!

Not sure if it matters but is this for retail or I/o version? Does it matter since it is basically the same tab?
For any ideas: maybe you could include a way for hulu to work without any work arounds? And maybe some lag fixes. Although that may be solved with a custom kernel.
Sent from my PC36100 using XDA Premium App

Decided to test this on the retail version.
The only problem is that root is broken because there are two su binaries installed.
/system/bin/su - installed from file Samsung_Galaxy_Tab_10.1_root.zip when you rooted the device.
/system/xbin/su - installed when you added [Tools] – SU/BusyBox/Misc – Galaxy Tab 10.1 (Update: 6/18/11).
To fix:
http://forum.xda-developers.com/showpost.php?p=14016703&postcount=18
------
the /system/bin/su binary need to be removed.
Su does not work on the tablet with two su binaries installed.
Use adb to remove /system/bin/su
adb remount
adb shell
cd /system/bin
rm su
reboot
I tried running titanium backup prior to a reboot after removing /system/bin/su and it would not work. I uninstalled/reinstalled and it worked, but a reboot may have fixed the problem.
I manually deleted all the odex files - no problems so far. I will provide an update later if I have problems.
------------
You can remove /system/bin/su when you update the image again.
JD

Yeah, I just noticed that myself actually. Don't know why I didn't catch it before.
Anywho, I think I'll prolly push an update to this tomorrow after I write a script to remove the odex's. It was my initial thought, but I thought it would be easier to used the updater-script to do it, but looks like just writing an additional one will be best.
Glad the su thing didn't confuse you too much!

Sweet thanks for this. Going to give it a whirl!

I flashed the Samsung_Galaxy_Tab_10.1_root.zip after flashing the Rom. Everying is working fine.
I didn't need to remove su from anywhere.
Thanks!
Sent from my GT-P7510 using XDA Premium App

Same here
Sent from my GT-P7510 using XDA Premium App

Any chance you can add a browser.apk that gives access to Google Labs?
Sent from my GT-P7510 using Tapatalk

touchpro247 said:
I flashed the Samsung_Galaxy_Tab_10.1_root.zip after flashing the Rom. Everying is working fine.
I didn't need to remove su from anywhere.
Thanks!
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
You will only have problems when you try to run an app that requires root (Root Explorer, Titanium backup....).

danielsjam said:
You will only have problems when you try to run an app that requires root (Root Explorer, Titanium backup....).
Click to expand...
Click to collapse
Nope, not at all. They both run fine. Thanks tho. Others may have that problem, I don't.

touchpro247 said:
Nope, not at all. They both run fine. Thanks tho. Others may have that problem, I don't.
Click to expand...
Click to collapse
If you have both su binaries - and all works - good to hear. I will flash again, but will reboot a second time to see if it matters. Those apps did not run until I remove the su from bin.
Strange how two devices with the same specs operate different on certain software.
JD

shouldn't that have been:
cd /system/bin ?
i didn't try mine w both since i didn't want hassle of find out if it worked or not. no reason for 2 su's.
danielsjam said:
Use adb to remove /system/bin/su
adb remount
adb shell
cd /system/app
rm su
reboot
JD
Click to expand...
Click to collapse

madsquabbles said:
shouldn't that have been:
cd /system/bin ?
i didn't try mine w both since i didn't want hassle of find out if it worked or not. no reason for 2 su's.
Click to expand...
Click to collapse
Yes - my bad - should be /system/bin - will correct it.
Thanks
Jd

Its because one su has the correct permissions and the other doesn't.
Sent from my GT-P7510 using XDA Premium App

how about adding some screenshots ??

pflorin said:
how about adding some screenshots ??
Click to expand...
Click to collapse
Looks just like stock...

So whats this have that stock doesnt,,,whats the pro's to flashing as opposed to what I already have?
concept0 said:
Looks just like stock...
Click to expand...
Click to collapse

camblue said:
So whats this have that stock doesnt,,,whats the pro's to flashing as opposed to what I already have?
Click to expand...
Click to collapse
When themes become available you'll be able to flash them. You'll aslo be able to flash a few other mods...
Sent from my GT-P7510 using XDA Premium App

anaphora68 said:
Any chance you can add a browser.apk that gives access to Google Labs?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
No, you're more than welcome to sideload an apk's you wish however.
I'll push out an update today that gets rid of my silly su mistake, gimmie a couple hours.
Glad you people are enjoying it.

Turn off ads w/ Root?

I'm sure this will get figured out but does anyone know if there's a way to move/change/disable files on a rooted HD7 to disable these god forsaken ads without giving Amazon $15 bucks?

Try disabling dtcp_apk.apk in system/app. Its icon says Kindle Special Offers so I think its the ad service, but it may cause issues if you delete it so rename it to .bak to be safe.

Awesome...can anyone confirm this works?

hope not. a sure way to be sure they will do everything they can to patch and lock up as tight as possible.

zeeebs said:
Awesome...can anyone confirm this works?
Click to expand...
Click to collapse
It does seem to work! The screensaver now shows random book/letters/etc type backgrounds, no ads. I still get the "customers also bought" in carousel view, but otherwise I haven't spotted any ads.
Here's the steps I did:
Code:
# adb shell
[INDENT]
# su
# mount -o remount,rw /system
# cd /system/app
# mv dtcp_apk.apk dtcp_apk.apk.orig
[/INDENT]
# adb reboot
I'm attaching a couple pictures I took of the lock screen. Thanks for the tip!!
UPDATE: As a side note, I tried putting these back and it seems to have disabled them permanently. If I move the apk back to its original name and reboot, it still has the ads disabled.
UPDATE2: Just wanted to comment that my ads decided to come back...took a week or so but they eventually showed up again. I moved the file again as above, and they are gone again (no harm no foul).

nvrmore100 said:
It does seem to work! The screensaver now shows random book/letters/etc type backgrounds, no ads. I still get the "customers also bought" in carousel view, but otherwise I haven't spotted any ads.
Here's the steps I did:
Code:
# adb shell
[INDENT]
# su
# mount -o remount,rw /system
# cd /system/app
# mv dtcp_apk.apk dtcp_apk.apk.orig
# reboot
[/INDENT]
I'm attaching a couple pictures I took of the lock screen. Thanks for the tip!!
Click to expand...
Click to collapse
Thanks for your sharing!

I can also confirm this works...thanks!

nvrmore100 said:
It does seem to work! The screensaver now shows random book/letters/etc type backgrounds, no ads. I still get the "customers also bought" in carousel view, but otherwise I haven't spotted any ads.
Here's the steps I did:
I'm attaching a couple pictures I took of the lock screen. Thanks for the tip!!
Click to expand...
Click to collapse
Thanks..

Worked like a charm thanks

spunker88 said:
Try disabling dtcp_apk.apk in system/app. Its icon says Kindle Special Offers so I think its the ad service, but it may cause issues if you delete it so rename it to .bak to be safe.
Click to expand...
Click to collapse
I just went into properties of this apk and unchecked all permisions. I can confirm that this worked as well. Still have the random pics, but it also disabled the shop unlock slide with date and time in its place. Will post again in a week to see if this is permanent or if it has caused any adverse effects
RE: Well so far I have not had any problems with the method i took for disabling the ads. They have not returned. And this seemed to be much easier and safer than using adb.

onemeila said:
I just went into properties of this apk and unchecked all permisions. I can confirm that this worked as well. Still have the random pics, but it also disabled the shop unlock slide with date and time in its place. Will post again in a week to see if this is permanent or if it has caused any adverse effects
Click to expand...
Click to collapse
I tried this and it worked great. The ads started this morning after an automatic "Upgrade". The weird thing is that I had to re-root my KF HD because both ES File Explorer and File Manager were both saying that it wasn't rooted. I wasn't getting the option to change permissions on either
app, but I was able to see system files. I was finally able to change permission after a quick re-root.
Thanks for sharing the info. It's been about a week for you. Is the mod still working fine?

Archangel1183 said:
I tried this and it worked great. The ads started this morning after an automatic "Upgrade". The weird thing is that I had to re-root my KF HD because both ES File Explorer and File Manager were both saying that it wasn't rooted. I wasn't getting the option to change permissions on either
app, but I was able to see system files. I was finally able to change permission after a quick re-root.
Thanks for sharing the info. It's been about a week for you. Is the mod still working fine?
Click to expand...
Click to collapse
Added to my previous post, but incase you didnt see yes its still working great. Did you just get your device? If so I'm guessing you got the upgrade from 7.1.3 to 7.1.5, correct? When amazon does an ota like that it removes root.

onemeila said:
Added to my previous post, but incase you didnt see yes its still working great. Did you just get your device? If so I'm guessing you got the upgrade from 7.1.3 to 7.1.5, correct? When amazon does an ota like that it removes root.
Click to expand...
Click to collapse
I actually replied before you updated your post, so I didn't see it. I bought it 3 days ago. I just checked it and yes, it's currently on 7.1.5.
Glad to hear it's still working. I hope they don't come out with an update that changes the mod. Thanks for the update.

Does anyone have the reverse process of this? As in to turn the Ads back on?

zeeebs said:
Does anyone have the reverse process of this? As in to turn the Ads back on?
Click to expand...
Click to collapse
Does anyone know the location of the lockscreen wallpapers that show up on the lockscreen once you have disabled the lockscreen ads? I want to put my own wallpapers in there instead.

It's not that easy. Wallpapers are located in the framework-res.apk under /system/framework
Google search editing the framework-res for more answers. It isn't that difficult but you need to be very careful and make sure you know what you are doing because you can potentially brick your device. Without a custom recovery, you won't have very many options if that happens.

soupmagnet said:
It's not that easy. Wallpapers are located in the framework-res.apk under /system/framework
Google search editing the framework-res for more answers. It isn't that difficult but you need to be very careful and make sure you know what you are doing because you can potentially brick your device. Without a custom recovery, you won't have very many options if that happens.
Click to expand...
Click to collapse
Thanks for the heads up, I will hold off then.

zeeebs said:
Does anyone have the reverse process of this? As in to turn the Ads back on?
Click to expand...
Click to collapse
You simply do the reverse of what you did to turn them off. Either rename the file back from dtcp_apk.apk.orig to dtcp_apk.apk, or turn on the permissions to what they were before you modified them. I will say that it took a few days (upwards of a week actually) before it re-enabled the ads. Not really sure what it took for it to re-read that file, but it might have been some combination of me powering down entirely, or an OTA update check that eventually kicked it back in.

onemeila said:
I just went into properties of this apk and unchecked all permisions. I can confirm that this worked as well. Still have the random pics, but it also disabled the shop unlock slide with date and time in its place. Will post again in a week to see if this is permanent or if it has caused any adverse effects
RE: Well so far I have not had any problems with the method i took for disabling the ads. They have not returned. And this seemed to be much easier and safer than using adb.
Click to expand...
Click to collapse
This does work. A little research goes a long way haha. Thanks +1 to you, sir.

nvrmore100 said:
It does seem to work! The screensaver now shows random book/letters/etc type backgrounds, no ads. I still get the "customers also bought" in carousel view, but otherwise I haven't spotted any ads.
Here's the steps I did:
Code:
# adb shell
[INDENT]
# su
# mount -o remount,rw /system
# cd /system/app
# mv dtcp_apk.apk dtcp_apk.apk.orig
[/INDENT]
# adb reboot
I'm attaching a couple pictures I took of the lock screen. Thanks for the tip!!
UPDATE: As a side note, I tried putting these back and it seems to have disabled them permanently. If I move the apk back to its original name and reboot, it still has the ads disabled.
UPDATE2: Just wanted to comment that my ads decided to come back...took a week or so but they eventually showed up again. I moved the file again as above, and they are gone again (no harm no foul).
Click to expand...
Click to collapse
It works.. thanks so much... you rock!!:good: