Develop Bugs

[Q] Hard-Brick Nexus 7

Hi, i have a bricked Nexus 7 flo (2013 Wifi)
After plug-in USB i have Qualcomm HS-USB QDLoader 9008.
Bootloader is broken, no-way to go bootloader or fastboot only Download mod via Qualcomm HS-USB with QPST tool.
But, i haven't needed files only i have 8064_msimage.mbn, MPRG8064.hex
What should be the APQ8064 but i do not know if the APQ8064-1AA.
What I miss are probably two xml files (rawprogram0.xml or sth like this, xml with partitions)
advice anyone answer? Thanks LuRy

bump?

Hello my friend, so if you hold the Volume Down button, and turn your tablet on, you are not able to get to the bootloader?

Pandae said:
Hello my friend, so if you hold the Volume Down button, and turn your tablet on, you are not able to get to the bootloader?
Click to expand...
Click to collapse
No, is not anyway to go bootloader.. Only black screen although all key combo.. Only QPST available USB interface..
After 10 seconds hold power button nexus only reboot again to HS-USB mode

I'm afraid I have no knowledge of fixing a bootloader problem. I do not know if anyone knows of a way, except to send the tablet for repair.

Pandae said:
I'm afraid I have no knowledge of fixing a bootloader problem. I do not know if anyone knows of a way, except to send the tablet for repair.
Click to expand...
Click to collapse
When i search for 8064 qstp looks like as good way but didnt right files..
Nexus have apq8064 flo/1aa snapdragon but google searchs is for e.g. nubia z5 with apq8064 without 1aa in cpu name and this files at qpst emmc downloader didnt work with msg contains sth with cookies in connection

lukyrys said:
When i search for 8064 qstp looks like as good way but didnt right files..
Nexus have apq8064 flo/1aa snapdragon but google searchs is for e.g. nubia z5 with apq8064 without 1aa in cpu name and this files at qpst emmc downloader didnt work with msg contains sth with cookies in connection
Click to expand...
Click to collapse
My main clue is this link
http://hi.baidu.com/ch_ff/item/c5baa02910fbbe110975082c

Now i don't feel so alone
Hello friend today i'm in the exacts needs of you, resolve that question.
My nexus 7 is dead too and after 3 nights of so much adb, fasboot, toolkits, flashs, roms, and recoverys nothing has worked.
i haven't tryed this yet because i'm afraid to brick it. i only have the files:
8064_msimage.mbn
8930_msimage.mbn
8960_msimage.mbn
extras
MPRG8064.bin
MPRG8064.hex
MPRG8930.hex
MPRG8960.hex
Click to expand...
Click to collapse
and afraid of using them i can't proceed. i'll try to make those XML by hand with the info i'll collect from my tablet.

Does anyone know any more about this?
I've got a hard bricked Nexus 7 (2013) that registers itself as a Qualcomm USB serial device. Is there any way to extract a bootloader from the stock firmware to flash through this tool?
It was bricked by an accidental restart during a bootloader flash, so I can't get into fastboot
It also mounts a USB Mass Storage device with some of the files listed above in it. Though I don't know what the effect of copying things into here would be. Though if anyone has a valid set of the following files, I could give it a go:
Code:
/image/acdb.mbn
/image/apps.mbn
/image/dsp1.mbn
/image/dsp2.mbn
/image/dsp3.mbn
/image/efs1.mbn
/image/efs2.mbn
/image/efs3.mbn
/image/mdm_acdb.img
/image/rpm.mbn
/image/sbl1.mbn
/image/sbl2.mbn
thanks

9point6 said:
Does anyone know any more about this?
I've got a hard bricked Nexus 7 (2013) that registers itself as a Qualcomm USB serial device. Is there any way to extract a bootloader from the stock firmware to flash through this tool?
It was bricked by an accidental restart during a bootloader flash, so I can't get into fastboot
It also mounts a USB Mass Storage device with some of the files listed above in it. Though I don't know what the effect of copying things into here would be. Though if anyone has a valid set of the following files, I could give it a go:
Code:
/image/acdb.mbn
/image/apps.mbn
/image/dsp1.mbn
/image/dsp2.mbn
/image/dsp3.mbn
/image/efs1.mbn
/image/efs2.mbn
/image/efs3.mbn
/image/mdm_acdb.img
/image/rpm.mbn
/image/sbl1.mbn
/image/sbl2.mbn
thanks
Click to expand...
Click to collapse
you can grab the stock bootloader from android.com, but I don't know if you can flash it.

