Looks like I have a hard brick with the device manager reporting qhsusb_dload. This appears to be related to corrupt partitioning, the last thing I flashed was a zip package in CWM and rebooted the phone and it didn't reboot by vibrating and showing the Samsung logo, it just was black.
I pulled the battery and attempted to power it on again and I was getting no response from the device, I plugged it into my pc and that's when I saw the qhsusb_dload missing driver which I found drivers for, but it doesn't help me.
My question is, is this something JTAG can fix? I don't want to take a chance on warranty replacement and getting a MF3 factory phone since I wont be able to Loki. Any info would be appreciated.
ChaosMinionX said:
Looks like I have a hard brick with the device manager reporting qhsusb_dload. This appears to be related to corrupt partitioning, the last thing I flashed was a zip package in CWM and rebooted the phone and it didn't reboot by vibrating and showing the Samsung logo, it just was black.
I pulled the battery and attempted to power it on again and I was getting no response from the device, I plugged it into my pc and that's when I saw the qhsusb_dload missing driver which I found drivers for, but it doesn't help me.
My question is, is this something JTAG can fix? I don't want to take a chance on warranty replacement and getting a MF3 factory phone since I wont be able to Loki. Any info would be appreciated.
Click to expand...
Click to collapse
Yes, unfortunately it's down to JTAG with a RIFF box or similar equipment.
GiantBallSack said:
Yes, unfortunately it's down to JTAG with a RIFF box or similar equipment.
Click to expand...
Click to collapse
Figures... now I gotta find someone that can do the JTAG/RIFF repair.
ChaosMinionX said:
Figures... now I gotta find someone that can do the JTAG/RIFF repair.
Click to expand...
Click to collapse
I found this on GSM-Hosting, and was reported to be a Samsung driver. If the driver installs successfully, QPST will probably see the phone, but I doubt that ODIN would. I still think you are down to JTAG, but here's the driver if you want to mess around with the phone some more
GiantBallSack said:
I found this on GSM-Hosting, and was reported to be a Samsung driver. If the driver installs successfully, QPST will probably see the phone, but I doubt that ODIN would. I still think you are down to JTAG, but here's the driver if you want to mess around with the phone some more
Click to expand...
Click to collapse
Thanks, I had the drivers after looking on google so now it shows up as Qualcomm HS-USB QDLoader 9008 (COM6). ODIN so far doesnt appear to be able to see the phone any longer. Will QPST be able to do anything?
ChaosMinionX said:
Thanks, I had the drivers after looking on google so now it shows up as Qualcomm HS-USB QDLoader 9008 (COM6). ODIN so far doesnt appear to be able to see the phone any longer. Will QPST be able to do anything?
Click to expand...
Click to collapse
If you had a full flash file, you could flash it with QPST and unbrick it. Those files are extremely hard to come by, only the service centers seem to have them. It may be possible to backup a different S4 and flash it but you may end up with an identical copy of the other person's phone. My only experience with QPST is changing the service programming for CDMA phones. Hard-bricks I had equipment for. I have it installed, I'll see if I can pull a dump of my phone that can be flashed, but I still wonder about the EFS partitions.
GiantBallSack said:
If you had a full flash file, you could flash it with QPST and unbrick it. Those files are extremely hard to come by, only the service centers seem to have them. It may be possible to backup a different S4 and flash it but you may end up with an identical copy of the other person's phone. My only experience with QPST is changing the service programming for CDMA phones. Hard-bricks I had equipment for. I have it installed, I'll see if I can pull a dump of my phone that can be flashed, but I still wonder about the EFS partitions.
Click to expand...
Click to collapse
Alright thanks, yeah I can get the phone in QPST its listed in Download mode. Wonder if a dump from a working phone could fix it?
ChaosMinionX said:
Alright thanks, yeah I can get the phone in QPST its listed in Download mode. Wonder if a dump from a working phone could fix it?
Click to expand...
Click to collapse
It's possible. Check your PM.
JTAG service only. Period
Sent from my GT-I9505 using xda premium
TheAxman said:
JTAG service only. Period
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Anyone on the forum do JTAG service? I dont want to take chance of ATT warranty sending me a MF3 phone.
GiantBallSack said:
It's possible. Check your PM.
Click to expand...
Click to collapse
I've done a lot of research and experimenting in this area, because I'm currently stuck in a similar situation with my phone stuck in QPST mode. If you have any knowledge about a working .hex file for this device, please let me know (PM me if needed?).
TheAxman said:
JTAG service only. Period
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Pretty much. Unfortunately in my case, JTAG appears not even a viable option. Might be different for the OP, however. Probably has a different "style" of hard-brick.
ChaosMinionX said:
Anyone on the forum do JTAG service? I dont want to take chance of ATT warranty sending me a MF3 phone.
Click to expand...
Click to collapse
There's a few people on the forums with JTAG boxes offering service. Perhaps the most reputable would be @connexion2005 - his website is mobiletechvideos.com. Costs $60 for an S4, plus extras (rush shipping, rush processing, data recovery, etc.), last I looked.
Only problem is, if you're hard-bricked because of the MF3 update somehow, you might be SOL. Last I heard, mobiletechvideos.com sent back a phone to another XDA member, unfixed for this reason. Still waiting to hear the whole story on this, so I wouldn't discredit mobiletechvideos.com yet. They're very good at what they do, and they've repaired thousands of hard-bricks on many different models of phones.
Aou said:
I've done a lot of research and experimenting in this area, because I'm currently stuck in a similar situation with my phone stuck in QPST mode. If you have any knowledge about a working .hex file for this device, please let me know (PM me if needed?).
Click to expand...
Click to collapse
We worked on a good bit today, and QPST just wouldn't cooperate with the phone in anyway. It wouldn't write aboot.mbn like the phone needs. A full flash in .mbn format is needed.
GiantBallSack said:
We worked on a good bit today, and QPST just wouldn't cooperate with the phone in anyway. It wouldn't write aboot.mbn like the phone needs. A full flash in .mbn format is needed.
Click to expand...
Click to collapse
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Aou said:
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Click to expand...
Click to collapse
I didnt have MF3 official on there, the only files from MF3 I used were the Modem, and Tasks's latest AOKP had MF3 RIL. I wonder if I am in the same boat as you?
I do however have a replacement device on its way tomorrow, I wonder if ATT has officially gone to MF3 for replacement warranty devices yet?
ChaosMinionX said:
I didnt have MF3 official on there, the only files from MF3 I used were the Modem, and Tasks's latest AOKP had MF3 RIL. I wonder if I am in the same boat as you?
I do however have a replacement device on its way tomorrow, I wonder if ATT has officially gone to MF3 for replacement warranty devices yet?
Click to expand...
Click to collapse
I certainly hope they haven't. If they have, I'd rather pay the $199 deductible on a new device through insurance instead!
Aou said:
I certainly hope they haven't. If they have, I'd rather pay the $199 deductible on a new device through insurance instead!
Click to expand...
Click to collapse
You and me both! I would just assume sell the warrantied device and pay difference to get a Google Edition, I am not real keen on HTC phones. Guess we will see what they ship me when it arrives tomorrow!
Aou said:
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Click to expand...
Click to collapse
nevermind, sorry
Well good news! My replacement from warranty came today and its still running MDL, so guess I will be returning the bricked device. Sigh of relief seeing MDL and not MF3 thats for sure :good::good:
ChaosMinionX said:
Well good news! My replacement from warranty came today and its still running MDL, so guess I will be returning the bricked device. Sigh of relief seeing MDL and not MF3 thats for sure :good::good:
Click to expand...
Click to collapse
man you sure lucked out there
GiantBallSack said:
It's possible. Check your PM.
Click to expand...
Click to collapse
Hey, could you tell me how it is possible ?
i have a I9505 in QPST DL mode and i don't know how to get a dump from a working model !
thx !
Related
after using the "Odin3 One-Click Downloader" my i9000 only loops the att logo on and off, recovery mode and download mode are no longer working... had anyone experienced this?
well this is f...ed up..... my i9000 was unbranded, and that one click crap must have flashed the captivate fw or smth, should i let my phone die in peace now?
There are different oneclick apps for different branded SGSs. Which one did you download? Sounds like you downloaded the AT&T version.
You have to boot your phone into download mode again to flash the correct ROM for your specific phone. There are many different ways to get the phone into download mode. Check the dev forum or instructions.
foxbat121 said:
There are different oneclick apps for different branded SGSs. Which one did you download? Sounds like you downloaded the AT&T version.
You have to boot your phone into download mode again to flash the correct ROM for your specific phone. There are many different ways to get the phone into download mode. Check the dev forum or instructions.
Click to expand...
Click to collapse
"[STOCK ROM] Odin3 One-Click Downloader and Drivers" I've downloaded this one... and i cant boot into download mode, the 3 button methods died on me
Its for captivate.... And your phine iscompletely bricked. Needs a new mother board.
Why people download weird **** from untrusted sources?
Sent from my GT-I9000 using XDA App
Phone is completely bricked. Happened to me, and a few others too. Seems that these one-click odin downloaders do more harm than good. Hahaha...
Anyway, phone is bricked. Samsung replaced the motherboard for me. Luckily it's under warranty at no cost to me..
Seifer1975 said:
Phone is completely bricked. Happened to me, and a few others too. Seems that these one-click odin downloaders do more harm than good. Hahaha...
Anyway, phone is bricked. Samsung replaced the motherboard for me. Luckily it's under warranty at no cost to me..
Click to expand...
Click to collapse
replace the motherboard? what the fudge.. i gave it to a local repair shop (samsung recommended one) and well.. they will try to reflash it or smth.. if that wont work, how much would replacing the motherboard cost? i'm out of warranty
dupel said:
Its for captivate.... And your phine iscompletely bricked. Needs a new mother board.
Why people download weird **** from untrusted sources?
Click to expand...
Click to collapse
What untrusted source? He went into Captivate forum here in XDA to download Captivate stock ROM. What do you think the outcome will be?
it might cost you around $150 or so, if i remember reading a recent post about a guy replacing his mb too. I think he had the same problem as you.
SwiftPolar said:
it might cost you around $150 or so, if i remember reading a recent post about a guy replacing his mb too. I think he had the same problem as you.
Click to expand...
Click to collapse
could you find that post for me? i cant seem to find it myself...
well, so far, i've found out that by flashing the i9000 (unbranded) with a captivate FW remapped all the buttons except for the power button, so download mode or recovery mode is impossible via any button combination. But if the phone does show something on the screen, its still only semi-bricked, in my case, its stuck at the bootloader. its fixable with JTAG ... i hope the service i took it to has a jtag device and will reflash to the i9k FW. and it would only cost me 10$ for the repairs
who had a similar experience?
I had exactly the same problem, after updating my phone through kies which failed halfway through i downloaded odin which at the time i didn't know was the wrong one and not for the i9000. in the end i had to get a new phone.
Sent from my GT-I9000 using XDA App
aaronlivo said:
I had exactly the same problem, after updating my phone through kies which failed halfway through i downloaded odin which at the time i didn't know was the wrong one and not for the i9000. in the end i had to get a new phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
were you under warranty? did you try to repair it ?
well my sgs is not fully bricked, it does not need a new motherboard... it just needs to be reflashed with jtag or smth >.<
a fully bricked (faulty) device would not turn on at all
allright, so just by flashing the phone with that one click odin crap, the repairs are going to cost me 250$
Well, today I tried setting up ClockworksMod so I could easily backup and restore my phone as needed. (As previous work i had caused issues and it wouldnt reboot until i reinstalled the rom)
Well, clockworkmod recovery would not install through the app, so I installed the image through Odin, and that worked flawlessly. I was able to backup and restore.
After it booted back up I was unable to add a new google account or erase the old one. Factory resetting it would casue it to get stuck in the boot loop again, until i restored it or reflashed.
Eventually I tried flashing another image, with repartition turned on.
Well, without surprise Windows 7 semi crashed and killed Odin.
Now when my phone "turns on" all i see is black. Nothing happens. I cant do any of the 3 button combos to get into Recovery or Download mode
Can anybody help me? I need to get this working ASAP!
Thanks
Edit : I need to check my eyes. I thought you can get into download mode.
If you cannot get to download mode with the 3-button-combo then you'll need a jig.
Intratech said:
If you cannot get to download mode with the 3-button-combo then you'll need a jig.
Click to expand...
Click to collapse
Dosnt that only work if the image of the phone and computer show up on the screen?
Absolutly nothing shows up for me
Can I have your battery cover to keep as a spare.
bncplix said:
Dosnt that only work if the image of the phone and computer show up on the screen?
Absolutly nothing shows up for me
Click to expand...
Click to collapse
You need a jig.
Uhm, why did you check repartition?
Also yes, you will need a jig. That's pretty much the only thing that can get you into download mode in this situation.
Transmitted from a Galaxy far far away via XDA telepathy.
Intratech said:
You need a jig.
Click to expand...
Click to collapse
Okay, going to just order one off ebay.
Will this do? hxxp://cgi.ebay.com/Samsung-i9100-Galaxy-S-II-Download-mode-USB-Dongle-Jig-/250824932406?pt=AU_MobilePhoneAccessories&hash=item3a6654bc36
But actually, it says it has to show one of those two screens, when mine is all black?
geko95gek said:
Uhm, why did you check repartition?
Also yes, you will need a jig. That's pretty much the only thing that can get you into download mode in this situation.
Transmitted from a Galaxy far far away via XDA telepathy.
Click to expand...
Click to collapse
Because it said it was needed for that image i was flashing
bncplix said:
Okay, going to just order one off ebay.
Will this do? hxxp://cgi.ebay.com/Samsung-i9100-Galaxy-S-II-Download-mode-USB-Dongle-Jig-/250824932406?pt=AU_MobilePhoneAccessories&hash=item3a6654bc36
But actually, it says it has to show one of those two screens, when mine is all black?
Because it said it was needed for that image i was flashing
Click to expand...
Click to collapse
It can still work in some cases, lets hope it does in yours.
Did you get that advise about repartitioning from Samfirmware?
Intratech said:
It can still work in some cases, lets hope it does in yours.
Hopefully! I just ordered one
Did you get that advise about repartitioning from Samfirmware?
Click to expand...
Click to collapse
Yes I did, was that something I shouldn't have done?
It sat on repartitioning for about 15 minutes, then windoes said Odin stopped responding and it killed it :/
I've been telling everybody to stop using the .pit files and repartitioning the device for every flash as you're just increasing the possibilities of things going wrong but people don't seem to take notice. Sadly in your case something did go wrong. You only need to use the .pit files and repartition the device if you mess up your partition table.
Those guys at Samfirmware really need to stop telling people to repartition their device for every flash.
Intratech said:
I've been telling everybody to stop using the .pit files and repartitioning the device for every flash as you're just increasing the possibilities of things going wrong but people don't seem to take notice. Sadly in your case something did go wrong. You only need to use the .pit files and repartition the device if you mess up your partition table.
Click to expand...
Click to collapse
Well, lesson learned. Today was the first time I even tried installing another ROM
Thanks for the help
Once my Jig comes in, I'll let you all know how it goes!
check if the phone heatens up extremely as soon as you put the battery in. if yes, thats a really bad sign.
a jig will only help you if you see anything on the screen. if the phone/screen doesn't react to ANYTHING, that's a full brick (happened to me too, jig didn't help, nothing helped, phone was completely dead and i had to send it in. fortunately, they repaired it within warranty).
lazyb2k said:
check if the phone heatens up extremely as soon as you put the battery in. if yes, thats a really bad sign.
a jig will only help you if you see anything on the screen. if the phone/screen doesn't react to ANYTHING, that's a full brick (happened to me too, jig didn't help, nothing helped, phone was completely dead and i had to send it in. fortunately, they repaired it within warranty).
Click to expand...
Click to collapse
See, this is what I was trying to say! I read everywhere that if somethign is on the screen the Jig will work, otherwise it wont. Others are replying to me here saying it should still work for me
I'm not too worried about it. I have 4 of the phones. I work closely with Samsung and they were given to me. It would still be nice if it recovers, so we will see!
i guess in situations where it was reported to work under these conditions the owners didnt fully exploit all different possibilites to get it back on and so they just came up with this false assumption.
nonetheless, it's worth a try. at least, the jig is pretty useful to remove the yellow exklamation mark and to reset the flash counter .
lazyb2k said:
i guess in situations where it was reported to work under these conditions the owners didnt fully exploit all different possibilites to get it back on and so they just came up with this false assumption.
nonetheless, it's worth a try. at least, the jig is pretty useful to remove the yellow exklamation mark and to reset the flash counter .
Click to expand...
Click to collapse
That's another thing I am unsure of, whats the flash counter?
bncplix said:
See, this is what I was trying to say! I read everywhere that if somethign is on the screen the Jig will work, otherwise it wont. Others are replying to me here saying it should still work for me
I'm not too worried about it. I have 4 of the phones. I work closely with Samsung and they were given to me. It would still be nice if it recovers, so we will see!
Click to expand...
Click to collapse
I'm not saying it will work for sure, what I'm saying is depending on the damage done it may still get you into download mode so you can flash the firmware.
bncplix said:
That's another thing I am unsure of, whats the flash counter?
Click to expand...
Click to collapse
to be precise, it's the "custom binary counter" which counts up as soon as you flash something modified manually on your phone. has nothing to do with your problem, though.
We need to find the way to boot the device externally, i.e. bootloader on ext. SDCard or the likes....
Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
y3kt said:
Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
Click to expand...
Click to collapse
Wow, sorry to hear this. the battery went dead before jtag finished? ouch. QPST will not help for this, a phone will still boot with no IMEI, this is not good, may want to start a warranty ticket on it. I have a jtag box, so there is a release update for the G4 for it? I did not know this, haven't check in awhile, pull the battery for a good while, replace and charge all the way, and give it one more shot. Sorry bro.
TheAxman said:
Wow, sorry to hear this. the battery went dead before jtag finished? ouch. QPST will not help for this, a phone will still boot with no IMEI, this is not good, may want to start a warranty ticket on it. I have a jtag box, so there is a release update for the G4 for it? I did not know this, haven't check in awhile. pull the battery for a good while, charge all the way, and give it one more shot. Sorry bro.
Click to expand...
Click to collapse
This is exactly what I didn't want to hear :crying:
I have used Riff as JTAG solution.
Unfortunately warranty is not an option for me so I will pull the battery for a couple of days before I try again. At this point it seems is really dead.
I have found many files for QPST that are supposed to do everything to a dead phone, even a command line utility for the same purpose, with some hex and mbn files, but as I said they all failed, it seems to me that eMMC chip is not working at all.
I'll keep you updated if I ever find a way to fix this phone.
y3kt said:
This is exactly what I didn't want to hear :crying:
I have used Riff as JTAG solution.
Unfortunately warranty is not an option for me so I will pull the battery for a couple of days before I try again. At this point it seems is really dead.
I have found many files for QPST that are supposed to do everything to a dead phone, even a command line utility for the same purpose, with some hex and mbn files, but as I said they all failed, it seems to me that eMMC chip is not working at all.
I'll keep you updated if I ever find a way to fix this phone.
Click to expand...
Click to collapse
I did not know this, I will keep that in mind for future ref. Really hope you get it going.
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
y3kt said:
Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
Click to expand...
Click to collapse
i have the same problem but i need an imge file to write it im my device (m919) do u have one?
shadigsm said:
i have the same problem but i need an imge file to write it im my device (m919) do u have one?
Click to expand...
Click to collapse
Yes, I do have an M919 dump image from a working phone you can use.
Here you have the link http://jtagbox.com/downloads/m919/M919.rar
y3kt said:
Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
Click to expand...
Click to collapse
Hi, I was wondering if you got your problem solved, I too have a Galaxy S4 M919 which came to my shop also with IMEI null, I also tried to repair it with RIFFBOX and the phone is dead now. I want to know if you repaired your phone and how you did it. Thank you very much. I also tried the M919 full dump you posted but the riffbox wont recognize it.
frankjasmin said:
Hi, I was wondering if you got your problem solved, I too have a Galaxy S4 M919 which came to my shop also with IMEI null, I also tried to repair it with RIFFBOX and the phone is dead now. I want to know if you repaired your phone and how you did it. Thank you very much. I also tried the M919 full dump you posted but the riffbox wont recognize it.
Click to expand...
Click to collapse
Hi, yes, I did repair the phone with RIFF BOX and a dump from a working phone the RIFF BOX programmer sent me.
y3kt said:
Yes, I do have an M919 dump image from a working phone you can use.
Here you have the link http://jtagbox.com/downloads/m919/M919.rar
Click to expand...
Click to collapse
Wow, they usually don't do that, keep that puppy in a safe location
Good deal.
y3kt said:
Hi, yes, I did repair the phone with RIFF BOX and a dump from a working phone the RIFF BOX programmer sent me.
Click to expand...
Click to collapse
Can you share the dump for the I337?
I'm having the same problem with my S4.
Thanks a lot...
I'm am in a loop, how do I flash from odin?
realgadawg said:
I'm am in a loop, how do I flash from odin?
Click to expand...
Click to collapse
You don't need to use ODIN to fix a boot-loop, just use the 3-button combo to go into recovery and flash a backup or a ROM (Following proper wiping steps).
y3kt said:
Hi, yes, I did repair the phone with RIFF BOX and a dump from a working phone the RIFF BOX programmer sent me.
Click to expand...
Click to collapse
can you share a working link with the dump for m919 please i need one to repair my dead i337
I have a RIFF BOX. I have an M919 here that is completely dead. I tried 3 P.C.'s that won't even detect it. RIFF doesn't see it either. Any ideas on what my options are ? This is driving me crazy, please help
I am somewhat new at rooting, though I have rooted 3 phones. I was rooted on Android 4.4.2 and when I flashed a ROM for 5.0 my screen turned black. It won't turn on, I can't get into recovery or download mode, and when I connect it to my computer through USB it registers it as QHSUSB_BULK. I am stuck right now, is a JTAG the only way to fix it?
vexxid said:
I am somewhat new at rooting, though I have rooted 3 phones. I was rooted on Android 4.4.2 and when I flashed a ROM for 5.0 my screen turned black. It won't turn on, I can't get into recovery or download mode, and when I connect it to my computer through USB it registers it as QHSUSB_BULK. I am stuck right now, is a JTAG the only way to fix it?
Click to expand...
Click to collapse
Does it charge or at least get warm? What ROM did you flash? Did you flash it via safestrap?
Can you access that bulk folder on your computer?
Tulsadiver said:
Does it charge or at least get warm? What ROM did you flash? Did you flash it via safestrap?
Can you access that bulk folder on your computer?
Click to expand...
Click to collapse
I don't know if it is charging and I flashed a rooted stock ROM for 5.0 (OA8) and it was via safestrap. How would I access the bulk folder, as it says driver is not installed?
A Verizon ROM? I thought you said a folder came up on your PC called something bulk.
Tulsadiver said:
A Verizon ROM? I thought you said a folder came up on your PC called something bulk.
Click to expand...
Click to collapse
It is not a folder, it detects my phone through usb as that. I don't know why, maybe I flashed the wrong ROM?
You were supposed to go back into download mode from safestrap and flash the OA8 kernel
Tulsadiver said:
You were supposed to go back into download mode from safestrap and flash the OA8 kernel
Click to expand...
Click to collapse
After further investigation, the file I flashed was OA1, but the download said OA8. I should have been more careful. Is there anything I can do now?
It probably is a brick. Pull your your battery for at least 10 minutes and try again. Still not sure where it is saying bulk folder.
Tulsadiver said:
It probably is a brick. Pull your your battery for at least 10 minutes and try again. Still not sure where it is saying bulk folder.
Click to expand...
Click to collapse
Okay, I will get back to you on that in around 15-20 minutes. And it does not have a bulk folder anywhere, what happens is an alert pops up on bottom of screen saying "driver not successfully installed" and when I click to check the driver it says QHSUSB_BULK where it should say Galaxy s5. Hopefully you understand, as I want to fix my phone.
Oh, under devices. This is probably a brick. Sorry.
Tulsadiver said:
Oh, under devices. This is probably a brick. Sorry.
Click to expand...
Click to collapse
How can I fix it, and how can I tell if it is a hard brick or a soft brick? Also, after 10 minutes with battery out, I cant turn on, or boot into recovery/download mode.
Try charging it. If it doesn't even feel warm it is a hard brick.
Tulsadiver said:
Try charging it. If it doesn't even feel warm it is a hard brick.
Click to expand...
Click to collapse
Anything I can do from that point on?
Like you mentioned, JTAG. There are JTAG services out there. I actually bought a riff box because I bricked my s4 but I got my warranty company to give me a new phone so I never had to use it.
Tulsadiver said:
Like you mentioned, JTAG. There are JTAG services out there. I actually bought a riff box because I bricked my s4 but I got my warranty company to give me a new phone so I never had to use it.
Click to expand...
Click to collapse
Ok, thank you for all your help.
Is it under warranty?
Tulsadiver said:
Is it under warranty?
Click to expand...
Click to collapse
yes, and I just did some google searches and is there a way to use a debrick.img or something on sd card to fix?
vexxid said:
yes, and I just did some google searches and is there a way to use a debrick.img or something on sd card to fix?
Click to expand...
Click to collapse
Here is a debrick IMG. I'm on 4.4.4 so I'm not sure it will work.
Edit. I think I'll have to make one 4.4.2 specific. I'll get back to you.
https://www.dropbox.com/s/zdyoje0rw982lk3/Unbrick_IMG.gz?dl=0
Tulsadiver said:
Here is a debrick IMG. I'm on 4.4.4 so I'm not sure it will work.
Edit. I think I'll have to make one 4.4.2 specific. I'll get back to you.
https://www.dropbox.com/s/zdyoje0rw982lk3/Unbrick_IMG.gz?dl=0
Click to expand...
Click to collapse
Thank you so much. One question though, what is the file extension, should it be .img?
vexxid said:
Thank you so much. One question though, what is the file extension, should it be .img?
Click to expand...
Click to collapse
What I gave you is what the debrick creator spit out.
DELETED
4llerbuntu said:
Hello.
PLEASE HELP ME.
I totally bricked my device. completely dead. i wiped the wrong partitions in fastboot, now it won't get detected at all. it won't even come on.
I'm in a country where its not possible to send it in to Asus for repairs.
computer still sees it as Qualcomm HS-USB QDLoader 9008
but i don't have the necessary tools or files to recover it. PLEASE HELP ME>.
Click to expand...
Click to collapse
Start saving money for new phone :^)
BTW just out of curiosity, what did you wipe?
DELETED
does your phone boot
4llerbuntu said:
The firmware partitions, modem, hyp, sbl1, recovery.
Forgot to flash them back before reboot.
Ive since learnt one can recover with QPST and some files. Problem is i cant find them for Asus.
Click to expand...
Click to collapse
you didn't wipe aboot, abootbak, hypbak? right? Our phone has a backup partition for each partition (abootbak, hypback, sbl1bak, modembak, etc), asus included these, so there must be some way to use them to unbrick. Are you able to reboot to fastboot mode? ( i guess not, but still to confirm)
You can unbrick with QFIL ONLY if you manage to find your device's RAM IMAGE (usually MPRxxxx.mbn) and BOOT IMAGE (usually xxxx_msimage.mbn). Other flash files are included in asus fota, only these two are not. @shakalaca might help to find these files or the entire service ROM. I have been searching for asus service but to no avail . I have flashed many lenevo and xiomi phones with QFIL. Here's is a very nice guide http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
You can request for ZF2 laser's service ROM on that website/blog. GSM FORUM is also a good forum to request service ROMs
DELETED
mohamedelkholy said:
does your phone boot
Click to expand...
Click to collapse
No it doesn't boot. It won't even power on
But it still gets detected as Qualcomm device when plugged in to pc
4llerbuntu said:
No i didnt wipe those.
Will the MPRxxx.mbn and msimage.mbn for another phone but similar processor and chipset work? I found those for MSM8916 for another device and im hoping i can use those.
Click to expand...
Click to collapse
I never cross flashed ram image. Be patient. Don't flash other device's ram image, it may worsen conditions. Keep this as the final solution, but NOT NOW. Also, you need boot image (.mbn) too.
DELETED
DELETED
deleted
Deleted
deleted
Deleted
Deleted
4llerbuntu said:
hmmn, i'm so sad. so nobody is willing to help me at all?
Click to expand...
Click to collapse
not really, I think we're all (ok, just me) don't have that knowledge to help you, or simply can't
4llerbuntu said:
i always assumed all the people who post on this board had the device.
Click to expand...
Click to collapse
Yes, all people there should have laser, and no, i dont have your type, and someone maybe just lurking around, want to buy this laser phone if they feel like it
4llerbuntu said:
Surely i can't be the only person who will ever have this problem.
Click to expand...
Click to collapse
Yes, me too, I think someone will do this thing, don't know why, just feel like it?
4llerbuntu said:
i hope someone is willing to help when it happens to another person.
Click to expand...
Click to collapse
I'm hope we got that knowledge too
4llerbuntu said:
Maybe i should just give up. i'm so down right now.
alright bye.
Click to expand...
Click to collapse
Sorry to hear that
Sent from my ASUS_Z00RD using XDA Labs
4llerbuntu said:
computer still sees it as Qualcomm HS-USB QDLoader 9008
but i don't have the necessary tools or files to recover it. PLEASE HELP ME>.
Click to expand...
Click to collapse
Are you sure msimage is same as gpt? I have attached my ze550kl msm8916 gpt dump. Seems there are three- gpt, gpt1, and gpt2. Try your luck with each one by one.
And please stick to one thread, b7mping the forum is not a solution to your problem. Update your OP by mentioned.ing the workarounds you have tried till now and useful links you have visited for fixing the issue. I know a friend who is a mobile repairer. He might have the service rom for your device. I am waiting for his reply
sziraqui said:
Are you sure msimage is same as gpt? I have attached my ze550kl msm8916 gpt dump. Seems there are three- gpt, gpt1, and gpt2. Try your luck with each one by one.
And please stick to one thread, b7mping the forum is not a solution to your problem. Update your OP by mentioned.ing the workarounds you have tried till now and useful links you have visited for fixing the issue. I know a friend who is a mobile repairer. He might have the service rom for your device. I am waiting for his reply
Click to expand...
Click to collapse
Thank you. I will do that
4llerbuntu said:
Hello.
PLEASE HELP ME.
I totally bricked my device. completely dead. i wiped the wrong partitions in fastboot, now it won't get detected at all. it won't even come on.
I'm in a country where its not possible to send it in to Asus for repairs.
computer still sees it as Qualcomm HS-USB QDLoader 9008
but i don't have the necessary tools or files to recover it. PLEASE HELP ME>.
Click to expand...
Click to collapse
Read this and see if any if it applies.
www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants
I'm not sure how the tool works, but maybe you can pull your backups and write back your partitions from the backup.
Sent from my ASUS_Z00TD using Tapatalk
Mods please help close this thread. ........