Related
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Sprite?
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
ruffruff said:
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Click to expand...
Click to collapse
Yes i had same problems. imo the 1.93 isnt a stable rom(yet) so im back with 1.37.456.2 this one is just perfect,very stable,less memory leakage.
Well, the problem is still on going. I can't flash my phone anymore for some reason, even though I've tried both, unsigned and signed Hard-SPL, which both of them flash fine. However, the phone gives me error [276] update error. So not sure what exactly is going on here.
Also, no, didn't sprite backup, phone's just being retarded, mobilecityonline will repair it, but it will take almost 4-6weeks, I cannot wait that long. What else should i try?
Okay, nope not fixed... Flashed it with 1.37, connected to the network for a few seconds, dialed somebody and no ring or anything, but when i called my phone i could hear my own voice. So I guess i have to send it in for repair. Damn.
berlinberlin said:
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
Click to expand...
Click to collapse
Could you please detail? I've flashed 1.93.xxx just in the day it appeared on the site and after flashing, I've restored the backup made with Sprite Backup to preserve the settings and so on. I wasn't worried about the contacts/calendar since I have them in Outlook, but I didn't want to start all over with settings, install programs and so. I've made the restore in "upgrade mode", restoring also the databases. The result was that I got a verry strange TF3D, displaying "Home" between the operator name and date, and strange behaviour. I've seen also that the animations were taken out so I've flashed back 1.37.xxx.3. Could be any problems generated by the restore operation? Should I use a different restore type (eventually not selecting "restore databases")?
I have had no problem with the new 1.93xx rom.
Touch FLO 3d is quicker (probably because the animation is disabled)..
and the battery life is about 20% better
Radio ROM Anyone
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
mhbr12742 said:
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
Click to expand...
Click to collapse
I am on 05 and has no problem ( have been using it for a day now)
I don't know, but If i plug the diamond into my adapter, the network suddenly works and I can actually make calls and everything's fine and dandy, but just on the battery, I can't call anyone, and if I pull out the adapter when the phone gets a signal, the signal stays but again, can't call anyone because i can't hear anything.
It's an awkward problem. I'm not sure if it's my battery or something. So I'm getting another battery off ebay since they don't sell HTC Touch Diamonds in the U.S. yet.
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
adwinp said:
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
Click to expand...
Click to collapse
Yes, me I had same problem twice - freezes on PIN input screen, second problem with this release is that sometimes PIN screen doesn't appear. Now I'm back on 1.37 and everything seems to be ok
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
THe Problem you've encountered:
1. Random auto reboot
2. Random freeze
3. etc.
It's sounds familiar to me. Well it's maybe have to do with SPL just like the Kaisers do.Well, I said maybe... So, what we did to our Kaiser before is flashing the HardSPL which has the same version number as the ROM flashed. So, if you're using ROM 1.93 then the HardSPL should be flashed is Olinex HardSPL 1.93 or you can try one by one of the developed HardSPL existed in this forum. My saying is, go with HardSPL 1.93 and see what happen. If it's still no go then it must have to do with the ROM itself.
Just my 2cents.
I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.
Shaolinstyle said:
I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.
Click to expand...
Click to collapse
Are you able to re-do the Hard spl?
Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.
Shaolinstyle said:
Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.
Click to expand...
Click to collapse
I know this sounds obvious and dont take it the wrong way but are you sure that the rom you are trying to flash as been unzipped properly and is named correctly. Try re-downloading a fresh rom and unzip it and rename it Rhodimg.nbh and put it on the root of your Sd card and try flashing it from the card. Also is the battery charged?
I am certain that the roms that I have been using are unzipped and named properly, there was actually a flahed rom on this phone that was workig fine until it started resetting with the rom on it, I wasn't updating or anything when it started to act up. Plus I use the same roms on a second TP2 which are working fine. I did try now to flash from my SD card, Hard SPL said it installed correctly but when I rebooted phone its doing the restart thing over and over still. Battery has been at 100% or close to for all flashes.
I have an interesting problem, kind of. Bought my phone second hand as supposedly unlocked & debranded but on boot up it after the HTC logo I get the Virgin Media logo, not really an issue though. Anyway the problem is when I switch the phone off and then switch on again it boots up fine to the home screen and then it will reboot itself and carries on doing this. i.e. boot up to home screen then reboot again continuously.
To get out of this reboot loop I have to remove the sim & boot the phone with no sim in it then switch off and insert my normal Vodafone phone sim and switch on again. after that the phone is fine until I power down and then the same thing happens.
Anybody else experienced this or got any ideas?? It came with 1.15.405.4 firmware already installed and I have tried reflashing with the same firmware using the goldcard method & it worked but the problem remains. When the sim registers on the network is when the reboot loop seems to start.
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
TieT said:
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Click to expand...
Click to collapse
Maybe it's a dumb question - But I'm having some issues that doesn't seem to get solved by a factory reset - Would it be an idea to reflash it for this, so the phone gets a fresh rom?
How would I do it specifically? Do you know of a guide somewhere?
sudman said:
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
Click to expand...
Click to collapse
have you tried a different sim card ?
Ye tried a different sim card, boots fine and all is good till you reboot the phone and then the same happens again. Anyways flashing was a disaster this time round as I was doing it on my work pc and Symantec kicked in thinking it found a virus with adb.exe and halted the process & quarrantined the file. Now everytime I try and reflash on a different PC I get the dreaded error(110):file open error. Disconnect the phone & all I get is a black screen & HTC logo. Nice. Thanks Symantec you've just bricked my Desire!!
*UPDATE* - Fixed.
Removed the battery, left it for a few hours then reflashed on a different pc and it flashed fine. Then thought I'd try & repeat so reflashed with the older rom from here (originally used the newer rom posted on Modaco) and got the error again and again couldn't flash back to the newer. Removed the battery left for an hour and then could reflash again and get it working!! Wierd
I had the same problem.
My Solution: remove battery, remove the SIM, put battery reboot, turnoff, remove battery, put SIM, put battery, boot
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
sorry, wrong thread
same here.
Tequila98 said:
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
Click to expand...
Click to collapse
i have the exact same problem!! any solution? after that the phone will boot loop over and over! damn!
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
hmmp
as long as i know, i did not install anything on my phone lately so thats the problem so far and i think tequila98 also having the same problem as me, cause when i remove my sim card the phone works fine. but ive reset my phone yesterday and not restarting so far hope this will continue.
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
jxleung said:
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
Click to expand...
Click to collapse
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Ehsan021 said:
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Click to expand...
Click to collapse
It's probably hardware problem with motherboard. Therefore I recommend you to take your phone to repair center and they should replace mobo with new one. That's what I did and now everything is ok.
I am having the exact same problem. Seems to be related to the SIM.
But the SIM works fine in another phone.
Did anyone find any more information?
If you get random reboots its most likely ther motherboard there is a massive thread about it on the forums. You need to send it off to a HTC repair centre.
Just got this problem.
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Tnx.
R
Edit:
Restored backup and is working fine again.
nandroid backup loop
rottunix said:
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Click to expand...
Click to collapse
I have the same problem.
rottunix said:
Restored backup and is working fine again.
Click to expand...
Click to collapse
I will try it. Maybe the backup is not only a backup but also a remove? Strange.
I will comment if this works also for me.
EDIT: Restore helps
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
time_lord2004 said:
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
Click to expand...
Click to collapse
Simply installing a custom ROM will not affect the radio partition.
Why not try a RUU to return to full stock. Find one for your phone and run that. If it still doesn't work then it's a hardware problem.
Ok, so I replaced the current 2.41.401.41 (August) ROM with the earlier 2.41.401.4 (January) in the hope that a ROM change might reset the cellular radio. It didn't. 'Turn on radio' still does not respond either.
I did this with the bootloader onlocked, but S-ON. I think my very last attempt to fix this could be to set S-OFF, in the hope that some tool might be able to access the radio partition and re-write it or reset it or something. (This is still in the slim chance that this fault really is in software and not hardware!)
Are there any xda tools that write to or reset the radio partition (when S-OFF is set)?
What the...?!!?? So I thought as one last go at this (unless someone had comments re the S-OFF/radio partition idea), I'd let the phone get the OTA update back to the latest OS. So first I executed 'fastboot oem lock'. That of course erased device and reset it again. Radio still not working, no surprise.
After that, restarted in bootloader mode to confirm it says 'relocked', then rebooted normally... and I've started receiving missed txts! WTF.
So with enough restarts/resets, it's fixed itself? Faulty hardware, yeah right. Unless it is on the turn and happens again. [Edit: Yes it has, damn.]
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
I got this disease a week ago, tried to restart, didn't help. Been tapping airplane mode like million times, nothing. Found this thread, followed your instructions guys.
time_lord2004 said:
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
Click to expand...
Click to collapse
Didn't work for me :/ moved on to zachariah's solution...
zachariah109 said:
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
Click to expand...
Click to collapse
Yes, IT WORKED.
Don't get me wrong, this is not the end.
Today. Radio doesn't work again. 5min off doesn't help anymore, unlocking-relocking bootloader ain't do **** too.
If you find any other action sequence which "fixes" radio, please share.
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
lightweaponx said:
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
Click to expand...
Click to collapse
Today I ran RUU. It didn't fix radio. Problem must be somewhere out of radio/system partitions range.
Well, I thought I'd do one final(?) post regarding this issue. I'm starting to concede that I might have a hardware fault, but it's taken a while to accept this.
About 2 weeks ago I started having problems with the 'swipe-down' at the top of the screen to look at notifications and settings (and it started responding badly in the camera app). Then it stopped responding completely... work-around was to use an 'open notifications' app.
However, I tried out 'Apex Launcher' as an alternative to the Sense interface, and swipe-down worked perfectly ok, so isn't the hardware ok? Isn't it a software issue? However, swipe-down had completely stopped working in the camera app by then (using a different camera app is acceptable work-around).
Roll forward to a couple of nights ago, I got notification and updated to android 8/Oreo, what have I got to lose! After the update completed, I can now swipe-down ok again on the home screen! But still not in the default camera app! So have I got a hardware problem or not...
But the big thing, and the biggest headache... once again after the big update (to Oreo) and reboot - once again the cellular radio was not working. I tried all my tricks of the past, nothing would make it go. A factory reset (to Oreo, not an old RUU), unlock and relock (which does a factory reset), nothing worked. Brought up phone info via *#*#4636#*#* and this seems to have had a make-over. There is now a button for 'mobile radio power' (must be a replacement for the 'turn on radio' option) which was showing as off. Turning it on seemed to do nothing (leaving it for a while and then waiting for screen refresh, this button would display as off again).
I'd probably rebooted, shutdown/gone into bootloader at least 2 dozen times, tried all combinations of everything I could think of and could not get it to wake up. At lunchtime today I was leaving the office, booting up my phone one last time and said to a workmate 'going to a shop to look at new phones'. 30 seconds later I look down at my screen... what the *(&$%*&!! I have a signal! Missed txts are coming in!
I know that now that the cellular radio is on, it'll keep running. It always has through this whole ordeal. It's just a matter of getting it to turn on in the first place, or starting after a reboot.
The fact that after installing Oreo the swipe-down works nicely (except for the default camera), and the cellular stuff works fine, once it is on, it really is difficult to conclude whether these are all software or hardware issues. But the reluctance of the system to turn on the cellular radio might be the biggest damning factor to point to it being dodgy hardware.
So the key is not to have to reboot ever again, or at least until the next flagship is out! I still have faith in the HTC stuff, but this has been frustrating...
Hope this helps someone out there!
So i've opened mine up - was due for a screen replacement anyway - tada bad contacts to the radio module (dry solder joint) physically pressed the radio module and it turned straight on. *i've added some paper layers underneath to keep *merckanikal* pressure on it (easier fix than reflowing) and now i know where it chip is i can press on the screen to add a little more if it doesn't work
It really ****ed me today however(seemed to cause phone to bsod, then reboot without radio) and the reason i've spent the last 3 hours replacing the screen and ****ing with the radio.
(whole day of work lost thanks to it. won't see that time back)
In other news i went and tested the note 8's spen - and i think i'm retiring the 10 this week. althought i've just fixed it shes' let me down for the last time.
The only negative i've gotten from the mechanical pressure is the lcd is showing a slight tinge of red now that the glue has hardened. and theirs pressure on the back of the screen. i used 4 layers of 80gsm paper (folded) to pack it out. i'm hoping as the phone heats and moves the paper will compact slightly more and the red blub on the screen will dissipate entirely -
- restarted over a dozen times to confirm the fix is atleast working for me. bootloader'd recoveried etc.. hasn't disabled the radio since..
Hope this helps for any of you still hanging onto the htc10.. (the pixel2's daddy, seriously just feels like the exact same phone*thats what she said?*)
time_lord2004 said:
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
Click to expand...
Click to collapse
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Dissmeister said:
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Click to expand...
Click to collapse
Did It Really Works
Adeel Ali said:
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Did It Really Works
Click to expand...
Click to collapse
Yes it works.
yldlj said:
Yes it works.
Click to expand...
Click to collapse
Brother Did U Tried It U Also Have HTC 10
Adeel Ali said:
Brother Did U Tried It U Also Have HTC 10
Click to expand...
Click to collapse
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
yldlj said:
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
Click to expand...
Click to collapse
Yes I Went From Oreo To Nougat Once
Adeel Ali said:
Yes I Went From Oreo To Nougat Once
Click to expand...
Click to collapse
Then erase persist. Or get back on oreo
RUU worked for me