Hey guys, I signed up here because I'm desperate for help!
To cut a long story short, I upgraded my N7 (wifi 2012 model) from 4.4.4 to 5.1.1 which was an awful idea as performance was through the floor. So I used the ADB tools to flash and downgrade back to a stock 4.4.4 image from the google repository.
Unfortunately, after flashing I tries to get to the recovery mode (was on the boot loader) and it said "error", wouldn't let me go any further and just kept me in the boot loader menu. I rebooted the device thinking it might have just needed a gentle shove, but it didn't reboot...it turned off after using the power off command.
Now when I "try" to turn the device on I get a black screen and nothing else. To confirm, this isn't the usual battery related "black screen" with grey static and the enabled backlight caused by long term discharge. The screen is totally black, no matter what key combination I use there is no visual response. The only time I can generally see any sign of life is when It's plugged into my laptop - windows plays the "new device detected" chime, but ADB can't see it and about 90% of the time windows states there was a device error. At this present moment the device is powered on (again, no visual sign) just a chime and an active driver showing in devmgmr for "Android ADB Interface".
ADB - Any attempt to use ADB fails and shows "no device found / connected", I've tried multiple solutions such as the nexus root kit but they all have the same issue, they just can't talk to the device. I know it's not the laptop at fault because it was detected fine multiple times prior to flashing it?
There is something alive in the device in terms of powering it off and off as holding the power+vol down button does do enough to trigger the windows chime to indicate it's powered on, but windows can't do anything with it at all. Note the device was 95% charged during the flash so it's not like it crashed mid way.
Any help would be appreciated, it'd be a shame to bin it
Thanks
Lawrence
Take the back off and disconnect the battery. Press the power button to discharge any leftover charge. Plug back in the battery, then try powering up in bootloader mode.
Sent from my LGLS991 using Tapatalk
Hi Psiphi,
I did as you suggested, took the case off and disconnected the battery cable - pressed and held the power button in different combinations to make sure it discharges any remaining power.
Sadly, no change - any attempt to power it on results in the same lack of response
Anything else to try?
Thanks
You might try forcing a flash using the Nexus Root Toolkit, but otherwise I am out of ideas short of buying new hardware.
Sent from my LGLS991 using Tapatalk
I agree use nexus toolkit, use the force flash mode... I recovered mine about 6 months ago it was dead... Nothing worked...
Sent from my LG-H811 using Tapatalk
Related
Hi everyone,
I have had some trouble with my Vogue. At first it simply would not turn on. I would get a red light when I plugged the phone in to charge it. I have been using my old phone for several months now. Today I went out to the nearest Bell store and it seems like anything new is going to cost in the $500 area because I still have 1 year left on my contract. So I have renewed my interest in getting my Vogue working again
The original thread describing my original problem (with the red light) is here:
http://forum.xda-developers.com/showthread.php?t=546674
I purchased a new battery and now when I plug it in on the USB I can turn it on (no lights, red, green, or otherwise) but it does turn on. It boots up just passed the blue “Bell” splash screen and then reboots. It does this over and over again.
I am able to get into the boot loader screen by holding down the power and camera buttons and pressing the reset button.
Any ideas on what I can do? Any suggestions are welcome.
Regards,
The Fish
Reflash your rom when you get to the bootloader screen.
If you are unlocked flash nfsfan or whatever, just rename the nbh file to 'VOGUIMG.nbh' and it will flash.
If you were on stock you'll need the nbh from the stock package.
OK, here is an update
I have tried a hard-reset (press Send and End buttons at the same time and press reset button). This worked but the phone still kept rebooting. Tried the original battery, phone booted a little further up before rebooting.
I got the phone into boot loader mode and left it plugged in on the USB cable for a few minutes. This time when I rebooted I became ecstatic. I got all the way to the “align your screen” stage before hearing the “phone is dying” sound and the phone turned off. So here is what I think may have happened:
I have long lost the home charger kit. So I have, for as long as I can remember, been charging it by plugging it into a PC via the USB. This is fine except that Windows will only power the USB for the device if there is a driver installed. The device/phone looks different to Windows when it is in boot loader mode then when it is fully booted up. If the device is so dead as to not even have a flicker of life I don't think Windows sees it.
I have been doing this tonight under Linux. Linux seems to either have the driver, a more generic driver or powers the USB all the time for any device. I noticed this same behavior when charging my Moto Razr the same way. Under Linux it just worked by plugging it in. Under Widows I had to install the driver. So maybe here is what happened.
The battery got SO dead that it was not able to boot the phone up far enough for Windows on the PC to see it, recognize it and begin powering the USB port. Perhaps leaving the phone in bootloader mode and plugged into a Linux box got the battery a little more charged till I got to the point of being able to align the screen.
Anyway, I am more then ever convinced that this is some kind of battery/power issue. The phone is now lying here powered up and charging (already at 20%). The carrier customizations ran, rebooted while I crossed my fingers, and came back up. I even called *BELL and got a message about activating my phone. Tomorrow if the phone is charged up and behaving normally I will get an ESN change done and be back in the world of decent smartphones. Man have I ever missed my Google Maps
The next step is to flash a more up-to-date ROM... if I dare mess with a good thing.
The Fish
I installed Go Launcher HD onto my KF and after that the device's performance became very lagged. So, I shut down the device in order to restart it. And when I turn on the device, Kindle Fire logo appeared and then the screen went black. After that, I cannot turn on the device as nothing appears (even the orange-color power button light.) When charging, the device becomes hot (which I think it's charging correctly.) But when connecting to PC, nothing comes up (again, even power button light) and the device manager cannot detect the device's plugged in. That's why I cannot try unbricking my KF with other unbricking softwares out there as it cannot be detected on PC. Please help me how to solve the problem.. (already tried pressing power button for 20sec but nothing happened)
Firmware is 6.2.2.something and it's already rooted
Please..
Thanks a lott!!
Uninstall and delete your drivers
Find and reinstall new drivers.
Use command prompt and fastboot to change bootmode to 4000
Reboot
Get rid of KFU
Sent from my Amazon Kindle Fire using xda premium
I installed the driver using the one from KFU.. and when using cmd, the message keep saying "No device found" although I connected to the PC.. =(
plss...
Did you uninstall then reinstall your drivers?
Sent from my Amazon Kindle Fire using xda premium
yep, bro! I just tried... nothing's happened.. the PC still can't see the device attached.. Also, even power button is not showing orange color..
Make sure you have a good charge on the device. You may have to leave it plugged in for a day to make sure. Afterwards, if you aren't able to get your screen to turn on, your next step would probably be to get a factory programming cable.
If you are able to turn the device on then it's probably just a matter of issuing the appropriate commands.
Sent from my Amazon Kindle Fire using xda premium
Try This
I had something very similar happen to me the other night. I couldn't power on the device. Nothing would see the device......computer or wall charger. I didn't have a green or orange power light either.
I held the power button in for 30 seconds. Let go and hit it again and it came back to life. Seems simple I know but it worked for me.
I did a good charge.. tried leaving charged for at least half a day (pretty enough amount of charging time.. I think) nothing comes up beside becoming hotter when charging and yes.. I did tried pressing the power button for 30 sec several times.. it really shows up nothing..
Btw, what's the factory programming cable, bro?
A factory programming cable provides power directly to the device instead of the battery and forces the device into fastboot mode. Your problem is that you are already in fastboot mode and if I'm not mistaken, the device will not charge in that mode.
The factory cable gives power to the device so you can issue fastboot commands to change the bootmode so you can charge it normally (among other things).
http://forum.xda-developers.com/showthread.php?p=24791016
Sent from my Amazon Kindle Fire using xda premium
So, please point me out.. should I try that one? cuz I'm from Asia and not okay to order that stuff.. should I really try with that one?
You have a couple of options, depending on how brave you are. You could make your own factory cable http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html Or you could CAREFULY open your device and make a temporary connection between the number 4 and 5 pins of the USB port. By opening your device you stand a real chance of causing irreparable damage.
But I can't see a reason why you wouldn't be able to find a "Motorola style factory programming cable" somewhere in your area. Search the web, you might get lucky. I wouldn't suggest doing anything that would get you in trouble with your local government though.
Sent from my Amazon Kindle Fire using xda premium
Hacking noob here. As in never. Sorry if this is "yet another annoying noob" issue.
I just got an N7 today and I'm having boot issues. I was able to use the device initially, I got it setup and it charged to 100% earlier. Then I did my first shutdown in order to investigate the bootloader. Since then it has been difficult to get it to power on.
The device is brand new, stock, and nothing done to it, other than user setup, and USB Debugging has been enabled. And I haven't dropped it or gotten it wet or dusty or anything fail you might be thinking of. No crazy apps, not rooting ,etc.
Reading up, it sounds like I need to power off the device, then simultaneously press Vol Up, Vol Down and Power (for some amount of time) in order to get into the bootloader /recovery menu.
This does not happen. Nothing happens.
So I tried to power the device back on. It doesn't.
I plug in the USB cable and I don't see the charging icon appear.
I notice a possible discoloration near the usb port, which could simply be the spot where the notification led is, but there is a visible "spot" that can be seen there. Wondering if this is an indicated that something is fried?
After messing around with cables and random button pressing I have gotten it to boot a couple of times, and seen the charge icon a couple of times, but I'm starting to suspect that this device is effectively DOA. Its been charged sufficiently (>60%) ever since I got it.
1. Anyone have any advice on this? I have no plans to wipe the device, I wanted to actually investigate sideloading the OTA. Answer - Ignore this.
2. Am I missing something? Is there a different/specific order of operations to start it? Answer - Bobos will fail.
3. Does it matter if USB power is connected while trying any of this? I've tried 3 different sources. And none provide a consistent state. Answer - No.
4. Can anyone else confirm this "discoloration" is visible at this spot? (halfway between the bottom center and the display area) Answer - Its just the notification led.
UPDATE: Turns out that pressing all 3 buttons causes a portal to another planet to open over Manhattan. Do not do this.
Instead simply press Power + VolDown to get to the bootloader.
I expect you have a defective device. However, you might just be doing weird things with your buttons.
To get to the bootloader, you just need to hold down the power button and volume down button. You don't need to have the microUSB cord plugged in.
For simply booting up the system: there have been times when I've had to hold the power button down for a while in order to get the device to boot up.
Sent from my Nexus 6 using Tapatalk 4
You need to hold the power button down a few seconds to turn on.
Boot loader is Power+VolDown
The discoloration is the notification led.
Thanks for the replies! I was able to finally get into the bootloader menu by following xdhall's instructions. And from there, into Recovery. Since using this method I'm not having any power on issues. It may be a "bug" in how it registers button presses, because it definitely isn't acceptable to have my experience occur (no usb charge, etc)
On to trying to update to 4.4 via the OTA recovery method. Google can't stop me now.
Thanks to sfhub for speaking to the discoloration. I really wasn't sure if I saw it before this issue started. Better to panic and ask, then assume and fail.
Oh yeah, don't press down all 3 buttons for 10 seconds from power off, it does wierd things.
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Sent from my Nexus 7 (2013)
I was just about to ask a similar question. Many thanks to zenrage for doing the work for me.
Sent from my SPH-L710 using XDA Premium 4 mobile app
BreakShadow said:
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
If you get the blinking LEDs, that is because the power is drained too low.
No blinking LED,just doesn't boot always at any battery level whatsoever. No issues with the buttons, they work fine when on. Untouched and locked system.
Sent from my Nexus 7 (2013)
BreakShadow said:
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Click to expand...
Click to collapse
I had that too...returned it.
It was totally random...and would shut down by itself at random even though I charged it recently. I think it's an issue w/ the battery level sensor because to get it to boot, I'd have to plug it in for 15min, then power it up...
My old N7 2012 never had that quirk
I'm glad you were able to solve your problem with your nexus 7! I hope you enjoy it!
Sent from my Nexus 5 using xda app-developers app
I was using the Nexus Root Toolkit v1.7.9 to flash stock back onto the device when it hung. Went to a black screen and then refused to power on. To elaborate, it will not display a battery icon when on the charger, nor can I get the device to display anything on the screen with any button combination. No fastboot. No twrp. Nothing. The only sign of life I have gotten from it is when connecting a usb to my computer (Windows 8.1) and holding down the power button on the device, I can hear it "connect" to the computer. In device manager, it shows up as APX. It had previously been shown as a USB device that could not return an ID...or something to that effect.
Without being able to boot the device up, I am clueless as to what to do. I have tried charging it for an hour. I have tried all button combinations, along with holding them for various lengths of time. I am just out of ideas and can't seem to find anyone else experiencing this exact issue.
Is anybody with more experience able to point me in the right direction?
Thanks in advance.
This happened to me awhile ago. When I first started to read about this issue it was that the battery becomes lose causing this issue. Another is just letting it sit idle for so long and no matter what the battery level it would cause this as well. Sorry can't remember all the technical stuff on that one.
I eventually contacted asus and sent it back. About two weeks later I was sent a new one.
Sent from my SCH-I545
This is a bizarre problem for me that's I can't find solutions to anywhere else. I have a 32GB Nexus 7 (NOT the 2013 variety) running Android 4.3. I've never rooted this tablet before, everything is original and I've never seen any issues with battery or screen performance before. After using my tablet during class with no problems and an 80% charge, I turned it off, traveled 10 minutes to a meeting, and pulled it out of my bag to turn it on. The screen didn't turn on, so I held the power button to soft rest it. Nothing happened, so I tried booting into the bootloader by holding down power and volume down. No luck there either. I plugged it into my computer and got an error message saying "USB device has malfunctioned". I tried using adb to reboot it or reflash a stock ROM with no luck, as the command prompt couldn't find my device. If I performed a soft rest or unlplugged my tablet from the computer, I would get a chime indicating that a USB device had been disconnected.
Does anyone have any suggestions with how I could proceed troubleshooting from here? I suspect there's probably a hardware issue, but that doesn't make much sense, since it was in a protected pocket for only 10 minutes and stopped working. Any help would be greatly appreciated.