Related
who can help me ,my nexus one can not make any sound,
I'm not sure if i can help you.
But I'm pretty sure anyone who does needs a little bit more information.
Is your N1 rooted or not? If yes which Rom do you use?
What happened before it stopped making sounds?
I could imagine that could be usefull for people trying to help.
Make a complete wipe and see if it helps
Hi!
Initially had this issue when I bought my N1 (a store sample) and it re-surfaced a week ago. Now this is from experience only, so I'm not pretending to know whether "your N1 fails to initialize soundboard for reason X"....
Issue that I solved succesfully is this:
I had no sound from the phone speaker (no ringing, no alerts, no music) - and actually all phonecalls were also silent (and ended up rebooting the phone about 15 secs into the call). What's freaky is that I was able to play music, hear alerts, take calls etc. over my headphones!
I was suspecting something to be wrong with the ringtones from the SD card.
So before wiping your phone (even with nandroid recovery it's a b*tch of a job) try this: Reset all alert tones to some default tones (which are in the rom). Turn N1 off, remove SD & sim, then let it reboot. Then power down, insert sim, keep SD out. Reboot. You should get the tones/sounds/in-call audio back after a few tries of these combinations. You can also try unmounting/remounting the card repeatedly. Also, it may help if you have a second SD card ready (empty or without). When you get the sound back, you can again start using your custom tones off the SD card.
(I usually wipe any unused ringtones in the process, and have even removed the tones from my card, and then reinserted them on the SD, which also seems to work after a few power-down/power-up cycles.)
Sorry, it's totally "unscientific" but if you have, say, half an hour to a full hour to spare do the above and your N1 will be back on track.
Pistolero0 is right we could use a little more info. Another thing that I would like to know is can you play sound through the headphone jack or Bluetooth or is it just the phone speaker.
Uh-oh... Just when I answered, I got the same problem again. This time, it's taken me a day to cycle/recycle. I've gotten the sounds back twice, only to lose them due to a random re-boot. I'm still suspecting it's a question of the SD notifications/ringtones messing up something in the system. (Or it's due to a certain app getting installed or uninstalled.)
So, the sound sometimes comes back, sometimes doesn't.
So, I'm also asking for help on this one....
Symptoms
No in-call audio whatsoever
No audio through internal speaker (the ear-speaker)
No audio through the speakerphone-speaker (on the back)
No notification sounds, no alarm sounds, no ringing.
Music cannot play (the track doesn't seem to advance).
All audio works over bluetooth headset - I can hear notifications/ringtones/alarms, screenlock sound, and even music (winamp & stock).
However, I still cannot make a call over BT (I do hear the ringing, but the audio doesn't connect on an incoming call. Outbound calls are completely silent on BT phones as well.
No sound whatsoever over the standard plugin HF-headphones (the ones that came with the N1).
So my plea is also, how do I fix this? (Wiped & Nandroid-backuped once, but the problem resurfaced, so I don't think that's the thing, then).
EDIT: Now trying the passimg method (FRG83-->GRI40-->root-->GRJ22+SU.zip) - I guess I should have done this aways back, (like 3months ago when I got my N1) but didn't.
There we go, froyoed for a while
EDIT: Now trying the passimg method (FRG83/D/G --> GRI40 --> root --> install GRJ22 update + SU.zip via clockwork) — I guess I should have done this aways back, (like 3months ago when I got my N1) but didn't.
There we go, froyoed for a while
Click to expand...
Click to collapse
What a bummer... Froyo, but NO sound. [O]I guess it is a hardware thing then after all, despite all the evidence I've seen so far?[/O]
RESULTS
Some hours later am now back on rooted stock GRJ22, but still no sounds. This must then be a hardware thing - albeit one that doesn't manifest itself always.
Suspecting something is wrong with the 3,5mm plug? (Or a wire is crossed somewhere, which silences the ear-speaker and speakerphone speaker alike).
Still suffering. Anyone got an idea?
Did anyone get their problem solved?
Well I've never had this problem but can I ask you a question when you flash do you use 3X system wipe and 5X data/cache wipe because I don't really think this is hardware cause or else in theory if it is hardware the problem should stay even after a reflash unless it is consistent with something else (example every time you hit X amount of memory used, every time you hit X amount of run time, etc).
So try the 3X system and 5X data/cache and see what happens.
Dude Random21 said:
So try the 3X system and 5X data/cache and see what happens.
Click to expand...
Click to collapse
You mean first do the system + data/cache wipes, then flash?
By system wipe, you mean the usual reset-to-factory status kind of wipe?
And how do you proceed with the data/cache wipe? Like, with Titanium or some other choice?
Sorry for the n00biness, I try not to flash schtuff too often. Anyway, I'm going to try your suggestion out as soon as I can.
Sorry for the late reply I haven't had much free time lately but why I say system wipe I mean either use temasek system wipe (if on Amon RA) or the built in wipe system option in clockwork mod depending on your recovery. And for data/cache that is the factory reset.
Update - One Factory Servicing Later, a fix of sorts
Okay. After two weeks of consternation I walked to the service center.
6 wks later (that would be today) I got my N1 back....
Motherboard had been replaced, rigid flex had been replaced, antenna had been replaced. Warranty repairs on level 1 & level 2 had been done. Anyway, quiiiiite happy now.
And yes, I do have sound. Luckily, I was still within warranty, and will continue to be. Lovely.
(Presently going back the FRG83 - FRG83D - FRG83G - GRI40 (gingerbreak root) - GRJ22 route).
As of right now I'm missing pretty much every file on my Internal Storage. No TiBu, no SMS Backups, no pics. However under storage in the settings menu it still shows 9 Gigs Free, which leads me to believe that its there, just not visible... There are some folders, but they are empty or don't contain the files it used to.
I noticed it at 2 AM when SMS backup & Restore notified me that it wouldn't backup because it couldn't find the SMS.xml file. I used Astro and ES File Manager to find it manually and I couldn't, at which point I noticed everything was missing.
Prior to that my phone was plugged into my PC, simply to charge. I was on the phone walking a friend through a Windows update and installing some software, and I plugged into my USB 2.0 port to charge the phone (3 hour phone call), which I've used multiple times. While it was plugged in I didn't really us the PC much other than google searches and reading news\posts\forums. I did however install Avast Antivirus cause I was walking her through it and I've never used it before. I'm hoping that had nothing to do with it. I googled Avast wiped my phone, and various similar phrases and didn't find any similar forum posts.
At this point, I could write a whole book about what might have caused it. I really have no clue. I'm looking for either anyone with a similar experience, or more importantly, anyone with a resolution.
Edit: I have a GSM Dev, Unlocked Rooted. Tmobile 4.4.2 using Faux Kernel.
That sucks dude! I haven't heard of this randomly happening on any phone I've had. Aside from recovery wipe accidents.
Drag!
Sent from my N5 cell phone telephone....
Haven't even been in recovery for a while. Even the backups made in recovery aren't there or aren't visible to the recovery either. I'm not even upset, I've lost things before due to my flashaholic tendencies, but I don't even flash stuff on this phone. That was one of the main reasons I kept this instead of my Nexus5, figured I'd be more productive not having to flash all the time. Might as well get a different phone...
More importantly I want to know the cause so that I and others can avoid it happening again. Almost makes me wish I kept my Nexus5, which now that I think of it, I have a fairly recent backup of on my PC. Who hoo!
Anyone with any thoughts or input, greatly appreciated.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
It's not a stock rom.
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Without getting a logcat there is nothing anyone can do except guess what the issues is.
donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
zelendel said:
Without getting a logcat there is nothing anyone can do except guess what the issues is.
Click to expand...
Click to collapse
I was hoping someone who had the same problem might chime in. What should I look for in the logcat?
johninor said:
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
Click to expand...
Click to collapse
I just clean flashed the latest version of the Lite ROM and it did not fix my problem.
donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
I tried a clean flash of the Lite ROM. That didn't solve the problem. I then flashed the latest factory image (MOB30W). I did not restore anything or install any apps except Google Play Music and Podcast Addict, which I am using to reproduce the problem. I still have the same problem. Bluetooth media audio is working indoors, but as soon as I step outside it breaks up and goes out completely for 20 or more seconds at a time.
I think that rules out the Lite ROM as the problem. Anyone have any ideas for me?
I googled looking for bluetooth audio breakup issues and I found a few things that were suggested to fix it. They were turning off the WiFi and and turning off GPS. I tried both and they did not help my problem. I didn't expect them to because they were fixes for people reporting general bluetooth breakup on specific devices, while I am seeing the breakup on Media Audio, but not Phone Audio.
If anyone knows of a better place to ask my question, please let me know. I've been searching and can't find an answer or a better place to ask the question.
After some research here may be a fix...
johninor said:
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
Click to expand...
Click to collapse
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
donnyutx said:
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
Thank you. I hadn't found that thread when I searched. I tried the several suggestions in that thread. One was clearing caches, which, of course, I had already done as a result of testing clean installs of the ROM I use and the latest stock ROM. So that didn't solve the problem. The other suggestion was turning off bluetooth scanning in location settings. I hadn't even known that was a thing. I tried turning off bluetooth scanning and wifi scanning this morning and used my phone all day as usual. It didn't solve my problem - no change at all. I had in an earlier test turned off the GPS and that hadn't helped either.
The second link, I believe is just a different way of installing ROMS and managing related stuff. I don't think that tool is going to do anything that I didn't do by installing the latest stock ROM with the flashall.bat script.
Alright, I have an issue that's been getting ridiclious the past few months. Ironically it all started when trump took office, but that's another subject....
On any rom besides a sense based rom, and i've tried alot, AICP, CM, Lineage, candy, etc etc. I'll have random reboots when getting text messages, or random reboots when trying to send a text message. I've tried all these roms wiped, with and without gapps, and i end up with the exact same result. Straight up random reboots.
The moment i wipe and restore the stock sense i imaged immeditately unlocking, no issues. I flash badboyz, no issues. I've been experimenting the past few months, and i can honestly say it only happens on non-sense roms. I thought it was because of gapps. So i ran CM11, which has been flawless since 2014, and without gapps, after a fresh flash and boot, the 1st text message i receive, instant hard reset.
The phone was s-on when i bought it, i took the latest OTA to grab carrier and OEM software and radios, then i did only the bootloader unlock, flashed TWRP, imaged my system. that was back in 2014 when the phone was first released. Since unlocking i've been running cm11 flawlessly for several months, at times a week or so of uptime, and i use my phone heavily.
Now it's to the point, when i flash a clean CM11, no gapps, just sitting on the table with the tethering on, either USB or wifi, it'll reboot. Sometimes itll get into a reboot loop and it'll take up to 10x of hard resets until it gets android fully loaded (mind you no gapps, no 3rd party, just the rom itself) before it's usable, that's if it doesn't run itself dead with the bootloops.
What's blowing my mind, if it's hardware, then why no issues on sense? Why only issues on non sense, and why now and not before? and the differences are all i can think of is software from: htc, sprint, google
When those 3 are removed, stability issues. but why now and all of a sudden?
anyone want me to supply something from adb? this has truly got me interested. I'm willing to copy and paste and upload some info. I'm really wondering what this issue is.
Thanks!
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
swerff said:
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Here's what I would say:
Because non-Sense ROMs don't have the same drivers, HTC developers, etc, they tend to be less stable as a group. The developers work hard to mitigate that, but the random reboots are the hardest for them to figure out. If you go through non-Sense ROM threads for years, you'll see that common complaint.
Now, as for CM11 being solid and now it's not, my guess is that updated firmware, radios, etc caused it. CM11 is quite a few years old and was written under older radios.
When the m7 was my daily driver, I had good luck on these three ROMs. They had the occasional reboot, but it was about once a week at most and rebooted right back in.
Resurrection Remix
PAC ROM
NusenSeven (Sense based from the m9)
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
swerff said:
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Misread and thought you updated radios recently. Not sure how replacing the battery would help, but you never know.
I had been running the three ROMs mentioned above with minimal issues when I used the m7 as my daily driver. I had run the latest RUU (see development section) to update to the latest radios, firmware, etc first. As I recall, all three were good. NusenSeven being stock based was most stable, but the others were good too.
swerff said:
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Worth a shot, but your instability seems relatively reproducible. Personally never done it. So I'm not sure that would help, but like I said before, you never know.
Well, tonight I'm going to replace the battery.
If that diesnt help, going to relock and ruu just to make sure, unlock and flash the same zip I've been using for years.
If there's still issues, something is going down regarding big brother not enjoying his stuff on my phone.
That's my take and opinion.
Sent from my One using Tapatalk
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
swerff said:
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Great! I'm glad it worked. It is odd, but what you say makes sense. Maybe the Sense ROM had something optimized in the kernel or ROM that the non-Sense ones don't. That's why I love this site; I learn something new everyday. Thanks for putting the results of your work in the thread for future members who may have the same problem.:highfive:
Well, update
It eventually got back into its old habits of randomly rebooting after ending phone calls or sending /receiving messages.
Soon after that it had issues if not coming out of airplane mode, which would require a hard restart, soft restarts were unsuccessful.
About week ago my son wanted to play on it, so i enabled airplane mode so he wouldn't accidentally call anyone.
Enabled airplane mode.
Handed phone to him.
Within 30 seconds I took it back, and in this time frame all he was doing was holding it/touching screen.
The phone now endlessly reboots to the initial HTC logo for maybe 5 seconds, goes black, and repeats. It will do this until the battery is dead.
Plugging in charger results in no battery charge state, screen or LED. After several moments of being plugged in with no signs of life, it'll light up to HTC screen, only 5 seconds later to go black and repeat, endlessly.
Holding power + volume down I can access the bootloader, which before it resets again I can pick recovery option.
It'll then reboot into HTC screen, saying entering recovery up at the top, but never doing so, and continue with boot loops.
The power button is not stuck, as holding only volume down will not encourage bootloader initialization.
Ideas?
swerff said:
Ideas?
Click to expand...
Click to collapse
It seems to have gone beyond the Sense working but non-Sense not working issues it started with. At this point, I'd probably try to RUU the thing back to stock and see if that fixes it. If not, I'd venture something hardware related. I wrote a guide on how to do this mainly because I kept forgetting all the steps. Hope it helps.
https://forum.xda-developers.com/sp...de-reset-phone-using-ruu-htcfastboot-t2876110
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
swerff said:
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
That's too bad. I don't know what to tell you my friend. I saw you could access the bootloader and select recovery, but if it's not stable enough to stay in fastboot, then that's beyond my knowledge capability. At this point, if it were me, I'd buy a new device or take it to a repair shop.
I'm investigating surface mount memory readers and the like.
I'm hoping to solder up something to pull the memory in binary.
The phone wasn't encrypted. There's a handful of photos I'd love to recover. Not having an external sdcard is stupid.
Sent from my One using Tapatalk
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.