since i bought this nexus 7 i noticed that the screen blacks out and it doesnt back to normal till after a few hours. but a couple weeks ago it this again and since then all i have is a black screen. i read online that this is a small issue that nexus 7 has. so i thought it was a goner till i got off the phone with Asus and i was told if i had Flash downloaded on device that could've messed it up and i should get into bootloader to do a factory reset, but i told them that this was impossible cuase nothing happens when i try getting into bootloader. okay after i tried multiples and actually got into the bootloader menu. but i'm stuck here, i can get into recovory. or anything...i mean if this was a serious issue i wouldnt have been able to get into bootloader menu
Droid_Boi86 said:
since i bought this nexus 7 i noticed that the screen blacks out and it doesnt back to normal till after a few hours. but a couple weeks ago it this again and since then all i have is a black screen. i read online that this is a small issue that nexus 7 has. so i thought it was a goner till i got off the phone with Asus and i was told if i had Flash downloaded on device that could've messed it up and i should get into bootloader to do a factory reset, but i told them that this was impossible cuase nothing happens when i try getting into bootloader. okay after i tried multiples and actually got into the bootloader menu. but i'm stuck here, i can get into recovory. or anything...i mean if this was a serious issue i wouldnt have been able to get into bootloader menu
Click to expand...
Click to collapse
If you bought it from Google then you can still RMA it
Droid_Boi86 said:
since i bought this nexus 7 i noticed that the screen blacks out and it doesnt back to normal till after a few hours. but a couple weeks ago it this again and since then all i have is a black screen. i read online that this is a small issue that nexus 7 has. so i thought it was a goner till i got off the phone with Asus and i was told if i had Flash downloaded on device that could've messed it up and i should get into bootloader to do a factory reset, but i told them that this was impossible cuase nothing happens when i try getting into bootloader. okay after i tried multiples and actually got into the bootloader menu. but i'm stuck here, i can get into recovory. or anything...i mean if this was a serious issue i wouldnt have been able to get into bootloader menu
Click to expand...
Click to collapse
When you get into Bootloader what happens?
Why can't you get into recovery?
Open back cover and check the battery connection, it might be loose.
You can fastboot the stock image over.
You can even "fastboot oem unlock" and then "fastboot oem lock" to factory reset it.
Sent from my Galaxy Nexus using XDA Premium HD app
Connect the tablet to your computer and press the power button + volume down and up..
Beamed from my Maguro.
Related
Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.
i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.
prelude91sit said:
i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.
Click to expand...
Click to collapse
Dear Brother !!
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Brother!!
Please let us know how it goes. I think there are many brothers on here in the same predicament.
On 2 separate occasions today I found myself looking down at my Nexus 6 to find it powering up.
Is anyone else noticing random resets? I have rooted, unlocked bootloader and removed encryption on mine.
I get this a ton of times. I'll take care the phone out of my pocket and screen is black. I'll hit the power button and the device is dead. Then I'll hold the power button until it restarts. This happens at least 2-3 times a day its very annoying
Sent from my Nexus 6
Imprezive13 said:
I get this a ton of times. I'll take care the phone out of my pocket and screen is black. I'll hit the power button and the device is dead. Then I'll hold the power button until it restarts. This happens at least 2-3 times a day its very annoying
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do anything to yours yet? (root, unlock bootloader or remove encryption)
same issue. Multiple times in last 7 days.
this time it happened when I was on call and call got disconnected and screen was blank. very annoying.
called GPS cutomer care, they want me to keep my phone in safe mode for a day.
I am completely stock and locked boot loader.
Sent from my Nexus 6
Did you get your phone from AT&T? If so they had a recall which had a problem where it causes reboots and shipped with wrong software.
I got it from Play store.
Mine was shipped from T-Mobile to my door
Sent from my Nexus 6
Same here, but much less common than you described. It's probably happened to me twice since I've owned it (I got mine on the 17th from Motorola).
Sent from my Nexus 6 using Tapatalk
Hmm try attaching a last_kmsg after a reboot to determine what causes the reboot or steps on how to reproduce it. I have not had a random reboot and mines was from t mobile.
Sent from my Nexus 6 using Tapatalk
zephiK said:
Hmm try attaching a last_kmsg after a reboot to determine what causes the reboot or steps on how to reproduce it. I have not had a random reboot and mines was from t mobile.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
oddly, on the n6, i cant get a last_kmsg, not through a terminal nor through looking manually, its just not there.
zephiK said:
Did you get your phone from AT&T? If so they had a recall which had a problem where it causes reboots and shipped with wrong software.
Click to expand...
Click to collapse
Mines from moto
I'm leaning towards this not being a software issue but a hardware issue. I've went ahead and opened a case with Motorola and they are sending me out a replacement phone. Hopefully this will fix this issue going forward.
It happens to me about once a day. I cannot pinpoint the cause.
It's happened to me twice in 8 days.
has happened to me every day since i bought it (wed 26th) bought from bell store in Canada (blue 32gb)
It's happening to me too. Got mine from AT&T. Mine randomly cuts off. Not rooted or anything.
Sent from my Nexus 6
I said before on other threads before, out of 3 nexus I bought from GPS one of them rebooted twice the first day, and the second day was unusable, rebooted every 5 mins. For me it was a hardware problem, i flashed factory image, factory reset, everything and nothing, called google, they send me the replacement, and never seen a random reboot on it.
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
rina__anir said:
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
Click to expand...
Click to collapse
If your warranty is still valid take it to service
donkeykong1 said:
If your warranty is still valid take it to service
Click to expand...
Click to collapse
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
rina__anir said:
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
Click to expand...
Click to collapse
Did you try factory reset from bootloader?
donkeykong1 said:
Did you try factory reset from bootloader?
Click to expand...
Click to collapse
Yes, I did. It flashed to the screen with 2 green arrows in a circle and 1 downward green arrow with a progress bar at the bottom but nothing happens during this period. I left the phone like that for about 30 mins just to see if anything would happen and nothing did.
8 days ago, I decided my s5 had had enough abuse, and got the z force. It's been an amazing phone, other than the heat, which has always seemed a little warm, but didn't do anything to slow the phone down. Up until today, it's been glitch free, and I loved it.
Until about six hours ago. I wasn't paying attention to the battery, it died in the middle of watching YouTube videos with my kids, so I let it finish powering down, plugged it in, and let it charge. Upon turning the phone back on, I got an error message saying the device failed validation and may not work properly. Five second delay and it powered on, and everything seemed to function normally. Rebooted the device, same screen. Factory reset the device, same screen. I took the phone back to Best Buy and got a replacement, and I'm hoping it doesn't happen again, I really happen to like this phone...but I'm curious. Moto's customer support's first question was if I'd unlocked the bootloader or rooted the device, but being verizon-locked, I'm well aware that isn't possible and haven't attempted it. Anyone have any ideas why my phone just randomly decided to fail the bootloader verification so I can try to avoid replicating this mess?
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Mace68 said:
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Click to expand...
Click to collapse
If you boot into the bootloader does it say if your device is locked or unlocked?
BladeRunner said:
If you boot into the bootloader does it say if your device is locked or unlocked?
Click to expand...
Click to collapse
No such luck lol. It says "oem_locked" and software status is "Official".
Sent from my XT1650 using XDA-Developers mobile app
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Mace68 said:
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Click to expand...
Click to collapse
Factory reset didn't fix mine, either. And as far as turning on the bootloader unlock option...I hadn't even enabled dev options on mine, so I'd assume that's just a coincidence on yours.