Database Info

The Impossible to root S3.

OS information:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
using the guide and downloads from here.
http://forum.xda-developers.com/showthread.php?t=2046439
the first thing i do is flash the proper bootchain from the thread, this flashes fine. no issues, no hiccups.
next thing i do is flash the recovery from the same thread, which is where i run into problems.
on the desktop i get this.
on the phone i get this.
when i reboot the phone and go back into download mode everything is back to normal like nothing bad ever happened.
comepletely confused and fed up with this thing, i've rooted literally dozens of phones and even the historically difficult G2 and Sensation were not this much of a PITA.
any advice on what's causing my issues would be a huge help.

Did you extract the recovery???
http://androidfirmwares.net/Guide/Details/9
Sent from my PACmaned, ktoonzified SGS3!

I had a problem with the TWRP recovery on the site like this and switched to the CWM recovery and it flashed. remember to check MD5s.
ps.. remember to close odin after you flash the first bootchain. and reopen it to flash the recovery.

By the way the filename looks, it looks like he did not extract the file.
Sent from my PACmaned, ktoonzified SGS3!

Casper34 said:
By the way the filename looks, it looks like he did not extract the file.
Sent from my PACmaned, ktoonzified SGS3!
Click to expand...
Click to collapse
He did. It's supposed to be a tar.md5.
Sent from my SCH-I535 using Tapatalk 2

tylerlawhon said:
He did. It's supposed to be a tar.md5.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
http://img42.imageshack.us/img42/3254/odin2ng.jpg
Look at the way the file name is. It still shows .tar.md5.
Sent from my PACmaned, ktoonzified SGS3!

I just flashed the no wipe version of blk3 or later firmware and go from there. I do this since the no wipe firmware already comes with a modified boot chain.

OP try this
http://d-h.st/GXW
I've personally used this successfully. Just download and use in ODIN.
Once rooted, you can easily change/update recovery using the EzRecovey.apk

andybones said:
OP try this
http://d-h.st/GXW
I've personally used this successfully. Just download and use in ODIN.
Once rooted, you can easily change/update recovery using the EzRecovey.apk
Click to expand...
Click to collapse
flashed the bootchain from the other thread, rebooted back into Download mode, attempted to flash your file, same result.
can i flash back to VRBLK3 and and proceed from there?
kidhudi said:
I had a problem with the TWRP recovery on the site like this and switched to the CWM recovery and it flashed. remember to check MD5s.
ps.. remember to close odin after you flash the first bootchain. and reopen it to flash the recovery.
Click to expand...
Click to collapse
Checked MD5's and both of the recovery options with no change.

crazy talk said:
flashed the bootchain from the other thread, rebooted back into Download mode, attempted to flash your file, same result.
can i flash back to VRBLK3 and and proceed from there?
Checked MD5's and both of the recovery options with no change.
Click to expand...
Click to collapse
That doesn't make any sense
I would yes, flash back to LK3, and proceed from their..
Best of luck, friend.

try it like this.
make sure you checked usb debugging enabled
open odin.
boot phone into download(odin) mode
plug in phone
flash bootchain as a pda
once rebooted unplug phone.
Close odin.
restart odin
uncheck auto reboot
boot phone into odin mode.
connect phone.
flash recovery.
pull battery and go from there.

flashed the no wipe BLK3 then started with the steps from the guide in the first post and got stuck in the exact same place.
is there any other option?

When you flashed the vralec bootchain you kept "auto reboot" checked correct? Then waited after the phone rebooted and odin said success before disconnecting? Did you run odin as administrator on your pc? Are you using the oem usb cable? I've recently flashed com 6.0.2.3 and twrp 2.4.4.0, so I know they've both at least worked. I once made the mistake of disconnecting my phone from odin when the status light was blue and the scroll log said finished, but now I always wait for the green success status light, idk if that might have happened to you.
Surge1223

I'm having the exact same issue. Is this a common problem?

