[Q] SafeStrap Installs Recovery In 4.3 But wont boot into it - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I am on MK2 4.3 and I have Safestrap installed and I installed the recovery and when I reboot into recovery It goes to the Custom screen then it fails to Go to the Splash screen where I can choose to go into TWRP . I had this working on MF3 but I had bricked my phone and and had to flash the allin one to fix it . I am successfully rooted with safestrap installed .. ANY IDEAS would be greatly appreciated...Thanks By the way it Says Safe system : Not Active. I thought I remember it saying Active before
Also is there another way to install a Recovery. Im coming from a Tmobile GS2 where you could flash recovery once within Odin and after that you could just flash different versions of Twrp or Cwm when needed. No locked boot loader . I always thought HTC was the only phones with locked boot loaders . I have been doing a lot of reading prior to posting this question and have been up all night . After bricking last night and recovering from it I got a crash course with this device.

spirodave said:
I am on MK2 4.3 and I have Safestrap installed and I installed the recovery and when I reboot into recovery It goes to the Custom screen then it fails to Go to the Splash screen where I can choose to go into TWRP . I had this working on MF3 but I had bricked my phone and and had to flash the allin one to fix it . I am successfully rooted with safestrap installed .. ANY IDEAS would be greatly appreciated...Thanks By the way it Says Safe system : Not Active. I thought I remember it saying Active before
Also is there another way to install a Recovery. Im coming from a Tmobile GS2 where you could flash recovery once within Odin and after that you could just flash different versions of Twrp or Cwm when needed. No locked boot loader . I always thought HTC was the only phones with locked boot loaders . I have been doing a lot of reading prior to posting this question and have been up all night . After bricking last night and recovering from it I got a crash course with this device.
Click to expand...
Click to collapse
Check your root condition is valid. If you do not have root you can not install the safestrap recovery.
To go to the safestrap you do not need to reboot into the recovery. You simply reboot as normal and safestrap splash screen would come up.
You can use odin to flash the recovery in the download mode or you can use adb command to push the recovery.
AT&T and verizon G4 bootloaders are locked. You can not unlock like HTC S-off. You can only exploit the bootloader with different methods based on your firmware version.

Simply reboot the phone and on boot up it will show you the splash screen. Not active means that stock slot is still selected.
Sent from my SGH-I337 running GPE using Tapatalk

sway8966 said:
Check your root condition is valid. If you do not have root you can not install the safestrap recovery.
To go to the safestrap you do not need to reboot into the recovery. You simply reboot as normal and safestrap splash screen would come up.
You can use odin to flash the recovery in the download mode or you can use adb command to push the recovery.
AT&T and verizon G4 bootloaders are locked. You can not unlock like HTC S-off. You can only exploit the bootloader with different methods based on your firmware version.
Click to expand...
Click to collapse
Im an idiot. I just realized I have been using the safestrap.apk I had on my sd that was for MF3. This will be my problem

jmjoyas said:
Simply reboot the phone and on boot up it will show you the splash screen. Not active means that stock slot is still selected.
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
Im an idiot. I just realized I have been using the safestrap.apk I had on my sd that was for MF3. This will be my problem..Problem solved.When you said the wrong slot was selected it made a light bulb light up in my head..Thanks bro

Related

[Q] HELP !!! MF3 Root Fail Bricked

I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again using ODIN 1.85 from PC to phone, since I still couldn't boot my phone or recovery (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)
Thanks
Amb669 said:
I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)
Click to expand...
Click to collapse
Thanks for your reply.
I have the same problem as this guy
http://forum.xda-developers.com/showthread.php?t=2407950
Any Idea how to fix it?
jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
Dont thinknthere is antthing you can do. We have no return to stock method at this point in time. This is why it is important to follow forum rules and read and search before doing something youll regret, im nkt saying this to be mean...but there has been at least 5 people these past few days who have done the exact same thing as you and have gone in here looking for help...
My best advice, throw in some money for the bootloader unlock bounty and hope somethung happens soomer than later
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
http://forum.xda-developers.com/showpost.php?p=44570305&postcount=366
Fail to recover
Tylorw1 said:
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
the Kies can detect the phone buy it fail to recover it. the progress bar runs a little and stopped. error message pop out on PC screen says "Emergency recovery failed, Please contact Samsung Customer Service"

[Q] Custom Recovery Problems

