Related
I've been having this problem on and off for a while, mostly I believed it was related to something getting corrupted when I restored my apps to a new Rom with Titanium Backup.
I am happy to say, that after scouring the web for days, and trying a lot of wrong information, I finally figured out how to fix this.
It's real easy. All you need to do is remove any *.apk files located in the /cache directory on your phone (did not even need to remount- though I did it as root just in case).
I never did figure out why only some apps will have this problem or how the problem first comes about, but I have successfully done this twice and have since been able to install/update files that had this error before.
Update (3/3/11): OK - After scouring the Internet for over a month I finally figured it out. My info above was only part right. The problem is specifically with ROMs/Kernels that move the dalvik-cache to the /cache directory (HTC puts it in the /data dir).
In any case, when it's in /data, it is using app space, and therefore you usually run out of app space and know about it. However, because this is in /cache, you don't really know what you are using. As you load up on apps, your dalvik-cache grows, and since these apps need the .dex files in the cache, even if you clear your cache, it will just get re-created.
the /cache dir is also where the apps are temporarily stored while downloading from the market. So....
1. If you are getting immediate download fails, that means that your cache is so full that you don't even have space for the temp file.
2. If you get "Invalid Package" that likely means that there was not enough cache left to install the .dex files (the download is also taking up some of this space).
Unfortunately, the only way to fix this is to either remove some of your apps, or move your cache to your SD card.
HOWEVER, I found this great app on the market called Link2SD, that allows you to only move select apps to the SD card, and you can also move the dalvik-cache files associated with these apps.
see this thread for specifics: http://forum.xda-developers.com/showpost.php?p=10711328&postcount=1
it lets you select which apps to move. You will need to create a new partition on your card, though.
So far results have been great and I can finally update the 30+ apps that have been stuck for me for the last 2 months.
almost forgot, if you adb shell or use terminal emulator, you can type "df" to see how much space is left on all your mounts.
My phone has been doing the same thing with the whole package file is invalid bs. I tried to follow your instructions on going to the /cache folder. When I went to the folder, it was empty, so I wasn't able to remove any .apk files. So now what? How do I fix this?
If you use a File Managemet app like ASTRO, it will show the folder as empty because you need root access to see the dir. However, if you use Terminal Emulator or adb shell (as root) you will see that there are indeed other directories, and probably these orphaned .apk files.
Hi,
I'm also having the same issue with invalid package. I cleared the /cahch direcotry and still have the issue -- Is there something else i can try before wiping and starting over?
thanks
Rudey
It could also be caused by the .android_secure folder on your SD card. Clearing this folder and letting the market restore them solves issues a lot ofthe time.
As always use TiBackup or something to backup all your apps first too to be safe.
As the OP, I can tell you that I have, in fact, been unable to fix this problem.
Initially the suggestion I posted above worked, however a couple of days later is was no longer working again.
I have tried every trick on the web, including:
1. Removing SD card.
2. Deleting the above mentioned folder
3. clearing market cache
4. Clearing all caches in recovery
5. logging out and back in to google talk.
The only thing that fixes it is a complete factory reset.
I currently have a combination of 3 errors:
1. No download at all.
2. Download unsuccessful
3. Invalid Package
some apps will still update, but what is really weird is that I am even getting invalid package on new apps (so its not a corrupt app already installed on the phone).
One last thought. Once I am unable to update an app, even if I remove it, I can no longer restore the backup using Titanium.
oughta try reformating your SD card and let the phone reformat it too.
sgt. slaughter said:
oughta try reformating your SD card and let the phone reformat it too.
Click to expand...
Click to collapse
don't see why this is different than un-mounting the SD which should do the same thing and has been tried.
sw99 said:
don't see why this is different than un-mounting the SD which should do the same thing and has been tried.
Click to expand...
Click to collapse
na actually reformating it will fully wipe everything on the SD and having the phone do it is best always as its always better to format with the device your using the disk on the most in general.
Found the problem, updated in OP.
sw99 said:
I've been having this problem on and off for a while, mostly I believed it was related to something getting corrupted when I restored my apps to a new Rom with Titanium Backup.
I am happy to say, that after scouring the web for days, and trying a lot of wrong information, I finally figured out how to fix this.
It's real easy. All you need to do is remove any *.apk files located in the /cache directory on your phone (did not even need to remount- though I did it as root just in case).
I never did figure out why only some apps will have this problem or how the problem first comes about, but I have successfully done this twice and have since been able to install/update files that had this error before.
Update (3/3/11): OK - After scouring the Internet for over a month I finally figured it out. My info above was only part right. The problem is specifically with ROMs/Kernels that move the dalvik-cache to the /cache directory (HTC puts it in the /data dir).
In any case, when it's in /data, it is using app space, and therefore you usually run out of app space and know about it. However, because this is in /cache, you don't really know what you are using. As you load up on apps, your dalvik-cache grows, and since these apps need the .dex files in the cache, even if you clear your cache, it will just get re-created.
the /cache dir is also where the apps are temporarily stored while downloading from the market. So....
1. If you are getting immediate download fails, that means that your cache is so full that you don't even have space for the temp file.
2. If you get "Invalid Package" that likely means that there was not enough cache left to install the .dex files (the download is also taking up some of this space).
Unfortunately, the only way to fix this is to either remove some of your apps, or move your cache to your SD card.
HOWEVER, I found this great app on the market called Link2SD, that allows you to only move select apps to the SD card, and you can also move the dalvik-cache files associated with these apps.
see this thread for specifics: http://forum.xda-developers.com/showpost.php?p=10711328&postcount=1
it lets you select which apps to move. You will need to create a new partition on your card, though.
So far results have been great and I can finally update the 30+ apps that have been stuck for me for the last 2 months.
almost forgot, if you adb shell or use terminal emulator, you can type "df" to see how much space is left on all your mounts.
Click to expand...
Click to collapse
Didnt solve my issue.. I had reformatted my phone and SD card and reinstalled my apps. It was working fine again but now its back to some apps update fine.. some get DOWNLOAD UNSUCCESSFUL and some get PACKAGE FILE INVALID.. any ideas.. Im on sprint lovers rom (latest)
It appears th LINK 2 SD needs a second partition that I dont have nor use with SPRINT LOVERS ROM and 2.2 .... am I missing something??
To the OP,
The program you linked to seems to be a variation of dark tremor's a2sd method (http://forum.xda-developers.com/showthread.php?t=715116). His lets you move data, cache, and/or dc to the ext partition, but doesn't (at least I don't believe it does) give you granular control over which apps remain in the standard location.
In my own use, I chose to move all user installed apps to sd, but dc remained on the internal memory (albeit, not in /data, but in the /cache partition). I figured this way, even if the sd card is missing, the phone will still boot. I won't have access to anything I installed, but whatever the rom came with will still be accessible.
Follow the instructions on that thread and create the second partition. You won't need more than 500mb. apps2sd or link2sd is the only way you can fix this problem unless you want to remove some of your apps.
Sent from my PC36100 using XDA App
gpz1100 said:
To the OP,
The program you linked to seems to be a variation of dark tremor's a2sd method (http://forum.xda-developers.com/showthread.php?t=715116). His lets you move data, cache, and/or dc to the ext partition, but doesn't (at least I don't believe it does) give you granular control over which apps remain in the standard location.
In my own use, I chose to move all user installed apps to sd, but dc remained on the internal memory (albeit, not in /data, but in the /cache partition). I figured this way, even if the sd card is missing, the phone will still boot. I won't have access to anything I installed, but whatever the rom came with will still be accessible.
Click to expand...
Click to collapse
Yes that's true, and I eventually went the app2sd route. However, I was trying to avoid that because of the slow speed of my sd card.
Sent from my PC36100 using XDA App
sw99 said:
Yes that's true, and I eventually went the app2sd route. However, I was trying to avoid that because of the slow speed of my sd card.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm not sure which app2sd method you're referring to, but keep the following in mind. I discovered this after my backup images failed to restore properly.
In the past, i'd be backing up boot, system, and data partitions. Obviously with dt's a2sd, I need to include the ext partition now. No problem. BUT, when restoring, i'd run into issues where my apps were present, but all settings were lost. After much confusion and head scratching, I tried wiping cache and dc AFTER the restore, but before the initial boot. The restore was a success now!
Apparently, with a2sd on the ext3, some remnants of cache or dc remain when backing up, even if cache is not selected. As part of any good restore, first thing is to always wipe, so now we end up with a hodge podge of files in the cache which I think causes the OS to revert all the settings back to default.
Just something to keep in mind.
i wanted to go back how my dhd was.. lots of problem.. i havent fix my radio problem yet and now this invaled package thing *face palm*
My phone is HTC G7, and I use data2sd to get 1.5G rom space, now there is still about 1.2G left, but I also met the "invalid package file" problem. I can't find any *.apk in /cache, (root, with "ls -a"). But if I uninstall some apps, I could install or update other apps successfully. I could not use Link2sd for I already have data2sd and I guess it's not a problem of insufficient space, because I still have enough rom space.
Do you have any new solutions?
supericexu said:
My phone is HTC G7, and I use data2sd to get 1.5G rom space, now there is still about 1.2G left, but I also met the "invalid package file" problem. I can't find any *.apk in /cache, (root, with "ls -a"). But if I uninstall some apps, I could install or update other apps successfully. I could not use Link2sd for I already have data2sd and I guess it's not a problem of insufficient space, because I still have enough rom space.
Do you have any new solutions?
Click to expand...
Click to collapse
The problem is not the apps, its the /cache running out of space. I suspect that the app you are using cannot move the dalvik-cache files (and is really just a shortcut to android's app2sd - which is not the same as darktremor or link2sd).
in terminal us df -k to see how much space you have on each mount to confirm that there is little space in cache.
If you really have that much space in your apps mount, then I would suggest moving the dalvik-cache back to its original location (search for instructions, as the only way I know how to do it is by installing darktremor's app2sd). If you are still having problems, you really are limited to either partitioning your SD card and using apps2sd or link2sd or removing apps.
hope this helps.
I have been having this issue for a couple of months now - with a bit of a twist. After wiping my dalvik-cache, my apps began to sucsessfully update - except for Google apps.
I have no idea why just those apps, but going into settings/Applications/Manage applications, and selecting each app, then clearing that apps cache, allowed those apps to sucessfully update also.
I am thankful I did not have to resort to the above fix.
Any solution if not rooted?
I've just started to get this error when trying to update the Google+ app. The error is only happening with Google+, every other app I update/install works fine.
I haven't rooted my device, and I'm hoping there's a way to fix the issue without rooting?
Device: Nexus One
Rom: Stock Android
Version: 2.3.4
Although I couldn't see anything in the cache directories, I checked in /system/app and couldn't find any package that looked like it would be Google+.
So, things have massively escalated today and my phone appears to be soft bricked. Joy. I'll run through what happened.
1. I encrypted my phone using the built in tool in Cyanogen Mod. After it rebooted, it was glitchy and I lost a load of apps, the phone really wasn't working well. Rebooted again, but no improvement.
2. I went into TWRP (2.8.x) to restore my old backup, which was on the SD card. After the initial wipe of the internal storage, the log showed
E: Can't mount storage
Click to expand...
Click to collapse
and the restore failed.
3. I reboot and phone goes straight into recovery mode as there is no OS installed (the recovery wipes the internal storage first). Internal Storage is now showing as '0 MB'. I cannot find a way of mounting this storage anymore. Have tried factory reset (doesn't work because file system isn't mounted), and rebooting a few times but no avail.
* There seem to be some options about flashing a .pit file using odin, but I do not have this file. My phone is the Note 4 SM-N910F Model. If I can do this through Odin then maybe this will resurrect the file structure and make this storage mountable?
* There may also be another option using ADB but I still don't know what commands to use.
Any help would really be appreciated as it seems there is some possibility of a fix. That being said my hopes are not that high...
I believe I may have fixed this. I would like to keep this up here in case in helps anyone in the future, I would imagine this is only useful for people who have encrypted their device. I'm not an Android expert so can't be responsible for any damage to devices or data loss etc.
It seems that the encryption must have gone wrong somewhat and this is likely to have impacted on the file system.
Although I couldn't wipe on the device, I was able in recovery to FORMAT data (not just wipe). Go to the wipe menu, then format. After this, reboot into recovery again and you should be able to mount again. It rebuilt the filesystem too.
This should be a quick fix that may help a few people with the issues with not being able to mount the file system. I hope this can help at least one person!
I managed to restore from my backup after and phone is now working. Thanks anyway!
Is there any way to set the default storage of play store apps to the sd card?
I've tried many combinations of partition types and numbers and cannot get Link2SD to accept my second partition. I had similarly bad luck with App2SD. Is there a known good combination of app, card, partition type, size, and number that lets me offload my apps onto the external SD card? I'm using a rooted but otherwise stock GT550T rom for T-Mobile. I have a 200GB Sandisk microSD card. 8GB phone with 4GB taken by default and I couldn't find much to remove. Any other good ideas as to how I can get my apps installed. Even with 0 games I cannot install my usual suite.
i have been experiencing the exact same problem, tried both apps2sd and link2sd, still no luck.. i actually managed to corrupt a brand new card, had to go exchange it. no luck with ext4 or any others... i hope we get some assistance
Yep. What they said.
Same issue. Any fix yet?
I would also like to know a way to get Apps2SD or Link2SD working.
Hey! Androeds 4.1up the link2sd does not work anymore if all of you, does not creates universal odexes for each app in sdext2. The zygote of libs in androed 4.4+ does not permits dalvik cache outside datadir.
The solution is odex all apps one by one, because gogle system apps never recognized and will never recognize odexed apps as third apps.
Is a long war against themselves new dumb zygote for deny odexes in sdext2 :
You need only copy the created odexes inside sdext2 togheter with apk's dir and link mannually, and finnally, delete the relative dex.
The rest is normally linked by link2sd
Apps2sd works for me. I am not rooted though. Let's try to troubleshoot. Go into settings/storage and make sure the sdcard is mounted and formatted. See if your screens match mine.
Apps 2sd is a lie!
Only a Half part of app comes to a dumb system in /mnt/secure and /mnt/asec.
Is a lie!
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
If you root your device, install link2sd (the real sdext linker) your apps will go to sdcard.
On androeds 4.1+ the .dex files need to be PURGED AND PUNCHED OUT DUE TO GOGLE'S SICKNESS NEW DUMB ZYGOTE, and converted to .odex.
I really like the phone itself, i honestly hope someone is able to make a rom for it. Cause out of the box i have basically no storage for apps and the apps 2 sd function in the rom only lets you move a handful of apps.
LINK2SD works on the Samsung Galaxy On5. I moved many apps and have tons of space now.
I don't know how typical my situation is, but I am having the same issue and thought i would attempt to provide a bit more in the way of detail.
My On5 is rooted with TWRP installed and functioning apparently normally. I can run apps that require root without issue, Titanium Backup for example. I have installed SuperSU and BusyBox which seem to behave normally, but Root Checker recognizes root and BusyBox but not SU Access.
When I try to use Link2SD, it doesn't recognize my second partition, and won't create a mount script. I can enter SU through terminal mode, and created /etc/fstab with mounting details for the second partition, but Link2SD still doesn't see it. Consequently, I can use the Move to SD function with some apps, but Link to SD is not functional.
I would contact LINK2SD support and ask them if the app is even capable of handling multiple partitions. My guess is no.
Link2SD not only is capable of handling second partitions, it requires them for the Link to SD function. I followed their instructions carefully for creating an appropriately formatted second partition. The issue seems to be that the phone won't allow it to mount. That is why I posted here.
n5dkj said:
Link2SD not only is capable of handling second partitions, it requires them for the Link to SD function. I followed their instructions carefully for creating an appropriately formatted second partition. The issue seems to be that the phone won't allow it to mount. That is why I posted here.
Click to expand...
Click to collapse
Yes I am sorry, that is why I should post before I have coffee. I see you need an ext4 and a fat formatted... I got it to work. Here are my exact steps..
1. Down root essentials, LINK2SD from app store. Also must be rooted and have TWRP installed. I also suggest a full backup.. Then move the backup to your computer, free space on the phone... Don't leave the backup on the sdcard as it about to be partioned and formatted!!!!!!!!!!!!
2. If you already did this and tried adoptable let storage then use the 'revert changes' and reboot
3. Go into settings a d format sdcard as standard Portable Storage. Click cancel or no if it wants to move anything over.
4. Go into root essentials, storage tab and click adoptable storage
5. Follow procedures to download apk needed (the app will automatically load the web page).. Edit.. When used how much percent of the sdcard to use It's elected 50%.. I am using a 16gb card.. So I split it down the middle.
6. Power down phone
7. Hold down volume up+home+power until logo appears... Essentially go into twrp
8. Do a kernel (system) backup if you haven't yet recently.
9. Flash Apk which will automatically reboot phone
10. Not sure this is important but I waited for my phone to full boot... Paying particular attention to the Toast saying that room essentials has been granted full permissions....
10b... Do not go into storage settings and try to format the second part of the partition... It's already been formatted..
11. Went into LINK2SD, Settings... And pressed 'app location' got a weird warning about hierarchical something or whatnot.. Pressed it a few times and finally got the right screen. SELECTED EXTERNAL.
That was it... Now when I move apps with LINK2SD it seems like a ton of more free space is clearing on the internal... Before when I moved apps I think it was just moving the data..
I got it working temporarily but somehow it started making apps unusable and un-re-installable again. I'll do a factory reset and reroot (I think I just have to sideload SU) and try your step by step this weekend.
The other possibility is the apps that come with the phone are so big they don't fit in the 8gb that comes with it. Every time a Google app gets an update I lose more space and I cannot move those apps to my knowledge. Its getting harder and harder. With this method do I get true adoptable storage? As in all apps and data share the space?
cracker_jax said:
I got it working temporarily but somehow it started making apps unusable and un-re-installable again. I'll do a factory reset and reroot (I think I just have to sideload SU) and try your step by step this weekend.
The other possibility is the apps that come with the phone are so big they don't fit in the 8gb that comes with it. Every time a Google app gets an update I lose more space and I cannot move those apps to my knowledge. Its getting harder and harder. With this method do I get true adoptable storage? As in all apps and data share the space?
Click to expand...
Click to collapse
Most apps are under 100MB.. Even if they download extra data there is no way any one particular app is over 8GB...
Try this...
Sort the LINK2SD app list by 'size internal'
Uninstall the top 3-4 apps that take the most space
Move any system apps you moved to the sdcard back to internal
Clear the app cache and dalvik caches
Reboot
Reformat sdcard
Reboot
Then try my steps to get adoptable storage...
Report back if you can
---------- Post added at 03:22 PM ---------- Previous post was at 03:20 PM ----------
cracker_jax said:
I got it working temporarily but somehow it started making apps unusable and un-re-installable again. I'll do a factory reset and reroot (I think I just have to sideload SU) and try your step by step this weekend.
The other possibility is the apps that come with the phone are so big they don't fit in the 8gb that comes with it. Every time a Google app gets an update I lose more space and I cannot move those apps to my knowledge. Its getting harder and harder. With this method do I get true adoptable storage? As in all apps and data share the space?
Click to expand...
Click to collapse
PS I heard rebooting after you move the apps to SD seems to also fix the problem.
djmcho said:
Most apps are under 100MB.. Even if they download extra data there is no way any one particular app is over 8GB...
Try this...
Sort the LINK2SD app list by 'size internal'
Uninstall the top 3-4 apps that take the most space
Move any system apps you moved to the sdcard back to internal
Clear the app cache and dalvik caches
Reboot
Reformat sdcard
Reboot
Click to expand...
Click to collapse
I did the instructions to get adoptable storage and it appeared to work (adoptable worked anyway) but Link2SD has no functionality with moving anything anywhere. The card is not formatted correctly for Link2SD. The main (SD) partition is receiving apps (migrate to SD built into Android) but very few and the internal storage fills up quickly. Basically the apps that work via App2SD were able to be migrated with the migrate button in Settings > Storage. I'd consider formatting the SD card's second partition so Link2SD could work on it again but I know already that it won't work with the "data" of the apps, even with Link2SD plus. I had limited success with FolderMount but that is a pain and I'm not sure it worked at all. Having data exist in two places seems to confuse my phone. Adoptable storage seems to be dead with most apps refusing to use it and Link2SD seems to be dead as it won't move most of my data without breaking the app.
cracker_jax said:
I did the instructions to get adoptable storage and it appeared to work (adoptable worked anyway) but Link2SD has no functionality with moving anything anywhere. The card is not formatted correctly for Link2SD. The main (SD) partition is receiving apps (migrate to SD built into Android) but very few and the internal storage fills up quickly. Basically the apps that work via App2SD were able to be migrated with the migrate button in Settings > Storage. I'd consider formatting the SD card's second partition so Link2SD could work on it again but I know already that it won't work with the "data" of the apps, even with Link2SD plus. I had limited success with FolderMount but that is a pain and I'm not sure it worked at all. Having data exist in two places seems to confuse my phone. Adoptable storage seems to be dead with most apps refusing to use it and Link2SD seems to be dead as it won't move most of my data without breaking the app.
Click to expand...
Click to collapse
App have to be enabled by the developer to move the data with the app, Dex etc.. For example Waze is... Here is my files list view from links2sd about Waze... As you can see everything Def moved over to the adoptable storage.
cracker_jax said:
I did the instructions to get adoptable storage and it appeared to work (adoptable worked anyway) but Link2SD has no functionality with moving anything anywhere. The card is not formatted correctly for Link2SD. The main (SD) partition is receiving apps (migrate to SD built into Android) but very few and the internal storage fills up quickly. Basically the apps that work via App2SD were able to be migrated with the migrate button in Settings > Storage. I'd consider formatting the SD card's second partition so Link2SD could work on it again but I know already that it won't work with the "data" of the apps, even with Link2SD plus. I had limited success with FolderMount but that is a pain and I'm not sure it worked at all. Having data exist in two places seems to confuse my phone. Adoptable storage seems to be dead with most apps refusing to use it and Link2SD seems to be dead as it won't move most of my data without breaking the app.
Click to expand...
Click to collapse
Continuing...
Where as chrome is not set by the developer to allow moving stuff like data over to SDcard. See attached... You will see some is on the phone and some is onbthe sdcard. If you want to move data over to the sdcard for apps that are not designed to do so you could purchase the pro version of Link2SD that allows for the forcing of data by creating linking. You might be able to do it for free using terminal emulator and the Linux linking command, which escapes me right now..
djmcho said:
Continuing...
Where as chrome is not set by the developer to allow moving stuff like data over to SDcard. See attached... You will see some is on the phone and some is onbthe sdcard. If you want to move data over to the sdcard for apps that are not designed to do so you could purchase the pro version of Link2SD that allows for the forcing of data by creating linking. You might be able to do it for free using terminal emulator and the Linux linking command, which escapes me right now..
Click to expand...
Click to collapse
My problem with the Plus version of Link2SD, which I purchased, is that whenever I liked the data portion (IIRC) the newly moved app would immediately force-quit when opening after that. So I would move the data back. It would still force-quit. So I would uninstall and reinstall. It would still force-quit. Sooooo if and when I used that function it completely broke the app until I did a factory reset.
Now, Link2SD plus has nothing to do with adoptable storage as I was able to move apk and data over simply by getting the correct formatting on my SD card, though I don't remember the correct combination of ext2,3,4 partitions that made it work. What I do remember is after that I would only ruin apps by moving the data. Now, with adoptable storage, Link2SD cannot use the card at all though I haven't tried reformatting the second partition as an ext2,3,4,whatever.
Maybe go back to trying to get support from Link2SD developer?
djmcho said:
That was it... Now when I move apps with LINK2SD it seems like a ton of more free space is clearing on the internal... Before when I moved apps I think it was just moving the data..
Click to expand...
Click to collapse
Excellent!! I just got time to try it, and I now have much more available space. Thanks for your help!
Hi,
I suddenly have a very strange problem. My internal memory changed for some reason to read-only. The built-in file browser can't modify files anymore, nor can any app. With Root explorer (root access) I can still modify files. I could just use Root explorer, but some apps actually crash because they can't access the internal memory, so that's no solution.
Here's the situation:
I have the SM-N9005, on Android Kitkat (4.4.2). I was rooted with CF Auto Root. I wanted to try Magisk (not realising that you needed at least Android 5.0 for it). I uninstalled Busybox, Xposed, and then did a full unroot via the SU app. Then I installed TWRP recovery, tried installing Magisk. Of course that didn't work. So then, with Odin, I reinstalled CF Auto Root. After that I reactivated Busybox and Xposed. TWRP seemed to have disappeared, so installed that again as well. Everything was back to the way it was, except for that internal memory issue.
Does anyone has any idea how to fix this?
I made nandroid backup, so I could just revert to that backup but I'd prefer to find a solution and know why it happened.
Thanks!
After installing and running twrp, did it ask to make changes to internal storage?
audit13 said:
After installing and running twrp, did it ask to make changes to internal storage?
Click to expand...
Click to collapse
It did not. And I've just found out that everything on the SD card can't be opened via the built in file explorer. I can create new folders and such, I just cannot open any files.
I says: "Not able access to external SD card. Try again if SD card is successfully mounted"
It's been a while since I used twrp but I recall being asked if I want to allow modifications to the file system.
Maybe it's time to flash back to stock using Odin and then restore your backup?
audit13 said:
It's been a while since I used twrp but I recall being asked if I want to allow modifications to the file system.
Maybe it's time to flash back to stock using Odin and then restore your backup?
Click to expand...
Click to collapse
Weird, I don't think it asked.
Yeah I guess is if no one comes up with a solution I won't have another choice.
So... Me being used to the older partition layout style on my Galaxy S5, I switched to a new ROM from MIUI (as I wanted to try how it feels like). In all of that. I forgot that I have to back everything up from my internal storage as it will be encrypted (who thought this was a good idea?). It's been 2 days now of me fighting with the phone, TWRP & OrangeFox yet to no avail. I supposedly am decrypting the /data partition as both recoveries accept the password I had set for my lockscreen, yet they still complain that they can't mount /data & that they're unable to mount storage. The issue is, that even though the recoveries are accepting the password, Android itself doesn't... No matter if I try my lockscreen password, my SIM card PIN or even default_password, none of them seem to work. I have an external sdcard in my phone, to which I do get access through MTP in TWRP/OrangeFox yet even after flashing stuff like Dm-Verity_ForceEncrypt etc. the internal storage is still being encrypted & I have no idea what to do. I found a command online that supposedly pulls the files from the internal storage & packs them into a nice .img file in EXT4 format, but when I do that, it seems to gather data for eternity (I have a 128GB phone, but come on, I only had like 35-40GB of data on it) where as for the person that I got the command from, it was just 6GB. When I try to open the .img file, it says that it's corrupted etc. & doesn't let me open it. I am now running out of options & have no idea what to do; I don't want to lose pictures from my phone, as I had some very important ones on there, that I just simply can't lose. Is there any help?
This is what I get in command prompt when I input my password through it:
D:\adb>adb shell twrp decrypt <mypasswordhere>
Attempting to decrypt data partition via command line.
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Unable to mount storage
But as I said, /data & internal storage are still shown as empty
Sithhy™ said:
... Is there any help?...
Click to expand...
Click to collapse
What is wrong with booting up your ROM, connecting to your PC via MTP and copying the files across to your PC?
DarthJabba9 said:
What is wrong with booting up your ROM, connecting to your PC via MTP and copying the files across to your PC?
Click to expand...
Click to collapse
The wrong thing with this method is that I CAN NOT boot into Android to copy over files because it asks me for a password before the lockscreen shows up... When I try to put in my password, it doesn't accept any & gives me a warning that my data will be wiped after I fail to get the right password after a few tries
Welp, I used the command 'adb pull /dev/block/dm-0 ./decrypted-data.img' to pull everything from the phone, but at this phone I don't even know if the file will have anything in it or if it's just empty & I lost all my important pictures for ever... Now I just gotta find a way to mount that image under Linux (or Windows), altough that will be a pain as that's a partition image, not just a regular one :crying:
Sithhy™ said:
The wrong thing with this method is that I CAN NOT boot into Android to copy over files because it asks me for a password before the lockscreen shows up... When I try to put in my password, it doesn't accept any & gives me a warning that my data will be wiped after I fail to get the right password after a few tries
Click to expand...
Click to collapse
Simply upgrading MIUI should not result in anything like this. Millions of people do that, without any trouble. What exactly was the ROM that you had before, and what exactly is the ROM that you replaced it with?
DarthJabba9 said:
Simply upgrading MIUI should not result in anything like this. Millions of people do that, without any trouble. What exactly was the ROM that you had before, and what exactly is the ROM that you replaced it with?
Click to expand...
Click to collapse
I was on Xiaomi.eu's MIUI, wanted to flash Pixel Experience ( https://forum.xda-developers.com/redmi-note-7/development/rom-pixel-experience-t3930709 ) to try it out. After formatting cache, Dalvik, data & system I flashed PE. After it booted up after a few seconds, it showed me the screen to input my password & make emergency calls. I tried putting in 3 different passwords, yet none of them worked. Now, after 2 days of struggling & almost giving up on everything, I managed to pull the data from the internal storage (I hope the file has content in it), wiped everything from my phone & installed PE again...
You should flash again same rom (which you use before flashing new one)
Sithhy™ said:
... After formatting cache, Dalvik, data & system I flashed PE ....
Click to expand...
Click to collapse
If you did format data (instead of just wiping it), then your internal storage is already gone - formatting data also wipes the internal storage. So, did you format data or did you just wipe it?
BTW: if you formatted data, then it would be wholly unusual to be asked for a password to decrypt the phone.
Sithhy™ said:
I was on Xiaomi.eu's MIUI, wanted to flash Pixel Experience ( https://forum.xda-developers.com/redmi-note-7/development/rom-pixel-experience-t3930709 ) to try it out. After formatting cache, Dalvik, data & system I flashed PE. After it booted up after a few seconds, it showed me the screen to input my password & make emergency calls. I tried putting in 3 different passwords, yet none of them worked. Now, after 2 days of struggling & almost giving up on everything, I managed to pull the data from the internal storage (I hope the file has content in it), wiped everything from my phone & installed PE again...
Click to expand...
Click to collapse
From TWRP/Orange Fox
Format Data (type yes)
Reboot recovery
Do a full wipe then install your Rom/Gapps etc
Reboot System.
I know about this method, but it isn't of any help when you want to keep the content on your internal storage
Sithhy™ said:
I know about this method, but it isn't of any help when you want to keep the content on your internal storage
Click to expand...
Click to collapse
I think that unfortunately the only way is to format data. Remember to make always a backup before installling roms. Every time you make a clean flash there is the issue with the password request as a workaround I noticed that if I install magisk just after the rom without rebooting to system the password is not requested
darhma said:
I think that unfortunately the only way is to format data. Remember to make always a backup before installling roms. Every time you make a clean flash there is the issue with the password request as a workaround I noticed that if I install magisk just after the rom without rebooting to system the password is not requested
Click to expand...
Click to collapse
Thanks for the info. That workaround will definitely come in handy sometime in the future... If I'll remember it
Sithhy™ said:
I was on Xiaomi.eu's MIUI, wanted to flash Pixel Experience ( https://forum.xda-developers.com/redmi-note-7/development/rom-pixel-experience-t3930709 ) to try it out. After formatting cache, Dalvik, data & system I flashed PE. After it booted up after a few seconds, it showed me the screen to input my password & make emergency calls. I tried putting in 3 different passwords, yet none of them worked. Now, after 2 days of struggling & almost giving up on everything, I managed to pull the data from the internal storage (I hope the file has content in it), wiped everything from my phone & installed PE again...
Click to expand...
Click to collapse
I had the same problem with that password until i discovery this:
https://en.miui.com/thread-324522-1-1.html
zpower said:
I had the same problem with that password until i discovery this:
https://en.miui.com/thread-324522-1-1.html
Click to expand...
Click to collapse
Thanks for the post, but that thread wasn't of any help either, as Android wasn't accepting any password that I put in for some reason
Sithhy™ said:
Thanks for the post, but that thread wasn't of any help either, as Android wasn't accepting any password that I put in for some reason
Click to expand...
Click to collapse
But you understand the concept of using the numeric keypad to mark pattern unlock coordinates?