Database Users

[Q] Did I KILL My Nexus 7 2012?

Hi Guys,
I was hoping to upgrade to Paranoid Android today but didn't get so far.
I went into Clockwork Recovery and did a Factory Reset. I then proceeded to wipe the Dalvik Cache and other Cache. Then after that I set it to format the SD Card.
I noticed that while in recovery I couldn't get my SD card to mount in Windows 7. I booted up the Nexus 7 toolkit and chose a sideloading option for the Paranoid Android zips while the Nexus 7 was in CM Mod. I was staring at a frozen screen so I held the power button and down volume for ten seconds.
After a while it got to the point where the Nexus 7 would not boot. It would not show me the Google logo and when plugged in the Battery Recharging graphic did not come on.
After a while I somehow got it to boot up again. I went back into Recovery Mode and tried the sideloading again. I was still looking at a frozen screen so I did the ten second power button reset.
Now it's bricked. There's no Google logo, no option to go into Bootloader or Recovery. There is no graphic indicating that the Nexus 7 is recharging.
It's been hours. I even went so far to open up the back cover, unplug the battery, and then plug it back in. There's nothing.
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
I thought out of everything I did that unplugging and replugging the battery would have reset the system and allowed me back into Recovery Mode.
Not so....
So, I have to ask: Did I kill my Nexus 7?
Is there any way to bring this thing back? I figure I will leave it charging in a 2A Charger overnight. I need some feedback though because I did some research and have seen that a lot of people are had this problem.

ev1lchris said:
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
Click to expand...
Click to collapse
Did you mean ADB drivers? I can't find anything on ADX. I would try uninstalling and reinstalling the drivers and toolkit as a quick step, I'd also consider other toolkits as a possible solution.

I think he meant APX. APX=done. Only solution: take out phone and call ASUS for an RMA number.

I refuse to believe my Nexus 7 is done.

ev1lchris said:
I refuse to believe my Nexus 7 is done.
Click to expand...
Click to collapse
If you haven't already, do a search on APX mode/drivers. You should find that the only way to recover once in APX is if you have made a copy of a file prior to bricking. That file contains a device-specific number that is required to perform the recovery. Additionally, even with that number the process is quite daunting. Good luck should you soldier on.
PS- You should also know that while in APX mode your device is "on" & the battery is discharging to a non-rechargeable state.

Yup, had the same thing happened to my N7 today after it crashed and could not recover to save it. Plugged it on my laptop and it recognized it as an apx device something. I already called asus for rma and I'll be shipping out mine on monday.

There is hope.
Sent from my ZTE V970 using xda app-developers app

First thing I'm going to do once I get my N7 back, make an nvflash blob http://forum.xda-developers.com/showthread.php?t=2455927

I don't think I ever got the chance to flash anything new onto my Nexus 7. I just did a factory reset and formatted the SD card.

It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!

ev1lchris said:
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
Click to expand...
Click to collapse
You returned from APX? This is a first; what did you do? Are you sure you were in APX?

Lucky! curious also on how you manage to get out of apx mode!

thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!

OffcerClancy said:
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Click to expand...
Click to collapse
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
ev1lchris said:
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
Click to expand...
Click to collapse
I think there's a bit of misunderstanding here about APX mode...
To put it simply... APX doesn't necessarily signify hardbrick.
APX is required for nvFlash operations, such as nvFlashing a new bootloader, should the original become erased/corrupted. Indeed, if that where to happen, the Nexus 7 would automatically default to APX mode... and await for somebody to perform such an nvFlash operation.
Currently the only way of performing nvFlash operations on the Nexus 7 is if the user had run the flatline procedure BEFORE damage had occurred to the bootloader. This procedure generates what are called 'wheelie blobs' on a per-device basis, and are unique to each Nexus 7... ie., they are not transferable. They are required to resurrect a dead Nexus 7 with a corrupted, damaged or erased bootloader.
However, you can electively get into APX mode, even with a functional bootloader. Indeed, the latter part of the flatline procedure requires it. How to do this is detailed here.
So, just because your Nexus 7 is in APX mode doesn't necessarily mean it's hardbricked or the bootloader is damaged/corrupted or erased... though, more often than not, that is exactly what it does mean.
Providing you haven't knowingly done anything that might affect the bootloader, pressing and holding the POWER BUTTON for a good 30 seconds or more, might just be sufficient to kick-start a seemingly dead Nexus 7 out of APX mode. I can't guarantee it will work of course... but it's got to be worth a shot.
And it seems to have worked for @ev1lchris.
Rgrds,
Ged.

