Gsm radio not starting - HTC One X

Hey, i have an issue with a htc one x, that i got softbricked used from someone, i managed to unbrick it and everything, but now it seems the radio wont boot up and i get either no signal or no signal and reboots (on cm10).
This is the logcat from cm10 http://bpaste.net/show/5mi1SYLOz3tmscCyS9DP/
the hboot is 1.12, is unlocked, s-on, radio 2.1204.135.20 .
does anyone know what to do? I have already flashed the stock RUU of the same version that was on (by getting getvar in fastboot), but still no radio signal (it says no service on the lockscreen, with a working sim inserted), wifi on the other hand is working well
assuming it was htc dev unlocked, probably if i bring it to warranty they will claim its void and ill have to pay for it ?
if i go under about phone and check baseband version i get unknown...
Thanks

Just a ques but I remember with first custom Maximus Jelly Bean rom by Football the radio wasn't working because it didn't match HBOOT.
I would recommend upgrade HBOOT again and flash one of the latest custom Jelly Bean roms from >> HERE.
And HERE's a easy and nice Jelly Bean firmware flasher thanks to Stuart0001.
I hope for you the device CID is correct to flash Jelly Bean.
And about bringing the device back to HTC for warrantee my ques is it will be voided but you never know.
crnkoj said:
Hey, i have an issue with a htc one x, that i got softbricked used from someone, i managed to unbrick it and everything, but now it seems the radio wont boot up and i get either no signal or no signal and reboots (on cm10).
This is the logcat from cm10 http://bpaste.net/show/5mi1SYLOz3tmscCyS9DP/
the hboot is 1.12, is unlocked, s-on, radio 2.1204.135.20 .
does anyone know what to do? I have already flashed the stock RUU of the same version that was on (by getting getvar in fastboot), but still no radio signal (it says no service on the lockscreen, with a working sim inserted), wifi on the other hand is working well
assuming it was htc dev unlocked, probably if i bring it to warranty they will claim its void and ill have to pay for it ?
if i go under about phone and check baseband version i get unknown...
Thanks
Click to expand...
Click to collapse

Laurentius26 said:
Just a ques but I remember with first custom Maximus Jelly Bean rom by Football the radio wasn't working because it didn't match HBOOT.
I would recommend upgrade HBOOT again and flash one of the latest custom Jelly Bean roms from >> HERE.
And HERE's a easy and nice Jelly Bean firmware flasher thanks to Stuart0001.
I hope for you the device CID is correct to flash Jelly Bean.
And about bringing the device back to HTC for warrantee my ques is it will be voided but you never know.
Click to expand...
Click to collapse
Yes the CID actually fits for the firmware for JB, did you look at the paste link i gave, at line 170, do you know what Ebl is? i believe there is the error, possibly really an incompatibility with hboot and radio?
But i cannot find much documentation on it in combination to the htc one x, i only found this in relation to xgold http://forum.xda-developers.com/showthread.php?t=1483053 , it seems the one x has the same baseband?
I have actually tried the fully stock ruu (ics based) that was supposed to come with it (flashed it as the wiki suggests), but i have the same issue/error, i even tried cm9 and it has the same issue.
Is hboot 1.12 outdated actually ? Im asking all of this, because i dont want to flash the 1.28 hboot and than i will only be able to use jb roms that still wont work =/
thanks again

If HBOOT is upgraded it's not possible to downgrade with a earlier ICS version unless you have a S-Off machine.
So you keep getting a radio and hboot mismatch.
What I'm trying to say is:
You flashed stock rom to try fix radio but because your device is S-ON hboot is locked and doesn't downgrade, it stays 1.12
CM10 roms are based on earlier HBOOT as well so if I'm not mistaking you won't fix the radio like that neither.
Your stuck atm I ques and only way is to flash to latest Jelly Bean, then the radio will work.
About the log, I'm not a Android expert mate, they don't say me much to be honest.
crnkoj said:
Yes the CID actually fits for the firmware for JB, did you look at the paste link i gave, at line 170, do you know what Ebl is? i believe there is the error, possibly really an incompatibility with hboot and radio?
But i cannot find much documentation on it in combination to the htc one x, i only found this in relation to xgold http://forum.xda-developers.com/showthread.php?t=1483053 , it seems the one x has the same baseband?
I have actually tried the fully stock ruu (ics based) that was supposed to come with it (flashed it as the wiki suggests), but i have the same issue/error, i even tried cm9 and it has the same issue.
Is hboot 1.12 outdated actually ? Im asking all of this, because i dont want to flash the 1.28 hboot and than i will only be able to use jb roms that still wont work =/
thanks again
Click to expand...
Click to collapse

