So I have looked on Google for a solution but I don't exactly know what my problem is called, which makes finding an answer difficult.
We have several note 2's at the place where I work. One of our employees recently (last week or so?) updated to Android 4.3 Stock (he has always been stock). Now he is getting a very strange popup on his screen, the screen will not lock and almost every time you hit the power button, it shuts the phone off. I have attached a photo of the popup
Any suggestions? This is a new one on me!
Thanks in advance!!
Found this http://forum.xda-developers.com/showthread.php?t=2392632 scroll down some to you see Exit_Permanent Safe Mode
Hope it helps..
Thank you!
wolfeyes30 said:
Found this http://forum.xda-developers.com/showthread.php?t=2392632 scroll down some to you see Exit_Permanent Safe Mode
Hope it helps..
Click to expand...
Click to collapse
Thank you sir that does!!! I appreciate your help!
Did it work?
Warranty
I did not actually try it. Know that I know what the problem is (and because his phone is not already rooted) we decided that the best course of action is to just get a warranty replacement for it.
I have never seen this issue before and after reading through that link you gave me, I am assuming the verizon update corrupted the phone.
But I am thankful for your help! I would have spent a lot more time trying to figure out what was going on with the phone without your help!
Haha... I just assumed it was rooted. Glad I could help ya a bit. Be well.
Related
I updated the firmware this morning and it looked like it had worked but then there was an explanation point in the notification bar saying there was an update available. I clicked the icon and everything froze. I tried to power off but it froze at the confirmation screen. I held the power button down with the volume down button to reset and it just took me to a page with gears and an orange explanation point. i did the data wipe with the same result. I did the reset button with a paperclip and same result. I downloaded the update onto a micro SD card and did the data wipe and was told by ASUS it would install the update from the SD but still nothing. I cant figure anything out, if anyone has suggestions or any similar problems let me know.
This is the thread you are looking for -> http://forum.xda-developers.com/showthread.php?t=1423503
Hope you fix it...
mine got bricked too. called Asus and they walked me through the factory reset process to no avail. they want me to send mine back to be fixed
I just RMA'd mine. I hope they dont release a do it from home fix because i have to wait about 3 weeks most likely til i get it back. what a bunch of b*ttholes.
joe14 said:
This is the thread you are looking for -> http://forum.xda-developers.com/showthread.php?t=1423503
Hope you fix it...
Click to expand...
Click to collapse
cassato said:
I just RMA'd mine. I hope they dont release a do it from home fix because i have to wait about 3 weeks most likely til i get it back. what a bunch of b*ttholes.
Click to expand...
Click to collapse
Had you read this guys link....you would see there is an easy fix for this.....I guess reading is too difficult........
I will put this in here just to help you out, though I doubt you will read it....
Drain the battery completely...re-charge.....and wham!!! all fixed....and I don't even have mine yet and I knew this......
slayer69 said:
I guess reading is too difficult
Click to expand...
Click to collapse
sorry to hear you are having problems, try hooked on phonics or something. it might also help you eliminate some unnecessary periods which seem to plague your posts.
perpetual reboot loop
slayer69 said:
Had you read this guys link....you would see there is an easy fix for this.....I guess reading is too difficult........
I will put this in here just to help you out, though I doubt you will read it....
Drain the battery completely...re-charge.....and wham!!! all fixed....and I don't even have mine yet and I knew this......
Click to expand...
Click to collapse
the OTA updates launched me into a perpetual reboot loop. i tried letting the battery drain all the way down but it didn't stop it once I powered back up the next day.
ASUS phone tech's want me to send it in for service, but before I send it I am hoping that someone has another solution I can try.
Hi People of the world! As you can see im new to here so yeah i just might be in the wrong section...
So, I just got my shiny android a week ago, and know it sits on my desk, lifeless, like a brick. Like literally its dead! I don't know if I can fix it or the BIOS (if theres one in Samsung Galaxies) is fried, or maybe the motherboard is fried, or the battery overcharged, etc. But I just cant do anything! I'm totally out of ideas!
Heres the problem, I first rooted my android successfully, and played around with my android a while. But as you expect I just coudn't wait for the jelly bean update! So, I desided I would give a try to take the Russian firmware instead. That was already a bad idea, but I read on some threads that it would work fine, so I downloaded one from Sammobile.com. The real mistake? I downloaded the wrong phone. I own a Samsung Galaxy S Advance NFC Version;GT-I9070P The one I downloaded was UnNFC version; GT-I9070. Well, I didn't realize that, and proceeded with entering download mode and eventually flashing the PDA file from Sammobile with ODIN. So I pressed start. It started the process, and after 5 min it said in blue: RESET. I saw the phone rebooting. Now, another big mistake: I started touching the power button, which I shouldn't have done. Then, instead of waiting, as soon as seeing the thing wasnt booting, I took out the battery and unplugged the USB cable. Then after a while the PASS appeared in green. So it went successfully? NONONO Now it wont boot! More specifically, it wont TURN ON! like it wont whow any sign of life. As if it had no battery or USB.
Today I discovered, If I hold Vol UP+Power+Home when its connected to my PC, it makes the beep, shows that it failed to install the driver for "U8500 USB ROM" What the (*^&(&%*(&^&* is that??? Also, in 5 seconds, the device disappears, meaning that I must hold the button combo for another 20 seconds.
So, I've got no connectivity to ODIN, nor Kies, and I cant go into download mode, nor recovery mode.
Any Help?
Pleeaase if you can help youre a super god of androids!
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
MikeSome1 said:
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
Click to expand...
Click to collapse
Exactly. Nothing at all.
The only evidence that its not fried is that the computer detects it as U8500 USB ROM for 5 seconds whenever i hold the power button or any combination. Nothing on the phone though.
Hey
Hey man got the same problem... I have put mine to a service center i will see what the'll do
pafiking said:
Hey man got the same problem... I have put mine to a service center i will see what the'll do
Click to expand...
Click to collapse
Yeah i think I should take it to service too, but I want to try at least first:cyclops:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Lynnfield4000 said:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Click to expand...
Click to collapse
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
Please help! I also bricked my Samsung S Advance I9070P after downgrading from JB to GB, since JB was updated for India I9070...but the phone bricked after downgrade. Everything was successful and it had auto-rebooted after the downgrade and stuck with Start up screen. When I removed battery and tried again..it bricked! No recovery mode, No download mode, no power on.
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
So you find any solution? I have a similar problem right now.
Hey lads, so ive been here on this forum for a long time and got a LOT of resources for my note and other phones so thank you ALL for that over the years. Now onto my problem. I started having the reboot problem where it will automatically reboot after a few seconds of booting up. I know there are threads concerning this and the usual suspect is the power button, concerning which I have messed with it, cleaned it, kissed it, caressed it, (ok seriously now) i shaved it down a bit so it wont be making unnecessary contact. I even removed the button completely. The first time i did it it seemed to work for a couple days but then it started again. I saw threads indicating it could be a battery issue as well so i ordered a new oem battery and unfortunately that didnt work either. Im just about ready to toss it (no warranty) but i thought i'd put this out there in case any 'higher level' users here may have any final insight to give me before i do that. I always appreciate advice and help of any sort so I'll go ahead and thank you all in advance
Thanks! :laugh:
looking forward to hearing from u lads.
Edit: oh and it doesn't happen in recovery or download mode. It just stays on no problem. I have flashed new and original roms, kernels, recoveries using odin etc. all to no avail
Hi all, thanks in advance for any assistance you can provide me. I have looked for similar posts but could not find any (maybe I just don't know what my issue is called). I bought an HTC EVO 4g LTE from a friend that had put meanbean on it (I assume it was the latest). I went through all sorts of steps loading twrp and getting s-off and whatever else I needed to do to load cyanogenmod 10.2. I was able to do this fine but the gapps I loaded would not show. I tried it together and separately and nothing would work. So I loaded (I believe) 3.16.651.3_stock_rooted_odex_CPTB.zip so that I could use my phone again with the gapps while I was waiting for some assistance on the cyanogenmod forums, which never came unfortunately. Everything was fine for about the past 10 days.
Today I used my phone all day and had no problems (extra info: I installed one app to access my bank info which went fine), but hours later and all of a sudden my screen basically got stuck. It looks like millions of randomly chosen colors for each pixel. The screen will turn on and off if I hit the top button (or let the display "timeout"), and I can hear the tones when I press the up and down volume buttons. This is telling me it's not bricked, but it is completely useless to me as is. When I reboot the phone, I don't see anything on the screen until the colors come up (which is after the vibration during the bootup sprint screen as far as I know). I was able to get fastboot to see it once but haven't been able to get back into the bootloader (there's nothing on the screen so I don't know what I'm doing).
Basically, nothing on my screen while it is booting up until it gets to the point where my laptop detects the USB connection, and the crazy colors comes on. BTW, as random as it seems, it's the same colors in the same exact position each time and it never changes. I haven't tried flashing any roms with fastboot because it seems my issues is bigger than a rom... I can't even see anything when I had it in the bootloader... This is my only phone and I use it every day. I'm really quite desperate and could use any and all help you're willing to provide. I've attached a zip with a picture of my screen so you all can see what I'm talking about. Thanks in advance...
just an update, got my laptop to see my device with fastboot so I'm gonna leave it hooked up. Could really use some advice on how to proceed because I'm at a loss. Thanks...
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
So can you say with any certainty that my issue is not due to the programming on the phone?
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
I just thought I would see a similar screen in the bootloader if it were a physical hardware issue.
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Magnum_Enforcer said:
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Click to expand...
Click to collapse
Okay great thanks for the reply... the touchscreen portion of the phone still works (I was able to answer a phone call today even though I couldn't see where I was touching). I saw some videos online so I'll watch carefully and order a new screen/digitizer or whatever. Thanks again
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk