please someone help to restore info - Vibrant General

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

Related

Helppp removing .apks with sdk method

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

problem with adb push

i get an error when try adb push a recovery file to my sdcard and ideas?
Need to give it a file name at the location you're moving it to I believe.
Example: adb push foo.txt /sdcard/foo.txt
ok thanx, how do i delete a file off the phone? when i install a custom recovery and reboot it goes back too stock recovery so i need to delete /system/etc/install-recovery.sh file, but need to know how
corolla90 said:
ok thanx, how do i delete a file off the phone? when i install a custom recovery and reboot it goes back too stock recovery so i need to delete /system/etc/install-recovery.sh file, but need to know how
Click to expand...
Click to collapse
enter this into command prompt or terminal
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh

installing su complete but nothing! 2.3.3 9023

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

Can not root and Update OTA again after unroot.

When I rooted ,I backup and delete some some flexT9 input file, then I find out I can not recive SMS after root .
So I unroot ,now I get OTA update but it's says error about I miss some flexT9 file.I can not restore file without root.
Now I can never root again ,and I can not even UPDATE OTA because system fille ar change.
What can I do NOW ?
Just make a full restore, root, ota rootkeeper, backup, temp unroot, OTA, re-root with OTA-Rootkeeper, install your apps.
I try restore, but sitll the same,I can't root...
Do you use OTA RootKeeper to unroot?
If so, you have a su-backup in /system which you an use to get the full root back.
Even when RootKeeper fails to restore, you an do in the shell.
JA.de said:
Do you use OTA RootKeeper to unroot?
If so, you have a su-backup in /system which you an use to get the full root back.
Even when RootKeeper fails to restore, you an do in the shell.
Click to expand...
Click to collapse
I do found the su-backup in /system.
How to get it back? How to do in the shell? I am new on Android. Thanks!
Download the zip which works before OTA2
Extract it to /sdcard/Download
Install Termial Emulator Form market ("Android Terminal Emulator", ConnectBot or so)
Start it and type: /system/su-backup
Prompt change to #
Type:
mount -o rw,remount /system
rm /system/xbin/su
rm /system/bin/su
dd if=/system/su-backup of=/system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
rm /system/xbin/busybox
dd if=/sdcard/Download/busybox of=/system/xbin/busybox
chmod 755 /system/xbin/busybox
/system/xbin/busybox --install /system/xbin/
dd if=/sdcard/Download/Superuser.apk of=/system/app/Superuser.apk
chmod 644 /system/app/Superuser.apk
mount -o ro,remount /system
exit
exit
Terminate the Emulator.
I have some trouble with rerooting. I've just done the following:
Rooted the TPT
Installed RootKeeper
Backup up root
Temp unroot
Installed OTA2
Tried to reroot - no success
RootKeeper says "filesystem supports root protection" and "protected su copy available"​When clicking Restore root it says "root su restored", but the checklist still says its not rooted (titanium backup says the same)​
Installed superuser from market
Tried to reroot again - still no success
Installed Terminal Emulator
Wrote /system/su-backup - and received "Permission denied"
Wrote mount -o rw,remount /system - and received "mount: Operation not permitted"
Any suggestions on how to get root back?
@krister461:
Just do what I have written.
You must have /system/su-backup, I think.
JA.de said:
@krister461:
Just do what I have written.
You must have /system/su-backup, I think.
Click to expand...
Click to collapse
I did try, see step 9-11.
I do have /system/su-backup, but I get permission denied when trying to use it from the terminal window.
type:
cd /system
ls -l su-backup
Owner should be: root
Group should be: root
Permissions have to be: rwsr-sr-w
If so - all is good and you have made a mistake.
If Not - :-(
Following your instructions, my screen says:
-rwsr-sr-x root root
and then mentions the Rootkeeper backup and it's size.
Am I okay?
toenail_flicker said:
Following your instructions, my screen says:
-rwsr-sr-x root root
and then mentions the Rootkeeper backup and it's size.
Am I okay?
Click to expand...
Click to collapse
Mine says the same.
Sorry for the w at the last character of the Permissions.
My fault. You are right. The x is correct.
I made another mistake.
Type cd /system before /system/su-backup
/system is not in PATH.
Good luck.
So our permissions are correct? We are okay? I'm sorry, just new to root and adb. Thanks
Yes all is okay. Only you have to start with
cd /system
in the shell. That's all.
I still get permission denied :-S
Just checked: cd /system is not necessary.
/system/su-backup gives you root (and
the #-prompt).
@krister461:
Did you type "/system/su-backup"?
The shell is case sensitive.
Is filesize the same as the su in the
zipfile?
Maybe your terminal emulator did not work properly.
The two that I mentioned are okay.
I am using Android Terminal Emulator, and writing it correctly. If I misspell it it says "not found".
Thanks for your help so far though

busybox update stopped defy from working?

Hi! My defy with cm 7.1-11 does not boot anymore.
The playstore asked me to update busybox app, which i did.
The app busybox sug gested to update my busybox binarys to 1.21, which i did. I choose normal install.
Now the phone does not boot up anymore, it is stucck on the red M with the bee and the text "cyanogen defy 7.1-11"
i can access the stock bootloader and the CM bootloader.
i connected to the adb and tried to push the old busybox 1.19
those are my commands
Code:
adb remount
adb push busybox /system/xbin/busybox
adb shell
# chmod 755 /system/xbin/busybox
# ln -s /system/xbin/busybox /system/bin/busybox
# /system/xbin/busybox --install -s /system/xbin
# exit
the process went fine, but still no boot.
can you help me without me loosing all data?
Backup data from cwm, then try flashing cm7 without data wipe. If you're lucky then it should work, otherwise you can try a dalvik wipe. If still not working then use the system wiper script, data wipe and flash cm7. After that restore the backup and it should work just fine
Sent from my MB526 using xda premium

Categories

Resources