Surge1223 said:
When you flashed the vralec bootchain you kept "auto reboot" checked correct? Then waited after the phone rebooted and odin said success before disconnecting? Did you run odin as administrator on your pc? Are you using the oem usb cable? I've recently flashed com 6.0.2.3 and twrp 2.4.4.0, so I know they've both at least worked. I once made the mistake of disconnecting my phone from odin when the status light was blue and the scroll log said finished, but now I always wait for the green success status light, idk if that might have happened to you.
Surge1223
Click to expand...
Click to collapse
yes i'm giving everything plenty of time before disconnecting. running in admin mode, using a known good USB cable, port and PC that i've used Odin through on my Note II without fail.

crazy talk said:
yes i'm giving everything plenty of time before disconnecting. running in admin mode, using a known good USB cable, port and PC that i've used Odin through on my Note II without fail.
Click to expand...
Click to collapse
Could you try using another computer?
Sent from my SCH-I535 using Tapatalk 4 Beta

SlimSnoopOS said:
Could you try using another computer?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
no change.
EDIT: as an aside, i can flash the complete BLK3 rom successfully without issue. so i don't believe it's a communication issue.

crazy talk said:
no change.
Click to expand...
Click to collapse
Aight, and how about trying Odin 1.85? I remembered someone from awhile back saying they used this and it helped them in their case. Here's one such thread mentioning Odin 1.85. There are a few more.
Edit: Wait, I reread your OP. All you're trying to do is flash CWM correct? And it does the same thing when you Odin flash TWRP? How about if you download and flash either recovery via Odin from Invisiblek on Rootz?
Alternatively, could you Odin flash the rooted VRBLK3 or VRBMB1 by mrRobinson? If so, how about downloading GooManager then installing TWRP by pressing Menu/Install OpenRecoveryScript. Since these are pre-rooted, you could install TWRP this way.

This is so strange. You probably already tried but you may have a bad download.
I agree with snoop, as long as you have a rooted Rom you can use goo manager to install TWRP through that app. Alternatively, you can try flashing a recovery through ez recovery. Andybones keeps a thread maintained in the themes and apps section for all recent recovery images. All you have to do is load it in the directory and hit flash.
If that still doesn't work, I'm speculating that you might have a problem with your recovery partition. I'd guess that a PIT file may fix it, however I wouldn't necessarily try that without further input from someone with more experience. A PIT file would repartition your phone and possibly fix the error you're getting in ODIN. This could happen if ODIN is attempting to place the file in your recovery partition, but is unable to properly locate the space for it. This may explain why everything you're trying is failing.
Sent from my SCH-I535 using Tapatalk 2

Wait just reboot the phone in recovery by holding power button+ menu + vol up and see what comes up, it might ask you to disable system recovery
Surge1223

Need help after losing root on CM10.2

Could someone please advise on how to keep me from doing any further real damage to my phone?
Here's my story...
Tried to flash Mastamoon's 8/9 build of CM10.2 on my VZW Galaxy S3 from CleanRom7. Used Cwm recovery. It flashed fine but I realized as I was setting up the phone that I lost root. In a panic, I booted into recovery and tried to restore 2 of my CleanRom nandroids but I got an md5 mismatch on both. So then I was able to restore my original 4.0.4 nandroid I made directly after rooting my phone last year. But still no root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pls note the baseband version as I flashed invisiblek's firmware zip about a week ago while on CleanRom. I realize now that there was a procedure in Mastamoon's thread about what to do if root was lost but I didn't read it before trying to restore my nandroids.
My phone is functioning right now but I would greatly appreciate any help trying to reroot and get back to where I was. Can I try to flash 4.3 again and then follow the steps in mastamoon's op to achieve root again? Thanks in advance
Sent from my SCH-I535 using Tapatalk 2

