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.

[SOLVED] Uninstall Swype?

I need to uninstall swype and reinstall it. Ive tried over writing it with the default apk but its not removing a theme I installed with metamorph. If I can uninstall it, a fresh install should fix it.
I just dont know how to remove it

I don't know if you want to go to this extreme, but I did. I fudged up the phone real good by removing and installing stuff. I finally got fed up and flashed it back to stock and applied root again. This time I'll keep my fingers out of it. I hated touchwiz in the beginning, but now it's kinda growing on me. I've never had an iphone but the home and drawer remind me of iphone wannabe. It's okay for now.
Sent from my SPH-D700 using XDA App

There a tool over at sdx-developers that can remove that when root explorer can't. I forget the name of it. There's also a pay app in the market that I think is called root manager that can successfully remove crap too. I didn't have much luck putting the general swype 1.61 in. It refused to install. That's when I think I just flashed it back to factory image. A full reset/wipe wouldn't fix it either.
Sent from my SPH-D700 using XDA App

I had to do this a few days ago for similar reasons. This is what I did:
First, you have to open your browser or other app with a text field. Select the text field then long press the text field again and switch the input method to the stock android kb.
Next, you have to make sure /system is mounted as r/w. The early versions of the the rooting scripts did not remount correctly but the newer ones supposedly fix it. I just looked in the initial rooting .bat file (on the PC) for the remount command and used adb to remount /system.
You can test if it's remounted correctly by renaming Swype.apk to Swype.bak with Root Explorer then going up a level and back to /system/app. If it's not mounted correctly it will show as Swype.apk again. If it shows as Swype.bak still, then you just have to copy the original Swype.apk to /system/app and then switch input method back to Swype!
Sent from my Epic 4G using XDA App

yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?

I don't know what's causing it but root explorer doesn't seem to work properly on the phone (not sdcard) filesystem in the system app folder. It's stuck in rw mode. People have said different things why but I forgot. I did noobnl's latest flash and it's still not working right. His script is removing the old root and my phone doesn't have that on there. I don't know what to tell ya. Maybe I should look for another root file manager.

kennethlongshaw said:
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
Click to expand...
Click to collapse
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)

dwyw42 said:
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
Click to expand...
Click to collapse
mmmm. That fixed. it. I owe you a beer

kennethlongshaw said:
mmmm. That fixed. it. I owe you a beer
Click to expand...
Click to collapse
Hi guyz.
I cant delete swype.apt file from /system/app/*
i am using SUFBS program (reed/write option enabled)
i tried use command in terminal:
Code:
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
but i get only;
Code:
permission denied
z4root show info that my phone is rooted
PDA i5800XXJI2
any ideas how to del that file? :]

Custom Rom App Removal

hey guys,
how would i go about removing apps from an installed custom rom?
ive tried titanium back... doesnt work, tried pulling the apps from the pack nothing,
ive tried root exploits and it just sends your phone into an almost
"paperweight"
like state,
any further moves i can do to remove various bits ? there as some things i just genuinely dont want.

Telling which rom and which apps might help

[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT] [19/NOV/10]
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??

fkofilee said:
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??
Click to expand...
Click to collapse
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.

when i say pull... lol. i mean removing them from the system completely

fkofilee said:
when i say pull... lol. i mean removing them from the system completely
Click to expand...
Click to collapse
I've just discovered there are issues where /system isn't getting wiped correctly prior to a new rom being flashed. Keep getting apps from other roms and such sitting in my /system folder even after a wipe and flash - at this stage I assume CWM is bugged? Could be your issue is related.

nope the ADB coding doesnt work as its almost like there is a PERMANENT R/w lock on the section i need to remove apps from

unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove

fkofilee said:
unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove
Click to expand...
Click to collapse
Get a new rom ???

hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.

how weird!!!... i used to terminal emulator to allow su (I.E to give system SU Permissions and now i can remove the apps ) haha
Shocked!!
Admin Please close & Deleted Thread.

fkofilee said:
hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.
Click to expand...
Click to collapse
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.

dr.m0x said:
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.
Click to expand...
Click to collapse
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.

fkofilee said:
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.
Click to expand...
Click to collapse
Yeah you ninja'd my last post
Glad to hear you're gtg now.

but mind you the mount script i ran and it didnt work lol.... maybe i did them the wrong way round, (Raise SU first then do mount cmd??)

dr.m0x said:
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.
Click to expand...
Click to collapse
Works. Thanks!

[Q] Editing Build.prop results in failure to boot [bricked]

As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.

Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...

the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop

Did you remember to restore the read/write permissions to build.prop? It should be set to 644.

As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.

I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.

gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium

You dont have access to recovery? Either TWRP or CWM?

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.

gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium

Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.

abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.

sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.

I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk

I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.

would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?

how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk

[Q] How do I delete system apks?

I can't figure out how to delete some of the system apks off my rooted Nook Simpletouch. Running 1.2.1, and Nootered it. Tried to ADB uninistall Phone.apk, but it just reports failure. I could use some help.

/system is usually read-only.
To make changes in its content you need to remount it read/write:
Code:
stop
mount -o rw,remount /dev/block/mmcblk0p5 /system
The stop is to be on the safe side, it stops the android subsystem.
After you are done making changes it's best to:
Code:
reboot

Renate NST said:
/system is usually read-only.
To make changes in its content you need to remount it read/write:
Code:
stop
mount -o rw,remount /dev/block/mmcblk0p5 /system
The stop is to be on the safe side, it stops the android subsystem.
After you are done making changes it's best to:
Code:
reboot
Click to expand...
Click to collapse
Just rename them. add ",bak:" to the end or similar. This will disable them, and if you notice instabilities because of getting rid of them you can just remove the appended extension. If everything runs well, you can then delete them with no worries.
I've renamed some of the recommended ones and have an error that comes up. "A problem has occurred, contact support". I need to figure out what is causing that to happen. its annoying but doesn't seem to be an actual problem.

What does "mmcblk0p5" represent?

mmcblk = multimedia card block device, 0 = first device, p5 = fifth partition

Thanks Renate, but It's not working. In order to rename or delete an apk off my Nook simpletouch, would someone please give me step instructions? I feel I'm missing something.

Code:
stop
mount -o rw,remount /dev/block/mmcblk0p5 /system
cd /system/app
mv BoringApp.apk BoringApp.bak
mv TediousApp.apk TediousApp.bak
reboot
And don't tell me that you have no boring or tedious apps!

The advice here is correct, better to rename sysapp extensions (.bak or .ap_) than delete as some might be needed by future apps/sys hacks/kernels. For those who can't adb by cable or keep it up wifi-wise, this is the easiest way even easier than root explorer:
https://play.google.com/store/apps/details?id=com.ghisler.android.TotalCommander
for sys or user app removal if you have to and can't use adb or even total commander, but then you shouldn't if not knowing sys file structures (I use Pro version, for removing many apps i just tested in a batch, sorted reminder):
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I renamed talk telephone music audio etc apks on nst but Gallery is the only one I removed on all android devices & nst as it's just nasty which has never been missed by later hacks and quickpic is much better anyway:
https://play.google.com/store/apps/details?id=com.alensw.PicFolder

I created another directory under /system called archive. I move apps I don't what to use and fonts I change into /system/archive then I can just move them back if I have issues.

This still isn't working. My commands keep getting rejected. It isnt allowing stop to work. Also, I tried "adb cd /system/apps" and when that didn't work, I tried
"adb shell"
"#cd /system/apps"
No dice.
EDIT: Got it. needed to call it shell instead of adb. I also accidentally wrote "apps" instead of "app".