Database Users

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.

Recovering from FRP Lock, did I brick my phone?

Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....

Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.

HELP!!!

Hi,
I recently purchased a Galaxy Tab 4.0 Lite (SM-T337a). I successfully rooted it using Kingoroot but upon restart the entire operating system seems to be gone. It is an overseas tablet (AT&T) that I got through the classifieds here in Australia.
There was nothing on there so I am not worried about losing data, I just want to be able to restore some form of OS onto it.
I can get into Android System Recovery <3e> and have tried installing the stock firmware through the SD card, but so far nothing has worked. I'm also having trouble getting my PC/Mac to identify it.
Any help would be appreciated.
Thanks!

http://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
download this and make the process
https://www.androidfilehost.com/?fid=529152257862688251

you have to flash the official firmware that you can find in sammobile and flash it whith odin. it should that your device is in download mod : down key home and power bottom on the boot

Look for the stock firmware for your model in this thread or somewhere in SamMobile, the language specified doesn't matter anyway cause you can always change that in setup but make sure that you've got the right one for your tablet. Then flash them using Odin

Us M3 updated to 5.0 but issues now

Hey Guys,
I tried updating my tablet from 4.1 to 5.0 and now i am having some issues. I have no keyboard and my fingerprint sensor doesn't work anymore. So i have no way of doing anything. When I try to bring up the keyboard i get the google voice window.Build number shows BTV-W09C128B350. Trying to understand the steps i need to do to get my tablet back and running normally. Do I need to go back to 4.1? Any help would be greatly appreciated.
Thanks
Erik

lamstang94 said:
Hey Guys,
I tried updating my tablet from 4.1 to 5.0 and now i am having some issues. I have no keyboard and my fingerprint sensor doesn't work anymore. So i have no way of doing anything. When I try to bring up the keyboard i get the google voice window.Build number shows BTV-W09C128B350. Trying to understand the steps i need to do to get my tablet back and running normally. Do I need to go back to 4.1? Any help would be greatly appreciated.
Click to expand...
Click to collapse
How did you do the update? Did you use Firmware Finder and it's DNS update or did you use the dload folder method? I used the Firmware Finder method and everything went smoothly even with an unlocked bootloader, You might try to use that method to reinstall Nougat, but you will need a keyboard to change your DNS settings to the one Firmware Finder needs and for that I suggest you try a USB keyboard connected through an OTG cable.
I will say that once you get Nougat working, the 5Ghz radio goes back to not working and the file that needs to be updated to enable it seems to have changed. So far, I can not find the correct file/setting to change to enable it. For me it is more annoying that I can't get it working than necessary because I am getting between 20 and 40 Mbs with the 2.4Ghz radio and that is plenty fast for what I ask this tablet to do.

johje said:
How did you do the update? Did you use Firmware Finder and it's DNS update or did you use the dload folder method? I used the Firmware Finder method and everything went smoothly even with an unlocked bootloader, You might try to use that method to reinstall Nougat, but you will need a keyboard to change your DNS settings to the one Firmware Finder needs and for that I suggest you try a USB keyboard connected through an OTG cable.
I will say that once you get Nougat working, the 5Ghz radio goes back to not working and the file that needs to be updated to enable it seems to have changed. So far, I can not find the correct file/setting to change to enable it. For me it is more annoying that I can't get it working than necessary because I am getting between 20 and 40 Mbs with the 2.4Ghz radio and that is plenty fast for what I ask this tablet to do.
Click to expand...
Click to collapse
i Johje,
I was able to rollback to Android 6.0 and 4.1. Do you have instructions on how you did the Firmware finder update?
Thanks again for your help
Erik

I used Firmware Finder to update to the most recent Full Update for the US version. After Selecting the firmware choose "Get an update through DNS" and follow the instructions. This will install the beta Nougat and restore your recovery partitions even if you have an unlocked bootloader. Once the tablet has Nougat installed, root by installing TWRP to the Recovery2 partition which will replace eRecovery and leave your main recovery in place. Use TWRP to Flash Magisk and PHH Superuser to root the tablet because from my experience SuperSU does not work for Nougat on this table. Once rooted you can enable the 5Ghz radio by finding the "cfg_btv_hisi.ini" file in the "cust_spec\vendor\etc" directory and then just change "band_5g_enable=0" option to "band_5g_enable=1" , after rebooting the 5Ghz wireless will be enabled.
Hope this helps

johje said:
I used Firmware Finder to update to the most recent Full Update for the US version. After Selecting the firmware choose "Get an update through DNS" and follow the instructions. This will install the beta Nougat and restore your recovery partitions even if you have an unlocked bootloader. Once the tablet has Nougat installed, root by installing TWRP to the Recovery2 partition which will replace eRecovery and leave your main recovery in place. Use TWRP to Flash Magisk and PHH Superuser to root the tablet because from my experience SuperSU does not work for Nougat on this table. Once rooted you can enable the 5Ghz radio by finding the "cfg_btv_hisi.ini" file in the "cust_spec\vendor\etc" directory and then just change "band_5g_enable=0" option to "band_5g_enable=1" , after rebooting the 5Ghz wireless will be enabled.
Hope this helps
Click to expand...
Click to collapse
I have also tried to update to 5.0. Everything seemed fine, but there is no keyboard, calc, file manager, etc. The "full..hw.." update seems to go really fast and it says it's done but there is no difference in what is on the tablet. Now I'm stuck at the point where it's A7.0, but I cannot do anything. Try getting google voice type to enter a complex email password
Any help on the second phase of the update is appreciated.
USA
C128
B350
used dload method to load.

nostep said:
I have also tried to update to 5.0. Everything seemed fine, but there is no keyboard, calc, file manager, etc. The "full..hw.." update seems to go really fast and it says it's done but there is no difference in what is on the tablet. Now I'm stuck at the point where it's A7.0, but I cannot do anything. Try getting google voice type to enter a complex email password
Any help on the second phase of the update is appreciated.
USA
C128
B350
used dload method to load.
Click to expand...
Click to collapse
Can you use Firmware Finder in your tablet's current state? If so, try updating using Firmware FInder's DNS method. You will need to be able to update your network DNS settings, though. Have you tried using a corded keyboard connected through an OTG cable or a bluetooth keyboard?
I did not try using the dload method because earlier attempts an updating Marshmallow to a more recent build always failed because of my unlocked bootloader.

johje said:
Can you use Firmware Finder in your tablet's current state? If so, try updating using Firmware FInder's DNS method. You will need to be able to update your network DNS settings, though. Have you tried using a corded keyboard connected through an OTG cable or a bluetooth keyboard?
I did not try using the dload method because earlier attempts an updating Marshmallow to a more recent build always failed because of my unlocked bootloader.
Click to expand...
Click to collapse
Unfortunately I could not fgure out how to do anything with it in that state (no keyboard, no internet, etc.). I tried to find a quality rollback for USA, but was not sure of what was out there that was correct. I ended up installing a EU version so at least it's working again (with old Android). I also realized the next day that my USB cord was bad and that's why I could not ADB or Fastboot anything. I'll try an upgrade again in the near future. Thx.

nostep said:
Unfortunately I could not fgure out how to do anything with it in that state (no keyboard, no internet, etc.). I tried to find a quality rollback for USA, but was not sure of what was out there that was correct. I ended up installing a EU version so at least it's working again (with old Android). I also realized the next day that my USB cord was bad and that's why I could not ADB or Fastboot anything. I'll try an upgrade again in the near future. Thx.
Click to expand...
Click to collapse
How did you install the EU old version? do you have link to the ROM?

[issue found][archived] FRP / OEM locked device that won't start OS

Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log

Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .