Database Info

[Q&A] How to build/modify your own linux image for eMMC install Debian sample inside

[Q&A] How to build/modify your own linux image for eMMC install Debian sample inside
This thread is for help and support with all linux distributions instalable in eeepad asus transformer. I will explain how to build your own image file or modify existing one in order to use lilstive OLife script.
As ubuntu is the most popular distro, please, all de questions related with ubuntu post them in lilstevie's thread.
You can install any distribution with arm architecture support, but you'll need to make some tweaks in the image in order to work propperly. As my experience in linux is most of it related with debian is the distro i will give the best support, but i'll try to answer every question you ask.
I've chosen debian armHardFloat port instead of debian armel fore many reasons, you can read about this port here:
http : //wiki. debian.org/ArmHardFloatPort
This port is still young so right now there are packages still unaviable to install but they are entering in wheeze day to day. If you preffer to use armel instead or armhf you can always do, you will loose improvement but you will have (at the time of writting this) less packages aviable. In the future (not far away) it will be the best option.
Building your own image:
There are many ways to create a image file but because we are going to need qemu in order to debootstrap the instalation the easiest way to create it is with qemu-img
Code:
qemu-img create debian-armhf.img 400M
I have only given 400M of space because is going to be a minimal instalation without desktop enviroment, it could be smaller but, just in case, that's the size i've chosen. The transfer with OLife it will be faster if the image is smaller.
When you boot for your first time you will find an error because there is no valid MSDOS partition table, this is ok, nothing happens because of that but if you want to avoid it use fdisk to create a partition table
Code:
fdisk debian-armhf.img
we need now to give format to the filesistem:
Code:
mkfs.ext4 debian-armhf.img
It will ask if you really want to do because it's not an ordinary partition and you have to type "s" to proceed
Now whe have ready the image and we have to mount it in some folder to install debian in it:
Code:
mount -o loop debian-armhf.img debian
asuming debian as the created folder for that.
We are ready to debootstrap de instalation:
Code:
debootstrap --verbose --arch armhf --foreign --include=btrfs-tools,locales,kbd,wpasupplicant wheezy debian http://ftp.de.debian.org/debian
this will make the first step to install wheezy armhf, --foreing parameter is because the target architecture is different from the host one and it's going to stop before de second-stage, it will include the packages btrfs-tools locales and kbd, you can add as many as you want but it will be always faster if you install them manually once installed in the transformer. I didn't install ssh server because i have a dock, but if you don't have it will be needed to complete the instalation with a remote shell, but you can also install packages later with chroot after the second stage.
In order to be able to chroot we will need qemu-user-static, with armhf it's needed 1.0 version with armel it's not necesary, it can be any version not too old. Also if you have an i386 system it's recomendable to install an amd64 kernel to do chroot or debootstrap will fail configuring cron. Actually i think in this sample image there is anacron instead of cron because there was an issue i thought it was related with that but later twb found out the problem was another different and now it's solved.
we will add qemu-arm-static to the instalation to be able to chroot
Code:
cp /usr/bin/qemu-arm-static debian/usr/bin/
we chroot to the new enviroment:
Code:
chroot debian
and execute the second stage of debootstrap:
Code:
./debootstrap/debootstrap --second-stage
After finish the instalation we will set the root password
Code:
passwd
and now it's ready, you can make tweaks, install packages (as ssh if you need it) or whatever you want, but you will have to add a repository to /etc/apt/sources.list in order to install any packages.
In this image and debootstrap proccess i've used german repositories because are the fastest for me, but you can use another one, right now it's neede also experimental repository to have working touch screen, but as soon xserver-xorg-input-evdev with full multitouch support enters sid as it won't be necesary
example of /etc/apt/sources.list
Code:
http://ftp.de.debian.org/debian unstable main contrib non-free
http://ftp.de.debian.org/debian experimental main contrib non-free
I have already installed in this image necesary packages for that and experimental repositories won't interfiere unless you pass the parameter for apt-file so you can forget about this if you want, but if you are building your own image apt-get install -t experimental xserver-xorg will do the work.
we have ready now our image but it need some files and tweaks to make everithing work in the eepad.
From here you can apply this to any arm image you want to test.
(all the files needed are in the attached file files.tar.gz in the rigth folders)
we need to add modules and firmware, i've extracted them from lilstive ubuntu.img
strictly necesary are:
Code:
/lib/firmware/nvram.txt
/lib/firmware/brcm/*
but you may need another ones if you are going to use external hardware, that's on you.
there are also two folder in /lib/modules one is for the asus kernel and the other one for chrome os kernel, i suggest to add both of them because it's just a bit space and you will be able to use the image with both kernels.
In order to make wifi work i've made /etc/modprobe.d/options.conf file with some parameters found in one of the threads of lilstevie and /etc/modules with the modules to load.
You will also need to configure /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf all this files are in the attached files.tar.gz but wpa_supplicant.conf is not because it depends of each ones wifi, but there is a wpa_supplicant.conf.example and you can always google for it a bit. If you don't have a dock make sure you do this correctly or you won't be able to connect to the internet and ssh device to continue instalation easily
if you want to be able to use adb (wich is really usefull if you for example did not correctly configure wpa_supplicant) you will have tu add also "/usr/bin/adbd" and /etc/init.d/adbd"
I've modify the original init.d script to avid LSB tags missing warning error, it's not really necesary rsyslog as previous service started but ... it works.
In order to make adb service start automatically we will execute (inside the chroot of course)
Code:
update-rc.d /etc/init.d/adb defaults
This may be different in non debian based distributions, but you can always ln manually to rcX.d
Finally, there is the "bug" it has made me think something was wrong and change cron with anacron, when you boot it appears to stop booting starting a service (cron, dbus, deppending what you have installed) but it isn't you can login pressing ctrl + alt + F2 (touchpad key),
we think it's related with the bootloader and default tty as 7 or something like that.
As workaround add in /etc/rc.local "chvt 1" (without quotes) just before exit 0 line
Because there is not oem-installation like in ubuntu after the first boot there are a couple of things to do, we have to resize the image to fit the partition, change password, configure locales and xorg keyboard-layout (if you have more than one locales) add an user and include in relevant groups and maybe more in the future so i've made a postinstalation.sh script included in /usr/bin:
Code:
#!/bin/sh
echo "Making online resize of the root partition"
partition=`mount -l | grep " / " | awk '{print $1}'`
resize2fs $partition
echo "changing root password"
passwd
echo "configure locales"
dpkg-reconfigure locales
echo "configure xserver keyboard layout"
dpkg-reconfigure keyboard-configuration
echo "configure localtime"
dpkg-reconfigure tzdata
echo "Please anter a user name"
read username1
adduser $username1
echo "adding user to relevant groups"
adduser $username1 audio
adduser $username1 video
adduser $username1 netdev
adduser $username1 plugdev
adduser $username1 bluetooth
adduser to bluetooth will fil because there is not installed any bluetooth manager so there is not bluetooth group yet, and remeber tu use OLife script to inject bluetooth firmware in order to have bluetooth working.
And that's it i think i haven't miss anything but i will update this when needed. You can now install your image with lilstevie's OLife script, you will have to rename it to ubuntu.img from now. If everithing went ok you can now install the desktop enviroment you prefer, on screen keyboard or whatever you like.
I haven't test network manager and i've only tested kde-netbook, but there are still broken dependencies and it's a bit slow. This will improve as soon as we have hardware acceleration (if we ever do), and armhf port goes ahead.
Lilstevie is going to host my images and maybe OLife script will have more options in the future, but from now you can download from here:
http://dl.dropbox.com/u/60048492/debian-armhf.img.tar.gz
(md5sum inside)
http://dl.dropbox.com/u/60048492/files.tar.gz
All credits and many thanks for lilstevie and twb for all the help they gave me.
I will apreciate any correction not only in this process but also in my english grammar/ortography

Please, any mod or admin can correct the word modufy in the title?
reserved

Thanks
Following your instructions, I can finally replace ubuntu with debian, which resides my home laptops, office desktop, and now, on my tablet as well. Unfortunately debian has no "onboard" package... and it's rather inconvenient without a dock.
Thanks anyway for bring debian to this tablet.

boseliquid said:
Following your instructions, I can finally replace ubuntu with debian, which resides my home laptops, office desktop, and now, on my tablet as well. Unfortunately debian has no "onboard" package... and it's rather inconvenient without a dock.
Thanks anyway for bring debian to this tablet.
Click to expand...
Click to collapse
What has onboard that haven't other onscreen keyboards? i haven't ever tried onboard and i just tried a couple of onboard keyboards in debian, i also did managed to load it automatically in login screen, But i did never went deeper, like "only appear if the focus is in textbox" or something like that.
Anyway i has to be easy to rebuild that package for debian or just install it from ubuntu. What do you exactly need?

onboard onboard
Onboard has keys that simulate middle-click and right-click of mouse. I tried to install ubuntu's deb file, but runs into problem with dependencies. Compiling the source on the tablet led to error related to gdk/gdk.h which i couldn't figure out how to resolve.
Onboard respond better than others, e.g. xvkbd and florence both have run-away key presses, i.e. a string of letters appear even for a quick single tap on a key.
Also, onboard integrates nicely with lightdm. I used xdm plus florence to log in (the screen keyboard hides most of xdm's GUI).
With fluxbox, debian seems faster than ubuntu+fluxbox on the tablet. That's why onboard is nice since fluxbox menu requires right-clicking on the desktop. Fortunately, fluxbox keys are easily configurable, so i still can shutdown by pressing some key combination.
Hopefully lilstevie has the time to work on hardware acceleration, which would then allows to dump android completely.

boseliquid said:
Onboard has keys that simulate middle-click and right-click of mouse. I tried to install ubuntu's deb file, but runs into problem with dependencies. Compiling the source on the tablet led to error related to gdk/gdk.h which i couldn't figure out how to resolve.
Onboard respond better than others, e.g. xvkbd and florence both have run-away key presses, i.e. a string of letters appear even for a quick single tap on a key.
Also, onboard integrates nicely with lightdm. I used xdm plus florence to log in (the screen keyboard hides most of xdm's GUI).
With fluxbox, debian seems faster than ubuntu+fluxbox on the tablet. That's why onboard is nice since fluxbox menu requires right-clicking on the desktop. Fortunately, fluxbox keys are easily configurable, so i still can shutdown by pressing some key combination.
Hopefully lilstevie has the time to work on hardware acceleration, which would then allows to dump android completely.
Click to expand...
Click to collapse
Ok, i'll give it a look and if i can i will build a debian package in order to include it in the image

I've managed to build a couple of packages for onboard. You can't imagine how much crap it's in building dependencies, mono, unity and so many things, so i've removed appindicator dependency because i don't think it's going to be really necesary. The true is that i don't have so much time right now so,
Can you please test it and tell me if you have any problem? I can try to rebuild another older version in order to avoid unity crap and those things without messing the code, but if this works well it's the eassiest solution.
You have to install both packages, the other dependencies are instalable from debian oficial repository, at least i haven't got any problem installing it in my building environment.
http://dl.dropbox.com/u/60048492/onboard_0.95.1-1_all.deb
http://dl.dropbox.com/u/60048492/python-virtkey_0.60.0-1_armel.deb

arch of python-virtkey is armel instead of armhf
Almost there... but obtained the following error msg:
Unpacking onboard (from onboard_0.95.1-1_all.deb) ...
dpkg: dependency problems prevent configuration of onboard:
onboard depends on python-virtkey (>= 0.60.0); however:
Package python-virtkey is not installed.
onboard depends on python-gconf; however:
Package python-gconf is not installed.
dpkg: error processing onboard (--install):
dependency problems - leaving unconfigured
Thanks again.

boseliquid said:
Almost there... but obtained the following error msg:
Unpacking onboard (from onboard_0.95.1-1_all.deb) ...
dpkg: dependency problems prevent configuration of onboard:
onboard depends on python-virtkey (>= 0.60.0); however:
Package python-virtkey is not installed.
onboard depends on python-gconf; however:
Package python-gconf is not installed.
dpkg: error processing onboard (--install):
dependency problems - leaving unconfigured
Thanks again.
Click to expand...
Click to collapse
python-virtkey is provided in my previous post, just install it, after that
#apt-get install -f
will resolve and install automatically pending dependencies.
I've already tried and it works.
EDIT: i have been working in the suppose you are runnin debian armel and not armhf

To get bluetooth working, you need an armhf build of brcm_patchram_plus.
Thankfully it's GPL'd, so here's a copy.

Hi,
I'm having a bit of trouble getting Debian on my TF101 using OLiFE.
I'm forced to use the android/Ubuntu dual-boot option, but that's another story.
Basically, there's a kernel panic and I can't see the entire screen without it rebooting one second later. I am able to flash my TF101 properly without bricking (it's a B60), but everytime I boot it up as my default OS, I get that rebooting screen.

NothingMuchHereToSay said:
Hi,
I'm having a bit of trouble getting Debian on my TF101 using OLiFE.
I'm forced to use the android/Ubuntu dual-boot option, but that's another story.
Basically, there's a kernel panic and I can't see the entire screen without it rebooting one second later. I am able to flash my TF101 properly without bricking (it's a B60), but everytime I boot it up as my default OS, I get that rebooting screen.
Click to expand...
Click to collapse
Kernel panic kinda implies the problem is with the kernel, not with Debian. If you're using the 3.1 kernel, try the 2.6 one by lilstevie. Whichever kernel you're using, you're better off seeking help in one of the kernel-specific threads.

rdnetto said:
Kernel panic kinda implies the problem is with the kernel, not with Debian. If you're using the 3.1 kernel, try the 2.6 one by lilstevie. Whichever kernel you're using, you're better off seeking help in one of the kernel-specific threads.
Click to expand...
Click to collapse
Could or couldn't it may also be a problem with initramfs and boot parameters. I now because i experienced it. So if you give us more information, better, try to record a video of the bootloop and pass it slowly to see the error, i did that and it worked for me

Franks Tools-new modified Ubuntu install
Hello i dont know if this is right thread,i like to ask you advanced users for some help.I wanna install ubuntua via new modified Franks tools by kenshin,released few days ago,i cannot find exact answer what i need to progress.
My questions are: How can i made nvflashable files system.img boot.img recovery.img and others to use franks tools? how to obtain these images?
2.) and if i will use those images that can be found here on forum can i then just flash for example Revolution HD rom? ,or does it destroy my installation of ubuntu via franks tools?
because i know that there is little play with partitions so i am not sure if i can flash any rom after use of franks tools dual boot option.thank you for help

shaola said:
Could or couldn't it may also be a problem with initramfs and boot parameters. I now because i experienced it. So if you give us more information, better, try to record a video of the bootloop and pass it slowly to see the error, i did that and it worked for me
Click to expand...
Click to collapse
I did everything stock and did exactly what you said to do for Debian, though I used the armel architecture and the adb wouldn't work with an error.
By everything stock, I mean that I didn't alter anything from the OLiFE folder except adding the ubuntu.img file.

NothingMuchHereToSay said:
I did everything stock and did exactly what you said to do for Debian, though I used the armel architecture and the adb wouldn't work with an error.
By everything stock, I mean that I didn't alter anything from the OLiFE folder except adding the ubuntu.img file.
Click to expand...
Click to collapse
The original kernel from OLiFE didn't work for me - I had a boot loop. Try manually compiling the lilstevie kernel, or using a kernel from Jhinta's kernel thread.
The packed kernels (CWM zips) for Ubuntu will work exactly the same under Debian. (or at least in the direct mount case - I don't know about loop mount)

i can't get wifi up ... could someone help?
it is shown in iwlist wlan0 scan but i can't find an network ...
while boot it sends many intervals and abort this progress with givin' up.
i just copied li/firmware file from olife.img und files from this thread over it ...
anyone could help please?

NoDiskNoFun said:
i can't get wifi up ... could someone help?
it is shown in iwlist wlan0 scan but i can't find an network ...
while boot it sends many intervals and abort this progress with givin' up.
i just copied li/firmware file from olife.img und files from this thread over it ...
anyone could help please?
Click to expand...
Click to collapse
what are you uing to scan? this driver ony supports wpasupplicant, not iw nor iwconfig

hi,
i installed the ubuntu image with olife on my transformer. i don't like ubuntu very much, i prefer debian which i run debian on my computer as well. i stumbled over this thread so i wondered what's the status of debian on our transformer.
can anyone tell me whats currently working.

hanswurschtus said:
hi,
i installed the ubuntu image with olife on my transformer. i don't like ubuntu very much, i prefer debian which i run debian on my computer as well. i stumbled over this thread so i wondered what's the status of debian on our transformer.
can anyone tell me whats currently working.
Click to expand...
Click to collapse
The same as in ubuntu. But you may need some tweeks. Depends of the kernel you are using. nvidia has released also a beta of the nvidia drivers for armhf and not only armel so you may use armhf or armel with jintha's kernel and have almost everithung working.

TF101 booting into Recovery

Hi.
First, I'd like to say I tried searching but no luck.
Second, I'm a total Asus noob. I'm pretty good with my HTC Legend, but I don't quite understand the transformer.
My problem: It boots directly into recovery. I bought it used, and it was rooted and running ARHD. When I bought it the seller showed me how to boot it : Boot it regularly, then select "reboot" in recovery, hold "vol-" and it boots into some sort of "menu" where I should press "vol+" to do a cold boot. This is necessary every time. He claimed that all rooted Transformers were like this; I highly doubt that.
So, is there any way I can make it boot normally?

He got it into a boot-loop, you can try fixing it by running my One-Click PERI tool, and then choosing the 'fix-bootloop' option.
This is not normal for rooted transformers, but is a very common and relatively easy to fix problem.

Thing O Doom said:
He got it into a boot-loop, you can try fixing it by running my One-Click PERI tool, and then choosing the 'fix-bootloop' option.
This is not normal for rooted transformers, but is a very common and relatively easy to fix problem.
Click to expand...
Click to collapse
Downloaded, but ADB doesn't recognize my TF101 (adb devices returns nothing)
Tried installing the supplied .inf , but it isn't supported (Windows echoes "The selected INF-file does not support this installation method") and nothing is changed.
So I guess I need some drivers now..
EDIT: Okay, I got the drivers working thanks to Brk's rootkit.
Ran your tool, with "u" as first argument.
Finished without problems.
Still goes to recovery and not booting Android.
Tried applying the "r" option, still boots into CWM 5.5.0.4.
EDIT2: New touch recovery installed, new ROM flashed but still no instant boot.

Ok good, you got out of the bad CWM.
Now you need to reflash your bad bootloader, goto the asus tf101 site, pick download, android, firmware. Then find the firmware for your Region (it'll be WW I believe)
download blobunpack from either searching 'windows' in rayman's blobtools thread or downloading the blob.zip from my boot splash change guide, take the new firmware, unzip the file called 'blob' to a folder with blobunpack.exe in there, then open cmd and cd to the folder, then run 'blobunpack blob', the blob will now be split into many smaller blobs. What you'll want to do is take the one named blob.EBT, then put it on the root of your transformer's INTERNAL storage (So either adb push blob /sdcard/) or use windows to just place it there.
Then go into adb shell or terminal emulator app and type"
Code:
su (Grant root if it asks)
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
It will reboot, you'll see a blue bar for just a moment, then it reboots again, and *Hopefully* won't get stuck.

Thing O Doom said:
Ok good, you got out of the bad CWM.
Now you need to reflash your bad bootloader, goto the asus tf101 site, pick download, android, firmware. Then find the firmware for your Region (it'll be WW I believe)
download blobunpack from either searching 'windows' in rayman's blobtools thread or downloading the blob.zip from my boot splash change guide, take the new firmware, unzip the file called 'blob' to a folder with blobunpack.exe in there, then open cmd and cd to the folder, then run 'blobunpack blob', the blob will now be split into many smaller blobs. What you'll want to do is take the one named blob.EBT, then put it on the root of your transformer's INTERNAL storage (So either adb push blob /sdcard/) or use windows to just place it there.
Then go into adb shell or terminal emulator app and type"
Code:
su (Grant root if it asks)
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
It will reboot, you'll see a blue bar for just a moment, then it reboots again, and *Hopefully* won't get stuck.
Click to expand...
Click to collapse
This pad is bought in the US. So I guess I should go with the US file?
Edit: Went for the US file, extracted blob.EBT, tried your command in the Terminal Emulator (i had to add ".EBT" after if=/sdcard/blob to make it work) but it still didn't- It moved the file, and I typed in "reboot". It rebooted, but no blue bar and I went straight to recovery. Trying again, but I doubt it will be any different.
Edit2: Nope, same sh*t. Getting kinda annoyed now...

No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.

Thing O Doom said:
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Click to expand...
Click to collapse
Oh thank you very much,this worked. The trick was to let the blob be extensionless.
However, I saw no blue bar, but it booted without going into recovery atleast

Glad it's finally working right
Go call the seller and complain >.<

Thing O Doom said:
Glad it's finally working right
Go call the seller and complain >.<
Click to expand...
Click to collapse
I thought it was solved, but no.
This comes back every time something in CWM is flashed - flashed a bootanimation, it came back, i ran your commands and it was solved. Flashed a new kernel now, it came back.
Ran the commands, it went away but I noticed my kernel wasn't changed and I can't overclock... I think I have a bad CWM accually.

You need to reflash a working CWM recovery then, I take it you're on that infernal ROM manager version. I'd flash Rouge XM 1.5 touch

Thing O Doom said:
You need to reflash a working CWM recovery then, I take it you're on that infernal ROM manager version. I'd flash Rouge XM 1.5 touch
Click to expand...
Click to collapse
Tried PERI but apperantly I cant give ADB SU rights, because wrote failed at /dev/block/mmcblk0p4 because of denied permissions.
Can I use dd to flash it like I did previousley?
Edit: I looked at the sauce of PERI and saw that it was flashing using a shell and DD so I entered it in a regular elevated ADB shell. Finally saw that blue bar I've been looking for and I have Team Rouge's (5.0.2.8) 1.5.0 recovery now. Thank you very much.

Actually, the same has happened to be, and i was trying to go back to stock ww, and i seem unable to find some kind of tutorial for that... I will try what was posted here at least to remove that initial loop.

MarkInDaPark said:
Tried PERI but apperantly I cant give ADB SU rights, because wrote failed at /dev/block/mmcblk0p4 because of denied permissions.
Can I use dd to flash it like I did previousley?
Edit: I looked at the sauce of PERI and saw that it was flashing using a shell and DD so I entered it in a regular elevated ADB shell. Finally saw that blue bar I've been looking for and I have Team Rouge's (5.0.2.8) 1.5.0 recovery now. Thank you very much.
Click to expand...
Click to collapse
Running PERI In CWM always gives root access x)
Try doing the fix bootloop function inside cwm.
Nice to see that you figured it out!

Thing O Doom said:
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Click to expand...
Click to collapse
That did the trick for me, my "boot direct to recovery" problem started when I accidentely selected Reboot to recovery under Advanced when I was "on that infernal ROM manager version" of recovery.

im having similar problems ..... Yep i updated CWM via ROM Manager to 5.8.3.4 (although since managed to downgrade it in theory to 5.8.2.1)
only way i can get into full Android is via a cold boot (but then i have no SD card or Wifi support) or by flashing a full new ROM each time I reboot !!!
problem i have is that im on my holidays and have no access to a PC
Google brought up a patched CWM version but even after flashing that in recovery it was still booting straight into CWM.

Well you r on holiday so can't do anything now... when you come back home try easy flasher to unroot and root again by that way you can get rid of that recovery....
Sent from my Transformer TF101 using xda app-developers app

[Q/A] SBK2v Net-Install Ubuntu

I find a bit vague about installation guides.
NOTE: ALL UR DATA WILL BE DELETED PLEASE BACKUP IT WITH THIS: NFLASH BACKUP / RESTORE OR TITANIUM BACKUP
ALSO USB IS NOT WORKING FOR THE STOCK ROM NOT FOR AR HD OR MAYBE OTHERS.)
GNOME HAS WIFI, BUT IT DOESNT SHOW. FLASH WONT WORK ON ARM UBUNTU.
This is for newcomers with SBK2v.
here we go:
U need Virtuel box Ubuntu: Link tot tutorial of that
Ok u also need olife for sbk 2 i posted new link in this forum: At the bottem of the page
Net- ubuntu installer form this thread: http://forum.xda-developers.com/showthread.php?t=1852702
A USB or something to get those files or download in virtual box ubuntu
ALSO THIS IS VERY [email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]!: U NEED BOOT IMG AND SYSTEM IMG or backup of your device (Recommended).
blob.APP - system.img
blob.LNX - boot.img
( if you unblob it with this tool: #24 scrol ldown a bit u see it its windows version i expect that u have that. use cmd then go the place where u unpakc that package example: C:\bloblunpack and then bloblunpack BLOB NAME)
atleast 15 gb ubuntu...
So lets get started:
After you did all those dam configuration of in virtual box ubuntu. Boot it and go to the folder there you paste the Olife SBKv2.
Paste the boot.img and the system.img (Or the blobs and rename as boot.img same as system.img) in the image folder of olife and ofcourse the net install ubuntu and rename the net install ubuntu to ubuntu.img.
Double click on Olife.sh and run it with terminal.
Type understood and ur password and ur at option screen.
u want ofcourse flash device so press 2
Dual boot
Default OS is Android
After that ( take a prox 10 - 20 min.). U start ubuntu up and it will give you login screen. Type first root and then temppwd. After that type /setup2.sh (If not working keep going until u get online partition install and reboot evertime until at that same place u get wifi configuration).
It says everything works correcly u say No (N) and configurate ur wifi.
After u reset it and waiting for wifi configuration is not there. U type the same user name / pass and then /setup2.sh (NOT FOUND D:? step3.sh). Y and select ur ubuntu etc.
If jhinta is not installed ( check it with uname -r it sohuld say 3.1 blah blah)
u can flash it with form NoDiskNoFun post:
flash it with "dd if=/Linux_for_Tegra/selfbuild.img of=/dev/mmcblk0p9" for second boot
and "dd if=/Linux_for_Tegra/selfbuild.img of=/dev/mmcblk0p10" for first boot
ALSO INSTALL ZRAM!!! VERY IMPORTANT!!:
make new clean document in /etc/init/ and call it zramswap.conf
and paste this in your browser : https://wiki.ubuntu.com/ARM/TEGRA/AC100?action=AttachFile&do=get&target=zramswap.conf adn then copy that and put it in zramswap.conf
Sound Problems? : Open terminal adn then : sudo apt-get install gnome-alsamixer. After it installed open in terminal with: alsamixer and then follow the same instructions: Set ADC Input on DMIC. Enable every DACL AND DHCR ( Not or, because my sound works on both sides when i turn these 2 on).
Jhinta kernel install(Wit the proper ziimage etc.):
Upcoming currently testing.
Pictures are coming. On pc first later on my tablet screen ( At the moment no camera :\)
Have fun SBK2 Users Cheers :3
Any questions, post it below.
Thanks to all developers
Waited for pretty long time :3
Changelog:
Just clean up the mess and i found loads of information

?
Thank you very much for this post ... it's very very helpful !
it work without dock ?
have to install ADB before or APX ?
is it possible to use a live DVD of Ubuntu ?
regards.
@+

samco08 said:
Thank you very much for this post ... it's very very helpful !
it work without dock ?
have to install ADB before or APX ?
is it possible to use a live DVD of Ubuntu ?
regards.
@+
Click to expand...
Click to collapse
Well ADB is glitchy as the OP said in the net installer. Also i dont think a live DVD works.
This is actually dock only.

For some reason once mine starts nvflash it goes back to asking if I want to flash as dualboot/ uboot/ etc. Am I doing something wrong? Using the Net-installer 0.6 and the system/boot/etc .imgs from olife prime

jmm42991 said:
For some reason once mine starts nvflash it goes back to asking if I want to flash as dualboot/ uboot/ etc. Am I doing something wrong? Using the Net-installer 0.6 and the system/boot/etc .imgs from olife prime
Click to expand...
Click to collapse
I havent use ubuntu quite a while because i am focusing school, becasue itsm y exam year...
Use your current rom + kernel and backup it and then rename it was in tutorial and use it.
Sorry i cant support anytime soon :\.
What i can remember that i unlockede the opengl option + I made it see like x86 but still a arm version kinda wierd.
Only problem for this tutorial itsn ow outdated i dont know what fixed in Bet - installer 0.6.
Maybe i do it once more. Just help for SBK2 army.
Anyways i find ubuntu on tf 101 only good for school stuffs etc. If you want use as normal house or something it wont be anything because chrome cant be installed in arm. Or anything iwth flash :\.
Anyways good luck

[Multiboot][Mountloop][No Pc] Transformazing

Transformazing
This is for tf101 only and i do not take any warranty, means when you destroy your device with that it is your fault !
I did not find this method, nor i developed the kernel, the only thing i did was that i packed the newest jintha kernel into cwm flashable packages and had the idea to install more than
one linux system because i was pretty nerved because i had arch, ubuntu and 13.04 installed and always had to rename one to ubuntu.img. So i put the kernel into 3 (maybe make more)
packages, which look for the files /mnt/sdcard/.linux1, (/dev/mmcblk0p7 rw loop=/media/.linux1.img), .linux2.img and .linux3.img. The point is to hide the files, so you dont see them
for default if you boot to android.
Installation:
Download a armel/armhf image, rename it to .linux1/.linux2,/.linux3 and put it to internal sd(under android /mnt/sdcard or /storage/sdcard0(or 1, roms differ.)(i suggest tubuntu v 1..1, 1.2 has more bugs lol)
Flash the kernel in cwm (linux1 kernel for .linux1, linux2 kernel for .linux2, ... easy, isnt it?
To go back to android flash one of these (http://www.mediafire.com/?labcx60jowrdx), or extract the kernelblob form your rom, or just flashing your kernel should also work(not tested by me).
Any questions?
Changelog:
There is no changelog and there wont be one because i only put the kernels into mountloop packages, but i will try to get a stable 2.6 kernel into a mountloop package(no luck until now)
Advanages of this and other mehods:
Mountloop:More than one Linux os possible
No Pc needed
Easy to remove linux
Easy to give more space to linux/android
Faster to flash
Sl101/tf101g should work too
Option to boot linux from microsd
Olife, tubuntu:Chose os on boot
2.6 kernels and kernels greater than 8 mb possible (only 2.6)
Whats up with these Kernels:
.linux1: 3.1.10: Jintha Kernel, working : Sound, Hw acceleration, Sd, microsd, usb(if a dev is connected at boot), ...
sometimes freezes, use tubuntu v 1.1 and not 1.2
.linux2: 3.1.10: same as above
.linux3: 3.1.10:: dont know which, better touchpad, sound, hw acceleration, sd, microsd, usb(if something is connected at boot), stable, does not work with tubuntu and raring images
.linux4: 2.6.36.4: sound only headphones, no hw acceleration, working with nearly every image
kernelexternal: boots the os installed on micro sd(explained in 2nd post)
Images:
Archlinux and Raring: http://goo.im/devs/x3maniac
Ubuntu 11.10: http://www.ulozto.net/xyFaPBA/ubuntu-img-gz
Tubuntu v1.1(lubuntu 12.10): http://www.novaspirit.com/tubuntu/tubuntu.php
Debian: http://forum.xda-developers.com/showthread.php?t=1476835
Ubuntu 12.04 netinstall: http://forum.xda-developers.com/showthread.php?t=1852702
Lubuntu 12.04. http://www.ulozto.net/xauaj1b/ubuntu-img-gz
If this thread should be in general, pls move it!
The video quality is really bad(really really really bad), so i suggest only watch it if you dont understand it.​
I added the kernels for android 4.2 file system
The .linux .img s have to be placed on /storage/sdcard0 on first user
then flash the packages for your img name (.linux1.img or .linux2.img) and you boot to linux,
flash your kernel (kat, for exmple), to boot back to android

Linux tips and instructions
nstructions for linux:
get flash:
working on both firefox and chromium:
sudo apt-get install gnash gnash-common browser-plugin-gnash
perforance is bad, sound is perfect on youtube many videos can be watched in html5, their performance is way better( full framerate)
Get multitouch working:
On 11.10: sudo apt-get install touchegg and add it to startupapplications
on arch: yaourt -S touchegg (i think xD)
on others: compile touchegg
Put an image to microsd:​(will erase files on sdcard)
dd if=/sdcard/linux.img of=/dev/block/mmcblk1p1
How to get sound(if not working)​sudo usermod -a -G audio yourusername
sudo chmod -R 777 /dev/snd
enable every dacl and dacr
disable dac and adc companding(if sound is choppy)
How to get network-manager working on systems with wpa supplicant installed(arch, raring, netinstall)
look at your modules: is there 3.1.10-g8c2655b-dirty? if not, i suggest downloading it from here
sudo apt-get install netwrok-manager network-manager-gnome
sudo leafpad /etc/NetworkManager/NetworkManager.conf: change false to true
sudo leafpad /etc/network/interfaces should look like this:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
and remove /etc/wpa_supplicant. (sudo pcmanfm or sudo nautilus and then you have a fm with root.)
Mount internal:
sudo mkdir /media/internal
sudo mount /dev/mmcblk0p7 /media/internal
internal is now on /media/internal, you can select any folder.
Get opengl:
install tegra drivers(find a deb, if in 12.10 you ca just enable it through software-sources.)
sudo apt-get install libgl1-mesa-swrast
How to resize img files:
From another linux image or from a linux pc: (i will show it with image called ubuntu.img)
cd /to/the/folder/of/the/image
e2fsck ubuntu.img -f
resize2fs ubuntu.img 3500M (3500M is new size, M means MB, G means GB...)
e2fsck ubuntu.img
How to get touchpad working:
sudo apt-get install xserver-xorg-input-mtrack
and add to xorg.conf this at the end:
Section "InputClass
Identifier "elantech_touchscreen"
Matchproduct "elantech_touchscreen"
MatchDevicePath "/dev/input/event*"
Driver "mtrack"
EndSection
set keyboard layout:
add to startup programs this:
setxkbkmap de/en/fr
mount/chroot into an image from an otherinstall programs to an image with no network manager)
sudo mount /dev/mmcblk0p7 /media/int (mount internal)
sudo mount /media/int/media/.linux123.img /media/int (not linux 123, but .linux1, .linux2...)(now .linux123.img is on /media/int)
(sudo chroot /media/int) (now you are in the image)(internet connection should be there with 2.6 kernel)
Desktop tips:
Lubuntu/lxde:
Pro: The fastest and freakin light
Very customizeable
Beautiful
Easy to use with other components (etc/xdg/lxsession/LXDE(or lubuntu)/autostart)
Con:Cant think of anything bad
Xubuntu/xfce4
Pro: Very fast
Costumizeable
Con:I dont Like it
no hw acceleration
xfwm4 didnt work with touch on an image
ugly?
kubuntu/kde4
Pro:Customizable
Looks good
Con:Slow
e17
Pro: touchoptimiced
fast
con: Ugly(download themes)
Not easy to use with other components
ubuntu
Pro: Looks cool
con: Sloooow
gnome: Doesnt work right on our device
gnome-classic/gnome-session-fallback:
Pro:nearly as fast as lxde
supercool look
good with touch and with keyboard
con: cant think of anything bad
plasma-active/kde-plasma: Not tested
I suggest installing sudo apt-get install gnome-session-fallback, it is very fast, volume buttons are working and you can set brightness.(also install gnome-tweak-tool and gnome-themes-standard)
Use Components from other desktops in lxde/xfce:
(to have a supercool looking fast desktop)
add to startupapplications the stuff you want or just run it:
in lxde: /etc/xdg/lxsession/LXDE/autostart
in lubuntu:/etc/xdg/lxsession/lubuntu/autostart
in xfce/gnome/kde: i think there is a app for that: startup-applications i think
Docks:
Docky: works best(not working on all images)
Cairo-dock:not that smooth
Avant: not tested
unity-2d-launcher: the default unityy launcher you can see on the left in ubuntu-desktop
Panels:
lxpanel: Highly customizeable, fast, light
unity-2d-panel: love it, it is the top panel of ubuntu
xfce4-panel: little better than lxpanel
Use other Windor-managers in different desktops:
Add to startupapplications too or run te comand.
metacity --replace
openbox --replace
xfwm4 --replace
Credits to:
Jintha
Lilstevie
x3maniac
shaola​

Post screenshots please
Sent from my GT-S7562 using xda premium

akshay007dhore said:
Post screenshots please
Sent from my GT-S7562 using xda premium
Click to expand...
Click to collapse
The screenshots are from whatever image you use, you can see them for example in the tubuntu thread, but i will make some of ubuntu 12.10 or arch( the ones i use) and post them
Btw, anyone knows how to add images to a post? xD

I must be missing something fundamental lol, i downloaded the tubuntu.img in your post, extracted and renamed it to .linux1 then flashed the linux1 mount-loop then restarted, and end up at busybox terminal (every single thing ive tried ends there)
i'll to download a different image and see how it goes.
---------- Post added at 08:48 AM ---------- Previous post was at 08:46 AM ----------
bottom line 6th button in from the right in the message box, or the attachments button up and slightly to the left :good:

JoinTheRealms said:
I must be missing something fundamental lol, i downloaded the tubuntu.img in your post, extracted and renamed it to .linux1 then flashed the linux1 mount-loop then restarted, and end up at busybox terminal (every single thing ive tried ends there)
i'll to download a different image and see how it goes.
---------- Post added at 08:48 AM ---------- Previous post was at 08:46 AM ----------
bottom line 6th button in from the right in the message box, or the attachments button up and slightly to the left :good:
Click to expand...
Click to collapse
You are doing it righ, strange...
Is it called .linux1 or .linux1.img? Because right now i am using the linux1 kernel. What happens if you try the linux3 kernel for example?
And: Try to recopy the tubuntu image a second time, maybe it is corrupt(had exactly this problem yesterday xD)
Tell me how it goes
And: what are you talking from left and right?

transformador said:
You are doing it righ, strange...
Is it called .linux1 or .linux1.img? Because right now i am using the linux1 kernel. What happens if you try the linux3 kernel for example?
And: Try to recopy the tubuntu image a second time, maybe it is corrupt(had exactly this problem yesterday xD)
Tell me how it goes
And: what are you talking from left and right?
Click to expand...
Click to collapse
Cool, lol and i was trying to direct you to the "insert image" button

JoinTheRealms said:
Cool, lol and i was trying to direct you to the "insert image" button
Click to expand...
Click to collapse
Oh, thanks )
Is it working now?

transformador said:
Oh, thanks )
Is it working now?
Click to expand...
Click to collapse
Sorry my tf101's power buttons broken, and the tab froze inside of cwm6 so had to angrly disasemble my tf101 just to restart it :crying: lol anyway havn't downloaded a new image yet, whats your recommendation? im mainly intreasted in trying these multitouch gestures but also the 3.1 kernel NEVER worked for me anytime i tried to install it, if this works with hwaccelation ill be stoked(youtube etc work well?)
btw i renamed the image ".linux1" without .img @ the end ...ill add it an try

Heres the output messges i get with both images(tried to make it short to save sometime writing it out, also i took a photo of the output with a terrible camera and couldnt the rest of it so ill retry and update)
tegra_init_mmc memory not recongnised, memory scaling disabled
uipi_phy_power_on: timeout waiting for phy clock to
uipi_phy_power_on: uipi write failed
tegra-echi tegra-echi.1: failed to power on phy
fsi-tegra-udc fsi-tegra-udc: can't get charge...........
...._config_settings
power_supply dock_battery: failed to report
sdhc1-tegra sdhc1-tegra.2:vddio_sd_slot
:vddio_sd_slot regulator.......
tegra.0
:vddio_sd_slot regulator........
tegra protected aperture disabled becouse nvmmc..........

if you have the the distro in an .img folder it will slow down becouse if has to work instie that folder, where if you extract the image in your ubuntu distro folder it would run a bit faster, don't know if ou are doing that or not but it is my 50 cent
Awsome work and thank you, i can use current roms and dual boot without thincking about the nightmare of trying to figure out how to nvflash buckup a rom, back one ub, and then see it update.

Can someone make a video tutorial on this? Would be really grateful
Sent from my Transformer TF101 using Tapatalk HD

Well been trying to get this to work all day, seems the mount loop doesn't work on my tf101 currently (b60 sbk1) i get the same output messages whether then .linux1 image is in /sdcard/ or not. I could be doing something wrong but ive tried soooooo many combinations of things i would have fixed it by mistake lol.
Never mind , its great to see ubuntu getting better and easier for the tf101. Many thanks to transformador and the rest of you guys working on ubuntu:good::good:

JoinTheRealms said:
Heres the output messges i get with both images(tried to make it short to save sometime writing it out, also i took a photo of the output with a terrible camera and couldnt the rest of it so ill retry and update)
tegra_init_mmc memory not recongnised, memory scaling disabled
uipi_phy_power_on: timeout waiting for phy clock to
uipi_phy_power_on: uipi write failed
tegra-echi tegra-echi.1: failed to power on phy
fsi-tegra-udc fsi-tegra-udc: can't get charge...........
...._config_settings
power_supply dock_battery: failed to report
sdhc1-tegra sdhc1-tegra.2:vddio_sd_slot
:vddio_sd_slot regulator.......
tegra.0
:vddio_sd_slot regulator........
tegra protected aperture disabled becouse nvmmc..........
Click to expand...
Click to collapse
Thats exactly the error when i boot it without .linux1.img (yes theres an .img behind it), try to recopy it there.
Suggestions: Delete .linux1.img and copy it there a secound time (do you have it on /sdcard or on another location? has to be /sdcard, it is a symbolic link to /media on mmcblk0p7, but the /media on android is something other)
Try another .img file. Maybe try netinstall? It has an option to enable multitouch , tegra drivers and you can select desktop. (resize it before installing desktop)
Try linux2 kernel and call the image .linux2.img.
If nothing works, i will download the kernel and see what its wrong (would be stupid because i am booting it with EXACTLY the same kernel i uploaded(did not even copy it to another location )
Dont really understand your next post, is it working now or not? XD

alizafar said:
Can someone make a video tutorial on this? Would be really grateful
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
If crappy quality is enough, for shure, but i only have a ****ing 320x240 phone camera xD
But if i can borrow my sisters phone, or my dads camera, i will do a video tutorial.
2 other things:
Who rated my thread 1 star? lol
Edit: forget what i wrote before xD
Video is up, but crappy quality...

plasmastrike said:
if you have the the distro in an .img folder it will slow down becouse if has to work instie that folder, where if you extract the image in your ubuntu distro folder it would run a bit faster, don't know if ou are doing that or not but it is my 50 cent
Awsome work and thank you, i can use current roms and dual boot without thincking about the nightmare of trying to figure out how to nvflash buckup a rom, back one ub, and then see it update.
Click to expand...
Click to collapse
The slowdown is minimal, i dont really recognice a speed difference between my mates tubuntu and mymethod.

Tried your suggestions, not working yet although the output messages have changed ill post them up later on. basically tried multiple roms/ recoverys, renamed the .img 1,2,3,4 etc. The last thing i can think of is my partition structures messed up or something from an earlier ubuntu nvflash, ill re-partition and re-try.

JoinTheRealms said:
Tried your suggestions, not working yet although the output messages have changed ill post them up later on. basically tried multiple roms/ recoverys, renamed the .img 1,2,3,4 etc. The last thing i can think of is my partition structures messed up or something from an earlier ubuntu nvflash, ill re-partition and re-try.
Click to expand...
Click to collapse
Does this method work for you? It is looking for ubuntu.img on /sdcard. It is from here:
http://forum.xda-developers.com/showthread.php?t=1537566
http://www.mediafire.com/?7f5fpatmgmg01ha
The kernel posted does NOT work with tubuntu, but it is 3.1
Also: you have it on internal, not external, right? has to be on internal

transformador said:
Does this method work for you? It is looking for ubuntu.img on /sdcard. It is from here:
http://forum.xda-developers.com/showthread.php?t=1537566
http://www.mediafire.com/?7f5fpatmgmg01ha
The kernel posted does NOT work with tubuntu, but it is 3.1
Also: you have it on internal, not external, right? has to be on internal
Click to expand...
Click to collapse
So far ive tried the net installer image and tubuntu(i thought the kernel might be an issue with it) ill try the older tubuntu. Ive tried x3maniac and shaola's versions. x3maniac's didnt do anything(after flashing it just booted into android) and shaola's had simular output messages as yours. And yeah its on /sdcard (internel) although was tempted to try externel but only got a class 4. I appreciate the help mate:good:

JoinTheRealms said:
So far ive tried the net installer image and tubuntu(i thought the kernel might be an issue with it) ill try the older tubuntu. Ive tried x3maniac and shaola's versions. x3maniac's didnt do anything(after flashing it just booted into android) and shaola's had simular output messages as yours. And yeah its on /sdcard (internel) although was tempted to try externel but only got a class 4. I appreciate the help mate:good:
Click to expand...
Click to collapse
I have got the same issue. tried all linux1, 2, 3, 4.zip files. On linux4.zip I get the following error meassage:
/host/media/.linux4.img does not exist
But the file is on /sdcard

[Q] Question about removing system/bin/recovery?

OK, in the middle of writing up this topic, my situation has suddenly changed. (And changed again.)
The story begins: an old AT&T Samsung Infuse 4G, still on Froyo. Put it through a factory-reset and began to fiddle with how to install Clockwork Mod recovery. So there's the guide to upload a modified 3e recovery.
I run adblinux to push the modified recovery over the stock 3e at "system/bin/recovery" -- but "system/bin" was only in read-only mode and adblinux can't run "mount" and doesn't have permission to enter shell and run "su" (or enter shell as root) and File Manager HD (with Super User privledges) can't modify read-only folder "system/bin".
I managed to find a go around by pushing the modified-recovery into the sdcard's root and going through a terminal emulator on the phone to overwrite the file... but I rebooted the phone without running "chmod" on the newly overwritten file and the Infuse bricked so bad that even the battery in off-state refused to refresh.
I understand and accept what I did should be labelled as 'idiotic', but I did manage to wait at the Samsung logo until adblinux recognized the device and eventually restored the original recovery back to "system/bin" (I also found out adblinux didn't have permission to run chmod in the "system/bin" directory).
So... A few questions before I continue:
Why did (pushing the old recovery) work? ADB initially did not recognized the phone, but then the Infuse came up as "I997ae56e13f recovery" -- why was the name now 'recovery?'
And why does running "./adblinux reboot recovery" brings back the bootloop? (In fact, I cannot enter recovery mode, so something is still wrong -- the recovery file is not 755 and I can't chmod a read-only file-system either from adb or via super-user terminal. The temp-root method times out.)
OK, now I'm going home. I'll probably still try to re-install SuperUser. Maybe that will allow adblinux to run "su" in shell, but I'm not going to try anything too extreme.

Justin20 said:
OK, in the middle of writing up this topic, my situation has suddenly changed. (And changed again.)
The story begins: an old AT&T Samsung Infuse 4G, still on Froyo. Put it through a factory-reset and began to fiddle with how to install Clockwork Mod recovery. So there's the guide to upload a modified 3e recovery.
I run adblinux to push the modified recovery over the stock 3e at "system/bin/recovery" -- but "system/bin" was only in read-only mode and adblinux can't run "mount" and doesn't have permission to enter shell and run "su" (or enter shell as root) and File Manager HD (with Super User privledges) can't modify read-only folder "system/bin".
I managed to find a go around by pushing the modified-recovery into the sdcard's root and going through a terminal emulator on the phone to overwrite the file... but I rebooted the phone without running "chmod" on the newly overwritten file and the Infuse bricked so bad that even the battery in off-state refused to refresh.
I understand and accept what I did should be labelled as 'idiotic', but I did manage to wait at the Samsung logo until adblinux recognized the device and eventually restored the original recovery back to "system/bin" (I also found out adblinux didn't have permission to run chmod in the "system/bin" directory).
So... A few questions before I continue:
Why did (pushing the old recovery) work? ADB initially did not recognized the phone, but then the Infuse came up as "I997ae56e13f recovery" -- why was the name now 'recovery?'
And why does running "./adblinux reboot recovery" brings back the bootloop? (In fact, I cannot enter recovery mode, so something is still wrong -- the recovery file is not 755 and I can't chmod a read-only file-system either from adb or via super-user terminal. The temp-root method times out.)
OK, now I'm going home. I'll probably still try to re-install SuperUser. Maybe that will allow adblinux to run "su" in shell, but I'm not going to try anything too extreme.
Click to expand...
Click to collapse
I am curious how adblinux differs from the linux compiled version of adb. Usually it's just called adb.
Anyway, if you are using a Linux OS, and you pulled the original recovery to your PC before overwriting it, it should maintain it's permissions. Likewise, a push would set the permissions like they were on the host PC as well. They say to chmod afterward, because if you are using a windows packaged/downloaded file, or pushing with a Windows PC, the permissions could be anything in the end (rarely what you really want).
As to why the device name changes, not sure. Device names change based on the ROM installed (not always serial number), so it's not out of the question that recovery could tack on something else.
With above, problem is, even with Linux, it doesn't always line up so permissions can be influenced in a push but you may not get what you were asking for. Try chmod 755 the recovery on the local side and adb push the recovery again, after making a backup of the recovery that is there and see if it continues to bootloop.
If all else fails, as long as you have download mode, you can always use ODIN (or Heimdall) to go back to stock (albeit newer Gingerbread). Option A gives you root only, option D, root + recovery (CWM).
Hope this helps.

Thanks for replying!
joel.maxuel said:
I am curious how adblinux differs from the linux compiled version of adb. Usually it's just called adb.
Click to expand...
Click to collapse
I.. have no idea actually. I don't know how to configure Wine to properly emulate an environment for the Windows ADB and I can't get the correct phone-drivers for my WinXP system. (Kleis won't recognize the rooted phone, though if I leave the phone plugged in while installing Kleis, it will interrupt with a "Samsung Mobile Device connected" message.)
joel.maxuel said:
They say to chmod afterward, because if you are using a windows packaged/downloaded file, or pushing with a Windows PC, the permissions could be anything in the end (rarely what you really want).
With above, problem is, even with Linux, it doesn't always line up so permissions can be influenced in a push but you may not get what you were asking for. Try chmod 755 the recovery on the local side and adb push the recovery again, after making a backup of the recovery that is there and see if it continues to bootloop.
Click to expand...
Click to collapse
Unfortunately I can't chmod and push at the same end.
-I tried changing the permissions of recovery file on my PC, but I wouldn't be able to push it onto the "system/bin" directory in the phone.
-I tried changing the permissions on the existing "/system/bin/recovery" file, but the phone says it's a read-only filesystem.
-I tried chmod from the phone in a different directory, but I can't move the file into the "system/bin" directory (cross-device link), delete the existing recovery file (read-only filesystem), and.. why don't I have the copy command?
joel.maxuel said:
If all else fails, as long as you have download mode, you can always use ODIN (or Heimdall) to go back to stock (albeit newer Gingerbread). Option A gives you root only, option D, root + recovery (CWM).
Click to expand...
Click to collapse
I thought flashing with Odin/Heimdall required access to recovery (to wipe all user data and cache folders either before or after the flash).
Without a recovery mode to boot into, won't I be sunk if things go wrong?
Also, I seem to have a different Heimdall frontend, one that doesn't have slots for PDA. It might be because I'm using an newer/older (1.3.1) edition from Ubuntu 12.04 (the official downloads page only has it for 12.10~13.04 editions of my OS), so I'm probably going to have to command-line it.
Code:
heimdall --verbose flash --factoryfs factoryfs.rfs --cache cache.rfs --modem modem.bin --kernel zImage
Look about right? (No partition image table from the tarball found in that forum link?)

Justin20 said:
I.. have no idea actually. I don't know how to configure Wine to properly emulate an environment for the Windows ADB and I can't get the correct phone-drivers for my WinXP system. (Kleis won't recognize the rooted phone, though if I leave the phone plugged in while installing Kleis, it will interrupt with a "Samsung Mobile Device connected" message.)
Click to expand...
Click to collapse
There is adb for Linux, I think adb is natively Linux anyway (the Windows version being the port). Don't have to worry about drivers if in Linux, due to the native support. If using Debian, Ubuntu (or any other Debian derivative), just need to run:
Code:
sudo apt-get install adb
But judging by immediately below, a different version of ADB probably won't change much.
Justin20 said:
Unfortunately I can't chmod and push at the same end.
-I tried changing the permissions of recovery file on my PC, but I wouldn't be able to push it onto the "system/bin" directory in the phone.
-I tried changing the permissions on the existing "/system/bin/recovery" file, but the phone says it's a read-only filesystem.
-I tried chmod from the phone in a different directory, but I can't move the file into the "system/bin" directory (cross-device link), delete the existing recovery file (read-only filesystem), and.. why don't I have the copy command?
Click to expand...
Click to collapse
'cp' should exist, be interesting if it did not. A different ADB could change the outcome (#1), but as pointed out before, you probably won't get the permissions you wanted in the end. Outcomes 2 and 3 would end up being the same, as the device is mounted read only.
You may get lucky with this:
Code:
adb shell mount -o remount,rw system
If root has any influence with this ADB session, it will remount your /system so you can chmod your recovery file on the device end.
Justin20 said:
I thought flashing with Odin/Heimdall required access to recovery (to wipe all user data and cache folders either before or after the flash).
Without a recovery mode to boot into, won't I be sunk if things go wrong?
Click to expand...
Click to collapse
My understanding is that it is completely separate, as the process will replace recovery to stock as well. But just in case, keep this one as a last resort.
I never used Heimdall, just ODIN through a WinXP Virtual Machine (only heard about Heimdall later), but when I used ODIN, I never had any problem with these generic drivers (adbsetup-1.3):
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/

Wow, I wish I took better notes last week. I had to go elsewhere and come back to this project and whatever progress I had made, I think I'm starting over from scratch.
I still can't mount/remount the system folder from anywhere (via ADB under Win/XP and Linux/Ubuntu 12.04); running "su chmod" from the phone still gives a permission denied, changing from Superuser to SuperSU didn't do anything (both programs did find the SU binary to be outdated), and adding a Busybox APK did not add a 'copy' function to my terminal emulator (on the phone) so running an ADB shell would be limited in that regard as well.
I'm going to have to take the phone to a McDonald's and attach a Google account to it. (I would have liked to have done all this offline somehow.)
joel.maxuel said:
when I used ODIN, I never had any problem with these generic drivers (adbsetup-1.3):
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
How did you manage to get your virtual OS to go "online?" When I tried installing the Google device drivers that came with adbsetup, a big red "X" popped up (Install failed).
I saw that there was a Java-based ODIN, but it's Java 8.0. Should I be using a later/earlier version of Odin/Heimdall? The latest versions don't support my OS (surprising since they support the latest, 14.04, and 12.10 but not anything between or 12.04, the other big release). The existing XDA threads all use Odin/Heimdall 1.1 -- the 1.3 version I have does NOT look like that (and does not have the "PDA" options in the GUI).

Justin20 said:
How did you manage to get your virtual OS to go "online?" When I tried installing the Google device drivers that came with adbsetup, a big red "X" popped up (Install failed).
Click to expand...
Click to collapse
Did the adbsetup binary change? I remember a DOS install process, so there shouldn't have even been a setup wizard (graphical anyway).
Anyway, to get the virtual OS to recognize, need to right click on the devices icon on the bottom status bar (at least in VirtualBox), looks like a USB drive, and select Android, or whatever pops up.
Hope this helps. Also, did the shell remount mentioned earlier have any effect (using adblinux)?
Sent from my Asus MeMO Pad 8"

joel.maxuel said:
Did the adbsetup binary change? I remember a DOS install process, so there shouldn't have even been a setup wizard (graphical anyway).
Click to expand...
Click to collapse
The DOS prompt process begins a driver install. From there, the Setup Wizard popped up.
joel.maxuel said:
Anyway, to get the virtual OS to recognize, need to right click on the devices icon on the bottom status bar (at least in VirtualBox), looks like a USB drive, and select Android, or whatever pops up.
Click to expand...
Click to collapse
Another bad sign: nothing pops up.
As for using mount/remount, the option "remount" was not found. (It would scroll down the whole list of options and switches.)
I think it's time for me to give up the ghost on fixing this issue. I still don't know how I managed to foul it up in the first place because I tried repeating it (entering the command-prompt from the phone, entering superuser, and moving files into "/system/bin") to no avail. So there is a modified 3e recovery file in "/system/bin" without the correct permissions that's preventing the phone from entering recovery mode (and slowing up the boot-up process and "battery recharge" icon when powered off), but other than that the device works, so that's something.
I still would like to try flashing the entire thing with ODIN/Heimdall if I could get either to work. (I ran the latest Heimdall, 1.4.0 32-bit, under WinXP only to find it was not a valid binary. The various Open Disk-Imager in a Nutshell (ODIN) apps out there, but nothing looks like those used on these forums (and did not include a PDA option).

Justin20 said:
The DOS prompt process begins a driver install. From there, the Setup Wizard popped up.
I still would like to try flashing the entire thing with ODIN/Heimdall if I could get either to work. (I ran the latest Heimdall, 1.4.0 32-bit, under WinXP only to find it was not a valid binary. The various Open Disk-Imager in a Nutshell (ODIN) apps out there, but nothing looks like those used on these forums (and did not include a PDA option).
Click to expand...
Click to collapse
The correct version of ODIN will be packaged with whatever image you choose. Just find a windows machine lying around, install the adbsetup drivers, and flash away. Hope this helps.