sijak said:
Could someone please advise on how to keep me from doing any further real damage to my phone?
Here's my story...
Tried to flash Mastamoon's 8/9 build of CM10.2 on my VZW Galaxy S3 from CleanRom7. Used Cwm recovery. It flashed fine but I realized as I was setting up the phone that I lost root. In a panic, I booted into recovery and tried to restore 2 of my CleanRom nandroids but I got an md5 mismatch on both. So then I was able to restore my original 4.0.4 nandroid I made directly after rooting my phone last year. But still no root.
Pls note the baseband version as I flashed invisiblek's firmware zip about a week ago while on CleanRom. I realize now that there was a procedure in Mastamoon's thread about what to do if root was lost but I didn't read it before trying to restore my nandroids.
My phone is functioning right now but I would greatly appreciate any help trying to reroot and get back to where I was. Can I try to flash 4.3 again and then follow the steps in mastamoon's op to achieve root again? Thanks in advance
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Are you absolutely sure root is gone? Try to download SuperSU and try to update the binaries.
Sent from my SCH-I535 using Tapatalk 2

Hey thanks for the quick response. I followed your advice. Dl'd Supersu from play store. Tried to update binaries and it said failed.
Sent from my SCH-I535 using Tapatalk 2

sijak said:
Hey thanks for the quick response. I followed your advice. Dl'd Supersu from play store. Tried to update binaries and it said failed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Look in the CM10.2 thread for a superuser.zip file that you can flash in recovery. Once you boot up CM10.2 you need to go into the Developer Options and change Root Access to apps and ADB.

So is it safe to boot into recovery from where I am now and flash 10.2 again. Then download and flash the superuser zip file? Just not sure what order to do things. Also I know i have to go into developer settings and change root access to apps and adb there. I'm a bit of a noob and just wanna do things in the right order. Thanks for taking the time to help out.
Sent from my SCH-I535 using Tapatalk 2

sijak said:
So is it safe to boot into recovery from where I am now and flash 10.2 again. Then download and flash the superuser zip file? Just not sure what order to do things. Also I know i have to go into developer settings and change root access to apps and adb there. I'm a bit of a noob and just wanna do things in the right order. Thanks for taking the time to help out.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'd boot into recovery and flash SU first then flash your ROM.

Tks I'll give it a try.
Sent from my SCH-I535 using Tapatalk 2

Would it be ok to flash supersu first then the rom and gapps in the same session?
Sent from my SCH-I535 using Tapatalk 2

sijak said:
Would it be ok to flash supersu first then the rom and gapps in the same session?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It should be fine.

I'm not able to boot into cwm via Rom manager. Nothing happens when I click ok. Is there another way to get in to cwm to flash those files? Btw, thanks for your patience.
Sent from my SCH-I535 using Tapatalk 2

sijak said:
I'm not able to boot into cwm via Rom manager. Nothing happens when I click ok. Is there another way to get in to cwm to flash those files? Btw, thanks for your patience.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
With the phone off hold down home, volume up and power until you see the Samsung logo flash, it should then boot into recovery. You could change your recovery to TWRP through the Goo Manager app if you wanted. Do you have Recovery showing in your Power menu when you go to turn the phone off?

airmaxx23 said:
With the phone off hold down home, volume up and power until you see the Samsung logo flash, it should then boot into recovery. You could change your recovery to TWRP through the Goo Manager app if you wanted. Do you have Recovery showing in your Power menu when you go to turn the phone off?
Click to expand...
Click to collapse
There's no option in the power menu to boot into recovery. I was hesitant to manually boot into recovery figuring I'd end up in the stock recovery not cwm.

sijak said:
There's no option in the power menu to boot into recovery. I was hesitant to manually boot into recovery figuring I'd end up in the stock recovery not cwm.
Click to expand...
Click to collapse
You'll be fine, you really can't mess it up, you no longer have a stock recovery since you have CWM installed.

sijak said:
There's no option in the power menu to boot into recovery. I was hesitant to manually boot into recovery figuring I'd end up in the stock recovery not cwm.
Click to expand...
Click to collapse
do some more reading. you don't seem to fully understand what you are doing. if you have CWM , your stock recovery is no longer existent.

