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.
Related
I have a Galaxy Tab 10.1 LTE and cannot get Odin to recognize the device while in download mode on two different computers. I have the drivers installed directly from the Samsung website (VZW_SCH-i905_USB_Driver_v1_3_2360_0). I get an error in device manager that says "Unidentified Device" and i haven't been able to find anything that fixes it. Does anyone have any recommendations or solutions to fix this?
emplox said:
I have a Galaxy Tab 10.1 LTE and cannot get Odin to recognize the device while in download mode on two different computers. I have the drivers installed directly from the Samsung website (VZW_SCH-i905_USB_Driver_v1_3_2360_0). I get an error in device manager that says "Unidentified Device" and i haven't been able to find anything that fixes it. Does anyone have any recommendations or solutions to fix this?
Click to expand...
Click to collapse
Did you follow ROOTING YOUR TAB section on http://forum.xda-developers.com/showthread.php?t=1171089? Is it 4g? If it's 4g, you don't use Odin. Odin is for the wifi version.
I am not trying to root my device, as it's already rooted and working fine. I'm trying to install the latest TW leak that came out yesterday and the only way to do it is via Odin.
I'm not clear on the TW leak applied via Odin method that you are using. More info/links would be helpful.
Are you trying to flash a ROM?
Update:
Are you talking about this leak-->http://forum.xda-developers.com/showthread.php?t=1364222?
Yes, that is the leak i am trying to flash.
I think i just figured it out. Finally found a different driver which seems to have worked. The file name is below.
20070813082717640_Samsung_USB_Driver_Installer.exe
I guess not...it hangs while it installs the 2nd driver. I've let it sit for almost two hours now and it's just sitting there doing nothing. Odin detects the device now, but it doesn't get past the SetupConnection part and eventually says it cannot connect using the COM port.
Also...i've now tried three different computers with the same result.
Hi Guys,
I had rooted my phone using motochopper then yesterday I received OTA update. Everything seems to be fine then later I started getting Samsung Text-to-Speech engine has stopped working everytime I opened Gallery. It was very frustrating, so I did factory Reset. After Factory reset when I go to last screen to startup my phone(Learn about Key Features:Air view, Air gesture) and click Finish. I get "Unfortunately Settings has stopped" error. I found the stock firmware here hxxp://galaxys4root.com/galaxy-s4-stock-firmware/ But every time I use Odin I get PIT Partition not found.
Please help guys, I am stuck, don't know what to do now. :crying:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
scott14719 said:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
Click to expand...
Click to collapse
I checked all appropriate settings for ODIN before upgrading the firmware. I got the same error all the time. I will research "Stopped Settings" error and let you know if I find anything. Thanks for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
zukaa12 said:
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
Click to expand...
Click to collapse
weird mine never said enter recovery. what i did was plugged in my phone and i did the ""Firmware upgrade and initialization" then it gose through all the agreements and downloads the firmware. then it'll auto boot in to download mode for the install. are you using the stock usb? which port are you using on your computer? is KIES up to date? do you have the right drivers?( then again i think kies will install them but just in case) try already being in download mode.
also you can try this http://forum.xda-developers.com/showthread.php?t=2261232
I tried same at&t stock firmware but this time I used Odin 3.0.7 like Adam recommended in another post to upgrade and it worked like a charm. Before I was using Odin 1.8.5 and I was getting Missing PIT partition error all the time.
Thanks all for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
stumpmuncher said:
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
Click to expand...
Click to collapse
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
What NOT to do with a new S4
RMXO said:
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
Click to expand...
Click to collapse
Did. Wouldn't have appealed for help without first making sure I followed the OP's instructions perfectly. I know the rules. I read the other posts before posting. I'm here for 2 things: To learn how to get the most potential out of my devices and to contribute from my experiences when I can. Thanks for your prompt reply though...
EDIT: solution to my stuck phone problem was solved by visit to ATT store for replacement. I can tell you what happened to my 7 day old device that brought it to the point where it would not load through Kies or Odin:
Eager to remove Samsung & ATT bloat stuff, I rooted using motochopper then used Titanium Backup to remove all ATT related apps & some of the Samsung apps. I got the unlock icon on lock screen as others have after root. I removed Superuser and replaced with SuperSU. Unlock icon went away and phone status went back to official. This is when I started noticing the Samsung text-to-speech program would frequently FC during the launch of few apps. Internet would also FC during certain operations. I read of others having success installing the stock ROM with ODIN and decided to give it a try. At first I got the no PIT error then finally after a few repeated attempts it moved past that point but then failed for some other reason during installation. I did notice a little activity on the progress bar on my device during Odin flash, but when the flash failed, that was it. My device was locked up. My PC & Kies would detect the device but could never connect or mount the device. My guess is that some of the Samsung apps I deleted were tied to the Samsung engines and the lack of their presence somehow caused FCs. Comments and questions appreciated.
Got the same Odin Mode Recovery Kies problem, No Pit fixed with ODIN 3.07 used PDA and loaded normal firmware.
I know this isnt the right place for this thread, but i lost my other login credentials and had to start fresh, so Im posting here....
Device: SM-T230NU
Problem: I used a website outside of XDA to root my device. I followed the instructions precisely too, I than unplugged the device hoping that replugging and restarting odin would fix the problem i have/had as displayed by the picture. I than tried rebooting the device, and got this error message: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. Well I downloaded Kies 3, and much to my surpise I got an error message about the samsung galaxy tab 4 7.0 not being supported by Kies 3. I am now downloading Kies 2.6, so I can atleast get this device booting normally.
If you knew this was not the place to post, why did you post a question here? A play by play of your device root is not of much interest to anyone! I hope you got it fixed up anyway!
It's been fixed. I found an alternate DL site that had Odin in the package..I used ODIN to run cf_auto_root which created that firmware upgrade issue...I had to Odin firmware from the links I found on these forums...it's rooted now though
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
Hi,
I'm having some trouble restoring the official FW on my old S4. The idea was that I wanted to give it to another family member, and would prefer to give them the stock FW rather than deal with whatever potential issues a custom FW offers (don't get me wrong, custom FW tend to be awesome, but I hope you get the picture).
I downloaded the latest, official FW for this phone and proceeded to try and flash it using Odin (MD5 file specified as PDA). Alas, this got stuck on flashing BOOT. So I tried to hook up the USB cable to a different USB port (I was using a hub before) and that went through BOOT, but failed with a write error later d.wn the line. This, alas, has been my experience thus far. I've tried other Odin versions and another FW version, all failing with the write error.
I've even tried to use KIES to restore, but now KIES fails to recognize the phone at all (neither normally, nor in the recovery mode as the phone suggests, nor can I "initialize" the phone, as apparently the GT-I9505 does not support it).
I do feel not all is lost, as I can get into the download mode without issues, but I'm unsure how to proceed. Please help.
OK, I think I got it.
It turns out my USB cable was sh*t. With a new USB cable it works fine.