Related
hi all,
I cannot see or mount my sd card. It can be read and written in PC, but my u8800 can't see it.
I loaded 2.3.5 official. After some search I rooted it somehow and installed "x5 settings" application (I dont remember why I installed it, damn). After using "selecting internal/external memory" area and rebootings, my sd card cannot be seen by the device anymore. When I plugged, there is an option "turn on usb storage" but it doesnt work, just turning and waiting when clicked. In the storage settings "mount sd card" doesnt do anything.
I formatted the sd as fat32, tried using it when backups restored and not restored. But doesnt matter.
Btw, my internal sd is completely free (as i see in the storage settings) but i cannot see it when plugged in the computer neither.
any help will be appreciated,
ismail
edit: when dload of 136 is in the memory card and opened in pink screen, it gives an "update failed".
edit2: 138 and 162 does the same, update failed. Again, i cannot reach my internal sd.
edit3: the problem may be not the sd card (update fails because I try to downgrade from 526 to 1xx). however i cannot reach internal sd. making downgrade from internal sd may solve the problem, anyone knows a way to reach it somehow?
Have you tried the trick to remove the battery and put the phone to charger and then installing? And after install you put battery back. Also make sure that there is free space in sd. Also make sure there is free space in sdcard. 500MB should be enought.
I put the b136 rom inside sd card. When battery out, if i plug the device, it starts normally. But if <power+-> combination is used when plugging, it goes to the pink screen and waits.
there are 14 gb free space in external and 2 gb in internal sd card.
btw, thank you for your reply.
I think you can mount internal sd in ubuntu while in pinkscreen. This requires you to have ubuntu and unlocked Bootloader. To install ubuntu, use WUBI, which is easy way to have it with windows. Blefish has posted a way to unlock to bootloader. There is a link for it in my signature. After these are ready, plug your phone while it's in pinkscreen to ubuntu, and search for 2gb partition. Then pud dload there and continue like you normally do.
I'm using Ubuntu right now I ll give it a try, thanks again.
edit: tried, but as far as there is no sd card mounted, it seems there is no way to unlock the bootloader. (error: /sdcard/bootloader.bin: cannot open for read: No such file or directory)
On project menu, which is accessible by *#*#2846579#*#*, there is an options menu for sdcard. I think that needed Google option to be enabled. Try to play with the options there(reboot after a change).
Also from X5settings, choose external memory.
acilipatos said:
I'm using Ubuntu right now I ll give it a try, thanks again.
edit: tried, but as far as there is no sd card mounted, it seems there is no way to unlock the bootloader. (error: /sdcard/bootloader.bin: cannot open for read: No such file or directory)
Click to expand...
Click to collapse
Can't you do it the automatic way? Do you have CWM installed?
dancer_69 said:
On project menu, which is accessible by *#*#2846579#*#*, there is an options menu for sdcard. I think that needed Google option to be enabled. Try to play with the options there(reboot after a change).
Also from X5settings, choose external memory.
Click to expand...
Click to collapse
There was google mode selected, i tried the others also. No change. imo, source of all the problems is the "x5 settings". I had installed and remove it many times, but before the last uninstall, i changed the option to "external". Now i dont have x5 settings enabled, and dont know how to reinstall since there is no sd.
julle131 said:
Can't you do it the automatic way? Do you have CWM installed?
Click to expand...
Click to collapse
no, i dont have CWM right now, before the sd card issue, I was trying to install it but the bootloader problem was preventing me.
can you try to install b518 or b517? they are official 2.3.5 betas, but with unlock bootloader.
I am downloading them and will try both.
edit: didn't work. "update failed" problem.
i cannot install CWM because there is no sd card mounted.
also cannot make bootloader work because there is no CWM and sd card.
So not able to install any custom rom from bootloader.
And since my version is b526, i cannot downgrade. (i dont know if the reason impossibility of the downgrade or the sd card problem or not mounting internal sd.)
I will wait the next (final) version. For now, i gave up. Thanks for all
The first thing I did after rooting, because it is what the tutorials and this forum always stress, is to make a Nandroid backup, which I did through TWRP Recovery. Nowhere did I see an option regarding where to save it. Low and behold, I find out that it saved the backup files, which are nearly 3gb in size, to the phone, instead of my larger SD card. Obviously I want to move it to the latter. But by what means should I do that, particularly so that the backup can be easily flashed onto the device later if need be? I don't want to move it only to make the files undiscoverable in Recovery.
(I apologize if this is a stupid question, but this is my first time rooting, and nothing useful was yielded from a forum search.)
beerindex said:
The first thing I did after rooting, because it is what the tutorials and this forum always stress, is to make a Nandroid backup, which I did through TWRP Recovery. Nowhere did I see an option regarding where to save it. Low and behold, I find out that it saved the backup files, which are nearly 3gb in size, to the phone, instead of my larger SD card. Obviously I want to move it to the latter. But by what means should I do that, particularly so that the backup can be easily flashed onto the device later if need be? I don't want to move it only to make the files undiscoverable in Recovery.
(I apologize if this is a stupid question, but this is my first time rooting, and nothing useful was yielded from a forum search.)
Click to expand...
Click to collapse
In order for CWM or TWRP to see the files on your memory card it has to be 32GB (those are usually formatted in FAT32). If you have a 64GB memory card that would be formatted in extFAT. The programs cant read extFAT so you would need to take the card out place it in your PC and use a FAT32 program to make it FAT32.
DarkMenace said:
In order for CWM or TWRP to see the files on your memory card it has to be 32GB (those are usually formatted in FAT32). If you have a 64GB memory card that would be formatted in extFAT. The programs cant read extFAT so you would need to take the card out place it in your PC and use a FAT32 program to make it FAT32.
Click to expand...
Click to collapse
My SD card is an old 32gb one. I don't have a USB reader, so how would I confirm on my phone that it is formatted as FAT32? And, assuming it is, what steps must I then take?
beerindex said:
My SD card is an old 32gb one. I don't have a USB reader, so how would I confirm on my phone that it is formatted as FAT32? And, assuming it is, what steps must I then take?
Click to expand...
Click to collapse
Download Partition Table then open it and click the the A for advanced. scroll to the bottom and find mmcblk1p1 and click it. It should show the memory card and what Filesystem it is.
DarkMenace said:
Download Partition Table then open it and click the the A for advanced. scroll to the bottom and find mmcblk1p1 and click it. It should show the memory card and what Filesystem it is.
Click to expand...
Click to collapse
The listed filesystem is vfat.
beerindex said:
The listed filesystem is vfat.
Click to expand...
Click to collapse
It shows the 32GB for space with the usage of your memory card right? If so you will need to remove the MicroSD card and place it in your PC and format it to Fat32. You can also try the Format tool built in to the phone in you options.
DarkMenace said:
It shows the 32GB for space with the usage of your memory card right? If so you will need to remove the MicroSD card and place it in your PC and format it to Fat32. You can also try the Format tool built in to the phone in you options.
Click to expand...
Click to collapse
Formatted through the phone and it is still listed as vfat through Partition Table. So does that mean I need to find another way of reformatting it to Fat32?
beerindex said:
Formatted through the phone and it is still listed as vfat through Partition Table. So does that mean I need to find another way of reformatting it to Fat32?
Click to expand...
Click to collapse
Yes, it needs to be FAT32 for recoveries to recognize it.
DarkMenace said:
Yes, it needs to be FAT32 for recoveries to recognize it.
Click to expand...
Click to collapse
I am not sure what I'm doing wrong, but I formatted again, this time using my computer (my S4 connected via data cable, with the microsd card inside), and once again, the result is vfat.
beerindex said:
I am not sure what I'm doing wrong, but I formatted again, this time using my computer (my S4 connected via data cable, with the microsd card inside), and once again, the result is vfat.
Click to expand...
Click to collapse
Did the card read FAT32 on your computer? IF it did it shouldn't change when you put it in the phone unless your running some type of custom software and it's messing with the file system.
DarkMenace said:
Did the card read FAT32 on your computer? IF it did it shouldn't change when you put it in the phone unless your running some type of custom software and it's messing with the file system.
Click to expand...
Click to collapse
It never specified. There is no media format listed like for the computer's internal HD, and when I click to format, it tells me nothing, nor gives me no options. It just tells me that it is done.
So I have solved the problem. Below is a reference for other users who might have the same issue:
1) Used GoodManager for Reboot Recovery
2) Made a new Nandroid backup, this time discovering that I could assign the backup to my sd card. And so I did exactly that.
3) Rebooted after backup made.
4) Connect phone to computer via USB, and use Windows Explorer to drag and drop the backup that was sitting on the phone in the same area where the new backup is.
Basically, knowing that I could back up to the SD card, and that TWRP created a file path for exactly that, I knew that I could move the old backup there too.
That said, I very much appreciate the help given to me.
DarkMenace said:
In order for CWM or TWRP to see the files on your memory card it has to be 32GB (those are usually formatted in FAT32). If you have a 64GB memory card that would be formatted in extFAT. The programs cant read extFAT so you would need to take the card out place it in your PC and use a FAT32 program to make it FAT32.
Click to expand...
Click to collapse
I was able to use TWRP to perform nandroid backup directly to my 64GB microUSB - it supported it without any problems (didn't have to even take the microSD out of the phone)
jj14 said:
I was able to use TWRP to perform nandroid backup directly to my 64GB microUSB - it supported it without any problems (didn't have to even take the microSD out of the phone)
Click to expand...
Click to collapse
So TWRP reads extFAT?
DarkMenace said:
So TWRP reads extFAT?
Click to expand...
Click to collapse
apparently it can read and write!
http://forum.xda-developers.com/showpost.php?p=42318153&postcount=46
(device specific)
jj14 said:
apparently it can read and write!
http://forum.xda-developers.com/showpost.php?p=42318153&postcount=46
(device specific)
Click to expand...
Click to collapse
I can't find TWRP in the market and when I goto their website it shows every carrier but Verizon.
DarkMenace said:
I can't find TWRP in the market and when I goto their website it shows every carrier but Verizon.
Click to expand...
Click to collapse
Just noticed you are on Verizon - I installed on my Sprint device, but it looks like it is available for Verizon S4 as well (I went to http://teamw.in/project/twrp2, and clicked "Get TWRP for your device", entered S4 as search criteria and found "TWRP for Samsung Galaxy S4 (Verizon) [jfltevzw]" as the last entry in the list.
Personally, I'd recommend downloading goomanager from the play store, and using that to install.
From http://teamw.in/project/twrp2/181
"Android App Install Method (Preferred):
You must be rooted to use the GooManager install. Download the GooManager app from either location:
Market Link
Direct Download
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically."
jj14 said:
Just noticed you are on Verizon - I installed on my Sprint device, but it looks like it is available for Verizon S4 as well (I went to http://teamw.in/project/twrp2, and clicked "Get TWRP for your device", entered S4 as search criteria and found "TWRP for Samsung Galaxy S4 (Verizon) [jfltevzw]" as the last entry in the list.
Personally, I'd recommend downloading goomanager from the play store, and using that to install.
From http://teamw.in/project/twrp2/181
"Android App Install Method (Preferred):
You must be rooted to use the GooManager install. Download the GooManager app from either location:
Market Link
Direct Download
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically."
Click to expand...
Click to collapse
What's goomanager? I've never heard of it. What's it do?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
What's goomanager? I've never heard of it. What's it do?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
It is basically a front end for goo.im (which is a very popular Android file hosting site) - provides downloads of ROMs, kernels, apps, GApps, recoveries etc
Read more at http://forum.xda-developers.com/showthread.php?p=25943528
So recently my device stopped recognizing the SanDisk 64gb micro-SDXC I had formatted as internal storage. As far as I am aware when you format a SD this way the phone turns it into an encrypted volume and stores the key on internal storage, presumably somewhere the user cannot normally access it. The card itself is not dead, plugging it into my computer verifies this, but I cannot access it. I think some write operation failed and made it invisible to the phone. the phone did the same thing to a 128gb PNY card, but I reformatted it on PC, then reformatted it again on the phone and now the PNY is working fine. my question is, is there any way to extract the encryption key for my 64gb card(Root based tool or otherwise) from the card profile on my phone and decrypt it on a PC so I can reclaim my data? The phone still has a profile for the card, so presumably the key is still in internal storage somewhere. I had about 40gb of media on that card that I had not backed up (photos, videos, music and such). My ohone is not currently rooted but i wouldnt mind rooting it if someone has a root only solution.
I would wipe cache, then data then try another ROM.
sciencetor2 said:
So recently my device stopped recognizing the SanDisk 64gb micro-SDXC I had formatted as internal storage.
Click to expand...
Click to collapse
It is possible, though I have not done it before, I avoid adoptable storage for this reason. Do NOT wipe your ROM, or you will permanently lose your encryption key to your data that you have on the card.
If you put the SD card into a Linux PC that can recognize the partitions (Windows will not show it), you will see two partitions, android_meta and android_expand. To decrypt the big one, android_expand, you will need to recover your key from the phone.
To recover the encryption key, you will need either root access or a custom recovery like TWRP, to access '/data/misc/vold' to retrieve the encryption key (aes-cbc-essiv:sha256). Save the .key file to somewhere safe.
Then something like
dmsetup create crypt1 --table "0 `blockdev --getsize /dev/sdb2` crypt \
aes-cbc-essiv:sha256 00010203040506070809010a0b0c0d0e0f 0 /dev/sdb2 0"
mount -t ext4 /dev/mapper/crypt1 /mnt/1/
More info here - http://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html
Once you have recovered your data, reformat the card and use it as portable storage
SenK9 said:
More info here -nelenkovDOTblogspotDOTcom/2015/06/decrypting-android-m-adopted-storageDOThtml
Once you have recovered your data, reformat the card and use it as portable storage
Click to expand...
Click to collapse
(url edited due to new user restrictions)
Thank you! this is exactly what I was looking for, but i couldn't find anything on google about anyone figuring out all the details (encryption key location, encryption method, usable tool for decryption)
now is there any way i can root, extract the key, then unroot so that i can RMA the phone? It seems to now render any sd i put into it unreadable by itself within about 5 minutes of formatting, regardless whether i format as internal or portable. not sure if this is hardware (reader malfunction) or some software is writing to the card incorrectly, but it is now doing it consistently.
sciencetor2 said:
(url edited due to new user restrictions)
Thank you! this is exactly what I was looking for, but i couldn't find anything on google about anyone figuring out all the details (encryption key location, encryption method, usable tool for decryption)
now is there any way i can root, extract the key, then unroot so that i can RMA the phone? It seems to now render any sd i put into it unreadable by itself within about 5 minutes of formatting, regardless whether i format as internal or portable. not sure if this is hardware (reader malfunction) or some software is writing to the card incorrectly, but it is now doing it consistently.
Click to expand...
Click to collapse
I do not believe it's possible to root or change the recovery without unlocking the bootloader, unless there's some other method I'm not aware of. Even MM systemless root method - http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380, requires unlocking the bootloader, which of course then technically voids the warranty.
However, in this case, it might be worth contacting Moto to inform them of what's happened, it's definitely some kind of bug in the software which has caused this, and thus you are stuck in this catch-22 situation. They might make an exception or have some other solution. Let us know how you go.
SenK9 said:
... requires unlocking the bootloader, which of course then technically voids the warranty. ...and thus you are stuck in this catch-22 situation.
Click to expand...
Click to collapse
Even more of a catch 22 situation, because if i read that correctly, the process for unlocking the bootloader also requires wiping the phone (and thus, the encryption keys) (i miss geohot with his 1 click soft roots). I will wait a little while and see if I or anyone else reading this thread can find a way around that, but it seems ill have to contact Moto support either way, since my 16gb model is barely usable without an SD card.
This is another example of why taking control of your phone before something goes wrong is so important.
Did you try wiping cache yet?
lafester said:
This is another example of why taking control of your phone before something goes wrong is so important.
Did you try wiping cache yet?
Click to expand...
Click to collapse
I checked the recovery menu but there didn't seem to be an option for wiping cache on this device (recovery menu was a little different than I am used to, only had option for factory reset) Also, while wiping cache might conceivably prevent it from screwing up future cards, I don't know if it will fix this one, and i'm not sure if i wanna risk wiping anything without getting my hands on the encryption keys first. if it becomes apparent that i'm just not getting root without wiping, then I'll try playing around with recovery options to at least get back SD slot usage.
You can erase cache in fastboot. If you are locked there is no way to root without wiping data.
lafester said:
You can erase cache in fastboot. If you are locked there is no way to root without wiping data.
Click to expand...
Click to collapse
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
YITBOS said:
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
Click to expand...
Click to collapse
I hadn't heard that... Got a source?
YITBOS said:
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
Click to expand...
Click to collapse
No all that does is allow you to unlock (providing you have a key of course).
well it looks like nobody has found a non wiping solution to root my phone, so I'm going to have to give up on the data and see if I can get back SD functionality, or just RMA the phone. I think i will also publish a script that allows you to plug in your phone and the SD at the same time and allow you to decrypt an internal formatted card by pulling the keys and using them to mount the drive to help people who are in similar situations, but have root. Thanks anyway for the help.
Hi Everyone, I'm stuck in the same catch 22 situation. Device is not rooted or bootloader unlocked, so can't access the key, and trying to root/unlock bootloader will wipe the keys. Any updates, @sciencetor2??
Have you written to Motorola/google about this?
I'm still not ready to give up on the data... hundreds of vacation pictures, that couldn't get backed up.
I'm in the same boat any good news on this?
As long as the phone can see the card, you can change it to portable storage. However, if something goes wrong and phone can not see the card anymore, it's nearly impossible to access the volume without the retrieving the key from the phone, and you must root the phone in order to get the key, as I understand.
I have another similar problem, SD card becomes locked writing and disappears from phone, even I used it as portable storage. And the card can't be formatted at all. So I believe the phone somehow does something and change the state of SD card!
Did anyone find a solution yet. Stuck with same problem. Will loose very important data.
Same here.
I adopted my sdcard as internal storage in CM13.
It was constantly in bootloop, so I formatted the internal memory of the phone to install a new rom ...
But now I can not recover the data within the sd because I can not access it nor with the new rom (I can not even mount it from TWRP) nor from a linux PC (the filesystem is unknown).
Pretty much ... I did not know that the sdcard adopted were encrypted!
Any solution? :\
Hello everybody!
Is there any way to recover the deleted ".key" file?
so i havent gotten back on this thread in a while but i think i at least figured out the "why" on why the card was no longer being recognized. it seems to come down to read/write speed. my 64GB and 128GB cards that i was having the issue with were both U1 cards, which means their read/write is only sitting around 10Mbps, and both of those had issues being detected by the phone after a little bit of time in use. I replaced the card in the same phone a few months back with a high throughput U3 card, and it has been running smoothly ever since. this leads me to the hypothesis that if the card is not fast enough for the phone's taste, it will just ignore it (or timeout on reads, not sure which is actually happening) which is leading to the issues we are experiencing. unfortunately this doesnt lead us to a solution for recovering from the existing cards, but hopefully it will help avoid making the mistake of using a slow card in the future.
Hi All,
there are all these interesting tips how to get adoptable storage to work on Marshmallow with e.g. Samsung devices:
sm set-force-adoptable true
sm list-disks
sm partition DISK private
Click to expand...
Click to collapse
But for me it does not work at all. Does anyone know what could cause this problem?
The phone I am using is a Galaxy A5 2016.
Modelnumber: SM-A510F
Buildnumber: MMB29K.A510FXXU2BPH3
OS: 6.0.1
Many thanks in advance for any help!
Best regards
Up, for me too this isn't working, with or without correct names of the sd card... No format and no repartition...
yellowt said:
Up, for me too this isn't working, with or without correct names of the sd card... No format and no repartition...
Click to expand...
Click to collapse
You can try this.
Please ensure to make a backup of your boot and system partition with twrp before installing.
Install the zip below with twrp then reboot.
Go to settings>storage then tap the sdcard.
You should see the adoptable storage options.
https://www.androidfilehost.com/?fid=24591000424965737
ashyx said:
You can try this.
Please ensure to make a backup of your boot and system partition with twrp before installing.
Install the zip below with twrp then reboot.
Go to settings>storage then tap the sdcard.
You should see the adoptable storage options.
https://www.androidfilehost.com/?fid=24591000424965737
Click to expand...
Click to collapse
Thanks but my phone is completely stock... That's why the adb method was so nice... Can I flash the zip via adb or in others ways?
Thanks a lot!
yellowt said:
Thanks but my phone is completely stock... That's why the adb method was so nice... Can I flash the zip via adb or in others ways?
Thanks a lot!
Click to expand...
Click to collapse
If you want to stay complete stock then this patch is not for you.
ashyx said:
If you want to stay complete stock then this patch is not for you.
Click to expand...
Click to collapse
So there is no information why on the stock version the mentioned commands do not work accordingly?
My phone actually needs to stay stock hence no option for the zip this time.
ev!denz said:
So there is no information why on the stock version the mentioned commands do not work accordingly?
My phone actually needs to stay stock hence no option for the zip this time.
Click to expand...
Click to collapse
It was removed from the framework, so unless it's replaced it's not going to work.
ashyx said:
You can try this.
Please ensure to make a backup of your boot and system partition with twrp before installing.
Install the zip below with twrp then reboot.
Go to settings>storage then tap the sdcard.
You should see the adoptable storage options.
https://www.androidfilehost.com/?fid=24591000424965737
Click to expand...
Click to collapse
I HAVE THE A510F and this just wiped my sd card... thought this would do, but thank you for the work you did and hope this helps others
popeye331 said:
I HAVE THE A510F and this just wiped my sd card... thought this would do, but thank you for the work you did and hope this helps others
Click to expand...
Click to collapse
Of course it wipes your sd card, that's what it's meant to do.
I don't understand the issue? [emoji53]
It doesn't give option for adoptable storage.... Only options are unmount or format.. Sorry for any confusion
popeye331 said:
It doesn't give option for adoptable storage.... Only options are unmount or format.. Sorry for any confusion
Click to expand...
Click to collapse
Did you tap the micro sdcard after installing the patch?
Can you backup your patched boot.img with TWRP then post it up so I can check it?
ashyx said:
Did you tap the micro sdcard after installing the patch?
Can you backup your patched boot.img with TWRP then post it up so I can check it?
Click to expand...
Click to collapse
Yes i did..... I will try to get you that... Honestly haven't never done that but will surely try
i got it to work...yes the zip is awesome and works great...but after install i hit storage/sd/format, after format was finished in notification it said new sd card detected, set up...i hit setup and there was the option for portable or internal storage so again thank you for the great work.......now i just need to figure out why it says device storage is 69 GB used out of 128 when my card is 64 and my phone is 16 and try to also figure out how to make sd the default for download......so again THANK YOU for this zip
popeye331 said:
i got it to work...yes the zip is awesome and works great...but after install i hit storage/sd/format, after format was finished in notification it said new sd card detected, set up...i hit setup and there was the option for portable or internal storage so again thank you for the great work.......now i just need to figure out why it says device storage is 69 GB used out of 128 when my card is 64 and my phone is 16 and try to also figure out how to make sd the default for download......so again THANK YOU for this zip
Click to expand...
Click to collapse
Don't worry about the combined incorrect storage capacity. It seems to common on all Samsung devices. Just pay attention to the individual storage capacity of internal and external which will be correct.
To make sure you are using the external Sdcard as default location tap the sd card and choose migrate data.
Hi ashyx,
I think I went through all the required steps:
- installed TWRP on my SM-A510F
- backed up system+boot partitions
- and finally installed the "adoptable_storage_enabler_ashyx_13916.zip" ZIP through TWRP.
However, once I rebooted, contrary to popeye331, I did NOT have any more options after I went to "Settings > Storage > SDCard" . Only "Format" and "Unmount" were shown, and after I chose "Format" it only offered me to format it as portable storage. After that was completed, I did NOT have a "New SD Card detected" notification as reported by popeye331.
Have I missed sopmething? Was I supposed to root my device by installing SuperSU via TWRP with your custom "UPDATE-SuperSU-v2.65-20151226141550.zip" file??
I hope you can help me as this is driving me nuts ... I wish I bought the HTC One A9 instead of the Galaxy A5 2016 now, I didn't know Samsung was the "Apple" equivalent in the Android ecosystem...
Thanks in advance,
Laurent
PROBLEM SOLVED !! Needed to disable Zip signature verification in TWRP !!
Ok, my bad, problem identified and solved !!!
I did not actually pay enough attention to the log messages during installation of the "adoptable_storage_enabler_ashyx_13916.zip" file through TWRP...
It did display an error message in red stating "Zip signature verification failed", and aborted installation tight after that, but somehow I missed it, rebooted thinking installation had succeeded, and didn't understand why it didn't work...
I only realised my mistake while going through the install procedure a second time. When I noticed the error message I thought at first the Zip might be corrupted, then I Googled the error message and I got the explanation:
Before installing this Zip file, you MUST TURN OFF the "Zip verification" option in TWRP !!!
Once I did that and attempted the installation again, the process went smoothly and succeeded, and after reboot I proceeded exactly as popeye331 explained, the process being actually a bit strange:
You must first format the SD card, but when you first format it you are only presented with the option to format it as portable storage.
HOWEVER, ONCE the formatting has gone through, you do indeed see a notification about a new SD Card being detected, and if you open this notification you are prompted to format the SD card either as portable storage or as internal storage... SO you just have to opt for the latter, and after the card is configured as internal storage it will move some application data onto it for you.... Once this is done it is strongly advisable to reboot, because you might still see the external SD card if your phone is plugged in throuh USB... After you reboot, you will only see one unified storage labelled "Phone" (although you still see the SD card and internal storage as separated entities in Settings > Storage on the device).
Anyway, THANK YOU SO MUCH ashyx for your excellent work, I'm going to make a little donation to you right away to express my gratitude and thank you for all your efforts !!! :good:
Cheers,
Laurent
laurentd75 said:
Ok, my bad, problem identified and solved !!!
I did not actually pay enough attention to the log messages during installation of the "adoptable_storage_enabler_ashyx_13916.zip" file through TWRP...
It did display an error message in red stating "Zip signature verification failed", and aborted installation tight after that, but somehow I missed it, rebooted thinking installation had succeeded, and didn't understand why it didn't work...
I only realised my mistake while going through the install procedure a second time. When I noticed the error message I thought at first the Zip might be corrupted, then I Googled the error message and I got the explanation:
Before installing this Zip file, you MUST TURN OFF the "Zip verification" option in TWRP !!!
Once I did that and attempted the installation again, the process went smoothly and succeeded, and after reboot I proceeded exactly as popeye331 explained, the process being actually a bit strange:
You must first format the SD card, but when you first format it you are only presented with the option to format it as portable storage.
HOWEVER, ONCE the formatting has gone through, you do indeed see a notification about a new SD Card being detected, and if you open this notification you are prompted to format the SD card either as portable storage or as internal storage... SO you just have to opt for the latter, and after the card is configured as internal storage it will move some application data onto it for you.... Once this is done it is strongly advisable to reboot, because you might still see the external SD card if your phone is plugged in throuh USB... After you reboot, you will only see one unified storage labelled "Phone" (although you still see the SD card and internal storage as separated entities in Settings > Storage on the device).
Anyway, THANK YOU SO MUCH ashyx for your excellent work, I'm going to make a little donation to you right away to express my gratitude and thank you for all your efforts !!! :good:
Cheers,
Laurent
Click to expand...
Click to collapse
Great stuff, thanks for the feedback.
ashyx said:
Great stuff, thanks for the feedback.
Click to expand...
Click to collapse
Is it work to a7 2016 too?
Hanif92 said:
Is it work to a7 2016 too?
Click to expand...
Click to collapse
Yes.
Okey let me try. Thanks
The dual boot 6 thread says it creates a secure micro SD partition but Its only for the 128gb devices. I have the 240gb device and I'm wondering if there is another way to make a partition like that.
Unfortunately, I'm not sure what you mean. Do you want to have a split SD partition or reformat the internal "SD card" (storage)?
I want to create a new separate partition one that would not be wiped when you format data. In the dual boot thread it says that it creates a new partition so there is a way I'm just wondering how to do it. Unfortunately the dual boot only works on 128gb device I got the 240...
Macusercom said:
Unfortunately, I'm not sure what you mean. Do you want to have a split SD partition or reformat the internal "SD card" (storage)?
Click to expand...
Click to collapse
jessejamesd2i said:
I want to create a new separate partition one that would not be wiped when you format data. In the dual boot thread it says that it creates a new partition so there is a way I'm just wondering how to do it. Unfortunately the dual boot only works on 128gb device I got the 240...
Click to expand...
Click to collapse
I'm not sure if this is easily possible due to how the super partition works. Unfortunately, this is out of my knowledge. There are ways of repartitioning your device but I'm not sure how it plays together with encryption
I found a guide for doing it but i cant because i need a twrp that has the commands to create or modify partition sizes. I have some knowledge about how to do it because i used to play with linux alot when i was younger. I know how to do it but im worried about encryption & whatever else that i dont know. All i know is they figured out how with the dualsix, I sent him a pm asking how hopefully it was him who compiled the scripts & knows exactly what to do. I really appreciate you taking the time to try to help. I love XDA & its members everyone is quick to try and help and there is not very many people who talk **** and act disrespectful. Thanks for being one of those awesome people!
Macusercom said:
I'm not sure if this is easily possible due to how the super partition works. Unfortunately, this is out of my knowledge. There are ways of repartitioning your device but I'm not sure how it plays together with encryption
Click to expand...
Click to collapse