reubendevries said:
you can grab the stock bootloader from android.com, but I don't know if you can flash it.
Click to expand...
Click to collapse
Try to use QPST tools, which lets you work with it via Qualcomm USB diagnostic connection.

Regarding Moorefield functionality

I'm wondering, when going through the different boot modes, bootloader and recovery, there is a third option that shows up on the pc called Moorefield. It's an unknown driver, which leads me to believe there is some sort diagnostic functionality to it. I guess it's just a matter of figuring out what drivers work. I was wondering if anyone has had this experience, and/or knows how to work with it.

Moorefield is the name for intel processor. It will come handy when all other option to recover phone are not working. But for that we need drivers and image file to jumpstart.

harpreet.s said:
Moorefield is the name for intel processor. It will come handy when all other option to recover phone are not working. But for that we need drivers and image file to jumpstart.
Click to expand...
Click to collapse
how ?

Ex search for intel phone tool which allows to flash images. I have not used it till now however i am pretty sure it will help recovering phone when fastboot , recovery , adb are unable to.

rikkxzzz said:
how ?
Click to expand...
Click to collapse
We've been looking into that over here: http://forum.xda-developers.com/zenfone2/general/unbricking-research-unbricking-method-t3162848

Lumia hard bricked

lumia hard bricked ,i'm connecting to PC ,PC shows unknown device and another time i'm try to connect to PC ,it shows USB device ,PC did't shows qualcomm boot loader,i'm install qualcomm boot loader driver but PC did't recognized my device... please help

more info... which device? did you tried WDRT?

dxdy said:
more info... which device? did you tried WDRT?
Click to expand...
Click to collapse
lumia 820,yes i'm tried WPRT

check this topic, helped me to restore bricked 925
https://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
(btw, i used hex file from lumiafirmware.com)

@Gokul Rajan, sorry for stupid question but have you tried another USB cable and/or another USB port? Also not too bad to give a try on the another PC before starting flashing your handset...

sensboston said:
@Gokul Rajan, sorry for stupid question but have you tried another USB cable and/or another USB port? Also not too bad to give a try on the another PC before starting flashing your handset...
Click to expand...
Click to collapse
i'm tried 4 more laptops and tried different USB cable but every laptops showed That.... any suggestion you have?

What do you do to brick your phone?
Did you tried Windows Phone Internals?

titi66200 said:
What do you do to brick your phone?
Click to expand...
Click to collapse
Yeah, very reasonable question!

titi66200 said:
What do you do to brick your phone?
Did you tried Windows Phone Internals?
Click to expand...
Click to collapse
i'm tried WPinternals, WDRT,some cmd prompt codes , the main problem is PC didn't shows Qualcomm Bootloder

is not need to show qualcomm bootloader (if i remember).. only imported is to not have conflict in drivers
just use tutorial posted in post #4
also in all tutorials say to use "Drivers_X2_Flash_Emergency" but this not helped to me, i used Drivers_Lumia_WP8x_2016-06.7z (from link in tutorial). have Windows 10 x64 PC
for step 2 download files from lumiafirmware.com
also, is little confusing for step 4 converting bin to hex but i downloaded hex file from lumiafirmware.com and worked for lumia 925...
important steps:
-drivers
-WDRT
-HEX.hex and msimage.mbn
- now you use command (put location and real names for hex and mbn file)
thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt
- remove battery
- put battery
- connect phone and you must get red screen on phone (this important)
- flash vpl file (enter location and name where vpl and other downloaded ROM files is)
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\****************
-when done screen must change to green
- use commend
thor2 -mode rnd -bootnormalmode
and thats all

this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....

fullcontrol said:
this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....
Click to expand...
Click to collapse
how to FIX it

fullcontrol said:
this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....
Click to expand...
Click to collapse
need your help , how to fix it??

