Hi guys!
Long story short I have a TF101G stuck in bootloop after a failed attempt to install a new recovery, I searched here for a possible solution and i found "OneClickRecovery" that seems to suit my situation perfectly.
My problem is that my device in not recognized by my computer (windows 10, but i tried also Ubuntu and Windows 7): when i plug it, device manager doesn't read any new device.
I manage to get it recognized in APX mode, but from what i have read around this forum solution as "wheelie" and "Easyflasher" works only for TF101.
Thanking you in advance for your help in this matter, I look forward to your reply
Related
Purchased a gtablet, all went smooth after I installed the TNT Rom, but found some sound issues, and found out that seemed to plague a lot of other people, so decided to try another ROM - can't even recall which one now. But now where I'm stuck at is if I hold down vol up and power, I get "Recovery key detected Booting recovery kernel image" and it sits there forever. Even if I take out the microsd card, I get the same screen. A normal power attempt sits forever at the Viewsonic "birds" screen. I've tried just about every rom, none take . I'm pretty sure I had the clockwork recoverymod installed, but now I can't even get into that.
I tried volume down + power, (ATP mode?) but none of the drivers I've found are for Windows 7 64 bit, so I can't access the tablet in that mode because the lack of drivers.
Any suggestions on what to do from here?
Thanks!
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
http://forum.xda-developers.com/showpost.php?p=9302497&postcount=5
Bottom of instructions section -- a few users have written posts on nvflash for windows.
LGCubana said:
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
Click to expand...
Click to collapse
Hi,
Thanks for the link.. I think I've seen that - I don't see a APX driver missing in Device Manager - there is a ADB Interface, however when I let that install drivers, it says the Device cannot start - Code 10.
I may have another computer I can boot up and try
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
butchconner said:
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
Click to expand...
Click to collapse
It did work on my old POS XP Laptop I knew that thing was useful for something!
Thanks again.. Never thought I'd be so happy to see "TapnTap" again. And now I'm up and running on the Vegan rom
Hello,
Sorry if this has been asked before. I have a TF300T that I can see when the tablet is booted when I connect it to Windows (Win7 x64). However, when I boot to TWRP, I can't seem to access the device. It shows up in Device Manager as 'Transformer' with the typical yellow triangle. I can't seem to find any drivers that make it work. Any suggestions would be greatly appreciate. Thanks.
Aesrys said:
Hello,
Sorry if this has been asked before. I have a TF300T that I can see when the tablet is boohen I connect it to Windows (Win7 x64). However, when I boot to TWRP, I can't seem to access the device. It shows up in Device Manager as 'Transformer' with the typical yellow triangle. I can't seem to find any drivers that make it work. Any suggestions would be greatly appreciate. Thanks.
Click to expand...
Click to collapse
Just curious why you would need to connect your tablet to your computer while in the recovery mode? Honestly I don't think you can do this.
Aesrys said:
Hello,
Sorry if this has been asked before. I have a TF300T that I can see when the tablet is booted when I connect it to Windows (Win7 x64). However, when I boot to TWRP, I can't seem to access the device. It shows up in Device Manager as 'Transformer' with the typical yellow triangle. I can't seem to find any drivers that make it work. Any suggestions would be greatly appreciate. Thanks.
Click to expand...
Click to collapse
I have seen several posts using transformer 201 drivers to correct this problem. I'll try to locate them shortly and report back.
This mode will work with adb and sideload adb.
Looks like this is most popular now. http://forum.xda-developers.com/showthread.php?t=1766220
Note: For this version of twrp if adb fails update your adb.
Hi, I'm kinda of a noob at this stuff, but I've learned quite a bit recently from just reading around, so bear with me if I don't understand or need more specific instructions. I have the trio stealth pro 7 and it is always stuck on the boot screen with the android logo when I boot. I was attempting to flash cm9 on the tablet but after I wiped the tablet initially, i couldnt find the cm9 rom on my internal memory while in recovery mode, so I ended up turning off my tablet, which now doesn't boot up anymore (stuck with android logo).
I found a fix where you can use livesuite and adb to fix this issue; however, after installing adb, my tablet is not being detected, (my phone does). My tablet is not being recognized by windows in general, and it doesn't show up under device manager. There was one part of the step where I need to install usb drivers for the tablet; however, I cant find any online. I have used the tablet before with my computer before the attempt to flash cm9, so I am guessing drivers should already be installed. I feel I can get this issue fixed if I can just get adb to recognize my tablet.
Perhaps this fix is not the one I need and maybe there's a simpler fix. I'm just too dumb to have realized it. Another note to add is, pressing the combination of power and volume buttons does nothing. Please help!!! thank you!!
Hi!
Yesterday I rooted my LG P500, then I wanted to make a backup from CWM from the phone. Now the I stucked in fastboot mode.
I have read many articles about this problem, and I could solve it, but my computer (win7 64 bit) cannot detect the phone correctly. I have tried with a lot of drivers, official ones, unofficial ones, but no connection can be made to the device.
In the device manager a single unknown device called "Android" can be found. Can anyone help me? Thanks.
Senki1988 said:
Hi!
Yesterday I rooted my LG P500, then I wanted to make a backup from CWM from the phone. Now the I stucked in fastboot mode.
I have read many articles about this problem, and I could solve it, but my computer (win7 64 bit) cannot detect the phone correctly. I have tried with a lot of drivers, official ones, unofficial ones, but no connection can be made to the device.
In the device manager a single unknown device called "Android" can be found. Can anyone help me? Thanks.
Click to expand...
Click to collapse
Fortunatelly I could unbrick the phone by using lgmdp. After I got recovery console and I could restore my rom.
Senki1988 said:
In the device manager a single unknown device called "Android" can be found. Can anyone help me? Thanks.
Click to expand...
Click to collapse
Force Windows to install the Android Single Sooner Interface by going thru the steps to manually update/install a driver.
Hello everyone, I bought a brand new IPPO Q78 (Android 4.0.4) via focalprice.com 2 month ago. First day of using it, and by using I mean simply installing a few apps, and after reboot, I got BOOT LOOP problem, so it wasn't able to get to tablets home screen. After lot of reading about similar problems, I was able to successfully unbrick it using (I suggest others with same cheap china tablet that are also soft bricked to use this program, it really was the only one which helped me):
http://forum.gsmhosting.com/vbb/f781/android-tablet-wifi-cpu-a10-a13-wipe-rom-easy-zakir-gsm-1656461
Here is my situation now, you can view it:
http://www.youtube.com/watch?v=cU1KYIrvZWI
Before, when it was soft bricked, at least after this android logo came the android animation that looped forever, but my computer was able to recognize and install the drivers for Android ADB device, now it can't, it won't recognize my tablet no matter what, ONLY when I press volume up and connect it to usb port, then it recognizes and installs vid_1f3a_pid_efe8 driver, which also I cannot use with LiveSuite, why? I really don't know, I've tried every possible solution found on forums (mainly here, but elsewhere also).
Whole this situation is a result of me doing the CWM upgrade/install, I'm a newbie, so I cannot tell for sure what was it, I just know it was from xda--developers forum, more accurately this thread:
http://forum.xda-developers.com/showthread.php?t=2189640
after this, poof. I think it is hard bricked, and my question is, is there a way to flash it (btw, tablet is rooted) by only having access through mentioned driver vid_1f3a_pid_efe8 and without LiveSuit, cause I would have to download and try a 100 ROM's before I pin the one that suits my tablet. It's really a tough program to deal with, but if it's the only one, I would gladly format and reinstall my Windows OS as many times I need to to get it working.