Database Users

Default android lockscreen

Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App

lakeside00 said:
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
you can remove the HtcLockScreen.apk from /system/app/ and it will default to the stock android one. Problem is that is suffers from the same fate as many others where the slder is up/down and the time is jummbeled on the left side.
Oh and of course to remove/rename the file in /system/app/ you must be rooted and in recovery mode.
I'm working on how to fix the screen. Flipz did it for android 2.0 but it isn't the same fix in 2.1. If I get more info I'll post back.

I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...

gmelchert said:
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
Click to expand...
Click to collapse
LOL! love the step by step edits...
I have a script that makes it easy, it is just a modified version of Toast's. It cuts it down to one command input instead of three.
Any way here are the steps:
With phone on plug it into your computer. Open two command windows. Navigate one to the folder you have downloaded toasts recovery script to.
1) In the window that is at evo-recovery> type: adb reboot recovery
This boots you in to the stock recovery
2)in the same window type windows-recovery.bat (adjust for your OS)
This gets you into Amon-RA's recovery
3) Wait for the phone to get the new recovery screen. In the other command window type: adb shell mount -a
Step 3 can be adb remount or you can type adb shell then at the # type #mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
Any way after that point you can exit adb shell back to the command prompt and push/pull anything to /system
unfortunately you can't see it right away and have to wait for reboot. Also this limits some of the apps that we can install because some will need to write to /system and cannot once rebooted.

ADB Push

I searched around and couldn't get a clear answer. I'm a noob at anything command prompt/terminal related.
I was screwing around with adb last night after figuring out that I can remove program .apks with the rm <com.whatever.program> command. I got a little trigger happy and removed things that I don't use, just to test it out. I made a nandroid backup before I started. The phone runs fine, but now the Market won't download anything. It just sits on the Starting download... screen.
One of the .apks I removed was GmailProvider.apk. Whether this is the problem or not, I'd like to reinstall it for practice. I can always nand restore later.
So my question is... How can I use adb push to reinstall an apk?
I tried:
Code:
adb push C:\GmailProvider.apk
adb install C:\GmailProvider.apk
adb install C:\GmailProvider.apk \system\app
And about every variation of the 3, in and out of the adb shell.
It didn't work, and I'm at a loss to do anything else. So does anyone have any suggestions?
EDIT: I think my "\" should be "/". I got this
Code:
BusyBox v1.15.2 <2009-12-02 TIME EST> multi-call binary
Usage: install [-cdDsp] [-o USER] [-g GRP] [-m MODE] [source] dest|directory
Copy files and set attributes
Options:
Then some usage stuff here.
Then I looked at the command prompt and made a face like .
Suggestions?
It might help to say that I'm using EvilEris 2.0.1, Windows 7.

Just reflash your ROM after doing a titanium backup. Easiest fix.

try this after putting GmailProvider.apk in your sdk\tools dir:
Code:
adb remount
adb push GmailProvider.apk /system/app
remount marks the system directory as read/write

silverramsrt said:
try this after putting GmailProvider.apk in your sdk\tools dir:
Code:
adb remount
adb push GmailProvider.apk /system/app
remount marks the system directory as read/write
Click to expand...
Click to collapse
Beat me to it. ADB is powerful and pretty cool if you know some good commands, but you can really mess up your phone if you know what I mean. Not mess up like brick (unless you really try) but more like phone won't load gmail now, phone won't get past the htc screen. As long as you have a nandroid backup you SHOULD be fine, the push, pull and rm commands are really the first step of rom building. If you know what files you pushed and rm'd you can make your dream rom.

CPCookieMan said:
Beat me to it. ADB is powerful and pretty cool if you know some good commands, but you can really mess up your phone if you know what I mean. Not mess up like brick (unless you really try) but more like phone won't load gmail now, phone won't get past the htc screen. As long as you have a nandroid backup you SHOULD be fine, the push, pull and rm commands are really the first step of rom building. If you know what files you pushed and rm'd you can make your dream rom.[/QUOTE
i am installing htc facebook.apk on a rom that has had all the Bloat removed.do i need to do something after i have pushed a apk file into system/app?? i have tried rebooting the phone and the program isnt there,ive tried going in the phone with root explorer and tried installing while having it in r/w and r/o and still cant get it to install.im not sure what im doing wrong.any help is apreciated
Click to expand...
Click to collapse

