I was carrying my phone and i dropped it, and now it won't turn on. Well i plug it to my computer and then i pressed the on button and it turns on but it gets to windows screen and reboots and does this over and over. BUT if i unplug it doesnt turn on anymore.
I've flashed it a couple of time but the last time i flashed it was back to the stock alltel rom because I wanted picture messages to come through.
I've reflashed it again and it goes through but when you unplug it. It turns off again.
So, when did you drop it? Like, right after you flashed a gsm rom onto a cdma phone (or vice-versa, not sure what alltel is, though I suspect it's cdma). Is dropping the phone even relevant to the story, or is flashing the cause of the re-boot cycles? You need to be a little more clear. By that, I mean, what did you do immediately before the re-booting started? Flash, or drop?
I suspect you need to go back to the stock rom and you'll be good to go. If dropping is the cause, go back to stock, and if it's still broken, send it in for repairs/warranty/insurance or whatever.
Farmer Ted said:
So, when did you drop it? Like, right after you flashed a gsm rom onto a cdma phone (or vice-versa, not sure what alltel is, though I suspect it's cdma). Is dropping the phone even relevant to the story, or is flashing the cause of the re-boot cycles? You need to be a little more clear. By that, I mean, what did you do immediately before the re-booting started? Flash, or drop?
I suspect you need to go back to the stock rom and you'll be good to go. If dropping is the cause, go back to stock, and if it's still broken, send it in for repairs/warranty/insurance or whatever.
Click to expand...
Click to collapse
Yup, Alltel IS CDMA.....
If it works while connected to the computer then you might have broken the battery-phone connection...or who knows. I'd definitely send it back if it is tstill in warranty.
Good luck.
Okay, i flashed it like 6 hours earlier to droping it, no i don't have warranty on it.
so i flashed it with back to the stock rom
then i dropped it 6 hours later and it keeps rebooting only when i have it plugged in but it wont turn on without it being plug.
You haven't answered whether or not you flashed a GSM ROM to your CDMA phone.
Can you see physical damage?
Oh, idk why but i typed something wrong, i've had this rom forum.ppcgeeks.com/showthread.php?t=42741 the alltel one since yesterday, and i dropped it today, After i dropped it put the battery back on but it didn't start up so i pluged it to my comp and it started up so i did hard reset while i had it plugged up to the computer and it didn't fix it.
*NOTE it can only start up (well try to start up but reboots) when i have the cord pluged up as soon as i take it out it wont start at all.*
So, i figured since it will only start up when i have a power source and reboots it might have a booting problem. So i reflashed it with the same rom i posted a link to..
I still have the same problem
Also i have no warranty bought phone from a friend.
*Also no damage just battery poped out when it got dropped*
Morbis0688 said:
Oh, idk why but i typed something wrong, i've had this rom forum.ppcgeeks.com/showthread.php?t=42741 the alltel one since yesterday, and i dropped it today, After i dropped it put the battery back on but it didn't start up so i pluged it to my comp and it started up so i did hard reset while i had it plugged up to the computer and it didn't fix it.
*NOTE it can only start up (well try to start up but reboots) when i have the cord pluged up as soon as i take it out it wont start at all.*
So, i figured since it will only start up when i have a power source and reboots it might have a booting problem. So i reflashed it with the same rom i posted a link to..
I still have the same problem
Also i have no warranty bought phone from a friend.
*Also no damage just battery poped out when it got dropped*
Click to expand...
Click to collapse
So before you dropped it it was working fine on the stock Alltel ROM?
If that's the case, its probably physical damage, although the constant restarts would indicate a software issue.
Make sure your battery is getting a good connection.
It may just be a damaged battery.
Yes, it was working fine, I got a spare battery at home so i'm gonna try that, but ya the restarting make me think a software problem cause its getting power really from the computer port.
Ever since upgrading to AT&T 2.2, I have a had an issue that on every other reboot, the phone radio does not turn on. I am not getting a SIM error, or any other error indication, nor does the phone go to airplane mode (bluetooth and wifi work). If I check phone settings, I get phone # unknown and no phone signal. Once I shut the phone down and turn it back on again, phone service is back.
I'd suspect a SIM issue, but this did not happen on 2.1. Could this be a bad flash (I could not get Kies Mini to push the firmware, I had to install via Odin)? Has anyone else seen this kind of flakiness?
Bump
Is anyone else seeing intermittent issues of the phone thinking it doesn't have a SIM installed? The good news is that I have not had two reboots in a row with this problem, the bad news is that I do see this on nearly 50% of boots.
I dont have the problem, if it does happens it only happens like once a week for me, it usually fixes it by going into airplane and back to regular
ryanmahan said:
I dont have the problem, if it does happens it only happens like once a week for me, it usually fixes it by going into airplane and back to regular
Click to expand...
Click to collapse
I tried that. On my phone, that does not remedy the situation. The SIM itself has not moved since the update (I can't remember if I pulled it when I ran the upgrade), so I don't think it's a loose contact.
att can fix
Bring the SIM and phone into ATT, they will fix it for you there, hopefully for free, that could work, just unroot before and unflash if you did, then say you have SIM problems and then tell them that you had it in during the update, sometimes that causes problems
I have this same issue. Yesterday after about 5 reboots the phone would not pick up any signal... at times and after several minutes, some signal would show up and then disappear again... After about the fifth time, I turned off WiFi, because it had been on the whole time and that fixed the problem. Signal came back after a while and was stable. Turning WiFi back on did not bring back the problem. I guess Froyo just does not like the WiFi being on when booting the phone. Hopefully this can help others fix this same issue when encountered.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well i am not so convinced it is the radio so much as the hardware, my original tbolt would reboot every 5 min or so no matter what. so read the forums,researched the web,talked to s friend at htc,verizon and vodafon. then i rooted it flashed different roms and radios nothing helped,along comes the official update do i reroot the phone and restore it the way i got it,set it up and let it do the ota update by itself,after 3 tries it finally took it,then a day or so later it froze so i pulled the battery booted back up once it was running started all over with the reboots every 5 min,the all at once it started to reboot all the time ,htc and verizon both said it is a known hardware failure and i got this bolt the same day ,rooted flashed,reflashed ran it to hell and back and not one reboot other than by drastic mistakes. both phones have the same chip so i would think its not a different chip but a defective series of chips, in closing i suffered the reboot problem on in the gb radio but with stock rooted ota setup.
I talked to them about it today "Verizon / HTC" and they said to do a factory reset that it fixes it, and it did. They said that it's the radio interacting with their cell towers and something glitches and it reboots. They're working on fixing the issue right now, HTC that is.
But yeah, my wifes stock phone has stopped rebooting now. We just received the phone Thursday.
Sorry for the length, but its a complex issue, it least its a bit entertaining ... if your not me.
My Sensation took a random fall last week while charging, It just happened to be that it landed on the usb cord and damaged the port. To give you some idea of the extent of the damage the plastic piece internally that has the pins was bent/broken. It obviously would not charge after this event.
I have a second battery and external charger so it was little more then a minor inconvenience to swap batteries twice a day for a few days until I could look into getting the phone replaced/repaired. For the next 4 days the phone worked flawlessly. I took the phone into a reputable repair location and they replaced the MicroUSB port for $45. Since then however I have had a series of issues that are randomly triggered as described below in point form.
1> After getting the phone back I used it for the rest of the day and then went to charge it. It charged for 5-15 minutes, then would stop charging. If I unplugged it and plugged it back in, it would charge for another 5-15 minutes, and stop charging again. After the second cycle I started trying various other charging parts: I tried a different HTC branded cable, different HTC branded wall adapter, a non-HTC branded charger (that worked fine previously), Tried charging with the USB port of my computer, tried power cycling the phone multiple times. None of these had any effect on the charging cycle so I swapped batteries and charged externally. When that battery died I tried charging with my regular HTC charger again and it completed the charge cycle with no issues, Since then I've swapped batteries again and it charged that battery with no issues, so definitely not a battery issue. The non-charging issue has happened a few other times as well, details in the following points.
2> The next day the went to sync my contacts and offload some SD card content. When I connected the phone the computer detected the phone and I chose to sync, its like it attempted to sync a few times before actually completing the sync, the software would say syncing, for a few seconds then disconnect, syncing then disconnected, after 3-4 cycles it stayed connected for a minute or so and the sync completed. Then as soon as it finished the software said disconnected and it hasn't be able to reconnect since. Now when I plug it in, it starts charging but no dialog box prompts for the usual (mass storage, charge only, USB tethering, etc). Computer sees it as a unrecognized USB device. Obviously I have rebooted both the phone and computer multiple times, still no data connectivity. I also tried a different computer that my other HTC device gets synced to and it also does not cause the phone to prompt for what type of connection.
Later that day I turned the screen on to find it saying no SD card was installed, weird... I rebooted, still no SD card found. So I shut it off, removed the SD card, blew it out with compressed air, reinserted and its been fine since.
3> The next day I noticed the phone died rather quickly, I was on the road so I swapped batteries and then I figured out why, after it finished booting up and I turned the screen off a few seconds later the screen turned back on and it waited at the lock screen, I would turn it off, it would turn back on, we had this argument for a solid 15 minutes off and on, off and on I also tried multiple reboots with no effect. Eventually it stayed off started working like normal. it was random times when it would turn on, sometimes 2 seconds sometimes a minute or more. When I would unlock the screen it would be at one of two places, either at the HTC locations app telling me to turn on GPS or with a prompt asking me to choose an action: either Dock or TuneIn (not sure how these are remotely related apps)
4> I keep my auto-rotate off but that night I was browsing with maxton (using the phone in portrait mode, but laying in bed so the phone is in landscape) and it kept rotating. I checked the setting and sure enough auto-rotate was off, but it insisted on rotating. I toggled auto-rotate on then off again, still kept rotating. Frustrated I plugged phone it, and went to sleep, it charged and in the morning it was not auto-rotating, acted as if nothing had happened.
5> SINCE THAT: the random screen turning on issues, charging issues, and rotation issues have each reoccurred a couple times sometimes independently sometimes in combination with each other.
FOR EXAMPLE:
Today the phone worked fine all day, I played games, surfed internet, sent email, charged it, talked on it, etc. Then tonight while talking it started randomly turning off/on, loading Locations, or asking about dock/Tunein, meanwhile jumping in and out of rotate because I was laying down (auto-rotate still off ). This caused it to jump in and out of speaker mode and the other party I was talking too got a real earfull of my feelings for the phone. I eventually left it on speakerphone in the dock mode and finished the call. 5 minutes later the call was done and the phone acted as though nothing was wrong. (At this point I felt like the phone deserved to be the star in a Steven King novel)
A couple hours later I went to charge it and it was doing its charge for 5 minutes, stop. Unplug/plug-in and charge for 5 more mins etc. This argument went on 4-5 times and it still charging now about an hour later.
So here is the question: Do you think this is something to do with the replaced USB port or the process of replacing it, or is it perhaps a corrupt OS? Keeping in mind that it was fine after the fall, no issues until the port repair. I'm running ARHD 6.0.4, I wanted to upgrade to 6.0.8 to rule out OS before going back to the service store, but Mike's link for the firmware upgrade is still down so I'm stuck for the moment, but I don't want to wait too long before going back to them. (if someone has the 3.33 ARHD firmware/radio please PM me I have ad ftp server you can send it to)
Reasons why I suspect/hope possible corrupt OS:
All the issues seem to be potentially software related.
I removed the SD card and SIM when they had the phone for repair, they most likely booted it up without the SD, perhaps there was some system files that corrupted when SD wasn't present?
Prior to the fall the phone had a couple occurrences of software issues relating to the SD card. twice in the last 3-4 months I lost ability to read the SD card but each time it was rectified with a reboot. Also ever since flashing ARHD 6.0.4 I I have had no bluetooth functionality. I could turn it on, but had no control panel to search for other devices or make the device discoverable, so there was definitely a software issues relating to that, I never used BT so it wasn't a big issue.
I'd really appreciate some thoughts, or 3.33ARHD firmware
Thanks in advance
Zenon
zenon1823 said:
Sorry for the length, but its a complex issue, it least its a bit entertaining ... if your not me.
My Sensation took a random fall last week while charging, It just happened to be that it landed on the usb cord and damaged the port. To give you some idea of the extent of the damage the plastic piece internally that has the pins was bent/broken. It obviously would not charge after this event.
I have a second battery and external charger so it was little more then a minor inconvenience to swap batteries twice a day for a few days until I could look into getting the phone replaced/repaired. For the next 4 days the phone worked flawlessly. I took the phone into a reputable repair location and they replaced the MicroUSB port for $45. Since then however I have had a series of issues that are randomly triggered as described below in point form.
1> After getting the phone back I used it for the rest of the day and then went to charge it. It charged for 5-15 minutes, then would stop charging. If I unplugged it and plugged it back in, it would charge for another 5-15 minutes, and stop charging again. After the second cycle I started trying various other charging parts: I tried a different HTC branded cable, different HTC branded wall adapter, a non-HTC branded charger (that worked fine previously), Tried charging with the USB port of my computer, tried power cycling the phone multiple times. None of these had any effect on the charging cycle so I swapped batteries and charged externally. When that battery died I tried charging with my regular HTC charger again and it completed the charge cycle with no issues, Since then I've swapped batteries again and it charged that battery with no issues, so definitely not a battery issue. The non-charging issue has happened a few other times as well, details in the following points.
2> The next day the went to sync my contacts and offload some SD card content. When I connected the phone the computer detected the phone and I chose to sync, its like it attempted to sync a few times before actually completing the sync, the software would say syncing, for a few seconds then disconnect, syncing then disconnected, after 3-4 cycles it stayed connected for a minute or so and the sync completed. Then as soon as it finished the software said disconnected and it hasn't be able to reconnect since. Now when I plug it in, it starts charging but no dialog box prompts for the usual (mass storage, charge only, USB tethering, etc). Computer sees it as a unrecognized USB device. Obviously I have rebooted both the phone and computer multiple times, still no data connectivity. I also tried a different computer that my other HTC device gets synced to and it also does not cause the phone to prompt for what type of connection.
Later that day I turned the screen on to find it saying no SD card was installed, weird... I rebooted, still no SD card found. So I shut it off, removed the SD card, blew it out with compressed air, reinserted and its been fine since.
3> The next day I noticed the phone died rather quickly, I was on the road so I swapped batteries and then I figured out why, after it finished booting up and I turned the screen off a few seconds later the screen turned back on and it waited at the lock screen, I would turn it off, it would turn back on, we had this argument for a solid 15 minutes off and on, off and on I also tried multiple reboots with no effect. Eventually it stayed off started working like normal. it was random times when it would turn on, sometimes 2 seconds sometimes a minute or more. When I would unlock the screen it would be at one of two places, either at the HTC locations app telling me to turn on GPS or with a prompt asking me to choose an action: either Dock or TuneIn (not sure how these are remotely related apps)
4> I keep my auto-rotate off but that night I was browsing with maxton (using the phone in portrait mode, but laying in bed so the phone is in landscape) and it kept rotating. I checked the setting and sure enough auto-rotate was off, but it insisted on rotating. I toggled auto-rotate on then off again, still kept rotating. Frustrated I plugged phone it, and went to sleep, it charged and in the morning it was not auto-rotating, acted as if nothing had happened.
5> SINCE THAT: the random screen turning on issues, charging issues, and rotation issues have each reoccurred a couple times sometimes independently sometimes in combination with each other.
FOR EXAMPLE:
Today the phone worked fine all day, I played games, surfed internet, sent email, charged it, talked on it, etc. Then tonight while talking it started randomly turning off/on, loading Locations, or asking about dock/Tunein, meanwhile jumping in and out of rotate because I was laying down (auto-rotate still off ). This caused it to jump in and out of speaker mode and the other party I was talking too got a real earfull of my feelings for the phone. I eventually left it on speakerphone in the dock mode and finished the call. 5 minutes later the call was done and the phone acted as though nothing was wrong. (At this point I felt like the phone deserved to be the star in a Steven King novel)
A couple hours later I went to charge it and it was doing its charge for 5 minutes, stop. Unplug/plug-in and charge for 5 more mins etc. This argument went on 4-5 times and it still charging now about an hour later.
So here is the question: Do you think this is something to do with the replaced USB port or the process of replacing it, or is it perhaps a corrupt OS? Keeping in mind that it was fine after the fall, no issues until the port repair. I'm running ARHD 6.0.4, I wanted to upgrade to 6.0.8 to rule out OS before going back to the service store, but Mike's link for the firmware upgrade is still down so I'm stuck for the moment, but I don't want to wait too long before going back to them. (if someone has the 3.33 ARHD firmware/radio please PM me I have ad ftp server you can send it to)
Reasons why I suspect/hope possible corrupt OS:
All the issues seem to be potentially software related.
I removed the SD card and SIM when they had the phone for repair, they most likely booted it up without the SD, perhaps there was some system files that corrupted when SD wasn't present?
Prior to the fall the phone had a couple occurrences of software issues relating to the SD card. twice in the last 3-4 months I lost ability to read the SD card but each time it was rectified with a reboot. Also ever since flashing ARHD 6.0.4 I I have had no bluetooth functionality. I could turn it on, but had no control panel to search for other devices or make the device discoverable, so there was definitely a software issues relating to that, I never used BT so it wasn't a big issue.
I'd really appreciate some thoughts, or 3.33ARHD firmware
Thanks in advance
Zenon
Click to expand...
Click to collapse
Wow long post XD OK I think your best bet would be to flash a stock ics rom. As it Is essentially the same as arhd ( I believe mike trys to keep it as stock as possible) if you keep getting the issues take it back and say to them. Just make sure they don't know you have changed the firmware in case they try to say You have messed it up and refuse to fix it. Worst case scenario I imagine would be if they damaged the board during the repair, but it definitely could be all software related. So flash stock rom and test for 2 days. If fixed then flash up to mikes update when its up if not then off to the repair shop for an argument
heavy_metal_man said:
Wow long post XD OK I think your best bet would be to flash a stock ics rom. As it Is essentially the same as arhd ( I believe mike trys to keep it as stock as possible) if you keep getting the issues take it back and say to them. Just make sure they don't know you have changed the firmware in case they try to say You have messed it up and refuse to fix it. Worst case scenario I imagine would be if they damaged the board during the repair, but it definitely could be all software related. So flash stock rom and test for 2 days. If fixed then flash up to mikes update when its up if not then off to the repair shop for an argument
Click to expand...
Click to collapse
Thanks for taking the time to read it, I know it was super long.I bought the phone with ARHD 5, but had glitches so I read and figured out how to update it to 6.0.4, so my knowledge is really limited to that of ARHD. Following your recommendation I have been doing some reading and I'm still a bit confused. If I flash the stock ROM and I going to lose my root and s-off which I need will need to move back to an ARHD ROM later?
It seems that I have seen more then one stock ROM in the posts I was reading about reverting back, so I'm unsure what one I should use, and will I also need to downgrade firmware and radio to go back to the stock ROM as well? I'm currently running 3.32.401.3CL309896 firmware, and 11.69.3504.00U_11.22.3504.07_M
Perhaps you can suggest a post that will give me instructions and all relevant files I need to revert back, preferable in such a way that I can just move back to a custom ROM later without worrying about all the preliminary work to make the phone ready
zenon1823 said:
Thanks for taking the time to read it, I know it was super long.I bought the phone with ARHD 5, but had glitches so I read and figured out how to update it to 6.0.4, so my knowledge is really limited to that of ARHD. Following your recommendation I have been doing some reading and I'm still a bit confused. If I flash the stock ROM and I going to lose my root and s-off which I need will need to move back to an ARHD ROM later?
It seems that I have seen more then one stock ROM in the posts I was reading about reverting back, so I'm unsure what one I should use, and will I also need to downgrade firmware and radio to go back to the stock ROM as well? I'm currently running 3.32.401.3CL309896 firmware, and 11.69.3504.00U_11.22.3504.07_M
Perhaps you can suggest a post that will give me instructions and all relevant files I need to revert back, preferable in such a way that I can just move back to a custom ROM later without worrying about all the preliminary work to make the phone ready
Click to expand...
Click to collapse
1. The current ARHD rom is 6.8.0 and iirc its super stable ..try it and see
2. flashing stock rom ..will restore everything to stock (recovery and rom and obviously root will be gone too ) but SOFF wont/cant be changed ..so you can just flash a 3.33 firmware then a custom recovery and then rom pretty much ..remember SOFF is all that is needed and literally you can change anything
3.right now the current firmware you have is sufficient to update to ARHD 6.8.0 but if you still want to flash 3.33 ..check here
4.for flashing firmware and ARHD rom ..check the stickies in sensation general section ..there is a dedicated thread for this process which was excellently written by joaquinf
I actually work in a repair shop like the one you visited, and I can tell you, it is NEVER our intention to damage the phones more, HOWEVER replacing a charging port requires quite a bit of heat to be applied directly to the Main Board, and occasionally, RARELY, this has adverse effects on the board. Not saying they DID damage it, and definitely not saying they wanted to damage it, but it can happen from time to time. Ive seen it myself.
If changing the software doesnt help, they should have some sort of warranty (we do) and they can try to troubleshoot it or put a different port down, as it may be shorting something out
ganeshp said:
1. The current ARHD rom is 6.8.0 and iirc its super stable ..try it and see
2. flashing stock rom ..will restore everything to stock (recovery and rom and obviously root will be gone too ) but SOFF wont/cant be changed ..so you can just flash a 3.33 firmware then a custom recovery and then rom pretty much ..remember SOFF is all that is needed and literally you can change anything
3.right now the current firmware you have is sufficient to update to ARHD 6.8.0 but if you still want to flash 3.33 ..check here
4.for flashing firmware and ARHD rom ..check the stickies in sensation general section ..there is a dedicated thread for this process which was excellently written by joaquinf
Click to expand...
Click to collapse
Thank you for the info and especially the link to 3.33 firmware, since Mike's link is still down. That was really the one piece I was waiting for before moving forward. I know 6.8.0 is compatible on 3.32 but because of my missing BT I wanted to upgrade the firmware before applying the new ARHD in the hopes that it fixes my previous existing BT issue along with the rest of my current headaches. I am familiar with joaquinf's dedicated thread it was what I initially used back when I upgraded to 6.4.0. Very well written and a great help :good::good:
I believe I will try for the 6.8.0 upgrade as my first attempt then stock if that is still giving me issues. I'll post back in a couple days with the results.
nickL0V3 said:
I actually work in a repair shop like the one you visited, and I can tell you, it is NEVER our intention to damage the phones more, HOWEVER replacing a charging port requires quite a bit of heat to be applied directly to the Main Board, and occasionally, RARELY, this has adverse effects on the board. Not saying they DID damage it, and definitely not saying they wanted to damage it, but it can happen from time to time. Ive seen it myself.
If changing the software doesn't help, they should have some sort of warranty (we do) and they can try to troubleshoot it or put a different port down, as it may be shorting something out
Click to expand...
Click to collapse
Thanks for you input. The thought that they did this intentionally never crossed my mind, I'm sorry if it at all came across that way. There were very accommodating and professional to deal with, and I'd be happy to recommend them as I truly believe this was a unfortunate side effect of the repair. By trade I'm a electrical engineer so I know all to well what the processes required to carry out the repair and the inherent possible risks involved, I considered doing the repair myself, but due to my schedule I thought it was easier to pay someone else to do it. Whatever the cause its unfortunate, but one thing is for sure, If I had of put the phone on the floor and not the night stand I wouldn't be sitting here now figuring out answers.
Lastly:
If anyone reading this is in need a repair shop in Hamilton ON Canada PM me I'll be glad to send you their information.
Thanks again!
Just an update for anyone who googles this and wonders what the results were. In the two days following my last post a couple weeks ago my phone continued to experience the random issues I described, however after those 2 days all issues disappeared and the phone worked fine. After three days of perfect functionality I flashed the 3.33 firmware and ARHD 6.8.0. The phone worked fine for one more day and then the same random issues, started resurfacing, but with much less frequency. So that brings me back to believing there is definitely something up with the physical repair. The issues are very spuratic, and I often get 1-3 days with no issue and then the phone starts spazzing out in any number of ways, for some random time. I don't find reboots or anything specific fixes it, other then just letting it spaz out until it returns to normal. Sometimes a drop of about 18" onto a solid surface such as a table or wood floor stops its spazzing, but at that it sometimes stops spazzing for 10 minutes, sometimes 1-3 days... which continues to make me think there is a short or bad connection somewhere.
Hello guys. I'm at my wits end and looking for some help.
I bought a new still sealed in the box Oneplus 7 pro off ebay back in April. Bad idea I know. Everything has been fine up until earlier this month when I started to notice that often times when I looked at my phone it would have no signal. After a few minutes it would reconnect automatically. I thought it was Straight Talk at first but it started to happen more and more frequently, and eventually it no longer would reconnect on its own. Since I was frustrated with the service I was getting with Straight Talk I switched to Verizon and the problem persisted. The phone will work fine for 10min, an hour, or half the day. Suddenly it will completely lose all signal. I've tried turning data on and off in the quick settings, or removing the sim card and reinserting and neither will not work. The only sure way to get the data back on is I either have to restart the phone, or turn the data on and off in the dialer diagnostic menu. Those are the only 2 ways to always get the data back on. After it comes back on it will work for several minutes to half the day before losing connection again.
Im currently running 10.3.3, but before this I was on 10.3.1 and had the same issue. I have reset the phone countless times, reinstalled the OS multiple times, tried different network types in the diagnostic menu and nothing works. I don't believe its a hardware issue because switching the data on and off in the diagnostic menu always works.
Does anyone have any clue whats wrong and what I should do? Thanks in advance.
ImagioX1 said:
Hello guys. I'm at my wits end and looking for some help.
I bought a new still sealed in the box Oneplus 7 pro off ebay back in April. Bad idea I know. Everything has been fine up until earlier this month when I started to notice that often times when I looked at my phone it would have no signal. After a few minutes it would reconnect automatically. I thought it was Straight Talk at first but it started to happen more and more frequently, and eventually it no longer would reconnect on its own. Since I was frustrated with the service I was getting with Straight Talk I switched to Verizon and the problem persisted. The phone will work fine for 10min, an hour, or half the day. Suddenly it will completely lose all signal. I've tried turning data on and off in the quick settings, or removing the sim card and reinserting and neither will not work. The only sure way to get the data back on is I either have to restart the phone, or turn the data on and off in the dialer diagnostic menu. Those are the only 2 ways to always get the data back on. After it comes back on it will work for several minutes to half the day before losing connection again.
Im currently running 10.3.3, but before this I was on 10.3.1 and had the same issue. I have reset the phone countless times, reinstalled the OS multiple times, tried different network types in the diagnostic menu and nothing works. I don't believe its a hardware issue because switching the data on and off in the diagnostic menu always works.
Does anyone have any clue whats wrong and what I should do? Thanks in advance.
Click to expand...
Click to collapse
at this point, you could try the opened beta https://forum.xda-developers.com/oneplus-7-pro/how-to/beta-15-rolling-t4114211. you could also try a different kernel to see if that helps.
I finally got off the stable and updated to the beta and the problem persist. Is there like a baseband firmware that I can flash that will upgrade the radio in the phone? Maybe that would work.
ImagioX1 said:
I finally got off the stable and updated to the beta and the problem persist. Is there like a baseband firmware that I can flash that will upgrade the radio in the phone? Maybe that would work.
Click to expand...
Click to collapse
I had that happen to me with an old device when I would select LTE only on my device. Have you tried changing the band from 2/3/4 G to only 2/3 G. This is not a solution to correct your problem, only a test to determine if your signal will remain constant.
Also, since your got the phone BNIB may need to contact 1+ support directly, as I believe you should be within the 1 year manufacturer warranty.