So, I've done this before, and I've never bricked a device until now.
I tried installing a custom rom for my Galaxy S3 on Verizon, but when I restarted, it says this:
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.
I can't get into clockwork, or any bootloader. Any attempt to do anything brings this screen up.
Now, I can get into the Odin downloader. (Power, volume down and home). But, I can't figure out how to get a Rom to load. This is where I am stuck. I have downloaded a few roms, all stock, but none of them want to be recognized. I have no idea where to go. I've been downloading stuff for 5 hrs and nothing has worked, so now Im going to the forumns. Any help is appreciated.
I have the Verizon i-535 Galaxy SIII.
You did not brick your phone you failed to unlock your bootloader. There are 2 guides in the android dev section for rooting.
http://forum.xda-developers.com/showthread.php?t=1974114
Odin back to stock and next time after rooting make sure to use EZUnlock 1.2 to unlock the bootloader BEFORE loading a ROM
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.
Hi,
I've one (big) problem that I can't fix.
I've been using Android 5.0.1 for more than 1 year as I didn't want to upgrade (it worked pretty well) and because I had the S6 rooted with PingPong root.
However, one month ago it started to run slowly, crashing apps, ... so I decided that, as I wanted to wipe the device, why not upgrade to MM (6.0.1)??, so I did.
I did a backup of all my data and EFS folder and downloaded a 6.0.1 ROM to flash it with ODIN. Everything went OK and finished flashing the rom, but when the S6 restarted it showed this in the recovery:
'dm-verity verificztion failed...
Need to check DRK first...'
And I cant boot.
I've tried some tips that are here and in other websites:
- I've flashed stock rom again
- I've flashed a stock rom without cache.img file.
- I Can't flash some files as I've R/L ON. (I've been trying to disable it for many months but I couldn't).
But the S6 doesn't boot...
Thank you!
What worked for me.
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Critical_DoubleShot said:
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Click to expand...
Click to collapse
Thanks for your reply!
I tried to downgrade to 5.1.1 or 5.0.1 but I get an error.
(SW REV CHECK FAIL DEVICE 2 BINARY 1)
That happens when you don't have the right firmware you have.
You CANNOT downgrade to 5.1 or 5.0 since you are on 6.0. The bootloaders refuses to be overwritten.
Critical_DoubleShot said:
That happens when you don't have the right firmware you have.
Click to expand...
Click to collapse
I'm trying to flash another 6.0.1 ROM (a bit older), but I get 'CHECK FAIL. DEVICE: 4, BINARY:3'
I've read that DRK problems are related with EFS files, so... Can I restore EFS folder (I've a backup from Android 5.0.1) to solve?? I don't know how to restore it without booting into the sistem (and without custom recovery)
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thank you for your reply!!
I had the device rooted, but with PingPong root, so Knox is still 0. However it shows that the system is "custom".
I'll try the warranty, they may not notice the "custom", just the knox.
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
orbgel10 said:
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
If you are talking about DRK, the only way to fix it that I know of, other than hw replacement, is via 3rd party professional repair tool. (Octopus/Octoplus box)
If DRK is ok, phone boots normaly, if it is messed up, the only way of booting is with custom kernel which bypass DRK check.
You can check it in recovery, if messed up it will say DM verity failed on bottom of the screen.
Ok, i send my phone to fix, i will tell you what happened.
Sent from my Redmi 3S using Tapatalk
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thanks for your reply!!.
I took my S6 (925F) to a Samsung service center as you said. However, they told me that my S/N was incorrect (I bought a second-hand S6 edge, I think someone changed it) so they couldn't fix it.
Now I'm trying to use SmartSwitch to do a factory reset but it asks me for the S/N and I don't have the original one, just a S/N from a non edge S6 (920F). How can I do the factory reset without my S/N??? Can I use the serial number from another 925F??
Now I'm trying to find an engineering bootloader, to bypass the R/L and flash CF-AutoRoot, custom recovery.... but I only find it for 5.0.1 or... for galaxy S6 G925T, not F.
Finally, I managed to fix my S6 by myself!! (not really, but at least it boots...)
This is what I did:
- I found a factory binary for my S6 so I flashed it via ODIN
- I flashed a 6.0.1 ROM without hidden and without cache
Then it boots without any problems. However, now I can't get into recovery
I hope this will help someone
So i think i have completely ****ed up, hopefully you guys can give me some insight
I was on the process of properly rooting a samsung s7 that i got since the root checker said that it was not properly root.
i decide to fallow this guide
https://forum.xda-developers.com/ve...ot-guide-verizon-s7-s7-edge-sm-g930v-t3411015
But i after flashing the ENG using Odin
the phone just keep restarting, over and over, it also does the samething in recovery mode.
Notes:
The phone was displaying Custom unlock login screen (Before Flash)
Also it was 6.0.1 update
and I got the the 7.0 update, to flash the ENG
If there is anything you guys can advice, ill appreciate.
If it can go in downloading mode you can flash stock firmware and try rooting again.