Related
It has taken me almost 4 Days (Since Sunday at 1pm Central Time to now) to download and install Linux on my ASUS Transformer TF101 running AOKP Build 33 using Linux Installer from Google Play... AND IT IS STILL NOT DONE!!!! It is at package number 50,280 of Debian Testing. I don't want to press the Home or Back button cause that might screw up my device... And I can't cancel cause the button disappeared... I tried to email the maker of the app to ask them if this was normal or if I could do anything about it and haven't got a reply back...
Can anybody help me?
It is probably your internet connection.
Just download it to your computer and transfer it as per this thread
http://forum.xda-developers.com/showthread.php?t=1449678&highlight=linux+installer
mrevankyle said:
It is probably your internet connection.
Just download it to your computer and transfer it as per this thread
http://forum.xda-developers.com/showthread.php?t=1449678&highlight=linux+installer
Click to expand...
Click to collapse
One, It has been done downloaded cause my WiFi has been turned off for 3 of the now 5 days.
Two, I am not using that app, I am using https://play.google.com/store/apps/details?id=com.galoula.LinuxInstall
Three, It says it is Verifying Packages and it is at 70,000 something.
EDIT: Okay I canceled using that app and am now using the one you suggested...
However I get a bunch of errors
Kinda like this:
/ $ su
~ # cd sdcard/ubuntu
/mnt/sdcard/ubuntu # sh ubuntu.sh
mkdir failed for /data/local/mnt, File exists
Loop device exists
mount: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
mount: mounting /sdcard/external_sd on /data/local/mnt/external_sd failed: No such file or directory
net.ipv4.ip_forward = 1
ubuntu.sh: line 31: can't create /data/local/mnt/etc/resolv.conf: nonexistent directory
ubuntu.sh: line 32: can't create /data/local/mnt/etc/resolv.conf: nonexistent directory
ubuntu.sh: line 33: can't create /data/local/mnt/etc/hosts: nonexistent directory
Ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
chroot: can't execute '/root/init.sh': No such file or directory
Shutting down Ubuntu ARM
failed.
failed.
failed.
failed.
failed.
failed.
/mnt/sdcard/ubuntu #
Not exactly the same but I also get an extra one saying loop255 not found and I looked and all my stuff in my dev folder has the year 2012 in front of it. So loop255 says "2012 loop255" making the script not work.
Edit 2: Here is correct output from terminal, I am on AOKP build 33.
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # cd /sdcard/ubuntu
[email protected]:/sdcard/ubuntu # sh ubuntu.sh
Loop device exists
mount: mounting /sdcard on /data/local/mnt/sdcard failed: I/O error
mount: mounting /Removable/MicroSD on /data/local/mnt/external_sd failed: I/O error
net.ipv4.ip_forward = 1
ubuntu.sh[58]: cannot create /data/local/mnt/etc/resolv.conf: Not a directory
ubuntu.sh[59]: cannot create /data/local/mnt/etc/resolv.conf: Not a directory
ubuntu.sh[60]: cannot create /data/local/mnt/etc/hosts: Not a directory
Ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
chroot: can't execute '/root/init.sh': Not a directory
Shutting down Ubuntu ARM
failed: I/O error
failed: I/O error
losetup: /dev/block/loop255: No such device or address
1|[email protected]:/sdcard/ubuntu #
Any update on the issue with the never ending "validating packages"?
I have the same issue. Was running it for the whole day until it reached 7000, then I canceled and tried again.
The weird fing is, when i tried it the first time, it worked very wuickly and without any issues. But as I had a far too small 500MB image, I tried it again. But since that, no success.
Is it possible that there are some old data kept somewhere?
Is it possible to do a clean start?
I tried already the "reset config" function.
Neverending Validating Packages, No Network Required same as previous poster...
gruinelli said:
Any update on the issue with the never ending "validating packages"?
I have the same issue. Was running it for the whole day until it reached 7000, then I canceled and tried again.
The weird fing is, when i tried it the first time, it worked very wuickly and without any issues. But as I had a far too small 500MB image, I tried it again. But since that, no success.
Is it possible that there are some old data kept somewhere?
Is it possible to do a clean start?
I tried already the "reset config" function.
Click to expand...
Click to collapse
I am having the same issue, I also have a Transformer TF-101
I had issues with the "other" Complete Linux Installer that resulted in I/O errors that I've read about being a problem on Transformer tablets or possibly NVidia Tegra tablets
I am using Linux Installer STD or "Galoula" linux installer
I e-mailed a note to [email protected] but it was kind of wordy and didn't include any attachments, don't know if I will get a reply
I did not mention to them that it was a TF-101
I will probably try debootstrap for myself in a while. I think they've put out a ****load of documentation and I can probably learn more from that documentation than I could by just running the app and installing...
Anyway, I too am not convinced that it's doing anything, I waited for 7000 last night and gave up.
Here is a screenshot of the last status report before I cancelled this time.
This is a really useful looking tool, that could save me a lot of time, but with ext2 filesystem I'm not sure how useful it would be...
Does anyone know how to get mkfs.ext4 on a transformer? It has kernel support, all of the existing filesystems are ext4. But no mkfs.ext3 or mkfs.ext4 seems to be available or on the disk already. I am thinking about preparing my loop file on another machine with some instructions from the wiki instead. It's just debootstrap... I already know how to use debootstrap. Hopefully this tool will recognize the installed system and prompt me to update my linuxchroot script, if it does that it would still be worthwhile to use.
--Kingdon
lol @ waiting 4 days, I'd have cancelled after 40 minutes
dotmaniac said:
It has taken me almost 4 Days (Since Sunday at 1pm Central Time to now) to download and install Linux on my ASUS Transformer TF101 running AOKP Build 33 using Linux Installer from Google Play... AND IT IS STILL NOT DONE!!!! It is at package number 50,280 of Debian Testing. I don't want to press the Home or Back button cause that might screw up my device... And I can't cancel cause the button disappeared... I tried to email the maker of the app to ask them if this was normal or if I could do anything about it and haven't got a reply back...
Can anybody help me?
Click to expand...
Click to collapse
4 days? Damn that's a long time. I could have flashed 4 nightlies. It took me 20 minutes on a low wifi connection with the epic 4g
treat ur girl like how u treat ur epic
I have the feeling it could have to do something with the /etc/hosts file
i blanked mine out (came prefilled by rom dev) and used AdFree
now it does not stuck at "validating", now its stuck at "resolving dependencies"
finaFub every
fixed in latest release
EXPLOIT NO LONGER WORKING DUE TO OTA UPDATE. BE WARNED.
Thanks to beaups for his exploit!
Download the zip file below, unzip it somewhere, run root.bat with your phone plugged in and usb debugging enabled. Currently this is for windows only.
Includes a fully working su binary and Superuser.apk, make sure to update the su binary the first time you run SuperSu!
Follow the instructions on the screen, they are very simple, only one thing to do!
Download:
http://www.gigashare.in/738af
HELP SECTION:
After you are rooted, I strongly suggest you unlock your bootloader immediately!!
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Make sure Wifi is enabled and connected! (seems to help, but not required)
If you are stuck at "waiting for device to reboot" for a long time or you get "/data/local.prop was not created, exit the script, try again." followed by lots of junk, reboot your phone and push your clock forward two days, reboot, and try again.
If the update fails to check for updates, reboot your phone and push your clock forward two days, reboot, and try again.
usb drivers, if you need them: http://binary100100.googlecode.com/files/HTCDriver3.0.0.007.exe
You're the man and you know this...
Sent from my HTC One X using Tapatalk 2
Damn. I'm already rooted yet disappointed I can't be part of this . Lol well Friday I will be donating like I said I would. Good job
Sent from my HTC One X using xda premium
Great work! Wonder how long this will last.
Sent from my HTC One X using xda premium
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Pumpiron579 said:
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Click to expand...
Click to collapse
should only reboot twice
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
StrykerGT said:
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
Click to expand...
Click to collapse
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
designgears said:
should only reboot twice
Click to expand...
Click to collapse
Is that taking into account the unstableness and the potential for it to spontaneously reboot on its own?
Mine doesn't get past "waiting for device to reboot"
Thanks for the script sir!
skatin707 said:
Mine doesn't get past "waiting for device to reboot"
Click to expand...
Click to collapse
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
designgears said:
should only reboot twice
Click to expand...
Click to collapse
mine rebooted once after checking for update, but when it ran all the code, prior to rebooting, i got errors in the code. looked and no SU on my phone. not sure what i did wrong. didn't reboot the first time, so i pushed the date ahead two days and then it did with the code that everyone is reporting.
designgears said:
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
Click to expand...
Click to collapse
I'll keep waiting, it hasn't even been 10 minutes.
hahaha...that was magical!!!! works!!!!
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
did you run the updater on the phone? if it is completed or still spinning after a few min just reboot and try again.
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
I set my date ahead and turned on my WiFi, checked for updates and it rebooted right away.
love you guys.
designgears said:
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
Click to expand...
Click to collapse
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
beppomarx said:
heres what i get... i did get the reboot after checking for updates though.
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
32 KB/s (334 bytes in 0.010s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse
reboot and try again! push your clock up two days.
StrykerGT said:
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
Click to expand...
Click to collapse
YUP! but there is a one click for that too
I'm trying to root my SE WT19i, but it's being impossible. I´ll tell you all what I've tried so anyone can see any solution:
I followed this thread for downgrading from andoid 4.0 to 2.3. First, flashed the phone with the 4.0.2.A.0.62 version.
Then, for installing adb drivers, tried installing PC Companion, but it wasn't able to install any driver. So, I searched and installed the drivers this way (installing the “Google USB Driver” package).
Then, following the first thread, downloaded the DooMLoRD's Easy Rooting Toolkit [v4.0] , and followed the instructions (USB debugging, unknown sources, even the 10 minutes screen timeout). Don't worked.
So, I flashed again the phone, with the 4.0.2.A.0.42, and tried one more time (and changed the options again according to the script's instructions). Don't worked.
Same for 4.0.2.A.0.58, that is the version that runs my phone now.
Then, I tried this method, by using the Super One Click. That program prompted me to install drivers, so I installed all I was prompted, but don't worked any exploit method of it (yeah, I know the other method "maybe won't work in Android 2.3 and higher", but I had to try).
As there were new drivers installed, I thought the DoomLord's script now, finally, will be able to work, so I tried again. Well, the console output is this (and it is generated in a few seconds...)
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2262 KB/s (1075144 bytes in 0.464s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
53 KB/s (439 bytes in 0.008s)
--- Free space on /system : 172928 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Well... the "files\zergRush" actually exists. I haven't modified anything in the files more than unzipping them. I don't know why don't recognise it, but because of that, I downloaded directly the zergRush script and replace it, but didn't worked either even when the DoomLord's script found it. I've also tried to unzipping it directly in C:\, but the results are the same.
I'm using Windows 7, but have tried to run in compatibility mode with xp sp3, and with admin permissions without results.
I don't know what more to do, I think I've tried all. Can anyone help?
PS: I was going to post this in the thread of DoomLord's script (that is the correct place for this, I think), but I'm not allowed yet, sorry.
Accordingly to the rules, bumping thread so it can be seen by anyone who could know about it.
I'm currently trying to contact someone in the IRC, but it'is a bit dead... :-/
install stock rom again and try again
That's already done. Several times. Now, I think the problem is more of the computer for not founding the zergRush script than of the phone. I need a way for getting the script working, but don't know how to...
--------------------------------------------------------------------------------------
Edit: I give up. I can't have my phone useless for more time (because is stupid reconfigure it each time you flash it...). I'm interested no more in rooting the phone. Thanks to all who have read this thread.
Hope I am putting this in the correct section, but I am looking for some technical help.
I am running the latest global stable rom (8.2.2.0), have the bootloader unlocked and it is rooted.
What I am trying to do is write to the file:
/sys/class/android_usb/android0/f_mass_storage/lun/file
but when I try to echo into the file, I get error 1. Running that through toybox or busybox gives a better error of permission denied. I changed the permissions to 777 on the file (to open it up completely) and same thing. I tried changing the owner of the file to root:root and that was successful, but still couldn't write to that file.
My goal is to re-enable mass storage via a shell script, but writing to that file is part of the process. Any thoughts as I am currently stumped. My best guess is that I need to modify the file /init.usb.rc but that requires making a custom kernel and ROM which is currently beyond my abilities.
So, quick update on this... was reading online that I'd need to remove the immutable flag on the file but it seems that file doesn't support chattr or lsattr.
The whole folder path doesn't support lsattr or chattr. Tried from recovery and same thing.
Still thinking about this but I am getting more and more stumped. Any developers or linux experts have any thoughts?
lsattr and chattr both throw the error "not a typewriter". Was thinking that maybe my busybox is out of date... going to try updating it and see if that helps.
Update 2 - updating busybox changed the "not a typewriter" error to an invalid ioctl error.
So, from what I can tell, this basically means that lsattr and chattr don't work on the sysfs file system type. And since the file doesn't allow you to add anything to it, mass storage on this phone (with the global stable ROM) is not possible.
I need to run a binary file, dalvikvm which located in /system/bin from TWRP terminal, but no matter what, it says, "No such file or directory found", and then I found that this is link file located another directory, I cd'd there and tried, but still the same result
I can be able to run the same file in Termux without any issues
Can anybody please help me on this?
Thanks
Hi, I think you need to mount the system partition before being able to access it. It's not mounted by default on TWRP, but when the phone is on it is (otherwise Android wouldn't work)
If you need help on how to mount partitions on TWRP, ring me (or google it, it's actually pretty simple)
Raiz said:
Hi, I think you need to mount the system partition before being able to access it. It's not mounted by default on TWRP, but when the phone is on it is (otherwise Android wouldn't work)
If you need help on how to mount partitions on TWRP, ring me (or google it, it's actually pretty simple)
Click to expand...
Click to collapse
Thanks for replying, it wasn't mounted at first, so I had mounted, still it didn't work, while some of the files in bin do work, some don't.
Then I copied the file to /sdcard and /tmp, and tried execute from these folders, still
Well, if when you're free, can you confirm if it's running on yours?
File: /system/bin/dalvikvm
Thanks once again
mizzunet said:
Thanks for replying, it wasn't mounted at first, so I had mounted, still it didn't work,
...
Thanks once again
Click to expand...
Click to collapse
I didn't found it inside, but it may be because I'm not rooted.
While searching around I've found this :
No such file or directory while running dalvikvm
I built AOSP Android and push the dalvik virtual machine in my device just to see if my built dalvik vm runs properly. I pushed it my device /opt directory but when I run dalvikvm, I get the error...
stackoverflow.com
It might get you out of trouble
Raiz said:
I didn't found it inside, but it may be because I'm not rooted.
While searching around I've found this :
No such file or directory while running dalvikvm
I built AOSP Android and push the dalvik virtual machine in my device just to see if my built dalvik vm runs properly. I pushed it my device /opt directory but when I run dalvikvm, I get the error...
stackoverflow.com
It might get you out of trouble
Click to expand...
Click to collapse
I looked into it.
I had no opt folder in root directory. So I made one, and moved dalvikvm to there and tried execute this time, it said permission denied, so I gave it chmod 755. But after that, it says "there no such file or directory".
Well, do you telegram account, so I could contact you there.
Thanks
Raiz said:
I didn't found it inside, but it may be because I'm not rooted.
While searching around I've found this :
No such file or directory while running dalvikvm
I built AOSP Android and push the dalvik virtual machine in my device just to see if my built dalvik vm runs properly. I pushed it my device /opt directory but when I run dalvikvm, I get the error...
stackoverflow.com
It might get you out of trouble
Click to expand...
Click to collapse
And even "file" binary, it says, there no file.
mizzunet said:
I looked into it.
I had no opt folder in root directory. So I made one, and moved dalvikvm to there and tried execute this time, it said permission denied, so I gave it chmod 755. But after that, it says "there no such file or directory".
Well, do you telegram account, so I could contact you there.
Thanks
Click to expand...
Click to collapse
This is really curious, tbh I'm not an expert around that subject, idk what's wrong with this binary...
Hopefully someone who knows more may help you with that. Have a nice day
This is because the binary you are trying to execute was compiled to run in the Android context, but you're trying to execute it in the TWRP one. Each binary has a path to a linker used during execution. The problem is that it refers to a linker that doesn't exist in TWRP.
Suppose we want to execte a binary file and obviously we can't:
Bash:
x00h:/ # /system/bin/awk
/sbin/sh: /system/bin/awk: No such file or directory
Let's take a look to its linker:
Bash:
x00h:/ # strings /system/bin/awk | head -n 1
/system/bin/linker64
Then, you will actually discover that it's sym linked to a linker that is available only when Android is running:
Bash:
x00h:/ # ls -ald /system/bin/linker64
lrwxr-xr-x 1 root shell 38 2009-01-01 00:00 /system/bin/linker64 -> /apex/com.android.runtime/bin/linker64
Since TWRP comes with its linker in /sbin/linker64, we can sym link it to /system/bin/linker64.
So, the hack:
Bash:
x00h:/ # mkdir -p /apex/com.android.runtime/bin/
x00h:/ # ln -s /sbin/linker /apex/com.android.runtime/bin/linker
x00h:/ # ln -s /sbin/linker64 /apex/com.android.runtime/bin/linker64
Retry, and it works:
Bash:
x00h:/ # /system/bin/awk
usage: /system/bin/awk [-F fs] [-v var=value] [-f progfile | 'prog'] [file ...]
Pray to God the TWRP's linker will be compatible and do the job (most binaries works fine), but sometimes you may get CANNOT LINK EXECUTABLE.