Hello:
I have downloaded the official ROM upgrade file from clubimate. THe file is named (JAM_UK_Aus_11200_171_11210) and it is a UK unit.
I started the upgrade and it keeps failing - the upgrade prog has wiped all 3 ROMS from the device so now it only resets to the upgrade screen (with USB V1.02) written on it.
Running the patch program produces the following really useful error 'Error 114: Radio Rom Update Error' and gives me an exit button only.
That is as far as I can get. Before the error it says it is upgrading the Radio ROM, but the Percentage does not increase at all, it looks like it may be timing out to the error.
Anyone else had this? Does anyone know how to fix it? I really Don't want my unit being a paperweight!!
Fixed:
Hello me again - this turned out to be a cable issue, got a different cable and it worked fine.
Re-download the Rom File and No-ID utility then try upgrade again.
Related
I have previously upgraded to RWE wm6, now the official ATT upgrader says "you have a newer version of this software" and wont update to the latest ROM. Any suggestions to fool the updater and install official WM6 release?
Thanks in advance- this forum always amazes me!!
Is a simple edit of the payload file all thats needed here?
File Edit
DocKill said:
I have previously upgraded to RWE wm6, now the official ATT upgrader says "you have a newer version of this software" and wont update to the latest ROM. Any suggestions to fool the updater and install official WM6 release?
Thanks in advance- this forum always amazes me!!
Is a simple edit of the payload file all thats needed here?
Click to expand...
Click to collapse
Yes.
http://forum.xda-developers.com/showthread.php?t=345531
Thanks
Awesome as always!! Thanks!!!!
Next question....Installer gets through initial phase, treo gets 4 dark colored bars, then connection is lost and install cant complete. I tried removing the SD card-no luck. Advice ?
Thanks again
I got the same problem , after the erase all data it just froze up ..... is it bricked. hopefully someone can help
I also had the same problem with my device but what i did is switch computers with Windows xp and with Activesync 4.5 that should do the trick
fixed
installed from XP instead of Vista...no problem at all. Appears Vista has trouble with recognizing the treo after loses activesync connection
seems my problem had to do with the unit, i did the sdupdater recovery tool from palm to no avail, finally i removed the battery and reinserted it and bam WM6 appeared after numerous attempt at upgrade and different ROMS tried. I asume the original upgrade got stuck and the removal of the battery, helped it finish. Who knows at least its not bricked
motorola has released recently an update for the milstone
every time i download this update (OTA) it downloaded successfully but when i hit install the phone restarts then starts to unpack then the phone boots with the message update failed so
i pulled the downloaded file from /cache/FOTA/update.zip
and tried to apply it using open recovery and i got the following massage
E:could not find update-binary
i guss it is the recovery i use
so please help me installing this update
ps: i will post the link to the update.zip as soon as i upload it
you may want to use the motorola software update tool installed to your pc. I also encountered the same problem as yours, but when i did this method, i was able to update my phone. hope this helps.
i have forget to mention that when i use the software it tells me that there is no update for my phone
Any change in this update anyway?
Thanks.
ya i heard it make u lose root for good closes loop holes in software don't do it!!
I updated via PC (MotoConnect) and lost root, but 2.1 root method still works, so I just rooted it again..
The battery usage from new firmware patch is crazy; 50% gone overnight. The most of usage is from "phone Idell". I should wait.
That's most likely a one time deal: I had similar in the update from 2.0.1 to 2.1 (or was it 2.0 -> 2.0.1..?). First night almost ran the battery dry, but after the next recharging cycle (and maybe a reboot) things were normal again. That's actually a fairly common issue judging from various milestone/android forums..
Also: all I noticed after this update was a small increase in battery life :]
Hi Peter,
are you in 3G or 2G mode?
I'm mostly on 2G.
**Edit** Sorry just started reading the Rogers 2.2 update thread and can see a lot of people are having the same problem...guess I should have read through that first. Sorry. Will try out anything recommended in there first.
I have a Rogers Captivate, and I'm trying to update to the official Froyo that was just released today.
I've installed Kies version 1.5.3.10113_29 and it finds my phone just fine.
So it pops up to say hey there's a firmware update for your phone and I click on it. It tries to back up my contacts and fails "Failed to Load". Then shows the upgrade window. I click on upgrade and it goes to the first stage of the process "Caution". I hit All information has been verified and the Next and it goes to stage 2 'Information'. I hit Allow saving, (or Proceed without saving, it doesn't matter because i get the same result every time) then Next.
Then I'm greeted with a message saying "MSC.Thunder.FirmwareUpdate has encountered a problem and needs to close."
I've tried every solution I can find and nothing works.
I'm running XP SP3. .NET framework is updated. I even went into the registry and created the Software/Samsung/FUS key that was recommended.
I'm ready to set my face on fire here does anyone have any ideas what's going on?
Thanks.
Hi,
I have a htc pro 7 bought in the uk and was running mango running the latest 5.11 bootloader, and i wanted to go to the newtech rom.
I downloaded RUU_Gold7Pro_HTC_Europe_5.11.401.02_Radio_5.71.09.02a_22.51.50.21U_NT_Mango_8107_22L_by_ansar (1)
and
RUU_Gold_7Pro_Europe_5.10.401.03_SLSPL_by_ansar
from the links in the forum and they downloaded completely.
I first powered into bootloader with vol down and then used the ROMUpdateUtility to flash the RUU_Gold_7Pro_Europe_5.10.401.03_SLSPL_by_ansar file which seemed to flash fine, the progress bar completed and phone ended up in the bootloader again.
Then following the instructions i went to the other file but when i ran the update utility this time it found the phone and tried to update but never got past 0% before prompting me that it failed after a 10minish wait.
I was able to pull the battery and turn on back into bootloader mode but when i tried flashing the second file again, it failed. (Should I be reflashing the first again every time too?)
I wondered if the package was faulty and so downloaded 7713_GOLD_USA_CHT_CHS_JPN_KOR(www.dft.so) package of the dft release but the same thing, stalls at 0%.
I am left in bootloader (attached pic) and before trying to go back to stock mango using the zune update would like to know if there is a way to get to (ideally) the intrinsic rom.
Many thanks for your help,
Edit:
Adding that I am using windows 7, will try xp on my old PC as soon as zune software can download....
Also is there a way to get out bootloader mode? as restarting just goes back into the bootloader again...?
Edit 2
Solved!
Solved!
Ok Sorted it in the end, It was my fault, I missed a step.
If anyone else gets this problem (and the error 262 in romutility to go with it) and you are left in bootloader 1.7 its simple.
My first steps were right, first flash RUU_Gold_7Pro_Europe_5.10.401.03_SLSPL_by_ansar
and then you get the bootloader, and you then have the 1.7 bootloader problem, but are NOT yet ready for custom roms!
you must then flash RUU_Gold_HTC_Europe_1.22.401.01_Radio_5.63.09.13_3a_22.36.50.15U_by_ansar
(or similar) which will you give you a 1.22 radio.
From here you can then use the dft tool to get a rspl or hspl as needed, and from there you can then flash a custom rom.
I stupidly didn't realise and thought that the slspl replaced the downgrade, which it doesnt!
Glad I got that cleared up! Am now on the custom rom and all seems good!
Edit:
Exact same symptoms here http://forum.xda-developers.com/showthread.php?t=1318726
Bootloader:SPL - 1.7.2250.0
MID: PC921000
my current Windows Phone 7 Version: 7.0.7392.0
wont appear in zune, wont flash with custom rom, gives error 262.
多谢楼上分享！！！！
So my nexus 5's camera stopped working with the error "cannot connect to camera" It's stock unlocked running android 5.0. I tried rolling back to 5.0 from 5.0.1 to try and solve this problem and it didn't work. I've tried other apps and nothing can seem to connect to the camera. The phone was not dropped recently so I can't imagine what it could be. Any thoughts?
Much appreciated!
Did u tried resetting via factory image?
https://developers.google.com/android/nexus/images
But beware of the script's settings. Internal memory gets deleted too if you don't edit the batchfile and remove -w
Code:
fastboot [COLOR="Red"]-w[/COLOR] update image-hammerhead-lmy47i.zip
If that doesn't help, its a hardware fault.
Don't know if this has been solved or not, but just recently bought a brand new N5 for the wife, unlocked it, and put a MM custom rom on it. Everything works great except for the camera giving this "can't connect" error. A reboot will temporarily fix it, but I was searching this forum to see if anyone had ever found a permanent fix. Most of the searches have mentioned unchecking Trusted Face, but the rom I'm running doesn't seem to have that. Not sure what else to try at this point. Has anyone else found a better solution yet?