I know this isn't quite the right forum to post stuff about gps navigation systems, but since we have some pretty good embedded systems engineers here i thought i would give it a try.
following problem:
i friend gave me a _really_ no name navigation system (PND) which he bricked because he edited things in the wince registry and accidently made something (don't ask me what) that made the PND crash. since then there is no lifesign of the pnd anymore. When i plug in the device, windows detects an "unknown device" and a red led is on on the device. thats all. There is nothing on the screen. Since the pnd has only two buttons (power and reset) there was not much i could try. i tried "hardresetting" it like i used to do on some htc devices (power and reset at the same time, different intervalls etc.) nothing worked out. i know that if this device would be not such a noname sh*t, it would be probably easy to get an wince image and flash the device via sd card. but since my friend gave me this device for free, i thought i'll try everything i can to get it running again. because the fact that he messed with the os made the pna a brick, a hardware failure can't be it.
some of the things i was wondering:
since it is nevertheless nothing more than just some device with wince, is it possible to somehow access the device to get it up and running again ?
is there a way i can flash the pnd in this state ?
the "red led" reminds me of a bricked qtek 9090 which had the same simptoms. is there maybe some "connection" between this since both are wince devices?
So here is again what i know for sure:
PND gives no lifesigns exept the "red led".
Windows detects an "unknown device".
Battery is fine (opened up pnd, checked voltage, is ok)
PND seems to be a "siemssen 6088" aka "strato 60800" aka somekind of a "malata [unknown model]" aka according to some forums somekind of a navigon devirate.
had wince 5 running.
registry had been messed with, since then dead.
any ideas what can be done?
thanks in advance.
Hi,
I just crashed my phopret. BUT due to some good ideas of user Users i solved my issue. I want to tell you how.
My history:
I already had the "update package" installed and used several WM 6.1 ROMs.
I love the Diamond rom from vincent. see link
Then i tried to flash my prophet with a rom for the charmer. Hm, bad. It crashed when it tried to restart. Anyway.
I tried to reanimate it. It failed. I stopped for that moment and started again a day after.
Now it runs again. Juhu. I tried every update , orginal ROM, Tera Term etc. But always the same issue:
Bootloader starts but only runs until info screen with the isp number etc.
"The Charmer rom erased everything so there was now Operating system at all."
Even the bootloader was not the original one with 3 colours and I was not able to connect to the PC because it stopped booting.
How to solve this issue:
Download the "Lazy Tool" from here
If you need additional info read this otherwise try it my way
Flashing Tool thread
1. Press Camera Button and Softreset (with stylus).
2. Remove ONLY the Stylus. --> Get the 3 Colour Screen.
3. Connect with Cable to the (this important) USb Port at your Mainboard (native ports).
4. Unpack it.
5. Run "Upgrade.bat" and keep the window opene in the Background
6. Go to "lib" and run the G3 or G4 "Rom update utility"
7. follow the introductions
Finish. You did it. Great job.
To get a good Rom.
Use the update utility and run after a reset the vincent rom.
BE ALWAYS AWARE THAT YOUR PROPHET IS CHARGED. Mine wasn´t once and i wondered why it always restarts again.
Some nice progs are:
Slide 2 View (Album like on the iphone)
Slide 2 Unlock (unlock like on the iphone)
Icontact (contacts like on the iphone)
Touch Response (get a vibration by pressing a button)
G Alarm (good alarm in the morning)
BT Remote (to remote powerpoint by bluetooth)
Thanks to everybody who develops nice tools like the "lazy tool" and shares his/her experiences with WM. Good job Friends.
Greatz,....
I recently (few days ago) bought my S710 (a.k.a. Vox) and it came with the WM5. So I found this forum nad Dr.Gonzo's thread about WM6.1 ROM (http://forum.xda-developers.com/showthread.php?t=384129), DL-ed the necessery sofware and followed the instructions (which seem to me like a peace of cake )
For some unknown reason I cannot finish the flashing of WM6.1, when I have to run the RUU I start the instalation, and after a minute or so (when the progress meter appears) the software says that the device is not connected. I tried this several times, always with the same problem.
what am I doing wrong? Please help me, so I don't feel like described in the subject of this thread.
P.S. and sorry if I made any gramatical errors, english is not my native language.
rbojan said:
I recently (few days ago) bought my S710 (a.k.a. Vox) and it came with the WM5. So I found this forum nad Dr.Gonzo's thread about WM6.1 ROM (http://forum.xda-developers.com/showthread.php?t=384129), DL-ed the necessery sofware and followed the instructions (which seem to me like a peace of cake )
For some unknown reason I cannot finish the flashing of WM6.1, when I have to run the RUU I start the instalation, and after a minute or so (when the progress meter appears) the software says that the device is not connected. I tried this several times, always with the same problem.
what am I doing wrong? Please help me, so I don't feel like described in the subject of this thread.
P.S. and sorry if I made any gramatical errors, english is not my native language.
Click to expand...
Click to collapse
you should firstly uspl your htc s710!(first treath) do do this its necesary that you app unlock your vox(as described in uspl treath) then you can update to any rom!(made for your device!)
...let me explain...
Like in the manual, first I rebooted (hardware reset) the device, then run SDA application unlock, soft reset, copied the necessery files to the root directory, run heret.exe through the .bat file.
the penguin appears on the screen for a short time, then the screen goes dim (like described). this is the moment I should start RUU, which I do, but one of 2 things happen:
1) either the RUU doesn't even recognize the device, and reports to check USB cable. The screen remains dimmed,
2) or it recognizes it, shows the USPL-vox on the device and starts update. At the very begining of update (zero or two %), it says that the device is not connected. the vox screen shows some info, and it's three-colored - blue, green, red (if I remember correctly). the RUU software exits, and then I hardware reser the device, to make it functional, but still with WM5.
what am I doing wrong?
EDIT: It's actually WM6, I needed a program to tell me that
Seems like your USB port on the PC is not working properly with the Vox. Try another Port or better an other PC to execute these tasks.
Could also be the cable - this may be easier to change.
I don't think that is possible, it's the same cable I use for connecting through ActiveSync and it works flawslessly. Any other ideas?
it's a standard USB-miniUSB cable I use for my old motorola mpx200 and my camera, don't beleive there can be a problem there?
Just try it - AS transfers a few bytes - a ROM is several MB. This is no proof.
Windows (ROM Update) also talks to the USB port in a different way than AS, so why not eliminating all parts that are outside the device (you have no other choice anyway).
- new/other USB cable
- new/other USB port
- new/other USB controler (e.g. other PC)
Can you not upgrade new rom from htc site?
I just traded my X1 for an x7510, but find many of the settings not reacting at all. It's apparently running a version of 6.5
USB to PC does nothing when clicked, along with various other settings such as Device Information and Format Microdrive.
I can't connect to my PC, so I can't even begin to sync or think about updating the ROM to something that might work again.
Does anyone have any useful tips how I could get this thing working again?
Go into bootloader, its camera button and reset. And it will work. Thats the whole points of a hard-spl...Make sure you have the correct drivers in windows.
...
Well, that's such an obvious solution I rightfully feel like a n00b now.
Thanks.
My phone is dead after switching external sd with internal sd via CWM script .zip file and a little tinkering in the phones system files.
(“I have done this before with success but had just flashed new firmware, and in the rush I was in wile doing it I obviously did something majorly wrong and super bricked my phone”)
After rebooting to complete a step I was doing, the phone did not turn back on, the pc does not detect it properly anymore, no button combinations work, such as pressing vol up when connected without battery, power button and pressing up + vol. No RESPONSE:.
when plugged into the pc it just flashes "OMAP4430 device" but appears and disappears all the time in device manager, now I know all drivers are correct and how to go into download mode, recovery mode and every trick you can with the O3D but none work anymore, phone does not turn on and it only recognizes it for a second showing “OMAP4430 device”.
PS Sorry for the new thread but I have searched the forum and the internet with no real answers, it would be great if there’s a fix for this situation or is my O3D dead to the world never again to be reborn.
NOW IF ANY ONE HAS MANAGED TO FIX A TRULY BRICKE O3D LIKE MINE PLEASE HELP!!!!!!!
sounds like a harware brick i did that to my thrill had to take it in
That’s what I’ve been fearing, my other issue is that the phone is actually a LG thrill from at&t I just call it a O3D because in Australia were I live we only have O3D, and let’s face it they are basically identical, any way would that mean I would have to send it back to the USA for repair?
well is it under warenty? if so youll have to send it to who ever you bought it from. if it isent ull have to get a new logic board and relace it your self or have some one relace it. or send it to lg to fix it
I had a similar problem when installing rom. KDZ:
http://forum.xda-developers.com/showthread.php?t=1473781
http://forum.xda-developers.com/showthread.php?t=1244490
The problem with "OMAP4430" device I solved by connecting the phone to the computer via a cable from HTC Wildfire (such problems I had with the original cable, LG).
It can change the cable will solve the problem.
I wish you luck.
(google translate)
You have to remove the battery when omap flashes on device manager let go off the button and push and hold it agen it should stay. try this time omap like have your cursor ontop of omap4430 as soon as it appear quickly right click properties and find the driver unplug reconnect it will install the driver when it detects it agen i think with this phones its impossible to hardware brick the phones if only it was easy like samsung just plug in download mode let drivers install and push start button done. if flashing a phone was like a movie lg would be inception
trust me i totaly bricked my phone i tryed every trick pulling the battery out and putting it in in download mode problem was omap didnt even show up just the other one and it would flash on and off way to fast to click on it in device manager then it would just stop.
So did you end up taking it in?, it should still be under manufacture warranty well hopefully I got it in october and I don’t even think the O3D has been out for a year yet.
defcomg said:
You have to remove the battery when omap flashes on device manager let go off the button and push and hold it agen it should stay. try this time omap like have your cursor ontop of omap4430 as soon as it appear quickly right click properties and find the driver unplug reconnect it will install the driver when it detects it agen i think with this phones its impossible to hardware brick the phones if only it was easy like samsung just plug in download mode let drivers install and push start button done. if flashing a phone was like a movie lg would be inception
Click to expand...
Click to collapse
The problem is that it only starts flashing with the battery removed so, and I can’t get into download mode at all, which is when it normally stays there and detects it properly, otherwise the drivers are all installed.
If it flashes omap its not a complete brick. If all fails try the resistor cable. You can find a post around in the forum
I have tried the resistor cable using 910k resistor, and I even checked it on the multimeter and it reads 908k resistance which should be ok since I think you can allow for a 1% difference.
I could figure out that ur device can be detected as OMAP, this means it isn't bricked totally, please be sure U remove UR battery, connect ur USB--phone side, then press volume up and insert the USB--pc side while pressing the button and continue pressing while ur pc is installing, first it will show OMAP, then after 10-20 sec it will show COM added, don't stop pressing until it finds the COM and installs it, then directly stop pressing and insert battery and don't try to turn it on and start flashing as usual
try to use other USB cable model like sony ericsson, it never failed me
hoping U will be lucky
See the problem is that no button combination work on the phone, pressing a button is like talking to a wall you get no response lol.
I have the same issue and I bought my phone off of Craigslist.. is there anything I can do? I cannot send in via warranty because I do not know when the phone was bought.
cephasara said:
I have the same issue and I bought my phone off of Craigslist.. is there anything I can do? I cannot send in via warranty because I do not know when the phone was bought.
Click to expand...
Click to collapse
its hardware bricked need a new logic board sorry to say
Hi, i had the same problem while upgrading to gingerbread. What windows version are you running? Ihad the same problem using win 7 x64. Got to a win xp computer with no lg software installed and used the tutorial of unbrick from this forum. had to try several times, but at least step by step my phone got back to life. Main thing is to get omap drivers installed on XP with no battery. Then taking the other steps mentionened under unbricking your phone in this forum.
Hope it helps
I have the exact same problem and NOTHING works.
Just to clarify everything, you guys had the same problem where the OMAP4430 device appears and disappears over and over again in device manager and by doing what you all describe, the phone got brought back to life?
Because none of those things work for me, I even tore an old sonyericsson phone apart to get the phone pins connected to my O3D battery and see if the old phone turned on, which it did, so the battery does work.
I installed the OMAP4430 driver without any problems and I guess from here, everything seems to be working for you other guys, right? Because the OMAP4430 is still getting connected and disconnected 10000 times BUT as a "Known" device which has the driver installed.
No need to answer this with "you need to send the phone to LG". Just want to see if I'm on the same track as the guys who got their phone working.
Btw, mine got bricked when formatting the external SD card with CM. Seems as if CM formatted something else..
KurdX said:
I have the exact same problem and NOTHING works.
Just to clarify everything, you guys had the same problem where the OMAP4430 device appears and disappears over and over again in device manager and by doing what you all describe, the phone got brought back to life?
Because none of those things work for me, I even tore an old sonyericsson phone apart to get the phone pins connected to my O3D battery and see if the old phone turned on, which it did, so the battery does work.
I installed the OMAP4430 driver without any problems and I guess from here, everything seems to be working for you other guys, right? Because the OMAP4430 is still getting connected and disconnected 10000 times BUT as a "Known" device which has the driver installed.
No need to answer this with "you need to send the phone to LG". Just want to see if I'm on the same track as the guys who got their phone working.
Btw, mine got bricked when formatting the external SD card with CM. Seems as if CM formatted something else..
Click to expand...
Click to collapse
So let me get this straight. Like a few months ago, there was a way to completely destroy your phone:
install CWM and run an OTA update on stock rom.
That completely ruined my phone. It was explicitly said that no unbrick method is available.
Now I hear several people reporting yet another unfixable brick, caused by
- Erasing your SD card through cyanogenmod
- Formatting /data ?
All the available methods of unbricking are said not to work. And by those methods I mean
- Opening recovery and do a factory reset (recovery can't be opened I heard?)
- Connecting to a Windows 7 PC with battery out and volUp depressed (device disappearing reappearing)
- Connecting to a Windows XP computer With battery out, volup depressed (Same problem as Windows 7?)
So to put it simple:
Doing some things with CWM OR CyanogenMod can render your phone unfixably bricked. There is a genuine risk in hard bricking your phone when you have CWM and/or Cyanogenmod installed.
I'm not going to install either of those for that very reason.
If the omap 4430 is detected when connecting the phone, then the phone should be recoverable. Try another pc system and then use the official lg recovery tool entering the imei number which should hopefully restore the stock rom.
Can i clarify whether or not any other devices appear in the device manager (Remember to hold the up button without battery until these appear and then insert battery after
The entries in device manager that should also appear would be something such as the following (This would probably vary based on whether in normal connection mode or flash mode)
PORTS
LGE android platrom usb serial Port (Com x) x may vary on system
UNIVERSAL SERIAL BUS CONTROLLERS
LGE Android Platform Composite Usb device
thealgorithm said:
If the omap 4430 is detected when connecting the phone, then the phone should be recoverable. Try another pc system and then use the official lg recovery tool entering the imei number which should hopefully restore the stock rom.
Can i clarify whether or not any other devices appear in the device manager (Remember to hold the up button without battery until these appear and then insert battery after
The entries in device manager that should also appear would be something such as the following (This would probably vary based on whether in normal connection mode or flash mode)
PORTS
LGE android platrom usb serial Port (Com x) x may vary on system
UNIVERSAL SERIAL BUS CONTROLLERS
LGE Android Platform Composite Usb device
Click to expand...
Click to collapse
They said that the omap driver keeps appearing and disappearing. You can't do anything if a driver does that!
Sent from my LG-P920 using XDA