Database Info

Bricked My Kindle Fire

I attempted to root a Kindle Fire Running 6.2.2 but was using a version on the Kindle Fire Utility to root 6.3. TWRP installed but now I'm stuck at the yellow triangle logo.
The biggest problem is my Window 7 laptop won't recognize the Fire when I plug it in with my USB cable. Therefore, none of the unbricking, KFU, or ABD utilities/commands are getting through to the device.
Has any one encountered this before?
(I've gotten stuck in a bootloop with TWRP before on another rooted Kindle Fire and that was easy to fix.) I don't know what to do when you laptop won't recoginize the Fire as a connected device.
I've rooted another Fire (though it was running 6.3) on this same laptop so the Kindle Fire drivers were installed.
I'd appreciate any help with this!!!
Sent from my Kindle Fire using xda premium

1) Unplug your kindle
2)
Microsoft said:
Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
At a command prompt, type the following command , and then press ENTER:
set devmgr_show_nonpresent_devices=1
Type the following command a command prompt, and then press ENTER:
start devmgmt.msc
Click to expand...
Click to collapse
3) After you follow those steps, look for any android/adb devices and DELETE them from device manager
4) Re-plug your kindle fire usb into computer
5) Windows should now auto detect drivers (if you have windows 7) and you can use fastboot to reboot your device or flash files.

Thank you so much for your reply! I tried what you said.
I set my Device Manager to show hidden devices. "Android Phone" appears as a device. When I expand it, I see "Android ABD Interface". The Android Phone device displays for a few seconds and then disappears. I hear the Windows OS make a tone as it appears and disappears. If I shutdown the Kindle Fire and power it on again, the device manager does the same thing.
I should probably explain more how I bricked my Fire.
I tried to root it as I explained in my first post. It was unsuccessful. When I realized the Fire was runnning 6.2.2, I tried to upgrade the firmware to 6.3.1 from the Amazon site, thinking I'd do that and then run the rooting bat file again. I didn't think to uninstall any of the rooting software before trying the update because the root was unsuccessful.
The Fire started the update but stopped almost immediately and got stuck at the TWRP logo.
Is there any thing else I can try?
Sent from my Kindle Fire using xda premium

I bet you are stuck in fast boot. Can u see it when running fast boot devices? Search as this is common... happened to me. Just need to run a com,and to change default boot mode
Sent from my Kindle Fire using XDA

Paulnsx,
Thanks for the reply.
Can you explain a little more about this >> "Can you see it when running fast boot devices"?
Where and how would I check for that? And, what is the command to change the default boot mode?
Sent from my Kindle Fire using xda premium

warranty
will Amazon replace it or is it obvious you attempted to unlock the tablet? I mean is there and indication on the boot screen?

Yes, it's obvious I was rooting it. To return it to Amazon (or the retailer in my case), I need to get it to boot normally, then reset it to the factory default.
Sent from my Kindle Fire using xda premium

Are you able to boot into the recovery? Also, you may be able to re install the drivers yourself. I know that I downloaded the KFU and it came with drivers and an unbrick app as well.

try the kindle fire section lots of good ppl to help and loads of info

I wish I could but as a junior member of xda, I'm not allowed to post there.
Sent from my Kindle Fire using xda premium

you should be able to post if its not in the dev section

You are right. I just tried (like you suggested) and my post went right up. Yeah!! Thanks for explaining this!!

I just want it back to the original status and I get nothing.... I've been at this for 3 hours and it still won't read my kindle
Update: Finally got the usb to read and everything is recovered.

[Q] Xoom won't boot

So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Update: I've been trying different cables. I found one where the computers will see that a devices is connected, but am getting "USB device not recognized" with either set of drivers that I have on both computers. Making progress, but could still use some help.

DiGi760 said:
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Click to expand...
Click to collapse
I had a problem similar to that about a year ago, somewhere in these forums was the suggestion to remove the SD card and then do a factory reset, it worked for me. My xoom just stopped working, I thought at first it was a flat battery but after charging the symptoms were the same as yours, might be worth searching through the forums if you haven't already

There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?

DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
Sorry can't help , mine is just over 2 years old and except for that one problem have never had any issues so have never needed to even connect it to a PC

DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
I recently discovered these handy files when I needed to return to stock:
4G Xoom (MZ600) Restore
3G Xoom (MZ601/3) Restore
WiFi Xoom (MZ604) Restore
If you need to find out which Xoom model it is, power on whilst holding the volume down button, this will take you in to fastboot. Then (you sound like you'd know how do this, PM me if you don't) use "fastboot getvar all". This will return the model.
Unzip the file above, there's a batch file in there which will install the drivers, then fastboot the firmware over.
If you boot to fastboot, then run the batch file, it installs the drivers, then "adb device", then it asks if your device is connected - it won't show up cos it's in fastboot. Just ignore that and say yes, and it'll start flashing the files.
Sorry if I'm too late - don't visit these boards much these days. Good luck, let me know if this works.

