Related
I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing
I'm having the same issue. It sounds like a fastboot -w is required to wipe out userdata and cache.
Unfortunately I can't seem to get my PC to recognize my tablet in fastboot mode. I might have to send my tablet back to Samsung to get reflashed.
kolor9 said:
I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing
Click to expand...
Click to collapse
That has happened to me when I was having battery issues. I was able to keep connecting and disconnecting the charger cable until I got my tab to work again.
yeah might be that as well, i noticed strange behavior for last weeks, suddenly it started draining battery very fast or shutting down in the middle of the battery. running very slow and freezing.
when connected to pc it always goes: connect/disconnect/connect/... (hearing windows sounds for that)
i fully charged that yesterday, will try to boot today.
HOWEVER i was able to get into recovery menu, wipe/delete cache, sdcard, factory reset, etc.
might be that firmware/rom/bootstrap has been fuked up when battery died suddenly?
sharing experience
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.
You may need to open up your tab and do the battery disconnect procedure. I finally had enough with my tab and opened it up. So far I am happy again.
i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again
Thanks for the suggestion but it did not work for me...I experienced same problem you mentioned below except I had gone on vacation and my tab battery died and when I was able to recharge it, it just recycles through the Samsung logo!
Tried all the suggestions on this site and no luck so far...I'm guessing it might be time to take it in to Tmobile and see what they have to say, probably not much!
I'm not ever going to get a Samsung tablet again...Asus from here on out!!!
cx5 said:
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.
Click to expand...
Click to collapse
ceperz said:
i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again
Click to expand...
Click to collapse
if its gsm go to overcome restocking method
Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium
It's been few days since ur post. But I'll give it a shot for trying to suggest.
Try holding power button for 8 seconds to properly power off. Then charge it for a good hour before starting the unit.
Else just keep charging it. Standard times are 4 hours to get zero to 100%.
Once my power used till zero and no response what so ever even after charge 5 mins. Finally let it charge 1 good hour & it came back to life.
Good luck.
Regards cx5, on the move via xda tapatalk.
fabricatedhero said:
Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Dont see a thanks buttom i appreciate it MAN !!!
If it really happened after installing bad apps it will only wipe recovery mode
Couldn't find a similar thread so I thought i'd post my problem.
Beginning last night, after watching a video using Pulse I realized the sound wasn't working. I restarted the Nexus 7, had the sound working again, but the device froze during the video (in pulse), and then reset on its own.
Since then, the Nexus 7 will reboot, then once on, will freeze after 30 seconds - 2 minutes, reboot again, and just loop in that pattern. Sometimes when it turns out, I'm not even able to unlock it before it reboots again.
Even if I turn off the Nexus 7 when I get the chance, it will turn on itself and continue the freeze -> reboot loop.
Right now I've been letting the loop continue until the battery runs out to see if it fixes the problem. Until then, has anyone else faced this issue? Any solution?
Details: An unrooted Nexus 7, few apps, only thing off market was to enable flash, got the device 2 weeks ago
Bump to see if anyone has a solution.
Will post a video of what happens when I get home from work.
Haven't heard of this before.... what happens if you boot into bootloader? Perhaps you just need to do a full wipe and re-install.
It actually freezes on bootload.
When I do a force turn off (power and volume down), it will turn off, then turn on by itself and continue the bootloop
Will try to upload a video of what is happening soon.
I have the exact same issue.
Can't restore or reflash because it won't go into bootloader\recovery.
What it WILL do is reboot incessantly. SUffice it to say I'm pretty pissed. This just happened suddenly.
I had not rebooted in a few days so I rebooted, and now it won't stop.
The only change I have made is I disable the magazine app because I read that it's a battery hog and I just do not use it. I can;t imagine disabling the magazine app would result in a full on boot loop where even recovery fails...
-M
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
kevlars9 said:
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
Click to expand...
Click to collapse
I have the same kind of issue. Left to itself the device reboots until the 'Google' display every 1 minute or so. When trying to get into bootloader it freezes when the Android on its back shows up....
So it seems no flashing is possible. BTW this happened when I tried to uninstall an app, similar scenario to some others reporting this type of problem.
I guess the next stop is the Chocolate Factory helpline :/
I contacted the Googleplex helpline at 6 am Pacific time and Anthony kindly promised a replacement unit for next week... No tech explanation or other info was revealed. Purchase from Google Play in the UK.
Finally given a solution, though a very annoying one.
Basically, since you have about 30 seconds - 2 minutes everytime it loads up, I was just told to try and see if I can factory reset from settings within that time frame. Took a 3 attempts (sometimes it would reboot while loading), but eventually got the factory reset going. Luckily I've only had this thing for less than 2 weeks and didn't have much stuff needed to back up.
Right on, glad to hear you got it sorted - in my case. though, this solution would not have worked, as mine never booted all the way through but got stuck at the boot logo (just in case others are reading this with similar problems). So it sems there are at least 2, possibly more, problem scenarios of this type.
My replacement unit from Google Play just arrived - impressed by the speed of proceedings (inside 2 working days from reporting to receiving in Scottish Highlands). Let's see how this one pans out...
HEy problem plss help Boot loop on N7
Hey my nxus wint get out of a boot loop and i cant get in to recovery mode by bootloader this have ben going on for some time and it started when i flashed a new rom ( Paranoide android )on my Nexus 7:fingers-crossed:
Eternal 2013 Nexus 7 reboot loop
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
I have a very similar problem. However, it began from no changes to my system. I am on Legolas' All-F2FS Recovery and the SlimKat F2FS system. At first I got stuck in a boot loop, and could get into fastboot, but cannot boot back to the custom recovery. Now, I get past the bootloop but cannot get past the loading screen, and still cannot get into recovery. I've tried wiping cache, I've tried reloading the recovery via fastboot -- but since all I have is fastboot access, I don't know what else to do. All my partitions are F2FS, so I am afraid to try moving back to any standard ext4 recovery. I am very interested in this thread, as I feel our issues are related. Keep me updated, and I will do the same if I find anything useful.
Any help I suspect is appreciated by more than just myself.
BTW, removing back and leaving battery unplugged for a while (which had helped with other bootloop issues) did not fix this one, nor did the cold boot from fastboot with usb plugged in to boot recovery.
superdave132 said:
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
I found a fix that worked for me!
I have Minimal ADB & Fastboot installed on my computer. If you're comfortable with the idea of connecting to your Nexus when it is in bootloader download (Fastboot mode), you can try this.
First, I downloaded a full reset file from https://developers.google.com/android/nexus/images:
The ones you'll want are either:
this one for 4.4.2
this one for 4.4.4
I unzipped the appropriate one directly into my ADB directory, and then executed the "flash-all" script by literally typing in "flash all" into the prompt.
This installed all of the default bootloader, recovery and system back onto my Nexus 7 (btw two names for the nexus are "Grouper" and "nakasi"). Then, I was able to clean boot into a reset Nexus 7 system. It was still unlocked. From there, I was able to reinstall a custom recovery (I went with TMW), and even reinstalled a custom ROM (I always stick with SlimKat, personally).
Note: You should also wipe data from the custom recovery once you've installed it.
Second note: In order to be able to load this stuff, I believe you have to unlock your system
To unlock your system in fastboot: fastboot oem unlock
I sincerely hope this helps you (and anyone else stuck in a similar situation to where I found myself). I had completely set my system up with F2FS, and now I'm back to EXT4. BUT, I have a custom recovery, custom rom and root access. Can't complain.:highfive:
Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.
Bump..
Anyone?
bump
Phone crapped out low batt. Plugged in rebooted, got to SIM card unlock screen, held power to force reboot (this the way to recalibrate battery on stock ROM, reset, charge to 100%.) Now, no matter I am stuck in a boot loop. 10 Mins nothing happening... Can still access recovery but unless default directory holds latest Lineage OS ZIP? (Is it still there?) Then may have to pull merged SD, format then manually download LOS on laptop & reflash.
Dayum!
fleamour said:
Phone crapped out low batt. Plugged in rebooted, got to SIM card unlock screen, held power to force reboot (this the way to recalibrate battery on stock ROM, reset, charge to 100%.) Now, no matter I am stuck in a boot loop. 10 Mins nothing happening... Can still access recovery but unless default directory holds latest Lineage OS ZIP? (Is it still there?) Then may have to pull merged SD, format then manually download LOS on laptop & reflash.
Dayum!
Click to expand...
Click to collapse
Confusing lines! Please, write clearly and provide useful information about your phone, it will help XDA members to help you..
Things i got,
You had stock ROM before bootloop happened and now you want to flash lineageOS, right ?
Things missing between,
Does your phone have unlocked bootloader ?
Does it has TWRP recovery installed ?
If not unlocked, then which version of stock ROM you had ?
Sorry, so many words, so little info!
I am happily running latest LOS nightly & latest TWRP on a Moto G4 Plus Athene build.
I once read that to recalibrate battery you needed to hold power button till phone turns off, continue to hold till on again. You would then charge to 100%. Charging to 80% mostly gives false threshold, hence turning off when rang.
I successfully booted phone to SIM unlock screen then held power till off then on, problem being it now sits at boot screen for all eternity! Rebooting from recovey same story. Turning off then on same story. Is there anything else to try before attempting reflash?
fleamour said:
Sorry, so many words, so little info!
I am happily running latest LOS nightly & latest TWRP on a Moto G4 Plus Athene build.
I once read that to recalibrate battery you needed to hold power button till phone turns off, continue to hold till on again. You would then charge to 100%. Charging to 80% mostly gives false threshold, hence turning off when rang.
I successfully booted phone to SIM unlock screen then held power till off then on, problem being it now sits at boot screen for all eternity! Rebooting from recovey same story. Turning off then on same story. Is there anything else to try before attempting reflash?
Click to expand...
Click to collapse
Try to clear delvik-cache and cache from
TWRP> wipe > advance wipe (don't wipe "data"). then reboot. (As delvik-cache is deleted, it will take time to rebuild delvik files)
If it take more time than 10 minutes, you will have to reflash.
In case, if any app store your data and you don't want to lost it (say massages/chat history/etc), then you can first give a try by dirty flashing.
For dirty flashing,
Download lineageOS.zip and gapps.
Move it to phone or directly flash from external sdcard, just wipe cache and delvik-cache, don't wipe "data" it will erase everything (apps and app-data)
If still doesn't boot after 10 minutes, then you will have to clean flash the ROM.
So is this due to instability?
Thanks!
Clean flashed but bootloop continues, do I need to flash stock then try again?
Edit: We in, hand up skirt!
Hello,
I need batterystats.bin for Note 4 SM-910c or exynos that is properly calibrated as am having a problem to boot without connected to power source.
The problem happened when I was calibrating my phone battery as it was always turned off around 70%-60%..quite intermittently. So I decided to try fully calibrate it by deleting the batterystats.bin (only) then keep using it until it empty then fully recharge it full for a few hour.
However the phone suddenly turning off and on quite a few times so I decided to pull the battery out and put it back. But after puttin it back I can't even start the phone at all, even I connected it to power source, it won't be able to start unless I boot into download mode and restart from there (cancel option). I cannot even get into recovery mode. Only download mode is possible.
I've tried flashing official rom a few times with older and latest firmware but to no avail. I even repartitioned using the pit files. Everything booted perfectly except that I can't start my phone properly and can't even get the phone on without connecting to power source.
Please kindly share your batterystats.bin for me. I'd like to try and put it into data/system manually. Hopefully it can solve my problem.
Thanks in advanced.
This is my phone's details: