Related
I accidentally formatted my internal sd card today, is there a way to recover any of the file?
Sent from my GT-I9000 using XDA App
Try this worked for me a long time ago
Good Luck
I tried Recuva, but an older version which I got for free. Anyone else have a suggestion? I have some very important files on my sd. :-(
Install ubuntu linux on internal memory (via XDA tutorial), then run a file recovery package through that.
Much more is available on ubuntu in that respect
-----------------------------------------------------------------------------------
*Remember if i helped, click thanks!
SXTN said:
Install ubuntu linux on internal memory (via XDA tutorial), then run a file recovery package through that.
Much more is available on ubuntu in that respect
-----------------------------------------------------------------------------------
*Remember if i helped, click thanks!
Click to expand...
Click to collapse
Right now this is my only hope. Where's the tutorial? By internal memory,do you mean right on the Nexus one itself? Also, would I be able to revert to CM7?
My turbo has a newly unlocked bootloader, thanks to beaups and jcase. I have TWRP installed and I'm ready to flash some ROMs, but TWRPs USB-OTG won't functions.
Has anyone used it yet that can help me?
I was just going to ask about otg ( for different reasons) I have a sandisk 64 gb flash drive (formated exFat) my phone sees it but won't open or format it. Any thoughts?
Sent from my XT1254 using XDA Free mobile app
drmrjake said:
I was just going to ask about otg ( for different reasons) I have a sandisk 64 gb flash drive (formated exFat) my phone sees it but won't open or format it. Any thoughts?
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
twrp.fstab must be modified by the twrp dev of your device... please tell him ....
/dev/block/sda1 is the needed path if he asks
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
twrp.fstab must be modified by the twrp dev of your device... please tell him ....
/dev/block/sda1 is the needed path if he asks
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
@baybutcher27 ?
Sent from my XT1254 using XDA Free mobile app
I had no issues with a 32gb sd card with otg adaptor formatted fat32. Read and write very fast, twrp recognized everything.
USB-OTG /dev/block/sda1 already exist.
https://github.com/bhb27/twrp_device_motorola_quark/blob/master/recovery.fstab
Check second post of TWRP thread there is a help we use it for months all the bug are resolved.... Today TWRP only access FAT32 drivers not a bug, to access other format like NTFS generates a bug that make the device not boot at all..
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
baybutcher27 said:
USB-OTG /dev/block/sda1 already exist.
https://github.com/bhb27/twrp_device_motorola_quark/blob/master/recovery.fstab
Check second post of TWRP thread there is a help we use it for months all the bug are resolved.... Today TWRP only access FAT32 drivers not a bug, to access other format like NTFS generates a bug that make the device not boot at all..
http://forum.xda-developers.com/moto-maxx/orig-development/recovery-twrp-2-8-7-0-touch-recovery-t3180308
Click to expand...
Click to collapse
ntfs needs a special boardconfig flag... did you already tried?
TW_INCLUDE_NTFS_3G := true
not sure i totlay get it, mine will read other flash/thumb drives, just not my 64 gb one. The larger one is formatted exFAT and are the smaller ones are formatted to FAT 32. is this a hardware or OS software issue?
drmrjake said:
not sure i totlay get it, mine will read other flash/thumb drives, just not my 64 gb one. The larger one is formatted exFAT and are the smaller ones are formatted to FAT 32. is this a hardware or OS software issue?
Click to expand...
Click to collapse
maybe the kernel in recovery dont support exfat
edit: strike the last.... exfat is supported by default
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
ntfs needs a special boardconfig flag... did you already tried?
TW_INCLUDE_NTFS_3G := true
Click to expand...
Click to collapse
yes on the kernel too doesn't boot. but months ago it may work if i make a new one today, waiting on the official release of TWRP 2.8.8.0 made for M source to worry about that.
On the kernel is not need because the OS can use NTFS but I try to enable it on the kernel to see if that help on the TWRP but no. :good:
baybutcher27 said:
yes on the kernel too doesn't boot. but months ago it may work if i make a new one today, waiting on the official release of TWRP 2.8.8.0 made for M source to worry about that.
On the kernel is not need because the OS can use NTFS but I try to enable it on the kernel to see if that help on the TWRP but no. :good:
Click to expand...
Click to collapse
hm... if you have ntfs enabled ... maybe the size of twrp was too big for your recovery partition (wich will cause nonboot)
Sent from my Xperia T using XDA Free mobile app
---------- Post added at 12:40 AM ---------- Previous post was at 12:31 AM ----------
baybutcher27 said:
yes on the kernel too doesn't boot. but months ago it may work if i make a new one today, waiting on the official release of TWRP 2.8.8.0 made for M source to worry about that.
On the kernel is not need because the OS can use NTFS but I try to enable it on the kernel to see if that help on the TWRP but no. :good:
Click to expand...
Click to collapse
one more thing... please check if aromainstaller works fine on your twrp (i dont own this device ) use the aromainstaller3.0 testzip (if your screen will be half size .... )
Sent from my Xperia T using XDA Free mobile app
BTW exFAT works just fine... on my external USB HD...
SdtBarbarossa said:
hm... if you have ntfs enabled ... maybe the size of twrp was too big for your recovery partition (wich will cause nonboot)
Sent from my Xperia T using XDA Free mobile app
---------- Post added at 12:40 AM ---------- Previous post was at 12:31 AM ----------
one more thing... please check if aromainstaller works fine on your twrp (i dont own this device ) use the aromainstaller3.0 testzip (if your screen will be half size .... )
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
full I don't see any log does aroma make logs? because i try the demo/test...
it gives me 255 then 255 and reads device configurations and present on the screen.
baybutcher27 said:
full I don't see any log does aroma make logs? because i try the demo/test...
it gives me 255 then 255 and reads device configurations and present on the screen.
Click to expand...
Click to collapse
ok then everything is fine
yea aroma make logs BUT they are not in recovery.log .... you need to pull them manually via adb
Sent from my Xperia T using XDA Free mobile app
in twrp my otg is not mounting .. any idea to get it work done ..
Formatted in the wrong format, or too high of a power draw.
Sent from my XT1254 using XDA Free mobile app
I have a Sandisk 32gb OTG drive, the new USB 3.0 version and my TWRP reads it fine, it backed up my stock rom nandroid to it,
Its formatted s FAT32
I don't know why my otg not detecting in twrp .. I formated to FAT32 but still it can't mount , when I'm clicking it can't check on box ..
Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
-UPDATE:
Here are three solutions for updating:
a) The downloaded .zip file has to be moved to /data (if wanted, into some subfolder of your choice. ES-File Explorer needs root for that) Then flash via TWRP.
b) Use flashify, choose copy to safe location (had some FC's afterwards)
c) Use cm-recovery, update via cm-updater (not yet confirmed)
davedophin said:
Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
Click to expand...
Click to collapse
1. I don't think so. For this we should need an updated recovery supporting this feature. Furthermore, the feature is not fully ready, imho
2. I don't know. Never had this problem.
Written with my XT1068 using Tapatalk on CM13
On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.
Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk
Dieselhorst said:
Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk
Click to expand...
Click to collapse
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.
Mavireck said:
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.
Click to expand...
Click to collapse
I believe you when you say Flashify can flash the rom. But as said, it's all way to complicated for the 'average' user. Especially because of the encryption, which causes the sd card to be unseen by, for example, your recovery or your pc. These things have to be solved first!
Written with my XT1068 using Tapatalk on CM13
Sure, that's why I say
This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Click to expand...
Click to collapse
.
I think we should stop debate now because we think the same
Mavireck said:
On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.
Click to expand...
Click to collapse
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!
davedophin said:
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!
Click to expand...
Click to collapse
The twrp team is awesome. They will find a fix.
I only tried flashing the ROM but i think you can flash at the same time gapps.
Alright, Flashify works, if you pick the option "copy to safe directory" or similar. "use provided path" doesnt work for me.
But after the update, Nova Launcher keeps crashing and titanium backup doesnt show up on the app drawer anymore, but is still installed and cant be uninstalled to reinstall. pretty weird. So for me, this option doesnt really work either.
I copy the update zip file to \Data\Media\0\twrp and i can update
Anyone knows if the SuperSU 2.60 works in the CM13 Moto G2014???
@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk
bhachech said:
@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I haven't used TB or Nova... CM 13 on Titan is running very well for me. As expected, in these early nightlies, some CM features are not fully implemented but that has not hindered my ability to use it as a daily driver for the past couple of weeks.
davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I use Nova and TB, no problems here
Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk
ygtenos said:
Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
I've tried like 4 releases of CM13 so far, never had a problem like that. But I only used builds from december, so I would suggest you go for a newer version, after a backup of course
Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)
So guys, I updated to todays build by moving it to the /data partition and then using twrp. Works like a charm! Thanks everyone for your help!
davedophin said:
Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)
Click to expand...
Click to collapse
Does not work for me (Moto Thea)
The sd card in my moto x4 device doesn't show up "format as internal storage" but I'm still able to use it as external. Can somebody help me
that option is not available. don't ask me why.
it's slow AF anyway, why would you nees it?
"... File-based encryption [FBE] cannot currently be used together with adoptable storage. On devices using file-based encryption, new storage media (such as an SD card) must be used as traditional storage ..."
The Moto X4 uses FBE ...
I guess the next question will be ...
https://android.stackexchange.com/q...k-encryption-instead-of-file-based-encryption
romhippo.com said:
"... File-based encryption [FBE] cannot currently be used together with adoptable storage. On devices using file-based encryption, new storage media (such as an SD card) must be used as traditional storage ..."
The Moto X4 uses FBE ...
I guess the next question will be ...
https://android.stackexchange.com/q...k-encryption-instead-of-file-based-encryption
Click to expand...
Click to collapse
I researched this heavily while building TWRP, but abandoned it in favor of trying to build TWRP that properly decrypts the default encryption.
It seems that the fstab.qcom flag "forceencrypt" will force FDE as the default encryption.
This tag (instead of forceencrypt) is supposed to enable an encryption selection option Developer Tools:
forcefdeorfbe=/dev/block/platform/c0c4000.sdhci/by-name/metadata
Click to expand...
Click to collapse
I have not fully tested either, but I may return to converting to FDE if I can't solve FBE in TWRP
I should also note... the kernel will overwrite changes to fstab.qcom on boot, so implementation is more difficult than first glance
Hi Mightysween, Thanks for the update. I hope somebody will find a way to disable Direct Boot (and the FBE requirement that come with it).
Offtopic: I am also following your TWRP topic. Thanks for making "the process" public. It is a very interesting read. Thanks for your efforts!
is it fixed on Oreo? I mean if I update to Oreo will possible to format as internal storage?
PherChe said:
is it fixed on Oreo? I mean if I update to Oreo will possible to format as internal storage?
Click to expand...
Click to collapse
No, not yet
Hi all,
I noticed, my TWRP (i tried cepheus and 3.3.0. 9.0 b8) does not show any files in the folder storage. Even not the called "emulated" or "0" folder.
So i can only sideload .zip or Install it via OTG.
But how to fix TWRP?
Thank you.
Full wipe/format data
But it has mounted because it does not show 0 MB. It only does not show the files
manuelbvb said:
But it has mounted because it does not show 0 MB. It only does not show the files
Click to expand...
Click to collapse
It's encrypted. Back up and as said format data.
manuelbvb said:
But it has mounted because it does not show 0 MB. It only does not show the files
Click to expand...
Click to collapse
Is it really empty or show random named files? If its random names, then its encrypted. If empty, try look inside folder of /data/media/0. Your internal storage files should be there and encrypted by default..
Why is there an encryption? How does it go to avoid in Future?
Thank you
manuelbvb said:
Why is there an encryption? How does it go to avoid in Future?
Thank you
Click to expand...
Click to collapse
There is always an encryption. The recoveries just can't handle it right now. They need more improvements. But our devs do a good job and I think it won't take a long time to fix this in near future.
Kollachi said:
There is always an encryption. The recoveries just can't handle it right now. They need more improvements. But our devs do a good job and I think it won't take a long time to fix this in near future.
Click to expand...
Click to collapse
@Kollachi so we must wait new release of TWRP? i've already cleaned data partition.. but encrypt is still here
ang3lx said:
@Kollachi so we must wait new release of TWRP? i've already cleaned data partition.. but encrypt is still here
Click to expand...
Click to collapse
Yup we need to wait until someone fix that. You need to FORMAT data. Wipe data isnt enough.
ang3lx said:
@Kollachi so we must wait new release of TWRP? i've already cleaned data partition.. but encrypt is still here
Click to expand...
Click to collapse
You need to format data, install remove force-encrypt zip then Magisk
When will there be a official TWRP, that Support erverything?