Database Develop

Constant rebooting

i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.

If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?

I do have a overclocked under volted kernal

sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...

WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !

Does your phone lock up (unresponsive) before rebooting?

Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.

Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.

I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.

[Q] Boot Loop when installing ROM

Hey guys; i'll try to provide you with all the information but honestly i'm not 100% on all of it so try and be patient.
I'm trying to go back to SuperE from Froyo by Laszlo which was absolutely killing my battery without me even using it. However, every time i flash it (and i wipe everything) after it goes past the G1 screen it just resets again.
I'm not sure if this is maybe because of the new kernel (2708) which i'm PRETTY sure i have, but am not 100%. I do know that i have one of the new radios though.
Would the kernel be causing the problem? If so how do i downgrade?
I hope you can help me out!
Thank you!

Q: Can you mention step-by-step what did you flash? And confirm the exact setup before flashing. I believe you mentioned your radio is 2708.
Powered by Android

Thank you for replying. I'll definitely try.
I'm back on FroyoByLaszlo-int2.1 because i couldn't successfully flash either Super D or Super E.
My Radio is 2.22.28.25
Kernel version says 2.6.35.10 - froyobylaszlo
Basically i did what i always do. I wiped everything, first by flashing the "all-wipe" and then going back and wiping it all manually.
Then i flashed the appropriate gapps, followed by the ROM. Rebooted afterwards, but every time it gets passed the G1 screen it reboots.
The only thing i can think of is incompatibility with the kernel but then again, i don't know crap, so that's why i'm asking

Yep, most likely it is indeed the incompatibility of the kernel with the radio.
I'd try flashing the ezBiffTestKernel20101106-2708.zip after the ROM+GApps.
Just use Google to find the kernel.
Powered by Android

The battery drain could be becos of the new kernel. Try installing the 35.9 kernel from ezterry (the one he had for CyanogenMod 6.1 2708) It is working good for me, the battery last for a whole day.

Reboot & Wifi "error" after 2 weeks of using any ROM

Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!

Sorry for the double post,
Is there a better forum to post this in?

spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate

Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.

Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance

spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.

I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.

bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...

New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?

New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl

Does anyone knows how to stop rebooting problem?

I am now using the Original Stock ROM and downloaded several Apps. After few days, it just gave me headache because of rebooting issues.
I downloaded already the following files:
CWM 5.0.7
Titanium Backups
BusyBox
SuperUser
But still, I encountered rebooting problem.
Can somebody help me?
If this one solve, then, I will add the solution to my Official Thread.
Thanks in advance Guys.

im on v20m stock rom...rooted but havent flash any clockwork recovery...so far havent got any reboot and in fact its the most stable ROM i use so far(from v20f stock to cm7 to cm9 to v20j stock to v20m stock)
what stock version do you have?
you said it started after downloading certain apps...try uninstalling those then check if it will still reboot.
last i would recommend is smartflash the stock rom again

In my experience, I've had random reboots for a number of different reasons. It's hard to tell what may be the cause just based on your description. Please provide more details. For example, Does it boot at all and then reboot after some use? Or are you stuck at the boot animation and cannot go to the home screen at all?
And when you said you are on stock ROM, is it the same stock you had before? Or is it a different one?
To share some of the reasons I've had in the past...
1) Incompatible kernel (may not be your problem since you are on stock)
2) Overheating (usually due to overclocking too rigorously and/or wall charging)
3) Messing up with settings somewhere
And as chupi said, just basing on what you wrote, it may be related to one or a combination of the apps you installed. Or, there may be just a bad combination of the apps that you are using.
I hope you have a backup prior to the app installation. That should help narrow down things, or at least go back to the pre-problem stage.

chupi_24 said:
im on v20m stock rom...rooted but havent flash any clockwork recovery...so far havent got any reboot and in fact its the most stable ROM i use so far(from v20f stock to cm7 to cm9 to v20j stock to v20m stock)
what stock version do you have?
you said it started after downloading certain apps...try uninstalling those then check if it will still reboot.
last i would recommend is smartflash the stock rom again
Click to expand...
Click to collapse
Thanks Chupi.
It is Okay now. I think, it is because of Fruit Ninja, Half Brick application. So, I just uninstalled it.
Also, I disable Background Apps of Yahoo Mail.
Everything is now OK.
I am using V20M.
Regards,
Jose Rey

aragorn7 said:
In my experience, I've had random reboots for a number of different reasons. It's hard to tell what may be the cause just based on your description. Please provide more details. For example, Does it boot at all and then reboot after some use? Or are you stuck at the boot animation and cannot go to the home screen at all?
And when you said you are on stock ROM, is it the same stock you had before? Or is it a different one?
To share some of the reasons I've had in the past...
1) Incompatible kernel (may not be your problem since you are on stock)
2) Overheating (usually due to overclocking too rigorously and/or wall charging)
3) Messing up with settings somewhere
And as chupi said, just basing on what you wrote, it may be related to one or a combination of the apps you installed. Or, there may be just a bad combination of the apps that you are using.
I hope you have a backup prior to the app installation. That should help narrow down things, or at least go back to the pre-problem stage.
Click to expand...
Click to collapse
Thanks Aragorn.
I think, some applications are not suitable for SU660. Right now, I just uninstalled the Fruit Ninja (Half Brick) and disabled the Background Apps of Yahoo Mail. Everything is Ok Now.
I recharge it through my laptop.
I am using V20m and it is the latest version.
Regards,
Jose Rey

I have the same problem. It regularly happens when Im playing games but when the weather is cold for some reason, it rarely happens. must be hardware.

Rom Install Issues

Hello everyone, I am new to this forum but have been rooting androids for years now. I have an issue now that I have never seen before. I have my HTC One rooted, S-OFF, firmware updated, everything as it should be. Heres the problem. Whenever I try to install a rom, (Insert coin, Renovate, etc.) the install goes totally fine. However, whenever I go to reboot into the system, it just hangs at the first splashscreen. The one with the green HTC logo and the powered by android at the bottom. It has sat for 5 minutes before I decided to turn it off. Anyone know a fix to this? thanks,
Parker.
PS. All of these are Aroma install roms, if that matters.

Have you tried flashing a regular Ron without AROMA, like the stock Rooted rom?
Based on the touchscreen issues with AROMA and thus phone, are you certain that you are flashing the correct carrier?

AarSyl said:
Have you tried flashing a regular Ron without AROMA, like the stock Rooted rom?
Based on the touchscreen issues with AROMA and thus phone, are you certain that you are flashing the correct carrier?
Click to expand...
Click to collapse
I've run into this on the 4.4.3 and 4.4.4 ROMs on my S-On HK edition. When the screen does go out after several minutes, I hit the power button and the phone works normally. I'm guessing that it has to do with old firmware being used with the 4.4.3+ ROM bases. I'm going to do Sunshine S-Off today so I can update my firmware and see if that makes a difference.

I have not tried a non aroma rom, that might just be my next step. I know for a fact it is the correct carrier rom, all the ones I have flashed are universal
I will try to do the power button thing you mentioned, thanks for the tip.
After work I will try all of these!

parkerskouson13 said:
I have not tried a non aroma rom, that might just be my next step. I know for a fact it is the correct carrier rom, all the ones I have flashed are universal
I will try to do the power button thing you mentioned, thanks for the tip.
After work I will try all of these!
Click to expand...
Click to collapse
Just got S-Off and upgraded the firmware to the latest. The problem has been solved for me. Boots right up now.

Which firmware did you upgrade to? I tried to upgrade to 2.22xxx and it didn't fix anything for me.