you need custom recovery (rooted mobile)
Reboot to recovery
Delete these files
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
Reboot system
P.s.s
By adb debugging
Type in :
adb shell
su
rm /data/system/locksettings.db
rm /data/system/locksettings.db-wal
rm /data/system/locksettings.db-shm
reboot
Enjoy
Thanks for the tip MASTER
Related
i try this on the comment prompt while phone running.
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
and it'll say:
rm failed for -f, read only file system
it wont let me write on the system im guessing.
Now i tried doing the same thing but phone mode is on recovery.
I have the nand protection unlocked so when i get to recovery mode
i have already the custom recovery setup showing, i don't run the recovery-windows.bat.
now when i type this on the comment prompt
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
after i hit enter it shows me
#
so im assuming the apk. has been removed
after i exit the comment prompt and i wipe the dalvik-cache
i reboot the phone and all the apps i removed are still there and running still.
help please
ahhh... so I had done method 1 of lagfix and I was looking to do CFLagfix instead...
method 1:
db shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
undo method 1..
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
BUT.. here's where I messed up... I accidentally looked at the wrong line of the undo and I'm pretty sure I did the undo method (restore to point of application)
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot
So now when I reboot all I get are a bunch of force closes...
I can't even get into recovery by holding down the volume keys and power
i have a nandroid backup but I can't get into recovery to restore it.. i'm not sure if there is a way to get into clockwork using adb commands?
BUT.. when I try a SU command it fails bc I get a force close on the phone. I'm just lost so if anyone can help me restore this thing.. or at worst.. to just restore to factory settings..I'd appreciate it.
adb reboot recovery should get you into recovery.
recovery doesn't work. says not permitted.
decided to flash the stock rom using ms_gurus method in http://forum.xda-developers.com/showthread.php?t=728698
hopefully i'll have a working phone so i can go about restoring
hello
After unlocking the bootloader then installing the recovery image
then from the recovery image
i install this file from sdcard su-2.3.6.1-ef-signed.zip
everything run smoothly and i get installation completed
but then when i boot to the device, the Rom Manager tells that there is no su into /system/bin
how to install su correctly ?
i'm on ubuntu with Nexus S 9023
thank you
even market enabler app tell "we got a problem Huston" that means no root applied
i've mounted the /system from recovery mode but nothing seem to activate the su
help please
Do you have /system/app/Superuser.apk ? Otherwise I would try to flash the zip again from recovery.
no doing /adb shell ls /system/app/
i can't find the Superuser.apk there
even i tried to flash the zip files 3 times
and removed the superuser then installed it from market
still not su
solved
ok, now i fixed this problem
extract the (su and Superuser.apk) from su-2.3.6.1-ef-signed.zip to /sdcard
Code:
./adb reboot bootloader
then choose recovery mode
then
Code:
./adb shell
Code:
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su
chmod 06755 su
link: opdecirkel.wordpress.com/2012/03/21/root-samsung-phones-running-android-2-3-x-without-flashing-kernels-or-executing-binaries/
1. adb shell rm /data/log/recovery_log.txt (even if fails it is ok)
2. adb shell "ln -s /data/local.prop /data/log/recovery_log.txt"
3. reboot your phone in recovery (do not do anything here)
4. reboot in normal mode
5. adb shell “echo ro.kernel.qemu=1 > /data/local.prop”
6. reboot again
7. adb shell … heeey you are root.
8. Install your favorite root tools: Superuser.apk, su, etc.
Hi there... I was trying this with an I9100 with XILA3 stock rom...
got stuck at point 5: permission denied
any advice?
I reboot to twrp recovery and mount vendor partition,
adb shell and run command: rm -rf /system/app/PrebuiltBugle
Then check it's removed succ , But when I reboot to system, PrebuiltBugle still exists at /system/app.