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

Root This is an ugly problem. Need some serious help.

Could it be a mainver problem? Idk what to do. I'm on the 2.95 OTA but I installed it through Ramjets firmware pg86img.
 
Yeah i'm on the black htc screen with 4 exclamation points, if I unplug the cable it shows bootloader and an orange text that says RUU and thats it. I tried locking the bootloader which worked through fastboot, so. But if I flash an RUU it writes everything but System i believe
 
Firmware, main version, etc doesn't matter when s-off. There are no security checks being performed so the ruu will take in normal circumstances.

Not sure what's going on with yours...

Any way you can post the exact error you are receiving?
 
ERROR [152] IMAGE UPDATE ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.

I've been using the one provided by the RUU Unroot guide in the All things root guide.
 
Also, I'm not super familiar with this method and you might have to use the first command from the bootloader but there is a method where I believe you type: fastboot oem rebootRUU

Then: fastboot flash zip nameofzip.zip

Name of zip being the ruu...

Edit: ninja'd the heck out of prinny :D:p
 
Alright, well, try this...

Code:
fastboot oem rebootRUU

fastboot flash zip (Whatever).zip

See if that helps at all...I'm a bit at a loss here now though...


Edit: Ninja'd by Brian
 
That's how I USUALLY do the RUU, since I abandoned Windows a long time ago...That or I just try flashing the pg86img.zip through bootloader from the SD card.

But yeah, let us know how that goes.
 
It gets all the way to the end of the green bar almost on my phone no matter what my error is the same even flashing it with fastoot. I believe it is getting stuck on rcdata tho, because at the end of the cmd prompt it says FAILED (remote: 53 image unzipping fail)
 
You can TRY...I can't promise anything there...I'm not too sure what RC data is.

Push comes to shove...remove it but store it somewhere safe, try it. Then if everything ELSE works, quickly throw together a zip with that...and flash that zip
 
It's just silly considering the same amount of effort could have been used to just answer the question. Snarky comments are more clutter than a repeat question in my opinion.
 
Do you guys know how to get out of RUU mode so I can go back to regular bootloader? I noticed when I did the fastboot oem rebootRUU it says it erases certain sectors to reboot into that.
 
Try the normal fastboot reboot.

If after a few minutes nothing happens....what I did (I don't really suggest this except as a very last resort) was just rip my phone off and rip the battery out...

^Last resort though.
 
Making a new RUU without rcdata now. I'd still like to be able to get out of this ruu mode. :/ So I have a hunch. I was on android 4.2.2 and the RUU wants to install 4.0.3... My bootloader has been relocked. And your bootloader needs to be unlocked to downgrade firmware and android version or something right? I mean even tho i'm S-off.. This is just strange.
 
Bootloader has to be unlocked to flash recovery and such with fastboot flash recovery recovery.img

In order to flash PG86IMG and new firmware and whatnot via the PG method, you need S-Off
 
Unplugging the battery and reinserting just puts it back to this mode and so does fastboot reboot. I'm surprised none of you know how this is happening. Coukd it be a driver issue? I'm not entirely sure if the drivers were ever installed because its windows 8.
 
Back
Top Bottom