Database Users

J16 Download Mode USB Failure

Hey guys,
I'm about ready to throw a brick through a window at Samsung's Headquarters, so I'm sure this will make an excellent first post.
Earlier today, my dad decided to update is rooted phone via a T-Mobile update sent out via the internet to the latest J16 firmware. Not surprisingly, his phone was one of many to get soft bricked. From this point I used ODIN to flash back to J15 and then used it again to upgrade to J16. Now, the phone boots normally, but it still seems to have ROM manager and other root applications on its hard drive despite the fact that ODIN should have wiped out all of the packages.
This coupled with the fact that I have failed to re-root the device and USB connectivity is awful compared to J15, I decided to try and flash back to J15 using ODIN. Only this time, when I get the device into download mode it isn't recognized properly as a USB device by my computer; therefore, ODIN won't recognize it either.
My dad is about ready to take the phone to T-Mobile in hopes of getting a new device, but before he attempts this I'm wondering if there are any solutions to my problems that A) Fix USB connectivity in download mode or B) Allow me to whipe all data and revert to J15 in some other manner.
Help would be appreciated!
Go_L_Den

go_l_den said:
Hey guys,
I'm about ready to throw a brick through a window at Samsung's Headquarters, so I'm sure this will make an excellent first post.
Earlier today, my dad decided to update is rooted phone via a T-Mobile update sent out via the internet to the latest J16 firmware. Not surprisingly, his phone was one of many to get soft bricked. From this point I used ODIN to flash back to J15 and then used it again to upgrade to J16. Now, the phone boots normally, but it still seems to have ROM manager and other root applications on its hard drive despite the fact that ODIN should have wiped out all of the packages.
This coupled with the fact that I have failed to re-root the device and USB connectivity is awful compared to J15, I decided to try and flash back to J15 using ODIN. Only this time, when I get the device into download mode it isn't recognized properly as a USB device by my computer; therefore, ODIN won't recognize it either.
My dad is about ready to take the phone to T-Mobile in hopes of getting a new device, but before he attempts this I'm wondering if there are any solutions to my problems that A) Fix USB connectivity in download mode or B) Allow me to whipe all data and revert to J15 in some other manner.
Help would be appreciated!
Go_L_Den
Click to expand...
Click to collapse
First and foremost make sure your plugging the usb into a usb port that is connected directly to the motherboard. Should stablize the usb connection. ( I had the same issue) Second flash to JFD via odin, then you want to upgrade to J16 via the vibrant version of kies mini. OTA update is not the greatest.

The JI5/6 updates don't wipe all data and apps, as they were designed to be OTA updates and not complete new installs. Can't have people complaining that an update wiped their entire phone, right? Stock JFD is a full flash which wipes all user data.
And yes, try to have it plugged directly into the motherboard's USB ports, make sure the contacts on the microUSB aren't corroded, and try deleting the Vibrant drivers and reinstalling them.

which version of odin you using? try 1.3 if not already

Kies or ODin
Nevermind I found it here ars.samsung.com/customer/usa/jsp/faqs/faqs_view_us.jsp?SITE_ID=22&PG_ID=2&PROD_SUB_ID=557&PROD_ID=560&AT_ID=341559

All you hace to do is go to USB settings and with the OTA update for J16, there's an option to choose "Ask what to connect" either samsung kies, mass storage, etc. Happen to me, did unroot, factory reset and there you go, just need to go to that stupid settings.

Failed root with odin, cannot detect with Kies 3

recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.

vivek318795 said:
recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
Click to expand...
Click to collapse
I'm running into the exact same issue, did you ever find a solution?

Same issue
I have the same issue. Is there no help? Chainfire? do you have a CF-Root for SM-N900V yet?
Thanks. any help is appreciated.

[Q] Soft Bricked Galaxy S5

