Database Users

Help Needed... Think I Bricked my Nexus S

Greetings,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I rebooted the phone. This morning, I tried to restore the superuser permissions by following the steps I found here on xda but after running the terminal script I rebooted my phone and when my phone wouldn't boot beyond the Google screen.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
I can't access clockwork recovery from the bootloader.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamaratee
__________________
Phone: Nexus
Rooted with problems

This post might help:
http://forum.xda-developers.com/showthread.php?p=9866675
It has the adb commands on how to replace the existing boot loader with cwm and all.
Hope it helps.
EDIT: If all else fails, you can try flashing a nandroid backup (2.3.3). This post would guide you:
http://forum.xda-developers.com/showthread.php?t=979851

Greetings Cygnum,
Thanks for the suggestion. I have a question: will these commands work on a Mac?

Thank you to AllGamer for suggesting that I post this question here and for the following suggestion:
AllGamer said:
please post the same question in QA or General, then we can all help you
PM is not the best place to ask for help.
The first thing to do is to download the full set of Android SDK 2.3+ for MAC
then we'll continue from there.
Click to expand...
Click to collapse
How do I proceed AllGamer? I downloaded the mac SDK from here (http://developer.android.com/sdk/index.html).

Follow steps 1-7 from here to get back Clockwork Recovery.
http://forum.xda-developers.com/showthread.php?t=878446
If your bootloader is already unlocked, you can skip those steps.
Do steps 8-9 to copy this file over to your USB drive.
http://devsforandroid.com/ip.board/index.php?/files/file/94-stock-deodexed-233-voodoo-rooted/
This rom is Master's Stock 2.3.3 ROM that is already rooted which should get you up and running.
Unmount, go back. Wipe system data, wipe cache. Go to advanced, Wipe Dalvik-cache.
Go back, choose to install zip from SD card. Locate Master's stock ROM. Flash that.
In the end, you'll have a stock deodexed rom that is rooted. Keep in mind that you will lose all your data, but that at least puts you back on track.

Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.

peeturr said:
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
Click to expand...
Click to collapse
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.

krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Yeah my bad. Just whatever had worked for me. Pretty new to mac myself.
Sent from my Nexus S using XDA App

krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.

kenvan19 said:
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
No. ~/ specifies your home directory

Thanks Everyone
Thanks for all the suggestions and help I received. I PM'd KenVan and he provided me with the script and my Nexus S is up and running.

I just had this problem on the weekend I could not get past the lockscreen so I flashed cyanogen nightly and bam booted fine
Sent from my Nexus S using XDA App

Problem Solved Over the Weekend
Thanks for the help everyone. I posted this in a couple places, so I forgot to update this thread.
I fixed the problem with detailed steps from KenVan. Thanks again though to all of you for your suggestions.

[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!

UPDATED XOOM FLASHING GUIDE 02/02/12​
I recently bought a US Xoom MZ604 and had trouble flashing it initially. I came to a realization that the newer models of Xoom reinstalls the Stock Recovery after you flash a custom Recovery (eg. CWM, Rogue Recovery etc). This is uber frustrating for newer Xoom owners, especially those who are new to the flashing community, simply because you don not know exactly what's going on.
Also, I could not find any proper, full and updated guide to flashing your Xoom. So i decided to take the initiative to do so.
WARNING: I DO NOT TAKE ANY RESPONSIBILITY IF YOUR XOOM TURNS INTO A USELESS BRICK. BY FOLLOWING THIS GUIDE, YOU WILL VOID YOUR XOOM WARRANTY WITH MOTOROLA. YOU HAVE BEEN WARNED TO EXERCISE CAUTION WHILE FOLLOWING THIS GUIDE. STRICTLY FOLLOW THIS GUIDE AND I ASSURE YOU, NOTHING WOULD GO WRONG.
In order to follow this guide, you need fundamental knowledge of ADB and Fastboot for Android. Search around the forum for this knowledge.
STEP 1: Obtaining Required Materials
a.) Download the latest version of Android SDK from HERE and install it into your the root of your C: drive.
b.) Download the latest version of Java SE from HERE and install.
c.) Download and Install the latest version of Motorola USB Drivers from HERE.
STEP 2: Unlocking your Bootloader
What is a Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. Source: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
1.) Make sure your Xoom is turned on. Connect it to your PC via USB.
2.) On your PC, open up File Explorer and Browse to:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
3.) In that directory, make sure nothing is selected, SHIFT+Right Click into empty space and select "Open command window here".
4.) Command Prompt will open up. Type the following command:
adb reboot bootloader
Click to expand...
Click to collapse
Your XOOM will reboot into the bootloader showing "Starting Fastboot Support Protocol".
6.) Type the following command into the Command Prompt to unlock your bootloader:
fastboot oem unlock
Click to expand...
Click to collapse
7.) Read the warning and follow the instructions on the Xoom Tablet itself from this point onwards. Use the Volume Down key to navigate to 'Accept' the agreement and press Volume Up to select.
8.) Once selected, your Xoom will now unlock and format itself, meaning, all data will be cleared and you will back to a factory rest.
9.) Reboot your Xoom with the following command:
fastboot reboot
Click to expand...
Click to collapse
10.) Exit Command Prompt.
STEP 3: Rooting your Xoom
1.) Download the latest version of "Universal Xoom Root" from this thread. Place the .ZIP file into the root of your SD card.
2. Download this version of "ClockworkMod Recovery - Modified for Motorola Xoom" and place it into this directory:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will your new Recovery. MAKE SURE THAT IT IS IN .IMG FORMAT.
2.) With your Xoom still connected to your PC, type the following commands into Command Prompt (open up using the same method as STEP 1) to install your new Recovery.
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
3.) Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery. If you miss this window and somehow end up booting your Xoom normally, repeat from STEP 3, section 2 onwards again. DO NOT CLOSE THE COMMAND PROMPT WINDOW.
4.)To root your Xoom, please perform the following:
"install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Click to expand...
Click to collapse
After the root flashes itself, DO NOT REBOOT YOUR XOOM!
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
6.) Reboot with CWM. Let your Xoom boot normally.
To test whether the root and flashing of CWM has been successful, type the following into your command prompt:
adb reboot recovery
Click to expand...
Click to collapse
If you are able to access the new Recovery, CONGRATULATIONS, you have successfully UNLOCKED & ROOTED your Xoom.
I would like to thank the Xoom Android community for your valuable commitment to into Xoom Android Development. Without you guys, the Xoom wouldn't feel much powerful in terms of usage. Also, I'd like to extend my gratitude to okantomi for his help when I first started out.
Those those experienced users of Xoom, please kindly help the newbies like me answer their questions in this thread. Could I also request the mods to sticky this thread for reference.
NOTE: For users who would like to revert to the original recovery, type the following into ADB: (tip provided by wontoniii)
adb shell mv /system/recovery-from-boot.p.old /system/recovery-from-boot.p
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
Reference Threads:
1.) [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
2.) [ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
3.) [Root] Universal Xoom Root - ANY XOOM ANY UPDATE

Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
This can be easily reverted with:
adb remount
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
Click to expand...
Click to collapse
In case someone could want the old recovery back without flashing anything

wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I believe your method is better, at least there's still a recovery to revert to in case something goes wrong. I'll add it to the guide. Thanks for the suggestion!
Sent from my Xoom using Tapatalk

My tool can do it automatically, check on the signature LordAIOTool, and if you guys can please test and tell me the results
---------- Post added at 08:57 PM ---------- Previous post was at 08:39 PM ----------
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I liked your idea too, will put on my tool (can I?)

XxLordxX said:
I liked your idea too, will put on my tool (can I?)
Click to expand...
Click to collapse
Sure, no prob

Thread moved to General.

This seams to be a good guide can anyone tell me if it works it is more detailed than the other guide ???? and why was it moved to general

This guide is great and easy and very updated i dont know why other people dont use it. One thing tho you should be more clear on how to reboot into recovery tell them to press volume up + power then let go then wait three seconds and after logo and press only the volume down

Having a problem with using your guide
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7

Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
dstruble said:
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Click to expand...
Click to collapse

kewlguru said:
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
Click to expand...
Click to collapse
That did the trick I figured it was something simple like that. Thanks for the help.

Superb Guide!
Many thanks, I spent the best part of a day trying various methods but found this to be the most n00b friendly
1 point it may be worth adding is to use adb you must have java installed on your pc, without you get error "adb.exe is not a valid win32 application"

first time root/flash rom question
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance

Don_Don said:
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Click to expand...
Click to collapse
Ihave similar story m8. I spent the majority of yesterday reading and learning how to root. This is by far the easiest guide to follow to ulock and root your xoom.

I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.

At which point do I back up data already on Xoom? Will there be any data loss?

Don_Don said:
At which point do I back up data already on Xoom? Will there be any data loss?
Click to expand...
Click to collapse
You have to backup your data before unlocking the bootloader, which is the VERY FIRST step.

gbenj said:
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
Click to expand...
Click to collapse
Yes you are right. Thanks for pointing that it, it could have confused some. I'll rectify that right away.

Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?

TADitto said:
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
Click to expand...
Click to collapse
Yes, this process will work regardless of your OS.

Duel booting thread Finished :)

