hello,
i got my Samsung Galaxy S4 from EE in England .. I9505 version .. and i found out that the Bootloader is locked .. so dose any one have any idea how to unlock it ..coz i need to root the device and change things up.. thanks in advance
As been stated multiple times, write protection does not mean it is locked. That's all dependent on your carrier
If I helped you out be sure to hit thanks
Swyped from a minimalist S2
MultiLockOn said:
As been stated multiple times, write protection does not mean it is locked. That's all dependent on your carrier
If I helped you out be sure to hit thanks
Swyped from a minimalist S2
Click to expand...
Click to collapse
thanks for your reply .. well how can i make sure? is it ok if i try flashing the root from odin?
MultiLockOn said:
As been stated multiple times, write protection does not mean it is locked. That's all dependent on your carrier
If I helped you out be sure to hit thanks
Swyped from a minimalist S2
Click to expand...
Click to collapse
thank you very much for this information .. well i tried to flash the root from Odin and it WORKS .... thank god the bootloader is not locked :good::good::good:
Mine too is from EE and had the same as yours. However attempted to root it yesterday. I ticked USB debugging and then used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Did you root yours following this method??
I'm stumped!!
flipflop104 said:
Mine too is from EE and had the same as yours. However attempted to root it yesterday. I ticked USB debugging and then used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Did you root yours following this method??
I'm stumped!!
Click to expand...
Click to collapse
thats weird .. the root is working just fine with me and the Titanium is working as well .. i changed the font and everything is ok with me ..
Untraceable said:
thats weird .. the root is working just fine with me and the Titanium is working as well .. i changed the font and everything is ok with me ..
Click to expand...
Click to collapse
How strange :crying:
Related
Got my shiny new Samsung Galaxy S4 on Friday and attempted to root it yesterday (I've previously rooted SGSII). I have used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Thanks in advance
flipflop104 said:
Got my shiny new Samsung Galaxy S4 on Friday and attempted to root it yesterday (I've previously rooted SGSII). I have used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Thanks in advance
Click to expand...
Click to collapse
Someone else has posted somewhere about the bootloader (write protection: enable). Could this be why it's not rooted even thought it appears to be?
flipflop104 said:
Got my shiny new Samsung Galaxy S4 on Friday and attempted to root it yesterday (I've previously rooted SGSII). I have used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Thanks in advance
Click to expand...
Click to collapse
Check your firmware, the new build MDM can't be rooted with CF.
If you have MDM then you can use Odin and flash any of MDE or MDF builds, they can be rooted easily , or use PRE-ROOTED OFFICIAL Rom from Development Section.
flipflop104 said:
Someone else has posted somewhere about the bootloader (write protection: enable). Could this be why it's not rooted even thought it appears to be?
Click to expand...
Click to collapse
Hahahah!!
If you don't know what you're saying then don't say anything!!
djembey said:
Hahahah!!
If you don't know what you're saying then don't say anything!!
Click to expand...
Click to collapse
Hehe I'm desperate!! lol
Did you install SuperSU or SuperUser from the market yet?
djembey said:
Check your firmware, the new build MDM can't be rooted with CF.
If you have MDM then you can use Odin and flash any of MDE or MDF builds, they can be rooted easily , or use PRE-ROOTED OFFICIAL Rom from Development Section.
Click to expand...
Click to collapse
Build is JDQ39i9505XXUAMDF which I thought was ok??? No???
ChronoReverse said:
Did you install SuperSU or SuperUser from the market yet?
Click to expand...
Click to collapse
Just done it
ChronoReverse said:
Did you install SuperSU or SuperUser from the market yet?
Click to expand...
Click to collapse
SU Binary Updater
Downloading manifest... okay! (in green)
Parsing manifest.... okay! (in green)
Latest version = 3.1.1 (in green)
Checking installed version = 1.15:SUPERSU (in red)
Fixing database.... okay! (in green)
Unpacking sutools... okay! (in green)
Checking current install path... /system/xbin/su (in green)
Downloading new binary... okay! (in green)
Gaining root access
Changing su file mode to 06755...
Making sure new su works... fail! (in red)
Is this lot just confirming what I already know - not rooted??
Not rooted. Is this AT&T or Verizon?
ChronoReverse said:
Not rooted. Is this AT&T or Verizon?
Click to expand...
Click to collapse
Neither, it's from EE in the UK and is the i9505
Any further suggestions??? Please.........
ken2802 said:
try supersu, from my point of view superuser seems to have a few problems with the s4 , atleast this was the case with my phone.
Click to expand...
Click to collapse
This seems to have done the trick. Titanium is now gaining root access.
Ok so I have followed the root method of "djrbliss" to the letter, every time I attempt the root it says "exploit failed", "cleaning up" and then "successful" then the phone reboots, I check to make sure it has rooted properly with one of the root checker apps and it says the phone doesn't have root access. So I have tried this multiple times taking suggestions from other threads and users such as ( clearing cache and doing a factory reset, and replacing the su and superuser files with the ones from the other cite) I was super jacked to root my new razr m but now I am not so sure, please help out guys.
WhatTheCuss said:
Ok so I have followed the root method of "djrbliss" to the letter, every time I attempt the root it says "exploit failed", "cleaning up" and then "successful" then the phone reboots, I check to make sure it has rooted properly with one of the root checker apps and it says the phone doesn't have root access. So I have tried this multiple times taking suggestions from other threads and users such as ( clearing cache and doing a factory reset, and replacing the su and superuser files with the ones from the other cite) I was super jacked to root my new razr m but now I am not so sure, please help out guys.
Click to expand...
Click to collapse
We need phone info build & ul status!
aviwdoowks said:
We need phone info build & ul status!
Click to expand...
Click to collapse
Android version 4.1.2,
Build number 9.8.1Q-78-1?
Sorry I'm not exactly sure what you mean
aviwdoowks said:
We need phone info build & ul status!
Click to expand...
Click to collapse
Oh and system version is 98.16.3.XT907.Verizon.en.US
It appears that you are on the most recent update, which, by itself is not rootable. However, there has been a work around achieved. I think it involves using RSD to go back to the previous version, rooting it, protecting root with Voodoo, reflashing the most current update, then restoring root via Voodoo. Anywho, check out the thread here: http://www.droidrzr.com/index.php/t...oot-razr-m-xt907-for-locked-devices-on-91878/
WhatTheCuss said:
Oh and system version is 98.16.3.XT907.Verizon.en.US
Click to expand...
Click to collapse
Seems you did not ud fully. Post a ss . Here are my steps if your BL is unlocked.
http://forum.xda-developers.com/showpost.php?p=44213644&postcount=5
Thanks! Ill let you know how it turns out
RikRong said:
It appears that you are on the most recent update, which, by itself is not rootable. However, there has been a work around achieved. I think it involves using RSD to go back to the previous version, rooting it, protecting root with Voodoo, reflashing the most current update, then restoring root via Voodoo. Anywho, check out the thread here: http://www.droidrzr.com/index.php/t...oot-razr-m-xt907-for-locked-devices-on-91878/
Click to expand...
Click to collapse
YES! it worked! thank you so much!
WhatTheCuss said:
YES! it worked! thank you so much!
Click to expand...
Click to collapse
Yay! Glad it worked out for you.
Okay, so I have this phone and the info attached to the imei DCNO Prod Test phone. It has the following build listed N900VVREBMJ5 test-keys. I checked for root access with a app and it didn't have root access. I tried to root with odin3 root_de_la etc and it came up with an error and was basically soft bricked. Was able to reload the pit file and eventually get it working again. I clearly don't know what I'm doing and bought this phone online and have learned very little since last night. It loads up with the custom logo etc etc. I'm looking load a regular stock rom onto or just a custom one, but no matter what I do I get an error.. Can anybody help.. thanks
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
shiftr182 said:
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
2swizzle said:
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
Click to expand...
Click to collapse
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
topurdue said:
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
Click to expand...
Click to collapse
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
topurdue said:
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
Click to expand...
Click to collapse
Anyways, i wiped deleted restarted and now i have root access.. blah blah ill be back im sure.
HI, I have a samsung Galaxy S4 I9500 with 4.4.2, I Have tried a lot to root it, but nothing seems to work form me, I flashed the last version of cwm,
try to root using the root your phone option in cwm and when I entered the super user app, the famous binary files problem comes up, I tried installing the super us by cwm
manually and the app just doesnt appear in my phone anymore, I want to try using philz touch method, so my question is, can I just flash by odin philz
even if i already have cwm already installed, or I have to do something extra before I tried to install philz? or do you know of any method that maybe I havent
tried yet that can make the root work?
plz help, Im tired of trying different options and nothing seems to work, everytime the binary options comes up, and now I dont even have or see the super user app anymore .
I thanks in advance for your replies.
Well. You can try this method: HERE.
- COUNCIL: Make all the process explained in the link I attached u. Reflash one second time the CF-Auto-Root package if you still without see the SUPERSU icon. Good luck :highfive:
Joku1981 said:
Well. You can try this method: HERE.
- COUNCIL: Make all the process explained in the link I attached u. Reflash one second time the CF-Auto-Root package if you still without see the SUPERSU icon. Good luck :highfive:
Click to expand...
Click to collapse
Thanks! didnt work but gave me an idea, i find the super user app and downloaded, i flash by the cmw, them i went to the play store, and downloaded the sper user app, and now it works.
Dont know whym but just work out.
Thanks for your reply!
warriorand said:
Thanks! didnt work but give me an idea, i find the super user app and downloaded, i flash by the cmw, them i went to the play store, and downloaded the sper user app, and now it works.
Dont know whym but just work out.
Thanks for your reply!
Click to expand...
Click to collapse
Enjoy your rooted machine :highfive:
Download SU from play store & later check for Root access via root checker app simple
Ankit Gor said:
Download SU from play store & later check for Root access via root checker app simple
Click to expand...
Click to collapse
thats exactly what I did, and it seems to works perfectly, thanks fot the follow up
Wondering if anyone in the know has heard of any development going on for this device? I recently bought one and it's not a bad phone for the price, but I've seen absolutely -nothing- on it anywhere online for the most part. It's barely root-able with what I've been able to find, and no custom recovery or really anything custom has popped up that I've seen.
Not sure if it's just that it's been only a few months since the phone came out, or if it's just not that great a phone. I upgraded from an HTC Desire 510 to this, and it was heavily customized/rooted/etc, and I want so badly to get back to where I was with it on this phone I cant stand it!
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
triiuzii said:
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
Click to expand...
Click to collapse
Right now rooting isn't the problem so much as keeping root. Because apparently the colonel has protection and will remove root whenever you reboot. That means things that require root on boot like backups, Xposed and a lot of other things won't work for us until someone complies a kernel with root protection removed. You can do some debloating and possibly the AdAway but that's about it right now.
*kernel. Damn voice to text.
That sucks. I upgraded from an LG Volt and I was able to do a whole bunch of stuff on it. The J3 is still very new, so hopefully development will happen soon.
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
mallamike said:
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
Click to expand...
Click to collapse
I guess that would depend on what you have experience with and what you can do. Thus-far root has been able to be achieved with Kingroot, though it wont stick through a power cycle (reboot/power off/etc), and using any of the methods available (at least that I'm aware of, only found two legitimate ones) to replace Kingroot with SuperSU (to facilitate having root stick past the reboot hopefully) causes a soft-brick every time forcing a re-flash of stock firmware through Odin.
At the very least make your voice heard, if nothing else hopefully more popularity will come this devices way and we'll see some development for it. My roommate is considering writing something for it, but it is a long process working solo, so anyone who has experience working with kernels or editing stock rom/writing custom roms feels up to helping out, shoot me a message and I'll get it over to him. He's a fairly experienced programmer and picks up what he doesn't already know pretty quickly.
Got one recently too. Would also appreciate any more information on rooting.
I have a J320A (AT&T) came stock with 6.0.1, can help test if needed
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Will this version of TWRP work on the Att variant running 6.0.1? Is there a way to root that device yet?
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
TechShui said:
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
Click to expand...
Click to collapse
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
what about the
SM-J320VPP = the verizon pre paid planversion. any working roots for me yet?
oh pretty pleeeeeez
Azhero said:
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
Click to expand...
Click to collapse
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
AnierinB said:
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
Click to expand...
Click to collapse
It doesn't work tried it 3 times. I even tried other ones no luck. They locked this thing down. Im surprise chainfire haven't tried this phone yet.
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Gotbootloopedtoomuch said:
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Click to expand...
Click to collapse
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
darknaio said:
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
Click to expand...
Click to collapse
Thank you so much! I tried using Odin to flash a software update and it worked perfectly. The phone is back up and running and all of the files are still there!
Right now i have TWRP 3.0.2 with supersu and i havent lost root yet also had no problem switching between backups, xposed working fine and also overclock too with setcpu, im currently running 5.1.1 using j320FN but TWRP was from j320F, i will put up links to the files if any of you are willing to try its up to you.
TWRP flash through odin : http://www.mediafire.com/download/blk7qa90vs6wik3/TWRP_3.0.2-0_SM-J320F.tar.tar
Supersu flash through recovery then update through playstore then install busybox after through playstore : http://www.mediafire.com/download/cpv2c71cp11x41f/UPDATE-SuperSU-v2.76-20160630161323.zip
Remember to turn on usb debugging and turn on oem unlock before flashing recovery, also if you manage to get recovery press they grey box on the right to change language to english. Hope this might help somebody on here because we really need full root for everyone.