Develop Bugs

[Q] Problem with Desire Z

Hi folks,
i´ve a problem with a Desire Z from a friend.
Every time when the phone boots, it stops at the HTC Logo.
I think it´s bricked
Is there any possible to flash the Rom (like Odin on Samsung Android Phones)
Thanks

If you power the phone off, then holding down the volume button, press the power button. Does the Hboot screen come up?
Also, you don't give a heck of a lot of info. Is the phone rooted, and/or S-Off? If not, then no, you can't flash a custom ROM.
But you may be able to flash the official ROM from Hboot.

the H Boot screen is this with "bootloader, reboot" and something with the 3 androids ?
when its that, i come into the hboot screen .. i did try the "factory reset" but it hangs on the 3 androids at the middle of the screen
EDIT: The Phone is not rooted, S-on stands there
but how can i flash a official ROM ?
i found one, but it recognize the phone

Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".

Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer

redpoint73 said:
Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".
Click to expand...
Click to collapse
okay, it´s a free phone without branding.
where can i read the CID !?
Nipqer said:
Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer
Click to expand...
Click to collapse
Where can i get adb mode ? the hboot or at the HTC LOGO !?

I have this problem too but i rooted and s-offed. What should i do now. Same things as him.

Nipqer said:
At a guess, it's a Hardware issue, there's a thread here about it.
Click to expand...
Click to collapse
Its possible, but also highly speculative. Damage to the ROM, or the ROM missing may also cause the same issue (stuck on boot splash).

bboy2000 said:
I have this problem too but i rooted and s-offed. What should i do now. Same things as him.
Click to expand...
Click to collapse
You're in (possibly) better shape then the OP. Try flashing any known good ROM from Hboot/recovery. Preferably a rooted ROM, if you want to stay rooted.
But its possible you may have something more going on than a bad ROM file, like mentioned in post #5 above.

i couldn´t find a tutorial how to flash the desire Z im H-Boot mode ?
can u give me a tutorial !?

[Q] Is my phone bricked to death?

Hi all, had a search but nothing seems like my case, I'm writing because I think I've seriously bricked the phone.
Rom:LeeDrOiD HD V3.3.3-Port-R5
S-Off
Stock Hboot
Flashed a new radio, rebooted and nothing showed up for a long time, tried (stupid idea i know) to remove the battery then BAM! Phone dead, any button combination won't work, so no I don't have fastboot, and it doesen't even light up the led if connected it to the wall charger, also the pc doesen't see it.
It's better to bring it to HTC ? Could it be fixed by them ?
Many thanks
Regards
Emilio

I'll try to remove the battery for some hours, and also will try with another battery
Any suggestions?

I think you know the answer to this.. Never take out the battery when flashing radios, the radio gets properly flashed upon first boot. If its corrupted, its bricked. Did you check md5? Can you? Can you get into bootloader? Or connect fast boot? if you can't get into fast boot, its back to htc. How did you flash? Recovery? pb99img our fast boot is the best.

When you flash a new radio, the hardware gets updated. If there something goes wrong, you desire is completely hard-bricked (and so nothing more than an expensive paperweight). And I am pretty sure, even HTC cannot fix a radio damage. Even if they can, they won't do it because you lost your warranty.

MatDrOiD said:
When you flash a new radio, the hardware gets updated. If there something goes wrong, you desire is completely hard-bricked (and so nothing more than an expensive paperweight). And I am pretty sure, even HTC cannot fix a radio damage. Even if they can, they won't do it because you lost your warranty.
Click to expand...
Click to collapse
Well..im not completely sure..if u are still in warranty period, you can try say they that you was applying an ota (for example one about the froyo update) and it failed..the ota also contain radio updates sometimes..and as the phone is bricked they can't know if he is s-off etc..

andQlimax said:
Well..im not completely sure..if u are still in warranty period, you can try say they that you was applying an ota (for example one about the froyo update) and it failed..the ota also contain radio updates sometimes..and as the phone is bricked they can't know if he is s-off etc..
Click to expand...
Click to collapse
good plan, id go with this.

[Q] Screen problem

Hi everyone
I need your hlep please
my one x was working great for more than 5 month but I want to root it and change the rom ( stupid idea )
it was on 2.20 and with ICS 4.0 update then I root it, after that the screen have a problem
some time it not work at all (balnk while I can hear the sounds) and some time its work but for few hour then become artifacts then blank again.
I try to relock the bootloader, unroot, and reflash the official ruu but I still have the problem.
plase I need your help

