Root qhsusb_dload

[oibarra93]

So crap, I may have overwritten the boot sector. I'm now getting qhsusb_dload as a device on my computer when I hook up my Vital to it.

I've searched around, and it seems to be a service mode, a mode in the lower level of the device. The problem is there seems to be no cure for it, as of yet.

I've seen a couple of forums fix this problem, but it's for their specific HTC, or Google phone. I'm wondering if there is a driver that can be made from the stock one to allow users to access that lower level firmware.

Maybe a JIG or JTAG or something, possibly anything to get it out of that mode.

Any help?

 

[Shabbypenguin]

you could try having someone make an unbrick image Downloading...

they flash that and give you the image, you write the image to an sdcard that is as big as the emmc chip is in your device (like the sgs3 is 16gb for the 16gb model). from there your device will boot as long as you have the sdcard in your phone, then you just need to flash the stock files back on the device however this phone does that.

 

[oibarra93]

Exactly, how would someone go about this?

 

[Shabbypenguin]

go about what?

 

[oibarra93]

go about what?

How can you make an unbrick image? And do Android phones have a native support for booting from SD cards?

I'm just curious about the whole process before I throw this two hundred dollar phone away.

 

[Shabbypenguin]

someone who has a booting phone needs to flash that zip in ecovery, thats all. i tried to make it as easy as possible .

qualcomm has had sdcard booting in their chips since at least 2012, but only when you overwrite the low level bootloaders.

 

[oibarra93]

someone who has a booting phone needs to flash that zip in ecovery, thats all. i tried to make it as easy as possible .

qualcomm has had sdcard booting in their chips since at least 2012, but only when you overwrite the low level bootloaders.

I see, well I have a bunch of backups on my SD card, but your tool is a shell script.
How can I execute that script? I don't have Linux. I also don't have a booting phone to execute that script.

That's really interesting, I never thought Qualcomm would ever become that user friendly.

 

[Shabbypenguin]

as i said, you need someone to make teh unbrick image.

 

[oibarra93]

as i said, you need someone to make teh unbrick image.

It looks like your script is just a ROM dump, of which I already have many. The device is in download mode, Linux recognizes it very well, and I am able to write to it, but exactly I need to write is unclear to me. I have a boot.img, a recovery.img, and a bunch of system files from the dump. I doubt any of these should be written to the MODEM of the phone. So what next?

 

[Shabbypenguin]

its not a rom dump it dumps the first 200mb's of mmcblk0 which when written to the sdcard and your aboot is screwed will cause you to boot off the sdcard instead.

 

[raymealer]

Will this work for the ZTE Mustang

 

[raymealer]

as i said, you need someone to make teh unbrick image.

Will that unbrick Creator work on the ZTE Mustang mine won't boot at all but shows up on the computer as qhsusb_dload

 

[raymealer]

I posted it here because it was quicker and kind of relates

 

[Shabbypenguin]

take your booting sdcard and reformat it ect get it back to working usable. insert it into your wifes phone and use terminal emulator and root

dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1

that will do an exact dump of her device byte for byte so make sure you are using at least a 4gb card, stick that in the nonbooting device and if that still doesnt work then im sorry nothing more i can do

 

[Izzxy]

take your booting sdcard and reformat it ect get it back to working usable. insert it into your wifes phone and use terminal emulator and root

dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1

that will do an exact dump of her device byte for byte so make sure you are using at least a 4gb card, stick that in the nonbooting device and if that still doesnt work then im sorry nothing more i can do

Did this work?? I having the same problem