Laurentius26 said:
If HBOOT is upgraded it's not possible to downgrade with a earlier ICS version unless you have a S-Off machine.
So you keep getting a radio and hboot mismatch.
I'm not a Android expert mate, these logs don't say me much.
Click to expand...
Click to collapse
yeah i know that, but my hboot is old 1.12 and the radio seems to be for ICS as well, since its from this RUU RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Apparently this RUU has the 1.12 hboot as default as well as the radio that i have on as default. Thats why im wondering why its not working.
I have seen one more thing though, the cpu is constantly at full speed and it wont scale down (doesnt matter which rom)

ICS HBOOT is 0.96 if I remember correct.
crnkoj said:
yeah i know that, but my hboot is old 1.12 and the radio seems to be for ICS as well, since its from this RUU RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Apparently this RUU has the 1.12 hboot as default as well as the radio that i have on as default. Thats why im wondering why its not working.
I have seen one more thing though, the cpu is constantly at full speed and it wont scale down (doesnt matter which rom)
Click to expand...
Click to collapse

Laurentius26 said:
ICS HBOOT is 0.96 if I remember correct.
Click to expand...
Click to collapse
Some people also on 1.12 HBOOT with ICS. Jelly Bean Hboot is - 1.21, 1.28, 1.31

tomascus said:
Some people also on 1.12 HBOOT with ICS. Jelly Bean Hboot is - 1.21, 1.28, 1.31
Click to expand...
Click to collapse
so for using the stock ics i shouldnt have newer than 1.12, right?

crnkoj said:
so for using the stock ics i shouldnt have newer than 1.12, right?
Click to expand...
Click to collapse
correct

k thanks all, just to let you know i dropepd the phone off at the store for warranty, will see what they say... will update once i know more, in case somone else gets this weird error ever again ^ ^

I have the exact same problem.
I was updating my hboot to 1.28 (sucessfully), then installed InsertCion 11.5.0 and then i had the symptoms mentioned in the first post.
So since i am already on the newest hboot with the most recent JB rom running im kind of out of options here.
I will be trying some stuff and will post here if I get it working again.
What is worrying me is that neither the baseband nor the imei are known to the phone.
I would be glad if anyone knows how to solve this problem.
thx in advance.

Sm0ken said:
I have the exact same problem.
I was updating my hboot to 1.28 (sucessfully), then installed InsertCion 11.5.0 and then i had the symptoms mentioned in the first post.
So since i am already on the newest hboot with the most recent JB rom running im kind of out of options here.
I will be trying some stuff and will post here if I get it working again.
What is worrying me is that neither the baseband nor the imei are known to the phone.
I would be glad if anyone knows how to solve this problem.
thx in advance.
Click to expand...
Click to collapse
Seems to be a rather common problem, I've got the same issue.
Hboot 1.12 and I can't get the radio working, I'm on CM10 and any ROM I try still not getting any luck.
Does any one have any fresh suggestions to fix our phones?

so to post back as promised, i brought the phone for warranty approx 2 weeks ago and called them today, since they didnt call me and it seemed weird to me and they told me the motherboard has to be swapped, to my luck under warranty. So i guess the x-gold checksum failure combined with nonworking cpu scaling must be more than just a bad software flash.