Sound like by dumb luck he stumbled in and fell assbackwards out of APX mode.

I brick my N7 when flashing 4.3 vía fastboot, ASUS replace the motherboard and its all good now
Enviado desde mi HTC One mediante Tapatalk

After months of use it is non responsive and in APX mode again. However, I have to highly suspect that the battery is playing a role here.
I have a rubber band constantly pressing the power button.
Let you guys know what happens.

I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?

ChiquiNL said:
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
Click to expand...
Click to collapse
If you're still under warranty and you have tried all you can to revive the thing then yes you should call Asus and do a RMA.

Here's an update on my situation...
I installed a battery I bought off of eBay and.... nothing. Still dead.
I'm charging it and I'm going to continue to have the rubber band wrapped around the power button but I think it's pretty much dead.
Such an awesome tablet that I used and depended on every day.
I bought a refurb N7 2013 but I really would have liked to save my N7 and continued using it.

LED Blinking. Phone not turning on.

Hello.
A few moments back, my phone died. Now, the LED light is blinking constantly and there is nothing on the screen.
When I connect my phone to my laptop, I hear the normal notification sound on connecting USB (on my laptop). Holding the power button probably turns off the phone because I can hear the notification sound on my laptop again but there is no change on the screen.
I can't open the recovery. I can't enter the bootloader mode.
If it helps, I was changing my ROM.
1. Updated to 14-8 (latest update, stock)
2. Format data,cache,dalvik,system
2. Installed Invicta
3. Format data,cache,dalvik,system
4. Reinstalled Nougat (fastboot) -> 14-4 (stock recovery)
And that was it. Rebooted and stuck.
Getting into bootloader mode will be more than enough.
Any help is greatly appreciated. If any information is required, I'll gladly provide it.
Edit - On connection, the phone shows up as this device in the Device Manager - RELINK HS-USB QDLoade 9008 (COM4)

@baunthiyal
Many ones have reported similar problem but while using any custom ROM..
And solution was " keep power button pressed for 2 minutes.."
You have flashed Stock and no one has reported about that on stock.. see if 2 minutes works or no..

____Mdd said:
@baunthiyal
Many ones have reported similar problem but while using any custom ROM..
And solution was " keep power button pressed for 2 minutes.."
You have flashed Stock and no one has reported about that on stock.. see if 2 minutes works or no..
Click to expand...
Click to collapse
Thank you @____Mdd
I already tried that. It doesn't seem to help. All I get are disconnect/reconnect sounds from my laptop (the phone is connected to my laptop).

baunthiyal said:
Thank you @____Mdd
I already tried that. It doesn't seem to help. All I get are disconnect/reconnect sounds from my laptop (the phone is connected to my laptop).
Click to expand...
Click to collapse
Actually i don't know anything about blank-flash, so i will not suggest to do that thing.. (hope more experienced person will look at this problem)
(Also there is one another thread for hard brick device, find in Q/A threads)
But i can suggest you to check your display if it's not an hardware issue (as you have only flashed ROMs, and they cannot do anything to hardware, but nothing wrong in checking)
- hold power and vol down for 10 second (reboot into bootloader)
- check command "fastboot devices"

baunthiyal said:
Thank you @____Mdd
I already tried that. It doesn't seem to help. All I get are disconnect/reconnect sounds from my laptop (the phone is connected to my laptop).
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

____Mdd said:
Actually i don't know anything about blank-flash, so i will not suggest to do that thing.. (hope more experienced person will look at this problem)
(Also there is one another thread for hard brick device, find in Q/A threads)
But i can suggest you to check your display if it's not an hardware issue (as you have only flashed ROMs, and they cannot do anything to hardware, but nothing wrong in checking)
- hold power and vol down for 10 second (reboot into bootloader)
- check command "fastboot devices"
Click to expand...
Click to collapse
I am currently trying the blankflash method. As for the bootloader mode, I can't access it. If I could, there wouldn't have been a problem.

HueyT said:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Click to expand...
Click to collapse
Thank you for the link, @HueyT
I am checking out that method.

This method might also be worth looking into: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
However, we currently don't have access to the NPJS25.93-14-8 GPT and/or bootloader images, so I don't know if it'll work. I also am not sure if this will work with the NPJS25.93-14-4 GPT/bootloader images as your device has newer images.
Just to clarify, when you re-flashed Nougat 93-14-4 (the March update), did you do a full flash (including GPT/bootloader) or just the recovery or system?

echo92 said:
This method might also be worth looking into: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
However, we currently don't have access to the NPJS25.93-14-8 GPT and/or bootloader images, so I don't know if it'll work. I also am not sure if this will work with the NPJS25.93-14-4 GPT/bootloader images as your device has newer images.
Just to clarify, when you re-flashed Nougat 93-14-4 (the March update), did you do a full flash (including GPT/bootloader) or just the recovery or system?
Click to expand...
Click to collapse
Hello @echo92
I flashed the OTA from this link on XDA - https://forum.xda-developers.com/moto-g4-plus/how-to/ota-update-june-security-patch-started-t3632792
I will look into the link you provided. Thank you.
Edit - Yes. I checked it. I am doing the blankflash method but can't work through it.
I receive this error - https://forum.xda-developers.com/showpost.php?p=72938736&postcount=49

baunthiyal said:
Hello @echo92
I flashed the OTA from this link on XDA - https://forum.xda-developers.com/moto-g4-plus/how-to/ota-update-june-security-patch-started-t3632792
I will look into the link you provided. Thank you.
Click to expand...
Click to collapse
Ah, my bad - I was just seeking clarification of point 4 in your original post '4. Reinstalled Nougat (fastboot) -> 14-4 (stock recovery)'
I was just asking if you did a full flash of the Nougat 14-4 update via fastboot, after you flashed Invicta?

echo92 said:
Ah, my bad - I was just seeking clarification of point 4 in your original post '4. Reinstalled Nougat (fastboot) -> 14-4 (stock recovery)'
I was just asking if you did a full flash of the Nougat 14-4 update via fastboot, after you flashed Invicta?
Click to expand...
Click to collapse
Yes, it was a full flash. Without locking the bootloader, of course.
PS - Please check my previous comment for the edit and give your advice as to what I am doing wrong.

baunthiyal said:
Yes, it was a full flash. Without locking the bootloader, of course.
PS - Please check my previous comment for the edit and give your advice as to what I am doing wrong.
Click to expand...
Click to collapse
Hmm, i honestly do not have any experience as to unbricking a device, only observing what others have done. Was the full flash done with flashing the GPT and bootloader (so downgrading the GPT and bootloader from the NPJS25.93-14-8 build you had)?
How many times have you tried the blank-flash? In the opening post of that thread you reported in, the opening poster mentioned having tried 5-6 times to get the device to communicate properly. Seems the process is a little fiddly too:
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
Click to expand...
Click to collapse
Credit to: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

echo92 said:
Was the full flash done with flashing the GPT and bootloader (so downgrading the GPT and bootloader from the NPJS25.93-14-8 build you had)?
How many times have you tried the blank-flash? In the opening post of that thread you reported in, the opening poster mentioned having tried 5-6 times to get the device to communicate properly. Seems the process is a little fiddly too:
Click to expand...
Click to collapse
1. Yes, I flashed the GPT and bootloader files as well. The files were for 93-14. This is something I have done before. (to return to stock, flash 93-14 images using fastboot and then upgrading to 93-14-4). Only difference, this time there was another upgrade (93-14-8).
2. I've tried the blankflash procedure a few times. I receive the following error (attachment).

baunthiyal said:
1. Yes, I flashed the GPT and bootloader files as well. The files were for 93-14. This is something I have done before. (to return to stock, flash 93-14 images using fastboot and then upgrading to 93-14-4). Only difference, this time there was another upgrade (93-14-8).
2. I've tried the blankflash procedure a few times. I receive the following error (attachment).
Click to expand...
Click to collapse
Yeah, that's what I was wondering, whether the 93-14-8 update makes it tricky to downgrade (unless you don't downgrade the GPT/bootloader).
What does the qboot.log.txt say (as mentioned in the output)?

QBoot Log
Find the logs below.
[ 0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.003] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 33258865 (0x1fb7d71)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = singleimage.pkg.xml
[ 0.009] Loading programmer
[ 0.009] ...filename = programmer.mbn
[ 0.010] Sending programmer
[ 0.225] Handling things over to programmer
[ 0.225] Identifying CPU version
[ 0.227] Waiting for firehose to get ready
[ 60.304] Waiting for firehose to get ready
[120.384] ...MSM8952 unknown
[120.384] Determining target secure state
[120.386] Waiting for firehose to get ready
[180.470] ...secure = no
[180.479] Flashing GPT...
[180.479] Flashing partition:0 with gpt_main0.bin
[180.480] Initializing storage
[180.483] Waiting for firehose to get ready
[240.563] Configuring device...
[240.565] Waiting for firehose to get ready
[300.643] Waiting for firehose to get ready
[360.721] Waiting for firehose to get ready
[420.800] Waiting for firehose to get ready
[480.876] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[480.877] Check qboot_log.txt for more details
[480.878] Total time: 480.879s
[480.879]
[480.879] qboot version 3.40
[480.879]
[480.879] DEVICE {
[480.879] name = "\\.\COM5",
[480.879] flags = "0x64",
[480.879] addr = "0x61FE5C",
[480.879] sahara.current_mode = "0",
[480.879] api.buffer = "0x12D0020",
[480.879] cpu.serial = "33258865",
[480.879] cpu.id = "2418",
[480.879] cpu.sv_sbl = "0",
[480.879] cpu.name = "MSM8952",
[480.879] storage.type = "eMMC",
[480.879] sahara.programmer = "programmer.mbn",
[480.879] module.firehose = "0xF88F18",
[480.879] cpu.ver = "0",
[480.879] cpu.vername = "unknown",
[480.879] api.bnr = "0xE16C10",
[480.879] }
[480.879]
[480.879]
[480.879] Backup & Restore {
[480.879] num_entries = 0,
[480.879] restoring = "false",
[480.879] backup_error = "not started",
[480.879] restore_error = "not started",
[480.879] }
[480.879]

baunthiyal said:
Yes, it was a full flash. Without locking the bootloader, of course.
PS - Please check my previous comment for the edit and give your advice as to what I am doing wrong.
Click to expand...
Click to collapse
You may want to ask the O.P. in the "unbrick" thread as he has more know how than me on unbricking.
---------- Post added at 01:28 PM ---------- Previous post was at 01:24 PM ----------
baunthiyal said:
Hello.
A few moments back, my phone died. Now, the LED light is blinking constantly and there is nothing on the screen.
When I connect my phone to my laptop, I hear the normal notification sound on connecting USB (on my laptop). Holding the power button probably turns off the phone because I can hear the notification sound on my laptop again but there is no change on the screen.
I can't open the recovery. I can't enter the bootloader mode.
If it helps, I was changing my ROM.
1. Updated to 14-8 (latest update, stock)
2. Format data,cache,dalvik,system
2. Installed Invicta
3. Format data,cache,dalvik,system
4. Reinstalled Nougat (fastboot) -> 14-4 (stock recovery)
And that was it. Rebooted and stuck.
Getting into bootloader mode will be more than enough.
Any help is greatly appreciated. If any information is required, I'll gladly provide it.
Edit - On connection, the phone shows up as this device in the Device Manager - RELINK HS-USB QDLoade 9008 (COM4)
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 . This thread is for LG G2 but may have some insight on unbricking QDLoade 9008

https://forum.xda-developers.com/moto-g4-plus/help/help-moto-g4-plus-hard-bricked-t3454528/page6
See latest post.

bullfinch110 said:
https://forum.xda-developers.com/moto-g4-plus/help/help-moto-g4-plus-hard-bricked-t3454528/page6
See latest post.
Click to expand...
Click to collapse
Hello @bullfinch110
Thank you for your reply.
The latest post says to wait and turn it on.
The other post says to flash the blankflash and go on from there. Therein lies the problem. I cannot successfully boot into the bootloader to try the fastboot commands.