voltrooon said:
Hi everyone
I need your hlep please
my one x was working great for more than 5 month but I want to root it and change the rom ( stupid idea )
it was on 2.20 and with ICS 4.0 update then I root it, after that the screen have a problem
some time it not work at all (balnk while I can hear the sounds) and some time its work but for few hour then become artifacts then blank again.
I try to relock the bootloader, unroot, and reflash the official ruu but I still have the problem.
plase I need your help
Click to expand...
Click to collapse
Got the same problem. I've read a lot the last days, trying to find out if revert to stock would solve the issue. But it looks to me like it wouldn't..?
It's very confusing, some people says its software problem, other it's hardware and their only advice is to return the phone. This is super frustrating! My phone is useless!

if it's software or hardware problem why it just apear after root ??
hope we find any way to solve it

voltrooon said:
if it's software or hardware problem why it just apear after root ??
hope we find any way to solve it
Click to expand...
Click to collapse
You're posting in the ENDEAVORU thread when you have an EVITA.
Who knows what you've done to your phone?

voltrooon said:
if it's software or hardware problem why it just apear after root ??
hope we find any way to solve it
Click to expand...
Click to collapse
Thing is; people get this issue wether rooted or stock.
I'm thinking of following this simple process (option 2): http://forum.xda-developers.com/showthread.php?t=1859714, doing it with the latest RUU (for me, I guess, since i bought my device in Sweden, it would be "RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.12_Radio_2.1204.127.19_release_271851_signed.exe"). But I don't know if it's worth it, or if that is the right RUU for me? My original version-main is: 1.28.401.9. Do you/anyone know if it would be more safe to use the original, or could I jump to the latest right away?
Also, I really would like find a way to fix this without going through the unrooting process. The last, and most important, step (6) looks like an make or brake thing to do...
"6. On your pc run the RUU that you downloaded earlier, follow the steps as prompted and patiently wait for it to finish.
REMEMBER your phone should be charged ABOVE 50% AND if the ruu or restore is INTERRUPTED 4 any reason during restore your
phone will be PERMANENTLY BRICKED.."
Here's a video, showing exactly how my phone looks/behaves:
http://www.youtube.com/watch?v=QdyKHf0F7RA

deud, if it's a hardware fault, which seems likely, the RUU won't help.
You can flash the latest, in your case 2.17.401.2

BenPope said:
deud, if it's a hardware fault, which seems likely, the RUU won't help.
You can flash the latest, in your case 2.17.401.2
Click to expand...
Click to collapse
What do you meen by latest being 2.17.401.2? For me it looks like 1.29.401.12 is the latest? I use this for source: htcruu dot com.
If not, where can i find that?
I'm on
hboot: 0.94.0000
rom: CyanogenMod 10 - Endeavor Unleashed | 028 | UNIFIED HBOOT | 4.2.1
kernel: tripndroid_pro_series-012

http://www.htcruu.com/Endeavor/RUU_...Radio_2.1204.135.20_release_274900_signed.exe

Ok, thanks. But I'm trying a different kind of thing now.. Gonna try update my hboot to latest 1.36 and installing ARHD instead. Or is that maybe a really stupid thing to do, since I can't go back after that..?
[edit]
Ok, so I did the whole update and all that things, and it actually seemed to do the trick?! Crossing my fingers...
Thanks for all the help Pope!

deud said:
Ok, thanks. But I'm trying a different kind of thing now.. Gonna try update my hboot to latest 1.36 and installing ARHD instead. Or is that maybe a really stupid thing to do, since I can't go back after that..?
[edit]
Ok, so I did the whole update and all that things, and it actually seemed to do the trick?! Crossing my fingers...
Thanks for all the help Pope!
Click to expand...
Click to collapse
WRONG.
Some two hours later; problem still exist. Desperate.

deud said:
WRONG.
Some two hours later; problem still exist. Desperate.
Click to expand...
Click to collapse
It sounds like a hardware fault. I'm not sure what you expect us to do here.

BenPope said:
It sounds like a hardware fault. I'm not sure what you expect us to do here.
Click to expand...
Click to collapse
It sure does.
Me neither... I'll continue googling.

