So it seems that UBSM actually requires stock launcher which I have either frozen or deleted as I use nova and had no need for it. This ended up causing my phone to be stuck at the ATT logo in black and white, is there any possible way of getting out of UBSM? I have seen a few fixes but I was thinking if maybe charging the battery to full would take it out of UBSM.
Veight said:
So it seems that UBSM actually requires stock launcher which I have either frozen or deleted as I use nova and had no need for it. This ended up causing my phone to be stuck at the ATT logo in black and white, is there any possible way of getting out of UBSM? I have seen a few fixes but I was thinking if maybe charging the battery to full would take it out of UBSM.
Click to expand...
Click to collapse
No, charging full wont turn it off, would kind of defeat the purpose lol, not like you couldnt have tried this any way though, its not a huge hassle to charge. The fixes are posted, you know where they are as youve said, do that and you should be sqaured away.
Sent from my SM-G900A using Tapatalk
Thanks. Yeah, I got it taken care of, didn't have a TB backup so I had to manually re-install everything which I was hoping to avoid. This time, I did set it up right and can use UBSM without any issues.
Related
Hey Everyone,
Just seeing if anyone might have a solution to my problem that I'm facing. I had rooted my phone when the root originally came out, and everything seemed to be working fine. I had been texting on my phone when it suddenly froze, I waited to see if it would come back, but it never did so I pulled the battery.
The phone originally booted to the M logo, but froze, after another battery pull the phone now won't turn on at all. As in it's not responding to the power button press at all. It's not being recognized by a computer, and there doesn't seem like much I can do.
Any suggestions out there? If my phone is bricked and can't even turn on, will a Verizon store know this? How could they?
thanks.
If u froze something like a system app that may have bricked it. Theres something u can flash which was a cracked version of an ota update that should fix it but u may not be able to receive official updates if u do that. Other option is to wait for an official sbf file
Sent from my DROID3 using XDA App
How can I flash something? There doesn't appear to be a way for me to access my phone. I can't get into restore or the bootloader.
What happens when you plug the phone into your charger(using the stock charger and cable)?
Nothing, no light, no anything
I actually haven't tried it in a situation like that so I can't give instructions :/
Sent from my DROID3 using XDA
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
g3m1n1 said:
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
Click to expand...
Click to collapse
I think that might be what I do, I can't imagine they would have a way of knowing it's rooted if the phone won't even turn on, charge, or anything.
Thank you, btw.
Try taking out the battery and plugging it in to the wall without it in it. If it starts to boot, let it. Then replace the batter and plug it into the wall again and let it charge up. Happened to my Droid X before and I was able to get it working by doing this.
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Niviac said:
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Click to expand...
Click to collapse
Honestly the Magnuson-Moss act protects you in that VZW has to prove that rooting caused the phone to fail. However in practice you end up having to take them to court which is too costly and time consuming. But to answer your question yes they could pretty easily figure it out.
But to put it differently no one else that I've read about has had a failure like yours. People have bootlooped and such, but no one has just had nothing happen on power-up. It doesn't sound like you did anything other than root, which couldn't possible cause this. Freezing apps and deleting system apps only causes force closes and bootlooping, you had neither.
Very screwy behavior on my Captivate. Hoping someone out there can help me diagnose this..
Captivate is running stock KK4; rooted via kernel swap method; some AT&T bloatware frozen in TiBu - no other image changes
The Captivate is struck on the swipe to unlock screen. I sync this phone to my company's Exchange server and have a PIN-lock policy enforced. I believe that it goes to the PIN at 15 minutes. The clock and swipe screen are showing a time less than 15 minutes after the last time I had used the phone; the screen was dark until I pressed power once, but now I can not make the screen go back to sleep. Plugging the phone into the computer does show the phone connected, and the Live Wallpaper is still running (i.e., it is not frozen in place, which I also see some times).
EDIT: After rebooting (vol-up and power does respond); it looks like something may have been up the same time as I was frozen with my phone signal - yellow instead of green; don't know if that was a coincidence or not
Any one have any ideas as to what may be going on here, and how I would remedy this?
Probably asking the obvious, but can you get into recovery or D/L mode to possibly reflash the rom?
jeeper11 said:
Probably asking the obvious, but can you get into recovery or D/L mode to possibly reflash the rom?
Click to expand...
Click to collapse
I can, and I can reboot, and have the phone work again for the next 24-36 hours before it freezes again.
I am hoping that someone has an idea of the root cause of this issue, bad flash or otherwise, to try to solve this once and for all. To be honest, I have had horrible experiences with GB on the Captivate, but since this is my work phone, paid for, and technically owned by my employer, I have been hesitant to stray too far from stock (heck, if AT&T's tethering manager could figure out that a corporate phone plan with tethering should be allowed to tether, I would have stayed fully stock).
I'm betting that it's bad behaved software, rather than a bad flash due to the unpredictable nature of this problem, but I am not sure of a way to capture logs in a consistent basis that would allow me to trap what actually goes wrong to solve this. GB seems to get progressively less stable the more apps are installed, but I don't know if that is the root cause, or just the increasing likelihood of installing something with an insidious bug. But short of stripping everything off and losing the advantage of having a phone with apps, I don't know how to solve this and the soft reboot issue that also came with the first GB leaks and never went away.
Sigh.
There could be just one rogue app causing it
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
h2whoa said:
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
ArtfulDodger said:
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
Click to expand...
Click to collapse
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
Hate to hear that and you're not the only one to mention swollen batteries around here lately either. Good luck to you!
theAPANT said:
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
h2whoa said:
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
Click to expand...
Click to collapse
Yes the easiest way to get rid of cwm is to flash the stock file. Go to http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G there are, i believe two methods, one using Odin the other flashing something in recovery. Just read. As for cm10.1 camcory is working on it so is smartguy. Even i compiled it but it doesn't boot all the way. Check insomniaforums.org that is probably where it will be posted
Sent from my Nexus 7 using xda app-developers app
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
afwolfpacked said:
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Bluetooth and camera dont work. I'm saying my own personal build doesn't boot yet but I'm trying some stuff. Right now I'm working on aokp 4.1.2 to get that fixed all the way, mainly because i like aokp and I'm stuck on 4.2.2
Sent from my Nexus 7 using xda app-developers app
I was just scrolling though instagram and all of a sudden the whole phone image started scrolling up and kept going now it is turning on and off and the picture is like a tv that is has no signal and is stuck in a bootloop. I've tried everything from battery pulls to blowing in it, a new charger, if you can think it ive tried it. It is 100% stock and I want to try a factory reset but I cant even get it to boot. If anybody could help me id really appreciate it! http://www.youtube.com/watch?v=w7-fStaJkYQ
JaceHagg said:
I was just scrolling though instagram and all of a sudden the whole phone image started scrolling up and kept going now it is turning on and off and the picture is like a tv that is has no signal and is stuck in a bootloop. I've tried everything from battery pulls to blowing in it, a new charger, if you can think it ive tried it. It is 100% stock and I want to try a factory reset but I cant even get it to boot. If anybody could help me id really appreciate it! http://www.youtube.com/watch?v=w7-fStaJkYQ
Click to expand...
Click to collapse
This seems a hardware problem
Yeah, I contacted at&t and samsung and they think it is also. They are sending me a note 4 replacement for free so im not complaining anymore!
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
jason504 said:
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
Click to expand...
Click to collapse
I am sure you tried factory reset already? I had a few in phones in the past do that. Usually was a bad battery. When did it all start? How old is phone? Any apps you install and it started doing this?
Leaning more towards you will need to ship in for a warranty with Samsung.
Nick216ohio said:
I am sure you tried factory reset already? I had a few in phones in the past do that. Usually was a bad battery. When did it all start? How old is phone? Any apps you install and it started doing this?
Leaning more towards you will need to ship in for a warranty with Samsung.
Click to expand...
Click to collapse
This is my 2nd phone the first one got screwed up with a update. I have had this one for about 4 months and it just started doing it about a month ago. Now it has done it 3 times this week. Once just now and it happens on the charger and off the charger. It has made me late waking up twice. I haven't done a phone restore yet and I haven't installed any new apps.
Sent from my SM-N950U using Tapatalk
jason504 said:
This is my 2nd phone the first one got screwed up with a update. I have had this one for about 4 months and it just started doing it about a month ago. Now it has done it 3 times this week. Once just now and it happens on the charger and off the charger. It has made me late waking up twice. I haven't done a phone restore yet and I haven't installed any new apps.
Click to expand...
Click to collapse
Sorry didn't read right tired ha. Black screen usually sign of bad screen. Got mixed up and thought it was restarting on it's on. If there was no apps that caused it. You didn't mess with any settings? Said your stock.
If none of the solutions others suggest soon don`t work. I'd go for a factory reset last resort. Worst case you will have to ship again to Samsung sadly
Nick216ohio said:
Sorry didn't read right tired ha. Black screen usually sign of bad screen. Got mixed up and thought it was restarting on it's on. If there was no apps that caused it. You didn't mess with any settings? Said your stock.
If none of the solutions others suggest soon don`t work. I'd go for a factory reset last resort. Worst case you will have to ship again to Samsung sadly
Click to expand...
Click to collapse
I see a lot of people having this problem. Not on here but online and it's not just the Note 8 it's the S8 too.
Sent from my SM-N950U using Tapatalk
jason504 said:
I see a lot of people having this problem. Not on here but online and it's not just the Note 8 it's the S8 too.
Click to expand...
Click to collapse
That's concerning. I take it most people with same situation as yours, shipped into sammy? Sucks you gotta go through this bs again maybe.
Just as suggestion, but if you use AOD try turning it off and and see if this fixes the problem.
I had this problem with Ironman ROM and turning off AOD fixed the problem.
How to Fix A Samsung Tablet with Black Screen
jason504 said:
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
Click to expand...
Click to collapse
Hi,
If you can't reboot your device to fix black screen problem, you can try FoneLab broken android phone data extraction to fix it.
Download and install the program on your computer, and then connect device to computer.
Then you can scan, select and recover data with a few clicks.
More details from fonelab and the post How to Recover Data from Android Phone That Won't Turn On or How to Fix A Samsung Tablet with Black Screen.