Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
I used to have a rooted EVO 4G through work, but recently they switched me over to an iSheep, and as you can imagine I absolutely hate it. And since it’s for work they’ve installed AirWatch so I can’t jailbreak it. But I also have a TF101 that's currently not rooted.
I got my TF101 about a year ago and rooted it like every good android user should. But after about 6 months, I found a small hair line crack in the touch screen. I unrooted it and sent it in to ASUS for them to repair. I always keep my tablet closed in the docking station when it wasn’t in use. I then found this thread, http://forum.xda-developers.com/showthread.php?t=1498237 that stated this is why the screen cracked. So ASUS and I went back and forth for about a month before they finally covered it under warranty and repaired my tablet.
When I got my tablet back I found they upgraded it to 9.2.1.27. I connected it to a computer so I could reroot it, but my tablet is no longer detected by a computer. I tried two computers and two data cables. I’ve also tried all the methods for installing the drivers. I didn’t want to send it back to ASUS due to the issues I previously had with them. I’ve been following Thing O Doom’s thread, http://forum.xda-developers.com/showthread.php?t=1681155 because he stated he's working on a rooting apk, but he no longer has his TF101 so progress has been slow.
But in my searching I found this thread,http://www.transformerforums.com/fo...rmed-fix-gain-root-after-8-6-5-21-update.html that stated I can get the zip out of an old ASUS update and put that on my sdcard and let the tablet update itself to an older version. ASUS made an instruction sheet for manually updating with a zip, http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101G/e6754_TF101_Update_SOP.pdf. Once downgraded I could use RazerClaw http://forum.xda-developers.com/showthread.php?t=1345049 to root, and then flash a recovery, rom, etc.
Will this method work? I have to believe no, it just seems too easy. I haven’t tried it yet because I worried about bricking my tablet and not being able to fix it since it won’t connect to a computer.
Any response, opinion, recommendation, experience would be greatly appreciated.
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
frederuco said:
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
Click to expand...
Click to collapse
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
You may be able to use Wolf's tut for this...
benmatlock said:
You may be able to use Wolf's tut for this...
Click to expand...
Click to collapse
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
air adb, there's at least 1 good free one in the play store.
Lethe6 said:
air adb, there's at least 1 good free one in the play store.
Click to expand...
Click to collapse
Thanks for the response, I looked into that and I thought you had to be rooted for it to work. I'll look at it again.
akt27x said:
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
Click to expand...
Click to collapse
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
akt27x said:
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
Click to expand...
Click to collapse
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
frederuco said:
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
Click to expand...
Click to collapse
I tried this and you're right it didn't install the older firmware. It looked like it was going to because the status bar was moving at the bottom, but after a few minutes it went to an android laying down with his guts open and a exclamation mark above him.
benmatlock said:
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
Click to expand...
Click to collapse
I think I've tried this. I have a terminal emulator installed and I followed some instructions about entering things like this in but I think I got a message stating access denied. But I'll try it again tonight and reply back with the results.
Re: [Q] Possible Downgrade to Root
Using wolf's instructions I tried this with a terminal app on my tablet and got the following.
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
I then tried this and got the following.
[email protected]:/ $ dd if=/sdcard/recoveryblob.bin of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
Sent from my Transformer TF101 using XDA Premium HD app
Woody said:
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
Click to expand...
Click to collapse
This weekend I tried to install the drivers again. I first went through the control panel and device manager and deleted anything that said android and asus, then rebooted my computer. I then tried to install PDANet because I read that it'll install the drivers needed and if you're having a problem it's an easy way to install them. During the PDANet install it told me to plug my transformer in to load the drivers. When I did it said it was installing new drivers but then it said they didn't install. My transformer came up as an unknown device in device manager.
I then went through and deleted the unknown device and checked in the control panel again, then rebooted my computer. I then put my tablet in APX mode to try and get it to load the drivers. Again it didn't install them and my transformer came up as an unknown device. I deleted the unknown device agian, rebooted, and went to ASUS website and installed ASUS Sync. When it finished I rebooted and then started ASUS Sync. Again when I connected my transformer to my computer it said it was loading the drivers, then it failed, and the computer showed my transformer as an unknown device. ASUS Sync also stated there was no device connected to it.
All the reading I've been doing, it seems like there are some other people experiencing the same issues I am, and I haven't seen where anybody has posted a solution. If anybody has any input please let me know.
I think I'm getting closer. I downloaded WLanAdb from the play store and followed the directions and downloaded the needed files to my computer. In the command prompt I type "WLanAdbTerminal devices" and my tablet will show in the list of devices. But WLanAdb is only setup to except a few commands, the main purpose of the app is for pushing files. It was the only wireless ADB app that I could find that didn't require root.
I then found SSHDroid in the play market and I downloaded putty to my computer. I connect to my computer using that. When I type "adb devices" I get a mesage that states
daemon not running. starting it now on port 5038
daemon started successfully
List of devices attached
I then left putty and went back to the command prompt and typed "adb connect (with my ip address and port from SSHDroid)" and it said it connected to that ip address and port. I then type "adb devices" and there are no devices listed.
Again I think I'm very close to getting my tablet connected wirelessly to adb. I think there is just one simply thing I'm missing. Any help would be greatly appreciated.
I'll continue to update this thread until my tablet is rooted or I reach a dead end, so this will be a reference for anybody experiencing the same issues as me.
Thanks in advance.
akt27x, did you ever come to a solution?
presbypenguin said:
akt27x, did you ever come to a solution?
Click to expand...
Click to collapse
I haven't. I'm now trying to make a Linux boot flash drive to see if I can get my tablet to connect that way, since I've read that Linux doesn't require drivers. I downloaded LinuxLive USB Creator but haven't had the time to try it yet.
Afternoon guys,
Before anyone has a go at me, I've have spent about five hours looking through this forum for what I'm looking for and i've tried all the easy unroot/easy flasher/etc and got all the stock Asus rom and recovery. AND the forum search is temporarily unavailable.
So here is what I have:
ClockworkMod Recovery v5.8.3.4
Liquid Smooth Rom
I have installed the stock rom, recovery and wiped everything.
If i press the power button it loads into CWM recovery.
If i press power and down vol, it loads to the wipe data/load android screen, and which it hangs on forever,
So I guess what im asking you good people of the internet is:
A) How do I finally get rid of CWM Recovery (because even if i install another recovery it boots back to CWM), and
B) How on gods earth do I get back to stock?
Now I know people are going to be like search the forums, I have, and I've tried literally everything that everyone has posted, and clearly while it's worked for millions of other people, my tablet is retarded and doesnt want to follow the norm.
Also i am the greatest noob ever.
Any help would be greatly appreciated.
Thanks
Hmmm, did you unzip the stock ROM once before flashing (it will still be a zip).
Otherwise, try using EasyFlasher and APX mode. For EasyFlasher, do not unzip the stock ROM, use it as it downloads from Asus.
killerkuk said:
Afternoon guys,
Before anyone has a go at me, I've have spent about five hours looking through this forum for what I'm looking for and i've tried all the easy unroot/easy flasher/etc and got all the stock Asus rom and recovery. AND the forum search is temporarily unavailable.
So here is what I have:
ClockworkMod Recovery v5.8.3.4
Liquid Smooth Rom
I have installed the stock rom, recovery and wiped everything.
If i press the power button it loads into CWM recovery.
If i press power and down vol, it loads to the wipe data/load android screen, and which it hangs on forever,
So I guess what im asking you good people of the internet is:
A) How do I finally get rid of CWM Recovery (because even if i install another recovery it boots back to CWM), and
B) How on gods earth do I get back to stock?
Now I know people are going to be like search the forums, I have, and I've tried literally everything that everyone has posted, and clearly while it's worked for millions of other people, my tablet is retarded and doesnt want to follow the norm.
Also i am the greatest noob ever.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
If your TF is SBK1 (Serial B6O or earlier, some B7Os work too) you can use NVFlash
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Stick the TF into APX mode (Vol up & Power from Powered Off state)
Run download.bat as Admin (Right click > Run as Admin)
@frederuco
I did unzip it and install it. It still hangs.
I tried EasyFlasher, but for some reason I run through it and the process completes, when i reboot the tablet nothing has changed.
@*Detection*
I can't get the link to work for some reason.
Thanks for your help so far, but stupid tablet stays stupid!
killerkuk said:
@frederuco
I did unzip it and install it. It still hangs.
I tried EasyFlasher, but for some reason I run through it and the process completes, when i reboot the tablet nothing has changed.
@*Detection*
I can't get the link to work for some reason.
Thanks for your help so far, but stupid tablet stays stupid!
Click to expand...
Click to collapse
Try the direct links here
WW and US in that order
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Otherwise go to http://www.xdafileserver.nl and navigate to stock ROMs section
*Detection* said:
Try the direct links here
WW and US in that order
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Otherwise go to http://www.xdafileserver.nl and navigate to stock ROMs section
Click to expand...
Click to collapse
Much appreciated! :good:
Fingers crossed this works!
*Detection* said:
If your TF is SBK1 (Serial B6O or earlier, some B7Os work too) you can use NVFlash
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Stick the TF into APX mode (Vol up & Power from Powered Off state)
Run download.bat as Admin (Right click > Run as Admin)
Click to expand...
Click to collapse
I downloaded it and ran it as admin, DOS flashed up and disappeared before i could read what it said.
the nvflash app does the same, even when i run as admin.
maybe this is a lost cause..
killerkuk said:
I downloaded it and ran it as admin, DOS flashed up and disappeared before i could read what it said.
the nvflash app does the same, even when i run as admin.
maybe this is a lost cause..
Click to expand...
Click to collapse
What is the first 3 characters of your tablet serial?
And was it in APX mode connected to PC USB with APX drivers installed ?
*Detection* said:
What is the first 3 characters of your tablet serial?
And was it in APX mode connected to PC USB with APX drivers installed ?
Click to expand...
Click to collapse
The serial starts with B40.
Im on a mac (as i have no access to a pc) but have VMWARE running windows 7, with APX drivers on it.
When i put it in APX mode, it comes up that it is connected as Nvidia APX device.
Could this be where I'm going wrong?
killerkuk said:
The serial starts with B40.
Im on a mac (as i have no access to a pc) but have VMWARE running windows 7, with APX drivers on it.
When i put it in APX mode, it comes up that it is connected as Nvidia APX device.
Could this be where I'm going wrong?
Click to expand...
Click to collapse
Yea probably, I've never tried using NVFlash on anything other than a PC running Windows
Try updating the NVidia APX Device with these drivers
http://forum.xda-developers.com/attachment.php?attachmentid=1489867&d=1353190140
Chances are its the drivers running on the Mac that are causing the problem with the USB > VMWare > TF101
I know nothing about Mac, but I heard you can install Windows 7 almost natively using Bootcamp or something? Might be worth trying that if you can't do it in VMWare
*Detection* said:
Yea probably, I've never tried using NVFlash on anything other than a PC running Windows
Try updating the NVidia APX Device with these drivers
http://forum.xda-developers.com/attachment.php?attachmentid=1489867&d=1353190140
Chances are its the drivers running on the Mac that are causing the problem with the USB > VMWare > TF101
I know nothing about Mac, but I heard you can install Windows 7 almost natively using Bootcamp or something? Might be worth trying that if you can't do it in VMWare
Click to expand...
Click to collapse
thanks dude, looks like i need a trip to a friends house!
killerkuk said:
thanks dude, looks like i need a trip to a friends house!
Click to expand...
Click to collapse
Good luck!
*Detection* said:
Good luck!
Click to expand...
Click to collapse
Thanks for your help!
All sorted and back to stock. looks like it was an issue with the mac. plugged it into a pc and everything worked out fine!
WOOOOOOOOOOOOOOOOOOOOOOOOO!!!
killerkuk said:
Thanks for your help!
All sorted and back to stock. looks like it was an issue with the mac. plugged it into a pc and everything worked out fine!
WOOOOOOOOOOOOOOOOOOOOOOOOO!!!
Click to expand...
Click to collapse
Great!
At least you know now you can do what you like with it firmware / ROM / Recovery wise, and always be able to return it to stock, you can't break APX mode unless you physically damage the tablet
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Click to expand...
Click to collapse
Are you using windows?
Did you try this?
Transformer Toolkit v2.0.1
Root your device with motochopper: http://forum.xda-developers.com/showthread.php?t=2230763
and from the playstore download and install goomanager and from goomanager install TWRP.
Then from TWRP flash CROMi-X
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
Click to expand...
Click to collapse
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
berndblb said:
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
Click to expand...
Click to collapse
Well I had tried motochopper around 20x before (and sadly, I am not exaggerating there) without it working once, but I felt that I should at least give it one more shot before saying I couldn't use it and of course now that I had asked for help it does work. lol; the IT curse strikes again. Thanks for that, monecani.
The drivers, on the other hand, are not working. :/ Windows is letting me try to install them now at least (before it was telling me there was "no compatible drivers" when I was literally having it select the ASUS specific ADB USB drivers, or just telling me that it had determined that my usb drivers that were in no way functioning were completely up to date), but then it fails install and says "This device cannot start. (Code 10)". I was able to install the drivers you gave me when the device was in launcher, but they didn't help me in fastboot, and actually interfered with my device being recognized properly by anything. I had to roll back the drivers to run motochopper.
I kinda agree with you on fastboot being something I don't strictly need, but would still be a good idea for me to have access to. Plus, I'm that special kind of person who cannot let something just be broken. It drives me crazy to know that something's wrong, even if I almost never use it, or even never use it.
Hello, first post on this forum, so yeah ^^ I am also kinda new to this. I have a gs3 which is rooted and all, but that is old, and methods has changed...
So i tried to root my shield tablet and it got stuck in a boot loop. I can not get it into the bootloader using adb tools, or fastboot, or atleast i knot know how to. I have ran the: adb reboot bootloader, without success. I have also tried the: adb devices command and i dont see my device there. I have installed mini adb drivers.
This happend when using this tool(windroid): http://forum.xda-developers.com/showthread.php?t=2499926
So im thinking that if there is a way to get out of this, that would be great. I really hope i have not bricked it... all i wanted to to was to get root so that i could connect a ps3 controller... :/
I tried to use the windroid program but the recovery did not install. so i did it manually following this tut http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
im am not complaining or anything, purly looking for help.
So, after trying i got it up and running. i did not flash any supersu.zip files, just installed it from the market. wen it asked me to reboot the device ended up like this. I am aware of the disclaimers and stuff. If i go to device manager on my computer i can se: SHIELD Tablet, with a yellow triangle. I also searched youtube and this forum to look for posts, but found none that could help.
image: https://www.dropbox.com/s/16y1icl89etg9q9/2015-04-18%2015.36.46.jpg?dl=0[/IMG]
**Update** I found out how to get into the bootloader manually, so ill continue trying...
I'm done
xswish said:
Hello, first post on this forum, so yeah ^^ I am also kinda new to this. I have a gs3 which is rooted and all, but that is old, and methods has changed...
So i tried to root my shield tablet and it got stuck in a boot loop. I can not get it into the bootloader using adb tools, or fastboot, or atleast i knot know how to. I have ran the: adb reboot bootloader, without success. I have also tried the: adb devices command and i dont see my device there. I have installed mini adb drivers.
This happend when using this tool(windroid): http://forum.xda-developers.com/showthread.php?t=2499926
So im thinking that if there is a way to get out of this, that would be great. I really hope i have not bricked it... all i wanted to to was to get root so that i could connect a ps3 controller... :/
I tried to use the windroid program but the recovery did not install. so i did it manually following this tut http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
im am not complaining or anything, purly looking for help.
So, after trying i got it up and running. i did not flash any supersu.zip files, just installed it from the market. wen it asked me to reboot the device ended up like this. I am aware of the disclaimers and stuff. If i go to device manager on my computer i can se: SHIELD Tablet, with a yellow triangle. I also searched youtube and this forum to look for posts, but found none that could help.
image: https://www.dropbox.com/s/16y1icl89etg9q9/2015-04-18%2015.36.46.jpg?dl=0[/IMG]
**Update** I found out how to get into the bootloader manually, so ill continue trying...
Click to expand...
Click to collapse
So, i fixed the problem by browsing back in the forums, did not know you could get into the bootoader by sing hw keys... lol
I fixed it by following this post: http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462