[Q] deleted buil.prop ...... phone still working(i have not rebooted) - General Questions and Answers

hey.... i have deleted build.prop file. when ive gone to rename backup file...........its says that opration failed................it has lost it root access.
ive tried adb push wont work..RO not RW....WHAT TO DO

Adb push to /local/tmp/
Then use root file manager to move and rename
Or Adb shell in then su from there

Thanks
I've restored a backup and your answer is nice.

Related

[Q] installing busybox - pushing files to droid

Hello,
I started experimenting with my Android yesterday when I found out about metamorph which requires rooted phone and busybox..
I managed to root the phone but couldnt install the busybox with the application from the market - it says that busybox was not found..
Then I installed the SDK platform, and wanted to do it with adb
I downloaded busybox ... tar.bz2 file and unrared it into SDK/tools and tried pushing it to my android to /system/local by doing:
adb push /Users/../android/platform-tools/busybox /data/local
but adb pushed the subfolders (children) to the /data/local folder instead of the folder with childen folders itself.
Now I wonder:
1. how to remove all those junk files?
2. am I doing the right thing? should I copy the tar.bz2 without unraring it? what is the right procedure?
is there any easier way to accomplish this?
Thanks for help
One way to get busybox is with titanium backup. Install the app open then menu*problems*Yes, do it.
jerrycycle said:
One way to get busybox is with titanium backup. Install the app open then menu*problems*Yes, do it.
Click to expand...
Click to collapse
This wont work with my telephone - HTC Desire

[Q] Unroot / Return to Stock Recovery for Nexus S 4G (Sprint)

Gang, I've searched and couldn't find. I rooted the Sprint Nexus S 4G and installed CW recovery.
Would some one please be kind enough to point me on how to unroot and return to stock recovery for a return.
Thank you!
Why do you want to return it?
dmora01 said:
Why do you want to return it?
Click to expand...
Click to collapse
Exchanging for another, I appear to have a defective screen which flickers when phone is shaken.
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
r80ies said:
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
Click to expand...
Click to collapse
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
What about the custom CWM recovery?
oldblue910 said:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
a2k said:
What about the custom CWM recovery?
Click to expand...
Click to collapse
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
oldblue910 said:
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Many thanks!!!!
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
a2k said:
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
Click to expand...
Click to collapse
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
oldblue910 said:
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
Click to expand...
Click to collapse
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
a2k said:
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
Click to expand...
Click to collapse
OK check /system/bin then. Is BusyBox in there?
oldblue910 said:
OK check /system/bin then. Is BusyBox in there?
Click to expand...
Click to collapse
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
a2k said:
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
Click to expand...
Click to collapse
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
oldblue910 said:
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
Click to expand...
Click to collapse
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
a2k said:
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
Click to expand...
Click to collapse
Oh no wonder! You're all set then. BusyBox is located within Titanium Backup's data folder. You don't need to worry. BusyBox will go away when you uninstall Titanium. So just follow my updated instructions and you're good. Let me know if you have any problems. Make sure you have a nandroid backup of your ROM before you delete root, just in case! You can never be too careful!
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
spdwiz18 said:
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
Click to expand...
Click to collapse
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
oldblue910 said:
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
Click to expand...
Click to collapse
Nope .... no such file. I even did a search for it with root explorer and it does not come up. If worse come to worse ill pull it from someone's Tom just so I have it on my phone. But I know I did not delete it.
Sent from my Nexus S 4G using XDA Premium App
That is very strange indeed. I wonder if Google didn't install it on the Nexus S 4G. Can any other NS4G owners verify if /etc/install-recovery.sh exists on your phone?

Finally got my phone back .. EFS issue

So i finally got my phone back from repair from regenesis , man what an effort and expense!
anyway , iv rooted , and i just wanna backup my efs this time lol. whats the best way ?
atm iv copied and pasted it from root explorer , i tried ADB pull , but it said something about cant use adb root due to production builds..
is the copy and paste of the files ok
, i have all the .baks and nv_data
Glad to hear it's working well. Back it up, in multiple places, via ES File explorer or similar. Just a typical copy-paste job. After this is done, open up terminal on the phone or adb shell and type:
su [enter]
[Allow superuser access via prompt]
cat /dev/block/mtdblock6 > /mnt/sdcard/efs_backup.img [enter]
and voila. /sdcard/efs_backup.img is your exact, rock solid /efs partition. This too should be stored in multiple places.
brilliant thanks alot!

[Q] Can not delete file in /Android/data/

i have install NFS17 last night,and game can not run,so i uninstall it.
but,this game data save in /Android/Data/com.ea.games.nfs13_na , size about 500MB ,i have already uninstall game,but i can't delete this folder anyway....i'm useing MEIZU MX3
delete use system file explorer,it tell me successful delete files,in face,folder have not delete,and i have already try other tool...like:ES File Explorer , AirDroid , XXX Explorer...
today,i try delete it by use "adb shell rm -rf /mnt/storage/Android/data/..../",but i get error message:"Permission denied",chmod also not work.
i have not get root permission , because "Phone Finder" may can hacked after i lost my phone if i get root permission.
And...i have try boot to recovery mode , but in recovery mode can't use "adb shell".
i don't want to get root permission to delete this file ,and MX3 have no other recovery(like:CMW)
π_π Who can help me?

Chinese Phone running Android 4.2 - Malware built in, cant delete despite root

It took me a while to figure out that the bast**ds had built in the malware in the firmware, with the launcher. Phone is rooted, and I have changed the launcher. But I can't delete the malware apks inside system/app.
They are named as com.google.hardware.ext0.apk, and another similarly named (android air, and measure too)..
Problem is, I can't delete them, I tried using ES File Explorer (yes, root is enabled. I can delete, change other files in system/app but for this) I am denied permission!!
Then I tried the terminal emulator.. after getting SU.. tried deleting them using RM and then 'busybox rm..' both failed. What to do? How to delete the f****ng malware files??
(If I switch on the WiFi, malware automatically downloads more crap, then I can't even switch off Wifi and Data! Hence I formatted the phone and have not entered any sim or wifi settings... but I can't delete the damn files!! Any suggestions please?? Going crazy here)
regards
If you could install a custom recovery to flash a zip that delete this app...
Try a Root System App Deleter or, boot in recovery mode and remove it via ADB

Categories

Resources