HueyT said:
You may want to ask the O.P. in the "unbrick" thread as he has more know how than me on unbricking.
---------- Post added at 01:28 PM ---------- Previous post was at 01:24 PM ----------
https://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 . This thread is for LG G2 but may have some insight on unbricking QDLoade 9008
Click to expand...
Click to collapse
Hello @HueyT
Thank you for your help. Sadly, this is not for our device. It is very specifically for LG.

baunthiyal said:
Hello @HueyT
Thank you for your help. Sadly, this is not for our device. It is very specifically for LG.
Click to expand...
Click to collapse
Unplug from USB, hold POWER and VOL.DOWN button for at least 2 min (use stopwatch) and see if you can get into bootloader mode

Moto G4 plus Blank flash error --device not detecting

I was upgrading to Nougat from Marshmallow, because of low battery phone switched off while updating. Now phone LED is blinking when I am charging and I have almost done all the things which are to be done. The only response I got is the LED light stop blinking and nothing happens then. Help me please, I have already charged it for 2-3 hours but still, it is not turning on.
I tried for blank flash but it showing the error msg. [Error opening device].
[ 0.000] Opening device: \\.\COM3
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.000]

1) Did you have stock Nougat previously on this device?
2)Which blankflash are you using? Is it the one from this thread? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 I see you've already posted in that thread.
3)You may have to try the blankflash a few times for it to connect. Verify that you're using the original Motorola cable or a high quality data cable and that your device is recognised by your computer (even if it's seen as Qualcomm HS-USB 9008 or similar).

moto g7 impatience and a bricked phone?

Alright. I am taking full responsibility for the stupid things I have done in the impatience of a Sunday afternoon, so I'm ready to accept that I just bricked my only phone.
So I decided that I wanted to root my phone, so without any previous experience or understandings of the systems, twrp and Magdisk.
My issues started when I tried to unlock the bootloader, and upon every single boot, it would briefly display that I had a "badkey", but I ignored that because it was still booting.
I then installed minimal ADB and fastboot and first flashed twrp, and then magdisk. Thats when the first issue started.
my phone was now stuck in a bootloop, saying something similar to my "badkey" error message, but in place of "badkey" was just "n/a"
This was bad. Really bad.
Next, I tried to fix it using my limited rushed knowledge, so I tried to flash a default moto g7 rom on to the phone. This was also a VERY big mistake.
This flash landed me into a phone that now displays absolutely nothing, and the only proof that I have that any of it even works is that, when plugged into my PC, it shows up on my COM4 port as Qualcomm HS-USB QDLoader 9008 (COM4).
Now here I am, at the mercy of the universe. If anyone has an idea or a similar experience or solution, please go ahead and share. If not, let this be a precautionary tale: Never rush; Never be impatient.

Xalllle said:
Alright. I am taking full responsibility for the stupid things I have done in the impatience of a Sunday afternoon, so I'm ready to accept that I just bricked my only phone.
So I decided that I wanted to root my phone, so without any previous experience or understandings of the systems, twrp and Magdisk.
My issues started when I tried to unlock the bootloader, and upon every single boot, it would briefly display that I had a "badkey", but I ignored that because it was still booting.
I then installed minimal ADB and fastboot and first flashed twrp, and then magdisk. Thats when the first issue started.
my phone was now stuck in a bootloop, saying something similar to my "badkey" error message, but in place of "badkey" was just "n/a"
This was bad. Really bad.
Next, I tried to fix it using my limited rushed knowledge, so I tried to flash a default moto g7 rom on to the phone. This was also a VERY big mistake.
This flash landed me into a phone that now displays absolutely nothing, and the only proof that I have that any of it even works is that, when plugged into my PC, it shows up on my COM4 port as Qualcomm HS-USB QDLoader 9008 (COM4).
Now here I am, at the mercy of the universe. If anyone has an idea or a similar experience or solution, please go ahead and share. If not, let this be a precautionary tale: Never rush; Never be impatient.
Click to expand...
Click to collapse
The bad key and n/a are normal for moto.
The Qualcomm deal is
Emergency download mode (edl)
You need to find a river blankflash
A bunch of threads on this.
There's one here
https://mirrors.lolinet.com/firmware/moto/river/blankflash/
It may work...
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
The bad key and n/a are normal for moto.
The Qualcomm deal is
Emergency download mode (edl)
You need to find a river blankflash
A bunch of threads on this.
There's one here
It may work...
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I tried lauching blank-flash, and im getting this in response:
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.010] Total time: 4.011s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Can I get past this?

