Database Info

[Q] Am i bricked ?

Hi All,
i rooted my phone using what i thought was the right img file, but i can only assume it was the wrong file as i can now do nothing, i can boot into the Moto symbol, i can get to the droid with the warning triangle and into the fastboot section but i can no longer detect it when connected to the usb...
can anyone suggest a fix or am i screwed ??
thanks for any help

Try reflashing it with my tool, using unbrick feature, maybe you need fastboot drivers, just download it from sdk
Sent from my awesome ICS Xoom with xda Premium HD

cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.

TheWhiteDragon said:
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
Click to expand...
Click to collapse
If you can boot, you are not bricked - just start over with the root process using the correct image.

hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support

tried doing the same using the different modes.
on Pad
Starting RSD Protocol Support
Same result on LAIOT

Recovery -
Same result.
this has all been done on a windows 7 laptop,
i have a linux laptop, will i get any more success using that with the google driver ?

just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.

TheWhiteDragon said:
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
Click to expand...
Click to collapse
Try a diff USB cable - download drivers from MOTOROLA website get this file - MotoHelper_2.1.32_Driver_5.4.0.exe
Okay here we go....
first thing let your xoom stuck on M logo.
Then hold power+volume up.
while power up press volume down to get firstboot.(make sure your PC and xoom know each other.)
You will see some text firstboot bla bla bla on left, top of screen.
Second thing open window cmd.exe
then type ...
cd /AndroidSDK/tools (where ever your adb.exe is located)
fastboot flash boot boot.img (the right boot image)
fastboot flash system system.img
fastboot erase cache
fastboot reboot
wait for reboot. You should see splash screen and you smile on your face.

TheWhiteDragon said:
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
Click to expand...
Click to collapse
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD

thanks Mjamocha
ill give it ago tomorrow, sorry been flat out at work.
ill also try xxlords again on another machine just incase its the drivers on the laptop which are the problem.

XxLordxX said:
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
Click to expand...
Click to collapse
sorry guys i have been flat out at work, SCCM deployment is taking a while to learn & play with.
but im back now and hopefully unbuggering my phone
i am going to redo all the bits you guys suggested on my PC rather than Craptop.
hopefully ill have more joy, ill let ya know how i get on 8)

What about using RDS?

woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.

TheWhiteDragon said:
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
Click to expand...
Click to collapse
Glad you got it going!

Had a similar problem where I had a boot loop and adb didn't recognise my device, but I could still put it into fastboot or recovery with power + vol down.
What I did was boot the Xoom so that it was stuck at the Moto logo, connected to the PC and queued up the fastboot command (fastboot flash boot boot.img) so the command window said "Waiting for device...", then reset the Xoom and manually put it into fastboot again at which point it picked up the queued command and started flashing.

Xoom bricked seen as APX in devices need drivers

Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?

Have you downloaded drivers from motodev?
Prior to the bricking, could you connect to your computer?

It will connect but it just shows up as APX in the devices and says its missing drivers. I went to moto and downloaded USB drivers but still does the same thing. The xoom does nothing when plugged in.

Windows 7 or XP?
Sent from my MB860 using xda premium

Windows 7. I did manage to get some drivers to install. Don't know if their the rite ones though. I clicked on let me choose such drivers, found some in SDK for htc,Samsung,and Motorola. Chose Motorola and it had several adb drivers clicked next and they installed. So now it just shows it as APX in the devices but no longer has the missing drive issue. Still no sign of life when trying adb or fastboot.

What mode is it in when you are attempting to connect it to your computer?
Sent from my MB860 using xda premium

It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.

ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?

Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?

ericman77 said:
Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?
Click to expand...
Click to collapse
ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
darchiuk said:
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?
Click to expand...
Click to collapse
qoole33 said:
Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?
Click to expand...
Click to collapse
Dear all,
I got the same thing.
I installed the driver from nvflash drivers. And I ran several commands to try, it showed no bootloader was specified. I guess maybe I damaged my bootloader. Does any of you unbricked your xoom?
Here is a link to my post, which showed my tries.
http://forum.xda-developers.com/showthread.php?t=1838002
Anyone could help us? Thanks a lot.