One of my favorite things about android is being able to duel-boot os's and playing around with Linux distros ,but ive seen a drop off of them being brought to Android sadly . so im starting this thread in order to get all the duel-boot,chroot boots and all other ones into one place if i forget one please let me now and ill do my best to add it
Note these are not all native boots and i take no responsibility for anything that happens to your device, these are not mine either and the owners should be thanked im just bringing them together :victory:
Native Boots
My favorite and best (in my opinion) are the native boots Starting off is Ubuntu as a native boot
UBUNTU
The original creators in bringing Ubuntu to the Acer a500 first are right here on XDA netham45 and sp3dev The original thread can be found here Here
To start off on booting Ubuntu Natively you're going to need Root obviously and acer recovery installer which can be downloaded from the Android market
for the sake of this tutorial ill go over booting it off the internal storage :laugh:
1.Start by making sure you have 8gigs free of internal storage as this is how big the .rar is unpacked
2. after you download acer recovery installer youll need to flash this recovery Here
3. After that download all 3 of these .rar's onto your pc put them in a folder of there own and extract the first one they should all merge giving you one rootfs File1 File2 File3
4.once you get the rootfs move it to the home directory of your internal storage
5. power off your tab and boot into your recovery using power and volume- and your good to go
6.some tweaks you could do would be
For sound
Code:
usermod -a -G audio <your username here>
For cpu frequency scale
Code:
sudo add-apt-repository ppa:artfwo/ppa
sudo apt-get update
sudo apt-get install indicator-cpufreq
it will appear in you task bar on reboot best set to performance
:laugh:
Backtrack
Ive been told it works the same way but replacing the ubuntu.img with the backtrack.img which you can download from
http://www.backtrack-linux.org/
Cannot confirm this if someone tests it please reply back
BODHI LINUX
Bodhi Linux is another Linux brought to android with the dev being here on XDA apapousek Make sure to look at the original thread and thank it Here
There are to differant builds Alpha1 and Alpha2 ill be going over Alpha2
1.Start off by using gparted or any partitioning tool should work, and partion your micro sdcard make the first one as ext4 and make it at least 1.5gb name it bodhi make your second partition 128mb at least of fat32 format
2.mount the partitions
3.download bodhi Linux from Here
4.Extract the bodhi tarball to the root of your micro sdcard by using the commands
Code:
sudo su
cd /media/bodhi/
tar -jxvf /home/name/bodhi_alpha2.tar.bz2
5.Copy recovery.img to the second partition and flash it using Acer recovery installer from Here
6.Boot into recovery and you should be good to go
7.once booted into bodhi open terminal and type in setupwifi
CHROOT
Not as good in my opinion alot less functionality but there still fun for testing out a Linux distro and require less space without having to sacrifice your recoveryThere basically running a virtual machine on top of android to run a Linux distro all the ones I've tried have been slower so i just tend to stay away from them but feel free too XD
First of all there's a couple of different apps that will help you get it installed hassle free (for the most part)
starting off there's Linux installer standard Here
There's also Complete Linux installer with two donate versions available Here
Manual Method
There's also a more manual way of setting up chroot.
1.Make sure you have a terminal emulator Here 7zip Here and a .img file for a linux distro ill put up backtrack since it seems to work well make sure you get the ARM version of Backtrack And finally Android VNC Here
2.Download the .Img file of your choice in this case Backtrack 5 and extract it once this is done you will get another folder with bt5.img.gz and a whole other bunch files right click on the bt5.img.gz and go to extract here now copy them all into a folder called BT5
3.copy the folder called BT5 to the internal storage of your device it will be around 5gigs
4.Make sure you have Root access and busybox installed
5.Now open up your terminal emulator app and type in
Code:
su
cd/sdcard/BT5
Then hit enter and type in
Code:
sh bootbt
You should see [email protected] if it worked if it did then you can go ahead and use BT5 commands or you can get a gui by typing in.
Code:
tightvncserver -geometry 1280x800
Hit enter then type in
export USER=root
hit enter then
vncpasswd
Now its going to ask you for a password just create any random one and then verify it . After that it will ask you if you want to create a view only password hit n
6.Finally open VNC android you'll have nickname which doesn't matter port which is usually 5901 if that doesn't work try 5902 or 5903 address leave bank and make sure your connected to [email protected] just hit connect and your done one final thing to remember though is when you want to exit you have to go back to terminal and type in exit to shutdown
WINDOWS
WINDOWS95
windows is actually run through an app which emulates it i believe it has little to none drivers instaled and you cant really do much that ive found but its fun to mess around with and show off :laugh: to get this up and running is pretty simple all you have to do is.
1.Download this .rar HERE
2.Extract the folder to get a sdl.apk and a folder called sdcard move both of them to the root of your sdcard
3install the .apk and open it when shutting down though you have shutdown the right way by hiiting shutdown if you dont on reboot youll get a scandisk error
WINDOWS XP
Windows xp is even slower more useless and way more complicated to run BUT its still kinda cool to have
1.First you'll want to download everything you'll need bochs for android from HERE Sdl.zip from HERE Bochs for pc from HERE and Qumu manager for pc HERE. Last thing you will need is a windows xp.iso file not .img but .iso (ide post one but i read somewhere its ilegal to post .iso for windows :/ )
2.Download and install boch's for android on your tablet then move the SDL.zip to the root of your SDcard
3.Install Boch's and Qemu manager onto your pc
4. what you going to need to do is run a virtual machine with the .iso you have so first thing you'll want to do is once you install Boch's for your pc hit the start button then go to all programs and find the Boch's folder inside of that folder there should be a program called Disk image creation tool.
5. Next type in hd then hit enter, after that type in flat then hit enter ten after that its telling you what size you want it to be usually windows xp doesnt need more than 1.5gb so type in 1500 and hit enter then finally type in c.img and hit enter.
6. Now you want to open Qemu, once inside Qemu you want to start a new virtual machine do this by going to the vm tab and click on new virtual machine.
7.you can give it any nickname it doesnt matter just give it one and hit next.
8.Now it wants to know how much ram you want to allocate to this virtual machine 512mb to 1gb is usually fine pick and hit next.
9. Then hit finish now what you want to do is install the .iso to the blank image file but you need to specify what it is so go to the drives tab, click on Harddisk zero.
10.now you have to find the file c.img its usually located in program files/bochs you might have to make sure all files is selected in your file type bar.
11.Select thec.img file and hit ok
12. Now you want to click on your cd-rom that is your windows xp.iso file so browse and find your windows xp.iso and click ok.
13.Now your ready to run your virtual machine just hit the run button (green one) and if everything went alright you should see it start to boot up.
14. Now you'll have some on screen prompts make sure you follow them and choose ntfs file system when it prompts you to. (process will take 30min+ depending on computer speed)
15. Once your installation has been completed and your at the desktop you want to stop virtual machine. click yes end session. (i know right all that time just to spend two seconds in it)
16.Now you want to find the c.img file which is no longer blank and has windows xp installed to it. Usually in program files/bochs copy it then paste it inside the folder called sdl on your sdcard. If there is already a c.img inside of it just overwrite it.
17.okay almost done (i promise ) your going to want to copy all this code
Code:
megs: 256
cpu: count=1, ips=6000000, reset_on_triple_fault=1, ignore_bad_msrs=1
# filename of ROM images
romimage: file=BIOS-bochs-latest
vgaromimage: file=VGABIOS-lgpl-latest
vga: extension=cirrus, update_freq=25
pci: enabled=1, chipset=i440fx, slot1=cirrus
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata1: enabled=1, ioaddr1=0x170, ioaddr2=0x370, irq=15
ata0-master: type=disk, path="c.img"
#ata0-slave: type=disk, path="d.img"
#ata1-master: type=disk, mode=vvfat, path=/sdcard/HDD, journal=vvfat.redolog
#type=cdrom, path="CD.ISO", status=inserted
boot: c
config_interface: textconfig
#display_library: x
# other choices: win32 sdl wx carbon amigaos beos macintosh nogui rfb term svga
log: bochsout.txt
sb16: enabled=1
mouse: enabled=1
sb16: wavemode=1, dmatimer=500000
clock: sync=none, time0=1
Now go to your sdcard/and go the sdl folder and find the bochssrc.txt file overwrite everything in that file with the lines of code you just copied
The megs value at the top is how much ram you want to allocate to windows xp
18 Save te text document and your ready to run windows xp just open up bochs on your phone
Miscellaneous
These are all the os's that ive found that have been duel booted but are not worth it or a tutuoriol was never released will update it as i find them.
so far the only one i know of is Armedslack thsnks to hellvy from what i know of its the same way as bodhi linux but using armedslack packages
MAC OS
Im trying to figure out old mac os and newer ones right now ill be righting a tut once i get it figured out