Sm0ken said:
I have the exact same problem.
I was updating my hboot to 1.28 (sucessfully), then installed InsertCion 11.5.0 and then i had the symptoms mentioned in the first post.
So since i am already on the newest hboot with the most recent JB rom running im kind of out of options here.
I will be trying some stuff and will post here if I get it working again.
What is worrying me is that neither the baseband nor the imei are known to the phone.
I would be glad if anyone knows how to solve this problem.
thx in advance.
Click to expand...
Click to collapse
I see one thing in common here, the guy from whom i bought the phone had Insertcoin on it installed as well. Now i dont want to point fingers or anything (as i dont know what else the guy did to the phone), but for now this seems to be the only common point.
From the log that i have put up it seems that the radio cannot start due to a checksum error (in the firmware?), as i wanted to warranty it, i didnt flash a newer radio firmware (but reflashing the same version didnt help).
For me the IMEI and Firmware version were missing as well (probably those get reported only after the radio gets booted, which in this case cant)
Btw did you see the nonworking cpu scaling as well?
isbrodie1 said:
Seems to be a rather common problem, I've got the same issue.
Hboot 1.12 and I can't get the radio working, I'm on CM10 and any ROM I try still not getting any luck.
Does any one have any fresh suggestions to fix our phones?
Click to expand...
Click to collapse
I dont really have a suggestion, other than to relock and flash the stock RUU on it and bring it in for warranty, for me they didnt do any issues and said they are just waiting for the motherboard they ordered to replace it under warranty terms (to no cost for me).
I do believe that either the radio firmware is borked (checksum error) or that this thing has something like a cpu firmware (sort of bios in pcs) for the tegra3 chipset which controls both the power scaling and checks the radio and has some corruption in it... Anything beyond this is just speculation.
These two posts might hold some anwsers if you know what you are doing:
http://forum.xda-developers.com/showthread.php?t=1483053
http://forum.xda-developers.com/showthread.php?t=1471241
As it seems that the one X has the same modem (X-gold 626 from intel) as the sgs2 and several other phones.
But as it seems that even the official repair center needs to replace the motherboard instead of just reflashing some firmware (one would i assume they have the proper tools/SBK to do s-off and flash whatever they like in whatever version they like), it might be that some regulators or that the radio broke physically due to bad quality or such

Hi all
Feels like this might be too simple for this thread but I had a similar problem recently on my stock One X - I had no service and my radio wouldn't turn on. I resolved it by turning off Fast boot (Settings - Power)

hey buddy... it didnt solved my prob.. anyone got the solution for the GSM Services Radio Off .. ??

Related

[Q] Noob asking from cid, s-off, getting back to stock, etc.