airmaxx23 said:
You'll be fine, you really can't mess it up, you no longer have a stock recovery since you have CWM installed.
Click to expand...
Click to collapse
I ended up in Android System Recovery so I just rebooted. Would this have anything to do with a locked bootloader? I had previously used Ez-unlock v1.2 when I first rooted but its not on my phone anymore.

sijak said:
I ended up in Android System Recovery so I just rebooted. Would this have anything to do with a locked bootloader? I had previously used Ez-unlock v1.2 when I first rooted but its not on my phone anymore.
Click to expand...
Click to collapse
So you're on a stock Rom right? Just accept an ota update then reroot again.
If not, then odin back to stock and reroot.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
So you're on a stock Rom right? Just accept an ota update then reroot again.
If not, then odin back to stock and reroot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes, stock rom. I am on the first nandroid I made right after rooting before I started flashing custom roms. I should read up about odin-ing back to stock. But I think I'll take the ota and reroot. Would the firmware I flashed a couple of weeks ago cause any problem with an ota update? Guys, thanks for your time and advice.

Lorenzo VonMatterhorn said:
do some more reading. you don't seem to fully understand what you are doing. if you have CWM , your stock recovery is no longer existent.
Click to expand...
Click to collapse
Before I lost root, I was using cwm as my custom recovery. When I was finally able to restore this stock rom nandroid, I downloaded rom manager again and it shows cwm 6.0.3.1 as my current recovery. But I can't boot into it as I described earlier. I also tried to flash cwm again thru rom mgr but it gave me an error notice.

sijak said:
Yes, stock rom. I am on the first nandroid I made right after rooting before I started flashing custom roms. I should read up about odin-ing back to stock. But I think I'll take the ota and reroot. Would the firmware I flashed a couple of weeks ago cause any problem with an ota update? Guys, thanks for your time and advice.
Click to expand...
Click to collapse
No it wouldn't, if you take the ota it'll rewrite your rom, firmware, kernel, and recovery and put everything on the same base. Then once you reroot everything will be on the vrbmf1 base and you should be good to go.
The reason nothing is able to flash recoveries is because you lost root permission. The only way for you to get it back is to reroot since you're unable to use SuperSU.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No it wouldn't, if you take the ota it'll rewrite your rom, firmware, kernel, and recovery and put everything on the same base. Then once you reroot everything will be on the vrbmf1 base and you should be good to go.
The reason nothing is able to flash recoveries is because you lost root permission. The only way for you to get it back is to reroot since you're unable to use SuperSU.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well, the ota failed to update. Tried a few times. So i'm gonna start reading about odin-ing back to stock. Hope i can count on advice from you guys as I move ahead. Thanks again.

Nexus 5 bricked using Flash 5.0.1 N5 Tool

Used Flash 5.0.1 N5 Tool to update to Android 5.0 from CM 11 kitkat, after using the tool when booting the phone it boots into a endless "android guy?" loop, nothing else happens. Tried to resolve it by installing TRWP to attempt to flash a custom mod, now booting it boots into a flickering TWRP screen and nothing else. Not sure what to do

T3hBraveBoss said:
Used Flash 5.0.1 N5 Tool to update to Android 5.0 from CM 11 kitkat, after using the tool when booting the phone it boots into a endless "android guy?" loop, nothing else happens. Tried to resolve it by installing TRWP to attempt to flash a custom mod, now booting it boots into a flickering TWRP screen and nothing else. Not sure what to do
Click to expand...
Click to collapse
Either do a factory reset from the stock recovery or flash the factory image using fastboot. Don't use a tool kit.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Either do a factory reset from the stock recovery or flash the factory image using fastboot. Don't use a tool kit.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
When I try to use cmd itself, nothing works. does not reconignize the commands

