Develop Bugs

please help m phone is dead!!!

try to flash with different firmware

Try running odin as admin and in xp sp 3 compatability mode. That worked for me.

unfortunately the same after running in admin mode in compatibility with xp sp 3.
i cant even get to recovery mode

How many times are people going to ask this same question without searching the forums?
Just removed the battery and then start the phone in download mode using the Volume down + Home key + power button and flash your rom with odin.

usb
You might also want to change the usb port that you used last time. for some reason i can use the ports at the front of my comp, it does the same thing as yours

Try this:
1)Unplug phone from USB
2)Restart Computer
3)Make sure Keis (the samsung software) is closed
4)Run Odin - Chooose pit, PDA, MODEM, CSC file
5)Put phone in download mode
6)Plug phone into USB
7)Wait for Oden to see it
8)Flash

Don't forget to use right pit file. 512 seems to be safest
Sent from my GT-I9000 using Tapatalk

Phone not recognized by PC after root (but still rooted)

So here's the story:
1) Phone worked flawlessly before root. Did an OTA to stock 4.1.1
2) Flashed CWM with Odin v1.85 --> removed battery --> worked without issues
3) Applied SuperSU v0.87 and this didn't go without issue. While in CWM before the reboot, there was some extra prompt (I have rooted a S3 before and did not receive the prompt) however I cycled too fast and I don't think I hit the right option. The phone rebooted anyway and I had root so I didn't think anything of it.
4) Wanted to add files to my SDcard a couple of days later and the phone didn't show up in My Computer (yes USB debugging is enabled, tried all USB ports, changed cables, uninstalled and reinstalled Samsung drivers, I've never used Kies to do anything with my phone - disabled it from the start)
I thought I should revert to stock and start over so I booted into recovery and CWM wasn't there anymore but I still had SU access. I installed Mobile Odin and placed CWM (the .tar file) on my internal (Placed on SDcard --> moved with My files to internal) and flashed CWM and while I didn't see any errors, now I'm data wiped/factory reset but I still can't boot into CWM, I still have SU, and my phone is still not recognized by my computer.
Anyway for me to fix this issue?
Android version: 4.1.1
Baseband: T999UVDLJA
Kernel: 3.031-370274...SMP PREEMPT Fri Oct 19
Build number: JRO03L.T999UVDLJA

tmayne said:
So here's the story:
1) Phone worked flawlessly before root. Did an OTA to stock 4.1.1
2) Flashed CWM with Odin v1.85 --> removed battery --> worked without issues
3) Applied SuperSU v0.87 and this didn't go without issue. While in CWM before the reboot, there was some extra prompt (I have rooted a S3 before and did not receive the prompt) however I cycled too fast and I don't think I hit the right option. The phone rebooted anyway and I had root so I didn't think anything of it.
4) Wanted to add files to my SDcard a couple of days later and the phone didn't show up in My Computer (yes USB debugging is enabled, tried all USB ports, changed cables, uninstalled and reinstalled Samsung drivers, I've never used Kies to do anything with my phone - disabled it from the start)
I thought I should revert to stock and start over so I booted into recovery and CWM wasn't there anymore but I still had SU access. I installed Mobile Odin and placed CWM (the .tar file) on my internal (Placed on SDcard --> moved with My files to internal) and flashed CWM and while I didn't see any errors, now I'm data wiped/factory reset but I still can't boot into CWM, I still have SU, and my phone is still not recognized by my computer.
Anyway for me to fix this issue?
Android version: 4.1.1
Baseband: T999UVDLJA
Kernel: 3.031-370274...SMP PREEMPT Fri Oct 19
Build number: JRO03L.T999UVDLJA
Click to expand...
Click to collapse
Sigh...
Go here and follow the instructions. My 10 year old was able to do it without an issue.
http://forum.xda-developers.com/showthread.php?t=1949687
Reload the samsung drivers on the computer and boot into download mode. After loading the root66 version via odin download Rom manager from the store and load cwm.

Sorry OP but I does anyone know a way to connect to a PC without install the samsung drivers? I'm asking because I don't have permission to install anything to my computer at work. I've tried this http://forum.xda-developers.com/showthread.php?t=1711009
and this https://play.google.com/store/apps/...9pZC5tdWx0aW1vdW50c2RjYXJkLndpZGdldC5mcmVlIl0.
but still no go. They all treated my SD Card as CD drive which can read only. Any input is greatly appreciated.

