Develop Bugs

[Q] Continuously restarting

I have installed Myn’s Warm Donut on my Kaiser with the stable kernel from atools and it was working just perfect. Also i installed the [email protected] update from Millence. System and data on Nand.
I have installed several applications and just configured the options of the phone and it started restarting. Sometimes 2-3 restarts before it continue loading. The battery shows 45%. And sometimes everything is working just fine and me just touching the phone to take it, and restart....
Already several times happened after several restarts like this all the data was lost.... and everything from the beginning.
Please give any advice!
PS. I'm using Donut because it is the fastest version

Same thing with me. Im running .32 on nand with froyo and it happens.
It also happened with myns as well. Something to do with data on nand I think.

If data is on sd partition i dont get the phone flushed but still sometimes restarting and the phone is sooo slow and often not responding

Once i got a message for missing and/or incorect UID after the restart and the phone was flushed. Immediately i restarted and Fixed the permisions, everything was ok after that, just like before. And today after installing one application and little useing after that i got a restart and everything was flushed. Fixing the permisions gave an error. Please help, how to fix this issue. Thanks!

Check if it those restarts are happening if your data connection or wi-fi is off. If not, turn on gps first and then your data/ wi-fi. Working for me

same problem for me

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.

"Wifi Turning On"

IF YOU DONT WANT TO READ THIS, SKIP TO NEXT PARAGRAPH
I have been running Jedi Mind Trick x4 for the past couple of weeks. Everything was working fine, super quick and super stable rom. Then, out of the blue yesterday, the Wifi stopped working. It just stalled at "Wifi Turning On". I never received an error message, it just would never connect. I took out the battery, took at the sim card, rebooted, problem persisted. Factory data reset, wifi worked for an hour, then again stalled at "Wifi Turning On". Flashed UVLI4 radio, problem persisted. I decided this must be a rom problem, so I wiped my data and flashed Jedi Knight 6 using CWM. Clean flash everything working fine, hour later wifi stalls. I look on the forums and I see a lot of people with ICS are having problem, but no solutions. Then I flash Jedi Jelly 5, a JB rom, again, wifi works for an hour then stalls. At this point I was so pissed off I decided to unroot my phone. I wiped all my data from external and internal sd, factory data reset, and unrooted using ODIN. Again, wifi worked fine, then stopped. Updated to 4.0.4 using Kies, now Wifi is bouncing between on and turning on. At "Wifi Turning On" most of the time.
IF YOU DONT WANT TO READ THAT^
Long story short: Im on stock unrooted 4.0.4, and my wifi stalls at "Wifi Turning On". Ive had the problem on custom ICS and JB roms.
I have seen this problem on other threads but no solutions, so I made a new one. This problem is particularly annoying since I dont have any service at my house and rely on Wifi Calling.
BTW: Bluetooth doesn't work at all.
Look to attachments for a screenshot of what Im seeing:
Anyone else having this problem? Has anyone found a permanent solution?
Thanks

[Q] Stuck on bootloader after changing screen density with Rom Toolbox

Hey guys. As the title suggests, I can't boot my Note 2 (sgh-i317). It is stuck on the AT&T logo and while it's stuck there it vibrates slightly every 5-6 seconds. I tried changing my screen density to 240 and it worked for a bit but annoed me. then I went to change it back and got this problem. I accidentally set it to 360 I think though, instead of 320. I have wiped the cache. I have wiped the data. I have installed roms countless times already with Odin. I'd imagine my reset counter is at over 10 just from today.
I've been searching on google and these forums for hours and have seen many suggestions, but none of them have worked. The farthest I have gotten was to get the phone to boot, but once I start going through all the setup stuff I begin getting error popups saying that Touchwiz home has stopped responding. As soon as I push OK the error immediately pops up again. I seriously can not do anything with my phone.
Is there any way to get a stock build.prop file somewhere for this phone, and if so, how would I install it if I can't even boot into the device?
Any help would greatly be appreciated. I have no idea where else to turn here. Thanks!
-Mark

Do you have a backup to restore from recovery ??
If not....then power down the device and remove the SD card and place it into a PC card adapter...
Then download or copy over a suitable rom...
Then place the SD into the phone and boot into recovery...
Fully wipe the device and flash the rom of choice...
Reboot....set....profit....g
Edit:
Are you certain that your power button is not stuck ?
If the method I suggested fails... and rebooting occurs with vibration...then your power button is suspect....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Thanks. Well I got it to boot finally, however there's been a couple issues since. It's on 4.1.2 right now...
1. Whenever I try to officially update to 4.3 through the settings, it downloads, then when installing it ALWAYS fails at 25%.
2. This is a big issue. My data connectivity is gone. I have no 4g access period. If I'm not using a wifi network, I can't do anything online, period. I've reflashed numerous times, and can't get it to recognize the network. I can make calls just fine, just no data.
I've tried wiping data and going to factory reset, but this doesn't help in any way whatsoever. I've popped out the battery and sim card and reinserted after a few minutes, still to no avail.
The funny thing also, last night my friend, who has the same phone, updated to 4.3 and got the EXACT issues I've been dealing with. The ONLY thing in common is that we have both rooted our phones in the past. When I first got 4.3 it worked fine. It wasn't until I rooted that these issues began. My friend's phone was not rooted, however it had been in the past. I'm thinking that this 4.3 update has an issue with phones that are rooted or have been at some time. I don't know how it can tell, but that's all I can think of. his phone now is also a doorstop, like mine.

K, fixed data connectivity from another thread here. For some reason, even if I wipe my system, it seems to still keep settings intact. In this case, nothing set in APN. Seems the more I try to fix my phone, the more problems show up.

If you updated to official 4.3...then yes ...a whole new host of problems are yours until the devs figure out the locked bootloader and it's knox flag...
Backups won't restore....and so forth...
Read around ....you'll see...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

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.