Wow, i've been on that Wagon for a long time. http://forum.xda-developers.com/showthread.php?t=1838002 Now I just gave up cause I don't think anyone has gone past installing the drives after it detecting as APX.

Thanks for your kindly reply.
So, you mean there is no hope.
Actually, I sent it to another MOTO local service center again. After one week, they told me they tried to restore the software in two steps, but only the first could be done, and then went back to brick again. And they thought there might be some damage on “the kit” of motherboard, and if I want to repair, the whole motherboard must be replaced totally.
If you still have the bricked XOOM, would you please try to draw the BCT and config.cfg from your device?
Again, I did another search. Although there is no available bootloader.bin, BCT and config.cfg for XOOM, I guess there might be possible to use SAMSUNG P7510's files, because the hardwares are almost same, and it's heard that P7510 could use XOOM's ROM.
Sent from my ZTE U970 using xda app-developers app

Another Bricked TF300

Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.

AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.

tobdaryl said:
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
Click to expand...
Click to collapse
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.

AdvanceArg said:
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
Click to expand...
Click to collapse
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?

tobdaryl said:
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
Click to expand...
Click to collapse
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.

AdvanceArg said:
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
Click to expand...
Click to collapse
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.

tobdaryl said:
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
Click to expand...
Click to collapse
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.

AdvanceArg said:
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
Click to expand...
Click to collapse
No problem we just need to get a starting place and have as much in our favor as possible.
I don't believe adb works in apx mode but we'll give it a shot.
No sdcards come with the tablet.
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.

tobdaryl said:
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
Click to expand...
Click to collapse
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.

AdvanceArg said:
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
Click to expand...
Click to collapse
[FONT=TimesNewRomanPSMT, serif]Download 10.4.2.9 JB from this thread post #3[/FONT]
[FONT=TimesNewRomanPSMT, serif]unzip once and you should still have a zip if you get a blob then do not unzip.[/FONT]
[FONT=TimesNewRomanPSMT, serif]rename to EP201_768_SDUPDATE.zip and copy to sdcard and place sdcard into your tablet.[/FONT]
[FONT=TimesNewRomanPSMT, serif]Power tablet and hope![/FONT]

nothing. Renamed US_epad-user-10.4.2.9 to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.

AdvanceArg said:
nothing. Renamed US_epaduser_10_4_2_9_UpdateLauncher.zip to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
Click to expand...
Click to collapse
I have some bad news for you.
Without adb or fastboot access I don't know of anything else to be done.
If you could have gotten into the bootloader menu we would have had a chance.
Maybe someone else will read this thread and have more ideas.
I'm sorry.
Good Luck!

same problem here. i have a tf300t and can only access apx interface.
I got into this mess, after by "accident" choosed the "wipe data" option present on the bootleader.
!! adb, fast boot do not work!! "power key + down button" dont do anything!
i'm getting a bit resteless because no matter were i search on the web i can not find anything suitable on how to resolve this issue...
there are some youtube videos that show a solution for tf100. it seems the same problem.
http://www.youtube.com/watch?v=CwvfNIHCYlQ
there is also a tool for tf100, called easy flasher. to bad it does not work for tf300t
http://forum.xda-developers.com/showthread.php?t=1688012
i think it is a question of seaching and waiting. someone will help and get or point to a solution. because if we google for tf300t bricked that are lots and lots of links stating this issue...
what a mess...

AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
Do you see anything after resetting by holding volume down and the power button? If you can get the tablet into fastboot mode you may able to revive it. If you can, ask the previous owner which version stock Android he was running before he tried to root it (it matters!).

This method worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps guys. Good luck!

[Q] Back To Stock

Afternoon guys,
Before anyone has a go at me, I've have spent about five hours looking through this forum for what I'm looking for and i've tried all the easy unroot/easy flasher/etc and got all the stock Asus rom and recovery. AND the forum search is temporarily unavailable.
So here is what I have:
ClockworkMod Recovery v5.8.3.4
Liquid Smooth Rom
I have installed the stock rom, recovery and wiped everything.
If i press the power button it loads into CWM recovery.
If i press power and down vol, it loads to the wipe data/load android screen, and which it hangs on forever,
So I guess what im asking you good people of the internet is:
A) How do I finally get rid of CWM Recovery (because even if i install another recovery it boots back to CWM), and
B) How on gods earth do I get back to stock?
Now I know people are going to be like search the forums, I have, and I've tried literally everything that everyone has posted, and clearly while it's worked for millions of other people, my tablet is retarded and doesnt want to follow the norm.
Also i am the greatest noob ever.
Any help would be greatly appreciated.
Thanks

Hmmm, did you unzip the stock ROM once before flashing (it will still be a zip).
Otherwise, try using EasyFlasher and APX mode. For EasyFlasher, do not unzip the stock ROM, use it as it downloads from Asus.

killerkuk said:
Afternoon guys,
Before anyone has a go at me, I've have spent about five hours looking through this forum for what I'm looking for and i've tried all the easy unroot/easy flasher/etc and got all the stock Asus rom and recovery. AND the forum search is temporarily unavailable.
So here is what I have:
ClockworkMod Recovery v5.8.3.4
Liquid Smooth Rom
I have installed the stock rom, recovery and wiped everything.
If i press the power button it loads into CWM recovery.
If i press power and down vol, it loads to the wipe data/load android screen, and which it hangs on forever,
So I guess what im asking you good people of the internet is:
A) How do I finally get rid of CWM Recovery (because even if i install another recovery it boots back to CWM), and
B) How on gods earth do I get back to stock?
Now I know people are going to be like search the forums, I have, and I've tried literally everything that everyone has posted, and clearly while it's worked for millions of other people, my tablet is retarded and doesnt want to follow the norm.
Also i am the greatest noob ever.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
If your TF is SBK1 (Serial B6O or earlier, some B7Os work too) you can use NVFlash
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Stick the TF into APX mode (Vol up & Power from Powered Off state)
Run download.bat as Admin (Right click > Run as Admin)

@frederuco
I did unzip it and install it. It still hangs.
I tried EasyFlasher, but for some reason I run through it and the process completes, when i reboot the tablet nothing has changed.
@*Detection*
I can't get the link to work for some reason.
Thanks for your help so far, but stupid tablet stays stupid!

killerkuk said:
@frederuco
I did unzip it and install it. It still hangs.
I tried EasyFlasher, but for some reason I run through it and the process completes, when i reboot the tablet nothing has changed.
@*Detection*
I can't get the link to work for some reason.
Thanks for your help so far, but stupid tablet stays stupid!
Click to expand...
Click to collapse
Try the direct links here
WW and US in that order
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Otherwise go to http://www.xdafileserver.nl and navigate to stock ROMs section

*Detection* said:
Try the direct links here
WW and US in that order
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Otherwise go to http://www.xdafileserver.nl and navigate to stock ROMs section
Click to expand...
Click to collapse
Much appreciated! :good:
Fingers crossed this works!

*Detection* said:
If your TF is SBK1 (Serial B6O or earlier, some B7Os work too) you can use NVFlash
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Stick the TF into APX mode (Vol up & Power from Powered Off state)
Run download.bat as Admin (Right click > Run as Admin)
Click to expand...
Click to collapse
I downloaded it and ran it as admin, DOS flashed up and disappeared before i could read what it said.
the nvflash app does the same, even when i run as admin.
maybe this is a lost cause..

