I tried using the Siemens upgrade for my SX66, which made it display Serial on the top and v2.07 on the bottom
I followed the steps reccomended for when such a thing takes place (ie doing a flash reset on the phone) but now the screen remains black and doesn't even display Serial and v2.07
When plugged into my computer, absolutely nothing happens and the computer does not recognize it.
I eventually got the screen to display USB, ran the update again but after about 15 minutes I got an error screen on the PC that read:
Error 201: Get Device Data Error
Can not get device data. Please make sure device are connected to PC and execute this update utility again
Please help!
Related
I tried to upgraded my SX66 system and radio rom. When I clicked "next" on the Blue Angel Flash ROM Tool to start up upgrade, the pocket pc screen turned off and my desktop was diconnected with the pocket PC (activeSyn showed "Not connected". And the desktop showed up the message "Cannot recognize USB device". I took a look at the PPC, its backlight was off and only had a message "USB v2.07" showed up". I tried to reset the PPC, but it is not working anymore, only show the message "serial v2.07". Any one help please!!!
DONT PANIC!
Try a hard reset, thats power button and reset switch at the same time..
Hi folks,
Very strange: I tried to connect to the PC with ActiveSync 4.1 and the BA in the bootloader mode. Didn't connect. Tried a couple of times, reinstalled AS etc. No chance.
Therefore I wanted to be sure, there is no connection problem, I started the MAUpgrade tool, which connected successfully and showed the EPROM versions on the screen. So I started the upgrade procedure, as expected the BA went in the bootloader mode, but as before, from there nothing went on - it was not recognised by the PC or AS.
The strange story about it is, I connected very easily in the normal mode, I upgraded already in the past successfully ...
BUT NOW I'm really in trouble, because I can't exit anymore the bootloader mode. I tried a hard and soft reset, I have removed the battery for 10 minutes .... Now way, the sceen is always in bootloader. If I put the device in the cradle, it recognizes this, by showing USB, without cradle, its Serial. The bootloader shows the version 2.08
Shoud I replace the device and enquire with my provider for a new one?
Thanks and looking forward to hear from you, Alexander
Hello!
I have this problem:
I've installed WM6.5 on my Trinity, and it worked well, but today I wanted to try WM6.1 (0.4.9.0 digital) also. The following happened:
Everything worked fine, but at 54% flashing my brother lifted the phone, possibly it lost the USB-contact, because the flasing stopped with an error message (unfortunately can't remember the error number). Since then if I try to flash it with WM6.1 or WM6.5, after 1% the phone resets itself, and the RUU gives a 270 error.
I have the original WM5 ROM also, but if I try installing it, after "Verifying information on your PDA Phone" screen I get a connection error 260.
What can I do???
After the phone resets itself, I can see the HTC logo, and the red letters and numbers, but that's all.
If I try HardSPL, I also get a 260 error.
Can you enter bootloader manualy?
If you can than see SERIAL change to USB when connected to PC it should be OK.
if you have a SD card, you can also try to flash "manualy".
- put your RUU... NBH at the root of the card,
- rename it trinimg.nbh,
- reinsert the card in the phone,
- enter in bootloader (power+cam+reset)
you will have a grey screen asking to push "power", do it and that's it.
if USB is well working, maybe you just need to reflash the hardspooler.
Thank you for your replies.
Fortunately I solved the problem.
I did the following:
1. To be sure, do all the stuff on a Windows XP machine
2. DISABLE "Allow USB Connection" in Active Sync so you see a small red X symbol next to the Active Sync symbol
3. Start the device into Bootloader mode (Cam+Power+Reset) and connect the device to your PC and make sure USB is written on the bottom of your screen (NOT Serial!)
4. Download splxploit (http://forum.xda-developers.com/atta...0&d=1180043588) and execute unlock on your PC
5. Follow the instructions
6. Download HardSPL (http://forum.xda-developers.com/atta...8&d=1185364317) and follow the instructions
7. Finally (to be sure) restart into Bootloader mode and check if SPL is showing "SPL-1.30.Olipro) - if this is the case you've done it !
8. Flash your preferred ROM via miniSD or USB connection
I m glad you solved this. Every day another new way of solving the flash problems.
Hi to All guys
i've got a trinity from my work and it has a custom rom.
I wanted to changed the rom so i download a wm 6.5 and erase the trinity with mtty. After that i try to install the rom with he RUUUupdate, but it get error 270.
Only in that moment i read on the bootloader and see that it haven't olipro or another HARDSPL installed.
So i looked for a solution and i try the unbrick with the splxploit. I did it and i get olipro on the bootloader, but i don't know how go on with install, if i use the exe i get 260 connection error.
Can you help me?
Hi,
Im using a stock v30a rom and windows 7.
Yesterday i tried to root my phone with the latest version of AIO tool.
I followed instructions to the letter but while rooting the screen remained blank
AIO tool displayed a message "nvflash started" and went idle.
Rooting older versions was a matter off seconds so after a while i figured nothing
is going to happen and unplugged the usb cable.
The AIO tool then displayed a "usb write error"
The phone is working fine now but when i connect it to my pc in mass storage mode
It disconnects and reconnects all the time as if i was taking the cable in and out.
I did a hard reset , reinstalled LG united phone driver but that did not help.
Update: I connected the phone to a pc at work and mass storage works fine.
Can someone please help me uninstall the nvflash driver?
Looks like the presence of both drivers confused windows.
Figured i post the solution just in case someone has
the same problem.
Remove battery plug usb cable with volume up and down pressed,
Windows recognise "Nvidia usb device" go to device manager and
uninstall its driver.
If next time you connect the phone you get "cdc serial device not
connected" error reinstall lg driver and you re done.
I've tried both normal & recovery booting and it doesn't turn on. Doesn't show the flashing logo either so I think I might be SOL unless there's a way for me to save it .
BAMvsGAME said:
I've tried both normal & recovery booting and it doesn't turn on. Doesn't show the flashing logo either so I think I might be SOL unless there's a way for me to save it .
Click to expand...
Click to collapse
If there is no sign of life, no known fix
send back to Amazon for a one time exchange if still under warranty
Sent from my sailfish using XDA Labs
Same thing just happened to me. I have a blank screen will not go into recovery mode or even pull up the screen.(black Screen) I just tried to downgrade to root. get nothing now. Take that back, my pc keeps beeping to leave me know a usb connectes, but then disconnects. tried different cables, one gives me a message USB Device not Recognized The last USB device you connected to this computer malfunctioned, and Windows does not recognize it. Another Cable in Device manager pops up MediaTek PreLoasder USB VCOM (Android). then disappears like every 15 seconds.
ivancunningham said:
Same thing just happened to me. I have a blank screen will not go into recovery mode or even pull up the screen.(black Screen) I just tried to downgrade to root. get nothing now. Take that back, my pc keeps beeping to leave me know a usb connectes, but then disconnects. tried different cables, one gives me a message USB Device not Recognized The last USB device you connected to this computer malfunctioned, and Windows does not recognize it. Another Cable in Device manager pops up MediaTek PreLoasder USB VCOM (Android). then disappears like every 15 seconds.
Click to expand...
Click to collapse
The following downgrades will permanently brick device:
- 5.3.2.1 to any lower version (no rollbacks possible)
- 5.3.2.0 to any version below 5.3.1.0
- 5.3.1.0 to any lower version
- 5.1.4/5.1.3 to any version below 5.1.2
- 5.1.2/5.1.1 to any lower version
This information is clearly spelled out in forum index. Contact Amazon for an exchange if within warranty.