Database Info

[Q] Nexus S not responding in fastboot

Hi all,
I am noticing something with nexus s.
When in recovery or in normal homescreen, my nexus s communicates properly with adb commands
But there seems to be no communication from the nexus s when in fastboot mode.
Everytime I enter a fastboot command, I always get a "waiting for device" and nothing happens.
Am I missing something?
Thanks.
Heeter

If your PC is running Linux then you will need to be root.

No I am running windows 7
I got the Android 1.0 driver. Windows Device manager recognizes that my phone is hooked up,
But when I type in "fastboot devices" it is not listed there.
Thanks
Heeter

When I hook up my Nexus S in fastboot mode, I see this at the bottom:
Code:
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Everytime I unplug/replug USB wire, another "STANDARD_SET_CONFIGURATION" line gets added
I type "fastboot devices" into fastboot, and my Nexus S does not show up.
The phone is currently unlocked, but I would like to lock to reset it and start from factory rogers setup again.
Any help would be greatly appreciated.
Thanks
Heeter

You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::

rubbamade said:
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
Click to expand...
Click to collapse
I do have that already, rubbamade.
My Device Mangler is recognizing Android 1.0, and has the drivers for that I took from PDAnet.
The PDAnet itself couldn't install properly, so I extracted the drivers from the package and manually installed them through the Device Mangler.
I still cannot connect to fastboot.
Heeter

I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter

I guess you made your decision already in getting rid of windows lol. Anyway goodluck with the fastboot issue. And I hope the 3G issue is looooooog gone from your life. Take it easy
Arnel
Sent from my Nexus S using Tapatalk

LOLOL,
A whole bunch of thanks for that radio to you again
Heeter

Good choice ditching windows. Lol
Offtopic: how is debian compared to Ubuntu concerning repo n 3rd party drivers? Seriously considering switching to debian since Ubuntu adopted the crapy Unity
Sent from my Nexus S using Tapatalk

The driver isnt right if your phone wont show. You have to let windows find the correct driver out of the drivers you point it to. Either point it to x64 or x86 directory only. No further. Windows will find it.
Go to the fastboot thread in development and get the drivers.
Uncle Jimmy says hello

Heeter, it's maybe a bit late but unless you're really strapped for disk space you can keep Windows and create a separate partition for Linux, using the grub bootloader to choose between the two. I'm a Linux user myself (mostly Arch but I love to test most new distros) but I have lots of disk space and I keep an up-to-date Windows 7 installed for testing purposes and gaming.
Since - I have to admit it - I suck at most games, my Windows doesn't get used much but I don't begrudge the space it takes up. On Debian you should have less trouble with the adk and drivers - here's a good post at Howtoforge about using the adk http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-debian-squeeze

Heeter said:
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
Click to expand...
Click to collapse
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.

bender_123 said:
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
Click to expand...
Click to collapse
I tried that like 50 flippin times! everytime, PDAnet stays locked up during the pulling driver area. I have come back half hour later, still not complete. Then, when I unplug the cable, it spits out an error, and uninstalls itself.
What I ended up doing was, during the PDAnet install, it creats a root folder in C:/Program Files/PDAnet (or whatever it is). Now when it got stuck there, I went into that root folder, copied the "usb-win" driver package from there and set it aside. Then I went into the Device Mangler, and right clicked and manually installed the PDAnet driver.
Hiya Gun26, Thanks for that link. I am actually a site supporter on that site, if you search up "Heeter" over there. Been for a couple of years now.
I guess I could go back to dual booting, haven't done that in a long while either.
Heeter