I have an ATT galaxy s4 rooted with Towelroot. I've tried using GooManager to install TWRP but all it did was prevent me from booting into the recovery, I was able to get out of the loop by holding volume down and the home button and then hitting volume down to cancel going into download mode. Next I tried using Rom Manager to install CWM but the same thing happened. Now I can no longer boot into recovery, it just fails and goes into download mode. My question is should I just flash the stock recovery or is there a way to get a custom recovery?
Android Version, 4.4.2
Model Number, SAMSUNG-SGH-I337
Baseband Version, I337UCUFNC1
Kernel Version, 3.4.0-1125940
Build Number, KOT49H.I337UCUFNC1
Security Software Version, MDF v1.0 Release 2
I didn't know what you needed so I just put everything here, let me know if I missed something or you need to know anything else.
binavik said:
I have an ATT galaxy s4 rooted with Towelroot. I've tried using GooManager to install TWRP but all it did was prevent me from booting into the recovery, I was able to get out of the loop by holding volume down and the home button and then hitting volume down to cancel going into download mode. Next I tried using Rom Manager to install CWM but the same thing happened. Now I can no longer boot into recovery, it just fails and goes into download mode. My question is should I just flash the stock recovery or is there a way to get a custom recovery?
Android Version, 4.4.2
Model Number, SAMSUNG-SGH-I337
Baseband Version, I337UCUFNC1
Kernel Version, 3.4.0-1125940
Build Number, KOT49H.I337UCUFNC1
Security Software Version, MDF v1.0 Release 2
I didn't know what you needed so I just put everything here, let me know if I missed something or you need to know anything else.
Click to expand...
Click to collapse
Since you are on the NC1 firmware the only recovery software you can use is Safestrap 3.72. You can read more about safestrap in here.
tsonav peculiar
sway8966 said:
Since you are on the NC1 firmware the only recovery software you can use is Safestrap 3.72. You can read more about safestrap in here.
Click to expand...
Click to collapse
Thanks for the quick reply. I installed Safestrap 3.72 then hit Install Recovery, however the state still says Not Installed, also Reboot to Recovery option is greyed out. I tried going into the recovery manually with the same result as the previous 2.
You need to change selinux mode to permissive. The. Safestrap will be able to install recovery
Sent from my SGH-I337 running GPE using Tapatalk
means ynlyof
jmjoyas said:
You need to change selinux mode to permissive. The. Safestrap will be able to install recovery
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
Sorry for the noob question but I am completely new to this, how exactly do I go about changing the selinux mode to permissive?
Ok, so I used SELinuxModeChanger to change selinux to permissive, and safestrap now installed. Now when I use the button combination Volume Up, Home and Power, it still does the same thing. If I allow it to boot normally I get a red message saying Safestrap Disabled starting system in 10 seconds, then 2 options at the bottom for booting into recovery and to continue. Is this normal or did I do something wrong?
That's perfectly normal.
Due to the locked boot loader, we cannot replace the stock recovery. Safestrap works around this by being available in normal boot mode.
Safe strap originally supported ROM slots (multi boot) and would show enabled when one of the ROM slots was selected. We can only use the stock slot, so don't worry about the disabled part.
Sent from my SGH-I337 running GPE using Tapatalk
jmjoyas said:
That's perfectly normal.
Due to the locked boot loader, we cannot replace the stock recovery. Safestrap works around this by being available in normal boot mode.
Safe strap originally supported ROM slots (multi boot) and would show enabled when one of the ROM slots was selected. We can only use the stock slot, so don't worry about the disabled part.
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply and clearing that up. However I would like to know if there is any way to get back the stock recovery? It is a bit annoying that every time my phone turns off that it gets stuck in a little loop. Also this error message shows up on my phone and if anyone opens it, it immediately goes back into the loop. My mother loves playing with my phone a lot so I can see future problems coming. Anyway for me to flash the stock recovery back on?
You can uninstall recovery from the safestrap app
Sent from my SGH-I337 running GPE using Tapatalk
I did that but I am still not able to boot into the stock recovery, it just keeps getting stuck in the loop.
binavik said:
I did that but I am still not able to boot into the stock recovery, it just keeps getting stuck in the loop.
Click to expand...
Click to collapse
Check the NB1 ODIN thread and see if there's a link to just the recovery. If not you'll have to extract and flash it from the full tar with heimdall or package it in a zip or use an app or something.
DeadlySin9 said:
Check the NB1 ODIN thread and see if there's a link to just the recovery. If not you'll have to extract and flash it from the full tar with heimdall or package it in a zip or use an app or something.
Click to expand...
Click to collapse
When searching the forums I found this post http://forum.xda-developers.com/showthread.php?p=52167761. It seems like the correct stock recovery. So I just download this, go into Odin, put my phone into download mode, then what? I've never used odin before but I assume that I would need to point it to the file but not exactly sure under which slot or which options to be checked.
binavik said:
When searching the forums I found this post http://forum.xda-developers.com/showthread.php?p=52167761. It seems like the correct stock recovery. So I just download this, go into Odin, put my phone into download mode, then what? I've never used odin before but I assume that I would need to point it to the file but not exactly sure under which slot or which options to be checked.
Click to expand...
Click to collapse
Never flashed it before, but the op says to put it in the PDA slot. Just have auto robot and f.rest checked. Do not have partition checked
Sent from my Nexus 5 using XDA Free mobile app
Thanks everyone. My stock recovery is up and running again and I also now have safestrap as well. That stock recovery file worked just fine, I just had to put it under AP for odin 3.09.

[Q] Not able to install TWRP or CWM recovery. AT&T S4 I337

*****************************************
*******HELP HELP HELP*************
*****************************************
Hi,
I am unable to install CWM or TWRP recovery on my AT&T US - S4 I337. Baseband is NB1.
I have tried almost every option on xda , rom manager , twrp manager , loki method using emulator , 3 way tool , casual etc.
Loki gives loki aboot version error. Earlier phone was on NC1 , got it on NB1 using odin.
I want to get rid of original stock , which is loaded with lot of crap and want to install light weight custom rom.
Any pointers , help is highly appreciated.
Thanks.
rdxdha said:
*****************************************
*******HELP HELP HELP*************
*****************************************
Hi,
I am unable to install CWM or TWRP recovery on my AT&T US - S4 I337. Baseband is NB1.
I have tried almost every option on xda , rom manager , twrp manager , loki method using emulator , 3 way tool , casual etc.
Loki gives loki aboot version error. Earlier phone was on NC1 , got it on NB1 using odin.
I want to get rid of original stock , which is loaded with lot of crap and want to install light weight custom rom.
Any pointers , help is highly appreciated.
Thanks.
Click to expand...
Click to collapse
Download Free version of Rom Manager and after install see if it will not install which ever you want through it CWM or TWRP. Way I do it. You are Rooted???? Here is link https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en After install open and click on "Flash ClockworkMod Recovery" then it gives you choice of CWM or TRWP
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
rdxdha said:
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
Click to expand...
Click to collapse
You can't install custom recoveries. Our bootloader is locked. Your only option is using safestrap
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
U can't install a traditional recover. Since U are on NB1, your baseband is locked and your only option is Safestrap (TWRP). Read the instructions carefully at least once all the way thru and then proceed. Pay close attention because it's not like most phones. It works just fine. U can have a heavily modified Touch Wiz Rom or even now a AOSP based Google Play Edition Rom.
Proceed here:
[INDEX] All things AT&T MK2, NB1, and NC1 (including ROMs
rdxdha said:
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
Click to expand...
Click to collapse
What are you looking for in CWM recovery that is different for Stock recovery????
tailgunner9 said:
What are you looking for in CWM recovery that is different for Stock recovery????
Click to expand...
Click to collapse
I am trying to install custom rom , without safestrap. As bootloader is locked on my phone , I cant use CWM.
Using safestrap , I was able to install [AOSP] Official 4.4.3 - S4 Google Edition. but now I am not able to encrypt my phone.
Any idea on how to encrypt phone now ?

Strange Recovery Action

I booted into recovery using TWRP and my device went straight into download mode and I could not get out. I have a unlocked at&t SGH i337 originally with the old bootloader or MDL.
Tried installing the tar file with Odin and it failed. The only tar file I can get to work is NB1 4.4.2. I can't install a custom recovery now cause every time I boot to recovery the whole process starts over.
My device is rooted and shows custom in the bootloader so I'm sure I'm unlocked but even so I went through the unlock procedures just to be sure.
Does this mean I need to use SafeStrap now???
Thanks for your help
PapaMag said:
I booted into recovery using TWRP and my device went straight into download mode and I could not get out. I have a unlocked at&t SGH i337 originally with the old bootloader or MDL.
Tried installing the tar file with Odin and it failed. The only tar file I can get to work is NB1 4.4.2. I can't install a custom recovery now cause every time I boot to recovery the whole process starts over.
My device is rooted and shows custom in the bootloader so I'm sure I'm unlocked but even so I went through the unlock procedures just to be sure.
Does this mean I need to use SafeStrap now???
Thanks for your help
Click to expand...
Click to collapse
Yep. If you ODIN'd the NB1 tar, welcome to the club... your bootloader is now locked and safestrap is the only recovery you can use.
Just to verify, double check your bootloader...
http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4
Got this thing unlocked once sure there's a way there's a will ?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
PapaMag said:
Got this thing unlocked once sure there's a way there's a will ?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
The first stage is denial.
guut13 said:
The first stage is denial.
Click to expand...
Click to collapse
It was a short denial, looks as though my flashing days are over for the most part

Please Help Very Frustrated.

hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that
Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.
I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue

Categories

Resources