Hi, I recently got a certified like new replacement VZW GS3 which freezes 10-15mins after the screen goes black while at the lock screen. To fix it at that point I have to pull the battery and turn the device on again. Buttons pressed while in this state do nothing, not even cause the menu keys to light up
Here is the sequence of events since taking it out of the box
Recieved it as 4.1.2 stock jellybean
Rooted, CWM Recovery, Unlocked bootloader - followed this guide - 29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii on rootwiki (can't post links)
Clean flashed Cleanrom 6 RC2, noticed the lockscreen freeze issue
Flashed lean kernel to see if it was a kernel issue
Clean flashed Liquidsmooth 2.4 to see if it persisted on other roms, it did
Odined back to full stock - issue persisted
Accepted new update that was released today - issue persisted.
The issue does not appear to happen when plugged into the charger.
I am now preparing the phone to send back to Verizon, but I am wondering if anyone has any suggestions. Based on google searches it seems that it is a hardware issue because changing roms/kernels/ going back to stock did not fix it.
Related
Hi
I got an issue after receiving an OTA update for my Nexus S. It was an official update asking my if I would like to install it. I choose yes and the device booted. It began to install and suddenly the triangle with exclamation mark popped up.
Since then, the phone only boots up randomly. Mostly if stays at a logo saying "google" in middle of the screen. No more Nexus bootup color game.
Is there any way to get this phone back to stock without being an expert?
It is a Nexus S 9020
I9020XXKD1
Kernel 2.6.35.7-ge382d80 android [email protected] #1
GRJ22
It was stock rom 2.3.4 and rooted at the time of the update
Any help is appreciated.
Regards
Martin
I am in the same ship Martin. Updated it to the 2.3.6 from 2.3.4 when I got the OTA. It was working fine, then the screen just stopped responding. It gets stuck at the google colour game now, and the screen turns off after some time. However, if I plug in the usb power charger, the screen lights up again, and the colour game proceeds a bit, then the screen turns off again. if i pull out the usb charger then, the screen lights up again. its been crazy since morning.
im sure that if we reset it, we can get it to work. but in my case i have been unable to do that. can someone tell us how to format/reset our nexus S?
Think I got it sorted.
Running 2.3.6. now, rooted. No loss of data for whatever reason.
What I did.
First of all, in one of those moments were the device was up, i copied a stock 9020T rom 2.3.6 on the sdcard.
In recovery mode, SDcard was never available. While reading through endless threads I found a recovery rom image called 5023_green.img
I had nothing to loose, so i flashed it using fastboot. A started in recovery and I got full access to my SDcard. I updated from full stock rom 2.3.6 I loaded to the SDcard earlier. Since then, no more issues. Surprisingly here I would have expected loss of root and wipe of all data. But this did not happen. All data is there in its place.
Cheers
Martin
Hello folks, first post, hope you can help.
My phone has a very specific problem that happens with every rom BUT with AOKP.
When the phone is on idle it just gets stuck, black screen, button lights are on. Only thing to do is pull the battery out. It also happened with the stock rom, so I tried to unroot it and give it to sprint but they couldn't take it because of a small crack on the screen(been there forever).
I came back home and tried to flash it with a custom rom again, and recovery was broken, so I flashed recovery on the device 3 times before it started working again.
I randomly chose AOKP and it was working pretty well, although it slowed down lately a lot. I tried to install JB on it recently and the problem returned, so I tried CM9 again, CM10 even tried Bugless Beast, same thing. I keep going back to the backup I have of AOKP and it's the only one that doesn't crash my phone.
I've attached the phone information so you guys can see exactly which built I'm running.
Bump.
Please help me fix my phone, I'm really at loss how to solve this problem,
Do you turn deep idle on? If so that could be the problem......when u flash a new rom, as your setting everything up, make sure deep idle is turned off.....the option is under advanced in the cm roms .......hope that helps
10....0011....10101
I installed a custom rom a few weeks back, and now am having problems with it.
When I attempt to turn it on, the boot animation won't even start before my phone decides to turn of and begin a constant vibration pattern.
I would connect to Odin and fix this, but when I load boot menu and the download screen, it does the same thing.
I was running Slimbean on android 4.0, then after having problems running that, I changed to Cyanogenmod. I then attempted to go back to stock because I was having problems with that too, and this is how I got to the problem I'm in.
Is there any way I can flash a rom without having to have the phone on? Anything I can do to fix this?
Thanks,
Hi Guys,
Prelude : 2 months back, my pure stock Moto G experienced i guess a battery drain and refused to start the next time onwards. When it was powered on, it just got stuck on the M Logo of the bootup. After the help from @lost101 & others, i was able to flash the custom recovery & rom and got the phone to bootup atleast although faced the same issue which i'll be writing below now.
Since that event has happened, everytime I flash a custom rom, the installation happens without any glitch which includes the rom.zip & gapps_pico.zip. Now when the ROM bootups, the startup screen shows up after which it starts optimizing apps. That's where is the issue starts.
For eg. optimizing app x (single digit) of 101, it doesn't goes beyond that point even after waiting for 15-20 mins or so, and i've to manually reboot using the power button after which again the optimizing apps screen comes up and this time the figure is optimizing app xx of 16/17, and in this turn the phone successfully boots up to the setup screen and works as normal. But after a few moments when i'm done setting up all my apps and everything, random issues turn up for eg. the notification quick tiles won't drop down. And when i restart the handset, again it shows the optimizing apps screen, the phones boots up to home screen but random issues pertain.
I've tried ROM's like Stock Debloated (5.1.1) , CrDroid, CyanPOP, RessurectionRemix all based on 6.0.1.
Before installing any ROM, i do an advanced wipe and all format the data. Right now the handset is running CyanPOP but the main issue is i'm unable to access the notification dropdown. It doesn't goes beyond the header.
One more thing, I installed RR (xt1022 specfic) with same pico_gapps on my Moto E & the rom booted up in no time and working as smooth as butter till date with no issues whatsoever.
I'll be helpful if some one can diagnose the issue. Thanks
BBThumbHealer.
Did you try flash stock firmware and then flash a costum ROM ?
@Eurofighter_ty : when the issue first happened, what I remember is that I tried installing the debloated stock ROM of 5.1.1 and not the pure stock having all the unnecessary gapps. And similar issue was encountered. Same thing happened with other custom ROMs.
Today I've now reverted to a previous version of CrDroid 6.0.1 released in April and it at least runs fine when in use although a reboot causes the same issue. However, CrDroid June update and CyanPOP had the issue in which the quick tiles didn't drop down along with refusal of bootup.
Try to flash the stock ROM via fastboot with all files
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.