Xalllle said:
I tried lauching blank-flash, and im getting this in response:
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.010] Total time: 4.011s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Can I get past this?
Click to expand...
Click to collapse
Nevermind! I got it working by A. Trying it a billion times and B. trying it on another pc. For some reason, that made it work.

OP5 : black screen when lineage logo display + white led

Hi ! my Oneplus 5 has slightly taken rainwater in my pocket. The phone wouldn't start up again.
I changed the battery. The phone reboots, the screen displays "1+ Powered by Android", then the screen starts to display lineage Logo and turns black and a white LED lights up.
I can't access the recovery mode by pressing power button + volume down.
Would you have an idea that would allow me to fix it? (I wanted to unbrick the phone but I can't enter to recovery ...)
thank you for your help

Use an EDL flasher (commonly known as unbrick tool). You can find it here on XDA

Pierre02 said:
Use an EDL flasher (commonly known as unbrick tool). You can find it here on XDA
Click to expand...
Click to collapse
Thanks for your answer. I wanted to follow this guide (https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706) but MSM Download Tool can't see my OnePlus (I followed the instructions but my phone doesn't appear under COMs and Ports).
For your information, I can get into the fastboot. With linux, the phone is well recognized in fastboot (it is also recognized with the tool TOOL_ALL_IN_ONE_2.0.1.3).
Code:
I tried this :
Sending 'recovery' (33689 KB) OKAY [ 1.320s]
Writing 'recovery' OKAY [ 0.317s]
Finished. Total time: 1.721s
Sending 'boot.img' (33689 KB) OKAY [ 1.289s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
fastboot: error: Command failed

tifriis said:
Thanks for your answer. I wanted to follow this guide (https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706) but MSM Download Tool can't see my OnePlus (I followed the instructions but my phone doesn't appear under COMs and Ports).
For your information, I can get into the fastboot. With linux, the phone is well recognized in fastboot (it is also recognized with the tool TOOL_ALL_IN_ONE_2.0.1.3).
Click to expand...
Click to collapse
You have to install drivers in special mode aka non signed driver install allowed mode in windows 10.
It's num 7 in the list of advance system startup.
For some reason i didn't had to do anything as my laptop already had everything somehow, i just open tool and flashed to 7.1 to test my phone. Now back to 10.
Only think I did before was installed htc 10 drivers to unlock and have custom rom on it.

atifsh said:
You have to install drivers in special mode aka non signed driver install allowed mode in windows 10.
Click to expand...
Click to collapse
Thanks but I did it (I followed this link : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ and I run "bcdedit /set testsigning on" then I restarted).
Maybe I have to uninstall some drivers before because my phone doesn't appear in the category " Ports (COM & LPT) ?
Here my screen after booting : https://cncloud.zaclys.com/index.php/s/bqMF3cDzMScjzgd
Thanks for your help

Hi ! I think I managed to install the driver (I had to remove old drivers).
Now MsmDownloadTool gives me this state :
Code:
Index : 1
Com : COM3
Status of Connection : Connected
SN :
Status of Communication : Param preprocessing
I'm stuck in "Param preprocessing". Phone have green LED. Any ideas ?
Thanks to help me to save my phone

For infomation, I succeed to use MSM Download Too. I was sotck in "Param preprocessing" because my battery was too low.
However, when my OP5 reboot, it displays the 1+ logo then get stuck with the red point and white circle, then reboot.
Any ideas ?

tifriis said:
For infomation, I succeed to use MSM Download Too. I was sotck in "Param preprocessing" because my battery was too low.
However, when my OP5 reboot, it displays the 1+ logo then get stuck with the red point and white circle, then reboot.
Any ideas ?
Click to expand...
Click to collapse
This is probably an hardware fault

Thanks for your support. Do you think it's the motherboard ?
Do you know if I can buy another one ?
Thanks for all, I apprieciate !