I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anything with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. I am very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODIN MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
I think this doesn't look good. What should I do to make my phone be working again and not showing that black screen?
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do I need to unlock it to make my phone work again? Thanks so much for your time
Did you updated after rooting your SGS3 Verizon?
Games are a part of Life but Life is not a part of a game!
I am in the same position as a lot of people with the s3. I have the Verizon model and had it unlocked using Odin while it was on 4.2. I accepted the Verizon update to 4.3 forgetting that it unroots it. Some people are saying that the only way to get my phone unlocked again is to find a way to flash it back to 4.2 version. Is there ANYWAY to unlock it on the 4.3 without bricking it??? If there is, how so???? Please help!!
Sent from my SCH-I535 using xda app-developers app
Check modem version and your product code and massage me again!
Games are a part of Life but Life is not a part of a game!
Related
So I need to bring my phone in to a verizon store because I am having the SIM card issue that a lot of people are getting. What are some things I should check so they don't know I rooted/unlocked at one point in time?
I used odin and to bring me back to stock bloated. I did a factory reset. I am not rooted.
When I go into download mode, it says:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
I think that means my flash counter is at 0?
Is there anything else that I should confirm before I bring it in to the techs?
buddydude said:
So I need to bring my phone in to a verizon store because I am having the SIM card issue that a lot of people are getting. What are some things I should check so they don't know I rooted/unlocked at one point in time?
I used odin and to bring me back to stock bloated. I did a factory reset. I am not rooted.
When I go into download mode, it says:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
I think that means my flash counter is at 0?
Is there anything else that I should confirm before I bring it in to the techs?
Click to expand...
Click to collapse
You're good. The reps at Verizon wont know what to check anyways. The only way you will get caught messing with flashing is if you send it back to Samsung.
buddydude said:
So I need to bring my phone in to a verizon store because I am having the SIM card issue that a lot of people are getting. What are some things I should check so they don't know I rooted/unlocked at one point in time?
I used odin and to bring me back to stock bloated. I did a factory reset. I am not rooted.
When I go into download mode, it says:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
I think that means my flash counter is at 0?
Is there anything else that I should confirm before I bring it in to the techs?
Click to expand...
Click to collapse
Yes your flash count is zero. Don't forget to take the naked pics of your GF off your phone either :silly:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Same with mine I think it's called a bricked phone and think there is nothing we can do about it, hopefully someone has a solution
Might Work?
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Click to expand...
Click to collapse
I dunno if this will work for you. But I had the same message and when I booted in Download mode I just hit Cancel then rebooted and it worked?
If you flashed cyanogenmod, that means you're bootloader is unlocked, which is a good thing.
Can you get into CWM or TWRP? I don't have a samsung so i don't know about ODIN (i presume it's like flashtools for Xperia).
For as long as your phone vibrates (or does pretty much anything when you boot it up) your phone is not hardbricked, which is also good .
Try getting into CWM, shut down your phone completely, wait 5 seconds, then do: Volume Down + Home + Power key . This will get you into bootloader state and try reflashing your old backup, a stock rom or cyanogenmod.
First time with these softbricks is always the most fun ^^. Been there done that, i thought i spend 250 euro's on a phone that was broken .
Btw. Always make a backup for these kind of situations.
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help."...
Click to expand...
Click to collapse
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Ok how do i get it?
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
Ok so is do i do the same thing as i was trying to flash or something like grab a kies file( the ones that take 2+ hours to download) and then flash or get to factory reset with the 4.3 file? if so do you know where i can grab a 4.3 update file to restore? please help me if you have skype or PM me? thanks
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
I just recently ODIN flashed the latest 4.3 stock firmware for my TMO GS3 and then attempted to roll back to 4.1.2. It didn't brick my device, but it didn't work either. I would simply fail to install. I was able to reflash, through ODIN, the 4.3 stock firmware (actually used the root66 version). Then I was able to ODIN flash CWM recovery and install Dandroid 5.1, which is also a 4.3 based ROM. All is well now. I guess I simply can't go back to any previous 4.3 ROMs now, and I'm not sure about any AOSP ROMs. I may give a try at some point to see.
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I start to wonder if people research before doing anything.
To say again. You can't downgrade. You have Knox. You possibly tripped the Knox flag. Reflash the 4.3 stock ROM. If that fails, It's most probably eFuse, if It's 4.3.
(Basically, eFuse messes up your phone aka bricks You phone aka @#%& it up.)
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
---------- Post added 5th January 2014 at 12:05 AM ---------- Previous post was 4th January 2014 at 11:59 PM ----------
mcgrabowski said:
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
Click to expand...
Click to collapse
You're right. The locked bootloader messed those who didn't research about it's life's real bad. 4.3 supposedly has eFuse in it, which FU*CKS your phone. I read it up on the Samsung Knox website, and it said that eFuse "rewrites a read-only part of the phone, resulting in a unusable phone." If u triggered that, it'll be a hard brick, (in my knowledge)
Knox itself is irritating. The Knox Warranty Void counter, which max at 1, is unresetable, (even with JTAG, will brick if h try) so your warranty is *poof*
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
scottrf8 said:
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
Click to expand...
Click to collapse
When you were on 4.3, was that an OTA update or an ODIN flash of a stock firmware? Or did you just have a 4.3 ROM from the forums that you loaded (AOSP or rooted stock based ROM with Knox, etc., removed) with TWRP or CWM? Supposedly from what I've been reading if you take the 4.3 OTA or ODIN flash the stock 4.3, the bootloader gets updated, as Irwenzhao mentions above and I've experienced, where you CAN'T downgrade again to 4.1.2 or earlier. I believe that just means you can't go back to a fully stock pre 4.3. I THINK it just means you can't ODIN back to a factory image earlier than 4.3, which is what I experienced. But with TWRP or CWM, I believe I can still load other ROMs at will regardless if they are pre 4.3 or not.
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
scottrf8 said:
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
Click to expand...
Click to collapse
Just to make it clear, Knox is a bootloader, which means u can flash anything that's not a bootloader, but your warranty would be history. Flashing anything trips the flag, even 4.1.1/2 stock ROMs.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
Truthfully, that doesn't clear it up. Do the stock firmware through Kies or ota include a bootloader and that's why it won't install? Thanks
Flashing the stock firmware through kies, ODIN, or the OTA update will update the boot loader as far as I know and will ruin any chance of returning to stock and void your warranty. As long as you don't want to do that, I don't think it's too big of a deal.
At this point, I couldn't care less about the warranty. I would think it's expired now anyhow. As long as I can flash ROMs and boy the phone up and use it. I'm happy.
Sent from my SGH-T999 using xda app-developers app
Ok, so I recently (about 2 weeks ago) bought a brand-new/stock Samsung Galaxy S3 through Amazon as an upgrade for Verizon. When I received and activated it, etc, it went through a series of downloading/rebooting/installing screens which I assume means that it was updating to the latest official firmware.
Anyway, now I want to try putting a custom ROM on my S3 (I'm kinda new at this, like I just started reading about it yesterday), and as far as I know, it's running Android version 4.3, which is also said to contain Knox, which would prevent loading any custom ROMs. However, when I go into download mode on my S3, it says the following:
---------------------------
ODIN MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
----------------------------
As far as I can tell, there's no mention of Knox, but maybe there's something I'm missing?
As I said, I'm new at this, so I might be missing alot of stuff. But my main question is whether or not I'd be able to root my phone and flash a custom ROM without damage (barring my own mistakes)?
OblivionDawn said:
Ok, so I recently (about 2 weeks ago) bought a brand-new/stock Samsung Galaxy S3 through Amazon as an upgrade for Verizon. When I received and activated it, etc, it went through a series of downloading/rebooting/installing screens which I assume means that it was updating to the latest official firmware.
Anyway, now I want to try putting a custom ROM on my S3 (I'm kinda new at this, like I just started reading about it yesterday), and as far as I know, it's running Android version 4.3, which is also said to contain Knox, which would prevent loading any custom ROMs. However, when I go into download mode on my S3, it says the following:
---------------------------
ODIN MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
----------------------------
As far as I can tell, there's no mention of Knox, but maybe there's something I'm missing?
As I said, I'm new at this, so I might be missing alot of stuff. But my main question is whether or not I'd be able to root my phone and flash a custom ROM without damage (barring my own mistakes)?
Click to expand...
Click to collapse
Knox has nothing to do with locked bootloader from 4.3 version. You're no 4.3 so no flashing custom rom/kernel/recovery for you. There is a work around called safestrap and it's not fully functional yet...you just have to wait a bit ...longer see how everything play out!
Oh, I was under the impression that Knox was the thing causing the bootloader to be locked. You're saying that 4.3 is just universally locked for the time being?
Also, am I still able to root my S3 using Saferoot while it's on 4.3?
OblivionDawn said:
Oh, I was under the impression that Knox was the thing causing the bootloader to be locked. You're saying that 4.3 is just universally locked for the time being?
Also, am I still able to root my S3 using Saferoot while it's on 4.3?
Click to expand...
Click to collapse
Yes and Yes, you can use saferoot to root 4.3.
OblivionDawn said:
Oh, I was under the impression that Knox was the thing causing the bootloader to be locked. You're saying that 4.3 is just universally locked for the time being?
Also, am I still able to root my S3 using Saferoot while it's on 4.3?
Click to expand...
Click to collapse
Verizon is responsible for locking the bootloader. Knox has nothing to do with it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Verizon is responsible for locking the bootloader. Knox has nothing to do with it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Tell that to every s4 owner.
ThePagel said:
Tell that to every s4 owner.
Click to expand...
Click to collapse
All knox does is count, unless I'm missing something.
Sprint and T-Mobile both have knox on their 4.3 update, but neither have locked bootloaders.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
All knox does is count, unless I'm missing something.
Sprint and T-Mobile both have knox on their 4.3 update, but neither have locked bootloaders.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
+1
OK, so I just got a new LG G3 and I'm in the process of trying to reset my GS3.
Not long after I got the phone, I tried to root it (rather unsuccessfully). Didn't work out, so I restored to stock. Used the phone for the next 2 years or so with no issues.
Went to reset the phone and I got the unauthorized software warning.
I have now tried to restore to a stock ROM via ODIN V3.09 but I keep getting a fail at aboot.mbn.
What kind of information do you need to assist?
Thank you in advance!
Still searching the forum... still trying...
ODIN mode screen reads:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER AP SWREV: 2
I'm trying again but using this file this time:
androidfilehost.com/?fid=23501681358553154
OK, seems to be working perfectly now!
Much thanks to "BadUsername" for his diagnosis of the problem and providing a link to the correct tar ball!!!!
forum.xda-developers.com/showpost.php?p=54158110&postcount=242