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?
In older versions of prime, I used to be able to use root explorer to remove applications from /system/app, and they would disappear from the tray. Lately, when I try to delete them using root explorer, they disappear when I hit delete, but they are still in the menu, and still fully functional.
I really despise having facebook on here (they just added it to the rom), and the other bloat that came with it, but not can't seem to remove it. Anyone know how?
compywiz said:
In older versions of prime, I used to be able to use root explorer to remove applications from /system/app, and they would disappear from the tray. Lately, when I try to delete them using root explorer, they disappear when I hit delete, but they are still in the menu, and still fully functional.
I really despise having facebook on here (they just added it to the rom), and the other bloat that came with it, but not can't seem to remove it. Anyone know how?
Click to expand...
Click to collapse
Have you tried using Titanium Backup to uninstall the app after you have removed it from the system/app folder?
Mark.
mskip said:
Have you tried using Titanium Backup to uninstall the app after you have removed it from the system/app folder?
Mark.
Click to expand...
Click to collapse
It appeared to work using Titanium. Does this mean it may be a root explorer bug? I guess I'll try downgrading to an older version of RE. I am not a big fan of titanium.
Tried a known working version of root explorer with no luck. I guess something changed in the rom or superuser which is preventing it from working properly.
compywiz said:
Tried a known working version of root explorer with no luck. I guess something changed in the rom or superuser which is preventing it from working properly.
Click to expand...
Click to collapse
If you remove the app from /system/app also delete the associated dalvik executable file from /data/dalvik-cache. This should kill the app.
Roach2010 said:
If you remove the app from /system/app also delete the associated dalvik executable file from /data/dalvik-cache. This should kill the app.
Click to expand...
Click to collapse
I tried deleting the executable file as well, but still no luck.
Turns out it seems to be more than just the apps, I tried removing the bootanimation from /system/media with no luck. It's like I don't have r/w access.
compywiz said:
I tried deleting the executable file as well, but still no luck.
Turns out it seems to be more than just the apps, I tried removing the bootanimation from /system/media with no luck. It's like I don't have r/w access.
Click to expand...
Click to collapse
This is probably a stupid question but did you make sure the folder was Mounted to R/W (and checking it sayds R/W at the top) via the button at the top of Root Explorer before attempting to delete the file?
Mark.
mskip said:
This is probably a stupid question but did you make sure the folder was Mounted to R/W (and checking it sayds R/W at the top) via the button at the top of Root Explorer before attempting to delete the file?
Mark.
Click to expand...
Click to collapse
It's ok, thanks for trying to help. Root explorer pops up a message if you try to delete something in R/O mode saying "... cannot be deleted because the file system is read-only."
It also seems to be working now, no idea why. Maybe a reboot did the trick. The files I remove from /system/app are now disappearing from the menu.
Still unsure on the boot animation though, is that still stored in /system/media/bootanimation.zip?
compywiz said:
It's ok, thanks for trying to help. Root explorer pops up a message if you try to delete something in R/O mode saying "... cannot be deleted because the file system is read-only."
It also seems to be working now, no idea why. Maybe a reboot did the trick. The files I remove from /system/app are now disappearing from the menu.
Still unsure on the boot animation though, is that still stored in /system/media/bootanimation.zip?
Click to expand...
Click to collapse
Yes bootanimation is still stored in /system/media/
compywiz said:
It's ok, thanks for trying to help. Root explorer pops up a message if you try to delete something in R/O mode saying "... cannot be deleted because the file system is read-only."
It also seems to be working now, no idea why. Maybe a reboot did the trick. The files I remove from /system/app are now disappearing from the menu.
Still unsure on the boot animation though, is that still stored in /system/media/bootanimation.zip?
Click to expand...
Click to collapse
Yes but if you're on Prime 2.0.3, there's one in data/local
Anything bootanimation in data/local will over ride the one in system/media.
compywiz said:
It's ok, thanks for trying to help. Root explorer pops up a message if you try to delete something in R/O mode saying "... cannot be deleted because the file system is read-only."
It also seems to be working now, no idea why. Maybe a reboot did the trick. The files I remove from /system/app are now disappearing from the menu.
Still unsure on the boot animation though, is that still stored in /system/media/bootanimation.zip?
Click to expand...
Click to collapse
Yes it is.
If you copy your new bootanimation.zip file to /data/local then it will look for it there first (before looking in system/media) and load up the new file. Tested it and it works fine using Root Explorer to copy the file across but just make sure the file is made specifically for the Transformer.
Mark.
Thanks guys!
Hi guys, I wanted to ask you if someone can help me installing the Asus Keyboard app on my TF300T with CM10. I have the Keyboard.apk , but it gives an error when installing... Any help?
Did you have the odex files too? And you need to manual place into /system/app. Normall install will not work.
Sent from my GALAXY Cooper
geldebanho said:
Hi guys, I wanted to ask you if someone can help me installing the Asus Keyboard app on my TF300T with CM10. I have the Keyboard.apk , but it gives an error when installing... Any help?
Click to expand...
Click to collapse
You will find the Asus Keyboard apk and odex file in the zip file
Just push it on /system/app
Ok, I'll try it later. Thanks!
It didn't work... Any ideas? :s
geldebanho said:
It didn't work... Any ideas? :s
Click to expand...
Click to collapse
Describe? It didn't work.
After placing each file in /system/apps ( I always set permissions as well 644). Reboot. you went to settings/Language & Input, placed a check beside it/Clicked Default and selected it.
If you pushed it with adb permissions may be correct already.
geldebanho said:
It didn't work... Any ideas? :s
Click to expand...
Click to collapse
It's the native keyboard from Asus with Odex file.
You have 2 solutions for push these files on your system, but you need root rights:
- 1st: by ADB
adb push XXX YYY : copy the file XXXX from your PC on to your system/app YYY of your phone
- 2nd: by an APK as Root explorer, Es File Explorer etc (with root rights)
just copy and paste thes 2 files to your SDcard and copy and paste again to the system/app folder.
After don't forget to reboot your device.
And finally you went to settings/Language and Input, placed a check beside it/Clicked Default and selected it.
philos64 said:
It's the native keyboard from Asus with Odex file.
You have 2 solutions for push these files on your system, but you need root rights:
- 1st: by ADB
adb push XXX YYY : copy the file XXXX from your PC on to your system/app YYY of your phone
- 2nd: by an APK as Root explorer, Es File Explorer etc (with root rights)
just copy and paste thes 2 files to your SDcard and copy and paste again to the system/app folder.
After don't forget to reboot your device.
And finally you went to settings/Language and Input, placed a check beside it/Clicked Default and selected it.
Click to expand...
Click to collapse
+1
philos64 said:
It's the native keyboard from Asus with Odex file.
You have 2 solutions for push these files on your system, but you need root rights:
- 1st: by ADB
adb push XXX YYY : copy the file XXXX from your PC on to your system/app YYY of your phone
- 2nd: by an APK as Root explorer, Es File Explorer etc (with root rights)
just copy and paste thes 2 files to your SDcard and copy and paste again to the system/app folder.
After don't forget to reboot your device.
And finally you went to settings/Language and Input, placed a check beside it/Clicked Default and selected it.
Click to expand...
Click to collapse
I did the 2nd method right from the beginning - I even set permissions for the files. The problem is that the settings thing stops responding when I try to open it with the files inside system/apps ...
geldebanho said:
I did the 2nd method right from the beginning - I even set permissions for the files. The problem is that the settings thing stops responding when I try to open it with the files inside system/apps ...
Click to expand...
Click to collapse
Just reboot when your copy/paste is done
No good... I did everything, copied the files to system/app with root explorer, rebooted, and the keyboard isn't even listed on the settings page...
geldebanho said:
No good... I did everything, copied the files to system/app with root explorer, rebooted, and the keyboard isn't even listed on the settings page...
Click to expand...
Click to collapse
OK I'll try to duplicate your issue and report back. Which cm10 rom are you using?
I chose cm10 nightlies and I can't get a proper install either, I'm looking into why.
I'm using the 09-11 nightly.
geldebanho said:
I'm using the 09-11 nightly.
Click to expand...
Click to collapse
Thanks I am working on it.
I deodexed and that failed to show installed.
Made a flash zip and that failed to show installed.
Now I'm really curious.
I need to flash stock rom and play a little then come back to cm10.
I'll report when I have more info.
I can't make it work no matter what I try, I'm sorry. If I think of anything else I'll reply here.
Maybe they are some missing librares they are in /system/lib/ ? Check the logcat, it should what is missing.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2
Thanks I'm looking into that now. I'll reflash stock and try to get a better idea what might be missing. I see where it fails and why but haven't been able to relate that to a lib or config yet.
Thanks for the help!
When I do something like this I don't always get it fixed but I certainly learn new things as I go.
I'm not making any progress on this problem, sorry but I'm finished unless something else turns up soon.
Maybe someone else can lend a hand.
I will flash CM next days, as I already unlocked bootloader. Myabe I can find out what is missing, but try to add all the apks from this screen, it from stock.
Sent from my unlocked ASUS TF300T
I have a OnePlus One CM11 rooted.
I read a post here:
http://forum.xda-developers.com/showthread.php?t=2064859&highlight=deleted
And therefore I "played" a little bit with my phone with those things:
1) \System\priv-app\ContactsProvider.apk
2)ContactsStorage from Setting ->Apps->All->ContactsStorage
Somehow I ended up with the situation that:
1)ContacsStorage does not appear at the apps list.
2)The directory \data\data\com.android.provider.contacts have disappeared.
I want to reinstall\flash the ContactsStorage app.
I know that reinstalling the rom will fix it, but I'm trying to avoid it.
Do you know of any other way I can do it?
Extract it from your ROM zip. Copy back to it's original location with a file manager (Root Explorer), set permissions and reboot.
davebugyi said:
Extract it from your ROM zip. Copy back to it's original location with a file manager (Root Explorer), set permissions and reboot.
Click to expand...
Click to collapse
I don't have my rom zip (This is the rom that came installed).
But returning the original backup apk and rebooting did not do the job
barak91 said:
I don't have my rom zip (This is the rom that came installed).
But returning the original backup apk and rebooting did not do the job
Click to expand...
Click to collapse
Then you are doing spmething wrong. What do you use to move? Is system set to R/W? permissions set? Same folder?
davebugyi said:
Then you are doing spmething wrong. What do you use to move? Is system set to R/W? permissions set? Same folder?
Click to expand...
Click to collapse
Attached screenshots.
barak91 said:
Attached screenshots.
Click to expand...
Click to collapse
The problem that the apk is vanishing after reboot is not a permission issue. Try a better file manager (in my case Root Explorer never fails). Mount system as R/W and do the rest.
davebugyi said:
The problem that the apk is vanishing after reboot is not a permission issue. Try a better file manager (in my case Root Explorer never fails). Mount system as R/W and do the rest.
Click to expand...
Click to collapse
The apk is NOT vanishing, it stays there.
The app of ContactsStorage is vanished from the apps list permanently.
As well as the folder in \data\data of com.android.providers.Contacts.
The option to sync google contacts is gone as well.
barak91 said:
The apk is NOT vanishing, it stays there.
The app of ContactsStorage is vanished from the apps list permanently.
As well as the folder in \data\data of com.android.providers.Contacts.
The option to sync google contacts is gone as well.
Click to expand...
Click to collapse
Did you make sure to also put the odex file in the folder as well?
Heisenberg said:
Did you make sure to also put the odex file in the folder as well?
Click to expand...
Click to collapse
I don't know what the odex file is.
I did not back the odex file so I do not know if it's the original, but there is a ContactsProvider.odex in there.
I tried installing it with both Flashify and Magisk, but both methods failed.
When I tried installing it via the included Xposed Installer, it also failed, but gave me the message:
> Error: Xposed_Framework.jar already exists in /system/framework
I'm guessing a previous installation failed, but left the file there.
My next idea is to delete that file from /system/framework and try again, but since it's in an RO directory I don't have permission.
I tried using a terminal emulator to mount the drive in rw mode, and also tried using a root file explorer, but either both methods don't work, or I just couldn't figure it out.
Anyone have an idea of how to remove or rename that file so I can try to install the .zip ?
-Thanks
Highfiverobot said:
I tried installing it with both Flashify and Magisk, but both methods failed.
When I tried installing it via the included Xposed Installer, it also failed, but gave me the message:
> Error: Xposed_Framework.jar already exists in /system/framework
I'm guessing a previous installation failed, but left the file there.
My next idea is to delete that file from /system/framework and try again, but since it's in an RO directory I don't have permission.
I tried using a terminal emulator to mount the drive in rw mode, and also tried using a root file explorer, but either both methods don't work, or I just couldn't figure it out.
Anyone have an idea of how to remove or rename that file so I can try to install the .zip ?
-Thanks
Click to expand...
Click to collapse
In the Xposed app you should be able to just run the uninstaller script. If that doesn't work, boot TRWP and delete it from there.
D3RP_ said:
In the Xposed app you should be able to just run the uninstaller script. If that doesn't work, boot TRWP and delete it from there.
Click to expand...
Click to collapse
Unfortunately, the uninstaller also fails.
It says it can't remove that file from a read only directory..
Highfiverobot said:
Unfortunately, the uninstaller also fails.
It says it can't remove that file from a read only directory..
Click to expand...
Click to collapse
flash installer or uninstaller through TWRP
wmcdrugs said:
flash installer or uninstaller through TWRP
Click to expand...
Click to collapse
Root Explorer....
This app does wonders, it allows you to modify directories in /system and other root folders. You can even change permissions of specific folders/files from read/write/read-only....etc. I've had this app since the earliest of android days and it has been my go to file explorer. Root Explorer of course requires root....but it completely unlocks your phone and allows you to modify any system file that is set to any permission. Of course there are other file explorers that allow you to modify system files, but this is the one that i have the most experience with. You should be able to access the system folder where the Xposed file remains and modify it so it can fix your problem.
djer34 said:
Root Explorer....
This app does wonders, it allows you to modify directories in /system and other root folders. You can even change permissions of specific folders/files from read/write/read-only....etc. I've had this app since the earliest of android days and it has been my go to file explorer. Root Explorer of course requires root....but it completely unlocks your phone and allows you to modify and system file that is set to any permission. Of course there are other file explorers that allow you to modify system files, but this is the one that i have the most experience with. You should be able to access the system folder where the Xposed file remains and modify it so it can fix your problem.
Click to expand...
Click to collapse
This!. I've used it for years. Not muss no fuss. It's not bloated like a certain couple others I know of. It just does what it does and does it well. Manages files. No extra garbage.Give it a try. I'd be surprised if you can't delete it with Root Explorer. If you do try it, go to the folder you want to delete the file from. Once in there, look at the top right of the screen. Somewhere up there It will say MOUNT R/W. Touch that and you should be able to do whatever you want to within that folder.
Do you have the magisk DNSCrypt module installed? If so, thats why you cant modify anything in /system. Not sure why or how it breaks it, but it does. Took me for ever to figure out what was causing it. Now that i removed the module, i can modify anything i want again.
Sent from my [device_name] using XDA-Developers Legacy app