Related
Hello,
I will really appreciate if you can help to understand few basic issues:
1) When rooting the phone, is the boot-loader must be unlocked? i.e., if I've rooted the phone successfully using some 3rd party utility, it means that the boot-loader was unlocked during the rooting process or it was unlocked in advanced?
2) If the answer to the first question is "yes" (i.e. bootloader must be unlocked before rooting), how it is possible that my data wasn't wiped after rooting? This means that the boot-loader was unlocked in advance? Or maybe the 3rd party application backed up the data before unlocking the boot-loader and than restored it?
3) I heard that in order to install SU, the stock-recovery must be changed to a custom one. Is it necessarily true?
4) How can I check which recovery is installed on the phone?
5) If the recovery is changed to a custom one, does it mean that I stop receive OTA?
6) Can I backup up the stock recovery before changing it? Or how can I know which one it is to search on the net?
7) Do applications, like Titanium, change the recovery upon installation?
8) How applications, like Titanium, move apps, that are not supposed to move in regular installation,from ROM to SD? Can it harm the performance of the app?
9) When deleting apps from ROM (System or Data) manually, do I need to delete other files or folders besides .apk files in system/app or data/app? Is there any cache or other data to delete?
10) Do I need (or should I in case of lack of space) clean some cache files from ROM? (Like Dalvik or others...) If yes, which ones and how?
Sorry for the long post, but It will really help me to understand all these issues, once and for all.
Thank you in advance!
yuri_feigin said:
Hello,
I will really appreciate if you can help to understand few basic issues:
1) When rooting the phone, is the boot-loader must be unlocked? i.e., if I've rooted the phone successfully using some 3rd party utility, it means that the boot-loader was unlocked during the rooting process or it was unlocked in advanced?
2) If the answer to the first question is "yes" (i.e. bootloader must be unlocked before rooting), how it is possible that my data wasn't wiped after rooting? This means that the boot-loader was unlocked in advance? Or maybe the 3rd party application backed up the data before unlocking the boot-loader and than restored it?
3) I heard that in order to install SU, the stock-recovery must be changed to a custom one. Is it necessarily true?
4) How can I check which recovery is installed on the phone?
5) If the recovery is changed to a custom one, does it mean that I stop receive OTA?
6) Can I backup up the stock recovery before changing it? Or how can I know which one it is to search on the net?
7) Do applications, like Titanium, change the recovery upon installation?
8) How applications, like Titanium, move apps, that are not supposed to move in regular installation,from ROM to SD? Can it harm the performance of the app?
9) When deleting apps from ROM (System or Data) manually, do I need to delete other files or folders besides .apk files in system/app or data/app? Is there any cache or other data to delete?
10) Do I need (or should I in case of lack of space) clean some cache files from ROM? (Like Dalvik or others...) If yes, which ones and how?
Sorry for the long post, but It will really help me to understand all these issues, once and for all.
Thank you in advance!
Click to expand...
Click to collapse
Im sorry but Ive already answered all of these questions and one in fact could take a good couple paragraphs to explain.
Maybe tonight I'll answer or you could check out xda university.
yuri_feigin said:
Hello,
I will really appreciate if you can help to understand few basic issues:
1) When rooting the phone, is the boot-loader must be unlocked? i.e., if I've rooted the phone successfully using some 3rd party utility, it means that the boot-loader was unlocked during the rooting process or it was unlocked in advanced?
2) If the answer to the first question is "yes" (i.e. bootloader must be unlocked before rooting), how it is possible that my data wasn't wiped after rooting? This means that the boot-loader was unlocked in advance? Or maybe the 3rd party application backed up the data before unlocking the boot-loader and than restored it?
3) I heard that in order to install SU, the stock-recovery must be changed to a custom one. Is it necessarily true?
4) How can I check which recovery is installed on the phone?
5) If the recovery is changed to a custom one, does it mean that I stop receive OTA?
6) Can I backup up the stock recovery before changing it? Or how can I know which one it is to search on the net?
7) Do applications, like Titanium, change the recovery upon installation?
8) How applications, like Titanium, move apps, that are not supposed to move in regular installation,from ROM to SD? Can it harm the performance of the app?
9) When deleting apps from ROM (System or Data) manually, do I need to delete other files or folders besides .apk files in system/app or data/app? Is there any cache or other data to delete?
10) Do I need (or should I in case of lack of space) clean some cache files from ROM? (Like Dalvik or others...) If yes, which ones and how?
Sorry for the long post, but It will really help me to understand all these issues, once and for all.
Thank you in advance!
Click to expand...
Click to collapse
1) To my knowledge, yep. (Not much experience with locked bootloaders, sorry!)
2) But then again, different phones have different bootloaders, they might work In different ways.
3) Nope. Most (if not all) root tools install SU without custom recovery.
4) when your phone is powered-off, press Vol up, home and power button (this depends on your phone, this is Samsung standard, what phone are u using?
5) Go to download mode, (Vol down, home and power button, again Samsung standard) and check if: System Status: Official. If yes, OTAs can be taken. If System Status: Custom, you cant take OTAs.
6) U most probably can. Use Online Nandroid Backup, free from Google play store, and backup recovery only. That should work.
7) No.
8) Depends on the app.
9) Again, depends on the app.
10) Cache and dalvik cache can be wiped from recovery. The custom recovery will do it for u. Wiping dalvik cache from recovery won't be useful, as it recreates itself on reboot.
No problem with the long post, always glad to help
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
Thank You
Lgrootnoob said:
Im sorry but Ive already answered all of these questions and one in fact could take a good couple paragraphs to explain.
Maybe tonight I'll answer or you could check out xda university.
Click to expand...
Click to collapse
I would really appreciate if you could answer, or refer me to the correct paragraph in XDA university or give a me a link to your previous answers.
Thank you very much.
Irwenzhao said:
1) To my knowledge, yep. (Not much experience with locked bootloaders, sorry!)
2) But then again, different phones have different bootloaders, they might work In different ways.
3) Nope. Most (if not all) root tools install SU without custom recovery.
4) when your phone is powered-off, press Vol up, home and power button (this depends on your phone, this is Samsung standard, what phone are u using?
5) Go to download mode, (Vol down, home and power button, again Samsung standard) and check if: System Status: Official. If yes, OTAs can be taken. If System Status: Custom, you cant take OTAs.
6) U most probably can. Use Online Nandroid Backup, free from Google play store, and backup recovery only. That should work.
7) No.
8) Depends on the app.
9) Again, depends on the app.
10) Cache and dalvik cache can be wiped from recovery. The custom recovery will do it for u. Wiping dalvik cache from recovery won't be useful, as it recreates itself on reboot.
No problem with the long post, always glad to help
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
Click to expand...
Click to collapse
Thank You for your help.
Regarding the last issue: if I wipe the cache, something bad can happen to the applications ot their data? I mean, should I do it only when flashi rom or is it healthy to do it in a while in order to clean unnecessary files?
yuri_feigin said:
Thank You for your help.
Regarding the last issue: if I wipe the cache, something bad can happen to the applications ot their data? I mean, should I do it only when flashi rom or is it healthy to do it in a while in order to clean unnecessary files?
Click to expand...
Click to collapse
The cache is actually a temporary section of the disk that does not contain any application cachery but things along the lines of software upgrade files. It is only wiped merely to make sure there is space for other mod's temp storage.
The data partition contains the data for yourr applications and the 'cache' as you see in settings for apps is for imagery and stuff so regardless if that is removed it wont matter.
The dalvik cache is compiled bytecode for the dalvik vm for each app. (Look up Java vm to get an idea of what I mean and then look up odexing and deodexing on xda university)
Here is some info on the thread http://forum.xda-developers.com/showthread.php?p=48151745#post48151745
Lgrootnoob said:
The cache is actually a temporary section of the disk that does not contain any application cachery but things along the lines of software upgrade files. It is only wiped merely to make sure there is space for other mod's temp storage.
The data partition contains the data for yourr applications and the 'cache' as you see in settings for apps is for imagery and stuff so regardless if that is removed it wont matter.
The dalvik cache is compiled bytecode for the dalvik vm for each app. (Look up Java vm to get an idea of what I mean and then look up odexing and deodexing on xda university)
Here is some info on the thread http://forum.xda-developers.com/showthread.php?p=48151745#post48151745
Click to expand...
Click to collapse
Thanks a lot!
I have few more questions, please:
1) So what will be the best way to clear the cache partition? Only from recovery? Even from stock recovery?
Is there any other way, like a feature in some application or can I delete it manually?
2) Regarding the data partition, I guess I can go each application and clear its cache and/or data from application manager... Is there a better way? By away, if I delete the data of application (not the cache), I loose all the configuration and personal data. What I mean by "cleaning" is to erase some false data that remained by mistake, not to remove the necessary data of the apps. It is especially important for apps installed on ROM. What will be the best way?
3) Is sometimes remains unnecessary junk data in Dalvik Cache? If yes, how to remove it? (not the all Dalvik Cache)?
4) By away, what is the best way to check whether my bootloader is unlocked and to check which recovery is installed? (custom/stock)
5) If I want to mess with the start-up task manager, using some ROM application - what are the "receivers" that are connected to the apps? what is the difference between disabling an app/task/service and disabling receivers?
6) What is the difference between recovery boot mode and bootloader boot mode? When do I need to use the bootloader mode?
6) And another question, with your permission, is what kind of backups are exist beside nandroid? ADB is a backup? Do they back up all the ROM? I guess I will need a custom recovery to restore those backups.
yuri_feigin said:
Thanks a lot!
I have few more questions, please:
1) So what will be the best way to clear the cache partition? Only from recovery? Even from stock recovery?
Is there any other way, like a feature in some application or can I delete it manually?
2) Regarding the data partition, I guess I can go each application and clear its cache and/or data from application manager... Is there a better way? By away, if I delete the data of application (not the cache), I loose all the configuration and personal data. What I mean by "cleaning" is to erase some false data that remained by mistake, not to remove the necessary data of the apps. It is especially important for apps installed on ROM. What will be the best way?
3) Is sometimes remains unnecessary junk data in Dalvik Cache? If yes, how to remove it? (not the all Dalvik Cache)?
4) By away, what is the best way to check whether my bootloader is unlocked and to check which recovery is installed? (custom/stock)
5) If I want to mess with the start-up task manager, using some ROM application - what are the "receivers" that are connected to the apps? what is the difference between disabling an app/task/service and disabling receivers?
6) What is the difference between recovery boot mode and bootloader boot mode? When do I need to use the bootloader mode?
7) And another question, with your permission, is what kind of backups are exist beside nandroid? ADB is a backup? Do they back up all the ROM? I guess I will need a custom recovery to restore those backups.
Click to expand...
Click to collapse
1: Only recovery.
2: "Cleaning" is not possible So the application manager is the only way and yes it would basically reset an application if you delete its data.
3: Its not necessary but can save space for more apps to be installed if you have removed apps manually or with titanium backup. However if you have uninstalled with the app manager in the settings app then the dex files in the dalvik cache are automatically removed. "Unnecessary junk", I have exactly what you are looking for: use Titanium backup's feature in the menu to remove unsused dalvik cache elements and integrate system dalvik into rom. (In the same section when you press the menu button)
4: What phone? (This is neccessary because of the variation in phones.)
5: The only legitimate way of stopping tasks is to disable the intent of the task(I think that is the reciever ). To do this you could use Autostarts from the Play store or you could use the Bootmanager Xposed module. Don't use any task manager unless you want problems. Disabling an app in settings would actually completely freeze the application meaning you could also not start it manually and it wouldnt be started at boot.
6: The bootloader loads recovery or Android. The bootloader is usable depending on the features given by your phone manufacturer. You would know the difference when you use recovery and if you have a Nexus device when you are in bootloader mode. Samsung devices have Download mode which is technically part of the bootloader and allows you to load custom software such as recovery, data partition, system partition etc.
7: You will use recovery to backup/restore.(I don't think that there is any other way because you are using the data that you are backing up or restoring if you didi it while you were running android. Adb cannot backup either but you could pull a recovery backup with adb from the sd card. Adb has a sideload feature for loading software in recovery with your computer. Again I need your phone model.
It seems you seek info on recovery and backing up, This will help a lot: http://xda-university.com/as-a-user/android-dictionary Specifically the Nandroid and Recovery section.
I will be more than happy to expand on any of these topics.
@yuri_feigin
I revised my answer to better suit what you were asking.
Are you still with me?
Hi!
I did search and was hoping to find a 'Titanium Backup' section within XDA all I saw where threads in various sections. So if there is one and I should be posting there just let me know!
I will explain my situation;
I'm have a Nexus 5 that is unlocked and rooted. Within Google's update last night I had to reboot my phone and all of a sudden com.android.ui force closes and nothing worked. I wasn't able to tap on any app, app draw, dock .. nothing.
Here's where my ignorance comes to play. Could I have restored my phone from a backup which was only 3 days old without having to wipe it?
Yeah, I wiped the phone, re-rooted and let all the Google apps update and I'm bringing down my Titanium backup from the cloud to the device to restore my apps from it.
So could I have done this in a better way? If there is the next time I'll do it!
And is there some definitive guide on Titanium Backup? I followed a YouTube tut and it appeared to be have captured what I needed but I feel that there's more to it! I just feel I should be using that app to backup more than just my apps + data.
Hope you can help!
Thanks!
Dave
MrBiggzz said:
Hi!
I did search and was hoping to find a 'Titanium Backup' section within XDA all I saw where threads in various sections. So if there is one and I should be posting there just let me know!
I will explain my situation;
I'm have a Nexus 5 that is unlocked and rooted. Within Google's update last night I had to reboot my phone and all of a sudden com.android.ui force closes and nothing worked. I wasn't able to tap on any app, app draw, dock .. nothing.
Here's where my ignorance comes to play. Could I have restored my phone from a backup which was only 3 days old without having to wipe it?
Yeah, I wiped the phone, re-rooted and let all the Google apps update and I'm bringing down my Titanium backup from the cloud to the device to restore my apps from it.
So could I have done this in a better way? If there is the next time I'll do it!
And is there some definitive guide on Titanium Backup? I followed a YouTube tut and it appeared to be have captured what I needed but I feel that there's more to it! I just feel I should be using that app to backup more than just my apps + data.
Hope you can help!
Thanks!
Dave
Click to expand...
Click to collapse
Hi Dave,
Unfortunately I would suggest to do first a wipe cache/dalvik cache before trying a factory reset.
Restoring apps system with Titanium is not really recommended (become worst than before). I tried and had many force close on system ui during the test.
regards,
P.
pfloc said:
Hi Dave,
Unfortunately I would suggest to do first a wipe cache/dalvik cache before trying a factory reset.
Restoring apps system with Titanium is not really recommended (become worst than before). I tried and had many force close on system ui during the test.
regards,
P.
Click to expand...
Click to collapse
I'm bit past that point. I wasn't restoring system app .. just user apps + data. That's one thing that I caught on to when I was learning about backup up was things NOT to backup and system apps where one!
Somebody in the G+ Xposed community told me to wipe cache was well. And my reply was the same that if the UI has force closed and nothing is responsive then how can I do this?
You'll have to pardon my ignorance as this is the first time I've encountered a problem like this. I've been pretty blessed so far! =)
MrBiggzz said:
And my reply was the same that if the UI has force closed and nothing is responsive then how can I do this?
Click to expand...
Click to collapse
does the Nexus 5 comes which a standard recovery where you can do it ... otherwise install a custom recovery.
but if you could access to titanium application with the constant popup, it has a option to clean cache.
good luck
pfloc said:
does the Nexus 5 comes which a standard recovery where you can do it ... otherwise install a custom recovery.
but if you could access to titanium application with the constant popup, it has a option to clean cache.
good luck
Click to expand...
Click to collapse
The other source I'd tapped told me since I have a custom recovery that I able to wipe cache and dalvik cache as well. This person has had the same issue.
So ... I learned something new today! =)
Hope you will get a full functional phone after that
also don't backup/restore system app files/ ie messaging> call log etc between different versions or different types of android
digijedi007 said:
also don't backup/restore system app files/ ie messaging> call log etc between different versions or different types of android
Click to expand...
Click to collapse
Yep, I said that third post down! =)
Only thing was I was expecting to be able to restore from the cloud. Instead I had to copy everything from the cloud back down to the phone.
Phone works though.
But in my case I was told to get into recovery which I had done but after that had no idea what to do. Wiping and restoring was a bit premature.
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
Last night i upgraded from nougat to oreo and applications start to crash.
And in some games i can't even log in with facebook / twitter. Everytime time i hit the login with facebook/twitter button, the game crash.
Torrent application not showing any text / pic.
The battery is not draining fast, but faster than nougat's.
Some application don't make to their page. Some do, but few seconds later *crash*.
Octopus' (keymapping app) service is running but the app always crashes when i try to run it.
SmartThings, sometimes bluetooth keyboard and mouse stop working.
I tried factory reset on setting, clearing cache on recovery mode. Nothing works.
I appreciate any help!
Uninstall and reinstall the apps, or clear data and not just cache in app manager.
Personally I always do a clean wipe on new OS versions partially because of this reason, you bring up old data from the previous version and often causes issues.
Beanvee7 said:
Uninstall and reinstall the apps, or clear data and not just cache in app manager.
Personally I always do a clean wipe on new OS versions partially because of this reason, you bring up old data from the previous version and often causes issues.
Click to expand...
Click to collapse
I did factory reset through setting menu, should i try hard reset?
Ah I thought you meant you reset the app settings. But yes a factory wipe in recovery is going to be more thorough than one through settings.
Other wise you can do a full flash in Odin using the stock firmware files, that method doesn't trip knox / warranty etc
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