I feel a little dirty having this as my first post, but this problem has been eating at me for a week now.
Current Bootloader Status:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I bought this Sensation from eBay a week ago in a Used state, the owner said the only problem it has was the radio did not function correctly, most likely due to a dodgy flash (it was already rooted, S-OFF and with SuperCID), which I solved by re-flashing using RevolutionHD. All seemed fine until the second boot, where it began to reboot randomly, but ONLY when it has been normally booted and not in the charger. Thinking how it only rebooted due to the charger, I immediately thought it was the battery, but after swapping the battery from my perfectly working EVO 3D with the one in the Sensation, it STILL rebooted constantly. When in either the Bootloader or 4ext, it does not reboot or show any problems.
Just as a precaution, I went through the S-OFF and SuperCID processes again to see if he did something wrong along the way. I then re-loaded 4ext and ran the superwipe script, followed by re-flashing with a re-downloaded RevolutionHD. After its first boot, everything seemed fine for a day, no reboots and working like a charm, but soon went back to its rebooting error again, exactly like before. The same with other ROMs, both ICS and Gingerbread.
As the last extreme, I opened the Sensation to see if anything seemed odd or out-of-place, which is when I found out that the WiFi flex cable was missing, which even though I know I can easily buy a replacement, it annoyed me a bit, but I was wondering if that could upset the OS?
So yeah, at the moment I am at an impasse with this phone and, if I can't get this to work, try to get a refund due to the missing parts.
Any ideas?
Hi,
you said you tried both GB and ICS. Did you flash the correct firmware with the roms? And which kernel did you use?
I used the firmwares recommended in the ROM threads and kernels that came with them.
That seems strange. Android Revolution HD is a very stable rom. I ran it for quite a long time until i couldnt see Sense anymore.. So your problem should not be rom related. I think the only thing you didnt try was wiping dalvik cache. I read in some rom threads that it is recommended to do it when you flash the rom. But I dont know if this would help. I only heard of people getting random reboots when they ran an unstable rom.
so when flashing Roms you used the 3.32 firmware? In my "personal" opinion I would be a bit upset for the missing part. Even if you were able to get the device to function as it should, missing parts are not acceptable unless previously stated in the purchase contract. Like i said only MY " opinion" but if it were my device and I was certain their was no mention of the missing parts, I would definitely take the device back. And I would buy another with all parts present, however this is just a opinion and its up to you on what you want to do. I think its wrong to sell a device with missing parts unless the buyer is aware of this before sale. So if it were mine, I'd take it back and have him explain why you were NOT told ahead of time about the missing part! I wish you the very best in whatever you decide to do! Good luck to you! The sensation is a great device and I think you will love it!
Sent from my HTC Sensation Z710e using xda premium
Thanks for the advice so far guys.
That's what I told my Dad (it's actually his phone he bought, but I'm doing all of the legwork, I'm an EVO 3D man ), I said he should ask for a full refund due to the product not being as advertised, but he still wants to keep it and replace the cable. Dads, eh? I assume that firmware updates the radio, correct? I noticed that when I flashed the latest firmware on the Sensation, the radio version DID NOT change. I have just finished flashing with the latest radio and RIL available for ICS ROMs, which has given me a new version number. I'll keep posted to tell you guys if it solved the issue or not.
Nope, still rebooting. Can the the lack of the flex cable cause issues with the OS? I think I've ruled out software by now, unless you guys have other suggestions?
Tezuka101 said:
Nope, still rebooting. Can the the lack of the flex cable cause issues with the OS? I think I've ruled out software by now, unless you guys have other suggestions?
Click to expand...
Click to collapse
do you have wifi turned on or what... it was the wifi cable right, I would check to see under setting that only mobile data is being used not wifi.... just my thought.
Sadly I can't switch it off, it constantly tries to switch it on, but due to the cable missing it always fails and retries constantly.
Tezuka101 said:
Sadly I can't switch it off, it constantly tries to switch it on, but due to the cable missing it always fails and retries constantly.
Click to expand...
Click to collapse
well you could try to reinstall the rom and in setup it asks about data usage i think try to click for mobile data only....
what rom are you using on the phone ????
I'm currently using RevolutionHD. I have tried Virtuous and getting the same result. I'm re-downloading RevolutionHD to try what you said and choose mobile only.
With WiFi on the off setting (but saying "Error") it still reboots. I've now run out of ideas what this could be. What else could be causing this?
Related
Hello,
As soon as I tap the wi-fi icon, it turns to an "error" state.
I ve seen some threads here, but could not be sure about the resolution. To give idea let me sum it up. My device has been brought from US and I am in europe. İt is alreasy ship s-off.
android version : 2.3.4
software number : android revolution HD 3.6.0. by mike1986
kernel version : 2.6.35.14-Sensation-faux123-v0.1.8+
baseband version : 10.42.9007.00p .....
build number : 1.73.401.2 CL161971
and this topic
http://forum.xda-developers.com/showthread.php?t=1193063&page=2
basilcallly tells to apply a signed ROM . But can you please advise which ROM would solve my wi-fi issue. and how to apply that?
Thanks in advance
I also had similar issue when I flashed the original recovery to remove the rooting and clock work mod...
Now if u have the original recovery installed...flash the OTA updates through it and if you don't have the OTA you need to flash the original ROM
After the flashing ur wifi will work normal
hello,
actually I am so new to the stuf. I havent applied any updates to the device, but I guesss it has been s-off ed and applied a different ROM before it has been sold to my friend in USA. Now, which exact ROM would you suggest me to flash and actually where I can find it and read the how to ?.
Thanks
after stock and root i was on Revolution 3.6.1 and now i am using S3N5EaY v 1.4.0 -> agree .. its very smooth - fast and looks great. but still the most important thing is : battery life.. so before i had to charge 2 times a day on hard-use.
theres no need anymore at the moment ;-)
try out by yaself..
hasan.acar said:
Hello,
As soon as I tap the wi-fi icon, it turns to an "error" state.
I ve seen some threads here, but could not be sure about the resolution. To give idea let me sum it up. My device has been brought from US and I am in europe. İt is alreasy ship s-off.
android version : 2.3.4
software number : android revolution HD 3.6.0. by mike1986
kernel version : 2.6.35.14-Sensation-faux123-v0.1.8+
baseband version : 10.42.9007.00p .....
build number : 1.73.401.2 CL161971
and this topic
http://forum.xda-developers.com/showthread.php?t=1193063&page=2
basilcallly tells to apply a signed ROM . But can you please advise which ROM would solve my wi-fi issue. and how to apply that?
Thanks in advance
Click to expand...
Click to collapse
Ello m8,
It appears your in the same boat as me, i have the wifi error too, it doesn't even turn on to be able to see networks, let alone connect to them so it's quite horrible.
What i've done:
Flashed pretty much every rom i possibly could. (old ones, new ones, no effect)
Changed the recovery to 4ext (which works great but didn't help)
Changed kernels (a lot)
Changed Radios and RIL files (a lot)
Flashed an official RUU (no effect at all)
Went back to S-ON as described in the tutorial on the main xda sensation guide, then S-OFF'd again.
I'm now back on P3D v 8 and it's running lovely but alas, still no wifi.
I've changed the back cover (the yellow connectors at the top have something to do with the wifi) Don't mess around with these as you may break something, changing the case had no effect, apparently the wifi still connects without the back cover on the phone.
I am literally at my wits end with this and i got my phone for free from my work and i was only supposed to have had it for a while (4 months) so if i say it's broke, they may take it back and i've lost the phone completely, if that wasn't the case then i would have sent it back after i'd tried everything software wise i could think of.
I'm not saying that you are in the same situation exactly but if you are then it looks bleak and i would say anything next to removing the wifi chip and replacing it would mean the wifi will never work, plus tutorials for replacing the wifi on a sensation are scarce to say the least (torque screwdrivers at the ready)
If i get it working i'll let you know how, please do the same if you get any joy.
Oh i almost forgot, another thread on another site they mention using an app called wefi, i didn't have any luck but you might.
Good luck matey Hope you have more than i did.
Hi,
I am having the same issue.
Have been running android revolution HD 3.6.5. by mike1986 and previous versions of it (2, 3) and no issues with the WiFi, as one day it just started (yesterday to be precise). I did not install anything or played with settings that could mess with the wi-fi. One day ago was working ok and the next not.
Tried the Wefi app but it did not help either.
feeling hopeless...
bk_25 said:
Hi,
I am having the same issue.
Have been running android revolution HD 3.6.5. by mike1986 and previous versions of it (2, 3) and no issues with the WiFi, as one day it just started (yesterday to be precise). I did not install anything or played with settings that could mess with the wi-fi. One day ago was working ok and the next not.
Tried the Wefi app but it did not help either.
feeling hopeless...
Click to expand...
Click to collapse
Looks like this error is more common than it would first have appeared, read my post a few up for what i've tried, i even feel like dropping it if it's something inside so as to knock it back into place, but i haven't yet Lol that's desperation.
I've got an appointment with HTC soon and i'm getting it changed, if anyone gets this sorted then let me know as i'd rather keep my phone.
dladz said:
Looks like this error is more common than it would first have appeared, read my post a few up for what i've tried, i even feel like dropping it if it's something inside so as to knock it back into place, but i haven't yet Lol that's desperation.
I've got an appointment with HTC soon and i'm getting it changed, if anyone gets this sorted then let me know as i'd rather keep my phone.
Click to expand...
Click to collapse
Hi,
I also tried all you tried and no results.
Changed the case with a friends phone but did not help either.
After a lot of reading through the forums did a logcat to see what the hack the phone is saying about this error and it seems it cannot load the driver.
If it helps smb to go deeper can post it.
Gave a thought or two about knocking it against the wall or throw it from the window but after-all, i think i can live for some time without wifi, my GPRS speed is not bad and maybe soon will be having 3G and during work time can use internet pass-through.
Worst case scenario, will sell it and get EDGE the new quad-core monster HTC will be releasing next year Q1 or early Q2.
dladz said:
Ello m8,
It appears your in the same boat as me, i have the wifi error too, it doesn't even turn on to be able to see networks, let alone connect to them so it's quite horrible.
What i've done:
Flashed pretty much every rom i possibly could. (old ones, new ones, no effect)
Changed the recovery to 4ext (which works great but didn't help)
Changed kernels (a lot)
Changed Radios and RIL files (a lot)
Flashed an official RUU (no effect at all)
Went back to S-ON as described in the tutorial on the main xda sensation guide, then S-OFF'd again.
I'm now back on P3D v 8 and it's running lovely but alas, still no wifi.
I've changed the back cover (the yellow connectors at the top have something to do with the wifi) Don't mess around with these as you may break something, changing the case had no effect, apparently the wifi still connects without the back cover on the phone.
I am literally at my wits end with this and i got my phone for free from my work and i was only supposed to have had it for a while (4 months) so if i say it's broke, they may take it back and i've lost the phone completely, if that wasn't the case then i would have sent it back after i'd tried everything software wise i could think of.
I'm not saying that you are in the same situation exactly but if you are then it looks bleak and i would say anything next to removing the wifi chip and replacing it would mean the wifi will never work, plus tutorials for replacing the wifi on a sensation are scarce to say the least (torque screwdrivers at the ready)
If i get it working i'll let you know how, please do the same if you get any joy.
Oh i almost forgot, another thread on another site they mention using an app called wefi, i didn't have any luck but you might.
Good luck matey Hope you have more than i did.
Click to expand...
Click to collapse
Dude I got the same problem and I did the same procedure so far but same results as well.
I am just wondering if you got any better results for this issue.
Thanks
Same problem, bad results...
I had the same problem. Both my Bluetooth and WiFi would get stuck on "turning on" but never did, I flashed so many ROMs and Kernels, Tried RUU's from Europe,Asia, and USA and nothing worked. SO I CALLED HTC...thankfully I was still under warranty (It's a 12 month warranty) and shipped my phone away after flashing the latest official T-Mobile RUU, Un-Rooting, and going back to S-ON. It's been a week...I called and they said THE MOTHERBOARD needed to be replaced, which I think is the "default fix" if they can't solve the issue. So hopefully in a week I'll have my phone back...Best of Luck...don't mean to be a Debby Downer but I tried EVERYTHING. Give em a call, it won't hurt to try.
I am experiencing terrible WiFi reception. This seems to be ROM independant. I flashed back to miktouch to get a stock kernel and see if it went away. I've moved from cm9.1 to aokp/jb and have the same problem.
I have never flashed a radio on this phone. In fact, its still s-on (please don't laugh, it keeps me from getting too excited and wiping my phone in a truck stop parking lot!)
The only thing I can think of is I tried overclocking it all the way to 1.7...it behaved very strangely for a minute before crashing and rebooting. So I set it back to 1.5 and went on my way.
Could this have damaged the wifi portion of the SoC or its tiny antenna connections?
Sent from my doubleshot.
Try reflashing just the Wifi modules. Click on the "Blue6IX" link in my signature & look in the 4th post, I believe, then pick the one you need. Couldn't hurt.
So, all the way back to stock, and still almost no wifi signal.
I've finally gone to the point of applying PG59IMG.zip onto a relocked phone, thereby restoring everything including the radio to absolutely stock, and still I got ****e for signal. So I guess something is broken, physically. I dread having to send this one back to T-Mobile. It's my third MT4GS in 6 months!. (The first died four hours out of the box, the second I warrantied after a couple months when the e and u keys started repeating to the degree that the hardware keyboard was useless.)
They're gonna start to hate me...and the sad thing is, It's not even the hacking that breaks the phones! (Maybe the dropping.)
Wow it's either you're an unlucky guy or mt4gs hates you
I had only a one and a second hand mt4gs which got dropped several times by the previous owner and it's been very2 stable to me since the 1st day I got it. Didn't have any hardware issues at all.
Before giving up, try installing a ROM AND fastboot flashing the boot.img from it. I'd suggest either Bulletproof or Miktouch. If I remember correctly if you are S-ON you can't write directly to the partition for the radio using the phone, you can only do it externally. So maybe somehow that partition got botched and reflashing the boot.img through fastboot may fix it. It's worth a shot.
Riyal said:
Wow it's either you're an unlucky guy or mt4gs hates you
I had only a one and a second hand mt4gs which got dropped several times by the previous owner and it's been very2 stable to me since the 1st day I got it. Didn't have any hardware issues at all.
Click to expand...
Click to collapse
Yeah, I actually drop this thing so much, I couldn't get $50 for it with all these nicks... Still works perfectly tho
iPacman
I always fastboot-flash the appropriate boot.img. this problem persists through all roms, including stock-based, aosp-based, and even relocking and flashing factory firmware as per blue's dev reference thread. Sad thing is, I love my phone so much that so far I'm just living with it. I have unlimited data, and at home I have 2 dd-wrt access points in repeater bridge mode for an 800 sq. ft. house! Everything thing else can hit both full strength. I can hit one or the other.....
Sent from my myTouch_4G_Slide using xda app-developers app
A very good day to everyone.
I have been using my HTC Sensation for a year and a half already and recently it's starting to crank up.
It started last week when I was using my phone when suddenly it just switched off by itself and no matter how I attempted to switch it back on again it would boot up to the lock screen page and baam, it shuts off again. It doesn't restarts by itself or anything, it just simply switches off and no, I am unable to switch it on again. The only time I am able to do so again is when I plug it into a power source, that is when it would finally be able to start up.
At first I thought that it wasn't something big until recently it started occuring more frequently and I noticed that it only occurs whenever I have my 3G switched on. If I'm plugged in, my phone would still be working without switching off even though I have my 3G switched on. But when I unplug it from its power source, I'll be able to use it with 3G on for a good 20-30mins or even lesser at times and there it goes shutting off by itself again. What actually got me dumbfounded is how I can be having 80% of battery power when this happens.
I have tried the using a card/paper as a wedge for the battery so that it connects better but to no avail even though I have noticed that indeed, my battery seems to have some extra allowance for it to fidget about within the confinements of the spot which is allocated for the battery. I have tried the switching the phone's data usage to GSM only as well as switching it to WCDMA only but both still didn't work. I have also done a factory wipe which didn't work, super wiped it before flashing ARHD once again which didn't work as well.
To make things worse, my phone is not covered under warranty anymore and my only last hope is that the problem lies with my phone's battery rather than the PCB board which is why I'm putting all my hope on the Anker battery which stocks would only come in next Monday which I don't wanna spend on only to find out that it's not gonna be able to save my phone from its miserable plight...
This is my phone's setup:
Android Version 4.0.3
Sense Version 3.6
Software Number - Android Revolution HD 6.8.0 XE by mik1986
Kernel Version - 3.0.16-g31a4fc7 [email protected] #1 SMP PREEMPT
Baseband Version - 11.76A.3504.00P_11.24A.3504.31_M
I'm really desperate to find a solution to this so if there's anyone of you who has faced this issue/solved this issue please enlighten me as to what I can do, any/all help would be greatly appreciated.
Try other Roms..yrs might be unstable...
Sent from my HTC Sensation XE with Beats using xda-titanium app
I've tried other ROMS already but it still force shuts itself whenever my phone's 3G is switched on. Any solutions?
seems like a radio problem ..reflash the firmware you are having or ..flash 3.33/3.32 universal firmware from kohr-ah firmware thread in sensation development section
once done ..get getril app ..open it and flash proper ril for the firmware if you not having matching ril
I've been using the 3.33 firmware for quite a while already but it's still not working. :/
Sorrowed said:
I've been using the 3.33 firmware for quite a while already but it's still not working. :/
Click to expand...
Click to collapse
Reflash it and see ...
Sent from my Nexus 7 using xda premium
ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.
I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon
It would help a lot of we had your last_kmsg file. To get the file, you can use this app: https://play.google.com/store/apps/details?id=net.solarnz.apps.lumberjack. Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it
ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried reflashing the 3.33 firmware but it keeps telling me that the installation has been aborted.
Skipjacks said:
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.
Click to expand...
Click to collapse
I've tried this method of yours as well but apparently it tells me the same thing when I try to flash the firmware. "Installation aborted" and I don't know why is this happening...
stanix.de said:
I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon
Click to expand...
Click to collapse
I've found a seller over here in my country who I'm going to be meeting tomorrow and finally test it out as to whether has it been my battery's problem or is it just my hardware being faulty. Will test it out and let you know of the end results, thanks mate!
android1234567 said:
It would help a lot of we had your last_kmsg file. To get the file, you can use this app: LumberJack(Had to change due to my account lacking the minimum requirement of 10 posts before I can post a link) Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it
Click to expand...
Click to collapse
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?
Sorrowed said:
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?
Click to expand...
Click to collapse
No, it would not.
Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.
Sorrowed said:
Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.
Click to expand...
Click to collapse
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
Definitely! Thank goodness it was just the battery otherwise there goes a great phone. Not to mention that with the anker battery it has a greater and better lifespan!
TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
My situation is identical to yours. 1,5 years old, constantly rebooting, after reboot the battery power drops to 4%. If it's connected to the power cord it works normally. Already ordered Anker battery and I'll see what happens.
If I look closely, I can see that my battery is a little bloated and not completely flat. Did anybody else noticed that?
So I guess all of this should be written on HTC Sensation FAQ page since it's not a bug, but a feature...
I recently took the plunge and upgraded my Hboot to 2.15. Followed the instructions exactly. Everything went smooth. Installed the updated Carbon and everything was ok. Then I noticed I am not able to get any signal higher than EDGE. I have done all the tricks I know of such as setting network to WCDMA only. The 3G and H will pop up but it will be grayed out. Then it drops down to EDGE again. This is the case on all roms I try. I installed the RUU for Jellybean (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2) Although I don't think it touched the Hboot, it installed fine.I am not sure if the 4G worked because I don't have it at home. But I needed a rooted rom so I reinstalled recovery and installed another rom. Sounds like a hardware problem right? Well it seems that it has happened to several people here on the forum. As well as T-Mobile forums. And it is not an outage since my wife and son get 4G fine on their phones. Any help or suggestions would be appreciated.
Ever thought of installing another Radio?
http://forum.xda-developers.com/showthread.php?t=1998270
Yeah using Temporary radio installer . But CM uses radios differently so not sure if that is a factor. I installed a lower RUU which downgraded my Hboot. Reinstalled Viper so we will see how this works. I am sure it is not a hardware problem since it happened at once when I upgraded Hboot and the same for others when they got the Jellyean update.
This is quite a common issue that a few people have faced.
Problem is, so far there seems to be no solution other than to send the phone back to HTC and get the mainboard changed (or apparently by hard bricking your phone and then unbricking it, via JTAG I would guess).
The same issue happened to me a couple weeks ago. I tried every single RUU, firmware, HBOOT, radio, you name it. But no matter what I did the phone was stuck in 2G mode and could only get 3G randomly for a few seconds when first booting up. Ultimately, my phone got hard bricked by an official RUU... go figure.
Not sure why it happens, but some have mentioned that it could be a side effect of upgrading to the Jellybean RUU while being S-OFF.
That's the weird thing. All I did was upgrade the hboot. I don't have 4g at home so I didn't even notice it right away.
Sent from my HTC One S using xda app-developers app
Same issue...
I have the same issue with my One S, after upgrading HBoot to 2.15, no more mobile data above 2G. Both TMO and HTC are saying the phone has to be sent in, but out of warranty I'd have to pay for it out of pocket.
So I agree that it seems to be the HBoot upgrade doing it. The ONLY thing I have not tried yet, is downgrading the HBoot <because of the complexity and desire to not screw this phone up even more>.
Looking for solid answers...
C.
I began posting this problem in a previous thread but am starting a new one to avoid clogging said thread.
Here are my phone details at the moment:
S-Off
SuperCID
HBoot 2.14
Radio 0-24p.32.09.06
Open-DSP-v34.1.0.45.1219
I bought the phone used off kijiji. It was stock when I got it. Rogers, Android 4.1, 3.17 firmware. I unlocked the bootloader, got SuperCID and S-Off, flashed TWRP and flashed a custom ROM - CleanROM. Things were okay for a bit.
Then I started getting random restarts and losing signal. I realized I was on 2.14 hboot so I updated to 2.15. I thought it fixed the problem but no- before long, more random reboots--though I did fix the signal issue.
So I flashed Beastmode kernal. Now, I did this without doing a full wipe - just threw it on top of CleanRom. Possibly a bad idea because everything kinda got all screwy at this point. The phone started acting really oddly--freezing a lot, restarting even more often, and sometimes the touchscreen would act up.
Next step: I tried to do a full wipe and flash a different ROM: KickDroid. Only thing was, it wouldn't flash. The installer would crash, most of the time at 30%. The phone would then restart, though it wouldn't boot (obviously), so I'd have to hold down the volume to put it into the bootloader.
Tried flashing CleanROM then - no go. It wouldn't flash either - phone would just power down.
This became a theme. The phone would just start turning itself off all the time. Even sometimes when I was doing a wipe in TWRP, the thing would just crash partway through and turn off. Somehow, this morning, I DID manage to get CleanROM to flash, but then it wouldn't boot- froze at the Google splash screen and turned off...
On timmaaa's suggestion at this point I went to an RUU and tried to get the phone back to stock. Went with the 3.18 Cingular RUU. For whatever reason, it didn't work the first time (might have been my fault - I forgot to uninstall HTC Sync Manager) but when I tried it again, it did. I was excited - phone was, hopefully, back to its old self, after all!
Booting to splash screen: freezes on the HTC logo. Turns off, randomly. AAGGHH!!!
So I try again, knowing, at this point, it's futile. The phone BEGINS to boot up. Gets to the Cingular screen and then just enters into Android - says it's going to start refreshing apps or whatever... and then it turns off.
Note that I have it sitting in the bootloader right now and it is not turning off. The bootloader itself seems to work well enough.
Even now, I tried to boot the thing up just one more time, and it again just nearly got into Android but turned off before fully loading.
I'm at a loss. It's not like I've been just randomly flashing things on here - I only used ROMs that worked for the phone. Maybe my dirty flash (is that the right terminology) of Beastmode was the problem, but I feel like it shouldn't continue to persist this long, after using an RUU. I'm wondering if perhaps it's a hardware issue at this point.
Any thoughts, ideas, suggestions, etc. are amazing... thank you.
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
timmaaa said:
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
Click to expand...
Click to collapse
Darn. Anything that can be done about that? Is it feasible or even worth it to try to replace it?
Get this - it just booted to Android, and seems to be staying there. For the time being, anyway.
Edit: never mind. lol. Turned right off again after connecting to wifi.
It all depends on whether you think it's worth the money to repair it, or just to buy a new device.
Alright. Thanks a lot for your help. I'll try to consider my options.
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
johnnyp12321 said:
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah, I'll give that a shot, too. Thanks. Though I'm not that optimistic at this point, lol.
On a related note: I have the opportunity to buy an HTC One XL with a broken screen for cheap. What do you guys think the options are for me (a) taking the mobo out of the broken one and using it in mine or (b) replacing the screen on the broken one with the working one from mine? Do you know how difficult/manageable either process is?
The phone seems to be more or less completely dead now. It will occasionally power up but can't do much beyond the bootloader. Anyone have any experience replacing motherboards on the HTC One XL? Is it possible to swap one out from a working phone? Or is it possible to use my screen to replace one on a phone with a broken screen?