Database Develop

reboot loop

I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman

Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One

Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.

I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.

Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91

houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue

Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman

The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE

Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman

[Q] Foce close error all installed apps not showing 2nd time...

Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.

i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run

Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.

I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.

nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later

I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.

read this
http://forum.xda-developers.com/showthread.php?t=793404

Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...

I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?

Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.

[Q] I9000M 2.3.3 stock constant reboot and screen turned off

Hi I have a strange problem with my Samsung Galaxy S Vibrant (I9000M) running 2.3.3 stock.
Description:
a) Booting the phone would show the big S animation and bong sound however after that the animation repeats in a loop with no more sound. The phone never reaches the home screen. I notice this mostly in the morning when I wake up.
b) Usually during the morning when I wake up to check the time the screen doesn't turn on but it seems as if the phone is still working; the chime for plugging in the charger sounds. (I thought the battery was dead but it was actually at 60%)
What I've done so far:
a) I brought it back to the vendor and got a new phone.
b) Holding the power button would turn off the phone, then I would turn it back on. Sometimes it requires that I pull out the battery which results in losing all my data on the internal memory like a factory reset.
Question:
I'm highly concerned. I've gone through two of these phones and problem "b" is always a prelude to problem "a". I'd like to know if there is a possible solution and/or what the problem might be?
Note:
a) The problem started happening a day or so after I started using Samsung IM. (Skype was installed but never used)
b) The problem started the morning right after I installed Skype. (I have since uninstalled Skype, it's still happening )

You should not be losing data on your SD card by pulling the battery.
Did they give you a new phone or a refurb?
What's the build number of your phone? Should be a number under the battery in YY.MM format.

Hi Black Rose
I was talking about the internal memory not the sd card.
It's a new phone.
The build is 11.11.

If you are running stock 2.3.3 and having those issues, I think the phone is faulty.
My wife is running 2.3.3 on an 11.03 build and has no problems.
The fact that you are losing data when you pull the battery sounds like the internal memory is failing.

Alright, thanks. Do you have an idea what causes the screen to not turn on for the second phone? (This new one doesn't loose internal memory on battery pull)

I had that happen to my own phone (also an 11.03) once with Froyo 2.2 and once with 2.3.3.
With Froyo I was able to plug in the charger and the phone "woke up".
The only time it happened on 2.3.3 I received a couple of notifications at the same time and had to power it off to get the phone to work again. It never happened again in the several months I was running 2.3.3.

Okay!
Thank you Black Rose for giving me some useful information. I was just worried that this would lead to something a lot worse.
Much appreciated!

This is my 3rd phone had the exact same problem as you I heard it was something with the mother board there is a board in here dedicated to the problems with the gt-i9000m
Sent from my GT-I9000 using Tapatalk

Thanks for letting me know bambam1978; I hadn't realized there was a whole topic for all the problems. I've been searching for the specific problem where most have customs roms which is why I started this one.

[Q] S5 mini 4.4.2 full stock random freeze/reboots

Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem

contrinsan said:
Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem
Click to expand...
Click to collapse
This seems to be a common error with the S5 mini. There is a whole thread in the German Android forum about this issue. Also the German Amazon product page for the S5 mini has about 40 users complaining about this problem.
Some users report that the reboots start after some weeks of usage. First it just reboots once per week, then it gets more frequent until it reboots once per day.
Factory resets or firmware updates do not help. Some users sent their phone in for repair but not with huge success.
But not every device is affected by this. So far I did not notice that behavior with my phone (G800F).
I guess it is a hardware issue as not every device is affected and the error gets worse after some time.
The only way to diagnose what's wrong with the device is to check the adb and kernel log (at least the last kernel log before reboot might be available at /proc/last_kmsg). But this would require rooting the device which in turn would void the warranty. It would also be interesting if those reboots also occur with CM 12 (installing this will also void your warranty).
So it seems that sending the device in (without a great chance of repair) is the only option that Samsung gives you without loosing warranty.
Alternatively you also might want to wait for the official Lollipop release and hope that this will fix the problem.
If someone with this problem already rooted his device it would be interesting to get the log files (adb + kernel) of the times of the crashes.

Thanks for your reply, so it might be a hardware problem after all

Phone keeps rebooting randomly and shuts down when idle for too long (during night)

Hello everyone,
This is my first post on XDA so please forgive me if I'm doing something wrong.
So my story, I got a refurbished unit at Swappa, I updated to the newest version directly (G920TUVU3DOI1) and it was working fine for the first week or so. Then the reboots started happening, I didn't give it too much thought but looked into it anyways.
At first I thought it was a problem with the WiFi and I tried to keep it off for a while, and it did work for a day but again the restarts kept happening, and now with the phone turning off during the night (no apparent loss in battery mind you).
Then I went to rooting and custom kernels.
I installed unikernel v8-0002 through Odin3_v3.10.6 and I tried removing some Samsung apps with TitaniumBackup in case there was some conflict happening but the restarts kept happening.
Then I installed a custom ROM, "XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S" to be more specific.
And to my surprise it worked great, no restarts or shutdowns for about 2-3 weeks, it was great!
But then out of the blue the restarts started happening, they started slow, about 2-3 a day.
But after a few days they went to 10-20 and after that 100-200 a day.
Something was definitely wrong. So I installed the original firmware again (G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME) and booted to the stock firmware, restarts kept happening of course (didn't expect them to stop).
So I retreaded my steps and installed multiple other kernels (Unikernel V9, Vindicator, multiple different flavors of them). Also I installed multiple ROMs (Arrow_ROM_v6.0.0, and DN5 - S6 FLAT - EDGE v4 OJ5 - deodex) but nothing seems to work;
I did multiple wipes, storage wipes, cache wipes, factory resets (from GUI and twrp-2.8.7.2-zeroflte) but every time the same thing happens.
I did notice that the phone stutters and freezes, a behavior that I have not experienced before.
I installed CatLog and got multiple log files when the phone restarts but all of them are different and there is no "pattern" to be found (at least in first inspection). I want to upload them but my post count prohibits it.
Please let me know what can I do, I will reply to your questions ASAP so at least I can get some light into what is happening.
Thank you!

I'm in the same boat. Never had a problem before. Received my phone back from Samsung after a screen repair and now, doesnt matter what rom, kernel, patch, it always ends in random reboots. Most often when I'm scrolling or if a page is loading something in the background. It does a lot of hot reboots (not full shutdown and start ups) so its quick but infuriating. Tried everything, slowly losing my patience.
Any idea what it could be? Something related to Knox? Bootloader/Modem?

#3
Hello, I am too having the same problem. Even after a factory reset