Related
Have been reading all the forums and had used the info here to put a custom ROM on my T-Mobile Wing. Unfortunately my Wing is now suffering a hardware problem and has to go back for a warranty replacement. This could obviously be a problem if it has a non-standard ROM on it. Because of this, I went ahead and grabbed the RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship.exe file via the threads and attempted to reflash my phone.
I am running the flash attempt from a physical Windows XP system. My phone is fully charged. I have an active partnership set up with the phone and active via ActiveSync. I start the flash process and the phone reboots into bootloader mode as expected. The flash process gets to 1% then the phone reboots into regular mode again and the RUU reports that the flash failed.
Am I missing something?
Update: apparently I was missing something. I had read the thread indicating the phone reboots at 1% and 30% (though mine only rebooted at 1%), but I assumed it would go back into the boot loader automatically which it didn't. On a hunch I tried forcing it into the boot loader and the RUU continued. Weird.
Have you HardSPLed your phone before? If you have, you have to bypass the SPL... Rumor goes, flashing the stock RUU WITH USPL will do this for you. I haven't tried it so I don't know if this will work or brick the device.
I had my phone picked up for warranty this very day. It was running Itje's latest ROM before the 6.1 update, but it totally died on my the other day. So now I'm hoping they won't mind too much about the hard-spl ing and the flashing and the overclocking *cough*
Good luck restoring your phone though. Maybe they won't care, I'm hoping for that
I basically took ivanmmj's advice and wrote a lil guide, I hope it gets sticky'd. http://forum.xda-developers.com/showthread.php?t=364543
DaMyth said:
I basically took ivanmmj's advice and wrote a lil guide, I hope it gets sticky'd. http://forum.xda-developers.com/showthread.php?t=364543
Click to expand...
Click to collapse
Glad to hear it worked. ^_^ I think that's the second account I hear of it working, so it must be something that DOES work.
Not to raise the dead but good thing I found this thread, worked or me too. Anyone know anything about the warranty replacements tmobile sends out? I'm assuming a refurbished model but anyone know the type o condition they are in?
The model that I got as a replacement, oh so long ago, has been working like a champ since I got it. It looked brand new, but then again, the original had problems not too long after I first got it, when the Wing was still a pretty new device.
Thats good to know, should only have to last me a month or two seeing how tmobile in their infinate wisdom lost the cell tower near my house a few months ago and contract is done on the 29th.... hello tilt!! (or touch pro )
So I was hoping that anyone here could shed some light on an issue that one of my friends who just bought a Nexus is having. His N1 is bone stock, and is an AT&T model. Every once in a while, completely out of the blue, the screen will turn black and restart, but then enter an infinite boot loop, where the only solution is to remove the power adapter and battery.
In trying to pinpoint the problem, we have noticed:
-It really only tends to happen when the device is plugged in.
-It's not related to the battery, charger, or microSD (since we tried mine to no avail)
-It's probably not kernel, ROM, or radio related (we let it do the OTA 2.2 update, and the crashes were still present)
I don't understand why it only happens when the phone is plugged in. The phone isn't hot to the touch, so I doubt that the battery is over heating.
Any help will be greatly appreciated. Thanks!
PS. I tried searching, but the only mention of boot loops I could find were on custom ROMs and Kernels...
Exact Same problem and Phone here!!!
Just got it today too! Please any suggestions would be nice! Want to root this phone but to afraid there is a hardware issue!
My friend ended up calling HTC and they asked him to return it, which he did, for a full refund. Ironically, he ended up getting a Samsung Galaxy S (ATT Captivate variety). Nexus one, although less powerful, is more sleek in my book...
I've got almost the exact same problem on an AT&T N1 running Froyo FRF91, the two differences I have are that the phone does feel hot to the touch, and that it never happened on 2.1. If anybody has some info on this it would be greatly appreciated, but I will be calling HTC/Google in the next few days to see if we can resolve this problem.
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
jpav80 said:
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
Click to expand...
Click to collapse
What can I do if it is unlocked? Any chance they still help you out? Or just forget it?
I don't think it would hurt to just give them a call. I have read some forums where people have sent unlocked phones in for repair and then got them back fixed and re-locked. It is worth a shot instead of having a faulty phone. I did the exchange option and it did take me a while to get my replacement phone, but that was due to HTC moving their repair facility according to the tech. The techs that I have talked to have been helpful. If I thought a tech was no good I just hang up and try again with a different person.
Jay
I have been having pretty much the exact same issues.
I have an AT&T unlocked/rooted N1.
Random reboots frequently when the phone is charging via plug or USB for seemingly no reason. I thought it may have been an app, or combination of apps, so I tried a combination of different steps to try and find a solution.
Wiped data/cache
Wiped data/cache & fix apk permissions (Amon Ra 1.7.0.1)
Wiped data/cache and flashed the current ROM I was using again
Wiped data/cache and flashed different ROMs (both 2.1 and 2.2 w/proper radio) including MCR r16-21, PhoenRom, LeoFroYo, Cyanogen 5/6 RC1 and even tried intersectRaven's Kernel's
Reformated the SDCard both via gparted from Ubuntu live cd and Amon Ra's recovery 1.7.0.1
Swapped out the SDCard thinking possibly a bad block
And finally re-flashed back to shipping stock 2.1 and stock recovery w/successful OTA 2.2 install
All steps I was able to get my N1 to randomly reboot plugged in or not. I even had it sitting on my desk at work unused for 30-40 min (running CM RC1) and it rebooted with no user input what-so-ever. It happens more often while plugged in but was not limited to charging state.
All that said, I finally called support, took about 30 min total to arrange a replacement. This included a factory reset while on the phone with the tech and I was able to get the phone to reboot within a few minutes of first boot.
Take it for what it is worth, but I am positive that this is a hardware issue in my case. Just hope my replacement goes without penalty (unlocked and all) and that my new N1 doesn't have the same issues.
So My phone is most certainly bricked this morning. I saw a few posts on the topic, as well as one that was locked. Seems that there a re more than 5 of us, can a mod by chance merge the posts, so we can start troubleshooting the issue, and keep it from happening in the future. I will describe what I have done, and maybe it will help someone come up with an idea of what binds us all to our bricks.
Once upon a time in a galaxy far far away I was a flashoholic:
So I get my black one in the mail, and start playing in the forums, seeing what's what, and I go about trying to moonshine, firmware doesn't match so it doesn't work, get her rooted, s-off with revone, and flash a few sense based roms. No problems. Try the cm rom listed in the first post of the 10.1 link, no gps, weak signal, back to sense. Finally get a few of the threads completely read, and find rc2 of 10.1 flash(using twrp 2.6.1.0, and I do all the wipes and format data, and factory reset before sideloading my roms) get it up and running, gps works, find the build.prop line to edit to get it to stick to sprint to work, and away we go, rom is good, problems are small, phone working exactly llike it's supposed to. I did play with trickster mod here and there, but didn't much care for the program. So was playing in original development, and saw that the twrp forum had new input, so I go into it, and see a new twrp available (2.6.3.0) dl, flash the .img, reboot recovery, wipe everything, sideload 10.1 rc2 again and gapps. Almost immediately noticed the temp on the phone was very warm, almost hot, and that was without being on the charger. It was bedtime, so plugged phone in, go to bed, get up look at phone, and its at 50 percent on the dot, and no red light. Houston we have a problem. So I start researching how to ruu back to stock, and just to see if it was the recovery, I flashed cwm, didn't like it, and then reflashed the older twrp, problem persists, well I really didn't want my phone to reach 0 percent battery, so the race was on, set phone on ac vent and charge it, take it off charger, it would drop 20 to 30 percent in five to ten minutes. Get ruu downloaded, can't get it to run, troubleshooting that, my battery plugged in is down to 6 percent and the speakers are hissing at me, when I see the problem, plug it in to the laptop, run ruu, watching phone, watching progress, complete!!! yes reboot phone, log in to gmail, get message about phone using more power than it's receiving (plugged in to wall again) and boom shutdown. So now I'm thinking to myself hrmm good or bad, red light says charging, go smoke a few cigs comeback in phone boots, and is charging, no errors, everything is running like it is supposed to, everything works. It's still very warm though for not running much of nothing, leave it in the cold air, and she charges up to 100% (albeit slowly took most of the day) unplug her, go to sleep, and about 3 hours later I heard the low battery warning, and woke up to my nice black brick. No red light, no pressing buttons for x amount of time, she is most certainly dead.
Hopefully this can help us figure out what is causing the bricks.
And only 3 more hours to the sprint store opens :victory: that's bound to be fun
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
phatmanxxl said:
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
Click to expand...
Click to collapse
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
I don't know, I love Slim ROMs but if it happens again Sprint will start asking questions and might investigate the phone, plus I got the last red phone in stock
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
How many brick threads have you seen in here on Sense roms?
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
Including folks that flashed gsm roms? Zero
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
i wont even flash an aosp rom on this phone i have seen a few people brick while on aosp.. and the dude i got my one from he bricked his first one running an aosp rom.. he said he rooted it flash an aosp rom.. was fine for a week or so the while listing to music on the phone it died brick.. im not saying its deff aosp roms but i have seen and heard enough where im not going to try it... lol im good with my sense:good:
I wonder what's the difference between GE ones and Sense ones.
raptoro07 said:
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
Click to expand...
Click to collapse
I guess you could summarize it like that, but I thought that I stated I knew it was going to die, shortly after I upgraded my recovery. All flashing after that was an attempt to troubleshoot/save the beast if at all possible.
Well I know what's causing the bricks.
So i figured out in part at least what is indeed causing the bricks. It was my first guess, but I messaged a couple of kernel devs, and the information they gave me led me to believe my first assumption was wrong. Apparently it was not. i am not sure if it's an aosp thing, a twrp (was using 2.6.1.0) when I found out, or just a really nice user error experienced by a handful of people. But regardless, either the kernel, and or some of it's settings are not being wiped in twrp to include an advanced wipe of all check boxes besides usbotg, a format data, and then a factory reset wipe. So when kernel or settings interact with new kernel/rom that you install and they don't play nice together, you get your nice little brick. Oh but how do I come across such preposterous conclusions you ask yourself? So I payed my 50 bucks, got my new phone, put my go to rom on it, and play away; lo and behold a stable 10.1 cm comes out. Can't resist, must flash, disapointing to see in the stable release the first thing I have to do is edit build prop to get sprint signal(it is a sprint rom yes?) Still liking the rom for what it is, probably my favorite, except Trebuchet is laggy as S**t(ping pongs kernels alleviate this, but his kernels are for 10.2). So in an attempt to fig the lag, i play with different settings and whatnot that I found laying around xda here and there. nothing is helping with the stutter I see on the home screen. So I go to the main One thread, and look around for kernels, I find one, don't figure it will work, but figure I'll just wipe if it does bad things to my phone; and it did. 8 boot loops later what do I do? Wipe everything as mentioned above, and sideload 10.1 stable, guess what happens on reboot? That's right bootloops. So some how the kernel or some of it or its settings at least are not going away as they should on a clean install, and that I'm sure is what is causing the bricks.
Ty,
I'll be here all night
You sure do keep a really good attitude through it all though. We've all been there but you are purposely putting yourself and wallet through it over and over to find the culprit. I for one appreciate it.
D
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
placebored said:
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
Click to expand...
Click to collapse
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
clsA said:
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
Click to expand...
Click to collapse
Thanks clsA. I'm surprised by that since in my experience a broken motherboard results in a much more substantial and obvious failure, but I guess the point is moot if I can't get into recovery to try anything else.
There isn't much of a market for new motherboards, and my experience with eBay sellers for oem components on this device makes me think trying to replace it there would be a fool's errand. I guess I could buy a used M7, but on the other hand the damn thing has basically been nothing but problems. The defective camera turned to garbage in under a year and one drop killed it? Unless anyone has another suggestion, I guess it's time to cut my losses on this thing. I may feel a sentimental attachment because I've nursed it along so much, but damn... a phone is a phone and this one has been a LOT more problematic than any other one I've had.
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
placebored said:
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
Click to expand...
Click to collapse
That's great, I'm glad you were able to fix it
Alright, I have an issue that's been getting ridiclious the past few months. Ironically it all started when trump took office, but that's another subject....
On any rom besides a sense based rom, and i've tried alot, AICP, CM, Lineage, candy, etc etc. I'll have random reboots when getting text messages, or random reboots when trying to send a text message. I've tried all these roms wiped, with and without gapps, and i end up with the exact same result. Straight up random reboots.
The moment i wipe and restore the stock sense i imaged immeditately unlocking, no issues. I flash badboyz, no issues. I've been experimenting the past few months, and i can honestly say it only happens on non-sense roms. I thought it was because of gapps. So i ran CM11, which has been flawless since 2014, and without gapps, after a fresh flash and boot, the 1st text message i receive, instant hard reset.
The phone was s-on when i bought it, i took the latest OTA to grab carrier and OEM software and radios, then i did only the bootloader unlock, flashed TWRP, imaged my system. that was back in 2014 when the phone was first released. Since unlocking i've been running cm11 flawlessly for several months, at times a week or so of uptime, and i use my phone heavily.
Now it's to the point, when i flash a clean CM11, no gapps, just sitting on the table with the tethering on, either USB or wifi, it'll reboot. Sometimes itll get into a reboot loop and it'll take up to 10x of hard resets until it gets android fully loaded (mind you no gapps, no 3rd party, just the rom itself) before it's usable, that's if it doesn't run itself dead with the bootloops.
What's blowing my mind, if it's hardware, then why no issues on sense? Why only issues on non sense, and why now and not before? and the differences are all i can think of is software from: htc, sprint, google
When those 3 are removed, stability issues. but why now and all of a sudden?
anyone want me to supply something from adb? this has truly got me interested. I'm willing to copy and paste and upload some info. I'm really wondering what this issue is.
Thanks!
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
swerff said:
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Here's what I would say:
Because non-Sense ROMs don't have the same drivers, HTC developers, etc, they tend to be less stable as a group. The developers work hard to mitigate that, but the random reboots are the hardest for them to figure out. If you go through non-Sense ROM threads for years, you'll see that common complaint.
Now, as for CM11 being solid and now it's not, my guess is that updated firmware, radios, etc caused it. CM11 is quite a few years old and was written under older radios.
When the m7 was my daily driver, I had good luck on these three ROMs. They had the occasional reboot, but it was about once a week at most and rebooted right back in.
Resurrection Remix
PAC ROM
NusenSeven (Sense based from the m9)
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
swerff said:
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Misread and thought you updated radios recently. Not sure how replacing the battery would help, but you never know.
I had been running the three ROMs mentioned above with minimal issues when I used the m7 as my daily driver. I had run the latest RUU (see development section) to update to the latest radios, firmware, etc first. As I recall, all three were good. NusenSeven being stock based was most stable, but the others were good too.
swerff said:
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Worth a shot, but your instability seems relatively reproducible. Personally never done it. So I'm not sure that would help, but like I said before, you never know.
Well, tonight I'm going to replace the battery.
If that diesnt help, going to relock and ruu just to make sure, unlock and flash the same zip I've been using for years.
If there's still issues, something is going down regarding big brother not enjoying his stuff on my phone.
That's my take and opinion.
Sent from my One using Tapatalk
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
swerff said:
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Great! I'm glad it worked. It is odd, but what you say makes sense. Maybe the Sense ROM had something optimized in the kernel or ROM that the non-Sense ones don't. That's why I love this site; I learn something new everyday. Thanks for putting the results of your work in the thread for future members who may have the same problem.:highfive:
Well, update
It eventually got back into its old habits of randomly rebooting after ending phone calls or sending /receiving messages.
Soon after that it had issues if not coming out of airplane mode, which would require a hard restart, soft restarts were unsuccessful.
About week ago my son wanted to play on it, so i enabled airplane mode so he wouldn't accidentally call anyone.
Enabled airplane mode.
Handed phone to him.
Within 30 seconds I took it back, and in this time frame all he was doing was holding it/touching screen.
The phone now endlessly reboots to the initial HTC logo for maybe 5 seconds, goes black, and repeats. It will do this until the battery is dead.
Plugging in charger results in no battery charge state, screen or LED. After several moments of being plugged in with no signs of life, it'll light up to HTC screen, only 5 seconds later to go black and repeat, endlessly.
Holding power + volume down I can access the bootloader, which before it resets again I can pick recovery option.
It'll then reboot into HTC screen, saying entering recovery up at the top, but never doing so, and continue with boot loops.
The power button is not stuck, as holding only volume down will not encourage bootloader initialization.
Ideas?
swerff said:
Ideas?
Click to expand...
Click to collapse
It seems to have gone beyond the Sense working but non-Sense not working issues it started with. At this point, I'd probably try to RUU the thing back to stock and see if that fixes it. If not, I'd venture something hardware related. I wrote a guide on how to do this mainly because I kept forgetting all the steps. Hope it helps.
https://forum.xda-developers.com/sp...de-reset-phone-using-ruu-htcfastboot-t2876110
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
swerff said:
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
That's too bad. I don't know what to tell you my friend. I saw you could access the bootloader and select recovery, but if it's not stable enough to stay in fastboot, then that's beyond my knowledge capability. At this point, if it were me, I'd buy a new device or take it to a repair shop.
I'm investigating surface mount memory readers and the like.
I'm hoping to solder up something to pull the memory in binary.
The phone wasn't encrypted. There's a handful of photos I'd love to recover. Not having an external sdcard is stupid.
Sent from my One using Tapatalk