Database Develop

What's wrong with my Note 4? Slowdowns galore and freezing

DOK2 all stock firmware here.
Got my phone back in december. My phone has been chugging alone fine until yesterday. not sure what happened but the lock screen takes minutes to come back. I tried doing a factory reset via software and when I did that the phone was still sluggish. Tried a stock recovery reset, and afterwards when i tried signing into my account and connecting to wifi at the initial setup the phone just rebooted back to the start screen again which i thought was real odd. It's currently restoring apps from the app store right now and it intermittently reboots itself while doing stuff. all while it's completely stuttering if i try to use it...
Is my phone starting to have internal memory failure? no SD card in the phone at the moment.
Should I try reflashing the DOK2 firmware via odin and then doing a reset again? Is that even possible with all the restrictions?

used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed

Check this thread for a workaround. I use an app to keep my phone from going into deep sleep.
http://forum.xda-developers.com/showpost.php?p=64584244&postcount=39
dtrinh4000 said:
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Click to expand...
Click to collapse

Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.

Bruce lee roy said:
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Click to expand...
Click to collapse
Did a factory reset and cleared cache, reflashed stock DOK2 from sammobile website using odin, cleared cache. things were going a little bit better at first but now just stuttering all over the place and randomly rebooting still. I only have very few apps downloaded, including facebook updates, instagram, all the samsung and google crap that forces updates...
Also want to add that booting into recovery takes a very long time, longer than i've ever noticed it taking... 7 min+ sometimes it will say "installing system updates" with the android guy chugging along, other times it will just have the android guy chugging....
Is there anything else I can try? Is there something I can test to verify that it's a hardware issue and not a software problem, like a flash memory checker?
This phone is out of warranty, and knox has been tripped so I have very limited options here. Would the Tmobile store let me do an exchange for a fee?

bump... anyone? am i really screwed?

dtrinh4000 said:
bump... anyone? am i really screwed?
Click to expand...
Click to collapse
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822

cuteman said:
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
Click to expand...
Click to collapse
I do get some touch wiz crashes and random app crashes . since I'm on dok2 is there any other rom or recovery I can flash ? Or so some super duper erase method? I'm pretty much ready to cut my losses and sell it for parts on eBay.

i'm not alone it seems
http://forum.xda-developers.com/note-4-tmobile/help/note-4-major-slowdown-bugs-boot-loops-t3311297
http://forum.xda-developers.com/note-4-tmobile/help/looping-screen-t3319204
http://forum.xda-developers.com/note-4-tmobile/help/reboot-shutdown-wont-removing-battery-t3316875

I am having same issue. Was running stock until 3 days ago, when I got fed up with the stock reboot and slow-down. I guess it's time to save up and get a new phone.

Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....

dtrinh4000 said:
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
Click to expand...
Click to collapse
Well, fool me once.... Having spent $800 on a phone that broke in just over a year, hell would have to freeze over before I give Samsung any money again.

Note 4 issues (my Take) post 11-06-2016 (Take the Poll)

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

Issues upon issues upon more issues!

I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.

Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..

Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.

Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time

Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.

bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome

bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.

romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol

Is there a way I can test the internal memory?

Factory reset has not restored Auto-Rotate, Active Edge, and the "ear sensor" when making calls

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.

Question mi 11 ultra keeps freezing

hi,so i got my phone with china rom which the seller bootunlocked it and changed it to the offical global rom like 6 months ago and from 3 4 weeks agao im facing a really bad problem,before that i got the problem that i tapped one time and the device would think i've tapped 2 times and it closed the app,i thought it's because of the screen protectors.but from 3 weeks ago i'm facing these real problems:
1-phone suddenly freezes for 3 or 4 seconds then it's responsive for like a second and again till i close all apps and then it gets a little better but after i restart which sometimes leads to a boot loop, it doesn't get smooth and normal, even after that,after some time like 30 40 minutes it freezes again. even the keyboard freezes.
2-if the freezing continues i get a "---- app is not responding wait close",sometimes the miui system shows the same error but if i click on the wait it wont crash or such, it justs behaves like it was before showing the error.
3-sometimes after the restart the battery percentage is shown 0, which i'm pretty sure it isn't. upon restarting again the problem solves.
4-sometimes in specific applications my tap is considered a holding and shows me the holding menu.
5-sometimes i get glitches and lines in some parts of google chrome webs which fades by just scrolling,specially if a video is playing on the web page.
the phone didn't got any physical damage in the past.
i've tried these but no avail:
1-updating the miui
2-disabling virtual extension memory
3-factory reset
4-flash and install the offical rom which somehow lead to a bootloop.
5-flash and install the xiaomi eu stable rom which didn't go on a boot loop but the freezing continued
6-flashing and installing the official rom which this time didn't got stuck in a boot loop but right after booting showed me the "miui is not responding" but i setuped the phone and it sill got the freezing problem.
i used multiple benchmarks and even filled my ram with some app to see if it's the stress leading to a freezing but all the scores were perfectly normal even for storage and ram and the phone wasn't freezing during the tests and benchmarks
sorry that the text got too long but i'm really desperate.

Try in safe mode to rule out a buggy 3rd party app. Run for a day or more.
If it fails that it may be a buggy system app.
Otherwise it may be a hardware issue.

blackhawk said:
Try in safe mode to rule out a buggy 3rd party app. Run for a day or more.
If it fails that it may be a buggy system app.
Otherwise it may be a hardware issue.
Click to expand...
Click to collapse
so i entered the safe mode but it's a black screen with the text : safe mode under it .then it went to booting itself with some vibrations and the non ending mi logo on the screen.

mr.fazeli said:
so i entered the safe mode but it's a black screen with the text : safe mode under it .then it went to booting itself with some vibrations and the non ending mi logo on the screen.
Click to expand...
Click to collapse
Sounds like the firmware is corrupted. This normally shouldn't happen.
Possible rootkit, a hardware failure or perhaps a single event upset hit the kernel or bootloader.
A complete reflash (impossible with a locked bootloader!) will purge any malware, remedy a SEU but not resolve a hardware failure.
Make sure all critical data is redundantly backed up now. It may crash and burn at any time running like that. Not good.
Return for warranty repair if possible.
That's my take on it, someone more familiar with that platform may have a better plan.

blackhawk said:
Sounds like the firmware is corrupted. This normally shouldn't happen.
Possible rootkit, a hardware failure or perhaps a single event upset hit the kernel or bootloader.
A complete reflash will purge any malware, remedy a SEU but not resolve a hardware failure.
For the latter a different rom may work if it bypasses the damage.
Return for warranty repair if possible.
Click to expand...
Click to collapse
I’ve flashed it 2 times with the mi flash tool and one time with the xiaomi eu rom fastboot registery. unfortunatly iv’e got no warranty for the phone in my country,so i fix it or i have to sell it cheap.

mr.fazeli said:
I’ve flashed it 2 times with the mi flash tool and one time with the xiaomi eu rom fastboot registery. unfortunatly iv’e got no warranty for the phone in my country,so i fix it or i have to sell it cheap.
Click to expand...
Click to collapse
See my previous edited post. The issue may be the bootloader has been corrupted and/or a hardware failure. You're in way deeper than I ever had to go with the firmware on an Android.

blackhawk said:
See my previous edited post. The issue may be the bootloader has been corrupted and/or a hardware failure. You're in way deeper than I ever had to go with the firmware on an Android.
Click to expand...
Click to collapse
Can i flash or reset the boot loader? Also thank u for helping me.

mr.fazeli said:
Can i flash or reset the boot loader? Also thank u for helping me.
Click to expand...
Click to collapse
Not if it's locked. Someone may know how to unlock it here, I do not. That may not be the issue though or the root cause... You're welcome but I'm afraid I wasn't much help.
Try some Google searches for that manufacturer and devices with the same issue. Add xda to the searches to search XDA, that works better than the XDA search engine.