I was in the middle of installing drivers for my device and was getting from ADB type errors using the supertool.
I didn't get far, and after getting the error i unplugged and turned off my screen and now it won't turn back on.
When i plug it into my computer it won't detect the device.
I had it for less than 30 minutes! Any advice here?
:sadly i've rooted and flashed many a phone, not sure what i did wrong here:
Hold vol down and power until it vibrates, then let go of power and hold vol down till fastboot. If you can't get to that, you're probably pretty bricked.
Note, there does not appear to be a vibrate motor in the Fire7. So no vibrate feedback.
Related
Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD
I think I was holding down the power while it was locked. it didnt reboot bus is now instead stuck with a black backlit display panel. home and return is on permanently and the charge light is also lit, despite not being plugged in.
holding down te power button for any length of time just makes the home and return flash for a minute and then back to solid.
no combination of power and volume up/down makes any difference. just flashing home and return lights.
HELP
do I just have to wait for the battery to run out?
Wait I'm a bit confused ...what current state is your phone in? Is it booted up if it is just adb that *****
a box of kittens said:
Wait I'm a bit confused ...what current state is your phone in? Is it booted up if it is just adb that *****
Click to expand...
Click to collapse
it was booted up. now it's just a dark screen with backlight, home and return buttons and charge light lit
plugging in USB and runningg adb reboot just says device not found
actually- when I plug it into USB it appears as in device manager for a few seconds
adb reboot during that period gives 'device offline' rather than device not found...
Hello,
I've just installed this ROM after wiping Cache/Delvik Cache and system wipe.
Now the phone is stuck on the boot screen and I can not get back into recovery to sort it out.
I held down power & vol+ buttons to get into recovery but nothing happens. The Home & Back buttons flash after 3 seconds then nothing happens.
Any thing else I should do to get into recovery ( TWRP)
My friend whop is a member asked this question on the Developers forum and so far no luck.
we have tried the following:
This is suggested by chogardjr: Plug your phone in to charge. Don't use a USB port for power. After you plug it in try the hard reboot again.
PLEASE HELP
Just for the sake of testing... Have him hold power without holding the volume. It should force reboot, not to the bootloader, so he can get a feel for how the reboot works. It can be finicky during a bootloop cause there are processes trying to run in the background. But it should do it if you hold power long enough.
Edit:
Also find out if the charge light comes on when he plus it in.
Tried and no joy.......
rking786 said:
Hello,
I've just installed this ROM after wiping Cache/Delvik Cache and system wipe.
Now the phone is stuck on the boot screen and I can not get back into recovery to sort it out.
I held down power & vol+ buttons to get into recovery but nothing happens. The Home & Back buttons flash after 3 seconds then nothing happens.
Any thing else I should do to get into recovery ( TWRP)
My friend whop is a member asked this question on the Developers forum and so far no luck.
we have tried the following:
This is suggested by chogardjr: Plug your phone in to charge. Don't use a USB port for power. After you plug it in try the hard reboot again.
PLEASE HELP
Just for the sake of testing... Have him hold power without holding the volume. It should force reboot, not to the bootloader, so he can get a feel for how the reboot works. It can be finicky during a bootloop cause there are processes trying to run in the background. But it should do it if you hold power long enough.
Edit:
Also find out if the charge light comes on when he plus it in.
Tried and no joy.......
Click to expand...
Click to collapse
I had a similar problem with a bad kernel flash and could not get the device to shut all the way off - thats why the keys are blinking. I plugged it in to a charger, left it like that for a few seconds, then unplugged, held it under a bright light and waited. After a few more seconds, it shut all the way down and I was able to boot to recovery in the usual way (power+down). You may have to try combinations or maybe not. But, you won't get to recovery until the phone shuts all the way down. High light under in the 'eyes', plugging and unplugging, and holding the power button for up to 30 seconds are all known ways to do this, but as was said before a bootloop has processes trying to run, so the machine can be 'confused' and have difficulty shutting down. Hope you are successful...
Thanks. I actually got it going with one of the answers posted for me, by powering it off under a bright light.
Sounds daft, but it works.
My power button stopped working a couple days ago but I was still able to wake device with volume buttons. I was worried that if my phone were to shut off I wouldn't be able to turn it back on so I booted into bootloader and was going to try and flash "oem off-mode-charge 0" (which should then make the phone power on when plugged into charger).
At the time I couldn't detect the device using fastboot and as I was searching around on my computer the screen on the phone turned off (was in bootloader at the time). I'm not sure at this point if my phone was on and that both the power and volume buttons were not waking device or if the phone turned itself off.
I have tried the hold the volume down and plug the charger in trick to try and get back into bootloader but nothing happens. When I plug phone into my computer it takes about 20 seconds but I get the little windows ding that something has been connected but phone is still not responsive. I'm starting to think I'm a little screwed here but welcome any input.
You just looking to get the screen to light up so you can implement a way to use the device without the power button? You could try gravity screen or something but first things first...
If its not lighting up on plugin have you tried connecting to a computer and opening ADB and issuing the command adb devices followed with adb reboot. If you wanna go back to bootloader just adb reboot-bootloader. That will restart device so screen is back on and I would turn on the Ambient Display mode so when you pick it up the screen comes on or get a volume power button app or gravity screen app that turns on when you take it out of pocket. Thats all I can suggest and hope any of this helps.
With phone plugged into computer, nothing shows up when I check adb devices or fastboot devices. I guess I'm unsure on what state my phone is in. None of the buttons do anything and nothing happens when I plug my phone into my wall charger (no charge light or screen on). The only response I can get is when I plug the phone into my computer windows makes a noise.
Anyone know what happens when a powered off phone gets plugged into the computer? Does windows make the little noise indicating a device has been plugged in even with it off?
It does not make a noise if its off.. That much I know. Interesting though. Are you sure you have the correct drivers installed for your nexus phone if you are on windows. Go into hardware manager by right clicking on my computer and make sure that its reading it correctly in usb devices without a yellow triangle next to it.
I should have the correct drivers. I just went ahead and reinstalled them through the nexus toolkit. In device manager it says: unknown USB device (device descriptor request failed).
I checked adb devices before all this happened and it displayed correctly. I then rebooted into the bootloader but the fastboot devices command did not show anything. It was shortly after that that the screen turned off. Will the screen normally time out when in the bootloader? I'm wondering if my phone is still in the bootloader with the screen off and both power and volume buttons non functional.
Only thing I can think of is to wait for it to die, then volume down + plug in to pc and when bootloader screen appears issue command fastboot continue and it should boot up. Then get something to remap key or an app. If this all fails after it dies and you restart it assuming debugging wasnt on or its just reading phone as media device of sorts not allowing adb then you may have to get the power button assembly possibly and install it yourself or open the back case and hit the power contact under the button and see if you can get it on. Thats all the ideas I have.
I'd also suggest that after you reinstalled drivers make sure you did a reboot and then plug in the device and also try using a different USB port and or USB cord also as odd as that sounds Ive seen it work before. Im pretty tapped on ideas tho. Do you know if you had usb debugging enabled?
Wireless charger
Sent from my Nexus 6 using XDA-Developers mobile app
Power Button replacement is pretty easy and cheap, there's a Tutorial
On YouTube
coremania said:
Power Button replacement is pretty easy and cheap, there's a Tutorial
On YouTube
Click to expand...
Click to collapse
Ok, cool. I'll take a look.
Managed to get it back into the bootloader this morning. So I guess this is a PSA, if your screen times out while in the bootloader, the volume keys will not wake device so since my power button is broken I couldn't wake it. At that point, the phone is in a state where it cannot receive any fastboot commands, even though it is in bootloader with the screen off. What I had to do was wait overnight for the battery to drain and have the phone power itself off. At this point the volume down plus plug in charger trick worked to get it back into the bootloader with screen on. At that point I was able to 'fastboot reboot' back into system.
Thanks for the insight people
double post
coremania said:
Power Button replacement is pretty easy and cheap, there's a Tutorial
On YouTube
Click to expand...
Click to collapse
It's easy but also annoying. Removing the 18 screws is the most annoying part
clapper66 said:
It's easy but also annoying. Removing the 18 screws is the most annoying part
Click to expand...
Click to collapse
I think the Nexus 6 deserve it
brumby05 said:
I should have the correct drivers. I just went ahead and reinstalled them through the nexus toolkit. In device manager it says: unknown USB device (device descriptor request failed)......
Click to expand...
Click to collapse
Driver issue.
Remove/uninstall the drivers from your PC when the phone is connected.
After that reinstall the adb/fastboot drivers.
N6 - Power mapped to VOL DOWN; turned off and can't get it back on
Hi all, I had to remap my power button - I mapped it to VOLUME DOWN. The other day I voluntarily powered down my N6 at a test center.....and haven't been able to get it to respond since. I do have a Pixel 2 XL on the way - but not that sure I'll want to keep it. The N6 is so sweet.
I've tried holding the volume buttons (POWER and VOLUME UP) for like a minute, but nothing. When I charge it, I see the battery symbol (full) but only for about 5 seconds.
ADB does not see any connected devices. Wug's NRT does not see any connected devices. I'm at a loss and afraid that I've lost my N6 and will have to use the Pixel 2 XL regardless what I think about it.
Any other ideas?
JMacD said:
Hi all, I had to remap my power button - I mapped it to VOLUME DOWN. The other day I voluntarily powered down my N6 at a test center.....and haven't been able to get it to respond since. I do have a Pixel 2 XL on the way - but not that sure I'll want to keep it. The N6 is so sweet.
I've tried holding the volume buttons (POWER and VOLUME UP) for like a minute, but nothing. When I charge it, I see the battery symbol (full) but only for about 5 seconds.
ADB does not see any connected devices. Wug's NRT does not see any connected devices. I'm at a loss and afraid that I've lost my N6 and will have to use the Pixel 2 XL regardless what I think about it.
Any other ideas?
Click to expand...
Click to collapse
Wow - just got my N6 to boot using this little tip I found on Reddit - https://www.reddit.com/r/AndroidQue...ny_way_to_turn_on_phone_without_power_button/
I was holding down the Vol Up and Power buttons (which are both the Volume bar since I remapped my power to Vol Down), but I hit 'enter' on the 'fastboot continue' text in the CMD prompt just after I plugged in the USB and the battery icon came up. It booted into bootloader mode briefly first, then went into system reboot. Whew!
I think your button assembly is broken and I would replace it. You could try the work around in Broken power button, any way to boot? by altarity, post #3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Dear all,
I was on beyond 5.3 with twrp 3.3.1.7 and I wanted to update everything. Magisk, root etc was working fine.
I downloaded the patched twrp file from the beyond telegram chat and flashed it as image into the recovery partition.
The installation was finished in 2 seconds, but stupid me chose to power off instead of rebooting the recovery.
So I tried to enter recovery using the button combo but nothing happened and I was stuck with the samsung logo.
The current status is that my phone only shows the samsung logo.
Holding the power button for a minute doesn't do anything.
Pressing the button combo for recovery mode doesn't do anything.
Pressing the button combo for dl mode makes the phone reboot. It vibrates for a sec, then the samsung logo shows again.
If I keep pressing all 3 buttons the phone keeps on rebooting and vibrating each time, but dl mode never appears. If I let go of the power button the logo stays and again, nothing happens.
So basically I can't enter dl mode nor reboot.
Should I let it run dry and try again or just throw out of the window immediately? :crying:
I let the battery drain over night. Phone was finally off.
So when I plug it in, the Samsung Logo appears and doesn't change. It just stays like that forever until the battery drains.
Pressing the power button doesn't do anything, no matter how long. It doesn't reboot nor does the logo disappear.
Pressing vol+, bixby and power again does nothing.
Vol-, bixby and power makes the phone reboot. The screen turns black, the phone vibrates shortly, the logo reappears. If I keep pressing the buttons the phone reboots again, and again, and again, mever reaching download mode.
If I let go of the power button and keep pressing vol- and bixby the phone stays black and won't even show the logo. Nothing happens. If I let go of either of the two buttons the logo appears again.
It won't boot, won't go into recovery or go into dl mode.
I'm doing all this while it's plugged into the usb port of my pc, and it doesn't get recognized. Samsung 300k tool doesn't recognize it either.
Now I know the meaning of "bricked" lmao.
Does anyone know how to possibly fix this?
Pressing only the power button for a minute literally does nothing. Like hell, how is that even possible?
You can try this to go to download mode:
Vol down + bixby + usb cable connect to PC
It's advisable to charge battery first before flashing firmware.
XTrail02 said:
You can try this to go to download mode:
Vol down + bixby + usb cable connect to PC
It's advisable to charge battery first before flashing firmware.
Click to expand...
Click to collapse
I tried that for like a thousand times already but now it chose to magically work somehow.
I think I peed myself a little when that ugly turquoise screen appeared and I screamed from sheer happyness.
THANK you!!!
The problem that doesn't stop giving lmao.
Got into DL mode, got odin to start, but after like 10 seconds my phone dies and odin fails.
Now I cant get into DL mode, but rather only the "an error occurred while updating the device software. use the emergency recovery function in the smart switch pc software."
Could it be the battery that simply dies?
hoeni said:
The problem that doesn't stop giving lmao.
Got into DL mode, got odin to start, but after like 10 seconds my phone dies and odin fails.
Now I cant get into DL mode, but rather only the "an error occurred while updating the device software. use the emergency recovery function in the smart switch pc software."
Could it be the battery that simply dies?
Click to expand...
Click to collapse
Yes most probably a discharged battery. Hopefully you can go to DL mode again after charging your phone.
hello,
I've and S10e and because an important app to me I need to go back to android 9 where it works.
I've read a lot info about downgrade, but no one says ROOT/UNBRICK.
Can someone inform if there is a way of downgrade without ROOT (maintaining the warranty).
thanks in advance
P.S.: Maybe too naive question, sorry for that