killerkuk said:
I downloaded it and ran it as admin, DOS flashed up and disappeared before i could read what it said.
the nvflash app does the same, even when i run as admin.
maybe this is a lost cause..
Click to expand...
Click to collapse
What is the first 3 characters of your tablet serial?
And was it in APX mode connected to PC USB with APX drivers installed ?

*Detection* said:
What is the first 3 characters of your tablet serial?
And was it in APX mode connected to PC USB with APX drivers installed ?
Click to expand...
Click to collapse
The serial starts with B40.
Im on a mac (as i have no access to a pc) but have VMWARE running windows 7, with APX drivers on it.
When i put it in APX mode, it comes up that it is connected as Nvidia APX device.
Could this be where I'm going wrong?

killerkuk said:
The serial starts with B40.
Im on a mac (as i have no access to a pc) but have VMWARE running windows 7, with APX drivers on it.
When i put it in APX mode, it comes up that it is connected as Nvidia APX device.
Could this be where I'm going wrong?
Click to expand...
Click to collapse
Yea probably, I've never tried using NVFlash on anything other than a PC running Windows
Try updating the NVidia APX Device with these drivers
http://forum.xda-developers.com/attachment.php?attachmentid=1489867&d=1353190140
Chances are its the drivers running on the Mac that are causing the problem with the USB > VMWare > TF101
I know nothing about Mac, but I heard you can install Windows 7 almost natively using Bootcamp or something? Might be worth trying that if you can't do it in VMWare

*Detection* said:
Yea probably, I've never tried using NVFlash on anything other than a PC running Windows
Try updating the NVidia APX Device with these drivers
http://forum.xda-developers.com/attachment.php?attachmentid=1489867&d=1353190140
Chances are its the drivers running on the Mac that are causing the problem with the USB > VMWare > TF101
I know nothing about Mac, but I heard you can install Windows 7 almost natively using Bootcamp or something? Might be worth trying that if you can't do it in VMWare
Click to expand...
Click to collapse
thanks dude, looks like i need a trip to a friends house!

killerkuk said:
thanks dude, looks like i need a trip to a friends house!
Click to expand...
Click to collapse
Good luck!

*Detection* said:
Good luck!
Click to expand...
Click to collapse
Thanks for your help!
All sorted and back to stock. looks like it was an issue with the mac. plugged it into a pc and everything worked out fine!
WOOOOOOOOOOOOOOOOOOOOOOOOO!!!

killerkuk said:
Thanks for your help!
All sorted and back to stock. looks like it was an issue with the mac. plugged it into a pc and everything worked out fine!
WOOOOOOOOOOOOOOOOOOOOOOOOO!!!
Click to expand...
Click to collapse
Great!
At least you know now you can do what you like with it firmware / ROM / Recovery wise, and always be able to return it to stock, you can't break APX mode unless you physically damage the tablet

Will Motherboard Replacement Solve Bricked TF300T?

Hi
TF300T JB 4.2.1
Bought new in the US in 2013 so has US SKU. Originally for my wife, but she now has an iPad Pro so I've got the hand-me-down!
Wiped it and unlocked the device successfully using the Asus V8 utility. Tried to flash TWRP from Win7 computer but something went wrong. The interface was still there, it would boot up okay but there was no sign of TWRP. Eventually, I went into fastboot and selected RCK. Nothing happened except the icon turned brown and just sat there. Then I tried a factory reset but it wouldn't have any, nor a cold boot. In desperation I turned the device off and tried to reboot. The initial "Asus" screen came up ("This device is unlocked" in top left-hand corner and the 'Nividia Tegra' logo in bottom right. No spinning circle of dots). It won't boot into fastboot, in fact the volume keys are totally unresponsive. On/off will turn off the device, but it immediately boots back to the same Asus screen. It's not recognised by the Win7 computer so I can't flash anything to it. I think I've tried everything this forum (and a few lesser ones!) could suggest, to no avail.
I believe I now have the proverbial 'bricked' tablet.
Nothing daunted, and not prepared to involve Asus support, I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
I'm no expert on the Android OS so any help from you experts would be much appreciated.
Thanks in advance.