Just adding another distro. I'm running ARMEDslack. You can use BODHI LINUX approach for installation, but use armedslack's Mini root filesystems instead. For me, there's so many stuff i have to do after installation (mainly recompiling apps & libs) and i'm not sure if anyone interesting in Slackware distro this day. So i'm not recommend this distro unless you have too much free time and know how Slackware work
Another thing, is there anyone get nvidia display driver works? i can't see any practical step to get it working, just ac100 display driver unbuntu package. If anyone get it working, pls share xorg.conf to me

Does ext4 partition has to be the first partition or second to boot bodhi because vfat as second partition cannot be recognized by cwm recovery and I cannot copy any files from internal to external sdcard

el.quechon said:
Does ext4 partition has to be the first partition or second to boot bodhi because vfat as second partition cannot be recognized by cwm recovery and I cannot copy any files from internal to external sdcard
Click to expand...
Click to collapse
first and its not meant to be copied you haven to dd it to it sorry you can't just copy it directly i don't think and fat32 is what the second partition needs to be

gears177 said:
first and its not meant to be copied you haven to dd it to it sorry you can't just copy it directly i don't think and fat32 is what the second partition needs to be
Click to expand...
Click to collapse
it booted in to terminal but usb port didnt work so couldnt use keyboard

No need to flash the kernel to recovery partition, use my dualboot bootloader.

It booted ok for me but it wont let me login at all
Sent from my LG-MS695 using Tapatalk 2

I have a couple questions...
How well does Linux(mainly Ubuntu) run on the A500? Like is it smooth and all the various controls work well.
Does the HDMI out work? If so can you extend the desktop through the HDMI out to another screen. Like have two different windows on each screen.

Drewmungus said:
I have a couple questions...
How well does Linux(mainly Ubuntu) run on the A500? Like is it smooth and all the various controls work well.
Does the HDMI out work? If so can you extend the desktop through the HDMI out to another screen. Like have two different windows on each screen.
Click to expand...
Click to collapse
I'm not sure bout hdmi if you do all the tweaks it runs reasonably well but won't run games and still lags when opening huge programs i had it for a couple of months for the most part you can install whatever you want some programs have missing repositories and you would need to create you own but there not that common i used it for compiling c+ as i need the multiwindow to do it but it will most likely crash if you try to update it i updated it to 12.04 successfully but was then having wifi problems you wil need an external usb keynoard to set it up at first when you boot up click on the top right corner and connect to wifi before doing the setup saves you a couple of steps

gears177 said:
I'm not sure bout hdmi if you do all the tweaks it runs reasonably well but won't run games and still lags when opening huge programs i had it for a couple of months for the most part you can install whatever you want some programs have missing repositories and you would need to create you own but there not that common i used it for compiling c+ as i need the multiwindow to do it but it will most likely crash if you try to update it i updated it to 12.04 successfully but was then having wifi problems you wil need an external usb keynoard to set it up at first when you boot up click on the top right corner and connect to wifi before doing the setup saves you a couple of steps
Click to expand...
Click to collapse
gears177 can you tell me how did you fix wifi after upgrading to 12.04, are you using the ubuntu image from netham and while upgrading did you have any trouble with the packages related to plymouth

el.quechon said:
gears177 can you tell me how did you fix wifi after upgrading to 12.04, are you using the ubuntu image from netham and while upgrading did you have any trouble with the packages related to plymouth
Click to expand...
Click to collapse
i never did fix it i tried everything i could think of nthing worked i dont know it seems that its not even turning on your wifi card i dont know maybe mess around in terminal and try to turn it on with wlan0 up or whatnot im not sure maybe if i get some free time ill try again as for updating i did it in small amounts and i didnt update everything im not sure but i did have a couple of errors they might of been related to plymouth

