Has anyone been able to fix the EIS not working after the 5.1.6 update? I seen where someone said to clear system cache in recovery, does that work and will it wipe anything off the phone?
UPDATE: Clearing cache in recovery fixes the EIS not working on 30fps modes. Just don't wipe "SYSTEM" like I did... Thank goodness for Nandroid backups
deleted
dgunn said:
Has anyone been able to fix the EIS not working after the 5.1.6 update? I seen where someone said to clear system cache in recovery, does that work and will it wipe anything off the phone?
UPDATE: Clearing cache in recovery fixes the EIS not working on 30fps modes. Just don't wipe "SYSTEM" like I did... Thank goodness for Nandroid backups
Click to expand...
Click to collapse
I am sorry, what cache? I thought there was no cache in Android 7+.
There will always be cache and it's located in recovery
dgunn said:
There will always be cache and it's located in recovery
Click to expand...
Click to collapse
Excuse me? I thought the Cache partition was no longer available in Android, at least in a Pixel phone, which I happen to own.
Here's the explanation.
https://www.androidpolice.com/2016/...-partition-changes-and-new-fastboot-commands/
Do Oreo Oneplus devices still have cache?
nabbed said:
Excuse me? I thought the Cache partition was no longer available in Android, at least in a Pixel phone, which I happen to own.
Here's the explanation.
https://www.androidpolice.com/2016/...-partition-changes-and-new-fastboot-commands/
Do Oreo Oneplus devices still have cache?
Click to expand...
Click to collapse
Yes it has cache in Oreo, see attached photo
https://www.bestusefultips.com/wipe-cache-partition-on-android-oreo/useatownrisk
dgunn said:
Yes it has cache in Oreo, see attached photo
https://www.bestusefultips.com/link removed
Click to expand...
Click to collapse
That's not the system Cache partition, that sounds like a user app cache. However, Dalvik no longer exists, and ART doesn't have a cache folder, so what that option really does, I don't know. Perhaps it removes cache files for each individual app? When you select that, does it clear cache instantaneously, or does it take 5-10 seconds overall (to go through each app individually?)
Also, please remove that link. It's not only completely inaccurate and written in broken English, but also it's dangerously inaccurate - it gives instructions to "clear cache," but instead, it's for factory reset.
dgunn said:
Yes it has cache in Oreo, see attached photo
https://www.bestusefultips.com/wipe-cache-partition-on-android-oreo/
Click to expand...
Click to collapse
Lol that Photo is from TWRP , coz recovery has that option, and to be clear OP6 do not.
Hi Guys, EIS is not working on my op 6 running OxygenOS 5.1.6 with locked bootloader. is there anything i can do to get it back working
nabbed said:
That's not the system Cache partition, that sounds like a user app cache. However, Dalvik no longer exists, and ART doesn't have a cache folder, so what that option really does, I don't know. Perhaps it removes cache files for each individual app? When you select that, does it clear cache instantaneously, or does it take 5-10 seconds overall (to go through each app individually?)
Also, please remove that link. It's not only completely inaccurate and written in broken English, but also it's dangerously inaccurate - it gives instructions to "clear cache," but instead, it's for factory reset.
Click to expand...
Click to collapse
So what you're telling me is that when I wiped this Dalvik off of my phone and did a reboot that it cleared all of my app cache? Because once I rebooted my phone after clearing the cache my phone began optimizing my apps the same as it always does when I clear system cache from any phone.
I still have Dalvik cache folders on my OnePlus 6 filled with dex, vdex and art files. So unless TWRP deletes all of these files as if it were a cache partition then I have no idea what it does or how it was able to make the phone reconfigure the .dex files
I also did not remove the link I posted instead I appended use at your own risk at the end of the URL so if someone would like to open and read it they can remove the use at your own risk and still see what the link was pointing to for a reference.
Yes indeed it is TWRP so fixing EIS may not be available unless you have custom recovery. Don't be a derp, use TWRP
Related
hey guys, getting an error when I try to clear my cache's on my epic in clock work, I don't remember the exact error but its when i try to clear the davlik cache, it gives me an error that the file already exists? Is this normal? I'm still pretty new at this so any information is definitely helpful.
krazydbiker said:
hey guys, getting an error when I try to clear my cache's on my epic in clock work, I don't remember the exact error but its when i try to clear the davlik cache, it gives me an error that the file already exists? Is this normal? I'm still pretty new at this so any information is definitely helpful.
Click to expand...
Click to collapse
I dunno, When I clean my Davlik, it cleans properly, as do all other cache's on my phone. Perhaps it's a defect?
Sent from my SPH-D700 using XDA App
krazydbiker said:
hey guys, getting an error when I try to clear my cache's on my epic in clock work, I don't remember the exact error but its when i try to clear the davlik cache, it gives me an error that the file already exists? Is this normal? I'm still pretty new at this so any information is definitely helpful.
Click to expand...
Click to collapse
Yes from what I gathered around the forums, this is normal. The fact that it claims that something cannot be mounted / already exists is because it is looking for a component pertaining to froyo. Since we do not yet have this update, it will continue to display that msg. Clockwork dev claims it still wipes the davik cache successfully. If this information is incorrect, please let me know.
Alright, as long as it's normal, just don't want to screw things up. Makes sense if it's designed for froyo.
krazydbiker said:
hey guys, getting an error when I try to clear my cache's on my epic in clock work, I don't remember the exact error but its when i try to clear the davlik cache, it gives me an error that the file already exists? Is this normal? I'm still pretty new at this so any information is definitely helpful.
Click to expand...
Click to collapse
Sounds like not a big deal, if it actually lets you clear the cache your fine. If not, you may just want to not clear it Other than that try flashing back to stock with Odin.
krazydbiker said:
Alright, as long as it's normal, just don't want to screw things up. Makes sense if it's designed for froyo.
Click to expand...
Click to collapse
I always get the same error but it always works.
Clockwork is not clearing my dalvik.
I get "can't mount /dev/blocl/mm3yxxxxxx; file exsists" or something to that effect. I have to clear it manually sans adb or root explorer. Just out of curosity, for a completely clean wipe...what directories should I be clearing? My factory reset works, but what dir should I clear for dalvic and cache? On the norm, I clear /data/dalvik & /data/data/ but still feel I'm missing something.
You only need to clear /data/dalvik-cache. Only rarely do you need to wipe /data
I've flashed a few roms now (masters stock rooted voodoo versions of nexus s firmware) and every time I do the boot logo just keeps on going until I do a battery pull and reboot, and then it's ok.
It's not a problem, I just wondered why this happens??
did you wipe dalvik, factory settings, cache?
did you change the kernel?
zephiK said:
did you wipe dalvik, factory settings, cache?
did you change the kernel?
Click to expand...
Click to collapse
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.
buachaille said:
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.
Click to expand...
Click to collapse
I was asking if YOU did wipe them because if you're going from one ROM to the other ROM you are supposed to wipe.
You lose your settings and apps. Back them up using Titanium Backup (Or any other related app).
Or.. better yet, just perform a nandroid backup. After that, wipe those 3 and reboot. See if the problem is resolved, if it is then you already know. If not then nandroid restore.
If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S
nxt said:
If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S
Click to expand...
Click to collapse
I am new to this so I'm still getting my head around it.
From stock I went to the rooted voodoo version of this - http://forum.xda-developers.com/showthread.php?t=971690.
From there I went to the stock rooted version of this - http://forum.xda-developers.com/showthread.php?t=979851
In both cases it says:
Rom Information:
Does it wipe: No
Does it flash the radio: Yes
So since they don't wipe, I assumed I shouldn't wipe anything, but it looks like I was wrong. From your post it looks like I should have wiped the cache and dalvik cache. I know how to do this in CW but I've never done it and my roms are working fine.
So next time master releases an update I gather I should wipe cache and dalvik cache yeah?
Also, when I do this will it remove any of my settings or apps?
Hope you can answer these questions, and thanks for advice so far.
<<edit>>
Just did a bit of googling and it looks like you don't lose settings when you wipe dalvik cache and cache, so what does actually get removed.
There is a thread stickied in development called ref roms themes and kernels. It gives step by step directions on how to flash all three including what should be wiped. Check it out
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
It says:
Does it wipe: No
Does it flash the radio: Yes
Click to expand...
Click to collapse
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.
EDIT: n/m..............
zephiK said:
It says:
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.
Click to expand...
Click to collapse
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??
buachaille said:
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??
Click to expand...
Click to collapse
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup
zephiK said:
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup
Click to expand...
Click to collapse
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App
buachaille said:
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I can usually get from booting into recovery to having a usable device with most everything set up in about...10 minutes? Assuming I already downloaded the ROM lol sometimes those mirrors are slooooooow.
Hi,
I backed up my phone with Titanium and after updating to 4.0.3 tried to restore data only, from that moment - messaging force closing.
what can I do ?
thanks
Clear any messaging related data, reboot, and then see what happens.
Thanks but it's the same - the app loads and than crashes immediately,
Can I re-download the apk somewhere ?
I know it's core element - but maybe it can be extracted from the whole update ?
Well just to reiterate make sure you wipe all relevant system apps in titanium as that should do it (just want to be sure ).
But you could reflash the rom again, or part of the rom.
And yes you could pull the apps from the rom and install them without reflashing (though you will have to use titanium to make it a system app probably).
Oh yeah you could try wiping the dalvik cache.
tried wiping the dalvik cache did not help. how can I flash only the messaging app ?
Shakty1 said:
tried wiping the dalvik cache did not help. how can I flash only the messaging app ?
Click to expand...
Click to collapse
Well I haven't done such a thing for a while but when I did a similar thing I did it like this:
1. Get full rom zip
2. Open zip with 7-Zip (or similar program).
3. Delete anything you don't want to be flashed again (I guess in your case nearly everything)
4. Flash
Note: I said open the zip, not extract it.
Can't guarantee this will work though I would personally just do a full wipe, flash the whole rom again, and be careful what you restore (i.e. don't restore system data).
Never use Ti to restore data after changing roms. It's the first rule of Flash Club.
Hi all, something I've been doing for many years after any sort of system update, is I clear the system cache partition - just for tidyness, maybe some placebo effect that it helps battery life.
Anyway, it's not where I would expect it to be, any know how to do it?
Non-root, locked bootloader Xperia 5ii.
It should be on the boot menu but on some phones it's oddly found in settings I believe.
Google it.
blackhawk said:
It should be on the boot menu but on some phones it's oddly found in settings I believe.
Google it.
Click to expand...
Click to collapse
I did Google it but it keeps bringing me to older Sony devices. I'm used to it being in recovery boot (Vol - + Power) but I can only see option for a full wipe/system restore.
Lav64 said:
I did Google it but it keeps bringing me to older Sony devices. I'm used to it being in recovery boot (Vol - + Power) but I can only see option for a full wipe/system restore.
Click to expand...
Click to collapse
Yeah I see what you're saying. Call Sony or your carrier.
Hopefully someone knows what going on with this.
Try sd maid pro, It can clean apps cache. Or Twrp wipe.
donkeyman1234 said:
Try sdmaid pro, It can clean apps cache.
Click to expand...
Click to collapse
SD Maid can't touch the system cache and normally has a default value it ignores when cleaning app caches. Best to manually clean suspect ones.
When clearing apk data doing it in Settings can leave what I presume to be nulls behind.
I had an a Android system apk that in Settings I couldn't completely clear it but this app could.
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com
It saved me from a factory reset. Another reason this app is a useful, versatile and powerful tool that I value.
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