Gokul Rajan said:
need your help , how to fix it??
Click to expand...
Click to collapse
Find in pcb testpoint or resistor cpu pin# SDC1_CLK first remove battery and usb cable too. short with ground. SDC1_CLK plugin usb cable and battery u will be see in Device Manager QHSUSB_DLOAD. 90008 com device. then leave to short with ground
Next step Folow this link
dxdy said:
check this topic, helped me to restore bricked 925
https://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
(btw, i used hex file from lumiafirmware.com)
Click to expand...
Click to collapse
(if you have recognized QHSUSB_DLOAD. 90008 com device. You can fix boot with WPinternals try with old versions. 1.1 or 1.0 enginering sbl's unlock bootloader method...)
If not help, possible to failure any components in pcb give it to repair service!

fullcontrol said:
Find in pcb testpoint or resistor cpu pin# SDC1_CLK first remove battery and usb cable too. short with ground. SDC1_CLK plugin usb cable and battery u will be see in Device Manager QHSUSB_DLOAD. 90008 com device. then leave to short with ground
Next step Folow this link
(if you have recognized QHSUSB_DLOAD. 90008 com device. You can fix boot with WPinternals try with old versions. 1.1 or 1.0 enginering sbl's unlock bootloader method...)
If not help, possible to failure any components in pcb give it to repair service!
Click to expand...
Click to collapse
Any other sollution???

adb waiting for device

When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects

Anyone?

no one?

bigd19888 said:
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Click to expand...
Click to collapse
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.

sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have minimal adb and fastboot installed
device is h811 20v
bootloader is already unlocked
and yes I'm using LGMobileDriver_WHQL_Ver_4.2.0

sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp

After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.

RuedasLocas said:
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
Click to expand...
Click to collapse
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS

bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
Don't allow Windows 10 to update your drivers - you can set that up in Windows. Google it for the how-to.

bigd19888 said:
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
Click to expand...
Click to collapse
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck

RuedasLocas said:
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
Click to expand...
Click to collapse
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow

bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Your device should be seen as "LGE Android Phone" (if your lg drivers are good).
Now gonna be tricky because my OS is in Portuguese, I don''t know exactly the path name in English... use your imagination
Connect the device on a USB 2 Port !!!
In windows device manager, select "update driver", "search software on the computer", "allow to choose from a list of avalable drivers". unmark the "compatible hardware" and find on the list the needed drivers. If the "LGE" drivers don't work, try to download Universal ADB Drivers, maybe it works.

bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
I'm thinking it could be a corrupted LG driver. Download another from the LG US site, ONLY. Uninstall the one you have installed now, reboot and install the newly downloaded one. Then connect your phone and see if it is recognized and shown correctly in Windows Device Manager. Also, in adb type lsusb and see if the phone is listed in the output.

bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Boss, no need to struggle with this ADB anymore.. there is a tool called FWUL which was created for people who have driver issues... Check it out here:
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
:good:

Locked bootloader by mistake, can't use the phone now

Hey all,
I just got a OnePlus 5T and because I needed a specific system language I decided to flash a custom ROM. I unlocked the bootloader, flashed Derpfest on it and it was all good until I made a mistake. From the Developers options I unchecked "OEM Unlocking" and then when I restarted into the bootloader I did a fastboot oem lock
Now the phone says it's corrupted and it won't boot. Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!

Emo113 said:
Hey all,
Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!
Click to expand...
Click to collapse
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps

sn809 said:
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps
Click to expand...
Click to collapse
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.

Emo113 said:
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.
Click to expand...
Click to collapse
That is superb. If you could do the other bit I would really appreciate it.
Thanks

sn809 said:
That is superb. If you could do the other bit I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Hey there, sorry I totally mis-read the last part of your original post as something that I should do and I didn't see that you need that. Since I used the MDM tool I didn't bother to try your way first and since the phone wasn't mine to keep I already gave it to the owner so I don't have access to it anymore.
Again, very sorry about that.

No dramas. I also got it from some one else who was kind enough to lend it to me and let me root it and wipe it clean and then get the file and start using his phone again.
Thanks