Qhsusb_dload

[CodeNameRedNeck]

I am not trying to place blame on anyone here I only want others to be aware of this. I know of one other guy who bricked his in the 4.2 AOKP Unofficial thread. I am not sure what this guy did.
This is exactly what I did.
Coming from the UCLL3 DeOdexed I rebooted to CWM v6.0.2.7.
Wiped and or formatted cache/system/data/dalvik accordingly.
Flashed the ROM (after previously checking MD5SUM), it seemed to go okay.
Flashed SuperSU v1.04 (MD5SUM checked and used before)
Flashed 12/20/2012 GApps (MD5SUM checked and I had flashed on two other JB CM ROMs), looking back I should have known right then something was wrong because it seemed to take longer than it should have.
Flashed JustunBean’s Aroma (themes only and had flashed that on at least two other ROMs)
Tried to flash MrMad’s TW Add on v1.3.3 (which I used on two other CM10.1 ROMs)
That is where things went bad. CWM came back saying something to the effect of “some errors cannot be overlooked” I said “WHAT”? I tried to flash it again with the same error.
I then tried to reboot system. No signs of life. No Samsung Logo.
After pulling battery and trying to boot again I pulled the battery again then hooked it up to pc. That is where I got windows needs to install drivers for your device “DHSUSB_DLOAD”.
I am looking into getting it fixed at MobileTechVideos.
Like I said not blaming anyone just letting people know that it can happen. This may be my first post and I am no Pro or a Dev but I have been flashing on the Skyrocket for almost two years to the day. I admit I am a Flash-Aholic.
Clarification. Nearly two years to the day plus or minus six or seven months

 

[xstokerx]

I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.

 

[ka724ka]

It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)

 

[vincom]

It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)

that wouldnt do it, but since you and op flashed aokp4.2 could be something within the rom that did it or internal ram failure, or it could be user error

 

[CodeNameRedNeck]

I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.

It was the ROM for the skyrocket out of the Skyrocket thread. Thanks for the info though.

[/QUOTE] ka724ka It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)
[/QUOTE]

Thanks for the info. I did not wipe internal SD although I have wiped internal SD many times before and battery was over 90%.

[/QUOTE] vincomthat wouldnt do it, but since you and op flashed aokp4.2 could be something within the rom that did it or internal ram failure, or it could be user error
[/QUOTE]
Thank you for the info. I hope it was not user error I took the same steps and procedures for all the ROM flashes that I have flashed and I have flashed many a ROM. I hope it is not RAM problems because I plan to get it Jtag-ed so my son can use it. The Skyrocket is an awesome phone.

 

[holeindalip]

One question. Why would you try to root the phone again after installing aokp zip?

Sent from my SAMSUNG-SGH-I727 using xda app-developers app

 

[CodeNameRedNeck]

I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.

One question. Why would you try to root the phone again after installing aokp zip?

Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Some developers use SuperUser and I prefer SuperSu so I flash the SuperSU file that I have.

 

[xstokerx]

Some developers use SuperUser and I prefer SuperSu so I flash the SuperSU file that I have.

could u not have just deleted superuser then downloaded supersu from the market?

 

[CodeNameRedNeck]

You could do that or just flash it while you are already there.

 

[crashpsycho]

why woul you flash the SUperSU when all you have to do is download the app from market and click switch and reinstall superSU doesnt mess with any of the files tha could cause this issue

 

[mtdew]

Well given many others have dl'd installed and successfully used aokp I'm going with user error.

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

 

[toyes]

Well given many others have dl'd installed and successfully used aokp I'm going with user error.

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yes thank you mtdew. With just about 250 downloads of the 4.2.1 ROM and 60 of the 4.2.2 I would have to agree with that.

I'm sorry that it has happened while trying to use my ROM, it is in no way intentional.

You do however root, flash ROMs at your own risk. Its a chance you take and sometimes things like this do happen.

Thanks
Toyes

Sent from my SGH-I727 using Tapatalk 2

 

[killablack]

I also recently had experience with qhsusb download but unofficial aokp port and just for future reference jtags are not always the solution; mobiltech repairs was unable to unbrick it through JTAG as the onboard emmc controller was unresponsive and I'm currently waiting for a repair through samsung; it gave me a new respect of the dangers of flashing.

 

[mr_magoo]

I also recently had experience with qhsusb download but unofficial aokp port and just for future reference jtags are not always the solution; mobiltech repairs was unable to unbrick it through JTAG as the onboard emmc controller was unresponsive and I'm currently waiting for a repair through samsung; it gave me a new respect of the dangers of flashing.

Erm.. You should change your user name dude..