Hello,
Hopefully I'm in the right place for posting something that seems to be this simple. The start of my problem is that the tablet will not stay off. When I try to shut it down, it shuts down normally, but then it starts to display the battery icons like it is plugged in and charging, but it is not connected to power. I can leave it in sleep mode and the charging thing will not happen, but turning it off displays the power charging screen and it further drains the battery. I figured something is screwy with the system so I would try to reset it to factory defaults. Now I have the other problem...
So I am trying to restore to factory defaults and I know to do this I have to start from off and hold down the up volume and the power button for a few seconds and as soon as the tablet starts to turn on release the power button but not the volume up button, and it should get me into the recovery/download screen. Unfortunately that is not working. I hold down the Volume up button and briefly hold the power button (3 or 4 sec or so) and I see the Samsung Galaxy Tab 2 7.0 startup screen and let go of the power button (still holding the Volume up button). Next I see the spinning blue circle around the Samsung logo and the tablet reboots. I can release the volume up button at any time after that and the results are the same, it just reboots. It's like it isn't seeing the volume button.
I have tried using the volume Down button instead of the volume up button but that too is just like I am not pushing any volume button at all. Once the tablet is on, the volume buttons function normally, so the switches are good.
Since I got this tablet used could someone have loaded something onto it preventing it from being rebooted into recovery/download mode? Maybe some custom firmware or something. I'm at a loss as to where to go next. Since I can't boot into recovery/download mode I can't get into Odin.
Any help is appreciated.
Rick
Hi. The tablet isn't rooted, is it? Can you try to boot it into download or recovery with the "quick boot" app from google play?
I don't think it is rooted, but I can't tell for sure since I can't connect to the Google play store. I tried downloading using the web browser, but my battery dies before if finished. I'll try swapping batteries and see what I can figure out. Thanks for the idea.
Rick
No, the device is not rooted. it also is not charging and I had a heck of a time getting it to connect to the play store. I think I need to try and reload the OS, but without being able to get into ODIN, or reboot into recovery, I'm not sure how to proceed. any suggestions?
When the battery thing appears do the power- volume up thing and hold it until the gtab logo appears.
I've tried that, and it just boots up as if I wasn't holding the volume button at all. Once the tab is booted, the volume buttons work as normal. I've even tried putting a different power/Volume/IR unit in (from a working tab with a broken screen) and that didn't make a difference.
I left the tablet all weekend and it just keeps showing that it is charging when not plugged in. By Monday the battery was 100% dead. It won't even charge. If I replace the battery with a battery from a working unit I'b back in the same place where I can't get it to boot to Recovery/download.
Hello,
I own a Nexus 5 (rooted, CyanogenMod11-M10, ClockWork recovery).
I had found a boot animation that I liked. I tested it but the images where smaller (768x1280), they had a black border around them which I did not like, so I decided to resize them to 1080x1920 also taking care to modify desc.txt with the new size.
But, upon reboot the screen went first crazy for a split second and then went completely black...
I cannot do anything now, I tried to access the phone with ADB but it tells me that I have to answer the onscreen question... I cannot even see the screen anymore
Is there anything I can do short of popping the back and disconnecting the battery?
Thanks
M
--- EDIT UPDATE
I tried Volume up (OR Volume down) + Power to reboot, it did reboot but the same problem appeared, then I tried Vol up AND Vol down + Power and it looked like the phone powered down (I could not see anymore the faint backlit screen)... Then I tried Vol up AND Vol down + Power to reboot in recovery but it does NOTHING... only the Power button alone works but it boots again normally and then again the same problem appears.
--- EDIT UPDATE SOLVED!!!!!!!
It just needed to rest apparently...
As I said I've powered it off by holding down volup, voldown and power... nothing was working: I could not boot into reveory and even the battery icon was not showing up, but after 15 minutes I've tried to reconnect the USB cable and this time the battery icon showed up... At this point I knew could reboot into recovery, so I did :laugh: then I have mounted /system and with ADB I've opened a shell so that I could delete the damned bootanimation.zip file... after that the phone rebooted OK (minus that glorious boot animation)
Yet, if someone has any idea why it had to wait off few minutes, please, add to this conversation.
I have a Moto G XT1034 that is stuck in a boot loop. I am not able to get to fastboot or recovery, it just keeps rebooting over and over again. It started at about 50% battery, now it's at 0% even though it's been plugged in for most of that time. This device has an unlocked bootloader, is rooted, and has been running kitkat for almost a year. Nothing that I can think of has changed today.
Things I have tried:
Holding vol up + vol down + power for 4 seconds
Holding vol down + power for 4 seconds
Holding power for 120 seconds
Letting the battery drain completely, and then plugging it in. It just starts with the reboot cycle again.
Any ideas?
That doesn't seem right. Try holding volume down and power for longer than 4 seconds.
Here's a video of me holding vol down + power for 120 seconds, as advised in Q28 of this sticky. Doesn't get me to fastboot.
I have a second moto g here, and have swapped the batteries, so the broken one has a fully charged battery. The bootloop continues when fully changed. Video here. Holding vol down + power for a few seconds, or 120 seconds also doesn't do anything when fully charged.
TravisTX said:
I have a Moto G XT1034 that is stuck in a boot loop. I am not able to get to fastboot or recovery, it just keeps rebooting over and over again. It started at about 50% battery, now it's at 0% even though it's been plugged in for most of that time. This device has an unlocked bootloader, is rooted, and has been running kitkat for almost a year. Nothing that I can think of has changed today.
Things I have tried:
Holding vol up + vol down + power for 4 seconds
Holding vol down + power for 4 seconds
Holding power for 120 seconds
Letting the battery drain completely, and then plugging it in. It just starts with the reboot cycle again.
Any ideas?
Click to expand...
Click to collapse
power off device....then fastly press volume down + power button for 4 secs and release
---------- Post added at 02:57 PM ---------- Previous post was at 02:52 PM ----------
TravisTX said:
I have a Moto G XT1034 that is stuck in a boot loop. I am not able to get to fastboot or recovery, it just keeps rebooting over and over again. It started at about 50% battery, now it's at 0% even though it's been plugged in for most of that time. This device has an unlocked bootloader, is rooted, and has been running kitkat for almost a year. Nothing that I can think of has changed today.
Things I have tried:
Holding vol up + vol down + power for 4 seconds
Holding vol down + power for 4 seconds
Holding power for 120 seconds
Letting the battery drain completely, and then plugging it in. It just starts with the reboot cycle again.
Any ideas?
Click to expand...
Click to collapse
flash costom recovery....using adb fastboot command
Thanks for the replies.
I am not able to power it off. I have found two ways of "powering off" which are to either let the battery drain, or to hold buttons during the black screen part of the boot loop.
If I wait for the black screen part of the boot loop, and quickly press vol down + power, it will stay black as long as I'm holding those buttons. If I hold them for 4 second and release, it then enters the boot loop a few seconds later. If I hold them for 120 seconds and release, it does the same thing a few seconds after releasing.
I am not able to open an adb connection to the device. "adb devices" shows no devices in all phases of the boot loop.
To predict future concerns, I have the proper drivers, and have used adb quite a bit to work with this device. Also I can use adb on the second moto g with no problems. So my pc is set up and configured correctly.
TravisTX said:
I am not able to open an adb connection to the device. "adb devices" shows no devices in all phases of the boot loop.
To predict future concerns, I have the proper drivers, and have used adb quite a bit to work with this device. Also I can use adb on the second moto g with no problems. So my pc is set up and configured correctly.
Click to expand...
Click to collapse
Try this topic and see if it can help you:
http://forum.xda-developers.com/moto-g/help/xt1032-bricked-please-help-t2980601#post57698711
Just remember to acess it when you have time to do all the tutorials that I've linked. Doing it with attention probably will solve your problem;
:good:
BobDiaz thanks for the suggestion. I still can't get to fastboot though, so this never does anything other than "waiting for device" If i plug in my second moto g, of course, then mfastboot works fine once I boot into fastboot.
TravisTX said:
Thanks for the replies.
I am not able to power it off. I have found two ways of "powering off" which are to either let the battery drain, or to hold buttons during the black screen part of the boot loop.
If I wait for the black screen part of the boot loop, and quickly press vol down + power, it will stay black as long as I'm holding those buttons. If I hold them for 4 second and release, it then enters the boot loop a few seconds later. If I hold them for 120 seconds and release, it does the same thing a few seconds after releasing.
Click to expand...
Click to collapse
in black screen you must do vol+power process 2 times..... first time nothing happen... in second time you press the power+ volume down the fastboot menu is shown...
That's very strange. Makes me think there's a hardware problem. The only point I can mention (sure you've tried this, but just to be sure) is to keep it simple: if your phone doesn't reboot after holding the power button down for about 10 seconds (with or without pressing the vol down button), then you almost certainly have hit a hardware issue. Especially if you've taken the lengths of swapping batteries and not seeing a difference.
I know that with my 1st gen Moto G, when I'm stuck in a boot loop after too much mucking around, I just hold vol down and power for ten or so seconds, and then it boots into fastboot mode. That's how the phone was designed. Best of luck.
Correction: the phone shuts down in just over ten seconds, and when it does I let go of the power button but continue holding the volume down key for several more seconds before I reach fastboot. As well, since I'm about to use fastboot, I've always got my phone plugged into USB when I do this. But, I just tried it unplugged, and it worked the same.
Try pulling the battery then holding up on volume and power button and home same time
Sent from my SM-N900V using XDA Free mobile app
TravisTX said:
BobDiaz thanks for the suggestion. I still can't get to fastboot though, so this never does anything other than "waiting for device" If i plug in my second moto g, of course, then mfastboot works fine once I boot into fastboot.
Click to expand...
Click to collapse
Hi TracvisTx, T
I just ran into exactly the same issue as you have mentioned here.
After doing downgrade from Lollipop to Kitkat, my moto g is stuck at bootloader warning. It power on's, gets stuck on warning, reboots. Does not charge to more than 0%.
I was wondering if you could come out of this issue and how? I am also unable to enter into fastboot mode! I have tried all the described combinations of power + vol (up/down) buttons.
Please help.
Thanks,
@beerbarfly - Hold vol down (or up) while turning on wall charger.
lost101 said:
@beerbarfly - Hold vol down (or up) while turning on wall charger.
Click to expand...
Click to collapse
@lost101, That's the entire issue. I am unable to enter into fastboot mode.
beerbarfly said:
@lost101, That's the entire issue. I am unable to enter into fastboot mode.
Click to expand...
Click to collapse
You said the phone is bootlooping - hold vol down (or up) immediately after reboot.
lost101 said:
You said the phone is bootlooping - hold vol down (or up) immediately after reboot.
Click to expand...
Click to collapse
lost101,
The screen blanks out, then it shows battery charging (0%), then goes to "bootloader unlocked warning" and then back to black screen.
In all this, even if you keep vol + power buttons pressed, nothing happens.
Infact, if it is in blacked-out screen step, and i keep these buttons pressed, it remains in black-out, does not even go to charging screen....
Looks like that is what is called as bricked phone
beerbarfly said:
The screen blanks out, then it shows battery charging (0%), then goes to "bootloader unlocked warning" and then back to black screen.
In all this, even if you keep vol + power buttons pressed, nothing happens.
Infact, if it is in blacked-out screen step, and i keep these buttons pressed, it remains in black-out, does not even go to charging screen....
Click to expand...
Click to collapse
Only hold either Vol up or down - forget about power button.
I rebooted my phone just now and instead of booting back up it only boots to recovery. I did a fresh rom install but it won't boot.
I had noticed that the volume down button had been acting up recently. So, I think the volume down is pressed down constantly forcing the phone to recovery. I think this may have been caused by the really humid environment I'm currently in, however, before rebooting the phone was working relatively fine apart from the unresponsive volume down.
Is there anyway I can force the phone to boot to the rom in this situation?
please check this video
https://www.youtube.com/watch?v=DBv_95ZCDvc
and see if it helps.
dud3me said:
I rebooted my phone just now and instead of booting back up it only boots to recovery. I did a fresh rom install but it won't boot.
I had noticed that the volume down button had been acting up recently. So, I think the volume down is pressed down constantly forcing the phone to recovery. I think this may have been caused by the really humid environment I'm currently in, however, before rebooting the phone was working relatively fine apart from the unresponsive volume down.
Is there anyway I can force the phone to boot to the rom in this situation?
Click to expand...
Click to collapse
That's a good idea--disabling the vol down button, and there may be a way.
I'm thinking you could pop the cover and clean out around the button--maybe unjam it if it's jammed. Maybe it could be lubed with a very light lubricant? Never heard of anyone lubing their phone buttons, I don't see why not.
Hi,
I have a MTCD-KGL for over an year now. The only issue I have with the device is that after power up, sometimes, not always it freezes after start.
Precisely:
- This happens once every 2-3 boots
- This happens regardless if it does a real power up or wakes after a sleep
- The freeze usually happens 10-15 seconds after startup, however sometimes it might happen immediately or take up to 3-5 mins to freeze
- When I set it up to sleep instead of shut down (after car power off) and the radio app has been turned on before shutting down, after power up of the car and device it would usually start the radio app again and turn on the sound and freeze only after this. Same is true for my navi app (Here to go) i.e. it would start the navi app after boot and then freeze. Sometimes I'm able to make a click or two before it freezes
- If it makes cold start (i.e. had been shut down) then it shows the launcher UI
- When it's frozen I could reset it via the reset button, however I can't power it off via the power button
- When it's frozen, the touch screen doesn't respond at all, while hardware buttons only make beeping sound. However nothing changes, no matter what button I press. Turning the volume knob makes multiple beeps, however the volume doesn't change. Pressing back, home or anything else also makes beep but no effect
- Shifting to reverse doesn't show the revers comer either
I have updated to numerous different firmwares, both KGL and others as well numerous KGL MCUs, however with all combinations the problem persists.
The device is not rooted yet, I could do it if it would be from any help.
Any idea? I don't know what might be causing this freeze, which is keeping the last snapshot on the screen and buttons beep, radio plays, but nothing else happens. Apparently it's not software problem, because updates of the firmware and the mcu would have solved it. So it should be a hardware one. Any idea where to look at?
Thanks and regards
flyzepp
flyzepp said:
Hi,
I have a MTCD-KGL for over an year now. The only issue I have with the device is that after power up, sometimes, not always it freezes after start.
Precisely:
- This happens once every 2-3 boots
- This happens regardless if it does a real power up or wakes after a sleep
- The freeze usually happens 10-15 seconds after startup, however sometimes it might happen immediately or take up to 3-5 mins to freeze
- When I set it up to sleep instead of shut down (after car power off) and the radio app has been turned on before shutting down, after power up of the car and device it would usually start the radio app again and turn on the sound and freeze only after this. Same is true for my navi app (Here to go) i.e. it would start the navi app after boot and then freeze. Sometimes I'm able to make a click or two before it freezes
- If it makes cold start (i.e. had been shut down) then it shows the launcher UI
- When it's frozen I could reset it via the reset button, however I can't power it off via the power button
flyzepp
Click to expand...
Click to collapse
Its an older unit and I would tend to think that your system is running out of memory.
I tried doing a System Update on mine but the dang head unit can't find the .img file in any slot nor usb port.