It all started when I forgot my pattern, I've tried to delete lockscreen.db from data/system using X-Plore, my pattern gone but I can't go to home screen, it just showed me Phone is starting the whole night.. I've also tried to restore the lockscreen.db to it's default (I did backup before), but the problem remains the same.. I can only access status bar and settings now
I'm on stock android 10 now, rooted with magisk and twrp installed but my phone seems encrypted (weird folders and files name) .. Can I do dirtyflash OTA via TWRP?? I don't want to lose my data since they are very important to me
Related
I have installed the XenonHD few weeks ago so i am not using the most updated version.
http://forum.xda-developers.com/show....php?t=1667442
today when i am using the phone as normal, it suddenly rebooted.
when it is started, it didnt show any launcher screen or wallpaper but it required me a password to start up the phone.
It shows " Type password to decrypt storage".
As i remember there is a button for activating the encrypt storage function in the system setting/ rom setting.
I am 100% sure that i didnt press it. This function is activated somehow after the sudden reboot......
Is there a way to get the password or extract the data from the phone before i flashing a new rom.....
maybe you should try wiping dalvik cache, or just randomly try to unlock, eventually it should ask you what your google account is, and you should be able to unlock. or else you have to do this: make a nandroid backup, then, flash a new rom, use titanium backup to extract the apps and their data from the nandroid. hope this helps.
Hi all,
I am new here and here goes my first post/querstion at XDA.
I was using some apk when my Device suddenly crashed. I restarted, everything looked fine. The problem started when I tried to open other apk which needs data file from Android Data folder for second operation. The apk was not able to access the files from data folder. I checked my file explorer and found the permissions(displayed at the end of the folder) have changed to -drw(for sure) from -rw(most probably). With this I am not able to delete/move any file from the device storage because the permissions of all other folders have changed to as abaove. If I try to move file, it makes a new copy on my extStorage but the original file is there as it is. The files can't be deleted either. Since my tab is rooted, I installed Root explorer to change file permissions. The permissions under Owner are all unchecked and Group/Others are checked. When I check the Read/Write/Execute permissions for owner, it says cannot be modified(its default disability message). Fed up of all this I went for Factory reset as a final option. I tried to backup using Ti but after some 10% it said not enough space. So I manually backed up whatever I could and went ahead with reset. I successfully did the factory reset and my tablet looked as fresh as when I bought it the first time. All factory apps only but when I was about to be happy, I opened the device storage just to find all those files and data still there, staring at me with their -drw stamp.
My device is Iberry(China I guess) and works on ICS. It is rooted. I had Su Superuser and busy box installed prior to the factory reset but after Factory Reset all apps are gone except their data in the device storage. Please help!
I have been using Nitrogen OS on my OnePlus 3T. I decided to try a Pie ROM, didn't like it, and wanted to revert back. I was having issues with TWRP mounting storage, so I decided to back everything up and wipe.
I used adb to pull the entire sdcard to my computer and verified all the files. I did a complete wipe in TWRP, then pushed the entire sdcard directory back to the phone. I verified everything was there with TWRP, then used it to restore from my last backup, and rebooted. Everything was totally normal.
Now, a day later, I've noticed that my files are not appearing in file managers. I don't know when this happened, whether it was first restart or what. They are on the phone, and taking up space, as can be verified with DiskUsage app, but they are just listed as 40 GB of "System data." See attached screenshot. My Files app can actually show some files, but they are listed as "Unsuccessful" and have no other info. See other attached screenshot. They no longer list in TWRP file manager either.
What gives? How did my files get turned invisible and "unsuccessful"? And can I get them back into usable files? Should I wipe, push backup file, restore, then push the rest?
Side note: TWRP now constantly asks about system modification, despite ticking the box to never ask again every time.
When I used payload dumper on the OTA for this device I ended up with 34 .img files. When I used TWRP to backup all the partitions from the OxygenOS I end up with 12 .win files. When I used dd commands to get copies of boot_a & boot_b and persist, I end up with .img files. When I used dd commands to get EFS backup I ended up with modemst1.bin and modemst2.bin.
I have all these back ups now but I'm not sure which type of file to use and when.
I have TWRP and Lineage on my 8T and they're working great. But I'd like to now restore OxygenOS, install the latest OTA, re-install TWRP, then install a newer version of Lineage. There's a good chance I'll slip up and have to recover my phone at some point and I'd like to know first if I'm better off trying to get TWRP booted and then restoring all the .win backups, or if I should just flash all the .img files from the payload dumper.
Can anyone offer some tips or explain the difference?
Look in TWRP thread. It mentions what partitions to backup (and restore) when changing ROMs.
Look in TWRP thread. It mentions what partitions to backup (and restore) when changing ROMs.
Click to expand...
Click to collapse
I've read through that thread and made a lot of notes, but I guess I'm just wondering at this point, since we have a fully-functional TWRP is it the case that as long as I have the .win files from the TWRP backup of boot, dtbo, super and data partitions that should be all I need?
Persist.img & Modemst1/2.bin & boot_a/b.img can be discarded? Or would you keep these on hand for other reasons?
FakeGemstone said:
I've read through that thread and made a lot of notes, but I guess I'm just wondering at this point, since we have a fully-functional TWRP is it the case that as long as I have the .win files from the TWRP backup of boot, dtbo, super and data partitions that should be all I need?
Persist.img & Modemst1/2.bin & boot_a/b.img can be discarded? Or would you keep these on hand for other reasons?
Click to expand...
Click to collapse
Persist and modem images presumably contain IMEI information, so better keep them somewhere safe. Boot_a/b.img can be discarded.
It's starting to make sense. Thank you for your explanation.
My phone had Lineage and TWRP installed and was running great, but I wanted to try out the backup and restore option of TWRP. So I backed up /data then used TWRP to restore the OxygenOS to the version I was using right before I installed Lineage. I restored OxygenOS to both slots and also I formatted /data.
After doing an minimal setup on OxygenOS, taking a quick look around to see if everything looked okay and rebooting to system a couple of times, I used TWRP to install LineageOS again. That seemed to work fine. I did minimal setup, took a look around, rebooted a couple of times, so far; so good.
I then followed the instructions from theincognito on Steps for backing up and restoring data in TWRP to restore the data partition:
It seemed to work fine, except I was never presented with a blank screen (a clue?) and the phone just booted to system normally. My apps and settings appeared to be restored BUT the 3-button system navigation icons (home/back/switchapps) were missing. So whenever I navigated away from the home screen there was no way to get back except to reboot the phone. It didn't matter if I switched to 2-button navigation or gesture navigation, none of it worked. So I guess the navigation options are all apps and those apps malfunctioned when /data was restored. Also, I could not enable Advanced Restart for the Power Menu. That's probably a system app, too. I didn't have a password on the phone at any time, or a SIM card installed. I know the TL;DR instructions in post #3 say that you should just reboot to system again if you have this problem, but doing so didn't fix the problem for me. I must have made a mistake at some point.
I ended up wiping the phone, doing a clean install of Lineage and setting up the apps and preferences the old-fashioned way.
I'd like to try this again to see if I can get it to work. Does anyone have suggestions of what went wrong?
Should I have tried restoring /data a second time before giving up and wiping the phone?
Does the fact I didn't get the expected blank screen after restoring /data have any significance?
Did the problem more likely originate with the backup process or the restore process?
Oh boy, it just dawned on me... Should I have also restored the backup of Boot/dtbo/Super? I assumed those wouldn't change if you were restoring to the exact same version of Lineage so I didn't bother with it.
I stumbled across a trick to get the restored data backup working again. I went to Settings --> Apps & Notifications --> App Info. Then I selected the option "Show System" from the list at the top with the 3 vertical dots. From the list of apps I selected 3-button navigation and then selected "force stop". After that, I rebooted and all the settings that were missing before were magically back in place, and both the Status Bar and the Navigation Bar were functioning and configured just the way I had them when I did the backup. I don't know anything about how system apps work so I can't explain why this helped, but I tested it twice with fresh installations of LineageOS and it worked exactly the same both times.
I should add that between this post and the one above from February 1st, I have re-installed Oxygen OS many times using old and new OTA zips, and installed Lineage OS several times, first on one slot then the other. And each time I've restored various back ups of LineageOS system files and LineageOS data files following the instructions, but always the result was a partial restoration of user configurations and missing status and navigation bars. I wonder that I'm the only person who found that booting twice after a data restore didn't bring back those menus. But hopefully if it happens to someone else they'll find this post and know what to do.
I've been having a bunch of problems recently with my rooted 7 Pro including Magisk Manager constantly "keeps stopping", not being able to access Hide to add new applications, banking apps starting to detect that I'm rooted and camera issues: the camera app not starting, the camera not popping up automatically and the image being usually reversed and occasionally upside down as well, depending on the app I'm using.
Given that Magisk appears to be dead/dying, having lost its developer to Google, I thought I'd start by getting rid of that and then performing a firmware upgrade in necessary to see if that fixes the other issues.
I uninstalled the Manager then ran the uninstall zip within TWRP. Rebooting though hangs on the initial "ASUS" screen.
I can get back to TWRP ok so I guess I'm not bricked yet. My next thought was to try a system upgrade but I seem to need to know the exact version I need, which, seemingly, I can only get via a working phone?
From the back, it says only model I002D along with SN and IMEIs.
I've done a TWRP backup to the external uSD card, and I have a syncthing copy of all of the internal memory that I can access without root.
My questions:
1. Is there something there which can help my figure out which firmware I need to download?
2. Is there any way to install this without wiping the phone?
Please see this post.
When I try to burn rom with TWRP, img burns but it doesn't start and zip gives an error and cannot burn.
When I first burned custom ROM (unofficial AEX), it did not start, so when I deleted the data from TWRP, it seems that I deleted things that should not be erased, so even if I burn it from the zip file, with the error message in the image below I...
forum.xda-developers.com