i am installing htc facebook.apk on a rom that has had all the Bloat removed.do i need to do something after i have pushed a apk file into system/app?? i have tried rebooting the phone and the program isnt there,ive tried going in the phone with root explorer and tried installing while having it in r/w and r/o and still cant get it to install.im not sure what im doing wrong.any help is apreciated
Click to expand...
Click to collapse
You do not have to do anything after an adb push.
What rom? Some roms have been modified to the point some htc apps will not work. Addionally a copy of the htcfacebook.apk from an eris build may not work on a sprint based or g1 based roms do to signature variations
Sent from my Eris using XDA App

zach.xtr said:
You do not have to do anything after an adb push.
What rom? Some roms have been modified to the point some htc apps will not work. Addionally a copy of the htcfacebook.apk from an eris build may not work on a sprint based or g1 based roms do to signature variations
Sent from my Eris using XDA App
Click to expand...
Click to collapse
im running xtrom 3.0.......i just went ahead and installed the social app flash and deleted what the ones i dont uses,but thanks for the help anyways.i was looking into pushing friendstream into it but found out its only works in sprint base builds

[Q] ADB will not remount!

Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.

you know, I've had the same problem lately. --curious to know what's causing it.

decalex said:
you know, I've had the same problem lately. --curious to know what's causing it.
Click to expand...
Click to collapse
Its good to know I am not the only one out there with this issue maybe someone can chime in with a fix. or some insight at least to what the problem may be.

Still no response.... Bump?

watermoore said:
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.
Click to expand...
Click to collapse
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.

DevinXtreme said:
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
Click to expand...
Click to collapse
Hey man thanks for your input, I really appreciate it. That didnt work either, on ADB or on Terminal Emulator. It responds correctly from both sources with:
Code:
remount rw
Remounting /system </dev/st19> in read/write mode
I am wondering if it has anything to do with the fact that the 64bit drivers dont install totally. this module called the "Abstract Control Module" hangs forever and doesn't install. However I ran over to my wifes 32 bit vista laptop where the drivers will install totally with no success either.

Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.

DevinXtreme said:
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.
Click to expand...
Click to collapse
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#

Bump again
Sent from my Epic

Okay since I'm not getting much love from the forum I'm guessing this is an uncommon occurance, in which case I am going to try one more thing before I send it back for a replacement. I am planning on going back to DI18 via odin then one click rooting. Then flashing the modem and other nessecary files to run 2.2 epic experience. Its the only possible thing I can think of that I haven't tried to address my problem. Thanks for the feedback I have gotten thus far.
Sent from my Epic

This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2

The e0pic and hero are way differentwhen it comes to adb
I was the same way lol I don't think adb works
Like I think the only way is to cp things
Sent from my SPH-D700 using XDA App

watermoore said:
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
Click to expand...
Click to collapse
That last one appears to have worked. Check and see if movetest.txt is in /system/fonts. If so, then you're in business. Just copy stuff across as root instead of pushing.

Well now I can use ADB fully. I odined back to stock then used the one click clockwork 3.0.0.05 ext4 batch then flashed Truley Epic Rebirth 1.2 and was able to remount correctly, push and pull all the way down to the root dir. I am not sure what changed but it just all of the sudden started working.... I'll take that lol

mirth18 said:
This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2
Click to expand...
Click to collapse
Well my issue was a bit different. I could get it show up with the "devices" command. When I tried to "adb remount" it would deny me. It would reply with "device not found". Which is really wierd because I could ADB shell with root access any day of the week. I just had to change my process to accommodate the limitation.
I would just ADB push files to the sdcard, mount into shell to gain full root permissions then finish my work.
Kind of a strange round about way of going about it but I learned quite a bit more linux commands that way lol

Fyi.. I am using ubuntu 11.04
Sent from my SPH-D700 using XDA App

No Staus Bar....Help...

Rooted my Kindle and worked fine until I tried to load up Red WiFi Icon from DroidPirates.com (MetaMorph File) and lost the entire Status Bar! I still have root but the device is useless without the status bar.....Thanks

This is not a development issue, it goes under questions.
Try uninstalling the mod, or reflashing from a backup.
Sent from my Kindle Fire using xda premium

Sorry my fault can an admistrator move this posting...sorry again.

Metamorph shouldn't be used anymore on things like the status bar and framework. These things do not like being messed with while they are in use. Instead, i highly recommend an app called zipthemer, it will take a metamorph zip file and turn it into a zip that can be flashed in the recovery menu. It will also make a undo zip that you can flash to revert back. Just make sure that if you change or update the ROM, remake both the theme and undo zips! That part is VERY important!

I had a similar issue trying to use a Metamorphose mod to change the lock screen slider color. In the end I pushed a clean framework-res.apk to the device via adb as described in the "unbrick your kindle fire" thread.
Basically whatever file is referenced in the Metamorphose zip is probably the one that you need to replace. Good luck!

I'll Give it a Shot and let you know..Many Thanks.

No luck yet any other Suggestions?

2147 said:
No luck yet any other Suggestions?
Click to expand...
Click to collapse
Pushing it via adb should be pretty simple just grab it from the 6.2.1 update.zip and push the framework.apk to the system
Sent from my ADR6350 using XDA App

It's not the framework, it's SystemUI.apk
Do you have twrp installed/working? Were you running stock 6.2.1?

Yup running 6.2.1 and twrp installed and working. I'll try pushing SystemUI.apk.. I'll let you know soon....Thanks

This is what I got;
c:\KindleADB>adb push SystemUI.apk /data/local/tmp
2423 KB/s (600596 bytes in 0.242s)
c:\KindleADB>adb shell mount -o remount rw /system
mount: Operation not permitted
c:\KindleADB>

If you have twrp installed, boot into it then.....
adb remount
adb push SystemUI.apk /system/app/SystemUI.apk
adb shell chmod 644 /system/app/SystemUI.apk
adb reboot
And you should be good to go

48 Hours Later you are the Man!!!!! It Worked!!! Dang...

One last thing after getting my Status Bar back I rebooted and TWRP launches and I get the Tablet Menu thing how do I get a normal boot?

Do you have the firefirefire bootloader? (The triangle screen when you first turn it on) if so, then unplug and turn your kindle all the way off. In terminal/cmd type...
fastboot -i 0x1949 oem idme bootmode 4000
It will say something about waiting for device, plug your kindle in. It will turn on by itself and run the command. When it's done (it should take just a second or two) type...
fastboot reboot
And it should boot up normal

Or what would be easier.... At twrp....
adb shell
idme bootmode 4000
reboot

That worked thanks Guys...........

[Q] Boot Animation WITHOUT Root -- /data/local permission denied

Hi there,
I'm looking to put a boot animation on my Nexus 7 without rooting it, similar to this thread: http://forum.xda-developers.com/showthread.php?t=1580642
When I issue the adb command, it thinks for a while and appears to be doing something and then comes back with "failed to copy 'bootanimation.zip' to '/data/local/bootanimation.zip' : Permission denied" The command I'm using is adb push bootanimation.zip /data/local
I've added adb to environment variables and my paths are also correct (bootanimation.zip is in the folder I've navigated to in cmd). I've also tried just putting bootanimation.zip into platform-tools. Is there something that I am missing that will allow me to do this, or is /data/local off limits in the N7?
I probably would've spent less time just rooting the thing, but I am trying to avoid that for now.
Thanks in advance for any insight!

i dont have a non-rooted N7 to test, but u may issue the following commands to see if u can access /data/local
adb shell
cd /data/local
ls
Click to expand...
Click to collapse
see if u get any error msg..