deud said:
It sure does.
Me neither... I'll continue googling.
Click to expand...
Click to collapse
maybe this will work with you http://forum.xda-developers.com/showthread.php?t=1671135
I can't apply the steps right but I think if we return it to the original fraimware it may work again

hedayrn school
Thanks, but I think I'll stick with the 1.36 hboot for now, since I read somewhere that these black/flickering screen issues can reduce within 2 weeks of use, screen brightness at max. Got something with voltage calibrating to do, if I understood it correct... And as far as I know, you can't downgrade from 1.36, yet.
The phone now works "ok", very few flickering problems, as long as it's on. If/when I turn the screen of, it usually meen I have to reboot the device, since it just won't wake up the screen again.
Therefore, I still wonder if it's a hardware fault, since it got significantly better after the hboot update?

"dude" can I ask you how to do voltage calibrating ?

voltrooon said:
"dude" can I ask you how to do voltage calibrating ?
Click to expand...
Click to collapse
I actually don't know what that is supposed to meen.. I just read it somewhere on one of them 1000 pages of nonsense I've stumbled over the past three days.. For real!
Anyway, I have mailed with HTC a couple of mails (they're seriously fast at answering, gotta give 'em that..), but they won't answer the simple question "Is it hardware/software?". Which is frustrating. And I also got pretty standard suggestions; format cache, system, etc... As I told them I had already done that, they said I should send the phone to them for repair. Don't know yet what to do.. I really would like to know if it's hardware/software problem!

Dude if you think its a hardware fault ,why dont you visit the nearest htc service center and send the phone back.

Hardware
I'v had the same problem.It is most probably hardware fault: Black screen of death: http://forum.xda-developers.com/showthread.php?t=1745886
and here is a fix that will make it more tolerable :
http://forum.xda-developers.com/showthread.php?t=1923943

Thanks so much! Gonna try it and report back!

e_yasini said:
I'v had the same problem.It is most probably hardware fault: Black screen of death: http://forum.xda-developers.com/showthread.php?t=1745886
and here is a fix that will make it more tolerable :
http://forum.xda-developers.com/showthread.php?t=1923943
Click to expand...
Click to collapse
Thanks so much I will try it and let you know what hapend

Another Airplane Mode Stuck Problem

