Ok, so My case is overly specific, and I couldn't find anything exactly like it around here. But I have a lot of info on the issue.
First off, I have the same phone as the dude who made this post a while back. My issue is different though.
(Model Number: SM-G950U1
Baseband: G950U1UEWU1AQE3
Build Number: NRD90M.G950U1UEWU1AQE3
CSC: G950U1OYM1AQE3
PDA: G950U1UEU1AQE3)
After doing a bit of research, I found out that it wasn't easy to root a US version of the phone, but my dumbass still tried, in the process, I managed to
-Deactivate USB debugging (a tutorial said to Erase the phone after the process, which failed and erased the phone)
-Break the Stock firmware
I tried flashing different firmware I found on some different [modded, ofc] versions of Odin, but with no luck, sometimes it'd just tell me it failed, other times it'd give me the infamous "Auth error".
Today, I found what appears to be the actual firmware for my phone (This one, right here) and after waiting literally 16 hours for the "free" download to be completed and checking the file for any viruses, I finally tried to flash it. I'm still trying, but up to now, 5/8 trials have failed (These trials are a combination of all the USB ports in the computers, the different ways to flash, and the different versions of Odin I've installed).
For extra background, I'm using an old DELL Latitude D500 from 2003 to flash the Firmware.
Now, all I want to know is if there's a way to get this to work. Do I need different firmware? The original cable? A newer PC? Different Odin Mods? Literally ANY help is much appreciated. (yes, I backed the phone up before attempting to root, no it's not my main phone, but I hold emotional value to it)
Quick edit: After all trials, all new errors appear to be AUTH! errors on the PC. I also tried flashing the files separately and the phone gives me the following errors:
AP: fused 6 > binary 1
CSC: fused 7 > binary 1
CP flashes just fine
I did not try to flash the BL separately out of the fear that it would flash incorrectly and not let me enter download more anymore.
Edit 2: yes, I'm using Samsung's USB drivers.
JOOC: Do you use Samsung's ADB ( USB driver ) or just one that is utterly idiotically hundred of times recommended in the WEB?
jwoegerbauer said:
JOOC: Do you use Samsung's ADB ( USB driver ) or just one that is utterly idiotically hundred of times recommended in the WEB?
Click to expand...
Click to collapse
I managed to install the latest version of Samsung's USB driver on the PC, so that's what I'm using.
Related
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.
I have spent hours over the last few days trying to root my Galaxy S5
It have firmware G900FXXU1ANG8 and is model SM-G900F
I have tried towelroot
it failed
i have tried Heimdall Suite
it detects the device but gives failure when trying to save pit file or do anything else
I checked several forums and they say use different driver so i use the zadig and installed libusbK and still problem.
I have tried Odin3_v3.07 Odin3_v3.09 and Odin3_v3.10 and they all dont pick up my phone.
i have tried two different cables and still nothing.
Anything else you can recommend and i have literally spent hours reboot and trying different drivers, restarting computer and looking for different fixes.
wbb1 said:
I have spent hours over the last few days trying to root my Galaxy S5
It have firmware G900FXXU1ANG8 and is model SM-G900F
I have tried towelroot
it failed
i have tried Heimdall Suite
it detects the device but gives failure when trying to save pit file or do anything else
I checked several forums and they say use different driver so i use the zadig and installed libusbK and still problem.
I have tried Odin3_v3.07 Odin3_v3.09 and Odin3_v3.10 and they all dont pick up my phone.
i have tried two different cables and still nothing.
Anything else you can recommend and i have literally spent hours reboot and trying different drivers, restarting computer and looking for different fixes.
Click to expand...
Click to collapse
flash this http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip u have to install samsung drivers u can find them in folder of kies. there is a folder with the name "USB driver" install this and odin will recognize your phone in download mode
Hello everyone, I'd like to start off by saying I am a complete newcomer to all this so please explain literally all of the terminology/jargon you intend to use and correct me when I use it wrong.
I have a Chinese version of the Samsung Galaxy Note 4 SM-N9109W and up until yesterday it was running out of the box on android 4.4.4. I care not for any of the data on the phone nor the warranty as there was none to begin with when it was gifted to me.
I attempted to "root" it as I didn't want any of the Chinese apps/restrictions on it but have failed miserably and now my phone is stuck in a bootloop.
I was following this guide if it helps: http://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948 and downloaded the appropriate Snapdragon version (SM-N9109W).
I cannot enter recovery mode by holding down *power+vol up+home* as it just keeps on rebooting. I can, however, get into the downloader by holding down *power+vol down+home*.
I have tried for the entirety of today to find a specific guide for the Chinese note 4 on xda, youtube and google but to no avail - nothing that I can find is identical to my situation and I am hesitant to do anything further to it by following a similar guide in case I make it worse.
I have repeatedly seen suggestions to "flash" stock rom and as I can get into the downloader I believe this would be a great starting point, but once again I am afraid to do anything without a specific guide for the N9109W.
A few people have referred to SamMobile to download stock rom, but a search for SM-N9109W lists 8 files for 4.4.4 and I believe I have no way of working out my PDA or CSC, yet again I don't know what these even are and they might not be relevant?
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience,
Ryan
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
ithehappy said:
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
Click to expand...
Click to collapse
Thank you ithehappy for the reply,
When I search for the stock firmware on SamMobile, I type in my exact model number (SM-N9109W). This search returns with a list of multiple different versions for my phone, of which 8 are 4.4.4 (my initial version).
Does it matter which version I download and install?
To my knowledge, I have no way of finding my CSC or PDA unless you know of a database I can use to search the information that is physically on my phone? Once again, does it matter that I know what these are or can I simply download, for example, version 5.1.1 and flash that on instead of my original 4.4.4? Or, will this just cause further possibly unfixable problems?
Thank you for your help
Anyone?
No, you can download any one you want.
Thank you for the help, ithehappy. I now have a working phone!
For future readers, I downloaded the latest version of 4.4.4 that SamMobile had (2015-03-27) for my model (SM-N9109W):
PDA: N9109WKEU1ANL3
CSC: N9109WCTC1ANL3
It failed the first time I tried flashing with Odin 3.10.7, but whilst I was hastily taking screenshots of my problem to post here I accidentally started the transfer again and it successfully installed that time.
I followed the instructions on SamMobile for the installation.
This version of the firmware I installed does not have any google services (thank China for that), so keep that in mind.
Thank you
First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound
undersound said:
First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound
Click to expand...
Click to collapse
1) Yes, of course.
2) No.
3) Don't know what you are talking about.
Odin is used to flash stock roms on Samsung devices. That is the only way.
There are links to guides in the help thread in the Q&A section.
Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk
jimmyoh said:
Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this
undersound said:
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this
Click to expand...
Click to collapse
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.
GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Click to expand...
Click to collapse
That's good to know, thanks. I was trying this with an extended usb cable so it can be the definitely the case.
Will try later today with a direct connection to a backport.
GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.
Click to expand...
Click to collapse
Managed to return to stock firmware, yay!
In case it helps someone else, here are my steps:
1. By dialing *#1234# on a similar phone I checked what ap/cp/csc version I needed
Code:
AP: I9505XXUHOF2
CP: I9505XXUHOF2
CSC: I9505OXAHOF2
2. Downloaded the correct firmware image (http://www.sammobile.com/firmwares/download/50091/I9505XXUHOF2_I9505YHNHOF2_PHN/)
3. Extracted the firmware file
4. Opened Odin v3.10.7
5. Rebooted Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6. Connected phone and waited until I got a blue sign in Odin
7. Added the firmware file to AP / PDA
8. Made sure re-partition was NOT ticked
9. Clicked the start button
10. Then I got a PASS!
So I guess there can be 2 reasons my first attempt of flashing stock firmware did not worked:
1. The firmware I used the first time was not correct for this phone (http://www.sammobile.com/firmwares/download/64897/I9505XXUPOL1_I9505PHNPOL1_PHN)
I did not know at that time about checking my ap/cp/csc described in Step 1 above so I was just downloading the firmware which seemed the most appropiate according to the country / provider.
What helped me a lot was when I found the explanation of the parts of the version number:
Code:
I9505XXUHOF2
I9505 = phone model
XX = country/region code
UHOH2 = modem
2. The second attempt I followed GDReaper suggestion and I used the usb cable directly on of the backports of my pc so that could have helped as well.
Another thing that was not clear to me at first were the providers code. Or well, they were clear to me that they were abbreviations for telecom providers but I did not bought these phones from a provider so I was not sure which one to pick. After a while I came to discover that I needed PHN which means Unbranded
Code:
---------------------
PHN = unbranded
TNL = Tmobile
VDF = Vodafone
Thanks all for the help
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