So I've had this for a few days now and I've noticed it's dropped connection quite a few times, and when, IF it reconnects without rebooting, it usually gets stuck on H+.
I'm currently on OOS 10.3.0. Tried a custom ROM, same issue. Tried regarding to 9.0.11, same issue. Bought a new SIM card, same issue. I'm thinking I have to get back to the T-Mobile 9.0.16 and send this back. I'm getting sick of this. Anyone have any ideas what the issue could be?
Sorry you are having so much trouble. This won't help, but my 6T global model (not T-mo) is the best reception phone I've ever had, at least on the ATT network.
It's hard to tell whether your problem is hardware based, something to do with the T-mo to global OS transition, or something else.
I have had it a full year and have no plans to swap it any time soon. I'm stock, unrooted (first time ever), and still on Pie for now, having deferred the update until it settles in a bit.
Good luck whatever you decide to do!
Sent from my ONEPLUS A6013 using Tapatalk
Signal is still dropping!
I'm having second thoughts about this phone. Two SIM cards and several calls to my cell provider and still no fix in sight.
I'm gonna see if the Swappa seller will send me a replacement.
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Frankenscript said:
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Scott said:
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Click to expand...
Click to collapse
I did exactly that, back to T-Mobile firmware, and the issue still existed. So I returned the device.
Related
hello guys I have a nexus with one gingerbread 2.3.4 and when I use the 3G network after 2-3 minutes the phone restarts. with this bug I can not use Internet
any ideas? Thanks!
Yes. Me to.
What ROM and/or kernel combo you guys using?
I have the stock rom ota gingerbread 2.3.4, nothing changed, full stock. I recently tried miui 1.5.20 the problem is the same. may be a hardware problem?
Does the phone get hot to the touch on the back? Does the phone still reboot if you turn off 3g data and you go exclusivly Wifi?
Had the same issue with my old Nexus 1. Called HTC support and they immediately said it was a defective board. RMA'd and got refurb, but at least it does not reboot when I use 3g.
Good luck.
thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?
poltor said:
thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?
Click to expand...
Click to collapse
I didn't help for me. I tried the 5.12.00.08 radio and it suffered from the same 3g reboots. But when I disabled 3g and used Wifi, never suffered from reboots.
If the phone is still under warranty, definitely encourage you to call them. HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.
jhsiao36 said:
HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.
Click to expand...
Click to collapse
+1 They are awesome to deal with. It really makes me sad that they are starting to lock down their phones, because I won't buy a phone if I can't run custom ROMs on it.
But with the radio, I highly doubt flashing to 5.12 would help. Google released the 5.08 radio with the OTA update to Gingerbread. If 5.12 was any better, I'm sure they would've included it. There had to have been a reason they stuck with 5.08.
If you aren't afraid of losing anything, or already made backups, you could try the passimg method of giving you a completely stock install. See if the problem occurs with that as well. This would rule out software vs hardware.
No one can really solve it?
JetChung said:
No one can really solve it?
Click to expand...
Click to collapse
I really don't think it can be resolve without sending it back to HTC for a replace/repair. As I said in my previous posts, I've tried 3 different ROMs - stock, cyanogenmod 6 and 7 - all exhibit the same issue - reboot when on 3g, but perfect if on Wifi. And yes, it will reboot even on a freshly install ROM (no apps installed).
HTC knows of this issue and they will replace/repair. I got a refurb and it works perfectly - stock, cyanogenmod 6 or 7.
Sorry, probably not the answer you wanted to hear, but search on <insert your favorite search engine> and you will find that this is a fairly widespread problem.
Thank you for your answer! It does not work, had sent a factory repair.
After several tests, on Monday I sent the phone in for service. I think it's a hardware problem, maybe a bad batch of motherboards.
my S / N: HT05... and your?
I will tell you just back from assistance.
Did you ever overheat it? I believe that the N1 has a problem if you really push it that it can overheat. Once it happens once it will happen again and every time it takes less and less to cause the reboot. Eventually it reboots just with 3G.
I was running mine in the car-mount with GPS, Google Maps (3G), screen on brightest, on a hot summer day while charging ... and it rebooted. Didn't think much of it but then it started rebooting every time I used GPS and charging.
In the end it was pretty near useless ... rebooting all the time. I sent it in twice (the first time they couldn't reproduce the problem) and the second time they replaced the board. Problem solved.
Now I am very careful not to overheat it.
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
TimidRat said:
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
Click to expand...
Click to collapse
So completely unrooted/returned to stock it STILL random reboots?
If so, sounds like a hardware related issue.
Yeah went all the way back to unrooted s-on, I was starting to think it was hardware related, thanks mattykins
I can confirm that this is a hardware issue. My first EVO had the exact same problem you had, and continued to get worse and worse to the point where it would cycle 10 times before actually staying on for a little bit.
I called Sprint and told them that I thought my phone was defective, and when I explained the problem they said it was a known issue and that it would be replaced free of charge.
A friend of mine is actually dealing with this very thing right now and he said that Sprint is now shuffling people off to HTC for defective phone replacements. If you are within 1 year of buying the phone it should be free, as per the manufacturer's warranty.
I also had this happen and got it replaced. Now I'm without root but at least my phone works. It's definitely hardware related.
Sent from my PC36100 using XDA App
I had the same problem, no matter the rom or kernel, it would reboot and get stuck in bootloop. I finally gave in and went to sprint, turned out it was something with the hardware that would heat up my battery and then when it got to a certain temperature it would cause it to reboot. Definitely take it into sprint.
Sent from my PC36100 using XDA App
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
TimidRat said:
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
Click to expand...
Click to collapse
Try anyway.
Technically you would win legally because the crack has nothing to do with the issue you're having thus the warranty is valid.
(Although I guess they could claim you must have dropped it and that could have damaged something internal)
But the worst case scenario is they say you have to pay the $100 to get a new one and if you don't you still have your phone.
The best case, they fix or replace it.
Either way, its worth a shot.
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
jcip17 said:
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
Click to expand...
Click to collapse
Thanks man. You're one of the people who make XDA such a cool place. It ain't like this is goodbye forever. I'll be in here fairly often. Tapatalk keeps me notified of what goes on. See you later.
Sent from my SCH-I535 using Tapatalk
Sorry to hear you're leaving. You've been a great help to a lot of us. I share your feelings toward Verizon, they are just too big to care. So go on.... have some fun with the new toy....there's so much development over there... I'm actually over in the note4 snapdragon side more recently because I'm running all other than Verizon MM stuff. Anyways thanks Stuey for your contributions and help!
Sent from my SM-N920V using XDA-Developers mobile app
stueycaster said:
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Click to expand...
Click to collapse
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Nice.
Sent from my SM-N920V using XDA-Developers mobile app
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
ryanbg said:
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
Click to expand...
Click to collapse
Isn't that going to overwrite the Dev Ed bootloader? I guess that's ok though because it's useless as a Developer Edition anyway right? And then I can do the unlock procedure.
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
stueycaster said:
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
Click to expand...
Click to collapse
We'll get DE back after you are stable. Uninstall Verizon Software Repair Assistant and Kies if you have it. To me, it looks like a USB/Driver/Software conflict going on preventing a successful flash. Try a different computer, and a different USB cable. Something is interrupting the write process.
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
stueycaster said:
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
Click to expand...
Click to collapse
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Dark_Plasma said:
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Click to expand...
Click to collapse
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Sorry to hear that....hoped you could revive it. For sure these things get blistering hot! I've been flashing like crazy this past week thinking my phone is cookin! So I know what your saying could be the culprit. Still hoping you find a way!
Sent from my SM-N920V using XDA-Developers mobile app
Very odd, I do a complete clean flash on all aosp roms available for the H918 and every single one won't allow mobile data to work. I go back to a stock rom and its fine. Has anyone encountered this? Almost as if T-Mobile locked aosp on me. Strange!
I've got the same issue on Verizon. I can get it to work for a bit but eventually quits until I do a network reset. Can't seem to find an answer in any thread and it's either always overlooked or ignored when someone mentions the problem.
Sent from my LG-VS995 using XDA-Developers Legacy app
chachh said:
I've got the same issue on Verizon. I can get it to work for a bit but eventually quits until I do a network reset. Can't seem to find an answer in any thread and it's either always overlooked or ignored when someone mentions the problem.
Click to expand...
Click to collapse
Yep I hear ya. I went back to complete stock. I had to kdz twice to get signal back on T-Mobile. I'm reluctant to root again. Believe it or not even with my phone bloated again I guess better battery life. I think routing now these days is too much hype. Fun though. But still. The thread for v20 is not much at all. And it seems like many are abandoning it and going back to stock. Not much of updates or anything. Only thing I liked was the sound mods.
Can someone link me to some instructions that involves Either rooting my note 4 that involves flashing the modems or a stock root that will also flash all modems? Can you also recommend a ROM that you have no had any issues with for at least a year?
I'm not sure if my board is bad or if it just needs to be reflashed. My girlfriend purchased the phone and broke the screen. So before I buy a new screen for it I would like to see if the board is still good.
Board's good (if it runs, you're golden)... and I recently had this problem, too... but mine was due to a system error in whatever ROM I running at the time. Sounds like you're on stock, though? I had that issue when I was on stock (within the first like 3 days having the device). The fix was getting ahold of Sprint on chat, and making sure they had the correct SIM ICC. They fixed it, refreshed, my phone rebooted and ran thru HFA and I had the LTE. Hopefully that's all it is. As for the other questions... umm, flashing TWRP thru odin gets you in the right direction for rooting. And as far as the ROMs go, anything by db_txs_db will work. Beyond that, starr53 ROMs work extremely well. Sorry if I ramble or speak in sentence fragments. Sometimes it happens. Best of luck and lemme know how it goes!
As far as I know firmwares only have one modern and if you have an SM-N910P that is not on the latest DQ15 update then it definitely worth fixing. Good luck