Database Users

[Q] Rooted, wiped data and OS. help

I rooted my Moto Electrify M (which to my knowledge is the same as the Razr M from verizon) and I was attempting to put CM10 on it. I was following the directions from http://forum.xda-developers.com/showthread.php?t=2012093&page=57 and I accidentally deleted my internal storage (which contained my zip files GAPPS and CM10. I now have a rooted/unlocked bootloader phone with no operating system and am unsure how to install CM10.
I attempted using my external SD in another phone to transfer the files. Once I booted up TWRP in recovery mode and attempted to install I could not find said files. I'm a super noob at this whole root thing, please help

I'm not sure what the problem would be, maybe try going into Mount in twrp and unchecking the box for external sd before looking for the files.

to clarify, when I am in "install" there are folders named /sd /sdext etc but there is nothing in the folders. I have tried toggling between external and internal memory while using the install feature.

What version of twrp do you have? I put my rom zips on the root of the sd card, and when I switch twrp from internal to external, everything is right there.
Try using the file manager and see if you can find the files. If you can, but still can't get to them in the install page, use the file manager to move them over to internal storage and see if they appear there.
Do you know how to use fastboot? You could flash cwm recovery instead, and see if that shows the files.

I have version 2.2.2.1 of twrp.
I cannot find them in file manager. I am using a galaxy s2 transfer the files from my pc to the external card. Here are my options for where to store the zip files.
(nvm I can't post links yet)
What I see here is NOT what I see when I use the SD card inside of the Electrify M.
The options available for storing the zip files are not showing up when in the file manager

Interesting.. I would go into fastboot mode and use Matt's Utility to reset the phone to stock and get your OS back. You should already have the right drivers installed, so start up your phone while holding the down volume key to get into fastboot mode, load up the utility and select the first option.
Then I would flash a newer version of TWRP and see if your file browsing issues persist, I'm using twrp 2.5.0.0. Or you could also opt to flash the CWM recovery instead, and see if that fixes your problem. I have used both of these recoveries and never had an issue finding the zips on my external sd.
Another option would be to give Safestrap a try, it will ensure you don't lose your default OS again. Safestrap will let you set up a custom rom installation alongside your stock rom, keeping it perfectly intact.

Fixed it gents. I reformatted my sd card and stuck it in the android folder that was created. I then mounted the external through twrp and found it instantly. My assumption is the problem was user error related. I now have cm10 installed and have my gapps working, but I don't have bluetooth or 4g functionality. Should I make a new thread regarding these problems?

I haven't tried CM10, but honestly I would just try another one(maybe CM10.1 would fix your problems). I'm not big into fixing issues with my roms, I just find one that works and stick with it.
There might be a solution for your problems, and yeah another thread would be the way to go to get more visibility on it, but personally I would just go for Carbon or AOKP or SlimROM, or one of the other options. I have tried out the three I just mentioned, and have had 4G and bluetooth working with each(except Bluetooth on Carbon, I never tested it out but I assume it works)
I wish I could help you more but I just don't know enough to troubleshoot those kind of issues.

[Q] Format internal with TWRP

hello people, i need to know a thing, not a major bug or high damage stuff.
when i boot into recovery (twrp) and format everything, including internal, i need to reboot again into recovery to get internal memory access via MTP mount. thats ok, the thing is, after i reboot, get access, move my new rom to internal and flash it.
after first boot, when i go on internal memory i didnt see my ROM.ZIP file there, but the space that it ocuped is there, in other words, when i format internal i get all my ~10GB internal, after first boot into the rom i can see my internal memory as ~8GB free, but the ~2GB ROM.ZIP file isnt there.
is it a mapping/partition table bug? where can i find my file again?

[Q] Formatted SD Card in MM and TWRP Issues?

Has anybody who's formatted their sd card as internal storage had issues seeing folders/zips in twrp? Previously was using the Indian MM on my MXPE and after a few days I formatted as internal...all was smooth but I guess I never went to use twrp again until I went to flashed the MXPE MM rom...booted into twrp but couldn't see any folders or zips in the internal storage so I had no way to actually flash the rom.
Wound up having to reformat the sd card as portable storage so twrp could read both storage locations again and was able to finally flash the rom...I'm thinking about trying to format again just to see if this is an actual issue or just a one time thing...but if anybody else has experienced the same thing let me know. Btw I'm using the 2.8.7.1 twrp.

I had this as well, and if i remember how MM works, it encrypts the card so that only the phone/OS can read it. So if you are going to be doing full flashes, i beleive it would lock out the sd card, though I'm not 100% on that. If you are trying to dirty flash a rom, or just a mod to it, boot to recovery, go to mount, move the files over to the actual internal storage, then flash.

I had the same issue. I backed everything up, formatted as portable, installed rom, then formatted as internal again, then re-copied all my stuff back onto it. @mseliga is correct as far as I know. I wanted to start everything fresh and clean, so I used a longer method, but moving the files to the actual internal storage should work.

Yep this sucked. When I go to es file explorer and navigate to the twrp folder it says cannot be found, but when I'm actually in twrp I think it lets me back up/restore. This sucks tho, I'm still not sure if its working 100%. What a hassle to have switch back and forth, smh
Sent from my XT1575 using Tapatalk

How to decrypt android marshmellow formated sdcard

i was on twrp 2.8.7.0 and installed http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-kushan-cm-marshmallow-rom-t3258489. then formatted my sd card as internal storage. today i wanted to update to the latest build of kushan rom, but in twrp my sd card was listed as 0 mb and i couldnt enter it. so i decided to flash latest cwm trough rom manager. after flashing cwm my internal sdcard was wiped(not by me-automaticly) and now marshmellow tells me that te sd card is not supportet...please format.....
i think that as the cwm wiped my sd card "the unique? encrpytion key?" got lost and therefor i cant axcess the sd card. im i right?
if yes i hope the encryption key is not unique and i can recover the files on the sd card

k2828 said:
i was on twrp 2.8.7.0 and installed http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-kushan-cm-marshmallow-rom-t3258489. then formatted my sd card as internal storage. today i wanted to update to the latest build of kushan rom, but in twrp my sd card was listed as 0 mb and i couldnt enter it. so i decided to flash latest cwm trough rom manager. after flashing cwm my internal sdcard was wiped(not by me-automaticly) and now marshmellow tells me that te sd card is not supportet...please format.....
i think that as the cwm wiped my sd card "the unique? encrpytion key?" got lost and therefor i cant axcess the sd card. im i right?
if yes i hope the encryption key is not unique and i can recover the files on the sd card
Click to expand...
Click to collapse
As stated many many times. The only recovery you can use is TWRP. Your sdcard shows 0 mb because it became part of your internal storage. So reflash TWRP and try again.

after flashing cwm i did nothing but booting once the rom and notice that everything was wipped and then flash twrp.
the result is i cant axcess my sdcard as the rom sais that the sdcard needs to prepared.
so my question is, can i recover the data on the sd card?

Not if you're at the point where the card needs to be prepared. What you should have done if you wanted to decrypt the MicroSD, is pulled the data off both card and internal storage, then gone into Settings > Storage & USB and converted the card to portable storage.
One thing. With CWM running, did you have any nandroid backups? If you did, you likely will have to reinstall CWM to free up the internal storage reserved for the nandroid backups. CWM by default allocates space for its nandroid backups that cannot be touched by the system or TWRP. Once you do that, you can then reinstall TWRP.

OK THX. I just created a image of the SD card.maybe in the future there will be a toop to decrypt such SD cards. For the future:
Is the SD card lost everytime i update the Rom build?
Is the SD card lost Ehen i change the Rom to another Android 6 Rom?
What do i have to do when updating to a Newer build oft the same rom,vor change to another Android 6 rom? Pull everything from bouth cards? Really? Thats a pain in the ass even with a uhs 1 SD card.
Whats the best way for backing up the data, so i can cop them back without trouble? Maybe ADB?
Whats about changin the recovery? Thats a nogo i think and whats about updating twrp?
What is a absolut nogo? What i ahouldnt do to f*** up the card again?

So many questions, but I'm going to answer just the last two, as their answer covers every other question in your post.
What is an absolute no go? What shouldn't I do to f*** up the card again?
Click to expand...
Click to collapse
The answer to this is so easy it's astounding. The answer is to not combine the card with the internal storage. Here's why. If you switch ROMs regularly in order to try them out, every single time you combine the storage the card has to be prepared for use, which means all data on it gets wiped. If you do a clean install of your current ROM and combine the storage, all data on the card is wiped. The reason the card gets wiped is because Android 6.x creates a virtual volume which spans both internal storage and the MicroSD. In order to ensure the data is secure Android encrypts the volume. This encryption is part of the reason Google throws up a warning to restore the card if you pull it out of the device.
By not combining the storage, you avoid the encryption problems, but you do have to deal with the issue of apps not seeing the MicroSD card. Unless an app with this issue is no longer being updated, this problem will resolve itself. Developers have to adapt to the new setup.
The encryption also impacts performance, though on my tests with it I didn't notice anything. The one thing it will do is impact the ability to perform backups. In my tests, the encryption prevented TWRP from doing anything useful, meaning no ability to install flashable zips or updated TWRP recovery images from the storage and no ability to do nandroid backups. TWRP could see the directory structure of the combined storage but could not see any files within the folders to install. Nandroid backups instantly failed with an "out of storage" error, even though I had some 15GB of space available on the MicroSD. TWRP's developers will need to adapt to this and custom ROM developers will have to recommend that users not combine storage.

Strephon Alkhalikoi said:
So many questions, but I'm going to answer just the last two, as their answer covers every other question in your post.
The answer to this is so easy it's astounding. The answer is to not combine the card with the internal storage. Here's why. If you switch ROMs regularly in order to try them out, every single time you combine the storage the card has to be prepared for use, which means all data on it gets wiped. If you do a clean install of your current ROM and combine the storage, all data on the card is wiped. The reason the card gets wiped is because Android 6.x creates a virtual volume which spans both internal storage and the MicroSD. In order to ensure the data is secure Android encrypts the volume. This encryption is part of the reason Google throws up a warning to restore the card if you pull it out of the device.
By not combining the storage, you avoid the encryption problems, but you do have to deal with the issue of apps not seeing the MicroSD card. Unless an app with this issue is no longer being updated, this problem will resolve itself. Developers have to adapt to the new setup.
The encryption also impacts performance, though on my tests with it I didn't notice anything. The one thing it will do is impact the ability to perform backups. In my tests, the encryption prevented TWRP from doing anything useful, meaning no ability to install flashable zips or updated TWRP recovery images from the storage and no ability to do nandroid backups. TWRP could see the directory structure of the combined storage but could not see any files within the folders to install. Nandroid backups instantly failed with an "out of storage" error, even though I had some 15GB of space available on the MicroSD. TWRP's developers will need to adapt to this and custom ROM developers will have to recommend that users not combine storage.
Click to expand...
Click to collapse
thx for your very detailed answere. but whats about when i am using i.e. kushan rom build 07.12.2015 and i update to kushan rom build 11.12.2015. will the sd card have to be prepared to use also? and what about when i update twrp to a marshmellow support twrp. di i need prepare the sd card then again?
TWRP could see the directory structure of the combined storage but could not see any files within the folders to install. Nandroid backups instantly failed with an "out of storage" error, even though I had some 15GB of space available on the MicroSD.
Click to expand...
Click to collapse
This is the point where my trouble began. as so as the sd card is prepared as internal you cant even see files of the real internal storage. flashing zips you can still do with adb sideload. another question could we backup the internal flash inlcuding prepared sd card with this:
http://forum.xda-developers.com/showthread.php?t=1818321
?
If yes, is there also a way to restore the backup made?

To make things crystal clear, once the card is set for portable storage you will not have to reconfigure the card again unless you choose to combine the storage. Upgrading a ROM to a newer version will generate a message in the notification bar that you have to prepare the card, but you simply select the portable storage option and the notification goes away. Upgrading TWRP doesn't require doing anything to storage.
Should you choose to combine storage, upgrading a ROM may cost you whatever is on both the internal storage and microSD. Upgrading TWRP with combined storage would require you to flash it using Odin, because you wouldn't be able to copy the TWRP image to the device storage.
Backing up the internal storage doesn't require anything more than a copy operation from the S4 to the PC, so no special tools should be required. That applies regardless of whether the storage is combined or separate. However, for best results with TWRP, the storage should not be combined.

Sorry for reviving this old thread, but I've the same issue.
I flashed a new rom without getting the decryption code or backing anything up(No NANDs, no sd backup). Is there still currently no way to retrieve the files that are encrypted on this SD?

I've done exactly the same, I'm hoping theres a way to decrypt it.

k2828 said:
i was on twrp 2.8.7.0 and installed http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-kushan-cm-marshmallow-rom-t3258489. then formatted my sd card as internal storage. today i wanted to update to the latest build of kushan rom, but in twrp my sd card was listed as 0 mb and i couldnt enter it. so i decided to flash latest cwm trough rom manager. after flashing cwm my internal sdcard was wiped(not by me-automaticly) and now marshmellow tells me that te sd card is not supportet...please format.....
i think that as the cwm wiped my sd card "the unique? encrpytion key?" got lost and therefor i cant axcess the sd card. im i right?
if yes i hope the encryption key is not unique and i can recover the files on the sd card
Click to expand...
Click to collapse
Have you found solution to decrypt the Sdcard.
I was facing this problem for almost 1 year I need only sdcard not data in it but I am unable to format it due to encryption but any device able to read the data and copy from that.
Even I can play Music out that SD card

Unless you're immortal, you're not decrypting the MicroSD card via brute force. Currently, the amount of time required to find the decryption key is longer than the current age of the universe.
If looking to simply format an existing card, use SDFormatter from http://www.sdcard.org.

Problems after extending SD Card as Internal memory- can't Backup (and others)

I have an unlocked bootloader, but I'm not rooted. I upgraded to MM via OTA and set my SD Card to be used as internal memory. I've had some problems since:
1) The first real issue is that Evernote is giving me a database read/write error and not working. It seems that to resolve that, I'll probably need to root. So, I went to do a MM nandroid before rooting
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
3) When i go into the Mount screen and select storage, it is showing Internal as just 2+GB free (which is correct), but 0MB for my Micro SDCard. So, it can't mount it.
4) Looking around, the fixes for this seem to be a bit severe in terms of formatting the SD Card again, etc. (ex. http://forum.xda-developers.com/showthread.php?t=2354029)
So, my questions are:
1) If anyone knows of a solution to that Evernote issue, that would be great
2) More importantly, what my options are for fixing the Backup problems
3) Specifically, with my SDCard now supposedly acting as internal memory, if i format the card per the common fixes, will that cause other unexpected problems with apps and other functions that are now using my SD Card as usable storage?

How did you set SD card as internal storage. Me: stock, no root, MM
Sent from my XT1575 using Tapatalk

I'm giving up on combined storage until twrp is fixed.

You just go into settings, storage, then click on the SD card. I'm back to lollipop at the moment, so I cant say exactly what to do next, but I think from there it should be clear. It may be an option up in the overflow menu at the top right. It will make you reformat your card as part of the process .

Thanx Chuck! Need to b.u. before formatting as internal...

I had the same issue with the SD card set as internal, couldn't make a twrp backup, so I had to reformat as storage and it works. Only bad part is now I can't move apps to SD
Is there a twrp fix in the works??

chuck-fu said:
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
Click to expand...
Click to collapse
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.

ScaryBugThing said:
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.
Click to expand...
Click to collapse
It's a known issue that the version displayed stays on 2.8.7.0 after updating.
Sent from my Moto XPE