Develop Bugs

Hardbrick of N7 and hope for help

Hey there,
unfortunately my Nexus 7 2013 Wi-Fi (flo), which was rooted and ran on
Stock Android 4.4.2 and TWRP, suddenly stopped working.
I was experiencing some lags and decided to reboot it, but it never
powered back on. I didn't modify any system files.
I'm unable to enter recovery or download mode, but it seems that it is
now in QDL mode:
lsusb:
Bus 002 Device 017: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL
mode)
dmesg:
usb 2-4: new high-speed USB device number 15 using ehci_hcd
usb 2-4: New USB device found, idVendor=05c6, idProduct=9008
usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-4: Product: QHSUSB_DLOAD
usb 2-4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-4:1.0: Qualcomm USB modem converter detected
usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0
I hope someone is going to be able to help me.

braxas said:
Hey there,
unfortunately my Nexus 7 2013 Wi-Fi (flo), which was rooted and ran on
Stock Android 4.4.2 and TWRP, suddenly stopped working.
I was experiencing some lags and decided to reboot it, but it never
powered back on. I didn't modify any system files.
I'm unable to enter recovery or download mode, but it seems that it is
now in QDL mode:
lsusb:
Bus 002 Device 017: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL
mode)
dmesg:
usb 2-4: new high-speed USB device number 15 using ehci_hcd
usb 2-4: New USB device found, idVendor=05c6, idProduct=9008
usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-4: Product: QHSUSB_DLOAD
usb 2-4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-4:1.0: Qualcomm USB modem converter detected
usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0
I hope someone is going to be able to help me.
Click to expand...
Click to collapse
Go into TWRP and flash the nandroid you hopefully made for the situation.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
Go into TWRP and flash the nandroid you hopefully made for the situation.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
TWRP doesn' work like i said . I only can get in QDL mode

Have you tried flashing the factory image?
Sent from my Nexus 7 using Tapatalk

i cant get into recovery or downloadmode

braxas said:
i cant get into recovery or downloadmode
Click to expand...
Click to collapse
I suppose you understand or knowleadgeable of getting your phone into Bootloader mode/..
If you can, you can always Fastboot things up..
If you can't, but knew how to, that's a bit scary..

power it off than volume down and power button and after a while it'll show you the bootloader than grab the factory images and flash them onto your nexus. I foyu want more info, search around. I've posted on one of the threads on how to use factory images

https://www.youtube.com/watch?v=XbV5480M5qg
Sent from my LG-MS770 using Tapatalk

I cant use the factory images because i cant get into fastboot or anything else. The only thing i get is the QDL mode.
I cant enter recovery or fastboot or anything else

braxas said:
I cant use the factory images because i cant get into fastboot or anything else. The only thing i get is the QDL mode.
I cant enter recovery or fastboot or anything else
Click to expand...
Click to collapse
I think you're fried, man. Every time one of my devices was stuck in QHSUSB_DLOAD it had to be JTAGed. That's a definite hard brick. Sorry I don't have happier tidings.

RMA is your way. Bad unit. That's what it was
Sent from my Z30 using XDA Premium 4 mobile app

[Q] QHSUSB_DLOAD equals permanent brick?

Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..

frol_swe said:
Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..
Click to expand...
Click to collapse
Have the same problem here

frol_swe said:
Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..
Click to expand...
Click to collapse
Try the nexus 7 toolkit. There are options for recovering bricks. Good luck
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Nexus 5X] [LG H790] Bricked device with wrong bootloader

