Develop Bugs

[HELP ME] Possible BRICK, Need Help BIGTIME

Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only')
*** RELOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012,02:17:11
In fastboot, it will not allow me to flash to boot, system or recovery. Various errors appears like:
- not allowed
- error code 0000008 (or something)
- '...' then 'complete', but its a total lie because its done nothing.
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!

You're on wrong section mate.
You will have better assistance in Q&A section.
Tips: you need 1.28.771.x RUU to revert to stock. 1.26.771.2 won't work as yours is HBOOT-0.94.0000

I tried
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
and it says there is a customer id error,
Do i need specifically 1.28.771?

Jaso333 said:
I tried
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
and it says there is a customer id error,
Do i need specifically 1.28.771?
Click to expand...
Click to collapse
Yes as that is the correct one for three UK, that's why you had the I'd error.

ckpv5 said:
You're on wrong section mate.
You will have better assistance in Q&A section.
Tips: you need 1.28.771.x RUU to revert to stock. 1.26.771.2 won't work as yours is HBOOT-0.94.0000
Click to expand...
Click to collapse
Well, he has 'developed' a brick....it's just not the development that's normally discussed here ;-)

ewok666 said:
Well, he has 'developed' a brick....it's just not the development that's normally discussed here ;-)
Click to expand...
Click to collapse
Haha!
Sorry , don't wanna laugh on the brick but what he said was funny.
Sent from my HTC One X using Tapatalk 2

Even though my CLID is coming up at 'NONE'?

It'll say none but you'll have the 3UK CID - you will have to wait for the 1.28.771.9 RUU to surface (if at all) or send it back to 3

Jaso333 said:
Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only')
*** RELOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012,02:17:11
In fastboot, it will not allow me to flash to boot, system or recovery. Various errors appears like:
- not allowed
- error code 0000008 (or something)
- '...' then 'complete', but its a total lie because its done nothing.
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
Click to expand...
Click to collapse
Have you tried unlocking the bootloader again to flash anything?
or
In fastboot "fastboot boot new-recoveryver.img"
Then "adb push rom.zip /sdcard/"

fastboot boot says its not allowed

wtfhax said:
Have you tried unlocking the bootloader again to flash anything?
Click to expand...
Click to collapse
Quoting myself

it wont let me unlock the bootloader!
to prove this:
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Android>fastboot oem unlock Unlock_code.bin
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.030s
completely ruined?

yea this happened to my phone
I had to reboot it a few times and keep trying fastboot oem unlock/lock
it should come good.

Jaso333 said:
Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only'
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
Click to expand...
Click to collapse
Had you try reflash stock recovery. I had successfully Ruu 1.26.707.2 from cook 1.28.401.09 then OTA to 1.28.707.10 and pass through a lot of pain warnings.
With correct original ruu, it allows you to recover (try mainfixer.bat) to origin factory status.
Sent from my HTC One X using xda premium

Jaso333 said:
it wont let me unlock the bootloader!
to prove this:
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Android>fastboot oem unlock Unlock_code.bin
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.030s
completely ruined?
Click to expand...
Click to collapse
Proper unlock command
fastboot flash unlocktoken Unlock_code.bin

EddyOS said:
It'll say none but you'll have the 3UK CID - you will have to wait for the 1.28.771.9 RUU to surface (if at all) or send it back to 3
Click to expand...
Click to collapse
Just seen on twitter @Three_UK have just tweeted that 1.28.771.9 is available.

wtfhax said:
Proper unlock command
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
DUDE [email protected] A F***ING LIFE SAVER!!!!!!!
I WAS USING THE WRONG COMMAND TO UNLOCK IT... FFS. IM SUCH AN IDIOT
ITS ALL WORKING NOW
Now to cancel the HTC Service.....

[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] Trying to Unlock Bootloader (And Root) Don't know original carrier

Hey Guys
First time rooting an android and having an issue trying to unlock the bootloader.
Following various guides when I try the command 'fastboot oem get_identifier_token' I get the following error back
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
Upon researching this I've found that the common cause of this problem is the HBOOT being too old to recognise the I]'fastboot oem get_identifier_token'[/I] command. So I've got back to step 1 on HTCDev and looking for a new RUU. The only problem is I've never known what carrier the phone came with as I purchased the phone on ebay. I've tried every RUU for the model number PG7610000 from the HTCDev site but none work. So my only question is, What do I do now?

Solved. For those with same / similar problem. I found that you can upgrade just the HBOOT via a SD Card, So I put the file on the card, and went into the bootloader and select Fastboot. It will find the Zip file and ask to install it.
Then you can follow the standard unlock & Root procedure.

M9 Unlock Token Verify Fail?

Not new to the scene here, just getting back into it. My M9 is giving me trouble; I've been through all the threads Google knows about in English and other languages.
** This is a "One M9 Unlocked" GSM phone; not developer version or carrier-specific **
[KillSwitch] Last Byte is 0X01, enable unlock - I enabled the bootloader unlock option in developer settings.
Using Download mode, as this is the new correct way. fastboot devices works and get_identifier_token works.
I tried several unlock codes from HTCDev.
Tried rebooting and all combinations of rebooting + getting new code.
Tried HTCDev fastboot.exe and android platform tools fastboot.exe.
Tried cmd and powershell.
Tried different folder locations (desktop and C:\Android)
Note that every time I get_identifier_token, the token is different. I don't remember if that's normal.
I've used HTCDev to unlock many devices, never had problems.
Output of every attempt to flash unlocktoken:
Code:
C:\Android>fastboot.exe flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.035s
What am I screwing up here?

xfinrodx said:
** This is a "One M9 Unlocked" GSM phone; not developer version or carrier-specific **
Click to expand...
Click to collapse
I am confused. Why are you trying to unlock a phone that is already unlocked?

Thanks for your question: It is the factory carrier unlocked version. It works with any GSM card without needing a carrier unlock code - however, the bootloader is still locked. Whereas it's nice to not be tied to a carrier, I'd also like to get involved with cyanogenmod again.

For whomever else finds themselves in this situation: Good luck, I have no idea what happened.
I tried and retried this process several times. Finally gave up in exasperation and tried later on a different machine because that makes no sense but why not... Here's my winning magic combination (that I already tried, but on a different machine)
Front panel USB port.
Complete HTCDev unlock procedure with caveats:
I used the Google Bootloader Interface driver; HTCSync has never been on this machine.
I used the Google platform tools fastboot application.
Everything else exactly as HTCDev prescribes.
Do this on two totally different machines; it might help to be exasperated the second time. Did literally nothing different... on to the roms now.

Error while unlocking phone

I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
C:\Users\Ben-Desktop\AppData\Local\Android\sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.005s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) Device is unlocked
OKAY [ 0.013s]
finished. total time: 0.020s
Click to expand...
Click to collapse
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0

ganeran said:
I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0
Click to expand...
Click to collapse
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!

Fain11 said:
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!
Click to expand...
Click to collapse
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?

ganeran said:
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?
Click to expand...
Click to collapse
Start reading here:
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133