Related
I accidentally hit the FACTORY RESET option in HBOOT, and it seems the phone just rebooted into TWRP without doing anything. However it seems my SDcard is now empty and unformatted. Earlier I had two "Internal SDcard" options in TWRP\Mount but now I just have one, and if I try to click on Mount USB storage, the removable disk appears as an unformatted disk on my PC. Is there any to fix this? Is the SD gone for good or can I recover the data?
Run a Ruu and your phone should be fine again (dont forget to relock your bootloader)
I think your data you wiped is hopelessy gone..
Sent from my HTC One S using xda premium
I made a nandroid luckily, but I just realised that the problem is due to the sdcard not actually being able to mount. It says
E:unable to mount '/sdcard'
I'm using TWRP 2.5, maybe I will try with 2.3.1.0.
EDIT: Okay that didn't help. If I run a RUU won't it erase my SD card? I don't want to lose what's on there, is there any way to fix it and be able to mount it again?
Bottom line: I need the data on my SD... is there any way to recover it?
djsubtronic said:
Bottom line: I need the data on my SD... is there any way to recover it?
Click to expand...
Click to collapse
No its gone sorry and no need for ruu just flash stock recovery and factory reset again.
Ten years of data just destroyed within the blink of an eye.
FML.
reformat the sd card and use recovery tools (google for them). most of your stuff will be easily brought back from the dead.
speedfreak007 said:
reformat the sd card and use recovery tools (google for them). most of your stuff will be easily brought back from the dead.
Click to expand...
Click to collapse
I did. It seems everything on the card was nuked. I tried about ten different recommended apps, none of them could find a single file even with deep searches.
djsubtronic said:
Ten years of data just destroyed within the blink of an eye.
FML.
Click to expand...
Click to collapse
I'm sorry for your loss. Now, not to be a douche, but 10 years? Have you traveled through time with your One S?
Fruktsallad said:
I'm sorry for your loss. Now, not to be a douche, but 10 years? Have you traveled through time with your One S?
Click to expand...
Click to collapse
It easily could have been downloaded data. I'm really sorry to hear about your loss, but always keep a copy of your SD card on your PC, no matter what.
djsubtronic said:
I accidentally hit the FACTORY RESET option in HBOOT, and it seems the phone just rebooted into TWRP without doing anything. However it seems my SDcard is now empty and unformatted. Earlier I had two "Internal SDcard" options in TWRP\Mount but now I just have one, and if I try to click on Mount USB storage, the removable disk appears as an unformatted disk on my PC. Is there any to fix this? Is the SD gone for good or can I recover the data?
Click to expand...
Click to collapse
before going through the trouble of an RUU, if you can see the unformatted disk from your computer just try formatting it there into a FAT32 partition like you would any other drive. This has worked for folks successfully. But as for data recovery....
Dang that sucks... was there some sort of confirmation before starting the wipe? I've always been paranoid that I might fat finger it randomly and it just wipes without some kind of second check
Reflash the recovery img from fastboot then boot into recovery, you should be able to mount sd
Zero help to anyone, but I did exactly the same thing myself and had to mount the SD card in recovery and format.
It hurts!!
Well it's official. All my data is forever gone. And no there was no notification, I hit "FACTORY RESET", and it just paused for a second then rebooted into TWRP with my SD instantly destroyed. I tried every possible trick in the book. The problem for me wasn't just getting it to mount and work again, I could have done that in 20 seconds. The problem was to try and get it back WITH all my data, which I failed.
In the end, I made a RAW disk image backup of the sd card partition which for some bizarre reason ended up with a file that was 6 MB in size instead of 10 GB... I knew my data had somehow got nuked. I decided to just reformat it (Quick Format) as FAT32 on the PC, then I ran a host of data recovery programs, even those that were specialised in finding stuff from formatted drives. None of them could even find ONE file. But after format I was able to use it as normal.
I have really no clue how the entire drive was nuked within a fraction of a second, even all the data on it, but it is what it is.
On the bright side, for some reason my phone seems MUCH faster now, especially when installing apps, and the battery seems to last noticeably longer too.
djsubtronic said:
Well it's official. All my data is forever gone. And no there was no notification, I hit "FACTORY RESET", and it just paused for a second then rebooted into TWRP with my SD instantly destroyed. I tried every possible trick in the book. The problem for me wasn't just getting it to mount and work again, I could have done that in 20 seconds. The problem was to try and get it back WITH all my data, which I failed.
In the end, I made a RAW disk image backup of the sd card partition which for some bizarre reason ended up with a file that was 6 MB in size instead of 10 GB... I knew my data had somehow got nuked. I decided to just reformat it (Quick Format) as FAT32 on the PC, then I ran a host of data recovery programs, even those that were specialised in finding stuff from formatted drives. None of them could even find ONE file. But after format I was able to use it as normal.
I have really no clue how the entire drive was nuked within a fraction of a second, even all the data on it, but it is what it is.
On the bright side, for some reason my phone seems MUCH faster now, especially when installing apps, and the battery seems to last noticeably longer too.
Click to expand...
Click to collapse
Hmm. Maybe I should do it too lol.
You should automatically upload your photos or files somewhere. Mine upload to Dropbox so if anything bad happens, nothing too bad can go wrong.
djsubtronic said:
In the end, I made a RAW disk image backup of the sd card partition which for some bizarre reason ended up with a file that was 6 MB in size instead of 10 GB... I knew my data had somehow got nuked. I decided to just reformat it (Quick Format) as FAT32 on the PC, then I ran a host of data recovery programs, even those that were specialised in finding stuff from formatted drives. None of them could even find ONE file. But after format I was able to use it as normal.
Click to expand...
Click to collapse
It's hard to do recover because normal format recovery might not work but you can try the old ver of Easy Recovery Pro 6.x(I don't know why but the lastest ver seems removed RAW recovery) and use the RAW recovery, it usually could find some stuffs. You can also try out Diskgenius.
My wife's Galaxy S3 suddenly decided it didn't want to boot past the Galaxy SIII logo (which includes the blue Cyanogen mascot at the bottom)
I was going to attempt to re-flash Cyanogenmod 10.2, but for some reason TWRP prompted me for a password upon going into recovery. Hitting Cancel here allows me into TWRP. I flashed the latest version on TWRP, and still I am prompted by that password.
I then found that I was unable to wipe Dalvik Cache, and then found that I'm unable to mount /data.
Well that's not good. I assume that I'll have to use Odin to go back to stock and re-partition? Any suggestions would be appreciated.
Sounds like your /data is encrypted. When you're prompted for a password, that's to decrypt the /data partition (it's probably the PIN she uses to unlock the phone). Hitting cancel simply leaves /data unencrypted and unmounted. If you hit mount within TWRP, you'll probably see a "Decrypt Data" button. Try using the PIN and see if that works.
Joe
erc. said:
My wife's Galaxy S3 suddenly decided it didn't want to boot past the Galaxy SIII logo (which includes the blue Cyanogen mascot at the bottom)
I was going to attempt to re-flash Cyanogenmod 10.2, but for some reason TWRP prompted me for a password upon going into recovery. Hitting Cancel here allows me into TWRP. I flashed the latest version on TWRP, and still I am prompted by that password.
I then found that I was unable to wipe Dalvik Cache, and then found that I'm unable to mount /data.
Well that's not good. I assume that I'll have to use Odin to go back to stock and re-partition? Any suggestions would be appreciated.
Click to expand...
Click to collapse
joeinternet said:
Sounds like your /data is encrypted. When you're prompted for a password, that's to decrypt the /data partition (it's probably the PIN she uses to unlock the phone). Hitting cancel simply leaves /data unencrypted and unmounted. If you hit mount within TWRP, you'll probably see a "Decrypt Data" button. Try using the PIN and see if that works.
Joe
Click to expand...
Click to collapse
Yes, I think you're right about the encryption. How does /data become encrypted? She doesn't recall encrypting it through settings, of course. Her usual pin doesn't work to allow access either. If I can't figure out the password to decrypt /data, what's next?
Within CM, the ability to encrypt /data is selected within settings. It will ask you to set a pin or passphrase, have more than 80% battery and will reset to encrypt (you'll see a green wireframe android icon and an encryption progress meter). This is all a conscious decision, so someone must have gone in there to set it, if that's the reason why it's asking for a password. You can set a different password for encryption, but you would have to do this from the command line, which doesn't sound likely here.
If encryption was interrupted, it's possible the drive isn't encrypted, but TWRP thinks it is (the key data is stored at the end of the partition). I'm paraphrasing, but if that bit is set, it will always think the partition is encrypted. The only way to wipe that is to completely wipe the /data partition, which you probably don't want to do unless you've got good backups (and nandroid will not backup /data/media, so be careful with that option).
Do you know if the phone had adb debugging enabled? You could try running logcat while it boots to see what the issue is. I had something similar happen to mine (hanging at the CM icon at boot) when I upped from the October CM10.2 nightlies to the M1 release and ended up using ODIN to return to stock - it's a good thing I had backups!
You can get a shell while in recovery to poke around. You can try mounting from the command line there (the /data partition will be listed in the /etc/recovery.fstab file).
If all else fails, and you have good backups, you could try wiping /data from within TWRP, but keep in mind that all pictures, texts, music, etc will go with it! I would only do this as a last, last resort.
I've seen several threads lately about issues with the partition layout in recent flashing (esp. with the MF1 update). I've reverted back to stock as a precaution, myself.
Joe
erc. said:
Yes, I think you're right about the encryption. How does /data become encrypted? Her usual pin doesn't work. If I can't figure out the password to decrypt /data, what's next?
Click to expand...
Click to collapse
joeinternet said:
Within CM, the ability to encrypt /data is selected within settings. It will ask you to set a pin or passphrase, have more than 80% battery and will reset to encrypt (you'll see a green wireframe android icon and an encryption progress meter). This is all a conscious decision, so someone must have gone in there to set it, if that's the reason why it's asking for a password. You can set a different password for encryption, but you would have to do this from the command line, which doesn't sound likely here.
If encryption was interrupted, it's possible the drive isn't encrypted, but TWRP thinks it is (the key data is stored at the end of the partition). I'm paraphrasing, but if that bit is set, it will always think the partition is encrypted. The only way to wipe that is to completely wipe the /data partition, which you probably don't want to do unless you've got good backups (and nandroid will not backup /data/media, so be careful with that option).
Do you know if the phone had adb debugging enabled? You could try running logcat while it boots to see what the issue is. I had something similar happen to mine (hanging at the CM icon at boot) when I upped from the October CM10.2 nightlies to the M1 release and ended up using ODIN to return to stock - it's a good thing I had backups!
You can get a shell while in recovery to poke around. You can try mounting from the command line there (the /data partition will be listed in the /etc/recovery.fstab file).
If all else fails, and you have good backups, you could try wiping /data from within TWRP, but keep in mind that all pictures, texts, music, etc will go with it! I would only do this as a last, last resort.
I've seen several threads lately about issues with the partition layout in recent flashing (esp. with the MF1 update). I've reverted back to stock as a precaution, myself.
Joe
Click to expand...
Click to collapse
Hey Joe, I appreciate you taking the time to answer the questions. I did edit my earlier response while you were responding, but to go into slightly more detail, her phone was just sitting on the arm of the couch, when she realized that it was off (it had been on just prior to that). She assumed the battery had died, but when I charged it to 100% and tried to boot it, that's when we found out that it wouldn't boot.
Anyway, wiping data isn't an issue. I have all of her photos and videos backed up, and most of her important stuff is stored in Google Drive. Unfortunately, trying to wipe data actually throws an error. Can you wipe /data if you can't even mount it?
EDIT: When I try to format data in TWRP, I get errors saying "E: Failed to decrypt data", and then it stops at "Updating partition details..."
Possibly a coincidence, She was previously using CM10.2 nightlies and just recently went to the M1 release.
So if we can't mount or wipe /data from recovery, I assume the next step is to go back to stock with Odin? And if that's the case, can you point me in the right direction? I am downloading Official VRBMF1 4.1.2 right now. Do I need a PIT file or something to fix the partitions?
Thanks again
Hrm..
I'd say going back to stock with ODIN will definitely get things back on track. You might need a PIT file to re-partition the device. You'll want to make sure it's the PIT for your model of phone (Verizon 16GB GS3, for example). Google turned up this:
http://teamuscellular.com/Forum/topic/3882-pit-files-for-all-us-variants-of-sgsiii/
I'm the SCH-I535 16GB so I used that one.
One other caveat - be sure you're running ODIN from a real PC - I was using a Virtual Machine and that caused issues.
Joe
erc. said:
Hey Joe, I appreciate you taking the time to answer the questions. I did edit my earlier response while you were responding, but to go into slightly more detail, her phone was just sitting on the arm of the couch, when she realized that it was off (it had been on just prior to that). She assumed the battery had died, but when I charged it to 100% and tried to boot it, that's when we found out that it wouldn't boot.
Anyway, wiping data isn't an issue. I have all of her photos and videos backed up, and most of her important stuff is stored in Google Drive. Unfortunately, trying to wipe data actually throws an error. Can you wipe /data if you can't even mount it?
EDIT: When I try to format data in TWRP, I get errors saying "E: Failed to decrypt data", and then it stops at "Updating partition details..."
Possibly a coincidence, She was previously using CM10.2 nightlies and just recently went to the M1 release.
So if we can't mount or wipe /data from recovery, I assume the next step is to go back to stock with Odin? And if that's the case, can you point me in the right direction? I am downloading Official VRBMF1 4.1.2 right now. Do I need a PIT file or something to fix the partitions?
Thanks again
Click to expand...
Click to collapse
joeinternet said:
Hrm..
I'd say going back to stock with ODIN will definitely get things back on track. You might need a PIT file to re-partition the device. You'll want to make sure it's the PIT for your model of phone (Verizon 16GB GS3, for example). Google turned up this:
http://teamuscellular.com/Forum/topic/3882-pit-files-for-all-us-variants-of-sgsiii/
I'm the SCH-I535 16GB so I used that one.
One other caveat - be sure you're running ODIN from a real PC - I was using a Virtual Machine and that caused issues.
Joe
Click to expand...
Click to collapse
Well, I wish I could come back with more insightful information, but through a bunch of poking and prodding in recovery, I was able to eventually format /data without having to use Odin. Thanks for the link, though. I'm saving the PIT file (same as yours), because who knows when it'll be needed.
This is actually the second time this phone has been stuck at the Galaxy SIII logo screen (with Cid, before the boot animation) in the past couple weeks. Both times were with the Cyanogenmod 10.2 M1 release. I think I might try RC1 to see if it behaves any better, but if not, it's back to stock she goes. If my wife didn't find TouchWiz so hideous, I'd likely go skip trying RC1 and go straight to stock and wait patiently for the 4.3 OTA.
Good morning-
I have a TF101 (with keyboard) running KatKiss 4.3.1_027 and gapps 4.3_20130914. Everything was fine until yesterday morning when I lost network connectivity and decided to reboot (this happens from time to time). Unfortunately, now my tablet won't boot. I get the splash screen with the swirling colored circles, but nothing more.
I tried booting to TWRP (v2.6.3.0 if it matters) and flashed KK and gapps again (including wipes as instructed). This time, it got to an "Upgrading Android" screen, went through my apps, but then got stuck on "Starting apps." I've given it about an hour in both situations and still nothing.
To make matters worse, my microSD slot is flaky and usually doesn't read my card. Based on what I've found, it looks like I have to use adb to push any new files to the tablet. If I boot TWRP and connect my TF to my PC (Windows 7), it tries to install "ASUS Android MTP Device" but is not successful (yellow exclamation point - "This device cannot start. (Code 10)"). I've tried downloading and installing the suite from ASUS, but that doesn't seem to help. "adb devices" doesn't list anything, so I'm stuck here as well.
Any help would be greatly appreciated. Thank you!!
Brian
Welcome to XDA!
This is what I responded to you over at TFF:
Sorry for the issues, it looks like the issue is a corrupt /data/ partition. By default "fsync" is off because this makes it faster, however it could get in a bootloop due to this speed. The fix is to flash the "fsync_on.zip" before the boot loop happens.
Once it happens, you are stuck, but there is help.
If you have TWRP 2.6.3.0, it is supposed to have USB support. Plug in a USB drive before booting to TWRP and it should be there.
To fix your issue and lose very minimal data, here is what will need to be done:
Boot to TWRP.
Backup only the /data/ partition. I would back it up to USB if possible, or if not back it up to the internal or microSD (if the microSD is playing nice).
Next (here is the leap of faith) do the wipe of the SYSTEM, CACHE, DAVLIK and DATA partitions. Do not do a FORMAT DATA, just a WIPE DATA (in the advanced section of the WIPE menu).
Now, install KatKiss and the GAPPS.
Wipe CACHE & DAVLIK.
Reboot.
Sign in to your Google account. You can have it restore apps if you want, I usually do myself, but it does not really matter.
Once it is done restoring your apps (or if you choose not to restore) open the Play Store an install Titanium Backup and the Premium Key for TiBu. You need the premium to restore from a TWRP backup.
Open TiBu and go into the Menu section, then find the option to restore from a nandroid backup. This will scan for any nandroid backups. Pick the backup to restore from and it will take a few minutes to scan the backup. Pick the apps you want to restore data and / or the app from.
Go make a coffee and wait for it to complete.
You may lose data from one or two apps, but you will have it from the rest of them. That is better than nothing.
Thank you!!
If that's all it is, then it's not as bad as I thought.
frederuco said:
If you have TWRP 2.6.3.0, it is supposed to have USB support. Plug in a USB drive before booting to TWRP and it should be there.
Click to expand...
Click to collapse
Unfortunately, this doesn't seem to be working for me. I used TWRP to power off my tablet. Then, I plugged in a USB stick into one of the ports on my keyboard, as this is the only way that I have access to a port. TWRP boots as expected, but I can't see my USB device anywhere. Am I doing something wrong? Is there a partition on the internal storage that I can use for the backup that won't get wiped by the process you outlined above?
Thanks again!!
You can use the INTERNAL storage option, just be sure that when you wipe you only wipe the DATA partition. Do not choose to FORMAT DATA.
WIPE DATA = wipes the /data/ partition without wiping /data/media/ (which is the /sdcard/ directory or INTERNAL)
FORMAT DATA = formats the entire /data/ partition.
As I said above, you can use the internal storage option but be sure to only use the wipe data option.
frederuco said:
You can use the INTERNAL storage option, just be sure that when you wipe you only wipe the DATA partition. Do not choose to FORMAT DATA.
WIPE DATA = wipes the /data/ partition without wiping /data/media/ (which is the /sdcard/ directory or INTERNAL)
FORMAT DATA = formats the entire /data/ partition.
As I said above, you can use the internal storage option but be sure to only use the wipe data option.
Click to expand...
Click to collapse
Just so I'm 100% clear:
Boot to TWRP
Check only "Data" from the left menu.
On the right side, "Storage: Internal Storage" is selected and nothing needs to be changed here.
Swipe to back up
Proceed with the steps in your original post.
Correct.
frederuco said:
Welcome to XDA!
This is what I responded to you over at TFF:
Sorry for the issues, it looks like the issue is a corrupt /data/ partition. By default "fsync" is off because this makes it faster, however it could get in a bootloop due to this speed. The fix is to flash the "fsync_on.zip" before the boot loop happens.
Once it happens, you are stuck, but there is help.
If you have TWRP 2.6.3.0, it is supposed to have USB support. Plug in a USB drive before booting to TWRP and it should be there.
To fix your issue and lose very minimal data, here is what will need to be done:
Boot to TWRP.
Backup only the /data/ partition. I would back it up to USB if possible, or if not back it up to the internal or microSD (if the microSD is playing nice).
Next (here is the leap of faith) do the wipe of the SYSTEM, CACHE, DAVLIK and DATA partitions. Do not do a FORMAT DATA, just a WIPE DATA (in the advanced section of the WIPE menu).
Now, install KatKiss and the GAPPS.
Wipe CACHE & DAVLIK.
Reboot.
Sign in to your Google account. You can have it restore apps if you want, I usually do myself, but it does not really matter.
Once it is done restoring your apps (or if you choose not to restore) open the Play Store an install Titanium Backup and the Premium Key for TiBu. You need the premium to restore from a TWRP backup.
Open TiBu and go into the Menu section, then find the option to restore from a nandroid backup. This will scan for any nandroid backups. Pick the backup to restore from and it will take a few minutes to scan the backup. Pick the apps you want to restore data and / or the app from.
Go make a coffee and wait for it to complete.
You may lose data from one or two apps, but you will have it from the rest of them. That is better than nothing.
Click to expand...
Click to collapse
frederuco said:
Correct.
Click to expand...
Click to collapse
Success!! Thank you! Thank you! Thank you!! Two follow-ups to this:
1.) Since I was never able to get this working, is there a way to access the USB/SD card slots on the keyboard dock in TWRP? Using the internal storage is good, but if I want to wipe the whole thing (since my microSD card slot doesn't work), I would really have no way of ever being able to do this.
2.) I actually went up to 4.4.2, mostly because I could. However, I seem to have issues with the Google Play store where apps are always stuck on "Installing..." then the get installed but not really. I think I'll go back down to 4.3 unless there's a way to solve this.
Thank you again!!
So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]
Did you ever find a fix? I'm having a similar problem.
Try to use fastboot restore everything.
I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device
Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.
If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.
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).