Related
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?
I just applied Daoist's CWM stock ROM update (should still be rooted, right?). It came up first time.
Then, I modded my build prop (set dpi to 120 because I like it that way). But maybe I screwed up the file name in Root explorer, because now I'm in a boot loop and if I try ADB PULL /system/build.prop it says "file not found."
I can't get SU through adb, so can't push build.prop to /system. ADB remount returns an error. permission denied. Transformer won't boot, so I can't do anything from it.
I CAN get to cwm, and have been trying to create an update.zip that will just copy build.prop to /system, but everything I have tried quits with "install aborted" message.
What can I do?
restore a nand and dont try and **** with it again, lol. no but really, restore a nand and then copy your build. prop and make a flashable zip and place on your sd card in case it happens again, so you can just flash it in cwm.
Resolved..
Well, why go back when you can go forward?
I went ahead and installed the Prime ROM. Looks like it is eating all my currently installed apps.
Y'all should know, though, that if your system can't find a build.prop it won't start. You can ADB to it and have a rudimentary set of commands, but your ability to significantly alter anything in your file system will be prohibited.
Lesson learned.
glg
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
mrevankyle said:
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
Click to expand...
Click to collapse
That is true. I had backups. But without a build.prop, the virtual machine won't start. There is no way to do a file operation to replace the backup. At least none that I found. I had to flash the whole system.
glg
I cant go to recovery through Rom Manager for some reason. It works manualy( power+volume) but when I click it from the app it freezes, and shows an exclamation point triangle
have you tried to reinstall the app?
Wich CWM do you have?
thy the above post; if that doesn't work, go into recovery manually and fix permissions
that must be why
I was following this video http://www.youtube.com/watch?v=PVyGw6vycFo
and it said I had to wipe my data which I did, and maybe CWM was removed?
Ill try to flash CWM and see what happens.
Worked! thanks
In wich way?
Have you reinstall Rom manager App or reflah CWM Recovery?
actually, theres been a trend going on here....
I went on recovery to check if its working after I flashed it and it worked, after turning it off and removing the usb out of my computer I tried again and it didnt work.
Any ideas why?
Edit: when I had ROM manager I already tried to Flash CWM there if you're wondering.
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Harbb said:
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Click to expand...
Click to collapse
where can I find /etc/install-recovery.sh and what do you mean by file explorer with root capability?
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Harbb said:
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Click to expand...
Click to collapse
fairly new to android so I have no clue what you are talking about sorry... can you give me some steps on how to do that. again I apologize, Im still new
Download this from the market, i'm sure you'll figure it out
quick unrelated question: I tried to apply the ROM and it didnt continue, it said it was aborted or something
HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!
Machlev said:
HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!
Click to expand...
Click to collapse
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
no MD5 file found while installing via TWRP. Should I wipe /system?
Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
I wiped system and pushed an md5 file. Still fails with no reason.
I use this ROM -
https://cyngn.com/products/oneplusone/
(On the bottom)
What error are you getting?.. You could try another download (that one may be corrupt) or CM11 ROM, you should still be able to keep your app data as long as you don't wipe that partition.. You only need to wipe system/dalvik/cache..
Sent from my OnePlus ONE
Are you mounting /system with TWRP before doing that?
Also, dont move the file, try cp which works better with crosslink devices
And try chmod 755 /system/build.prop with adb while in recovery and check the build.prop isnt edited in Windows so EOL is Windows-like, then use Notepad++ to change to UNIX-type
easy, you copy pasted so permissions are not the same as the original
reflash system or rom
Sent from my A0001 using XDA Free mobile app
Yep. Permissions should be rw-r-r (or 644). If you don't know what you're doing don't mess around with system files.
Transmitted via Bacon
I have a clockworkmod file in the root of sdcard. I can see it in ES File Explorer but I cannot see it when I connect the phone to my computer. I use clockworkmod recovery only by booting into it when I need to...not by flashing it.
Although it dissappears when I delete it in ES File Explorer, if I refresh the screen it is still there. Anyone know what this file is exactly and how to get rid of it for good?
I tried another app called File Manager by Gira.me. It shows this file as ...
Path: /storage/emulated/0/clockworkmod
Type: */*
Size: 0 B
Last modified: Unknown
Permissions: ---
MD5: Unknown
When I try to delete it it says "Not enough permissions". There must be some way to delete this file.
Boot cwm, adb shell, rm the file
beekay201 said:
Boot cwm, adb shell, rm the file
Click to expand...
Click to collapse
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
xda6969 said:
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
Click to expand...
Click to collapse
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Aerowinder said:
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Click to expand...
Click to collapse
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
xda6969 said:
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
Click to expand...
Click to collapse
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Aerowinder said:
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Click to expand...
Click to collapse
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
xda6969 said:
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
Click to expand...
Click to collapse
Yes, you need to be rooted for restorecon command (su). A lot of people had troubles like yours when they moved to Lollipop (me too). Now that the recoveries have been updated, it's no longer an issue for most. You may still need to run the command, though. I suppose if you did a full wipe in stock recovery, it would fix the problem.
Your question about restoring app data with nandroid is vague and could be answered in a few ways. With your issue, the data partition is actually where the problem is, so I wouldn't recommend restoring the partition.
Instead, you might use Titanium Backup or something similar to back up only app data. But you need root for that.
Easiest solution is to root, fix issue, then, if you really want to, unroot. Don't need to wipe anything.