Related
I permrooted pre-OTA, and received the OTA shortly after rebooting, which broke my permroot. I wiped, downgraded, installed OTA and tried permrooting again but now when I type su, term returns 'su: unknown user root' rage works to drop me in a root term, but following the process does not succeed in giving me permroot.
When trying to find any more information about the error I've been getting, I've tried 'whoami' and 'passwd' and they both return 'uknown uid 0'
Any thoughts?
Sent from my T-Mobile G2 using XDA App
the initial root was done with visionary, but i have tried rage in addition.
bump..any ideas?
do i need to play with any permissions when i get temproot via rage??
bump......
bump msglength
jakobdroid said:
When trying to find any more information about the error I've been getting, I've tried 'whoami' and 'passwd' and they both return 'uknown uid 0'
Click to expand...
Click to collapse
whoami and passwd are failing because there is no passwd file. But it's saying you are uid 0, so you are the root user.
What happens when you try the rage method, do you get error messages ? Which bit isn't working exactly ?
If you got temp root then try the gfree method for perm root.
Sent from my HTC Vision using XDA App
following the steps everything goes well until
# /data/local/tmp/root
i get:
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/bin/su/su' : Not a Directory
jakobdroid said:
following the steps everything goes well until
# /data/local/tmp/root
i get:
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/bin/su/su' : Not a Directory
Click to expand...
Click to collapse
The "mkdir failed" message is normal, just ignore that.
But the "cp" message indicats a problem. Check the files on your sd card, have you already got a folder called "su" on it before you started this procedure ? Because that will make things go wrong, there needs to be a *file* su on your SD card, after you have copied it across from your PC using "adb push". If you already have an "su" directory, rename it as something else, then start again with the procedure.
Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
EDIT: Go to 3rd post.
kpaekn said:
Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
If you're wanting to root, go straight to the source; the guide in the Wiki here is based on the work the devs who actually found the means to root the device.
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Is USB debugging turned on and is the SDcard not mounted?
Sent from my T-Mobile G2 using XDA App
Sounds like the SD card is mounted on your PC and not the phone ? It needs to be mounted on the phone or this won't work.
Sent from my HTC Desire Z
All that command does is copy that file from your computer to the sdcard. You could accomplish the same thing by dragging and dropping that file to the sdcard.
The 'push' command just means "copy from location A to location B"
Sent from my HTC Vision using XDA App
You could always just mount the SDcard... but anyway, to solve this type in "adb remount" and enter the command before pushing the file
Sent from my HTC Vision using XDA App
USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
kpaekn said:
USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
The adb remount error is expected (the command requires your ro.secure prop to be set to 0, which you can't do until you have rooted).
So you were able to copy files to the SD card? Just to verify again, you should try mounting the SD card to you computer (so it shows up as a device on your computer's file explorer), copy over a file, unmount the card from your computer (and remember to also hit the button on phone to do so), and then try the ADB push commands again.
Ok, with the phone on plug it into your computer and mount USB storage. Drag and drop 'su' and superuser.apk into the sdcard then unmount USB storage. Make sure USB debugging is on at this point (you'll see it in the notification task bar). Do these commands:
Code:
adb push rage /data/local/tmp/rage
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/*
Then in the terminal app type:
Code:
/data/local/tmp/rage
You'll see some message pop up saying something about 'forked #### childs' and that's temp root. Then follow the instructions on running gfree to gain full root. Btw, you can just copy and paste all those commands if you think you'll make a mistake.
You may also be able to run the '/data/local/tmp/rage' command with the 'adb shell' command, never tried it myself though.
kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Oh come on !!!
the path separator in linux (and the phone is a linux computer) is / and not \ !!!
So the command is:
Code:
C:\AndroidSDK\tools>adb push su /sdcard/su
Just to tell you something about the unix shell:
The \ char is a so called escape character that you use to tell the shell that it should not ignore the next character even if it is a white space (i.e. space)
You would use it if you have to specify a path that contains spaces:
i.e.:
Code:
mkdir dir\ with\ 3\ spaces
will create a directory with the name "dir with 3 spaces". This would not work without the \ characters.
have fun - Guhl
Haha... it's funny how simple the answer was.
Thanks for your guys' help.
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
/data/local/tmp/root
Click to expand...
Click to collapse
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
sammd301 said:
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Click to expand...
Click to collapse
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
raitchison said:
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
Click to expand...
Click to collapse
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
gbarayah said:
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
Click to expand...
Click to collapse
right now...neither method works not the "visionary r14 or ADB/RAGE/GFREE" I wouldn't mind using either method, the problem is that ADB/Rage/GFREE METHOD keep giving this error message "mkdir failed for /system/xbin, File exists" which I have done a ton of research and still can find a fixed,
sammd301 said:
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
Click to expand...
Click to collapse
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
ON YOUR PHONE:
1. Launch Terminal Emulator
2. Execute /data/local/tmp/rage
3. Wait for the message: "Forked #### childs."
4. Menu > Reset Term - Terminal Emulator will exit.
5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Click to expand...
Click to collapse
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Right now I going to try to use this command to fix the error and if it doesn't work, I will then try to flash a custom and see how that goes...Update will be posted as I go along....thanks for the kind help....
raitchison said:
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Click to expand...
Click to collapse
I will attempt to flash ClockWorkmod, once I try out "ianmcquinn" suggesting in trying to fix the rooting error...thanks for the help
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Yes I used the wiki instruction to gain temporary root on the phone and proceeded to tryout the above command...I got mostly error with the command below is what I en-counted as I enter the command....
# /data/local/tmp/busybox killall rage
No error here just # prompt
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
No error again just # prompt
# rm -rf /system/xbin
Error "rm failed for -rf, Read-only file system"
# mkdir /system/xbin
Error "mkdir failed for /system/xbin, File exists"
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
Error "cp: can't stat '/system/xbin/busybox': Not a directory"
# chmod 4755 /system/xbin/busybox
Error "Unable to chmod /system/xbin/busybox: Not a directory"
# /system/xbin/busybox --install -s /system/bin
Error "/system/xbin/busybox: not found"
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
Error "cp: not found"
# cp /sdcard/su /system/bin/su
Error "cp: not found"
# chmod 4755 /system/bin/su
Error "Unable to chmod /system/bin/su: No such file or directory
I am now going to attempt the Clockwork custom rom flash..
Folks victory is mine....No, VICTORY IS OURS, I sincerely like to thank all of you all, who replied with helpful suggesting...especially the following members "raitchison" from West Hill, CA and "ianmcquinn" a true senior member of xda-developer.
This is what I did to finally get the phone rooted....
I took "Raitchison" advice by trying to use flash_image to flash ClockWorkMod recovery... but during the process I could not get pass copying file to the phone root system folder usind android terminal emulator ...so I input this command "chmod 777/system" to gain write access to the folder...after doing that I manually moved busybox file to system folder and attempted a rooting the phone using the rooting instruction from the HTC G2/DESIRE Z wiki site...at...
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
And this time around, everything went as normal after rooting the phone I open root required app and Wa La...no error message...
Guys I once again wants thank you all for the support....I also looked forward to help out others facing the same issue...so if anyone has encounter the same or similar issue please feel free to post here and I will response....
Can any one help me I am trying to close this thread...How do I go about doing it....thanks
There is no need to close the thread, if anyone has a similar problem and finds it via search they can come in here and bring the discussion back up, otherwise if there is no activity it will naturally fall to the bottom of the thread list.
It works for me I just did it yday using visionary and gfree all on my phone weird that it doesn't work for you?
Sent from my Liquid Metal using XDA Premium App
[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully？？？
alexsec said:
[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully？？？
Click to expand...
Click to collapse
ZN's method still works just fine.
http://forum.xda-developers.com/showthread.php?t=1531646
i can't root!
i can't root!
Verify the device is showing under the device manager, usb debugging is turned on, and that it is being run as administrator.
What OS are you using?
i have the same problem. Can't root after the recent update. using W7, executing it with and without administrator rights. Executing with administrator rights it says something of ADB.
alexsec said:
i can't root!
Click to expand...
Click to collapse
Updating script. Try once again.
rooted!! thanks!!
How to Updating script. Try once again.
@ ZeroNull, can you confirm whether ICS_rooting_A10x_A5xx works for the latest build?
Build number
Acer_A100_2.001.01_COM_GEN2
I have been unsuccessful so far:
==========================================
Preparation is finished.
-
Executing of the main script.
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
I can confirm that I successfully rooted my A100 using ZeroNull's simple method (http://forum.xda-developers.com/showthread.php?t=1531646)
Build number: Acer_AV041_A100_1.037.00_WW_GEN1
I didn't even use the new script, I'm still using the old one (ICS_rooting.zip)
Unfortunately I can also confirm problems with recent updates of the SuperUser APK (It did not assign the correct Group ID), but apparently they were fixed in the latest update (v3.1.3)
Good Luck.
---------- Post added at 10:30 AM ---------- Previous post was at 10:05 AM ----------
alexsec said:
i can't root!
Click to expand...
Click to collapse
alexsec said:
How to Updating script. Try once again.
Click to expand...
Click to collapse
Hi alexsec, did you try with the new script, it creates a different directory than the old script did, and it uses the mkdir -p option so it creates any parent directories it needs:
Code:
adb shell "mkdir -p /data/local/tmp"
adb push tools /data/local/tmp
adb shell "chmod 0755 /data/local/tmp/mempodroid"
And it does a better job by waiting longer for the tablet to reboot:
Code:
rem Wait reboot tablet
for /L %%i in (1,1,7000000) do @rem
I even modify the getroot.sh script just to change back to the old su command and modify its permissions:
Code:
cd /data/local/tmp
echo >/data/local.prop
toolbox mount -o remount, rw /system/
cat su >/system/bin/su
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
sync ; sync ; sync
reboot
Good Luck...
@android:/ $ export PATH=/data/local/bin:$PATH
@android:/ $ cd mnt/sdcard/ubuntu
@android:/mnt/sdcard/ubuntu $ su
@android:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
Error: Image file not found!(mnt/sdcard/ubuntu/ubuntu.img)
1|@android:/mnt/sdcard/ubuntu #
this is my error. i've tried many things, any suggestions?
the image file is there, and ive downloaded it again, checked permissions, it is the large image from the complete linux installer app.
now i did some other things, and have gotten the responce:
$ export PATH=/data/local/bin:$PATH
$ cd mnt/sdcard/ubuntu
$ su
Segmentation fault
$ sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
sh: can't open /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
$
i re- rooted my device and am now coming up with the original error message again.
so, i added a \ to before mnt and now it says:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cd /mnt/sdcard/Ubuntu
[email protected]:/mnt/sdcard/Ubuntu $ su
[email protected]:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/Ubuntu/ubuntu.img
Validating image checksum... /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh: line 74: /data/data/com.zpwebsites.linuxonandroid/files/busybox: Permission denied
FAILED!
Error: Checksum failed! The image is corrupted!
1|[email protected]:/mnt/sdcard/ubuntu #
so im going to download and add the large ubuntu file to the directory
same error: "dirname : not found"
I have the same error, "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found"
freewalk said:
I have the same error, "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found"
Click to expand...
Click to collapse
Use root explorer or es file explorer to check if
the folder exists. Also, running sh script should be written like this: sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
ireakhavok said:
@android:/ $ export PATH=/data/local/bin:$PATH
@android:/ $ cd mnt/sdcard/ubuntu
@android:/mnt/sdcard/ubuntu $ su
@android:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
Error: Image file not found!(mnt/sdcard/ubuntu/ubuntu.img)
1|@android:/mnt/sdcard/ubuntu #
this is my error. i've tried many things, any suggestions?
the image file is there, and ive downloaded it again, checked permissions, it is the large image from the complete linux installer app.
now i did some other things, and have gotten the responce:
$ export PATH=/data/local/bin:$PATH
$ cd mnt/sdcard/ubuntu
$ su
Segmentation fault
$ sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
sh: can't open /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
$
i re- rooted my device and am now coming up with the original error message again.
so, i added a \ to before mnt and now it says:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cd /mnt/sdcard/Ubuntu
[email protected]:/mnt/sdcard/Ubuntu $ su
[email protected]:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/Ubuntu/ubuntu.img
Validating image checksum... /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh: line 74: /data/data/com.zpwebsites.linuxonandroid/files/busybox: Permission denied
FAILED!
Error: Checksum failed! The image is corrupted!
1|[email protected]:/mnt/sdcard/ubuntu #
so im going to download and add the large ubuntu file to the directory
Click to expand...
Click to collapse
" $ su
Segmentation fault" This error prevents you from having real superuser. Try to reinstall the ROM without wiping data.
" Error: Image file not found!(mnt/sdcard/ubuntu/ubuntu.img)"
Make sure that the image really is there with root explorer or es file explorer.
" line 74: /data/data/com.zpwebsites.linuxonandroid/files/busybox: Permission denied"
It seems that the script is trying to use its own busybox. That is all I know from this issue.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Use root explorer or es file explorer to check if
the folder exists. Also, running sh script should be written like this: sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
The folder and the script exist, "…linuxonandroid/files/bootscript.sh". I have installed the app, "Complete Linux Installer", to my Galaxy Tab 10.1 (P7500). I have rooted my Galaxy Tab ("TAB"). The app also confirms that the path contains the target image (i.e. /mnt/sdcard/ubuntu/ubuntu.img).
However, when the app runs the bootscrip, there is an error message "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found". The code line is at below.
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Could you please kindly let me know what goes wrong? Thanks in advance.
freewalk said:
The folder and the script exist, "…linuxonandroid/files/bootscript.sh". I have installed the app, "Complete Linux Installer", to my Galaxy Tab 10.1 (P7500). I have rooted my Galaxy Tab ("TAB"). The app also confirms that the path contains the target image (i.e. /mnt/sdcard/ubuntu/ubuntu.img).
However, when the app runs the bootscrip, there is an error message "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found". The code line is at below.
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Could you please kindly let me know what goes wrong? Thanks in advance.
Click to expand...
Click to collapse
I can't test it in my tablet, because I'm not home. But when I get there I will test the app myself. You could try using the native Ubuntu from development section. Its kernel can dual boot ICS test 4.0.4.
Edit: worked for me. Here is the log
http://snipurl.com/24sad15
Remember that /mnt/sdcard is externalsd and /sdcard/ is internal memory.
Delete everything you downloaded and the app. Then redo everything, following the guide perfectly.
Sent from my GT-I9100 using xda app-developers app
Thanks and How to try native Ubuntu in Galaxy Tab?
julle131 said:
I can't test it in my tablet, because I'm not home. But when I get there I will test the app myself. You could try using the native Ubuntu from development section. Its kernel can dual boot ICS test 4.0.4.
Edit: worked for me. Here is the log
snipurl.com/24sad15
Remember that /mnt/sdcard is externalsd and /sdcard/ is internal memory.
Delete everything you downloaded and the app. Then redo everything, following the guide perfectly.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot. I shall try again.
One more thing. How to try the native Ubuntu?
freewalk said:
Thanks a lot. I shall try again.
One more thing. How to try the native Ubuntu?
Click to expand...
Click to collapse
Its like installing a custom ROM. There is a topic for it in development section. You put archos.ext4 to /data/local (or was it /mnt/storage? Just read from the topic.) Then flash kernel from the same topic. To return just flash stock ROM and reinstall custom ROM. It doesn't affect to sde.
Sent from my GT-I9100 using xda app-developers app
freewalk said:
The folder and the script exist, "…linuxonandroid/files/bootscript.sh". I have installed the app, "Complete Linux Installer", to my Galaxy Tab 10.1 (P7500). I have rooted my Galaxy Tab ("TAB"). The app also confirms that the path contains the target image (i.e. /mnt/sdcard/ubuntu/ubuntu.img).
However, when the app runs the bootscrip, there is an error message "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found". The code line is at below.
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Could you please kindly let me know what goes wrong? Thanks in advance.
Click to expand...
Click to collapse
I have the same issue, indeed that the 'dirname' can not be found.
the $PATH show the following 2 dirs '/system/bin:/system/xbin' and none of them contain 'dirname'.
might it be because I have rooted my galaxy note 2 N8000 with the stock image according method 1 on rootgalaxynote.com ?
rootgalaxynote.com galaxy-note-10-1-root/how-to-root-galaxy-note-10-1/
any help would be appreciated....
freewalk said:
"/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found".
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Click to expand...
Click to collapse
C'mon folks, It's all there for you in the error message!
It breaks down like this ; dirname is a program the tells you the directory name of an executable file location, well in reality it probably just trims the value pass in looking the last / the print everything before that i.e calling
Code:
dirname /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
will give an out put of
Code:
/data/data/com.zpwebsites.linuxonandroid/files
this is normally part of busybox. Is suspect however that whatever busybox binary it's attempting to use does has not been configured to include dirname or at the very least the symlink hasn't been created so it would need to be called with a busybox prefix , i.e
Code:
export imgfile=$([B]busybox dirname[/B] $0)/ubuntu.img
or just save the f*****g about and hardcore imgfile to the path of the image file, for example
Code:
export imgfile=/mnt/sdcard/ubuntu/ubuntu.img
or wherever you're ubuntu.img is located, should be that simple, If you run into further trouble post the full content of the /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh shell script. I suppose someone could tell the dev to add some sanity checking to his scripts if alot of people are running into this problem!
metacm said:
I have the same issue, indeed that the 'dirname' can not be found.
the $PATH show the following 2 dirs '/system/bin:/system/xbin' and none of them contain 'dirname'.
might it be because I have rooted my galaxy note 2 N8000 with the stock image according method 1 on rootgalaxynote.com ?
rootgalaxynote.com galaxy-note-10-1-root/how-to-root-galaxy-note-10-1/
any help would be appreciated....
Click to expand...
Click to collapse
already found the issue, busybox installation went wrong.... 'Busybox Installer' app didn't worked out, but luckly 'BusyBox free' did the work.
which version of busybox is installed
metacm said:
already found the issue, busybox installation went wrong.... 'Busybox Installer' app didn't worked out, but luckly 'BusyBox free' did the work.
Click to expand...
Click to collapse
can you tell which version of busybox is installed
same error
Hi all,
Sorry for my poor language...
I have same all of you dirname issue, bootscript.sh is in the path (tested with root explorer).
Can somebody tell me what is exactly this error "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found".
Because we can understand 2 thinks :
1-dirname not found bootscript.
2-Busybox not found dirname.
Thank for your help.