T3hBraveBoss said:
When I try to use cmd itself, nothing works. does not reconignize the commands
Click to expand...
Click to collapse
Do you have fastboot installed on your pc? Google 15 second adb install xda.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Do you have fastboot installed on your pc? Google 15 second adb install xda.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I used this tool already
Can you PM me? I PM'd you

T3hBraveBoss said:
I used this tool already
Can you PM me? I PM'd you
Click to expand...
Click to collapse
I don't do pm. What specific problems are you having running the fastboot commands? Toflash the factory image it's as easy as double clicking on the flash-all batch file after you extract the factory image
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I don't do pm. What specific problems are you having running the fastboot commands? Toflash the factory image it's as easy as double clicking on the flash-all batch file after you extract the factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Trying to flash without a toolkit, cant even do cd desktop.. Whats happening
"The system cannot find the path specified"

T3hBraveBoss said:
Trying to flash without a toolkit, cant even do cd desktop.. Whats happening
"The system cannot find the path specified"
Click to expand...
Click to collapse
If you're using the 15 Second adb install you should not have an issue with the path. If you've used the tool kit since running the 15 Second install run it again. Then go to the folder where you downloaded and extracted the factory image and find the flash-all.bat and double click that.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you're using the 15 Second adb install you should not have an issue with the path. If you've used the tool kit since running the 15 Second install run it again. Then go to the folder where you downloaded and extracted the factory image and find the flash-all.bat and double click that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Decided to boot into OS X and try to resolve this used this guide (without a toolkit)
http://www.androidrootz.com/2013/11/how-to-unroot-nexus-5-complete-stock.html
but at the last step, this came up (pretty sure its not fixed yet)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

T3hBraveBoss said:
Decided to boot into OS X and try to resolve this used this guide (without a toolkit)
http://www.androidrootz.com/2013/11/how-to-unroot-nexus-5-complete-stock.html
but at the last step, this came up (pretty sure its not fixed yet)
Click to expand...
Click to collapse
Any reason you're flashing such an old version of android?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Any reason you're flashing such an old version of android?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I updated the with the latest files, its going through the process now. But last night I used to a toolkit (from the same site) to flash factory image and it was stuck on erasing cache for the whole night. Myself doing it manually is now on the same step. How long is is supposed to "erase cache"

T3hBraveBoss said:
I updated the with the latest files, its going through the process now. But last night I used to a toolkit (from the same site) to flash factory image and it was stuck on erasing cache for the whole night. Myself doing it manually is now on the same step. How long is is supposed to "erase cache"
Click to expand...
Click to collapse
It'll take a little while but not all night. Maybe 15 minutes.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 02:53 PM ---------- Previous post was at 02:41 PM ----------
jd1639 said:
It'll take a little while but not all night. Maybe 15 minutes.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
If cache isn't flashing you may have bigger issues. What happens if you lock your bootloader and then re-boot the device? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
It'll take a little while but not all night. Maybe 15 minutes.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 02:53 PM ---------- Previous post was at 02:41 PM ----------
If cache isn't flashing you may have bigger issues. What happens if you lock your bootloader and then re-boot the device? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Its locked now, getting error

T3hBraveBoss said:
Its locked now, getting error
Click to expand...
Click to collapse
You're getting the error because your bootloader is locked, that's good news. Unlock the bootloader and follow method two of the attached. Flash ask the images except for cache. See if that works
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5 using XDA Free mobile app

This is what I tried doing, I was using the same commands. It takes forever to wipe the cache

jd1639 said:
You're getting the error because your bootloader is locked, that's good news. Unlock the bootloader and follow method two of the attached. Flash ask the images except for cache. See if that works
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is what I tried doing, I was using the same commands. It takes forever to wipe the cache

jd1639 said:
You're getting the error because your bootloader is locked, that's good news. Unlock the bootloader and follow method two of the attached. Flash ask the images except for cache. See if that works
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I actually used a similar but different method to the link you sent, in progress on method 2 but, trying to flash userdata.img results in error error: cannot determine image filename for 'userdata.img'

