MY power button no longer works. My phone is still unlocked but since the official OTA came out I flashed back to unrooted stock and got the OTA and left the phone alone for a while.
Now I can't flash anything in fastboot it just says waiting for device. I can't even navigate through the fastboot menus on the phone with the volume rocker. Think it has something to do with the power button.
How do I get around this?
Please move to q & a ....
Sent from my Nexus S 4G using Tapatalk 2
Take it to a repair center and have them fix it. I had the same problem. It will come and go. Mine stopped working, started back working and finally, quit again. If u have insurance the process should be fairly simple
Okay, so here it goes:
- Been trouble with "sudden loss of mobile network issue" for a month or so (ref: http://productforums.google.com/forum/#!category-topic/mobile/android-devices/NCwPW3A_ibM http://code.google.com/p/android/issues/detail?id=14672 )
- So I flashed to 4.0.4 stock image from the google website, a. Everything worked so well, and I got my signal back. I followed these guides (http://floatingsun.net/articles/howto-flash-gsm-galaxy-nexus-to-google-factory-image-on-mac/ http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html) and they worked for me well (again).
- I wanted to lock and reunlock my bootloader again from fastboot. Locking process goes well. But when I tried to unlock my bootloader, after that yes/no screen my computer went dead. And my phone freezes on the bootloader. I pulled out the battery, and then put it in.
Magically, my phone booted by itself (without me touching the lock button). And the OS loads up seamlessly. Everything inside works well, except the power button. It's unable to put the device to sleep or even bringing the power menu. I rebooted several times via ADB, still no change.
- Maybe it's hardware problem, so I turned off my phone via ADB, and it's always turn on again right after. Then I tried to pull out the battery, and nope.... still turning back on. At one chance I pulled the battery, and immediately pressed the Power button and Vol Up, so it'll boot to bootloader. The bootloader boots that way.
- Yes, bootloader boots, but fastboot wouldn't recognize my phone. Plus I can't use the vol button and power button in the menu. It just freeze. typed "./fastboot devices" didn't give me any feedback. rebooting the bootloader via fastboot always prompt the < wait for device > endlessly.
- Upgraded to JB 4.1.1 OTA via software updater, no change on these 3 issue.
SUMMARY:
1) Power button not working, both in bootloader or in OS. But putting phone to bootloader by using power + vol button works, so I guess it's not hardware..
2) Bootloader freeze, fastboot works fishy. Cannot do anything here. (see above)
3) Everytime I turn off, it always turn back on.
I appreciate to those who read all above carefully. Thanks. I hope I can find answer.
SOLUTION(S) to try:
1) try sdk in windows at home. I'm using mac at the office. (I guess it's just the same) NOT WORKING
2) Try this tool at home (http://forum.xda-developers.com/showthread.php?t=1672708) NOT WORKING
3) last and least; go to samsung repair service
DEVICE INFO:
i9023
IMEI ok
BASEBAND: i9023XXKF1
BL Version: i9020XXLC2
kernel: stock
Build Numb: JRO03E
Tried solution #1 and #2, still same response. On command prompt still displayed < waiting for device > endlessly :/
Any advice?
Broken power button. It's a hardware issue, not software. It's a known issue that when the power button breaks on the Nexus S it stays as "pressed" and you cannot scroll in bootloader and you cannot use fastboot.
What do you want to achieve anyway? Unlock your bootloader? Might I ask why you locked it in the first place?
polobunny said:
Broken power button. It's a hardware issue, not software. It's a known issue that when the power button breaks on the Nexus S it stays as "pressed" and you cannot scroll in bootloader and you cannot use fastboot.
What do you want to achieve anyway? Unlock your bootloader? Might I ask why you locked it in the first place?
Click to expand...
Click to collapse
I see... just found the culprit a few hours ago.
I wanted to restore it to factory default, following this guide.
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2. The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
strabo231 said:
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2.
Click to expand...
Click to collapse
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
Click to expand...
Click to collapse
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
Click to expand...
Click to collapse
sd_shadow said:
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
Click to expand...
Click to collapse
Ah Shadow! I was hoping you'd see this. Let me clarify a little bit.
1. I am able to get phone to boot into OS. I did try to install the update.zip already but I'm still having the same problem with the boot loader.
2. I know about the easy sbf, and tried that with this particular phone, but because of the problem with the boot loader when easy sbf or RSD Lite switch the phone, or attempt to switch into flash mode, the computer no longer recognizes the phone.
3. I did think about rooting the phone to try to open up a few other options to at least get around the problem. Since it's on .629 already though I'm limited to rooting using easy sbf as far as I've understood, but again since I'm having the issue with the boot loader that hasn't been an option I have been able to successfully use.
4. The power button on the phone isn't working, so I'm unable to use the key combo to access the boot loader; however, I have a factory cable...now I say factory cable not meaning the stock charging cable...but the 5-wire factory cable. Typically with Motorola phones using this cable you simply remove the battery, and then with no battery in the phone hold down both volume buttons and plug the factory cable in and it automatically reverts to the boot loader.
I know that there is a consumer replacement boot loader for the droid 1 to fix issues like this, but I haven't seen one for the two. The other issue is that the replacement is an sbf file which ill be unable to use, and didn't know if that was something that would exist as an update.zip that could be flashed through the stock recovery
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
sd_shadow said:
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
Click to expand...
Click to collapse
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
sd_shadow said:
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yeah I tried that last night. I saw where you were having problems with it too. I had seen where a few months back there was someone else that was having this issue that you were trying to help walk them through, but the thread kinda died off, so I wasn't sure if there was ever a resolution to it. Ok well thanks for your time. I'll be sure to post an update for people coming behind me if I manage to get anywhere with it.
strabo231 said:
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
Click to expand...
Click to collapse
if you are still working on this a Bootloader Only
HS_S_signed_AP_BL_D11_cdma_droid2we_Consumer_replacer.zip
has been posted here http://sbf.droid-developers.org/cdma_droid2/list.php
If you're still looking to root, try Framaroot from here. It worked for me on .629. No idea about the bootloader however . Good luck though!
HI there.
I'm really looking forward that someone may be able to unbrick my phone or at least navigate me how to turn back bootloader, using command-line, as this would solve the whole problem.(unauthorized device + Bootloop + hardpressed volume UP button, occuring problems on the other one as well) :crying::crying:
Device, OS, Settings status: HTC VILLE (S4), Fully rooted, CM11s stable, S-OFF, SU, CID 1111111 , TWRP 2.8.1.0 hboot 2.16, ADB: xxxxxxxxxxx unauthorized device :highfive:
Actual status: After i recovered clean copy of my CM11 from TWRP (was trying some custom roms, which i didn't fully met my expectations), i decided for the first time to use Titanium Backup Pro and restore all user and system apps, settings and data which i perfomred earlier, what found out not to be the smartest move. Either way, after approx 24h my phone went down, restarted itself, unfortunatelly only as far as Bootloop
Everything would be just fine if i could just get back into bootloader. Additional problem i mentioned before is my volume button. It works but not 100%, after my phone felt down on it and vol up is hard pressed and sometimes it jams. This leads us to another (minor? :crying problem that appeared during normal use of device. Namely due to this hardpressed VOL UP button sometimes i couldn't even turn off the screen with power button (which is perefecly working if )
Concluding i`ve stuck on Bootloop. Whenever trying to turn on the bootloader with multiple combinations of pressing vol + power button, phone just restarts again. (i did that many times before without any problems) . However i'm able to turn it off sometimes
My main problem for now is with unauthorized device under ADB so i can`t neither start recovery nor bootloader using command-prompt line.
Is there any chance to bypass this unauthorized status in ADB? or should i look after new handset ? Hope that someone will be able to help . I'm willing to give away my endless gratitude full support and even reasonable amount of gold stash
XDA masters, HTC ONE S lovers and supproters, Anyone capable PLEASE HELP
Jesz Jeżyk said:
HI there.
I'm really looking forward that someone may be able to unbrick my phone or at least navigate me how to turn back bootloader, using command-line, as this would solve the whole problem.(unauthorized device + Bootloop + hardpressed volume UP button, occuring problems on the other one as well) :crying::crying:
Device, OS, Settings status: HTC VILLE (S4), Fully rooted, CM11s stable, S-OFF, SU, CID 1111111 , TWRP 2.8.1.0 hboot 2.16, ADB: xxxxxxxxxxx unauthorized device :highfive:
Actual status: After i recovered clean copy of my CM11 from TWRP (was trying some custom roms, which i didn't fully met my expectations), i decided for the first time to use Titanium Backup Pro and restore all user and system apps, settings and data which i perfomred earlier, what found out not to be the smartest move. Either way, after approx 24h my phone went down, restarted itself, unfortunatelly only as far as Bootloop
Everything would be just fine if i could just get back into bootloader. Additional problem i mentioned before is my volume button. It works but not 100%, after my phone felt down on it and vol up is hard pressed and sometimes it jams. This leads us to another (minor? :crying problem that appeared during normal use of device. Namely due to this hardpressed VOL UP button sometimes i couldn't even turn off the screen with power button (which is perefecly working if )
Concluding i`ve stuck on Bootloop. Whenever trying to turn on the bootloader with multiple combinations of pressing vol + power button, phone just restarts again. (i did that many times before without any problems) . However i'm able to turn it off sometimes
My main problem for now is with unauthorized device under ADB so i can`t neither start recovery nor bootloader using command-prompt line.
Is there any chance to bypass this unauthorized status in ADB? or should i look after new handset ? Hope that someone will be able to help . I'm willing to give away my endless gratitude full support and even reasonable amount of gold stash
XDA masters, HTC ONE S lovers and supproters, Anyone capable PLEASE HELP
Click to expand...
Click to collapse
It turned out everything was fine, I was unable to start bootloader because of hardware malfunction, and being more specific, hard-pressed Vol Up Button was sending signals and because of that The combination of Vol Down Button + Power brought no results. Once I lifted gently Vol Up Button with thin sharp tool, i was able to start bootloader Hope, this information will save some stress in the future. I wasn't fully aware of, thinking that if Vol Down Button was perfectly fine bit hardpressed Vol UP button shouldn't occur malfunctioning of the other button
**Edit** I managed to fix it. I'm an idiot. My case was preventing me from pressing/holding the buttons well. In a list ditch effort while setting up my OG Pixel XL i took the case off my oneplus 7 and the button combinations worked.
Can't get into recovery mode or bootloader mode. I believe I bricked it while trying to get newest OTA installed. OTA was failing so I was trying to return my phone to completely stock. Everything was fine until I hit complete uninstall on magisk and it rebooted my phone. I'm using magisk 19.2, newest stable release.
The only thing I see now is the one plus power on logo, then message about bootloader being unlocked. Pressing volume up+power button will get the phone to power on but never loads to bootloader mode, only a black screen after the warning screen about having an unlocked bootloader shows.. Volume down+power and volume up/down+power do nothing.
Any advice on this would be appreciated before I send it in for an RMA