For those who stuck at the warning screen of: 150 connection error.....
Try to do a bootloader update (can be found on xda-ftp), wich most of the times work, and when the update is done, don't reset your device as asked, but immediately update your device with your desired rom.
This has worked for me, after days of no succes and having constantly the 150 connection error message.
If this thread or solution has already been created, then i apologize...
Great succes..
Related
Hi friends,
I got HTC S620 Smartphone from my brother US. It was working well for the past 6 months and i updated to WM6 also now suddenly it got corrupted and shows the following error. It takes 30 min to boot and hangs with this following error. i Unable to do anything. I tried to update WM6 again but same still same error. I gave it to HTC service center in chennai and he unable to resolve this problem. And I Unable to open folder with usb cable. Any one please help me.
t-zones
While retriving the URL :
http://wap.t.zones.com
the following error occured:
Network error 19:
The Attempt to connect to the server failed
More Information Try Again
Alert
Cannot Start 'winwapexe'. A critical component
is either missing or failed due to low memory.
Try to hard reset your phone.
Well I've tried everything possible, updated device manager fro vista. MDA Vario 3, connects for active sync but after running KaiserCustomRUU.exe. where it update the crrunt ROM version... it changes the screen into 3 color screen , after few minutes in the same condition............ 0% process........ and then........... shows me an error message as under:
ERROR [262]: UPTAE ERROR
The ROM update utility has encountered communication errors during the update process. The program will guide you step-by-
step to recover from the errors so you can continue the update.
and i need to restart MDA. although on recovery process it directly come to normal screen instead of 3 color screen, which means (i guess) it never started changing ROM current picture.
Any help about it plz.
Regards
Iaan
iskhan said:
Well I've tried everything possible, updated device manager fro vista. MDA Vario 3, connects for active sync but after running KaiserCustomRUU.exe. where it update the crrunt ROM version... it changes the screen into 3 color screen , after few minutes in the same condition............ 0% process........ and then........... shows me an error message as under:
ERROR [262]: UPTAE ERROR
The ROM update utility has encountered communication errors during the update process. The program will guide you step-by-
step to recover from the errors so you can continue the update.
and i need to restart MDA. although on recovery process it directly come to normal screen instead of 3 color screen, which means (i guess) it never started changing ROM current picture.
Any help about it plz.
Regards
Iaan
Click to expand...
Click to collapse
First did you do everything in this post?
iskhan said:
Well I've tried everything possible, updated device manager fro vista. MDA Vario 3, connects for active sync but after running KaiserCustomRUU.exe. where it update the crrunt ROM version... it changes the screen into 3 color screen , after few minutes in the same condition............ 0% process........ and then........... shows me an error message as under:
ERROR [262]: UPTAE ERROR
The ROM update utility has encountered communication errors during the update process. The program will guide you step-by-
step to recover from the errors so you can continue the update.
and i need to restart MDA. although on recovery process it directly come to normal screen instead of 3 color screen, which means (i guess) it never started changing ROM current picture.
Any help about it plz.
Regards
Iaan
Click to expand...
Click to collapse
you have vista then your prob better off flashing via sd, also you shouldn't have started a new thread to ask this question, this forum isn't intended for every time someone has a problem and searches and can't find the answer to start a new thread. PM someone you see posting that seems knowledgeable and ask that person if you can't find what you are looking for.
Flashing through SD is always the best. And its a lot safer than USB way.
Thanks for the help guys... closing thread as this issue can be fixed by reading the sticky and also the wiki..
Peace,
Josh
During a ROM flash yesterday I got a STOP unsigned driver message. I clicked continue but I've ended up with a persistent ERROR [302] : UPDATE ERROR message.
At first I thought I'd bricked my phone. No matter what I did or I couldn't sort it and I even tried a search here on XDA but couldn't find anything useful that worked.However I'm lucky enough to have more than one PC so I simply flashed the phone on another PC.
This worked first time so I've now successfully flashed the phone. I'm posting here as it my help someone else in a similar situation. I still haven't found out why ROM update utilities no longer work on my main PC but I'll get to the bottom of it when I've more time.
I had the same problem too and thought that my phone is bricked. It wasn't a good feeling at all right?
yesterday night i checked for update in my phone htc 820 desire g plus, yes it was there and i was downloading and installed it, what happens was at the time of installing there shows an error message and phone stopped it right there. i din't even touched my phone until it was installing. after error message i restarted my phone using the volume up and power button but again its shows the error message, then again i tried of formatting and factory restore setting, but the same error message displayed that "ERROR COMMAND".even i restarting my phone many times but the same message displaying "ERROR COMMAND" suggest me some thing in this regard.
And you just installed the official OTA update?!
Strange. If you have nothing else changed, it's time for claiming your warranty and/or contact the HTC support.
If no warranty, best to ask in the Desire 820 Q&A, Help & Troubleshooting forum.
Hopefully someone there can give a better advice.
Good luck !
Hey everyone;
I've been experiencing a problem with my phone recently(Samsung Galaxy S Plus GTi9001). It's been bootlooping all of a sudden with no apparent cause after average usage. I have scoured the internet for a solution, but to no avail. I shall try to summarize everything that led up to this in this post:
I had installed Chritopher83's CM12 custom rom on the device using the given instructions and the specially partitioned TWRP recovery provided.
Everything worked smoothly for a couple of months with the only oddity being optimisation of apps on every boot, which used to take uncharacteristically long.
Then I faced this problem:https://www.youtube.com/watch?v=Kr46ugrpL6U. The device boots normally until the TWRP logo and flashes over and over again. From what I've been able to gather, this is due to an error in the bootloader.
I'm unable to access recovery to perform a data reset or reflash a new rom. When I try to connect it to a PC, I get the error "USB device not recognised". This also prevents me from using adb or ODIN to flash anything(using adb gives me the "waiting for device" forever). I tried following the advice mentioned in the FAQ of the ROM herehttp://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330, but even that gets stuck at waiting for device.
Hoping for your help in resolving this problem...