Related
I'm sorry for being so loud, but I've seen a few "progress pages" in Wikis and I still can't get a clear picture of who (if anyone) is actually working on linux for the HTC Magician (Qtek s100, iMate Jam, Dopod xxx, etc.).
I found this project:
http://userpage.fu-berlin.de/~zabel/magician/README
and it appears to be very very promising; it already delivers some small functionality on the magician (I've tried it). But there is much much work to do before it can be released to the general public.
In general, I don't think there are many people working to get the Magician on Linux...
So I am asking here: are you working on this? do you know who is working on this?
I am a SW developer by trade, but I have no time at home to code.
However, I would like to give whatever little time I can find to:
- act as a beta tester;
- develop one or two patches (kernel mostly);
so we can get Linux running on the Magician.
Thank you.
Hi,
This doese indeed look promising.
I have no qualifications in software etc, but i do like fiddling with linux -).
I too would be a beta tester.
So is anyone working on this?
Hi. As vnevoa found out, I am working on the Magician when I find the time.
Unfortunately, to my knowledge, there is no-one else currently working on this. So developers are needed!
For people interested in kernel hacking, there is the [email protected] mailing list and the #htc-linux IRC channel on freenode.net
The biggest missing parts currently are battery control, sound and the phone.
For everyone else, any improvements to the Magician wiki pages would be more than welcome. To build a proper userspace image for the Magician, support for this machine in OpenEmbedded has to be improved.
Wow!
That haret thingy is wonderfull.
What is the current state of the version for the Magician? Does it boot to GPE?
This is a great thing, really. No need to flash a new firmware, and boot linux! Amazing. I'm using Linux on ipaq and it is very nice. But I would miss phone operation. With haret we can have both things running.
Good work. Has anyone tested USB host on magician under linux?
futaris said:
Good work. Has anyone tested USB host on magician under linux?
Click to expand...
Click to collapse
USB host works, but it is not connected to the usb plug.
The bluetooth chipset is a CSR usb chip.
pH5 said:
USB host works, but it is not connected to the usb plug.
Click to expand...
Click to collapse
does that mean, usbnet is not possible? in my case, nothing happens if i connect the magician to my computer. dmesg and lsusb say nothing about a new device. insmodding usbnet doesnt help either. tried the same with a htc universal, usbnet works fine on my machine.
[edit]works for now, if connected via external-powered usb-hub. maybe a driver problem? activesync in windows-mobile is possible without using the hub.[/edit]
And if you check the website you can see all teh file you need to download if anyone know a programm for make call/sms/mms or ONLY calls and run on this linux please give information about
ok i try this one in a few and i edit my post when i have test all
ok today the : 28.12.2006
mmmm i have some trouble with extracting the gpe archive it's seem to be corrupted soooo bad.
BUT the first problem it's this famous default.txt the script to run haret if anyone have a working script please copy information here of the .txt file that's can be helpfull.
the error of my default.txt is: Failed to load kernel \carte de stockage\zimage
must i need to rename the zimage file???
and i have a question ... it's possible to make a "bootable" SD? if yes i can try to run another handled linux perhaps???
OK i have found i must rename the magician-zimage-2.6.XXXX to : "zimage"
so i have downlaod latest version of haret and take the default.txt WITHOUT changing
harte start but of course i haven't the gpe file so it's say error BUT it's launch now i must really found a good archive i have try under linux but the archive still in read only i can't change it to read AND write so all i uncompress are still not working under linux it's better on windows don't know why .....
(mmm risk to brick my magician if i try another gpe file .......)
and of course: sorry for my bad english
now i edit the post when i have MORE important news
Hey All,
I just installed those updated drivers on my wizzard with mfrazzz's Crossbow Reloaded 1.5 rom. After a reboot I can't start bluetooth anymore. Are there some regkeys I have to change to get this working? I can uninstall the package to see if it will work again with the bluetooth drivers in the Crossbow Reloaded 1.5 rom, but that'll be the easiest way.
Hopefully anyone can help me.
Thanks in advance.
The CAB file in question
Considering that cab file is from the Hermes/ WM6 Black ROM, it's probably NOT going to work on a Wizard.
Based on looking at the cab, it replaces 4 .dll files. My guess is that those are not compatible with the Wizard drivers. Just do a remove program and see if that fixes it. If not, then delete these four in \Windows and you should go back to the ones that were built into the rom:
serial_btur.dll
OEM_Misc.dll
btagext.dll
bthuart.dll
mfrazzz, do you maybe have a cab file for the bt drivers in your rom?
Hmmz, your tip worked. Thanks. I simply renamed those files to *.org and that did the trick. But maybe a question though, aren't there newer BT drivers for our wizzard?
You are a total @#$%$#@. What would make you think they were even for the wizard? And those bt drivers never even helped the the problem that black was having on the hermes. You need to do some more reading buddy. Lets not end up with bricks here
HUGE BREAKING NEWS!!! THIS JUST IN:
May 12th, 2008
ENTER "FrankenKaiser"
For the past several weeks, I've been working with Jocky on unbricking devices with nuked SPL's as a result of task 2a MTTY commands. Last week the amazing Jocky found a way to exploit OEMSBL & to Security Unlock a BRICKED device via dload mode. That's right, you heard correctly, Jocky Security Unlocked a bricked device, giving me access to all of the OEMSBL, Radio Boot Loader commands!!!
Subsequently, Jocky has written a tool that will then use this exploit to load a new SPL via Dload mode into ram & do some device initialization. After three chalenging & frustrating weeks, we were able to load a SPL into ram, get the spl to stick & voila.....I now have the first ever Kaiser recovered from being a nuked SPL brick!!!!
I won't give to many details, as this is really Jocky's baby & it's his place to share the information as he sees fit, but I'll tell you that this tool may be the start of something huge! It will allow you to test SPL versions & recover from bad SPL flashes. I believe this tool is also going to be the center of fixing the locked AT&T radio's.
I can take no credit for this tool, I was really nothing more than a brave & willing guinea pig, that occasionally floated theories, & remembered some of the little stuff.
Jocky did let me name the tool, based on the first thing I thought & said when we were talking about the theory behind the tool, which was "Oh my God, It's alive, it's aliiiiive!!!!", so the tool has been named FrankenKaiser!
If you have a Bricked Kaiser, Let me know, post it here in this thread until Jocky start a thread specifically related to this new tool. Please don't overwhelm Jocky with requests & PM's, as the tool must be moddified for each & every different OEMSBL version. If you have a task 2a or other bricked Kaiser, please PM me or post the info here on this thread & depending on the type of brick you have, someone will let you know if this tool can help you.
Okay, it's true I've put my Tilt thru hell & back trying to help out the noobie. I have done partial flashes, radio & rom, to recreate their problems in an effort to guide them thru the solutions.
I've alway been able to recover......Until now!
A WARNING TO ALL USERS FROM OTHER DEVICES NEWLY COMING TO THE KAISER!!!
After countless trips to hell & back for my device, it finally, It is totally dead. After doing a few MTTY task & info calls while assisting a noobie I decided to format my device & the nand storage to start afresh. Now I am stuck in OEMSBL.
Should you try and format or dump bad blocks as previously possible on some older devices using the task 2a command. There are several thing you need to know. Firstly, you'll need to immediately flash a new SPL BEFORE soft resetting. Otherwise, your device will not boot period. You will find that the service LED light stays green like it is fully powered, & the "GREEN" light will come on whenever you hit the power button, but when you plug it into the USB port on your PC, it will only be seen as new hardware & will add the following new devices: a NMEA GPS Device, a Qualcomm Data Device, an Qualcomm Diagnostic Interface, a Baseline Modem, Baseline Storage Device, etc. But A/S will not run & MTTY cannot communicate using standard commands nor can it be used thru the USB port.
The reason this happens is becauser you have just completely formatted the NAND, essentialy killing the Boot Loader or SPL.
As of this time, there is no known recovery for this type of brick. Several people are working towards a fix, but unless your device is security unlocked, there will be no miraculous recovery.
ALWAYS EXCERSIZE EXTREME CAUTION WHEN COMMUNICATING THRU MTTY WITH SPL OR WITH OEMSBL. DO NOT ASSUME THAT THE SPL COMMANDS ARE STATIC> THEY CAN & DO CHANGE BETWEEN DIFFERENT SPL VERSIONS & DEVICES.
As an example, Tilt Devices with the 1.56SPL can execute the boot command, whilee HTC 1.93SPL devices cannot & require a task 8 to reset.
If you do not know what SPL is, or have no idea the available commands & their effects, do not use them.
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Laurentius26 said:
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Click to expand...
Click to collapse
Laurentius is right; it would surprise me if the Flash from SD-card would not work for you!
Good luck,
Edward
sorry to say that but it is a true brick now, it is recognized by windows because there it falls back to qualcomm diagnostic mode (which will not help you at all) I had exactly the same situation and you won't be able to flash it, send it to htc for repair
No, The screen will not turn on & when plugged in it now acts as accessories or hardware for my PC.
The chipset inside the device is still getting power, & it is a chipset that is powerful & used for many, many things. So, it's no suprise that it sees the modem, the Basecom Interactive, Basecom NMEA device, etc...What it doesn't see is all of it integrated into a package & it actually creates 6 or 7 port connections thru XP Hardware Wizard for each "accessory".
What I believe has happened is that the unit has been completely formatted meaning the actual Windows CE has been destroyed, formatted, removed, kaput...
The only way to revive I think would be to reload CE into the device the way Mfg's & OEM's do.
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Da_G said:
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Click to expand...
Click to collapse
nope, there is now way to do that
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
GSLEON3 said:
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
Click to expand...
Click to collapse
sorry, that's a misunderstanding my post was referring to the use of pst software/mtty and usb connection, and I reckon that it's cruel to give the man hope, though you can always buy yourself a piece of software built based on jtag, special serial connector and a book how to to that but given the sources you mentioned I reckon you haven't read much about the problem yet, my kaiser is about two be back from service this week and if there was no breakthrough on the internet about that with last 2 weeks then there is no know way how to talk to qualcomm diagnostic software directly using usb.
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
_Alex_ said:
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
Click to expand...
Click to collapse
yes Alex, also SPL (which is the real problem here), and you can't use pdocwrite unless you could actually talk to the device which in qualcomm diagnostic mode you can't with this software as it will not accept any commands other than specific to that mode, I have flashed windows mobile device for about 4 years now and that's actually the first time I ended up with a real brick but of course htc can easily fix it (they did it in 1 day, most likely in less than 30 minutes) but they have equipment to do that which I don't and only few users on xda have that kind of equipment, to get more info about it you could look in the search for task 2a there were bricks like this before us
Alex,
Yes CE, Radio, SPL, OS... All see to be completely wiped with the task 2a command. I don't think pdocwrite will work as its still needs a medium to connect to my device. That medium is what I have yet to find. The first step would be to somehow restore boot loader. I am currently trying to see if I csan use qpst to push linux to the device. I haev found some CE restore utilities for reverting from linux, but first I need to be able to at least boot to SPL or another Bootloader.
Whats about Windows CE and KITL Mode?
The device stays in OEMSBL. If you use the MotorolaQ drivers, you will be able to connect to the right COM port and issue radio bootloader commands. You will probably be able to unbrick it depending on what problem it has. First try the easy one:
* Execute "setboot 0" and "cego" commands.
If this does not work, then probably your SPL has been erased in NAND, you can check that by dumping radio memory address 0 right after executing "cego" command. (commands: "cego" and "mb 0 40000").
If it's all 0xFF then your SPL has been erased. Here's how to fix that:
1) Issue command 'setboot 1' (with the default 0, the application ARM is hang because it tries to execute 0xFF), this way it keeps the SPL in memory after reset.
2) Copy a full SPL at address 0 by issuing 256K times 'mb <address> 1 <byte>' (i've written a small app that does this for you...)
3) Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader, in my case (OEMSBL version 1.27.12) the patch was 'mw 901708 1 0000a0e1' you'll have to figure it out yourself if you have a different OEMSBL version.
4) execute 'cego' and see the bootloader 3color screen appear again (keep the bootloader keys pressed if you have not used a patched SPL in step 2)
5) Flash HardSPL.
6) Connect to OEMSBL again and execute "setboot 0".
7) See the device booting OS
Thanks pof!
setboot 0 returns ARM9BootMode:0, so it is communicating. However, I get invalid command errors with the cego & mb commands. You think there is a way to flash an spl.nbh using OEMSBL thru pnewbootloader? I believe you're right on the money & from what I've learned playing around today is that the task 2a command indeed formats the NAND. So bye bye bootloader. I think it's now just a matter of finding a way to flash spl back. That said however, I can figure things out given a lot of time, but I'm definitely nowhere near a bright bulb on the XDA X-mas tree, so to speak. So you'll have to forgive me if the meaning of "Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader" escapes me.
Thanks again!
When I used to work @ symbol we used to interface with our devices directly in IPL mode using hyperterminal (included in windows). I wonder if you could accomplish something like that?
From there we used to use IPL commands (I dont remember them because this was a long time ago)
GSLEON3 said:
Thanks Oli!
However, I get invalid command errors with the cego & mb commands. Also, where can I find the spl patch app you've written? I searched high & low.
Thanks again!
Click to expand...
Click to collapse
I think POF is talking about JumpSPL correct? I am surprised it didn't work after what POF recommended his right on 99% of the time!
I believe s right. I just think the cego command isn't correct for my device. I think maybe this command has changed just as spl commands can change between versions. The mb command also returns an invalid argument.
But it's definitely down the right path.
GSLEON3
I really wish I could help you out man. You have done alot on this forum for alot of people. Unfortunately I'm about as lost in here as a hooker in a pecker patch. Sorry bro, wish I could help.
pof's method only works if your device is security unlocked
Please dont get mad i looked every where to see if this had already been posted. When i run Hard-SPL I keep geting to 260 error it starts just fine asks me if i will grant access to the application which i do and it starts to do its thing but then halts and i get the 260 error and it dose not go any farther any suggestions?
did you remove your sim and sd card?
In addition, if you have not removed them back up your data. Then do a hard reset. Then remove sim and sd card. It maybe an open port problem so restart your computer as well. Hope this helps.
tried
Gave that a try after it asks if it is alright to load the file on my phone it auto resets phone then 260 error happening again im on vista 64 bit and even tried what the main website said for vista users but half the guide dose not really apply so im not sure what to do or what im doing wrong. any more suggestions?
Need Help
Anyone that has been able to run HardSPL on a vista 64bit system please point me in the right direction I really want to set up my custom roms on my phone that I have found! Please help!!!!!!!!
sorry i couldn't help you i always thought a 260 error was due to open connections or ports.
When you downloaded the zip file for hardspl did you use vista's unzip?
If so you may get an error because vistas unzip program sucks ass and you need to use another application to unzip the hardspl software.
crazigamer said:
Anyone that has been able to run HardSPL on a vista 64bit system please point me in the right direction I really want to set up my custom roms on my phone that I have found! Please help!!!!!!!!
Click to expand...
Click to collapse
Did you go through the connection settings in the mobile device manager and disable usb connections?
Are you using vista..sometimes it doesnt look for a new set of drivers for the Phone when its in tri color mode..try rebooting and leaving the phone in tri color mode...once you do that, start from scratch after it gets all the drivers installed
This advice is thanks to tochill. Try this and see if it works. Vista often does not automatically load the drivers. I used Vista 64 to flash without a problem. It was a little tricky to get it to load the drivers at first but after they are loaded you should be fine. If it doesn't work let me know and I will see if I can find the drivers for it.
Also make sure you have the most updated version of Windows mobile device center.
not sure what to do
When am I suppose to disable usb connections of the phone in WMDC ? and also I used winrar to extract the folder. also the phone auto reboots after it is promted to allow the program to launch to install hardspl and then I get the same 260 error again any more suggestions? Im sorry for all the trouble here I just really want to get this to work. everyone said it was easier to mod tilts but it seems to be harder then my iphone lol
update ur drivers if ur using vista
for me vista was a pain to flash so i just use my desktop which is xp and its happy flashing for me all the way...piece of cake now after u do it a few times
crazigamer said:
When am I suppose to disable usb connections of the phone in WMDC ? and also I used winrar to extract the folder. also the phone auto reboots after it is promted to allow the program to launch to install hardspl and then I get the same 260 error again any more suggestions? Im sorry for all the trouble here I just really want to get this to work. everyone said it was easier to mod tilts but it seems to be harder then my iphone lol
Click to expand...
Click to collapse
Before you connect your phone.
You don't need to do any of that. What you need to do is DL the USB driver from A/S & associate it with you device in WMDC. There are several good threads on doing it. Start Here: http://forum.xda-developers.com/showthread.php?t=291723
Even tried xp
I have even tried using XP I still get the same outcome my phone auto restarts after I tell it to run the program. What am I doing wrong? I am suppose to run the main file off of my PC not the phone correct? and just go trough the setup?
Can some one tell me how they did it step by step because I have followed the instructions on the HARDSPL main thread and it dose not work. And so I am correct this will work with the new ATT Tilt right?
tried all of that still dose not work any other vista run arounds? God i wish i still had my xp discs
Please feel free to message me on aim username is kl3pto really could use some help.
GSLEON3 said:
You don't need to do any of that. What you need to do is DL the USB driver from A/S & associate it with you device in WMDC. There are several good threads on doing it. Start Here: http://forum.xda-developers.com/showthread.php?t=291723
Click to expand...
Click to collapse
Thanks that was a thread I was looking for to post to the OP as the next step. I have had to reinstall vista 5 times and each 5 times had to do something different to get it to work.
NP, I also suggest with Vista, you flash HardSPL via Jump. Don't flash ROM's or Radios with JumpSPL, but with the 1.93 SPL, I have tons more success using the Flash HardSPL method than the .exe
Has anyone ever tried to flash a rom or develop a rom that can be flashed by a Mac? I have Missing sync to sync my Tilt and to download .cabs and .exe's.
Works great by the way. I have flashed several roms from Windows XP on the " other side " of my Intel chip, so no problem there. Just wondering can it be done from the Mac side? And has anyone done it?
I have been using Macs and Apples for over 25 years ( started with Apple IIc) and never once had the urge to switch so comments from the "Apple Bashers" will mean nothing to me
Just curious.
no i'm not going bash apple but i haven't come across anything for mac and i believe the kaisercustomruu.exe can only be run only on windows
I have successfully flashed my Tilt using a Parallels install of XP Pro. Of course that requires an Intel Mac to accomplish...
NotATreoFan said:
I have successfully flashed my Tilt using a Parallels install of XP Pro. Of course that requires an Intel Mac to accomplish...
Click to expand...
Click to collapse
I have flashed several roms using both Parallels and Bootcamp on the other side of my Intel/Mac chip and .exe file will not run on OS X but is it possible to create a rom using say a .dmg package instead of an .exe package?
The problem is far beyond the fact that the package is in exe the tools to actually flash the rom are windows only
I'd just flash from the MicroSD card.
Read here:
http://forum.xda-developers.com/showthread.php?t=336158
AstainHellbring said:
The problem is far beyond the fact that the package is in exe the tools to actually flash the rom are windows only
Click to expand...
Click to collapse
Obviously you can't just re-package under a different file extension. What " tools " are you refering to? Kitchen tools? Again just re-packaging. Leopard can run on an intel chip. Word, Excel, etc, can run natively on a Mac. Can you put together a rom or write one from scratch that can be downloaded natively to a Mac and then flashed to a Kaiser? Even theoretically?
You can use whatever OS you want... Just do what Peterfnet suggested... Use the SD card method... It's safer and easier.
Just follow the link provided by Peterfnet!
Rayan said:
You can use whatever OS you want... Just do what Peterfnet suggested... Use the SD card method... It's safer and easier.
Just follow the link provided by Peterfnet!
Click to expand...
Click to collapse
It wasn't a "how do I flash a rom question " , I press a button and my screen twirls from OS X Leopard to Windows XP , I flash a new rom, press another button and my screen twirls back to Leopard and all my Mac apps. ( new Intel Chip for Mac)
The question was " what do the knowledgeable people here think? " Are there limitations of computer science that would prevent this or just limitations of available ground work that I could create?
Edit: I re-read this post and it sound kind of terse, I didn't meanit that way.
Thanks for your input Rayan
I see no reason why it would not be possible to flash a ROM natively inside Mac OS. But in order to do so, the flashing application written by HTC would need to be recoded to run on Mac.
If you extract the .exe file that is inside the rar file posted by the chefs here, you will see 5-10 files, one of which is the OS.nbh file. If you can write a program for Mac OS that can communicate with the Kaiser and call that file, then it would be possible. (DISCLAIMER: I am NOT a programmer, so it is a definite possibility that I could be talking out of my ass.)
Since flashing is not yet available to Linux users, then Mac is probably still a bit off.
peterfnet said:
I'd just flash from the MicroSD card.
Read here:
http://forum.xda-developers.com/showthread.php?t=336158
Click to expand...
Click to collapse
best option all around
Well, ever since I discovered the SD Card method I don't flash it through the PC anymore... No more fears of freezing up, power failures and such!
In fact, I carry several "test" ROMS in my card just to install them on the go whenever I'm bored! LOL...
Here's an answer from someone who is paid to write software....
You're correct there is no technical reason that you can't flash your phone from a Mac OS.
Basically the whole process is a few commands & responses sent across the USB port and then the nbh image streamed via the port to the waiting device.
Here's the bind: Microsoft is well known for not working well with others. Why would they be motivated to provide non-MS OS the ability to flash "Windows Mobile"? It's kind of like iTunes being able to integrate with non-iPod MP3 players as well as it works with iPods (or so I've heard).
Thanks all , it looks like I have my next project. Thanks for all your input. peterfnet and Rayan thanks when HTC comes out with their new rom update and new driver package at the end of the month I'm going the card method for a change.