Related
Hello
I am new to this site and was hoping someone could give me a some assistance. I recently used Mirage 1.8 to update my i780 to WM6.1. the eboot and the PDA installed just fine but I can not for the life of me get the phone and phone boot loader update to install. I am using the i780 Phone Upgrade ROM DXHH1 file, found it on this site. After I click detect and then power up the phone I hear the connection sound on the computer that the device is recognized and then the Mirage software starts its thin. Then I hear the disconnect sound and then Mirage goes through the Kw.kim retry steps. And the phone shuts down.
I have tried the modem drivers but I seem to be having a problem with them. I downloaded and installed this file "Samsung_CDMA_modem_4.34". When I connect the Phone it shows that it found the i780 USB device but then it begins to install Samsung Mit's USB Device and then it fails to install the device properly...so it does not complete the installation properly. How do I go about installing the driver properly? I do not see it on the list of devices in system manager, where can I manually update the driver and were do I find the file once the software is installed. Or do I need to try something else?
So I just tried a WM6 Eng rom and it all installs fine but just like the WM6.1 I can not get the phone to turn on in the wireless manager. What do I need to do to get the phone to turn on?
Thank you.
DXHH1 is meant for Asian version of i780, what's yours? for which country?
And can you please tell us if you are using XP SP2 or 3 and not Vista because flashing in Vista with Mirage Updater will NEVER work even if you have the right driver.
Try this. Uninstall the Samsung drivers frist and then reinstall it after reboot.
Then instead of using a separate DXHH1 Phone only image, download a full Russian PUHE1 IMG file (you can search for this easily in this forum) and flash everything (eBoot+Phone+PDA). If you can flash the Russian IMG successfully, you will be able to boot up your i780 in Russian langauage and only after that you can try DXHH1 IMG (I mean the full IMG rom and not individual files)
Good luck
EFN said:
DXHH1 is meant for Asian version of i780, what's yours? for which country?
And can you please tell us if you are using XP SP2 or 3 and not Vista because flashing in Vista with Mirage Updater will NEVER work even if you have the right driver.
Try this. Uninstall the Samsung drivers frist and then reinstall it after reboot.
Then instead of using a separate DXHH1 Phone only image, download a full Russian PUHE1 IMG file (you can search for this easily in this forum) and flash everything (eBoot+Phone+PDA). If you can flash the Russian IMG successfully, you will be able to boot up your i780 in Russian langauage and only after that you can try DXHH1 IMG (I mean the full IMG rom and not individual files)
Good luck
Click to expand...
Click to collapse
You can flash using VMWARE (trial available) and install WinXP inside the virtual machine.. that's how I flashed your V4
disable USB connection in activesync...
People, here is a link to the Samsung modem driver:
http://fus.samsungmobile.com/i600/Samsung_CDMA_modem_4.34.zip
Thanks for the replys.
My i780 is from France and it had the French ROM but not any longer because I forgot to back it up.
I have XP SP3 on my computer.
I have uninstalled the drivers as well as activesync. Restarted computer. Then installed the drivers suggested by Mochan above. Then installed activesync.
Connected the i780...all of the drivers were installed properly (Samsung MITs device found and installed and i780)
Opened activesync on computer and unchecked "allow usb connections".
Reconnected the device and powered it up and the computer found new device and installed "Samsung Mits".
I downloaded both the Russian and the Italian full Rom updates.
Opened Mirage v1.8 and selected first the russian Rom for edoot+pda+Phone selected detect.
Plugged in phone to usb and all of the steps worked up till the phone image. It says on the phone "phone image downloading" and on the computer it shows "switching usb to phone" and "Downloading phone".
Then for some reason the phone shuts down automatically and stays powered off.
Then Mirage brings up the message "Attempting to open com 0..." KW.KIM Create Retry (25) etc...Finally Download failed.
I have tried this with the Russian, Italian and English ROMs available. I have tried it with the following settings on the phone on and off:
- Emercency mode
- Regular restart of phone
- Reset phone by holding Red Green and Power button together.
- Removed the battery completely and restarted.
- Restarted with Sim installed and with sim removed.
- Settings/Connections/USB connection mode switched from Activesync to Mass storage and then switched back to Activesync.
- Settings/System/USB to PC "Enable advanced network functionality" selected and then deselected.
What am I missing?
Why does the phone shut down during the Phone.bin file download and not complete the downlad and install? Is there some setting that I am missing or a com port that I need to establish so they will communicate properly.
Everything seems to work on the phone even without the phone.bin file installed. The problem is that when I try to connect to wireless manager and enable the phone nothing happens and it does not register the sim card. Also In the Settings/Connection/USB connection mode I only have listed Activesync and Mass Storage. There is no listing for modem (I noticed in one of the other posts that they had the option to select modem). Is there something I need to do to enable this option.
Sorry for the long rant but wanted to make sure everyone had all of the info.
Thanks
my brother had a similar problem with his i780 - the phone refused to be recognised when flashing the phone.bin, the pda and eboot flashed perfectly no problem. We realised it was a problem specifically with the device as my i780 flashed all three parts fine.
In the end he got the device replaced which flashed fine!! Maybe there are a few dodgy phones out there! My advice would be to try and find a French rom and flash your device with that. Hopefully the rom will be compatible with the phone part of your phone!
Just downloaded the French rom from an xda thread. It would not load up under the eboot+PDA+Phone option but it did load under the PDA option in Mirage. Still can not turn on the phone under wireless options on the i780.
The phone/radio worked fine with the original rom. Once I did the first rom update to switch from french to english only using the pda update I lost the phone/radio functionality. So I dont think it is a hardware issue rather a software issue. For some reason it is not making the connection. I just dont know what it is. Could it be something with mirage? Why would the phone shutdown during the software install?
so looks to me that the problem is with the phones modem set up. I do not have it listed as an option for usb connectivity. Is there a reg edit or some other steps I should take in order to get the phone to set up the usb modem?
Thank you.
I still have had no success with my problem, has anyone come across any info about an official i780 update? Or does anyone know what I can do to get around my proble to install the phone rom? Thank you.
I have the same problem with apetrovic. I have used with phone off, which is a big pain. Just like a PDA with no phone. This is all happened after flash Russian image. The original rom was German. my i780 simply turns off after downloading and ends up with no port created.
Any clue, please.
I have downloaded your suggested driver, run the setup, restarted the computer and connected the i780 in Emergency mode with activesync disabled and the Computer keeps installing Samsung MITs Drivers and not the CDMA Drivers you supplied. I used the Add Hardware wizaer, interrupted the install process when the i780 is first connected and even tried the update driver option and I can not install the CDMA driver I always get the error that "The specified location does not contain information about your hardware." How do I get the CDMA drivers you provided installed and not the MITs?
Thank you
apetrovic said:
I have downloaded your suggested driver, run the setup, restarted the computer and connected the i780 in Emergency mode with activesync disabled and the Computer keeps installing Samsung MITs Drivers and not the CDMA Drivers you supplied. I used the Add Hardware wizaer, interrupted the install process when the i780 is first connected and even tried the update driver option and I can not install the CDMA driver I always get the error that "The specified location does not contain information about your hardware." How do I get the CDMA drivers you provided installed and not the MITs?
Thank you
Click to expand...
Click to collapse
Yes, I have also tried to intervene the installation of the MITs driver to install the CDMA driver, and Windows XP sp3 says "The specified location does not contain information about your hardware." So, I could not install the CDMA driver.
I do not know how to get rid of the MITs driver completely, so that Windows XP does not even recommend this driver when I install the CDMA driver. Windows always complain the MITs driver is not signed.
I wonder if those who have successfully installed the CDMA driver also see the MITs driver in the device manager when i780 is connected to PC under the emergency mode. This looks important for the moment for you and I in resolving the issue.
Anyone who can tell us what driver is on when i780 is connected to PC under the emergency mode? Thanks in advance.
I think the problem for us is that we have lost the modem option on the i780 under settings-usb connection mode. Since we do not have the option the computer will not download the drivers. The drivers that are downloaded are prob ok because they are intended for USB sync but when you go to the device manager there is no i780 modem installed under modems...so my theory is that the computer is not installing the modem driver because it is not finding a modem on the phone. So we need to somehow get the modem option installed and available on the phone and then the computer will install the drivers and then we can properly install the wm 6.1 phone update. please let me know if you find anything out.
apetrovic said:
I think the problem for us is that we have lost the modem option on the i780 under settings-usb connection mode. Since we do not have the option the computer will not download the drivers. The drivers that are downloaded are prob ok because they are intended for USB sync but when you go to the device manager there is no i780 modem installed under modems...so my theory is that the computer is not installing the modem driver because it is not finding a modem on the phone. So we need to somehow get the modem option installed and available on the phone and then the computer will install the drivers and then we can properly install the wm 6.1 phone update. please let me know if you find anything out.
Click to expand...
Click to collapse
That's an interesting theory noticing the messages in the mirage loader.
"Switching USB to PHONE..." and then
"PHONE-Switching USB to PHONE...
PHONE-Automatic driver detection failed..
PHONE-Attempting to open COM 0...
PHONE-Port Create failed...: COM 0"
These clearly look related to the modem meaning we should be able to see the device under modem in the device manager of Windows XP.
In fact, my i780 got the phone rom flashed just for once successfully when I flashed the russian image (eboot, pda, and phone, altogether). I don't know what mysterious thing happened here, and then I have never succeeded back again in flashing the phone rom since then. My phone used to work no problem before this. I just wanted to have windows mobile 6.1, and now I know I should have clicked "PDA" in the mirage loader instead of "EBOOT+PDA+PHONE".
Well this is becoming more and more difficult!! I contacted US Samsung support to reflash my i780 and they can not do it becuse the phone is not sold in the US and then I contacted Samsung France and they cant flash it because they can not ship it back to the US. I need to have an address in France for them to ship it to. So now stuck with a phone that only has PDA functions.
If there is someone out there who can help me I would appreciate it. The problem is that I used the Roms available on this site to upgrade to WM6.1 and I lost my phone/radio function. Now my phone is stuck in flight mode. I was able to install the eboot and the pda bu the phone portion will not install. I followed the directions and installed just the PDA portion initially and it killed my modem/phone/radio function. Before the phone worked and modem was listed as an option under settings usb connection mode...now it is not.
I have tried to install a French ROM (because it was purchased in france)and that did nothing.
So if there is anyone out there that can help guide me in installing a functioning rom WM6 or 6.1 I would greatly appreciate it.
apetrovic said:
Well this is becoming more and more difficult!! I contacted US Samsung support to reflash my i780 and they can not do it becuse the phone is not sold in the US and then I contacted Samsung France and they cant flash it because they can not ship it back to the US. I need to have an address in France for them to ship it to. So now stuck with a phone that only has PDA functions.
If there is someone out there who can help me I would appreciate it. The problem is that I used the Roms available on this site to upgrade to WM6.1 and I lost my phone/radio function. Now my phone is stuck in flight mode. I was able to install the eboot and the pda bu the phone portion will not install. I followed the directions and installed just the PDA portion initially and it killed my modem/phone/radio function. Before the phone worked and modem was listed as an option under settings usb connection mode...now it is not.
I have tried to install a French ROM (because it was purchased in france)and that did nothing.
So if there is anyone out there that can help guide me in installing a functioning rom WM6 or 6.1 I would greatly appreciate it.
Click to expand...
Click to collapse
I didn't know that you are in the states causing the problems. Too bad. I have two questions for you to clarify the problem.
Before the phone worked and modem was listed as an option under settings usb connection mode
Does this mean you could see the third option called "phone" in USB connection mode in i780? Currently there are only two modes, which is ActiveSync and Mass storage.
I was able to install the eboot and the pda bu the phone portion will not install. I followed the directions and installed just the PDA portion initially and it killed my modem/phone/radio function
Does this mean that upgrading only PDA may brick our i780 not necessarily with eboot and phone? Because I keep thinking that, it may be eboot I updated from this site not turning on the modem in i780.
Sorry about your and my problem. Thank you for your feedback.
Does this mean you could see the third option called "phone" in USB connection mode in i780?
Yes there was a 3rd option but it was "Modem".
Does this mean that upgrading only PDA may brick our i780 not necessarily with eboot and phone?
When I first used the upgrade I used the i780 PDA portion only, as suggested.
apetrovic said:
Does this mean you could see the third option called "phone" in USB connection mode in i780?
Yes there was a 3rd option but it was "Modem".
Does this mean that upgrading only PDA may brick our i780 not necessarily with eboot and phone?
When I first used the upgrade I used the i780 PDA portion only, as suggested.
Click to expand...
Click to collapse
Sorry but I think that there is a bit of confusion.
During the normal use of the phone, you never see a modem in the device manager.
You can see the phone as lan card (used by activesyc), as a different lan card (when internet connection sharing is enabled), or as storage device (if you enable the related function in the control panel).
No modem.
During the flash process of the pda section the phone is still seen as a lan card.
ONLY when the phone sectin is flashed the phone switch to phone/modem mode.
Going to the problem you must launch the phone flash process and ceck what happen in the meantime in the device manager.
Is a question mark present ?
There is a unknown usb device ?
And if is the case what is the pid and the vid of the device ?
The Solutor said:
Sorry but I think that there is a bit of confusion.
During the normal use of the phone, you never see a modem in the device manager.
You can see the phone as lan card (used by activesyc), as a different lan card (when internet connection sharing is enabled), or as storage device (if you enable the related function in the control panel).
No modem.
During the flash process of the pda section the phone is still seen as a lan card.
ONLY when the phone sectin is flashed the phone switch to phone/modem mode.
Going to the problem you must launch the phone flash process and ceck what happen in the meantime in the device manager.
Is a question mark present ?
There is a unknown usb device ?
And if is the case what is the pid and the vid of the device ?
Click to expand...
Click to collapse
I stumbled upon a website that had an image that showed a modem in both the device manager and the usb connection mode areas...I have looked for it to post the image but I dont know where to find it again...starting to get lost from all of the info I have come across trying to fix my phone...getting confusing now.
Anyway, here is what happens in device manager when I do the following:
-Activesync disabled - i780 in emergency mode - Samsung MIT's USB Device listed under Windows CE USB Devices
-Activesync disabled - i780 normal - 1st before WM6.1 is running it shows Samsung MIT's USB Device listed under Windows CE USB Devices. Then that goes away and windows mobile based device shows up under network adapters.
- Activesync enabled - i780 emergency - Found new hardware installs without error...look in device manager and there is a yellow exclamation point next to Samsung MIT's USB Device under Windows CE USB Devices.
- Activesync Enabled - i780 normal - 1st before WM6.1 is running it shows Samsung MIT's USB Device listed under Windows CE USB Devices. Then that goes away and windows mobile based device shows up under network adapters.
Now during all of the above steps there is never an unknown USB device listed. Also I tried using mirage with these same above settings and each time I get the notification that usb device not recognized and then the phone suts down and I get the KVM com port messages, and it fails to install the phone rom.
I would like to provide you with the pid and vid but I don't know what pid and vid stand for. please let me know and I will get it for you.
Thanks for the help.
So.... Can anyone confirm if the steps are the same like s3?
Shouldn't be in this section, you should know that...
Sent from my SPH-L900 using Tapatalk 2
Thread moved to Q&A.
can you do this without rooting?
No need for root to repair.
As long as the default samsung password works, it should be the same.
But I don't have my phone in hand yet. So I cannot confirm if default password work
So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns
trim81 said:
So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns
Click to expand...
Click to collapse
Trim, how were you able to get in and repair MEID? I used *#7284# to set the UART and USB to modem, but once I do that, Windows won't recognize the device. I do see a notification about "Qualcomm CDMA Technologies MSM" but no driver can be found.
If I set UART/USB back to PDA I can get Windows to recognize the device using mskip's device drivers.
trim81 said:
I had to manually insert everything in qpst.
Click to expand...
Click to collapse
by that you are referring to the data profiles, right? but how did you get your ESN allowed on boost, were you able to have customer service do it for you or did you actually spoof the ESN?
##3424# use that ibstead
After youre in everything is straifht foward
trim81 said:
##3424# use that ibstead
After youre in everything is straifht foward
Click to expand...
Click to collapse
What version of QPST are you using? I have build 378 and it's only good enough to establish the com port for QXDM. If you have a more recent version could you share it with us?
I'm not at home now... But look into the s3 forum, the repair method is the same, I used alpineman method.
But this phone is easier, in that no dfs is needed... Everything is repairable with qpst.
Like mentioned tho. I'm not sure if the towers or down or not.. But it will never take an ota activation both via profile 0 or wifi.
I ended having to input the settings manually via qpst
I won't go into spoon feeding, and step by step, it's already published - - look into the galaxy s3 forum
I used the same program versions as that thread
Edit
I used qpst 2.7 build 378
Can someone with knowledge please help create a voicemail. Apk hack for boost?
Still having problems
trim81 said:
Edit
I used qpst 2.7 build 378
Click to expand...
Click to collapse
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.
Chanman said:
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.
Click to expand...
Click to collapse
Yes!!! I did it. I thought I would share what worked for me in hopes that this will help others.
I ended up using *#7284* and then putting UART and USB both on MODEM. As I mentioned in my previous post, this causes the device to be detected as "Qualcomm CDMA Technologies MSM". I had to install a specific generic Qualcomm driver, which I have included in this post. After that, since I was only able to use QXDM/QPST/DFS to write the voice specific settings and HA profile (not passwords), the thing that ended up working for me was CDMA Workshop's free NVItem writer. Using this tool I was not able to read the crucial NVItems (466 and 1192), but I was able to write them. I did a byte-for-byte identical write, cloning the NVItems from the original phone (which I was able to read from). After the tool indicated the items were successfully written I rebooted the phone and everything worked!
guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.
I used all drivers and programs in the galaxy s3 post.
Follow that guide
iwin2000 said:
guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.
Click to expand...
Click to collapse
The driver I included in my post is a Win32 driver only. If you have Windows 7 64-bit it won't work. I had to use this particular driver on a 32-bit Windows XP machine. Sorry for not including that information in my post. You might be able to make a virtual machine to get the driver to load. I wasn't able to find a 64-bit Qualcomm CDMA MSM driver.
Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.
iwin2000 said:
Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.
Click to expand...
Click to collapse
Happy this worked for you. I believe this is the standard way to get into the phone (these instructions are all over Youtube and the S3 forum). The reason why I had to do things differently is that when I tried that approach, even though the devices show up as "Samsung" without any errors in Device Manager, QPST and DFS show "no phone" or can't connect to the port, even though it's there. Maybe I just got unlucky, or you got lucky, or both
So I'm playing with the brand new Sprint S3 with LJ7 stock rom and is stuck at the very first step. Managed to get the COM port opened in the PC for Samsung USB diag mode, however, the DFS 4.0.2 and QPST failed to connect. I can choose the right port to open in DFS, but whenever I try to read from the phone, it shows researching device forever, and I'm certain the spc code is correct (got from the app getmymsl, and I could use it to edit the data file). In QPST, there is no device listed under that COM port (normally you should see the phone listed as SURF****)
Searched and followed this instruction: http://forum.xda-developers.com/show...7&postcount=14 but still not working for me.
Just now I tried install the samsung usb driver and DFS 4.0.2 in a freshly installed windows 7 (64bit) machine, so the only COM ports installed/opened are the samsung's, but still the same symptoms.
I've heard people talking about downgrade ROM and radio for those software to work, but I also saw people directly using DFS for the newer ROM. What did I do wrong then? Please help.
BTW, I dial ##3424# to bring out the diag mode panel, and tried different combinations such as:
Modem / dm+modem+adb
PDA / dm+modem+adb
modem/ rmnet+DM+modem
pda/ rmnet+DM+modem
all gave me the same issue: having the COM port opened but the device could not be recognized.
However the phone was recognized fine as a media device.
procter said:
BTW, I dial ##3424# to bring out the diag mode panel, and tried different combinations such as:
Modem / dm+modem+adb
PDA / dm+modem+adb
modem/ rmnet+DM+modem
pda/ rmnet+DM+modem
all gave me the same issue: having the COM port opened but the device could not be recognized.
However the phone was recognized fine as a media device.
Click to expand...
Click to collapse
Try doing a factory reset. I find that after you flash the phone once using ##DIAG#, you won't be able to flash it a second time after the firmware upgraded. That's just been my experience though. You would still be able to see the port, but it won't read/write. Instead use *#PATH# instead.
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.
Hi all,
I got given this Tab3 because the smd power socket connection guts were physically broken inside socket.
Fitted new power socket (I'm an electronics repair engineer by trade) and checked all pcb (printed circuit board) tracks leading from new fitted socket to ensure there were no hidden breaks ...... new socket refit was 100% successful .....with no solder shorts / bridges and no broken tracks leading to mainboard.
I left Tab3 on charge overnight and next day switched Tab3 on only to be greeted with dreaded .PBL and .PIT failed issue.
After extensive (days!) research I gathered together all necessary firmware and tools and decided that its an easy firmware fix if flashed to an original Samsung SM-T210 UK firmware.
(Please note I dont know past history of this Tab3 .... I dont know if it was rooted / upgraded firmware etc ..... I doubt it though as it belonged to a 7 year old)
Big issue ..... Odin flash tool won't show coms port connection on PC via USB (have tried 3 different laptops one with XP, one with Win7 32bit and another with Win7 64 bit. I've installed / uninstalled / reinstalled multiple Samsung usb drivers that were verified to work with my Tab3 SM-T210 model on each PC .... no joy. Even installed / uninstalled / reinstalled Kies from Samsung .... still wont connect when Tab3 is in download mode. Have kept PC device manager open and nothing appears in device manager. Also have tried 6 different makes of Usb A to micro Usb cables. Have disabled all antivirus, UAC, firewall and Win defender etc ... still no go!
When I go into download mode (power + Vol- +Home buttons) a warning screen does appear BUT it only shows right hand side of graphic warning ..... left hand side is totally grey from top to bottom. (LCD screen is not faulty as it displays full screen info on failed .pbl / .pit flash memory checks) When I then select Vol+ this vertical half graphic info and half grey screen disappears just leaving the backlight on .... which I assume means Tab3 is in proper download mode?
I can go to all recovery modes which allows me to factory reset and delete user cache etc .... it seems to go through the proper routines of reset but upon restart .pbl and .pit failed error in red memory check list is still there.
I can also try and flash firmware file from external sd micro card .... Tab 3 recognises firmware OK and shows Install ..../SD, but then after approx 5 minutes it restarts to failed .pbl /.pit error list again.
Apologies for long post, but from reading above issues can anyone please confirm ....
1) Is half graphic normal when going into download mode? .... or does this point to a previous incorrect or unfinished flash issue?
2) I have downloaded proper .pit flash (LT02) file and original firmware flash for my Tab3 ..... can I flash this any other way other than using Odin ....eg is there any bdm flash method (direct hard wired) flash method to motherboard from external programmer ....like they use for car ecu flash recovery?
3) As I dont know exactly whether Tab3 was rooted / flashed with wrong firmware / incomplete flash upgrade, is there a software tool that can attempt to list what firmware is on my Tab3 at present?
4) I can get into ADB recovery within recovery mode but havent a clue how to use this method .... is this a possible recovery method to use, as I can see SMT210 ADB device in PC device manager when going into recovery mode?
many thanks in advance for help, :good:
Tab3SMD
OK all, here's more info .......AND another additional issue!
I got stuck back in again tonight because not knowing anything about Tab3 ADB recovery mode was bugging me, so here's what extra I've done so far
While "poking my nose" into tonnes more Xda forum troubleshooting guides I discovered I might need PitMagic tool to try and sort my .Pit partition error via ADB recovery mode.
I tried to find Pitmagic but discovered this is now part of EFS Professional, so downloaded EFS Pro and found this got me nowhere as I needed to also install Android SDK .... which also requires Java Development kit, so I downloaded the full Android Studio and Java JDK 8u91 and installed all (about 1.2Gb and requires ~ 4.2Gb hard drive space!)
Anyway, I now ran Android Studio and then ran EFS Professional, opened my Tab3 into ADB recovery mode and connected Tab3 and PC via usb .....
All looking good EFS reported
Initialising ADB server ..... Okay.
ADB server is running!
Searching for device..... OK
Connecting to device .....OK
Checking device status .....
THEN BAMMMM ....popup from EFS
Connected device is currently UNKNOWN
Please ensure ADB server has been authorised by the connected device by confirming your PC's RSA fingerprint, then press OK to continue
like, wtf! .... one step forward and 6 back!
Can anyone please tell me what this means or better still how to proceed from here?
Anyone?
Anyone??? .....Tab3 is still soft-bricked
I did figure out how to use ADB flash recovery mode using PC.
Unfortunately this also did not allow me to flash any firmware (original or custom) due to admin permissions
(I think this is due to USB debugging not activated within Developer options).
I'm sorta banging my head off the wall with this one .... a bit like what came first? egg or chicken?, because since Odin isn't being recognised by the PC, I cannot flash rom and even though the PC fully communicates with Tab 3 in ADB mode, it won't allow me permission to sideload any flash files because I reckon I need root based permissions, and since the darn thing isn't booting fully, I cannot manually change anything!
I then started thinking about trying to sneak around this permissions issue by flashing CWM or TWRP, but again flash fails due to no permission.
All in all, for me this has been a great learning experience tackling the multiple Android recovery modes, and since I feel so close to cracking this non boot issue, I hate to give up and bin it.
Perhaps someone with much more experience can please help me here?
Is there any way of forcing superuser status on this Tab 3 SM-T210, so as to allow me to flash stock rom via ADB recovery mode?
many thanks in advance for your help,
Tab3SMD