Database Users

LINUX BOOTS at OPAL! Thanks to linwizard project!

Hi there,
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.
1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.
After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.
Which IP to use to connect with OPAL I still must investigate.

Well ip connectivity now works:
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
Notas:/# ifconfig usb0 up 192.168.2.200 netmask 255.255.255.0
Listik:/usr/src/linux-2.6.27/Documentation# ping 192.168.2.202
PING 192.168.2.202 (192.168.2.202) 56(84) bytes of data.
64 bytes from 192.168.2.202: icmp_seq=1 ttl=64 time=2.95 ms
64 bytes from 192.168.2.202: icmp_seq=2 ttl=64 time=1.72 ms
And how to do it:
prolong "set CMDLINE" line with
ip=192.168.2.202:192.168.2.200:192.168.2.200pal:usb0
But in this image there doesn't seem to be any telnet/ssh server running. I will try cook image with ssh server support later

Download error
Were not able to re-upload

404 file not found error!!

http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/
and open latest gizard-<date>.tar.bz2
or that I suppose.
The latest link should be http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20090703.tar.bz2

does this mean any chance of android working? anyone tried?

Hey,
I'm a new Opal user and I'm interested in getting *nix running on my device. I still haven't had the chance to mess around with this stuff but I'm excited to see this thread.
I was looking into the possibility of running Android on the Opal and it seems the closest thing is this thread bout running it on the Herald (it uses the same processor as the Opal).
I don't any experience in Linux porting so I thought I'd share this, in case anyone else is interested. And at the same time, I'll try to see if I can get something working based on what has been/is being done for other devices.
Sorry for the long post.

Hey Folks,
Any progress on getting Android on Opal? I am eagerly waiting to load one.
Kindly let me know, if this version of Linux when loaded, gives the UI.
Cheers'
Vijay
cijoml said:
Hi there
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.
1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.
After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.
Which IP to use to connect with OPAL I still must investigate.
Click to expand...
Click to collapse

Android can boot on Opal
I have some good news, Android can boot on the Opal. This is just a proof of concept as it's missing tons of drivers and is completely useless.
Touchscreen and all keys except for the volume control (and obviously the reset button) are not working. So you basically can't do anything when you run it.
What I tried is the same as what's written in this thread about running Android on Gene. They're using the build made for the Herald/Wing (just as I was proposing in my last post) with customized initramfs and kernel.
You'll find all the necessary details in that thread. However, there's a newer build than the one mentioned there it's wing-linux-0.4pre2.cab. And the suitable kernel for that build is supposed to be the pre2 posted in this post but it didn't work on my Opal so I tried the older Gene kernel and it worked. The main difference between the two is bluetooth support, and that's obviously is of no use for us.
This doesn't effect the Windows rom, nor does it requires any special partitioning. Still it's best to have everything backed up before launching it, just in case.
This is the official site for the wing/herald build:
http://wing-linux.sf.net/
This thread on their forums about the Gene port will probably be of use to us:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4
I'm reading about the next steps but as I said before, I don't have any previous experience or knowledge about this type of things. If someone can give me hand, I would be more than grateful. At any rate, once I have better understanding of the concept I'll contact the people behind the Wing and the Gene ports.
P.S: If you do try to run this, keep in mind that this will take lots of time, specially for the first launch. And when you get an error saying something like "android sh: can't access tty" just ignore it and keep waiting. After a while you'll have a flashing "android" on the screen, and after some more waiting you'll reach the main screen.

Is this just THE BEGINNING
Sooper Stuff..!! So is this just THE BEGINNING??
How do we port the drivers and other required information in the build?
Cheers'
Vijay
www.msigeek.com