Thanks for giving me something to try. I uninstalled the moto drivers I had and installed the ones included in the zip file and restarted my computers. The Windows 8 computer never recognizes that the xoom is connected in any mode. The 7 machine does see it in fastboot mode but as a "fastboot" device for which it fails to find drivers. When I run fastboot getvar all, all I get is <waiting for device>.
I do know that this is a wifi only (mz604) xoom. Thanks for the image files. If I can get this stupid thing to communicate with a computer, I think I'll be in business.

In fastboot mode (vol -) it won't acknowledge that it's connected. Just fastboot your image over and it will work.

If I try to do anything with fastboot, it just says "< waiting for device >". Fastboot doesn't see a device to flash to.

OK, it's either your cable or your driver. Many cables are for charging only, and have no data lines. I throw those away.
As to drivers, I'm Debian for 15 years so can't advise on Winduhs.
Oh, one more thing: I've noticed that on my old HP laptop I had to use a certain USB port, or else it wouldn't comm with my phone for fundamental actions like loading new firmware.

These were the drivers I used: https://motorola-global-portal.cust...sion/L3RpbWUvMTM4NjM1MjA0NC9zaWQvWEo3SWU5SGw=
They don't seem to be windows 8 certified though.
Sent from my Nexus 5 using Tapatalk

We finally got it. We used DriverEasy to look for drivers because we have a bunch of extra licenses and the drivers we had obviously weren't working. DriverEasy was able to install an "Android Bootloader" driver that must not be part of the SDK. Once that was installed, I was able to use fastboot to flash the images from above. The device is in good working order again and fully updated.
Thanks for all your help.

Always nice to hit the Thanks button for those who've helped.

APX Drivers?

Anyone know where I can locate the APX drivers for the Tf700?
I've scoured Google and the only reference I could find linked to a file that was removed.

vexille said:
Anyone know where I can locate the APX drivers for the Tf700?
I've scoured Google and the only reference I could find linked to a file that was removed.
Click to expand...
Click to collapse
Check this post:
http://forum.xda-developers.com/showthread.php?t=2263822

LetMeKnow said:
Check this post:
http://forum.xda-developers.com/showthread.php?t=2263822
Click to expand...
Click to collapse
Tried those - didn't work.

vexille said:
Tried those - didn't work.
Click to expand...
Click to collapse
What is exactly "didn't work"? You can't install on your OS or your OS still can not recognize your device...
What OS are you running? I just want to know more information...

I couldn't get the universal drivers to work on win 8.1 either - even starting it in test mode. Yest to find apx drivers that work with it

LetMeKnow said:
What is exactly "didn't work"? You can't install on your OS or your OS still can not recognize your device...
What OS are you running? I just want to know more information...
Click to expand...
Click to collapse
Win 7 64.
Device originally detected as APX but with yellow !. Then Windows installed it as "unknown device".
Uninstalled that from Device Manager and rebooted. Connected tablet and get "unknown device" again.
When I try to update driver to those in link it says "best driver already installed"

Just tried those drivers on my notebook (fresh install of Win 7 64). Same thing - Unknown Device.
Think I have to face the fact that my tablet is bricked

vexille said:
Just tried those drivers on my notebook (fresh install of Win 7 64). Same thing - Unknown Device.
Think I have to face the fact that my tablet is bricked
Click to expand...
Click to collapse
Why is it bricked? Can you boot into your bootloader? What is exactly you want to do to your device? Maybe, someone can help you if you can tell us more details about your device. Your bootloader version, ROM, kernel, stock firmware, and your current state of your problems...
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
sbdags said:
I couldn't get the universal drivers to work on win 8.1 either - even starting it in test mode. Yest to find apx drivers that work with it
Click to expand...
Click to collapse
I took your advices a while back not to upgrade my system to Win8 so I am still running Win7, hahaha....:silly::victory:

LetMeKnow said:
Why is it bricked? Can you boot into your bootloader? What is exactly you want to do to your device? Maybe, someone can help you if you can tell us more details about your device. Your bootloader version, ROM, kernel, stock firmware, and your current state of your problems...
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I took your advices a while back not to upgrade my system to Win8 so I am still running Win7, hahaha....:silly::victory:
Click to expand...
Click to collapse
I attempted to update my CM10 ROM to CM11. Went through the process of upgrading CWM via Clockwork ROM Manager but I suspect that it didn;t work.
Booted into CWM, did a factory reset and Dalvik Wipe. Then attempted to install the CM11 ROM. It failed (can;t remember th exact error).
After that I could restart into the recovery menu (3 icons) - but the next time I tried to restart I ended up where I am now.
Endless loop of the Asus logo with the "device is unlocked" mice type - that's the only screen I get.
I can get into APX mode (I think) but when I connect the tablet to a PC it's not recognized.
Can Asus do a factory repair? I know I'll get cahrged for it but at this point I have a near mint tablet, the keyboard and very expensive leather case that's just junk if not.

