Database Users

Factory Reset wiped out the internal SD card! I thought it's not meant to happen?!

This is the first time I'm using a device that doesn't have an external SD card, but I've all along understood that the internal SD card does not get wiped when you do a factory reset, and I'm sure I read that again on another thread just the other day.
My N7 is rooted using Wug's toolkit, with CM10.2 and Bulletproof kernel.
Yesterday I decided to do a factory reset (under Settings, Backup & Reset, Factory Data Reset), but after I did it, all the stuff I had on the internal SD was gone, including my backup files, the ROMs I had transferred there, etc.
Surely this is not meant to be the case, is it??

internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?

sfhub said:
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
Click to expand...
Click to collapse
Thanks for that! (Thanks coming your way). Well, better to know now than later! The down side is that I lost my CWM backups and my Titanium Backup files, but the good thing is that I think I have a TWRP backup that's on my computer.
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?

Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.

oohyeah said:
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
Click to expand...
Click to collapse
I am not sure what issue you are having with TWRP, but you can flash it to the recovery partition and boot to it automatically. If that's the only reason you don't like it, I'd work on fixing the install rather than jumping to another recovery.
oohyeah said:
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Click to expand...
Click to collapse
I would probably do it from recovery. I don't know what CWM does on this platform as I've only used it on other platforms.

What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Sent from my Nexus 7 using xda app-developers app

geckocavemen said:
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Click to expand...
Click to collapse
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign. I remember doing some searches and it seemed like this was normal. I remember the reason was that the N7 would always rewrite the recovery or something. From your responses, I'm guessing it's not normal?
The only way I could get into recovery was using the Wug toolkit using USB debugging/ADB, which really sucked, cos if it bootlooped and I can't get into the system to turn on USB debugging, then I'm not sure what I would do (though I read there's some way around it or something). I had never encountered any such thing with all my many other devices which all run CWM.
So what's up with all that?

"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery

User_99 said:
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
Click to expand...
Click to collapse
This will work fine. If you have no aversion to installing apps, Rom Toolbox Lite gives you power widgets you can put on your desktop then go to recovery with one touch. I use Quick Boot PRO, although the free version of that all may do recovery also. One might work for you until you want to play with mods.
Sent from my Nexus 7 using Tapatalk 4

oohyeah said:
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign.
Click to expand...
Click to collapse
That is stock recovery.
You need to get rid of /system/etc/install-recovery.sh
You can get rid of it by hand, or just install SuperSU from TWRP. Then flash TWRP to the recovery partition.

Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!

oohyeah said:
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
Click to expand...
Click to collapse
None of your blunders has anything to do with TWRP.

khaytsus said:
None of your blunders has anything to do with TWRP.
Click to expand...
Click to collapse
OK let me get something straight.
Obviously, the factory resetting that wiped out all internal storage (the original point of the thread) has nothing to do with TWRP, and I never said it did. On this point though, I'm surprised that it doesn't seem to be more well known that a factory reset would do wipe out all your data (did several searches and only found 'confirmations' that your internal SD data would be left untouched), though I'm glad that I know it now.
The suggestions on different ways to boot into recovery were helpful, though I believe that I would still have encountered the dead android, or would I not have?
What's certainly still not clear to me though is regarding the problem of not being able to boot into recovery and getting the dead android with the exclamation/triangle. After the first few replies, I expected to hear that this was NOT meant to be the case and that I did something wrong in the process or whatever.
However, what I seemed to get was that this is the expected behavior, and what I needed to have done was to "get rid of /system/etc/install-recovery.sh".
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.

oohyeah said:
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
Click to expand...
Click to collapse
Dead android = stock recovery, so normal there.
When you flash a custom recovery on a stock ROM, there is a file, /system/etc/install-recovery.sh, or I actually prefer just renaming /system/recovery-from-boot.p, which will automatically verify your recovery image and restore it to stock if it doesn't match. So you must always remove this file, or the ROM will restore the stock recovery on boot.
TWRP makes it easy to remove either file by mounting /system in read-write mode and using its built-in file manager to remove it. You can do the same in CWM using adb.
As for point 3, yes, try to reboot into recovery again. If you didn't remove (either file), you'll find stock recovery again.

Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.

oohyeah said:
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
Click to expand...
Click to collapse
It really depends on what ordering you do your actions in.
/system/etc/install-recovery.sh doesn't exist on a stock factory shipped system.
It only gets put in place after you install an OTA. If you do all your upgrades using the factory images, you'll never encounter it.
What it does is during your boot process, it will check to see if your recovery is different than what it expects (ie stock). If so, it will install stock recovery by taking the stock kernel and patching it.
If any of the following are true, it will not overwrite your recovery:
/system/etc/install-recovery.sh is missing (or modified to not run as the original file)
/system/recovery-from-boot.p is missing
you are not running the stock kernel
The most common way for install-recovery.sh to be missing is you always used factory images.
The most common way for install-recovery.sh to be modified to not do the original function is if you installed SuperSU. It will overwrite install-recovery.sh with its own.
So in all the back and forth, it is quite possible you got rid of install-recovery.sh or had it modified simply by installing root.
If you then subsequently installed custom recovery, it would stay in place.
Previously you were installing TWRP and flashing it onto the tablet, but upon booting into android, install-recovery.sh realized it wasn't stock recovery, and overwrote TWRP with stock recovery.
That is why whenever you rebooted, you got fallen android (which is stock recovery)
If the way you installed cwm is to use "fastboot flash recovery cwm.img" then the only reason it is around is because something else you did got rid of or modified install-recovery.sh. cwm would be no more immune to install-recovery.sh than twrp was.

oohyeah said:
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
Click to expand...
Click to collapse
Just to clarify, you didn't lose root. You just lost the supersu app, a root permission manager, because it was installed to your /data partition. The su binary was still in /system, all you would have had to do was install supersu from the market.

I'm not sure what else you were expecting from a "factory reset"

creaturemachine said:
I'm not sure what else you were expecting from a "factory reset"
Click to expand...
Click to collapse
Did you read the thread? He explained his reason for expectation quite well.
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?

Skaziwu said:
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Click to expand...
Click to collapse
Depending on which level you are looking at, it didn't really change the behavior, but rather how your data is organized.
Factory reset has always wiped out /data.
On older devices, they put the /sdcard in a separate partition and formatted fat32.
These are the ones that were surviving a factory reset.
On newer devices, the internal /sdcard is starting to migrate onto a directory in /data and the "sdard" you see is "virtual". Since it is on /data, when you wipe data, the virtual sdcard is also wiped.
Some recoveries try to simulate the previous behavior by doing a "rm" of every directory except the virtual sdard when you choose to wipe, instead of the erase/format that Android is doing.
The advantage of keeping the sdcard as a directory under /data is you don't need to decide how much space to split between the sdcard and your /data. Also permissions on files are more flexible being in an ext4 filesystem. Finally since everything is emulated and accessed via MTP, you don't need to unmount the filesystem, so your PC can access it.
There are also cons with this approach, but that is what Google is going with.

[Q] Copy files to the device on twrp?

I installed a rom which had a bad install so i was stuck in a boot loop, And no matter what I try i always get the boot loop, Im able to boot into twrp but going to mount im unable to see it on my windows 7 laptop? I have no idea how to push files to the device with adb as im what you'd call a slow learner lol.
Any ideas would be much apreciated.

I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!

Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?

crazyboy81 said:
I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!
Click to expand...
Click to collapse
Thats an easy one compared to me lol. go to advanced, terminal command and type in the following minus the brackets (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota)

metapy said:
Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?
Click to expand...
Click to collapse
My problem isnt anything like the bootloop, Ive done a full wipe and now have nothing on my phone to install, adb sideload isnt working for me for some reason as its coming up as adb is not a recognised command? I feel screwed?
EDIT: I may have solved my problem, currently pushing a rom onto the phone with adb sideload

Cyanogen-11 stuck while booting (yes, I googled)

Hi, everybody!
I am stuck with the problem, I cannot solve, and cannot google.
I saw a lot of similar, but none of the directions helped me to fix my phone.
I've got my Nexus 4 which was a great phone until I updated it to 4.3, some of the screen portions became senseless on some applications (starting from SMS, to some game apps).
I was suggested to downgrade or change ROM, which I am trying to figure out right now.
I've rooted my phone with SuperSU-v1.85 and installed Clockwork-6.0.4.3.
Once I've done it, I was trying to load an images of cm-11 and gapps-4.4 with
adb push
it finished all operations in cmd, however, I got
E: Can't mount /sdcard
Thus, I've tried to install all zips from sideload and my cmd.
I didn't touch kernel.
Once I've done this, I tried to reboot, but Cyanogen stuck, running circles.
I've tried to do factory reset, clear cache and dalvik, however none of those worked.
I also have been doing this with a more stable release (cm-10.2.0), but I got same thing.

bagelisnotaname said:
Hi, everybody!
I am stuck with the problem, I cannot solve, and cannot google.
I saw a lot of similar, but none of the directions helped me to fix my phone.
I've got my Nexus 4 which was a great phone until I updated it to 4.3, some of the screen portions became senseless on some applications (starting from SMS, to some game apps).
I was suggested to downgrade or change ROM, which I am trying to figure out right now.
I've rooted my phone with SuperSU-v1.85 and installed Clockwork-6.0.4.3.
Once I've done it, I was trying to load an images of cm-11 and gapps-4.4 with
adb push
it finished all operations in cmd, however, I got
E: Can't mount /sdcard
Thus, I've tried to install all zips from sideload and my cmd.
I didn't touch kernel.
Once I've done this, I tried to reboot, but Cyanogen stuck, running circles.
I've tried to do factory reset, clear cache and dalvik, however none of those worked.
I also have been doing this with a more stable release (cm-10.2.0), but I got same thing.
Click to expand...
Click to collapse
Try another rom besides CM.

scream4cheese said:
Try another rom besides CM.
Click to expand...
Click to collapse
Tried MIUI.
Same thing.
Did I brick it?

scream4cheese said:
Try another rom besides CM.
Click to expand...
Click to collapse
I've tried stock ROM 4.2.2, flashed it with flashall.bat, stupidly, it works.
However, what is the problem with the custom ROMs?
Do I do something wrong?
ps. screen is still unresponsive in some areas.

Maybe you'll have better luck with TWRP 2.6.3.3.

audit13 said:
Maybe you'll have better luck with TWRP 2.6.3.3.
Click to expand...
Click to collapse
Just tried it.
Didn't work out with MIUI.

Just put the files directly onto the phone either by downloading them on it or transferring normally over USB.
Reboot into recovery
From here you got options but to make it simple do a full wipe. A full wipe is deleting everything but your internal storage. That includes / system /data and everything else your recovery shows but the internal storage. Then just flash the ROM zip and gapps zips from your internal storage after the wipe and reboot
If you delete your internal storage you will wipe out the zips you just put there. Along with your media. Pictures music and whatever else is on there
Wiping your data will wipe your apps. So if you want, back them up with something like titanium backup prior. They will still be there after you flash the custom rom as long as you don't wipe your internal storage.

[Q] Cannot mount anything in TWRP, sdcard folder empty

Hi All
I am in the process of flashing Cyanogenmod 11 onto my TF300T however I am in a world of hurt. First I updated to the latest TWRP (2.6.3 -4.2). When i boot up into TWRP it is asking me for a password which I do not know. If I press Cancel i cannot see any contents of /sdcard. Also if I insert a microSD card, again cannot see any contents. TWRP is telling me there is no operating system installed and if i reboot it just comes straight back into TWRP.
I apologise if this question has already been asked but I just cant figure this one out.

What bootloader version do you have? What helped me was to reboot into the boot loader (using volume down+power, has three options RCK, cold-boot linux, Wipe data [dont ever ever ever wipe data]) and select cold-boot linux (the android guy in the middle) and it would boot back into my ROM. If you cant get in that way, you are going to have to use ADB on your computer and use the "adb reboot-fastboot" command. If you get in, back up your files, because you're at the event horizon of losing all your data. If your bootloader is 10.6.1.8 youre going to need to flash the latest asus stock firmware from their website.
Sent from my TF300T using XDA Premium 4 mobile app

Lyshco said:
Hi All
I am in the process of flashing Cyanogenmod 11 onto my TF300T however I am in a world of hurt. First I updated to the latest TWRP (2.6.3 -4.2). When i boot up into TWRP it is asking me for a password which I do not know. If I press Cancel i cannot see any contents of /sdcard. Also if I insert a microSD card, again cannot see any contents. TWRP is telling me there is no operating system installed and if i reboot it just comes straight back into TWRP.
I apologise if this question has already been asked but I just cant figure this one out.
Click to expand...
Click to collapse
u should back to twrp 2.5, or u should use scanno twrp.

Tunameltsalad said:
What bootloader version do you have? What helped me was to reboot into the boot loader (using volume down+power, has three options RCK, cold-boot linux, Wipe data [dont ever ever ever wipe data]) and select cold-boot linux (the android guy in the middle) and it would boot back into my ROM. If you cant get in that way, you are going to have to use ADB on your computer and use the "adb reboot-fastboot" command. If you get in, back up your files, because you're at the event horizon of losing all your data. If your bootloader is 10.6.1.8 youre going to need to flash the latest asus stock firmware from their website.
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am using bootloader 10.6.1.3. When I cold boot linux it just continually boots up into TWRP.
Whenever I try to run an ADB command i get "error: device not found". I have installed the android SDK, tried to install the USB drivers but no luck (possible windows 8 issue?).
It doesnt matter if I lose all data on it, i dont keep anything really important on it.
I have rolled back to 2.5.0 TWRP and it still asks me for a password.

I've switched over to my Mac now and have been able to push the CM-11 ROM into the sdcard directory. However when I attempt to flash it, it fails immediately with the log saying.
E:Unable to mount '/system'
E:Unable to mount '/cache'

Lyshco said:
I've switched over to my Mac now and have been able to push the CM-11 ROM into the sdcard directory. However when I attempt to flash it, it fails immediately with the log saying.
E:Unable to mount '/system'
E:Unable to mount '/cache'
Click to expand...
Click to collapse
I had something similar, tried many things but nothing worked so i ended up flashing stock ROM again with fastboot.
If you need help on how to do that just let me know.

rtfm
and more serious:
cm11=android4.4=new PITs(like with 4.1 to 4.2)
solution:
flash scsnnos twrp 2.6.3.0 from his omni thread and it works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

screeny added
Sent from my TF300T using XDA Premium 4 mobile app

Buster99 said:
rtfm
and more serious:
cm11=android4.4=new PITs(like with 4.1 to 4.2)
solution:
flash scsnnos twrp 2.6.3.0 from his omni thread and it works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok this morning I have tried the following:
1. Flashed Scanno's TWRP from the OMNI thread using this command:
> fastboot -i 0x0B05 flash recovery recovery.img
2. Booted up into TWRP, again /sdcard is empty.
3. Pushed the OMNI ROM onto /sdcard using:
> adb push omni-4.4.2-20131218-tf300t-HOMEMADE.zip /sdcard/
4. Went to Install and selected the zip then it immediately fails saying:
Unable to mount '/system'
Am I missing something here? From above i see that i flash 'recovery'. Do I need to flash 'system' with fastboot?

no, but maybe your PITs are corrupt. do you still have an older nandroid backup you could try to restore first?
oh just read that twrp asks for password. is that still the case?
Sent from my GT-I9505 using XDA Premium 4 mobile app

Yep it's still asking me for a password.
What are PITs?
I'm not sure if I have a backup. When in TWRP if I go to restore it can't find any. It's like the whole tablet is wiped. Does this have something to do with not having the ability to mount anything?
Sent from my HTC_PN071 using Tapatalk

Ok, Buster99 I followed your instructions over at this thread and am now back up and running with stock.
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
For me to go to KitKat, can I just flash the OMNI ROM now?
EDIT: Nevermind, I am all back up and running, thanks so much for the help, i was getting a bit worried that I had bricked it!

HELP
So I just tried getting cm11 on my tf300t, i installed TWRP 2.5 and rooted my device, everything went well. I then did a factory reset and wiped cashe. I tried installing then cm11 zip file with no success. I get the message that it failed. And now im on a device with no ROM to boot into and no working ROM to flash on the device.
Since there is a SD card slot on the device, would it be possible to put another ROM on there and then flashing that?
Please help me!

ollemolle said:
So I just tried getting cm11 on my tf300t, i installed TWRP 2.5 and rooted my device, everything went well. I then did a factory reset and wiped cashe. I tried installing then cm11 zip file with no success. I get the message that it failed. And now im on a device with no ROM to boot into and no working ROM to flash on the device.
Since there is a SD card slot on the device, would it be possible to put another ROM on there and then flashing that?
Please help me!
Click to expand...
Click to collapse
in order to install CM11, you need a special TWRP modded for KK: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
You can copy a CM11 nightly and the TWRP onto a SD card and flash from there, or use fastboot.

cmendonc2 said:
in order to install CM11, you need a special TWRP modded for KK: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
You can copy a CM11 nightly and the TWRP onto a SD card and flash from there, or use fastboot.
Click to expand...
Click to collapse
Hello, i have a similar problem, i wanted to install CM11 on my TF300T, i downloaded the latest version of TWRP from their site for the tablet, installed via Fastboot and everything seems to be ok, when i try to flash it (via CM OTA) it ask me for the password and it didn´t mount any data, but when i reboot the tablet it just keep loading twrp and i can't get to fastboot nor adb nor APX, so i have no idea on how to restore or boot back to the OS, or i just bricked the device?
thanks

josush said:
Hello, i have a similar problem, i wanted to install CM11 on my TF300T, i downloaded the latest version of TWRP from their site for the tablet, installed via Fastboot and everything seems to be ok, when i try to flash it (via CM OTA) it ask me for the password and it didn´t mount any data, but when i reboot the tablet it just keep loading twrp and i can't get to fastboot nor adb nor APX, so i have no idea on how to restore or boot back to the OS, or i just bricked the device?
thanks
Click to expand...
Click to collapse
What stock bootloader are you on?

cmendonc2 said:
What stock bootloader are you on?
Click to expand...
Click to collapse
i'm not really sure about the number but it was the latest one from ASUS, i was on the official 4.2.1 ROM when i moved to CM10 a few months ago

josush said:
i'm not really sure about the number but it was the latest one from ASUS, i was on the official 4.2.1 ROM when i moved to CM10 a few months ago
Click to expand...
Click to collapse
When you restart you tablet, and hold the vol down key while rebooting it will give you a bootloader number: 10.6.x.x.x

cmendonc2 said:
When you restart you tablet, and hold the vol down key while rebooting it will give you a bootloader number: 10.6.x.x.x
Click to expand...
Click to collapse
that's the point, it doesn't do anything, is like i'm not holding or pressing it, it just show the ASUS Logo screen and in the top left it says that the bootloader is unlocked as usual, i don't think is a wardware problem because it was working the last time it booted on Android

josush said:
that's the point, it doesn't do anything, is like i'm not holding or pressing it, it just show the ASUS Logo screen and in the top left it says that the bootloader is unlocked as usual, i don't think is a wardware problem because it was working the last time it booted on Android
Click to expand...
Click to collapse
Once it goes to recovery, adb will be accessible. Then follow Buster's recovery method.

D801 (Tmobile) Stuck in TWRP - No OS Boot

This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!

brickwall99 said:
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
Click to expand...
Click to collapse
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.

freebee269 said:
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
Click to expand...
Click to collapse
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.

brickwall99 said:
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
Click to expand...
Click to collapse
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.

freebee269 said:
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
Click to expand...
Click to collapse
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...

brickwall99 said:
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
Click to expand...
Click to collapse
that's because you have no adb connection. no connection = no pushing files. that's why i said you need to get adb working first.

I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!

brickwall99 said:
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
Click to expand...
Click to collapse
good news. hope you get up and running now. still update your twrp.

freebee269 said:
good news. hope you get up and running now. still update your twrp.
Click to expand...
Click to collapse
Okay I got the ROM transferred and I have installed it successfully.
Using this one: http://forum.xda-developers.com/showthread.php?t=2598361
But when I reboot it goes straight to recovery.
A factory reset fails. I'm only able to advanced wipe of system/data, also it fails when I wipe cache or dalvik.
So I've tried wiping system/data, then installing the ROM again, and it just reboots straight back to recovery.

I sideloaded TWRP 2.6.3.5 for tmobile. Verified it shows 2.6.3.5 TWRP now. I'll try to sideload/install the ROM again.
Edit: When trying to factory reset it says failed to mount cache.

Okay so I have successfully installed the ROM with TWRP 2.6.3.5 and when I reboot it still goes straight into recovery.
What next?
Thanks
Edit: Is there perhaps something wrong with the bootloader, or what? I'm thinking part of the issue is because I can't mount or wipe cache/dalvik?

I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle

rawb123456 said:
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
Click to expand...
Click to collapse
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.

Any luck? I tried flashing CM11 on TWRP 2.6.3.2 (per XDA instructions) and it failed. Now I am stuck in recovery and can't ADB new recovery
brickwall99 said:
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Click to expand...
Click to collapse