Anyone?
I know the TF300 is a bit long in the tooth now, but all I want to know is whether a bricked one can be recovered by replacing the motherboard. There must be someone out there who has done the replacement and can advise me? Also, I apologise if this in in the wrong section, I guess it should have been in the 'Help' section, but I didn't realise until I'd posted it.

capelyddol said:
Hi
TF300T JB 4.2.1
I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
Click to expand...
Click to collapse
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99

ebonit said:
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
Click to expand...
Click to collapse
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access. The initial boot-up screen is all I get, in perpetual loop. The only way to shut it down is reset with vol-up., though it's possible it may be in some sort of variation of apx mode at this point as the screen is blank. I've no way of knowing as my win 7 computer only acknowledges an 'unknown device' at that point, and nothing when the initial boot screen is there. Vol-down doesn't seem to have any effect at all. Windows has already installed the drivers so won't re-install, or uninstall them as it's 'unknown'. I did once manage to get it recognised as an 'apx device' but with an '!' (not sure how I did it as I haven't been able to replicate it since!) but I don't think that helps me even if I could replicate it without the '!', Nvflash requires I have the necessary back-up files, which of course I don't. I don't know where to go from here except to replace the motherboard. Once I get the device apart I may try disconnecting the battery, vol-down, and reconnect, to try booting to recovery, but I'm not optimistic of that working.
I'll certainly be very happy to consider any other suggestions you, or anyone else, may have.
I tried Buster99's method, but as my TF300T isn't recognised by Windows that was a non-starter.
Once again, many thanks for your input.
capelyddol
(John)

capelyddol said:
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access.
Click to expand...
Click to collapse
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB

ebonit said:
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
Click to expand...
Click to collapse
ebonit ~ Thanks for the links. I checked out huebinger's and pulled my motherboard out, then bought the one you linked to on eBay. Hopefully, I didn't do any damage getting the MB out. I'm more used to the tough old internal wiring of desktop computers!
I'd already backed up the data and done a factory reset before I began my abortive attempts at rooting so hopefully I'll be starting with a clean slate once I get the new board installed. It's going to take a while to cross the pond to France, but I'll report on how it goes once it arrives.
Thanks again for your help, it's much appreciated.
John.
(capelyddol)

Hello,
My tf300t got bricked while upgrading twrp.
nothing helped, i put away the tablet, after a year i found her ... so i said to myself "why not" ?! so i ordered from ebay a motherboard, and it's work like a charm, but the tablet is old now ;0
now i want to setup a lite rom ....

mitomon said:
Hello, now i want to setup a lite rom ....
Click to expand...
Click to collapse
What do you mean?

What do you mean?
Click to expand...
Click to collapse
I was wondering that, too!
It's good to know the s/h motherboard cured his tablet's ills, though.

My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
Go to folder /Universal Naked Drivers 0.72 you unziped at start on your Desktop.
Select file android_apxusb.inf, then right click -> Install.
Force driver install and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Click to expand...
Click to collapse
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)

capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
Click to expand...
Click to collapse
Congratulations! You did a good job. Thanks for your report.
First of all, to avoid any issues to get your device on N 7.1 Nougatella please follow exactly Tim's install instruction step by step in post #1. https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
You need Kang TWRP as advised by Tim. Don't forget to format data through Kang TWRP before. It takes up to one hour. Then change file system to F2FS for data only no cache and system. Successfully done your device is now ready to install Rom, pico Gapps and SuperSU fresh downloaded via Tim's links there.
PS: About your USB issue take another USB port on your PC not via hub!
Good luck!

