So i recently flashed the new "stock" gingerbread ROM, but it comes with all the bloatware. I was trying to remove the bloatware through windows command prompt/adb but after i push the old hack to get root (psneuter) and try to run it, i get the error: Failure to set prot mask <Inappropriate ioctl for device>. How do i get root access though adb with the new gingerbread rom (The adb shell still shows # instead of $)?
My TB is still rooted on the phone, i just want to remove the stock apps from my computer which is a lot faster. Thanks
Why don't you just flash a debloated gingerbread rom? And if your phones rooted just use root explorer from market to delete system apps.
Related
Okay, my Atrix is rooted and USB Debugging is on, but when I try to remount adb, it says "remount failed: Operation not permitted". Since I can't get adb shell to the # to come up, I type "adb shell su" and I get a Permission denied. I originally rooted with SuperOneClick and enabled sideloading with it and today I rerooted, unrooted, then used DesignGears' new root script to reroot and clean up SuperOneClick's root. Still no adb root access. I have TitaniumBackup, Superuser, and RootExplorer installed and even downloaded Root Checker to check if i really had root. I've spent almost all day looking this up and the closest I've found is the thread that talks about adb showing the device offline with the fix of copying over another adbd to the sbin folder(which I also tried) and adb still doesn't seem to recognize my root. The only time I can get the # prompt is when I do a shell root with SuperOneClick, but that is just a temporary root. Is anyone else experiencing this?
Edit: forgot to mention that adb works fine when I connect my NexusOne, so it's probably not the computer.
I have a Motorola Droid X on Android 2.3.3.
Motorola One Click Root goes all the way through and says that the phone should be rooted, but it never is. Here is the alternate method I attempted:
First I used SuperOneClick 2.2 in "Shell Root" mode to get the superuser (#) prompt in adb shell. From there I was able to mount the /system folder for read/write access.
I then copied, "chmodded" and --installed busybox to /system/xbin/.
Next I copied su to /system/bin and changed its permissions to 0755.
Finally, I installed a Superuser.apk
I still get no superuser prompts when I run a root app or type "su" in adb.
What am I missing?
U need to reset your phone and try all over again
Try to wipe/erase the application data of your root app and/or Superuser app, and try again to see if Superuser prompt will popup.
Several days ago, I upgrade ROM of my phone, and restored data and applications, then rooted, but when I type 'su' in Terminal Emulator application, it will wait for a few seconds and failed with "permission denied" error. I use strace to try to figure out why, I noticed that the real UID (10083) of Terminal Emulator application is not as same as the one (10069) send to Superuser. So I wiped the application data and Superuser application data (in fact, I also reinstalled them), then Superuser will prompt when executing 'su' command.
So I don't use adb push/install all that often but since I deleted mobile hotspot on my phone (I thought I had it frozen but apparently I didn't) I cannot upgrade my system.
I am rooted, and have tried installing from an emulator on the phone (and shell) as well as installing from and adb on the PC.
When I try to adb remount I get the following error:
remount failed: Operation not permitted
I have re-rooted thinking that an early version of root wasn't rooted for adb and also hoping that would let me install via shell. How can I get Mobile Hotspot back on?
Ok, so I was able to run a mount from terminal and copy the files and get the upgrade to go through.
So does anyone know why adb remount doesn't work? Is it because of the Moto Blur?
I have been recently messing with a Verizon ellipsis 7, it is rooted and I was trying to install some android 5.0 apps, boot animation, and fonts. Well I got a bootloop so I adb'd in and undid my modifications by pushing my backup of /system. Well that is where I went wrong Im guessing, I know have no access to adb shell, everytime I give that command I get this error
Code:
C:\android-sdk\platform-tools>adb shell
soinfo_link_image(linker.cpp:1635): could not load library "libc.so" needed by "
/system/bin/sh"; caused by load_library(linker.cpp:757): too small to be an ELF
executable: libc.soCANNOT LINK EXECUTABLE
Next I did adb pull /system/lib/libc.so and it is 0k in size. Now here comes the interesting part I did not modify my tablet yet to allow me to run adb in root mode so I cannot push the correct libc.so file to regain access to the adb shell. I am now stuck on the android screen (it is just stuck there not looping) can not run adb logcat because I have no access to shell and cannot push anything to the /system folder because I cannot run adb as root. So what do yall think, am I screwed?
Anyone have any idea?
im in the same mess, i messed with my system directory, got stuck on the verizon screen adb'd a backup but no go. wish i could help.
any idea of how to get root inside factory mode? my backup wasnt rooted
Hi there
I fiddle largely with MTK based phones and when I tweak a phone, I normally only need ADB root access. So my general process has been to:
1. OEM Unlock the device
2. unpack the boot.img and change the default.prop values (ro.adb.secure etc) to allow ADB root access.
3. Use ADB to get temporary write access using adb Root, then ADB remount Rw. Then you can pull and push files.
However I have an MT8735b, Android 7.0, Alps based device that will simply not give me ADB root access. so when I run "adb remount rw" or any of the equivalent shell scripts you can use instead, it just won't give me write access.
So I heard that newer phones based on these chipsets and also ones like 6737M are locking the device up in other ways.
My question is, does anyone have any ideas or knows anything I could try to get root access?
Any help is much appreciated.