Hey Guys -
I was excited today to update my Shield Tablet (Original Wi-Fi (Not K1) to Nougat today and finished recently. Unfortunately, when I plug it up to change, it freezes for a minute then goes into a boot loop. To get out of the loop, I unplug it from charger. In fact, when I boot to bootloader menu, the volume keys won't allow me to select an item when plugged in.
My original charger broke long ago but for over a year now have been using a 2.4A charger without any issues. I tried charging it using a 1.2A, but still went into loop, too. Don't know why it only decided to do this after an update. Any suggestions?
BTW - here's how I updated if it helps...
1. Flashed 4.4.0 via ADB/Fastboot
2. Flashed TWRP (twrp-multirom-20160410-UNOFFICIAL-shieldtablet_m)
3. Copied SuperSU (BETA-SuperSU-v2.71-20160331103524)
4. Installed FlashFire
5. Downloaded OTA for Nougat and flashed it using FlashFire (retaining root & Recovery - default options)
I looked up the OEM power specs and says 2.1A so going to try that out. I can see it having issues with hardware, but not when only change is software - plus - why when charging 1.2a did I have issues? Odd
Any suggestions or thought? Thanks!
I have the 32gb LTE tablet and mine behaves exactly the same way since I updated to Nougat using the same steps you did (after which a factory reset didn't solve).
I narrowed down the bootloops to when I use a Samsung charger (both Adaptive Fast Charge compatible or the older non fast charge ones). As soon as I plug it in to one of those it goes in a boot loop and doesn't come out until I unplug. The boot loops don't happen if I use an Apple iPad charger but it charges EXTREMELY slowly. It went from 0% to ~50% in about 7 hours!!
i had the excat same problem guys and there is a real easy fix check out this thread but make sure you get the right blob file
https://forum.xda-developers.com/shield-tablet/help/flashing-5-0-update-k1-flashfire-t3554089
Related
Hey guys,
yesterday I bought my TF300T and was satisfied.
It's the first tablet and actually it should be a gift.
Yesterday evening I came home and plugged it to charge. Everything went fine.
After a while I recognized, it stopped charging, but wasn't full.
Today I went to the shop and we figured out that the data cable was broken.
Replaced.
Later this day I came home (with fully charged device) and used it some time. Shut it down.
Then I plugged it to the wall: Nothing happened.
I tested it first with a different USB device: No current - no charge (Galaxy S2).
Then I tried a different AC adapter. Worked on SGS2, but not on TF300T.
Then I started it again and it shew a screen with a red triangle. Then it rebooted.
After thist it now seems to have a bootloop.
It's stucked at the Asus boot screen.
I already made a wipe through the recovery menu, but it changed nothing.
So, to make a summary:
- first tablet
- broken data cable
- broken AC adapter
- broken bootloader
I will return it tomorrow and hope they still have one new on stock (just to reset my "experience").
But I still want to know if there "would" be a solution for this problem.
On my SGS2 I can use Odin and just flash a new firmware.
What's on Asus?
If you can get to adb you might be able to flash new firmware. But unfortunately Asus has nothing like Samsungs Odin You could try the sd card method, stick the firmware on an sd card, reboot into recovery and hope. Google it for more info. I would just take it back though
Hi All,
Just thought I'd share my.. well so far resolution to the problem I was facing. So I purchased a Nexus 5 from eBay and sure enough it ran out of the 4% battery it had, however after leaving it to charge I noticed once turned on the battery was still at 0%. I tried a different charger (Plus and USB) and again still didn't work. I read various fixes such as leaving the phone turned off and charging it for an hour, also disconnecting the battery from the mainboard and holding the power button for 15 seconds but neither worked.
I then went to flash the stock ROM but to do this it's recommended you have 60% battery so I wasn't going to risk it as it may end up being bricked but as I got to that stage I looked back at my Nexus and it was 9% charged. It seems that through following the Stock ROM flash tutorial I put the phone into "USB Debugging Mode" while connected to my laptop, it seems in this mode it charges fine. To me it seems there is a software issue (may very well have been caused by the restore carried out before the phone was sent to me" I'm going to leave it charging via USB and perform a full stock flash and root hopefully this should permanently sort the problem.
Ok
Sent from my Nexus 5
Dear XDA-community,
My Nexus 5 (D821 32GB) only charges while in bootloader mode.
Symptoms:
It spontaneously stopped charging in a normal way yesterday. By that I mean, that my Nexus 5 does not charge while switched on. While switched off, it loops the following way: it switches on, shows battery logo with the lightening, then goes to the logo that shows an empty battery (even though it isn`t empty, this logo usually shows loading progress, in my case it is not animated, meaning it just stays "empty"), after what the phone switches off and it goes back on again.
My temporary solution:
To circumvent that, I found out that it always charges while the bootloader screen is on (bootloader version: HHZ20h), and sometimes charges while in recovery mode (I have TWRP 3.0.3.0). So I used this method to load the battery.
My troubleshooting:
After extensive search on Google, the only reasonable thing that was said in one of the forums was that probably Android 6.0.1 detects some kind of danger to charging my battery and refuses to do it (I had the Xtrasmooth 6.0.1 custom rom with Xposed installed, stock kernel). Next thing I did was installing the app "Ampere" which told me that my phone`s battery, even though close to 3 years old, is in "good condition". Assuming that it is the OS that is messing with my charging issue, I completely wiped my phone, only leaving TWRP and an unlocked bootloader.
Please note:
I have tried all kinds of cables and chargers, even tried connecting to the PC to charge. My original charger works perfectly fine, and the charging port itself is clean. Like I said, the phone charges only while in bootloader. Battery life is also normal.
Question to you guys:
Here I am, with a fully wiped Nexus 5, ready to install a new custom ROM and being unsure what the issue might be.
Can anyone help me get my phone back to charging while the phone is on?
Is there a way to separately flash/work with usb connector drivers?
Thank you in advance :fingers-crossed:
Update 1:
Flashed latest factory image and returned phone to complete stock, problem persists. Why would the charging port not work while the phone is on?
Update 2:
Enabled USB debugging. Phone is not only not charging, but also cannot connect via USB to my computer as MTP (it is simply not recognized at all). In Windows Device Manager, it does not show up at all, even under "Other devices" (I uninstalled all possible drivers to see if it Windows 10 would react to it getting plugged in, it does not). I believe the problem is not the hardware of my phone (as it can charge and connect to the PC while in bootloader, fastboot commands work, could not manage to get the ADB commands to work in recovery), it must be some kind of internal driver issue.
Hi,
I have exactly the same issue. I have tryed all. I flash my Nexus 5 to Android 5 and the to 4.4.4 but nothing worked. Have you being able to fix the problem?
I also think this is not a hardware issue since I have changed the charging port and nothing happened and the same with the battery.
Santiago
It could be a defective USB flex cable. There are 4 pins: 2 for charging, 2 for data transfer. It's possible for the phone to charge and not be recognized as a phone when connected to a computer.
audit13 said:
It could be a defective USB flex cable. There are 4 pins: 2 for charging, 2 for data transfer. It's possible for the phone to charge and not be recognized as a phone when connected to a computer.
Click to expand...
Click to collapse
5 pins...
Yes, there are 5 pins but I throught 2 were used for data, two for power. I admit I was wrong in this belief.
http://pinoutguide.com/CellularPhones-A-N/smartphone_microusb_connector_pinout.shtml
Hey guys,
I've got a Google Pixel phone today and it's having a major problem. Battery won't charge, at all. Here's what I did:
1. Checked and cleaned the USB-C port
2. Checked with 2 chargers (A normal USB 2.0 type charger and a LG G6 fast charger)
3. Tested it with 2 USB-C cables. One is from the LG G6, the other one is the original that came with the phone.
4. Tried charging it using the laptop USB ports (3.0)
5. Ran a battery tester which said the battery was alright (an apk)
Android version running: 8.1.0 with Feb. security patch
The seller also said that the microphone and possibly the loudspeaker don't work. I would love to charge the phone and try the Android P BETA program on it, see if it solves anything.
I've ordered a new battery from Sweden (possibly not original, but I've read that it's alright)
Any tips?
Thanks!
Edit: The phone indicates that the battery is charging (both when it's shutdown and plugged in). The battery is at 1% now and the phone shuts down immediately - won't power-up at all.
I have a similar issue with a Pixel I bought refurbished (might just return it) - but the battery won't charge past 75%; got up to 84% one time, though. Even plugged in, once the battery gets to its 'max', the percentage will actually go down a little, to around 70% (if it stays plugged in at >70% then it usually goes down, with screen off). I also noticed mine doesn't seem to charge at all when powered off (probably a big warning sign) and also sometimes won't charge until booted up and unlocked (sucks to pick up your phone that's been plugged in a couple hours to see 4% battery with the charging indicator on the status bar says the phone is charging....).
It WILL charge if it gets booted into (TWRP) recovery - so, if your phone stays on while connected to laptop, try booting into bootloader and fastboot boot twrp-latest.img (easy to find thread for that, or just go TWRP.me website and find it there).
If that doesn't work (locked bootloader, etc.), try charging it while in the stock recovery, but I don't think it'll give you an indicator. If all those fail to give it a charge try charging inside bootloader, plug and unplug a few times, make sure USB connectors are clean. Good luck with the replacement battery, screen/digitizer can easily get messed up during dissasembly...
Edit: noticed you said won't power on at all, if you can't even get to bootloader (vol down+power with phone off) then battery or USB assembly is probably no good. Does LED flash red on the top of phone?
dacdoug said:
I have a similar issue with a Pixel I bought refurbished (might just return it) - but the battery won't charge past 75%; got up to 84% one time, though. Even plugged in, once the battery gets to its 'max', the percentage will actually go down a little, to around 70% (if it stays plugged in at >70% then it usually goes down, with screen off). I also noticed mine doesn't seem to charge at all when powered off (probably a big warning sign) and also sometimes won't charge until booted up and unlocked (sucks to pick up your phone that's been plugged in a couple hours to see 4% battery with the charging indicator on the status bar says the phone is charging....).
It WILL charge if it gets booted into (TWRP) recovery - so, if your phone stays on while connected to laptop, try booting into bootloader and fastboot boot twrp-latest.img (easy to find thread for that, or just go TWRP.me website and find it there).
If that doesn't work (locked bootloader, etc.), try charging it while in the stock recovery, but I don't think it'll give you an indicator. If all those fail to give it a charge try charging inside bootloader, plug and unplug a few times, make sure USB connectors are clean. Good luck with the replacement battery, screen/digitizer can easily get messed up during dissasembly...
Edit: noticed you said won't power on at all, if you can't even get to bootloader (vol down+power with phone off) then battery or USB assembly is probably no good. Does LED flash red on the top of phone?
Click to expand...
Click to collapse
Hey, thanks for the tips.
I unfortunately tried all of that before it wouldn't boot up anymore, so no luck there. Also, no indicator at the top, battery is probably alright, might be a software issue or something, but can't tell since I can't update it to Android P or atleast downgrade it. I guess I'll have to wait for the battery to arrive and then try it like that. Hopefully that works.
There's a lot of aspects to this problem at this point, I'll try to be detailed.
I was recently given a bricked Verizon S7 (SM-G930V) to work on (full stock rom). The battery is completely dead, and when plugging it in to a high power charger it shows the recovery booting screen for 1-2 seconds, then black screen, then recovery booting again. So the recovery seems to be broken, and its putting it into a bootloop. From what I've been able to find over the last few days I believe it was caused by either a bad ota update, or it loosing power in the process of updating.
Im able to get it into download mode, but the recovery seems to be completely broken. I've left it on a charger overnight four times (combos of plugged in, on a pad, in download mode, and looping) and it hasn't charged at all.
When its on a high power charger I'm able to get it into download mode, but it dies as soon as i try to swap it to my pc. I have a high power official samsung wireless charging pad, but when its only on the pad its completely unresponsive. If I plug it into the charger and have it on the pad at the same time, im able to get it into download mode and switch it and get it to show up in odin.
I've tried flashing the latest verizon branded firmware, as well as the unlocked firmware (with various combinations of odin versions and settings) and I either end up with an error on the phone (odin/firmware too old) or it just completely fails and the phone turns off. Even when deselecting auto reboot in odin, after a failed attempt (complete(write) operation failed at various points) it reboots.
Only thing I can think of is that the charge pad + usb combo isnt providing enough power with a completely dead battery, but I don't have a working S7 to swap the battery into to charge it, and when its looping or in download mode its not charging at all.
Any ideas?
Download latest firmware using samfirm