Database Info

[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

Absolutely cannot get phone working with ADB

Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!

On Mac try sudo adb whatever
Always with sudo
Sent from my MB865 using xda app-developers app

xxDriveNxx said:
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
Click to expand...
Click to collapse
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.

cogeary said:
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
Click to expand...
Click to collapse
I guess I'll have to give the factory wipe a shot tonight. I was really hoping it wouldn't come to that since I can't use Titanium Backup due to lack of root.

all i did was have my phone plugged in while i was installing the drivers. but i did have to download the ones from your post.

I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.

kousik said:
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
Click to expand...
Click to collapse
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).

Bob G said:
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Click to expand...
Click to collapse
FYI adb will not work in mass storage mode.adb needs the phone memory and other access which are not there when you connect your phone in mass storage where it acts merely as a card reader
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...

Just in case anyone else was on the fence about doing this: I had tried a million things (trying different computers, different USB cables, installing and uninstalling different drivers, editing driver inf files, editing adb_usb.ini, etc) for several days and nothing worked. I was skeptical about the factory reset helping, but now that I did it I can finally connect to my phone. Yay!

[Q] Have TWRP No OS no SU can't install os

Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.

Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979

berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.

I still haven't had any luck. Does anyone have any ideas?

You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.

http://forum.xda-developers.com/showthread.php?t=2646279

berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so

Whoops, forgot screen shot

Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....

berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.

hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...

berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.

_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?

berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.

So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....

hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!

hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

[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.