Database Users

Galaxy Tab is restarting forever (not flashed)

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

Nexus 4: Boot loop with locked bootloader and no USB debugging - HELP!!!

Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!

ThuanBui said:
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
Click to expand...
Click to collapse
I'm having the same problem!

For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).

andr0idfreak said:
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
Click to expand...
Click to collapse
I've done this many times but still no luck

ThuanBui said:
I've done this many times but still no luck
Click to expand...
Click to collapse
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can

Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.

monkeying. around said:
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Click to expand...
Click to collapse
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:

sideloading 4.4.2 and stuck on boot loop
ThuanBui said:
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
Click to expand...
Click to collapse
bro mime nexus 4 has stuck into boot loop after upgrading from 4.4 to 4.4.2 .i was sideloading the zip dont know whats the issue ......i was rooted but went to stock via nexus roottool kit to get OTA . any suggestion

​
joshnichols189 said:
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
Click to expand...
Click to collapse
all you got to do is download the toolkit and flash the software your phone is using and put it in fastboot and begin
:good::good::good::good::good::good::good:

locked bootloader wont unlock

Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers

truebattleaxe said:
Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers
Click to expand...
Click to collapse
also I wanted to add. I have the android sdk installed and all drivers installed properly. as well as adb/fastboot.

Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
hey slow cobra. yes fastboot does recognize the device. however fastboot oem unlock doesn't do anything.

Nexus stucked on boot after battery fully discharged

Hello guys,
I have a big problem with my girlfriend's Nexus 4 with CM11
She left the phone COMPLETELY discharged (0%) for the whole night (about 9 hours)!!
The morning after she put it on charge (with power supply) and when she tried to restart it remained stucked on the boot animation...and then we realized that something was wrong.
I tried this to recover:
1) Wipe cache / Dalvik cache KO (It starts then upgrades applications then remain stucked on "Starting applications")
2) Deleted batterystats.bin KO
2) Full wipe + flash CM11 KO
3) Full Wipe + flash KO Paranoid Android
4) Flash stock (with stock recovery) KO
When I say "KO" I mean that the nexus starts-up but remain stucked on the boot animation (except for the test 1)
I can, however, enter fastboot mode.
I honestly don't know what to do anymore
Do you have some ideas?
Thank you very much!

Is the imei properly displayed?
Flash back to stock 4.2.2 then try flashing back to cm11. Make sure you have a compatible modem and bootloader for cm11.

Do you have the red light?
If yes, look here
http://forum.xda-developers.com/showthread.php?t=2250454
Personally, I managed to charge the battery with wireless charger only.
Unleashed by my Nexus 4

I had the same problem but i somehow got out of it. Don't worry if i can remember how did it solved it i will surely post it.
Sent from my Nexus 4

Use a toolkit to flash the factory image. This should solve your problem. Good luck.
Gesendet von meinem LG-P880

I tried to flash stock 4.2.2 and it worked but unfortunately the nexus didn't recognize the sim card .
Searching the internet I found lot of people talking about a weird IMEI code. Well, I checked mine and it was blank!
Yes, there is no more IMEI code and the phone si actually like a tablet.
Anyway, I contacted the amazon's customer care and they opened me a RMA.
Thanks to all of you for the help

troubleshooting, bricked overnight

Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.

PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/

I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?

PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.

I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.

PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look

That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...