Related
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Rooted?
You mention in the title that the phone is rooted. To be able to discount hardware errors, have you tried flashing a factory image to set it back to stock? If the same problems continue, then I suggest that you return it to Google. I did this myself when the back of my N6 started to peel and the process was painless, since they send you the new phone before you return the old one, so you lose no airtime.
saraddictive said:
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Click to expand...
Click to collapse
Yes, as mentioned, flash a factory image to rule out any software issues. However, it is most likely hardware failure. Especially the camera fault. I've noticed this is becoming a rather common issue lately. So, you should probably RMA again.
Thanks guys. I was just concerned as I unlocked the bootloader and rooted the phone almost immediately after I got it. If I try to RMA it, they won't cry foul over a re-locked boot loader,will they?
Also,I have a feeling this might be an OTA that is acting up. It appears that loads of people have had issues after installing an ota (I did this before unlocking and rooting) so I'm going to try to flash a factory image. Thanks guys
Hello everyone,
as an update, I did exactly as dahawthorne and evolution_tech said, and re-flashed a factory image. However, i found it extremely strange that both my nexus 6s were experiencing the same issue so i did a little research.
Turns out, many users from 5.1 have been experiencing issues with changing their dpi in android 5.1 and above. Because I'm not all that familiar with build.prop and using adb shell (tried using it once, it wouldnt work properly so i just gave up), im not going to bother changing my dpi and it works all fine and good now.
To anyone else experiencing the same issue, check this page out: http://forum.xda-developers.com/nexus-6/general/dpi-conflicts-lmy47e-t3061261.
Cheers
Yep, well known issue.
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Note 5 crash
Yep, have the same problem, but I have not attempted to Flash the Phone yet...
Did multiple factory resets, clear caches... but to no avail. There is no structure or pattern in crash rate. Although it is getting more often day by day...
Found no working sollution, but it feels like there is a bad memory segment or something. Everytime it randomly uses that segment... crash!
Really don't know. Will try to get warrenty fix.
Let me know if you found a sollution on your side?
Cheers,
Wim
kbiscu1t said:
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Click to expand...
Click to collapse
OP here. Made a warranty claim, they seem to have replaced the motherboard as the solution. Complete repair experience from warranty claim to package back at my doorstep was less than two weeks, which is impressive for what I've heard about Samsung's support. Good luck!
HI,
I'm writing this in a new post not to be confused with out dated information!
My wish is, someone smarter than me write it! but it just has not happened..
The main issue is:
Note 4 tmo
1. Freezing.
2. Restarting randomly.
3. MMC failures.
4. Kernel Panic.
5. Sluggish.
6. Goes to sleep and does not awake.
7. Bla, Bla.
Remember, this is in my opinion!
If you can use it say thanks if not don't flame, but feel free to set the record straight!
Thoughts...
To many phones have gone wacky on or about the same time as the MM update.
In my humble opinion its software not hardware or is it!
I think its faulty/borderline firmware that may run on some but due to maybe another underlying issue pushes the phone over the edge!
Since the clean-up I have had no other issues, see below!
Troubleshooting, Best practices
Troubleshooting best practices
*Start out with good tools*
1. Good USB Cable
2. Fully Charged Battery
3. Good software tools such as Odin, Kies, etc.
4. Known workable drivers (windows, Mac)
5. Always do a back-up of your stuff.
6. Have good working copies from reliable sources such as firmware, roms, TWRP, etc.
7. Make sure your hardware is Genuine, there is Note 4 knockoffs & Micro-sd card knockoffs, Battery Knockoffs swirling around the internet!
8. Remember, Garbage In Garbage out! if your system is conflicting you can't rely on your back-ups, dirty flashing, etc tear it down and rebuild including internal SD
9. Factory reset, wipe, format, (this must happen to start fresh.
10. If your googling for research please don't choose all but say search in the last month etc. conflicting information exists.
11. Please match your kernel with the rom & firmware ask the developer of the rom for advice.
BAD Information
in our search for answers, we may come across info that was good at one time but no longer! so be careful.
examples:
1. You can revert back to KK from MM.
(not sure that's true, although Odin will let you downgrade to the AOG1 firmware of the N4T2, I'm not sure its stable.
But it won't then let you reflash the ANK4.
2. Just because its on the internet don't mean its true.
3. Just because the Samsung guy says its the Motherboard, its still suspect.. (I'll tell you my car transmission story later)same theory
3a. He pulls his pants down and craps just like we do!
4. You can't make chicken salad out of chicken $h!t, just because it has chicken in the title..
Dude my note 4 is totally F'd phones just stop working when they are old. I've had this note 4 since a week after it came in 14. Been a great phone but I switched to the s7 edge because of this. S7 edge screen cracked so I'm using this one as a backup and MAN it sucks ! My issues are mainly with battery. I've tried a new battery and don't help, it dies at 30% it charges slow, drains fast. Also a lot of glitches my back button don't work on YT? camera can't focused on an object more than 3Ft away. Thus phone is a mess. Can't wait to fix my s7 edge. Just needs to come up with an extra $320 stupid Assurant won't fix my s7 edge. Taking off JUMP. Till the switch insurance companies soon they will
Sent from my SM-N910T using Tapatalk
nano303 said:
Dude my note 4 is totally F'd phones just stop working when they are old. I've had this note 4 since a week after it came in 14. Been a great phone but I switched to the s7 edge because of this. S7 edge screen cracked so I'm using this one as a backup and MAN it sucks ! My issues are mainly with battery. I've tried a new battery and don't help, it dies at 30% it charges slow, drains fast. Also a lot of glitches my back button don't work on YT? camera can't focused on an object more than 3Ft away. Thus phone is a mess. Can't wait to fix my s7 edge. Just needs to come up with an extra $320 stupid Assurant won't fix my s7 edge. Taking off JUMP. Till the switch insurance companies soon they will
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yep I'm with you brother! (still writing the thread though!)
SO far So Good Here's What I DID
1. Download all necessary firmwares.
2. changed to a smaller tried and true micro-sd card (just in case)
3. Charged my battery.
4. formatted my sd card with SD-formatter on the PC
5 loaded all files on the sd card with a usb-micro-sd reader/writer
6.Moved PC files all in one location on the HD such as C:/note4/kernels
or C:/note4/roms or C:/note4/firmware.. (I think you get the picture)
7. in TWRP I wiped,factory reset, formatted data on internal SD, everything except the external sd. (a couple of times)
8. with ODIN I did flash the T2"s firmware listed as :N910T2UVU2A0G1 just to downgrade from MM.
9. Then let it boot with minimal input, after shutting it down back to DL mode.
10 with odin install DOK2 firmware, it is more stable.
11 then flashed TWRP but unclick the auto-boot. (Thanks to Bigbiff & TWRP team)
12 Unplug after TWRP flashes and pull the battery. (2 or 3 Seconds)
13 boot in recovery using home, Power and volume UP.
14 now flash rom of choice I used N5 Express ver. 3.4D (Thanks rmarinella )
15 with Freeza's kernel 3.10.40 BeastMode Thanks Freeza)
16 customize with your personal settings then backup ( backup before you do to much tweaking though)
Special thanks to all folks that put so much time into this phone! if I left someone out, let me know!
Here's some photos!
I know you say Quadrant bench marks are bull?
well they will detect stuttering, lag etc.
So you guys had a huge performance hit today? I thought my ram was going or something. Long pauses in responsiveness, 10-15 second lock screen turn on from time to time, random jitters. Forced me to wipe everything and upgrade to MM from 5.0.1. Right around my last tmo payment for the phone too. Suspicious. The upgrade seems to have made things a little better (still some small issues) but now I'm paranoid. Probably my last samsung phone...shame (this is primarily due to the lack of battery and expandable memory though).
If anyone had a lot of success with a custom ROM please repot back.
EDIT: phone rebooted after posting this. Will have to tinker more.
gdewald said:
So you guys had a huge performance hit today? I thought my ram was going or something. Long pauses in responsiveness, 10-15 second lock screen turn on from time to time, random jitters. Forced me to wipe everything and upgrade to MM from 5.0.1. Right around my last tmo payment for the phone too. Suspicious. The upgrade seems to have made things a little better (still some small issues) but now I'm paranoid. Probably my last samsung phone...shame (this is primarily due to the lack of battery and expandable memory though).
If anyone had a lot of success with a custom ROM please repot back.
EDIT: phone rebooted after posting this. Will have to tinker more.
Click to expand...
Click to collapse
Good luck, thanks for posting!
I got my Note 4 back in late 2014. I picked the Note 4 over the Nexus 6 and I regretted it after the first Lollipop update.
I truly believe (imo) Samusng gave us a borked Lollipop update because at the time the S6 had came out the gate with Lollipop and the newer version of TouchWiz.
There was a rom that was made from a Sprint S6 edge which the creator tried to port over as best he could to the Note 4 and it was very fast and snappy, The only issue was the radio would stop working and would randomly reset every so often. Everything did work including the Theme store and the edge apps. What makes the Note 4 so weird acting (imo) is the older version of TouchWiz still lingering on the Note 4 and Note Edge.
It got worse when the MM update came out. I was using a stock rom, unrooted and it was terrible. I finally got a Nexus6 last year and the phone is still snappy and fats, if not faster on Nougat. Samsung knew that people would still keep their Note 4's over the Note 5 due to the lack of missing features like a removable battery, sd card slot, and IR blaster.
I dont think their is much you can do unless you run a custom rom.
Welp since I still have issues with my Note4 and am completely new and not very knowledgeable about it... I had the same issues with my stock phone;(it even bricked on me once) I snooped around and now I've settled with installing that app "WakeLock" and let it always run (Partial wake lock setting 4);
* I know its not fixing the problem but I'm a noob *
its been almost a week now and it phone doesn't freeze, reboot, lag(majorly);
Before I had to remove battery at least 5 times a day and pray it would turn back on;
bvzxa3 said:
I got my Note 4 back in late 2014. I picked the Note 4 over the Nexus 6 and I regretted it after the first Lollipop update.
I truly believe (imo) Samusng gave us a borked Lollipop update because at the time the S6 had came out the gate with Lollipop and the newer version of TouchWiz.
There was a rom that was made from a Sprint S6 edge which the creator tried to port over as best he could to the Note 4 and it was very fast and snappy, The only issue was the radio would stop working and would randomly reset every so often. Everything did work including the Theme store and the edge apps. What makes the Note 4 so weird acting (imo) is the older version of TouchWiz still lingering on the Note 4 and Note Edge.
It got worse when the MM update came out. I was using a stock rom, unrooted and it was terrible. I finally got a Nexus6 last year and the phone is still snappy and fats, if not faster on Nougat. Samsung knew that people would still keep their Note 4's over the Note 5 due to the lack of missing features like a removable battery, sd card slot, and IR blaster.
I dont think their is much you can do unless you run a custom rom.
Click to expand...
Click to collapse
I think your on to something!
Thanks for your post.
Xirazer said:
Welp since I still have issues with my Note4 and am completely new and not very knowledgeable about it... I had the same issues with my stock phone;(it even bricked on me once) I snooped around and now I've settled with installing that app "WakeLock" and let it always run (Partial wake lock setting 4);
* I know its not fixing the problem but I'm a noob *
its been almost a week now and it phone doesn't freeze, reboot, lag(majorly);
Before I had to remove battery at least 5 times a day and pray it would turn back on;
Click to expand...
Click to collapse
I hope an expert chimes in... but I think wake lock is doing what a good working kernel is suppose to do! correct me if I'm on the wrong track.
Most of my issues seem to be kernel related. There are times when the phone will act up just because I plugged it in or will loop when trying to shutdown. I think part of it was having a bad TWRP flash that screwed with subsequent actions. Secondly, my phone seems to run fine until I install any GAPPS. The camera is always having issues and I would get random wake lock and boot loops.
Right now, I flashed DU 10.6 and then ran a backup before flashing GAPPS. Then, using that as a base, I'm going to try and find a happy GAPPS and DU 10.6 combination. I may have to try a minimal GAPPS approach and install things as needed on /data
cal3thousand said:
Most of my issues seem to be kernel related. There are times when the phone will act up just because I plugged it in or will loop when trying to shutdown. I think part of it was having a bad TWRP flash that screwed with subsequent actions. Secondly, my phone seems to run fine until I install any GAPPS. The camera is always having issues and I would get random wake lock and boot loops.
Right now, I flashed DU 10.6 and then ran a backup before flashing GAPPS. Then, using that as a base, I'm going to try and find a happy GAPPS and DU 10.6 combination. I may have to try a minimal GAPPS approach and install things as needed on /data
Click to expand...
Click to collapse
Thanks,
Keep us updated on you progress!
Good luck.
sloanster said:
Thanks,
Keep us updated on you progress!
Good luck.
Click to expand...
Click to collapse
Thanks for the luck wishes. I think they might have helped
So, thinking more about my issues, I realized that it was not only kernel problems, but random issues depending on how I flashed and what I flashed. Today, I have what I think is a CLEAN and working install. Previously, I would have issues with Wifi starting up and Camera focusing and SuperSU installation.
Here's what I did to get my clean install:
Always backed up a copy each step of the way so I could have checkpoints to go back to and build upon.
First, I downloaded the newest version of ODIN: 3.12.3
Then, I flashed a new copy of TWRP recovery via ODIN: twrp-3.0.2-0-trltetmo.img.tar
SHUT DOWN PHONE (Do not reboot)
SIT 2 MINUTES
boot into recovery using VOL UP + HOME + PWR
ADVANCED WIPE: check everything BUT Internal Storage and MicroSD and swipe to wipe.
Install ROM (no other files!) and wait.
Back out of menus until TWRP home menu and choose reboot, then in the submenu, Shutdown
SIT 2 MINUTES
boot regularly
SIT 15 MINUTES This part is hard to do, but just go do some reading and come back.
Then, SHUTDOWN and TURN BACK ON.
You should still be on the Welcome screen upon boot.
Make sure you can connect to Wifi and your SIM is being read. If not, start over from the advanced wipe and make sure to wait when needed.
If that all works, skip the gmail and name prompts and get to the home screen.
Shutdown wait a minute and boot to recovery
run a backup and name it PRE-GAPPS or something (DO NOT USE ENCRYPTION, it has not restore properly from encryption in my experience)
Then, flash your GAPPS file and SHUTDOWN and wait a minute. I used PICO GAPPS (Open Gapps; ARM | pico | 6.0) so I could install what I wanted later from Play Store.
Boot up normally, skip any logins etc and make sure camera, wifi and phone work. If yes, shutdown and boot into RECOVERY, backup and name WORKINGGAPPS or something.
Boot into system and start the Google Account logins etc.
At this point, I ran another backup Called WITHGOOGLE
And finally, I booted back into the system and started loading my other applications and adding some of my tweaks, then running another backup. LOL
It was a time consuming and patience testing practice, but I'm happy now that my phone is working as expected. I'll report back if it stays stable or not. At least I have back ups to revert to.
cal3thousand said:
Thanks for the luck wishes. I think they might have helped
So, thinking more about my issues, I realized that it was not only kernel problems, but random issues depending on how I flashed and what I flashed. Today, I have what I think is a CLEAN and working install. Previously, I would have issues with Wifi starting up and Camera focusing and SuperSU installation.
Here's what I did to get my clean install:
Always backed up a copy each step of the way so I could have checkpoints to go back to and build upon.
First, I downloaded the newest version of ODIN: 3.12.3
Then, I flashed a new copy of TWRP recovery via ODIN: twrp-3.0.2-0-trltetmo.img.tar
SHUT DOWN PHONE (Do not reboot)
SIT 2 MINUTES
boot into recovery using VOL UP + HOME + PWR
ADVANCED WIPE: check everything BUT Internal Storage and MicroSD and swipe to wipe.
Install ROM (no other files!) and wait.
Back out of menus until TWRP home menu and choose reboot, then in the submenu, Shutdown
SIT 2 MINUTES
boot regularly
SIT 15 MINUTES This part is hard to do, but just go do some reading and come back.
Then, SHUTDOWN and TURN BACK ON.
You should still be on the Welcome screen upon boot.
Make sure you can connect to Wifi and your SIM is being read. If not, start over from the advanced wipe and make sure to wait when needed.
If that all works, skip the gmail and name prompts and get to the home screen.
Shutdown wait a minute and boot to recovery
run a backup and name it PRE-GAPPS or something (DO NOT USE ENCRYPTION, it has not restore properly from encryption in my experience)
Then, flash your GAPPS file and SHUTDOWN and wait a minute. I used PICO GAPPS (Open Gapps; ARM | pico | 6.0) so I could install what I wanted later from Play Store.
Boot up normally, skip any logins etc and make sure camera, wifi and phone work. If yes, shutdown and boot into RECOVERY, backup and name WORKINGGAPPS or something.
Boot into system and start the Google Account logins etc.
At this point, I ran another backup Called WITHGOOGLE
And finally, I booted back into the system and started loading my other applications and adding some of my tweaks, then running another backup. LOL
It was a time consuming and patience testing practice, but I'm happy now that my phone is working as expected. I'll report back if it stays stable or not. At least I have back ups to revert to.
Click to expand...
Click to collapse
Yeah, I believe I would have move my important stuff off the internal and wiped it!
You can't be sure conflicting stuff does not linger..
Take the poll
page 1
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.
A few days ago, I was trying to launch an app from my phone's home screen when it suddenly rebooted itself and downloaded/installed an OTA update, removing root in the process. So it looks like Google just force-restarted it and updated it without my consent!
Or, if not that, then I truly must have the worst luck imaginable - like astronomically, unbelievably bad; so bad it could be legendary - almost as if I were cursed by some mythical, malevolent creature with magical powers.
For what I'm about to assume might have happened to be what actually happened, the odds are probably astronomically against it occurring, or nearing the realm of quantum impossibility (or, at the very least, it would be extremely-improbable and highly-unlikely, statistically speaking).
There have been a handful of times (3-5, but I haven't kept count) in the few months I've had this phone that, after unlocking the screen, I see a window drawn over my phone's home screen: a notification dialog with info about downloading/installing a security update for the OS. At the bottom of the window I recall there being two buttons: one to confirm, reboot my phone, and download/install the update, and the other to postpone the update until some later time at night.
Since there was no button for the polite, socially-acceptable equivalent to responding, "NO, **** YOU! STOP ANNOYING ME WITH THIS PROMPT TO UPDATE! I NEVER WANT TO DOWNLOAD AND INSTALL AN UPDATE, OR SEE THIS POP UP EVER AGAIN!", I've just used the "back" button on my phone to dismiss this notification/prompt rather than accepting one of the two equally-unacceptable choices it offered me and being forced into downloading and updating my phone.
So, in theory, it's possible that, at the same exact moment as my phone's screen refreshed to draw this update notification/prompt again, I just happened to also click in exactly the wrong place - the place where that dreaded "reboot" button was drawn - thereby selecting the option to immediately reboot my phone, downloading and installing the update in the process. It would've had to have happened so quickly - literally, within the same 1/90th of a second - that the screen was drawn so that I didn't even see the notification appear before clicking the option to accept and reboot/install the update immediately.
1/90th of a second: that's just a hair over 11 milliseconds, or a hundredth of a second. And I just happened to click in exactly the wrong spot at exactly that moment?
Utterly, unimaginably, and even ridiculously bad luck if this is what actually happened. But aside from Google simply forcing a reboot/update remotely while I was using my phone, it's the only other thing I can think of that might've caused this.
Whoever programmed this functionality should at the very least be publicly shamed and insulted for it, but possibly also dragged out of their bed in the middle of the night into the street and beaten mercilessly. I don't know the law well enough to be aware of the name of the crime for such a thing (annoying millions of people with this almost-unavoidable and heinously-obnoxious nag to update their phone's OS, and causing maybe thousands of them to suffer some sort of financial loss, pain & suffering, or tragic inconvenience by accidentally accepting and applying the update - especially if they happened to be on a limited mobile data plan, or were roaming at the time). However, I'm fairly certain that most people who have experienced something like what I've been through and am forced to deal with now as a result of an OTA update being applied against their will would be fine with either or both of these things being administered as the just and appropriate form of punishment for such a crime.
So, all that being said, what are my odds that I'll be able to not only restore root to my phone without wiping it and losing all the sensitive data I had saved with root access but hadn't had the time to back up yet during one of the most difficult and tragic weeks of my life (I can't even begin to explain all of the other **** that has gone horribly wrong recently), but to also recover compensation for the cost of exceeding my data plan while visiting another country due to the update being downloaded at an EXTREMELY inopportune time? My guess: probably worse than the odds of accidentally clicking to accept and immediately download and apply an OS update within the same ≈11 milliseconds the nag for it was drawn on my phone's screen while also in the middle of giving a presentation in a super-important, multinational business meeting.
But hey, I figured I would share this post here anyway in the hopes of maybe learning that Google force-pushed an OTA update and pissed off millions of people who then filed a class action lawsuit because of it, and I just hadn't heard the news about it yet, but it was also recent enough that I could still get in on that action and recover at least some part of what I've lost in the past week.
And if not that, maybe I'll at least somehow get confirmation of having some of the worst luck imaginable, or validation that I'm not crazy, or just some sympathy and comfort from the community during a very dark time in my life when I sorely need it.
And I guess if there's even a modicum of hope I'll discover that I'm not completely alone in this world of **** that I now find myself in, and that there are others who have suffered a similar fate or misfortune as a result of either unbelievably bad luck with their phone, or Google forcibly cramming something very large and uncomfortable into an extremely sensitive area against their will - maybe even at one of the worst possible times of their life - then maybe there's even some hope left for my life; some point to even continuing it and trying to get out of the horribly-****ty, godforsaken nightmare I'm stuck in right now.
Or maybe I'll just learn that it is actually somehow possible to restore root to my phone without needing to wipe it first so I'm at least not quite as completely screwed as it looks like I am right now.
≈-∞
Google Pixel 5, OS 11
rooted with Magisk, no TWRP/recovery
recently forcibly OTA-updated to build RQ1A.201205.011
Disable updates permanently. I'm more concerned with the damage updates will do than malware at this point
leveleyed said:
A few days ago, I was trying to launch an app from my phone's home screen when it suddenly rebooted itself and downloaded/installed an OTA update, removing root in the process. So it looks like Google just force-restarted it and updated it without my consent!
Or, if not that, then I truly must have the worst luck imaginable - like astronomically, unbelievably bad; so bad it could be legendary - almost as if I were cursed by some mythical, malevolent creature with magical powers.
For what I'm about to assume might have happened to be what actually happened, the odds are probably astronomically against it occurring, or nearing the realm of quantum impossibility (or, at the very least, it would be extremely-improbable and highly-unlikely, statistically speaking).
There have been a handful of times (3-5, but I haven't kept count) in the few months I've had this phone that, after unlocking the screen, I see a window drawn over my phone's home screen: a notification dialog with info about downloading/installing a security update for the OS. At the bottom of the window I recall there being two buttons: one to confirm, reboot my phone, and download/install the update, and the other to postpone the update until some later time at night.
Since there was no button for the polite, socially-acceptable equivalent to responding, "NO, **** YOU! STOP ANNOYING ME WITH THIS PROMPT TO UPDATE! I NEVER WANT TO DOWNLOAD AND INSTALL AN UPDATE, OR SEE THIS POP UP EVER AGAIN!", I've just used the "back" button on my phone to dismiss this notification/prompt rather than accepting one of the two equally-unacceptable choices it offered me and being forced into downloading and updating my phone.
So, in theory, it's possible that, at the same exact moment as my phone's screen refreshed to draw this update notification/prompt again, I just happened to also click in exactly the wrong place - the place where that dreaded "reboot" button was drawn - thereby selecting the option to immediately reboot my phone, downloading and installing the update in the process. It would've had to have happened so quickly - literally, within the same 1/90th of a second - that the screen was drawn so that I didn't even see the notification appear before clicking the option to accept and reboot/install the update immediately.
1/90th of a second: that's just a hair over 11 milliseconds, or a hundredth of a second. And I just happened to click in exactly the wrong spot at exactly that moment?
Utterly, unimaginably, and even ridiculously bad luck if this is what actually happened. But aside from Google simply forcing a reboot/update remotely while I was using my phone, it's the only other thing I can think of that might've caused this.
Whoever programmed this functionality should at the very least be publicly shamed and insulted for it, but possibly also dragged out of their bed in the middle of the night into the street and beaten mercilessly. I don't know the law well enough to be aware of the name of the crime for such a thing (annoying millions of people with this almost-unavoidable and heinously-obnoxious nag to update their phone's OS, and causing maybe thousands of them to suffer some sort of financial loss, pain & suffering, or tragic inconvenience by accidentally accepting and applying the update - especially if they happened to be on a limited mobile data plan, or were roaming at the time). However, I'm fairly certain that most people who have experienced something like what I've been through and am forced to deal with now as a result of an OTA update being applied against their will would be fine with either or both of these things being administered as the just and appropriate form of punishment for such a crime.
So, all that being said, what are my odds that I'll be able to not only restore root to my phone without wiping it and losing all the sensitive data I had saved with root access but hadn't had the time to back up yet during one of the most difficult and tragic weeks of my life (I can't even begin to explain all of the other **** that has gone horribly wrong recently), but to also recover compensation for the cost of exceeding my data plan while visiting another country due to the update being downloaded at an EXTREMELY inopportune time? My guess: probably worse than the odds of accidentally clicking to accept and immediately download and apply an OS update within the same ≈11 milliseconds the nag for it was drawn on my phone's screen while also in the middle of giving a presentation in a super-important, multinational business meeting.
But hey, I figured I would share this post here anyway in the hopes of maybe learning that Google force-pushed an OTA update and pissed off millions of people who then filed a class action lawsuit because of it, and I just hadn't heard the news about it yet, but it was also recent enough that I could still get in on that action and recover at least some part of what I've lost in the past week.
And if not that, maybe I'll at least somehow get confirmation of having some of the worst luck imaginable, or validation that I'm not crazy, or just some sympathy and comfort from the community during a very dark time in my life when I sorely need it.
And I guess if there's even a modicum of hope I'll discover that I'm not completely alone in this world of **** that I now find myself in, and that there are others who have suffered a similar fate or misfortune as a result of either unbelievably bad luck with their phone, or Google forcibly cramming something very large and uncomfortable into an extremely sensitive area against their will - maybe even at one of the worst possible times of their life - then maybe there's even some hope left for my life; some point to even continuing it and trying to get out of the horribly-****ty, godforsaken nightmare I'm stuck in right now.
Or maybe I'll just learn that it is actually somehow possible to restore root to my phone without needing to wipe it first so I'm at least not quite as completely screwed as it looks like I am right now.
≈-∞
Google Pixel 5, OS 11
rooted with Magisk, no TWRP/recovery
recently forcibly OTA-updated to build RQ1A.201205.011
Click to expand...
Click to collapse
yes, automatic system updates are turned off. it's the first thing i do when i set up a new phone. so like i said, either Google still forced an update on my phone - despite having the automatic update setting turned off - or i have unbelievably impeccable timing on top of horribly bad luck.
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
leveleyed said:
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
Click to expand...
Click to collapse
This is a simple solution and has been discussed before.
Get the boot.img for your current build
Copy it to the phone and patch it with Magisk Manager
Fastboot flash the resulting patched image
Accidentally OTA updated my pixel, all fine but root gone
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted. Of course my root is gone now, but i want to root it again. Bootloader is...
forum.xda-developers.com
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
l7777 said:
This is a simple solution and has been discussed before.
Get the boot.img for your current build
Copy it to the phone and patch it with Magisk Manager
Fastboot flash the resulting patched image
Accidentally OTA updated my pixel, all fine but root gone
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted. Of course my root is gone now, but i want to root it again. Bootloader is...
forum.xda-developers.com
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
leveleyed said:
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
Click to expand...
Click to collapse
Try downloading magisk directly and installing. Or are if it already downloaded it and install that one.
leveleyed said:
yes, automatic system updates are turned off. it's the first thing i do when i set up a new phone. so like i said, either Google still forced an update on my phone - despite having the automatic update settingl turned off - or i have unbelievably impeccable timing on top of horribly bad luck.
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
Click to expand...
Click to collapse
I'm sorry this happened to you.
But I think you more than likely thought it was off, I don't see why Google would "force" updates for only you.
leveleyed said:
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
Click to expand...
Click to collapse
Try downloading Magisk v22.
There is no longer Magisk Manager.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
l7777 said:
Try downloading magisk directly and installing. Or are if it already downloaded it and install that one.
Click to expand...
Click to collapse
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
leveleyed said:
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
Click to expand...
Click to collapse
Yes you should be able to uninstall it manually. Won't hurt anything.
leveleyed said:
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
Click to expand...
Click to collapse
No don't use canary, use v22.
But why can't you inside it? It's in Magisk settling. If you must uninstall it, you can try that also then install v22
andybones said:
I'm sorry this happened to you.
But I think you more than likely thought it was off, I don't see why Google would "force" updates for only you.
Try downloading Magisk v22.
There is no longer Magisk Manager.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Yeah, I know it was off because I am paranoid about automatic updates. I have them off in both Play Store and for system updates. I checked the setting after I rooted previously, and after it updated. So I guess it was actually just extremely bad luck/timing to click the location of the 'reboot and update now' button within the same frame the prompt appeared on my phone's home screen so that I never even saw it before it started rebooting and applied the update.
andybones said:
No don't use canary, use v22.
But why can't you inside it? It's in Magisk settling. If you must uninstall it, you can try that also then install v22
Click to expand...
Click to collapse
I couldn't unhide it because I was unable to launch Magisk at all. Every time I tried, I was just prompted to download it.
After uninstalling/reinstalling Magisk, downloading and extracting the boot.img for my current version of Android OS, patching in Magisk, and flashing the patched boot.img, I'm happy to report that I've successfully restored root without loss of my data partition!
Thank you so much to everyone here who helped me to get this resolved!
Now, hopefully I can find an app (or perhaps a Magisk module) that will prevent the system update notifications/prompts from even showing up on my phone, thereby eliminating the potential risk of needing to go through this again.