ok suddenly today my phone just rebooted while using a camcorder app called ancorder. but after reboot, it kept saying that it was checking sd card for errors. my sd card was unaccessible except for my second partition (where all my apps are stored via link2sd). then i just uninstalled the camcorder app and all the folders associated with it. after that i rebooted the phone a couple of times to see if the sd card error would go away but instead it got worse. now after rebooting, and after entering my pattern for pattern lock, it kepps saying launcher pro force close. it keeps on force closing again and again. what do i do to save my phone? Any help would be deeply appreciated.
(I own a milestone xt720 that is rooted and apps are stored via link2sd in sd card second partition. i am using stock 2.1.)
androidlover123 said:
ok suddenly today my phone just rebooted while using a camcorder app called ancorder. but after reboot, it kept saying that it was checking sd card for errors. my sd card was unaccessible except for my second partition (where all my apps are stored via link2sd). then i just uninstalled the camcorder app and all the folders associated with it. after that i rebooted the phone a couple of times to see if the sd card error would go away but instead it got worse. now after rebooting, and after entering my pattern for pattern lock, it kepps saying launcher pro force close. it keeps on force closing again and again. what do i do to save my phone? Any help would be deeply appreciated.
(I own a milestone xt720 that is rooted and apps are stored via link2sd in sd card second partition. i am using stock 2.1.)
Click to expand...
Click to collapse
I think this has happened to many of us.
Remove the SD card and put it directly into a computer to do filesystem repair. (If you aren't able to put it directly into a computer, second best is USB mode from OpenRecovery followed by whatever your computer's safely remove/eject proceedure is and an immediate phone reboot or battery pull when you're done just to be safe). If that fails, copy what you can and reformat the FAT partition. Basically the phone's FAT filesystem repair doesn't seem to be sophisticated enough to handle some types of corruption that seem to happen.
Some people will say it's not necessary to use the safely remove/eject procedure when using USB access because FAT is designed for unsafe removal, but my experience says otherwise. I've started to safely remove religiously (since late Feb-ish) and I've gone from nearly weekly corruption to only once when I forgot to do that. In any case using safely remove won't do any harm.
Another thing to know about the ext partition--the phone does not unmount /sd-ext when it is exported over USB (that's why widgets and such can be stored there safely but not on the main FAT partition). This may also be true in OpenRecovery (it's mounted as /sddata there). When it's exported over USB, the ext partition becomes a live filesystem managed by both your phone and your computer and neither seems to understand that the other can be changing the filesystem simultaneously. Probably if you're using Windows or MacOS this isn't a problem (unless you're modifying partitions or reformatting) because they're don't know what to do with ext partitions (by default that is). On the other hand, linux systems may automount it (I know Ubuntu does). This can lead to corruption and data loss on the ext partition if you monkey with the ext partition over USB mode (i.e. repartitioning etc).
THX a lot for the advice! it really helped me a lot!! ur advice has helped me fix my sd card problem!! but unfortunately now how do i get out of the launcher pro force close loop?? by spamming the keys i managed to get to the notifications bar and from there with more spamming i managed to get to aadvanced task manager but i cant kill any open apps from there. Is that of any use?? i have attached some images of my phone's constant force closing.
androidlover123 said:
THX a lot for the advice! it really helped me a lot!! ur advice has helped me fix my sd card problem!! but unfortunately now how do i get out of the launcher pro force close loop?? by spamming the keys i managed to get to the notifications bar and from there with more spamming i managed to get to aadvanced task manager but i cant kill any open apps from there. Is that of any use?? i have attached some images of my phone's constant force closing.
Click to expand...
Click to collapse
I'm not sure. Have you tried disabling Advanced Task Killer?
I think the worst case solution is factory reset, but you'll lose your data and configurations. It looks like you have OpenRecovery installed so you could try backing up System, Data, Cache, and SD Data using nandroid and then try a factory reset to test.
Boot into OpenRecovery, wipe Dalvik-cache & cache partition, rebbot, it's worth a shot.
3rdstring said:
Boot into OpenRecovery, wipe Dalvik-cache & cache partition, rebbot, it's worth a shot.
Click to expand...
Click to collapse
Is there anyother way?? Im not so sure what these operations actually do to my phone although i do have openrecovery installed on my phone.would you care to explain? i can just go to the openrecovery app and go into recovery from there right?
THX for the advice anyways!!
androidlover123 said:
Is there anyother way?? Im not so sure what these operations actually do to my phone although i do have openrecovery installed on my phone.would you care to explain? i can just go to the openrecovery app and go into recovery from there right?
THX for the advice anyways!!
Click to expand...
Click to collapse
This will just clear out some temporary files & the phone will rebuild the dalvik-cache on reboot (which will take a little longer).
3rdstring said:
This will just clear out some temporary files & the phone will rebuild the dalvik-cache on reboot (which will take a little longer).
Click to expand...
Click to collapse
Ok i finally wiped my dalvik cache and cache partition but when rebooted it was still the same D:. the launcher pro was in a continuous force close loop...... Any help to solve this major problem would be greatly apprecited!!!
androidlover123 said:
Ok i finally wiped my dalvik cache and cache partition but when rebooted it was still the same D:. the launcher pro was in a continuous force close loop...... Any help to solve this major problem would be greatly apprecited!!!
Click to expand...
Click to collapse
First make nandroids of system and data. Then upgrade your OpenRecovery to Androidiani OpenRecovery (basically update files on your sd card). In Androidiani OpenRecovery try to use the Application Management Menu to uninstall Launcher Pro. Hopefully you will be able to get the stock launcher after a reboot then. If so, delete all of Launcher Pro's data from the /data partition and then reinstall Launcher Pro from the market.
If you don't mind losing all your preferences and reinstalling your apps, it may just be faster to jump directly to "Wipe Data / Factory Reset" in Open Recovery. If that doesn't work it means your /system partition is corrupted.
Mioze7Ae said:
First make nandroids of system and data. Then upgrade your OpenRecovery to Androidiani OpenRecovery (basically update files on your sd card). In Androidiani OpenRecovery try to use the Application Management Menu to uninstall Launcher Pro. Hopefully you will be able to get the stock launcher after a reboot then. If so, delete all of Launcher Pro's data from the /data partition and then reinstall Launcher Pro from the market.
If you don't mind losing all your preferences and reinstalling your apps, it may just be faster to jump directly to "Wipe Data / Factory Reset" in Open Recovery. If that doesn't work it means your /system partition is corrupted.
Click to expand...
Click to collapse
Thanks a lot for the advice!! Is this the link on how to install Androidiani to xt720?? http://forum.xda-developers.com/showthread.php?t=1011882
How will i be able to access androidiani openrecovery?? Thanks a lot for ur help!!
androidlover123 said:
Thanks a lot for the advice!! Is this the link on how to install Androidiani to xt720?? http://forum.xda-developers.com/showthread.php?t=1011882
How will i be able to access androidiani openrecovery?? Thanks a lot for ur help!!
Click to expand...
Click to collapse
Short form:
Download OpenRecovery-3_3.zip from here http://code.google.com/p/androidiani-openrecovery/
Rename /sdcard/OpenRecovery directory to /sdcard/OpenRecovery.bak (directory only, leave /sdcard/OpenRecovery.zip alone it should stay the same as before you started anything)
Extract OpenRecovery-3_3.zip into /sdcard (will create a new /sdcard/OpenRecovery folder and add /sdcard/update.zip)
Copy contents of /sdcard/OpenRecovery.bak/updates into new /sdcard/OpenRecovery/updates (Optional)
Reboot into OpenRecovery (same methods as before)
That's all folks!
Just a word of warning: Androidiani is very Milestone A853 centric. I wouldn't touch any of their baseband utilities with a 10-foot pole.
Mioze7Ae said:
Short form:
Download OpenRecovery-3_3.zip from here http://code.google.com/p/androidiani-openrecovery/
Rename /sdcard/OpenRecovery directory to /sdcard/OpenRecovery.bak (directory only, leave /sdcard/OpenRecovery.zip alone it should stay the same as before you started anything)
Extract OpenRecovery-3_3.zip into /sdcard (will create a new /sdcard/OpenRecovery folder and add /sdcard/update.zip)
Copy contents of /sdcard/OpenRecovery.bak/updates into new /sdcard/OpenRecovery/updates (Optional)
Reboot into OpenRecovery (same methods as before)
That's all folks!
Just a word of warning: Androidiani is very Milestone A853 centric. I wouldn't touch any of their baseband utilities with a 10-foot pole.
Click to expand...
Click to collapse
I'd just llike to ask: is it possible to uninstall the launcher via adb?
Mioze7Ae said:
Short form:
Download OpenRecovery-3_3.zip from here http://code.google.com/p/androidiani-openrecovery/
Rename /sdcard/OpenRecovery directory to /sdcard/OpenRecovery.bak (directory only, leave /sdcard/OpenRecovery.zip alone it should stay the same as before you started anything)
Extract OpenRecovery-3_3.zip into /sdcard (will create a new /sdcard/OpenRecovery folder and add /sdcard/update.zip)
Copy contents of /sdcard/OpenRecovery.bak/updates into new /sdcard/OpenRecovery/updates (Optional)
Reboot into OpenRecovery (same methods as before)
That's all folks!
Just a word of warning: Androidiani is very Milestone A853 centric. I wouldn't touch any of their baseband utilities with a 10-foot pole.
Click to expand...
Click to collapse
I managed to uninstall launcher pro by switching to the voice dialler in advanced task manager. from there, i said to the device "settings" and it brought me to the settings!!! from there i just uninstalled the launcherpro app. THX a lot for ur help and time, Mioze7Ae!!!
Related
So ive been trying to get apps2sd and i have succesfully done it by using apps2sd2 from the market to partition my card and then i followed the steps by Mailman below and it worked..all my apps were in the sd etc with 73 MB free...but when i click on market...it gives me an option that there is no connection when in fact i do and 2 seconds after it showa the force close message.. anyone have any idea how to fix this?
I had the same issue, had to do a full data wipe to fix it.
well seems that a full data wipe fixes it, but then when i input the commands in the terminal emulator
lucid app
lucid data
lucid dalvik
so i can get everything to the sd card it starts doing the same thing again..any ideas what is causing it?
I'm unfamiliar with the method you're using to get your apps on your SD card - mine are running on the SD card also, but I used the good ol' symlink method to do so...
It would appear your marketplace can't access your apps, or, is being locked out of something - perhaps a permissions issue on your sd partition? I had that issue when I first set up mine. All the apps were copied over with the same user/group and the market place freaked out.
The only way I was able to fix it was to copy all my apps off the sd partition to my computer, do a full datawipe, nuke all my apps, and reinstall them.
I set up a shell script that took the contents of ~/apps/*.apk and sent each to adb install, on its own line, and automated the whole thing. Took about 3 minutes to reinstall my 80 or so apps, and it restored all the app permissions to what they were supposed to - market didn't have a problem afterwards.
futango said:
I have found my problem. This works great. I can't have data on my SD or it will be really sluggish. I redid the flash and the commands, but left out "lucid data" and the phone has 72MB free and feels fast again.
Click to expand...
Click to collapse
Don't move the data and everything should work fine.
i see what your saying. ill have to try that out, but now it seems that after i wiped my data and pressed home+back to reboot my phone it is stuck at the T mobile G1 screen and doesnt want to do anything at all anymore...it just got worse.any way to fix this? ove tried wiping again and i formatted my dscard so no update to reinstall..what should i do?
just wait... when you wipe under the new builds, it may take 10mins to boot for the first time.
also I don't know how it is possible to do app2sd with terminal emulator. when you rm dalvik-cache or app that program should crash before the shell script or command finish
I had this happen as well.. more than once.
And each time it was a result of moving the "data" over to the SD card.
I finally learned my lesson... and my phone is now solid.
Hi,
My experience on 5.02 h is that the data move does not work correctly also.
I have moved the :
apps
apps-private
davik-cache
without any problems.
85 apps installed and 61 megs free with this method.
Browser and market cache cleared 1st.
I found this to be an issue only when I had tried to make my EXT2 partition too big (Over 2GB). Exact same error, moving data to the SD, Market crash. The problem was tied to moving the data though.
I had the same problem. It apeard after I installed TA utility.
The problem is that Market is looking for it's cache directory and can't find it. In my case it's looking for it on the SDcard and I have to make the directory myself: /sdcard/cache/market.
If you have not attempted to move the Market cache to SD you might want to see if you have a /cache/market in your internal memory, and if not create it.
It should solve your problem. (worked for me)
im having the same problem too.. the Application section doesn't work for me, but im able to still go into the Game section. i tried adding a cache folder to the SD still doesnt work
Hi Everyone,
I recently just flashed my stock Rogers 2.2 phone with Serendipity 5.12 and noticed something odd. None of my files in in /mnt/sdcard or on my external SD Card were deleted. I followed these steps:
Rooted
Backed up with Titanium backup
Transferred my .zip file to the root of my phone (I don't know I did it at this step as it should have been erased....)
Flashed back to stock AT&T JH6 using ODIN3 (as my phone is a 1010 build)
Master reset (said completed successfully)
Rooted again (messed up on this as I said my phone was below 2.0 firmware, had to re-root again [without derooting] saying my phone was above 2.0 firmware)
Installed Rom Manager and booted into Clockwork Recovery Mode
Selected my .zip from my sdcard (I did this manually vs renaming it update.zip)
It booted up into Serendipity fine and and I said yes to the lag fix conversion
Then I went back to re-install apps I noticed Titanium Backup was showing me my old backup which I transferred onto my external SD. Then I used "My Files" to see that I had my previous Dropbox, Kongregate, roms, and all my other old folders from stock on the /mnt/sdcard still! I thought these would have been erased surely with the Flash and Master Clear. Now I am curious how "pure" my flash" is, and that maybe I should try this all again. Anyone experience this before and can let me know why this happened? Or let me know that this is normal?
Thanks!
none of the files should be deleted unless you did a master clear....
Ah, well I did very strange! Anyone have any advice on what I should do next? Retry the whole process, or do a master clear from serendipity?
I don't understand what the problem is. What do you mean how "pure" your flash is? Are you worried that you have a mix of two roms loaded at the same time or something?
If that's the case, I assure you that you don't. The actual partitions that hold the OS are formatted before the new firmware is installed, including your data partition. The internal and external sd cards are never formatted because they have absolutely nothing to do with the firmware.
Oh well I guess by "pure" I meant that some of the old files (installers, folders left by programs) may affect the stability and speed on the new ROM. However, you are right the files used by the OS are on the root of the SD card (i.e. / ). I guess I'll leave it for now... Very strange that master clear didn't wipe out everything!
EDIT: Great now my SIM card is not being recognized although it was recognized upon first boot of the phone...
NightTickler said:
Oh well I guess by "pure" I meant that some of the old files (installers, folders left by programs) may affect the stability and speed on the new ROM. However, you are right the files used by the OS are on the root of the SD card (i.e. / ). I guess I'll leave it for now... Very strange that master clear didn't wipe out everything!
EDIT: Great now my SIM card is not being recognized although it was recognized upon first boot of the phone...
Click to expand...
Click to collapse
So much for alleged purity. Leave the CWM update on the sdcard as update.zip and simply copy the ROM zip to your sdcard and install it. All that flashing to stock, master clearing and renaming is silly.
As to why the master clear didn't work, did you do it with the phone fully booted up, debugging on and touchwiz running?
opcow said:
So much for alleged purity. Leave the CWM update on the sdcard as update.zip and simply copy the ROM zip to your sdcard and install it. All that flashing to stock, master clearing and renaming is silly.
As to why the master clear didn't work, did you do it with the phone fully booted up, debugging on and touchwiz running?
Click to expand...
Click to collapse
Oh so that is what that update.zip on my sdcard was, CWM. I deleted it... oops! I should just be able to install ROM Manager again and get that update.zip back right?
As for the master clear. I was fully booted, debugging was on, but I don't know if I had Zeam or Touchwiz running... Probably Zeam I guess! Makes sense thanks!
Easy Clockworkmod Recovery
NightTickler said:
Oh so that is what that update.zip on my sdcard was, CWM. I deleted it... oops! I should just be able to install ROM Manager again and get that update.zip back right?
As for the master clear. I was fully booted, debugging was on, but I don't know if I had Zeam or Touchwiz running... Probably Zeam I guess! Makes sense thanks!
Click to expand...
Click to collapse
Instead of installing Rom Manager, just add this to the root of your sdcard. This is the update.zip that Rom Manager puts on your phone. Hope this helps.
modest_mandroid said:
The actual partitions that hold the OS are formatted before the new firmware is installed, including your data partition.
Click to expand...
Click to collapse
Code:
format SYSTEM:
format CACHE:
format DATADATA:
format DATA:
delete_recursive SDCARD:.android_secure
delete_recursive SDCARD:Voodoo
delete_recursive SDCARD:Android
delete_recursive DBDATA:
format CACHE:
format DATADATA:
delete_recursive DBDATA:
I think that's sufficient.
I did this my first flash and didnt realize that the files were still there until I was about to reflash a new ROM on it.
You have to master clear the phone; if you use that awesome program that flashes you back (forgot the name) it has an option to do this for you.
FLAC Vest said:
I did this my first flash and didnt realize that the files were still there until I was about to reflash a new ROM on it.
You have to master clear the phone; if you use that awesome program that flashes you back (forgot the name) it has an option to do this for you.
Click to expand...
Click to collapse
I think you're talking about Odin one-click that flashes your firmware back to I897UCJF6 and clears your phone. You can find it on the XDA forums here: http://forum.xda-developers.com/showthread.php?t=731989
MikeyMike01 said:
Code:
format SYSTEM:
format CACHE:
format DATADATA:
format DATA:
delete_recursive SDCARD:.android_secure
delete_recursive SDCARD:Voodoo
delete_recursive SDCARD:Android
delete_recursive DBDATA:
format CACHE:
format DATADATA:
delete_recursive DBDATA:
I think that's sufficient.
Click to expand...
Click to collapse
Yeah, I just tried to distill it into words that someone new to rom flashing could digest. Speaking of that though, any clue why the Galaxy S line stores databases in /dbdata whereas just about every other Android phone uses /data/data/ ?
adm226 said:
I think you're talking about Odin one-click that flashes your firmware back to I897UCJF6 and clears your phone. You can find it on the XDA forums here: http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
That's exactly what I was talking about, thanks for the clarification. I have all of the files to root and restore in a folder on my comp; so easy once you get the hang of it.
Sent from my Nexus One using XDA Premium App
Hey, so I've been on Dexter's 2.2 for a few weeks now and love it, but the oddest thing happened last night. The phone locked up so I had to do a battery pull (this isn't an unusual occurrence), but when it restarted, most of my apps were gone- including my launcher, my keyboard, my widget apps... A few are still there, in addition to the ones that came with the phone, but most have apparently vanished.
Yet when I look at the internal memory, it hasn't changed- there's still around 65MB left, which is the amount I had before this happened.
Any idea what happened, and if I can get it back to normal? I know how to start from scratch using OpenRecovery, I just wanted to see if you guys could think of a way to salvage things before I went to all that trouble.
Thanks in advance!
Do you have a 2nd partition on your sdcard for apps2ext or link2sd?
I think what 3rdstring is suggesting is correct--your ext partition became dirty when you pulled the battery in ways that the automatic fsck on the phone can't fix. In this case, the phone won't mount it at boot to avoid causing further data corruption. You probably need to take your sd card out and use a linux desktop/laptop to run fsck.
I think Androidiani OR has a menu option to manually run fsck on the ext partition, so you could also try that.
If you don't care about risking losing the files, you can try to nandroid backup/restore of the SD Data partition. OpenRecovery isn't as picky about mounting sd-ext. A nandroid backup&restore of SD Data will create a tar (possibly containing corrupted files), reformat /sd-ext as a fresh ext2, and then extract the tar (with possibly corrupted files).
I do have an ext partition, but I didn't think I was using it- I didn't create any directories on it to start using apps2ext or move the dalvik cache there or anything- I just had it in case I wanted to do these things in the future.
It makes sense that it's probably related to this, though. I'll give fsck a try and let you know what happens.
Thanks!
bjlange said:
I do have an ext partition, but I didn't think I was using it- I didn't create any directories on it to start using apps2ext or move the dalvik cache there or anything- I just had it in case I wanted to do these things in the future.
It makes sense that it's probably related to this, though. I'll give fsck a try and let you know what happens.
Thanks!
Click to expand...
Click to collapse
If you ever booted Dexter's ROM without bugfix v2 or later, it would have created /sd-ext/app for you. This is automatic in Dexter's ROM.
Before posting this, I tried looking at other forum threads and over the internet in the last week, but could not find a solution so far.
I have a Huawei Y300 with Android 4.1.1. It was rooted and was pretty much fine except for some issues (they happened in time, are not caused by the rooting itself). Meanwhile, I changed the SD card and the defects include:
- cannot set contact photos (it stops when it tries to crop image)
- cannot change theme (it shows it empty and says "internal storage full" - which is not true, plenty of free space shows up in app manager)
- can't use file manager - doesn't see anything from Local
- without a card in it, gallery and camera don't work at all
I did a factory reset and cleaned the davlik folder, but didn't change anything.
The problems come, I think, because Link2SD creates symbolic links to some folders, and those folders are not the same in a new card. For instance, when I use Root Browser and click Properties on some folders, I get:
Path: /sdcard
Symlink:/storage/sdcard0
But, when I use phone's File Manager, it does not see the files from "storage0", it shows only files located in "storage/sdcard1"
I tried to do a system update, by putting a firmware zip (or app) on the card. But it does not see it there, because it sees what the symlink tells it to see. So I'm stuck in a loop.
Because it was impossible to make Link2SD see the new card, I used another phone, with Android 4.4. After endless attempts, I got that phone to see the two partitions on the card and function. (I had to make Link2SD system app and chose ext4 for second partition.)
I took the card back to the problem phone and only sees the first partition, not the ext4 one.
In Link2SD storage info it shows:
Internal (69% free)
SD Card (unmounted)
External SD (93% free)
Second Partition (not found)
System (33% free)
Cache
When I click Recreate mounting script - it says sd card not found.
Relink files: /data/sdtext2 not found
I basically would like to get the folder structure back to the original settings, maybe use the phone without card or with a new card, with or without rooting - just the simplest way possible, but to be able to use photos for contacts and wallpapers.
update
After numerous attempts, I managed to get into recovery mode from Link2SD (the same ) and started firmware update.
It lists doing some operations, but very soon it says wiping cache... and installation aborted.
Should I try with a different ROM? This one is from Huawei website, official, general version.
it's done!
Not that anyone answered, but in case you have the same problem: it's fixed!
Again with Link2SD. Made a third partition on the card, than in Link2sd click the left upper corner for more options. Scroll down for Restart. It gives options for recovery. Deleted everything with the two options to wipe cache and I don't know what else. And than chose restart from volume keys and upper button as enter.
It didn't do an upgrade, rather a downgrade to a previous factory version but i'm happy with it.
Won't risk another rom change.
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).