Database Users

[HELP] TF101G Stuck on EEEPad inicial screen

Hi everyone, I'm a new member to the forum, but have been a follower for quite some time.
Let's start by introducing my device wich is:
EEEPad Transformer TF101G with ICS running the latest WW_9.2.2.6 firmware.
The device is rooted and running ASUS stock recovery.
Everything was working fine until I decided to do a Cold Boot.
It got stuck on the cold boot menu for like 3 hours and I decided to turn it off.
After that it got stuck on the inicial Asus splash screen. I forced it to turn off a couple a times and it eventually booted up.
I knew something wasn't right, so I backed up all my files and applications.
Then decided to do a factory reset through POWER + VOL-
After that it never booted again, and after a few seconds on the splash screen I hear a click noise, like the hard drive is turning off.
When I try force it to turn off, it starts up again automatically.
I've tried to flash it through nvflash, but being a TF101G it also means it is sbkv3, wich is not supported by nvflash.
Also tried boot recovery tools, but it won't even start, because as I try to connect it to the computer through adb mode, after that "click" noise, the device becomes disconnected.
I didn't try any dangerous applications and stuff like that, just decided to do a simple cold boot, the device is a week old.
If I'm posting this in the wrong section I apologize.
And hope someone can come up with a good idea.
Thanks in advance.

Obviously somethings corrupted and in my opinion the only way to fix it would be to reflash the rom in apx mode using nvflash but that doesn't seem to be possible for your device as of yet but if everything is still stock maybe you can unroot the device (or play dumb) and get it replaced under warranty?

I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...

Akusura said:
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Click to expand...
Click to collapse
Eek.. since it was factory resetted I think you need to send it to warranty. Not much we can do now with just a splash screen on sbkv3

I don't consider myself an advanced user.
But I really did search everywhere and I got the idea that only with APX and without a compatible NVFlash I was screwed.
But I still had some hope.
Do you think they will give me trouble because of it being rooted?
I my opinion I don't think they will ever know, because It won't boot, It won't run recovery mode (stock) and nothing else at all, the only way to fix it is to flash it, but maybe I'm just being naive.
I treated it with all the care in the world, so only by divine intervention it is a hardware problem.
But you never now...

you should be ok (should)......
i done pretty much the same thing to a customers TF and Asus fixed it no problem.

The fact is that I actually didn't do anything wrong.
Just a cold boot that didn't work, followed by a a factory reset...
How long did it take for yours to get fixed?

Help! Asus ZenPad 10 Z300 series stuck on logo screen

Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:

[update]
OK so after failing to flash any zips (or anything!) to the device, I left it on in fastboot mode while I went to work. Now upon coming home the tablet is just a black screen! The laptop recognises it because Windows makes that chime sound when its plugged in via USB. But other than that, I can't get a response out of it Button combinations don't seem to help so now I'm not sure what to do!
Can anyone help me please? :crying:

Unless the bootloader is locked, you may have made a mistake trying to flash the ROM and trying to install a custom recovery. Anyways, if you hadn't made any changes yet to the system, I would have said check the battery first because it may be malfunctioning and not the phone it's self. I know from experience that it may have been the battery considering the way you said it was not reading the battery percentage right and shutting down. And that "bootloop", this was probably happening because it didn't have any power to start up the device as this is exactly what my device did when I had a faulty battery. My best bet is to 1 try to get a new battery, and then 2 see if your system is still intact otherwise try and reflash with the stock ROM (through adb or any computer to android debugger) and then reinstalling the right recovery that goes with the device or that of which is c-o-m-p-a-t-a-b-l-e.
Using CM12.1 on my SGH-T999

I exactly got the same issue, nothing I particularly have done as far I know, my tablet suddenly rebooted and now is stuck on Asus logo with the little circle that keeps turning.
I tried to let it go till my tablet get completely discharged and also tried to charge it completely, nothing change.
And when I wanna access to the recovery, I just get the green android mascot with the message "ERROR!". So I can't even access the recovery to reset my tablet :crying:
Edit: Tried a fastboot erase userdata and an erase cache, still bootlooping

Sorted
The only way I fixed this was by returning it to the shop and having the device replaced! Not the ideal solution, but it worked. :good:

MrLewk said:
The only way I fixed this was by returning it to the ship and having the device replaced! Not the ideal solution, but it worked. :good:
Click to expand...
Click to collapse
I guess I will have to do the same

MrLewk said:
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
Click to expand...
Click to collapse
Asus has the firmware (Nougat) for this Z300M but I've no idea how you would get this loaded. Something to learn but as long as the OS is available you should be able to get back stock, latest OS............
zls

Zenfone Hardbrick help plz..(have tried everytghing)

So here is my sadness. i got my Zenfone2 back Z00A (ME551L) from having the screen repaired from asus themself. it was sluggish so i factory reset and it corrupted. i tried to flash the stock ram but then it went to hell. long story short i ended up wiht the White USB screen which means hard brick(correct if im wroong). i followed http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 to try and get it back to normal. the 1st time it flashed it worked in the Downloader (FW+OS complete). But when using Flash tools it hung up on the yellow flash button. I have no clue what happend. I try to start from the beggining but it wont complete like it did at 1st. So im stuck with the 4 color boot to fastboot. Wont connect to ADB so i cant sideload or recover from ADB in recovery. any help plz. i just miss my zenfone 2 ahha.
so in recap:
It wont flash fully in Flashtools 1.14.
Wont FW+OS complete in the downloader tool(only FW finishes)
No recovery mode options like it disappeared
When i let it boot normal it says updating with the android guy for 30 seconds then goes to dead guy with error.
plz any help would be outstanding and helpful

fuzydino said:
So here is my sadness. i got my Zenfone2 back Z00A (ME551L) from having the screen repaired from asus themself. it was sluggish so i factory reset and it corrupted. i tried to flash the stock ram but then it went to hell. long story short i ended up wiht the White USB screen which means hard brick(correct if im wroong). i followed http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 to try and get it back to normal. the 1st time it flashed it worked in the Downloader (FW+OS complete). But when using Flash tools it hung up on the yellow flash button. I have no clue what happend. I try to start from the beggining but it wont complete like it did at 1st. So im stuck with the 4 color boot to fastboot. Wont connect to ADB so i cant sideload or recover from ADB in recovery. any help plz. i just miss my zenfone 2 ahha.
so in recap:
It wont flash fully in Flashtools 1.14.
Wont FW+OS complete in the downloader tool(only FW finishes)
No recovery mode options like it disappeared
When i let it boot normal it says updating with the android guy for 30 seconds then goes to dead guy with error.
plz any help would be outstanding and helpful
Click to expand...
Click to collapse
Check my signature below...charge fone after flashing in xfstk,when in bootloader , select power off and charge.
read all the thread

timbernot said:
Check my signature below...charge fone after flashing in xfstk,when in bootloader , select power off and charge.
read all the thread
Click to expand...
Click to collapse
awesome your are my hero . worked like a charm!

Marvelous stuff

A8 stuck in bootloop while in download mode...you heard that right!

hello,
i recently flashed a chinese A8 (a8000),it gave a headache following a PIT file issue but it nevertheless completed...assuming it had a battery...i unplugged it while the android robot was cleaning up...it switched off immediately, i tried to boot it, it did... i went to recovery and reset it, then it only goes to charging... so i figured i might have messed it up...so i went to download mode and as it started to flash...it rebooted...Odin gave write error and the phone rebooted to a 'error has occurred...' BSOD. the problem now is, it stays on for 10 seconds and reboots again to the same message, AND if i go to Download Mode, same thing , it wont stay on long enough for me to flash anything to it. and the phone wont boot unless i plug it..i hope its a software issue... if there is a solution i need it badly!!!! Thanks!!

That's a tough one. It loops and gives error on both download mode, recovery mode, and when booting to system? And power needs to be connected to make it boot at all?
Sent from my Honor 5X using Tapatalk

tys0n said:
That's a tough one. It loops and gives error on both download mode, recovery mode, and when booting to system? And power needs to be connected to make it boot at all?
Sent from my Honor 5X using Tapatalk
Click to expand...
Click to collapse
Yes, and it crashed while flashing so ony have access to 10 seconds of download mode. Never heard of this issue or i don't know the magic "google" word for it.

go to samsung or replace battery

FitseMan said:
hello,
i recently flashed a chinese A8 (a8000),it gave a headache following a PIT file issue but it nevertheless completed...assuming it had a battery...i unplugged it while the android robot was cleaning up...it switched off immediately, i tried to boot it, it did... i went to recovery and reset it, then it only goes to charging... so i figured i might have messed it up...so i went to download mode and as it started to flash...it rebooted...Odin gave write error and the phone rebooted to a 'error has occurred...' BSOD. the problem now is, it stays on for 10 seconds and reboots again to the same message, AND if i go to Download Mode, same thing , it wont stay on long enough for me to flash anything to it. and the phone wont boot unless i plug it..i hope its a software issue... if there is a solution i need it badly!!!! Thanks!!
Click to expand...
Click to collapse
I also had a bad experience with a chinese version of a J3 Pro. Luckly I revive it from a chinese forum (google translate... it was a pain in the a..) and succesfully flash a ROM (I didn't find anything on xda).
On that forum were detailes about win drivers version, odin version and so on! Don't ask me what site/forum it was because it was purely random based on google translate...
Keep trying on chinese forums to find a solution, I don't think here you can find anything to use on chinese versions!

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"...