Hello,
I've got (had) an SM-G900W8 running the XtreStoLite v2.0 LP BETA5 ROM on the XXU1BOA3 kernel. I installed TWRP 2.7 via Odin, and left the latest modem and bootloader updates I got through KIES3.
At which point I got the chance to sell the handset on Kijiji, provided I could get the stock ROM back on.
I downloaded the latest Odin (3.09) and the correct Firmware for my handset from sam mobile, and factory reset the device. I pulled the battery, let it sit, and tried to flash once I got it back up in download mode, and it wouldn't work.
This isn't too much of a surprise to me, because since I flashed TWRP, Odin hasn't ever worked for me. Regardless of how many times I've tried to flash the modem and/or BL that XtreStoLite asked me to use in their how to thread, it wouldn't work. I was willing to ignore it b/c the ROM worked with the modem and BL it was running.
My problem is that once I tried to reboot, the system hung at the BL animation. I went back into recovery, and tried to move my backups off my external storage (I had 2 back ups that were about 2 or 3 gigs each, too much for the local storage) to the local card and restore (b/c TWRP won't restore from the external card) and the back ups failed.
Now I've got the BL screen, but it won't advance to the animation, and it won't boot to TWRP either.
I tried to restore from KEIS, but it says my device isn't supported by KIES 3 (it is). I could really use a hand here. Every time I try something this gets worse. I'm no pro, but I've had no problem figuring this out on my old HTC handsets.

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck

Odin doesn't recognize my s7 edge (trying CF auto root)

Hi, I've been reading the thread for CF auto root to give it a go. I've downloaded the drivers (I've got 1.5.51 now installed, haven't been able to find later ones), I've got the 2.74 SU version that helps to overcome a recent security policy update issue reverting root status and the CF auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip) which has odin 3.10.6 included (not quite sure if I can use any recent odin version). I even got my stock firmware com sammobile and extract the proper boot.img from the AP* file (just in case I got something wrong at sometime). I've enabled the OEM unlock too on developer options. I understand I can give it a go without having to go with a custom recovery (still not sure and haven't got the whole picture about the dm-verity thingy and what effects has on the device but someone mentioned something like loosing the encryption or so). This is my first try on getting root on my s7 edge G935F (international version), so it shouldn't have any boot.img problem (but trying to be prepare since I can't go about without my phone being working).
So, I've got my phone into download mode, started odin, loaded on AP the tar.md5 file from the CD auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5), connect the device throuhg usb cable and I was expecting Odin to recognize it but nothing happens. Since in the threads I've been researching for s7 edge there is no indication on waiting to see something happening on ODIN (but in some other threads - not s7 edge related though - mention something about having to see a blue indicator on COM), I'm not quite sure if I'm expected to just hit start even if no apparent change is happening on ODIN nor there is some drivers installing/configuring when connecting the device on download mode. Since I'm quite new to this, I'm no sure if I should connect the device first with some other option enabled, like USB debugging or if I'm missing something quite obvious for someone familiar with flashing with odin?
Kind regards for any help!
PS. I did tried to find an answer through searching but foung nothing related s7 edge wise so I'm at a loss not even knowing if just hitting start without having the device recognized on ODIN will do any harm at all (that newbie I am)

Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap

skinza said:
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
Click to expand...
Click to collapse
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.

cmanh said:
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
Click to expand...
Click to collapse
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc

skinza said:
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
Click to expand...
Click to collapse
Thanks again! for now I won't be going for a custom rom but wanted to be able to install a firewall to stop some apps from draining my prepaid data (limited)..
I was planning on having xposed installed but it seems I need a custom recovery for that as well.. I used to have xprivacy on a previous nexus 4 and loved I could limit some permissions that are still missing now on marshmallow but haven't got a grip yet as per the effects due to the dm-verity thing.. would you happen to know anything about it? and I was also wondering about if I do need to have the OEM unlock still enabled now that I'm rooted? (The later because I'd been robbed of my cellphones in the past - even recently a new s7 edge that didn't last me even a month and wouldn't want to let them have an easy pie on having the device available)
Regards!

I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also

Singhathia said:
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Click to expand...
Click to collapse
Got the same issue. I'm new with this. My colleague wants me to learn and test and load Lineageos on some brand new S7 G930F devices he gave me which I have already switched to dev mode with OEM unlock and USB debugging on and the devices smoothly jumped into ODIN downloading.... mode
I also have the proper Samsung USB Driver installed. (did it several times after ODIN didn't recognize my device)
However, according to the manual, I should start up ODIN, then connect the device via USB cable to the workstation (as unsuccessful I already tried 3 workstations with Windows 7 and Windows 10) whilst having the phone in download mode... .BUT NOTHING APPEARS in the Log field and the ID:COM Box doesn't change colour and my manual says that it should.
My workstation however recognizes the devices with positive messages so I guess the drivers are good.
My co-worker gave me ODIN v3.10, but as this didn't work I downloaded and installed V3.12, but unfortunately also without any luck.
What am I doing wrong?

which OS?

S7 edge SM-G935F
Hey guys,
i tried rooting my s7 edge but after i got into TWRP my phone went into a bootloop. when i got back download mode, odin still found my phone, though everytime i tried to enter TWRP again, odin said there was a FAIL and my phone immediatly went back into bootloop. I tried to reinstall the samsung usb drivers but now odin cant find my phone anymore.
Before i screw up even more, can someone please help me? right now im stuck in download mode and odin 12, 11, and 10 all wont recognize my phone, also not if i use different cables. my windows laptop however still gives me the device found and device disconnected sound everytime i (dis)connect my phone.
any ideas?
thanks
EDIT: Okay i tried my USB 3.0 port and now odin found my phone. just weird... now i just need to solve the problem that I'm still stuck in the Bootloop but that probably doesnt belong in this thread

Can't Update or Flash Firmware to Galaxy S8

I have a Galaxy S8 SM-G950U on Verizon.
​In March I flashed my phone with the following ROM so I could get the S9 messanger,
https://forum.xda-developers.com/galaxy-s8/development/rom-pixelish-s9-rom-custom-snapdragon-s8-t3766891
Everything worked for a few months, including system updates. But as of roughly two months ago I am unable to install any system updates, they always fail. The rest of the phone works fine, its just the updates.
​I have tried to use Smart Switch to install the update through my PC, but the process would freeze after downloading the update. The same happened when I tried emergency software recovery through Smart Switch.
I also tried using Verizon's software update utility to both update and recover the phone, but the program would freeze just like Smart Switch.
I have also tried flashing both stock firmware and re-flashing the ROM to the phone with no success. I have tried flashing with the following 4 versions of Odin:
- Odin3-v3.12-PrinceComsy-
- Modded Odin v3.13.1 Raymonf
- Odin3 v3.13.1_3B_PatcheD
- Odin3_v3.12.3
​No matter what version I tried, Odin would either outright fail or freeze at either "SetupConnection" or "Intializing". I tried plugging my phone into both USB 3.0 and USB 2.0 ports. I was very careful to get the correct stock firmware for my phone. I downloaded the stock firmware from both sammobile.com and samsung-firmware.org
​I also tried simply restting the phone to factory setting both from inside Android and from Recovery Mode.
​Does anybody have any clue what might be causing this and what I can do to fix it?
I really dont want to be stuck with a phone that can't get updates.