That was just a suggestion about the dual booting - if you enjoy gaming, why give it up? Linux and Mac may be great (and BSD let's not forget) but for gaming it's either Windows or a console. I don't think you'll have any trouble with the adk and drivers on Debian. Good to hear about your connection to Howto Forge - it's a really useful site.

Thanks for that Gun,
I haven't had time to move back to Debian, and I really do like gaming once in a while.
I should be up and running dual boot this weekend.
Thanks again, guys.
Heeter

i'm having this same problem, it's rather annoying

[Q] CMW (internal storage) no ROM (on SD) on TF101 b80

hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "

im on recovery and when i run adb devices it just blank. any walk through is much appreciated!

Do yo have USB debugging on?

I dont know because i was about to flash a new rom so i did a full wipe already

Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.

i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe

i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.

I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!

Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!

If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.

thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...

still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.

yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz

monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.

Trouble getting adb to work

Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob

SD card not found
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob

emueyes said:
Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob
Click to expand...
Click to collapse
What USB cable are you using? Try to use your Xoom oem cable. Also, make sure that you try different USB ports, especially the ones tied more directly to the pc motherboard. It's finicky like that. Recheck your drivers. I'm not familiar with that PDAnet source. Motodev is the place to get them from. You may also need the java sdk from oracle.
There are some useful guides on setting up adb/fastboot/rooting in General...you may have to go back a few pages but it will be worth it to make your task easier.
Good luck!
---------- Post added at 10:51 AM ---------- Previous post was at 10:47 AM ----------
emueyes said:
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob
Click to expand...
Click to collapse
Which recovery mode are you talking about? Have you unlocked and installed a custom recovery, as in a ClockworkMod-based recovery? If so, which one? They have some different behaviors. If it is stock recovery, I don't think it sees the external sdcard at all.

Also make sure usb debugging option is enabled. And flash another recovery image.
You don't really need to root. Just unlock the bootloader. Push the recovery image. Reboot to recovery. And flash a pre rooted rom from team EOS.
Sent from my MZ601 using Tapatalk 2

[Q] Trouble with fastboot

Hi all,
I had a nice, long, detailed post typed out but then my browser at work crashed, so here is the revised edition:
I recently (three days ago) bought a TF300T tablet. Absolutely love it. As any android fan does, I immediately wanted to root it to get the full benefit of the device. I followed the step-by-step guide on the cyanogenmod wiki and have been successful (after a few hours of figuring things out) in unlocking the device. I am aware at this point that my device is unlocked and my Asus warranty is voided. I am also aware I may have to follow different steps to root it, and am willing to do so accordingly.
I'm not set on using cyanogenmod, but that seems to be the most popular and well-known one so I'd like to use one that is established.
So, up until now I have followed that guide but I am having an issue with flashboot. When I go to do the 'fastboot devices' command, I get nothing. It just jumps to the next line, as if I sent a blank command. When I type 'adb devices' it works fine and shows some letters&numbers so I know my device is recognized.
With all that being said, can anyone advise me on which step I'm doing wrong, if any?
Also, I'm -really- cautious about potentially bricking this thing. I still have 30 days at Best Buy but I'm also an employee there and my co-workers know I'm trying to root so if I brick it, it may not be as easy to return it as with a normal customer. I also have the Accidental Damage & Handling plan so if I DO brick it, I can smash it and get a new one without too much incident, if it comes down to it (which obviously is a LAST resort)
My device is as following:
Asus Transformer Pad TF300T unlocked, firmware .29.
I' have about 15 tabs open in Google Chrome right now after SEARCHing the forums, specifically the TF300 forum, and I'm filtering through all the posts right now. If I find a solution I will post asking for this thread to be deleted.
I'm very tech-savvy, but completely new to android. I don't own a smartphone, and this is my first android device, so this is an incredible learning experience. If anyone feels so kind, could you please explain the different terminiologies used in the rooting scene? I hear stuff about blobs, .build files, DE, WW, US stuff. What's what? And what does it all mean?
Thanks so much, and here's to hoping my computer doesn't crash as soon as I press "post"!!
-Opethfan89
*edit* Forgot to add that when I use the command
fastboot flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
the command prompt just stays stuck on "waiting for device", while my device is stuck on "Starting fastboot USB download protocol"

Slight resolution
So I am just posting with a slight update to what I've been trying to get this working. I uninstalled the ADK, all drivers, and started over from scratch. I installed ADB using the method listed on the CyanogenMod wiki, and it works fine (I can use all ADB commands from command prompt and it lists my device when I use the 'adb devices' command.
So I'm continuing to follow the steps on the CyanogenMod wiki page and I get back to the part about Fastboot. I boot into fastboot mode, plug the device in, and the new development is that my computer DOES recognize fastboot only in device manager. I do have a yellow exclamation mark near it meaning I don't have the proper driver installed.
So now my newest question is, how do I install the driver for -just- fastboot, or where can I find the .inf file so I'm able to install it myself?
I'm SO close to rooting this device I can just taste it!! Any device is very much appreciated
Thanks!
Opethfan89

Are you following this guide?
http://forum.xda-developers.com/showthread.php?t=1668173
Pretty easy to follow and the easiest way to install recovery and root device.

Yes I have followed that guide and like I said I get to the step where fastboot SHOULD be recognized by my computer but it isn't. It shows up in my device manager with a yellow exclamation point so I literally just need the driver to make things work and I should be rooted.

This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.

Have you tried to see the index on tf300t development?
Hope you have all you need and all process.
For Fastboot : [GUIDE] Help for flash more faster when you use Fastboot Line Command
And for Drivers:
ASUS Android USB Drivers.zip - 2012/04/13 - MD5 Sum: 43af8f39ed421caabecd6c4a2de17212 - Size: 8.28 MB (8687221 bytes)
ASUS Pad PC Suite (PC version V1.0.41) - MD5 Sum: 02d7661affefeb0ae05f577b6b24b37a - Size: 145.09 KB (148570 bytes)
ASUS Sync V1.0.82 - MD5 Sum: a7d229ee2f2678819e6a99711d1f572d - Size: 62.18 MB (65195236 bytes)
You will find all you need for your TF300t in this index

As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem

vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop

philos64 said:
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
Click to expand...
Click to collapse
I think you do need to install android sdk because of the fastboot files are in there and need it to use fastboot that could be the reason why his computer does not recognize the tablet when he is in fastboot mode. If you look at your android manager you will see a file under android tools that fastboot files are installed.

you need to specify device id
fastboot -i 0x0b05 flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
try that op

IT WORKED!!!!
EndlessDissent said:
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Click to expand...
Click to collapse
See, I think that's where I messed up. None of the guides say to download ASUS' drivers, and in my anxiousness to root I must have overlooked that step. I will try this today and post my results accordingly!! Also, no offense taken by the linux comment, and I've used linux in the past, but I've had quite a few times where it doesn't "just work" (Like using a broadcom wireless card on my old laptop. I had to learn how to use ndiswrapper and whatnot, not a pleasant experience for a linux newb at that time!!)
I recently removed my Linux partition (was using ubuntu 10.10 because I hate unity!!) and can re-install it if it will make my rooting process easier?
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
Yea I didn't download the asus pad suite drivers, and I think that is what is causing my issue. I wish I could post links to the guides I am following but none of them specify that. They just say to download the android SDK and all drivers are included.
FlyingPoo said:
you need to specify device id
try that op
Click to expand...
Click to collapse
I did do that, flyingpoo. At one point my cmd line showed "Sending file recovery.img (5***kb)" but the tablet never picked it up, so I know there is just some miscommunication between the tablet and the PC. When I typed adb devices in cmd line, I see the device listed, but when I type fastboot devices in cmd line, it just goes to a blank line.
I will try the above listed solutions and hope that something works. Thank you all so much for your help!
*edit* This guy, right here? Yea, he's freakin ecstatic! I installed the drivers from EndlessDissents' post, and it worked!! As soon as I booted into fastboot mode, my computer recognized the device. I then used the command that FlyingPoo used (which I tried in the past), and it showed:
Code:
c:\recovery1>fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' <5306 KB>...
OKAY [2.417s]
writing 'recovery'...
OKAY [2.053s]
finished. total time: 4.473s
So now I'm following the next few steps to root it. I've backed up my apps using Astro as well as the ASUS backup suite, and I'm using CWM for a backup of my entire system at the moment.
Thank you again to everyone who responded. I always get hung up on the simplest step, but once that is overcome everything else is a smooth ride downhill

One last noobish question to ask, and then I think I'll be done:
I've downloaded the root-signed.zip file, as well as the latest CyanogenMod file I could find (The official wiki didn't have one listed for any asus products, for some reason?) as well as a google apps for cyanogenmod. I put the files on my SD card but nothing on there is detected within CWM. So the noobish question is which directory do I need to put the files in for CWM to detect it?
That being said, I'm also wanting to backup my system to my external SD card and I selected the option in CWM to backup but it said no sd\ext was detected. Any thoughts?
Thanks again everyone for your responses.
*EDIT* For anyone following this thread, I did figure it out. Another guide I referenced specifies that you copy the files to the INTERNAL SD card (which is kind of confusing, as SD card explicitly refers to an external memory card) and then choose it from CWM. So for me, I downloaded the files on my computer, copied them to my SD card, put the SD card in my tablet, and copied the files to the root directory of the internal storage on my tablet.
Thanks again everyone, I now have root (at least, I'm pretty sure I do?)
Mod, please feel free to close this thread as necessary.

[Q] Bricked - Formatted Partitions with no OS to install

Hello guys, so before I go any further I'll say that I have spent two days attempting to figure out ways to get my self out of this trouble and I've come close, but no cigar. The limiting factor here is the inability to connect to a PC.
Ill begin with the intent: format all partitions to F2FS. I finished backing up all important data to cloud storage and what little I could to my PC (photos only). While I was able to connect my phone to the pc, all I could get it to recognize was as a camera device, not an MTP device, so I was limited as to what files I could back up (hence the cloud storage used for the rest). I tried many different drivers (LG mobile device drivers, Google USB driver, Installing google SDK tools, etc).
I admit that I messed up not realizing I would've needed to restore the f2fs roms previously downloaded in order to re-flash in TWRP. I went ahead and formatted the phone to F2FS and all I have is TWRP 2.7.1.1. I have tried mounting through TWRP in windows XP sp3 and also in windows 8, I can not get the phone to mount the internal SD card in order to drop an f2fs compatible rom to flash.
So I basically have a useless phone at the moment (TWRP and no OS). I was hoping there would be an option to flash a rom image using ODIN, but I can't seem to find any helpful instructions online. Any help at this moment would be greatly appreciated. I'll answer any questions I can.

murph187 said:
Hello guys, so before I go any further I'll say that I have spent two days attempting to figure out ways to get my self out of this trouble and I've come close, but no cigar. The limiting factor here is the inability to connect to a PC.
Ill begin with the intent: format all partitions to F2FS. I finished backing up all important data to cloud storage and what little I could to my PC (photos only). While I was able to connect my phone to the pc, all I could get it to recognize was as a camera device, not an MTP device, so I was limited as to what files I could back up (hence the cloud storage used for the rest). I tried many different drivers (LG mobile device drivers, Google USB driver, Installing google SDK tools, etc).
I admit that I messed up not realizing I would've needed to restore the f2fs roms previously downloaded in order to re-flash in TWRP. I went ahead and formatted the phone to F2FS and all I have is TWRP 2.7.1.1. I have tried mounting through TWRP in windows XP sp3 and also in windows 8, I can not get the phone to mount the internal SD card in order to drop an f2fs compatible rom to flash.
So I basically have a useless phone at the moment (TWRP and no OS). I was hoping there would be an option to flash a rom image using ODIN, but I can't seem to find any helpful instructions online. Any help at this moment would be greatly appreciated. I'll answer any questions I can.
Click to expand...
Click to collapse
ODIN? This isn't a crappy Samsung device. Flash factory images with fastboot in bootloader, or adb push a flashable ROM zip to your internal storage and flash it in recovery. If you don't know how to do that, I don't know why you're messing with your device at all. If that's the case, first link of my signature for threads on how.

Lethargy said:
ODIN? This isn't a crappy Samsung device. Flash factory images with fastboot in bootloader, or adb push a flashable ROM zip to your internal storage and flash it in recovery.
Click to expand...
Click to collapse
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7). I would need to reformat the partitions to ext4 in order to fastboot flash stock images no?

murph187 said:
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7).
Click to expand...
Click to collapse
Theres a thread for diagnosing driver issues. You might have to disable signature enforcement on Win8.
Flashing factory images will reformat it to ext4, I'm pretty sure.
Also, there is hardly any UI difference in 8 compared to 7. Even the "start menu" is theoretically the same, just with a different layout. Pinned shortcuts and a list of shortcuts.. You can install a 3rd party start menu if you're someone that can't adapt to something new. Any complaints that "Windows 8 is terrible" are just stupid.

murph187 said:
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7). I would need to reformat the partitions to ext4 in order to fastboot flash stock images no?
Click to expand...
Click to collapse
Make your suffer short. Try lg flashtool. Link in my signature.

bitdomo said:
Make your suffer short. Try lg flashtool. Link in my signature.
Click to expand...
Click to collapse
Your method worked thank you very much! Mod can close thread.