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
Related
OK, never had any auto resets, just had to manually restart often to cure various ills. Then yesterday it was stuck on the dimmest backlight setting. This morning picked it up from charging overnight and it's 100% dead. Switched batteries, plugged it into various computers and USB power sources. Dead.
Anyone brought a G2x back to life?
Have you tried a wall charger? If your battery discharges completely, like deader than dead, then sometimes you have to plug it into a wall charger and leave it there for several minutes before the phone will even show its connected to a charger.
I guess the real question to ask first is, what did you have it plugged in to? What kind of charger? Was it plugged into a surge protector?
It was plugged into the LG wall charger it came with overnight. I tried a iGo USB wall -> USB power supply and a USB port on my desktop windows PC.
dylanear said:
OK, never had any auto resets, just had to manually restart often to cure various ills. Then yesterday it was stuck on the dimmest backlight setting. This morning picked it up from charging overnight and it's 100% dead. Switched batteries, plugged it into various computers and USB power sources. Dead.
Anyone brought a G2x back to life?
Click to expand...
Click to collapse
It depends on how dead it is, if its a hardware defect of some sort then you're probably SOL. But, you don't have to be able to turn it on per se to use NVFlash, so if I were you I would try to see if you can get the device to be recognized using the APX drivers. If you can, then you might have a chance.
My G2x died after freaking up during one of the Davlik cache clears....
It originally would boot up and get stuck at "LG", but after a while it was completely unresponsive (not even a Boot Logo) and wouldn't even turn on. I thought it was fried. Luckily we have NVFlash that you can use without booting the phone up.
Take the battery out and press and hold the VOL keys, then plug it in. Your PC should "ping" letting you know something was connected. Then just reflash a recovery.
I did this a ton of times and it didn't work at first. I kept flashing stock then CWM, then stock, then CWM (different versions too). Eventually it displayed the LG logo and allowed me to boot into CWM where I flashed a new rom.
Been solid ever since.
I also read about this in the Asus Transformer forums (cause I just picked one up) and read about a guy experiencing the same thing.
Worth a shot. The NVFlash method will at least let you know if it is DEAD or just not working. If NVFlash doesn't connect then it is hosed. If NVFlash connects and accepts a new recovery, then something just got corrupted.
All good now! I unplugged, removed battery, let sit a while. Put the battery back in and it booted! Yet more strange behaviour from the G2x, but as usually I get it working again and stick with this phone.
But today I got a second from craigslist to play with alternate ROMs. Trying CM7.1 RC1 first, it's working pretty good on my Nook.
Just received today my brand new OPO from OnePlus, buyed it with invite, it came from LONDON-HEATHROW - UK.
The phone immediately powers down after boot. It displays the "Power off, Shutting Down" message, but simply refuses to actually let me into the OS.
I've tried:
- Full factory reset (all wipes)
- Reinstalling rom with fastboot (30O) AND with simple recovery sideload (25R)
- Formatting again
- Different cable, Different charger
- Without SIM card, with SIM card (with and without sim deck)
- With cable, without cable
- Boot cycle (+30secs power button)
The battery is at ~35%, But battery does NOT charge. Tried with different chargers and cables, over an hour but it doesn't charge at all. Screen turns on when "charging" and shows battery icon with percentage. And plug is all way in.
Have made a ticket to OnePlus but i dont think i get answer in half a month.
It will stay alive if I hang in Recovery and in Fastboot. It will stay on in that all day. The minute I boot into the OS it shuts down.
Edit: Found out that someone has same problem with nexus5.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-shutdown-immediately-boot-t2569000
On video same thing as me. I haven't rooted device.
Anybody have any ideas?
Very disappointed because waited this day 2 months and then i can't even try the software. Phone feels and looks good. But its too expensive to only be a paperweight.
Did you unlock your bootloader and flash a custom recovery before you tried to flash a rom?
Mr Woolf said:
Did you unlock your bootloader and flash a custom recovery before you tried to flash a rom?
Click to expand...
Click to collapse
yes i did.
Also tried the boot cycle (at least 30sec power button) with no luck.
I think its a hardware issue... Replacing is good way..
Sent from my Miui v6 by Abhi
okay, i try to get logcat from boot. First issue is that usb debugging is off by default. So i found a way to change this ON with TWRP, and adb and sqlite3.
Changed adb_enabled value from /data/data/com.android.providers.settings/databases/settings.db to 1.
And
Added persist.service.adb.enable=1 to /system/build.prop
Next problem is that when i turn phone on, it boots normally, and when it has booted up it shows on back: Allow USB debugging? And buttons Cancel and OK, but i can't press those because of that stupid Power off. Shutting down... window.
Any solution how to confirm usb debugging?
Micco85 said:
Just received today my brand new OPO from OnePlus, buyed it with invite, it came from LONDON-HEATHROW - UK.
The phone immediately powers down after boot. It displays the "Power off, Shutting Down" message, but simply refuses to actually let me into the OS.
I've tried:
- Full factory reset (all wipes)
- Reinstalling a rom with fastboot AND with simple recovery sideload
- Formatting again
- Different cable, Different charger
- Without SIM card, with SIM card (with and without sim deck)
- With cable, without cable
- Boot cycle (+30secs power button)
The battery is at ~35%, But battery does NOT charge. Tried with different chargers and cables, over an hour but it doesn't charge at all. Screen turns on when "charging" and shows battery icon with percentage. And plug is all way in.
Have made a ticket to OnePlus but i dont think i get answer in half a month.
It will stay alive if I hang in Recovery and in Fastboot. It will stay on in that all day. The minute I boot into the OS it shuts down.
Edit: Found out that someone has same problem with nexus5.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-shutdown-immediately-boot-t2569000
On video same thing as me. I haven't rooted device.
Anybody have any ideas?
Very disappointed because waited this day 2 months and then i can't even try the software. Phone feels and looks good. But its too expensive to only be a paperweight.
Click to expand...
Click to collapse
I suggest you do an RMA ASAP or you'll be screwed. I was having issues with my device not the same as yours and 3 emails after never got a response from OnePlus so I contacted Paypal. I'm sure they'll reply back that way, good luck.
Knight-Rider said:
I suggest you do an RMA ASAP or you'll be screwed. I was having issues with my device not the same as yours and 3 emails after never got a response from OnePlus so I contacted Paypal. I'm sure they'll reply back that way, good luck.
Click to expand...
Click to collapse
Ticket has been made on same day i received OPO.
I Managed to get LogCat from startup. See attachment.
Micco85 said:
Ticket has been made on same day i received OPO.
I Managed to get LogCat from startup. See attachment.
Click to expand...
Click to collapse
You're better off asking a Dev I can't help you there.
My tablet is unrooted, untouched, unmolested, etc. Running 5.0.1 from the ota update.
My tablet's battery died while I was using it a few hours ago. I put it on the charger and wait a bit before turning it on. It boots up normally but I'm immediately greeted with the "power off" message box as soon as android loads. I've done fastboot and did the recovery boot (whatever that means in this case) and nothing I have tried has helped.
I'm afraid of tampering with it to install custom roms, because if that doesn't work the warranty would be void.
Anyone experience this problem before?
Sounds unusual but my only recommendation is to leave it on the charger overnight to get it fully powered up.
If not, you might have to boot into the stock recovery and perform a factory reset. At that point if it still doesn't work, if your tablet is completely unrooted with a locked bootloader, just send it to Nvidia.
Yeah it sounds like it's gonna get rma'd. It was charging the whole time, in the 4 or so seconds it was on the lockscreen before turning off it would show the battery percentage at something like 60%+, so it was definitely charging.
After enough tries it just wouldn't even give me the nvidia start up splash screen. I managed to do a factory reset (which seemed to take a really long time). The factory reset let it get back to the lockscreen but it immediately turned off again.
Other things for people who might have this problem as well:
It started after I put in a 32gb micro SD card I bought for it. I think the SD card is fine because it works in my phone.
Also this tablet was only about 4 days old when it broke.
The tablet is completely stock. I'm lucky it broke so soon as I was about to root it.
http://forum.xda-developers.com/shield-tablet/help/tablet-shutdown-boot-t3035492
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
so i have had a nexus 5 for about a year now, my brother had it from launch, one day it bricked and my brother bought a iphone, so, ofcourse i reflashed the rom, and it worked again, but with weird buggs and quirks, now suddenly it didnt want to charge, so i have decided to factory reset, and ive also replaced the battery (i had one laying around and hadnt come around to puttin it in)
so, heres the issue:
when the device is off, and you plug in the usb cable, it recognizes it, and starts the charging animation, then this animation crashes and it restarts, it does this, over and over again..
when i go to fastboot mode, and i plugg in the usb, my laptop (and pc) recognizes it, and then gives an error, just so it can start the cycle over again, and i cant get adb working like this...
any help?
Which ROM did you flash?
Edit: Oh, and how did you flash it?