Database Users

[Q] Really Bricked?

I had an Asylum Custom Rom installed.
I also had TWRP as the recovery installed.
I decided to try the new COLOR ROM public beta that I got from the OPPO forums.
I went into TWRP recovery, did a full wipe and then proceeded to install the new COLOR ROM.
When I rebooted, the phone never turned on again.
Now I cannot get to fastboot, recovery, or turn on the phone at all.
I browsed through many forums and tried
1. Charging phone for 5 hours (no led light when plugged in) -> nothing
2. Holding Power button for 30 secs, (5 times to try a hard reset) -> nothing
3. Holding Down button for 10 secs -> nothing
4. Power and up volume -> nothing
5. Power and down volume -> nothing
6. Plugged into computer USB and tried all button combos -> nothing
Is my phone really bricked now?

I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?

killerskincanoe said:
I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?
Click to expand...
Click to collapse
Nothing. no response whatsoever. I've worked with many different phones before starting with the Nexus One and I've always been able to get out of a potentially bad situation because I could at least always get to fastboot or recovery, but in this case, nothing. It really is like working with a brick, hence the term "brick". Now i can really understand the meaning of the term.

such a bummer. it certainly makes me think twice about trying other ROMS now jeez

update
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.

dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
good to hear !!
I couldnt really believe that flashing a rom using recovery affects fastboot let alone button combos/charging...
btw what were the costs of replacing the battery ? or was it free of charge under warranty...

dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
Glad to hear it turned out that way. Really strange situation.

Oualcomm HS-USB Diagnostics 9008
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.

olezhek1975 said:
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.
Click to expand...
Click to collapse
I suggest you to ask addel in oppo forum, she can help you just pm her and tell your problem, because she has an app like odin in samsung to totally flash new rom inage from pc like odin did. But its not officially released by oppo and its hard to find, so i suggest you to contact her
Sent from my GT-I9205 using XDA Free mobile app

[Q] [HELP] Hard Brick Nexus 7

Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<

EverAngelOn said:
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
Click to expand...
Click to collapse
Can you get into the bootloader still?

I can't
b3ltazar said:
Can you get into the bootloader still?
Click to expand...
Click to collapse
No, I can't. The screen is completely black.

Have you tried any of the suggestions in the thread you linked in the OP?

EverAngelOn said:
No, I can't. The screen is completely black.
Click to expand...
Click to collapse
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures

Wugs tool kit
First when you plug it in hold all three power buttons
Second
I also have used the tool kit it gets stuck all the time on the flashing system. I think its a time out error because of the complexity of extracting the image and flahing the image with out a retry or check command. Here is a fix that i have figured out. When in Wugs tool kit download the Os Version you want on your device locate the folder with the downloaded image and extract it using 7 zip. once extracted flash the remaing .img files seperatly under andvance setting menu select flash system then user data it should boot right up. if you forgot what version you flashed previously flash all img files boot bootloader system user etc. if you still have problems let me know. i can give you my email.
Click thanks if i helped

b3ltazar said:
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Click to expand...
Click to collapse
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.

EverAngelOn said:
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
Click to expand...
Click to collapse
Unfortunately it sounds like you erased your bootloader and nvflash can do nothing for you unless you used the unbrickable mod before u f'ed up your tablet. Try sending it to asus for Warranty tell em you installed the ota update and it wouldn't boot up afterwards. I have read many threads about this issue with nobody being able to recover there tablet. Asus does have global warranty

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.

Ouh....DFU? I think this thing is totally bricked.

I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?

Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !

raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.

Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.

stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!

Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....

stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!

Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable

Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!

Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...

twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.

SM-950F Hard bricked, JTAG?

Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?

S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me

Thanks, I'll give it a shot

ok let me know then

Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/

Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30

A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??

Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?

Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.

Nexus 7 2012 hard bricked (can't boot)

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.