Database Users

[Q] Not booting - Secure Fail: Recovery - any recommendations?

Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Any ideas?
Thank you

Go into Recovery mode (Vol Up + Home Button + Power Button) and Factory reset Data & Wipe Cache Partition...

moin786 said:
Go into Recovery mode (Vol Up + Home Button + Power Button) and Factory reset Data & Wipe Cache Partition...
Click to expand...
Click to collapse
Still get the same thing. It starts to boot to recovery then says something that fails then goes to the screen I have posted previous.
This is what first loads (pretty quick - had to reboot about 10 times to get it)
recovery booting...
SYS REV CHECK FAIL : no version
Secure : Secure Version Failure (recovery.img)
Set Warranty Bit : Recovery

norem0rz said:
Still get the same thing. It starts to boot to recovery then says something that fails then goes to the screen I have posted previous.
This is what first loads (pretty quick - had to reboot about 10 times to get it)
recovery booting...
SYS REV CHECK FAIL : no version
Secure : Secure Version Failure (recovery.img)
Set Warranty Bit : Recovery
Click to expand...
Click to collapse
What did you do prior to this? It looks like you flashed a custom recovery but Knox is terminating the boot process.

Have you tried to odin back to stock?
Sent from my Galaxy Note 3 ?

Trying to use Odin - downloading a stock ROM now.

No. You must get into download/Odin mode by pressing volume down + home + power simultaneously, then launch Odin, then connect phone to computer.
Sent from my SM-N900V using Tapatalk

norem0rz said:
yes, I was using clockwork and did something wrong...
doesn't the phone need to boot up before I can use Odin?
Click to expand...
Click to collapse
If you have a Verizon retail version of the Note 3, you can not use Clockworkmod recovery. Because your bootloader is locked. You can only use Hashcode's Safestrap (in the Development section).

cam30era said:
If you have a Verizon retail version of the Note 3, you can not use Clockworkmod recovery. Because your bootloader is locked. You can only use Hashcode's Safestrap (in the Development section).
Click to expand...
Click to collapse
+1
Which means you must be rooted first, then install Safestrap, which is a modified TWRP recovery. You can thank Verizon for that bullsh!t
Sent from my SM-N900V using Tapatalk

Thank you all - using Odin with this link http://forum.xda-developers.com/showthread.php?t=2483380
Got me back up and running.

Flash PIT - this will fix it
You need to flash the PIT with ODIN, latest version (3.09, I believe). Google for a download mirror that hosts the PIT for whichever type of note 3 you have, then flash it with odin (should work while in the invalid software screen). Then, if it doesn't reboot, just remove the battery and unplug that sucka. When it reboots, it should go back to download mode or just regular bootup. I recommend setting up adb, which makes it much easier to put the phone into whatever mode you desire with a simple dos command.

got out of it
this happened to me last night, I went into Odin mode "home, volume down, power button" instead of selecting odin mode from that menu I selected "reboot phone" (or something to that effect) My note 3 restarted......PHEW...... hope this helps someone

enable android recovery mode
SM-N90OV
ok so I once got to the point to where I could not but factory reset my phone and so I did settings > backup and restore > factory reset > YES I'M SURE!!! then my phone when into recovery mode as it should normally only to tell me that it could not enter recovery. Verizon's fault and now I cant access my recovery mode. is there a way to get back into it so I can finally flash a new rom. oh I had figured out how to get out of the boot loop thing by entering download mode and canceling. but it would be nice to be able to mess with this beast of a phone. please help me. I don't want to do something I wasn't supposed to. im not sure want to do with klms agent deals with knox right?

Em also one of the victim
hi
i am rooted (de la Vega ) safestrap installed using Jelly beans 6 & stock Rom as well. i don't know how but i am not being able to get in the recovery to format the device.
Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
What i do is getting into the download mode and only pressing Volume down to continue boot and Viola my phone restarts every time, but the thing which is pinching me is i can't able to format the phone.. Help required please.

xaneey said:
hi
i am rooted (de la Vega ) safestrap installed using Jelly beans 6 & stock Rom as well. i don't know how but i am not being able to get in the recovery to format the device.
Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
What i do is getting into the download mode and only pressing Volume down to continue boot and Viola my phone restarts every time, but the thing which is pinching me is i can't able to format the phone.. Help required please.
Click to expand...
Click to collapse
look at page one towards the bottom, the OP posted how to fix your problem

