I flashed the Cyanogen Mod 7 onto the phone about 3 months ago, and today tried a different ROM as my girlfriend's O2 card (It's a UK Orange phone) wouldn't work in it, and the SIM unlock code which I paid for wasn't working - the guy I bought the code from said it's probably ROM-related.
I've tried flashing a LeeDroid ROM, and an INSERTCOIN ROM but neither work. With Leedroid I get bootloops, and with the other it gets to a colourful background but nothing else on screen and no other buttons do anything.
I've gone into bootloader mode and tried just running an exe file (for example an HTC_WWE_BRAVO_date_version number_etc from the laptop with the phone connected via USB, but this doesn't work either.
At my wit's end now as I think I've bricked the phone...
Can anyone help at all?
Why does flashing ruu not work?
ur supposed to be in fastboot. not hboot when trying to restore using ruu
Thanks for the tip -
I get as far as an updating signature message for about 10 seconds, then it crashes out with:
ERROR [131]: CUSTOMER ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
This problem is easy to fix. Create goldcard with linux, put this in your desire and then flash ruu again:
http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
I managed to successfully create a goldcard, but upon flashing the RUU .exe file, it gets to the 'updating signature' part (before the percentage completion bar has even started) and then crashes out with the following message:
Error [132] SIGNARURE (sic) ERROR
Please try to flash again with a different ROM update utility (or words to that effect).
EDIT: Now working. Thanks MatDroid!!
Related
i have a xda orbit and i am trying to flash it with o2 premium full rom. i have done things like removing the microsd and sim and have ran the cid unlocking utility which came in the package. it goes to 100 and the phone goes black and with a linux cartoon and goes white then. afterwards the update utility runs after accepting everthing it looks for the settings and give me an error saying check the cradle the error is 270. if i enable the active sync manually it installs and goes to 3% giving me an error 260 image corrupt pls help!
Have you tried flashing any other ROMs and have they worked OK?
yup all of them are doing the samething. but i noticed 2 files in the root of the phone memory and i found similar files in the rom package so i copied those two in the root. and then the romupdate utility dected my phone in the bootloader and it worked. i am not sure this way the reason i could be something else not sure.
Hello,
if got the T-Mobile MDA III with WM6.0.
Now i want to update my ROM with WM 6.5, bit i only become the following error:
Your image has corrupted. please check your update utility.
Can anyone help me???
i hope you can help me.
thx
markus
try to re-download the rom and make sure you run a USPL first if it's your first upgrade. Search the forum if you need help
it dosn´t works
i´ve tried 5 different roms but no one works.
its the second upgrade on the fon.
Try a new update of SPL, files here= http://forum.xda-developers.com/showthread.php?t=311403
Download "ArtemisUSPL.zip"
1. Unzip
2. Connect your phone to computer, make sure activesync is enabled (green icon)
3. Run start_uspl.exe on your computer and wait until process finishes
4. The phone reboot.
When boot is done, you are CID unlock forever normally so you can flash all rom you want.
Then, You can flash now your rom, just run RUU from your rom folder and normally it's good.
If it always don't work, give us all the number show in your 1st screen when the phone boot (IPL, SPL ...)
yes, tell us what numbers you get on your screen
also what error are you getting
and what OS are you on....vista? XP ? Did you get an activesync connection before you tried flashing?
also try putting phone into bootloader mode first and then flashing, sometimes helps. (hold down RECORD/NOTES button when you reset)
once you've got an error number ( eg error 260 ) you can try searching the forum for that error number and see how everyone else has coped with it.
Helo dear friends.
Well I just wanted to get some Hebrew in my Hero.
I have the Orange hero in Spain. Upgraded to official rom - 2.73.61.5, worked fine.
Now i am trying to downgrade it, so i can root it, so i can add all the fun stuff (including hebrew).
Did the gold card, since i understood that this hero is CID locked. (and maybe i am wrong). Then failed few times with error 140 when tried the 1.76.405.6 and 1.76.405.1 rom downloads. Then tried to downgrade to 2.73.405.5 rom as someone suggested here... and the process started happily, downloaded Splash1 ok, system ok, userdata ok, boot ok, bootloader ok, then GOT STUCK ON "Radio-V2 - updating" (at about 85%.. froze!)
(I attached a picture).
This happened few times, sometimes never even started to download, was just froze at the beginning of the process with: "zip header checking..."
So every-time this happened i had to disconnect it, pull the battery out or something, and try again. (I also found out that for some-reason things moved forward when restarting windows which by the way, works on parallels, mac ...)
Now the hero is stuck on the white error screen i guess, pictures attached.
Mmmm... hope someone can suggest something... straight and to the point, i feel i am going circles will appreciate allot.
Thanks in advance
Cheers!
First off ... KEEP THE PHONE PLUGGED IN! (So the battery doesn't die... If i remember right... fastboot chews through battery)
Next.. how long has it been stuck?
Well, first time for 30 minutes of no movement, then at the rest of the attempts i kept losing my patient each 20-30 minutes... in a process that might take 10?
yeah the battery ran out once..
thanks.
Trying again, now it's stuck on "system - updating". 20 minutes.
Please help.. someone?
Should i try another rom? any suggestion for Orange Spain?
Someone experienced problems via Parallels ?
Parallels as in your trying this from a VM? I would bet thats your problem! While it techincally shouldn't make a difference... I would try with real PC!
yes, virtual machine...
Ok, and that PC, should it have all the drivers for the phone? i mean now that the hero is stuck, would a different computer recognize it?
I should just download the rom to the computer and try to install it?
thanks.
You'll want to install the USB drivers (The HTC Sync download from htc.com likely has these included...)
If the VM still see's it - any PC with the drivers installed correctly will see it.
If you get the the custom recovery image flahed, you'll be able to do everything from your mac after that...
ho really? can you elaborate a bit on that? start with: " custom recovery image flahed"
Thanks.
Details @ http://forum.xda-developers.com/showthread.php?t=561124
Thanks. and this i do after i downgrade successfully the rom (with lets say a proper PC?) ?
Do i need to root after downgrading?
As far as I remember - Yes - you will need to root the phone, then:
adb remount
adb shell rm /system/recovery.img (If this fails with file not found dont worry about it)
I seem to remember needing those when I rooted my hero ...
Thanks kiall, resolved it at the end, without downgrade, no PC, just pushed the Recovery to the formatted sdcard, flashed it and the modaco rom and then radio and hebrew fonts, all is ok now...
Thanks for you time.
Hi just got my Desire, been a devoted WM user and all android is a bit strange to me. I have a Nexus 1 and love it but i thought i would try the Desire as my friend bought one and was able to use it to sync with our MS exchange server which i was never able to do with the Nexus 1. I was very impressed when i bought the phone that connecting to our VPN and syncing with exchange seemed to work well. I purchased the phone while on a convention trip to prague, as i was needing to connect to our exchange mail. After a few days with the phone It began rebooting on data connections without any notice and would often not reboot some times just flashing the white HTC screen and continually rebooting itself. I decided to try and root the phone to possibley stop this from happening using the excellent instructions from benko286 http://forum.xda-developers.com/showthread.php?t=696189 .
i'm attempting this on a Windows 32 machine so im using the "Guide to root using Windows" after step 5 and running "step1-windows.bat" my Desire screen appears with HTC in the middle and each of the four corners of the screen has a triangel caution symbol. at the end of running the bat file in the command window just before rebooting to boot loader the last line said "FAILED (remote: 51 partition update fail)
and my Desire went into the aboved mentioned screen. I am able from the command prompt to re-run the step1-windows.bat file so I still have usb connection obviously but the same issue continues. I am not sure where to go from here.
My machine if restarted turned off (remove battery) continually comes up with this above mentioned screen, I am hoping that this is not an idicaction of a bricked device. I have tryed my best to go through the vast amounts of great information on XDA- developers, but can't find any pertaining to my situation. Is there anyone out there that can give me a point int he right direction?
Much appreciated.
Blaiz
I can't really help you with this, but am just posting to give this thread a little bump and keep it on the top of the list.
Hopefully someone here might be able to help you out. Good luck,
What is going on? This is the second time i've heard of this thing with the HTC logo in the centre with four triangles in each corner. No one seems to have any idea what this is and i've personally never heard of it throughout the last few months of owning a Desire.
hi thanks so much for the support, I guess lokoing back i should have put this in the tutorial thread. im not sure where i can go from here other than only using the Nexus lol.
this is what it finished with at the command prompt
-----------------------------------------------
INFO[RUU]WP,system,99
INFO[RUU]WP,system,100
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
FAILED (remote: 51 partition update fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\TEMP\r5-desire-root-alt\r5-desire-root-alt>
------------------------------------------------------
the step1-windows.bat file seems to run in succession 2 times the first time looks fine then it begins once again to start the flash. at the end of the second run is what i have copied and pasted above. I'm really to much of a newbee to understand what the error is "FAILED (remote: 51 partition update fail)"
as i unplug the usb cable the screen now goes white with
------------------------------------------
BRAVO PVT1 SHIP S-ON
HBOOT-0.80.000
MI CROP-031D
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02-2
Mar 29 2010, 21:34:33
RUU
-------------------------------------
with 2 caution icons in both bottom corners, when i pull out the battery and restart the machine it goes back to the original black screen with HTC and the four caution icons in the corners.
Thanks for any suggestions or information from any sources with similar issues.
All the best,
Blaiz
is there a microsd card in the unit when you try this? Is your phone unbranded? Have you created a gold card?
I have tryed with the original SD card inserted and i have tryed with it removed i have also reformatted the SD card and inserted it then removed it again. The phone i bought is from The Czech Republic, Prague, it was bought unlocked and unbranded i believe from an O2 phone shop in Prague 10 days ago.
I will try the gold card method next but im not sure how to go about this state.
as i am unable to boot the device I can't seem to get adb shell to find the device.
Blaiz said:
as i am unable to boot the device I can't seem to get adb shell to find the device.
Click to expand...
Click to collapse
Open up the phone in RUU mode and plug in your phone.
Download this and execute it
http://shipped-roms.com/shipped/Bra...io_32.30.00.28U_4.05.00.11_release_122704.exe
thanks abc27 downloading now
only question i have is should i not stay with the a similar rom and use a current stock ROM of 1.21.* instead of the 15 or will it matter to get me out of this situation?
Blaiz
such as the
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
instead as my original bootloader was 0.80.*
Blaiz said:
such as the
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
instead as my original bootloader was 0.80.*
Click to expand...
Click to collapse
Then you should use that release instead.
I thought you were hboot 0.75 and I didn't want to upgrade your bootloader.
cheers thanks again abc27
is it fixed with it? ^^
i cant believe my luck or lack of it
downloaded the
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
and i get to about 85% of the Rom image update and it gives me an error!
------------------------------------
ERROR[110]: FILE OPEN ERROR
The ROM Update Utility cannot open the requested files or the files are damaged. The RUU cannot continue with the update.
Please get a complete RUU package and try again.
---------------------------------------
I have tryed 5 times to flash and no luck maybe i should try another ROM file but which one?
Hmm that sounds quite odd.
Try redownloading ROM.
try this one http://www.wuala.com/HTC_Desire/RUU...00.28U_4.06.00.02_2_release_126984_signed.zip
seems the file u downloaded is corrupted
tryed redownloading still exact same issue with
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
from
http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126984_signed.exe
Alkymia the file you are directing me to is a zip file no? it doesnt seem to contain the RUU file.
it is a zip to flash it on ur bootloader, u must put the zip onto ur SD card and then try to flash it as u flashed the rom to root it, r u able to enter into bootloader?
Hey there, I think I've bricked my device and naively thinking it would be pain-free and careless as it was in my DHD, it was an utter brain melter with it's little brother device and I've spent the past 2 days frantically trying to fix it, probably making it worse.
Here's the problem:
- USB responds on PC with notification, doesn't seem mounted
- Unable to access any form of recovery/bootloader
- Attempted VM RUU but at the end it has a 101: File read error, even though the file is intact.
- Attempted latest RUU amongst various others, with an image write error.
- Loaded fasboot via PC & flashed downgrade from http://alpharev.nl/ - although flasher said it was 'successful' the RUU mentions 2.0.x-something and fails again
- Now a black screen that doesn't even show 4 corner error.
So yeah, I'm so lost right now. Any help at all is appreciated, since it's so messed up might as well try experimental methods of recovering this. Thanks a lot.
deolol said:
Hey there, I think I've bricked my device and naively thinking it would be pain-free and careless as it was in my DHD, it was an utter brain melter with it's little brother device and I've spent the past 2 days frantically trying to fix it, probably making it worse.
Here's the problem:
- USB responds on PC with notification, doesn't seem mounted
- Unable to access any form of recovery/bootloader
- Attempted VM RUU but at the end it has a 101: File read error, even though the file is intact.
- Attempted latest RUU amongst various others, with an image write error.
- Loaded fasboot via PC & flashed downgrade from http://alpharev.nl/ - although flasher said it was 'successful' the RUU mentions 2.0.x-something and fails again
- Now a black screen that doesn't even show 4 corner error.
So yeah, I'm so lost right now. Any help at all is appreciated, since it's so messed up might as well try experimental methods of recovering this. Thanks a lot.
Click to expand...
Click to collapse
Option A: Create a goldcard (you can use your DHD, or if you alread yahve one use that goldcard) and flash the latest WWE RUU (Link on my guide)
Option B: Less safe. Use the 2.3.3 RUU (Link on my guide)