Ok, so following on from the MeeGo thread, I have Ubuntu booting on the Nexus S using the same method and same kernel.
The Ubuntu image used is the HD2 Ubuntu image (v 0.3), loaded from a file on the internal memory (again, no flashing required - you can thank me later).
The touchscreen isn't yet working, but that's my kernel at fault. Will fix that with the MeeGo stuff.
If you want to try this yourself, first grab yourself a copy of Ubuntu for HD2, and take just the rootfs.ext2 file and drag it to your Nexus S (put it in a folder called 'ubuntu' - lowercase is important!).
Then use fastboot to boot the following image (or flash it to recovery partition if you're daring and know how dangerous that can be):
http://dl.dropbox.com/u/8657343/bootUbuntu.img
You will need to do one minor edit once the device is booted; you will see the screen output is very weird; ADB push the following file to /etc/X11/xorg.conf, and then reboot Ubuntu:
http://dl.dropbox.com/u/8657343/xorg.conf
If you're in any way interested, please click the thanks button! Otherwise, enjoy!
nice!
the next thing we'll need after getting the touch screen working
is to have a calling app daemon, and make sure internet works on both 3G and WiFi
nice, look same at Ubuntu Netbook Edition
What about Galaxy S?
Njcki said:
What about Galaxy S?
Click to expand...
Click to collapse
In theory the same stuff should work; I don't have a Galaxy S to test on or I'd try it. I don't know anything about the Galaxy S' bootloader, or how much the kernel would differ (I'm guessing not at all, since this is a stock Samsung kernel from the Android kernel source)
I did an article on my site http://www.android-ita.com/dev-port-di-ubuntu-sul-nexus-s/
Maybe some italian devs, will help you
Thanks for this, gonna have a play now
Why is it dangerous to flash the boot image to recovery? Isn't fastboot lower level than recovery, or have I got that wrong?
nice, thanks. trying this as soon as my wife gets off my phone.
Oh my god.. You are awesome good sir. Will give it a run when touch is up and running!
I'd love it to be run from Android....i dont want it natively, just to test it...booting for example from an android app
I would love to know if this will work on Epic 4G. I'm going to give it a shot to see what happens.
Great job
Could you give us the sources of your kernel ? Is it patched ?
Tyruiop said:
Great job
Could you give us the sources of your kernel ? Is it patched ?
Click to expand...
Click to collapse
There are no changes to the kernel at all so far. I changed the config file to enable VTs, that's it.
Ok, thank you, I'll try to build one myself
can this method be used to install android 2.3 on a phone running android 2.1,
especilly in the case when upgrading is difficult because of kernel and locked bootloader (like motorola devices) ? excuse me if it is a silly question, i'm not a coder.
would it be possible to make an app that re-boots into fastboot and runs the fastboot command. since we dont always have a comp available to run fasboot which makes this useless if your not at home, or have a laptop (in which case you dont need ubuntu on a phone)
works on Nexus One right now ?
--> ok I'm trying
It blocks on X screen of my nexus one.. before the classic bootanimation.zip
Someone have any idea about that ?
Ok, so I've got wifi working . Here is my solution. A little bit crappy but... hey... it's a start ! Also, I tried compiling the kernel with the module built in and it wont boot, and I don't know why ?
Howto get wifi :
1) Boot Ubuntu following stroughtonsmith indications
2) Download http://tyruiop.org/~tyruiop/wifi_nexuss_ubuntu.tar.bz2
3) push the vendor directory at the root. The path must remain (/vendor/firmware etc...) and the bcm4329.ko file wherever you want.
4) reboot under ubuntu
5) *optional, only if ifconfig -a doesn't show eth0* type insmod /path/to/bcm4329.ko
6) Type "ifconfig -a". An eth0 interface should appear. It's wireless. You can configure it with wpa_supplicant without a problem .
Uhm.. with Nexus One, Ubuntu blocks on X SCREEN (before the classic bootanimation).. Maybe something that I do is wrong ?
- Download HD2 Ubuntu
- mkdir ubuntu/
- put in ubuntu/ the fs on the archive I downloader
- put ubuntu/ in the SDCARD
- adb reboot bootloader
- fastboot boot bootUbuntu.img
Is it correct ?
Related
This thread is about installing Android natively on your Vogue so it completely replaces Windows Mobile.
[size +1]Important: This thread is now out of date, if you want to flash Android, use the new "norootfs" NBHs.[/size]
There are 2 installation methods:
If you are already running android from your sd card then use method 2, if you want a fresh install of android 1.5 from a windows machine use method 1.
For both methods, you must have a HardSPL installed, if you have flashed a custom wince rom before then you will, otherwise read one of the other threads on XDA about how to do this.
Method 1:
------------------------------------------------------------------
download the following:
http://www.mediafire.com/?zldjhfnkzk2
Unzip it and follow the instructions in README-ANDROID.txt.
All you have to do is copy the androidinstall.tar file to your sd card and run ROMUpdateUtility.exe on your PC.
Now Donate:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
You will also need a new rootfs:
http://it029000.massey.ac.nz/vogue/files/rootfs.zip
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
There are 3 ways to flash a rom.
1. Use ROMUpdateUtility under windows (this may not work on these roms, i haven't tried it). Rename the nbh file to RUU_signed.nbh.
2. Use HTCFlasher under Linux, this is what I have been doing and although a bit quirky, it does work. A binary that fixes a few things with HTCFlasher is on the website.
3. Rename the nbh file to VOGUIMG.NBH, put it on an SD card and boot the phone while holding down the power and camera keys.
When it starts, it should be running from nand. The tmp and cache dirs are still mounted from sd, so you do need the sd card in there but it's not really used much.
If something goes wrong or you haven't copied the correct files, press volume up while it is booting (after the two vibrates preferably). It will display a message saying that its in recovery mode. You should be able to plug the phone into a computer and the sd card will appear as a usb drive. You can also connect using adb.
There are a few limitations, rootfs must be less than 13M, system must be less than about 90M and data must be less than about 128M. This means unless you use a very stripped down system with apps2sd, hero probably won't work.
I've put a linux adb binary on the files page that fixes the annoying history 'feature' too.
Remember, this will completely wipe windows mobile and all your data from the phone. Run android from SD first to make sure you like it and don't want to be able to easily go back to windows mobile.
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Woot!
Doing this now =)
dzo said:
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Click to expand...
Click to collapse
I'm paypaling 5 bucks right now.... and I dont have a Vogue, I have a kaiser, but hey, $5 is long overdue for all the work you've done for the kernel... if NAND support hits the kaiser, I'll probably throw another $5-10 your way.
*paypaled - I normally dont do this kind of stuff, but its the holiday season, the MSM Android project has made SO much progress cause of DZO, if everyone just donated $5-10, it would at least be a nice gesture for all the work he's done*
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
If I understand correctly, theres "NO" build in here, you play with builds in your DS, and when you are ready and like one..you just use that system.sqsh data.img rootfs (provided) and..the nbh, all in the root of the sd card. And it will flash the nand with your files! So..thats it!
Nice one dzo, hoping for you to get to kaiser
Hey Martin, I can't even use these flashable images, but if it weren't for you I wouldn't even be running Android via haret, plus you've answered so many of my questions and I've never donated. So, since you're actually now, I'll donate $10.
flashing from windows
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
gswarriorfan said:
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
Click to expand...
Click to collapse
nothing that hasnt already worked works there is no change...
dj13241 said:
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Click to expand...
Click to collapse
yea camera + power + reset hole
Shidell said:
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
Click to expand...
Click to collapse
i can answer a few
1 nothing that wasnt already working this isnt a build!!!, this is a way for VOGUE users to be able to put a working build "data.img and system.sqsh" they already have working on their phone and to be able to get rid of android
2 this isnt a build
3 320x240 shows more on screen 320x428 and 320x480 show more on screen but it is a little blurry
4 you will require adb drivers located on http://code.google.com/p/vogue-android and as far as i know they work on vista 32 and win 7 32 bit and there are different ones also located at vogue-android for win 7 64b
there are adb drivers for linux in the android SDK located here http://developer.android.com/sdk/1.6_r1/index.html make sure you download 1.6r1 though! 1.5r3 doesnt work for our devices in linux
5 just reflash any wm rom (that works with vogue of course)
mrkite38 said:
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
Click to expand...
Click to collapse
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Ahhh ok I get it now. I'll still donate when I get it up and running. Thanks!
OMFG!!!! dzo you are something else!!!
I just got my Vogue a few weeks back and I am surprised on how well Android runs on this thing (I have a Raphael as well, but no comparison to this)
Having a flashable rom to a WM device... unbelievable...
Kudos for your work man!!!!
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Click to expand...
Click to collapse
I tried that and it came back in bootloader with 'RUUNBH' in the upper right corner. Then I added the task3 and it booted normally. Who knows, maybe I did something else funny.
I used htcflasher on my newly-reloaded ubuntu laptop, but I wasn't able to get it to work under windows. So I thought that maybe flashing from windows was ok, but it just needed a kick through mtty to get going.
What do those two bootloader commands do? Not that it really matters since dzo says the newest version should work from windows anyway...
egzthunder1 said:
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
Click to expand...
Click to collapse
Boot back to bootloader and flash it! Did that myself last night.
Also, how do we make a smaller data.img? I keep getting 256MB versions.
scizzle said:
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Click to expand...
Click to collapse
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Thanks you so much dzo. i got this working, now im going through all my android files on my computer to find a build that i like, and wanna keep as my main build, but one thing, does the data really have to be less than 128mb? because almost all my android builds are alot bigger which is annoying.
but other than that it worked like a charm. thanks so much.
p.s. once i get some $$ (the 15th of december [my payday]) and find a permanent build i'll send some donations for you hard work.
dzo said:
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Click to expand...
Click to collapse
Legend! Thank you. I will try it as soon as I can figure out the data.img haha.
scizzle said:
Also, how do we make a smaller data.img? I keep getting 256MB versions.
Click to expand...
Click to collapse
jamezelle said:
i used the following commands to make a new data img
Code:
dd if=/dev/zero of=~/data.img bs=1048576 count=128
mke2fs -F ~/data.img
to make a blank 128 mb data.img file in my home folder
Click to expand...
Click to collapse
- I can now confirm that flashing the nbh with the ruu works from Windows.
- dzo, I have a panel type 3 us sprint vogue. everything booted up fine, the buttons work, but the touchscreen isn't. Will post logcat / dmesg in a bit.
edit: uploaded zip w/ logcat and dmesg
Hi chaps,
I've just bought a Galaxy tab with plans to port Meego to the device.
I'm new to all the Android stuff, and tbh the myriad methods for doing this/that/the other and the relative lack of explanation of what's actually being done in these various methods/tools is quite confusing (and worrying).
So, if you'll bear with me, I have a few questions which are probably quite basic.
I've rooted my Tab using SuperOneClick, no problems there, I also understand that there is a leaked flashing tool called (Multi)Odin and an open source flashing tool called Heimdall. I understand adb.
So onto the questions:
Before I start messing about, how should I backup my existing firmware image? I see people talking about taking image dumps using dd, or Odin or Heimdall. What is the preferred method? And how should one then restore the device from these backups?
Alternatively is it possible to simply download the firmware directly from Samsung (I see links to later firmware, but really I'd be happy with what I have currently - P1000XXJK5 and FROYO.XWJJ7)?
I'm assuming that the best installation method would be to replace recovery, then I can add my own kernel and have it boot a rootfs mounted on the external SD card for example. Any thoughts?
I've seen one thread about people compiling their own kernels, with panics and the like which are solved by giving the full path to the initramfs extracted from the existing image. Any clues as to why the built version doesn't work? This is not so important as I can have a look at this when I build the Samsung source.
Is anyone looking at the bootloaders? Is there any information anywhere about them (as changing the bootloader to allow selection of the kernel to be booted would make life easier)?
Thanks for your patience!
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
lardman said:
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
Click to expand...
Click to collapse
Samfirmware get their images direct from Samsung insiders. They are not dumps.
If you want to dump from your device search "rotobackup" here in the dev forum.
Sent from my GT-P1000 using Tapatalk
alias_neo said:
Samfirmware get their images direct from Saunaing insiders. They are not dumps.
Click to expand...
Click to collapse
Ok that's reassuring.
alias_neo said:
If you want to dump from your device search "rotobackup" here in the dev forum.
Click to expand...
Click to collapse
Great, just what I was looking for, many thanks
So some more questions:
Any limit to the size of the kernel? Presumably just the size of the partition (which after extracting the image for backup seems to be a pretty large 15.4MB)?
What do all the .rc files in the raminitfs do? They are as follows: fota.rc, init.goldfish.rc, init.rc, init.smdkc110.rc, lpm.rc, recovery.rc
The init.rc is the normal init.rc file, so that's fine. Presumably the recovery.rc file is run if the bootloader detects that recovery mode is wanted (holding down keys during boot). The init.goldfish.rc? I guess this is to do with the emulator, though why it would be in a release image I don't know.
I assume that init.smdkc110.rc is automatically run somewhere along the line, though I don't see where it's started.
Any thoughts on lpm.rc and fota.rc? Are multiple .rc files run for the normal and recovery boots?
Thanks
lpm.rc is for low power mode that displays battery charging animation
goldfish is for running the rom under qemu.
backup your rom using rotobackup. compile samsung's kernel from sources, mix up default initramfs with meego's init scripts. pack all Meego stuff into loop mounted disk image. then flash zImage to kernel and your disk image to factoryfs using heimdall. I assume you have experience hacking N8xx/N900 and Maemo or Meego?
factoryfs is around 300MB so I think it should fit Meego and it (and kernel) can be easily restored with heimdall.
Thanks for the comprehensive reply
Yes I do have experience hacking Maemo/Meego, though have never really had to fiddle with init scripts before and this is as good a reason as any to learn.
I'd actually like to dual boot, so am modifying recovery.rc to bring up the Meego system on the external SD card.
Am just fiddling about building extra kernel modules now (needs btrfs for my image for example) and modifying the recovery.rc file.
Hmm, well I was all set to go and flash my new zImage and was looking for the heimdall command line, when I saw this at the top of one of the threads in this part of the forum (http://forum.xda-developers.com/showthread.php?t=870690):
Restoring to factory after using this process (you need using stock images):
heimdall flash --kernel stockzImage --recovery stockzImage --factoryfs factoryfs.rfs
Click to expand...
Click to collapse
Which has made me worry a bit that I've missed a recovery partition with its own kernel and wrongly assumed that the same kernel is used for both recovery and normal running, just with a different .rc file to be interpreted by init.
Any thoughts?
Do we trust the partition sizes reported here: http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
They seem very small for the kernel partition. I used RotoHammer's dd method to grab the contents of the partitions as a backup, so am assuming the sizes shown above are not correct (or represent something else?)
Going back to RECOVERY and ZIMAGE partitions - the ZIMAGE partition contains a recovery.rc, the question is really whether, even if they use the same zImage in both the ZIMAGE and RECOVERY partitions, the version in the RECOVERY partition is actually booted if recovery mode is selected (by holding the up volume key, etc.)? OTOH it may be that the RECOVERY partition is either empty or unused, has anyone tested specifically to see whether recovery.rc is run from the ZIMAGE partition?
Well I think I can answer my own question there, I flashed my modified kernel (modified recovery.rc) only to the KERNEL partition, and it boots normally if I don't touch anything, and just gets stuck on the first Samsung screen if I boot in recovery mode.
So it's doing something, I just can't tell what. Not sure if any kernel messages are getting lost behind that image, or perhaps they aren't even output to the framebuffer at all. I seem to remember seeing something about disabling the splashscreen so I'll go and have a look for that. Anyone got any other suggestions?
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
I see from the Nexus S port that including adbd in the image seems to be the way to go for early messages, I'll need to generate a new Meego image and have another go later on.
Interesting, I can't see that I've done anything wrong, and my extra init shell script is not started. I am trying to use the "exec" keyword in recovery.rc to start a shell script which will pass control to the Meego rootfs. At the start of my shell script I start adbd (i.e. still within the initramfs), so I should be able to tell if it has started, and it doesn't appear to do so.
Therefore I did some Googling, and I've seen that in some cases the initramfs init does not implement the "exec" keyword (http://forum.samdroid.net/f9/new-init-exec-import-implemented-3280/). This is troublesome for me as it's what I'm trying to use, but at least would explain why I don't seem to leave the init process
I couldn't see the Samsung specific source for init anywhere, has anyone found any? I'm not happy to replace it using the standard Android source as I'm guessing there's code missing which allows the bootloader to tell init how the device was started so that it knows which of the .rc files to run. Has anyone looked into this?
Thanks
Looking at the code in that link it looks pretty straightforward, just a case of parsing the kernel command line (though I might just reverse engineer the existing init first to make sure I'm not missing anything).
Would still be easier to get the actual source code from Samsung, so I've emailed their Open Source group.
lardman said:
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
Click to expand...
Click to collapse
I get it with CM
Does CM use a compressed initramfs? I'm using one of those and wondering if it's something to do with the (admittedly small) extra time required to move to init.
I don't have my Tab with me here, could someone post the output of /proc/cmdline please? You'll need to be root. Thanks.
Well it's booting you'll all be glad to hear.
More details to follow, but from memory the following were required:
Custom kernel to add btrfs support (as the image I'm booting is a btrfs partition on the external SD); kernel patch to allow compile-time cmdline to be added to the end of the bootloader cmdline (to enable console=tty0); replace Android init with init script to perform some basic setup then pivot_root to the Meego partition.
Next steps are to get the Meego system running usefully (which includes getting a terminal as currently I just have a login prompt but no way of inputting anything!) and also seeing whether I can get dual booting working with an Android system standard boot and Meego replacing the recovery boot.
Poor pic, but still: http://people.bath.ac.uk/enpsgp/Tab/PICT0040.JPG
Good stuff. Thanks for keeping us informed.
After you've got the groundwork for this done, how easy would it be to get Ubuntu running?
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
brilldoctor said:
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
That's using chroot, which I don't want. I want it running natively.
Sent from my Galaxy Tab
BACKTOP v0.00001
Click to expand...
Click to collapse
Alright, so this is a guide to finally get the backtrack 5 software running inside of webtop. It uses chroot and xterm to allow full access to the software contained within the backtrack 5 arm image.
Prerequisites:
CWM Installed:
For all version: http://forum.xda-developers.com/showthread.php?t=1138541
WebTopMOD installed:
For 2.3.4 go here: http://forum.xda-developers.com/showthread.php?t=1169457
For 1.8.3 go here: http://forum.xda-developers.com/showthread.php?t=1093790
You do not need to download the Debian disk image. Will we be using the backtrack disk image instead.
BusyBox Installed in /system/bin:
Downloaded "BusyBox Installer" from the app store.
BE SURE TO INSTALL IN /SYSTEM/BIN!
Click to expand...
Click to collapse
The Goods:
BackTop.zip:
Download and un-zip the attached files into /sdcard/bt
BackTop.zip
BackTrack 5 ARM Image:
PART 1 : Download Link : http://bit.ly/p1BT5
PART 2 : Download Link : http://bit.ly/BT5p2
PART 3 : Download Link : http://bit.ly/BT5p3
These download links are from the xperia backtrack project and where I took inspiration to get it working in webtop. After using 7z to unarchive just place bt.img in the /sdcard/bt folder. The archives other contents can be safely ignored.
Click to expand...
Click to collapse
What you should have by now:
WebTOPMOD for Atrix.
BusyBox Installed in /system/bin.
Downloaded scripts placed in the /sdcard/bt folder.
Downloaded bt.img placed in the /sdcard/bt folder.
Click to expand...
Click to collapse
Give it a go:
Step 0: Connect the phone to display/lapdock. Run webtop and wait for it to boot.
Step 1: Open LXTerminal from the dock and type "cd /sdcard/bt"
Step 2: To run BackTop type "sudo bash backtop"
You should be presented with a white xterm screen. You can now use all the utilities built into backtrack 5 with ease. You can even run the gnome desktop environment! (More on that bellow)
Click to expand...
Click to collapse
Running Gnome:
You first need to kill off all the webtop crap do this by typing the following in xterm.
"ps ax|grep awn|awk '{print $1}'|xargs kill"
"ps ax|grep panel|awk '{print $1}'|xargs kill"
Then start gnome by typing "gnome-session" in xterm.
Click to expand...
Click to collapse
Accessing sdcards:
You'll need to make two directories inside of backtrack /sdcard and /sdcard-ext to do this type:
"sudo mkdir /sdcard"
"sudo mkdir /sdcard-etc"
Once you've done this simply reboot your phone and restart BackTop.
Click to expand...
Click to collapse
Known issues:
ettercap causes network connectivity inside of webtop to fail.
If something does go terribly wrong you can always force quit backtop with the following command:
"sudo bash /sdcard/bt/forcekillbt"
Click to expand...
Click to collapse
Cool stuff, I'll definitely check this out. Moved to development.
mate I don't have webtop but as a network engineer I'm giving this a big thumbs up, super cool to have a pen testing suite in your phone!!!
reserved #10Chars
It might just be me but do your links work? Specifically the http://bit/ly ....etc. thanks
Sent from my MB860 using XDA App
edit: had a smart attck and everything is tip top...well done sir...thx!!
that is the most metal thing ever
I'd prefer it actually dual boot on my phone for hac..I mean testing on the go xD
What will this one do that the others don't?
Cheers
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
If you don't know what BackTrack is then you don't need it.
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
its a pen testing Linux suit. its essentially Linux loaded up with hacking tools meant for testing networks to prevent hacking or "penetration". hack your own network. discover the vulnerabilities. and patch them. - to put it simply
This is amazing. Thanks.
7z issue with the bt.7z
Hum... I might be doing something wrong but I am not able to uncompress the 3 volumes posted in the links... I was able to download them all but the only one who actually I can uncompress is the first one and it generate a file bt.7z that I am also unable to uncompress... I am getting the following msg when I try to 7unzip them:
"cannot open file 'x:\xx\xx\bt.7z.002' as archive"
Should I join them all into one then use 7zip?
Forget it I just found it out by myself... is using a program to join them all into one then Unzip it.
My dream come true .............. i assume that we can run kismet and metasploit framework ?!
What kernel and rom were you able to make this run well with as i am having really bad reboots after i undock the phone from the lapdock as i am running faux123 kernel and cherry crust v3.
webtop when connected to hdmi not doing anything...
I was trying to use this backtrack distro on my AT&T Atrix and I must admit that I am a kind of noob on this ... I wasn't seeing big advantage until now that we have bt to use instead of the stock version...
I have no Lapdock so I am using Ronaldo_9 CWM version to run Webtop on HDMI in my GB 2.3.4 ( 4.5.91 from Kenneth Penn ). It was working til I followed these instructions ...
Well a little bit of what I did:
1- Downloaded the WebTopMOD from Joe Ferreira v2 to install with CWM.
2- Got also BusyBox installed through the BusyBox Installer over my /system/bin
3- Downloaed (even knowing it's not needed) the Debian disk from Joe Ferreira link (to install webtopmod).
4- Downloaded the BlackTrack 5 image from the links on the first post
5- Downloaded the BackTop.zip from the first post
6- Created the /sdcard/bt folder and put only the bt.img and forcekillbt and backtop files from Backtop.zip file onto it...
7- Plugged in my HDMI cable over my tv (yes I have no lapdock)
8- The Webtop option pop's up and when I selected it.....
Nothing happened... not even an error msg or stuff... the only thing still working is EC... but webtop none.... Does anyone of you have any clue or hint of what can I do about it?
EDIT: Got it working... it was because of the broken V2 WebtopMOD so I flashed the V1 and everything went fine.... Thank you all for not helping it made me a better researcher
I think I just wet myself I've been waiting for someone to come up with this since they started the ARM archticture and ported it to the XOOM tablet
Sent from my MB860 using XDA Premium App
The built in wifi doesn't support packet injection does it?
baumerman said:
The built in wifi doesn't support packet injection does it?
Click to expand...
Click to collapse
It doesnt....
Sent from my MB860 using XDA App
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
kholk said:
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
Click to expand...
Click to collapse
That would be awesome... just amazing how u dealing with a lot of stuffs simultaneously ....... tyvm for visiting this thread its almost dead...
Doing a simple (means not a complex one) research at Google it seens that there's no much of Monitor mode for android cell phones so far... not sure why if nobody cares or if it's not possible... but u got skill enough to give the last word
Hope to hear something soon...
I wish there was more development for this, and +1 for packet injection
gzrecoil said:
I wish there was more development for this, and +1 for packet injection
Click to expand...
Click to collapse
There is monitor mode for iPhone and itouch... not sure the reason why not for android :-(
Sent from my MB860 using XDA App
I've spent some (much) time this week with trying to get ubuntu running on the optimus 2x. I have succeeded to boot and get the wifi, X11 and the touch screen sort-of working.
The ramdisk is completely replaced with a busybox executable, some symlinks to it and a shell script that mounts the necessary stuff (/dev/block/mmcblk1p2 as ext3), changes root directory and calls /sbin/init.
USING THE FOLLOWING WILL VOID ANY WARRANTY YOU MIGHT HAVE LEFT AND MIGHT ALSO BRICK YOUR PHONE!
Seriously, don't do this if you don't wish to risk the data on your phone.
I will be providing some demo images for people who don't have a build environment up and running. These images will not work particularly well, don't get your hopes up .
If you want to have a big linux installation (more than 3 GB) you can flash the images to the second partition on your external sd (obviously you have to create this yourself first). You can use the following boot image (which assumes that linux is on /dev/block/mmcblk1p2 with ext3:
https://ha.xxor.net/o2x/boot-20110813.img
I have also targzipped the modifications to the file system that were required to get stuff going here:
https://ha.xxor.net/o2x/o2x-20110813.tar.gz
This should be extracted directly to the root file system.
The kernel source code is up at https://github.com/ergoen/LG-Optimus-2x-linux-kernel
Things that have been done to get this to "work":
1. Boot partition
Apart from grabbing the busybox stuff from some nexus one boot image (I'm sorry whoever fixed it, I don't remember where I got it from ) the boot command line had to be modified a bit, changing stuff from the default usually ends up in a phone that won't boot, but I discovered that it's possible to append new arguments to the default ones. So the following have been appended:
console=tty0 root=/dev/mmcblk1p2 init=/sbin/init
The console=tty0 makes sure that you see stuff on the screen while ubuntu get's running. The last two are not necessary to boot, but ubuntu seem to like (need?) them (or at least the init=/sbin/init), since otherwise you never get to the login prompt on the screen.
2. The Ubuntu installation
To make it possible to communicate with the phone at all adbd was put into the /sbin/ folder and a symlink was created /system/ -> /. Also the "/sbin/adbd recovery &" command was added to rc.local to make it autostart.
2.1. Modules and wifi
We need the /lib/modules/2.6.32.9 directory. Most files inside that were generated using the "depmod" command, the exception is wireless.ko which was taken from android, the firmware and nvram files needed for the wifi chip to work were placed in the /lib/firmware/wl/ folder. To make the wifi module autoload with the proper firmware "wireless" was added to /etc/modules and the file /etc/modprobe.d/wireless.conf was created with the contents describing the location of the firmware and nvram.
To make the wifi autoconnect on boot the /etc/network/interfaces file was modified with the following contents:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
(To make the wifi autoconnect to your wireless you need to run the command "wpa_passphrase networkname networkpassword > /etc/wpa_supplicant.conf using adb or chroot)
2.2. X11
Getting X up by running xinit produces a simple black screen on the phone. At first I thought the problem was that the refresh rate was set to 106 Hz, indeed changing it with xrandr and pushing a new mode got me a visible xterm on Kubuntu 11.04:
https://ha.xxor.net/o2x/xterm.jpg.
On Ubuntu 10.10 it even gave me a nice colored gdm screen:
https://ha.xxor.net/o2x/gdm.jpg
But the image I got there was static and wasn't being updated. Turns out the reason the screen was black earlier with the 106 Hz rate and the reason why the screen is now just showing an image is that the framebuffer device doesn't update the screen like it should..
By modifying the kernel source to redraw the screen every 50 ms (~20 Hz) it's possible to get a scren that works. This is an ugly hack in the tegra-fb driver though, so I'm open for suggestions on how to solve it in a better way!
2.3. Touchscreen
By default the only thing the touchscreen does is force the mouse up in the left corner, I think this is due to some multitouch thing. Some more kernel hacking (basically half-disabling multitouch) makes the touchscreen work.
Pictures:
https://ha.xxor.net/o2x/SAM_0671.jpg
https://ha.xxor.net/o2x/SAM_0672.jpg
Video:
http://vimeo.com/27662093
Thans to RaYmAn and lilstevie on #tegralinux for all their help this far!
3. Misc
(K)Ubuntu 11.04 uses a new version of libc which crashes with the current nvidia kernel (2.6.32.9) on this hardware (http://developer.nvidia.com/tegra/forum/errata-657451-tls-bit-20-cp15-c13-3), so I'm going back to Ubuntu 10.10 until someone ports a newer kernel to the Optimus 2x or this problem can be solved in another way.
edit 1: Ubuntu 10.10 with much more working X11 noted in section 2.2.1.
edit 2: X11 working even more, touchscreen works aswell!
edit 3: Landscape mode works with both X11 and the touchscreen now, getting ready for alpha 1!
Current status:
Working:
- adb (best way of controlling device currently)
- X11 (only framebuffer with hardcoded refresh rate of ~20Hz)
- landscape mode fixed! =D
- touchscreen (probably only single touch)
- wifi (only when running things from console, ubuntus network manager does not recognize it)
Not working:
- Basically everything else
Alpha 1:
EDIT: Seems that multiupload has screwed up and this link was going to some crap, anyway this is not relevant anymore
Username 'ubuntu', password 'ubuntuxda'. Don't use this if you don't know how to restore the boot partition! (Or else you won't be able to boot back into android!)
Experiments:
Tried disabling the CONFIG_TEGRA_ERRATA_657451 switch in the kernel to make newer linux versions boot. This might be a bad idea in the long run, but this far things are working better than with the switch enabled..
I tried Ubuntu via chroot method posted in other thread, but I'm a noob.. Can you please explain what is different about your ubuntu?? Does it boot without Android and doesn't need VNC stuff?
Yes, it boots instead of android when turning on the phone, but it doesn't work completely, so I mostly put it up here so that people could help test and fix/hack things.
You rock! Unfortunately I'm no dev, so can't help but hopefully others will, so we'll get a fully working linux on our phone, and maybe later even meego. Is there btw drivers for the gpu? Because hdmi, with usb host ofc, would be really useful!
Anyway, good job, really!
This looks great ergoen! I'm no dev either but I can't wait until it's available to everyone, I would love to have Ubuntu running on my O2x.
Best of luck!
gpu drivers are closed source, and the ones released by nvidia require a newer kernel (2.6.38), so thats not really possible yet.
Newer kernel will be necessary anyway though, since the crashes I'm getting seems to be due to a bug in tegra which gets worked around in 2.6.36. I'm not skilled enough to perform that port though. I will of course give it a try, but most likely I'll go for some older version of ubuntu and/or perhaps meego instead.
Håller med tidigare poster. Would be awesome with native Ubuntu and Meego on the phone... keep up the good work, can't wait to follow this development.
Sent from my Optimus 2X using XDA Premium App
ergoen said:
... I realized that it tried to run the screen at [email protected], which is hmm, wrong . So setting up a script at /etc/xprofile, which makes sure the refresh rate is 60Hz...
Click to expand...
Click to collapse
What would happen if you changed this to 72Hz instead? I saw that info when I was browsing System Information in some app. Im not a dev At. All. But tell me what you think it's probably a stupid question
Sent from my Optimus 2X using XDA Premium App
I can give it a try later, not that it would make any difference .
edit: 72 Hz also seems to work, cool, that's higher refresh rate than my computer screen...
ergoen said:
I've spent some (much) time this week with trying to get ubuntu running on the optimus 2x. I have succeeded to boot and get the wifi working, also X sort-of works (software fb). I have only slightly modified the kernel (built with CONFIG_SIGNALFD=y so that Meego wont complain in a related attempt to get that os booting). The ramdisk is completely replaced with a busybox executable, some symlinks to it and a shell script that mounts the necessary stuff (/dev/block/mmcblk1p2 as ext3), changes root directory and calls /sbin/init.
USING THE FOLLOWING WILL VOID ANY WARRANTY YOU MIGHT HAVE LEFT AND MIGHT ALSO BRICK YOUR PHONE!
Seriously, don't do this if you don't wish to risk the data on your phone.
I will not provide a complete root file system for two reasons:
1. It's pretty easy to make yourself, grab the omap3 kubuntu mobile image from the kubuntu site, or use rootstock from an ubuntu installation to build one yourself.
2. My upload sucks, and putting several hundred MB onto the interwebz would hurt me.
However, I have placed an image of my boot partition here (assumes you've got ubuntu on the second partition of the external memory card formatted with ext3):
https://ha.xxor.net/o2x/boot.img
I have also targzipeed the modifications to the file system that were required to get stuff going here:
https://ha.xxor.net/o2x/o2x.tar.gz
This should be extracted directly to the root file system you aquired earlier.
Things that have been done to get this to "work":
1. Boot partition
Apart from grabbing the busybox stuff from some nexus one boot image (I'm sorry whoever fixed it, I don't remember where I got it from ) the boot command line had to be modified a bit, changing stuff from the default usually ends up in a phone that won't boot, but I discovered that it's possible to append new arguments to the default ones. So the following have been appended:
console=tty0 root=/dev/mmcblk1p2 init=/sbin/init
The console=tty0 makes sure that you see stuff on the screen while ubuntu get's running. The last two are not necessary to boot, but ubuntu seem to like (need?) them (or at least the init=/sbin/init), since otherwise you never get to the login prompt on the screen.
2. The Ubuntu installation
To make it possible to communicate with the phone at all adbd was put into the /sbin/ folder and a symlink was created /system/ -> /. Also the "/sbin/adbdb recovery &" command was added to rc.local to make it autostart.
2.1. Modules and wifi
We need the /lib/modules/2.6.32.9 directory. Most files inside that were generated using the "depmod" command, the exception is wireless.ko which was taken from android, the firmware and nvram files needed for the wifi chip to work were placed in the /lib/firmware/wl/ folder. To make the wifi module autoload with the proper firmware "wireless" was added to /etc/modules and the file /etc/modprobe.d/wireless.conf was created with the contents describing the location of the firmware and nvram.
To make the wifi autoconnect on boot the /etc/network/interfaces file was modified with the following contents:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
(To make the wifi autoconnect to your wireless you need to run the command "wpa_passphrase networkname networkpassword > /etc/wpa_supplicant.conf using adb or chroot)
2.2. X11
Getting X up by running xinit produces a simple black screen on the phone. After some troubleshooting and voodoo magic I realized that it tried to run the screen at [email protected], which is hmm, wrong . So setting up a script at /etc/xprofile, which makes sure the refresh rate is 60Hz, and running it after xinit gets you a xterm!!!
https://ha.xxor.net/o2x/xterm.jpg
Telling /etc/X11/xinit/xinitrc to run it makes sure that it gets set up properly by the startx script, unfortunately startx doesn't go through for me on kubuntu because of some weird error caused by a hardware problem in tegra: (http://developer.nvidia.com/tegra/forum/errata-657451-tls-bit-20-cp15-c13-3).
Unfortunately this (probably) means that either we'll have to stay with old versions of libc or get a newer kernel (2.6.36 contains fix). Old libc seems backwards, but porting a new kernel requires a bit more skill than I possess.
2.2.1. Ubuntu 10.10
Grabbed the image ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img.gz from http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/release/ . After first unpacking the tgz, then unpacking the raw disk image to partition images (with 7zip on windows) and then flashing the 1.img file to the second partition on my sdcard I managed to run a much more bug free ubuntu than before.
Ubuntu 10.10 (Maverick) uses an older version of som libraries that don't crash with the old o2x kernel.
This has lead to the following:
https://ha.xxor.net/o2x/gdm.jpg
Obviously touch screen isn't working properly (pressing it puts the pointer into the upper left corner :S) so can't get further than this currently.
3. Misc
avahi-daemon and cups seems to be crashing all the time and restarting, so removing them (apt-get purge if ubuntu/kubuntu) will make the boot much cleaner. Also I get lots of alignment trap kind of errors that shouldn't be there for different kinds of services, (due to tegra bug mentioned earlier).
edit 1: Ubuntu 10.10 with much more working X11 noted in section 2.2.1
Click to expand...
Click to collapse
Its good you got it to work.Saves me some work.I was gonna begin this project my self after the 19th when my exams end.Maybe i could help you.
ergoen said:
I can give it a try later, not that it would make any difference .
edit: 72 Hz also seems to work, cool, that's higher refresh rate than my computer screen...
Click to expand...
Click to collapse
Most computer screens usually support atleast 72hz also, it's just that it only works with d-sub, and sometimes only at a lower resolution.. It's possible to make special drivers to some screens to enable higher refresh rate through dvi also.
Anyway, it's good the screen on the phone refreshes at 72hz instead of 60 for android, but in linux I really don't see the benefit.. Doesn't hurt to have though. Btw, if we would stay on this kernel, can we use the drivers from android then? Shouldn't gpu also work? Or are the drivers limited and don't allow xorg for example? Sorry if it's stupid question, don't have that much knowledge how android works yet.
Update: X11 and touchscreen work on Ubuntu 10.10 Maverick with new kernel (just a few hacks )!
manasgirdhar: sure! Lot's of things to do new kernel is needed for anything newer than ubuntu 10.10, and even here things like sound etc (cpu scaling maybe too) don't work.
kruppin: actually i removed the xorg.conf now, the phone thinks its running at 106 Hz and it works. Unfortunately in practice it goes at more like 20 Hz because of the hack I made to enable the fbdev output in the kernel. Android doesn't use X11, so those drivers wont be of any use. (I will post the kernel modifications to github soon)
edit: kernel source up on https://github.com/ergoen/LG-Optimus-2x-linux-kernel
A List of Things working at 2nd Post would be nice.
So anybody could fast see Updates,...
Edit:
Have you tried some "cleaner" Linux like Debian?
Alpha 1 is up in the second post for anyone who wants to test it (don't ^^).
I have not tried debian no, I thought ubuntu would be the easiest to google errors and bugs for .
You are great! i was hopin' for this since I have mine. You should try to make usb(otg) work to get some devices going i will try to test it soon
That's amazing We have to test USB OTG function. If it works by default, I'll try this right now
It is possible to make a dual-boot: ubuntu and android?
I don't think usb otg works since I am basically using the android version of the kernel, I also won't be able to try since I don't have a cable... (will buy one sooner or later).
Dual boot probably works if you flash the boot.img onto the recovery partition instead of the boot partition (/dev/block/mmcblk0p7 instead of /dev/block/mmcblk0p5). I have not tried this though. That way regular booting would give android and booting while holding volume down would give ubuntu, only problem with this is that cwm will be gone and the only way to fix broken things would be to flash with nvflash.
well it is not a major deal if have cifs avail needs kernel support as well. Benee mentioned (might) some otg support, mayb u could ask.
also, you might give E17 a try, it is butter-fast, and has a touch module for keyboard (letter zooming.!..) LINK
this can be compiled on a lot of hw, and gives good response with fbdev non-accel drivers also.
and most linux apps work on it fine. ofc until we have 2d/3d accel and might try compiz/fusion as well
LINK
Great job ergoen!
I've worked on exactly the same some weeks ago but i never accomplished it. because i stuck creating a working ramdisk. Which toolchain do you use?
MfG
Backtrack5/Ubuntu v10.04 Up & Running On Tab 10.1
StatementHave this on my Samsung Galaxy S2 and working perfect so i figured i would give it a try on the Tab 10.1. There were alot of people who helped get this running for other devices i will mention them so dont worry. Alot of modifications had to be made in order to get this to run on the Tab because it was really made for a phone not a tablet so please follow all the steps cause there is certain code that i had to right to get the screen size to fit. Everything is fully functional and working. Finally i think this would be a nice addon to your Tab esp if your a big Ubuntu fan, I am currently working with other developers to see if we can update this so it has the new Ubuntu v11.10 but for now follow the steps and enjoy and if theres any questions or requests just write on the thread and PM me. ENJOY!!!
Disclaimer
I am not responsible for damaged devices, bricked devices, Soft bricked devices, and if you run wrong code ETC
Thanks To:DooMLoRD, anantshri, n1nj4dude, KingOfThaJungle None of this would be possible without these guys and if im missing anyone please let me know and im sorry
Before We StartThere are going to be 10 files attached at the bottom you need to download all 10, place them on your desktop for now i will explain what your going to do with them after. Next you need to download 7Zip heres the link http://www.7-zip.org/download.htmlOk now those 10 files waiting on your desktop extract ONLY 1! i chose to extract bt.7z.001 once you extract you will be given a .img file create a folder called bt and put all ten of the files inside bt including the .img so you now should have a folder on your desktop called bt with 11 files in it. Take this folder and put on the root of your Tab.Now there will also be another file attached called bt5_sgs2_shell_scripts_v2 take this file and put it on the root of your Tab. Reboot into recovery mode and wipe cache and davik cache and then flash that file once complete reboot your Tab.Once your rebooted use some kind of file explorer i used root explorer and check the /sdcard/bt folder for the following it should look like this when you explore it./sdcard/bt/bt/sdcard/bt/bt.img/sdcard/bt/installbt.sh/sdcard/bt/startbt/sdcard/bt/stopbtOnce your verify that the above if correct you can proceed
Instructions On Launching BTStart Terminal Emulator on your Tab and enter the following commands step by step.sucd /sdcard/btsh installbt.shstartbtbtNow your in Back Track 5 shell! You should see [email protected]:
Instructions On Launching VNC ServerDownload VNC Server from the marketThen still in terminal typevncserver -geometry 1280x700You then will be presented with [email protected]: againThen look under it were it says new 'X' desktop is localhost1 that it the last digit in your port number if you ever exit VNC or close terminal or reboot you will have to run some commands to get back witch i will show you in a minute but always look at that localhost # cause it will change if you reboot so pretty much if it says localhost2 your port would be 5902 get it?
Now Launch AndroidVNCEnter the following into AndroidVNCNickname: btPassword: 12345678Address: 127.0.0.1Port: 5901Username: (Leave Blank)Color Format: 24-Bit Color (4bpp)
Getting Back In After RebootType the following commands to get back insustartbtbt
Screenshots & LinksAt Bottom Thank you and Enjoy!!!
Go to this page for the 10 files http://www.mediafire.com/?f9gk3p3t9wip5
Uhm... file bt.7z.001 is corrupted!? Please check. However, thank you.
go onto the original thread and get the files from there sorry i only posted the mirrors heres the link and your welcome hope you enjoy
http://forum.xda-developers.com/showthread.php?t=1331419
Haven't tried yet but looks great, sweet!
works good. nice guide. i suggest people download bt5_sgs2_shell_scripts_v2 from the link in the 3rd post
Cool. Does the wireless "card" in this device support injection?
FillTheVoid said:
Cool. Does the wireless "card" in this device support injection?
Click to expand...
Click to collapse
I would love to know this
Sent from my GT-P7510 using Tapatalk
i believe it does but im not 100% on that
I cannot get this to work. Every time I try to install the bt5_sgs2_shell_scripts or bt5_sgs2_shell_scripts_v2, it says installation aborted. Needs to be Nandroid restored otherwise it won't boot. Any ideas?
So can i use both of honeycomb and ubuntu alternatively or together? Because in screenshots i can still see honeycomb taskbar at bottom over Ubuntu.
Nice work. And how to uninstall it?
Ok for JAYDAWGX7: are you wiping cache and davik cache before flashing and is your cwm up to date? if so and still having problem try a different kernal and get back to me
Ok for PARAG31: yes you can run bolth all backtrack5/ubuntu is doing is running threw vnc you are not loosing honeycomb you still have that as a base platform backtrack/ubuntu is just running threw vnc so to answer your question this does run bolth
I try with two diferents kernels and roms first task650 in paris v5 and other with task650 new honecomb 3.2 stock and no luck to install the zip file in recovery instalation aborted allways display. please post your roms and kernels info to migrate and run this on my gt
celtichazard said:
I try with two diferents kernels and roms first task650 in paris v5 and other with task650 new honecomb 3.2 stock and no luck to install the zip file in recovery instalation aborted allways display. please post your roms and kernels info to migrate and run this on my gt
Click to expand...
Click to collapse
Yep, same problem here. Any ideas? Any one else try this?
P7500 running Overcome 10.1 Rom, with Pershoot Kernel 2.6.36.4, with CWM v5.1.2.3. Yes with wipe of both cache.
EDIT:
After further investigation, the zip file only contains the files found in the bt folder. Just extract it to the /sdcard/bt dir. Assuming that it makes no other changes to system.
Got to [email protected], haven't done the rest yet! Will update post later.
EDIT:
Everything works after this.
Plus, i dont think monitor mode or injection works. Not without modified drivers (STILL HOPING ITS NOT THE CASE). Maybe usb? Hows usb hosting on this? Hope someone can answer these questioms.
I have a compatible wifi adapter, but no usb adapter for the tablet! I'll put it on my buy list.
Will this work on the 3G version also?
Edit: Awesome! It works perfect, thanks! Only remember to have busybox installed guys!
The correct resolution is 1280x752, so it is : "vncserver -geometry 1280×752"
also ur script isnt flashable. only thing in /data is busybox, just install busybox from market and change script
will work on 3g and wifi versions
very nice, also works on GTab 7310 (8.9 Wifi 3g)
heaven, thank you!
Awesome, works like a charm, and it blows everybody's mind.
I spent a little time on try to get capture mode to work, but gave up with the original network drivers.
I hoped it would be possible to use a normal usb wifi stick connected to the adapter, compile the drivers, and load them as modules, but i'm getting error messages when doing that, and that's where my knowledge of linux ends.
Anyone tried this yet? Any pointers? (currently flashing overcome 2.0, will try to post errormsg later)
Also, I read in one of the CarrierIQ threads that one of the pieces of the app actually uses libPcap to snoop on our asses. Would it be any help (or problem) that that's enabled in the parent OS?
Just one question: Can I use bluetooth keyboard/mouse with it? And will TrueCrypt run?