Hi guys, same problem here though with a Dutch Vodafone version of the Desire-Z which I think is my problem -- hopefully one of the things I've tried below will solve yours and somebody in this forum knows where to get the shipped ROM that will fix my problem!!!
My wife's Android Desire Z - Stock ROM, S-ON, got stuck looping with a failed
android.process.acore message and after trying a cache clear that didn't help
I set out to factory reset it. Figured the nuclear option would be dead simple. Nope.
I did a Factory Reset from the Hboot menu, by holding volume down and pressing the power button then using volume button to navigate to "Factory Reset." This simply froze the phone at the HTC menu for an hour. Not good.
From there dozens of resets and reboots and fastboots would sometimes successfully boot to my wife's setup (so nothing was reset at all), only to get stuck in the acore loop again.
I was once quick enough to put it into airplane mode and that stopped the error message loops. YAY! I could try a reset via software! But when I attempted
Settings > SD & phone storage > Factory data reset
it simply rebooted to HTC screen, Vodafone
screen, HTC screen, vodafone screen. ANOTHER loop.
OK, next try was to flash the ROM with an original shipped version. Because my phone is S-ON (you see this status when you go to the Hboot menu) it means I can ONLY flash the original shipped ROM -- no upgrades, no backrolls.
Couple forums in Dutch said the shipped ROM for the Vodafone Desire z in NL was Bravo/Froyo WWWE (World Wide English)
so I located this file:
At shipped-roms.com -- the one you want for a Vodafone UK unit is this:
To flash your phone, you put that file on a pc which has HTC Sync installed,
boot your phone to the hboot menu, choose Fastboot, make sure the red letters read "Fastboot USB" and start the RUU exe.
Didn't work for me, as the USB connection failed after the unit reset: Error 171, Error 170.
Tried installing HTC Sync AND the Universal boot drivers
and the Android Booloader Driver, as per the helpful advice from Bob Denny here:
Universal Windows USB Drivers (ADB, BootLoader, Disk Drive, HTC Sync)
And yep, I disabled anti-virus, had a fully charged phone, but for some reason
the pc wouldn't see the phone after it rebooted so I abandoned the RUU via windows option.
Because there's another way. You can put a PC10IMG.ZIP on the SD card in the root directory and flash the rom when by loading it with the phone's bootloader, again located in the Hboot menu under Fastboot.
I extracted ROM.ZIP from the RUU -- run the exe so it unpacks the files and stop there, open task manager and right click ADB.exe, choose Open file Location and you'll find ROM.ZIP there.
Rename it PC10IMG.ZIP and copy it to the root of you SD card. (I had to do this with an SD Card reader attached to the PC since my phone wasn't visible on the USB.
I booted to Hboot with the volume down and power buttons, chose
Fastboot and watched the the Zip load (blue verticle progress bar upper right of screen), check it (brown progress bar upper right), then NOTHING -- back to the Hboot menu.
If yours works, you'll get a question "Do you want to Upgrade" and that will flash your ROM.
So this is where I need help: I got No error message, and no invitation to
update. Reboot takes me back to screen loop. Normal power-on does the same.
The RUU reports that I'm running version 126.96.36.199
(of what? Vision Gingerbread?) and the Bravo/Froyo WWE Rom reported itself to be version 1.59 something. As this is an S-ON phone, I know I can't roll back to earlier ROMS, and can only install
the exact version as shipped.
So the questions I THINK I need answered:
1. Does anyone know for certain, or know where I can find out, which ROM
shipped with the Vodafone NL Desire-Z in 2010? I can get Kernel source for it at the HTCDev site, but I see no compiled ROM there -- anything I can do with kernel source?
2. Anyone know where can I get the right PC10IMG.ZIP file to flash the unit from the SD Card? (I tried Shipped-Roms.com and
dozens of google permutations -- Dutch Vodafone version simply isn't to be found.)
Any help deeply appreciated, and I hope one of the steps I've taken so far solves problems for the others of you having this problem in this thread.