Hi,
I'm really having trouble with my HOX.. This is the limited edition HOX (half black and half white) Cushnie et ochs.
Problem:
-Stuck on airplane mode(turning off)
-No IMEI and Baseband
-Heats up
--Sometimes network signal shows up (imei and baseband shows up as well) BUT can't receive/send message or can't make calls (when this happens it doesn't heat up)
--It worked one time but back to the same problem when rebooted
Details:
-ENDEAVORU PVT SHIP S-OFF RL
CID-111111111
HBOOT 1.39.0000
RADIO 5.1204.162A.29
-Acquired with a superCID
-unlocked
-currently running ViperX 4.0.5
Actions taken:
-RUU
-Flashed custom ROMs
-Flashed boot.img's
-Flashed kernel's
-Flashed lower radio version(doesn't seem to have an effect coz radio in HBOOT is the same as in Settings.(compared when baseband appeared)
-Wiped everything that needs to be wiped
--Still no luck--
----Can't flash a nandroid backup coz i don't have one(if somebody can point me to the right direction i will flash it immediately)
Hoping somebody here will and can help me.
Thanks in advance!

Hoping somebody will help me..
Can't flash nandroid backup coz i don't have one and i don't know whaT to download because i don't know the original CID of this HOX if it matters.

2 months ago I receive 2 hox have problem like you. No imei, baseband. Still wifi. Stuck in airplane mode. No sim card detect. I try to re flash ruu, rom, radio but nothing better. Last try, i use box to s-off both hox, after that i try to downgrade the radio version of hox, one hox become normal. One hox still problem. After few day contact htc and friend, they confirm some hox have problem with hardware. Finnaly, i replace a new hox mainboard.
I think u should return it to htc for mainboard replace. It is a hardware problem
Sent from my HTC One X using Tapatalk

Huongnv said:
2 months ago I receive 2 hox have problem like you. No imei, baseband. Still wifi. Stuck in airplane mode. No sim card detect. I try to re flash ruu, rom, radio but nothing better. Last try, i use box to s-off both hox, after that i try to downgrade the radio version of hox, one hox become normal. One hox still problem. After few day contact htc and friend, they confirm some hox have problem with hardware. Finnaly, i replace a new hox mainboard.
I think u should return it to htc for mainboard replace. It is a hardware problem
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
I believe it's out of warranty.. Well i will try to downgrade the radio. Thanks for your reply.

I just wanted to try flashing a nandroid backup. Hoping someone will point out which Nandroid backup i will use.
Thanks in advance!
Flashed low radio version, Still no luck.

mcoolit23 said:
I just wanted to try flashing a nandroid backup. Hoping someone will point out which Nandroid backup i will use.
Thanks in advance!
Flashed low radio version, Still no luck.
Click to expand...
Click to collapse
You are S-OFF you can install any RUU just download the 3.18.401.x RUU install on your hox and see what will happend after this. Receive the update to 4.2.2 and everything will be stock and you will see if the problem it's still there.

Thant said:
You are S-OFF you can install any RUU just download the 3.18.401.x RUU install on your hox and see what will happend after this. Receive the update to 4.2.2 and everything will be stock and you will see if the problem it's still there.
Click to expand...
Click to collapse
Will try that.. I will let you know what happen later...

Thant said:
You are S-OFF you can install any RUU just download the 3.18.401.x RUU install on your hox and see what will happend after this. Receive the update to 4.2.2 and everything will be stock and you will see if the problem it's still there.
Click to expand...
Click to collapse
Hi again. I can't seem to find any 3.18.401.x RUU.. only the OTA.. Sorry for being such a newbie but how to flash OTA?

mcoolit23 said:
Hi again. I can't seem to find any 3.18.401.x RUU.. only the OTA.. Sorry for being such a newbie but how to flash OTA?
Click to expand...
Click to collapse
You can't. It's just a update, not a full rom. Do you try androidruu website? You can download sense 4 android 4.0.4 for low radio. Or just download radio img and flash it via bootloader.
I think it possible
Sent from my HTC One X using Tapatalk

Huongnv said:
You can't. It's just a update, not a full rom. Do you try androidruu website? You can download sense 4 android 4.0.4 for low radio. Or just download radio img and flash it via bootloader.
I think it possible
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
Yup searched there already.. 3.14 is the latest there... Downgraded radio earlier as per instruction but nothing happened. Battery drained very fast, from 100% to 69% in a few minutes(10-15 mins)

mcoolit23 said:
Hi again. I can't seem to find any 3.18.401.x RUU.. only the OTA.. Sorry for being such a newbie but how to flash OTA?
Click to expand...
Click to collapse
Sorry my mistake install this RUU 3.14.401.31 and see what will happend
EDIT: If nothing changed go to ICS rom and see what will happend if nothing changed maybe is a hardware fault.
When you run fastboot getvar all are you see the IMEI in information?

Thant said:
Sorry my mistake install this RUU 3.14.401.31 and see what will happend
EDIT: If nothing changed go to ICS rom and see what will happend if nothing changed maybe is a hardware fault.
When you run fastboot getvar all are you see the IMEI in information?
Click to expand...
Click to collapse
I already tried that RUU.. Will try ICS RUU later.. Yes I see the IMEI in fastboot getvar all. Will let you know what will happen after I Flash ICS later. Will still download it.

Ok. Battery drain very fast because phone alway search signal but stuck in airplane. Is your phone hotter than normal phone on the top speaker?
Get var all alway display the imei and baseband, it's normal with other phone. But it't cannot show in phone when boot into rom
I think problem is not a rom.
Some information i hear about china, they remove the cpu tegra 3 and replace other and it become normal. I haven't test yet because i don't have a tegra 3 cpu for replace
Sent from my HTC One X using Tapatalk

[Q] Rooted HTC One M7vzw S-Off KK Rom Trouble

Ok so I'm exhausted at this point because I can't find a fix anywhere, and am fairly certain the issue I've been having is due to my flashing a custom ROM with an incompatible Firmware or something of the sort.
The basics are I have an HTC One M7 from Verizon that was on JB when I first purchased it. I HATED Blinkfeed, but also a lot of the sense things. I had previously rooted and put a custom rom on my HTC Incredible and had a totally amazing experience.
So I ran with the M7 and custom rom for over 6 months without issue. Finally I found out that dev's had found the exploit to get rooted users up to date with the new 4.4.2 KitKat. So I read up on the flashing instructions from a couple of different sources, researched the Developers I was interested in Rom's from, and eventually flashed a Venom Rom. Well immediately my freshly wiped clean rooted, s-off phone, now running
3.1.605.1, HBoot 1.56, and supercid started having troubles. I would wipe/flash/boot run on the ROM for a few days, it would crash, I would wipe/flash STOCK/boot let that sit for a while, then wipe/flash another ROM/ boot etc.etc.
So now to the issue. I cannot get audio out of anywhere else on the phone besides just holding it up against my head. No speaker phone functionality, No headset, No ringtones, No Notification sounds, No touch sounds of any kind, ZIP, NADA. No matter what I flash STOCK/Custom ROM/XXYYzz same issue no sounds. I can place calls and get calls fine, but only if I am actually holding my phone to feel it vibrate. If I'm in a call people can hear me just fine as long as I am holding the phone to my ear and talking. If I try plugging in my headset suddenly they can't hear me, nor I them. If I try to put the phone on speaker, same thing occurs, it's almost as if we are both on mute. Then there is the strange and unusual issue of me not being able to get a single sound out of the phone. No matter what I do I can't get it to make a peep.
For days I have been trying to find a fix for this issue, to no avail. So I turn to the community and hopefully you all can be of some help!
Specs are below. Thanks in advance!
HTC One M7 Verizon
Unlocked bootloader / S-Off / Root privileges
Model: HTC6525LVW
HTC Sense V: 6
HTC SDK API: 6.17
Platform: 4.4.2
Super CID: 11111111
Baseband: 1.13.41.0109_2
Kernal: 3.4.10-Nuk.3rn3l-KK-s6
Build: 1.54.401.5
Release Keys: CL325784

Have you tried doing an ruu to conpleet stock to see if it still happens, or are you just flashing stock roms? If you do an ruu and the sound still dosent work, its more than likley a hardware issue.

cmlusco said:
Have you tried doing an ruu to conpleet stock to see if it still happens, or are you just flashing stock roms? If you do an ruu and the sound still dosent work, its more than likley a hardware issue.
Click to expand...
Click to collapse
Yes I have tried both the ODEXED and DEODEXED versions for my version/system.
It's crazy that this problem hasn't been encountered before, and/or been discussed in the search terms I have been using.
At this point I am running completely stock with the exception of being rooted and S-Off with an unlocked bootloader. If I can't find a way to wipe & restore the entire phone contents from fastboot/bootloader/ADB shell commands, I am just going to give up and reset, lock, and S-On so I can bring the phone to Verizon to get another.
This is just the last of many problems I have had with this phone since I got it. My husband has the exact same phone, and hasn't had any of the problems I've had.
I wouldn't say I am a n00b with adb and fastboot, flashing recoveries & ROM's, but I am not a coder, and really can only operate the basics without a coder's help.

Odexed and deodexed refer to roms, not ruu's. You need to do an ruu thru hboot using fastboot commands.

cmlusco said:
Odexed and deodexed refer to roms, not ruu's. You need to do an ruu thru hboot using fastboot commands.
Click to expand...
Click to collapse
My apologies, I have flashed and done so much in fastboot over the last few days my head is spinning.
I downloaded a 2.10.605.1 RUU Decrypted file, went into fastboot and downgraded my system. Hoping that the entirely different operating system would get the speakers working. NOPE
At this point I'm exhausted, tomorrow I plan on finding the thread that has the steps to get everything locked and back to stock and use the warranty for this POS. I miss my Incredible
Thank you so much for you help though, I appreciate someone responding.

Well if you did the ruu, all you need to do is take the kk ota, then use fastboot commands to lock the bootloader and then go s-on.

cmlusco said:
Well if you did the ruu, all you need to do is take the kk ota, then use fastboot commands to lock the bootloader and then go s-on.
Click to expand...
Click to collapse
That's my plan I'm downloading the needed file to remove the tampered/relocked warning before going s-on. What makes me sad is everything was fine with my phone (unlocked and all) until I broke down and decided to update to KitKat.
Thank you for being responsive to me. The first few days I was feeling very sad that no one had given any kind of response to my issue. You also were the only person who responded to another cry for help by me a few weeks back when this all started. So thank you again for being such a valuable member of this community, even when you have to repeat yourself, I'm sure, many times to those of us who are just starting to get the hand of all this information/terminology/etc. :good::good: