my qtek s100 is totally ****ed up, tried a rom upgrade but now I only get this error 114 message. Have looked through a lot of threads without finding somethin that works for me. Have also tried to update again with an original rom, but no luck. any suggestions? help plzzzzz
Related
I did big storage to my qtek s110 yesterday. It was just fine until I tried to upgrade the newest Radio 1.13. I followed the instruct very carefully, however after successfully flashed the Radio, and I restart my s110. It didn't find the Radio!!!!! Then, I tried to flash back my old Rom, but the screen shows "sections = 1! upgrade not allowed". Now, I cannot use it anymore, and I cannot flash back to the old rom.
What can I do to save my baby????
Please help me. thanks.
..
Thank you for your reply!
I flashed my s110 with a shipped UK i-mate rom. It works fine. But I tried to reflash it to the orignal rom using sd card however the "press power button to flash" messege never comes out. What can I do to get back the orignal rom?
Thanks in advance.
Please help me out here... Got my new G4 Prophet screwed during upgrading... Now it can't boot up at all.. Bootloader is working tho, could somebody send me a SD dump image for G4 Prophet? Thanks a lot!!!
Anyone please help~~~ Thanks a lot!
leiz_ca said:
Anyone please help~~~ Thanks a lot!
Click to expand...
Click to collapse
why do you need an SD image, you can use a ROM updater to fix 95% of the problems
Thanks, Jesterz. You are right, I got it fixed an hour ago... here is the story, just in case it may help other people later.
Got my XDA Neo and it was in Chinese rom, which has Wi-fi disabled. So I tried to upgrade to AKU3.2. but there was an error, something like "Can't write" or similiar. Then cellphone just stop responsing. Tried soft-reset and hard-reset, both stopped at splash screen (where shows the version of IPL/SPL). Bootloader still working tho.
Then try to download some rom from xda-developers, especially that stopatbootloaderfix, but the updateutil just can't update it, report different types of error code. Others just complain no connection through activesync has been established. After trying for over 5 hours and got desperate, that was the moment I login here and ask for help.
Today I tried the stopatbootloaderfix again but this time with "Allow USB connection" disabled in ActiveSync... and it works! It successfully flashed the ROM and now I am running the new AKU2.3.1 rom!
Happy....
Same Prob
Hi, where i can find this stopatbootloaderfix?
Looks i have the same problem. my Prophet stays at the Splashscreen with IPL, SPL, GSM, OS :-(
OK, worked it out by pressing and holding the powerbutton while performing a softreset
leiz_ca said:
Thanks, Jesterz. You are right, I got it fixed an hour ago... here is the story, just in case it may help other people later.
Got my XDA Neo and it was in Chinese rom, which has Wi-fi disabled. So I tried to upgrade to AKU3.2. but there was an error, something like "Can't write" or similiar. Then cellphone just stop responsing. Tried soft-reset and hard-reset, both stopped at splash screen (where shows the version of IPL/SPL). Bootloader still working tho.
Then try to download some rom from xda-developers, especially that stopatbootloaderfix, but the updateutil just can't update it, report different types of error code. Others just complain no connection through activesync has been established. After trying for over 5 hours and got desperate, that was the moment I login here and ask for help.
Today I tried the stopatbootloaderfix again but this time with "Allow USB connection" disabled in ActiveSync... and it works! It successfully flashed the ROM and now I am running the new AKU2.3.1 rom!
Happy....
Click to expand...
Click to collapse
Are you telling me this solution is also for error 326? If so Darn!!!
Don't remember whether i had a Error 326 or not.. Sorry..
whenever i try to ugrade my rom i get this 262 error. so then i tried to do the official wm6 rom from at&t for my att tilt but it went through the whole process of upgrading but after it said it was finished it rebooted my device and nothing changed. it was still the regular wm6 that comes on the phone. It says my ROM version is 1.62.502 and my RADIO version is 1.27.14.09. How am i supposed to upgrade and what can i upgrade to . Im trying to use hyperdragon. Please respond asap Thank you
wmontae said:
whenever i try to ugrade my rom i get this 262 error. so then i tried to do the official wm6 rom from at&t for my att tilt but it went through the whole process of upgrading but after it said it was finished it rebooted my device and nothing changed. it was still the regular wm6 that comes on the phone. It says my ROM version is 1.62.502 and my RADIO version is 1.27.14.09. How am i supposed to upgrade and what can i upgrade to . Im trying to use hyperdragon. Please respond asap Thank you
Click to expand...
Click to collapse
Read First, ask later. This problem has been asked a thousand times. Hard reset & Re-install activesync.
Moderators please close this thread!
i have a htc tytn2, no lock
its dutch, did the update from mobile 6 to 6.1, no problem
when i want to update with a different rom, (even hard spl tried it also)
i run the KaiserCustomRUU it works til i get the %, it stays at 0% and after a time i get an error 262 update error.
can somebody give info to update my radio, the original radio from htc is not good and when i am calling i have an echo.
total rom update even to English is no problem. but it wont update....
anybody?
mrijnvis said:
i have a htc tytn2, no lock
its dutch, did the update from mobile 6 to 6.1, no problem
when i want to update with a different rom, (even hard spl tried it also)
i run the KaiserCustomRUU it works til i get the %, it stays at 0% and after a time i get an error 262 update error.
can somebody give info to update my radio, the original radio from htc is not good and when i am calling i have an echo.
total rom update even to English is no problem. but it wont update....
anybody?
Click to expand...
Click to collapse
There are some ideas in here for getting past 262 errors: http://wiki.xda-developers.com/wiki/RUU_Errors
Ta
Dave
@ daveshaw
thanks, but after soft reset its starting up normaly, next update the same, always that fault...
nobody, any ideas??????
mrijnvis said:
nobody, any ideas??????
Click to expand...
Click to collapse
Try re-installing active sync and try again. Error 262 usually means that connectivity is lost between your USB and phone. Re-installing active sync might solve the issue.
Also try and do a forum search using the search option right at the top of the page using the key words "Error 262" you might get some more inputs on how to sort this.
I have an Qtek S100 and according to the imei check its an o2 rom.
After a long time i decided to use my qtek again just for fun and see what i can do with it.
In windows 2003se it keeps giving low battery although its connected to usb, anyway i decided to give it a go and installed wwe05 but totally forgot about the radio rom that needed to be 1.12. (it was 1.13).
So it gave "bad radio" during startup.
I tried to flash it with multiple radio roms, including the original o2 one, but some dont start at all and some keep getting stuck at 45%.
and eventually give error 114, i can flash it back to original rom, but as soon as i want to update the radio, same thing happens.
now it gives "no radio" in wwe05, and after flashing back to 2003se it says "no gsm".
the radio wasn't giving any error/problem before i decided to update the os, so i doubt it's an hardware issue. i checked mutiple threads about 114 radio, but haven't found a sollution yet.
maybe somebody here can help me get my radio back.
You should read this Thread first http://forum.xda-developers.com/showthread.php?t=705702. Maybe there is the Solution.
i tried them all with normal usb flash, they all stop at 45% and give error 114.
Next Idea is here : http://forum.xda-developers.com/showthread.php?t=494635&page=2
Dont use a USB HUb !
k, i charged battery as long as possible, (althought i think its nearly dead) it now shows 100%.
I'm also using a different system now with windows 7,, when trying to flash it doesn't give an error, but after a few seconds its shows "congratulations", but it hasn't done a thing....
i can only try a windows xp in vmware, will try next first.
nvm, tried multiple roms, guess one of them changed my bl, cause its showed version 1.5.0 when its needs to be 1.00 or 1.02, so i tried to update my bootloader with pnewbootloader and version 1.02.nb0 and it resulted in an error ITFlashRom and never came back to the living. no boot no bootloader. paperweight is going in the bin. topic can be closed.