Database Users

My wizard 200 totally dead now

I updated first time that was fine ..
Again i updated with wrong os ..may i think..
Now not switch on my wizard 200 ..
Here i search for reparing this problem..
Then i got jtag ,,that can help..
But i hav no software for doing this ...
I need some ideas ..which software use for direct flashing the rom..?
...,
,
.
.
..
.. Help...........thanks in advance

Pleas...need help ..
Not switch on

possible resuscitation for you wiz 200
I had some bad flashes with my wiz 200 too, a K-jam to be exact
my best guess is dig a bit deeper in the wizard forum
and you find out that there ways to revive it.
1 thing you could try is,
remove your SD-card
get a very bright spot-light so you can see if you phone is working, only the backlight is not activated
press and hold the camera button and press power on, release the power button and you should get a 3 color bar screen.
If it doesn't, search for the MMC restore trick somewhere on this forum
please let us if it worked
Atleast the MMC trick saved my tiny behind
I wish i could search it for you, but i can't open multiple tabs yet on my mobile

ok dear i try this method..if get it ...
it will be the best and best work in my life....
i keep try to unbrick my wizard 200 ...
i only stop searching ...after i die....
i work hard for it...lets wait...i just checking..

well the good news is you could get a broken screen wizard for pretty cheap.

HI DEAR
After all i followed...but not switch on yet..
Wat is the next procedure for unbrick my wizard 200... Help need
no bootloader..no led..after full charge..also..help need

i have solution man
hey u need answer to this question contact me personaly at [email protected] and i can give u the answer.come at chat i will make your wizard live alive man.message me the time to chat

help
no one is here..
can u help for jtag on wizard200
can i get jtag for wiza200
ca i get gtag software ..?
anyone ..pls i want to be unbrick my wiza200...

Elf jtag - for those whose own a brick

Hi all,
First of all, let me introduce myself: I'm newbe here, I'm membre just a couple of weeks ago. I'm from spain, so sorry if my English is not good. Excelent forum. Great jobs.
Well, testing roms in my elf I made a brick, totaly dead, (no led at all, no response to any combination of buttons, no response to charger or ActiveSync), so I started searching for Jtag info, but there is very few over internet, at least i didn't find it. More than this I'm not familiar with Jtag, so even if I find info, maybe I don't know how to handle it.
I'm sure that there is a lot of people owning HTC ELF bricks, so I'd like to share the info I found to see if together and with masters help we cand find a solution to "revive" our HTC elf using Jtag.
I just found a russian forum containig some info, so here you are what I found:
You'll find attached 3 files:
PIMG_0013 is the board pinout picture
Wiggle_arm is one JTAG interface circuit
70057019 is another in detail JTAG circuit and schema
I don't know how to post the images themselves, so I attached them.
I hope this will be the beggining of a good investigation job and a way to recover all this dead ELF.
I have some more info regarding to the software they use, please ask me if you need it.
Regards.
SPECIAL THANKS TO THE ORIGINAL POST OWNER: IWAN

UP
No one knows anything about Jtag?

Half solution
Hi, i had the same problem and i found something "good" on the web, cuz i haven't found a complete solution but it's a start.
1.- Remove battery for about 2 hours
2.- attach battery again and then press power, volume down, red and green buttons, middle button, and then reset button, release reset button fisrt and others after that.
Yeah, it sounds stupid but i tried and worked for me, now at least have bootloader mode, if you get this, try "how to unbrick" topic in this forum, there is a lot of info in it.
Cheers.

i can't physically press all that buttons at once.can you explain by steps? are you releasing any buttons until you press last button?

you only need to press red and green and reset i think, been a while since I have done this.
What issue are you trying to solve?

Acer F1 system successfully run Android 2.2

Turn：mikeyangly（Come from：pdafans.com）
Touch screen, and drive signals are not supported, I hope the faithful machine can solve this problem
System Download:rayfile.com/zh-cn/files/4e80a502-973c-11df-abb4-0015c55db73d/

GREat news !! hope its just a question of time for the others drivers!

On my neotouch android doesn't boot. It stays on this:
EDIT (22:05): now it boot. I haven't got in the root of Storage Card .

s200 froyo 2.2
O ye,this is a very great news,incredible ,we jump directly to Froyo 2.2,as you say it is a matter of time and developers now.The waiting has began!
Otherwise phone boots very quck:
-no touch
-no sound
-no keys
-no gsm ...
we hope all will be on soon

good start. hope problems are possible to be solved....

Oh very goog!!
Does tsamolotoff's TS driver works?
its drivers work with ubuntu!

Wow great news!I am waiting for a full working version(rom)

Android just has more free apps than windows..
that would be the only reason i would want android

free apps... oh well
The only reason i would want android is a bunch of games ported for this system. Android for games and WinMob for everything else. and all this stuff in one device. that would be nice

very good.

Why do I have blue screen after 10 seconds working of it?

Because there are many problems to resolve to use android on our s200...The os is not alredy usable like in htc hd2,and our device is not supported like the htc one.So maybe the project for s200 is end.I wish i could use android in my phone,but maybe i will never see a usable interface