vexille said:
I attempted to update my CM10 ROM to CM11. Went through the process of upgrading CWM via Clockwork ROM Manager but I suspect that it didn;t work.
Booted into CWM, did a factory reset and Dalvik Wipe. Then attempted to install the CM11 ROM. It failed (can;t remember th exact error).
After that I could restart into the recovery menu (3 icons) - but the next time I tried to restart I ended up where I am now.
Endless loop of the Asus logo with the "device is unlocked" mice type - that's the only screen I get.
I can get into APX mode (I think) but when I connect the tablet to a PC it's not recognized.
Can Asus do a factory repair? I know I'll get cahrged for it but at this point I have a near mint tablet, the keyboard and very expensive leather case that's just junk if not.
Click to expand...
Click to collapse
I think that I know why your PC did not recognize your device... Do you know how to use ADB? What is happening when you enter "adb devices" in your adb prompt? Does your Asus screen have a spinning circle under Asus logo? I guessed that you are stuck at the bootloader screen and waiting for your OS to start so there is no spinning circle...
Please answer those questions above and maybe some experts can help you out... Good luck...

LetMeKnow said:
I think that I know why your PC did not recognize your device... Do you know how to use ADB? What is happening when you enter "adb devices" in your adb prompt? Does your Asus screen have a spinning circle under Asus logo? I guessed that you are stuck at the bootloader screen and waiting for your OS to start so there is no spinning circle...
Please answer those questions above and maybe some experts can help you out... Good luck...
Click to expand...
Click to collapse
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line

vexille said:
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
Click to expand...
Click to collapse
Oh well, you can not boot into your bootloader and can not get adb running. I hope that someone or experts can jump in and give you some good advices... Maybe, _that, sbdags, lj50036, and berndblb are actively helping users around here... good luck...:fingers-crossed:

vexille said:
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
Click to expand...
Click to collapse
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.

berndblb said:
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
Click to expand...
Click to collapse
Thanks!
I'll give these a try tonight.
I see a bunch on eBay for under $250 so I imagine it would be cheaper to just ditch this one if I can't get it working as opposed to sending it back to Asus for repair.

vexille said:
Thanks!
I'll give these a try tonight.
I see a bunch on eBay for under $250 so I imagine it would be cheaper to just ditch this one if I can't get it working as opposed to sending it back to Asus for repair.
Click to expand...
Click to collapse
I believe Asus charges $300+ for replacing the board, so yes, you're probably better off buying it on ebay.
Just don't ditch the old one too far - you may need the parts. Or you can sell them

berndblb said:
I believe Asus charges $300+ for replacing the board, so yes, you're probably better off buying it on ebay.
Just don't ditch the old one too far - you may need the parts. Or you can sell them
Click to expand...
Click to collapse
Well struck out on all accounts (I had left it plugged in at the Asus logo last night).
Appreciate all the help but I think it's eBay time for whatever I can get and sell the mobile dock and fancy leather case.
Then to decide what brand to get next....

berndblb said:
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
Click to expand...
Click to collapse
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:

LetMeKnow said:
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
Click to expand...
Click to collapse
I've tried every suggestion and cannot get past the "device is unlocked" mice type and static Asus logo.
When using adb it doesn't find any devices. I'll be putting it up eBay tomorrow for whatever I can get.
Looking at the new Samsung Galaxy 8.4 Pro as a replacement.

LetMeKnow said:
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Hi LMK - you can't win'em all...
I'm good - just returned from a family visit to Germany. Fighting the jetlag - groan. And having to go back to serious work Friday - big groan.
So what did you replace the 700 with - if anything? I get you're snatching it away from your nephew once in a while to do some testing? What kind of a uncle are you? You are probably ruining all his game scores! LOL

berndblb said:
Hi LMK - you can't win'em all...
I'm good - just returned from a family visit to Germany. Fighting the jetlag - groan. And having to go back to serious work Friday - big groan.
So what did you replace the 700 with - if anything? I get you're snatching it away from your nephew once in a while to do some testing? What kind of a uncle are you? You are probably ruining all his game scores! LOL
Click to expand...
Click to collapse
I hope that you had a great time with your family... I am still looking and have not decide it yet.. I always backup my stuff before messing with the device. Plus, my nephew has a few hour of playing on the tablet per day any way.. So I can take it any time that I want, hehe....:laugh: I also have a higher authority as an uncle...:silly:

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?

I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up

Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.

I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen

carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.

a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here

carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.

your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here

carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers

Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated

my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?

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.