Related
Hi i dont know if its just me but i was doing somethin with system app but for some reason i gets wrong and i dont have a nandroid backup yet so i decide to factory reset all goes ok but when i finishes setting up the account and language i got an error its says unfortunately setup wizard has stopped, but lucky i enter playstore and install apex and all its ok so the app wich let me do that was google search but after factory reset i didnt have it so i installed from play store and make it a system app with titanium, is this ok or not, i fell a bit slower the device jeje or nothing happens with this conversion of a user app to a system app? sorry for my english
Well, actually a factory reset is nothing more than deleting the user's data. Files which are stored in the system partition stay untouched. So your modification is still present even after "factory resetting".
Best thing you can do to totally reset it: Download the latest (4.4.2) factory image for "hammerhead" (=Nexus 5 codename) from Google and flash it. It contains all partitions and resets them to it's original state There are tutorials out there on how to flash a factory image
Oh but thats all i did just uninstalled google search and backup with TB but for some reason it doesnt let me to restore it so i have to do the factory reset! but now i installed as a system app is there a big problem with touching that app?=?
Okay, let me summarize what you did:
1) You messed around with system apps.
2) You don't have a Nandroid-Backup - so you choose to factory reset your phone <- Which actually doesn't revert your modifications since the "system" partition remains untouched.
3) You set up your phone again but the system wizard keeps crashing.
4) You installed Apex Launcher and it fixed this problem.
5) Google Search isn't available after the factory reset, so you download it from Play Store and make it a system app.
6) Now your system feels slower in general.
--> Is that correct?
If yes, what exactly do you want to have now? Reset your phone like it was on the first day?
And why did you touch system apps at all? What did you want to modify?
Greets,
experience7
Google now stopped working thats why i touch google search jeje
Enviado desde mi Nexus 5 mediante Tapatalk
I can only recommend to completely reset your phone by factory image. Trust me, it will remove all your problems!
Hello,
I've been trying to undo the mcs_heartbeat changes I've applied while my Nexus 5 was on KitKat, but the app Push Notification Fixer is not compatible with Lollipop, so I tried to directly uninstall Google Play services via Titanium Backup, to then have a clean reinstall and convert to system app again. In this last process however, TB seemed to become non responsive while it was converting it to system app, so I decided to force a reboot after 5~ mins.
Now every time it reboots after I see around 2 secs of the lock screen.
Tried to restart into safe mode, same thing. At this point, scared, I decided that I'd be willing to lose all the data if it meant have the phone working again, so I tried a format, but that seems to just not work, after a while it simply reboots normally to the same bootloop. It won't get past "Formatting /data..."
Another problem is that I usually keep USB debugging off because it makes winamp music transfer not work, so I don't have it. I'm really a beginner, so the solution might be simpler than I can imagine, but could anyone please help?
edit: formatting went through, but it clearly didn't solve the problem, as it now keeps rebooting as soon as a glimpse of status and navigation bar are seen (for 0.5s max, on a full black background).
halp, what do why doesn't formatting restore everything to how it should be?
1.Download factory image from google ,
2. download and install fastboot/adb drivers (there's a pack on this forum that only requires 3 clicks)
3. Unzip the factory image archive
4. connect phone to pc , reboot to bootloader ( press and hold volume down and power ) ,
4.a type in a command window , from the folder where u have fastboot.exe "fastboot devices" -quotes . If you get a long string of numbers everything is fine
4.b if your bootloader isn't unlocked , type in a command window
fastboot oem unlock
5. run the flash-all.bat from the folder where you unzipped the archive
6. wait
7. wait some more
8. phone should reboot full stock.
Factory reset doesn't touch your modification , nor does it restore corrupted files. All it does is delete your app storage , settings and cache.
Um, sorry if this sounds annoyingly silly, but if I do factory reset on my Nexus 5, will that delete all of my pictures, PDF document, videos, music, etc2?
I am aware that the app will be wiped clean like how the phone is first received, but I'm not sure if factory reset will also delete all of my stuffs I mentioned above.
I got stuck in boot because I think I have too much app on my phone.
dvdlesher said:
Um, sorry if this sounds annoyingly silly, but if I do factory reset on my Nexus 5, will that delete all of my pictures, PDF document, videos, music, etc2?
I am aware that the app will be wiped clean like how the phone is first received, but I'm not sure if factory reset will also delete all of my stuffs I mentioned above.
I got stuck in boot because I think I have too much app on my phone.
Click to expand...
Click to collapse
Yes it will
Sent from my Nexus 9 using XDA Free mobile app
Hi guys,
Unfortunately my Nexus 5 kinda died on me today and I'm almost devastated. The phone froze and then restarted (I pressed the power button a couple of time, so I’m not sure if I restarted it or it did it by itself) and stayed stuck on the Google logo screen. I tried a couple of things but none works – booting it in recovery -> wipe partition cache; shutting it down and restarting it; leave it like that and praying to God…
I need your help. What can I do in order to fix this and keep my personal data on the phone – apps (with their data – I have a couple of journaling apps that are very important to me), messages, pictures, history, calls and so on…
The most important thing for me is to retrieve this data, so a factory reset is out of the question. Is there any way I can fix this? If not, how can I recover/retrieve all my data from the phone?
P.S. I'm using the latest Android OS, without that last OTA update, the booloader is unlocked and stock...
You could flash twrp, create a nandroid backup, copy the backup to your phone for safe keeping, restore the backup to an identical phone (you'll have to change the serial number of the backup to the phone that will be used for the restore), and hope it all works.
If you don't have access to an identical phone, you could try wiping the phone and restoring the backup.
You could flash twrp and copy off the important data.
Lastly, you could flash a stock rom, flash twrp, and restore your data and apps.
audit13 said:
You could flash twrp, create a nandroid backup, copy the backup to your phone for safe keeping, restore the backup to an identical phone (you'll have to change the serial number of the backup to the phone that will be used for the restore), and hope it all works.
If you don't have access to an identical phone, you could try wiping the phone and restoring the backup.
You could flash twrp and copy off the important data.
Lastly, you could flash a stock rom, flash twrp, and restore your data and apps.
Click to expand...
Click to collapse
Thank you for your kind and quick reply. I'm almost a complete android illiterate so I will bug you with a couple more questions, just for a better understanding.
So flashing TWRP means installing it...
1. Am I able to do this, considering the state of my phone? And will I be able to do the nandroid backup?
2. Is this tutorial good? http://www.xda-developers.com/how-to-install-twrp/
3. My phone is not rooted. Does this matter?
4. My phone has a capacity of 15 gb, of which approx. 1.5 gb were left free... Will I still be able to do the backup?
Thank you
The TWRP tutorial should be good - it's an XDA post...
You don't have to install TWRP, though it's a good idea unless you really don't want it. You can run it temporarily and on the next boot you'll be back to normal stock recovery. Booting temporarily will allow you to make a backup, but the risk is that you also back up the problem and then restoring the backup will also restore the problem - but it's worth a try.
"3. My phone is not rooted. Does this matter?" No, TWRP doesn't need root.
"4. My phone has a capacity of 15 gb, of which approx. 1.5 gb were left free... Will I still be able to do the backup?" Probably not - a backup is probably about 3GB, but if you manage to get as far as connecting to your PC and seeing your internal storage in Windows Explorer, you can copy the essential data (photos, etc.) to the PC and then do the backup and attempt the restore.
Press power & volume down simultaneously until you get to the bootloader screen with the green robot on its back. Connect the device to the PC - I'd recommend a direct laptop connection, not via a USB hub.
Start a CMD window and navigate to your PC adb/fastboot directory.
Type "fastboot devices" (no apostrophes) - if you're properly connected, you'll see something like "459uirgggg4 fastboot", which is your device id. A blank line means no connection.
To boot TWRP temporarily - "fastboot boot twrp.img".
To install TWRP permanently - "fastboot flash recovery twrp.img".
Once complete, use the volume keys to find "Reboot recovery". When you're in recovery, with any luck you may be able to see your internal storage in Windows Explorer, and you can at least retrieve your data. You could then try the restore, and if it doesn't work, a full installation of the latest ROM and rebuild your device from there (though Google automatically restores most of your apps if you had chosen that option).
Double-check these commands against other posts - I offer no guarantees, but at least a bit of hope...
Good luck.
Thank you! One more quick question, if I get as far as connecting and seeing my internal storage, would I be able to erase some data, in order to make room for the backup?
Yes, that's exactly what I meant. Photos are simple to identify, take up quite a lot of room, and can easily be transferred to your PC for safety and then deleted from the device. Anything free-standing (i.e. photos, for example, are independent of the app which captured them) and easily-identifiable, copy and delete from the device. Things like SMSs are trickier, since they may be held in not-obvious places or formats. If you take a copy to your PC, and delete to free space, you may have enough space for the backup, but as I mentioned you may just be backing up the problem as well as the system (backups don't tend to copy user data).
dahawthorne said:
Yes, that's exactly what I meant. Photos are simple to identify, take up quite a lot of room, and can easily be transferred to your PC for safety and then deleted from the device. Anything free-standing (i.e. photos, for example, are independent of the app which captured them) and easily-identifiable, copy and delete from the device. Things like SMSs are trickier, since they may be held in not-obvious places or formats. If you take a copy to your PC, and delete to free space, you may have enough space for the backup, but as I mentioned you may just be backing up the problem as well as the system (backups don't tend to copy user data).
Click to expand...
Click to collapse
Okay, here's the current situation - I managed to connect it to my pc and it's visible.
I saved my photos and cleared up some space. I now have 9 GB of available memory.
I tried TWRP (didn't install it though, as I receive an error, saying that it can't complete the command) and manage to boot it and enter the backup menu.
Unfortunately, it cannot backup my data, as it remains stuck on "updating partition details"...
Not sure what to do... Should I wait longer? It stayed like that for approx. 50 min, before I restarted it. Should I try a previous version of TWRP? Should I try a different program/method of doing a nandroid backup?
Also, there were options to backup my: system, cache, data, boot etc. Choosing to backup only my data would do the trick? As I said, I'm most concerned about my journaling apps, that were not backed up.
Anyways, here is something interesting that happened after I restarted it during the TWRP stuck backup process - the phone started and passed the google logo screen! And I managed to enter it. Things appeared to be normal and I was overwhelmed by hope. However, when I tried to open an app, it froze and started all over again. And one more detail, the battery was low, like 10%. It was low yesterday, too, when it died the first time. Could it be related? Do you guys make anything out of this? Should I proceed by backing up my data and flash a new OS?
Nice to see some progress...
The first thing to do is to get the battery properly charged. Some functions (I'm thinking specifically of encryption, which demands at least 50% charge plus the device plugged in) won't work properly on a low charge. It may not be the cause, but it certainly won't help if the battery is low.
9GB is now plenty to take an entire backup. The TWRP backup screen shows how much data is in each partition. I'm not entirely sure exactly what "data" does back up - I very much doubt (from experience) that it will back up things like photos, but as I said before some data is stored in obscure places and you may be lucky. Back up everything except cache - the defaults in 3.0.2.
Definitely back up EFS. Read around and see the havoc it causes if you have problems and don't have it backed up.
So... you temporarily booted into TWRP? Latest 3.0.2? And the "updating partition details" message was after you pressed the backup button? There shouldn't be any delay - my backups of 6GB on my N6 take only 5 minutes - the N5 is slower but not that much slower, and you have a lot less to back up. If TWRP still continues to be difficult, yes, try the previous version. Even back to a version 2 if necessary.
Try the backup when the device is charged, save it to your PC, and then reboot. Fingers crossed. Good luck.
dahawthorne said:
Nice to see some progress...
The first thing to do is to get the battery properly charged. Some functions (I'm thinking specifically of encryption, which demands at least 50% charge plus the device plugged in) won't work properly on a low charge. It may not be the cause, but it certainly won't help if the battery is low.
9GB is now plenty to take an entire backup. The TWRP backup screen shows how much data is in each partition. I'm not entirely sure exactly what "data" does back up - I very much doubt (from experience) that it will back up things like photos, but as I said before some data is stored in obscure places and you may be lucky. Back up everything except cache - the defaults in 3.0.2.
Definitely back up EFS. Read around and see the havoc it causes if you have problems and don't have it backed up.
So... you temporarily booted into TWRP? Latest 3.0.2? And the "updating partition details" message was after you pressed the backup button? There shouldn't be any delay - my backups of 6GB on my N6 take only 5 minutes - the N5 is slower but not that much slower, and you have a lot less to back up. If TWRP still continues to be difficult, yes, try the previous version. Even back to a version 2 if necessary.
Try the backup when the device is charged, save it to your PC, and then reboot. Fingers crossed. Good luck.
Click to expand...
Click to collapse
Dahawthorne, thank you! I managed to make a backup after following your suggestion regarding the battery.
However, I didn't do a factory reset... not yet. Something strange happened while I tinkering with it (basically starting it and shutting it down with a furry) - it entered the OS! And everything was there and seemed to be fine, I was able to access my apps and saved a couple of things. But... when I clicked on a web page, it froze again and I was back at square one. Could it be that I have too many tabs/web pages in the background?
If it's only Chrome (or other browser?) that's making it freeze, you might want to try installing a different browser.
In the meantime, given your situation, I'd concentrate on recovering all the data you want and copying it to your PC for safety in case you have to resort to a factory reset or full re-flash of the ROM.
In case you can't find the data for the reasons I originally mentioned, you could try the Play Store for backup applications - e.g. there's a good SMS backup app which will back up & restore your texts. There may be something similar for your journaling app.
(And what's a "furry"...? )
I need help with removing popup ads, they have a x in the top right, i never encountered this before and it's our of the blue, i have no out of the ordinary app, i have went through and looked at every app, i don't know what's causing it, i have factory reset, i have odin, i reflashed rom, it still pops up, random ad, it seems to go away, i don't understand,
If you really wiped or did a real factory reset, usually the /data partition is been erased, where the apps and those data are been stored.
Imho there are two possibilities:
a)your phone were rooted and some kind of bloat-adware has been installed somehow as system software (partition /system)
b)after factory reset, one of the APKs you are installing successively contains malware (did you checked "untrused source" for apk installing?
Anyway, a full wipe and reinstall of any stock/cfw should fix this behaviour.
Disable Google restore when you first boot after resetting or it'll install the same apps again
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