Related
Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
Ever since the big update (023 or what it was called) my phone reboots its self now and then when I let it sit. It startaed doing it once a week then it started doing it many times a day. 5 days ago I did a repair and it has worked fine until today. It reboots it self again and you're stuck at the pin code.
I've heard that I'm not alone with this problem but few people seem to care. Well I care, A LOT.
How do I fix this.
Obviously it's something SE's done given the fact that it started after the big update.
Im starting to get very tired of this piece of crap and will soon flush it down the toilet. Hang ups, slow interface, reboots, poor screen sensitivity after a while, rediculous sound quality, poor bluetooth support. This is my last SE phone, they're totally incompetent. I tend to use my 9 million year old Nokia handset more than this infernal piece of f**k.
Well .. thanks ..
memory card error ! try copyin all your stuff on your pc then format the card in your phone then copy back worked for me !
GlennQ said:
Im starting to get very tired of this piece of crap and will soon flush it down the toilet. Hang ups, slow interface, reboots, poor screen sensitivity after a while, rediculous sound quality, poor bluetooth support. This is my last SE phone, they're totally incompetent. I tend to use my 9 million year old Nokia handset more than this infernal piece of f**k.
Click to expand...
Click to collapse
Oh FFS dont say that! You will get flamed on here by the kids who think this phone showed apple how to do it.
Slag the X10 of at your own peril! All I did was ask one question and made a comment about 2.1 on the phone and got 3 pages of people phanboying it up.
Your right though the phone is **** and mine is up for sale to get a Galaxy S But thanks for the tip I shall format the card so when I sell it it wont reboot while they are looking at it.
My phone keeps rebooting, and I don't care.
Just kidding. I had this problem before, but it seems to be better now. I was using the program Vault, and I hid away "Backup and Restore" and "SIM Toolkit". After I restored them to normality, I stopped having phone restarting issues.
Also, please don't start a flame war with your complaints about your phone. No one else seems to be having as many issues as you, it is probably something you are doing wrong.
krazykirk said:
Also, please don't start a flame war with your complaints about your phone. No one else seems to be having as many issues as you, it is probably something you are doing wrong.
Click to expand...
Click to collapse
See it's saying thing like that that adds fuel to the flames! Its an open forum so people can express opinions on it yet all I read on here is:
"It's your fault you cant use the phone" this does nothing but incite a retaliation from the poster as if some one said "It's not your girlfriends fault she doesn't cum its yours, I mean she cum for me last night" it would get your back up.
If somebody express an opinion about something does not mean they want a flame war I simply expressed my opinion and agreed with what the OP said.
krazykirk said:
My phone keeps rebooting, and I don't care.
Just kidding. I had this problem before, but it seems to be better now. I was using the program Vault, and I hid away "Backup and Restore" and "SIM Toolkit". After I restored them to normality, I stopped having phone restarting issues.
Also, please don't start a flame war with your complaints about your phone. No one else seems to be having as many issues as you, it is probably something you are doing wrong.
Click to expand...
Click to collapse
What do you mean by "I hid away"?. You mean that you just uninstalled Backup & Restore? I have not installed SIM Toolkit whatever that is.
same problem here.
phone reboots once or twice a day and it gets stuck at the pin screen.
this is really annoying.
will try to format the card, and there is another thread were someone said he replaced the battery and the problem was gone.
Found the probable cause of the reboot problem:
Check the "[GUIDE] SIM Card Locks randomly - Howto solve. (rooted SE X10i/a phones only)" in the X10 Anroid Development section.
Try killing Backup & Restore in the Program menu and voilá, the famous SIM card kill bug.
I disabled the SIM card PIN code so it doesn't stick there. The bug is still there but the phone works.
Great work SE - No just kidding - You bunch of amateurs.
well ... the method is for rooted devices, so there is no solution for this yet.
i did format the card to see if i solved anything.
if it reboots when your reading from the card like useing MP3s or looking at photos ! its becuase ther is a bad sector try poping your card in a card reader then let windows tell you there is a error and let it fix this !
i know this sounds stupid but i too had this problem and hav noticed it does it when the battery is at a certain temp (hot) i mite be wrong !!! or is it just a coincidence
Well... formating the card does not help.
Any other ideas?
berbecverde said:
Well... formating the card does not help.
Any other ideas?
Click to expand...
Click to collapse
Do you use a taskkiller? If so stop killing 'backup and restore' .
GlennQ said:
Try killing Backup & Restore in the Program menu and voilá, the famous SIM card kill bug.
I disabled the SIM card PIN code so it doesn't stick there. The bug is still there but the phone works.
Great work SE - No just kidding - You bunch of amateurs.
Click to expand...
Click to collapse
You don't need a taskkiller on Android. The whole problem with this bug is that people are trying to kill apps/services that shouldnt be killed in the first place.
This is a firmware bug...
I have had a similar problem... however my phone is a new one from the SE repair facility in Poland. It has the latest firmware and the phone exhbits the rebooting with no SIM or SD card installed. The problem also doesn't appear to be related to battery temperature as it can also occur from cold.
I will try an unbranding and see if the same issue exists.
Vin87 said:
Do you use a taskkiller? If so stop killing 'backup and restore' .
You don't need a taskkiller on Android. The whole problem with this bug is that people are trying to kill apps/services that shouldnt be killed in the first place.
Click to expand...
Click to collapse
I am not using any task killer.
Mine just started rebooting itself today too after owning it for two weeks. Have been updated to firmware 026 rooted for a few days and notice it only does it when the battery reaches lower than 50%. Gonna re flash it tomorrow and re root it. Reformat the sd card. Will update on if it keeps rebooting.
Sent from my X10a using Tapatalk
I did a Reset To Factory defaults and 24 hours whitout phone reset.I hope this did it.
berbecverde said:
I did a Reset To Factory defaults and 24 hours whitout phone reset.I hope this did it.
Click to expand...
Click to collapse
That did't do the trick for me. Taskkillers will force the bug to trigger, so will the backup & restore program (that seems to runt constantly).
The fix would be to: FIX THE FREAKING BUG IN THE BACKUP & RESTORE PROGRAM, or simply delete it (which is impossible now).
Idiot SE.
Well, it seems mine is rebooting too.
I don't know how often... i just saw it once... out of the blue.
Phone was in standby when happened.
I watching tv and i saw the display turned on with the boot animation and then i figured out what happened.
I uninstalled the backup tool with Titanium. Let's see...
2 day and no reset,i am happy
Have you ever encountered this phenomenon where, when you click an app it just takes you back to the main page. The app does not load at all.
Why does this happen? What is causing the app not load.
The only way for me to work around this problem, is to restart the OS. Powering down and then powering up again solves my problem. There have been no need for me to pull out the battery or use the Reset feature.
But it puzzles me what is going on in the back ground to cause this problem.
Marketplace is one app that i had problems with at times.
I just need to understand this problem. Cos i do not want to keep rebooting the phone to solve such problems.
I noticed this behavior yesterday -- specifically with the Marketplace App after my son had tried to install the Assasin's Creed demo. Seemed like the Marketplace was in a "hung" state at that point, which only an OS restart would resolve -- either that or waiting for the OS to fix itself, if that's possible.
You're not alone, and it's certainly something that Microsoft will resolve in their 1.1 update.
Honestly, this was such a minor issue for me, that I really did not pay too much attention to it, but it IS there, and I think it is an OS problem, rather than the LG Optimus' fault. How I fixed it was that I launched something else, like Facebook or Twitter ( basically something third-party ), and then pressed the start button. It seemed to resolve the issue for me, not sure what degree of success others will have.
The marketplace is fairly buggy and can cause you in some pretty irritating issues. I know Microsoft is working on it... with new servers and services sometimes getting everything right can take a bit...
Here's how I bricked my phone, for the ones who're interested:
I think it's a pretty funny story, so keep reading if you're searching for some entertaining story.
So I Bought a flipout because I wanted a small phone. I was pretty satisfied by the phone and it's performance, althought it's kinda an effeminate phone. Anyways, before I knew it (When I booted up the phone for the first time) I was disgusted by Orange's laggy intro: it was supposed to be an explosion followed by an implosion which created the Orange logo (sort of XBOX style). The reality was less: a very laggy 2 or 3 fps intro. Bravo Orange if you were actually aiming for this rate.
When I boot up the phone it shows the menu just like any other phone, but it came with another disgusting fact: MotoBlur. Lag, lag and lag. There it was, in all it's glory:
- It's laggy (not as much as Orange's intro...)
- Uses default services (calendar, gallery) with some unfinished 3D features (that caused needless lag)
- "Happenings" which connects your twitter, facebook and other things.
Although I have to say, I did like the lil tab that shows above and tells you on which screen you were. It looks kinda like the following (excuse me my drawing skills):
.: : . |^| . : :.
resp. -3 -2 -1 0 +1 +2 +3
Anyways, I had to get rid of this "MotoBlur" and the first thing I had to do was to root my device. I remember the days with the G1 which were a hassle to just root your phone, so I was hesitating if I really wanted to go through all this again...
But after a lil search, I found that nowadays we have superoneclick, androot, z4root, etc... etc... So I tried one of these "new" apk's which gave me a small error, so then I tried z4root which was quite easy, fast and simple. I was in. Things were going my way, hell, I even found a brand-new-looking 4GB microSD on my work. Just out of nowhere there it was, very small, laying down on the ground waiting for me to get picked up.
What goes up, must go down...
So there I was with my first steps trying to remove MotoBlur, and although I knew there were tut's about how to remove Orange and Blur, I just couldnt wait. I made backups of my system apk's with Titanium which was quite easy, and it was that precise moment when I was like "GET!", i'm sick of this MotoBlur, let's remove these "things". They are right in front of me, just get rid of them... And while continuously hitting the "remove" button I was daydreaming of a simple usefull handy phone. Bam, bam, bam, I deleted one app after the other, even Google Talk didn't had a chance. Everything was going smooth, bye Blur.Calendar.apk, bye odex, bye Blur.gallery.apk, bye Blur.happenings.apk,... ... ... about 20 apk's later, I was quite satisfied.
But you know how it goes when you just delete stuff without greater knowledge. You BRICK your phone. But people, this was just the start. I had some force close after this one man operation, but my phone was smoother. I have to admit, things were comming unexpected. First I couldnt find my gallery (removed). Then I found out I couldnt download anymore from the Android Market because I deleted Blur.calendar.apk which is connected with Calendar.apk which syncs my G-Mail account which is needed before you can download anything from the Market. Hah! Owned.
Backups.
So there I was having these problems, but the phone still works great. I have to admit I silently thought: luckely I made a backup, and was kinda proud I wasn't one of those noobs who just goes forward without a save game, right? Right? Guys...? Anyone...? . ... ...Wrong! The reality was I couldn't even "restore" with Titanium. The backups weren't real backups, but just data-backups which were stored on my sdcard in .tar format. Aaarrgh!
No problem, no problem. There has to be a way to fix this, someone did this stupidity before me. Obviously. Ofcourse. No?
When I was searching about why I couldn't fix my Titanium backups, someone answered to someone else that's because he couldn't sideload the apps. He needs to root his phone in a way so sideloading is enabled. Great! Sideloading it will be then.
Sideloading is def a great way to install .apk's without the market, because I tried a factory reset (hoping that would solve everything) and I couldn't download anymore from the market. I had to sideload ASTRO which was successful with the right ADB drivers - even though I didn't knew what ADB meant I did register on MotoDev's website (so I can download the little bastard).
Easy peasy. Now I'm back on track with ASTRO and an easy install of Flan Gallery (fixed camera) replaced my gallery. We're off to set!
Despite this minor victory I was aware I'm still not were I wanted to be. Factory reset doesn't get me were I want to be and I'm still having issues. But no problem no problem. This time I'll turn my questions to the community, not google. That's eventually why there is a community? That's why we are open source? Yes. Score. Win.
So maybe some knowledgeable people will reply because they can help the ones who are trying to learn. I think I'll start with how to fix the calendar-issue and then I'll try to make a ROM-backup, so I can install a new ROM or whatever. That's probably a better idea then before. Cool, I even got a quick reply by someone who told me to go to this-and-this site, which is better for noobs. Allrighty then...
Trying my own way.
Since things weren't going were I wanted to, I thought now it's time to give it a real last try by searching about this mystery "ADB" and eventually to push some apps into system/app/ so I could fix all this misery. I found what I was searching for, however the tut about how to push apps sounded like someone was holding a gun against the writer's head. It really sounded like he wrote it against his will.
Desperate attempts.
I started today (15 april) around 5pm local time with this whole pushing-thing because I thought I had the knowledge that I needed and even surprised myself by actually successfuly pushing some apk's using a quick and nice XDA how-to, but then things went from worse to worser. I pushed Blur.calendar.apk, Blur.service.apk, Blur.email.apk, Blur, Blur, Blur... Ironically thát what I wanted to remove at the start came voluntary back in my system/app/ of my phone.
That's quite funny especially when I rebooted my phone and I kept getting force close com.motorola.blur.service.main and I couldn't get around this except by using voice-commands (double tap home button). "Find ASTRO" I said. Finding ASTRO... Opening ASTRO... Ingenious! It was quite amazing that this feature actually works without any bugs or misunderstandings. So I started root manager, rebooted the system with r/w settings so I can try a final attempt by trying to remove blur-service.apk from the system/app/ which actually didn't had any impact. Nothing really happened.
The end.
And there I was having these problems, and the phone doesn't work. A friend of me adviced me on Steam-chat to hard-reset the phone. I could care less, but we had a little discussion about what has more effect hard-reset or factory-reset? Btw... Holding down the power button and the camera button...?! The phone doesn't even has a camera button! Hilarious.
I eventually did the hard-reset with another tut and now the phone is... ehm... kinda... pretty... bricked. It just boots up and then gives 1 continously looping force close of the blur service (which I allready had), and another force close when I finish setting up the blur account wizard. At the end of the wizard it just force close and shows the wizard again,... and again... and again...
Mathematical summon:
+1 noob
+1 bricked phone
- $$$
- (a lot of) time
+ frustrations/stress
+1 story
Equals a possitive outcome?
i've not rooted my Flipout as it seems there's not much you can do with a rooted one anyway
but I've done bad flashes before...many times
and i've always been able to rescue those phones by flashing the original rom. just wondering if this might be an option for you..
See if you can flash that device using RSDLite, I can see some tuts in this board that features this, likely that debranding guide. Hold up+power when it's off and boot into flash mode, not camera+power
A brick = a dead phone, no boot, no flicker, nothing. If it acts like a brick it's a brick, otherwise it's just a messed up phone. I'm sure you'll be able to recover yours...
Sent from my HTC HD2 using XDA Premium App
Moto phone + rsdlite + flipout sbf= fixed phone. Just find those two things and you can restore your phone back to fresh out of the box state again. Promise.
Sent from my SGH-I897 using Tapatalk
Yeap i just did it first try hold "up" button on the keyboard + power for 4 sec then plug usb. in flex options i checked everything and it all went god then
Just got this today and it's great besides being a bit smaller than my g6 and because of front camera design only being technically 5.5in screen for most apps especially games.
However since I have had it, it has randomly rebooted itself twice for no real apparent reason. Is this a known issue or something anyone else has experienced? I want to try to get a bit more information on it before contacting the eBay seller. It is a refurbished.
I have never experienced a random reboot. You might want to try factory resetting your phone and then setting it up with the fresh start option instead of restoring from a Google cloud backup. Was your phone on Nougat or Oreo when you received it? Were there any major software updates?
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Nickvanexel said:
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Click to expand...
Click to collapse
Must be rogue app, had mine 3 months and never had a glitch or reboot.
Sent from my PH-1 using Tapatalk
If you are still having the random reboots you might want to boot your phone into safe mode to verify that a third party app isn't causing the problem. Since your phone was refurbished it's also possible that it was damaged by the previous owner or returned for the same issue you are experiencing. I did read that some early PH-1 buyers had to return their phones because of hardware issues like overheating.
Just did it again while using chrome. Just froze up for a few seconds and restarted. Doesn't seem to be overheating and the first time it happened before I installed anything I think. Guess I'll try a reset and go from there.
Factory reset twice now. No 3rd party apps installed. Updated all apps on Google play. The default phone apps.
Now the phone is freezing and rebooting itself constantly. Out of control. I am in safe mode right now and hasn't frozen yet. I don't know what the hell is going on.
Would love to be able to fix this issue myself without having to do return shipping. I have contacted the seller already though.
If it doesn't freeze or reboot at all in safe mode that usually means an app that you downloaded is causing the problem. The normal thing to try would be to factory reset the phone, download one app and see if there are problems. If the phone seems to be fine download a second app and use the phone long enough to see if the phone is stable. If it seems fine download a third app and do the same.
That's obviously very time consuming and if you were running a phone with heavily modded code like OnePlus with Oxygen it would probably be worth the investment of time. But this phone runs stock Android. Unless you are installing something unusual that might cause stability issues what you are describing sounds like a hardware problem. You might have bad memory for example and not enough is going on when the phone is in safe mode to trigger the unstable behavior.
I think returning or exchanging the phone you bought is definitely your best course of action. I really like this phone but it sounds like yours is defective or damaged.
The only other thing that comes to mind is that sometimes if you own more than one phone the Play Store will show apps that aren't compatible with the phone you are actually using. Dialers, messaging apps, camera apps and music players made for a specific phone brand aren't usually compatible with other brands because they need modded framework to function properly. Some apps that definitely are not compatible with this phone do show up in my Play Store Library available for download. Is it possible you are downloading an incompatible app?
I factory reset and haven't installed a single app. Just updated everything that was stock with the phone after reset. I was thinking faulty ram too, seems like it is.
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Grab a BTS zip from the back to stock thread... And flash that...
I'll bet however it was updated had some yuck in it...
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Someone in the Essential stock ROM dump thread just described the exact same behavior that you are experiencing. He hopes reflashing stock will fix it but since it's identical to what's happening with your phone I think he's going to end up disappointed. You might want to check out his post and see if he has any luck. It was the latest post in the thread so it should be easy to find.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page41
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Nickvanexel said:
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Click to expand...
Click to collapse
Sorry I didn't notice that. I haven't done any flashing on this phone but I know I read that people with the Sprint phones were flashing the regular stock image to get rid of the Sprint apps and get updates from Essential rather than Sprint. But if you don't want to unlock your bootloader you can download official factory images from the Essential website and sideload using a computer. Flashing instructions are on the download site.
https://www.essential.com/developer/current-builds
Alright I reflashed the latest firmware from essential page via adb sideload. I highly dout it worked but I'll see.
What would I need to do from here to do a complete fresh reflash completely overrighting any trace of the old os? I still want to keep it stock but doesn't matter if I need to unlock the bootloader. Just want a complete wipe of the old os and fresh reflash to be sure any traces of corruption are removed to be sure if it's a hardware issue.
That's easy on single partition phones but much more difficult on phones with an A & B partition like the PH-1. You definitely need to unlock the bootloader. On my Pixel XL you needed to flash the factory image separately to partitions A & B to ensure there was nothing left from before but the procedure might be different on this phone. I went through the flashing instructions when I got this phone and think if you flash the full restore stock image it supposedly returns both partitions to stock automatically but that definitely didn't happen on the Pixel. Considering that this phone is supposed to be easy to hard brick (which was virtually impossible on the Pixel) I wouldn't chance it unless you can't return or exchange the phone from the seller.
Well side loading the ota from essential website didn't work. I'd say it's already hard bricked. Still crashing after a while of using it. Last night I loaded as many apps at one time as I could. Got maybe 10 opened at once before it crashed. Seems like faulty ram to me.
Wife just had it happen on her new White one twice today while playing Pokemon GO.
She says she also had her podcast app and hangouts open but minimized and not being actively used in the background.
She's on a fresh install of Oreo 8.1 with the Gcam mod by MGC_5.1.018_Urikill_vXXII.apk using the settings suggested by aer0zer0
Anyhow I hope its just a completely random fluke and not a serious issue as I have a new black one from Amazon in the mail and would really hate to have to return these otherwise wonderful devices.
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Nickvanexel said:
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Click to expand...
Click to collapse
Ouch okay that most certainly sounds like a bad hardware issue as you suspected earlier.
Thankfully in her case the reboots were well apart from one another and the phone was fine after the reboot. Even let her play PKGO.
I mostly came in to comment to hopefully help by voicing that it had happened and the circumstances in which it did for her with the idea it might pinpoint some flaw in the overall system if there was one.