Root Well, I did it- got bricked- but REAL bricked too

[agentc13]

please read this thread. we're currently working on this "qhsusb_dload" brick mode. forum.xda-developers.com/showthread.php?t=1522351 any help is appreciated.

That's for a different phone, I doubt that it will help with this issue.

 

[dalem50]

Just call support and tell them your phone isn't turning on, they'll mail you a replacement phone overnight via UPS. I've done this myself even two times with a custom recovery and ROM. The first time my phone was bricked and the second time the replacement phone had a faulty antenna.

 

[b_randon14]

I think your toast man. Booting into download mode(volume diem and power) and ugly it into your computer and see if it mounts anything.

Fastboot does not work for the triumph and should likewise never be used. If you flashed an nb0 file phone a different phone then it probably repartitioned the internally memory( where all the important stuff is) and could possibly be unfixable.

Thus phone is very hard to fubar and very easy to root and flash Roms and put a cwm recovery on it. There are guides for all these procedures that work and are very simple to follow.

If you can get the mobile partition to mount in download mode it may be fixable, or if you can get anything to mount in osx under download mode
If not I wide get a replacement!

 

[jdash52]

Hey y'all,

Thanks for all the followup messages- I'm going to post some more details about what I've sort of uncovered since last posting. I'll explain briefly and want to ask another question of sorts -- something I need a sureshot way of confirming.

I did receive a replacement from VM finally. I backupped via nandroid CWM 5.xx and put on CM7. I then began poking around in QPST and other diagnostic tools to see if I could get to the bottom of the troubles I was having with the previous unit. Part of what I'm doing now is using multiple applications to pull out different pieces of what is needed to rebuild the bricked unit. More on those things later ...

But what I do think I uncovered has me puzzled ... The replacement phone I received is showing that it has a Surf MSM 7630 processor in it... this is a S1 Qualcomm snapdragon and slower than the S2 MSM8655 the Triumph is supposed to have.

So--- can anyone tell me a reliable way to pull the correct processor model from the phone? If in fact it is a 7630 then I obviously should not and will not accept this as "replacement" for the hardware I actually purchased. Anyone heard of such a thing before?

This info came out of DFS 3.3.07, where among lots of things, it will display the (presumed) processor model.

Thoughts anyone?

 

[marc12868]

Hey y'all,

Thanks for all the followup messages- I'm going to post some more details about what I've sort of uncovered since last posting. I'll explain briefly and want to ask another question of sorts -- something I need a sureshot way of confirming.

I did receive a replacement from VM finally. I backupped via nandroid CWM 5.xx and put on CM7. I then began poking around in QPST and other diagnostic tools to see if I could get to the bottom of the troubles I was having with the previous unit. Part of what I'm doing now is using multiple applications to pull out different pieces of what is needed to rebuild the bricked unit. More on those things later ...

But what I do think I uncovered has me puzzled ... The replacement phone I received is showing that it has a Surf MSM 7630 processor in it... this is a S1 Qualcomm snapdragon and slower than the S2 MSM8655 the Triumph is supposed to have.

So--- can anyone tell me a reliable way to pull the correct processor model from the phone? If in fact it is a 7630 then I obviously should not and will not accept this as "replacement" for the hardware I actually purchased. Anyone heard of such a thing before?

This info came out of DFS 3.3.07, where among lots of things, it will display the (presumed) processor model.

Thoughts anyone?

Actually it's a S2 scorpion. It only runs at 800mhz so that probably isn't accurate at all.. You can try to use z-device test and got to the cpu section and see if it shows your cpu model number.

 

[jdash52]

please read this thread. we're currently working on this "qhsusb_dload" brick mode. forum.xda-developers.com/showthread.php?t=1522351 any help is appreciated.

This driver is the needed driver to work with Qualcomm devices over USB. Being in Download mode is a symptom of your problem but this driver is most likely correct if you have a chance to correct the issue.

 

[jdash52]

Actually it's a S2 scorpion. It only runs at 800mhz so that probably isn't accurate at all.. You can try to use z-device test and got to the cpu section and see if it shows your cpu model number.

Whoops, I made a mistake. They are both S2, you're right. That was me inadvertently saying it is a S1, not what DPS said.

Screenshot:

1 core and no processor name yet frequencies look right. The revision and serial # are filled 0's. What do you get?

 

[marc12868]

Whoops, I made a mistake. They are both S2, you're right. That was me inadvertently saying it is a S1, not what DPS said.

Screenshot: View attachment 29195

1 core and no processor name yet frequencies look right. The revision and serial # are filled 0's. What do you get?

Idk. My MT's touchscreen doesn't work so I can't test. But that looks all like it would be the right processor.

 

[RussianBear]

That's for a different phone, I doubt that it will help with this issue.

both phones run on a qualcomm chip. that thread has progressed tremendously since i've last posted. we'll have a guide for sensation phones and maybe other ones (that have the emmc system) to be able to unbrick their phones from doing a wrong s-on operation.

This driver is the needed driver to work with Qualcomm devices over USB. Being in Download mode is a symptom of your problem but this driver is most likely correct if you have a chance to correct the issue.

see this post: http://androidforums.com/triumph-al...ph-experiment-thread-caution.html#post4190389

if you were to get similar backup files for your phone, you could try and flash them from qpst's "mmc software download module". we're yet to find similar files (hex and mbn) for sensation, so there is no way to test this theory yet. if any triumph user with a qhsusb_dload brick could try that, that would be awesome.

 

[agentc13]

both phones run on a qualcomm chip. that thread has progressed tremendously since i've last posted. we'll have a guide for sensation phones and maybe other ones (that have the emmc system) to be able to unbrick their phones from doing a wrong s-on operation.



see this post: http://androidforums.com/triumph-al...ph-experiment-thread-caution.html#post4190389

if you were to get similar backup files for your phone, you could try and flash them from qpst's "mmc software download module". we're yet to find similar files (hex and mbn) for sensation, so there is no way to test this theory yet. if any triumph user with a qhsusb_dload brick could try that, that would be awesome.

Well, this phone does not have s-off (or s-on either), how does that have anything to do with the Motorola Triumph?
We have easier ways to take care of the issues that were asked about in this this thread. I understand what you are trying to get done for your phone, but it doesn't really pertain to the issue that was going on in this thread.

I am not trying to knock your efforts with the sensation, but it doesn't relate to this device or thread.

 

[RussianBear]

Well, this phone does not have s-off (or s-on either), how does that have anything to do with the Motorola Triumph?
We have easier ways to take care of the issues that were asked about in this this thread. I understand what you are trying to get done for your phone, but it doesn't really pertain to the issue that was going on in this thread.

I am not trying to knock your efforts with the sensation, but it doesn't relate to this device or thread.

i was not talking about s-off or s-on. i'm talking about the qhsusb_dload issue that he had and the possibility of using qpst to fix it.

We have easier ways to take care of the issues that were asked about in this this thread.

was his problem ever solved? not talking about the warranty return.