Related
Ok I've searched for a while and couldn't find anything. I couldn't get the SDK workaround to work.
I put the wrong patten in too many times and now it's asking for my gmail username/password. I've put in everything I can think of but it never works. I NEED some of the texts on there and yadda yadda. Is there ANYWAYS to get around this?
Put in your Gmail and type "null" for your password
Sent from my GT-I5800 using XDA App
Do I need to be connected to the internet? My account is under @Yahoo so would I need to sign in with that?
Thanks for the help..
Update: Null doesn't work =/
Ok. I'm offering $20 to the first person who can help me fix this. I'm on Froyo (latest version) on an HTC HD2. I just NEED to get past this unlock issue. Resetting the phone is out of the question
i'll give it a try, maybe $20 will buy me a new scarf.
so you forgot both your pattern AND your google account? or did you not have a google account on there? or what.
I have a gmail account on there and I've tried every possible combination I would use and it doesn't let me on. I'm out of ideas here
Are you putting in the whole gmail address or just the first part before the @ ?
I'm putting both
It's [email protected] and I've tried @yahoo - @gmail [email protected] Etc..
Nothing works.
This really shows why its important to remember what account you put on the phone even if its not the email you use.
Sent from CM6 on my T-Mobile Mytouch 4g via Tapatalk.
Yes.. Yes I know that.
The thing is that I've tried EVERY gmail account I have.. That's only two though. I've read that there's a bug that causes me to not be able to log in or something?
Is there ANY way to set the default to Disk Drive instead of charge only? If I could do that I could use the adb method..
Anyone? =/
Try factory resetting
Sent from my GT-I5800 using XDA App
One possible solution...
Did you have root?
If you hopefully did,
1) install a custom recovery using adb
2) reboot phone into recovery mode
3) create a nandroid backup (not with ext)
4) wipe data, cache, dalvik-cache, rotate settings and battery settings, NOT SD-EXT
5) restore nandroid backup and phone will be restored.
6) reboot
siidheesh said:
Did you have root?
If you hopefully did,
1) install a custom recovery using adb
2) reboot phone into recovery mode
3) create a nandroid backup (not with ext)
4) wipe data, cache, dalvik-cache, rotate settings and battery settings, NOT SD-EXT
5) restore nandroid backup and phone will be restored.
6) reboot
Click to expand...
Click to collapse
YES! I'll look into this. Thank you!
Fix from the Android issue tracker
It seems during an incoming call, you can back out to Home & access settings to disable the pattern lock or reset your phone's designated email account. There are a bunch of workarounds posted in the Android issue tracker, bug 4784 - try to see if any suggestions help you:
h ttp ://code. google.com/p/android/issues/detail?id=4784
The workaround in comment #35 worked for me, I disabled the pattern lock altogether.
hth,
- C
After successfully restoring backup on the new phone the fingerprint doesn't work.
Details about restore process are here: https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413/page10
Before TWRP backup I did set two fingerprints. After restoring on new phone if I try unlock screen with fingerprint I'm getting message "Fingerprint hardware not available"
I can unlock screen using PIN but I can't add new fingerprint nor delete two existing.
When I delete one fingerprint, it greyed out (screenshot attached) but when I return back to Fingerprints it's still there.
Adding new fingerprint starts fingerprint setup but right before end I'm getting message (screenshot attached):
Enrolment was not completed.
Fingerprint enrolment didn't work. Try again or use different finger
Fear not, this is not hardware issue. I went back to stock image and I can setup and use fingerprint and delete fingerprints.
So, I went back to square one and flashed stock image, boot, reboot, TWRP, flashed StatiXOS, boot. At this point checked, fingerprint is still working in StatiXOS.
Rebooted to TWRP, wipe and restore my StatiXOS backup and still having the same issue with fingerprint.
Reading some threads my guess is that fingerprint should be disabled before backup. The fingerprint info is probably saved on fingerprint chip and factory reset should fix the issue.
Turther search lead to other threads about same issue and it seems deleting some files/folders in data partition reset fingerprint settings.
Unfortunately none of them doesn't match 3a. Have no time now but will investigate further other solutions. Pixel 3 threads might have the answer.
I had exactly the same prob on AOSiP on my Pixel 3 XL. Was not able to find it out or to solve it. Back to Stock and it worked fine w/o any probs. Since some days I am on DU and also no probs so far.
gogoffm said:
I had exactly the same prob on AOSiP on my Pixel 3 XL. Was not able to find it out or to solve it. Back to Stock and it worked fine w/o any probs. Since some days I am on DU and also no probs so far.
Click to expand...
Click to collapse
Same here, gave up and flash stock again. I was trying some stuff and noticed if I create another account and switch I can enable fingerprint but only for that account. So, something is screwed up in default account settings.
The best advice I can offer is from this Pixel XL thread: https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
MAKE SURE YOUR LOCKSCREEN IS OFF... No fingerprint set up... Not a pin set up... No pattern set up. If your more secure than swiping up to open your screen your not getting in to TWRP 3.2.0-0 decrypted.
Click to expand...
Click to collapse
Unfortunately I don't have another Pixel 3a around to test, but it make sense.
So you already tried data/system/ & change locksettings.db to locksettings.db.bak ? It should create a new locksettings.db after you go into phone settings to set up a new pin/fingerprints then go & delete locksettings.db.bak or you can leave it...either way.
SketchyStunts said:
So you already tried data/system/ & change locksettings.db to locksettings.db.bak ? It should create a new locksettings.db after you go into phone settings to set up a new pin/fingerprints then go & delete locksettings.db.bak or you can leave it...either way.
Click to expand...
Click to collapse
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Even if it work on my phone it might not work on different phone. If I'm in charge of security on Pixel 3a project I will at least compare hardware fingerprints (i.e. serial numbers, MAC address, etc) of the phone with previous data save in encrypted file in some very protected area
However, it could be useful to all dummies like me who screwed their phones.
Pogo said:
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Not much luck today. I have created two backups on rooted StatiXOS:
- one with fingerprints and PIN unlock
- one without fingerprints and swipe unlock (no protection at all)
Before running backup checked all boxes in Backup option (Boot, System, System Image, Vendor Image, Data)
Note: only Boot, Data and System Image are actually required, but just in case
After that I've tried the following:
1.
- flash factory ROM to make sure there is no traces of my settings
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to TWRP, wipe Dalvik/Art, System and Data
- copy my backups to TWRP as well as all other folders originally on sdcard
- go to restore and select my backup with fingerprints
- only check Boot, Data and System Image boxes
- reboot, all good so far. PIN and fingerprint works, only needed to re-enable fingerprint in apps that use it like my banking app
2.
- back to fastboot, deleted file data/system/locksettings.db
- rebooted, there is no lock or PIN, just swipe
- "Pixel is starting..." message show up on display
- launcher and apps are not available, but Settings are available from status bar
- can add new fingerprint, delete fingerprint but the message on home screen won't disappear
- gave up after 10 min of waiting
3.
- flashed factory ROM again
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to fastboot, delete file data/system/locksettings.db
- reboot, there is no lock or PIN, just swipe
- same as before but the message is now "Phone is starting..."
- gave up after 10 min of waiting
Need to actually USE my phone, so I stopped here and restored my trusty backup.
So, you can restore your backup with fingerprint. Judging by my experience restore is fully functional only on the physically same phone (same s/n, same MAC, etc, no hardware modifications).
Deleting data/system/locksettings.db did remove lock but still didn't make phone fully functional. However it's promising.
Click to expand...
Click to collapse
Pogo said:
Pogo said:
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Not much luck today. I have created two backups on rooted StatiXOS:
- one with fingerprints and PIN unlock
- one without fingerprints and swipe unlock (no protection at all)
Before running backup checked all boxes in Backup option (Boot, System, System Image, Vendor Image, Data)
Note: only Boot, Data and System Image are actually required, but just in case
After that I've tried the following:
1.
- flash factory ROM to make sure there is no traces of my settings
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to TWRP, wipe Dalvik/Art, System and Data
- copy my backups to TWRP as well as all other folders originally on sdcard
- go to restore and select my backup with fingerprints
- only check Boot, Data and System Image boxes
- reboot, all good so far. PIN and fingerprint works, only needed to re-enable fingerprint in apps that use it like my banking app
2.
- back to fastboot, deleted file data/system/locksettings.db
- rebooted, there is no lock or PIN, just swipe
- "Pixel is starting..." message show up on display
- launcher and apps are not available, but Settings are available from status bar
- can add new fingerprint, delete fingerprint but the message on home screen won't disappear
- gave up after 10 min of waiting
3.
- flashed factory ROM again
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to fastboot, delete file data/system/locksettings.db
- reboot, there is no lock or PIN, just swipe
- same as before but the message is now "Phone is starting..."
- gave up after 10 min of waiting
Need to actually USE my phone, so I stopped here and restored my trusty backup.
So, you can restore your backup with fingerprint. Judging by my experience restore is fully functional only on the physically same phone (same s/n, same MAC, etc, no hardware modifications).
Deleting data/system/locksettings.db did remove lock but still didn't make phone fully functional. However it's promising.
Click to expand...
Click to collapse
In the future (I've done this on the last several phones running AOSP or similar) I always change locksettings.db to locksettings.db.bak before doing a nandroid because I've had issues restoring ROMs then my PIN won't work, etc. Once I've unlocked my phone on a restore I change it back to locksettings.db
Click to expand...
Click to collapse
Dear community, I am facing several troubles with my OP7pro which I think can be quite easily handled but my knowledge is just too little.
I am running OOS 10.0.2 with Renovate ICE, rooted with Magisk and on TWRP 3.3.1-70 - stock kernel and normally encrypted. I am facing various troubles that started after upgrading from 9.5.13 tot Android 10. I do not know if they are directly related. I do have Nandroids, BUT the phone is my daily driver, also for work, and a factory reset will just take too much time.
What are the troubles you ask?
- I am not able to enter the menu Buttons&Gestures/navigation/set up navigation bar. The screen blinks and I am back in the upper menu. If I press this menu again I get a "Settings stopped". This sucks, because I want to set up my on-screen buttons
- I used to use Plus Beat in combination with RICE on Android 9. Worked perfect. Whatever I set up, Plus Beat just does not work. That sucks big time.
- I am not able to set on screen buttons to for example switch between recent apps or get anything else but horizontal recents (which is slow and to me sucks). QuickSwitch via Magisk doesn't bring anything.
NOW TO THE QUESTIONS:
I GUESS (! but am not sure!) that a factoryreset could and should solve these problems. I could and would do that, but, I need to be up and running and have my settings back quickly. Internal memory (root) I could copy to PC and paste back afterwords. But is there some way I could put my settings (in the menu) and all my apps (250+) back via Nandroid data?
I have the following things backed up in TWRP:
- Boot
- System Image
- Vendor Image
- Data
- Modem
- EFS
If I do a complete new factory set-up (for example via Maurefranio's tool), to refresh my system (I guess the failure is in there), can I put back other parts of the Nandroid to have all the rest back? Also in the menu-settings, color-setting etc. etc. etc.?
I know it sounds rooky, but I hope someone takes time to help me a little. I do use Titaninium etc. but I can't spend hours and hours on a recovery. In that case I'd probably decide to keep using the OP7pro as I do, but it's frustrating that RICE and Plus Beat don't work fully and some other errors. The usability to me is 4 out of 10 - where in Android 9 it was surely 9 out of 10.
Greetings,
existenz
Are you running a substratum theme? That could be the settings issue. But that's about all I could help with. Never restored anything using twrp on this phone. Most I've done is backup my apps with swift backup, factory reset, or MSM tool, and restore my apps.
How quickly do you need your phone up and running? You could backup with swift backup, factory reset and only restore what you need for now then do the rest when you have time.
@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!
exis_tenz said:
@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!
Click to expand...
Click to collapse
In that case, I would just use swift backup, backup to your device. Transfer SD card contents to your computer, factory reset. Transfer SD card files back. Swift backup can backup all apps and data. I believe that would work for what you want.
I, however, do not know what parts of the nandroid do what as I usually just don't bother with it.
GeekMcLeod: appreciate your advise, but Nandroid is there for a reason.
Is there anyone who can please help me what to do best? I mean, one of those Nandroid-partitions holds the clue, right?
I am also facing overnight Batterydrain of about 30% (from 80 to 50 in about 7-7,5 hours).
No Nandroid specialists in the house?
You need to wipe your data. Use Swift to backup apps, messages and call logs. Google will do it's best to restore settings upon setup. Your problem is almost guaranteed to be in data. If you need that data, I would recommend going back to whatever version of pie you were on before. Swift won't restore app permissions, as far as I know so be sure to double check if you restore apps with Swift.
Hi, I'm kinda at my wit's end with this problem that I'm currently facing and would very much appreciate some help. For some background, I'm on a Oneplus 7 Pro running stock firmware (OOS 11.0.7.1). I originally was planning on installing a Magisk module to spoof my device (Pixelify) to gain Pixel features. I noticed that one of the features was patching over the Android System Intelligence. It didn't work out the way I was expecting and I decided to uninstall the module. That went fine, but I wanted to make sure I was on the correct version of Android System Intelligence as well, so afterwards, I went into settings and "uninstalled all updates" to the app, which I assumed would have reset that particular app back to the version that originally shipped with the device.
Now, here's where the problem began. I restarted my device and I ended up sitting on the boot animation screen for over 20 mins. At that point, I knew something was wrong as it still hadn't booted into the system yet. I went into TWRP and decided to do a full reflash of the ROM (without wiping my data) and reflashed magisk as well. No luck either, still stuck at the infinite boot. So I went a step further and dirty flashed again without reinstalling magisk to see if it might have been any other modules not playing nice. Of course, that didn't work either and I'm still currently bootlooping. It's been going for the past 3 hours now...
In any case, would anyone have any suggestions on what I can do without doing a full wipe? I have access to TWRP and decrypting works fine. All of my files seem intact at the moment and from what I see, the ROM is has installed mostly fine, just something is causing it to hang during boot. Is there any way I can view the code running in the background during boot to see what's causing it to hang? Or maybe some other potential solution that I could try?
HunterBlade said:
Hi, I'm kinda at my wit's end with this problem that I'm currently facing and would very much appreciate some help. For some background, I'm on a Oneplus 7 Pro running stock firmware (OOS 11.0.7.1). I originally was planning on installing a Magisk module to spoof my device (Pixelify) to gain Pixel features. I noticed that one of the features was patching over the Android System Intelligence. It didn't work out the way I was expecting and I decided to uninstall the module. That went fine, but I wanted to make sure I was on the correct version of Android System Intelligence as well, so afterwards, I went into settings and "uninstalled all updates" to the app, which I assumed would have reset that particular app back to the version that originally shipped with the device.
Now, here's where the problem began. I restarted my device and I ended up sitting on the boot animation screen for over 20 mins. At that point, I knew something was wrong as it still hadn't booted into the system yet. I went into TWRP and decided to do a full reflash of the ROM (without wiping my data) and reflashed magisk as well. No luck either, still stuck at the infinite boot. So I went a step further and dirty flashed again without reinstalling magisk to see if it might have been any other modules not playing nice. Of course, that didn't work either and I'm still currently bootlooping. It's been going for the past 3 hours now...
In any case, would anyone have any suggestions on what I can do without doing a full wipe? I have access to TWRP and decrypting works fine. All of my files seem intact at the moment and from what I see, the ROM is has installed mostly fine, just something is causing it to hang during boot. Is there any way I can view the code running in the background during boot to see what's causing it to hang? Or maybe some other potential solution that I could try?
Click to expand...
Click to collapse
When you removed the magisk module and uninstalled the updates, did you boot into TWRP and wipe your cache and dalvik cache(but not factory reset or wipe data partition)? If you didn't wipe cache or dalvik, try booting into TWRP and wipe cache and dalvik cache(but DO NOT factory reset). To wipe cache and dalvik cache, boot into TWRP and sekect the Wipe option, then select "advanced wipes", you'll see a list of partitions, select only the cache and dalvik partitions(do not select any other partitions) then swipe the slider to initiate the wipe, when it finishes, reboot your device, it might take 10 or 20 minutes to boot because it has to rebuild the cache and dalvik cache with the new changes that you've made.
Generally, when making changes to the system partition, booting into recovery after making the changes and wiping cache is required in order for the device to load the system with the changes that were made instead of continiung to load cached data from before the changes were made, this tends to cause issues because the device is loading cached data that it can't use or understand anymore. Also, reflashing your ROM without wiping cache and dalvik cache would not solve this issue. You should do this any time you add/remove/modify/delete/uninstall/edit anything at all in the system partition, even if you only changed one tiny thing, you still need to boot into recovery then wipe cache and dalvik cache then reboot to apply the changes. This is not required when changing things in the user partition but it is absolutely vital that you do it when changing anything involved in the system partition.
Droidriven said:
When you removed the magisk module and uninstalled the updates, did you boot into TWRP and wipe your cache and dalvik cache(but not factory reset or wipe data partition)? If you didn't wipe cache or dalvik, try booting into TWRP and wipe cache and dalvik cache(but DO NOT factory reset). To wipe cache and dalvik cache, boot into TWRP and sekect the Wipe option, then select "advanced wipes", you'll see a list of partitions, select only the cache and dalvik partitions(do not select any other partitions) then swipe the slider to initiate the wipe, when it finishes, reboot your device, it might take 10 or 20 minutes to boot because it has to rebuild the cache and dalvik cache with the new changes that you've made.
Generally, when making changes to the system partition, booting into recovery after making the changes and wiping cache is required in order for the device to load the system with the changes that were made instead of continiung to load cached data from before the changes were made, this tends to cause issues because the device is loading cached data that it can't use or understand anymore. Also, reflashing your ROM without wiping cache and dalvik cache would not solve this issue. You should do this any time you add/remove/modify/delete/uninstall/edit anything at all in the system partition, even if you only changed one tiny thing, you still need to boot into recovery then wipe cache and dalvik cache then reboot to apply the changes. This is not required when changing things in the user partition but it is absolutely vital that you do it when changing anything involved in the system partition.
Click to expand...
Click to collapse
Thanks for the response! Unfortunately, I already wiped the dalvik cache after I reflashed my ROM yesterday and it didn't end up being able to boot. Since the OnePlus 7 Pro is an a/b device, there's no other cache partition to wipe.
I ended up leaving it to run on the boot animation screen until it ran out of battery (just to see what would happen). Besides for the phone becoming burning hot to the touch, it just stayed at that screen for another hour or 2 before it finally ran out of battery. This leads me to believe that it's definitely doing something in the background at that time, but just not sure what.
Edit: Just for some extra context, I also created a flashable zip of the latest OEM version of the Android System Intelligence APK and flashed it to system/app through twrp. Since I'm not able to boot to unlock my device, I thought this was the only way to install the app. In any case, it didn't make a difference either. Not sure if this means maybe the APK wasn't the issue or if this just didn't install the app the way I was expecting. No error codes when flashing the zip though.
HunterBlade said:
Thanks for the response! Unfortunately, I already wiped the dalvik cache after I reflashed my ROM yesterday and it didn't end up being able to boot. Since the OnePlus 7 Pro is an a/b device, there's no other cache partition to wipe.
I ended up leaving it to run on the boot animation screen until it ran out of battery (just to see what would happen). Besides for the phone becoming burning hot to the touch, it just stayed at that screen for another hour or 2 before it finally ran out of battery. This leads me to believe that it's definitely doing something in the background at that time, but just not sure what.
Edit: Just for some extra context, I also created a flashable zip of the latest OEM version of the Android System Intelligence APK and flashed it to system/app through twrp. Since I'm not able to boot to unlock my device, I thought this was the only way to install the app. In any case, it didn't make a difference either. Not sure if this means maybe the APK wasn't the issue or if this just didn't install the app the way I was expecting. No error codes when flashing the zip though.
Click to expand...
Click to collapse
Use TWRP to create a backup of your device in its current state, then try to extract the data from the backup, if the data is intact, it can be restored once you get the device working. If your data is intact in the backup, you can do a full system and data wipe via TWRP then reflash your ROM then restore the data that you want restored. This "should" get you back to where you want to be. Be careful, be certain of what you do at every step or you may end up losing data or not being able to get it to work while at the same time be able to keep your previous data.
Droidriven said:
Use TWRP to create a backup of your device in its current state, then try to extract the data from the backup, if the data is intact, it can be restored once you get the device working. If your data is intact in the backup, you can do a full system and data wipe via TWRP then reflash your ROM then restore the data that you want restored. This "should" get you back to where you want to be. Be careful, be certain of what you do at every step or you may end up losing data or not being able to get it to work while at the same time be able to keep your previous data.
Click to expand...
Click to collapse
Just finished backing up my data through TWRP and and did a full reformat of my device. After reflashing my ROM, I was back up and running! So thanks for the tip! However, after restoring the data partition, I realized that the issue was with the data partition specifically rather than on the system side as I had the same problem again. So I cleared the data partition again but kept data/media (internal storage) intact, and just like that, the device booted just fine this time.
Would you have any suggestions on what I could do to to troubleshoot the data partition? I have some important app info that I need to get the data back from.
Or if not, do you know how to capture logs from a failed boot?
HunterBlade said:
Just finished backing up my data through TWRP and and did a full reformat of my device. After reflashing my ROM, I was back up and running! So thanks for the tip! However, after restoring the data partition, I realized that the issue was with the data partition specifically rather than on the system side as I had the same problem again. So I cleared the data partition again but kept data/media (internal storage) intact, and just like that, the device booted just fine this time.
Would you have any suggestions on what I could do to to troubleshoot the data partition? I have some important app info that I need to get the data back from.
Or if not, do you know how to capture logs from a failed boot?
Click to expand...
Click to collapse
Logs from logcat do not persist through reboot. You need to look at your last_kmsg file, kmsg persists after reboot and it should capture the issue. If you have important app data, it should have been stored in data/media in your Android/(name of app) folder and your apps should be in data/data/app folder.
In the future, I recommend booting into TWRP and creating a backup before you make any kind of changes to your device, then, if the change causes an issue you can just boot into TWRP and restore the backup, this will put you back to what you had right before you made the change. Then you can troubleshoot what caused the issue and find a solution to how to apply your change without causing the issue again.
Droidriven said:
Logs from logcat do not persist through reboot. You need to look at your last_kmsg file, kmsg persists after reboot and it should capture the issue. If you have important app data, it should have been stored in data/media in your Android/(name of app) folder and your apps should be in data/data/app folder.
In the future, I recommend booting into TWRP and creating a backup before you make any kind of changes to your device, then, if the change causes an issue you can just boot into TWRP and restore the backup, this will put you back to what you had right before you made the change. Then you can troubleshoot what caused the issue and find a solution to how to apply your change without causing the issue again.
Click to expand...
Click to collapse
Yeah, lesson learned with that. I'm just glad I was able to backup my data in TWRP, which means I should theoretically be able to extract them back out again if I really need them. But back to the topic, I did check my last_kmsg file and it was unfortunately empty.
What I did do though was since I still have access to my recovery, I pushed my PC's adb keys to my device to be able to execute the command and grab a logcat during boot.
Could you by any chance take a look at the file (it's a onedrive preview link) to see if you might be able to notice the issue? I'm going into the territory of Googling everything and I was just completely lost when I looked at the file as I have no idea which errors actually matter and which ones don't. Thanks in advance!
HunterBlade said:
Yeah, lesson learned with that. I'm just glad I was able to backup my data in TWRP, which means I should theoretically be able to extract them back out again if I really need them. But back to the topic, I did check my last_kmsg file and it was unfortunately empty.
What I did do though was since I still have access to my recovery, I pushed my PC's adb keys to my device to be able to execute the command and grab a logcat during boot.
Could you by any chance take a look at the file (it's a onedrive preview link) to see if you might be able to notice the issue? I'm going into the territory of Googling everything and I was just completely lost when I looked at the file as I have no idea which errors actually matter and which ones don't. Thanks in advance.
Click to expand...
Click to collapse
Too many errors for me to volunteer my time to figure out.
All I can say is, at each line that reports an error, it states the error then lists the service(s) or app(s) that are involved in or effected by that error, everything listed after the error all the way down the list to the next error are related to that error.
Do a Google search for each error and the name of the package that immediately follows that error.
Droidriven said:
Too many errors for me to volunteer my time to figure out.
All I can say is, at each line that reports an error, it states the error then lists the service(s) or app(s) that are involved in or effected by that error, everything listed after the error all the way down the list to the next error are related to that error.
Do a Google search for each error and the name of the package that immediately follows that error.
Click to expand...
Click to collapse
No worries, totally understandable. I think Titanium Backup might actually be my saving grace, as it's able to read TWRP files as well. So all I have to do is run my backup through that and have it directly restore my data. In any case, appreciate the advice you've given so far!
you might probably found a fix but you're supposed to put the other os in the internal storage and not the micro sd card since it wont detect bootable drives just like on a pc and if u didnt install the os on the sd card then you can search for a boot unlocker which can unlock your phone from the infinite boot based on your phone and os
have a good day
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