I have TWRP 2.8.7.0 and the latest VZW 5.1 debloated ROM from VitaTaf's thread. It's been a while since I backed up my /sdcard/ to computer. I realized that my TWRP backups are visible when booted into recovery; however, the /sdcard/TWRP/ folder is empty when booted into Android. Using Root Explorer, I am able to see the backup files in /data/media/0/TWRP, but the same files do not show up when connected to a Windows computer via MTP (which, if I'm correct, leads to /sdcard/).
I have tried the restorecon command from HERE, but the backups still do not show up in /sdcard/ after a reboot. I am able to move them to a different folder on /sdcard/, but it takes a long time and does not seem to be an actual solution. Trying to move the backups from /data/media/0/TWRP to /sdcard/TWRP/ results in an error.
Has anybody else encountered this strange issue? Any assistance would be appreciated.
AFAIK the folder is hidden. Try boot into TWRP, connect to the PC and then mount storage in TWRP.
A second option is directly backup to an external USB-Drive.
Thanks for the tip. I figured it might be an issue with permissions, and your suggestion gave me an idea. I booted into recovery, deleted the /sdcard/TWRP/ folder, rebooted into recovery, and created a backup in the newly created TWRP folder. It now shows up normally in Android and when connected to PC via MTP.
Related
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
voltage88 said:
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
Click to expand...
Click to collapse
I fixed it!!! Anyone that has a similiar issue. This is what I did.
In a previous thread, I saw that 4.2 will redo the sd card structure. After some research, it was recommended to change the path to /data/media/0. I was then attempting to do the command as follows 'adb push Trickdroid_8.0.0.zip /data/media/0' (without tick marks)
The file was pushing as it should (no progress bar) however, it would fail at the very end saying it was unable to locate the directory.
After seeing adb fail in that manner, I knew my sdcard was not mapped to the above path. What I did was boot into recovery, go to mounts and storage, mount my sdcard. Go back to the first menu now.....From here, select advance, and view log. It will tell you where your sdcard is being mapped to. Simply push your zip file to this directory and success! I have a working phone again.
Fastboot still doesn't recognize my device however. I'd be more then happy to be educated as to what I may have done wrong.
Currently irate because I already typed all this then hit enter to be told I can only register once from this ip.
Any way...
Rooted vs98027a Android 4.4.2 via Stump Root
Used AutoRec which installed TWRP 2.7.00
Backed up Stock Rom
Mount button is missing
Rebooted into Stock to transfer backup to PC and place "cm-12-20150603-NIGHTLY-vs980.zip" as well as Lp gapps.
Rebooted back into TWRP
Wiped, then Installed the CM Nightly, wiped cache and rebooted.
Stuck in LG Boot loop.
Use buttons to boot back into TWRP, open Restore and It's just a blank navigation window.
TWRP just became ****ing worthless
Tried to wipe and possibly install same CM again. Still boot looping.
Tried getting to download mode, but it reboots before installing driver.
I have not a clue as to what to do next.
I can't get it to mount.
ADB Sideload Fails.
Terminal Command lets me select a blank navigation window.
And my original file structure is in like sdcard/0/0/0/0/0/0/0/0/ etc.
Please help, or at least redeem CM and TWRP's value somehow, because this is bs.
I sort of fixed it.
Restore showed up blank, because within the many /0/0/0/0/0/0/0/0 a new TWRP folder would be made or course containing nothing.
I also learned the adb is this magnificent goddess that can do things even when your phone can't.
Throughout further reading I glimpsed upon something about "loki" files that aren't compatible with specific versions of twrp or something. So If you've also been through this and still feel brave enough to flash a custom, then make sure you get the newest version of twrp...
As for the Restore issue, assuming you have a backup saved on pc, wipe everything then adb push the whole file (TWRP/BACKUPS/BLAHBLAH/BLAUGHESDIHF) to /sdcard/.... then it should show up in restore, if it doesn't then use file manager to place it in the right TWRP directory... You can also use the file manager to move the restore folder to the "correct" twrp folder if you don't have it backed up.
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
golfnut22 said:
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
Click to expand...
Click to collapse
Edit: Well, that was easy. I just set up the ttinstall folder, then copied the rom and gapps zip files there, unmounted, then selected install from the twrp menu (rom first then gapps), rebooted and presto...running again.
I recently got my Nexus 6 back with a new (to me) motherboard installed. After allowing multiple OTA updates to the current (March 2017) firmware, getting my apps installed and setup, etc., I went to make some changes to the /system partition.
Knowing that /system is mounted read-only normally, I downloaded the current copies of adb and fastboot, as well as TWRP. I booted my phone into fastboot, ran fastboot boot twrp.img, mounted /system, and used adb to make a change. I then booted normally, but didn't see the effect of the change, so I checked with adb, and the change wasn't there. OK, that could be a few things, so I went back into TWRP, and -- this is where it gets weird -- saw the change.
Yes, if I boot up on TWRP and mount /system, I see whatever changes I have made to the /system partition visible when running TWRP, but when I boot the stock bootloader, I don't see any of them. It is behaving as if there are two /system partitions: one visible when booting with TWRP and the other visible when booting with stock.
I've never seen this before. Any thoughts?
NoelJB said:
...
Knowing that /system is mounted read-only normally, I downloaded the current copies of adb and fastboot, as well as TWRP. .
I've never seen this before. Any thoughts?
Click to expand...
Click to collapse
Is TWRP the latest version 3.1.0.0?
Did you use a recent rootexplorer?
For instance prev, version ES file explorer does not work with recent Android.
When booting TWRP-recovery normally the system partition needs to be mounted manually.
Why do you use adb to make changes to system, instead of the file manager of TWRP?
> Is TWRP the latest version 3.1.0.0?
Yes.
> Did you use a recent rootexplorer? For instance prev, version ES file explorer does not work with recent Android.
Not rooted, hence using TWRP to edit the /system partition.
> When booting TWRP-recovery normally the system partition needs to be mounted manually.
Yes, hence my comment about mounting /system.
> Why do you use adb to make changes to system, instead of the file manager of TWRP?
What would it matter? The contents of /system shown by the TWRP file manager are identical to those shown by adb shell. My problem is that the contents don't match what I see when booting with the stock bootloader. As I said, it is as if TWRP were showing one /system partition, and the stock bootloader were showing another.
NoelJB said:
... adb instead of the file manager of TWRP.....
What would it matter?.
Click to expand...
Click to collapse
.... using a shell and an 2nd device is rather different. I prefer the filemanager; it's more direct.
Sorry no more thoughts....
Lemme guess...
You're on the bone stock kernel...
If that's the case... There's a thing that keeps stuff from working... I wish I could be more help but... It's been almost 2 years since I've seen this...
I THINK you can flash any other kernel and it will solve your problem... Or maybe one of the root solutions would do it too...
Sent from my Nexus 6 using Tapatalk
did you solve it?
One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks
wittier said:
One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks
Click to expand...
Click to collapse
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.
When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.
NLBeev said:
When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.
Click to expand...
Click to collapse
thanks. it is the latest TWRP.
I fixed it, see above, it wasn't the drivers on the PC.
The PC works with my other N6. This N6 has issues.
The workaround of wiping in TWRP fixed it. I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.
wittier said:
... I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.
Click to expand...
Click to collapse
Updating TWRP to the latest version is a good practice.
wittier said:
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.
Click to expand...
Click to collapse
I updated my other N6 last night.
After flashing stock ROM and TWRP and booting to TWRP only, I didn't have to wipe before I could push files to the phone.
The other phone is more difficult.