Database Info

Upgrade to WM6 without USB?

Hey everyone, I'm new here , and I thought I'd start with a quick question.
My HTC Universal is a bit handicapped (bought it off a friend who said it was broken, apparently the USB plug terminals weren't fully soldered, but I couldn't connect all of them and it will only charge through USB and nothing else.)
If someone has an HTC schematic or a high-res image of the motherboard, I could possibly try to revive USB transfer capabilities (but that area is a bit damaged from not having a small enough soldering iron ), *OR*, if there is a way to reflash from within the OS using a SD card, that would be great.
Hope someone knows the answer to this, thanks!
Edit: And if it's of any possibility, how much would a replacement board be? Enough to satisfy a 100% working USB connection?

No ideas? If someone can at least give me a schematic or a high-res pictures of both sides of the board then I could possibly fix the USB to 100% functionality.

If you check the WIKI for the Universal you shoul be able to find a link for downloading the Service Manual. It shows the total un-assembly-re-assembly process step by step. You may also find instructions for SD flashing there as well. I have never flashed my Uni by SD, but I have don other phones like that. Most of the HTC's are capable. There is even info in the Service manual telling you what to have on the SD and wht to name the files from proper use. Give it a search.

Thanks! I have the manual already so I'll give it a look over. I wasn't entirely sure and I thought I wouldn't see anything but I'll look more in-depth .
Just a side note, does anyone know where I can get a replacement motherboard and how much it will be? Just curious, as that option might be available if it isn't too expensive.

WM6 & Joystick Issue

I am currently using an SPV C600 with the latest Orange ROM (2.0.14.0 & Operator Version: 11.2.1.8). It is unlocked (SIM and Applications) and SuperCID.
I followed to the T the instructions posted on this web site for upgrading to WM6. I tried all the flavors, but on all of the them, the keyboard driver seems to have a problem, because the joystick does not answers to push (down or on the side) too often.
I extracted the keyboard.dll from the current Orange Rom and incorporated it onto one of the WM6 (not really importany which one) using the ROM cooking tool. I also removed the first 2 bytes as instructed and recompiled. Loaded the new WM6 Rom with the Orange keyboard.dll but as soon as the upgrade is completed and the SPV reboots, it stays stuck on the Orange splash screen.
I put back the Orange ROM for now until I guess some advice on the step I might have missed.
Thank you

Joystick
No one else had that issue? and if so, what did you do to resolve it?
Thank you

claudef said:
No one else had that issue? and if so, what did you do to resolve it?
Thank you
Click to expand...
Click to collapse
what editing did you do? i mean e.g. initflashfiles, rgu files, etc.

ericjm said:
what editing did you do? i mean e.g. initflashfiles, rgu files, etc.
Click to expand...
Click to collapse
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=320910
and edited the initflashfiles.dat as instructed below (on the same link provided above)
7) Edit as much as you wish, dont forget to get rid of the first two bytes in the initflashfiles.dat file before you build rom again

I'm having the same problem with my Cingular 2125... I've tried all the WM6 versions and the joystick won't work right... It feels like I have to push really hard for it to work like it's a sensitivity thing.
I tried flashing back to WM5 and it worked just fine...

Sometimes my SPV C600 is fine........sometimes it's not

I had similar issues with my SDA. Every time I pushed in (enter) it would move up, and moving right wouldn't work all the time. What my problem was, wasn't software but hardware. I opened my phone, and unscrewed the joystick from the cover. What I found was a rubber ring under the joystick was out of place (probably keeping dust and dirt out), and it was interfering with movement. It must have some how shifted while my phone was in my pants pocket. All I did was remove, then replace the rubber properly, and now my joystick works just fine.

i hav had da same problem with my 2125..... but not always....

Not Hardware related
thecraze said:
I had similar issues with my SDA. Every time I pushed in (enter) it would move up, and moving right wouldn't work all the time. What my problem was, wasn't software but hardware. I opened my phone, and unscrewed the joystick from the cover. What I found was a rubber ring under the joystick was out of place (probably keeping dust and dirt out), and it was interfering with movement. It must have some how shifted while my phone was in my pants pocket. All I did was remove, then replace the rubber properly, and now my joystick works just fine.
Click to expand...
Click to collapse
For some of us, the problem is not hardware related as going back to WM5 makes the joystick work properly all the time.
Cheers..

