Develop Bugs

[Q] Need RUU help to restore back to Stock

Before I start, , I want to say that I have read other similar posts and not found an answer to my query.
First, I just wanted to thank you for the wonderful stuff you guys do on these forums. I have used your expertise for many previous issues that I have had in the past. I cherish my Androids a lot more now thanks to you guys.Now, onto the problem that I am currently having. I will try to make it short.
SHORT VERSION:
I need help to unroot the phone and I can't get the "correct" RUU to work.
LONG VERSION:
I rooted my phone and installed Android Revolution HD for ICS. After a while, I decided to upgrade to JB via CM10.
At first, the WiFi would start giving me problems, it would get stuck at "on and never going off" or "off and never turning on." So I remedied that by just restarting the One X which was fine. Then the screen started to act up. Whenever I restart my phone the screen would work just fine. I would put it down for a while, but whenever the screen goes off, it responds slower and slower until the display no longer turns on. However, the phone still works as if it was on via the touchscreen. I can still open apps, just as long as I can guess where to go.
This left me with two thoughts:
1.) The screen is not broken because on restarts, or before it blacks out completely, the screen is just fine. No dead pixels, no lines, no light bleeding to anything.
2.) The OS (I think) is not broken because it always responds to what I am doing.
Therefore I think there exists a problem between the hardware trying trying to communicate with the screen. So I want to return the phone back to the manufacturer.
I have looked on other forums and I am here to ask for help. I can't find a way to solve my problem.
When I try to unroot, I get stuck at the RUU portion. And I honestly think I am using the correct RUU. As you guys know, I need to put the phone back to its original everything to get a chance for the manufacturer to help me out.
So please! Help me with the unroot!
On a side note: the phone works perfect when it is charging AND with the screen on. Don't know why.
This is my phones info from the HBOOT screen:
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13
eMMC-bootmade: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012, 02:27:11
CID: HTC___622
For those that are wondering, this is the RUU that I used.
Endeavor/RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe
Maybe that was the issue, I don't know. There are 4 HK (Hong Kong) RUUs if I'm not mistaken.
I look forward to your help and response!
Once again, thanks for all the helpful tips/tricks/flashes and roms.
Gratefully,
johnchiu

Oke are you familiar with the fastboot commands ?
Do these 2 commands with the phone in fastboot usb mode !
Fastboot getvar version-main
and
Fastboot oem readcid
To get the right info for the ruu you need !

Try this one:
http://htcruu.com/securekey.php?fil...Radio_2.1204.122.17_release_268338_signed.exe
Although, I thought the 2.17 was available, that one should install on your hboot.
You'll need to do:
fastboot oem lock
Then run the RUU as administrator (right click it).

So when I did the "fastboot oem lock" whenever I go back to the hboot, on top it says that my phone has been "***RELOCKED***"
I remember before I unlocked the phone it said ***LOCKED*** so if it now says ***RELOCKED*** and I want to ship it in for repairs...wouldn't that be a red flag that I tampered with the phone?
Also, I have SuperUser installed on the phone, how do I get rid of it? Because I think that looks awfully suspicious too haha.
I am downloading the RUU right now, hopefully it works, I will let you know how it goes. Thanks @BenPope

Your bootloader will always say that its been relocked after you unlocked it, can't do anything about that ! And the RUU will flash a stock rom, stock recovery and the stock boot.img back. So all traces of previous root is gone !

So what should I do to make my phone as close to it was first coming out of the box.
For example, I really want to get rid of SuperUser but I don't know how to.
How do I check if everything is stock? Etc.
Thanks again for your help!

Just run the ruu and everything is stock !!! Can't get closer to stock than that !
A ruu wipes the phone 100%

I tried it again...and it failed again. I don't know what to do.
Every RUU that I have tried to install so far all say:
ERROR [140]: BOOTLOADER VERSION ERROR
How is it possible that every version fails? Please help!

Hmm do the fastboot commands i posted in the beginning of the thread, the cid and main version commands ..... See whats comes out ?

Sorry forgot to post them. These are the latest ones.
C:\fastboot>fastboot getvar version-main
version-main: 2.18.401.2
finished. total time: 0.007s
C:\fastboot>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__622
OKAY [ 0.025s]
finished. total time: 0.025s

There is the bug ! You need at least a 2.17 based RUU ! But i dont where to find it at the moment

Are there no ways around it? I can't be the only person with this problem can I? I purchased this phone back in May 2012. So my phone was one of the original units sent out. Thanks for your rapid response and time.

Maybe there is one at the file factory but i dont have an account there

secretaznmanxxx said:
Sorry forgot to post them. These are the latest ones.
C:\fastboot>fastboot getvar version-main
version-main: 2.18.401.2
finished. total time: 0.007s
C:\fastboot>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__622
OKAY [ 0.025s]
finished. total time: 0.025s
Click to expand...
Click to collapse
That's odd.
You have the European version-main and a Hong Kong CID.
You might want to look for a backup of a HK ROM to restore.

