Radio not working after reboot - HTC 10 Questions & Answers

Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?

I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?

time_lord2004 said:
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
Click to expand...
Click to collapse
Simply installing a custom ROM will not affect the radio partition.
Why not try a RUU to return to full stock. Find one for your phone and run that. If it still doesn't work then it's a hardware problem.

Ok, so I replaced the current 2.41.401.41 (August) ROM with the earlier 2.41.401.4 (January) in the hope that a ROM change might reset the cellular radio. It didn't. 'Turn on radio' still does not respond either.
I did this with the bootloader onlocked, but S-ON. I think my very last attempt to fix this could be to set S-OFF, in the hope that some tool might be able to access the radio partition and re-write it or reset it or something. (This is still in the slim chance that this fault really is in software and not hardware!)
Are there any xda tools that write to or reset the radio partition (when S-OFF is set)?

What the...?!!?? So I thought as one last go at this (unless someone had comments re the S-OFF/radio partition idea), I'd let the phone get the OTA update back to the latest OS. So first I executed 'fastboot oem lock'. That of course erased device and reset it again. Radio still not working, no surprise.
After that, restarted in bootloader mode to confirm it says 'relocked', then rebooted normally... and I've started receiving missed txts! WTF.
So with enough restarts/resets, it's fixed itself? Faulty hardware, yeah right. Unless it is on the turn and happens again. [Edit: Yes it has, damn.]

Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.

amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.

I got this disease a week ago, tried to restart, didn't help. Been tapping airplane mode like million times, nothing. Found this thread, followed your instructions guys.
time_lord2004 said:
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
Click to expand...
Click to collapse
Didn't work for me :/ moved on to zachariah's solution...
zachariah109 said:
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
Click to expand...
Click to collapse
Yes, IT WORKED.
Don't get me wrong, this is not the end.
Today. Radio doesn't work again. 5min off doesn't help anymore, unlocking-relocking bootloader ain't do **** too.
If you find any other action sequence which "fixes" radio, please share.

So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.

lightweaponx said:
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
Click to expand...
Click to collapse
Today I ran RUU. It didn't fix radio. Problem must be somewhere out of radio/system partitions range.

Well, I thought I'd do one final(?) post regarding this issue. I'm starting to concede that I might have a hardware fault, but it's taken a while to accept this.
About 2 weeks ago I started having problems with the 'swipe-down' at the top of the screen to look at notifications and settings (and it started responding badly in the camera app). Then it stopped responding completely... work-around was to use an 'open notifications' app.
However, I tried out 'Apex Launcher' as an alternative to the Sense interface, and swipe-down worked perfectly ok, so isn't the hardware ok? Isn't it a software issue? However, swipe-down had completely stopped working in the camera app by then (using a different camera app is acceptable work-around).
Roll forward to a couple of nights ago, I got notification and updated to android 8/Oreo, what have I got to lose! After the update completed, I can now swipe-down ok again on the home screen! But still not in the default camera app! So have I got a hardware problem or not...
But the big thing, and the biggest headache... once again after the big update (to Oreo) and reboot - once again the cellular radio was not working. I tried all my tricks of the past, nothing would make it go. A factory reset (to Oreo, not an old RUU), unlock and relock (which does a factory reset), nothing worked. Brought up phone info via *#*#4636#*#* and this seems to have had a make-over. There is now a button for 'mobile radio power' (must be a replacement for the 'turn on radio' option) which was showing as off. Turning it on seemed to do nothing (leaving it for a while and then waiting for screen refresh, this button would display as off again).
I'd probably rebooted, shutdown/gone into bootloader at least 2 dozen times, tried all combinations of everything I could think of and could not get it to wake up. At lunchtime today I was leaving the office, booting up my phone one last time and said to a workmate 'going to a shop to look at new phones'. 30 seconds later I look down at my screen... what the *(&$%*&!! I have a signal! Missed txts are coming in!
I know that now that the cellular radio is on, it'll keep running. It always has through this whole ordeal. It's just a matter of getting it to turn on in the first place, or starting after a reboot.
The fact that after installing Oreo the swipe-down works nicely (except for the default camera), and the cellular stuff works fine, once it is on, it really is difficult to conclude whether these are all software or hardware issues. But the reluctance of the system to turn on the cellular radio might be the biggest damning factor to point to it being dodgy hardware.
So the key is not to have to reboot ever again, or at least until the next flagship is out! I still have faith in the HTC stuff, but this has been frustrating...
Hope this helps someone out there!

So i've opened mine up - was due for a screen replacement anyway - tada bad contacts to the radio module (dry solder joint) physically pressed the radio module and it turned straight on. *i've added some paper layers underneath to keep *merckanikal* pressure on it (easier fix than reflowing) and now i know where it chip is i can press on the screen to add a little more if it doesn't work
It really ****ed me today however(seemed to cause phone to bsod, then reboot without radio) and the reason i've spent the last 3 hours replacing the screen and ****ing with the radio.
(whole day of work lost thanks to it. won't see that time back)
In other news i went and tested the note 8's spen - and i think i'm retiring the 10 this week. althought i've just fixed it shes' let me down for the last time.
The only negative i've gotten from the mechanical pressure is the lcd is showing a slight tinge of red now that the glue has hardened. and theirs pressure on the back of the screen. i used 4 layers of 80gsm paper (folded) to pack it out. i'm hoping as the phone heats and moves the paper will compact slightly more and the red blub on the screen will dissipate entirely -
- restarted over a dozen times to confirm the fix is atleast working for me. bootloader'd recoveried etc.. hasn't disabled the radio since..
Hope this helps for any of you still hanging onto the htc10.. (the pixel2's daddy, seriously just feels like the exact same phone*thats what she said?*)

time_lord2004 said:
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
Click to expand...
Click to collapse
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try

Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Dissmeister said:
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Click to expand...
Click to collapse
Did It Really Works

Adeel Ali said:
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Did It Really Works
Click to expand...
Click to collapse
Yes it works.

yldlj said:
Yes it works.
Click to expand...
Click to collapse
Brother Did U Tried It U Also Have HTC 10

Adeel Ali said:
Brother Did U Tried It U Also Have HTC 10
Click to expand...
Click to collapse
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?

yldlj said:
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
Click to expand...
Click to collapse
Yes I Went From Oreo To Nougat Once

Adeel Ali said:
Yes I Went From Oreo To Nougat Once
Click to expand...
Click to collapse
Then erase persist. Or get back on oreo

RUU worked for me

Related

Help! Phone crashes after booting OS!

Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.

Signal problems after update

Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.

Problems Updating OTA - Stock Non-Rooted

I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.
robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.
aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.
Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?

D855 very weird wifi related problem

I used to have the problem described in this thread (http://forum.xda-developers.com/lg-g3/help/wi-fi-bluetooth-fm-radio-d855-t3284582/) and it evolved to another problem so I've decided to create a new thread.
I've already factory reset my phone several times, had marshmallow, lollipop and kit kat (current version) and none of the versions seem to fix my problem.
My phone randomly has wifi and bluetooth and other times it just doesn't. When it has wifi, I can use the phone for a while and after that the phone will simply crash and start bootlooping or will boot and turn off right away or turn on and have no wifi(and IP adress unavailable on settings). When the phone has no wifi, I can use it as I want , it won't randomly crash or start bootlooping.
Trying to reboot the phone will, most of the times, result in a booloop which can only be solved by removing the battery(sometimes even that won't solve it, and I have to wait a bit before I can put the battery back again)
Is there any way I can find out what's causing the bootloop, like a log or something through adb?
Really hoping you can help since I'm running out of ideas. Thanks for your time.
myclarity said:
I used to have the problem described in this thread (http://forum.xda-developers.com/lg-g3/help/wi-fi-bluetooth-fm-radio-d855-t3284582/) and it evolved to another problem so I've decided to create a new thread.
I've already factory reset my phone several times, had marshmallow, lollipop and kit kat (current version) and none of the versions seem to fix my problem.
My phone randomly has wifi and bluetooth and other times it just doesn't. When it has wifi, I can use the phone for a while and after that the phone will simply crash and start bootlooping or will boot and turn off right away or turn on and have no wifi(and IP adress unavailable on settings). When the phone has no wifi, I can use it as I want , it won't randomly crash or start bootlooping.
Trying to reboot the phone will, most of the times, result in a booloop which can only be solved by removing the battery(sometimes even that won't solve it, and I have to wait a bit before I can put the battery back again)
Is there any way I can find out what's causing the bootloop, like a log or something through adb?
Really hoping you can help since I'm running out of ideas. Thanks for your time.
Click to expand...
Click to collapse
problem is that most logs get cleared at boot, last kmsg might have some info but why not just do a cse flash of the kdz ?
suljo94 said:
problem is that most logs get cleared at boot, last kmsg might have some info but why not just do a cse flash of the kdz ?
Click to expand...
Click to collapse
I'll get last kmsg and post it here in a bit.
already done cse flash, factory resets, etc., nothing works.
myclarity said:
I'll get last kmsg and post it here in a bit.
already done cse flash, factory resets, etc., nothing works.
Click to expand...
Click to collapse
and you tried diffrent versions I see it might be a hardware failure
suljo94 said:
and you tried diffrent versions I see it might be a hardware failure
Click to expand...
Click to collapse
I've attached some files after turning wifi on when ip adress is unavailable, hope this can help :/

Question Soft Reboots After Every Reboot [SOLVED]

EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.

Categories

Resources