Related
So, I've had this rooted G1 for a long time. It was running Flan, and quite well, today, i kept getting errors, so I rebooted, after reboot, it would not go past the first bootscreen, I can still access recovery mode, but I have no idea what is going on, I tried to reflash Flan, and I kept getting error in sector E, or something like that, anyone know what's up?
I think I had a similar problem. It just died on me randomly and immediately started to reboot. It got stuck on the bootscreen (mine was the second I believe; the one after Tmobile G1). I did an alt+w wipe and rebooted. It took a long time, but just be patient and see if it will boot.
Didn't boot, I unrooted, and it booted, but now I'm stuck at the activation screen, Win 7, will not get the damn driver right, and Mint doesn't know what ADB is, even thought I installed correctly, or so I think, It's been so long since I've used ADB.
Since Mint is just ubuntu in a nice frock, follow this to get adb talking to your phone:
wddglr said:
You will now set up your bashrc file and UDEV to recognize your HTC Device.
!!START -------------------------------------- ADB + FASTBOOT --------------------------------------
The Android Debug Bridge (adb) is one of the tools that will help you the most when you run into flashing problems or running shell commands directly from your machine. UDEV will not recognize your G1 out of the box, but we will configure it with some rules so it can connect.
We will work with /AndroidSDK as the location of your sdk. If this is not your setup, I think you're smart enough to figure it out.
Editing .bashrc file to use tools from /AndroidSDK/tools/ directory -
Go to your home folder.Example: /home/wddglr/
Press Control + H to view hidden files.
Look for your .bashrc file and double click to open it with gedit.
Add the following lines to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools
IMPORTANT NOTE
Setting up UDEV to recognize HTC Device -
Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click save and close.
To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
Setting up fastboot -
Download this fastboot binary from http://android-dls.com.130.4 KB [http://android-dls.com/files/linux/fastboot]
Once downloaded to your desktop, right click and select Properties.
Navigate to the Permissions tab and configure the following option:Execute: [√] Allow executing file as program
Click Close.
Move the fastboot bianary to your /AndroidSDK/tools/ directory.
Reboot.
-------------------------------------- ADB + FASTBOOT -------------------------------------- END!!
Click to expand...
Click to collapse
I got it working, I forgot to do the root exploit thing, anyways, I installed the Danger SPL, newest radio, Cyan works, all of the 2.1+ builds don't, they just stay at the first boot screen, I even left one going over night, never got past the first boot screen, I'm annoyed as hell with this. Could it be something to do with the newest radio? The one after 26I?
Just womdering?
did yyou have your sdcard patitioned? If so you may want to wipe your ext partition and also repair your ext partition and then reflash a flan rom?
That's what I thought, because I had a second SD card, just Fat32, and it booted after a reroot, so I formatted the whole SD, but now I'm scared of using anything but Cyan.
Ok, new issue, I tried putting SuperEclair V8 on the G1, and I get this error:
E:Can't symlink /system/xbin/bb/
[
E:Failure at line 61:
symlink /system/xbin/busybox SYS
TEM:xbin/bb/[
Installation Aborted
So what's the issue with this, gives me that error after a complete reroot, and multiple wipes.
Godfrd824 said:
Ok, new issue, I tried putting SuperEclair V8 on the G1, and I get this error:
E:Can't symlink /system/xbin/bb/
[
E:Failure at line 61:
symlink /system/xbin/busybox SYS
TEM:xbin/bb/[
Installation Aborted
So what's the issue with this, gives me that error after a complete reroot, and multiple wipes.
Click to expand...
Click to collapse
I am having the same exact issue with the same exact rom, if anyone can help it would be much appreciated
thanks
nate
I had my system running fine building cm7 for encore, and ezgingerbread for g1 no problem. Then the problem with kernel.org came up. For some dumb reason I decided to run this command from android/system/ rm -rf `ls -a | grep -v "^\." ` That command comes from the ezgingerbread compile instructions and is said to clear the build tree. I've used it for ezgb before without problems. However after running it from android/system/ there is nothing left in the directory. I tried to go thru the settup to compile instructions from the beginging. Nothing happens when i try to repo sync or do anything associated with command repo. Please help. thanx!!!
Okay this little package has been the bane of my resoning with g++ and build essentials I found the fix for it as I was playing with 2.3.6 webtop and trying to fix synaptic getting stuck at preparing packages, still looking into it but this needs to get out there.
Okay problem:
libc6-dev cant install due to needing to overwrite package in rootfs
simple fix when you run into this download this and this
and from the terminal run:
sudo dpkg -i --root=/osh --force-all libc6-dev_2.9-4ubuntu6_armel.deb linux-libc-dev_2.6.28-19.66_armel.deb
and resume your stuck install:
sudo apt-get -f install
update: noted a linux-libc complaint from dpkg on my latest webtop setup, updated instructions accordingly.
This seems interesting. Does force install the package break dependencies?
Hi, i try but the error not gone... can you help me?
when i run sudo apt-get -f install the result is:
18 upgraded, 100 newly installed, 21 to remove and 107 not upgraded.
2 not fully installed or removed.
Need to get 0B/43.7MB of archives.
After this operation, 80.0MB of additional disk space will be used.
Do you want to continue [Y/n]? y
E: Internal Error, Could not perform immediate configuration (1) on libc6
The same error is present in every instalation and i cant install nothing
tks
I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
No one can help me?
eclaro said:
I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
Click to expand...
Click to collapse
Please, any help?
hello guys sorry for my english, but at the time is possibile to have kali linux on android 4.4.2 of galaxy s5??? i try a lot of guide but nothing, thanks
Yes there is a way. I am running Kali Linux on my Galaxy s5 now!!
Download linux deploy and install Kali linux from there.
GL!
la2o said:
Yes there is a way. I am running Kali Linux on my Galaxy s5 now!!
Download linux deploy and install Kali linux from there.
GL!
Click to expand...
Click to collapse
i've already tried but nothing , maybe can you send me a pvt message with a little guide for the installation?? p.s. i have a sdcard of 8 gb
I tried Linux on Android but it gives invalid argument mounting the loop device. Linux Deploy has an option to not use a loop device and install to a folder I think. Not positive. Try Advanced Linux Installer. That might work. It costs but it's way better than the free version. Try Standard Linux Installer first if you like.
Could you please add some note on how you managed to install?
I am trying with several options, but always get stuck on a "dd: permission denied" creating the volume
Z
I'll try to provide that info. What you're seeing likely means where it's trying to write isn't allowed. Try changing the install location to somewhere safe like /data/kali or something. Also I just found out the S5 won't do ext2 so if you're trying to do a loop device use ext4 if possible. Sorry I don't have more info at the moment.
I am having the same issue. What SU app are you using? I am using SuperSU, I read that SuperSU might be the problem but I do not know the conditions on how to switch SU apps. Hopefully we can find a solution.
Just got running.
use a terminal emulator as root
cd /data/data/ru.meefik.linuxdeploy/linux/bin
rm sh chroot
ln -s /system/bin/mksh sh
ln -s /system/xbin/busybox chroot
make sure your file location is on your sd card
change image size to appropriate size.
also change to ext4 file system
DipSprayArc said:
Just got running.
use a terminal emulator as root
cd /data/data/ru.meefik.linuxdeploy/linux/bin
rm sh chroot
ln -s /system/bin/mksh sh
ln -s /system/xbin/busybox chroot
make sure your file location is on your sd card
change image size to appropriate size.
also change to ext4 file system
Click to expand...
Click to collapse
Can you explain this deeper? I typed that in an emulater but no luck
DipSprayArc said:
Just got running.
use a terminal emulator as root
cd /data/data/ru.meefik.linuxdeploy/linux/bin
rm sh chroot
ln -s /system/bin/mksh sh
ln -s /system/xbin/busybox chroot
make sure your file location is on your sd card
change image size to appropriate size.
also change to ext4 file system
Click to expand...
Click to collapse
Also here are screen shots of my errors, settings, and anything else I figured might be useful to you. Thanks for help in advance.
I think it's long overdue for a Galaxy S4/5 guide. I know tinkering must be done and there are several issues to negotiate. I've found scattered info here and there but nothing definitive. Complete Linux Installer or Linux Deploy. Either/or. The only way I've ever got Linux to work is by installing to a directory and doing a chroot into it and doing a debootstrap.
Please&ty.
Is the stock WiFi radio compatible with packet injection or monitor mode on the S5 that you know of? I never put much effort into the install after I had such as hard time initially, attempting to install it to my extSdCard.
Solution
Hi there, I tried to install the kali distro in a s5 (g900f) with de Linux Deploy v 1.5.5 and I couldnt, i downloaded the 1.4 and neither but with de v 1.3 I could make it!
So if you are having any troubles with the installation, just download a previous version from the project's github (here)
Hope it helps!
su error
[email protected]:~$ su
Password:
su: Authentication failure
[email protected]:~$ sudo -i
sudo: PERM_ROOT: setresuid(0, -1, -1): Permission denied
[email protected]:~$
And now ?
plz help bro