jcbofkc said:
Sigh...
Go here and follow the instructions. My 10 year old was able to do it without an issue.
http://forum.xda-developers.com/showthread.php?t=1949687
Reload the samsung drivers on the computer and boot into download mode. After loading the root66 version via odin download Rom manager from the store and load cwm.
Click to expand...
Click to collapse
Thanks for the quick reply and I apologize if I wasn't clear but I was attempting to use Mobile Odin (my first time) because my phone was not being recognized by my PC and thus desktop Odin wasn't working either (even after reinstalling drivers and booting in download mode which I tried before posting).
However, I did find the answer eventually. If people have problems losing CWM after root, the error I made was not extracting the image file from the .tar before flashing with Mobile Odin. I eventually returned to stock but that didn't solve my PC not recognizing my device until I found this:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
Credit was given to Nacos on XDA
I didn't bother with Kies and obviously used the latest Samsung USB drivers. Problem solved!

Perfect.
Sorry if I sounded a little short. I am glad you found the solution.

after rooting my phone (samsung galaxy s duos 2) it is not getting detected by pc when connected using usb. Everything else works fine. Please help me to resolve this issue

[email protected] said:
after rooting my phone (samsung galaxy s duos 2) it is not getting detected by pc when connected using usb. Everything else works fine. Please help me to resolve this issue
Click to expand...
Click to collapse
Probably best if you ask in your devices forum if you think it had to do with how you rooted. They'll be more familiar with it and any problems that can occur.
http://forum.xda-developers.com/s7582
The only thing I can say is to uninstall kies, install standalone USB drivers (try both the latest and the older version released for your device on Samsung's site), reboot pc and phone and try to connect again.
Good luck!
Sent from my SGH-T999 using Tapatalk

tmayne said:
Thanks for the quick reply and I apologize if I wasn't clear but I was attempting to use Mobile Odin (my first time) because my phone was not being recognized by my PC and thus desktop Odin wasn't working either (even after reinstalling drivers and booting in download mode which I tried before posting).
However, I did find the answer eventually. If people have problems losing CWM after root, the error I made was not extracting the image file from the .tar before flashing with Mobile Odin. I eventually returned to stock but that didn't solve my PC not recognizing my device until I found this:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
Credit was given to Nacos on XDA
I didn't bother with Kies and obviously used the latest Samsung USB drivers. Problem solved!
Click to expand...
Click to collapse
well nobody wants to help me fix my issue so i will trthis and hope it works.. malfun after trap kernel root no wifi and phone malfunction not recognized by pc.. worked fine nevver any issues till i used g360t1 trap kernal root, didnt relise twrp had a official for his model or i eould have done that so now i need to go on pc to revert back then root using twrp but pc wont connect to phone ahj bullsht
now glad i have root but cant get on pc and all fixs do nothing, not usb cord or pc or mtp settings ect ect not drivers nothing like that.. can i flash stock using twrp, yes but no not me not my phone keeps saying fail so stuck with no wifi and cant connect to pc to tether and its pissing me off.. can someone please help like how has this never happened to anyone at all.. its not a common sense fix here

Don't work , tried all still not working after root
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
Is there no fix ?

[Q] Need some help.

I wanted a fresh start on my SG3, so I formatted my entire phone including the sdcard. Now my phone doesn't have a OS installed and my sdcard doesn't have any rom on it. I thought of just taking my sdcard out and using a sdcard reader to transfer a rom. But I couldn't find my ultra sdcard reader. I found a solution using adb in the "Samsung GS3 Toolkit" to transfer files. But I needed to install the phone drivers, now here's the problem. I can't seem to install the MTP driver without fully booted into android.
Could anyone give me some advice or point me in the right direction? Thank you.

xSignificant said:
I wanted a fresh start on my SG3, so I formatted my entire phone including the sdcard. Now my phone doesn't have a OS installed and my sdcard doesn't have any rom on it. I thought of just taking my sdcard out and using a sdcard reader to transfer a rom. But I couldn't find my ultra sdcard reader. I found a solution using adb in the "Samsung GS3 Toolkit" to transfer files. But I needed to install the phone drivers, now here's the problem. I can't seem to install the MTP driver without fully booted into android.
Could anyone give me some advice or point me in the right direction? Thank you.
Click to expand...
Click to collapse
Install samsung Kies on your pc to obtain the drivers. Then boot your phone into download mode and flash a stock image. I have a step by step guide in the general section for this.

Towle said:
Install samsung Kies on your pc to obtain the drivers. Then boot your phone into download mode and flash a stock image. I have a step by step guide in the general section for this.
Click to expand...
Click to collapse
My phone doesn't connect to Kies http://puu.sh/27nCI and while it doesn't get connected. It give me a error while trying to install the MTP driver.

xSignificant said:
My phone doesn't connect to Kies http://puu.sh/27nCI and while it doesn't get connected. It give me a error while trying to install the MTP driver.
Click to expand...
Click to collapse
You don't need to connect your phone to Kies. Just download Kies to your computer to get the correct drivers onto your computer. After that, use Odin to flash a factory tar image.
Hold Vol Down, home and power to get into download mode.

Towle said:
You don't need to connect your phone to Kies. Just download Kies to your computer to get the correct drivers onto your computer. After that, use Odin to flash a factory tar image.
Hold Vol Down, home and power to get into download mode.
Click to expand...
Click to collapse
Thank you for your help, it all worked out now.

[Q] cant get the note8 to be seen by win8 (recovery mode)

I put the note 8 in recovery mode, plug it into the laptop and Odin (3.09 and 3.07) cant see it...
If I plug it in while that note is booted up into android, Odin will see it... but obviously i cant flash stock 4.4.2 on it when its booted up.
Any suggestions?

senectus said:
I put the note 8 in recovery mode, plug it into the laptop and Odin (3.09 and 3.07) cant see it...
If I plug it in while that note is booted up into android, Odin will see it... but obviously i cant flash stock 4.4.2 on it when its booted up.
Any suggestions?
Click to expand...
Click to collapse
Assuming you are not rooted and are not planning to root. Is this correct?
Do you have the Samsung Note 8 drivers installed on the PC? Are you following the steps listed HERE?

CCallahan said:
Assuming you are not rooted and are not planning to root. Is this correct?
Do you have the Samsung Note 8 drivers installed on the PC? Are you following the steps listed HERE?
Click to expand...
Click to collapse
Yeah, not rooted, not looking to root.
I get as far as step 7 and the part where it says " Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click. "
I dont get *anything* in the COM port.
Also I've tried I watching the Device manager as i plug the tablet in and there is no change.
Its like the device isnt being detected.
BUT
If I plug the device in when the tablet is started normally the device *IS* detected, (and Odin can see the COM port)

senectus said:
Yeah, not rooted, not looking to root.
I get as far as step 7 and the part where it says " Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click. "
I dont get *anything* in the COM port.
Also I've tried I watching the Device manager as i plug the tablet in and there is no change.
Its like the device isnt being detected.
BUT
If I plug the device in when the tablet is started normally the device *IS* detected, (and Odin can see the COM port)
Click to expand...
Click to collapse
What version of Windows are you running? It is best to use a PC with Windows 7 if possible because Win 8 is harder to get working with Odin.
Couple things you can try.....
- Try different USB port and USB cable (this is probably obvious and most likely you have done already)
- Make sure you are plugged directly into the PC and not a USB hub.
- While Odin is up boot the phone multiple times into download mode and see if Odin will find it. Sometimes it takes 3 or more times.
- Uninstall the Samsung drivers on the PC, reboot, and re-install.
- Try a different PC if you have that ability. Preferably one running Windows 7.
If all else fails, might be able to get Heimdall to work: http://forum.xda-developers.com/showthread.php?t=755265
Not sure if it is confirmed working on the Note 8 so might have to research it a bit before trying.
---------- Post added at 10:08 AM ---------- Previous post was at 09:35 AM ----------
From what I have seen posted in XDA Heimdall does work on the Note 8.

senectus said:
Yeah, not rooted, not looking to root.
I get as far as step 7 and the part where it says " Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click. "
I dont get *anything* in the COM port.
Also I've tried I watching the Device manager as i plug the tablet in and there is no change.
Its like the device isnt being detected.
BUT
If I plug the device in when the tablet is started normally the device *IS* detected, (and Odin can see the COM port)
Click to expand...
Click to collapse
I just want to check if you know the difference between recovery mode and download mode. You mentioned in your question that you booted to recovery mode. If you are planning to flash software using Odin you should boot to download mode instead.
- Volume Down, Home and Power buttons boot to download mode as mentioned in instructions linked by CCallahan
- Volume Up, Home and Power buttons boot to recovery mode

kuitsu said:
I just want to check if you know the difference between recovery mode and download mode. You mentioned in your question that you booted to recovery mode. If you are planning to flash software using Odin you should boot to download mode instead.
- Volume Down, Home and Power buttons boot to download mode as mentioned in instructions linked by CCallahan
- Volume Up, Home and Power buttons boot to recovery mode
Click to expand...
Click to collapse
yeah sorry, bad use of words.. it was download mode. Recovery mode gives you format etc options.
Will try heimdal tonight, failing that i'll have to try and dig up a win7 machine :-/

I used odin on windows 8.1 without any problems.
Galaxy Note 8.0 Xposed Build N5120XXDNE4 / Baseband N5120XXCMG7 / Kernel SphereKat-Rev5.1 on Telstra LTE

SM-P607T charges but will not connect to any PC - won't even try

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.