• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Unable to unlock bootloader at HTCdev with rom 2.14.401.1

Lunarpac

Lurker
Hello!

I'm having issues unlocking my bootloader at HTCdev.
There doesn't seem to be a RUU matching my version.

Currently I have:
Android 2.3.5
ROM 2.14.401.1
HBOOT 1.09.0099

I've tried downloading the HTC EU RUU (phone bought in Sweden), but I get ERROR[190]: ROM IS NOT UPDATED when I try running the PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R
from my desktop with the usb cable plugged in and usb-debugging enabled. The program then tells me to update.

However, there are no further updates available when using manual update search from the phone.

It seems it wants me to "update" (or in my case, downgrade?) to 2.13.401.3 in order to run the RUU, but I already have 2.14.401.1.

I've tried a couple of things, including a guide using zergrush to edit the version in my phone to 2.13.401.3 (didn't work).

Can I solve this issue? Or is it simply htcdev that hasn't updated their RUU to match the latest version?

Thanks on beforehand,
Lunarpac
 
I'm having issues unlocking my bootloader at HTCdev.
There doesn't seem to be a RUU matching my version.

I'm having a similar problem. I've tried 3 different RUU's from HTC Dev and all give me the same error. "Model ID Error" :confused:

I was wondering if the problem was that I'd rooted my phone before trying to unlock it. But apparently that's not it.

Mine is the US Virgin Mobile model... apparently it's a "limited edition" :cool: Christmas White one... what evz, I haven't heard there's any difference other than the color.
 
Since that ROM was just released, I don't think there is an RUU to update the bootloader for it yet. You may have to wait a couple weeks.
 
I'm the same but cmd won't find my device when it says "Waiting for device"

Any help?
That usually is a driver problem. Make sure you have the most updated HTC driver (BY downloading HTC Sync). If you do and it still doesn't work, unisntall the driver and re-install it again.
I had the same problem once and what I did was to actually use a different laptop and worked like a charm. So the problem is not the phone but the laptop.
 
Back
Top Bottom