gears177 said:
i never did fix it i tried everything i could think of nthing worked i dont know it seems that its not even turning on your wifi card i dont know maybe mess around in terminal and try to turn it on with wlan0 up or whatnot im not sure maybe if i get some free time ill try again as for updating i did it in small amounts and i didnt update everything im not sure but i did have a couple of errors they might of been related to plymouth
Click to expand...
Click to collapse
Thats it plymouth i dont know why it keeps failing to instAll and i tryed that thousand times upgrading it always break wifi
Sent from my LG-MS695 using Tapatalk 2

el.quechon said:
Thats it plymouth i dont know why it keeps failing to instAll and i tryed that thousand times upgrading it always break wifi
Sent from my LG-MS695 using Tapatalk 2
Click to expand...
Click to collapse
try installing it manually might work

sorry it took so long guys but its finally done for the most part

does netham have a source code for his kernel

el.quechon said:
does netham have a source code for his kernel
Click to expand...
Click to collapse
maybe in the original thread i didnt find one but then again i didnt really look
http://forum.xda-developers.com/showthread.php?t=1158260

Great work man! I am so happy as a huge ubuntu fan to have this tutorial here for my beloved device.
Sent from my A500 using xda app-developers app

Hey guys is there a script like v6supercharger for ubuntu
Sent from my LG-MS695 using Tapatalk 2

lifeofcoding said:
Great work man! I am so happy as a huge ubuntu fan to have this tutorial here for my beloved device.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Thanks
el.quechon said:
Hey guys is there a script like v6supercharger for ubuntu
Sent from my LG-MS695 using Tapatalk 2
Click to expand...
Click to collapse
I dont believe so someone could always make one....

Backtrack works natively.
If you go on kernel-xp website there is a RTL8187 kernel for chroot which works well. Its based on acer ICS source code
Sent from my Galaxy Nexus using xda premium

[Q]How to extract CPUID from bricked A500

My partner has a bricked A500. It will NOT boot so any utilities utilising adb/dmesg fail. I can boot into fastboot mode (v0.03.11-ICS) but fastboot returns USB write errors stating invalid partition format "." So, I assume I have to use nvFlash to re-write the partition table but this still requires the SBK that I can not generate as I do not know what my CPUID is.
I have read so many threads all offering tweaked variations of the same process but I haven't found as yet a definitive how-to on re-creating your CPUID/SBK on a bricked device as they all assume you either know your CPUID or the tablet stills boots so you can retrieve it easily.
Does anyone have any links to resources to assist? I currently can boot into fastboot and APXmode. Attempts to factory reset seem to kick off OK but then fail with errors erasing data/cache etc... I have both windows/linux and the tablet is recognized in APX/fastboot mode on both OS's.
Thanks

1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE

Error: Failed to open device
Dr.GM said:
1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE
Click to expand...
Click to collapse
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!

dishoom said:
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!
Click to expand...
Click to collapse
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.

Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse

dishoom said:
Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse
Well, if I'm not mistaken, it should be 16. You can try it either way.
Click to expand...
Click to collapse

SUCCESS!!
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:

dishoom said:
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:
Click to expand...
Click to collapse
Speaking for the rest of the mentions, you are most welcome.

[GUIDE][Dual Boot][TheEasyway] How to setup Linux RootBind Method [Updated May 16th]

