"Unauthorized Verizon Software" - Verizon Samsung Galaxy Note II

So, to start off, I messed up big time...
I'll give you the short version, but try to provide as much info as possible. I switched roms a few times in the last few days, going from Trents 8, to the newest Dirty Unicorns, to Trents 10 (where I started having issues) back to DU. I was trying to figure out where the issues came from, and came across someone saying that going from a touchwiz based rom, off of it, and back on, can cause problems. I then read that one of the best ways to fix this was to flash stock firmware and reflash new roms. I tried doing this...
Little did I know, it was a HUGE mistake for me to flash the 4.3 firmware through odin, and when the phone restarted, the "Galaxy Note II" page just kept flashing on and off for a few minutes. I think tried flashing older firmwares, with pit file, but I kept getting errors when I restarted saying that I didn't have Verizon Authorized Software.
Sooo this is where I'm stuck right now. I can't boot the phone at all, and when I try to flash the root66 firmware (the one that's supposed to fix everything?) I still get this verizon unauthorized page. It seems from what I've read that the bootloader relocked because of my 4.3 flash, and I can't find any info on how to unlock that. Anyone have suggestions? I'd really appreciate it!
Update: I retried the 4.3 firmware, and right now "Android is upgrading..." so I'm assuming this means my bootloader is locked, I've lost root, and all that jazz right? From what I've read so far there isn't any way to unlock the bootloader again, am I right? If so, can you point me in the right direction? Much appreciated!

xanderharris86 said:
So, to start off, I messed up big time...
I'll give you the short version, but try to provide as much info as possible. I switched roms a few times in the last few days, going from Trents 8, to the newest Dirty Unicorns, to Trents 10 (where I started having issues) back to DU. I was trying to figure out where the issues came from, and came across someone saying that going from a touchwiz based rom, off of it, and back on, can cause problems. I then read that one of the best ways to fix this was to flash stock firmware and reflash new roms. I tried doing this...
Little did I know, it was a HUGE mistake for me to flash the 4.3 firmware through odin, and when the phone restarted, the "Galaxy Note II" page just kept flashing on and off for a few minutes. I think tried flashing older firmwares, with pit file, but I kept getting errors when I restarted saying that I didn't have Verizon Authorized Software.
Sooo this is where I'm stuck right now. I can't boot the phone at all, and when I try to flash the root66 firmware (the one that's supposed to fix everything?) I still get this verizon unauthorized page. It seems from what I've read that the bootloader relocked because of my 4.3 flash, and I can't find any info on how to unlock that. Anyone have suggestions? I'd really appreciate it!
Update: I retried the 4.3 firmware, and right now "Android is upgrading..." so I'm assuming this means my bootloader is locked, I've lost root, and all that jazz right? From what I've read so far there isn't any way to unlock the bootloader again, am I right? If so, can you point me in the right direction? Much appreciated!
Click to expand...
Click to collapse
No, the bootloader can't be unlocked. You can at least get root with saferoot on 4.3.

Or downgrade with mobile tech videos

Related

[Q] Phone won't boot past Splash Screen.

Hi,
I've seen a few people with this problem and I've tried a few solutions, but here we go. Earlier today I took the phone out of my pocket and it was on the splash screen, rebooting it didn't fix it. Taking out the battery didn't seem to do much either. I can not get into recovery mode ( I'm holding power, home and volume up and all it does is constantly flash at me ).
I can get into download mode and I have tried flashing a stock Rom onto the phone, from the samfirmware site: http://www.sammobile.com/firmwares/3/?download=15332 this goes through the motions what appears to be successfully. But when I restart the phone I have the same problem and I still can't get into recovery mode.
I am a complete novice at this, the phone is still under its warranty so I was a little apprehensive to flash any other firmware but I fear that the phone may well be bricked. I have looked at this thread but as the Odin Flash hasn't technically failed I'm not too sure. I have downloaded the JellyBean leak to try and flash but again, I'm a little apprehensive to do so, other than that what are my options?
Thanks.
I bit the bullet and flashed the 'leaked firmware' and that seemed to have worked. Playing with it now, is it worth going back to stock or stick with this? Given its a test build.
davexeno said:
I bit the bullet and flashed the 'leaked firmware' and that seemed to have worked. Playing with it now, is it worth going back to stock or stick with this? Given its a test build.
Click to expand...
Click to collapse
Good man! That's exactly what you needed to do. Basically the JB leak firmware will wipe your device as it flashes, which is why it worked for you. As far as staying on that firmware goes, it is quite stable. You could stay on it if you like, or could just re-flash the stock ROM which you downloaded before. It should flash in Odin no problem now that you're booting.
Hopper8 said:
Good man! That's exactly what you needed to do. Basically the JB leak firmware will wipe your device as it flashes, which is why it worked for you. As far as staying on that firmware goes, it is quite stable. You could stay on it if you like, or could just re-flash the stock ROM which you downloaded before. It should flash in Odin no problem now that you're booting.
Click to expand...
Click to collapse
Hey, thanks for the reply!
Its actually my Misses phone. She seems happy with it now and on stock she was getting a "low memory" problem that I think was down to a perpetually generating log. Re-occurred no matter how many times we reset the phone, so I think I'll stick with this Rom to see if the problem comes back or not, it might actually end up being more stable.
Actually considering flashing my G Note now I realise how relatively easy it is!
davexeno said:
Hey, thanks for the reply!
Its actually my Misses phone. She seems happy with it now and on stock she was getting a "low memory" problem that I think was down to a perpetually generating log. Re-occurred no matter how many times we reset the phone, so I think I'll stick with this Rom to see if the problem comes back or not, it might actually end up being more stable.
Actually considering flashing my G Note now I realise how relatively easy it is!
Click to expand...
Click to collapse
Always good to get the Misses' phone going again to stay in the good books Actually, the JB leak is still stock.. it's not a custom ROM. It's just a pre-release JB firmware, almost identical to the officially released JB firmware. By all means see how you go with it, as long as you're not having any issues.
Yes, really easy! Nothing to stress over The same process will apply for a Note, you just have to use different firmwares obviously.

[Q] Bricked, recovered, OTA'd, bricked again. HELP!

I got a Note 2 yesterday, bought it used. I turned it on, everything seemed normal. I took it to Verizon, they activated it for me in the store, and while I was there, the lady activating it also accepted an OTA software update. I have no idea what version I was on, or what the OTA was. When I got home, the phone shut down as part of the OTA, and everything appeared normal. The little android with a box screen came up, cycled through the progress bar, etc. However, when it was done, the phone rebooted, and froze on the "Samsung Galaxy Note II" screen. I gave it a while, then battery pulled, tried everything I could think of. Couldn't get into the recovery menu. It would get to Odin, but that was it. Anyways, after a very stressful night working on it, I found the thread here:
http://forum.xda-developers.com/showthread.php?t=2040264
I downloaded the "Alternate Restore Mirror" link, put the phone in download mode, and installed from Odin on my computer. The phone booted up, everything worked beautifully.
Then, tonight at work, I checked for software updates, and was informed that there was an available update. I downloaded and installed it(I think the phone said it was 7MB?), and THE SAME THING HAPPENED. Phone is frozen on the "Samsung Galaxy Note II" screen. I plugged it into my laptop, put it in download mode, and did exactly what I did this morning. Odin says everything was successful, and reboots the phone. But it hangs on the "Samsung Galaxy Note II" screen, no matter what I do. I've tried searching, and followed every guide on how to unbrick it I can find, but no matter what software package I use, it fails on "sboot.bin". The only one that will work and not fail is the "Alternate" in the link above, but when I use that one I still have a bricked phone.
I -really- need advice here, guys. I'm in way over my head.
So, a little more information. If I have a ROM that doesn't have an sboot.bin attached to it, it will write just fine and not show any errors. However, the phone will hang up on the "Samsung Galaxy Note II" screen. If I write a ROM that tries to write sboot.bin, it fails. Every time.
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Jiggabitties said:
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Click to expand...
Click to collapse
I did. When it tries to write either image, it fails on sboot.bin. Every image that includes sboot.bin fails on sboot.bin so far. I -really- don't know what to do.
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
viper31573 said:
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
Click to expand...
Click to collapse
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
skiahmutt said:
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
Click to expand...
Click to collapse
not sure what else to tell you that would help
viper31573 said:
not sure what else to tell you that would help
Click to expand...
Click to collapse
Well, the best place I can think to start is to nail down exactly what's happening, then try to figure out WHY it's happening. Once I know the what and why, the solution should be apparent. While I'm not against someone chiming in with a fix that works but I don't understand, I'm here to learn, and would like to come to a better understanding of the issue.
First: what is sboot.bin?
Second: do I need a specific sboot.bin for a specific ROM?
Third: what can cause sboot.bin to fail?
Fourth: is there a way to push just sboot.bin to the phone through Odin or other software?
Fifth: am I fixating on sboot.bin when it's not my issue?
Sixth: did you really read my whole post and get to this point? Wow, thanks! I appreciate you taking the time to try and help me, folks like you are what make the community so strong!
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
viper31573 said:
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
No worries. Thanks for the effort at least!
Okay, a bit of an update... I unzipped and removed sboot from a couple of the ROMs I have, and they flashed successfully, but the phone still hangs on the "Samsung Galaxy Note II" screen... I feel like I'm on the verge of figuring this out, I -know- it's got something to do with sboot now.
Can I write JUST a bootloader to the phone without writing anything else? If so, how?
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
also try flashing the pit file.
mike7728 said:
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
Click to expand...
Click to collapse
I think it was the 4.3 update. So, what's the knox bootloader, and what ROM can I flash to the phone that'll work with the knox bootloader?

Camera seems like it's stuck in macro focus

Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.

[Q] Looking to move from Alliance 26 to DN3 5.2 NEED HELP PLEASE

As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Applejackson said:
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Click to expand...
Click to collapse
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Thanks for the reply.
devious_z said:
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Click to expand...
Click to collapse
Thanks for taking the time. I guess my main concern was with the bootloader and whether or not I had to upgrade it and possibly lock it accidentally, or if I could just stay with the bootloader I have now, which is actually VRUEMJB. Used the method outlined in the AllianceRom thread for flashing the ROM. Since I still have a virgin bootloader I didn't want to lock it. I think I'll just try flashing the ROM as I have it, after a wipe of course, and I can always flash a recovery backup if need be.
I did try looking through the info in the threads for the ROM, but there are thousands of pages on the original and 90+ in the [**UPDATED] Verizon DN3 thread. The ones that I have read through have some conflicting information, so this query is really just to eliminate any confusion on my part before changing anything I can't change back.
Update: Tried and failed.
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Applejackson said:
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Click to expand...
Click to collapse
I guess I would start with reinstalling the MJ9 firmware through odin, and then try the rom again. You mentioned you were actually on MJB earlier which doesn't sound right.

Secure Check Fail BOOTLOADER

Hello, im having massive problem here! Been at it for few hours but haven't came by a solution.
So, im selling phone so i decided to delete everything on it by TWRP, all data and the operation system, dont know if that was good idea.
Now, i have downloaded roughly 10 different stock ROMs with androids from 5-7 versions.
Any time i try to (flash)?/Install that stock rom im getting error on the phone about Secure Check Fail BOOTLOADER
Can't do nothing, i would really appreciate someones help!
Any screen shots or whatever needed please ask
kryspek said:
Hello, im having massive problem here! Been at it for few hours but haven't came by a solution.
So, im selling phone so i decided to delete everything on it by TWRP, all data and the operation system, dont know if that was good idea.
Now, i have downloaded roughly 10 different stock ROMs with androids from 5-7 versions.
Any time i try to (flash)?/Install that stock rom im getting error on the phone about Secure Check Fail BOOTLOADER
Can't do nothing, i would really appreciate someones help!
Any screen shots or whatever needed please ask
Click to expand...
Click to collapse
Flash the original firmware that the phone was running. Looks like bootloader is locked and preventing you from flashing firmware. Or try emergency recovery firmware in smart switch
I'm having the same problem on Note 9 Korean version, just trying to flash EU stock rom without triggering Knox in order to use Samsung Pay. There's just no way, when I flash the latest firmware downloaded from Sammobile it just gets stuck in SYSTEM, and the phone says Secure Check Fail: Bootloader. Don't know what to do anymore...
I've tried rebooting (both phone and computer), different versions of Android, running Odin as an admin... Even changing USB ports.
Please send help

Categories

Resources