Hello everybody!
I am relatively new One X owner and my previous handset was the famous HD2, so I used to be quite familiar with all the tweaks and mods. But now I have apparently stepped into a whole new world with a lot more complicated rules. There's talk about cid-numbers, nandroid backup, s-on/s-off, how you can't downgrade, etc. I tried to use the search, but I would like comprehensive answers to all my questions.
First thing first, what's a cid-number? I've read it has something to do with regions and operators, but how does this affect the device? Is this some kind hardware change or just software related? Is there even "international" versions available? Since I am ex HD2 user, the only difference between that device was the T-Mobile and international variat. Now it seems, there's a lot more different handsets available.
How does the cid-number affect the phone? Does these custom roms require specific cid-numbers? Can they be changed at all? What I've learned, my device cid-number is HTC__Y13. Does this mean something? And does it mean I can install for example the ARHD's newest Jelly Bean?
Talking about Jelly Bean, there has been talked about not being able to revert back to ICS? Why? Is actual physical changes made with the device, so it can't be downgraded? I never read people having such problems with the HD2. You could always revert back to older custom, or stock rom, if you wished to do so.
Then there's s-on and s-off. What does this mean exactly and how does it affect my device? I've already unlocked my bootloader, installed the custom boot and custom rom? Am I still somehow locked? I didn't even realize this has something meaningfull purpose.
I've probably already made my first mistake by not creating a nandroid backup. To clarify, I recently changed my stock rom to ARHD 9.7.0 and followed all the noobie instructions, but didn't realize that nandroid backup was somehow essential. Does this mean that I'm screwed somehow or is there a way to fully revert back to stock? Back in the HD2 era, you could have just downloaded the official stock rom and get your device back to stock. So what I'm asking, can I completely revert back to stock if I want for example send the device for repair?
And finally about the official updates. I've read a lot about not being able to update your rom, without reverting back to stock. Is this true and why would people want to do that? Doesn't the new custom roms include all the new improvements and upgrades? Why would people want to install custom rom, then revert back to stock to get the latest updates and then go back to custom? Maybe I've missed something?
Maybe these questions have been aswered a thousand times, in which case I would greatly appreciate, if somebody could point me to the right direction. If not, I would also appreciate, if you could answer any of my questions. It's not funny being in the dark.
Esaj2 said:
Hello everybody!
I am relatively new One X owner and my previous handset was the famous HD2, so I used to be quite familiar with all the tweaks and mods. But now I have apparently stepped into a whole new world with a lot more complicated rules. There's talk about cid-numbers, nandroid backup, s-on/s-off, how you can't downgrade, etc. I tried to use the search, but I would like comprehensive answers to all my questions.
First thing first, what's a cid-number? I've read it has something to do with regions and operators, but how does this affect the device? Is this some kind hardware change or just software related? Is there even "international" versions available? Since I am ex HD2 user, the only difference between that device was the T-Mobile and international variat. Now it seems, there's a lot more different handsets available.
How does the cid-number affect the phone? Does these custom roms require specific cid-numbers? Can they be changed at all? What I've learned, my device cid-number is HTC__Y13. Does this mean something? And does it mean I can install for example the ARHD's newest Jelly Bean?
Talking about Jelly Bean, there has been talked about not being able to revert back to ICS? Why? Is actual physical changes made with the device, so it can't be downgraded? I never read people having such problems with the HD2. You could always revert back to older custom, or stock rom, if you wished to do so.
Then there's s-on and s-off. What does this mean exactly and how does it affect my device? I've already unlocked my bootloader, installed the custom boot and custom rom? Am I still somehow locked? I didn't even realize this has something meaningfull purpose.
I've probably already made my first mistake by not creating a nandroid backup. To clarify, I recently changed my stock rom to ARHD 9.7.0 and followed all the noobie instructions, but didn't realize that nandroid backup was somehow essential. Does this mean that I'm screwed somehow or is there a way to fully revert back to stock? Back in the HD2 era, you could have just downloaded the official stock rom and get your device back to stock. So what I'm asking, can I completely revert back to stock if I want for example send the device for repair?
And finally about the official updates. I've read a lot about not being able to update your rom, without reverting back to stock. Is this true and why would people want to do that? Doesn't the new custom roms include all the new improvements and upgrades? Why would people want to install custom rom, then revert back to stock to get the latest updates and then go back to custom? Maybe I've missed something?
Maybe these questions have been aswered a thousand times, in which case I would greatly appreciate, if somebody could point me to the right direction. If not, I would also appreciate, if you could answer any of my questions. It's not funny being in the dark.
Click to expand...
Click to collapse
hello, so: cid is region/operator number, for europe is htc__01 for example, and you can't change it while we don't have s-off, it's just a number that says to the ruu if it's the right version of phone or not, cid 11111111 is called supercid, and permit you to install every ruu in this world for this phone, but still we can't have it until we achieved s-off.
s-on/s-off are security on/security off, and except for few test devices, everybody have s-on when they buy a phone, and developers and hackers have to find a way to modify it to s-off, which will permit us to flash different hboot version, and downgrade, and change boot animations (the first one, not the second with animation, it's already moddable).
to return back to stock rom you have to relock your bootloader with fastboot command:
Code:
fastboot oem lock
and then download ruu version for your phone from here: http://htcruu.com/?dir=Endeavor
but you should download one with newer/the same hboot version and with your cidnum
to see hboot version just enter in bootloader and look to it there, for cidnum write this on cmd:
Code:
fastboot oem getvar cid
then enter in bootloader and launch .exe you downloaded and follow instructions, in some minutes you'll have completely stock rom! (but still no warranty, because you unlocked your bootloader, and when you relock it, it'll be written RELOCKED, instead of LOCKED when it's new).
flash jelly bean with new sense it's a risk now because it will flash also new hboot, that won't permit you to install previous rom or ruu, so you'll stay on jelly bean until somebody will do rom for this hboot! so i suggest you to wait some weeks and it will be official and more stable and better.
good luck in this new world
Thanks a lot! I guess there's different opinions about the warranty, because I have read that people have been able to fix their devices (under warranty), even after unlocked bootloader, if the device was returned to factory condition prior the repair. So warranty won't be voided completely and all the hardware issues are covered.
I've used app called "Cid Getter" and it gives me this line: [CID is:]: [HTC__Y13]. Is this my cid-number? If so, what is the right stock ruu for me?
HBOOT-1.12.0000 <------ I guess this is my hboot version?
In theory can the device be hacked , so the bootloader would say LOCKED, even if you unlocked it before? Or is this totally impossible?
Esaj2 said:
Thanks a lot! I guess there's different opinions about the warranty, because I have read that people have been able to fix their devices (under warranty), even after unlocked bootloader, if the device was returned to factory condition prior the repair. So warranty won't be voided completely and all the hardware issues are covered.
I've used app called "Cid Getter" and it gives me this line: [CID is:]: [HTC__Y13]. Is this my cid-number? If so, what is the right stock ruu for me?
HBOOT-1.12.0000 <------ I guess this is my hboot version?
In theory can the device be hacked , so the bootloader would say LOCKED, even if you unlocked it before? Or is this totally impossible?
Click to expand...
Click to collapse
y13 i think that it's europe, try to download normal europe no brand version, if you'll have problems try another one,
yes, 1.12.0000 is your hboot version, and it's not the newest so you can download the last ruu without problems
no it can't, but even if it would be possible, it'll be pointless because you gave a number to htc, and they know your imei adress, so even with LOCKED, they'll know... in some countries they don't make problem about, if it's a hardware fault, in others you'll have problem, i don't know just ask htc in your country if you'll need it
Yes I have the European version, since I live in Finland and it is part of Europe and the European Union. Here we don't have branded phones so I guess that doesn't cause any problems. Also the phone was not sim-locked. Could you post me a link to a correct RUU? Does the radio version matter somehow?
What comes to the warranty, I probably will have to see that if it comes to it. Hopefully there's no reason to send the device for repair.
And if I understood correctly, I shouldn't upgrade to ARHD Jelly Bean, because it's going to cause some troubles, if I want to revert back to stock?
Esaj2 said:
Yes I have the European version, since I live in Finland and it is part of Europe and the European Union. Here we don't have branded phones so I guess that doesn't cause any problems. Also the phone was not sim-locked. Could you post me a link to a correct RUU? Does the radio version matter somehow?
What comes to the warranty, I probably will have to see that if it comes to it. Hopefully there's no reason to send the device for repair.
And if I understood correctly, I shouldn't upgrade to ARHD Jelly Bean, because it's going to cause some troubles, if I want to revert back to stock?
Click to expand...
Click to collapse
what radio do you have? i don't know what's the difference, but i think there is a difference between mid-europa and north europa, so maybe there is something different.
about arhd jb you'll NOT BE ABLE to revert back to ics, so no ruu, neither other rom from xda, because they are done for other hboot as i know, so if you'll install it, you'll have it until someone will do something for this hboot
The radio version is 2.1204.135.20. I'm not sure, but I don't think there being a difference between Northern-European and Middle-European devices, at least what comes to the radio version.
So I guess I should stick with the current ICS ARHD 9.7.0 build for now... Thank you for your great help! :good:
http://htcruu.com/Endeavor/RUU_ENDE...Radio_2.1204.127.19_release_271851_signed.exe
this seems to be similar radio, try with it
Hi,
Ive tried without success to get the CID of my phone with get cid app from store or using emulator and the getprop ro.cid command.
Nothing...
What can I do for get it? :S
Esaj2 said:
The radio version is 2.1204.135.20. I'm not sure, but I don't think there being a difference between Northern-European and Middle-European devices, at least what comes to the radio version.
So I guess I should stick with the current ICS ARHD 9.7.0 build for now... Thank you for your great help! :good:
Click to expand...
Click to collapse
CID isn't the only way to find out the RUU for your phone. If you'd done the right thing and checked your software build before rooting to make sure there is an RUU for your phone then you'd know which RUU is for you. For example:
If you were running 1.29.401.11 then RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe would be the one for you
Esaj2 said:
if I want to revert back to stock?
Click to expand...
Click to collapse
Have a look here bro http://forum.xda-developers.com/showthread.php?t=1859714
See you
Franky

Problems with Cyanogenmod and One X

Hey everyone,
I'm new to this whole Rooting and Custom Rom Thing, so today I sucessfully unlocked my bootloader and installed the latest Cyanogenmod 10 build, unfortunatly there is no way that the newest build starts successfully on my phone it keeps stuck with the HTC logo (I've tried all of the boot.img loading and cache deletine before). Then I installed the second latest cyanogenmod and it worked just fine. My phone started and I could configure all of the important things but now I am experiencing trouble with the Wifi. Everytime I try to Activate the Wifi it disables itself instantly. Does anyone have a solution to this problem?
And furthermore I am experiencing another trouble with my HTC:
When I was in Stock firmware (and also now with ARHD Custom Rom) my WiFi seems not to work properly. I can activate it, but it keeps loosing connection although it seems to be still connected with the Wifi but if i try to connect to the internet by browser or something else, the phone keeps telling me that there is no internet connection. I welcome all of your tipps and solutions!
It would also be great if some of you could tell me which Rom is the Best Built on 4.2.1 in terms of Battery Life and Stability.
Thanks for your help!
Best Regards,
DevastatedMind
Do you have the latest hboot for your cid?
And, for me, the best rom 4.2.1 is Ice Cold Jelly
I have the same problem.
With my WiFi and 3G
I had it with ARHD and now with VenomX.
The only thing I can think of is the hboot 1.39
It may be caused by your hboot
Where can I get the latest HBOOT? And how do I install it on my device?
Thanks you already for your help!
Use this procedure for upgrading your hboot.
Not follow the steps 2-3-4, download the firmware.zip and copy it in folder when you have fastboot
For the hboot, see this thread.
You know you cid?
I have the latest hboot 1.39 and have the same problem.
So upgrading might not be a good idea.
Bas. said:
I have the latest hboot 1.39 and have the same problem.
So upgrading might not be a good idea.
Click to expand...
Click to collapse
With which rom you have the problem?
And if this is a problem with a rom, write in that thread..
leditor force
I had the problem with ARHD and VenomX
Upgrade hboot, installed ARHD, reinstall ARHD, install VenomX same problems.
With ViperX, have you choise no at voice of kernel during the installation?
No if I remeber correctly I chose Yes (to backup).
Was this wrong?
You have to choise no when you are installing ViperX
If I may ask whats the difference?
So my CID is o2_____102
What does that mean for me now?
Bas. said:
If I may ask whats the difference?
Click to expand...
Click to collapse
Because the voice: "yes" install modules for a kernel custom, and if you have flashed the stock kernel, you don't have to choise yes, but no
DevastatedMind said:
So my CID is o2_____102
What does that mean for me now?
Click to expand...
Click to collapse
I don't see your cid in the thread that i linked.
What is your hboot?
1.36?
Yeah my HBOOT is 1.36 according to fastboot.
I own a German o2 Branded One X.
And when I read out my CID I get this as an response:
o2___102
Where can I get now the latest Hboot?
I tried downloading some software from HTCdev.com but as it looks like it is the exact same that I have already installed on my phone.
my build nr. is: 3.14.401.31 CL128187
I'm pretty confused at the moment. Actually.
DevastatedMind said:
Yeah my HBOOT is 1.36 according to fastboot.
I own a German o2 Branded One X.
And when I read out my CID I get this as an response:
o2___102
Where can I get now the latest Hboot?
I tried downloading some software from HTCdev.com but as it looks like it is the exact same that I have already installed on my phone.
my build nr. is: 3.14.401.31 CL128187
I'm pretty confused at the moment. Actually.
Click to expand...
Click to collapse
For your cid is the latest hboot..
If you have problem with a specific rom, you have to write in the rom thread.

