While using the SkipSoft ToolKit in order to flash a factory image to my Nexus 4, it ran into an error.
I tried again, this time downloading from Google myself, /occam-lrx22c-factory-86c04af6.tgz .
During the process, the toolkit got to "waiting for phone", and that's it. Nothing after that.
The phone won't turn on and won't go into recovery (power+volume down).
If I plug it into the PC again, there is a sound of recognizing a device. Buy not SkipSoft and not wugfresh will recognize it, nothing that ADB and Fastboot aren't working.
Is this a hard brick, or is there something I can do?
If ADB does not respond its maybe hard brick what happens when charging
So far, connecting it does nothing, both to a PC and to a wall charger. But I'll trying and keep it for the night.
If nothing happens jtag may help.
And thats hard. I suggest to get professional help or buy Nexus 5.
;_;
If you can get it into the bootloader there's hope. But if it won't even turn on then it's most likely bricked. Will power + vol up get you into the bootloader?
Sent from my Nexus 9 using XDA Free mobile app
Like I said, I cannot get into anything.
Related
Hi,
I. Have gotten myself into quit a frustrating situation. My nexus 7 was unlocked, rooted and had several different custom roms installed at various times and had never had a problem. But then one time in particular, when trying to flash a rom (which I can't even remember which one it was,) after the rom had "successfully" been flashed, it rebooted to the splash screen, which it stayed at for a very long time; before just turning into a series of flashing vertical lines that never end. I can use the power+vol- method to get to fastboot, but not recovery; it would appear that my recovery has been wiped as I get the same google splash screen loop as when I try to boot. My problem is that nothing I do allows me to successfully connect the device to my pc (w7, 32bit.)
I have uninstalled any conflicting drivers, un/re-installed the proper drivers from like 7 different guides, I have also tried two different nexus root toolkits. I even tried to use a Linux machine to no avail. I have switched USB cables, everything I have tried has not worked. This is by no means my first foray into android devices, I even freshly installed my android SDK and still my computer just fails to recognize the nexus 7 in fastboot mode.
Any tips or advice would be a godsend. Thanks.
This sounds like a issue a few people have been having.. As far as i know as of a week ago there is no solution . You need to flash the boot-loader it sounds like. There is a thread about this. Search for NV FLASH .. OR APX MODE. Sorry for being lazy and not looking for the thread for you..
They may have some things in that thread that you have not tried.
Turn your Nexus off and plug it into your computer. Does your Nexus start charging? A completely bricked Nexus wouldn't charge. If it starts charging, then try turning it on into Fastboot mode.
Sorry, I'm no dev. Just a random thought to try. But if your Nexus can charge you shouldn't be fully bricked, hopefully. At least this is what I think.
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
My bro bricked his N7
He was rooted and unlocked, flashed a rom now it bootloops on the logo. Now when doing adb devices, it doesnt detect the device when in bootloader, went to device manager and shows problem with driver. Tried other drivers but says its up to date. Thing is I just upgared his friends N7 with the same drivers so I know thats not a problem.
It wont go into recovery either. Now when it is bootlooping, the decive is recognised when doing adb devices. So can I flash a factory image when it is bootlooping or does it have to be in fastboot?
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
dramdrum said:
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
it doesn't even acknowledge that I plugged anything in to the computer at all.
chismay said:
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
Click to expand...
Click to collapse
Just goes to bootloader?
Edit seems to be working now even though when doing adb devices in fastboot it doesnt list the device id
In fatboot mode you don't have adb access - down load a recovery image and name recovery.img
Hold shift and right click in the folder recovery.img is in
Choose open command here, in cmd type
fastboot devices
If you see your serial number proceed
fastboot flash recovery recovery.img
When finished reboot to recovery and flash rom of choice
ps, you have had to either change your path in enviromental variables to include platform-tools from the sdk or have both fastboot.exe and recovery.img in the same folder that cmd is pointed to
Sent from my HTC Vision using xda premium
So I managed to bricked Nexus last night trying to flash the factory images. It wouldn't flash correctly through the Nexus Root Toolkit, due to the outdated bootloader. I tried to install the 4.2 boot loader through recovery, (as it was flashable). It it didn't work, and I can't boot into recovery as it gets stuck on the splash screen. And of course I can do anything in fastboot because the tablet freezes when I plug in USB. Anything else I can try?
Here's some quick info.
Recovery- TWRP 2.3.3.x
Bootloader- 3.3.4
ROM- CM10.1
Sent from my Rooted Nexus 4
JiG Brick USB
JiG Brick USB might help, but i don't know for sure.
AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
Are you able to boot into boot loader? If yes, you are not bricked. You can flash the factory image and you can flash a new recovery.
Sent from my Nexus 7 using xda app-developers app
So I got back from school today and tried to turn it back on again, and it decided to boot up normally.
This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?
Ethicistabdiel said:
This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?
Click to expand...
Click to collapse
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...
AndDiSa said:
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...
Click to expand...
Click to collapse
What I mean is that as soon as the USB is plugged in, the bootloader on the Nexus becomes completely unresponsive, I can no longer use the volume buttons to navigate the options or the power button to progress. It appears for all intents and purposes frozen and remains so after the USB is unplugged. Commands sent from ADB while the Nexus is in the bootloader just say "awaiting device" and nothing happens and I can't see the Nexus with ADB Devices.
I may not be using the best terms, I'm assuming the bootloader is the screen where you are given the options of recovery, restart the bootloader, start and so on. That screen becomes completely frozen when the usb cable is plugged in. If I select for it to go to recovery and do not plug in the USB cable, it goes to the google splash screen and the recovery never loads. I've had this Nexus fully rommed before, it has Clockwork Mod Recovery Manager on it and I've had no trouble getting it to load previously.
I'm doing all this because I tried to install a new rom (Paranoid Android Nightlies, latest version) and it did not install properly, upon start it says gapps has stopped and the setup wizard has stopped working - the OS will not load but will just keep repeating these error messages. Thus, I'm trying to either get into recovery or send ADB commands to the tablet to fix it.
AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
All fixed now. It was actually the computer, an issue with the USB, did it on my laptop and was able to fix it pretty quickly. It was you differentiating Fastboot from ADB that got me there though, I tried that on my PC and when it didn't work I then did it on the laptop. Most likely wouldn't have gotten there without you, at least not so quickly. Thank you very much!
[Q] Nexus 2012 doesn't turn on. I get "USB Device not recognized" when plugged in PC
fixed
Cocalarix said:
I was trying to install 4.4 and it got stuck at the sending 'boot' command. I tried a few times more, tried other drivers, same thing. It was in bootloader so I decided to restart it (this is the moment I regret). Since then I can't open it up. Tried the Vol buttons + Power for 20 secs, nothing works.
The only sign of life is when I connect it to a PC via USB. The PC shows me a Device not recognized error. Is there anything I can do?
It's a Nexus 2012 Wi-Fi 16 GB and I had 4.2.2 installed on it, but now everything is wiped out.
I found this: http://forum.xda-developers.com/showthread.php?t=2455927<br />
But I only made a backup with apps and user data with the Nexus Toolkit. I don't think I have the Blobs on that.
Also, the Nexus Toolkit tells me if I can't get to the bootloader, I might need to use ODIN, but I have no idea how to use that: http://www.andromint.com/download-odin-latest-version/
Anything I can do?
Click to expand...
Click to collapse
I'm in the same boat as you and I've been doing this stuff for years, do I have NO idea what I did. I was reimaging it back to 4.3 from 4.4 since Kit Kat broke flash videos for me.
As for ODIN, where you linked to is for Samsung devices. I don't know anything about ODIN, so not sure if that will help. It appears our devices are bricked. Whether they are hard or soft bricked, who knows. Also, since fastboot and adb cannot recognize our devices, ODIN doesn't do us any good even if it WERE for the Nexus 7.
I'm sending mine back into ASUS since it's still under warranty. At least, it's not a year old, but unlocking the bootloader has probably voided my warranty, but I have no other choice.
I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.
Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.
Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.
Hi all!
First of all I would like to give small heads up - I've been searching XDA and web for two days and ended with no working solution.
Situation:
Suddenly my Nexus 7 (2012) just died. No charging signs, nothing. So i tried Google described and random hardware resets using buttons with no luck.
I ended with situation:
device is not turning on - no screen flickering, not even small amount of pixel light visible,
ADB - no devices found,
fastboot - no diveces found,
nvflash - only my GeForce PC card found
when I connect device to PC I have to hold power button for ~10sec and there I hear "boing" (USB dev. disconnected), "boing" (USB device connected) sounds.
device is visible as APX device with "!" mark
I've tried:
hardware reset by pressing: power button, power+volume's buttons for different amount of time,
taking back and disconnecting battery,
using different software to discover device,
editing driver .inf file to recognize my device as ADB device. It did but still no visibility via ADB or fastboot (URL: http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/),
read and tried to use things from: http://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495.
No result at all...
One more - when I unplug and then plug in battery while having back taken I can hear sound that something is "running".
Please help!
@kepisty89 You can check here. Install the driver and check your device is detecting or not, actually you've a fried bootloader.
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
kepisty89 said:
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
Click to expand...
Click to collapse
Hi, kepisty89...
Unfortunately, APX mode is generally never good news .
It usually indicates that the Nexus 7's bootloader has either become corrupted or has been erased, and effectively hardbricking the device.
-----
See here, for a post I wrote for another XDA member with similar issues to yours, back in December 2014, where I elaborate further on this problem.
-----
I suspect your Nexus 7 will require a motherboard replacement .
Rgrds,
Ged.
I have similar issue, but mine I can get to bootloader but that's it, if I try to power it on all I get is the Google and unlock padlock, can't get to recovery, but my device is seen via fastboot ADB Wugfresh NRT, but as soon as I try to write to it ie flash files or try to restore device, ADB locks up, and when it says rebooting device my nexus tries to reboot but I get a black screen and Wugfresh says waiting for device, I have to force reboot bootloader hold power button vol down for NRT to see it again in fastboot. I can also boot tempery recovery via NRT but when I select mount it pops up on PC but I can't copy anything to it, also it says I have no OS installed.
Sent from my Nexus 6 using Tapatalk