Solution
HI all
What worked for me is just ODIN
MI9 t0 MJE
and this is the beauty of ANDROID really happy to get it back..
Downloaded MJE for N900V http://www.sammobile.com/firmwares/3/?download=23535
Root through this in my case Vroot worked Kingo didn't work for me http://forum.xda-developers.com/showthread.php?t=2528707
Thn safe strap and all done

you guys and gals rock
saved my bacon ,was a little confusing to my novice self but downloaded odin to pc and ran it,downloaded clean vzw file and pit file ,plugged phone into pc and drivers loaded then ran odin and followed the steps.
Thank you very very much

[Q] Flash I9505 without going in download mode?

Hi,
I've got my good old 9505 I bought right at release on which the Volume UP button (or more likely whatever hardware it's connected to, as the button itself works perfectly normally) has become stuck pressed.
That causes a little problem - I can't enter Download mode anymore (Normal power up enters recovery due to the stuck key, Vol Down cancels Recovery and boots normally).
I had a custom ROM and recovery on it, and in order to send it for repair I obviously want to put it back to stock status, so I have reflashed a stock MI8 image I found using ODIN, using the custom recovery's "Reboot in Download mode" command.
Now the problem is I have bad luck and likely had an incompatible modem, and after booting even with cache/data wiped I have the Samsung keyboard crashing constantly and WiFi won't work.
Of course restoring the stock image wiped my custom recovery, so I can't use the same trick to get back into Download mode and reflash another modem.
I can't use Mobile ODIN or reboot menus with a "Reboot Download" option, as those requires root, but... rooting needs Download mode.
I can connect to Kies, but for my region it unfortunately says the current ROM is already the latest.
Does someone have an idea I didn't think about?

is there a way to reboot to download mode via usb debugging?/adb shell or something like that?

I found something that suggested it, however while I've painfully been able to go enable USB debugging (with the UI that locks and the "Samsung Keyboard has stopped" messages that appear between nearly every tap) adb devices returns nothing. Maybe the same issues cause debugging to fail too...

make sure that all instances of kies are stopped and also try reinstalling the drivers?

OK, found an app called "Kingo Android Root" that works from the PC through adb, and managed to root it again. It took some time to connect, but once it did it went through the procedure OK.
Then I could transfer the apk for "Quick Boot" to the phone through MTP, and its reboot menu worked to reboot in Download mode
Got a new modem flashed, and WiFi is back. The Samsung keyboard is still crashing every 5 secs, but I'll just try reflashing the OS, never know...

now that you can get to download mode, you can just restore everything back to stock? no? should fix any fc's you're getting, unless they are related to the physical fault with the volume up button being stuck?

Yes, it's just a matter of finding the right stock ROM... :\

OK, the MKF ROM for my country I found here works perfectly fine.
Issue closed then, hope this will serve other people who might end up in a similar situation
Now to see how the service center reacts to a stock config but with Knox flag set...

good luck, and don't forget to let us know how you get on with the service centre/knox situation.

