Related
First off, my tf700 is rooted and unlocked. Now, after I flashed the US JB update through clockwork recovery, I lost recovery as expected. But what was unexpected was that i lost recovery completely. I installed TWRP through the goo app and now i have a working recovery. Here is the kicker, when i hold vol down and power I am brought the the screen that has several icons. They are RCK, the Android, USB icon(fastboot), and wipe data. I can only select the RCK option no matter how i try to select the other icons. both vol up and vol down select the highlighted icon.
Any help or suggestions would be greatly appreciated. Thanks
DroidEris1981 said:
First off, my tf700 is rooted and unlocked. Now, after I flashed the US JB update through clockwork recovery, I lost recovery as expected. But what was unexpected was that i lost recovery completely. I installed TWRP through the goo app and now i have a working recovery. Here is the kicker, when i hold vol down and power I am brought the the screen that has several icons. They are RCK, the Android, USB icon(fastboot), and wipe data. I can only select the RCK option no matter how i try to select the other icons. both vol up and vol down select the highlighted icon.
Any help or suggestions would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Imo,your recovery was still there after updating to Jelly Bean,but it was different from ICS (Volume down + Power get you directly to those icons) so you ended up installing TWRP.However,if your OS still starts you could try installing this recovery and maybe will help get fastboot back,even if i find it odd that recovery is working but fastboot not.
Pretoriano80 said:
Imo,your recovery was still there after updating to Jelly Bean,but it was different from ICS (Volume down + Power get you directly to those icons) so you ended up installing TWRP.However,if your OS still starts you could try installing this recovery and maybe will help get fastboot back,even if i find it odd that recovery is working but fastboot not.
Click to expand...
Click to collapse
Unless I'm reading the OP of the linked thread wrong, don't you need fastboot to flash that recovery in the first place? I'm also having issues getting fastboot to work.
Sent from my Incredible 2 using xda app-developers app
androidxen said:
Unless I'm reading the OP of the linked thread wrong, don't you need fastboot to flash that recovery in the first place? I'm also having issues getting fastboot to work.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
You can also use ADB to install a recovery.
it's not that fastboot isn't working. it's just that I can't highlight it to enable it. both Vol up and Vol down select the highlighted item. which in my case is RCK. I can't select anything other then that. I'll try the ADB commands when I get home.
thanks for getting back to me
SOLVED!
Well, I managed to fix my fastboot issues. All i had to do was downgrade to the stock .30 software then update back to the 10.4.4.16 OTA. At that point, I was able to access the fastboot mode and was able to flash the latest clockwork without issue. TOTAL PITA but everything works fine. Now time to root.
DroidEris1981 said:
Well, I managed to fix my fastboot issues. All i had to do was downgrade to the stock .30 software then update back to the 10.4.4.16 OTA. At that point, I was able to access the fastboot mode and was able to flash the latest clockwork without issue. TOTAL PITA but everything works fine. Now time to root.
Click to expand...
Click to collapse
+1
Real pain having to start over again....
UPDATE: Before you go the long route...... I left it for a while and later tried again and figured out that you can only scroll through the icons using the LEFT (volume down) button. The right button is the SELECT button, so just hit the vol-down again till you are on the fastboot icon, them the vol-up button!
SplicedX said:
First off, my tf700 is rooted and unlocked. Now, after I flashed the US JB update through clockwork recovery, I lost recovery as expected. But what was unexpected was that i lost recovery completely. I installed TWRP through the goo app and now i have a working recovery. Here is the kicker, when i hold vol down and power I am brought the the screen that has several icons. They are RCK, the Android, USB icon(fastboot), and wipe data. I can only select the RCK option no matter how i try to select the other icons. both vol up and vol down select the highlighted icon.
Any help or suggestions would be greatly appreciated. Thanks
Click to expand...
Click to collapse
I don't even have a USB icon, how do you get that icon? I have these 3 icons:
RCK
ANDROID
WIPE DATA
Neo3D said:
I don't even have a USB icon, how do you get that icon? I have these 3 icons:
RCK
ANDROID
WIPE DATA
Click to expand...
Click to collapse
JB does not have the USB icon. You are already in a fastboot mode when you boot into the bootloader. If you look at the fine prints in the upper left corner, you will see that you are in the fastboot mode..
fastboot working?
LetMeKnow said:
JB does not have the USB icon. You are already in a fastboot mode when you boot into the bootloader. If you look at the fine prints in the upper left corner, you will see that you are in the fastboot mode..
Click to expand...
Click to collapse
I also have this problem and when i plug my transformer in to my win8 pc, it does not seem to appear in device manager. when i boot twrp, it appears in device manager and appears in adb devices as "recovery" but in the opening bootloader mode, it doesn't seem to appear over usb... help this poor newb!
relaps said:
I also have this problem and when i plug my transformer in to my win8 pc, it does not seem to appear in device manager. when i boot twrp, it appears in device manager and appears in adb devices as "recovery" but in the opening bootloader mode, it doesn't seem to appear over usb... help this poor newb!
Click to expand...
Click to collapse
Win8 is a little tricky. You may not have a fastboot driver for your device. You could search around to see if you can find a driver for win8.. I think that sbdags has a win8 driver somewhere on his original post. Naked driver may work but you have to test it out for yourself because I don't have win8 to test, sorry... I will let you know if I can find the driver for win8.. What do you want to do with your device? You may be abe to achieve what you need with adb too, just a thought...
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
shreef said:
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
Click to expand...
Click to collapse
Do you have nvflash backup? if not, I believe you're done. You need to send out for repair.
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
ArmyAg08 said:
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
Click to expand...
Click to collapse
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
shreef said:
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
Click to expand...
Click to collapse
APX is NOT adb -- you need to issue commands using fastboot. Did you use the manufacturer's switch? "adb devices" won't return anything, even on a perfectly healthy 700. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1926286
and don't forget to use that switch: -i 0x0B05, as in
fastboot -i 0x0B05 <command>
For example, fastboot -i 0x0B05 devices or fastboot -i 0x0B05 reboot
EDIT: APX = FASTBOOT, for clarity.
MartyHulskemper said:
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
Click to expand...
Click to collapse
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
MartyHulskemper said:
APX is NOT adb -- you need to issue commands using fastboot.
Click to expand...
Click to collapse
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
shreef said:
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
Click to expand...
Click to collapse
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
OK, I have sent it to ASUS!
Thank you guys for your care and help.
Regards
ArmyAg08 said:
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You're right. I wasn't mad/annoyed at your post. I just wanted to point out it has been known for a while now that ROM Manager does funky things on the 700. I'd just stay away from it -- iIn the sense that if one aspect of a program is broken by a device's particulars, changes are relatively high that some other aspect(s) is/are broken as well and you might get to know which one(s) that is/are by first-hand experience.
_that said:
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
Click to expand...
Click to collapse
You're right. I was cutting the curve. I'm sorry for the confusion.
okantomi said:
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
Click to expand...
Click to collapse
That is quite the accurate summary.
@OP: hope ASUS treats your device nicely and you can get back in our midst with a 700 working well for you, soon.
Tablet: ASUS TF300T, Unlocked.
SO: Cyanogen 10
Old (working) Recovery ROM: “recovery-jb.img”
New (NOT working) Recovery ROM: “recovery-clockwork-5.5.0.4-tf300t.img”
Keys combination don’t work, just the APX one.
Symptom: the cyanogen didn’t work well so I changed the recovery ROM. As the new Recovery locks when executing from the bootloader, I decided to restart in recovery directly from the cyanogen (power button –>Reset -> Reset into Recovery). VERY BAD IDEA: Now the tablet always tries to start in recovery and gets stuck on the start screen. I can only enter the APX with keys combination. I cant enter boot loader and ATX doesn’t recognize fastboot & adb instructions.
Hi, I believe cyanogen 10 uses a jellybean bootloader and CWM 5.5.0.4 is for an ICS bootloader, so you will need to flash CWM 6.0.2.3 which is for jellybean bootloader.
Have a look at link below and download 'recovery-jb.img' & follow the how to flash.
http://forum.xda-developers.com/showthread.php?t=1668173
Hope this helps.
santdiego said:
Hi!
I have cyanogen 10 installed, but I tried to change my Tf300T Clockwork Recovery with this rom: "recovery-clockwork-5.5.0.4-tf300t.img"
Click to expand...
Click to collapse
Why?
pjc21 said:
Hi, I believe cyanogen 10 uses a jellybean bootloader and CWM 5.5.0.4 is for an ICS bootloader, so you will need to flash CWM 6.0.2.3 which is for jellybean bootloader.
Have a look at link below and download 'recovery-jb.img' & follow the how to flash.
http://forum.xda-developers.com/showthread.php?t=1668173
Hope this helps.
Click to expand...
Click to collapse
Hi! the problem is that I am stuck in the first screen when I turn on the tablet. The keys don't respond, the USB dont work , I cant go into bootloader and cyanogen dont start. It is just in the first screen since it try to boot from recovery always.
NixZero said:
Why?
Click to expand...
Click to collapse
My cyanogen didn't work fine. When I saw this article I thought that maybe I had installed a wrong ROM so i change it with the instructive one.... bad idea...
Have a look here
http://forum.xda-developers.com/showthread.php?t=2034866
pjc21 said:
Have a look here
http://forum.xda-developers.com/showthread.php?t=2034866
Click to expand...
Click to collapse
I think it goes into APX mode, holding "vol +", the screen remains off but the USB recognizes the APX. What should I do at this point to re install the ROM CWM or enter bootloader? when I go out the APX mode all remains the same, the tablet is still stuck .
Ok I no expert here so anyone else please correct me if I'm wrong.
When you say the USB recognizes APK, do you mean (assuming your running windows) that you can see your tab in device manager - something like 'Asus Android Device - Asus Android Bootloader Interface'
If so try this, open cmd (I always run as admin, don't know if it makes a difference) navigate to your /android-sdk/platform-tools and type
'fastboot -i 0x0B05 device' and hopefully you will get a response about your device (tab). If you do I would assume you could then flash recovery, ie put recovery-jb.img in your platform-tools folder and in cmd type 'fastboot -i 0x0B05 flash recovery recovery-jb.img' once done type 'fastboot -i 0x0B05 reboot' and hopefully all will be good, you may then need to reflash you rom not sure.
If your tab does not show in device manager then I have no idea sorry.
Hope this helps.
pjc21 said:
Ok I no expert here so anyone else please correct me if I'm wrong.
When you say the USB recognizes APK, do you mean (assuming your running windows) that you can see your tab in device manager - something like 'Asus Android Device - Asus Android Bootloader Interface'
If so try this, open cmd (I always run as admin, don't know if it makes a difference) navigate to your /android-sdk/platform-tools and type
'fastboot -i 0x0B05 device' and hopefully you will get a response about your device (tab). If you do I would assume you could then flash recovery, ie put recovery-jb.img in your platform-tools folder and in cmd type 'fastboot -i 0x0B05 flash recovery recovery-jb.img' once done type 'fastboot -i 0x0B05 reboot' and hopefully all will be good, you may then need to reflash you rom not sure.
If your tab does not show in device manager then I have no idea sorry.
Hope this helps.
Click to expand...
Click to collapse
Hi! thx for your help. fastboot and adb don't recognize the tablet in APX mode. My PC recognize APX mode. I installed the drivers for APX and I have nvflash ready to work, but it seems to be useless without access to fastboot.
pjc21 said:
'fastboot -i 0x0B05 device'
Hope this helps.
Click to expand...
Click to collapse
respond "< waiting for device >"
You have to wait for NVflash for JB bootloader.
Hazard17 said:
You have to wait for NVflash for JB bootloader.
Click to expand...
Click to collapse
Hi I have NVflash from here: http://androidroot.mobi/t3_nvflash/ butt this method also use fastboot and i cant access to it.
Hi, sorry to say after alot of searching and reading looks like the only soluation is to send it to Asus for repair.
I have been trying to put cwm on the tf300t for about two days now reading everything and still got no where. The device is unlocked i used asus apk to unlock it. every time i do the power and down step i do not have the usb option just rck, cold start, wipe data. i cant do anything with fast boot to put cwm onto the tablet. any help would be appreciated. i tried reinstalling fast boot and reseting the tablet. i am on 4.2.1
Which guide are you using? The 4.2 bootloader automatically connects in fastboot mode as far as I know when you get into the bootloader menu which is why the USB icon isn't there. You should be able to use fastboot commands whilst in the bootloader menu
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
Which guide are you using? The 4.2 bootloader automatically connects in fastboot mode as far as I know when you get into the bootloader menu which is why the USB icon isn't there. You should be able to use fastboot commands whilst in the bootloader menu
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
I did read that somewhere and i tried running the recovery through fastboot but it just says waiting and does nothing. I also noticed when i plug it into the computer it says fastboot on the usb but it has a little symbol next to it as if it wasnt running right,but i have reinstalled it a few times
AFAIK, there is no version of CWM compatible with the 4.2 bootloader. You'll need to use the TWRP versions that end with -42.
I have tried installing TWRP running command "fastboot -i 0x0B05 flash recovery twrp.blob" still no luck just says waiting for device and the tablet stays at the rck screen
HELP
my asus transformer tablet TF700T not start me and when I turn on fatboots goes straight to recovery mode and flash the recovery and not fully started and when I enter apx mode the screen goes black and the pc but nothing happens reconose urgent help is a very good tablet and do not want to lose
We will need quite a bit more information to be able to help.
What rom are your running?
What recovery?
What bootloader?
What did you do when this happened?
Did you use "Wipe Data" from the bootloader menu?
When the tablet is booted to recovery, do you have ADB access?
Sent from my K00C using Tapatalk
berndblb said:
We will need quite a bit more information to be able to help.
What rom are your running?
What recovery?
What bootloader?
What did you do when this happened?
Did you use "Wipe Data" from the bootloader menu?
When the tablet is booted to recovery, do you have ADB access?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
hello not that bootloader used is the fastboot mode was upgraded by that updates the tablet occupying official firmware us sku and if ise a wipe data from fastboot and when I turned on me is in recovery and enpiesa to flash if I could mean and how to fix it and what I learned is that the adb is used from the fatboot of which I can not enter because it goes straight to recovery and flash not even fully into the
I guess you are using a translator for these posts?
Could you please try to seperate sentences?
It is very hard to read and understand what you are trying to say.
We need your bootloader version number. For example: 10.6.1.14.10 would be the latest. What do you have installed?
We also need the recovery version number. For example: TWRP 2.6.1 would be one possibility.
It sounds as if you installed an incompatible recovery and then used "Wipe Data" from the bootloader which is not a good idea.....
You are in a "forced reboot to recovery loop".
You do not need access to the bootloader for ADB to work in recovery. Try searching web pages in your language to get ADB drivers installed on your PC.
Sent from my K00C using Tapatalk
---------- Post added at 09:21 PM ---------- Previous post was at 09:15 PM ----------
Actually reading your post again it sounds as if you are on stock firmware.
Did you install a custom recovery?
If not, reboot the tablet. It will start the recovery.
Connect the tablet to a power source and leave it like that overnight.
It could be that the recovery is still trying to finish the "Wipe Data" command and you keep interrupting it.
Leave it alone for 6 hours.
Sent from my K00C using Tapatalk
berndblb said:
I guess you are using a translator for these posts?
Could you please try to seperate sentences?
It is very hard to read and understand what you are trying to say.
We need your bootloader version number. For example: 10.6.1.14.10 would be the latest. What do you have installed?
We also need the recovery version number. For example: TWRP 2.6.1 would be one possibility.
It sounds as if you installed an incompatible recovery and then used "Wipe Data" from the bootloader which is not a good idea.....
You are in a "forced reboot to recovery loop".
You do not need access to the bootloader for ADB to work in recovery. Try searching web pages in your language to get ADB drivers installed on your PC.
Sent from my K00C using Tapatalk
---------- Post added at 09:21 PM ---------- Previous post was at 09:15 PM ----------
Actually reading your post again it sounds as if you are on stock firmware.
Did you install a custom recovery?
If not, reboot the tablet. It will start the recovery.
Connect the tablet to a power source and leave it like that overnight.
It could be that the recovery is still trying to finish the "Wipe Data" command and you keep interrupting it.
Leave it alone for 6 hours.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
firmware version is 10.6.1.14.10 and TWRP recovery is 2.7.0.0 and donot like making procedure adb if I could provide a link to the procedure by a thank ....... adb serious look at what step was I did the update and then did a wipe data and when you start the blinking recovey
Ok, I got the first part and your bootloader/recovery combination is fine.
Could you try different words to explain what you meant by this:
israelmena59 said:
adb serious look at what step was I did the update and then did a wipe data and when you start the blinking recovey
Click to expand...
Click to collapse
berndblb said:
Ok, I got the first part and your bootloader/recovery combination is fine.
Could you try different words to explain what you meant by this:
Click to expand...
Click to collapse
what happened is that when I did a wipe data update from fatboot
I did the upgrade and then wipe data from fastboot .....go into recovery and is blinking and then fail the recovery
israelmena59 said:
what happened is that when I did a wipe data update from fatboot
I did the upgrade and then wipe data from fastboot .....go into recovery and is blinking and then fail the recovery
Click to expand...
Click to collapse
I don't understand. What do you mean by "blinking recovery and then fail the recovery"??
Do you see an Android falling on his back with an open belly and exclamation mark?
That wold be the stock recovery, but you said you had TWRP 2.7 installed????
Sent from my K00C using Tapatalk
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
berndblb said:
I don't understand. What do you mean by "blinking recovery and then fail the recovery"??
Do you see an Android falling on his back with an open belly and exclamation mark?
That wold be the stock recovery, but you said you had TWRP 2.7 installed????
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I send you a video so you can see what happens when you turn
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
israelmena59 said:
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
I send you a video so you can see what happens when you turn
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
Click to expand...
Click to collapse
I send you a video so you can see what happens when you turn
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
Yes, I think you have a forced reboot to recovery issue.
It's not clear from that video at which point you let go of the buttons, but I think you don't press them long enough.
We have to see if you can get into fastboot.
Keep holding Power and Volume Down past the first Asus screen and until you see a screen with 3 icons: RCK, Android and Wipe Data.
Confirm if you can get to that screen.
Sent from my K00C using Tapatalk
berndblb said:
Yes, I think you have a forced reboot to recovery issue.
It's not clear from that video at which point you let go of the buttons, but I think you don't press them long enough.
We have to see if you can get into fastboot.
Keep holding Power and Volume Down past the first Asus screen and until you see a screen with 3 icons: RCK, Android and Wipe Data.
Confirm if you can get to that screen.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I can not get to fastboot
israelmena59 said:
I can not get to fastboot
Click to expand...
Click to collapse
Connect your tablet via original USB cable to your PC.
Open Device Manager if you are on Windows.
Boot the tablet and let it loop on the TWRP logo.
Does it get recognized in Device Manager in any way? Any change in the list of connected devices?
If not, I'm afraid this is a brick.
Sorry
berndblb said:
Connect your tablet via original USB cable to your PC.
Open Device Manager if you are on Windows.
Boot the tablet and let it loop on the TWRP logo.
Does it get recognized in Device Manager in any way? Any change in the list of connected devices?
If not, I'm afraid this is a brick.
Sorry
Click to expand...
Click to collapse
appears a driver called "transformer"
israelmena59 said:
appears a driver called "transformer"
Click to expand...
Click to collapse
Ahhhh - a shimmer of hope! That is good news.
Does the driver show a yellow triangle with ! in it?
If not - even better.
Do you have ADB and/or fastboot installed on your PC?
Sent from my K00C using Tapatalk
berndblb said:
Ahhhh - a shimmer of hope! That is good news.
Does the driver show a yellow triangle with ! in it?
If not - even better.
Do you have ADB and/or fastboot installed on your PC?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
if it appears with a yellow triangle
as I install adb or fastboot on pc
israelmena59 said:
if it appears with a yellow triangle
as I install adb or fastboot on pc
Click to expand...
Click to collapse
Sorry, I don't understand. Is that a yes or no on having adb/fastboot installed?
berndblb said:
Sorry, I don't understand. Is that a yes or no on having adb/fastboot installed?
Click to expand...
Click to collapse
no no I have installed adb / fastboot on pc
as I install adb or fastboot
but first let's focus on the problem and I can fix it
israelmena59 said:
no no I have installed adb / fastboot on pc
as I install adb or fastboot
but first let's focus on the problem and I can fix it
Click to expand...
Click to collapse
Don't understand your last sentence.
But if you have adb, open a command prompt from the folder where you're adb.exe is and issue this command:
Code:
adb devices
If that returns a string of numbers and letters, you have an adb connection to the tablet.
If it returns nothing you'll have to get the correct drivers.
But try this first and we'll see...
berndblb said:
Don't understand your last sentence.
But if you have adb, open a command prompt from the folder where you're adb.exe is and issue this command:
Code:
adb devices
If that returns a string of numbers and letters, you have an adb connection to the tablet.
If it returns nothing you'll have to get the correct drivers.
But try this first and we'll see...
Click to expand...
Click to collapse
a link to download adb