Related
I have a Fascinate. And it shows no signal. A circle with a line through it at the top. When I go into Baseband Version it says unknown. And hardware version does also. How can i fix this? I was thinking the modem.bin file would fix it. But all i can find is the epic modem.
Have you tried activating it? Dial *228 option 1. If that doesn't work try *228 option 2.
that doesn't do anything. its as if i don't have a radio. no signal at all. service is great in the area.
nuthin2los said:
that doesn't do anything. its as if i don't have a radio. no signal at all. service is great in the area.
Click to expand...
Click to collapse
have you tried updating radio to newest version in DI01?
how would i do that is i dont have service?
I doubt there is anything you will be able to do about it. Just get it warranty replaced; it's a hardware failure. Same thing happened on my Droid1.
Unfortunately, you have nice little PDA device, but it will no longer be usable as a phone.
We've seen a number of these, and not one has been saved yet. We simply do not have the modem.bin file to replace it with.
This happens when you flash anything using the "PHONE" box in Odin, not the "PDA" box. It will also happen if you flash another carriers modem.bin file over yours, regardless of which box you choose. Always, always, use the "PDA" box in Odin.
There's only two things to do at this point.. Wait until we get a modem.bin, or exchange the unit.
DI01 modem.bin is available. I'm not sure if the stock one is as well.
forum.xda-developers.com/showpost.php?p=8279071&postcount=1
CrimsonSentinel13 said:
DI01 modem.bin is available. I'm not sure if the stock one is as well.
forum.xda-developers.com/showpost.php?p=8279071&postcount=1
Click to expand...
Click to collapse
That's an update to the modem.bin, not the actual modem.bin file. It won't work if you have the same problem as the OP.
Feel free to try it. I guarantee it won't work, but you can't make anything worse at this point. We can recover from just about everything, except the modem.bin issue.
still no modem.bin???
I'm having a similar issue. How do I get this fixed?Do I go to verizon, or samsung? the samsung webpage told me to call a representattive, so I'm assuming there is no repair spot in my area.
Besides, I bought this over ebay (it was mint condition). Do I still have warranty?
Thanks everyone for any help
no warranty 4 u..my problem is the same as your and the wont send a replaacement because i ddnt nuy from a vzw store smh
There is a fix for this over at droid forums a post by me in the Samsung Fascinate Development section this forum wont let me post a link
PM me
Sent from my SCH-I500 using XDA App
trapstarr56 said:
still no modem.bin???
Click to expand...
Click to collapse
It bugs the hell out of me to post this as it is untested, but if the phone is already bricked (flashed via PHONE in Odin or flashed a ROM made for something *other* than the Fascinate), this thread seems to have a modem.bin.
http://forum.xda-developers.com/showthread.php?t=842625
Again....and I cannot stress this enough: DO NOT USE THIS FILE. FOR ANYTHING.
PERIOD.
(unless you used the "PHONE" option in Odin or flashed a non-fascinate ROM)
I used DJ05 but I just got back to DI01 because of 3G network availability. but once I got back in DI01 my fascinate doesn't detect 3G. the web only works on wifi. when I turn off the wifi button it does nothing. even 1g or 2g siganal didn't come up just signal bar shows on. I have no idea to fix it. does anybody can tell me what I need to do now?? without wifi zone it work like feature phone to me..
How exactly did you revert back? I'm assuming you used ODIN? If so, did you choose the Phone button or the PDA button to flash the image? If you used the Phone button, then your modem is dead, and cannot be recovered, so you will have to find some way to replace your phone.
Dial *228 and press 1 to activate/reprogram your phone. I had the same thing happen to me. It's just not activated anymore.
Crashspeeder said:
Dial *228 and press 1 to activate/reprogram your phone. I had the same thing happen to me. It's just not activated anymore.
Click to expand...
Click to collapse
I just did it, and now I can see the triangle icon(roaming) same spot as 3G icon.
but still 3G icon doesn't come up, not available using internet without wifi.
how should I do... If I upgrade to froyo It will be fixed automatically?? haha
ivorycruncher said:
How exactly did you revert back? I'm assuming you used ODIN? If so, did you choose the Phone button or the PDA button to flash the image? If you used the Phone button, then your modem is dead, and cannot be recovered, so you will have to find some way to replace your phone.
Click to expand...
Click to collapse
yes you right. I used odin and put two images, one "DI01modem.tar" via phone section and the other one "DI01package3.tar.tar" thru pda section. so should I find some way to fix?? what else I can try???
enoch. said:
yes you right. I used odin and put two images, one "DI01modem.tar" via phone section and the other one "DI01package3.tar.tar" thru pda section. so should I find some way to fix?? what else I can try???
Click to expand...
Click to collapse
Somebody correct me if I'm wrong, but as far as I know, there is no known way to recover from modem failure caused by flashing with the Phone button in ODIN. I'm sorry, but it looks you will either have to buy a new phone, or find a way to convince Verizon to give you a warranty replacement.
Posted from my DL09 SuperClean Fascinate with Voodoo
ivorycruncher said:
Somebody correct me if I'm wrong, but as far as I know, there is no known way to recover from modem failure caused by flashing with the Phone button in ODIN. I'm sorry, but it looks you will either have to buy a new phone, or find a way to convince Verizon to give you a warranty replacement.
Posted from my DL09 SuperClean Fascinate with Voodoo
Click to expand...
Click to collapse
+1 to that. Hope you have insurance, that is your only hope now. As an FYI, the DI01 package already contained the modem. It is called an AIO package for a reason.
There is no way to recover your phone if you used the Phone option instead of the PDA option in Odin.
ivorycruncher said:
Somebody correct me if I'm wrong, but as far as I know, there is no known way to recover from modem failure caused by flashing with the Phone button in ODIN. I'm sorry, but it looks you will either have to buy a new phone, or find a way to convince Verizon to give you a warranty replacement.
Posted from my DL09 SuperClean Fascinate with Voodoo
Click to expand...
Click to collapse
but sir, everything works but 3G doesn't. even wifi works. do we call this situation "bricked" ? hmm I put only DI01 modem.tar in the phone button and after pass sign I put the DI01 package.tar in the pda section. only thing doesn't work is 3G network. should I buy another one? I bought this phone from ebay and my carrier is pagepluscellular. so I don't have insurance and no supported carrier.. so sad....
enoch. said:
but sir, everything works but 3G doesn't. even wifi works. do we call this situation "bricked" ? hmm I put only DI01 modem.tar in the phone button and after pass sign I put the DI01 package.tar in the pda section. only thing doesn't work is 3G network. should I buy another one? I bought this phone from ebay and my carrier is pagepluscellular. so I don't have insurance and no supported carrier.. so sad....
Click to expand...
Click to collapse
Do phone calls work? Does anything via the 1X network work? You could try reflashing the DI01modem.tar via PDA, but that would be the only possible fix besides a new phone.
imnuts said:
Do phone calls work? Does anything via the 1X network work? You could try reflashing the DI01modem.tar via PDA, but that would be the only possible fix besides a new phone.
Click to expand...
Click to collapse
oh... If I failed to reflash via pda, nothing happen after then? I don't have to worry about fail via pda right??
Correct. You can't really hurt anything by flashing via turn PDA button.
Posted from my DL09 SuperClean Fascinate with Voodoo
Gunnermike, from here and Android central flashed in Odin using the phone button by mistake. He re-flashed the modem using PDA and reported that everything worked as it should afterwords.
At this point, you don't have anything to loose.
I made the same mistake (select phone instead of PDA) when I tried to install voodoo lagfix. After reading this thread I downloaded the modem.tar file for my version of Froyo and the PIT file. I entered the download mode and through odin I updated the phone modem using the modem.tar file and pit file. It worked like a charm. Now everything is OK. Be sure to remove the SIM card before update.
Thanks a lot for the ideea.
P.S. I used PHONE not PDA when I fixed my modem. And do not forget the PIT file.
Hello everyone,
Upon waking up this morning, I found that my phone was stuck on the (very first) Samsung logo. Before going to sleep, I was already booted and everything was stable.
I attempted to enter CWM recovery, but it would not work. It would continue to show the Samsung logo.
Entering download mode, I see the following -
Product name:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
This is strange, and pretty wrong. My product name is empty, custom binary download is "No" instead of at least "3" (I never have used TriangleAway), and I wasn't using an official Samsung ROM before the problem.
The very first thing I tried was flashing the Siyah .tar file. I get this:
"<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed."
If I attempt to flash a full, multi-part .tar.md5 file in PDA, ODIN v3.04 shows a "There is no PIT partition." error and fails. Re-partition is not ticked.
Therefore, I've tried to flash each of the following, with re-partition ticked:
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
Each of them fail with a "Re-Partition operation failed." error.
If I try to flash a .pit file and the full .tar.md5, I get the same "Re-Partition operation failed." error. The same happens when I try to flash the .pit and Siyah at the same time.
Once a flash fails, I need to turn my phone off and on into download mode again, or else ODIN will stop on "<ID:0/004> SetupConnection.." and not continue for every type of flashing attempt.
The same thing happens for both ODIN v1.85 and v3.04, I've taken my battery in and out, I've tried this on two different computers, I've used every USB port, my Samsung drivers are up to date and Kies it not running in the background.
I've searched Google and XDA for hours, and I'm pretty sure the the problem I need to resolve is the "Re-Partition operation failed." error. However, almost no one on the internet has ever had this error.
The absolute very last abnormal thing I did with my phone was use the app "GetRIL" app as recommended on page 857 of the Siyah thread. The process said it succeeded, but the RIL didn't match the Baseband in the end. My phone was completely functional after, and I don't think the app even asked for root privileges at any point, so I'm not sure if it could have been capable of causing an issue this dire.
Is there anything I can do? I just can't imagine how my phone could have broken itself overnight while charging...
Any help would be greatly appreciated.
Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.
Kangburra said:
Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.
Click to expand...
Click to collapse
CWM is completely inaccessible!
I'll try a service centre after I've tried absolutely everything with this phone... I don't think I'm covered by warranty after rooting (Although they maybe won't be able to tell given how messed up the download mode seems to be right now)
Same problem here!
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:
nicoroldan1 said:
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:
Click to expand...
Click to collapse
If you can't get to recovery then you must return to Samsung.
Kangburra said:
If you can't get to recovery then you must return to Samsung.
Click to expand...
Click to collapse
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?
nicoroldan1 said:
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?
Click to expand...
Click to collapse
I don't know, it would depend on your terms of warranty.
If you are stuck you could try to unbrick it yourself.
Mine woke up to the exact same thing. Sadly I don't have a solution for you, this happened 1 week after being bought so I just had it replaced. I had not modified it in any way nor I tried any repair on my own (no reason to).
Sorry for your phone bro... id still try sending it to Samsung, if it's that screwed maybe they won't try to figure what happened.
Sent from my GT-I9300 using XDA Premium App
I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps
kart_y_26 said:
I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps
Click to expand...
Click to collapse
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:
I would suppose the nand chips are damaged for whatever reasons, which makes a trip to the service center inevitable.
aegixnova said:
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:
Click to expand...
Click to collapse
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app
kart_y_26 said:
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
It's a stock ICS taken from sammobile.
I've tried running ODIN v3.07 on my 32bit Windows 8 tablet, and my 64bit Windows 8 notebook across both 1.5.4 as well as 1.5.5 Samsung drivers, in both XP compatibility mode and default. Nothing.
Windows updates the drivers after my phone enters download mode, so I've tried flashing both before and after the driver download and installation. Same result.
I haven't tried running ODIN v3.07 on my Windows 7 computer (But I have for v3.04), so I'll give it a go later. I think I know what the result will be
I've given up, and will contact Samsung to get the phone repaired by them. I'll edit this post or bump the thread later with details of how the warranty was handled. I'm hoping that the end result will be favorable for me.
Thanks for the help, everyone. :good:
Same thing happend to me :/ Tried to flash PIT partition via odin again and it failed! Official service center voided my warranty. My phone is now at the unofficial service and i am waiting if it can be unbricked! He said if the phone gets to DL mode it should be OK!
Good luck buddy
Sent from my GT-I9300 using xda premium
I took my phone to an unofficial phone repair shop, 'Fonebiz'.
They replaced the entire phone circuit board within the hour, and Samsung was billed due to my phone still being under warranty. I don't know whether they were unknowledgeable of warranty checking procedures, uncaring of warranty procedures, or simply could not tell due to the extent of the phone's brokenness. Needless to say, I lost the contents of my internal SD, but thankfully most things were backed up.
Either way, I recommend unofficial repair centres which can be funded by Samsung, and my few days without the phone really let me appreciate the quality of the product and service I received.
I'm guessing that the problem was either a pure hardware fault, or Siyah kernel's dual-booting functionality messing up how partitions can be flashed to the phone. I'm not placing blame on anything, however.
I'm very pleased with both Samsung and the end result. :good:
I wish the very best of luck to everyone. This seems to be one of the few ways these solid phones can be bricked, and it's heartening to see that it can be resolved under warranty.
hey,
thanks for making this thread.
it is indeed devastating to find that other people experience my same problem and how they needed to replace the phone
i did nothing to my phone, no root, original firmware.
maybe dropped it once or twice but it worked fine afterwards for plenty of time.
last night i went to bed after putting it to charge as i usually do, while it was on and perfectly working.
this morning it was showing the s3 logo (weird thing is that the led was flashing as if the phone was still on and notifying about new emails)
then everything happens as in the OP
- no stock recovery abailable - reboot loop showing only the logo and nothing else
- normal boot stuck only showing the logo
- people haven't been mentioning this but: with the phone completely off, if i connect the charger it shows the battery empty with just the "in progress" circle and nothing else happens..
- download mode accessible but no "product name", and the unseen before "system status: custom"?
- what does that mean? anybod with a working s3 can tell us what they have in download mode? much appreciated
- all the while firmware is "samsung official" and custom binary is "no"
1. are people certain i cannot bring this back to life?
2. can anybody suggest a way to maybe retrieve at least some of my data?
3. warranty is a little tricky - bought on ebay.... anybody claim warranty in this situation? or have any pointers how to go about it?
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair
DorinAlex said:
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair
Click to expand...
Click to collapse
http://www.freesamsungrepairs.com/
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
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 !