Hi guys, I unlocked the bootloader in my HTC ONE A9 and I installed the TWRP recovery it asks me how to screen whether to keep the read-only and therefore without modifying the partition system or allowing the changes ... I have the official rom and honestly not I currently intend to change rom..I haven't received + OTA updates for several years now ... I don't know what to choose in this screen because as I should put Magisk and how do you know the "safetyNet" check if it finds the modified system folder pass the control ... now you who are + experts than me I ask you the courtesy to clarify this doubt ... there is a fact that even a zip could modify the system folder ... so if I choose allow changes and install the Magisk zip automatically makes changes to the system folder and then the SafetyNet does not pass?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Captain_Throwback
I ask for your help please, because only you can help me in this problem ... I just don't know how to solve. I am desperate
Practically I put the TWRP latest version 3.4 from this link h**ps://dl.twrp.me/hiae/ (I can't put the full link because I don't have 10 posts yet, it seemed right to write it to make you understand where I downloaded them from) , I load it via the windows cmd command and until I access recovery everything is working, as soon as I enter recovery the first time TWRP asks me as per the screen in the first post whether to keep the read only or allow the changes and I choose "allow changes by swiping down" ... then I restart and from that moment the phone restarts continuously in loop ... I then reflected the original rom (even before I had the original rom) , I change version this time and put the twrp 3.2.1.0 as usual, everything works before accessing recovery, as soon as I access recovery, a problem appears in the decryption and then manages to start the twrp menu I always put allow changes to the file system, I go out and loop again, restarting continuously ... now I am thinking possible that the problem is that I have to select keep read only? otherwise I can't explain why everything works and as soon as I enter recovery for the first time and I swipe on allow the changes then restart the phone in loop ... When it goes in loop I can access recovery and the strange thing is that the language is always in English although I select the Italian language, it is also strange that the setting is not saved ....
android version is 7.0 (software 2.17.401.2)
so now I'm reflecting the original rom a second time without putting any twrp waiting for your answer in understanding where the problem lies .. I hope you can help me .. thank you very much in advance. @Captain_Throwback
fabulas_ said:
@Captain_Throwback
I ask for your help please, because only you can help me in this problem ... I just don't know how to solve. I am desperate
Practically I put the TWRP latest version 3.4 from this link h**ps://dl.twrp.me/hiae/ (I can't put the full link because I don't have 10 posts yet, it seemed right to write it to make you understand where I downloaded them from) , I load it via the windows cmd command and until I access recovery everything is working, as soon as I enter recovery the first time TWRP asks me as per the screen in the first post whether to keep the read only or allow the changes and I choose "allow changes by swiping down" ... then I restart and from that moment the phone restarts continuously in loop ... I then reflected the original rom (even before I had the original rom) , I change version this time and put the twrp 3.2.1.0 as usual, everything works before accessing recovery, as soon as I access recovery, a problem appears in the decryption and then manages to start the twrp menu I always put allow changes to the file system, I go out and loop again, restarting continuously ... now I am thinking possible that the problem is that I have to select keep read only? otherwise I can't explain why everything works and as soon as I enter recovery for the first time and I swipe on allow the changes then restart the phone in loop ... When it goes in loop I can access recovery and the strange thing is that the language is always in English although I select the Italian language, it is also strange that the setting is not saved ....
so now I'm reflecting the original rom a second time without putting any twrp waiting for your answer in understanding where the problem lies .. I hope you can help me .. thank you very much in advance. @Captain_Throwback
Click to expand...
Click to collapse
Just don't allow changes. It's not that hard, lol.
Captain_Throwback said:
Just don't allow changes. It's not that hard, lol.
Click to expand...
Click to collapse
@Captain_Throwback
you are right, but since everywhere it says that you have to allow the changes it seemed very strange that if I allowed the changes it would go in a loop ... I reflected the rom again, put the Twrp 3.4 back and this time I gave "keep read only "and the problem did not arise ... but there are still a series of problems in TWRP, at the beginning when I start TWRP immediately after entering the encryption sequence, the screen appears where it says:" unable to mont storage "in red and then successfully decrypted and immediately the TWRP menu appears ..... I tried to make a backup but there are a series of errors as you can see from the screen below ... I also flashed magisk v21 from twrp and here too it gave me errors at the beginning similar to the ones it gave me for backup, although in this case it told me successfully installed at the end. After I did a check with a root checker and it tells me that the root was not done, also with magisk manager I did a SafetyNet check and it gives me both false, both CTS certified and base intefrity ... so there is something that it's not working properly ....
Before loading Magisk from recovery I had checked the SafetyNet with an app and it gave me CTS false and basic integrity true, then after loading Magisk both false ...
Then each time I select the Italian language in Twrp and the next time it always starts in English ... I don't understand why it didn't save the setting.
is there any particular version compatible with HTC One A9 of TWRP? I downloaded the hiae version from the link posted in the previous post ... I honestly don't know how to fix ..
Can you help me please to solve? thank you
fabulas_ said:
@Captain_Throwback
you are right, but since everywhere it says that you have to allow the changes it seemed very strange that if I allowed the changes it would go in a loop ... I reflected the rom again, put the Twrp 3.4 back and this time I gave "keep read only "and the problem did not arise ... but there are still a series of problems in TWRP, at the beginning when I start TWRP immediately after entering the encryption sequence, the screen appears where it says:" unable to mont storage "in red and then successfully decrypted and immediately the TWRP menu appears ..... I tried to make a backup but there are a series of errors as you can see from the screen below ... I also flashed magisk v21 from twrp and here too it gave me errors at the beginning similar to the ones it gave me for backup, although in this case it told me successfully installed at the end. After I did a check with a root checker and it tells me that the root was not done, also with magisk manager I did a SafetyNet check and it gives me both false, both CTS certified and base intefrity ... so there is something that it's not working properly ....
Before loading Magisk from recovery I had checked the SafetyNet with an app and it gave me CTS false and basic integrity true, then after loading Magisk both false ...
Then each time I select the Italian language in Twrp and the next time it always starts in English ... I don't understand why it didn't save the setting.
is there any particular version compatible with HTC One A9 of TWRP? I downloaded the hiae version from the link posted in the previous post ... I honestly don't know how to fix ..
Can you help me please to solve? thank you
Click to expand...
Click to collapse
If you're having issues with TWRP, please post them in the TWRP thread, and follow the instructions in that thread's OP for posting a log. I can then review the log and reply there.
P.S. And while you're at it, you should read the FAQ in the TWRP thread to get some better understanding of why that read-only page is there.
P.P.S. Ugh, I forgot my TWRP thread got lost when they flattened the forum. Well, recovery.log is in /tmp, so you can use adb pull to retrieve it, or if you have an SD card in the device, you can switch to it as your default storage in the Mount page and then use Advanced -> Copy Log.
P.P.P.S. I'm using TWRP and Magisk 21 without any issue on my device, but if you're on old firmware, then that could be why it's not working for you. Let me upload a debug TWRP version and we can see exactly where things are going wrong. Give me an hour or so to build it.
Captain_Throwback said:
If you're having issues with TWRP, please post them in the TWRP thread, and follow the instructions in that thread's OP for posting a log. I can then review the log and reply there.
P.S. And while you're at it, you should read the FAQ in the TWRP thread to get some better understanding of why that read-only page is there.
P.P.S. Ugh, I forgot my TWRP thread got lost when they flattened the forum. Well, recovery.log is in /tmp, so you can use adb pull to retrieve it, or if you have an SD card in the device, you can switch to it as your default storage in the Mount page and then use Advanced -> Copy Log.
P.P.P.S. I'm using TWRP and Magisk 21 without any issue on my device, but if you're on old firmware, then that could be why it's not working for you. Let me upload a debug TWRP version and we can see exactly where things are going wrong. Give me an hour or so to build it.
Click to expand...
Click to collapse
the firmware version is not old, it is android version is 7.0 (software 2.17.401.2) taken here on xda and it is the same version I had received via OTA.
Since the root with Magisk was not successful and, moreover, the safetyNET gave me both CTS and false basic integrity I reflected the rom again now so that we have a clean phone .. first we solve the problems with TWRP and then after I see to put Magisk ... now so I reflashed the rom and checking the Safetynet without having put the Twrp yet it gives me false CTS and basic integrity true, I then put the twrp 3.4 and the Safetynet remained the same ... my fear is that when I put Magisk back even the base integrity becomes false as before ... but for the moment I don't put Magisk ...
I did the backup again with the twrp to see if anything had changed but nothing, same errors ...
I am very willing to do what you ask me, the problem is that I am not an expert, so I can only do it if you tell me step by step what to do ...
You asked me for the recovery.log but I didn't understand how to recover it, could you explain me step by step in detail? you told me that you were preparing the debug that then I should load I don't know if this is enough or you always need the recovery.log ... anyway yes i have an sd card in the phone ...
As for writing in the TWRP room, I initially searched for it but couldn't find it and so I wrote in my phone section.
thank you very much for your willingness to help me
fabulas_ said:
the firmware version is not old, it is android version is 7.0 (software 2.17.401.2) taken here on xda and it is the same version I had received via OTA.
Since the root with Magisk was not successful and, moreover, the safetyNET gave me both CTS and false basic integrity I reflected the rom again now so that we have a clean phone .. first we solve the problems with TWRP and then after I see to put Magisk ... now so I reflashed the rom and checking the Safetynet without having put the Twrp yet it gives me false CTS and basic integrity true, I then put the twrp 3.4 and the Safetynet remained the same ... my fear is that when I put Magisk back even the base integrity becomes false as before ... but for the moment I don't put Magisk ...
I did the backup again with the twrp to see if anything had changed but nothing, same errors ...
I am very willing to do what you ask me, the problem is that I am not an expert, so I can only do it if you tell me step by step what to do ...
You asked me for the recovery.log but I didn't understand how to recover it, could you explain me step by step in detail? you told me that you were preparing the debug that then I should load I don't know if this is enough or you always need the recovery.log ... anyway yes i have an sd card in the phone ...
As for writing in the TWRP room, I initially searched for it but couldn't find it and so I wrote in my phone section.
thank you very much for your willingness to help me
Click to expand...
Click to collapse
TWRP thread has been re-created here: https://forum.xda-developers.com/one-a9/recovery-twrp-touch-recovery-t4185995
Please note the in the OP there how to pull a log, and then post your recovery log there. You don't need to perform a backup, just boot TWRP and then pull the log.
Captain_Throwback said:
TWRP thread has been re-created here: https://forum.xda-developers.com/one-a9/recovery-twrp-touch-recovery-t4185995
Please note the in the OP there how to pull a log, and then post your recovery log there. You don't need to perform a backup, just boot TWRP and then pull the log.
Click to expand...
Click to collapse
I have recovered the recovery.log file
I started the Twrp -advanced-copy log and saved it in the SD card .. is that correct?
I'm sorry I didn't understand if I have to post the log in the thread you linked from the TWRP or I have to put it here ... the file recovery.log I upload it to a host site and I'll put the link .. just tell me in which thread. Thanks.
fabulas_ said:
I have recovered the recovery.log file
I started the Twrp -advanced-copy log and saved it in the SD card .. is that correct?
I'm sorry I didn't understand if I have to post the log in the thread you linked from the TWRP or I have to put it here ... the file recovery.log I upload it to a host site and I'll put the link .. just tell me in which thread. Thanks.
Click to expand...
Click to collapse
TWRP thread.
Captain_Throwback said:
TWRP thread.
Click to expand...
Click to collapse
log loaded into the thread
fabulas_ said:
Ok perfect .. very kind. Thanks.
Before unlocking the bootloader and then doing the root I had a space problem as the internal memory is only 16gb ... now since the phone is still fine I wanted to find a solution.
And I saw that through the Link2SD app I can move some apps to the microsd (maybe the apps I use less), to do this I read that you have to make a partition in the microsd so that you can move the apps and that it is seen as "an extension of the internal memory" ... so I should connect the microsd to the pc to create the partition ... then there is another way which is to format the microsd as internal memory but this is not recommended ... while instead do as I wrote before a partition in the microsd and use it as an "extension of the internal memory" do you think it is a good solution to solve the app space problem? because I only have the apps in the internal memory ... the media are automatically saved on microsd ... so in theory by making a partition in the microsd the partition is an extension of the internal memory and the non-partitioned part should be used by the camera to save photos and videos .. do you think it's feasible?
One last thing as an app to remove the various system apps that I don't use like some Google apps, now that I have root I can do it ... which app do you recommend to do this?
Click to expand...
Click to collapse
Replying here as this conversation is no longer related to TWRP.
I'd actually recommend partially formatting the SD card as internal memory (depending on the size and speed of your SD card). If you have a large capacity UHS-3 card, you can set it up in Android with mixed adoptable storage, so that part of the SD card gets allocated as additional Phone Storage, and the rest can still be used as a standard SD card. That's how I have the card in my A9 set up because of the memory issues you mentioned.
The thread I used to convert mine is here: https://forum.xda-developers.com/idol-3/general/make-sd-card-semi-adopted-t3399510
An alternative link is here: https://android.stackexchange.com/q...into-two-parts-part-adoptable-storage-and-par
(both describe the same process)
Once that's done, you'll have an option to move data for each supported app to the SD card, or you can migrate all of your data to the new partition.
I don't recommend removing any system apps - rather I would just disable apps that you don't need in Settings. You can't really reclaim the space and do anything with it, since system is read-only. There are also ways to "remove" the apps systemlessly using Magisk, but you'll have to research that on your own if you choose to go that route.
EDIT: I have a 128GB card which I split into two 64GB partitions to give me more internal space, while retaining portable storage. This is what that looks like in Android.
EDIT 2: FYI - The TWRP you're currently using fully supports identifying and mounting mixed Adoptable storage, while the official TWRP doesn't. So you'll want to make sure you stay on that one if you decide to go that route.
Captain_Throwback said:
Replying here as this conversation is no longer related to TWRP.
I'd actually recommend partially formatting the SD card as internal memory (depending on the size and speed of your SD card). If you have a large capacity UFS-3 card, you can set it up in Android with mixed adoptable storage, so that part of the SD card gets allocated as additional Phone Storage, and the rest can still be used as a standard SD card. That's how I have the card in my A9 set up because of the memory issues you mentioned.
The thread I used to convert mine is here: https://forum.xda-developers.com/idol-3/general/make-sd-card-semi-adopted-t3399510
An alternative link is here: https://android.stackexchange.com/q...into-two-parts-part-adoptable-storage-and-par
(both describe the same process)
Once that's done, you'll have an option to move data for each supported app to the SD card, or you can migrate all of your data to the new partition.
I don't recommend removing any system apps - rather I would just disable apps that you don't need in Settings. You can't really reclaim the space and do anything with it, since system is read-only. There are also ways to "remove" the apps systemlessly using Magisk, but you'll have to research that on your own if you choose to go that route.
EDIT: I have a 128GB card which I split into two 64GB partitions to give me more internal space, while retaining portable storage. This is what that looks like in Android.
EDIT 2: FYI - The TWRP you're currently using fully supports identifying and mounting mixed Adoptable storage, while the official TWRP doesn't. So you'll want to make sure you stay on that one if you decide to go that route.
Click to expand...
Click to collapse
so if I understand correctly you did exactly what I would like to do and that is a partition in the microsd to be used as an extension of the internal memory and the rest to be used as an external memory .... in any case you are confirming that it is not convenient to format the microsd as internal memory but only make a partition .. you have 32gb of internal memory I think with only 16gb it is really insufficient memory.
I have a 64gb Lexar class 10 microsd (633x microSDXC UHS I class 10) it's not slow but not even super fast ... do you think it's good for performance or will I have to buy another one?
Now I take a look at the 2 links you gave me ..
As for the system apps that I would like to uninstall they are the various apps like:
Chrome (I use another browser)
documents
Drive
Sheets
Photo
Google Play Movies
Google Play Music
Presentations
and some others
You told me that I can not do it because I have the system in read only, but it would be that famous TWRP screen where I put "keep read only" or would it be something else?
I sincerely would like to uninstall them, they just take up space and put them in my apps just to mess with them so I'd rather delete them ..
fabulas_ said:
so if I understand correctly you did exactly what I would like to do and that is a partition in the microsd to be used as an extension of the internal memory and the rest to be used as an external memory .... in any case you are confirming that it is not convenient to format the microsd as internal memory but only make a partition .. you have 32gb of internal memory I think with only 16gb it is really insufficient memory.
I have a 64gb Lexar class 10 microsd (633x microSDXC UHS I class 10) it's not slow but not even super fast ... do you think it's good for performance or will I have to buy another one?
Now I take a look at the 2 links you gave me ..
As for the system apps that I would like to uninstall they are the various apps like:
Chrome (I use another browser)
documents
Drive
Sheets
Photo
Google Play Movies
Google Play Music
Presentations
and some others
You told me that I can not do it because I have the system in read only, but it would be that famous TWRP screen where I put "keep read only" or would it be something else?
I sincerely would like to uninstall them, they just take up space and put them in my apps just to mess with them so I'd rather delete them ..
Click to expand...
Click to collapse
Deleting them saves you no space. They are on the system partition, and you can't put anything else there anyway. Disabling them is the best way to go, and like I said before, because system is read-only, you can't really delete them anyway (I'm sure you recall what happened when you allowed modifications before in TWRP). But you'll have to deal with that yourself.
I'd recommend a UHS-3 card like I said before, but you can try it with the one you have and see how it performs, just to make sure you understand the process.
Captain_Throwback said:
Deleting them saves you no space. They are on the system partition, and you can't put anything else there anyway. Disabling them is the best way to go, and like I said before, because system is read-only, you can't really delete them anyway (I'm sure you recall what happened when you allowed modifications before in TWRP). But you'll have to deal with that yourself.
I'd recommend a UHS-3 card like I said before, but you can try it with the one you have and see how it performs, just to make sure you understand the process.
Click to expand...
Click to collapse
Ok then I turn them off as you said ..
The fact of having put "keep read only", in the future this thing can create problems for me? you wrote about "But you'll have to deal with that yourself." this sentence worries me because it makes me think that maybe that choice can create problems for me in the future ...
Thinking about it, about the fact that I had that loop problem when I put "allow changes", it could not be that the reason was because the memory was compromised given the various errors it gave me and having made the "format data" that I did it fix the errors I could also do "allow changes" without anything happening?
fabulas_ said:
Ok then I turn them off as you said ..
The fact of having put "keep read only", in the future this thing can create problems for me? you wrote about "But you'll have to deal with that yourself." this sentence worries me because it makes me think that maybe that choice can create problems for me in the future ...
Thinking about it, about the fact that I had that loop problem when I put "allow changes", it could not be that the reason was because the memory was compromised given the various errors it gave me and having made the "format data" that I did it fix the errors I could also do "allow changes" without anything happening?
Click to expand...
Click to collapse
I've guided you as much as I can - at this point you should research and figure out where to go from here. Or you can try allowing modifications and see what happens. If it works, great. If not, well then you know what you have to do. You should be able to recover from any situation at this point. If you run into issues with TWRP, you know where the thread is .
Captain_Throwback said:
I've guided you as much as I can - at this point you should research and figure out where to go from here. Or you can try allowing modifications and see what happens. If it works, great. If not, well then you know what you have to do. You should be able to recover from any situation at this point. If you run into issues with TWRP, you know where the thread is .
Click to expand...
Click to collapse
if you tell me that being read only will not give me problems in the future I keep it like this ... I certainly know what to do by now as you say ... only if you tell me that being read only it will give problems and it will be a strong limitation then I try to make the last effort and try again ... if instead you tell me that I could leave it even so that it will not be a problem then I leave it like this ... now in TWRP this screen does not appear + which allows me the choice although I have always chosen "keep read only" but I never checked the box "do not ask me again" .... the possibility to write to the file system is only from TWRP or could I get it in another way?
@Captain_Throwback
I mention you because it may be that you have already read my post and therefore you would not have seen this addition.
I managed to successfully uninstall some apps like play music and play movies via adb with commands given via cmd..it worked perfectly.
practically just enter on
adb shell
and then through this command:
pm uninstall -k --user 0 com.google.android.videos (just enter the package name)
obviously you will know these things for sure it was just to tell you how I did it.
as for what I had written before .. if in the future I need to write on the system I have the possibility to modify this in some way since the choice screen on TWRP does not appear +?
As for the partition of the Microsd I gave a reading and I saw that it is done via adb so if I understand correctly always where I deleted those apps from the system ...
In the meantime I would try with the microsd that I already have is 64gb .. I would put 32gb the internal partition and the rest external ...
In this case I insert the microsd in the pc and open adb and give these commands
adb shell sm list-disks adoptable
The name of my microsde will appear then in case it is disk: 179,128 I give this other command:
adb shell sm partition disk: 179,128 mixed 50
so to do 50% internal and 50% external ... only these 2 commands I have to do and stop? Thanks
@Captain_Throwback
I made the partition to the microsd, I take the liberty of writing to you just because you recommended this method ... if you prefer I ask in the thread you indicated ..
Basically the result is that I see the partition correctly while the remaining external memory tells me that it is damaged if I click on it it tells me "configure" and makes me format the microsd, doing this obviously also removes the partition ...
I tell you exactly the steps I took ..
I ejected the microsd from Settings / Storage after which I gave these commands:
adb shell sm list-disks adoptable
adb shell sm partition disk: 179.32 mixed 65
I didn't do anything else ... the result is what I wrote you before. I am attaching a photo so you can see it. I recognize that you have already helped me enough and thank you very much ... let me know .. Thanks.
fabulas_ said:
@Captain_Throwback
I made the partition to the microsd, I take the liberty of writing to you just because you recommended this method ... if you prefer I ask in the thread you indicated ..
Basically the result is that I see the partition correctly while the remaining external memory tells me that it is damaged if I click on it it tells me "configure" and makes me format the microsd, doing this obviously also removes the partition ...
I tell you exactly the steps I took ..
I ejected the microsd from Settings / Storage after which I gave these commands:
adb shell sm list-disks adoptable
adb shell sm partition disk: 179.32 mixed 65
I didn't do anything else ... the result is what I wrote you before. I am attaching a photo so you can see it. I recognize that you have already helped me enough and thank you very much ... let me know .. Thanks.
Click to expand...
Click to collapse
Did you read both links I posted?
Pretty sure one describes that scenario...
EDIT: You can also boot into TWRP and format your portable storage and that should fix it.
Captain_Throwback said:
Did you read both links I posted?
Pretty sure one describes that scenario...
EDIT: You can also boot into TWRP and format your portable storage and that should fix it.
Click to expand...
Click to collapse
I went to re-read both the link as per your indication and perhaps I found the solution in the second link (located at the bottom of the page) I will report here what is written for convenience.
____________________________
In addition though, you might get the error that your SD card on your device storage is corrupted. If so follow these steps.
After you have partitioned the disk and while your SD card is corruped enter In the terminal the following:
$> adb shell sm list-volumes all
Which will list your volumes, for example:
private mounted null
public:179,1 mounted B5B1-140C
private:179,3 unmountable null
emulated mounted null
Then enter the following replacing 179,3 with whichever disk numbers you are given:
$> adb shell sm format private:179,3
$> adb shell sm mount private:179,3
Now your SD card in device storage should be properly mounted and your portable storage will still be there.
______________________________
Attached I have put what I see in adb with the command
adb shell sm list-volumes all
In my case as you can see it is a little different there are some voices in + and also a little different ... for example there are 2 voices one "unmonted" and one "unmountable" according to the explanation it should be the unmountable one but it is " public "and not" private "as in the example.
So in my specific case I also have to change the command to be given after and write "public" instead of "private" like this?
adb shell sm format public: 179.33
adb shell sm mount public: 179.33
As for the formatting you told me in TWRP you had to do it now with the partition already done I guess, but doing it from TWRP does not format the entire microsd by canceling the partition (as happens if you format it from the phone menu) but only formats the external partition?
Can you tell me the exact procedure to do from TWRP because I tried but can't find how to format it ...
I tried to go to Advanced-partition SD, here it makes me select only Sd card lexar 21017Mb (which would be the internal partition), then there is Microsd card (0MB) which is not selectable because it is the one that says damaged ... not i know if this is the correct path..can you let me know please? Thanks always
fabulas_ said:
I went to re-read both the link as per your indication and perhaps I found the solution in the second link (located at the bottom of the page) I will report here what is written for convenience.
____________________________
In addition though, you might get the error that your SD card on your device storage is corrupted. If so follow these steps.
After you have partitioned the disk and while your SD card is corruped enter In the terminal the following:
$> adb shell sm list-volumes all
Which will list your volumes, for example:
private mounted null
public:179,1 mounted B5B1-140C
private:179,3 unmountable null
emulated mounted null
Then enter the following replacing 179,3 with whichever disk numbers you are given:
$> adb shell sm format private:179,3
$> adb shell sm mount private:179,3
Now your SD card in device storage should be properly mounted and your portable storage will still be there.
______________________________
Attached I have put what I see in adb with the command
adb shell sm list-volumes all
In my case as you can see it is a little different there are some voices in + and also a little different ... for example there are 2 voices one "unmonted" and one "unmountable" according to the explanation it should be the unmountable one but it is " public "and not" private "as in the example.
So in my specific case I also have to change the command to be given after and write "public" instead of "private" like this?
adb shell sm format public: 179.33
adb shell sm mount public: 179.33
As for the formatting you told me in TWRP you had to do it now with the partition already done I guess, but doing it from TWRP does not format the entire microsd by canceling the partition (as happens if you format it from the phone menu) but only formats the external partition?
Can you tell me the exact procedure to do from TWRP because I tried but can't find how to format it ...
I tried to go to Advanced-partition SD, here it makes me select only Sd card lexar 21017Mb (which would be the internal partition), then there is Microsd card (0MB) which is not selectable because it is the one that says damaged ... not i know if this is the correct path..can you let me know please? Thanks always
Click to expand...
Click to collapse
You seem to have figured out the command so you should just try it. You seem to want confirmation before you do any steps, and I'm not really here to hand-hold - you're going to have to just try these things and see what happens. I've found that's the best way to learn.
In TWRP, to format the portable partition on the SD card just Wipe -> check "Micro SD card" -> swipe to complete action.
Hopefully one of those methods will resolve your corrupted issue and you can use the card. I don't plan on replying here any further so please don't ask me anymore questions or mention me. Thanks.
Related
Everyone,
I've written this a bunch of times but and putting it in
it's own thread so folks can read and use it.
Memory and Storage:
/sdcard -- internal memory of the tablet
/sdcard2 -- microSD card in the external slot
/usbdisk -- USB key slot
Stock Recovery Info:
Main method: Put your recovery folder and update.zip on /sdcard, turn off the tablet, the press power and volume + to initiate standard recovery.
Second method: Put your recovery folder and update.zip on a microSD card. Edit the command file in the recovery folder with Notepad to change the location from /sdcard to /sdcard2 and save it with the name "command" (NO
.txt or other file extension). Then boot recovery with power/volume + and the OS will use the sdcard (assuming you don't have a live recovery/update.zip file in /sdcard).
Third method: If you can boot recovery to CWM but can't get your ROM to work, go in recovery to the mount menu and go down to the mount USB memory option and choose it. Then plug your connector cable from the miniUSB port to your PC. When you plug into your PC an Explorer window should open and you should have a drive letter representing the G-Tablet (it's G: on mine) on your menu. You now can select that letter and you have access to your tablet memory (/sdcard). I've even had a time or two when not a single file showed!!! I added update.zip and recovery and loaded
a ROM!
The tablet boot process apparently checks /SDCARD. If it doesn't find a recovery file there it does the same check if you have a miniSD external card installed. The large USB slot is not useable for booting or recovery so far as I have determined or read.
I hope this helps you.
Rev
EDIT: I didn't put one fact in here about recovery that everyone should know. When you run a recovery operation, the system deletes the command file so you can't accidentally do it again. If you have to run a recovery or
attempt to load something again, make sure you have a command file in the recovery folder with the correct command in it!!! Sorry I omitted this first time around.
Placeholder
Placeholder
Hope everybody who needs this has seen it. I won't kick it up again.
Rev
Can you also add information about partitioning of /sdcard and why would one need it?
Is there another "hidden" flash memory available for firmware or all mods and custom ROMs go into /sdcard only?
Thanks so much, I thought I'm dead cuz I wiped out everything.
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
HackaMathecian said:
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
Click to expand...
Click to collapse
You need to use nvflash (nvidia tegra SoC flashing utility). There are alot of posts about it. Do be carefull if you go this route, as even though you will not damage your tablet, it may be difficult to put it back to a bootable state if you don't do it properly.
thanks!
thanks great. simple and to the point. should help people that get confused. thanks again!
Vlad_z,
It has been my experience that when somebody gets boot loops, it often involves a
partition problem. Also, sometimes the G-Tablet does flaky things. I have one I
just shut down. Restarted it with boot looping and had to rebuild.
The three locations listed above are the three memory places you can store stuff
unless you find software that custom sets up something else.
Rev
Os Money:
http://forum.xda-developers.com/showthread.php?t=861950
This thread completely explains the NVFlash process.
Rev
That's kind of odd, my removable sd card ended up with the label ex-sd. Doesn't seem to be messing anything up though.
sixtofive,
I've never seen or heard of that with the stock ROM. Are you running a different ROM?
Some of them do change the directories.
Rev
So simply put, we should copy and backup the recovery folder and update.zip in /sdcard (or tablet storage) and when things get f'ed up, we move the recovery folder and update.zip back into the /sdcard?
Maybe it's just me, but I looked into the recovery that was already in the tablet and there's nothing in it; is that normal? If not, can anyone provide the back up recovery folder and update.zip just in case?
sam,
Recovery is simply a folder which holds a file named "command" in it. Command is a file
that has the command line in it with the command and parameters to "recover" or "load" files onto your G-Tablet.
Sometimes when your tablet gets messed up, you can still use recovery and are lucky. But sometimes the recovery partition gets damaged and then you have to look
for other ways to get in and fix things.
http://forum.xda-developers.com/showthread.php?t=1010943
Many of us keep telling people there is a lot to learn here -- and Android doesn't have
all the stuff built into it Windows does. Nor is Android known for it's great documentation!
If everyone would read all the stickies at the start of the forums, it would provide
probably 80% of everything they need to know.
Rev
If OP also put links to stock ROMs, that would be great
interesting...even though I don't have a microSD card in mine /sdcard2 seems to be a valid directory within "root explorer"
what partition and memory structure should I be seeing on my brand new g-tablet? any suggestion on "mount" and "df" output?
Question, which is the best method or quicker to backup before attempting other rom installs?
Deleting CWM
How would one delete CWM so that the tablet can be returned?
Got my gtablet last evening. Seems there is a lot to learn.
thanks butchconner...
Thanks all the people who are contributing at xda. You are doing a wonderful job. In fact I bought this device because of you ( I think Viewsonic owes you guys a lot. At least they avoided a big loss because of you. )
Two questions:
1) Is it recommended to flash back to stock before changing roms?
2) Is there a link to the stock Rom files that I am missing?
Thanks
Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers
Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?
One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue
Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!
try this- http://forum.xda-developers.com/showthread.php?t=2329200
Hey guys, I've found a way to recover files from the INTERNAL Memory of the Samsung Galaxy S4.
A lot of people have said that it's not possible, but I'm here to prove them wrong.
You have to have rooted your phone before carrying out these steps. Don't post here asking for help rooting, there's plenty of other threads that can help you with that.
I hold zero liability in the event that you make a nice brick out of your phone. If you do not feel comfortable working with these commands, then please don't follow them.
You're going to need an SD Card that's at least the size of the internal memory on the phone. A smaller one would work, but keep in mind not all the files are going to be recovered.
If the SD Card is brand spanking new, you can skip step number 1.
Format the SDCard with a layer of 0's. This is done so that none of the old data will interfere with your recovery. This step is optional.
Root the Device
Install Terminal Emulator
Insert the SDCard
In Terminal Emulator run the command to gain super user privileges
Code:
su
Grant Terminal Emulator super user privileges
Run this command,
Code:
dd if=/dev/block/mmcblk0p29 of=/storage/extSdCard/raw.dd
Wait. Leave your phone plugged into an AC Adapter, and go grab a can of pop. This command will take a looong time. Couple hours to a day.
Once the command is finished running, shutdown your phone.
Remove the SDCard, and connect it to a computer
Download TestDisk
Open PhotoRec
Select the SDCard and press enter
Use the first option of "Unknown"
Then press "Other"
Select the Directory to backup the files to
Profit
'
How it works:
By dd'ing the internal memory to a file on the SDCard, you're doing a raw copy of the data.
Once the data is copied onto the SDCard, PhotoRec will scan the SDCard for deleted data, doing so will scan the raw file for photos. Not just photos, all files can be recovered using this method.
This method works on all rootable phones, provided you can figure out where the dev block for the internal memory is.
Hope you guys get your files recovered. I know I did
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
jamieridler said:
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
Click to expand...
Click to collapse
Any app you recommend in particular?
Bingley said:
Any app you recommend in particular?
Click to expand...
Click to collapse
Tbh I just downloaded the first app I came across that was free and had half decent reviews, can't remember what one, it was a little while ago, but there are loads of them in the store.
jamieridler said:
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
Click to expand...
Click to collapse
A lot of those apps are for the external SD Card, only support the FAT filesystem, and not as robust as PhotoRec from TestDisk.
Newer devices(Such as the S4) have an ext3 filesystem I believe, and a few paid apps claim to offer support for it.
... Not to mention TestDisk is Open Source :angel:
zzarzzur said:
A lot of those apps are for the external SD Card, only support the FAT filesystem, and not as robust as PhotoRec from TestDisk.
Newer devices(Such as the S4) have an ext3 filesystem I believe, and a few paid apps claim to offer support for it.
... Not to mention TestDisk is Open Source :angel:
Click to expand...
Click to collapse
Although some might well be limited to FAT filesystem, some are not, its up to the user to check before downloading and installing. After that rather simple search and install, I managed to recover every img file on my phone, current and deleted, and back it all up to external memory, all with a free app, which offers img file recovery for free and any other file type of your choice for a small, one off, cost, if you needed it. I recovered almost 1gb of img files in under 10 minutes.
Am I correct in assuming your method copies the entire contents of the internal memory, or a portion of it, to an SD card before starting the search for deleted files? I'm just an amateur with little knowledge trying to figure out how your method works. Sorry don't mean to bash your method of doing it either, just commenting on this as your post suggest no one has ever been able to do this before and your method is the one and only way it can be done.
But if the device is factory reset, will you be able to get files? If i sell my device i don't want anyone sneaking on my photos.
problems
zzarzzur said:
Hey guys, I've found a way to recover files from the INTERNAL Memory of the Samsung Galaxy S4.
A lot of people have said that it's not possible, but I'm here to prove them wrong.
You have to have rooted your phone before carrying out these steps. Don't post here asking for help rooting, there's plenty of other threads that can help you with that.
I hold zero liability in the event that you make a nice brick out of your phone. If you do not feel comfortable working with these commands, then please don't follow them.
You're going to need an SD Card that's at least the size of the internal memory on the phone. A smaller one would work, but keep in mind not all the files are going to be recovered.
If the SD Card is brand spanking new, you can skip step number 1.
Format the SDCard with a layer of 0's. This is done so that none of the old data will interfere with your recovery. This step is optional.
Root the Device
Install Terminal Emulator
Insert the SDCard
In Terminal Emulator run the command to gain super user privileges
Code:
su
Grant Terminal Emulator super user privileges
Run this command,
Code:
dd if=/dev/block/mmcblk0p29 of=/storage/extSdCard/raw.dd
Wait. Leave your phone plugged into an AC Adapter, and go grab a can of pop. This command will take a looong time. Couple hours to a day.
Once the command is finished running, shutdown your phone.
Remove the SDCard, and connect it to a computer
Download TestDisk
Open PhotoRec
Select the SDCard and press enter
Use the first option of "Unknown"
Then press "Other"
Select the Directory to backup the files to
Profit
'
How it works:
By dd'ing the internal memory to a file on the SDCard, you're doing a raw copy of the data.
Once the data is copied onto the SDCard, PhotoRec will scan the SDCard for deleted data, doing so will scan the raw file for photos. Not just photos, all files can be recovered using this method.
This method works on all rootable phones, provided you can figure out where the dev block for the internal memory is.
Hope you guys get your files recovered. I know I did
Click to expand...
Click to collapse
So i've followed your guidelines to a 'T' with a brand new 64g (huge, i know) Sd card, but the command line responds with, "writer error: file to large". Any advice as to how to proceed?
Really appreciate your efforts on this issue, btw!
How I unbricked "Decryption unsuccessful" The password is correct but... (Apps2SD)
Hello, I don't usually post in tech forums, I usually the guy that only reads,
but this is the time when i could not find the straight answer to my problem and had to google the solution out of similar posts, so I decided to glue everything together and write my solution to this particular situation,
so I might save a lot of time to someone who got in exact or similar situation.
Sorry for my crappy English, but here we go.
What this post trying to solve:
You stuck at boot loop: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt.
and how to make it work Apps2SD with Huawei P9 SD card with enabled password protection.
Basically my Huawei P9 (EVA L-19) with Android 7.0 Nougat got running out of internal space, and i am really a heavy user on apps. Kirin 955 handles just fine as long as it has at least 10Gb of internal free space.
I have SD card 64Gb, but huawei stopped support, native move apps to SD, long time ago. My device is rooted, so I was searching for a solution. There is few apps that can transfer your internal memory apps to SD by using root, but the one that actually worked for me is Apps2SD. The thing is, my SD card is password protected (Huawei native function) I want to keep this function in case of device getting stolen.
Problem is, many third party apps that move your apps to SD, does not know anything about Huaweis SD card password feature. In fact (as far as i tested) only Huawei phone allows you to enter password and show contents of SD card, no PC, or for example Samsung phone will recognize this SD card.
So i was messing with Apps2SD, partitioned my SD card in to 2 primary partitions, 1- exfat, 2- Ext3. It works kinda fine, but after reboot, there is delay, Huawei unlocks SD card after main boot part, and Apps2SD does not understand this and show that it failed to mount second partition.
In this case, Apps2SD starts giving you solutions, one of them is this ADVANCED mounting option. It does not tells u about any dangers, nothing really.
I chose that option to see if it will be able to see second partition contents faster, rebooted - boom bricked.
You see the message: "Decryption unsuccessful" and asks you for decryption password. It might be SD card password, not sure, it does not matter, because you can type ANYTHING and it always say:
"The password that you entered is correct but unfortunately your data is corrupt". And gives you only option: fully data factory reset. Now hold your horses, dont press that. I just knew that this is bull**** and no way
my personal data is corrupted, its just some hadshake issue. (I was right i fully recovered everything up n running)
Assuming you got in this mess, your device must be rooted and you probably have TWRP recovery, cause Apps2SD work only with rooted devices.
To recover from "Decryption unsuccessful" boot message and restore all data and settings:
Got to TWRP recovery by holding power button and volume UP (after phone vibrates, hold both buttons 2sec more and then release power button, and then after 2sec more release volume up, cause if
you do this too fast, u will end up in wifi recovery by Huawei, and it wont work anyway cause your device rooted).
Then go to advanced and file manager, locate sdcard folder (this will be internal memory, not external), you should be able to see all of your personal files! Copy them to flash drive by connecting with OTG.
What we gonna do now is: do a full nandroid backup: TWRP, backup, check: BOOT, SYSTEM, DATA. and do a backup to flash drive connected with OTG or hard drive if it works for u.
After backup is done, go to WIPE, select format data, select DATA partition and see what original file system it uses. Now format in any other system, then reformat again to your original file system.
DATA partition somehow lost its encryption handshake key and this caused the problem, reformatting fixes it.
Now do a full wipe as if you would install new rom, wipe: system, data, storage, cache, dalvic cache.
Restore your previous nandroid backup, reboot to system,now your phone should boot with all the apps and settings just as you left.
You might be missing some pictures and other media in main storage, just connect your P9 with usb cable to pc, and restore previously backed up media from flash drive manually in pc interface (copy paste, replace all),
some small minority files might wont copy, don't worry about it, Im not sure but they are mostly indexing files, all ur media will be back in place.
Now, how to make Apps2SD work with this configuration?
Don't use that advanced method to find SD cards second partition, use any of first 3, the 3rd one worked for me just fine, cause its SU library based one.
Don't move your apps fully to SD, or they will "disappear", move everything except APK, ODEX, DEX (Lib is optional, you usually can move this one just fine). SO basically app core will stay in main storage but cache and app data will be on second SD card. This way, after you reboot your phone, you will have to wait like 3mins and App2SD will link your files to apps itself just fine. It might will show some errors right after reboot, but after Huawei unlocks its card, files will be linked, and apps wont be "gone" cause app core still stays in main storage.
This way i managed to save a lot of space and move most of app storage to SD card, P9 became very responsive, even in 2018 this is a really fast smartphone.
Sorry for a messy post, I'm not a writer, but I hope this helps to someone!
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
So glad this helped someone
dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919
zgfg said:
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919
Click to expand...
Click to collapse
I'm not entirely sure what caused it, but I suspect Apps2SD just like in the original post (I installed/tried to use it shortly before the problem occured).
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
johnfr92 said:
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
Click to expand...
Click to collapse
Hey...did u get dmsetup to work?