Develop Bugs

[Q] unlocking bootloader.

ive done all the neccessary steps to unlock the bootloader when i run the RUU it tells me my rom version is out of date but when i try to update it says already current. thanks for any help

Whats your carrier? Are you sure your using the right RUU? When i was doing this, i had a problem similar. I had to exit htc sync before the RUU exe would finish the install. Try that and see if that helps.

Mine is metropcs. I'm still trying but the methods I've tried aren't working. It's on 2.3.4 and hboot version is 1.10.... I've rooted lots of Android devices but this bootloader is a PITA lol edit:I'm good now
Sent from my HTC-PG762 using XDA

[Q] 1.29 update failed

I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.

hy3301 said:
I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
Click to expand...
Click to collapse
You need to flash stock recovery. bootloader doesnt matter. Are you in europe?

hy3301 said:
I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
Click to expand...
Click to collapse
as far as i did my last OTA am on a branded phone. I restored my backup stock rom installed stock recovery and downloaded the OTA and installed fine. No need to relock bootloader or anything else. have you tried rebooting your phone and trying again? or have you flashed the proper stock recovery mate

Doesn't work for me either,puted the stock restore,i even relocked my bootloader and still nothing,it doesn't seem to work,i will try to update trough recovery mode,hope that will work.
Sent from my HTC One X using XDA

Same here, any solutions

I don't think that i will try to update to 1.29 anymore,i read on a site that 1.30 will be lauched very soon,so i will try to update to 1.30 when it will came up.I don't know what else to do,i mean,i've tryed everything and still no luck with this update.

I have exactly same issue as you,but what I think if its be realise of 1.30 for us be same problem if we don't find any solution now.

I'm in Japan. I've tried that, nothing worked.

Mine is unbranded. I've tried all of them. I've had enough of it.

It won't work. Don't waste your time.

No solutions seemed to work so far. My choice is to ignore it.

Yes, me too. No more 1.29.

Same here, was 1.28 and unlocked the bootloader and rooted. Tried CWM method but doesn't work and hope someone will have solution to this.

I have same problems i surf a lot today,and I find that my problem is that 1.29 Update CID is different from my phone CID. U can get u CID by cidgetter from store. And if u try to flash update by cwm it shows what Phone CID's supporting update witch u have. Just try to check this guys,thats what i find and my opinion it should work.
I think my solution to find update witch supports HTC__001 CID

So basicaly you are saying to download the update and then reboot the phone,enter in recovery mode (cwm) and then try to flash the 1.29 update that we've downloaded?i allready tryed that and it doesn't work,gives me an error and stops.if it's a CID problem can't we just put our HOX CID into the update?i think that i've seen somewhere on xda a metod to do that but i don't remember in which topic.
Sent from my HTC One X using XDA

if it possible to change CID in update,so yeas its solution witch we need. But I don't know how to do it.

I think we will skip the 1.29 update and wait for the next one.I'v just read on the forum that version 1.32 was released (nothing confirmed yet,just some pc screenshots),maybe that version will work.I will check periodicaly for the 1.32 update and see if it works.

I found a thread talking about deleting the lines about CID in a update-script file or something similar. I've tried that, but still ended up with error. I am going to give up.

Did any of you flashed something on 1.28?I am thinking that after i updated to 1.28 i flashed the 3 dot removal.Maybe this is the cause that the update fails?

I haven't flashed anything,just rooted flashed cwm and superU. No updates gonna work for us till we get S-OFF its just one solution. Follow guys in S-OFF Discussion they progressed a lot on it. If they crack our S-ON to S-OFF we can do with our phones whatever we want to do. And install whatever we want to install including updates. Now just wait...

Serious help needed, unknown baseband, no signal. HTC won't repair..

Hello fellow hox xda people... I am very stuck in this situation, gutted because I love my hox.
It started when I lost my phone signal for a few hours.. stupidly in a panic I tried to flash stock recovery to try and fix it.. then I noticed my imei and baseband showing as "unknown".. I have relocked and run the ruu but the problem still remains.. I fear u have somehow corrupted the radio partition...
It isn't the sim because that works in another phone, I have tried another sim but still no signal.
I sent it to HTC to repair under warranty but because it had been relocked the won't touch it without me paying £150 to replace main board..
Does anyone have any ideas or thoughts?
I am waiting for the next official update to come and see if writing the new radio will fix it...
Sent from my HTC One X using xda app-developers app

