Hi guys. I have an issue which now happens too often to ignore. I have two batteries and sometimes when I turn phone to change them it will boot loop/ get stuck on Samsung i7000 Logo. To solve this I used to boot into recovery do a back up -> full wipe -> start phone to see if it works -> recovery -> restore. Restore package would have a strange name 2000-01-01.00.00.15 - so phone also loose current date and time settings.
I thought it was ROM issue so I did clean install of a ROM I never had issues with before but it now does the same thimg. So it must be a problem that goes deeper then just ROM re-install. Can someone advise how to fix it? Or how to do a proper Hiroshima-Nagasaki wipe that will wipe everything to bare semiconductors and new re-install.
Thanks
just go to sammy service shop and have them change cmos battery on your Note mainboard
Cmos battery - most likely. Taking main battery out even for 2 sec resuls in loss of time and date. I use network automatic time so it sets within few secs after turning the phone back on. But for the first few seconds shows 00:00.
Dont see how it can be linked to my bootloop problem. Must be 2 separete issues then.
Related
I decided to do a reboot just to have a fresh start after adjusting some app. The phone was stuck at the flashing Darky logo for indefinite amount of time. After a minute or so of flashing logo, phone vibrates shortly and continues flashing the logo. That repeats each minute.
Taking out the battery and retrying didn't help, same thing.
In the past 48h since last boot, I've installed a bunch of apps, mostly games, so it's natural to look for a culprit among them. However, right now I can hardly do anything with the phone. I can access the recovery menu, download mode probably as well and that's it.
I'm ready to flash the Resurrection Edition, but first I'd like to exhaust other options for fixing the problem or at least backing up everything I can. I have partial backups but would very much like to access the latest changes that weren't backed up.
My questions are:
1) Is there some kind of boot logging that I could turn on, access and which would point to the problem? I'm comfortable using ADB if it's needed.
2) I did a CWM backup. What did it backup? Primarily, what about contacts, SMS messages?
3) The most important question: If I reflash the ROM and then use CWM restore, will the problem repeat itself? (If an app is the source of the problem and all apps are backed up and then restored, I'm afraid the problem won't go away. I see few big image files in the backup folder which suggests that everything will be restored as it was. Bootloop too?)
Additional hints for experts on what might be causing the problem:
There are only two incidents that come to mind.
First is that I did a wipe flash of darky 9.1, then a regular flash of 9.2. After I discovered my GPS simply doesn't work on 9.2, I did a regular flash back to 9.1. This was about 2 weeks ago. Is there something in this procedure that might leave some problems that would show up in the future?
Second thing is a incident I had 2 days ago (the time last reboot was done and last time I've had a successful boot).
I left the phone ON over night, and in the morning found it turned off. I thought it might be a dead battery so I plugged it in. It wouldn't start for few minutes but then booted normally.
During that day I found it OFF one more time, for no apparent reason. This time battery was nowhere close to low. It turned off while in standby/locked screen mode so I can't say that it was doing anything in particular.
(Even the turning off during the night is suspect. It had sound on, it was near my head, and I'm sure that low battery warnings would wake me up. It might just be the case it turned off for no apparent reason like it did during the day.)
i think, that when you flashed 9.1 over 9.2, it could leave some weird things, because everyone is talking bout updating, and no-one even think about downgrading rom.
Answer 1. If you used SpeedMod kernel, I think you can turn Logging in Tweaks Menu at RM, and start phone with plugged USB cable to computer (running adb).
Dunno bout other kernels.
Darkyy normally turned off logging, because ROM was bit faster without it.
Answer 2. Probably contacts were synced to Google (contacts.google.com) <--- try it
I think SMS messages are backed up together with whole ROM (contacts too).
Answer 3. Probably yes, problem will repeat. I don't know but maybe there is some way you can restore only some things, not whole system.
I think you should make "Backup Everything" in CWM, then try flashing 9.2 again.
Weird that GPS were not working there.
It seems something bad was happening that caused random reboots.
What apps that require root, you were using? Swapper, Galaxy Tuner, Overclocking?
I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.
next time something like this happens use adb logcat to figure out what is actually going wrong
exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )
Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.
exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption
I am currently experiencing continuous reboot on my Single Sim Z3+ phone on .253 firmware. It used to be ok but about a week ago I started experiencing this problem as soon as I reboot the phone after setting it up from a fresh install with full wipe. It seems to work normal on earlier builds like 28.0.A.8.266 so only happens on 32.1.A.1.185; 32.2.A.0.224 - .253. I repeat, I have done fresh install with Full wipe several times but problem still exists. Urgent help needed.
Thanks
yawo76 said:
I am currently experiencing continuous reboot on my Single Sim Z3+ phone on .253 firmware. It used to be ok but about a week ago I started experiencing this problem as soon as I reboot the phone after setting it up from a fresh install with full wipe. It seems to work normal on earlier builds like 28.0.A.8.266 so only happens on 32.1.A.1.185; 32.2.A.0.224 - .253. I repeat, I have done fresh install with Full wipe several times but problem still exists. Urgent help needed.
Thanks
Click to expand...
Click to collapse
Hello yawo76,
I have the same device, and I had the same problem, what I did is the next:
With flashtool, download the stock firmware via xperia firm on the same tool (I have successful with E6553_32.2.A.0.253_1295-0156_R6C), after that, in the options, be sure that the MiscTA Exclude options are check, that's the clue. After that complete the setup menu, and try again.
Regards! and sorry for my horrible english.
I do have the same issue. I have Z3+ Dual. Random reboot and/or sleep of death.
What I saw from other posts about hardware issue (no other proof), is about the NFC antenna. But I tried and nothing changed.
I have my phone fresh ROM .253 MM installed and click all the way to home screen and let it sit. Well, nothing happened for many hours 5-6hr. Almost every other hardware functions off. However, once I turned on WIFI, something happened. Blank screen and 3 red LED blinks to reboot. A few moments later at home screen.
Soon, sleep of death (SOD). It is like, when the phone is standby (black screen sleep), when I pushed power button to wake the phone, it won't turn screen on. Like it's hang or something. No choice but to hard reset so that I could turn back on.
Then, I played with WIFI setting and saw a "Keep Wifi On during Sleep". I switched to "never" and tried let it sit again. I found out problem was gone for 10 hours (this is best record now, usually 2-3 hours, reboot happened).
I am still monitoring.
Wish you can try and confirm this.
I ran many tests about this issue. Found out it was the material of board or CPU or power which was not made strong enough. I tried tuning the CPU a little (just like PC of CPU tuning). So that it will not cause SOD, random reboot issue. It was also adjusted such that the battery saves much and prolong the usage of the phone.
With sitting of standby the phone is not running warm. Messages or phone calls will not delay in receiving. Plus, it draws about 2% of juice during standby of 6-8 hours.
Worth the try.
I'll try to make this short.....
I am using N910T3. Phone was charging in car while using (stop by roadside). Out of sudden it shutdown and went into reboot loop and the phone is extremely hot. I took the battery out for soft reset and try to turn on again. Phone will freeze at different screen (Lock Screen, Home Page, Samsung Logo, Powered by Android) and give two separate vibration before reboot.
I thought it is battery problem so I bought a new battery to try, but still the same problem. So I went on to backup all file before I perform hard reset. While doing that, I find out the phone can be use for longer before reboot if it was stay off for a long time. So I have this crazy idea: put it in a fridge. Surprisingly it works! The phone will not reboot anymore and I can manage to backup all file before doing anything else. Also, the phone will not charge if you plug in right after a few reboot.
Then, along with the fridge method, I perform factory reset through normal android setting. Now it will just stuck at powered by android screen while in reboot loop. I then try to flash with Odin, multiple times. Flash by Odin is complete, phone restart, then it freeze and reboot, at different screen (Installing system update, Erasing, powered by android).
Out of frustration I try with the fridge method to flash, and IT WORKS AGAIN!!!. The phone can now boot to welcome screen where you first setup your phone. However, it will then freeze again and reboot while doing so.
There was only this one time, where I left the phone off for a day after flash with a previous stock ROM, turn it on and skip as much setup as I can, finally reach the homepage screen, then will stay on without any reboot issue. I thought I finally fix it. I then power off the phone, put in my Sim Card and SD Card, power it on, then again, reboot issue appear.
I tried flash with latest stock ROM, previous stock ROM (one updates away), flash any stock ROM with pit file. I sometimes will get error code on device after flash (can't remember the exact error). I also cannot boot into recovery mode without flashing a twrp. Sometimes if success, I will get straight to Lock Screen without going through the phone welcome setup process. But again, none of these I tried can solve the reboot loop.
I may went too far and mix up all steps to the phone. Does anyone have any idea how to fix this? Or is my phone, as I believe, has a faulty motherboard that cause the reboot loop? Thanks in advance for reading through my problem!
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
oscarmaldonado said:
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
Click to expand...
Click to collapse
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
jackgan said:
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
Click to expand...
Click to collapse
Try a firmware flash before newsest. Then take the ota
anyone know if a 910t3 mother board will fit in a 910t frame? Asking cuz I wanna switch them out.
Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.
Ashu14 said:
Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.
hi i have the same problem with my mi a2. i can turn it on when is on charger but when i want to unlock the screen and to move something on screen is turning off. when i unplug the charger turning off too. do you found solution on your problem ?
Click to expand...
Click to collapse
Hello, I have the same problem. I now have to carry an external battery with me, because plugging it in is the only thing that wakes up my phone. If I don't have a charger, then I have to hold power for 30; seconds to force reset. It's really annoying, causing me to miss calls and alarms. Anyone know of any fixes? Thanks
Hey,
I am facing the exact same problem. Though I had an additional problem. My phone didn't charge when I plugged it in until I restarted it. Factory resedidn't help either.
In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc
KevMetal said:
In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc
Click to expand...
Click to collapse
tried with wifi toggle off but didn't work.
didn't tried persist partition
tried update software but still didn't work.
if there any hardware issue please let me know.