First off, I'm trying to get my mesmerize flashed over to verizon. I realize I could sell and buy a fascinate but wheres the fun in that?
Now for the problem. I have been trying to get this device into DIAG mode successfully for a couple days now. Depending on which rom I flash to it (stock roms) I am able to get to the phoneuti and place the USB into MODEM mode, cdmaws will connect to the port but then does NOT read anything on the other end.
Currently running a Fascinate VZW froyo rom, I type in **87284 it opens PhoneUtil and I am able to switch both UART and USB to MODEM. I can connect to the ports with both software but QPST reads NO PHONE and cdmaws can't find the phone. At one point I had one of the stock mesmerize roms on there (can't remember which) cdmaws was able to find the phone but it said it was in mode "DOWNLOAD" and wouldn't read or write anything.
Any thoughts? I've searched many forums and websites and have not encountered any problems where one was able to supposedly get into diag mode but not be able to read the phone through the software.
So I reflashed this with the mesmerize EC_10 official FROYO rom. I connected to cdmaws, read the phone and it says Device mode is "Download". I click OK and it says it's ready. Whenever I try to read anything it wont let me. Try to enter SPC 000000 and it says it didnt accept and makes me wait 10 seconds before anything else. The samsung i500 16 digit password is not accepted.
This is the closest I've gotten to being able to flash this phone so far. Anyone else have similar situation?
added the COM ports in QPST and it says NO PHONE. I'm stumped.
I also own a fascinate that I was able to plug in and just do whatever I wanted. Didn't even need to put it into DIAG mode.
Related
Hi,
I installed cynogenmod 7 on my captivate, but due to some issue regarding TV out I tried to uninstall it. I used one-click stock 2.1 ODIN to go back to stock. But now my samsung captivate is not working at all. I am using charged battery, but the phone does not start at all. It only goes into download mode and nothing else. ODIN hangs at factoryfs.rfs. I have tried almost all methods on xda forum and tried almost everything from google searches. Nothing is working. I used Win 7, Vista and XP and 2 different computers. The phone is not recognized by the PC many times.
I talked to someone and he said that my phone has hard-bricked. And it needs advanced soldering and a special box to repair the phone. Can anyone help me, please?
Thanks!
you might be able to hard reset it. unless you totally effed the EEProm. which the only way to fix is to put it into Developer Mode and try to put a Stock EEprom back on it. (or find the ClearCMOS pins and short them)
chalk this up to a learning experience, better to learn a little at a time than to just dive to the bottom of the ocean with no recovery.
do you even know about the hardware in it? if you did, you could grab the developer tools. (I like QPST and QDXM myself)
backup the important stuff, just so in case you totally brick the thing.
I do not know anything about the hardware in my samsung captivate. The phone connects to the computer some times. Device manager shows Samsung USB Component Device and Samsung Mobile Modem #2 in Win 7 64bit. But QPST, QDXM and adb devices do not recognize the phone. ODIN recognizes it but now ODIN is stuck at <ID:0/005> File analysis..
Since the phone does not start at all, I can not hard reset it. Nor can I go into developer mode. It only goes into download mode saying "Do not turn off target!".
Do you think there is a way to repair / unbrick the device? Can you guide me through the steps, please?
Have you tried taking out the battery and the sim card and then putting the battery back in and using the 3 button method to get into download mode so odin will recognize you? Or have you tried buying/making a JIG?
I've tried a few other forums but haven't got any replies, I guess since the Galaxy 5 isn't such a popular device. I figured if there's anyone who can help me they will be here though.
I wanted to put CWM on it so I could get a CM7 port on. Unfortunately it's just about impossible for it to get detected on USB. I've installed Kies (and even the generic USB drivers found in the SDK). In 2 days I only got it to connect once, and then I went and bricked it.
The one time it finally connected I ran Odin and tried loading CWM onto it. It still hadn't finished after half an hour so I figured it ended with an error that was never displayed. So I unplugged it and as expected - brick! I can get into download (upgrade/firmware) mode so I think it can be fixed if I can get CWM on it (and just install the CM7 port I had originally intended to put on).
Problem is I cannot get the darn thing to connect! to my computer I've tried two separate PCs, one running Window 7 x64 and another running XP x32. Is there a a certain process of connecting things? I haven't ran across anyone making mention of one.
Has anyone else experienced USB problems like this with Samsung phones? Would it even be possible to flash CWM on after it's been bricked like this? When I boot (normally) all I get is an image showing a phone and a PC with and exclamation error connecting the two. Please help!
Try to look for stock firmware on the forum.xda-developers.com and flash via ODIN. You need to be able to put the phone into download mode, so maybe get an USB jig. That should do the trick. Odin has to recognize your phone. First of all right click on the ODIN executable and select "Run as administrator" on windows. Plug the phone in the DL mode and wait until it appears as active in Odin. Then flash the ROM and pit file. (Don't use ODIN one click). If ODIN does not recognize your phone try a different USB port or reinstall Kies. The Kies trick was which I used and it was able to recognize my phone.
Thanks, martin0176. I can still manage to get the phone into download mode - it's getting recognized by a PC that's the problem.
Could you tell me more about the pit file? I only have an ops file.
Try a different cable. I was having the same problem on the Samsung Continuum and it turned out that the cable was working for power, but not for data.
Well I finally rooted my sidekick and went to backup the stock rom via rom manager and it rebooted and never got past t mobile sidekick boot screen so I downloaded odin the pit file and the tar but when I put my phone into download mode i cant get it to recognize the sidekick when I plug it in it just says unknown device and i have the driver down loaded any help please
Windows can be picky about drivers sometimes.
I recommend uninstalling the driver, opening regedit, and manually deleting any remaining registry keys associated with the Samsung drivers. (This will take you some time.)
After that, reinstall the driver and try again.
I think you may need to google some of what I said here to get it done. But, you can do it if you take some initiative.
well i tried deleting kies and reinstalling it whitch i thought it was the driver if im wrong or theres a more direct driver can someone tell me when i plug my sidekick in i get usb device not recognized message
uncapj said:
well i tried deleting kies and reinstalling it whitch i thought it was the driver if im wrong or theres a more direct driver can someone tell me when i plug my sidekick in i get usb device not recognized message
Click to expand...
Click to collapse
Ok. Give me some information.
I need to know what you installed as a driver. I need to know what Odin you are using. I also need to know where you got your information; what threads did you search for and read?
Is Windows complaining when you plug the device in or is the Odin program just not seeing your device?
When we do get your device back, also consider the risk/reward here. These customs aren't really offering the earth shattering things you might be hoping for. We're geeks and we are splitting hairs when we talk about improvements. The truth is, the final official KJ2 is a reliable and stable OS on its own. (If it wasn't, developers would be basing their work on older versions.) It's just something to think about...
Anyhow, get some more info out here and we'll help you Odin back to stock. After that, it's up to you.
well i got a drive from softpedia as well as kies and i searched various forums and topics im using windows xp sp3 and odin 3 as well as got the pit and tar files from lins on this site i
windows is the one that wines when i plug the phone in it says unknown device and no drivers for device found
You should have downloaded a Samsung USB driver for Mobile Phones. At one point, we were using Vibrant drivers to access the phone. Did you get real Samsung drivers for this phone?
You do NOT want to use Vibrant drivers.
Also, let's not rule out a hardware problem.
If you are rough with your phone's USB port, you can bend/break a pin in there. You could have a bad port.
If your phone isn't working like a USB pin drive on any (and every) computer you try, you may have a problem.
You should also check your cable and the physical port on your computer.
i got the kies from the samsung web site it was under the sidekick model nuber and showed a picture of my phone also i believe the softpedia driver was probably the vibrant driver
FYI, Kies only works if can get booted. We won't be using it until we can get a proper recovery of some kind.
What is happening? Is it just sitting there and vibrating over and over? Or does it appear to be rebooting?
Does it keep showing the t-mo logo flashing on and off the screen? Or is it just sitting there vibrating?
If you seeing the logo and the device is rebooting, you must use the Odin tool. If it is just hung up in the boot process, you can use Android Commander to get into clockworkmod.
I'm going to upload you some files. I'll private message you a link to download them.
We'll close out our public discussion here.
Hello everyone! I'm new to the forums as a member, but used this for info since a few years back. Ok, so i've spent the past week trying to unbrick a samsung galaxy s2x (t989d on telus or koodo) and it seems alot of people are having trouble with this model. I've brought back another one identical to this one before, but it was only softbricked, so i could still enter download mode and use odin and just searched my butt off to find original roms and all and wound up bringing it back to life.
This one though... It's hard bricked with the dreaded QHSUSB_DLOAD mode. Found drivers for it to use it in windows, found QPST 2.7 build 422 and tried that to no avail since QPST always tells me the HEX files have a scrambling method which cannot be determined (even with it's own hex files that come with it, and tried on 2 different computers, one x86, one x64) so still stuck there. Tried ADB in windows but it never wanted to work in any way, also tried ADB with ubuntu linux but the devices list always ends up empty no matter how hard i try and what i change, even with other phones that are not bricked it won't list them at all... Also tried to use the SD card method and push an image on it to try and boot off the external SD using original rom from odin i have found, but have no idea exactly which image i need to push into the SD or if it need modification in any way to be able to boot like that, or if even the t989d does in fact truly support external SD card booting.
Before anyone says:" Ya you need to JTAG that, it's the only method..." First, no one around here has anything to jtag with and i don't want to cross the border to get it done, second this is the kind of job i need to get done without spending any money if at all possible cause phone is not mine and client on a restricted budget. Now i know this CAN be done as alot of people here and there were able to fix their phone that were on the same qualcomm series chipsets. I just need some help to do this on this phone, and any SERIOUS help would be apreciated.
I have access to original rom file for the particular MC4 version i have in hand, i have original rom file for another version of the 989d which i got to unbrick the first t989d a friend sent me, i have a NVbackup qcn file pulled out of my firends working t989d, and i also have a full backup made with TWRP on my friend's working phone. Wanted to pull out a better backup using darkspr1te's Brixfix-2-1 tool but like i said, in windows ADB wont work in any way even with python installed and all that, drivers also installed, but ADB isn't a recognised command. And in Ubuntu, no way to list any phone at all, even if i installed all the ADB files, JDK, did the whole rules file, changed attributes to the rules file, did the .ini file, and killed and restarded hdev and server... So i'm kind of at witts end right now, plus i've been sick and had a major headache for the past 2 days, and spent so far around 38 hours on this phone plus my normal job this week... So ANY help would be GREATLY apreciated, and i will gladly use this experience to help out the community and help put out a tool or whatever to unbrick all these damned t989d
Just le me know if you need any more info or files to help out and i will gladly do all i can to comply
Thank you in advance to this great community
Nobody?? not even a troll ?? pretty sure that not even a mouse is stirring
Update: I have finally been able to start to get somewhere with this. I was able to extract most of the MBN files needed for QPST from the stock rom, and created my own partition.mbn out of a PIT file i had from a previous t989d. And now i get the phone to accept download and don't get errors for those files, but it stays stuck when sending reset packets. So my guess is that either the partition.mbn file isn't good, or the mprg8660.hex file i used to substitute and test isn't 100% compatible with the MSM8260 chipset. I tried all i could but never was able to find the real mprg8260.hex file anywhere. So if anyone has mprg8260.hex and/or a working partition.mbn for the t989d, i would be grateful to get those so i can continue troubleshooting this and get it working. If you want any of the MBN files and everything i have so far, just send a PM or reply to this thread and i will gladly upload for you.
Don't use the 8660 hex, it might make it go out of DLOAD or SD mode and you'll get a HS-USB 9005 state instead of a HS-USB 9008 or a HS-USB 9006 state, and then you'll need to manually flash it while it reboots every 5 secs in factory recovery mode. Not fun stuff. Also, if you're playing in QPST, make sure you using 2.7.411 or later. And be careful. there is a 2.7.422 that is actually an old version with a Trojan floating around.. Also, be warned, If you don't know what your doing in QPST, you can make things a lot worse.
Lord Zog said:
Don't use the 8660 hex, it might make it go out of DLOAD or SD mode and you'll get a HS-USB 9005 state instead of a HS-USB 9008 or a HS-USB 9006 state, and then you'll need to manually flash it while it reboots every 5 secs in factory recovery mode. Not fun stuff. Also, if you're playing in QPST, make sure you using 2.7.411 or later. And be careful. there is a 2.7.422 that is actually an old version with a Trojan floating around.. Also, be warned, If you don't know what your doing in QPST, you can make things a lot worse.
Click to expand...
Click to collapse
So far i had no problems using 8660hex, only stays on 9008 download mode so far, even after it's supposed to pop back to diag mode. And i AM using 2.7.422 but it doesn't seem to have a trojan or anything or else my anti-virus would've told me, but still kinda looks like an old version since most of the devices supported are the old ones and has nothing newer than 7XXX series on protocol modes in the settings menu. But like i said, so far i got it to respond with the 8660 and accept the mbn files, but still no change yet, still wont reset/reboot, still wont turn on or anything, just stays in download mode seen as a 9008. So i'll check to find 2.7.411 to try it out and see if does anything else. Even if it would reboot every 5 secs in factory recovery mode it would still be a step further than i am now right now it does nothing and stays in download mode. But thanx alot for the info!!
Suraido said:
So far i had no problems using 8660hex, only stays on 9008 download mode so far, even after it's supposed to pop back to diag mode. And i AM using 2.7.422 but it doesn't seem to have a trojan or anything or else my anti-virus would've told me, but still kinda looks like an old version since most of the devices supported are the old ones and has nothing newer than 7XXX series on protocol modes in the settings menu. But like i said, so far i got it to respond with the 8660 and accept the mbn files, but still no change yet, still wont reset/reboot, still wont turn on or anything, just stays in download mode seen as a 9008. So i'll check to find 2.7.411 to try it out and see if does anything else. Even if it would reboot every 5 secs in factory recovery mode it would still be a step further than i am now right now it does nothing and stays in download mode. But thanx alot for the info!!
Click to expand...
Click to collapse
hi,
were you able to resolve this ? I have the Skyrocket (I727R) and i was wondering if you could share the files and possibly how you fixed this problem,
any help would be appreciated.
thanks
Hello everyone who may still peruse this section of the forums. I know I have a low post count, but that's cause I normally find answers to my problems by reading... Today is a struggle.
I have recently aquired a Sprint Galaxy Note Edge, it has the n915pvpu5dqi5 firmware installed.
I have followed directions from a couple of different sources and have been able to get freezas Notedge beta rom with the Emotion kernel installed and working, however I'm still limited on LTE bands my phone will connect to.
My intention, and I don't know if it is possible or not, is to use QPST and QXDM to modify my NV memory.
I have reverted back to the original n915pvpu5dqi5 firmware, and I am trying to get into diagnostic mode for QPST.
I used *#66336# and set the CP Debug level to CP RAMDUMP ON.
After reboot I used ##3424# went to Qualcomm USB setting and set RNDIS + DM + MODEM.
When I go into QPST to backup, (using my MSL in the box titled SPC) it starts to Backup NV memory from phone, and it will get to 18% before giving an error that says "Could not communicate in Diagnostic Mode."
Can anyone advise me on how to get into diagnostic mode or if it is possible with this phone being upgraded to the latest bootloader(QI5), or is there another kernel out there other then stock that will allow me to get into diagnostic mode (I'm told a lot of the custom ones cut it out, why? Over my head...) to edit the NV memory and unlock other lte bands
what is QPST ? and what are you trying to accomplish?