Need to return to stock w/out functioning power button

cubsfan187

Senior Member
Dec 11, 2010
656
340
0
Elgin,IL
OK here's the quick version of what happened.

Last night, before leaving work, I was playing a game (dice w/buddies) and when I was finished I put the phone to sleep. Picked it up after my 45 min drive home and the screen wouldn't turn on at all. Pulled the battery and as soon as I put it back in the phone vibrated and started the boot process. I didn't even hit the power button. I let it do it's thing and just watched. The screen was all kinds of jacked!! Vertical banding and discoloration to say the least. Well it took about 10 min to boot but when it did the touchscreen was unresponsive. After about 10 min of batt pulls to reboot and check the screen, I called VZW for a replacement.. (They overnighted one and it will be here this morning) So after that call, I just put the phone down and fed my daughter and did a few things around the house. Went back about 2 hrs later and pulled the battery and rebooted the phone to find that the screen now works! BUT the power button does not. It won't wake the phone up,put it to sleep, nothing. It's dead. So I thought I would unroot/relock and take it back to stock so I can send it back. Here is the problem with that; with the power button broken, fastboot won't recognize the phone. I can get into the bootloader via rom toolbox lite (JRummy app) and that works fine. But whether I try it thru adb or WugFresh's toolkit, as soon as the phone hits "Checking fastboot status", it fails. When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.

So how can I return to stock without a working power button? Even if I was to get it back to stock somehow, I can't relock it as I would have to hit the power button to accept the warning. Is there any other way?
 

eqjunkie829

Senior Member
Apr 17, 2011
1,490
596
0
West Jordan, UT
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
 

cubsfan187

Senior Member
Dec 11, 2010
656
340
0
Elgin,IL
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.

Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
 
Last edited:

cupfulloflol

Senior Member
Feb 27, 2010
487
176
0
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.

Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.

When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
 

cubsfan187

Senior Member
Dec 11, 2010
656
340
0
Elgin,IL
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.

When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.

The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
 

cupfulloflol

Senior Member
Feb 27, 2010
487
176
0
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.

If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
 

cubsfan187

Senior Member
Dec 11, 2010
656
340
0
Elgin,IL
When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.

If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.

I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
 

cupfulloflol

Senior Member
Feb 27, 2010
487
176
0
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
 
  • Like
Reactions: bodh and cubsfan187
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone