I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.
Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk
psiphi said:
Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
No chance with solution number one.
As I said I 've left it charge for more than 10 hours. Measured the battery's poles.
Around4 volts, 2.7 amps. Everything's fine with the battery.
The tab won't boot at all. Can't enter bootloader, can't be recognised by the USB, can't use the Root Kit.
tedsorvino said:
I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.
Click to expand...
Click to collapse
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.
GedBlake said:
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.
Click to expand...
Click to collapse
Thank you. Even if the news are bad, it's a really valuable piece of information. At least now I know.
Related
Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
chris_te said:
Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
Click to expand...
Click to collapse
Can you boot into fastboot? recovery?
Edit: Sorry, saw that you wrote you can't...
I added the information afterwards. Sry
Basically, there are two ways to fix this:
1) I don't know how, but through QHSUSB_DLOAD you probably can flash something...
2) JTAG Repair.
1) Sounds interessting. I thought at something like this: UnBrickable Resurrector
But is there a chance to get this solution to our nexus 4?
2) Nexus 4 - JTAG Brick Repair Service is also interessting but i don't know how much time it take vom germany to usa to germany back.
I thought the nexus 4 is unbrickable
If you got it into Download mode, then you should be able to get into recovery. (Assuming you didn't do a bad flash of that)
Unplug it
Hold volume down and power
Plug it into WALL CHARGER (not a computer) while still holding the buttons
Someone also flashed a Nexus 7 kernel (also Franco) to his Nexus 4. Didn't look good because the Nexus 7 kernel overwrites a partition from the bootloader, if I remember correctly. Here is it explained better. The last post from the guy who flashed it didn't look too good also. Sorry to hear man.
Maybe you can RMA it. I don't recommend it because it's your own fault, but everyone makes a mistake sometime sooner or later.
I am another one who did the same mistake - accidently flashed the franco Nexus 7 Kernel. ::crying:
Even the Qualcomm flash tool which I tried couldn't get acces to the device. So I'm waiting for my replacement device now and hope LG can fix the problem.
chris_te said:
Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
Click to expand...
Click to collapse
Sorry to hear your bootloader has been obliterated. Try to RMA via Google or contact LG and find out how much they will charge to flash the device.
On a side note, I'm curious if you're able to put the phone in to download mode (not fasboot or recovery).
1. Make sure it is off
2. Hold volume up + volume down and plug in USB.
Even if you can get to download mode I don't think we have what we need to get the device working (LG drivers, KDZ image, etc) but this would indicate some promise for the future.
Until the Qualcomm USB Dowland mode is figured out, you're boned. Gonna have to send it away.
comminus said:
On a side note, I'm curious if you're able to put the phone in to download mode (not fasboot or recovery).
1. Make sure it is off
2. Hold volume up + volume down and plug in USB.
Click to expand...
Click to collapse
Hi,
I tried your suggestion and it did't work
The phone tried to boot into download mode but didn't get it. Screen was always black. After 10 second the phone vibrated and tried it once more.
Do you think the people of MobileTechVideos can help me?
I'm still waiting for a response from Josh.
Here is a link to a Nexus 4 - JTAG Brick Repair Service video: http://www.youtube.com/watch?v=gYtNWt1h66E
And if all this does not work, i have to send it to the google RMA.
If it were me, I'd pay LG to fix it. Either contact Google for RMA or contact LG and ask them what they would charge to flash the device.
Sent from my Nexus 4
chris_te said:
Hi,
I tried your suggestion and it did't work
The phone tried to boot into download mode but didn't get it. Screen was always black. After 10 second the phone vibrated and tried it once more.
Do you think the people of MobileTechVideos can help me?
I'm still waiting for a response from Josh.
Here is a link to a Nexus 4 - JTAG Brick Repair Service video: http://www.youtube.com/watch?v=gYtNWt1h66E
And if all this does not work, i have to send it to the google RMA.
Click to expand...
Click to collapse
Just press VOL - key and plug into USB connected to PC, ARE YOU IN FASTBOOT MODE ?!
IF YES, flash stock firmwares... and let the device rest for 15 min.
then plug into AC charger and let it charge for min. 1 hour...
If nothing happens, you possibly damaged your battery !
I had the same issue... I sent it for RMA.. Although by this method, many have recovered, if there is no battery issue as such !
Give it a try !
And dont use toolkit... Use FASTBOOT COMMANDS ! MANUALLY !
You have to reach fastboot mode:
1) Turn the phone off!! Not so easy (for me when never done before)!! Unplug it and try to press power, it often needs a little time/serveral tries.
When off :good:- very important:
2) Hold volume - and power simultaniosly - and plug it into WALL CHARGER (not a computer) while still holding the buttons.
3) Fastboot Mode!!!? --> :laugh:
4) Plug it to PC and flash stock rom
Good luck!
torsin said:
You have to reach fastboot mode:
1) Turn the phone off!! Not so easy (for me when never done before)!! Unplug it and try to press power, it often needs a little time/serveral tries.
When off :good:- very important:
2) Hold volume - and power simultaniosly - and plug it into WALL CHARGER (not a computer) while still holding the buttons.
3) Fastboot Mode!!!? --> :laugh:
4) Plug it to PC and flash stock rom
Good luck!
Click to expand...
Click to collapse
The people who said the bootloader was overwritten are most likely right. Its done. This phone has the same processor as the s3 and on the s3 QHSUSB_DLOAD is the kiss of death.
QHSUSB_DLOAD=Qualcomm High Speed USB Download
Its basically a piece of hardware waiting for firmware to be loaded at a factory level. You need JTAG
billard412 said:
The people who said the bootloader was overwritten are most likely right. Its done. This phone has the same processor as the s3
Click to expand...
Click to collapse
btw: s3 is arm not qualcomm, but not important here.
Was referring to the us variants that also use the qualcomm snapdragon s4 processor like the n4 does
Ah, okay - sorry I don´t know!
And for the record, Qualcomm chips are ARM cores.
Also for the record, my JTAG solution for this model will recover a device that is hardbricked via bad software flash. In this case you have flashed a Tegra kernel into the device and likely also into the incorrect partition as well. I have a complete backup of all necessary zones required for boot (sbl's, aboot, boot, rpm, tz and a few others). If you've damaged your Nexus 4's bootable zones and the device is hard bricked due to it, I can repair it for you.
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you ill try that. it was at 33% battery when this happened though
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
i know about the screen time out, i tapped the screen for it to rewake and it didnt work, then i tried pressing the sleep button once for it to unlock and that didnt work. so it indeed shutoff
frap129 said:
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Click to expand...
Click to collapse
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Anyway, I would proceed with a dead battery or loose battery connector hypothesis first. It's not obvious why writes to /boot, /cache, /data, or /system would affect the bootloader.
Anything is possible at a low enough probability I suppose, but you should start troubleshooting operations with the high-probability scenarios first.
For instance - with the power off, will the "charging screen" display when you plug the tab in? How about APX** mode? (Plug in to PC and start with Power+Vol-up). If you didn't see either of those, it's likely a power supply or hardware problem.
good luck
** make sure you exit APX mode by holding down the power button for at least 20 seconds. I'm not sure if it shuts itself down after an inactivity timeout - you don't want to be draining power while trying to charge the tab.
bftb0 said:
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Click to expand...
Click to collapse
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
frap129 said:
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
Click to expand...
Click to collapse
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
bftb0 said:
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
Click to expand...
Click to collapse
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
frap129 said:
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
Click to expand...
Click to collapse
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Odin is Samsung only
Sent from my Galaxy Nexus
You can hold the power button for 10 seconds and wait till you see the Google logo. Then release and hold it 10 seconds again, when the screen turns off hold the volume down button and wait for it till it automatically boots again. You'll enter bootloader mode. Download wugfresh' nexus root toolkit and install it. When the program is loaded there is a flash stock option on the right side of the program. Select the soft brick / boot loop option under the flash button. While in boot loader mode connect your nexus and press the flash button.
This is all I know!
Sent from my Nexus 7 using xda premium
NEXUS 7 Bricked - NO OS - tried everything but...
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
USB debugging doesn't mean **** when you are in a custom recovery. It has adb already. Your problem is your computer. Fix your computer by following one of the bajillion threads and posts about the nexus 7 drivers issues.
Installing drivers does not need android to be booted.
Your best bet is to put it in fast boot mode and follow Google's own instructions to flash it back to stock.
Sent from my Galaxy Nexus
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
I must admit I'm a little 'hazy' myself when it comes to ADB related issues... I've never had much cause to use ADB. (Think I've used 'adb pull' on a couple of occasions). And I've never been in the invidious position of not having a bootable Android OS on my Nexus 7 either - which does seems to happen a quite lot with TWRP users, less so with CWM users.
Anyway... just had a tinker... and you could try the following workaround... this seemed to work to for me.
----------------------
Locate the folder on your PC where you keep your FASTBOOT and ADB .exe files...
Copy whatever ROM .zip you want into this folder.
The following example uses SmoothROM-v5.0.zip ... There is nothing to stop you from renaming this to something shorter, for ease of typing later... so, in my case, just smooth.zip.
Boot your Nexus 7 into the BOOTLOADER (Vol down [hold] + Power button), and then into RECOVERY (TWRP) and hook it up your PC.
Open a command prompt window on the aforementioned folder... and type...
Code:
adb devices
...which should yield something like the following...
Code:
List of devices attached
012345679ABCDEF recovery
(If you don't see a serial number... then you definitely have a driver problem...)
Otherwise, it's just...
Code:
adb push smooth.zip /sdcard
Or whatever ROM you wish to 'push' to the emulated SD card.
This will likely take a fair few minutes for a 300Mb+ size file (typically the size of your average ROM)... on my Windows XP box it took 4 minutes (1328 KB/s, 32565894 bytes in 239.486s) to copy over. And there are no 'progress gauges' of any kind, either... So season your patience a liitle. You can always pull up another command prompt window and type adb devices again to ensure you still have an ongoing ADB connection.
Once copied over, and still in TWRP, you can just flash it.
Good luck.
Rgrds,
Ged.
Still nothing on mine. im just about to give up and wait to see if google releases the N7 second generation at the i/o
If You familiar with Linux, You can try to understand the logic of
changing the modes.
You need to run udevadm monitor in one terminal. Then press some
combinations of key/s and look for changes with usb-devices.
The better, if You run wireshark and sniff USB interface with your device.
Put attachment here, with a comments what was pressed.
since it seems to be a hardware problem, not software, im just going to send it to asus and see what they can do.
Hello,
I've had my Nexus 4 for about six months now and have never had any issues with it until two weeks ago. I've been using TWRP and multirom on it to try out Firefox OS, CM11, LuneOS, Sailfish OS, and Ubuntu Touch (running with 4.2.2 as base per requirements for Sailfish and LuneOS). I installed the latest LuneOS build about two weeks ago which involves installing via MultiROM and then switching it to be the primary ROM for the device (temporarily moving Android 4.2.2 to a secondary ROM going back into recovery and reversing it when I'm ready to use my other OS's again).
Anyways I started up LuneOS as usual with no issues and messed around with a bit before deciding to reboot (still into LuneOS not recovery) for whatever reason but the phone never did turn back on. I set the phone down for a few minutes not paying attention so I'm not sure if anything (visibly) unusual happened.
I'm not able to get it to go into recovery mode no matter how long I hold volume down + power (or any other combination of the volume/power buttons) and Nexus Root Toolkit does not detect any ADB devices. I've managed to get it to show up in Device Manager twice under Other Devices as "Jellybean on Mako" but still can't do anything with it.
When I plug the device in I can see the backlight turn on but nothing ever displays on the screen. I've been trying for two weeks now and have tried charging it for hours plugged up to my PC, original wall charger, QI charger, and have even taken the device apart to unplug the battery for a while which didn't help either.
Any input would be appreciated as I'm pretty discouraged at this point.
Does phone respond to fastboot commands?
audit13 said:
Does phone respond to fastboot commands?
Click to expand...
Click to collapse
It doesn't appear so. In Nexus Root Toolkit I get the error message that FASTBOOT device was not found.
Just to update I bought a new battery and replaced it and still have the exact same issue with the device so I can safely rule that out. Does anyone else have any suggestions please?
Maybe some info in this thread will be of use: http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
You said it finds "Jellybean on mako" did you try doing adb reboot recovery or adb reboot fastboot? Might work if you had debugging on. Also what shows up on the screen when you shut the device down and attempt to go to bootloader?
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
phnxnvrdies said:
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
Click to expand...
Click to collapse
UPDATE STATUS - If I plug it into the pc without the battery i get a windows driver install box that says "Installing APX..." does this indicate the NVFlash is corrupt or is there a way to get out of apx mode.. im not familiar with that mode .. only ADB & fastboot..
Update 2 - After reading lots, I've come to conclude its hardbricked, must have had an error in memory or whatever.. its stuck in APX mode so im going to replace the whole MB with a working 32GB [model me370t] & start over .. maybe ill not install so many ROMS via multirom.. just a few - THREAD BE CLOSED - I'm done here, good luck to anyone with similar results
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
GedBlake said:
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
Click to expand...
Click to collapse
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Gabu1405 said:
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Click to expand...
Click to collapse
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
GedBlake said:
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
Click to expand...
Click to collapse
Well, charged my device for a whole day, and now I tried to do the button combinations which you sent the link, nothing happened.
I thought that my battery could be unplugged or the cable was loose or something, so I opened the tablet and it was fine.
So, I just decided to do the button combinations while plugged into my PC, and I noticed that doesn´t matter which combination I try, the tablet disconnects from the PC and instantly reconnects, but still in APX mode.
I guess it is Game Over for me, gonna recharge it again, and try again tomorrow.
Thanks again.
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Hi!
I had a Nexus 7 stuck in APX mode as well. Without the blobs saved you can't do anything. I tried a lot of thigs but nothing really helped. I ended up searching for an another N7 with a broken screen but with a working motherboard online. I was lucky and find one around $15. I swapped the boards and it was good to go.
Zsolti
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Check out my guide.