This is an exciting good news. Soon we can use the Android system has. Thank you for your efforts.

Sadly theres no kernel/android dev that has an s200, so android partly working on it might never happen, unless a dev picks it up and starts making patches/fixes for the kernel.

Not so good if you think that s200 and hd2 project started togheter,but hd2 after 1 month has a usable android or ubuntu release and our s200 has only a not usable android "desktop".Our device is not supported by comunity as hd2,so correct me if i m wrong,but i think no one still working on android s200 release

Ok guys it has been a month since first post, anyone reckon this is going somewhere? who was developing this in the first place? I am willing and ready to help in any way I can (I have stated this before) if necessary. I have a working s200, but no experience in linux programming, although I could learn some basics if needed.
Maybe we could send some android devs a pm? I mean how hard can it be if our hardware is so similar to the Liquid, AND we already have it running on our processor...?
I have seriously considered leaving the s200 and getting an HD2 by now...
Greets

no news of any progress for a while now...
anyway i never expected a fully working android on our neotouch. theres just not enough guys working on it like on the HD2...

can someone mirror this file please?
i dont want to download & install rayfile's client...
Thanks.

It s a really hard porting job...Hd2 owner has a good partialy stable android port,but as you all know there's 20 times hd2 then s200.The problem on our phone is the restricted comunity support

Well, it seems that when I got my s200 broken nobody raised the banner from my cold hands
Now my device is up and running again, and maybe i'll try to do something more... don't expect ts to work in android, as it's completely functional via tslib, and i don't know droid's architecture to determine why this PoS of an OS can't use it... if you really want it guys, why don't you experiment with sequence of input_abs_* functions within ts worker thread in driver ? There're so many *experts* who make ROMs via kitchens or do fancy icons/pictures - take up your time and learn C / linux kernel... I started with barely basic knowledge of the first (and I was lucky with the fact that there're many pre-coded drivers that simply needed some testing, or with semi- or fully-compatible initialization (many thanks to dcordes, Cotulla and the team))

[Q] A way to adapt LK to Blackstone?

Hello all XDA community,
I've got an HTC Blackstone sleeping in my desk and I wondered if any possibilities could be considered to port LK on this device.
Indeed, this bootloader have received many improvements on HTC Leo and now this one can be assimilated as a "native Android device". And the most important thing, I think, is that it is open source.
So, any dev have already worked on it?
I've see that lk can be customized depending of the memory of the device in lk/target/<target_name>/atags.c such as the "startup.txt" of HaRET.
But I don't know exactly what is the compatibility of the MSM 7201A of the device with this bootloader.
I think there are a lot of modifications (screen, display, NAND type,...) to do for adapating lk but, like everything else, a start can be great
Thanks to all answer!

LK already works on the RHOD. (Still being refined, but does work).
A dev needs to pick up a Blackstone and work on porting from RHOD, it's pretty similar.
Or, as I already suggested, if someone has an extra (or unused) Blackstone, ACL will take it and in time should be able to port it pretty easily (in theory). He's working hard on RHOD right now, but I'm betting he would help Blackstone users if someone donated a device to him.
Food for thought.

[Q] Touchscreen allignment

Hi guys,
first of all I want to thank everyone that has and is still developing for our phone, GT540 is my first android phone and I am simply amazed with its potential which wouldn't be possible for one to use without the help of people like mike gapinsky, mur4ik, miroslav_mm, tejas, among others that aren't least important than the ones mentioned.
Well, on with the matter of this post, can someone please me why the touchscreen works perfectly on stock 2.1 roms and with ported 2.2, 2.3 and 4.0 ported roms it's completely impossible to allign?
After some research, I found out that the screen is faulty and lg managed to bypass it with kernel source code... or so I believed because today, I found about TeamWinner's touch recovery and I thought "this is great, i'll try it right away but, i'll probably go back to CWM due to allignment issues..."
So if the screen is faulty, has TW found a way to bypass that? because, when I tried it the touch screen worked perfectly, like on a stock rom!!!! I doubt that TW compiled some sort of code to bypass this problem and make it work perfectly so, what makes the screen go crazy on custom roms?
Thanks in advance to all of you.

It is most likely the (library?) they use to interpret touch that causes issues
The only people that can produce fully working (lol) code is the OEM..

I get that the issue is probably in the libs but,if so why does the touch works fine in recovery and not in the OS? And is it that difficult to try to resolve this issue having correctly working source code?
I'm at the time initiating on Linux and I'll give it a go at android development soon cuz I have advanced knowledge at C programming and I'll try to take a look at it... meanwhile if someone discovers anything useful we could try to resolve this issue.

You wanna calibration?
it posible to bring in serveal ways, but devs too lazy to make this

So, any suggestions?

I have the same problem. Any answer?

There's nothing you can do about screen calibration, unless you're some advanced programmer ( that's the only way to make calibration, port it from android 2.1 )
So if you really wanna calibration the only way to have it, is to go back to 2.1.

I use LSsetting and Touch Calibration for calibration, but I can't understand if they are really working or is just placebo
Anyway, I find calibration on Miroslav ICS a lot better than on previously roms; sometimes it doesn't get the touch, but when it does it's a lot more sensitive.