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.
Any help is appreciated! First some background:
Flashed device to stock using KK 4.4 version d80020c following steps found here http://forum.xda-developers.com/showthread.php?t=2432476. Successfully rooted using directions (and ioroot25) found here https://www.youtube.com/watch?v=HKuedInhdjU&noredirect=1.
Here's where I got into trouble...Downloaded TWRP 2.7 recovery img and flashed via Flashify. Since this step, my D800 has the exact same symptoms found on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
- No download mode (tried many times)
- No recovery (tried many times also)
- Secure booting error
- LG detected as qhsusb_bulk in device manager
- Device is recognized as 15 different drives, one of which contains a folder named image with 79 different files being .B0X files and Microsoft Access Add-in Data files
- Upon restarting, LG logo with secure booting error, then the screen goes black while your phone is still on
I've followed the steps in the thread that matches my G2's symptoms, run ubuntu 13.1 in VM, apply usb filters for my device which is then recognized as either LG Electonics Inc. QHUSB_BULK or Unknown Device 05C6:9006 when running in VM.
Upon running command ls /dev/sd* in VM Ubuntu Terminal, all that is returned is /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 which are the partitions for Ubuntu, no LG.
I've tried to download and update the Qualcomm drivers, device manager tells me that the drivers were recognized, but cannot be installed and do not pass the hash check (Note: PC is running Windows 8.1).
I've spent over 12 hours on this trying to fix this problem, researched and searched everywhere. If I could get ubuntu to recognize the device, I would be able to continue on with the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
Links for windows 8 qualcomm drivers, suggestions on how to get the device recognized in ubuntu vm, experiences from others in similar situation, or any with experience working with LG to get a repair done if I'm SOL (as in eMMC is fried) would be so helpful right now.
Thank you all!
After flashing recovery did you flash a patched kernel to boot stock kk?
Sent from my LG-D800 using Tapatalk
I had the same, also with a lot of drives etc.
Screen is black but low backlighted?
Then try with pluged USB Cabel in Phone, hold Power button until screen is realy off, then hold the Power Up Button and plug Cabel into PC.
So I got download mode after I tryed many times
I had problems a few weeks ago getting mine to go into Download mode... turned out that the cable I was using was great for charging, but sucked for everything else. Once I switched to a different cable things worked fine and I was able to load D80010c on the device.
I was running D80020c this morning (with the D80010c boot.img to have a custom recovery) and decided to do an update. Since you can't load D80020k if you have the older bootloader I went all the way back to D80010c, updated to D80010o, D80010q, D80020c and finally D80020k. I was able to root that using IOroot and have restored everything back onto my phone.
-Daryel
Thanks so much for the responses! I've tried endlessly to get the device into download mode, and tried a new cable to no avail. Any other suggestions?
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
d800 partitions are here
Still no luck
bender_007 said:
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
Click to expand...
Click to collapse
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Sneaky Elephant said:
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Click to expand...
Click to collapse
As soon as in the background of the white menu (factory reset) the secure boot appear plug it in. I'm not sure how much usb filter helps you(maybe it does) but try installing ubuntu over WUBI installer so your win remains. Or at least try ubuntu from usb stick. So you can know for sure if it's working.
Hi Sneaky E. I have the same issue you have. I'll be following your thread. If I figure anything out I'll let you know. I am also having an issue getting mine to charge now. Have you tried downgrading your TWRP?
VirtualBox Error
VirtualBox recognizes the device is plugged in, but won't allow me to push the device for use in linux. I keep getting this error message:
Failed to attach the USB device LG Electronics Inc. QHSUSB__BULK to the virtual machine Ubuntu.
USB device 'LG Electronics Inc. QHSUSB__BULK' with UUID {d8db3712-b86c-4257-a87b-275cef04e5a3} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Click to expand...
Click to collapse
I've tried all USB ports, 2.0 and 3.0. I feel like if I can get past this there should be no reason linux can't see the partitions in the phone. Please Help!!!
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
ambetdelarosa said:
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
Click to expand...
Click to collapse
What are the negatives to doing a JTAG fix?
Sneaky Elephant said:
What are the negatives to doing a JTAG fix?
Click to expand...
Click to collapse
Here is your fix.
follow exactly. LINK
ingoljosh said:
Here is your fix.
follow exactly. LINK
Click to expand...
Click to collapse
Followed steps already, still can't boot into recovery.
Sneaky Elephant said:
Followed steps already, still can't boot into recovery.
Click to expand...
Click to collapse
if your device is insured maybe report it lost and pay deductible and get a new one AND NEVER ROOT AGAIN
linux cant recognizy my lg g2 f320L
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
dr jam said:
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
Click to expand...
Click to collapse
The same with me - UP
install ur Ubuntu sing VMware....then partitions will appear.........
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
install ur Ubuntu using VMware......then ur mobile will be recognised and partitions will appear.....
Hello to All,
Yesterday I have tried to mount on my Nexus a partition that was not in use (22gb), used the terminal emulator...
After that command my Nexus wont start... anything not even the LOGO Google appear, when I connect to my PC with the USB cable he recognize only this on the device manager.
Asus transformer Prime APX interface.
Test that I have done:
Try to change baterry and the problem is the same
When I connect to the charger I dont receive any logo
Trie to boot on recovery mode fail
Change the driver in the device manager and start with Nexus root tool kit but it don't work...
Can anyone help me???
Thanks
Tiago Silva
Tsilva80 said:
Hello to All,
Yesterday I have tried to mount on my Nexus a partition that was not in use (22gb), used the terminal emulator...
After that command my Nexus wont start... anything not even the LOGO Google appear, when I connect to my PC with the USB cable he recognize only this on the device manager.
Asus transformer Prime APX interface.
Test that I have done:
Try to change baterry and the problem is the same
When I connect to the charger I dont receive any logo
Trie to boot on recovery mode fail
Change the driver in the device manager and start with Nexus root tool kit but it don't work...
Can anyone help me???
Thanks
Tiago Silva
Click to expand...
Click to collapse
Hi, Tsilva80...
I hate to be the bearer of bad news, but this has all the hallmarks of a corrupted or erased bootloader, in which case your Nexus 7 is probably irretrievably hardbricked.
The lack of the 'white-on-black' Google logo on boot; the lack of the 'white-on-black' battery charging animation when plugged into a wall socket... and the APX entry on Windows device manager, are all symptomatic of a dead, corrupted or erased bootloader.
And without a working bootloader, not only will the device not boot, but you can't even run fastboot commands in order to fastboot flash a Google factory stock image. The bootloader is critical; without it, nothing happens. It's the 'Achilles Heel' of the Nexus 7.
---
APX mode is the default state the Nexus 7 enters into in the absence of a working bootloader, with the expectation that somebody with the necessary technical skills and equipped with an nvFlash tool, will nvFlash a replacement bootloader.
Unfortunately, there is no universal nvFlash tool available for the Nexus 7.
Unless you have, at some point, previously generated unique device dependent 'wheelie blobs' using the flatline procedure (See here and here for more details on this) your only option, is to have the devices motherboard replaced.
Even with the 'wheelie blobs', I haven't read anywhere of anybody successfully using them to revive a hardbricked Nexus 7.
---
Your only glimmer of hope, is that you may have inadvertantly ('deliberately') entered APX mode, by mistake... by pressing VOL-UP (holding) + POWER ON when the device was powered down.
If this is the case, then you **might** be able to break out of APX mode by LONG PRESSING the POWER BUTTON for 15-20 seconds... But this will only work if there is a working bootloader for the device to boot into. If it's erased or somehow corrupted, the Nexus 7 is hardbricked.
See this post, for a list of Nexus 7 button combinations, and more details about entering and exiting APX mode.
---
I really hope you can get your Nexus 7 working again, but based on your post, I can't say I'm optimistic. I suspect you will need a new motherboard.
For what's it's worth... Good Luck.
Rgrds,
Ged.
Hello, I am a new member and I'm having a hard time trying to fix my phone.
Currently, I can't go into any mode. I have neither fastboot or download mode.
I also can't get into my twrp through factory reset since it tries to reboot my phone.
However, whenever it tries to reboot, I get error: Boot certification verify and the screen goes dark.
I have tried to solve it by following this thread:
http://forum.xda-developers.com/showthread.php?t=2582142 but nothing has worked so far.
Can anyone please help me?
rawtomato said:
I also can't get into my twrp through factory reset since it tries to reboot my phone.
Click to expand...
Click to collapse
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
iowabowtech said:
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
Click to expand...
Click to collapse
I get there and selecting reset reboots the phone. However, an error about phone ceritication verify pops up
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
iowabowtech said:
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
Click to expand...
Click to collapse
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
rawtomato said:
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
Click to expand...
Click to collapse
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
iowabowtech said:
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
Click to expand...
Click to collapse
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Be very careful
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
iowabowtech said:
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Click to expand...
Click to collapse
It seems like i have messed my phone up really badly.. Thank you for the ideas but yes, I will continue to look for more options for now
Edit: I have never tried the first method you showed me before but I have tried the second and the third method and did not work. Would I be able to fix it if I take it to a shop?
virginwidow said:
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
Click to expand...
Click to collapse
Thanks for your reply but I absolutely have no idea how to get into the dd / phone part using linux. I'll continue to look for more threads close to my problem but I have no clue as of yet.
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.