Three days with nothing from me, you'd be excused for thinking either I was dead, or my tab was! Thankfully, neither. In fact - SUCCESS!!! We're both alive and well, and for the tablet at least, performing better than ever.
TWRP installation took me two days. First, the computer (Win 7 32-bit) refused to recognize the TF300T and 'fastboot' could have been renamed 'nerverboot'. Strangely, the whole business seemed to evolve over time. Persistence was the name of the game - trying different USB ports, booting and rebooting (both tab and desktop). Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Code:
fastboot devices
returned '???????????????' over and over again. By uplugging/plugging the cable into the tablet a few times I suddenly got a nice long string of letters and numbers. It came and went a few times but after a while seemed to stabilize till I felt ready for the big push of TWRP. I got so many error messages: 'can't find twrp.img' (I'd renamed it); 'can't open twrp.img'; 'insufficient memory', etc, etc.. Suddenly, it worked. It took just over eight seconds to download the 6.95MB. Booting into recovery was rather heart-stopping, but it came up a treat.
After that it was relatively simple to set up the TWRP (I found Djibe89's guide https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744 especially useful and there's a copy in the -djibe Transformer Pad TF300T pack v3' http://bit.ly/djibe-tf300t-v3.
Flashing KatKiss 7.1_TF300T_029, open_gapps-arm7.1-pico, and SuperSU-v2.82 from the microSD I'd copied them to went like a dream and before I knew it the old tab was humming with life once more. I'm a very happy chappy!
I have just two queries (so far ) 1. djibe89 mentions the file 'deviceID.apk' but Tim doesn't. Is it still necessary? I believe it's to keep Google happy, but I've no problems downloading from the Play Store, so I've not installed it as yet.
2) While installing the 'Battery Calibration' app it briefly stated that the tab wasn't rooted. I assume if I've achieved all the above, then it must be?
Now I'm going to play. No doubt I'll be back with a few more queries before too long!
Special thanks to ebonit for his help and support.

capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
Click to expand...
Click to collapse
hi ,
you said that you succeeded to unlock the tablet ?
how ?!
i tried with unlocker v7 and 8 , i got the network error.
my tf330t is on 4.2.1.
i try hard reset, nothing helped.
i changed the mb, succeeded to root with motochopper.
please , i need help.
thanks

mitomon said:
I tried with unlocker v7 and 8 , i got the network error. My tf330t is on 4.2.1.
Click to expand...
Click to collapse
To avoid any issues please reinstall your system by doing a Buster99 https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. Be sure you have the latest firmware "WW_epad-user-10.6.1.27.5"
After that delete your Google account. Then you may unlock your device with V7.

capelyddol said:
TWRP installation took me two days. Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Click to expand...
Click to collapse
Hope you have Kang TWRP now as required by Tim in post #1!
I'm sorry, but you never mentioned that you cannot access your Tablet via ADB. Therefore please note, the best ADB tool, every Android user may have on his PC, is "Minimal ADB & Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790.
BTW, the answer to your first question is nope, you don't need it. The answer to your second one is yes the device is rooted. However check the update status of your SuperSU. Hope you did fresh download Rom, Apps and SuperSU via Tim's links in post #1 of the Nougatella thread?

I have installed Kang TWRP 2.8.7.2 as per Timduru's link. My tab was wiped before installation so all apps were fresh downloads. SuperSU was 'UPDATE-SuperSU-v2.82-20170528234214.zip' again, as per Timduru's link, as was the ROM ' KatKiss-7.1_TF300T_030.zip'. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!

capelyddol said:
My tab was wiped before installation so all apps were fresh downloads. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
Click to expand...
Click to collapse
You are welcome! It's good to hear that you did such a good job. Using the thanks button is always greatly appreciated.
Please note, if you have any issues or you are changing the Android system, Format /data through Kang TWRP is always required. Format /data is more than wipe (you did wipe!) or factory reset. It takes up to 1 hour to be successfully. After that your system is really clean.
"Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb." advised by Tim in post #1.