Seems like you've screwed your IMEI. This happened to me on the SGS2 where my EFS got corrupted luckily I had saved my EFS and managed to flash it back.
Not sure if this method also applies to HTC products, or it could be your phone has a hardware fault. If they are trying to charge you then nothing you can do I'm afraid then just cough up especially if it is a corrupted EFS.
Edit : EFS only applies to the Samsung phones, seems like your radio is screwed, if you still have your phone there is a radio thread on the development section, flash a radio again and it might just restore it back.
Sent from my HTC One X using Tapatalk 2

Thank-you for your reply... I did notice similar problems with gs2 when doing research on Google. I have looked at the radio which leads me to think I may be up the proverbial creak... I did try flashing the new leaked radio but with no luck... I do have quite a bit of blind faith in the up coming official update... is there a way of formatting the radio partition and the ruu re-writing it?
Sent from my HTC Wildfire using xda app-developers app

stout0_0 said:
Thank-you for your reply... I did notice similar problems with gs2 when doing research on Google. I have looked at the radio which leads me to think I may be up the proverbial creak... I did try flashing the new leaked radio but with no luck... I do have quite a bit of blind faith in the up coming official update... is there a way of formatting the radio partition and the ruu re-writing it?
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
We can't really do anything in regards to that as we have no S-OFF. Where we can flash radios and rils. Still clueless how it would have damaged it as we don't have S-OFF.
Sent from my HTC One X using Tapatalk 2

It does seem to be a bit of a mystery!... the imei is still there when I check the barcode in hboot screen... does that indicate anything do u think?
Sent from my HTC Wildfire using xda app-developers app

stout0_0 said:
It does seem to be a bit of a mystery!... the imei is still there when I check the barcode in hboot screen... does that indicate anything do u think?
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
Just relock your bootloader, flash with an RUU (branded or unbranded) and everything should be fine. This kind of thing happens once in a while. It happened with my S II and Sensation back in the day

Hi, and thank-you for your response. I have tried that numerous time but still have the same problem, I have flashed the leaked radio too on various roms to no avail..
Sent from my HTC Wildfire using xda app-developers app

stout0_0 said:
Hi, and thank-you for your response. I have tried that numerous time but still have the same problem, I have flashed the leaked radio too on various roms to no avail..
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
That's very odd. That's what I've always done when my IMEI or baseband goes missing. Flashing the official OEM ROM usually writes the ROM, kernel and the baseband if I'm not mistaken. Kinda like when you flash a OEM firmware to the iPhone. It writes over everything hence why you have to use a custom ROM that doesn't update the baseband if you want to preserve your SIM unlock.
I installed Android Revolution HD 7.2.1 the other day (nice ROM by the way). Decided I wanted the benfits of Francos r12 kernel. Flashed it and then had no GSM signal. Baseband and IMEI were both unknown. Thought to myself "f*^k here we go again".
Downloaded this. Went back into the bootloader. Relocked it via adb. Then whilst still in the bootloader, I clicked on the RUU that I downloaded from here.
Once everything booted back up, had GSM, IMEI and baseband back. Proceeded to unlock the bootloader and flash ARDH 7.2.1 again but left out Francos kernel for the time being lol.

More for the legal heads etc. here, but HTC-Dev's website states:
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
If you should require support, please feel free to contact us via the support section of our website, http://www.htc.com
Click to expand...
Click to collapse
It specifically says security is left on to protect the radio etc. - surely this should then be covered by HTC as, according to them, there's no way we could break it. The way I see it, either their 'security' didn't work, or the problem isn't caused by a bootloader unlock?

Hahaha! I couldn't help it. I just had to flash Francos r12 kernel again and what do you know? No IMEI and baseband. All good though. Restored from a nand backup I did earlier this evening and all is well again. Downloaded the kernel again just to make sure the md5 wasn't bung, flashed and same thing happened again. So when you get your HOX working again, don't flash Francos r12 kernel lol.

Eambo said:
More for the legal heads etc. here, but HTC-Dev's website states:
It specifically says security is left on to protect the radio etc. - surely this should then be covered by HTC as, according to them, there's no way we could break it. The way I see it, either their 'security' didn't work, or the problem isn't caused by a bootloader unlock?
Click to expand...
Click to collapse
That applies to every device apart from, maybe, Tegra3. The radio might be accessible.

have the same insuee... yesterday i pick my phone and it has no signal...i think no problem reboot the phone...and no changes.. after i see that imei is unknown and baseband too... the phone with or without sim when i open sim slot says that has a problem to see the sim.. root relock flash stock and other roms is not helped -.-
sorry for my english guys.. but seriosly i tryed a lot of things nothing to do -.-
now i'm downloading an old RUU for flash it to change the radio...