[Q] Update to JB

I tried updated to JB from Viper 2.7.1 by attempting to go back to stock using RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.28.110.7_R2_Radio_1.1204.103.14_release 256500_signed.exe & it didnt go to plan.
After I relocked the bootloader I couldnt get any further with the process & my phones battery ran flat, I had to use the battery script to get enough power back into the phone so I could continue, again It wouldnt work, at first I thought my phone had been bricked but when I re-unlocked the bootloader Viper came back to life.
What is the best way to go about updating to JB?
My CID T-MOB005
HBoot 0.94
Radio 1.1204.103.14

Are you sure you got the right version number ?
Do the fastboot command
Fastboot getvar version-main
If it matches this ruu
http://androidfiles.org/ruu/securek...Radio_1.1204.105.14_release_260731_signed.exe
Then you can use it. The 1.28 ruu fails because it wants to downgrade the hboot. Hboot 0.94 is in line with the 1.29 version number. So my guess is that when you use this one you will succeed !

after using fastboot getvar version-main I got 1.28.110.7

Hmm funny .... Download the ruu i linked
Keep the bootloader locked ... And keep the phone in the bootloader and select the ruu.exe by clicking with the right mouse button ...select RUN AS ADMINISTRATOR

C:\x>fastboot getvar version-main
version-main: 1.26.401.2
finished. total time: 0.034s
C:\x>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__102
OKAY [ 0.014s]
finished. total time: 0.014s
which ruu should i pick?
hboot 0.43

5had said:
C:\x>fastboot getvar version-main
version-main: 1.26.401.2
finished. total time: 0.034s
C:\x>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__102
OKAY [ 0.014s]
finished. total time: 0.014s
which ruu should i pick?
hboot 0.43
Click to expand...
Click to collapse
Sent you PM !

thanks Mr Hofs
does the .exe need to be in a specific folder when run? i.e. platform-tools
is the file OTA_ENDEAVOR_U_ICS_40_TMO_UK_1.28.110.7-1.26.110.5_release256527.zip for updating stock ROMS?
it will probably be Saturday before I can make another attempt, I will let you know how I get on

No afaik you don't need to run it rom a specific place. But running it from within the fastboot can't do any harm

just an update to this thread
ran RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.29.110.11_Radio_1.1204.105.14_release_260731_signed.exe successfully.
performed OTA updates from TMobile culminating in JB :laugh:
finally installed ViperX 3.3.7 & all OK until I restored apps in Titanium, now Sense crashes randomly, I must have restored an old version of Sense by mistake.
Thanks for your help MrHofs

Nice ! :thumbup:
Or did you restore some of the old system ? Either way at least the updates worked fine

it looks like Ive restored something I shoudnt have!
I would recommend the RUU route to updating to JB every time, nice n simple

Unless the ruu is not available !

HTC One X issue

Hi All
I am new to this forum, I have read and re-read almost every thread, my issue is that my phone is stuck and I cannot get any Rom to be loaded on this device. I have tried everything(well almost)
The most recent thing I tried was to load the latest recovery and dump the lollipop rom on to the sdcard, the error was that the recovery partition is newer than the rom, however this was the latest rom? Can anyone help me please...i have been on this for two weeks now.

AK1234 said:
Hi All
I am new to this forum, I have read and re-read almost every thread, my issue is that my phone is stuck and I cannot get any Rom to be loaded on this device. I have tried everything(well almost)
The most recent thing I tried was to load the latest recovery and dump the lollipop rom on to the sdcard, the error was that the recovery partition is newer than the rom, however this was the latest rom? Can anyone help me please...i have been on this for two weeks now.
Click to expand...
Click to collapse
:\Users\101641\Desktop\HTC1>Fastboot oem readcid
..
bootloader) DEBUG: cid: OPTUS001
KAY [ 0.015s]
inished. total time: 0.016s
:\Users\101641\Desktop\HTC1>Fastboot getvar version-main
ersion-main: 4.19.980.7
inished. total time: 0.080s
:\Users\101641\Desktop\HTC1>
More info, can anyone help or am I just going to have to leave this phone as a paper weight?

AK1234 said:
:\Users\101641\Desktop\HTC1>Fastboot oem readcid
..
bootloader) DEBUG: cid: OPTUS001
KAY [ 0.015s]
inished. total time: 0.016s
:\Users\101641\Desktop\HTC1>Fastboot getvar version-main
ersion-main: 4.19.980.7
inished. total time: 0.080s
:\Users\101641\Desktop\HTC1>
More info, can anyone help or am I just going to have to leave this phone as a paper weight?
Click to expand...
Click to collapse
hi
Do you use cm12.1 with new storage layout ?
if so u must see this thread http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
I hop that will help you

Taha.ineflass said:
hi
Do you use cm12.1 with new storage layout ?
if so u must see this thread http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
I hop that will help you
Click to expand...
Click to collapse
Thanks, managed to find another rom and it worked...I am now on 4.2.2...Going to try again to update...