A Lil' help
I'm going through the Gene port thread here and on the Wing-linux sourceforge forums but I'm still a bit overwhelmed.
I would appreciate any help as I'm completely new to porting. I have some programming and linux knowledge but never attempted this type of things.
Click to expand...
Click to collapse
So am I.
Hmmm...
Right. Lets do it the way I did it.
1. Get the touchscreen working. Through HaRET, you must have got the GPIO interrupt whenever you pressed the touchscreen. You must have got two numbers corresponding to each press - a smaller number and a bigger number. The smaller number is the GPIO, and the larger number is, well, lets say a special GPIO value for the same pin.
Now checkout the Gene branch through git.
Goto /wing-linux/kernel/arch/arm/mach-omap1/board-htcherald.c
Scroll down to a block of code where you'll see the touchscreen code. Enter the smaller number in the .dav_gpio statement, and the IRQ number in the OMAP_GPIO_IRQ() statement below.
2. Follow the Kernel build instructions on the development section of the wing-linux wiki (the two make commands)
Copy the zImage into the linux folder on your SD card
Boot into wing-linux. The touchscreen should start working.
3. Now, hopefully, after the touchscreen's working, You would essentially just require two more buttons - the home button and the back button for minimum functionality. Everything else can be worked on by the touchscreen.
Then follow the instructions on the wing-linux forum (Page 2) to get the KEY(row,col) values of the keys on your handset. Hopefully you should get atleast a couple. Note down the corresponding keys and their KEY(r,c) values output.
4. Fire up board-htcherald.c again and goto the place where you have the KEY(r,c,KEY_blah) thing and replace the codes as per your obtained KEY(r,c,KEY_blah) values (The Home button is the one commented as Left Button)
5. That's all I can help you with as of now. I'm also figuring out a stable way of getting the DPad and the center select key to work, but It'll take some time.

Thanks kshaurya!
(This guy right here is the one who fixed the kernel for Gene, I asked him for some pointers).
I don't want to take my device apart just yet (I usually do my best not take to dismantle anything that I haven't owned for at least 3 months unless absolutely necessary) and I couldn't find a place that states what touchscreen it uses. I'm just hoping that it's the same a tsc2046 as well. [Is there anyone without a warranty and/or willing to check for us?]
I'm gonna double check the values I got from the touchscreen as for some reason I seem to have to IRQ values, probably forgot to get rid of some spamming irq. And, at the same time, I'm currently setting up a VM as a building environment, my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines.
If anyone else have some experience and wants to try this, refer to: http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation (using haret to get the GPIO and IRQ values needed).
And to:
http://sourceforge.net/apps/trac/wing-linux/wiki/Development (acquiring the source code from Wing Linux and how to build it).
And a quick question for anyone that tried booting Android on the Opal, what screen did you get when Android finally finished booting?

I don't want to take my device apart just yet
Click to expand...
Click to collapse
Huh? where did that come from? Wing Linux will not touch your WM.
I seem to have to IRQ values
Click to expand...
Click to collapse
Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.
my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines
Click to expand...
Click to collapse
Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.

kshaurya said:
Huh? where did that come from? Wing Linux will not touch your WM.
Click to expand...
Click to collapse
I mean to check the screen, in case it turned out to be different that what you have.
kshaurya said:
Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.
Click to expand...
Click to collapse
Yeah, stupid typo.
I noticed now that one of them appears when I keep the screen 'touched' for a bit longer.
kshaurya said:
Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.
Click to expand...
Click to collapse
I'm not gonna build the complete thing. Seems like I got too exited and failed to notice that building the kernel only requires a cross-compile toolchain, te rest is for compiling the whole thing.
I'm not THIS stupid usually . Honestly!
Thanks again!

I'm not THIS stupid usually . Honestly!
Click to expand...
Click to collapse
Its pretty normal

Weird.
I've only changed the two touchscreen values and built the kenrel. It finished without any error but now it won't boot.
It gets stuck, even before the space allocation part, with this error: "sh: can't access tty; job control turned off". And then it displays a prompt.
I'll try modifying an older build, I'm pulling them from the repos at the moment.
After all, the pre2 kernel from Gene didn't boot on my device (although it got stuck later on).

Try doing a clean install - Remove the linux folder and try again.
Also, make sure that you're not forgetting to checkout the Gene branch.
Code:
git checkout Gene
Is your default.txt modified? And have you downloaded the modified initramfs.cpio?
check in the Gene forums for that.

Already tried the clean install, no dice. The default.txt is untouched and I'm using the modified intramfs. What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command. I could probably ssh via usb but I have no clue how that might help.
And I've already checked out the Gene branch from the beginning.
I've tried compiling the kernel for pre1 (after changing the screen values) from SVN and it did boot (both using the cabs for pre1 and pre2) but no touch screen yet. All in all, I'm guessing that there's too much hardware difference here.
And the button for lowering volumes didn't work either, it seems like whatever you changed for getting it to work on Gene is the same as what we need here, but I'll think about that later.
I only have two ideas left:
- Trying to go back to a more stable build (with lesser features and lesser possibilities for errors). Maybe 0.3.
- Trying to create some kind of hybrid kernel using this alongside the HTC Vogue build as it probably has closer hardware to the Opal (obviously, I'm talking about everything beside the MSM7500 400MHz processor that it has). I'm hoping it won't get to this cause I'm definitely under qualified for that at the time being.

What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command.
Click to expand...
Click to collapse
Could you post a screenshot?
I've tried compiling the kernel for pre1 (after changing the screen values)
Click to expand...
Click to collapse
I'm assuming you mean the touchscreen values? Try interchanging and see.
Trying to go back to a more stable build
Click to expand...
Click to collapse
I wouldn't recommend that. Defeats the whole purpose.
Why don't you try getting in touch with darkstar?

kshaurya said:
Could you post a screenshot?
Click to expand...
Click to collapse
A friend borrowed my digital camera, I tried my laptop's webcam but the text it too blurry. Couldn't fix it using gimp either. So here's exactly what's showing on the screen:
Code:
mdir: Cannot creat directory `/mnt' : File exists
modprbe: could not parse modules.dep
initramfs: Creating device nodes:
initramfs: Loading /initrd.d/10-initfs.sh module
initramfs: Loading /initrd.d/30-wingboot.sh module
Selected:
ROOT_DEVICE=/dev/
CMDLINE=debug quiet psplash=false loglevel=7 init=/sbin/init console=tty0 video=omapfb:accel fbcon=rotate:3 4 root=/dev/
initramfs: Loading /initrd.d/80-loopboot.sh module
initramfs: Loading /initrd.d/85-blockboot.sh module
booting from: /dev/
mount: Mounting /dev/ on /mnt failed: Invalid argument
Unable to mount rootfs device
sh: can't access tty; job control turned off
/ $
And after the prompt, on the same line, there's a flashing '_' waiting for input.
Using the original zImage (from the pre2 cab) it's right around here that the screen clears and the Wing Linux installation script kicks in.
kshaurya said:
I'm assuming you mean the touchscreen values? Try interchanging and see.
Click to expand...
Click to collapse
Will try that next.
kshaurya said:
I wouldn't recommend that. Defeats the whole purpose.
Click to expand...
Click to collapse
I meant it as just a temporary test to till the cause of the incompatibility is figured out. With less things that could go wrong, it'll be easier to locate the ones that are going wrong.
kshaurya said:
Why don't you try getting in touch with darkstar?
Click to expand...
Click to collapse
You're right. I should post a thread on the project's forums asking for his help.

[2011 DISCONTINUED] Android Theming & Tweaking [NEW PROJECT WANTED]

DISCONTINUED DUE TO GINGERBREAD RELEASE AND NO TIME TO REWRITE ENTIRE SCRIPT
WILLING TO START NEW PROJECT WITH SOMEONE ELSE
INBOX ME IF YOU WANT MY HELP FOR A PROJECT
This application will allow you to:
Do everything to theme froyo
And More!!!
Android Theming & Tweaking v2 Alpha
Download below
2.0 Development - Enhancements Finished:
Work Directory can be placed anywhere
Work Directory Move & Update
Animated Splash Screen
Phone tools by Che123 & Me

using windows 7, it is not working for me! I click on 'click me' file and nothing happen
Edit: Click me.bat doesn't open menu.bat automatically, after I click 'click me.bat' I had to click 'menu.bat' to get the options to appear.

works like a charm~

good to see you're porting this over
i'll include the windows version in the original thread and have every OS in one place
all thanks for the windows version go to you
i'll also try and fix any bugs as i know better what the scripts are doing

blackfox888 said:
using windows 7, it is not working for me! I click on 'click me' file and nothing happen
Edit: Click me.bat doesn't open menu.bat automatically, after I click 'click me.bat' I had to click 'menu.bat' to get the options to appear.
Click to expand...
Click to collapse
Sorry for that, I'll have a look tomorrow and see what's wrong
I'll post a new update with lots of fixes tomorrow
(Strict parents - spent so long on computer they nagged me to turn it off, I'm 16 and they still boss me around lol)
I'll make sure all menus work (including click me) and most of scripts work properly
//edit
The only reason I know of for it not working is because you have a space in your username for Windows. Fix will be up today
//edit
The reason I didn't post it in yours because its too buggy to display in your thread, I wanted to keep a high standard in your thread. Once its finished I'll post it in yours
Sent from my HTC Desire using XDA App

shoey-n said:
The reason I didn't post it in yours because its too buggy to display in your thread, I wanted to keep a high standard in your thread. Once its finished I'll post it in yours
Click to expand...
Click to collapse
Would greatly appreciate that
Thanks again for your porting work
Regards

Alpha 2 Released!
Fixed all visible bugs, all menus (including CLICK-ME) should now all work
Most scripts should work properly
Report all bugs to thread (either post up error shown or name of script)
Any suggestions for extra features are welcome as well (I'll tell cgrec92 about them for his version as well)

shoey-n said:
Alpha 2 Released!
Fixed all visible bugs, all menus (including CLICK-ME) should now all work
Most scripts should work properly
Report all bugs to thread (either post up error shown or name of script)
Any suggestions for extra features are welcome as well (I'll tell cgrec92 about them for his version as well)
Click to expand...
Click to collapse
the click-me still not working for me on windows 7 x64

To get the patch work in windows 7 all you need to do
is place the "ThemePro" folder on you desktop!!
mine wasn't working either until i did that

nope still not working

then also try to enter the
"properties" of both the '.bat' files in the directory and play with the "compatibility" options.

hmmm, I don't see why it doesn't work, I'll do some research about x64 because it works fine x32
Can you post up the path to your desktop please (if you don't want to show username, replace with ** but if there's a space in your username include it clearly)

Found a better way of calling the other files, it will work with everyone
(sorry for issues VeeDubZ)
You will be able to run Theme-Pro from anywhere you want, no need to place on Desktop
The Work Directory will still be placed to Desktop by default, I'm adding an option to let you specify the directory you wish to put it
(e.g Where would you like to place your Work Directory?: C:\Users\shoey-n\My Documents)
The update will be up today, and I hope to merge most of Theme-Pro 3.0 features by tomorrow

Hi shoey-n,
Why do you use this command line in CLICK-ME.bat :
call "%homedrive%%homepath%\Desktop\ThemePro\menu.bat"
Click to expand...
Click to collapse
instead of this one :
call "menu.bat"
Click to expand...
Click to collapse
?
I had the same issue than VeeDubZ with the original click-me.bat and by using this command line, it solved it.
Cheers

Thanks for the suggestion, I just noticed that when I was testing out my new way of doing it. That way will be much easier. I'm updating it with that now
New version should be up tonight
//edit
Sorry guys, I've updated the script but haven't had time to upload ( internet is really slow, so it'll take about 15 minutes )
So I'll do a major update for the release tomorrow, just for you lot

thanks for the fix, no worries about the problems with it, i started using the linux version for now, your version will just save me rebooting to use that one.
my path is the standard path that a user would use without any spaces C:\Users\vaughn\
Thanks for the progress update, looking forward to the release.
V.

Alpha 3 is out, few changes and enhancements to this version
Been tested outside of ThemePro but not inside. Hopefully new method works (hopefully uploaded right one )
Added transparent notification drawer mod (uploading for themepro 3.1 Mac/Linux in 5mins, compiling it and adding to scripts right now)
Changelog is up on first post

alpha 3 broke it all for me... none of the options work, Cmd spits out an error about "er" not being a system variable, and not being able to find the directory...

That means I made a typo somewhere, the way I done it means I only have to check 2 files so should be easy to fix, thanks for reporting the bug, fix will be up in the morning
Sent from my HTC Desire using XDA App

Beaverman20 said:
alpha 3 broke it all for me... none of the options work, Cmd spits out an error about "er" not being a system variable, and not being able to find the directory...
Click to expand...
Click to collapse
Thanks for your bug reporting, it's all fixed now
I've tested it and can confirm working

[22/12/10][SUSPENDED] IcedCube GingerHD2 [Rooted][Experimental][MDJ Kernel]

PLEASE READ THIS POST AND UNDERSTAND IT CLEARLY BEFORE USING THIS ROM!​
Heyo,
This ROM is now a port of the Nexus S Gingerbread ROM leak for the HD2. I would like to make it clear that this ROM may be unstable and not for everyday use! Since we're using a version of Android designed for a different device, we may have issues. The leaked build I'm using is available here - some modding is required though.
Starting from 0.05, my builds come with a 96MB Data.img file to get you out of trouble. I will provide data.img files that are 128MB, 256MB, 512MB and 768MB in size. You can make your own image via a terminal on Linux like this (don't type the dollar sign or the stuff behind it)
Code:
[email protected]:~$ dd if=/dev/zero of=/path/to/Android/folder/data.img bs=1M count=128M
[email protected]:~$ mke2fs /path/to/Android/folder/data.img
(answer 'y' to the question when mke2fs says "data.img is not a special block device, proceed? [y,n]")
Installation
Extract the "Android" folder in the ZIP file below to your MicroSD Card, pop it into your HD2, open File Explorer from WinMo, find the Android folder, tap CLRCAD.exe and then Haret.exe and watch the sparks fly.
For patches, extract the files in the patch archive to your MicroSD Card, overwriting any existing files.
Downloads
You can download the ROM from my server below. Please don't use download accelators, they will make my VPS cry...
LATEST VERSION IS 0.5, PLEASE DO NOT USE OLDER VERSIONS AS YOU WILL BE ASKED TO UPGRADE IF YOU SAY SOMETHING IS NOT WORKING ON THOSE OLDER BUILDS!
Version 0.01 > Get the goodness here! <
Version 0.02 (Patch only, download v0.01 first!) > Get the goodness here! <
Version 0.03 (Only a data.img for people who are having boot problems) > Get the goodness here! <
Version 0.05 > Get the goodness here! <
Version 0.05 requires 7-Zip to extract
Disclaimer
If I used any of your works and I did not acknowledge you, I am not claiming your work as my own. That would be the wrong thing to do (and I am not intending to "kang" any sources). I am also not responsible if your device is bricked or broken by direct or indirect use of this ROM.
Credits
spbeeking - The person that dumped the gingerbread SDK build in the other thread, in which that got over 210 Posts.
dakluck - Found the fix for BSOD (temporary).
m-deejay - Used his kernel. They rock.
jubeh - Found the problem with the SDK Build's lagginess.
supercurio - For the Nexus S ROM Dump.
...last but not least, all HD2 Owners that have given up 250MB+ of their MicroSD Card space to test GingerHD2.
Credit will be given where due. Watch this space!

Changelog Key:
+ means addition/change
- means removal
[!] means danger/caution.
v0.0.6 - Changed over to m-deejay's Gingerbread, working with his base to make a "lite" ROM.
This version is currently under development and will be released when deemed finished!
v0.0.5 Release 1 - ??/12/10 - Coming very soon.
+ Switched to Nexus S ROM Base
+ Replaced Nexus S default GL drivers with the ones for the HD2
+ Working Radio - SMS & Texts should work...
v0.0.4 - 10/12/10 - R.I.P, I totally fudged up v0.04 SDK Sources. Stupid me!
v0.0.3 - 10/12/10 - Patch 2
+ Basic data.img only for people with boot problems. Only use with older releases, don't use it with v0.0.3+ builds.
v0.0.2 - 8/12/10 - Patch
+ Switched kernel to m-deejay's kernel for working 3G Connection, data should work.
+ Fast bootup speed.
[!] Black Screen of Death occurs if you allow the device to go to sleep.
NOTE: BSOD can be fixed temporarily, see below.
[!] Erratic behaviour occurs if you haven't PIN unlocked your SIM Card before booting this ROM.
[!] Can take a while to do things, ie. very laggy.
[!] Black screen after HTC logo, no android logo.
[!] Keyboard comes up as white space (?)
... Possible other things that are buggy or whatnot.
v0.0.1 - 8/12/10
+ First release. Boots somewhat and then has problems.
Temporary Fix for BSOD in sleep (present in v0.0.3 and below)
After pressing power button once, press and hold power button till vibrate, then press back button. May take a few attempts but persistance is key.
(Credit to dakluck)
Bug List
None as of yet for 0.05... (Currently in-dev)
(Outdated) Checklist
WiFi? Not yet working.
BlueTooth? Not tested.
SMS Sending? Seems so (according to m-deejay).
Calls? Working.
3G Data? Working - select APN before going on the 'net.
Sound? Not working, but I'm working on it.
Camera? Not working.
Camcorder? Not working.
Screen (blacklight, touch etc)? Working.
Lights (keypad): Working.
Accerometer/G-Sensor? Not working.
(..to finish..)
Having boot problems?
Download the 64MB Data.img which is v0.03 (it's just a zip with the data.img I use for this ROM) and extract it to the same folder (for example, if GingerHD2 is located in GingerROM on your MicroSD Card, extract it to that folder). Then you should get to the desktop.

IcedCube said:
Reserved for changelog and other stuff
Click to expand...
Click to collapse
that's pretty nice gingerbread , cooool i can't wait to see this fully working

WOW !
Keep up the amazing work !!!
much appreciated.
I will try the build now.

Cool thank you.

thanks
excellent work,at less we can have a try for 2.3,thanks.keep working on 2.3

As I've said, you won't get into the Android UI, but if you can confirm that the kernel is getting stuck at "init: untracked process X exited unexpectedly", that would be appreciated.

Nice work, thanks for sharing. The init.rc file you mention is linked to a pastebin link in the original dump thread. Should be easy to search.

phiredrop said:
Nice work, thanks for sharing. The init.rc file you mention is linked to a pastebin link in the original dump thread. Should be easy to search.
Click to expand...
Click to collapse
No worries. My eMac is being a pain, so I'll have to find the pastebin link manually.

Just a quick bump, I'm just fixing the bootup issue. Once done, I'll upload a patch for you guys (and girls).

Cool... I will give it a spin
Sent from my HTC bravo using XDA App

Keep up the good work. My pray from Indonesia
Sent from my Nexus One using XDA App

Thanks for the credit and all, but didn't you say that you used your own sdk dump?
Sent from my Decepticon using XDA App

spbeeking said:
Thanks for the credit and all, but didn't you say that you used your own sdk dump?
Sent from my Decepticon using XDA App
Click to expand...
Click to collapse
I just wanted to give you a shoutout because you did the dumping before I jumped into the fray and dumped the sources myself
And on that bombshell, the v0.02 patch is up! See the second post for changelog, and first post for downloads. Here's how to install the patch:
For patches, extract the files in the patch archive to your MicroSD Card, overwriting any existing files.
Click to expand...
Click to collapse
It couldn't get any harder. Or could it...?

thanks alot!
seems like the 0.02 patch is down.
mirror pls!

the patch is down

where is the patch? the broken patch link....

youngquazy said:
the patch is down
Click to expand...
Click to collapse
Patch is online; uploaded to wrong folder on VPS. Oops.

Version 0.02 download link Damage

File patch is missing in your server. Version 003 is imminent? thanks

Kernals, Nand, full functioning Android?

I gave my Dad my old blackstone when my Desore turned up.
He has winged that he can't get the marketplace and about all those general WinMo issues that people have (it dead etc)
I can't find a clear message on the status of NANDROID for blackstone.
TIAD8s site has NAND versions that are missing bluetooth or other funcitons
It appears there are basic functions that are lost according which kernal is being run.
I'm willing to do one completely convoluted install just to get Froyo style on my dads phone but only once. I never have trouble with new flashing procedures (slow and steady wins the race) but I don't want to hand him back the phone broken especially as he uses hands free in the car
So - can anyone say categorically that a NAND version work fully?

Categorically: Not yet. Wondering if ever...

Forget it...

Think Tiad8 only has test team working on a NAND build anyway?
Not seen it in action yet

Kernals?! ....

I find deliberate typos (NOT TEXT SPEAK) can get people to engage.

olly230 said:
I find deliberate typos (NOT TEXT SPEAK) can get people to engage.
Click to expand...
Click to collapse
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .

t8 let people wait and wait.
though it's good to try, we don't know whether he really works on it as he start many threads to other device besieds HD.

arrrghhh said:
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .
Click to expand...
Click to collapse
Desore was a proper typo, I'll put my hands up to that

Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.

MietasSR said:
Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.
Click to expand...
Click to collapse
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post.
With your post here I had to smile a little: now your name is connected to the "null nands" for many consumers in tiad8's forum. Even I thought you're part of it now and that's why I tried the build yesterday again: Boot partition to small and Kernel not working.
I think now it's getting to the critical point in the NAND experiments: correct or good partition sizes for NAND (some members there startet to change partition values in the image files with a hex editor) and more important: building a working kernel with modules for Blackstone NAND.
Until now all experiments reached a few preparing goals: getting a working .nbh for starting into fastboot, getting a recovery.img for a working CWM etc.
But now (if I am completely wrong please correct me, I really want to know) you have to change partition and ram parameters in clk and hope you will spare the protected parts.
And after that: Kernel and Modules for Blackstone on Nand. I am starting to believe here would be the real point for developers.
I started to build Kernel and Modules, a Boot Environment (initrdgz) from git and packed them with changed parameters in a Tinboot-Package. I can flash with the .nbh, I can boot, I got a lot of errors in init first, but I succeeded in running and loading the kernel, I get access to the changed mtd partitions etc. Debugging on Blackstone with Echo "" ist quite funny.
I got stuck when I tried to cp files from SD card to the /system partition (which is mounted r/w) - I can cp files from / to /system anyway. Big ?? for me. But I like to play with it a little more, because I learned a lot.

ThaiDai said:
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post..
Click to expand...
Click to collapse
Me Too!! Does this mean you are working on different things?

[Q] native linux help

well.... i had native linux on my iconia on honeycomb but when i installed the nvidia drivers it broke the linux image, i could never get it to boot again. now i am on ics patched bootloader with dual boot and all that jaz,,,, now i cant seem to find a working link for the rootfs. could someone help me with turning the 3 part rootfs in to one or am i missing something? i really would like this as my secondary image on my blovid tab any help would be awsome

tarsh249 said:
well.... i had native linux on my iconia on honeycomb but when i installed the nvidia drivers it broke the linux image, i could never get it to boot again. now i am on ics patched bootloader with dual boot and all that jaz,,,, now i cant seem to find a working link for the rootfs. could someone help me with turning the 3 part rootfs in to one or am i missing something? i really would like this as my secondary image on my blovid tab any help would be awsome
Click to expand...
Click to collapse
Not sure if this is what you looking for but heres a working rootfs image
http://forum.xda-developers.com/showthread.php?t=1158260&page=36

see... thats a 3 part rootfs. i dont know what to do with the three parts. thats ware im stuck

tarsh249 said:
see... thats a 3 part rootfs. i dont know what to do with the three parts. thats ware im stuck
Click to expand...
Click to collapse
just download them all then put them all in the same folder and hit extract on part 1 and it will merge all 3

When you install that driver, also you can uninstall it, when kernel boots up, press ctrl+alt+F1 then user name and password, type
sudo apt-get remove nvidia-tegra
After done, reboot and get xorg.conf and put it to /etc/X11, then reinstall nvidia-tegra driver. If you using nvidia-tegra. Sorry for bad English.
Xorg.conf is http://pastebin.com/0a6T6c18
Copy that text and save it as xorg.conf then move it to /etc/X11 directory.
I think that you can find better rootfs from androlinux.com . On that Ubuntu image you can upgrade distribution.

well extracting all three isnt working for me...