Good day,
I think I f***ed up the encryption of the files in the /sdcard folder.
I'm using the unofficial TWRP recovery for this device (the official one and OrangeFox don't work) and installed the latest LineageOS. Before that I made a backup of the official MIUI 11 that was installed on the device.
Now, my original problem was that after I installed WhatsApp on the new LineageOS, it always tried to find a backup on my Google Drive (which doesn't exist) instead of using my local backups. So, since I wanted to restore it, I decided to go back to MIUI 11, backup WhatsApp via Titanium AND Google Drive, just in case, then go back to LineageOS and then finally restore WhatsApp to it's original state.
Not only was I not able to restore MIUI 11 because I always got an ERROR 255, but I also now have an encrypted internal storage that I cannot decrypt at all.
About the ERROR 255: I had a 2nd user (called "Guest") on the device, and from what I've read, having multiple users is what often causes this ERROR 255. I removed it, but it didn't help.
My biggest concern right now is the encrypted internal storage. At some point I had an issue with TWRP where it was stuck at "Trying Decryption" when I started it and input my code. So after a few retries, I just hit cancel. I then flashed LineageOS and my guess is that TWRP flashed it without giving it proper access to /sdcard?
does anyone have an idea how I can decrypt my internal storage? Or is it all lost and I have to "Format Data" via TWRP?
EDIT: This is what my files look like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!
Try your phone pin for decrypt in twrp or boot and you have access through usb... or not?
Oh I did try my PIN in TWRP and connecting via USB already, but the folders and files names are just a mess - can neither copy, delete nor open them.
Wow... big problem...
Related
recovery: TWRP 2.5.0
ROM: aokp_primoc_unofficial_Jan-19-13
kernel: the one that came with the aokp rom .zip found in this page
anyway I try to do a factory reset in TWRP and it failed (sd - ext wouldnt wipe for some reason) so I just wipe everything else (system, cache, davlek, and android_secure). I install AOKP and reboot.
so AOKP's colorful unicorn bootloader comes up and I'm greeted by the new interface. It asks for the default launcher and I decide to go with nova launcher. About 30 seconds later the thing reboots and I go through the same process over and over again.
I tried a different kernel as well, lean kernel, and it never got past the "this is for development purposes only" screen. this >
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried getting back to stock, but even when I recover the back up I made in TWRP before I changed ROMs it gives me the "this is for development purposes only" screen again and never continues.
Things I've tried
Running an RUU program. always fails.
getting the RUU rom file from the temp folder, renaming it, PK76DIAG, and putting in my sd card. says hboot version is old.
flashing a different ROM. gives me a black screen
reformatting sd card, still can't wipe sd - ext
Scrolling through the internet I can see that a lot of people have trouble with the One V and boot looping, but none of their solutions help me,
I'm really at my wits end so if anyone has had this trouble before I'd love the help
Is this even in the right section?
I have a Virgin Mobile Galaxy S II (which is just a rebranding of the Sprint Epic Touch 4G).
I'm rooted, running CM 10.2 nightlies (no stable versions available)
New build update came, I downloaded and updated to it, it updated my phone from 4.2.2 to 4.3.1, I was happy, seemed a lot smoother
Couldn't get any data or wifi though, so I rebooted, but my phone wouldn't get past the screen that says Samsung Galaxy S II
Booted into recovery, tried restoring the nandroid backup I made just before installing the new build
Won't restore boot image, I can use advanced restore to restore system, data, cache, etc, but not boot, which is kinda important since I can't turn use my phone without it
Help pls
EDIT: So I just kept trying to reboot it because I had nothing better to do while trying to find a solution, and it randomly worked, so I am back wjere I was before I installed the new nightly build.
BUT, I just made a new nandroid backup since the one I had lacked /boot, but as I was making the new nandroid backup it said this:
06:25:51 /boot not found! Skipping backup of /boot!
06:25:51 Consider installing patch file for your device, for a complete nandroid!
06:25:51 /recovery not found! Skipping backup of /recovery!
So apparently my phone has no /boot right now or /recovery, so I can't turn my phone off until I get a new one. Any advice on how to do that would be appreciated.
Just flash a different ROM or the one you were on before. Make a new nandroid. Restore the data portion if you want.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Search didn't turn up anything related to my issue and it doesn't seem to break the phone, but I'd like to know what's going on. After successfully flashing TWRP 2.8.0.2, then the CyanogenMod 11 M9 snapshot (2014-08-04) and the latest gapps (2014-01-05) last night, this morning I go to make a nandroid and imagine my surprise when TWRP isn't there, but CWM 6.0.5.0 (touch version). WTF? It seems like CWM functions properly, and my phone's working fine, but I never flashed CWM. The only thing semi-related in the CM 11 thread is a post from May 2014 about needing to use CWM 6.0.4.8 for future CM builds, but I succesfully did it with TWRP, soooooooo. I don't know what's going on. Does CM 11 automatically flash CWM for some compatibilty reason? The only other thing that might be useful info is that I did have my phone connected to my PC the whole time last night, since I had just finished unlocking bootloader, copying the CM 11 and gapps zips, etc. and I did have a CWM img in my adb/fastboot directory (since I wasn't yet sure which recovery I was going to flash), but it was the 6.0.4.8 non-touch recovery, which isn't the version that's been mysteriously flashed to my phone, and I never entered any commands to flash that img anyway. Any thoughts?
i think you might have clicked "update CM Recovery" in the developer options. that's the only real explanation i can think of
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The "update CM recovery" thing sounds the most plausible at this point. Thanks for taking the time to read. Although Rick James might be on to something.
So my beloved Tab S finally died recently due to accidental damage. I have wept every night since. :'(
Jk but seriously, I miss it badly. I had the perfect setup on LineageOS and everything working nicely, then it fell off the arm of the sofa and smacked the screen hard. Cracked badly and the digitizer is also broken. I was able to complete a full backup in TWRP using the adb shell, so I'm pretty happy with that.
My new device is a Huawei Mediapad M3. It's the best tablet at the same kind of screen ratio I could find. Decent price too. I've not been able to unlock the bootloader or root it just yet, but I expect to have this done shortly.
My question for you guys is how can I extract my apps from the backed up data partition in my TWRP backup from my Tab S to my Mediapad?
I can easily access the data archive by renaming the file extension to .tar and opening in winrar, but when I copied a single app folder to my phone (just to test it) the app did not appear in the app drawer after restarting.
Has anyone here had experience extracting apps from TWRP backups successfully?
Basically you are looking for /Data/yourappname/ and /sdcard/Android/yourappname folders.
I would suggest first install yourappname.apk, then when it will make folder structure in mentioned above paths, copy your backup data for yourappname over and restart. That should do it.
PS: but for dealing with /Data partition you need root access in your new tab. Also , pay attention for attributes of the files copied over.
Yes, you can restore your apps with titanium backup and a twrp backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cleanly installed Xiaomi Eu rom, then got root access by flashing Magisk 24.3. The installation went smoothly. According to the Root Checker app, I have root access on my device. But when I try to modify a file in the system folder with the Root Explorer app, it won't let me do it and gives me an error message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know if I've missed something or I'm uninformed, but is it not possible anymore (or never was) to modify system files in Miui based roms?
Hmm... Try using FX File Manager
I highly recommend this File Manager!
Did you flash magisk directly using twrp? If so, that might be the problem.
See this post:
Gapps error 70, resize System Partition.
Hello. After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos. >Fastboot boot twrp.img>advanced>flash current twrp. After that I've wiped and format data...
forum.xda-developers.com
user0u said:
Did you flash magisk directly using twrp? If so, that might be the problem.
See this post:
Gapps error 70, resize System Partition.
Hello. After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos. >Fastboot boot twrp.img>advanced>flash current twrp. After that I've wiped and format data...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I have flashed it using twrp and also from fastboot mode.
Never mind, I fixed it flashing (using TWRP) the MAKERW-STABLE-4.1.11.zip file from this thread https://forum.xda-developers.com/t/...-script-to-install-all-roms-via-twrp.4405061/