Device: Nexus 5X - LG H790 - 16GB
Hey guys!
I've spent the past... 7hr reading and trying different things but nothing seems to work.
Here's what happened: I was trying to install a custom rom which required a custom bootloader.
Everithing's good 'till I mistankenly flash the bootloader for Nexus 5 instead of 5X. And hell was unleashed... the phone got bricked as soon as I rebooted it.
It won't turn on, no matter the key combination: Power, Vol Up + Power, Vol D + Power, Both Vol + Power, the same while pluggin the USB to the computer, w/ and w/o the power key. It won't turn on.
On linux, the device is displayed as:
Code:
Bus xxx Device yyy: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
And there's only one device generated, a TTY:
Code:
/dev/ttyUSB0
I can't see partitions. If I try to dd the device through the bus:
Code:
:~# dd if=/dev/bus/usb/xxx/yyy of=img
0+1 records in
0+1 records out
50 bytes (50 B) copied, 0.000147159 s, 340 kB/s
:~# xxd img
0000000: 1201 0002 0000 0040 c605 0890 0000 0102 [email protected]
0000010: 0001 0902 2000 0101 0080 0109 0400 0002 .... ...........
0000020: ffff ff00 0705 8102 0002 0007 0501 0200 ................
0000030: 0200 ..
Here's the dmesg output:
Code:
[34405.332730] usb 2-2: new high-speed USB device number 36 using ehci-pci
[34405.465440] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34405.465444] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34405.465446] usb 2-2: Product: QHSUSB__BULK
[34405.465447] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34405.465868] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34405.466518] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
[34425.715761] usb 2-2: USB disconnect, device number 36
[34425.716093] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[34425.716129] qcserial 2-2:1.0: device disconnected
[34430.584072] usb 2-2: new high-speed USB device number 37 using ehci-pci
[34430.716784] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34430.716790] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34430.716792] usb 2-2: Product: QHSUSB__BULK
[34430.716794] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34430.717197] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34430.717303] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
If I connect to the TTY via screen, I always got the same response no matter what (I'm unable to reproduce it right now, but it was a 16 bytes [32 hex chars] fixed response, mostly zeroes).
So, I'm lost here.... the best response I found was to contact LG and ask for a replacement. So, I already sent an email to them. But the fact is, that I live in Argentina, and the phone was bought in USA through a friend, so I don't know if that option is gonna work
Every help is appreciated!
What can/should I do? I use Debian, but I've no problem using Windows 7 x64 if it's needed.

I'm on the same situation. I own a 32gb H790. I was taking random pictures with the google camera app, and suddenly it began to reboot, after that.. endless bootloop. I bought some usb c cables and tried to flash the original images (previous to that, it didn't had any mods, neither root). The flash somehow failed, and it didn't charge or boot since then, it only shows a flashing red light when connected. I couldn't enter recovery nor download mode either so the solution from the other thread didn't work for me. I guess RMA is the only solution for now.
I sent it to LG with a friend (I'm not from USA also), lets see what they say when they see it.

hackancuba said:
Device: Nexus 5X - LG H790 - 16GB
Hey guys!
I've spent the past... 7hr reading and trying different things but nothing seems to work.
Here's what happened: I was trying to install a custom rom which required a custom bootloader.
Everithing's good 'till I mistankenly flash the bootloader for Nexus 5 instead of 5X. And hell was unleashed... the phone got bricked as soon as I rebooted it.
It won't turn on, no matter the key combination: Power, Vol Up + Power, Vol D + Power, Both Vol + Power, the same while pluggin the USB to the computer, w/ and w/o the power key. It won't turn on.
On linux, the device is displayed as:
Code:
Bus xxx Device yyy: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
And there's only one device generated, a TTY:
Code:
/dev/ttyUSB0
I can't see partitions. If I try to dd the device through the bus:
Code:
:~# dd if=/dev/bus/usb/xxx/yyy of=img
0+1 records in
0+1 records out
50 bytes (50 B) copied, 0.000147159 s, 340 kB/s
:~# xxd img
0000000: 1201 0002 0000 0040 c605 0890 0000 0102 [email protected]
0000010: 0001 0902 2000 0101 0080 0109 0400 0002 .... ...........
0000020: ffff ff00 0705 8102 0002 0007 0501 0200 ................
0000030: 0200 ..
Here's the dmesg output:
Code:
[34405.332730] usb 2-2: new high-speed USB device number 36 using ehci-pci
[34405.465440] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34405.465444] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34405.465446] usb 2-2: Product: QHSUSB__BULK
[34405.465447] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34405.465868] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34405.466518] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
[34425.715761] usb 2-2: USB disconnect, device number 36
[34425.716093] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[34425.716129] qcserial 2-2:1.0: device disconnected
[34430.584072] usb 2-2: new high-speed USB device number 37 using ehci-pci
[34430.716784] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34430.716790] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34430.716792] usb 2-2: Product: QHSUSB__BULK
[34430.716794] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34430.717197] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34430.717303] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
If I connect to the TTY via screen, I always got the same response no matter what (I'm unable to reproduce it right now, but it was a 16 bytes [32 hex chars] fixed response, mostly zeroes).
So, I'm lost here.... the best response I found was to contact LG and ask for a replacement. So, I already sent an email to them. But the fact is, that I live in Argentina, and the phone was bought in USA through a friend, so I don't know if that option is gonna work
Every help is appreciated!
What can/should I do? I use Debian, but I've no problem using Windows 7 x64 if it's needed.
Click to expand...
Click to collapse
As far as I know, you are now the owner of a beautiful paperweight. Short of replacing the motherboard, there isn't anything you can do. Hopefully you get a free replacement, but I wouldn't bet on it Best of luck!

Well, thanks guys... I got a reply today from LG, here it is:
Thank you for taking time to contact LG and we really appreciate your e-mail!
I hope everything is going well with you.
You are a valued customer and we regret to hear of any problems you have encountered with our product and we’re very sorry as LG doesn’t expect this to happen. I do recognize the frustration and disappointment this has brought as I would definitely feel the same if this has happened. Please accept our apology for the trouble or inconvenience you have experienced.
In response to your concern, you are welcome to send in the device to our facility so that our licensed technicians may run a full diagnostic test on the device and perform necessary repairs to address the issue - or to have it replaced under warranty if necessary. For your convenience, we will email you prepaid label so you won't have to pay shipping the device back and forth.
I would be more than happy to process a repair authorization for you. Please keep in mind that this process may take approximately 7-9 business days from the day the device is delivered to our facility to the day that it is delivered back to you. If the phone falls under manufacture defect, phone will be repaired right away for free or will be replaced depending on technician’s assessment and diagnosis. You may have an alternate option by visiting your local service provider. Would you like to proceed with the LG service option or would you like to try with your service provider first?
Should you decide to send the unit back, please let us know. Please also include the following so that we can set a repair ticket for the unit:
- phone number
- alternate phone number (if any)
- complete physical address where the unit will be shipped back after repair
- IMEI number (or ESN or MEID number)
- copy of the receipt (bank/credit card statement, email confirmation or order number)
If you have questions or need further assistance, please let me know. You can reach us out via LG Live Chat on our website (link removed, LG's website), or on our phone support by calling our technical support hotline 800-243-0000/ 1-800-793-8896.
Thank you and we wish you all the best.
Sincerely,
Click to expand...
Click to collapse
So, I'm gonna post how it goes, for future reference.

I found someone who fixed a similar brick on another LG phone. I think you can find similar images for the 5X.
I'm not allowed to post links yet so google "hard brick to hell and back"

wbxp99 said:
I found someone who fixed a similar brick on another LG phone. I think you can find similar images for the 5X.
I'm not allowed to post links yet so google "hard brick to hell and back"
Click to expand...
Click to collapse
Yes, I read that one before
No images nor KDZ for 5X
Thanks!

hackancuba said:
Well, thanks guys... I got a reply today from LG, here it is:
So, I'm gonna post how it goes, for future reference.
Click to expand...
Click to collapse
Did you tell them how your phone was bricked? I mean, that you flashed the bootloader for Nexus 5.
I'm in a similar situation (hard brick after "trying" to install original images) and I'm running out of ideas.

I met exactly the very same problem, flashing Nexus 5's bootloader to 5X. Moreover, I'm in the similar situation with you. I live in China and bought 5x in US.
I tried many methods I can find but none of them works. Finally, I send the phone to a local LG Mobile Phone service shop. The staff said the model is never sold in China but they can try. About two weeks later, they told me that, the phone is repaired. I got it yesterday. Until now, it works well.
And yes, they did charge 600 yuan (about 91 usd) from me. Not bad. Wish you have better luck.

guillermo1996 said:
Did you tell them how your phone was bricked? I mean, that you flashed the bootloader for Nexus 5.
I'm in a similar situation (hard brick after "trying" to install original images) and I'm running out of ideas.
Click to expand...
Click to collapse
I didn't actually told them what happened
So far, they told me I need to ship the phone to US and they'll repair it. The only issue now is trying to find the buying receipt from BestBuy, since I don't have it... damn!

Try using the LG UP tool.

Fire TV 1 Bricked with Marshall London HS-USB Diagnostic 9006

My Fire TV bricked and none of the described un-bricking method works.
When connecting through USB I can see "Marshall London HS-USB Diagnostics 9006 (COM21)" port in Device Manager. I also observed that MiFlash tool recognize it as "\\?\usbstor#disk$ven_qualcomm&prod_mmc_storage&rev_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}"
I have unbricked my Mi Phone using this tool and it requires a ROM containing boot, kernel, system etc. images and other flashing scripts. Do we have similar kind of ROM available for Fire TV?

I am in the same boat.

Did you try this

{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Looks like I goofed up big time. Now I only see QHUSB_DLOAD and I am not able to see any drive on OSX or Linux. I am suspecting the Mi Flash tool that I was using to check it did something. Instead of showing "\usbstor#disk$ven_qualcomm&prod_mmc_storage&re v_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}" it is now showing COM20.
On linux I tried this command
Code:
dmesg | tail
and it shows following output
usb 1-2: new ISB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB_DLOAD
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered for Qualcomm USB modem
qcserial: 1-2:1.0: Qualcomm USB mode converter detected
usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
Any help in this regard is appreciated.

{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Ok.. I have a Linux VM (ubuntu 16.x) booted up, and the FireTV is recognized as a /dev/sdb device. I have downloaded the .bin file from amazon. How do I decompress the BIN file to get the images folder to dd over to the firetv partitions?
I am a linux newbie, so missing that key step
NEVERMIND - Figured it out

Thanks Rbox & {ParanoiA} for hte unbricking guide. I successfully recovered my FireTV and am back up and running.

Rbox/{ParanoiA} any way to recover my fire TV from the state it is currently in.
One more observation. Now it is showing the connection as "Marshall London HS-USB Diagnostic 9008"

After googling a bit I zeroed in that it should be recoverable. I a following this link
http://www.androidbrick.com/unbrick-all-qualcomm-snapdragons-from-qualcomm-hs-usb-qdloader-9008-if-you-have-the-right-kind-of-rom-qhsusb_dload/
However I need following files (MPRG8064T.hex and 8064T_msimage.mbn) in addition to what mentioned in this. I am not able to find anything other than MPRG8064.hex and 8064_msimage.mbn anywhere. I am not sure whether I can use these files or not

MPRG8064.hex and 8064_msimage.mbn did not work
Can Anyone provide MPRG8064T.hex and 8064T_msimage.mbn file?

Just uploaded the requested - http://www.mediafire.com/download/jqfx835f5ompvf4/q.7z
the link contains the non T variant of the requested files

In an attempt to get the device from 9008 to 9006 mode, I attempted http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html without success

After two months of reading and testing every trick i've read on blogs, youtube, russian or chinese forums, and still at the exact same place. No matter what I do or try, I can't get out of the bloody 9008 state. Did any of you had any breakthrough on the problem? Thanks!

[D855P] Model "Unknow" in LGUP, after use LG FlashTool

Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???

fdelago said:
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
Click to expand...
Click to collapse
Any luck unbricking your device?
I have the same problem here