Hello everyone ! I made this guide for all who want to try to dualboot Android and Ubuntu using the RootBind method.
But first, what is RootBind ?
Actually, the RootBind method consist to have a Linux file system, living in a folder of our Android partition.
The default location for this linux file system is /data/linuxroot.
The way to switch between Android and Linux is to flash an Android kernel or the linux kernel. That's all.
It means you'll be able to have a linux installation, without erasing Android ( Still available, not touched at all ) and it means that you can easily manage your Linux installation.
You dont want it anymore ? Just delete a folder. You want to try another version, but you dont want to lose your current data ? Just do a zip of the folder, and extract a new version instead.
Advantages :
No need to repartitionate your tab.
It works with all TF101.
It doesnt touch current Android Installation.
It has same free space as your /data Android partition.
You can easily access it from within Android.
It has good performances
Kernel has everything working
And you only need to flash an Android or Linux Kernel to boot desired OS.
Everything is possible thanks to @jrohwer and @DjDill and @TravellingGuy.
Dont forget to thanks them : jrohwer Kernel Thread - jrohwer 14.04 Kubuntu IMG / DjDill images thread / TravellingGuy Image thread​Of course, every manipulation is risky, Me, jrohwer, DjDill, Travelling Guy, my dog, or even my math professor, can NOT be responsible for any damage on your tab, use this guide at your own risk​First Post : Dualboot setup
Second Post : How to change the linux location / How to have multiple linux installations
Third Post : FAQ & Tips​
DualBoot setup. Linux installation
First of all, here is all what you'll need :
The last rootbind kernel : Download Here Take the zip version.
[*]WARING : Note that if you use the last kernel ( 15 one ) YOU MUST TAKE MODULES AND EXTRACT IT IN /lib/modules/ when installation is done
The last Linux IMG of your choice, DjDill made imgs for this method with everything pre working here : DjDill images thread / TravellingGuy Image thread / jrohwer 14.04 Kubuntu IMG
Kernel for booting back Android You can find the KatKiss kernel there for exemple : KatKernel
A terminal emulator in Android or ADB Shell
If you dont want to use one of DjDill img, you'll need the bcm4329 tar from there : http://forum.xda-developers.com/showpost.php?p=43203818&postcount=569
You need to have a rooted device with a custom recovery. Check by here or by there
This method works on any TF101
Note that all command can be done with ADB shell aswell.
If you choose to install one of DjDill img :
Boot to Android as usual
Copy all download files to your tab. You can rename the kernel zip to Linux_Loader.zip and Android_Loader.zip to be clearer.
Now, I assume you have files in internal storage ( change sdcard0 by sdcard1 if it's on microSD )
We will now ensure terminal has root permissions :
Open Terminal emulator
Type su then Enter
SuperUser will ask terminal emulator root permission, allow it.
If you have an error with this command, your device may not be properly rooted.
Now we will setup installation location and extract our linux tar.gz ( Be aware it may take a while ) :
Code:
busybox mount -o remount,rw /
mkdir /data/linuxroot
chmod 755 /data/linuxroot
cd /data/linuxroot
tar -pxvzf /storage/sdcard0/yourubuntufilename.tar.gz
busybox mount -o remount,ro /
If you don't choose to install one of pre configured img :
Boot to Android as usual
Copy all download files to your tab. You can rename the kernel zip to Linux_Loader.zip and Android_Loader.zip to be clearer.
Now, I assume you have files in internal storage ( change sdcard0 by sdcard1 if it's on microSD )
We will now ensure terminal has root permissions :
Open Terminal emulator
Type su then Enter
SuperUser will ask terminal emulator root permission, allow it.
If you have an error with this command, your device may not be properly rooted.
Now we will setup installation location and extract our linux tar.gz ( Be aware it may take a while ) :
Code:
busybox mount -o remount,rw /
mkdir /data/linuxroot
chmod 755 /data/linuxroot
cd /data/linuxroot
tar -pxvzf /storage/sdcard0/yourubuntufilename.tar.gz
cd /data/linuxroot/lib/firmware
tar -pxvzf /storage/sdcard0/bcm4329.tar.gz
cp nvram.txt nvram_3429.txt
busybox mount -o remount,ro /
The setup is now complete.
In order to boot your linux installation, flash the linux kernel.
To get back to Android, flash the Android kernel.
​

How to change the linux location / How to have multiple linux installations
Here we are, so in order to have multiple linux instllations or change defaut linux installation location, you will need a Linux computer. ( Or a Virtual Machine, that's what I use, with Virtual Box for exemple.
You will need 3 tools to get it done too.
You can get it there abootimg, blobpack and blobunpack files at the end of first post ( Thanks to @shaola ).
I post the zip in attachement for mirror.
MORE INFORMATIONS ABOUT THESE TOOLS : http://forum.xda-developers.com/showpost.php?p=13713619&postcount=3
Now you have to get in the Rootbind kernel, the blob file. Blob file in Asus ROM can contain any partition of the device ( System, kernel, recovery etc ). In this kernel blob, there is only the kernel partition. Soooo, here we go for some commands.
Open your linux computer
Place all four files in same place ( better to have a folder created for this ). I'll take exemple of ~/kerneltf/ It's a exemple, so adapt in consequencies of course.
Now you have your four files in same place, blobunpack, blobpack, and abootimg-i686 so let's start with commands :
Go to the desired place :
Code:
cd ~/kerneltf
Unpack the blob containing partition imgs
Code:
./blobunpack blob
This will create partitions img. The one that interest us is the .LNX partition. ( Here blob.LNX )
Now unpack the kernel parition img
Code:
./abootimg-i686 -x blob.LNX
This will create 3 files, bootimg.cfg, zImage and initrd.img
The file we want to edit is bootimg.cfg. so open it with a text editor.
You'll see the last line is a cmdline. At the end we have the location of linux system place.
For exemple here : root=/dev/mmcblk0p7 bind=/linuxroot that means, the folder takes place in mmcblk0p7 ( /data partition of device ) and is placed in /linuxroot folder. So with Android layout it means /data/linuxroot.
You can now change the location of your folder, so you have some choices :
1-Change the folder location or name. ( This can be used to have multiple linux systems )
So you have this part : root=/dev/mmcblk0p7 bind=/linuxroot
If you want to change folder place/name change this part : bind=/linuxroot into whatever you want
For exemple root=/dev/mmcblk0p7 bind=/linuxroot2 or root=/dev/mmcblk0p7 bind=/linuxroot3 ( To have more linux systems )
Or root=/dev/mmcblk0p7 bind=/Linuxroot/Linux1
ATTENTION as said in rootbind thread : Make sure, however, not to put the Linux rootfs to the "internal storage" (/data/media) or any subdirectories thereof. This plays havoc with the Android media scanner when re-booting into Android and your tablet may slow down to a crawl.
2-Change the folder location in order to have it on an other partition like SDCard
For this choice, a 2nd partition on your SDcard is greatly recommended and should be in ext4. ( Must be the second partition, it is better for general use of SDcard )
So root=/dev/mmcblk0p7 bind=/linuxroot will become root=/dev/mmcblk1p2 ( can be p3 p4 or more if you have more than 2 partitions in your sdcard to have several systems on your SDcard ) the bind argument must be deleted as it will not be used.
3-Change the folder location in order to have it on first partition on SDCard
The problem here if you want your linuxroot folder in you SDcard with your other files, is that sdcard MUST be formatted in ext4 and so will not be recognized directly by Windows ( Using MTP in the TF will work but not Storage Mount ) cause Windows doesnt support ext4 partition. It's definitively the worse choice IMHO. The precedent process is definitively better choice. More than that it could make MediaScanner in Android going crazy too ( a .nomedia can maybe do the trick but not sure ).
More again, it hasnt been tested at all so you're the only responsible, but if you want to do it :
For exemple, to put folder on SDcard, you should change root=/dev/mmcblk0p7 bind=/linuxroot to root=/dev/mmcblk1p1 bind=/linuxroot
This means your folder is in sdcard ( The one in the tab ) at root in /linuxroot folder. ( /storage/sdcard1/linuxroot in android )
THIS HAS NOT BEEN TESTED YET, I CANT TELL YOU IF IT WORKS OR NOT.
Sooo, now you seted up your new location ( BE SURE TO DONT TOUCH ANYTHING ELSE ON THE CMDLINE, ONLY THIS PART ):
We will now repack the kernel to get it flashable.
Once again, be sure that you didnt make mistake with the file, and you only edited root=/dev/mmcblk0p7 bind=/linuxroot this part without deleting something or got a typo error.
We will now update the new bootimg :
Code:
abootimg-i686 -u blob.LNX -f bootimg.cfg
Then we will rename old blob file to create a new one with our modified kernel:
Code:
mv blob blobold
Now, we will repack our blob in order to make a new flashable zip with our kernel:
Code:
./blobpack blob LNX blob.LNX
You're done, make a copy of the old zip, rename it as you wish ( avoid spaces in the zip title ) for exemple Linux_Loader_2.zip
Then open it, and replace the blob file with your new one.
Now you're good to flash. Be sure to install a linux system in desired location before flashing it of course. See post 1 for this !

And a last one !
Envoyé de mon Nexus 4 en utilisant Tapatalk

Nice does work with TF101 G model (3G+) ?
Envoyé depuis ma TF101G-B80 with Revolution HD 4.0 (3.6g release) by Mike _1986

stephane.papin said:
Nice does work with TF101 G model (3G+) ?
Envoyé depuis ma TF101G-B80 with Revolution HD 4.0 (3.6g release) by Mike _1986
Click to expand...
Click to collapse
Yes, it works with all TF101
Si t'as besoin d'aide, hésite pas à me MP

Is a bootloader within the realm of possibility?
Thanks for the write-up.. I'm at the drinking my coffee while the untar keeps chugging stage, and it occurs to me that a bootloader would be very cool to have. Kernels flash so quickly, the recovery method isn't far off in terms of usability.. but it did motivate the question: is it possible?
So I'm just curious - is there any reason why we couldn't have the android and linux kernels both on disk to be loaded by a bootloader based on user choice?

Hello,
I have tried the "DjDill img" method.
When it finishes booting, it tells me that there are networks, and yhat I have to configure wifi.
I can't find how.
ifconfig shows lo and wlan0, and wlan0 is up but of course has no address.
if I try a iwlist scan, it tells me that wlan0 is an interface that doesn't support scanning.
In "settings manager/network connections", if I try to add a connection, it doesn't see my ssid.
Do you have any idea or point me to some doc/tuto.
Thanks in advance
nbenm

nbenm said:
Hello,
I have tried the "DjDill img" method.
When it finishes booting, it tells me that there are networks, and yhat I have to configure wifi.
I can't find how.
ifconfig shows lo and wlan0, and wlan0 is up but of course has no address.
if I try a iwlist scan, it tells me that wlan0 is an interface that doesn't support scanning.
In "settings manager/network connections", if I try to add a connection, it doesn't see my ssid.
Do you have any idea or point me to some doc/tuto.
Thanks in advance
nbenm
Click to expand...
Click to collapse
What kernel and what image did you used?
Tapatalké depuis mon Nexus 4 MIUI !

Couple questions
First, BIG thx to you and all the devs for hacking the tf-101!!
I've tried several of the images and they all worked as posted (Go figure ). I will be trying to compile a kernel for some custom work.
1 - Are the kernels compiled on the TF-101 and the tarballed?
2 - Any idea if Kali Linux 1.0.6 ARMHF Image, build will work?
I'll be using an external wifi dongle and not the internal.
Again much excitement to the tf-101 world!

Kingzak34 said:
What kernel and what image did you used?
Tapatalké depuis mon Nexus 4 MIUI !
Click to expand...
Click to collapse
I'm using kernel:Ubuntu-3.1.10-12-rootbind-oc1.0GHz.zip from your rootbind kernel link
I use image:tf101-14.04-xubuntu-armhf.tar.gz which is a DjDill image.
Before you reply me, I wanted to try "TravellingGuy Image". On its page, it was told to create wlan0 entry in the interfaces file. I did this and it works now.
But I can't understant why:
- iwlist scan doesn't work
- network manager doesn't see any of the multiple essids tahere are here
When I try to iwconfig essid "my_ssid", it says "cannot read /proc/net/wireless". Does it need some module ?
Thanks
nbenm

nbenm said:
I'm using kernel:Ubuntu-3.1.10-12-rootbind-oc1.0GHz.zip from your rootbind kernel link
I use image:tf101-14.04-xubuntu-armhf.tar.gz which is a DjDill image.
Before you reply me, I wanted to try "TravellingGuy Image". On its page, it was told to create wlan0 entry in the interfaces file. I did this and it works now.
But I can't understant why:
- iwlist scan doesn't work
- network manager doesn't see any of the multiple essids tahere are here
When I try to iwconfig essid "my_ssid", it says "cannot read /proc/net/wireless". Does it need some module ?
Thanks
nbenm
Click to expand...
Click to collapse
Ubuntu-3.1.10-12-rootbind-oc1.0GHz.zip doesnt exist ?
It's Ubuntu-3.1.10-12-rootbind-oc1.2GHz.zip
Or Ubuntu-3.1.10-10-rootbind-1.0GHz.zip
If you choose the Ubuntu-3.1.10-12-rootbind-oc1.2GHz.zip, wifi will works by default with defaut network manager without needing any cmd config or anything on pre installed DjDill img, IDK for Travelling guy img I didnt tested it, but you can try the other method if you're on Debian img and wifi doest work.
If you choose DjDill img, choose one of the lastest, This one http://forum.xda-developers.com/showpost.php?p=50335555&postcount=1
Or the 1.1 14.04 one, end of this post : http://forum.xda-developers.com/showpost.php?p=50335574&postcount=2
Or the Lxde build from same post.
But I suggest to use the first for now, it's the newer and have a lot of fixes.

Updated !
With second post and added jrohwer 14.04 IMG !

image: Kubuntu 14.04 With Tegra drivers.
kernel: Ubuntu-3.1.10-12-rootbind-oc1.2GHz.zip also tried Ubuntu-3.1.10-10-rootbind-1.0GHz.zip
It boots into KDE fine now but initially had some warnings even after running depmod -a. I had to issue the comnmand depmod -a a few times and it black screened once on boot.
I cant seem to get the wifi networking working even though it finds local networks clicking on the networks in the GUI doesn't do anything. Any help here. This is my first linux boot on the transformer but I have used Ubuntu since gutsy. I have to admit I am a little confused after reading a couple of posts here about exactly comes with these premade images. For instance the nvidia drivers are they included as modules in these images. When i read jrohwer's thread for the image he includes his apt sources list and states that the it took a little to get the nvidia drivers working?

Like I said on the other thread to setup Wi-Fi you have to setup in cmd line. Search on the net to setup with nmcli command or you install another network manager
Tapatalké depuis mon Nexus 4 MIUI !

Kingzak34 said:
Like I said on the other thread to setup Wi-Fi you have to setup in cmd line. Search on the net to setup with nmcli command or you install another network manager
Tapatalké depuis mon Nexus 4 MIUI !
Click to expand...
Click to collapse
Yes sorry I was struggling with the command for nmcli. I should have elaborated ... Tried various commands .. and this was what worked.
Code:
nmcli dev wifi
to list off the possible availables ap's then to join what you want
Code:
sudo nmcli dev wifi connect "whatever ap u want to connect to"
much easier to hunt down answers with a working intenet connection
Sorry bout that. I suppose my other question about the nvidia drivers is most likely too silly to answer ??

dasbooter said:
Yes sorry I was struggling with the command for nmcli. I should have elaborated ... Tried various commands .. and this was what worked.
Code:
nmcli dev wifi
to list off the possible availables ap's then to join what you want
Code:
sudo nmcli dev wifi connect "whatever ap u want to connect to"
much easier to hunt down answers with a working intenet connection
Sorry bout that. I suppose my other question about the nvidia drivers is most likely too silly to answer ??
Click to expand...
Click to collapse
What question ?
You dont have to do anything with the driver as in 14.04 build from jrohwer, is pre installed.

Kingzak34 said:
What question ?
You dont have to do anything with the driver as in 14.04 build from jrohwer, is pre installed.
Click to expand...
Click to collapse
Thanks i was reading jrohwer's thread for the 14.04 image and he was discussing the fact that it took alot of work to get the nvidia drivers up and running and then gives his apt sources list for download but after what u said it sounds like this is for people who want to get there own images together with working nvidia drivers. So compiling your own modules. Sorry I just wasnt sure. Anyways thanks for the trouble. I have connected to the ap but cant get a connection out to the internet. Oh well maybe I will try that lubuntu image on the first page. Thanks

dasbooter said:
Thanks i was reading jrohwer's thread for the 14.04 image and he was discussing the fact that it took alot of work to get the nvidia drivers up and running and then gives his apt sources list for download but after what u said it sounds like this is for people who want to get there own images together with working nvidia drivers. So compiling your own modules. Sorry I just wasnt sure. Anyways thanks for the trouble. I have connected to the ap but cant get a connection out to the internet. Oh well maybe I will try that lubuntu image on the first page. Thanks
Click to expand...
Click to collapse
Sounds weird, you successfully connected but dont have access to internet ?
Correct command for connecting on AP with a password is
sudo nmcli dev wifi connect <ssid> password <password>
And yes, the files that jrohwer gave, is for those who want to create a 14.04 with nvidia driver working img.

Kingzak34 said:
Sounds weird, you successfully connected but dont have access to internet ?
Correct command for connecting on AP with a password is
sudo nmcli dev wifi connect <ssid> password <password>
And yes, the files that jrohwer gave, is for those who want to create a 14.04 with nvidia driver working img.
Click to expand...
Click to collapse
Ya its at a hospital with no wpa type encryption only a login web page with name and password. I am most certainly connected ifconfig shows I have pulled a IP address etc etc. I have been reading about similiar problems in other linux type threads where there is automatic redirection to the login page. I actually use an app hellowifi to automatically enter the info in katkiss 4.4.2 so I am actually having trouble getting the address of that login page lol. I will give it a try at home where i have a wpa2 encrypted connection

dasbooter said:
Ya its at a hospital with no wpa type encryption only a login web page with name and password. I am most certainly connected ifconfig shows I have pulled a IP address etc etc. I have been reading about similiar problems in other linux type threads where there is automatic redirection to the login page. I actually use an app hellowifi to automatically enter the info in katkiss 4.4.2 so I am actually having trouble getting the address of that login page lol. I will give it a try at home where i have a wpa2 encrypted connection
Click to expand...
Click to collapse
Ho yeah I see, sometimes I cannot get login at the university hotspot, cause it doesnt want to redirect to login page.
I dont think you'll got problem with a 'normal' router.