Good news, received my S4 after a one week turnaround (shipping included), and it was repaired under warranty even with the Knox bit set and me having dismantled it (thanks Sammy for not putting "warranty void" stickers, pretty much the first manufacturer I see who doesn't!)

[Q] HELP corrupt bootloader Verizon S5 G900V

So i don't know exactly what has happened to get here. I have a new Verizon Galaxy S5 that I Towel Rooted and installed Safestrap. Things were going fine and I made a nandroid backup of my Stock slot. I decided to try Alliance rom in slot 1 which all went fine and i booted into Alliance. I was customizing my phone with colors and clock position etc. Some of the icons weren't there anymore so I decided to reboot to get everything loaded back in. Well when i hit reboot the screen went black and nothing came back on. Now when I turn it on I get the Galaxy S5 splash screen and blue words at the top saying "RECOVERY BOOTING...." then it shows the Android with it's chest door open and the globe spinning, then it goes to the Android laying down with a red triangle over its chest door, and then reboots. It just loops like this. Does this mean my bootloader is corrupt? Or can I Odin flash the stock firmware and PIT?

If your bootloader was corrupt, you'd either end up on the secondary bootloader page or have a nonresponsive, brick for a phone.
So corrupt bootloader was just your guess? Because I don't see any evidence for that yet. You've ended up on the Recovery mode page or at least that is what your description sounds like (a screenshot or photo would have been good). More than likely something is just messed up in your Safestrap or custom recovery configuration.
The most obvious options would be to either check and/or reinstall Safestrap /your custom recovery. Or if you prefer, revert to full stock, then proceed from there.
The last part that you wrote is unclear.. but you imply that you can't do a normal boot at this point? Can you boot to download mode then? Pull your phone battery for ten seconds.. then press and hold the volume down key, then the home key also and then the power key. You should boot to the black download screen that shows your Knox status. If this works, then you can flash a full stock firmware from there with Odin to stabilize your system.
.

Thanks fffft for your response.
As it turns out you are correct in that the bootloader is not corrupt because I can get to download mode. I tried flashing the stock firmware back on through Odin, but that didn't work, it still just looped. What finally did work is this thread http://forum.xda-developers.com/showthread.php?t=2784880 Thanks to Misterxtc. It must have needed the PIT as well.

Can't get my SM-G900F rooted... ("Recovery is not SEAndroid enforcing"?)

Hello there, beginner here.
I'm having issues getting my SM-G900F rooted, which is running Android 5.0. My phone doesn't reboot into recovery after flashing cf-auto-root, and the trouble shooting section about this issue doesn't help me too.
I used this cf-auto-root release, as it states to be the one for SM-G900F and Android 5.0.
I then followed these steps with the Odin version included in the download.
However, after flashing, my phone does not reboot into recovery, and just stays in Download mode, with Odin saying PASS.
I know that there's a trouble shooting section below in the steps I linked, but it is not helping me, or I don't understand it. In fact, I have several questions about these steps, and maybe someone can help me about it. Let me cite the original post and my questions about it.
...
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
Click to expand...
Click to collapse
First question arises here. How should I put my device into download mode if I wanted to use the "ADB reboot download" command? According to the steps, it is not connected to my PC at the moment. So I chose to get into download mode with VolDown+Home+Power.
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
Click to expand...
Click to collapse
As said, my phone does not reboot, even after Odin states "PASS". So I tried the steps explained in the following note:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens.
Click to expand...
Click to collapse
What is meant with "do the entire procedure again"? My phone is now sitting in download mode, with Odin saying PASS. Should I just press "Start" again in Odin? That does nothing on my phone.
Should I pull the battery? My phone is still on then, since it takes the power from the USB connection. So I disconnect it too? If I do that and put the battery back in, it immediately automatically boots, and I get the following error on my screen:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
And then it just hangs there, and installs nothing. If I try to restart it normally, it goes back to this screen, all the time.
If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
Click to expand...
Click to collapse
This does not work together with the behavior I stated before. When I pull the battery and the USB connection to turn it off, and insert the battery back in, it immediately boots up. I'm not sure if I was too slow pressing VolUp+Home+Power, but my phone still says the aforementioned SEAndroid error.
Can anybody help the noob I am? In what state is my phone now? Do I understand correctly that it indeed wants to boot into Recovery, but does not like it because it is not fulfilling some "SEAndroid security stuffs"? =3
Thanks for all the help in advance.
PS: These are the lines if I get back into download mode:
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START

Looks like I go another way now... just installing TWRP, what I mostly wanted (I think at least)...
When I was stuck with the SEAndroid boot all the time, I turned it off again and booted back into download mode, then flashed TWRP from here dl.twrp.me/klte/ (using the most recent *.tar file, and selecting it in ODIN as the PDA file).
After I did that, my S5 booted normally again. But as soon as I turned it off and tried to enter Recovery mode with VolUp+Home+Power, it first still spit out the 3 SEAndroid lines, but then TWRP showed up a second later... it offered me to install SuperSU as I wanted to reboot, which worked. When entering the SuperSU installer after my system booted, I selected the TWRP method to finally root my phone, and that seems to have worked. moving on now...
I just wonder if this is a normal procedure, or if I messed up somewhere so that it became so complicated.
Or maybe I'm just dumb.

DEAD!

Hello guys,
A friend of mine gave me his S6EDGE+ because it didnt boot anymore after he woke up. The night before that he installed an update but the phone worked fine after that.
The phone showed this message: http://imgur.com/a/cwLyM
I thought that it was easily fixed by flashing original 7.0 firmware but as you can guess i was wrong... It keeps rebooting right after the "Samsung Galaxy S6 Edge+" screen
So i tried to flash original 6.0.1 firmware but the same result
After that i flashed 7.0 again and after that twrp 7.0 but it never booted into twrp
So i flashed android 6.0.1 and the newest twrp for 6.0.1 but it still didnt booted into recovery and i am not able to boot in recovery.
After that i tried some older versions of twrp for 6.0.1 and it sometimes gave me the error: Recovery is not seandroid enforcing. I tried the same with 7.0 and older twrp versions, same results.
I also tried to flash 5.1.1 but i couldnt flash it.
What i also tried is to flash 7.0 bootloaders and after that 7.0 firwmare and the same for 6.0.1
I'm really desperate and dont know what to do anymore..
Current status: bootloop
I can enter download mode: http://imgur.com/a/XiS6Z

When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.

1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?

kdogguk said:
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
Click to expand...
Click to collapse
i can see that the images aren't working, ill fix that in a sec.
Yes i used odin and downloaded everything from sammobile because ive actualy paid them for de downloadspeed

justanpotato said:
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
Click to expand...
Click to collapse
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes

no, u need learn some things about Binary Vercion, ima sure u have a B3 in this moments, so , download any firmware with Binary 3, if need more infor about that, check here http://forum.gsmhosting.com/vbb/f68...combination-compatibility-w-o-errors-2189001/

ruubs said:
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
Click to expand...
Click to collapse
You've never stated the results of your stock firmware flashing, using Odin. This is key, this tells you whether the firmware was flashed correctly or not.. If you picked the wrong stock firmware to flash, Odin will show it "Failed."
If your buddy just updated firmware, then it's likely he's on the newest one, but check in SamMobile to verify if it's accurate. If shows the most current firmware was updated in January or something then he might not be on the most current one, as this shows that he's behind on updating his phone, so it's uncertain which it last updated to.
If I were you, I'd verify first whether the Odin flash passed or not, prior to attempting any custom flashing.. After Odins finished flashing in the upper right corner will either show "Pass" or "Fail," it needs to show "Pass" before you can proceed to do anything else, as this confirm whether the stock firmware flashed correctly or not.
If it doesn't Pass, you have flashed the wrong firmware. Might be good to verify with your buddy, which carrier he had originally. If you indeed have a Samsung S6 Edge+, with the larger 5.7 inch screen, the model numbers begin as so, "SM-G928x" with difference being the "x" at the end, which coincides with whichever carrier it's on, (e.g. "A" for AT&T, "T" for T-Mobile" - U.S. carriers).
It wouldn't be a bad idea to confirm whether you're using the most up to date version of Odin, either. Don't remember what that is but a quick Google search under this topic would do it.
Just for shyts and giggles, you did verify that your PC recognizes the phone, right? And that it lists under "Device Manager" correctly, as well as Odin recognizing it after you plugged it in?
If it does "Pass," it should reboot by itself into the stock firmware since prior to flashing you selected "autoreboot" and "reset time" if it doesn't reboot correctly or gets stuck on the splash screen, unplug it from the PC and manually boot it into stock recovery. Do this by first pressing the following buttons at the same time and holding them till the phone powers off, power button, home button, volume up and volume down.. After it powers off, push and hold, power button, home button and volume up, till the phone boot to stock recovery, amd of course you can let go of the buttons/keys. Then using volume buttons to select factory reset and pressing the power button to confirm the selection. After it factory resets you can then select reboot to system and it should boot normally and you've recovered the phone.
The upper left corner in Odin will show the results of the flash, there shouldn't be a reason for it not booting if it indeed shows "Pass," cuz this confirms firmware flashed correctly, if it shows "Fail" then you flashed the incorrect firmware. You'll need to locate the right one so that Odin shows "Pass," otherwise you wont ever recover your phone, regardless of anything else you find interesting to flash, bootloaders, TWRP, root, ect.. Don't flash anything else till you get the stock firmware flashed correctly. If you're unable to accomplish this then, I'd recommend calling Samsung or your carrier, is it still under warranty? My charging port broke after 2+ years, I have insurance though w/ T-Mobile, called them to see what my options were, was planning on fixing it myself to avoid the $175 insurance deductible, if I made a claim, but as it turns out, since I have insurance, the phones still under warranty and per the CSR, it will continue to hace warranty as long as I pay the $7/month insurance. Thought most warranties are 12 months but I wasn't going to correct her if she was wrong so I went ahead with it and 2 days later new phone came and I sent my broken one back! Old phone has lil scratches on the screen, couple lil dings along the sides, obviously an older phone but now I gotta new one, ita flawless!
It won't to try if this don't work out..
Good luck