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!
Its been a while now, the issue probably triggered when I tried to set up multirom and install Marshmallow a few months back. I do not run multirom anymore, and even if I do a clean install (factory reset), when the phone first boots, it shows the "Android is starting" screen with "Optimizing x of 136" and takes a good 5 minutes. Why is this happening? After a factory reset I have no apps installed! I have deleted the multirom folder as well as the sdcard/Android/data folder, in case its picking up the app data in these folders to optimize. Is there something I'm missing?
Because when you flash a ROM or factory reset your device, Dalvik / ART cache gets wiped. While optimizing apps it gets created again...
I think goldengargoyle is baffled why there are 136 apps for optimization, when he erased all his data, including apps. This actually annoys me also, should't there be only a few(10-30) default apps to optimize?
goldengargoyle did you figure it out? I did the same now and i was not expecting to have 140+ apps optimizing ...
goldengargoyle said:
Its been a while now, the issue probably triggered when I tried to set up multirom and install Marshmallow a few months back. I do not run multirom anymore, and even if I do a clean install (factory reset), when the phone first boots, it shows the "Android is starting" screen with "Optimizing x of 136" and takes a good 5 minutes. Why is this happening? After a factory reset I have no apps installed! I have deleted the multirom folder as well as the sdcard/Android/data folder, in case its picking up the app data in these folders to optimize. Is there something I'm missing?
Click to expand...
Click to collapse
To truly ensure the issue is fixed, back up what you need from the phone and fastboot flash a stock rom (preferably one of the last builds), let it boot then, go though the set up as you typically would, transfer the rom and other things you would like to flash to the phone, fastboot flash TWRP and finally, flash whatever you transferred.
Hello
I'm trying to update from 41.2.A.7.35 to 41.A.7.53 using flashtool. I am relatively familiar with Flashtool at this point. I have installed stock firmwares a couple of times. Each time I have flashed a firmware i checked all boxes in the "Wipe" pane giving me a fresh install.
What i was curious about was, how can i prevent from formatting my drive each month when a new update rolls out. So what setting do i leave checked and unchecked in the flashtool? I'm mostly concerned with retaining apps and appdata along with settings and messages.
Thank you
I normally mark all in wipe section. Today i flash customized AU without problems.
normally no wipe neccessary
Hummusman said:
how can i prevent from formatting my drive each month when a new update rolls out. So what setting do i leave checked and unchecked in the flashtool?
Click to expand...
Click to collapse
If you do not upgrade the Android version, or go from 39... to 41... or you have "strange" behavior before or after the upgrade: do not wipe anything
Some partitions like /system are overwritten anyway. If you are root you might get away with wiping cache/dalvik if anything feels strange.
When switching ROMs or upgrading Android versions I use Titanium backup to shorten the process:
- look for unsaved apps after upgrade -> bloat candidates, let TB delete deal with them after looking at the list and deciding what to let go
- restore all user apps with data
- manually restore all logins of apps that have accounts e.g. email (the time consuming part)
I use Apex launcher and its setting are restored too, so I will have a familiar look and feel even on a different ROM.
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