Went into twrp v2.8.7.0 to check something then a reboot when red text appeared int hte upper left corner where stock recovery does saying "Recovery is not seandroid enforcing" and eventually went into "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again" the damn thing will not connect to kies in any way, shape or form I have 2 usb 3.0 ports and 2 usb 2.0 ports. I've tried multiple cables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- uninstalled kies and reinstalled not checking unified drivers but it will not connect to kies. It isn't recognized by the Samsung drivers yet my the usb drivers see my note 4 is, 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 anyone has any suggestion, please let me knoiw thanks
I ended up on that screen recently after a failed firmware flash in Odin. I was attempting to flash the latest 5.1.1 firmware I found on Sammobile. My note (P600) has a finicky micro-USB port, so that could have been the problem.
On second try, it worked just fine. Even though Windows explorer wasn't recognizing my tablet, Odin saw it just fine (you can see where it says "added" after plugging it in). I'd recommend giving that a try.
Thats what got me ant the kies thing besides everything pointing kies being the only way out- odin didnt recognize it's existence- plug, unplug nothing on the odin window… I was actually on 5.1.1 and was fine I just don't know who the hell went wrong
Sorry if this is too obvious, but are you able to get it into download mode before trying ODIN?
Hi no it goes right to "Please select recovery mode in kies and try again" nothing else when I was able to get to download mode before it was not showing up in odin at all.
QUOTE=jerrys0828;71275901]Sorry if this is too obvious, but are you able to get it into download mode before trying ODIN?[/QUOTE]
Related
I am currently on a stock unrooted 4.1.2, SPH-L710. I have been attempting to root my Galaxy S3 using Odin3 v3.07 on Windows 7 using a variety of methods. I get the basic gist where you put the phone into download mode and then flash a *.tar or *.tar.md5 in the PDA field. It gets as far as "Firmware Update Start" and then "<some file name>" (like recovery.img--varies with the solution), but it never progresses past this point. Looking at some guides, it appears that there should be a "NAND write start!!" message which never appears, as well as a progress bar, which I never see. This leaves me stuck in download mode, but thankfully if I just unplug the USB cord Odin detects it as a failure. Following that, I am always able to boot back into Android, so it seems Odin is unable to touch anything at all.
I tried to use this toolkit (http://forum.xda-developers.com/showthread.php?t=1703488), but despite installing drivers, I could never get it to recognize my phone as being in USB debugging mode. This is after all drivers had installed correctly. I have also heard that there can be problems using usb cords other than the original, but I have made sure to use the OEM cord. Any ideas on what might be the problem?
doublering said:
I am currently on a stock unrooted 4.1.2, SPH-L710. I have been attempting to root my Galaxy S3 using Odin3 v3.07 on Windows 7 using a variety of methods. I get the basic gist where you put the phone into download mode and then flash a *.tar or *.tar.md5 in the PDA field. It gets as far as "Firmware Update Start" and then "<some file name>" (like recovery.img--varies with the solution), but it never progresses past this point. Looking at some guides, it appears that there should be a "NAND write start!!" message which never appears, as well as a progress bar, which I never see. This leaves me stuck in download mode, but thankfully if I just unplug the USB cord Odin detects it as a failure. Following that, I am always able to boot back into Android, so it seems Odin is unable to touch anything at all.
I tried to use this toolkit (http://forum.xda-developers.com/showthread.php?t=1703488), but despite installing drivers, I could never get it to recognize my phone as being in USB debugging mode. This is after all drivers had installed correctly. I have also heard that there can be problems using usb cords other than the original, but I have made sure to use the OEM cord. Any ideas on what might be the problem?
Click to expand...
Click to collapse
You could try using a different USB cable. The OEM ones have been known to cause problems with Odin.
As far as USB debugging goes, I've had some Windows 7 computers that will see the phone with USB debugging disabled, and some won't unless I uncheck USB debugging.
QBking 77 has a nice video on rooting the S3 at: http://www.qbking77.com/how-to-root/root-samsung-galaxy-s-iii.html
Good luck!
Install drivers again. Plug your phone let it be recognized. Unplug the phone. Put it in download mode, plug it. Let the computer recognized it. Unplug. Open Odin and try again.
There's a method by Chainfire in Original Development, which works great.
Sent from my SPH-L710
Completely new to android. Regular mode, pc recognizes easily. Download mode, not at all. No unknown device. If on the Note I pick "upgrade from adb" then the pc devise manager shows a samsung device adb device. So, it sees it. but still Odin does not see it. Tried USB debug mode on/off on the tablet. Restarted PC and tablet several times. Using original usb cable, tried various usb ports. Am I missing something obvious? I feel that I am.
I would install kies from samsung. Completely reinstall drivers from with in kies and go from there. You could actually push the recent update from kies to your tab and that will do it in odin mode. Give it a try…
Sent from my SM-P600 using Tapatalk
Bizack said:
I would install kies from samsung. Completely reinstall drivers from with in kies and go from there. You could actually push the recent update from kies to your tab and that will do it in odin mode. Give it a try…
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Using Windows 7,
Uninstalled Kies 3, reinstalled, updated, uninstalled/reinstalled all drivers. Tried usb debugging on/off (which changed the drivers) Odin perfectly detects the tablet in regular mode. In recovery/download mode I still don't even get an unknown device. It sees the Samsung Adb device, but neither kies (though maybe it shouldn't) nor odin "see" the device. Tried various usb ports, multiple computers. I am on most recent firmware for the P600
Working with tablets (first ipad 2, now the new note) make me feel like I know nothing about computers.
beleghm said:
Using Windows 7,
Uninstalled Kies 3, reinstalled, updated, uninstalled/reinstalled all drivers. Tried usb debugging on/off (which changed the drivers) Odin perfectly detects the tablet in regular mode. In recovery/download mode I still don't even get an unknown device. It sees the Samsung Adb device, but neither kies (though maybe it shouldn't) nor odin "see" the device. Tried various usb ports, multiple computers. I am on most recent firmware for the P600
Working with tablets (first ipad 2, now the new note) make me feel like I know nothing about computers.
Click to expand...
Click to collapse
Recovery and download mode are two completely different things. If you are in recovery then Odin will not see the tablet. You have be in download mode. Power the device off and restart it by holding down the power button and volume down at the same time. If you hold power and volume up you will go into recovery which does you no good for Odin.
nrage23 said:
Recovery and download mode are two completely different things. If you are in recovery then Odin will not see the tablet. You have be in download mode. Power the device off and restart it by holding down the power button and volume down at the same time. If you hold power and volume up you will go into recovery which does you no good for Odin.
Click to expand...
Click to collapse
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
beleghm said:
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
Click to expand...
Click to collapse
Samsung is the only manufacturer I have used that does download mode. Most others have bootloader mode that works with adb. Though using Odin is easier for beginners than adb.
Sent from my SM-P600 using XDA Premium HD app
beleghm said:
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
Click to expand...
Click to collapse
i don't know what the hell is going on here... mine won't work
i have the note 3 and it works fine, i just re downloaded and reinstalled kies 3, kies will recognize the tablet when it is booted normally
as soon as i boot into download mode, odin won't see it.
what gives? i have usb debugging on, i can't figure this out, what am i missing, as im sure it is super simple....
asaqwert said:
i don't know what the hell is going on here... mine won't work
i have the note 3 and it works fine, i just re downloaded and reinstalled kies 3, kies will recognize the tablet when it is booted normally
as soon as i boot into download mode, odin won't see it.
what gives? i have usb debugging on, i can't figure this out, what am i missing, as im sure it is super simple....
Click to expand...
Click to collapse
For me, I had to use the old Kies, not Kies3. I didn't even get a device showing up in device manager when USB Debugging was enabled, though if i switched USB mode from MTP to Camera, I would get a device Samsung_Android that looked like it wanted ADB drivers, but manually pointing it to the drivers included with Kies3 didn't work.
beleghm said:
Completely new to android. Regular mode, pc recognizes easily. Download mode, not at all. No unknown device. If on the Note I pick "upgrade from adb" then the pc devise manager shows a samsung device adb device. So, it sees it. but still Odin does not see it. Tried USB debug mode on/off on the tablet. Restarted PC and tablet several times. Using original usb cable, tried various usb ports. Am I missing something obvious? I feel that I am.
Click to expand...
Click to collapse
I have a sm-p600 that has been rooted and had a custom rom on it. I went to change the resolution and it rebooted and then i got a bootloop and now i am unable to get into my custom recovery and i cannot connect through adb or in download mode with no unknown device message as well. any suggestions to fix this would be appreciated.
Make sure Kies isn't running in the background, it screws with ODIN....
Hi, I recently tried using a stock image with odin for my galaxy tab pro 8.4. Odin started flashing but failed when sending system.img.
I tried this process twice and got the same result even using a different USB port in may computer and a different cable but, after the second try (and as the first one I disconnected the computer and restarted into download mode), the tablet usb stopped working.
When I connected it in my first two tries, I got the typical windows sound when you connect anything in the usb, now I dont get anything and not even in the device manager. I tried with another computer and got the same problem, no usb connected sound and nothing in device manager.
My device is now stuck in odin mode. If I try to reboot normally I get into download mode but with the message "Firmware upgrade encounterd an issue. Please select recovery mode in Kies & try again".
I have tried deleteing de drivers and installing kies but still nothing.
Can you help me please?
Nevermind
MarcoZM1978 said:
Hi, I recently tried using a stock image with odin for my galaxy tab pro 8.4. Odin started flashing but failed when sending system.img.
I tried this process twice and got the same result even using a different USB port in may computer and a different cable but, after the second try (and as the first one I disconnected the computer and restarted into download mode), the tablet usb stopped working.
When I connected it in my first two tries, I got the typical windows sound when you connect anything in the usb, now I dont get anything and not even in the device manager. I tried with another computer and got the same problem, no usb connected sound and nothing in device manager.
My device is now stuck in odin mode. If I try to reboot normally I get into download mode but with the message "Firmware upgrade encounterd an issue. Please select recovery mode in Kies & try again".
I have tried deleteing de drivers and installing kies but still nothing.
Can you help me please?
Click to expand...
Click to collapse
For anyone facing this, you have to wait for the tablet to run out of battery and then connect it again to the computer. It will be detected as before.
Hi,
I tried to downgrade my i9000 and now it's only showing the soft brick sign.
I used to run CM11 with CWM before I decided to downgrade to stock.
I connected the USB cable then used Odin with the same PIT file that I initially used to install CWM. I guess so far so good as it recognizes something on the COM port associated with my USB entry and the background turns yellow.
I have picked the 3 stock files that match my model (GT-I9000M), went in downloading mode and hit Start.
Odin reports that successfully checks the files, then right after "SetupConnection" it ends with Success 0 / Failed 1.
I just do not get farther than that. There is no action in the square above the COM port and there is no other message. The phone remains in Downloading mode and there is no progress bar displayed. at any time.
Anybody can make any suggestion on how to fix it?
When do I know it's totally bricked?
Many thanks.
Until it still goes to downloading mode it is not bricked. This has happened to me once when i tried to go back to stock using odin and odin said it was connected but will say failure after setting up connection my problem was that Virtual box for ubuntu was preventing the phone from being fully connected.
The main problem is that maybe your usb connection in your computer might not be fully recognizing the phone
so try different usb port, open odin in administrator mode, and continue trying it until it works
usually when i use odin i keep the computer as still as possible until flashing has been done completely.
Also are you using the right files because that could be a problem.
Here is the video I originally used to teach me to odin back to stock but its for the samsung vibrant but the procedure is the same
https://www.youtube.com/watch?v=l3K9my9kAvI
Hope i helped
Thank you for your message. You were right, the problem came from USB, specifically from the driver and OS, I guess.
I failed to flash it on Win7 and Win10, as described above, then I told myself I will give it a try on a XP machine (32 bit). It worked like a charm, first attempt.
Regards.
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.