If I'm not mistaken you can't roll back the radio using an old ruu.. I think I tried but it failed. I have also flashed the latest ota update but that didn't work either.. beginning to think its hardware as the weekend before it first happen it was dropped onto its screen from chair height with no immediate problems or damage... really struggling with this..
Sent from my HTC Wildfire using xda app-developers app

stout0_0 said:
If I'm not mistaken you can't roll back the radio using an old ruu.. I think I tried but it failed. I have also flashed the latest ota update but that didn't work either.. beginning to think its hardware as the weekend before it first happen it was dropped onto its screen from chair height with no immediate problems or damage... really struggling with this..
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
No way...no changes...but my HTC are never dropped down..I have no idea why it's doesn't work..some one can help us?

AlexVendettA said:
No way...no changes...but my HTC are never dropped down..I have no idea why it's doesn't work..some one can help us?
Click to expand...
Click to collapse
Check out GetRIL app free in playstore. Bu also see xmoo's radio collection thread under and. dev. section. There are instructions
Sent from my HTC One X using xda premium

eyosen said:
Check out GetRIL app free in playstore. Bu also see xmoo's radio collection thread under and. dev. section. There are instructions
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
thank you.. but..it's the same -.-'' i think i'll pay htc for repair..
p.s. think that it's hard problems..

i'm just trying to... open an old ruu take the boot_signed.img from rom.zip(windows/temp) and flash it in fastboot then i relock my device and flash ruu.. hope that it will work

Fingers crossed bud!.....
Sent from my HTC Wildfire using xda app-developers app

Not trying to start a flame war or anything, but this is why I stopped buying HTC phones and went with the S3. Because ever since they started with this HTCDev garbage, modding your phone became ridiculously difficult.

no way need s-off to downgrade hboot... s-off is not possible for now.. w/o javacard......i don't have idea what to do.. then f-.ck all.. drop my hand down and monday send my phone to htc and cross the fingers for free repair...
p.s. i think..to go to an phone store and say that i wanna see an one x white/grey and change it accendentely.. (stupid and illegal but can work )
edit: it's hardware fault i think..

[Q] Help needed with Desire Z

Hello,
I tried to help out a friend with rooting a Desire Z. He used the guide on http://forum.xda-developers.com/showthread.php?t=1178912. He was still on stock and everything and the guide pointed to that to do first.
According to him everything went fine untill he got at point "I - 4a) Manual Downgrade". After reviewing the files he had used it seemed to me that he had used the G2 version of PC10IMG.zip instead of the Desire Z version (could see it when inspecting how large the file was)
He told me that all other steps before (the temp rooting etc etc) was no problem. And after he rebooted his phone the install of PC10IMG started. After the first reboot however the phone stuck.
The situation now is a follows:
* phone does not boot. It gets stuck at the white screen with green HTC letters/logo and then does nothing
- S-ON
- Phone does boot into Hboot (version HBOOT-0.82.0000)
- RADIO-26.02.01.15_m2
- eMMC-boot
I can get into Fastboot and can send commands thru adb to the phone. However commands that try to flash result in a FAILED blabla signature. Probably since its S-ON status
SDcard is recognized (finally) and I managed to make it accept a stock rom. Many other .zips fail. System says no image or wrong image when searching for them.
I suspect the phone has a wrong bootloader (?) and will only accept G2 roms (wich would not be right since its a Desire Z (?)).
Things I tried so far:
* flash a stockrom: It did do something (saw the blue "loading" bar in the bootloader). After it's done it verifies and returns to the bootloader. The I reboot but it still hangs at white screen with green letters HTC/logo
* tried to flash other roms by putting then on the SD. Gives message no image or wrong image
* tried with adb with fastboot. Nothing is accepted.
Is this phone beyond DIY repairs? Advice or tips would be greatly appreciated (since this crap costed me already a full saturday and sunday)
Many thanks in advance!
(PS: I should have the basic knowledge about rooting, adb and such. Also I rooted my own desire Z succesfully already)

use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE

demkantor said:
use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE
Click to expand...
Click to collapse
Thanks a lot for your reply!
I tried what you suggested 3 times and this is the outcome:
The program starts up fine. Checks the phone with no errors. After a few install screens the phone reboots into a black screen with silver letters HTC (same as seen with adb/fastboot I think?). It starts wiping userdata. Then it says "busy sending"; goes all fine.
The it gets to the point sending "signature" (not sure if I translate correct. I have a dutch version or at least the install was in dutch).
And after a while I get:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
during install it said I had image version 1.00.000.0 and asked if want to update to 2.16.531.6
Anymore advice or sugestions I could try?
Thanks in advance for your answer!
[EDIT]
Seems I can go into some kind of recovery mode (choosing recovery from menu >> gives black screen with greenish icon >> gives red triangle
at that screen I do volume + and power and it gives me a menu in wich I can choose update from SD. Not sure if that can help me in any way? Maybe there is some .zip I can install and reset everything back to factory or something?
Tried already to select something there but gives an error:
(in yellow line) E: Can't mount /cache/recovery/command
Sounds serious tome

Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium

demkantor said:
Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Tried quite a lot of RUU versions but everytime the same damn message:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
Tried to get unlocked bootloader with the tool from HTCdev but that gave me a message ERROR[191]: ROM not supported
Anything else I can try out? (going to try and see if I can get something of a rom thru a goldcard but my hopes dwindle by the minute
Thanks in advance for any help/advice
[EDIT]
After hours and hours of reading I can only think of 2 things myself:
1. somehow the emmc is defunct (broken or totally messed up beyond flashable)
2. it has a wrong radio version (= bricked beyond DIY repairs as far as I could read)
Therefor I descided to contact a company that can JTAG the phone and restore it to its glory. What is a reasonable price for such?
If anyone else has still some tips I'll keep watch of this thread

You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium

demkantor said:
You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks a lot for your advice Demkantor
According to my friend he checked for OTA updates a few days ago (was his motivation in the first place to unroot and flash a custom since he was pissed that his great device didnt get much love anymore from updates and after seeing my Desire working on a custom hehe)
I checked out the RUU versions and also read that they kinda only work if it essentially updates the device (checked the site http://shipped-roms.com/index.php?category=android&model=Vision.
Tried a lot from there but only the WWE versions (CID of gsm was one of those numbers that indicated the gsm is unbranded)
For the sake of it I did make a goldcard and tried to use the extracted rom from an RUU. No luck. It sees it, sends it but fails at checking after that and returns to Hboot. Had a hope that the downgrade (step before perm root) was kinda succesful...
Gonna give it one last try with one of the none WWE versions with the lastest version number to see what it does.
I'll keep you posted!
PS: Damn I wished Gigabyte would make phones! I bet they'd put in some kind of recover rom in case the **** hits the fan hehe

[Q] HBOOT Update failed remote: 12 signature verify fail

So here's my story. Recently been using CM10.1, and decided it was time to make a change. So I began doing some research and found a stock rom. The reason I wanted a Stock is because I missed the Camera app for it. So I decided why not go back. Only problem is it needed a hboot of 3.30. So then began my quest. I began finding firmware to update the HBOOT. Here's the kicker, my CID is SuperCID. I tried running Fastboot oem writecid to HTC__001, and it changed it, but it would not accept the update, I was getting FAILED (remote: 12 signature verify fail) multiple times, it didnt matter what I did. It just would not push. So I decided I'd finally create an account on XDA just for the sake of asking for help. Ive been lurking since I owned my HTC Aria when It was brand new. Any help would be appreciated. One last sidenote, Im S-ON. So no luck there.

Disenfranchised said:
So here's my story. Recently been using CM10.1, and decided it was time to make a change. So I began doing some research and found a stock rom. The reason I wanted a Stock is because I missed the Camera app for it. So I decided why not go back. Only problem is it needed a hboot of 3.30. So then began my quest. I began finding firmware to update the HBOOT. Here's the kicker, my CID is SuperCID. I tried running Fastboot oem writecid to HTC__001, and it changed it, but it would not accept the update, I was getting FAILED (remote: 12 signature verify fail) multiple times, it didnt matter what I did. It just would not push. So I decided I'd finally create an account on XDA just for the sake of asking for help. Ive been lurking since I owned my HTC Aria when It was brand new. Any help would be appreciated. One last sidenote, Im S-ON. So no luck there.
Click to expand...
Click to collapse
Same issue. Tried going back to stock and have same problem. hboot 154 here ((((((((((

ipmanwck said:
Same issue. Tried going back to stock and have same problem. hboot 154 here ((((((((((
Click to expand...
Click to collapse
Hboot 3.30? Doesn't sound like an endeavoru..
look in the bootloader, does it say evita/endeavoru?
edit: 1.54 sounds like a HTC one, if that is the case youre in the wrong forum

DOH ! too many beers my bad

Well atleast that solves the problem for one of you
Sent from my HTC One X using xda app-developers app