Same problem here with Xda IQ, down function on the joystick can be tempremental.

Same here... Dang I thought it was my Tornado.. Looks like THIS SAME PROBLEM has occured to many other folks as well....

I have seen this on my tournado aswell - I dont think its firmware related, maybe a hardware defect.
On an off the joystick would go unresponsive (down especially), it got progressivly worse over 6 months or so - possibly due to me pressing harder and harder to make it work - it got to the point where the little rubber cap in the middle of the joystick poped out which rendered it unusable as it just tore up my thumb.
Joystick is also trashed now, just sits loosely and dosnt 'click' in anymore, still works if you press in though.
This all happened over about a year and a half of heavy use.
Maybe it was me abusing it but reading this thread...

Kaiser won't charge and sound does not work after flash new rom + radio

hello,
I flashed my kaiser yesterday with
radio : 1.70.19.09
rom : e. Abusalza - that is actually the Ultimate-X2.V10.Premium rom
Now my kaiser won't charge and the sound doesn't work anymore a
I have tryed to
- hard reset - problem still there
- flashed the radio 1.27.12.32 by micro SD flashing because my PC won't see my mobile phone - problem still there
I have given last night some resets with the stylus and because it was night I think I have accidentally pus the stylus into the charger hole and maybe I destroyed something but that is no reason for the sound to not work.
What should I do?
What is the best radio for my rom and for Romania - operator Orange

i believe you lost sound by flashing the 1.27 radio, i believe that is a wm6.0 radio only but i could be wrong, you will have to have the usb port repaired, no way around that, ive heard of people messing there ports up with their stylus before, your not the first. next question is before you started this thread, did you ask this question anywhere else?

so what radio should work correctly with WM 6.5 ? can you give me a link ?
no i have posted here first because I couldn't find any similar problems regarding both charging and sound

ockty3 said:
so what radio should work correctly with WM 6.5 ? can you give me a link ?
no i have posted here first because I couldn't find any similar problems regarding both charging and sound
Click to expand...
Click to collapse
A 6.1 Radio please do some research before starting a new topic, the Sticky @ the top of forum holds valuable information aswell as the WIKI.
Another good place to look is people sigs who are using 6.5 in the threadz or on the Kaiser board.
Also regards charging there has been threadz where it's just been the usb port is damnaged and pulling one of teh connection terminals has fixed it.
Good luck

yeah, thanks you wore right... I flashed a new radio 1.65.20.29 and the sound works now. A strange thing is that if I put my headsets into the USB port they are working so do I still have a chance of just mismatching between the rom and the radio ?
PS: can you move my post in a section that is not in the first page so that I can still post?
10x

Try to flash the shipped ROM for your carrier and see if the problem persists.

I can't do that. I don't even remember what rom was that because it was a Portuguese version and I didn't understand the menues so I flashed it 2h after I bought it 1 year ago.
Now I am at 10% with the battery and I can't flash anymore any other kind of rom.... but I was thinking to go to a phone shop and charge my battery just until I flash it again.
now I have 2 questions:
- does the ROM has anything to do with charging the battery (because I thought that the radio does that )
- how can I charge my battery any other way ? If i put a 5V transformator on the + and - of the battery will it charge? can I damage the battery this way ?

ockty3 said:
I can't do that. I don't even remember what rom was that because it was a Portuguese version and I didn't understand the menues so I flashed it 2h after I bought it 1 year ago.
Now I am at 10% with the battery and I can't flash anymore any other kind of rom.... but I was thinking to go to a phone shop and charge my battery just until I flash it again.
now I have 2 questions:
- does the ROM has anything to do with charging the battery (because I thought that the radio does that )
- how can I charge my battery any other way ? If i put a 5V transformator on the + and - of the battery will it charge? can I damage the battery this way ?
Click to expand...
Click to collapse
- answer to first question most likely not. Some roms do drain battery life quicker than others but charging is not specific to a rom.
- i haven't tried this. there is a pretty good chance you will as i don't think your phone battery has clearly labled + and - current sources. You might want to hit mike chanon up on this. "mikechanon" one word.