HELP - Setup Wizard Stopped working.

Hi,
I was a bit dumb to assume I bought a htc_himauhl, and I tried to flash a custom rom, but I couldn't. My device is a htc_himaruhl. Fortunately I was cautious enough and I've created a backup of the stock rom in TWRP recovery.
I've restored the backup after realizing the error, but now I'm facing another problem: The setup wizard keeps crashing.
How can I fix it, or atleast bypass it? I was thinking about doing it through adb shell in recovery, but I don't know how. Also I was trying to enable the developer mode, but it doesn't let me do it until the setup wizard has finished.
(I can go into settings when I plug the phone on usb while the "setup wizard stopped" error message is showing, and I can pull down the menu from the top.)
Details about the device:
Retail name - HTC One M9 Prime Camera Edition
Factory unlocked - sim free
Code:
fastboot oem readcid
...
(bootloader) cid: HTC__001
OKAY [ 10.110s]
finished. total time: 10.111s
Code:
fastboot getvar mid
mid: 2PRG10000
finished. total time: 0.003s
Code:
OS-2.18.301.10
Thanks in advance for any advice.

Help! I think I've bricked my phone!!

Hi,
I think I have bricked my old htc one x! I have tried to fix the issue by spending the last few days reading through and trying as many of the solutions on this site as I can but I seem to be constantly running into roadblocks in my attempt at fixing it.
Basically I had cyanogenmod on it for the last 3 years and had lent it to my mother to use (I could never get google play working but everything else was ok), after years of thinking I should really put some stock RUU on it for her, because cyanogen is different to what all her friends had and she couldn't do things in quite the same way.
I relocked the bootloader and started to install an HTC X RUU for t-mobile (first mistake - I am in australia) and this did not work, I then downloaded what I think is a compatible RUU and the battery had dropped below the minimum 30% I needed, and was slowly losing power, I tried to unlock the bootloader again so I could fix it but the battery was too low to unlock it (I tried to use "fastboot flash unlocktoken Unlock_code.bin") and the phone seemed to alternate between a restart loop and just being stuck in the bootloader.
This is the error I get when I try to unlock it
"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
< waiting for any device >
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
OKAY [ 0.138s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s"
After researching and looking at similar issues, the only fix seemed to be to use a bat file
"@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
I've spent all day running this trying to get the phones voltage up to 3680 so I can then unlock the bootloader and put on a customer clockwork or something so the phone can charge from fastboot/bootloader or just black screen, I only need 10% I believe however the bat file works great from 2700-3500 or so, (this takes maybe 3 hours) then the bat file bombs out with errors such as
"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>ping /n 6 localhost 1>nul
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>goto start
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot getvar battery-voltage
< waiting for any device >
getvar:battery-voltage FAILED (command write failed (No error))
finished. total time: 0.004s
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s"
Is there any help anyone could give me ? I honestly have looked all over the place seeking a fix but am having real trouble
Any help would be appreciated !

Did you at any time think of shutting the phone off, or leave it to discharge until it shuts of by itself? This way you could fully charge it as long as it is turned off, power it on holding volume down and then try to unlock again.
If you succeed you could flash the latest TWRP 3.0.2-0, and flash a CM21.1 (new layout), as well as the according GApps to obtain all needed PlayService files. If done so after a reboot you could setup a Google account and everything else. But make sure to flash ROM and GApps in one run. Don't reboot prior to flashing the appropriate GApps which would, in case of my example, be OpenGApps, ARM, 6.1 pico.
Sent from my HTC Pixel XL using XDA Labs

Thanks for the reply, I've managed to get it up to 3650 voltage and it then allowed me to unlock the bootloader through a combination of the bat file and charging whilst it was dead.
Now I will try and put a nandroid backup or something on it, I am having big trouble finding an RUU for vodafone australia that matches the CID:
radio. 5.1204.162.29
cid: vodap021
mid: pj4611000
main version: 3.14.862.27
Any advice here at all ?

grim61 said:
Thanks for the reply, I've managed to get it up to 3650 voltage and it then allowed me to unlock the bootloader through a combination of the bat file and charging whilst it was dead.
Now I will try and put a nandroid backup or something on it, I am having big trouble finding an RUU for vodafone australia that matches the CID:
radio. 5.1204.162.29
cid: vodap021
mid: pj4611000
main version: 3.14.862.27
Any advice here at all ?
Click to expand...
Click to collapse
I'd stick with the latest available CM 12.1 ROM, or alternatively XenonHD found in the original Android development section. I'd recommend to download the appropriate GApps on OpenGApps.org and flash ROM and GApps in one single step. On XenonHD Nova launcher is used as far as I remember. That on is quite stock Android like, and with GApss installed all should work fine. So I'd recommend using XenonHD.
On my One X the battery died two or three month ago and I finally got it opened up. So I'm now waiting for a new battery to install and finally flash it again.
Sent from my htc_pmeuhl using XDA Labs