jd1639 said:
You're getting the error because your bootloader is locked, that's good news. Unlock the bootloader and follow method two of the attached. Flash ask the images except for cache. See if that works
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
so I was able to flash stock back on, but it still has twrp and won't factory reset and wont boot

T3hBraveBoss said:
so I was able to flash stock back on, but it still has twrp and won't factory reset and wont boot
Click to expand...
Click to collapse
That's weird. Did you flash the recovery.img? It appears that some of the partitions aren't flashing.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
That's weird. Did you flash the recovery.img? It appears that some of the partitions aren't flashing.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is what I get what I try to wipe

Please help me ASAP

Hi i tried rooting my phone and it failed and now it just stays on the logo saying recovery is not seandroid enforcing. I've tried using odin to bring it back to stock form but it just fails. I only got the phone on saturday and if my mum finds out she'll kill me. Please help me ASAP.

I have same problem b4 bro but when i flashed stock rom downloaded from sammobile then flash it via odin then it works again.

itsme...KG said:
I have same problem b4 bro but when i flashed stock rom downloaded from sammobile then flash it via odin then it works again.
Click to expand...
Click to collapse
Do you know a way to fix this, and thanks for replying

So you want to reflash your phone to make it stock again?
If that's the case you can download the newest stock files from sammobile (WARNING SLOW ASS DOWNLOAD)
Once you've downloaded the latest firmware you can flash it to your phone with odin, it will make your phone stock again
Once you have done that, go into the recovery and factory reset. (By holding the powerbutton+home+volume up whist the phone is turned off)
This will however wipe your data. I advice you to make a backup beforehand.
Then just setup the phone like a new phone, or restore it from a backup on samsung's cloud (if you have a backup there).
Hope this helped.

BillyLeader said:
Hi i tried rooting my phone and it failed and now it just stays on the logo saying recovery is not seandroid enforcing. I've tried using odin to bring it back to stock form but it just fails. I only got the phone on saturday and if my mum finds out she'll kill me. Please help me ASAP.
Click to expand...
Click to collapse
Most probably you flashed wrong ROM. So please let us your model number ? (g920i or g920f or g920t,...) and your country. .. so you can take right stock rom to revert back..
Galaxy s6 very very hard to hard brick. . So don't worry you can get the phone [emoji1]
Sent from my SM-G920I using Tapatalk

sendhiloo7 said:
Most probably you flashed wrong ROM. So please let us your model number ? (g920i or g920f or g920t,...) and your country. .. so you can take right stock rom to revert back..
Galaxy s6 very very hard to hard brick. . So don't worry you can get the phone [emoji1]
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Doesn't the "recovery is not seandroid enforcing" appear at the top left of the boot screen regardless of the rom? I thought it was because of the non-stock recovery.

Yes.now he want to back to stock rom
.
Sent from my SM-G920I using Tapatalk

sendhiloo7 said:
Yes.now he want to back to stock rom
.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Okey, so we are on the same page

teleqraph said:
Okey, so we are on the same page
Click to expand...
Click to collapse
Yeah. Once he provide the info. We can help him
Sent from my SM-G920I using Tapatalk

When you flash a custom recovery, you need to boot to recovery on your first reboot, otherwise your phone will override it. Flash your custom recovery again, and when you restart your phone, hold volume up, power and home button.

my model is G920F

Billy Leader said:
my model is G920F
Click to expand...
Click to collapse
Which country?
Sent from my SM-G920I using Tapatalk

recovery is not seandroid enforcing <- this text means you have custom recovery.
But as the guy said s6 replaces the custom recovery as soon as you reboot it after flashing custom recovery,so you need to boot back in recovery mode(hold the vol up,power,home button as soon as it reboots).
and just go to any website (sam mobile and download the suitable stock rom for your mobile,country p.s slow download)
have you disabled knox before trying to root it or before flashing stock rom with odin?
try to put it in download mode then flash that stock rom
and as you said its in boot loop,you can fix it,its not bricked

sendhiloo7 said:
Yeah. Once he provide the info. We can help him
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
My model G920F

If you want to restore stock back. Please download stock rom for g920f from samfirm tool.
In the tool put model and region . Once you downloaded , flash the rom using odin tool.
In the tool pls check decrypt automatically
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G920I using Tapatalk

sendhiloo7 said:
If you want to restore stock back. Please download stock rom for g920f from samfirm tool.
In the tool put model and region . Once you downloaded , flash the rom using odin tool.
In the tool pls check decrypt automatically
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
First time I find this tool. Is this usable for any version?

jefkim666 said:
First time I find this tool. Is this usable for any version?
Click to expand...
Click to collapse
Yes. I always use this tool download stock firmware.
we will get full download speed, not like sammobile.com dead slow speed.

Where do i get the file?

sendhiloo7 said:
Yes. I always use this tool download stock firmware.
we will get full download speed, not like sammobile.com dead slow speed.
Click to expand...
Click to collapse
I recommend anyone to follow these instructions from @sendhiloo7 if you need to download stock firmware. It is WAY faster than other methods. ?

Root samsung galaxy s3

I rooted my samsung galaxy s3 (shv-e210s) yesterday. After root my phone got slow. I can't got maximum speed on my phone and phone restarted sometimes automatically. So I unroot my phone immediately. Then problem solved and phone working normally. I want know why my phone get slow after root and how to root galaxy s3. (I use king root app to root my phone)
(Sorry for my bad English)
Sent from my SHV-E210S using Tapatalk

ap mobile ko falash kr do ap ka mobile fast ho jay ga
Sent from my SM-A7100 using Tapatalk

saleemsahu100 said:
ap mobile ko falash kr do ap ka mobile fast ho jay ga
Sent from my SM-A7100 using Tapatalk
Click to expand...
Click to collapse
Please use English language
Sent from my SHV-E210S using Tapatalk

my english is week but i tried i say you fulflash your mobile then problum solw
Sent from my SM-A7100 using Tapatalk

saleemsahu100 said:
my english is week but i tried i say you fulflash your mobile then problum solw
Sent from my SM-A7100 using Tapatalk
Click to expand...
Click to collapse
How to ful flash? Can you give me a tutorial or article link?
Sent from my SHV-E210S using Tapatalk

[email protected] said:
How to ful flash? Can you give me a tutorial or article link?
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
[email protected] said:
I rooted my samsung galaxy s3 (shv-e210s) yesterday. After root my phone got slow. I can't got maximum speed on my phone and phone restarted sometimes automatically. So I unroot my phone immediately. Then problem solved and phone working normally. I want know why my phone get slow after root and how to root galaxy s3. (I use king root app to root my phone)
(Sorry for my bad English)
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
Hello, Kingroot may cause many issues in addition to many privacy and security concerns
however to root your device:
-enable OEM unlock
-get SuperSU.zip from chainfire's website
-put it in the phone
you need the twrp to root your device and as there is no exact twrp for your device i9300 twrp seem to work on your device here is the link: https://dl.twrp.me/i9300/twrp-3.1.1-0-i9300.img.tar.html
-go to odin and uncheck auto reboot in options
-put phone in odin mode and flash the twrp image in AP/PDA option
-now when the flashing is done take battery out and put it back
-press volume up and home and power buttons
-swipe the arrow if TeamWin Recovery Porject appeared
-press install
-go to where you saved the zip file and press on it
-wipe the arrow
-once rooting is done reboot device
TIP: you can now recheck the auto reboot option
hope this helps