My feeling is that there is now damage to the usb port after pushing the stylus into it.
You say above that would not affect the sound - BUT the sound is output through the usb port and bent or crossed pins in the socket can cut off sound as well as stopping charging. This can mean that sound may still work using the headphones.
Get a magnifying glass and a strong light and examine the port. Bent pins can sometimes be straightened using a needle. Hopefully the port has not got cracked solder joints to the motherboard.
Because you have both charging and sound problems (and PC won't see mobile), I think there is a stong possibility this is a hardware not a software problem. (even if it started as a software issue)
Mike
EDIT - there is also a plastic part that can break off on some usb ports - from memory, I can check later, the Kaiser has one of these.

the reason why your usb port got damaged is probably because you stuck the stylus in it (like everyone is saying including yourself).
the reason why you accidently stuck the stylus in there is because you were constantly soft resetting your device.
the reason why you were constantly resetting your device was because you were trying different things to get the sound to work...including trying a radio which is meant for winmo6.0
the reason why you were trying a radio meant for winmo6.0 is because you didn't read the FAQ on the first page of the pda corner ultimate thread.
the reason why you are looking for a link to the suggested radio(s) is once again lack of reading the FAQ. the FAQ on the first page of that thread has links to the correct radio.
its a sad chain of events but the root cause is that you simply did not read the FAQ on the first page which clearly states which radio is recommended and has the link right there!
i hope you as well as other people new to flashing ROMs can learn from this experience and just try to start reading what is clearly written.
i hope you are able to repair the damage of the usb port. good luck!

mikechannon said:
Because you have both charging and sound problems (and PC won't see mobile), I think there is a stong possibility this is a hardware not a software problem. (even if it started as a software issue)
Click to expand...
Click to collapse
The the sound problem is now resolved by changing the radio - the sound works now.
I will try tomorrow to see if I can do something with an magnifying glass.
10x, I will post after I'll try to repair it.

so I took a magnifier glass and you wore right one of the pins was stuck into the plastic part. I took it out and I think now it's ok.
10x mikechannon

[Q] Install stock kernel without any method which uses charging port?

Greetings to all of you. I hope you be very patient with my poor english (I write and speak spanish) and this long post (please, read all of this) and please help me with this question, my first question here.
I am a XDA user a time ago, 2 years or least; I have flashed the kernel or the ROM of a lot of Android devices (+10, tablets and phones) using your knowledge posted on this wonderful community and I talk about this to prove that I'm not a totally noob and I never had a problem like this before; sadly, this happens with my own phone: SGH-T959V.
The charging port stopped working as data transfer port and just worked as charging port, this occurred just 2 months ago; but it was not relevant for me because I did not use the function in a long time, I used to charge my phone when it requires energy and nothing else. But I read about a CyanogenMod update (unofficial) for my phone and decided try it. Then I download it, install it via CWM and it worked successfully; I had a beauty JB 4.2 running on my 3 years old phone. I noted that there was a trouble with the RAM size, the new CM ROM just recognizes 346 MB of the RAM and the last ROM (CM 9) could recognize the 512 MB. I looked for a post here which talked about my problem and I found it, they suggest to install another kernel and I proceeded to do it. It was the 3 am or close, I was tired and here comes the first big mistake: I download and install a wrong kernel, a kernel for the T959, not the T959V. I cannot remember the name of the wrong kernel (because I deleted it from my PC) but since I installed it, the phone is always on recovery mode and the title of menu is: “Devil touch recovery v6.0.1.9”.
I tried to install the last kernel which worked fine (hefe-kernel-v0.8.1) and I always get the following messages: (as with any other kernel or ROM)
E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
E:failed to find “cache” partition to mount at “/cache”
Status 4 error and Status 7 error appeared too. (I solved the status 7 error modifying the Meta.inf data into the zip)
I formatted the SD card, put the kernel there and tried again to install it, but I have no success. I fixed permissions, tried to wipe data, wipe cache, but the same messages appeared. I look for a solution on some threads here and read about the cache format, they talk about ext3 and ext4 but I cannot find the way to reformat the phone with a kernel which has the right format to then, finally, install the right kernel for the phone. Well, at this point, I thought about all the mess up and then I conclude: Why the hell I don’t just recover the phone via download mode and Odin? If you remember, the charging port just worked for charging, not for data transfer or any other usb function; yep, I got it on that dawn: I was screwed.
Next morning, I carried the phone to the technical service (here in Cali, Colombia. It is not from Samsung) looking for a new charging port, the technician told me that he had the right repairing part; he said that was the same of the SGS3 (IFC700). I returned the next day for my phone and I found a major disaster: the “technician” did not apply properly the heat gun and all the electric conducting lines (the 7) were pasted at the pins of the old and damaged port.
I searched for another technician and thanks God could find one that gave me hope, although somewhat unreal, for my bad luck. He suggested me that if we could detect the origin of the electric conducting lines on the mainboard (unit U701, specifically) we could make a bridge between them and the pins of the new charging port; the problem is that I surf and surf through all internet and found only this pdf: On bit ly :/1dS7M61 (I cannot post links yet.)
But here, they do not give information about the PCB and the specific connections for pins, so, here comes my first question:
Do you know the specific origin of the seven electric conducting lines of the charging port? And, if you do, do you know if possible make a bridge with them?
In case this does not work, do you know how to recover the phone to the original kernel and ROM (as Odin does) but without using the usb cable, just the SD card?
I will stay watchful. Thank you for your time, your patience and your help.

Most of the lines for the pins are on the surface layer and go right up to the connector so unless you have ripped them all the way off you should be able to tell what goes where. The first and last connections are GND and there's a big area of gnd on either side of the connector. There are 2 other lines that are VCC I can't remember which lines now from memory but it should be fairly obvious to a technician. The last 3 are the tougher ones. TX and RX each have a tiny little line on the surface layer which leads up to the corresponding pin. The last one is the host mode pin which actually comes out from inside the board into the pin itself. If you look really close it looks like a little dot where the pin would sit. That last one I found nearly impossible to repair, but the other lines you can peel off the coating and solder a really small wire on top of them to complete the connection. All the more important lines are visible so unless somebody really jacked up your phone a decent tech should be able to repair it mostly.
If this doesn't work you're screwed. And even if you can repair 6 of the 7 lines the one that tells the phone to be in dock or download mode is necessary if you can't get into download mode with the volume buttons.

TwitchyEye said:
Most of the lines for the pins are on the surface layer and go right up to the connector so unless you have ripped them all the way off you should be able to tell what goes where. The first and last connections are GND and there's a big area of gnd on either side of the connector. There are 2 other lines that are VCC I can't remember which lines now from memory but it should be fairly obvious to a technician. The last 3 are the tougher ones. TX and RX each have a tiny little line on the surface layer which leads up to the corresponding pin. The last one is the host mode pin which actually comes out from inside the board into the pin itself. If you look really close it looks like a little dot where the pin would sit. That last one I found nearly impossible to repair, but the other lines you can peel off the coating and solder a really small wire on top of them to complete the connection. All the more important lines are visible so unless somebody really jacked up your phone a decent tech should be able to repair it mostly.
If this doesn't work you're screwed. And even if you can repair 6 of the 7 lines the one that tells the phone to be in dock or download mode is necessary if you can't get into download mode with the volume buttons.
Click to expand...
Click to collapse
Thanks for the fast answer! I will show this to the techinician and I hope that he can repair it; although I really think it is almost impossible, the lines are all deeply ripped, just the third and fifth line survived the attack.
Again, I want to answer just one more time about fixing the problem of installing kernels or ROMs via recovery mode (please read again the first post): "E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
E:failed to find “cache” partition to mount at “/cache”
Status 4 error and Status 7 error appeared too. (I solved the status 7 error modifying the Meta.inf data into the zip)"
Do you know how to fix this? Or install a stock kernel without those problems?
Thank you!
PD: I will post the answer of the technician to this.

Yeah the kernel you flashed screwed up your phone and the only way to recover is through heimdall or Odin which you'll need usb for.

Thank you again for your attention. Unfortunately the technician could not find the download mode pin, so it's official: my phone is a paperweight. I thank you again for your help and interest, have a good weekend.

First of all, fo ur problem, I believe that the only way u can save ur phone is using heimdall to flash another mtd kernel (if u can luckily boot into download mode) but sad that ur usb port was doom (correct me if I am wrong).
In addition, why on new kernel the phone just shows 384MB of RAM? Just fyi, new aries kernels changed the way counting RAM as they don't count the reserved RAM that the init system took but just the remain. As if u look into the kernel, there is somewhere says that RAM = total subtract reserved (in a specific calculation not words). That's why u saw 384MB even in fact we have 512MB. N why it is 384 but not 400 or 450, idk lol. So if anyone is curious bout this can have this rep as an answer as well
Sent from my SGH-T959V using Tapatalk 2

You don't need the download pin if you can get into download mode by holding the volume buttons. If you need a usb jig to get into download mode then you're out of luck. Otherwise your phone will function normally except when you put it in a dock or try to use otg which as far as I know we don't have support for anyway.

PX5 cannot boot anymore (SOLVED)

UPDATE 24.11.20
I have recovered my HU by reading the whole night on this forum and TO THE AMAZING work of several people here.. especially GREAT GREAT thanks to marchnz and to scorillo_ro I build myself the USB cable and followed all the instructions I could find. With some moments of headache .. finally I flashed a new ROM and it booted up!!!
I have to go down on my knees to you guys for the super AMAZING work you have done. Wihtout you I woulld be now 180€ poorer. (new HU).
___________________________
When booting I get this errors...
I got a MTCE_LM PX5 unit (8Core A53 CPU 2GB RAM)
It is always very difficult to enter Recovery so I tried several times but it doesnt work. Either I just didnt mage it right or the recovery is broken.
In the pictures you can see 2 different messages. I have the feeling the long message version is when it normally tries to boot into the OS but fails.
The short message looks like when I managed to get into recovery reboot but it fails too.
Or its the same message .. it just blinks up for 10ms or something and dissapears and then blinks back after 5 secods ... I had to take like 20 photos to catch it. So maybe its the same actually.
Anyone has a clue what I can do from now on?

Great to hear another success story.
It took alot of effort to develop the method, for which was made possible by a member posting the schematic diagram to the forums for the benefit of all. Your post helps other too, so thanks!

Thanks again for the endless hours you put into developing the esiest method possible (for this SOM).
I am REALLY pissed at the Chinese somehow. They develop great stuff sometimes but fail to think over the edge. It is so easy to destroy your OS by small or stupid mistakes. And then there is no OTG to easily reflash the rom. I mean the hardware supports it. They could (and luckily and finally some new models support OTG on at least one USB port right away). But why was this not implemented right from the first designs for the headunits is puzzling me.
I would love to help anyone who needs help. But I have the PX5 HCT V4 SOM so you people wrote exactly how to do it for this specific SOM... I am not sure I can add anything of what wasnt said already.
I just had 2 main issues. The USB cable was found but not recognized at first.
So what I figured out was that you should not use more than 2 resistors to make the voltage division (thats what I did first) and I just had 2.8V on the division. I did it fast and not clean, means. No really good soldering connections.
Then I rebuild the whole thing used a good cable just 2 resistors (2kOhm and 3.3kOhm) and I soldered everything as clean and as compact as possible with least distanced to each part. So it gave me 3.1V on the division.
This was recognized immediately. Ahh.. and it helps too if you can use some contact spray for electronic parts. Because the pins sometimes do not sit well inside the SOM board.
Then the flashing of the ROM didnt want to work. It gave me an error on downloading the firmware.
Solution was to simply erease the flash memory.
But everyone who goes to your thread and reads at least the first 20 pages gets rather the clue on the minor issues. But its actually all written in there... just need to read it