[Q] Samsung Note 3 Lollipop Issues (Sprint Stock Build) - Sprint Samsung Galaxy Note 3

So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???

jcohenlv said:
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
Click to expand...
Click to collapse
I can't say I had any problems like this. I was running Stock rooted OC5 for a while and had really no problems with it. I didn't have any pattern or pin unlock though, so maybe it would have been different? I would have stayed stock but my Flashaholic took hold and made to start trying out other ROMs.
As for rooting, I have found it very easy to root this phone. I haven't had a problem either using auto-root or flashing superSU.

Factory reset is easy.

w7excursion said:
Factory reset is easy.
Click to expand...
Click to collapse
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck

jdelano said:
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
Click to expand...
Click to collapse
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much

jcohenlv said:
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
Click to expand...
Click to collapse
Glad to hear that, I hope it stays that way

You should read more before trying to root

Related

S3 Lock Screen Issues - Getting Stuck

weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
I think I have the same issue as you, but in case I don't I will post what I am seeing on my device.
In about the same frequency, say once in every 15 unlocks from phone sleeping, the screen will come on but will be completely unresponsive. Doesn't matter if it is swipe unlock or pin code etc, there is no response to touch input on the screen. In fact, I think the screen is just frozen or the operating system is causing the lock screen to hang.
If the lock screen is hanging, pressing power will:
(a) sometimes make the phone sleep again
(b) make the phone screen kind of glitch/blip and then it takes input again
(c) does nothing and the screen remains on and hung/frozen
Occasionally mashing both the volume key and power key will help fix it, but usually if it is completely stuck I have to do a hard reset (holding HOME+VOL UP+POWER and then selecting reboot from the menu).
Now - I think this could be an app, but not sure.
When I first got the phone, set it up with my Google account etc, it went ahead and downloaded ALL the apps I had installed on my previous phone (HTC Sensation running Android ICS). So if it is an app, it is having issues with this phone, not the OS, imo.
I uninstalled all those automatically downloaded apps, and used the phone for a bit without my normal stuff installed. Then started installing apps singularly.
I think it is either Facebook or Alarm Clock Xtreme. The latter makes more sense given it would be polling the system to find out when to go off, so it is doing more in the background I would expect than Facebook or any other non-system app.
Other apps I have installed/running:
Swiftkey X
3G watchdog
Dolphin Browser HD
ES File Explorer
Winamp (locks without this running or running at all in lock screen mode, so that is not the issue)
Real Calc
Google Drive
Facebook
Alarm Clock Xtreme
It is quite frustrating for a brand new phone to have these issues. Not sure if it is hardware related, and if it is, I want to find out soon so I can take it back to carrier within their 28day device swap RMA period.
Thoughts?
So others may try to help or identify the possible cause / fix .......
What is your firmware version?
Are you rooted, custom ROMs or Mods etc?
Stock ROM,Baseband : XXLE8. Build No :XXALE9.
But my screen responds after i press wake button again. You are right seems to be issue with the app. i will just compare your apps and below are the ones which are common between us.
Facebook
3G watchdog
Dolphin Browser HD --i never use
Google Drive
a fix that worked for me
Steps to the solution that worked for me (so far) were to uninstall:
1. Alarm Clock Extreme (no noticeable result but I wasn't needing that application anyway)
2. I had WIFI Fixer installed because of the problems I experienced with the WIFI connectivity on my Galaxy S3.
I disabled that application and problems seemed to go away for a time, but every so in a while they resurfaced. Much less often than before, though.
I was still stuck with my WIFI problem anyway, so I looked into solutions for that problem and since I could not find a workable solution I uninstalled Wifi Fixer and started tweaking my WIFI settings.
While doing that I noticed that disabling "Network Notification" under the Settings -> WIFI -> Advanced tab fixed both my problems.
Now I can't be 100% sure this solution works for all, but I am pretty sure the application that created the problem was "WIFI Fixer".
It's been more than 4 hours now without the "disabled unlock screen from hell", and I’m very happy.
LOOOL
Actually...
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
This is not a solution, this is a work-around....
It will remove the standby wifi.... My phone was at 0% battery in one night... But actually yes, the phone doesn't hang up when unlocking.
Someone who had replaced the phone could tell me if the problem is solved with a new one ?
calint said:
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
Click to expand...
Click to collapse
Sadly having the same issue! and only sing LG6 and LG8 of the UK firmware was release.. out the box was LG4 if I am not mistaken... have been putting off custom roms due to the fact stock one is so far good..
This fix seems to be working..Thanks! will live with battery drain as data is expensive in SA!
khan.dharvesh said:
weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
Click to expand...
Click to collapse
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
It worked!!
douglasurbano said:
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
Click to expand...
Click to collapse
This worked for me!!! Thank you!! I was about to take a hammer to this phone! :good:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
RhavoX said:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
Click to expand...
Click to collapse
Not sure what ROM and kernel you are using, but at a big guess, try reflash another kernel or with less aggressive settings.
Sent from my GT-I9300 using xda premium
hey guys. I have a problem with my s3's lock screen similar to the described. whenever I press the power button to unlock, it takes 2 second for the screen to turn on. Anyone got any ideas on that?

[Q] Problem when my phone is recovering from Sleep mode

Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service

[Q] X10 Mini Pro bricked while locking bootloader

Hi!
I installed "U20_nAa-14_2.6.29.6-nAa-14" and "MiniCM7-2.2.1-mimmi" on my phone. The mobile network didn't worked, so I tried closing back the bootloader. I made it with "s1tool relock.exe", and it really closed it back. The instructions I followed while doing it, said that I shouldn't start the phone after doing the relocking and disconnecting it from the computer. Accidentally I switched it on, and now it won't turn on. Only the startup vibration and green led flash. If I connect it to the computer it keeps connecting and deconnecting, I don't know how to open up the bootloader again if it's possible at all.
Is it repairable?
Thank you for your help.
Rodage said:
Hi!
I installed "U20_nAa-14_2.6.29.6-nAa-14" and "MiniCM7-2.2.1-mimmi" on my phone. The mobile network didn't worked, so I tried closing back the bootloader. I made it with "s1tool relock.exe", and it really closed it back. The instructions I followed while doing it, said that I shouldn't start the phone after doing the relocking and disconnecting it from the computer. Accidentally I switched it on, and now it won't turn on. Only the startup vibration and green led flash. If I connect it to the computer it keeps connecting and deconnecting, I don't know how to open up the bootloader again if it's possible at all.
Is it repairable?
Thank you for your help.
Click to expand...
Click to collapse
Flash THIS with flashtool. The download is about 213 MB, although it may say differently when downloading, just wait till it's finished.
It's original Sony Ericsson Firmware and can be flashed on a device with a locked bootloader. Not sure about the version, although it says 2.1.1.A.0.6, it may be older, but i don't have a U20, so I can't check. It should be possible to upgrade it with Sony Update Service if it's an older version. Good luck.
Thank you!
It worked. Can I ask that too, is there a safest way to solve the no network problem?
Rodage said:
Thank you!
It worked. Can I ask that too, is there a safest way to solve the no network problem?
Click to expand...
Click to collapse
Depends on your simlock certificate or how your phone was unlocked from it's original network. There are two or three methods (msm_7227_semc, msm_7227_setool2, and maybe one for omnius too) , just try them and check if you get a signal before you flash any custom firmware. If you don't get a signal, relock it again and try a different method.
Flashtool used to be quite good at figuring out which method worked best, but I don't know if that still supports unlocking 2010 devices. I've got 0.9.13 and there is a BLU (Bootloader UnLock) button.. just try that
I opened it again with msm7227_semc, bacuse the others didn't worked, and installed it again. Now everything is fine, but the home button and the screen lock still not works:/ I think I'll leave it this way, and not risk one more time my network connection.
Thanks for your help.
Rodage said:
I opened it again with msm7227_semc, bacuse the others didn't worked, and installed it again. Now everything is fine, but the home button and the screen lock still not works:/ I think I'll leave it this way, and not risk one more time my network connection.
Thanks for your help.
Click to expand...
Click to collapse
If it's unlocked and the network is still there you can do whatever you want with it There's no need to lock it ever again so you can experiment with kernels and roms all you want.
What was the matter with the home-button and the screenlock? Do the other buttons work and is the screen ok when you slide out the keyboard?
SmG67 said:
If it's unlocked and the network is still there you can do whatever you want with it There's no need to lock it ever again so you can experiment with kernels and roms all you want.
What was the matter with the home-button and the screenlock? Do the other buttons work and is the screen ok when you slide out the keyboard?
Click to expand...
Click to collapse
The other buttons are all fine, and the home looks fine too, just the only way to use it is to turn on the screen with it. Which hasn't got a lock on it, when I push any button, it switches right to the home screen. Turning on lock patterns and others didn't helped. Maybe can I use external applications to substitute the functions?
Rodage said:
The other buttons are all fine, and the home looks fine too, just the only way to use it is to turn on the screen with it. Which hasn't got a lock on it, when I push any button, it switches right to the home screen. Turning on lock patterns and others didn't helped. Maybe can I use external applications to substitute the functions?
Click to expand...
Click to collapse
Hmm, sounds a bit like the ROM doesn't want to go to sleep. Maybe you could reboot into recovery, and wipe data/factory reset, wipe cache and wipe dalvik-cache (from the advanced menu). I'm sure you already did that, but it can't hurt to do it again, and see if that fixes the problem
The phone should enter deep-sleep after about 5 seconds after the screen is turned off, in which case the only way to wake up the screen are the power-button and the home-button. pressing menu or back should keep the phone asleep. If after about 10 or 20 seconds you can still wake up the screen with the back or menu buttons you might want to check if there's an app keeping the phone awake.
Done factory reset and cache wipe already multiple times. Just realized how annoying is the dysfunctional home button, so I tried MiniCM7-2.2.0, MiniCM9-3.0.5 with nAa-11,13,14 and nAa-ics-04. Unfortunatley didn't worked the home button or the screen lock with none of them. At first time, I installed the MiniCM10, but the phone was relatively slow with it and buzzed, so I switched to MiniCM7.
Screen timeout and turnoff delay both set to immediately, but even the camera button can turn on the screen no matter how many time elapses. Can the original MiniCM apps keep it awake? I installed a task killer, but no change.
Rodage said:
Done factory reset and cache wipe already multiple times. Just realized how annoying is the dysfunctional home button, so I tried MiniCM7-2.2.0, MiniCM9-3.0.5 with nAa-11,13,14 and nAa-ics-04. Unfortunatley didn't worked the home button or the screen lock with none of them. At first time, I installed the MiniCM10, but the phone was relatively slow with it and buzzed, so I switched to MiniCM7.
Screen timeout and turnoff delay both set to immediately, but even the camera button can turn on the screen no matter how many time elapses. Can the original MiniCM apps keep it awake? I installed a task killer, but no change.
Click to expand...
Click to collapse
If it happens on all ROMS, maybe it's your home-button keeping the phone alive, as in that it makes continuous contact. Wouldn't know what to do about that though. Does it happen on stock firmware too?
SmG67 said:
If it happens on all ROMS, maybe it's your home-button keeping the phone alive, as in that it makes continuous contact. Wouldn't know what to do about that though. Does it happen on stock firmware too?
Click to expand...
Click to collapse
No, when I restored it with the Sony Update Service everything worked fine on the stock 2.1, and it is still possible to turn on the screen with the home button, but it's other functions are out.
Wow, this time I didn't installed the gapps like it was written in the CM wiki (http://wiki.cyanogenmod.org/w/Install_CM_for_mimmi), both the home button and screen lock works. Why it is written in the "Install CM for mimmi" article if the gapps on the download page is for MiniCM10?
Whatever, shame on me, I should've just take it seriously, and not follow the instructions blindly.:silly:
Thanks for all of your help.:good:
Rodage said:
Wow, this time I didn't installed the gapps like it was written in the CM wiki (http://wiki.cyanogenmod.org/w/Install_CM_for_mimmi), both the home button and screen lock works. Why it is written in the "Install CM for mimmi" article if the gapps on the download page is for MiniCM10?
Whatever, shame on me, I should've just take it seriously, and not follow the instructions blindly.:silly:
Thanks for all of your help.:good:
Click to expand...
Click to collapse
If you get the ROM from the thread in x10minipro development section of this forum, there is a link to the proper gb-gapps

phone will not turn

I used my phone this morning and it was fine. A few hours later I went to use it and it would not turn on. It is fully charged. I am running go launcher. I usually don't get asked which launcher I want to open it with when I wake my phone. But that screen flashed very quickly but I could not choose as the screen went blank very quickly. The screen was blank but the back button and the home button were lit up. I hit the power button so many times but nothing happens except the the 2 buttons lighting up. I went into recovery try to boot from there but nothing hapeens. It just goes to the HTC screen and hangs there. Its been on that screen for 10-15 and then I go back into recovery and still nothing. I tried to do a factory reset. It went to a screen with a picture of the phone and 2 green arrows going in a circle and a green down arrow inside the circle.
I have no idea what is going on. I have not done anything new to the phone. It is stock and I got Kit kat on it a few weeks back. Everything has been fine up until this morning. I understand the go launcher could cause a problem opening up the phone. But I don't understand why I cant do a factory reset from recovery. Any and all help is appreciated. Thanks
I also noticed that in the bootloader the very first line says 'LOCKED" is it supposed to say that?

M5 boot stuck half-way, rest of screen black, shuts off after a min

Hi all,
I got this Xperia M5 that's been giving out warnings about memory being full and I suppose it finally gave in. It only partially boots after like a full minute of showing you those blue waves. When it 'boots' the screen is black and nothing works, except you can see the status bar with just the battery icon, no-SIM icon and the clock.
Weird thing is when the device is powered off, you can press the power button once and it'll display a large battery indicator which shows the percentage normally-- I've seen this go up from 0 to over 90 something incrementally.
But when it's 'on' the way I just described, the battery is always at 0% with a red ! next to it.
Anyway, when it's in this weird half-life mode, you can actually pull down the notification bar normally, and tap stuff as well. Flashlight works, you can see an actual WiFi list (nothing happens when you connect) etc. When you launch stuff through here though, like settings, it won't open anything. It'll make the sound as if it's launched something but the remainder of the screen will still be black.
Using the dedicated camera button, I can access the camera. It works (sort of), meaning you can see the camera display where the screen used to be black. And it immediately says "system process is not responding," so I'm guessing this is a system issue where it can't load basic stuff like the homescreen?
Whatever you do or don't do, it stops responding after a couple minutes and shuts itself off.
Stuff I've already tried:
- Safe mode (volume down + power), just 'boots normally'
- Recovery mode (volume up + power) done that for over two minutes, does nothing or just 'boots normally'
- Hold down the tiny yellow 'off' button under the SIM/SD cover, did nothing.
- Xperia Companion: PC won't recognize the phone either in that zombie state, or when it's off, so I tried 'device cannot be detected', shut phone down, held down volume down button, connected USB still holding down, waited for a while and viola, nothing happened.
It's factory OS, never messed around with it and I don't know the version (could be 5?).
Any ideas?
Guys at this point all I'm wondering is if anyone ever managed to brick a phone that's as semi-responsive as this one, in the history of bricked android phones anywhere.. I mean how could it be bricked when you can (sort of) boot and even open the camera?
you said it boots in download mode?
paranoic(d) said:
you said it boots in download mode?
Click to expand...
Click to collapse
No I wouldn't say download, it's weird-- there's the status bar at the top and soft navigation keys at the bottom, but the homescreen in between these is black. I tried tapping this black area to see if stuff is there logically but you just can't see them, but there was no interaction, no sound or anything.
I am able to pull down the status bar to reveal the usual buttons and such, like I mentioned before you can turn on the flashlight, click to see a list of available wifis etc. But you can't access settings through here, I mean you tap settings and the main part of the screen is still black.
The only way to get the screen to work is to open the camera through its dedicated button, where the camera display works normally, you can switch cameras etc. Tried accessing the gallery through here but it didn't work.
I just don't wanna buy a new phone when this one doesn't seem bricked at all. If it like didn't respond at all and nothing appeared on the screen I wouldn't think twice before buying the first phone I see on Google.
im afraid that you have to flash stock rom again if you will boot into download/fastboot mode.but your problem seems strange.what was the last thing you have done before phone stuck like this?
paranoic(d) said:
im afraid that you have to flash stock rom again if you will boot into download/fastboot mode.but your problem seems strange.what was the last thing you have done before phone stuck like this?
Click to expand...
Click to collapse
Not my phone but it'd been going on about low memory for a while now. I got the PC to recognize it once in that zombie state, so I'll try that with Companion if I can get it to half-boot again. I'll post updates if anything happens.
antiglue said:
Not my phone but it'd been going on about low memory for a while now. I got the PC to recognize it once in that zombie state, so I'll try that with Companion if I can get it to half-boot again. I'll post updates if anything happens.
Click to expand...
Click to collapse
okay keep us updated

Categories

Resources