Related
My Device Info:
Rooted, AT&T Galaxy Note 2 running 4.1.2...no custom ROMs, kernals, tweaks or mods, etc...
The Issue:
I've been ignoring the latest OTA update that AT&T has been pushing since my device is rooted. However, unbeknownst to me at the time, my phone got into my toddlers hands last night and I'm assuming he accidentally pressed something that caused the download process to begin.
What I've Tried So Far:
The phone will boot up like normal, but when I try to select anything then the screen goes black showing nothing but the notification bar. Then after a few seconds the phone auto-reboots itself. Sometimes it hangs on the Samsung splash screen while I hear notifications going off in the background. From recovery, I've selected to wipe data/factory reset and wipe Dalvik cache, but no change. I had one Clockwork mod backup on my extSDcard that won't restore giving me and MD5 mismatch error. It was only from a couple weeks ago so it was created from this device. I'm a relatively seasoned Android OS tweaker but its been a while since I've been actively doing anything but rooting. I need some suggestions as to how I should proceed....thanks in advance
Momomuffins said:
My Device Info:
Rooted, AT&T Galaxy Note 2 running 4.1.2...no custom ROMs, kernals, tweaks or mods, etc...
The Issue:
I've been ignoring the latest OTA update that AT&T has been pushing since my device is rooted. However, unbeknownst to me at the time, my phone got into my toddlers hands last night and I'm assuming he accidentally pressed something that caused the download process to begin.
What I've Tried So Far:
The phone will boot up like normal, but when I try to select anything then the screen goes black showing nothing but the notification bar. Then after a few seconds the phone auto-reboots itself. Sometimes it hangs on the Samsung splash screen while I hear notifications going off in the background. From recovery, I've selected to wipe data/factory reset and wipe Dalvik cache, but no change. I had one Clockwork mod backup on my extSDcard that won't restore giving me and MD5 mismatch error. It was only from a couple weeks ago so it was created from this device. I'm a relatively seasoned Android OS tweaker but its been a while since I've been actively doing anything but rooting. I need some suggestions as to how I should proceed....thanks in advance
Click to expand...
Click to collapse
In Settings/About Device: you can tell which build you have or if you had the update or not. The phone was prolly shipped with MA4..or MC3. The newer update was MH3.
I don't know if updating if would cause that issue though.
Mebby it's something that the toddlers did or coincidental hardware issue.
You might need a reset from in the device..under Setting/Backup Reset..this may erase all you data and info on the SDCard
If you are still having issues...mebby an Odin back to stock MA4 and test again
qkster said:
In Settings/About Device: you can tell which build you have or if you had the update or not. The phone was prolly shipped with MA4..or MC3. The newer update was MH3.
I don't know if updating if would cause that issue though.
Mebby it's something that the toddlers did or coincidental hardware issue.
You might need a reset from in the device..under Setting/Backup Reset..this may erase all you data and info on the SDCard
If you are still having issues...mebby an Odin back to stock MA4 and test again
Click to expand...
Click to collapse
Once the phone boots and the pre-home screen displays ready to swipe. Once I swipe, like I'm trying to access the home screen, the entire display goes black except the status/notification bar. If I power off the screen and back on again, the swipe screen displays again, swipe it again, it goes black again. The status bar, volume selection pop-up display on the screen are responsive and functional. I just can't navigate through the phone whatsoever past the swipe screen. It's like the home screen UI/launcher doesn't exit. Previous to the problem, I was running Smart Launcher Pro with no problems....this is by far the weirdest issue I've ever run across
Momomuffins said:
Once the phone boots and the prOute-home screen displays ready to swipe. Once I swipe, like I'm trying to access the home screen, the entire display goes black except the status/notification bar. If I power off the screen and back on again, the swipe screen displays again, swipe it again, it goes black again. The status bar, volume selection pop-up display on the screen are responsive and functional. I just can't navigate through the phone whatsoever past the swipe screen. It's like the home screen UI/launcher doesn't exit. Previous to the problem, I was running Smart Launcher Pro with no problems....this is by far the weirdest issue I've ever run across
Click to expand...
Click to collapse
It could be a launcher issue.. perhaps an inverted color scheme
Flash a different launcher or rom in cwm..or odin to stock
Or push a different launcher then install and reinstall your own
qkster said:
It could be a launcher issue.. perhaps an inverted color scheme
Flash a different launcher or rom in cwm..or odin to stock
Or push a different launcher then install and reinstall your own
Click to expand...
Click to collapse
Just did Odin to Stock...successful...BUT the phone booted up and I have the "Android is upgrading...<starting apps.>" box...its been sitting there for at good 15min+...
Also...once the screen went black earlier the phone would reboot even after wiping it clean of absolutely everything...something somewhere got seriosuly borked...
Momomuffins said:
Just did Odin to Stock...successful...BUT the phone booted up and I have the "Android is upgrading...<starting apps.>" box...its been sitting there for at good 15min+...
Click to expand...
Click to collapse
***UPDATE***
Pulled the battery and booted into stock recovery....wiped data/factory reset/wipe cache...reboot...I was able to nav further into the UI than I was previously able to like into the SMS app and system settings then BAM...auto-reboot again and the famous "Android is upgrading..." box is back...sitting there...again...this is insanity...it's no longer rooted, stock firmware, no data aside what's generated during the initial device set-up... SAME shiz as far as the reboot and the spontaneous, hanging OTA upgrade...
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.
Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.
Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.
I really apologize if this in the wrong section, or forum, but I am very worried. Earlier I was messing around and I tried flashing the Xposed framework for lollipop. I have TWRP and I made a nandroid backup, I flashed it, all was well, and I rebooted. Well It was hanging for a while, too long, on the cyanogenmod booting screen. It was active, it wasnt frozen, the circle kept coming out from the logo.
I was like "damn, it must not have worked." So I powered off, hopped into recovery, and flashed the nandroid backup I had made.
Well now I have the same problem, It gets to the logo, and continuously flashes the circle, just nothing ever happens. Ive had it trying to boot for probably 10 mins now while I am typing this. I can get to recovery no problem, and have nandroid backups made, so I mean there has to be a way to fix it.
Can anyone help? Also, I'm working with a mac computer but I can pull up parallels desktop if need be.
Thanks in advance.
ALSO,
Where can I download a stock rom for 4.4.2 for The Galaxy Tab 8.4 T320
The only link I found is on some weird 3rd party website and is gonna take 9 hours to download. It is a .zip file and I need it to be able to work with odin, so hopefully there is a .tar in the zip correct?
All this crap because of stupid Xposed. omg.
Sorry guys, im freaking out.
Also, I think I have an idea why it wont boot..
I cannot clear the Cache, or the dalvik cache. It says "E/ Failed to mount : ' Cache" and same for dalvik cache.
And When I try to "repair filesystem" it also cannot mount cache and says the cache size it 0, and free space is 0. Someone please help. I don't want to cry myself to sleep tonight.
Also, I am downloading a stock rom right now, but it is one from Canada, I couldnt find one from the USA. But it was the one with the most downloads, so it doesnt matter where it's from as long as it is for my model, SM-T320, correct?
NOBODY, has any suggestions? God I'm gonna end up trying this on my own and ending up with a hard brick. Please, out of any of the 30 people who have viewed this, anybody?! :/
-Disregard this post-
I did it, ****ers!
Thanks for all the help!
As in, I flashed the stock rom with odin, and It was sucessfull.
Then I flashed TWRP and restored my nandroid. All was well.
A little late since you fixed it, but for future reference incase someone else has the problem.
XAR firmware is for the USA wifi models,
you could also flash with Samsung kies back to stock (downloads off samsung servers), though odin works too.
you could of disabled xposed with this command line if you had a custom recovery like twrp,
TWRP - Advanced - Terminal command
touch /data/data/de.robv.android.xposed.installer/conf/disabled
There is also a key combination that can disable it too not sure if it works with the lolipop beta though
http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9883
Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
Click to expand...
Click to collapse
otyg said:
A little late since you fixed it, but for future reference incase someone else has the problem.
XAR firmware is for the USA wifi models,
you could also flash with Samsung kies back to stock (downloads off samsung servers), though odin works too.
you could of disabled xposed with this command line if you had a custom recovery like twrp,
TWRP - Advanced - Terminal command
touch /data/data/de.robv.android.xposed.installer/conf/disabled
There is also a key combination that can disable it too not sure if it works with the lolipop beta though
http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9883
Click to expand...
Click to collapse
Thanks man, but I think my whole problem was something was corrupted with the Cache, it said I had 0 cache memory, with 0 free,
And I couldnt clear the cache, or dalvik cache for the life of me. Or even mount it for that matter.
I'm really thankful for all the posts I found on this website though, that's where I got the idea to flash it with Odin.
I'll try this again (this website crashed when first posting this)
Leased phone (January 2017) use for my business. Has had (3) OTA updates since April. Started having issues after 3rd update mid-June (freezes / reboots). Most times have to pull the battery to get it to boot. Have wiped & restore several times, from Settings and Recovery boot menu. Cleared App cache and partition cache. Had the local Sprint Store 'supposedly' flash the OS from a PC but nothing improved. Described these issues below but was only met with a blank stare and an offer to open my wallet to replace with a refurbished phone without knowing what is causing the issue.
On some occasions when the device is not responding it heats up. Messages of Apps that stop responding include System UI, Package Access Helper, Touchwiz and Gmail, among others.
When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '
Further trying to diagnose, Sprint Zone / Device Diagnostics / Flagged / System Updates - always states 'Update now', but Settings / System Update / Software update message reads 'The latest updates have already been installed (N910PVPS4DPE2 / N910PSPT4DPE2 / N910PVPS4DPE2).
Investigated alternatives with Samsung (they replied the same day, Sprint Community message July 20th still hasn't replied) I can take it to a service center to have the hardware checked for a fee but it is not nearby and I'd like to first understand what the issue is.
From what I've described does anyone know what could be causing these issues? I have read where some updates were causing problems but I've tried most of those remedies and nothing has helped yet. Perhaps the Sprint Store, in an effort to extract more money (this is how it seemed) did not or was not able to flash the OS?
Any help would be greatly appreciated.
best thing to do is odin back to an older version and retake the update if you wanna go thru that again
but id recommend reverting back to OG5 and then flashing a rom you will have less reboots....as least on my end i did
JLFitzpatrick said:
...When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '...
Click to expand...
Click to collapse
The stock recovery you describe, it's normal for the Android guy to fall down and display the red x or whatever you saw when there's no update to apply but the dm-verity failure isn't normal. It could indicate bad repair or maybe it was rooted at some point? Wiping and Odin flash doesn't always rid the phone of that but Knox trip remains always until Samsung repairs a rooted phone. Dunno the cause of your dm-verity failure but maybe, if it was stock un-rooted all along, it may a read only partition failed or corrupted?
As suggested above, you may fix the dm-verity by taking a couple of OTA updates after Odin flashing an older one. Don't go back any older than OG5 though.
I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times.
That may solve some issues but it could be hardware failure or a corrupt partition. If the dm-verity goes away, see if your problems are resolved. If you didn't root and have a warranty, make whoever warrants it replace it; the failure is legit.
Sprint Zone and ItsOn is garbage IMO. Bloat that kills the experience that Samsung intended. Albeit, Samsung isn't so innocent with bloat ruining the experience either. Just my opinion on the bloat. By the time users add their own bloat, there's but enough RAM and with all the services running, battery takes a hit and phone lags. Run package disabler (search in Google Play) or root to manage it is what I'd suggest. FWIW, I have no random reboots or phone heating up while in standby running Marshmallow. My phone sleeps like a baby.
If no warranty applies and root is an option, you could try rooting with Chainfire Auto Root for Note 4 and then full un-root. The developer removes the dm-verity flag if it's there for modified read only partition reasons. But of coarse that also trips Knox warranty bit, so be aware. Dm-verity can prevent OTA's from updating but that's an alternative with root and Knox trip risks. No warranty should mean less risk unless the phone belongs to your employer.
Sent from my SM-N910P using Tapatalk
Thank you for your replies.
I had pointed out the 'dm-verity verification failure' text to the goof-offs at the Sprint Store, you'd think I was speaking in a foreign tongue. Phone is leased on our personal family plan and used for my business. I've never rooted it myself, not sure what the Sprint people did at the store but that text was there before they supposedly flashed the OS.
I apologize but am in over my head with the suggested repairs. Although having upgraded PC's am familiar with the process; revert to previous clean OS and upgrade over that. I'll take your suggestions and just have to study a little more to understand the correct procedure.
Yesterday afternoon I tried the folks at Samsung again since their support team had replied the same day before (still waiting for a support response from Sprint since July 20th) and went to a live support chat. The woman was very helpful but unfortunately, I had to jump off for a meeting. Before I jumped off she had me put the phone into Safe Mode. I had tried to get there before but the instructions I was given were incorrect (not found in recovery boot). It has since been in that mode and has been much more stable, still freezes occasionally but doesn't reboot itself and runs zippy as hell except for momentary freezes. I have the Chat ID # and will try again today to see what they can do before trying other suggestions. I gave them the HEX DEC numbers and it sounded like they could access the phone with those, this morning their Chat was full so I'll have to try later.
samep, if you don't mind can you give me some clarification on your suggestion:
"I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times."
My interpretation:
Settings / Security / disable reactivation lock
Remove accounts (first back up phone log & sms to samsung account, back up wifi passwords to google account)
Settings / Backup and reset / Factory data reset
Boot to recovery menu / factory reset again (partition and dalvik cache evidently get cleared through reset)
Boot to recovery menu / 'flash an older tar' ? (Is this 'Apply update from ADB (Odin)' or SD card? This is where things get fuzzy. Can I load the stock tar (OS?) to a formatted sd card and apply the update from there or do I have to install Odin on a PC? Where is the best place to get a 'stock tar' (or Odin) from and which version(s) should I use for a Note 4, or is that explained on a particular website. There are many sources of information on Odin and firmware but I'm not sure which to trust if I need to do this would prefer to do this just once.)
Thank you again for your help, and I apologize for my ignorance on this subject.
But the best thing about ignorance is that it can be overcome with a little effort and knowledge.
To answer the question, boot into download mode from powered down state by holding volume down, menu and power. Yes, you use Odin installed on PC for that. But first you need the Samsung USB driver and Odin installed, plus the stock tar.
This thread will get you going with resources and brief instructions.
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
I'd suggest PC1 stock tar, then let it OTA.
(Your interpretation was mostly right up to the question about how to flash the tar after the factory reset and power down.)
Sent from my SM-N910P using Tapatalk
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
JLFitzpatrick said:
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
Click to expand...
Click to collapse
If you're feeling overwhelmed, you could bring it in. There's a chance it is hardware and the steps may prove redundant.
Up to you. At least you have something to point to as an issue.
Sent from my SM-N910P using Tapatalk
So I've gone through all the steps, phone is wiped, reinstalled Samsung USB Driver, have Odin open as Administrator and the phone in 'Android Recovery', Phone does not show up in Odin.
Have seen a couple versions of setting a connection (Odin open first, phone connected first); tried all of those and tried Odin open not as administrator. There is no connection. Tried other instructions to put into Developer Mode and enable USB bugging. Nothing, disabled USB bugging and booted back to recovery. Still nothing.
In Recovery mode it does not state 'Odin mode'. Tried the Recovery menu option 'Apply update from ADB' message reads 'Update from external storage diabled'. Tried 'Reboot to bootloader' (WTH), that does show Odin Mode at top of screen but phone still does not show up in Odin on PC. Then have to pull battery to reboot to Recovery mode. What steps am I missing here?
When phone is booted up normally it connects to PC without issue.
Finally got Odin to recognize the phone. Through a few searches I tried one remedy that suggested manually updating the samsung usb drivers in device manager which did the trick. Realized earlier that from recovery mode you do need to select boot to bootloader to get into Odin mode (listed on top).
Installed 6.0.1 - PD1 currently phone is installing OTA updates, hopefully this does the trick. Thanks again for your help.
On Tuesday the phone updated OTA from PD1 (April 27, 2016) installed via Odin to PE1 (June 1, 2016) then PE2 (June 29, 2016). Recovery Mode screen no longer shows dm-verity failure message so that's fixed. Phone is mostly stable, however still not as stable as it was on PE1 from what I recall by the release dates. Phone still freezes although it usually does not crash if I leave it alone but still does crash at least once a day. Safe Mode does not help, as the worst culprits are system Apps (Gmail, Drive are the worst).
It seldom overheats now but did yesterday. 3rd Party CPU cooler found Package Access Helper, Context Service and System UI as causing an issue. Cleared App Cache for all three but problems persist. Clearing App Cache in Settings / Storage takes at least three tries to clear all but 4.00 KB. I have been clearing Partition Cache every morning just to get through most of the day otherwise it will freeze when I first start to use it. Battery is also draining faster than before.
Any suggestions? OTA updates were at work on a stable WiFi signal. I'm thinking of Odin flashing back to PE1 (or PD1) and stopping further OTA updates. Anybody tried this? Will be traveling for a couple of weeks and need a stable phone, like I used to have. Thank you.
Samsung has been having memory management issues. IMO, this is the reason they keep increasing RAM in recent phones and getting help from Google. But 3 gigs of RAM should be sufficient.
A custom ROM may resolve that but you could try a package disabler from Google Play to freeze some unneeded bloat.
I couldn't say which stock version is best because I've ran all of them without random reboots and lag is minimum. The custom ROMs have been daily driver stable for me. I use them when traveling too.
Sending PM to OP as well with additional info.
Sent from my SM-N910P using Tapatalk
New including my solution without wiping:
I have great news, everyone:
First, a very brief summary of what didn't fix the issue:
I had tried flashing the full February factory image, both manually and using the Google Pixel Flash site without wiping, without any luck.
What just fixed the issue now:
I flashed the new (2nd) February full factory image without wiping. When I noticed I didn't get the corruption paused boot screen during one or more parts of the flash-all.bat flashing process, the phone booted normally after it was completely done.
So at the most, if this issue happens again, hopefully I'd only have to wait until the next full factory image is available.
Not pertinent to the solution, but:
Normally in the past, I go ahead and sign in, and let everything load, and then go back into Fastboot and flash my manually Magisk'd boot.img, but this time when it got to the lock screen, I went back into Fastboot right from there and flashed the Magisk'd boot.img I had prepared from before flashing the factory image. I then shut the phone off. I turned the phone on, and still, no corruption paused boot screen.
I haven't flashed a kernel yet. No idea if any need or can be updated for the 2nd February update - I just haven't checked and don't know if there is updated source code available, or if there will be before the March update.
Click to expand...
Click to collapse
Old:
Yes, I know there's a hair on the screen of my images taken with my original Pixel 1 of my Pixel 6 Pro.
Click to expand...
Click to collapse
I know there are other related threads such as this question thread Unlocked Pixel 6 Pro - "Your Device is corrupted and cannot be trusted" error after trying to manually flash Dec 2021 factory image, and other individual posts in various threads, but I wanted to create a thread where I will maintain the OP with what we figure out about this issue.
Click to expand...
Click to collapse
TL;DR:
So far, it seems the only full way to eliminate the issue includes flashing (via Flash-All.bat from the full firmware zip or Official Google Android Flash Tool) with a full wipe, so losing all user data and system settings. When these flashing methods require temporary rebooting in order to start flashing in a different mode, you may have to manually get the phone past the corruption screen for the flashing method to continue where it left off.Temporary workarounds are to use either of those two flashing methods while not wiping (in Android Flash Tool, have all the checkboxes unchecked) - this doesn't keep this screen from showing every time you reboot or turn the phone on after being off, but the phone is useable, even with a rooted stock kernel - I haven't tested a custom kernel again.
Click to expand...
Click to collapse
Back to the details you may or may not want to know...
This is the corruption screen in question, it precedes the normal bootloader unlocked screen, but in this case, it always requires a manual press of the power button to proceed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
The g.co/ABH link takes you to Understand warning about operating system safety. It's not very helpful in my opinion as it doesn't tell a way to fix the issue without a full wipe. Below are the contents of the page:
Understand warning about operating system safetyWhen you turn on an Android device, it checks the operating system to make sure it's safe to use. This means the code comes from a trusted source and hasn't been changed or corrupted.
If your operating system could have a problem, you can get a warning message that brings you to this page (g.co/ABH).
If you changed the operating system on purposeYou can continue using your device. But you acknowledge that your device might not work properly and your data could be exposed to corruption and security risks.
We recommend restoring your device's operating system. If you have a Pixel or Nexus, learn how to flash your device with the latest factory image.
If you didn't change the operating system yourself
If your device is a Pixel, learn how to get help.
If it's a different Android device, contact your device manufacturer.
Click to expand...
Click to collapse
Spoiler: My original post from another related thread, in response to someone else's question about the solution.
sybor said:
Did you managed to do it using Android Flash Tool without wipping the device?
Click to expand...
Click to collapse
roirraW edor ehT said:
I'm preparing to create a catch-all thread just for this issue. I just experienced the issue for the first time, although I've observed the others who have encountered it under various circumstances.
For myself, it wasn't flashing the February image that caused the error, it was after I flashed a certain custom kernel.zip through EXKM (EX Kernel Manager) that I had the issue. I won't name the kernel as I don't think it's any particular kernel that's the issue, although I don't know what the cause is.
Previous to updating to the February firmware, I was on the January (and with Verity and Verity NOT disabled either time) and was using a different custom kernel zip without any issue. I went through the process pretty much identically to how I had previously. Using the stock kernel worked fine, and using the stock kernel rooted with Magisk 24.1 worked just fine as well. I first had the issue after rebooting from flashing a kernel.zip through EXKM, and I still have it.
I'm not 100% sure this was necessary but using the Android Flash Tool or the manual firmware flash-all.bat (both without wiping, and the Android Flash Tool with no checkboxes checked) both resulted in the phone being usable again, however when I reboot I still get that first (and different than the bootloader unlocked screen) corruption screen.
I will create my thread with images very soon, but I wanted to share what little I know so far, and at least the phone works, it's just a slight PITA that when I reboot or boot from the phone being off that I get that error which requires a manual power button press to go past. Note that during the re-flashing process that I sometimes had to manually press the button during the times the flash process reboots the phone into a different mode before it would continue the flashing process.
Click to expand...
Click to collapse
As you can see below, after flashing (but without wiping) I'm able to boot as normal (only tested with the stock February kernel, rooted with Magisk 24.1), with the only exception being the third screenshot from the top-left, about corruption, and requiring manually pressing the power button to get past the screen.
In case I need this post #2.
In case I need this post #3.
In case I need this post #4. (Last one of these)
It happened to me once when I sideloaded January's OTA and a full wipe with the Android Flash Tool worked, manually flashing via adb did not. However, I got that corrupt boot screen when flashing February's update via AFT. It was worse trying to fix the problem this go-around because I wiped the phone multiple times via AFT with various options (wiped, disable verity, even relocked the bootloader and returned to stock). It finally stuck but I'm not sure what I did.
I tried all the suggestions on XDA and around the Internet but nothing helped. Closest thing I could figure out was maybe one of the boot slots had had encryption and the other didn't so the update failed? It sucked, because now I'm hesitant to flash any kernels or even a patched magisk image because that damn corrupt boot screen appears way too easily.
Had this come up once on my wife's 5a.
This means there is dm-verity corruption:
Boot Flow | Android Open Source Project
source.android.com
Not a big deal really, the Magisk wizards will figure this out eventually. Sideloading the OTA fixed it.
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
EDIT: And Ninja'd by 1 minute by @V0latyle
Lughnasadh said:
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Beat you to it, thanks for the additional explanation
V0latyle said:
Beat you to it, thanks for the additional explanation
Click to expand...
Click to collapse
I edited my post to reflect your Ninja prowess
Lughnasadh said:
I edited my post to reflect your Ninja prowess
Click to expand...
Click to collapse
It happened to me back in December when I first got my P6P and was rooting it. I couldn't get it to boot though. I tried using the repair tool, but it wouldnt find my device. I tried manual flashing via adb, but it would fail. I was about to send it back to google when I figured I would try to switch boot partitions and that fixed it.
dunno how I got this message as I only got it after flashing a custom kernel which dev said includes the magisk version that does not veed verity disabled.
i hope in march ota when I flash that it will go back to previous boot slot it dont say that.
I will probably do a full wipe and flash when I get some time as the message is annoying as it adds delay to boot
V0latyle said:
Had this come up once on my wife's 5a.
This means there is dm-verity corruption:
Boot Flow | Android Open Source Project
source.android.com
Not a big deal really, the Magisk wizards will figure this out eventually. Sideloading the OTA fixed it.
Click to expand...
Click to collapse
Thank you! Sideloading just now didn't fix it for me. I tried it while I was already on the February full firmware.
Spoiler: The details of my sideloading
I just sideloaded the full February OTA after I manually restored the unrooted stock February kernel. This might have been the first time I've sideloaded an OTA, or only the second time - I might have done it once on the Pixel 1. The Result code was 0 (zero) for both verification and installation, which appears to mean success where 1 would mean failure.
After success, I booted Android, unlocked the phone, kept it unlocked, and I waited at least 10 minutes since your instructions say:
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Click to expand...
Click to collapse
I never actually saw a notification regarding it, however - like I would if I tried an actual over-the-air update - "Finishing Update" or something like that. I rebooted after than 10+ minutes and still got the paused-boot corruption screen. After unlocking I waited again and then rebooted and same result.
I'm contemplating flashing the full firmware image for January without wiping and with suppressing reboot so no February-specific data is affected by suddenly being on the January firmware, and then immediately applying the February OTA again to see if that helps.
Do you anticipate any problems with this plan, or do you have a better suggestion for me to try first? No worries if anything goes wrong - I have nothing on my phone that isn't backed up, I'm just trying to avoid having to re-copy hundreds of gigs of FLAC formatted music yet again, LOL!
Lughnasadh said:
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
EDIT: And Ninja'd by 1 minute by @V0latyle
Click to expand...
Click to collapse
Thank you! I appreciate the details and the additional link to relevant information.
roirraW edor ehT said:
I'm contemplating flashing the full firmware image for January without wiping and with suppressing reboot so no February-specific data is affected by suddenly being on the January firmware, and then immediately applying the February OTA again to see if that helps.
Do you anticipate any problems with this plan, or do you have a better suggestion for me to try first? No worries if anything goes wrong - I have nothing on my phone that isn't backed up, I'm just trying to avoid having to re-copy hundreds of gigs of FLAC formatted music yet again, LOL!
Click to expand...
Click to collapse
Well, this is how things went wrong on my wife's Pixel 5a:
Restored boot image in Magisk, installed OTA. Rebooted. Successful boot, no root (because she rebooted it before I had a chance to install to inactive slot)
Switched active slot to the "old" slot. Bootlooped.
Dirty flashed January factory image on old slot. Verity EIO corrupt warning. Bootlooped.
Dirty flashed January factory image to both slots. Bootlooped, Rescue Party data corrupt warning.
Downloaded and dirty flashed February factory image to both slots. Bootlooped, Rescue Party.
Sideloaded the February OTA to the "new" slot. Successful boot. Attempted to live boot previously patched image, I believe January patched with 23017. Rescue Party.
Patched February boot image in Magisk Stable 24, rebooted to bootloader and live booted. Successful. Performed Direct Install in Magisk, and rebooted. Successful boot with root.
There is something to do with the OTA mechanism that will bork everything if you try to mess with it. I do know that if it doesn't successfully boot the updated slot, it will mark that slot "unsuccessful" and won't try to boot it again, and will then revert to the old slot. I don't know why it didn't just boot the old slot in my case.
Going forward, at least until we figure out the problem with automatic OTAs, the safest method of update is either dirty flashing the factory image (can use Android Flash Tool as well), or sideloading the OTA.
I posted this back in November/December after trying to flash factory image without the wipe command (factory image not ota). The problem with mine was I couldn't get past the message. At all. I wiped the device twice in recovery menu and it still wouldn't boot. I had to reflash The mid November build (on both slots) and wipe in between.
Then in December I disabled Location for ImsService in the privacy menu and the message appeared again - this time it would boot but only for two seconds, then it would automatically restart. Duplicated the issue after January update but haven't tried it since.
Many posts on Reddit for the 5/5a with this issue and the fix for those devices was to update Play Services and All apps in safe mode (with Bluetooth off - many users experienced their devices restart with the 'device is corrupt' message after turning on Bluetooth). I'll edit my post when I find the other posts to these issues, but it seems like a few things can cause this message to appear.
Awesome thread though. Unfortunately it looks like @roirraW "edor" ehT will be copying 200gb of music soon enough if no solution is found.
searching for 'corrupt' on reddit's GooglePixel sub shows this problem was mostly prevalent from November-December, Pixels 4-6.
Alekos said:
I posted this back in November/December after trying to flash factory image without the wipe command (factory image not ota). The problem with mine was I couldn't get past the message. At all. I wiped the device twice in recovery menu and it still wouldn't boot. I had to reflash The mid November build (on both slots) and wipe in between.
Then in December I disabled Location for ImsService in the privacy menu and the message appeared again - this time it would boot but only for two seconds, then it would automatically restart. Duplicated the issue after January update but haven't tried it since.
Click to expand...
Click to collapse
Interesting experience. Thank you for sharing the details.
Alekos said:
Many posts on Reddit for the 5/5a with this issue and the fix for those devices was to update Play Services and All apps in safe mode (with Bluetooth off - many users experienced their devices restart with the crop message after turning on Bluetooth). I'll edit my post when I find the other posts to these issues, but it seems like a few things can cause this message to appear.
Click to expand...
Click to collapse
I'm trying this now since it won't hurt any. I rebooted to safe mode, eventually remembered to turn off Airplane mode, I turned off Bluetooth just to make it a controlled experiment, then I updated the ~14 apps that had updates available. For the heck of it, I checked to see if there was any Play System update available to me and there wasn't, so next I uninstalled all updates for Google Play services, and reinstalled them.
I then rebooted, but I still have the paused-boot corruption screen. Worth a try, though. If you find more details, let me know, please.
Alekos said:
Awesome thread though. Unfortunately it looks like @roirraW "edor" ehT will be copying 200gb of music soon enough if no solution is found.
Click to expand...
Click to collapse
LOL!!
Edit: I wish going to safe mode didn't cause Nova Launcher Prime from resetting all my home screen widgets. It's not that big a deal to reconfigure them but I wish there was a way to keep that from happening.
My three Weawow weather widgets and my two Multi Timer widgets are the worst - and not terrible, just a little bit tedious. I'm getting used to it, though! LOL!
roirraW edor ehT said:
Interesting experience. Thank you for sharing the details.
I'm trying this now since it won't hurt any. I rebooted to safe mode, eventually remembered to turn off Airplane mode, I turned off Bluetooth just to make it a controlled experiment, then I updated the ~14 apps that had updates available. For the heck of it, I checked to see if there was any Play System update available to me and there wasn't, so next I uninstalled all updates for Google Play services, and reinstalled them.
I then rebooted, but I still have the paused-boot corruption screen. Worth a try, though. If you find more details, let me know, please.
LOL!!
Edit: I wish going to safe mode didn't cause Nova Launcher Prime from resetting all my home screen widgets. It's not that big a deal to reconfigure them but I wish there was a way to keep that from happening.
My three Weawow weather widgets and my two Multi Timer widgets are the worst - and not terrible, just a little bit tedious. I'm getting used to it, though! LOL!
Click to expand...
Click to collapse
what's interesting is, just from reading the posts on Reddit, looks like Pixels 4-5 were fixed by the update solution, but not for the 6. Here's one post.
Also, your message is completely different than the one I saw. Mine looked like the attachment.
edit--
And it looks like at least 10 users on this sub have posted about this issue, including this user who still can't fix his phone.
edit--#2--
shoot I know, Safe Mode causes weird things to happen with Launchers.... dammit sorry!!
edit --#3-- fixed link, woops thanks @roirraW "edor" ehT
Alekos said:
what's interesting is, just from reading the posts on Reddit, looks like Pixels 4-5 were fixed by the update solution, but not for the 6. Here's one post.
Also, your message is completely different than the one I saw. Mine looked like the attachment.
edit--
And it looks like at least 10 users on this sub have posted about this issue, including this user who still can't fix his phone.
Click to expand...
Click to collapse
Very interesting. Maybe there's a slight difference in the cause or some other detail we don't know yet, since the problem on mine wasn't preceded by wired or wireless headphones being used. Very interesting! Your link "this" became garbled. Here's the fixed link. this
Alekos said:
edit--#2--
shoot I know, Safe Mode causes weird things to happen with Launchers.... dammit sorry!!
Click to expand...
Click to collapse
That's quite alright, not your fault. I've only recently started fooling with safe mode so it's still a slight surprise to me each time, but I think it won't stay a surprise for much longer.
Alekos said:
edit --#3-- fixed link, woops thanks @roirraW "edor" ehT
Click to expand...
Click to collapse
You're welcome!
I had this error after a non-wipe upgrade, coupled with bootloops. I had everything backed up so I did a complete factory image install and re-rooted. The phone runs like new again and all rooting conflicts are resolved.