Develop Bugs

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.

Zuk z2(Plus) Wifi Issue

Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.

KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Guys any help

KartmanCV said:
Guys any help
Click to expand...
Click to collapse
Use some other rom... Recommended crdroid latest build... Use picogapps... And try again...
The issue could be rom related and even after trying new rom the problem still persists then it could be a baseband issue...
Try the recommended rom first with complete full wipe .. Good luck

Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,

nicky.phoenicks said:
Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,
Click to expand...
Click to collapse
Were you able to fix it??? How did you resolve? After three years, I faced this issue all of a sudden after I changed my phone's battery, and tried everything with software but no fix. Any possibility that it is a hardware issue? How can it be deeply inspected to find the real cause of this problem?

KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Is there any fix found for this? or is it forever? Need help, need to give this phone to someone but can't fix this issue. Please help through any ways.

You may try resetting the carrier and wifi network. This may help.

You may try resetting the carrier and wifi network. This may help.

Factory reset on a corrupted Android OS?

So about a few years ago, I tried to root my galaxy note 4 (n910aucu2doi3), but I guess it rejected the root because it instantly bricked my phone, to the point where I had to completely wipe it using android recovery. The only way to get my operating system back was to download it online and install it through my PC (I had to find the exact version for my phone as well, 5.1.1 at the time, because it rejected every single other version).
Everything seemed to be working fine, except that I couldn't install software updates on my phone anymore. It was permanently stuck on 5.1.1. It was a bit of an annoyance but I didn't think much of it at the time.
Fast forward to now, and I'm getting several signs that my OS may be corrupted. My phone is constantly freezing, crashing and restarting. Maneuvering through applications causes the phone to freeze for a few seconds before either restarting or crashing the app. I want to say it's definitely a software issue, but I did install a new battery recently and it was working fine for a few weeks, could that be the issue?
If not, I want to start over, but I'm not sure how, and I don't know if it's safe to do a factory reset on this OS. Is there anyway I can get a fresh stock version of an android OS that can also update?
Any help is appreciated, I'm pretty much desperate.

I manually updated to 6.0.1 with the help of this thread https://forum.xda-developers.com/note-4-att/general/updates-thread-t3663943
It seems to have fixed the issues so far, and my phone can automatically update again

Phone broke down on its own.

Hi Friends, installed oreo on my phone and everything was fine. One day the phone suddenly hung up, then started to reset. I installed Cleanrom. The problem persisted in him. The battery was a little swollen, I bought a new battery, and the problems remained.
The phone was reset when entering whatsapp last night and the software was corrupted. When I deleted system / data / cache with Twrp, it gave errors and the phone is no longer available. I came to mind to install kdz, I installed kdz, the phone was fixed. Currently whatsapp installed is still no problem but I can not root phone resets.
Do you think my phone is broken, is there a solution for this? What should I do. Thanks.

Wifi/Mobile Data no longer works

Hey guys,
My Pixel 2XL initially had some reboot issues so I decided to root it, and was able to do that successfully with magisk on stock firmware with some modules installed as well. It regained its functionality for the most part but unfortunately the Wifi stopped working (kept searching, could'nt find any network). It would sometimes randomly work on some reboots but whenever it did, the phone would auto-reboot after a while and lose the function again (but would work perfectly otherwise).
So I decided to unroot and factory reset with stock firmware thinking it might be a partition defect, just to see if that fixes it but it didn't. And what's more, the phone has once again returned to bootlooping like before root. Can anyone help me find out the issue here? And if I can manage to root it again and get it working, is there some way to resolve this issue (maybe through a custom kernel)?