Hi everyone,
sorry if this is posted in the wrong area, I'm new to the forum. I've read everything I can find, but I can't find a solution, assuming one exists.
I installed Renovate 3.1 by throwing the zip file onto my phone, and flashing it with TWRP. Turns out that isn't how it's suppose to be installed. Everything actually works well, except I've tried go back to stock (was thinking about selling the phone), but every time I try to load the stock firmware via Odin3, it fails. On my phone it says Secure check fail : (pit) or (bootloader).
Have I screwed my phone up beyond repair?
Thanks in advance.
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.
hello everyone
phone: i9505
I few weeks ago i rooted my phone (no problem) made a back up using rom manager on sdcard.
I decided to restore my phone with the back up i had made. Once it had finished restoring, I rebooted phone, go to unlock the screen and i am spammed with messages like: unfortunately process com.google.process.gapps has stopped and so on. Could not use phone because there was so many messages coming up!
my friend advised me to re-root it so i did, the problem didnt go away......
searched google found no answer to my problem
I thought un-rooting will solve the problem so I downloaded latest stock uk firmware (4.4.2) from sammobile, ran odin, put MD5 file in PDA, successfully un-rooted but when i turn my phone on now there is some writing on the top left corner it says (its pretty hard to make out it goes so fast):
REBOOT MODE = 0X684E39A6
POWER ON REASON = 0X1 (key power on)
CABLE: 0X00
DEBUG LEVEL MID
BOARD REV: 11
MSM CHIP REV 2
MSM HW ID: 0X71B0E1
BOOTLOADER VERSION: I9585XXEGNG8
BOOTLOADER AP SWAEV: 4
SPEED BIN: 2
ACPU PVS:2
SERIAL NUM:0X07FF9243
when i put my phone in dowload mode it says all this^ as well
after unrooting i went to setting and did a factory reset
ive tried rooting again, then unrooting but my phone doesnt seem fully unrooted? it says im on official, i also noticed i cant place widgets on screen
i tried google search but could not find an answer, mainly because i dont know what to search for but i know somethings not right
i just want my phone back to how it was, for now
if you need anymore info please let me know!
thanks in advanced!
Have you tried this guide to installing stock? I used this and it worked fine.
http://forum.xda-developers.com/showthread.php?t=2265477
There's a bit at the bottom about bootloops, I don't remember if I had one but I know I had to flash it anyway due to a problem I had after flashing the stock rom, so to be safe you should probably flash that after stock is flashed on as well.
lichking21st said:
Have you tried this guide to installing stock? I used this and it worked fine.
http://forum.xda-developers.com/showthread.php?t=2265477
There's a bit at the bottom about bootloops, I don't remember if I had one but I know I had to flash it anyway due to a problem I had after flashing the stock rom, so to be safe you should probably flash that after stock is flashed on as well.
Click to expand...
Click to collapse
thanks for the reply
ill try this and seee how it goes! i hope it gets it sorted
HI all,
So I today I messed up and I need your help :crying:. Basically here's whats going on: I decided to root my phone since I found that battery was complete garbage, so I decided to root the phone with TWRP and Odin and after flash a new kernel for my phone as well as SU. Everything went fine. However, when i tried to reboot my phone to get a custom rom i wanted, it keps telling "kernel is not seandroid enforcing" and would be stuck in a boot loop (which apparently is normal and would just need to flash a rom for it to work). Finally I just decided to boot factory, so I can get to my files and put that damn custom rom. Long story short, I was able to put it, wiped system in TWRP and flashed this new rom only to get another error "THis package is for device trltetmo, this device is trltexx". Now I couldnt even factory reset anymore. At this point I decided to flash my back up that I did before and yet ANOTHER problem "cannot restore system mounted read only". After couple of hours of research, I needed to change the name of the file to system.image.mbn i think, I changed a file called system.ext --> system.image.ext. Needless to say that it didnt work. Final thing I decided to do is simply to flash a stock rom with odin and reverse the root, so I downloaded a stock rom for note 4, started the whole process with odin and now it is stuck at system.img.ext4....and i have no clue what to do, I dont know even know what I did before is the problem or it is something else, all i know is that odin is stuck at that message. Should I just let it go, should I stop it? Help! please
Wow, true hardship you get it back running?
Try using Kies and doing firmware upgrade mode to see if it can download and load the stock firmware for that device.
Greetings.
I tried to flash the original firmware of my SM-G530H (4.4.4) using odin ( Odin3_v3.10.6 ) but every time it fails right at the beginning of the process.
I download the firmware (brazil/claro) from the Sammobile website, did everything that this tutorial told me to (androidmtk.com/flash-samsung-stock-rom-using-odin) but it fails every
time.
It is not a connection problem because odin recognizes the device and the process starts, but it fails right after the beginning.
Does anyone know what might be happening?
Thank you!
I forgot to mention that the phone is still working. I want to flash the stock rom because I rooted and the battery seems to be having some issues after that.
My problems started when I did this root (http://forum.xda-developers.com/gra...lly-rooted-galaxy-grand-prime-t2935607/page40).
I noticed it changed the baseband of my phone from to HVCU to HCXU, and according to what i have understood from my searches that's why i keep receiving the error message "Error: Secure Check Fail : aboot" on the phone every time I try to flash the original firmware (http://www.sammobile.com/firmwares/download/42103/G530HVCU1ANL4_G530HZTA1ANL4_ZTA/).
Does anyone know how can I fix it?
Thank you very much! :good:
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.