Need help Flashing stock Android 2.3.5 ROM

Hi, I've got a Desire HD phone which I got unlocked and unbranded from the start and it came with some version of Froyo out of the box. Since then I've updated it through via wifi and currently it's on GB 2.3.5 and after the last update the phone has been telling me that it has no updates available. Furthermore, I have never flashed or rooted this phone so it's still a virgin
Further information on my phone is as follows:
Android Version: 2.3.5
HTC Sense Version: 3.0
Software Number: 3.13.707.4
AND some pics of the specs are in the attachment, please check them out.
Now due to some performance issues I wanted to reinstall either 2.3.5 or lower version of gingerbread or if possible the latest version of Froyo available for my phone. I have already tried restarting, taking out the battery, doing factory reset, wiping the phone and sdcard both from within the phone settings and from the HBoot and Recovery menu as well to no avail.
So I would like to ask you guys for steps and possible links to correct RUU for re-flashing the stock version of unbranded 2.3.5 or lower version of gingerbread or if possible the latest version of Froyo. I don't want to mess with the phone too much by going into the rooting and installing custom ROMS just yet, but that would be my last resort if all else fails.
I'm a newbie so please be gentle in replies
Thanks in advance!
STOP STOP STOP DONT DO ANYTHING!
don't flash any froyo ruu or wwe this will mess your hboot and you'll be in a whole world of hurt.
If you've done a factory reset you shouldn't be having performance issues as that takes you back to factory condition of course.
How ever
Your first course of action now should be goto market and get emmc checker and see if you have the bad chips (sain I think).
If you dont have issue I suggest you do HTCDEV unlock and root your phone or flash a new rom, ive only used SVHD which is ics sense rom which is pretty damn awesome, but im moved on to samsung galaxy s4 (unrooted) now so haven't used newest version yet.
Have a look around the dev forum there are a few really good guides .
Sent from my GT-I9505 using xda app-developers app
I recommend getting s-off and unlocking the HBoot to get the best performance from your phone. I must say that this is not for the faint-of-heart and things sometimes can and do go wrong .
I bought a second hand Desire HD running stock Telus GB for very little money so I didn't have much to lose if I pooched the phone. If you do decide to unlock the HBoot, make sure you upgrade to 2.00.0029 first.
What performance issues were you having?
ranger4740 said:
STOP STOP STOP DONT DO ANYTHING!
don't flash any froyo ruu or wwe this will mess your hboot and you'll be in a whole world of hurt.
If you've done a factory reset you shouldn't be having performance issues as that takes you back to factory condition of course.
How ever
Your first course of action now should be goto market and get emmc checker and see if you have the bad chips (sain I think).
If you dont have issue I suggest you do HTCDEV unlock and root your phone or flash a new rom, ive only used SVHD which is ics sense rom which is pretty damn awesome, but im moved on to samsung galaxy s4 (unrooted) now so haven't used newest version yet.
Have a look around the dev forum there are a few really good guides .
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ran that app and it says " Brick Bug? NO. Sane Chip "
So I'm guessing my phone is good, right?
I've been having some major bugs popping up on my phone ever since I upgraded to the 2.3.5 update. My phone camera gets stuck while taking pictures, at times it has restarted my phone when I take a picture, the GPS/Location keeps popping up at every boot and I can't seem to disable it, the Connect To Computer message which used to let me select in which mode I want to connect my phone to the PC has stopped showing up and the phone only connects in charging mode to the PC, the speaker phone keeps turning itself on whenever I make a call or receive a call. I've read up on all these bugs on many forums and tried all the solutions to no avail, I have already done factory resets, battery pulls, cleaning of the usb connector, tried different usb cables on different computers, formatted the memory card etc, but none of these things worked for me.
So I'm left with one choice only, that is to erase everything on this phone and flash a fresh ROM onto it to see if it fixes the issue. And just to be on the safe side I want to install anything lower than 2.3.5 since that's when all these bugs popped up one by one for me. And I don't want to root my phone just yet or unlock it or do any experiments with it yet.
So my question is, how do I backup my current ROM in case if anything goes wrong I could revert back to this one and then how do I flash an official earlier version of GB compatible with my phone and where to get this ROM. Since my phone came unbranded and unlocked, I'm assuming the WWE versions would work well for me right? I once saw in my phone somewhere that it told me I have htc_asia_WWE version on my phone, if that helps. But I would rather get an English only version which has no other language settings in it, like chinese, vietnemese etc etc which my phone currently has.
Thanks in advance!
vxdesigns said:
Ran that app and it says " Brick Bug? NO. Sane Chip "
So I'm guessing my phone is good, right?
I've been having some major bugs popping up on my phone ever since I upgraded to the 2.3.5 update. My phone camera gets stuck while taking pictures, at times it has restarted my phone when I take a picture, the GPS/Location keeps popping up at every boot and I can't seem to disable it, the Connect To Computer message which used to let me select in which mode I want to connect my phone to the PC has stopped showing up and the phone only connects in charging mode to the PC, the speaker phone keeps turning itself on whenever I make a call or receive a call. I've read up on all these bugs on many forums and tried all the solutions to no avail, I have already done factory resets, battery pulls, cleaning of the usb connector, tried different usb cables on different computers, formatted the memory card etc, but none of these things worked for me.
So I'm left with one choice only, that is to erase everything on this phone and flash a fresh ROM onto it to see if it fixes the issue. And just to be on the safe side I want to install anything lower than 2.3.5 since that's when all these bugs popped up one by one for me. And I don't want to root my phone just yet or unlock it or do any experiments with it yet.
So my question is, how do I backup my current ROM in case if anything goes wrong I could revert back to this one and then how do I flash an official earlier version of GB compatible with my phone and where to get this ROM. Since my phone came unbranded and unlocked, I'm assuming the WWE versions would work well for me right? I once saw in my phone somewhere that it told me I have htc_asia_WWE version on my phone, if that helps. But I would rather get an English only version which has no other language settings in it, like chinese, vietnemese etc etc which my phone currently has.
Thanks in advance!
Click to expand...
Click to collapse
No actually read what EMMC chip you have, that app is made for samsung phones and will only check for those.Type out the one you have
audit13 said:
I recommend getting s-off and unlocking the HBoot to get the best performance from your phone. I must say that this is not for the faint-of-heart and things sometimes can and do go wrong .
I bought a second hand Desire HD running stock Telus GB for very little money so I didn't have much to lose if I pooched the phone. If you do decide to unlock the HBoot, make sure you upgrade to 2.00.0029 first.
What performance issues were you having?
Click to expand...
Click to collapse
If I want to flash the stock ROM, do I still need to do s-off and unlock the HBoot or are these only necessary to flash custom ROMS???
Steam. said:
No actually read what EMMC chip you have, that app is made for samsung phones and will only check for those.Type out the one you have
Click to expand...
Click to collapse
Not sure what you are saying ...
The eMMC app shows this info:
Phone Model
HTC htc_ace
eMMC chip
Type: SEM04G
Brick Bug?
NO. Sane chip
vxdesigns said:
Not sure what you are saying ...
The eMMC app shows this info:
Phone Model
HTC htc_ace
eMMC chip
Type: SEM04G
Brick Bug?
NO. Sane chip
Click to expand...
Click to collapse
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Steam. said:
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Click to expand...
Click to collapse
I did get a RUU which meets my specs exactly, or so I think:
http://www.shipped-roms.com/downloa...60.29_26.14.04.28_M_release_234022_signed.exe
I ran it, updated my phone, it's the same version which is already on my phone, it completed without any issues, but the bugs are still there. So I'm assuming it didn't really reinstall the software from scratch, it just updated the software without making much changes to it, pretty much like a factory reset, right???
Can you please tell me why we need to unlock the HBoot??? Is it to enable us to flash custom roms???
What I want to do is erase the 2.3.5 GB software completely from my phone so it has no trace of it, then install stock/untouched 2.3.3 GB or any other GB version compatible with my phone. So please provide steps and insight into this process.
Thanks
Steam. said:
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Click to expand...
Click to collapse
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Never mind your actually s-off...
Did you do full wipe before flash?
Apparently you really should be using 4ext recovery on dhd as clockwork doesnt quite do the job right?.
Sent from my GT-I9505 using xda app-developers app
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Choose full wipe in aroma installer. i recommend you to used SVHD 1.70 then upgrade OTA 1.73. does not flash version 1.74. this got so much error.
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Flash 4ext, wipe everything and reflash 1.7.0, and then update to 1.7.3.CWM never wiped my partitions properly, it blows compared to 4ext.

[Q] Why is my HTC One x (PROTOTYPE) stuck on ICS?

Why is my HTC One x (PROTOTYPE) stuck on ICS?
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Rad io_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just check the attachments. It has all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and I Thank you for it, I hope you can help me!
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
I did that
nogotaclue said:
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
so you have a stock recovery now? and receive ota notifications?
Yes
nogotaclue said:
so you have a stock recovery now? and receive ota notifications?
Click to expand...
Click to collapse
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
sN_iPower said:
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
Click to expand...
Click to collapse
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
alright
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
alright im going to try that now, I will get back to you once I done it
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
sN_iPower said:
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
Click to expand...
Click to collapse
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
sN_iPower said:
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
Click to expand...
Click to collapse
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
Click to expand...
Click to collapse
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Thant said:
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
Click to expand...
Click to collapse
sN_iPower said:
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Click to expand...
Click to collapse
Actually @Thant replied also, try what he suggests at the bottom of his post to update your hboot, it's a different one to the one you tried, then try a higher ruu
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
Maybe you are right he must to prepear and know the chance to broke his OneX is big because is prototype.
Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
That had crossed my mind actually, but he is receiving ota notifications and the results he posted from "getvar all" indicate everything is as it should be, same model number even.
I have come across an early prototype before and the only 2 differences were the casing and slightly larger headphone jack socket. AFAIK the hardware was the same. Unfortunately, the one I saw wasn't working so I don't know what version of android it had
nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 androidruu/?developer=Endeavor
Click to expand...
Click to collapse
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
xb2 said:
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Thant said:
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Click to expand...
Click to collapse
Ah, I see. Manual flashing stock rom is still ok anyway.
Thanks for the info, Thant
Sent from my HTC One X using xda app-developers app
Welcome... this had been discussed...
http://forum.xda-developers.com/showthread.php?t=2232063
I have Htc one x Prototype only ics no custom recovery no jb
hi, i have a htc one x protoype(engineer model) i have tried many times to install custom recovery and jb ruu but result is always same. bootloop and black screen. is someone can help. i know only xda members can help. so plz

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

Categories

Resources