and when i get home to activate it, after buying a PNY 2gb card to try to root the new one, Verizons system crashes like 2 min before i am able to activate. I called customer service to try and activate it, and the lady asks for my number, she's like "that number isn't in our system sir" It's a new number, so i figured maybe i got it wrong, check my old incredible and yep, it's the right phone number. this goes on for a few minutes, with me giving her every number on my plan with her saying "nope, not in our system." I'm thinking wtf happened?!
she puts me on hold and comes back saying "sorry our system is down" duhhh. now i have a phone that I cannot activate
i'm in the ##778 menu trying to edit everything to match my phone right now, kinda frustrating!
will this work?
I know the PRL can't just be edited, I was trying and it froze the phone... maybe i can get by without it lol.
ok got my phone rooted before programming the phone. VZW is back up too.
now all i need now is a way to make root persistant, it doesn't seem to work for me
Code:
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
anything I did wrong?
generic.imitation said:
ok got my phone rooted before programming the phone. VZW is back up too.
now all i need now is a way to make root persistant, it doesn't seem to work for me
Code:
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
anything I did wrong?
Click to expand...
Click to collapse
You can only issue those commands from recovery root shell ATM.
rynosaur said:
You can only issue those commands from recovery root shell ATM.
Click to expand...
Click to collapse
I was in recovery.
I went thru the whole root process, was able to remove cityID, and got to the part where you make root persistant, but it keeps giving me that error.
I'm also curious about this... the same exact thing is happening to me. The whole process goes flawless until "ln - s /system/bin/su /system/xbin/su"
Hopefully someone has an idea... any help is appreciated.
*EDIT*
I'm not sure why this works, my guess is that perhaps system/xbin/ was being read and because of that it wouldn't allow me to write su to it (from system/bin/). Maybe I'm way off, but either way, this did fix my problem(s):
After following the instructions for rooting as far as possible, have the command "ln -s /system/bin/su /system/xbin/su" in cmd but don't press enter yet. On the phone, select "Reboot" and right after selecting reboot press enter on cmd. Press the up arrow key and press enter again (and repeat multiple times until the phone reboots). You may even want to make a .bat file for this.. If all went well, you saw something similar to:
Code:
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
ln: /system/xbin/su: Permission denied
ln: /system/xbin/su: Permission denied
ln: /system/xbin/su: Permission denied
ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
As you can see, right before the phone reboots it accepts the "
ln -s /system/bin/su /system/xbin/su" command. Unfortunately, you have to do the same
thing with the last command, "chmod 06755 /system/xbin/su". You have to get adb to recognize
your phone in recovery (again) by following one of the tutorials/10 min video tutorial and follow
the same steps as before.
Concise:
Follow your choice of tutorial for rooting phone up until "ln -s /system/bin/su /system/xbin/su"
Follow my terrible instructions for getting phone to accept the above command.
Again get adb to recognize your phone in recovery. (Including applying update.zip again).
Follow my terrible instructions for getting phone to accept the "chmod 06755 /system/xbin/su" command
Reboot.
I have the EXACT same problem... my entire process works up until that line and then it says permission denied... quite frustrating
is there any other way to get it to work without rebooting? The reason being i only get ADB to work about once every 50 years so once i reboot my chances of getting it back to do the final chmod line is another 3 day long process.. and also the remove command dosent work either it says no such file or directory found
There might be another way, hopefully somebody with more knowledge can help you out... in the worst case scenario you can try my above "method," but it's definitely a pain to accomplish.
Related
Hey
So Ive been trying to unlock my phone using this thread..
http://forum.xda-developers.com/showthread.php?t=913681
I get stuck here..
Copy your nv_data.bin to temporary folder on your phone:
adb shell "mkdir /sdcard/efs"
adb push nv_data.bin /sdcard/efs
adb shell
su
ls -l -a /efs
If there is an nv_data.bin.md5 file in the directory, all is well. You should continue with these commands:
mv /efs/.nv_data.bak /efs/.nv_data.bakk
mv /efs/.nv_data.bak.md5 /efs/.nv_data.bakk.md5
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
rm /efs/.nv2.bak
rm /efs/.nv2.bak.md5
busybox cp /sdcard/efs/nv_data.bin /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin
exit
exit
Click to expand...
Click to collapse
How do i get to this adb shell thing?
Sorry Im just new to this android stuff. Help would be appreciated!
Code below works as far as getting root via adb
But after reboot I get following error:
Code:
? su
link_image[1717]: 2977 missing essential tablesCANNOT LINK EXECUTABLE
Do you know what's missing here?
Code:
./adblinux push psneuter /data/local/tmp
./adblinux push su-v3 /data/local/tmp
./adblinux push busybox /data/local/tmp
./adblinux shell chmod +x /data/local/tmp/psneuter
./adblinux shell chmod +x /data/local/tmp/su-v3
./adblinux shell
$ /data/local/tmp/psneuter
# exit
./adblinux shell
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/stl5 /system
# busybox cp -vaf /data/local/tmp/su-v3 /system/xbin/su
# ls -l /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# ls -l /system/xbin/su
# rm /system/bin/su
# busybox ln -s /system/xbin/su /system/bin/su
# ls -l /system/bin/su
# busybox cp -f /data/local/tmp/busybox /system/xbin
# busybox chown 0.2000 /system/xbin/busybox
# busybox chmod 0755 /system/xbin/busybox
# ls -l /system/xbin/busybox
# exit
./adblinux install -r Superuser.apk
./adblinux reboot
Hi,
I am new here, but advanced linux user
I have already done this succesfully on my X10i - thanks 1st working howto on linux OS
Theres propably mistake with these steps:
./adblinux shell chmod +x /data/local/tmp/psneuter
./adblinux shell chmod +x /data/local/tmp/su-v3
In my case these commands left errors. They have to simply mark these binaries as executable. But chmod +x * doesnt work (dont ask why ) - so I marked them as executables (su,psneuter,busybox) in desktop linux os before transfer and it worked.
The next mistake is in the line:
busybox cp -vaf /data/local/tmp/su-v3 /system/xbin/su
Because busybox is not yet in the system path - so you have to type:
# /data/local/tmp/busybox cp -vaf /data/local/tmp/su-v3 /system/xbin/su
Until
# /data/local/busybox cp -f /data/local/tmp/busybox /system/xbin
You can use busybox directly.
chmod +x doesn't work on android, you have to use chmod 777 or 666 or the like to get it to work properly.
Semperverus said:
chmod +x doesn't work on android, you have to use chmod 777 or 666 or the like to get it to work properly.
Click to expand...
Click to collapse
Or do it on linux GUI and mark as executable before transfer to Android device
I tried following this thread: http://forum.xda-developers.com/showthread.php?t=1349652
When I open a CMD window and type this is what happens:
c:\>cd adb
c:\adb>adb shell
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Superuser.apk
rm /system/app/Superuser.apk
# rm /system/bin/su
rm /system/bin/su
rm failed for /system/bin/su, No such file or directory
# rm /system/xbin/su
rm /system/xbin/su
# rm /system/bin/su
rm /system/bin/su
rm failed for /system/bin/su, No such file or directory
#
I can't seem to remove '/system/bin/su". I restarted my KF and typed "adb shel" "su" and it says "permission denied". Does that mean my KF is good to ship back and not rooted now?
bal1985 said:
I tried following this thread: http://forum.xda-developers.com/showthread.php?t=1349652
When I open a CMD window and type this is what happens:
c:\>cd adb
c:\adb>adb shell
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Superuser.apk
rm /system/app/Superuser.apk
# rm /system/bin/su
rm /system/bin/su
rm failed for /system/bin/su, No such file or directory
# rm /system/xbin/su
rm /system/xbin/su
# rm /system/bin/su
rm /system/bin/su
rm failed for /system/bin/su, No such file or directory
#
I can't seem to remove '/system/bin/su". I restarted my KF and typed "adb shel" "su" and it says "permission denied". Does that mean my KF is good to ship back and not rooted now?
Click to expand...
Click to collapse
Try to install an app that requires root like OpenVPN for example. If it doesn't install or work properly, you're unrooted. Or try to su in with a terminal emulator.
I always have problems to root official 2.3 with automatic ways, and found that this caused from some adb miscommunication.
So this is how to do it manual, in case automatic ways stacked.
First install adb-sdk and add its path to system variables, so to don't have to go to adb' s path before you can run it.
Then download doomlord' s rooting tool and extract it to drive C:\DoomLordRoot.v3.
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Preparation steps on device:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) uncheck fast boot from settings -> applications
Click to expand...
Click to collapse
Open windows command prompt window and do the above:
Code:
adb push c:\DoomLordRoot.v3\files\zergRush /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
chmod 777 /data/local/tmp/zergRush
./data/local/tmp/zergRush
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\busybox /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit again from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\su /system/bin/su
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit once more from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\Superuser.apk /system/app/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
cd /data/local/tmp/
rm *
reboot
This is basic what the runme.bat file does, just some paths corrected to point to the right locations.
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Oneclickroot v2. 2 did the work for me or something like this
Sent from my U8800
SS said:
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Click to expand...
Click to collapse
This probably means that rooting failed.
What messages you get when you run zergrush?
dancer_69 said:
This probably means that rooting failed.
What messages you get when you run zergrush?
Click to expand...
Click to collapse
I got messages for sending 149, then 189 zerglings, then messages about not being able to mount, find or write to directories.
It seems like it wasn't able to get root access to be able to run its process.
In any case, I just downgraded to the previous release and then used ZergRush, which worked perfectly
don't work.
try this, it works for my B528 rom!
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7
I just rooted my SG S4 Android 5.0.1 with auto-root. Everything worked fine (root complete and SU installed) till I think I gave a bad mount command in the root directory on the phone in terminal (i guess here it went wrong, not sure. Or perhaps during installation of bash or nano) when I was installing bash and nano. Since it rebooted, I **lost the wifi and cannot adb shell into my phone** anymore from mac.
Afterwards, I managed to flash clockwork mod recovery v6.0.4.6. and was able to mount /system, which enabled the ./adb shell again. However i can now only pwd and cd, everything else gets this error: /sbin/sh: ls: Permission denied
I think my phone is still recoverable, however I don't know what to do and don't want to risk making things worse. Which andoird wizard can help me please?
**Below here were my bash nano install commands:**
./adb shell
su
mount -o remount,rw /system
cp -r /storage/extSdCard/bashnano/terminfo /system/etc
cp /storage/extSdCard/bashnano/profile /etc
cp /storage/extSdCard/bashnano/bash /data
cp /storage/extSdCard/bashnano/nano /data
chmod 755 /data/bash
chmod 755 /data/nano
cd /system/bin/
mv sh sh.old
ln -s /data/bash sh
ln -s /data/bash bash
ln -s /data/nano nano
export TERMINFO=/etc/terminfo
export TERM=linux
mount -o remount,ro /system
**P.S. So I also performed a regular mount in root, which i think is what made things bad, but not totally sure!**
ansjovis86 said:
I just rooted my SG S4 Android 5.0.1 with auto-root. Everything worked fine (root complete and SU installed) till I think I gave a bad mount command in the root directory on the phone in terminal (i guess here it went wrong, not sure. Or perhaps during installation of bash or nano) when I was installing bash and nano. Since it rebooted, I **lost the wifi and cannot adb shell into my phone** anymore from mac.
Afterwards, I managed to flash clockwork mod recovery v6.0.4.6. and was able to mount /system, which enabled the ./adb shell again. However i can now only pwd and cd, everything else gets this error: /sbin/sh: ls: Permission denied
I think my phone is still recoverable, however I don't know what to do and don't want to risk making things worse. Which andoird wizard can help me please?
**Below here were my bash nano install commands:**
./adb shell
su
mount -o remount,rw /system
cp -r /storage/extSdCard/bashnano/terminfo /system/etc
cp /storage/extSdCard/bashnano/profile /etc
cp /storage/extSdCard/bashnano/bash /data
cp /storage/extSdCard/bashnano/nano /data
chmod 755 /data/bash
chmod 755 /data/nano
cd /system/bin/
mv sh sh.old
ln -s /data/bash sh
ln -s /data/bash bash
ln -s /data/nano nano
export TERMINFO=/etc/terminfo
export TERM=linux
mount -o remount,ro /system
**P.S. So I also performed a regular mount in root, which i think is what made things bad, but not totally sure!**
Click to expand...
Click to collapse
If you can get into download mode ,flash stock rom from Sammobile