-Hope- said:
Hello, Kingroot may cause many issues in addition to many privacy and security concerns
however to root your device:
-get SuperSU.zip from chainfire's website
-put it in the phone
you need the twrp to root your device and as there is no exact twrp for your device i9300 twrp seem to work on your device here is the link: https://dl.twrp.me/i9300/twrp-3.1.1-0-i9300.img.tar.html
-go to odin and uncheck auto reboot in options
-put phone in odin mode and flash the twrp image in AP/PDA option
-now when the flashing is done take battery out and put it back
-press volume up and home and power buttons
-swipe the arrow if TeamWin Recovery Porject appeared
-press install
-go to where you saved the zip file and press on it
-wipe the arrow
-once rooting is done reboot device
TIP: you can now recheck the auto reboot option
hope this helps
Click to expand...
Click to collapse
I try to find correct chainfire root file for my phone. But I can't find correct root file for my phone. Chainfire's root files compatible for android 4.4.4 but my phone android version is 4.3 (my phone model is shv-e210s)
If you can please tell me other way...!!!
(Sorry for my bad English)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SHV-E210S using Tapatalk

[email protected] said:
I try to find correct chainfire root file for my phone. But I can't find correct root file for my phone. Chainfire's root files compatible for android 4.4.4 but my phone android version is 4.3 (my phone model is shv-e210s)
If you can please tell me other way...!!!
(Sorry for my bad English)
Click to expand...
Click to collapse
Did you flash twrp?
Flash this through twrp
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip

-Hope- said:
Did you flash twrp?
Flash this through twrp
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Click to expand...
Click to collapse
Are you sure this root files compatible for android 4.3?
Sent from my SHV-E210S using Tapatalk

[email protected] said:
Are you sure this root files compatible for android 4.3?
Click to expand...
Click to collapse
It works on all versions

[email protected] said:
Are you sure this root files compatible for android 4.3?
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
To help you understand, flashing SuperSU.zip in TWRP will root any android version.
But....
Before you try flashing TWRP, verify that your device does not have a locked bootloader, some S3 model numbers that have 4.3 had locked bootloader. TWRP can not be flashed on devices with locked bootloader.
If your device does not have a locked bootloader you can flash TWRP using Odin, but if it is locked DO NOT flash TWRP using Odin because it will damage your device and you'll have to repair it.
If your bootloader is unlocked and you successfully flash TWRP, boot into TWRP and use the "install" option to flash the SuperSU.zip file and then you will be rooted.
Reboot and enjoy your rooted device.
I recommend booting back into TWRP and immediately use the "backup" option to create a backup of your stock firmware.
If you have issues with your device after this, you can boot into TWRP and use the "restore" option to restore the backup that you made, this will return your device to exactly what you had when you create the backup, similar to Windows Restore.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
To help you understand, flashing SuperSU.zip in TWRP will root any android version.
But....
Before you try flashing TWRP, verify that your device does not have a locked bootloader, some S3 model numbers that have 4.3 had locked bootloader. TWRP can not be flashed on devices with locked bootloader.
If your device does not have a locked bootloader you can flash TWRP using Odin, but if it is locked DO NOT flash TWRP using Odin because it will damage your device and you'll have to repair it.
If your bootloader is unlocked and you successfully flash TWRP, boot into TWRP and use the "install" option to flash the SuperSU.zip file and then you will be rooted.
Reboot and enjoy your rooted device.
I recommend booting back into TWRP and immediately use the "backup" option to create a backup of your stock firmware.
If you have issues with your device after this, you can boot into TWRP and use the "restore" option to restore the backup that you made, this will return your device to exactly what you had when you create the backup, similar to Windows Restore.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Can you tell me how I verify my phone bootloader locked or unlocked?
Sent from my SHV-E210S using Tapatalk

Im successfully rooted my device. Its worked to my device. Thanks your informations @Droidriven and @-Hope- [emoji11]
Sent from my SHV-E210S using Tapatalk

[emoji11]
Sent from my SHV-E210S using Tapatalk

[email protected] said:
[emoji11]
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
Don't forget to boot into TWRP and choose the backup option to make a backup of your stock ROM. Do this BEFORE flashing a ROM or making any kind of modifications to your device.
Don't be like the rest of the idiots that modify their device without making a backup first.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Thanks for your advices...!!!
Sent from my SHV-E210S using Tapatalk