Database Info

(Possible Brick) Power button not work, bootloader freeze, device turns on itself

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.

[Q] HOX Stuck on Boot logo

Hi there, I'm new at this forum and new at android so please be patient with me!! This is my problem and I have a few questions too.
I wanted to perform my htc one x AT&T interface so I rooted it succesfully, then I installed recovery PWRP v2.6.0.0 but i dont know what went wrong and now i cannot start my phone, it is stuck on htc boot screen. I'm really afraid of what can happen now. I've read that if you install the wrong ROM i can brick it. I want to know how to fix this, and if i can flash any any any ROM at this forum. I know that htc is not upgrading this phone to android 4.2, just to 4.0.4, which is the one i have, but can i upgrade to 4.2 sense 5 using a custom ROM? please if you need any info ask for it and thank you!! Evermore, I wiped system, sdcard, cahce, etc...

We will need some further information from you. You said your phone hangs at the HTC screen when you try to boot it, does it stay on that screen constantly, or does it perform multiple boot loops? Here's a couple of options:
Scenario A (phone stays in htc screen constantly): hold volume down + power together, keep holding them and your button lights will start flashing then the screen will turn off. After a couple of seconds let go of the power button but continue holding volume down until you reach the bootloader (a white screen with text).
Scenario B (phone performs multiple boot loops): hold the volume button while it's booting, the next time it reboots it will enter bootloader as long as you keep holding volume down.
Now that you're in the bootloader, please post the first five lines of text you see. Also please tell us which root/unlocking method you used, and whether you've flashed any custom ROMs or anything at all before your phone stopped booting.
Sent from my Evita

timmaaa said:
We will need some further information from you. You said your phone hangs at the HTC screen when you try to boot it, does it stay on that screen constantly, or does it perform multiple boot loops? Here's a couple of options:
Scenario A (phone stays in htc screen constantly): hold volume down + power together, keep holding them and your button lights will start flashing then the screen will turn off. After a couple of seconds let go of the power button but continue holding volume down until you reach the bootloader (a white screen with text).
Scenario B (phone performs multiple boot loops): hold the volume button while it's booting, the next time it reboots it will enter bootloader as long as you keep holding volume down.
Now that you're in the bootloader, please post the first five lines of text you see. Also please tell us which root/unlocking method you used, and whether you've flashed any custom ROMs or anything at all before your phone stopped booting.
Sent from my Evita
Click to expand...
Click to collapse
Thank you for your reply. I fixed this problem installing DM9 ROM and now works great. Here are the first five lines you asked:
It is unlocked
EVITA PVT Ship S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I used X-Factor root and at a first time it used to get stucked on htc white scrren logo, then i performed a cache restore through adb and at that time it started rebooting over and over again.
If you can help me now with the following will be great: I want to know if i can upgrade my OS to 4.2 JB with Sense 5 having superCID and s-on, or if there's a ROM out there that can simulate Sense 5 for 4.0.4. If it exist, could you tell me which will work fine? thank you very much

You can definitely run the Android 4.2.2 / Sense 5 ROMs with your current setup, no problems. You will need to flash the Beastmode kernel as well as the ROM to fix signal drop issues though. All of this can be found in our Android Development section.
Sent from my Evita

[Q] HOX Evita in bootloop - can't get to bootloader/recovery

Hi - I just flashed ViperXL via TWRP (2.5, IIRC), but haven't flashed boot.img yet. Phone is now rebooting to the dev screen, then the One logo screen, then black again. I can't get to the bootloader or to TWRP. I've tried the volume-down button during boot to no avail. I've got ADB at the ready if needed...
S-On, hboot 1.14. I've done this many times before w/o issue.
Any ideas?

While the phone is rebooting just keep holding volume down. If it isn't working it's a case of bad timing. You need to flash the boot.img, why didn't you? Also, you should upgrade to TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita

I agree with timmaaa, failure to get into hboot if the screen comes on, is almost always a matter of not performing the button sequence correctly.
The most common errors while dooing this:
1) Letting go of the vol down rocker too early
2) If you press the vol down rocker after the white "HTC One X" boot splash screen is already up, its too late. You have to do it before the boot splash appears.
The most foolproof way to do it, is hold both vol down and power at the same time. Hold them for several seconds while the screen is on, and the capacitive buttons should flash a few times, then the screen should go black as the phone restarts. Let go of the power button ONLY, and DO NOT let go of the vol down rocker until the bootloader screen appears.
EDIT. Thanks (sarcastically) for solving your issue on another thread here, and then not updating us here. (cross posting is against the rules for a reason). I wasted my time trying to help, when you already solved it.

Volume and power buttons stop functioning after kernel flash.

I flashed francor 58 through the franco updater on top of mahdi rom 6/70. When I got boot loops I reflashed r57 (had previously worked) and when it came up I no longer had working volume rocker and power buttons. If I hold down power the device DOES power off. I tried flashing other roms as well as stock and the problem persists.
I did an e2fsck on data and a factory reset with the google image and I still have the problem. The power button also fails to activate the screen in recovery. But it allows me to select and enter recovery from the bootloader.
Any help would be greatly appreciated.

zetorung said:
I flashed francor 58 through the franco updater on top of mahdi rom 6/70. When I got boot loops I reflashed r57 (had previously worked) and when it came up I no longer had working volume rocker and power buttons. If I hold down power the device DOES power off. I tried flashing other roms as well as stock and the problem persists.
I did an e2fsck on data and a factory reset with the google image and I still have the problem. The power button also fails to activate the screen in recovery. But it allows me to select and enter recovery from the bootloader.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you ever find what the problem was? I'm having the same issue.

Help, same here...
I flashed yesterday latest LaboDJ's Linaro (62v2) over an older version and this morning my power and volume buttons aren't responding at all.
I flashed back system.img and boot.img from latest ota.zip but the problem persists.
Buttons are working fine in bootloader...

Did you guys try other kernel? I never heard this problem before. Try to clean flash any rom and see if it solves.

No luck, even flashed the whole L factory image...
as soon as my screen goes off, my only solution to bring it back alive is to keep power pressed 15s and let it reboot. Proof that the button press is somewhat registered in hardware I guess

Mosquito2001 said:
No luck, even flashed the whole L factory image...
as soon as my screen goes off, my only solution to bring it back alive is to keep power pressed 15s and let it reboot. Proof that the button press is somewhat registered in hardware I guess
Click to expand...
Click to collapse
Holding down the power button for 10-15 seconds is hard-coded to be a battery pull emulation, not affected by ROM nor kernel.
Did you try running the flash-all.bat? (backup to a PC first)

Do sensors work well?

ok, I'm not 100% sure how but got my buttons back
What I last did before they start working again was to boot into bootloader then recovery which was still default (open Robot with red triangle).
I kept volume up while pressing power as I've read on some post (hard reset?) and the phone rebooted to android with both volume and control buttons working.
Did I reset something extra or is it pure coincidence? Guess time will tell

[SOLVED][Q][HELP][HOW TO] Unable to bypass unauthorized device

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