I searched long and hard, but couldn't find the answer...hope it hasn't already been answered
I used the easy root and it looks like it got stuck on step 3. (S-off is accomplished, but no root). So I tried to start with step 7 manually rooting it.
I do adb shell push psneuter /data/local/
return: Permission denied.
I also can't chown nor chmod anything. I am on windows 7, running the command prompt as admin, and have adb setup properly (or so I have read). Any ideas?
phatwcinfrcr said:
I searched long and hard, but couldn't find the answer...hope it hasn't already been answered
I used the easy root and it looks like it got stuck on step 3. (S-off is accomplished, but no root). So I tried to start with step 7 manually rooting it.
I do adb shell push psneuter /data/local/
return: Permission denied.
I also can't chown nor chmod anything. I am on windows 7, running the command prompt as admin, and have adb setup properly (or so I have read). Any ideas?
Click to expand...
Click to collapse
go here http://forum.xda-developers.com/showthread.php?t=951190
they will help
Make sure to turn usb debugging back on.
Sent from my ADR6400L using XDA App
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.
Okay well its not as urgent as the title but I am having some problems rooting my thunderbolt. I am using the root method here http://forum.xda-developers.com/showthread.php?t=996616 however, I getting stuck. The first three commands provide a return in terminal but the last two
adb shell chmod 777 /data/local/psneuter
adb shell chmod 777 /data/local/busybox
just return to C:\sdk\platform-tools. I proceeded to the next command adb shell and I get a # instead of $. Any ideas? I have tried it in both charge only and disk drive with usb debugging enabled and fast boot off. In the instructions I am following it didnt specify what to do with the exploits contents so I dropped them all in the platform-tools folder.
http://chat.andirc.net:9090/?channels=#
type in your name and #thunderbolt
I got a ton of help rooting my phone yesterday
Ive pushed all kinds of other stuff, I did do the add system enviromental variable to XP so this could be my issue, though like i said its worked for other things ...
ERROR I GET>
CANNOT STAT
adb push stock-hc-flyer-hboot_1.11.0006.nb0 / && adb shell dd if=/stock-hc-flyer-hboot_1.11.0006.nb0 of=/dev/block/mmcblk0p18
NO SUCH FILE OR DIRECTORY
a thourough explanation or a cut and pastable pointing my adb to this file, its in the root, the variable is to the root C also, so....
PLEASE HELP, to get me past this 10+hours of hell
May be a connection between your computer and phone issue. I have this error when I wanted to root my nexus s. Try different driver for your flyer.
Accidentally sent from my Google Nexus S using XDA Premium
Make sure the adb works via "adb devices" and "adb shell". If it does not work you can try "adb kill-server" first.
I don't think you can write (push) to "/" without "adb remount". Not sure if it is a good idea to write to root directory.
Alternatively, you can use the storage in /data/local/tmp, it is always writable.
I have a NEC Terrain NE-201A1A, use android 4.0.4 stock rom, I don't know how to root it, who can help me? Thanks so much
There is not any root method
zolahn said:
I have a NEC Terrain NE-201A1A, use android 4.0.4 stock rom, I don't know how to root it, who can help me? Thanks so much
Click to expand...
Click to collapse
At least for now, there is not any permanent root method. Only a temp shell root. NEC Terrain is NAND/bootloader locked, S-on and does not have fastboot support.
You should have used search. More about this:
Rooting NEC Terrain
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
NEC Terrain Rooting and Flashing Guide
Root method discovered for NEC Terrain?
Unlocking of NEC Terrain SIM/Root
FFDA said:
At least for now, there is not any permanent root method. Only a temp shell root. NEC Terrain is NAND/bootloader locked, S-on and does not have fastboot support.
You should have used search. More about this:
Rooting NEC Terrain
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
NEC Terrain Rooting and Flashing Guide
Root method discovered for NEC Terrain?
Unlocking of NEC Terrain SIM/Root
Click to expand...
Click to collapse
I read all thread but I can't install this driver in my computer, I think this driver is not correct for my phone, do u have other driver for nec terrain?
I'm using linux
zolahn said:
I read all thread but I can't install this driver in my computer, I think this driver is not correct for my phone, do u have other driver for nec terrain?
Click to expand...
Click to collapse
I am assuming that you are using Windows so try this ADB Driver Installer.
Hi
FFDA said:
I am assuming that you are using Windows so try this ADB Driver Installer.
Click to expand...
Click to collapse
Can u guide me how to root it? (tmp root). thanks
I can try
zolahn said:
Can u guide me how to root it? (tmp root). thanks
Click to expand...
Click to collapse
I have never tried getting temp shell root from windows, but it should pretty simple. First of all you have to set up adb (if you don't have it yet try this) and then just do this:
In windows cmd, go to folder where your run_root_shell file is.
Push run_root_shell to /datal/local/tmp folder using command: adb push run_root_shell /data/local/tmp/
Set permissions to run_root_shell: adb shell chmod 777 /data/local/tmp/run_root_shell
Go to adb shell using command: adb shell
Lastly get root temp using command: /data/local/tmp/run_root_shell
Good luck
zolahn said:
I read all thread but I can't install this driver in my computer, I think this driver is not correct for my phone, do u have other driver for nec terrain?
Click to expand...
Click to collapse
Here's a list of root apps you can try:
Framaroot
Vroot
For PC(plug your device into your PC and start rooting):
Kingo android root
These are really simple applications that helps you root your device with just a click.
---------- Post added at 09:46 PM ---------- Previous post was at 09:43 PM ----------
Before I forgot to mention this, after you've root your device with Kongo android root, the action can be reversed(unroot). You can't unroot with framaroot(in my memory), with vroot you can simply unroot your device by uninstalling this app.
FFDA said:
I have never tried getting temp shell root from windows, but it should pretty simple. First of all you have to set up adb (if you don't have it yet try this) and then just do this:
In windows cmd, go to folder where your run_root_shell file is.
Push run_root_shell to /datal/local/tmp folder using command: adb push run_root_shell /data/local/tmp/
Set permissions to run_root_shell: adb shell chmod 777 /data/local/tmp/run_root_shell
Go to adb shell using command: adb shell
Lastly get root temp using command: /data/local/tmp/run_root_shell
Good luck
Click to expand...
Click to collapse
So if i use ubuntu, how can root it?
Let's try Linux!
zolahn said:
So if i use ubuntu, how can root it?
Click to expand...
Click to collapse
You understand that this temp shell root does not let you debloat the phone, resize partition, ect? It basically lets you read more partitions through adb shell (Command line. NO graphical interface)?
If you still what to gain temp root:
Open terminal. Press
Code:
CTRL+ALT+T
at the same time.
In terminal paste:
Code:
sudo apt-get install android-tools-adb
and enter password. If you get an error that there isn't such application or similar paste this command:
Code:
sudo add-apt-repository ppa:phablet-team/tools && sudo apt-get update
and then the first one again.
Add the rule to 99-android.rules file. Open the file with this command:
Code:
sudo gedit /etc/udev/rules.d/99-android.rules
and paste in the window that just opened this line (Don't forget to add YOUR account name where it saids so in this line)
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", ATTR{idProduct}=="0358", MODE="0666", OWNER="[B]your Linux account name[/B]"
save and close the window.
At this point you may need to restart your PC for changes to take effect, so better do it. Also turn debugging mode in your NEC Terrain and connect it to you PC with USB cable.
Go to folder where your run_root_shell file is, right-click and choose "open in terminal".
Check if ADB is set up right. Type in terminal:
Code:
adb devices
Your should see text like this:
Code:
List of devices attached
ea1f2870 device
Tell me if you see this:
Code:
List of devices attached
???????????? no permissions
Push run_root_shell to /datal/local/tmp folder using command:
Code:
adb push run_root_shell /data/local/tmp/
Set permissions to run_root_shell:
Code:
adb shell chmod 777 /data/local/tmp/run_root_shell
Go to adb shell using command:
Code:
adb shell
Lastly get root temp using command:
Code:
/data/local/tmp/run_root_shell
If you see # instead of $ in terminal you have shell root privileges.
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
I bricked my Kindle hdx 7" and am looking for help. i JUST COULDN'T LEAVE IT ALONE. rooted wth towelroot, rolled back to 13.2.2.8, Safestrap, Nexus 1.02 for safestrap on rom slot 1. Could not get instant video, so attempted update to 13.4.5.2 to see if that would work. Realized I forgot to backup like I am supposed to do and stopped update. After no boot it went to stock recovery and I did a factory reset, just like everyone says not to do, and now I am in bootloop. Gray Kindle Fire logo for about 45 seconds, then black screen for about 45 seconds. I can communicate throught abd, but I don't know what to enter. I have found TUT from r3pwn which seems really helpful, I just cannot use keyboard fast enough to get it in,(nerve damage from brain tumor). I have seen at some point that I should get into fastboot mode, I can do that, I just don't have Windows drivers. I have been all around XDA and cannot remember where I saw things. can someone point me in the right direction? Thank you.
It took a while, but, accomplished it with help from @Davey126, reading posts from @draxie, @ONYXis, @EncryptedCurse and others. Too many to list.
Fastboot mode is useless to you anyways, as you haven't unlocked the bootloader.
The important thing is that you still have ADB access. If you can't enter the commands in time, just make a batch script to do it for you.
Code:
adb wait-for-device
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
As far as I know, you only need to add adb wait-for-device before it tries to run any of the other commands.
Save the above code as .bat in your text editor of choice (i.e. Notepad). Remember to change the local path (in the second to last line) to wherever the .bin is on your computer.
EncryptedCurse said:
Fastboot mode is useless to you anyways, as you haven't unlocked the bootloader.
The important thing is that you still have ADB access. If you can't enter the commands in time, just make a batch script to do it for you.
Code:
adb wait-for-device
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
As far as I know, you only need to add adb wait-for-device before it tries to run any of the other commands.
Save the above code as .bat in your text editor of choice (i.e. Notepad). Remember to change the local path (in the second to last line) to wherever the .bin is on your computer.
Click to expand...
Click to collapse
Thank you for your help, I will do this after work.
I couldn't connect with adb on laptop, connected today and batch file stops.
adb wait-for-device
adb shell
[email protected]:/ $
Then when kindle powers off for boot loop, cmd window exits.
Any ideas?
my new batch file and logcat. is it hopeless, or more to come on learning adb?
notjoken958 said:
It took a while, but, accomplished it with help from @Davey126, reading posts from @draxie, @ONYXis, @EncryptedCurse and others. Too many to list.
Click to expand...
Click to collapse
Glad you got it working. Like most complex device recovery efforts it take a lot of reading/filtering and trial/error/retries before being rewarded with meaningful successes. As you probably learned each journey is a little different; almost impossible to develop step-by-step recovery guide that wouldn't eventually have dozens of amendments covering 'special circumstances'. Enjoy your revived HDX!