Related
I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
I used this & it worked for me. Easy & quick: http://forum.xda-developers.com/showthread.php?t=2219803
I used the method mentioned above. Seemed to work perfectly. Very easy too.
Sent from my SPH-L720 using Tapatalk 2
Is the bootloader locked or unlocked on the Sprint version ?
Doesn't it have to be unlocked since they are reporting success rooting it?
mysongranhills said:
Doesn't it have to be unlocked since they are reporting success rooting it?
Click to expand...
Click to collapse
These threads are a bit confusing and i want to make sure before i decide to get one
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Wow thats crazy flashing something to your phone that isn't made for it.
opz187 said:
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Click to expand...
Click to collapse
We have a Stock (dump) build, which will be made available later today that flashes just fine.
If you're following the Engadget bootloader thread, i posted this earlier today..
http://forum.xda-developers.com/showpost.php?p=40844084&postcount=141
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
With regards to the boot methods - we have found something interesting.
@crawrj Had used the Moto root method and couldn't use Solid Explorer properly (i.e. couldn't open init.rc to view, copy system files, etc)
He then used the CF autoroot method and functionality came back.
While not specific enough to point at anything (we don't have logs to look at) I would advise you to check your apps that need root to make sure they function properly.
Just FYI.
I used the AT&T root method and worked fine for me only took 20 seconds.
http://forum.xda-developers.com/showthread.php?t=2252248
Just follow the steps and you will be rooted.
Sent from my SPH-L720 using xda premium
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Pheonix28 said:
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
Click to expand...
Click to collapse
Sorry didn't see this post.
Sent from my SPH-L720 using xda premium
benny3 said:
Is the bootloader locked or unlocked on the Sprint version ?
Click to expand...
Click to collapse
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Shadow_God said:
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
I have the HTC ONE and it has the Write Protection enabled also. We have a work around that can be flash through recovery, Not sure how you would implement it with Odin but here is the Link, Maybe you can look at it and may help
http://forum.xda-developers.com/showthread.php?t=2236849
JasonJoel said:
I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Motochopper, featured in you tube (http://www.youtube.com/watch?v=6fi1tYaoP0U) or (http://www.youtube.com/watch?v=GrvrXXFb2Uo) and be sure to Download the Drivers from the samsung website. For some reason, the drivers within XDA didn't work for me. Once I D/Ld the one specifically for Sprint, motochopper was able to communicate w/my s4 and rooted it:good:
I've not tried the motochopper stuff so I can't speak for that.
I can confirm that I had success the first time with no driver download needed when I used the CF auto-root method. I simply plugged the phone in, let Win7 download the drivers. I then put it in recovery mode (vol down, home and power button, release power button) and once win7 downloaded those (MHT etc) drivers I loaded the file through pda in odin and it went right through with no problems whatsoever.
The CF auto-root thread is here:
http://forum.xda-developers.com/showthread.php?p=39901375
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Unknownforce said:
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Click to expand...
Click to collapse
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
k2buckley said:
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
There is nothing wrong with staying with what you know.
Once we get a complete package, which may not be too far in the near future, we'll know more.
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
crawrj said:
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
Click to expand...
Click to collapse
I can attest to this and I'm still functional.
But, for the masses, there are a few of us willing to try if you want to wait.
Here's hoping we know more very soon. :beer:
Just got the notice. Updating now!
About damn time.
Sent from my XT1058 using XDA Free mobile app
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Yay, now do I unroot and try the OTA or do I wait for the full image.
ChrisAG said:
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Click to expand...
Click to collapse
You can? How? I didn't save the link to the release notes, and can't find them now.
thedosbox said:
You can? How? I didn't save the link to the release notes, and can't find them now.
Click to expand...
Click to collapse
Removing provider name from the Status bar:
Settings > Wireless & Networks > More > Mobile Networks > Show Mobile Network (check on or off)
I completely forgot about the carrier being removed. Really cool.
Sent from my XT1058 using XDA Free mobile app
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Steve-x said:
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Click to expand...
Click to collapse
Ugh... I have TWRP on mine. Can I just unroot, or I need to remove TWRP? (read: flash stock 4.4.2...)
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
R3dbeaver said:
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
Click to expand...
Click to collapse
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
R3dbeaver said:
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
Click to expand...
Click to collapse
If your bootloader is unlocked then it is very simple. Just go to fastboot and flash the TWRP recovery, once flashed you can access it from fastboot. TWRP will load, then you can just select to restart the phone from it and it will ask if you want to root the phone, swipe to confirm and it will do it and restart the phone for you. Once the phone is booted you will need to finish the process - it should prompt you to update SuperSU, I selected the play store option, it downloaded and installed and was done. From there do yourself a favor and install AdAway
waiting for the firmware image..... anybody knows where to get it?
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Steve-x said:
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Click to expand...
Click to collapse
Would you please send the download link when you are convinient? I searched and find this http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25, but looks something wrong with the system.img.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Thanks, works a charm, went from rooted 4.4.2 to 4.4.4.
PS- I grew up in Langley.
I don't know if it's dumb luck or not, but I didn't even unroot and was able to accept OTA to 4.4.4.
This is what I did to prepare the phone:
- Uninstall Xposed Framework from within the Xposed installer itself. Left the installer app in place.
- Changed recovery from TWRP back to factory.
- Enabled all apps previously disabled.
At this point my phone was still rooted. I accepted the OTA and everything worked fine.
Afterwards, I re-installed Xposed from the installer app, and re-disabled the apps I don't use. But left the factory recovery in place since I don't have a need to go into TWRP for now.
Everything is working fine.
No Rogers Update?
I just picked up a Moto X (Brand New) It came with 4.2.2 Im with Rogers, It is a Rogers phone , its been 2 hours now still no software update notification. When I try to check manually in about phone, system update. Keeps telling me my device is up to date??
Any one experienced this before? Or am I being to impatient
Now, a dummy question: what is Rogers?
Rogers is the Canadian phone company that's selling the original Moto X
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.
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk
Ok, I have rooted Galaxy S4s and 5s, usually the T-Mobile versions. I just ordered a used SM-G950F off ebay. It did not say if it was Nougat or Oreo.
Been searching, and have not found my answer, so I hope someone might be able to send me a link or advise me.
Want a rooted S8. Stock rom would be ok, but I would prefer custom down the road.
This is how I have been rooting the S4s and 5s
Put SuperSU zip on phone.
Then flash TWRP from Oden and not let it reboot. Do a battery pull, and then start the phone to recovery, then flash the SuperSU from TWRP.
Can I do this with the S8 ? (SM-G950F)
Thanks!
Come on you gurus, just take 1 minute and help me out ..... ffs
or maybe I posted the question in the wrong place, or your bored with the question.
I was a mod on another type of forum, I posted a sticky ... you dumb asses
ctbale said:
Ok, I have rooted Galaxy S4s and 5s, usually the T-Mobile versions. I just ordered a used SM-G950F off ebay. It did not say if it was Nougat or Oreo.
Been searching, and have not found my answer, so I hope someone might be able to send me a link or advise me.
Want a rooted S8. Stock rom would be ok, but I would prefer custom down the road.
This is how I have been rooting the S4s and 5s
Put SuperSU zip on phone.
Then flash TWRP from Oden and not let it reboot. Do a battery pull, and then start the phone to recovery, then flash the SuperSU from TWRP.
Can I do this with the S8 ? (SM-G950F)
Thanks!
Click to expand...
Click to collapse
There's literally dozens of guides on how to root the G950F. Come on you guru, do a Google search for one minute and help yourself out.
DAViiD__ said:
There's literally dozens of guides on how to root the G950F. Come on you guru, do a Google search for one minute and help yourself out.
Click to expand...
Click to collapse
I think I just set the hook ......
ctbale said:
I think I just set the hook ......
Click to expand...
Click to collapse
But seriously, I heard about a bootloader, (version 2?) that if I try to flash twrp might brick my phone. Have not actually pulled the trigger on buying a SM-G950F yet, but want to know if I can attain root on this device if its on android V8.0
I did try searching, but it just sits there with no results no matter what I put in the field. Might be because I am in Alaska and my internet SUCKS!
I am at the point I would pay someone like $20 via paypal if they know what they are doing and they want to give me Tech Support
ctbale said:
But seriously, I heard about a bootloader, (version 2?) that if I try to flash twrp might brick my phone. Have not actually pulled the trigger on buying a SM-G950F yet, but want to know if I can attain root on this device if its on android V8.0
I did try searching, but it just sits there with no results no matter what I put in the field. Might be because I am in Alaska and my internet SUCKS!
I am at the point I would pay someone like $20 via paypal if they know what they are doing and they want to give me Tech Support
Click to expand...
Click to collapse
The process I've followed is as follows.
Now please take into account that I flash twrp and part of that process is that data partition needs to be formatted, so make sure anything that's needed back it up.
Have a look at some roms, download one to your memory card.
Flash twrp via Odin, you will need to wipe data in twrp and return to twrp.
Flash the Rom in twrp as normal.
Now if you want just root, flashing cf-autoroot via Odin is the of other choice, flashing magisk or supersu will involve twrp so like I said earlier you'll end up wiping data.
Hope this helps in some sort of way
Thanks! I have been searching for hours in my free time to see if I can do this. I just read in a few threads that if the phone is on Oreo it would have a locked bootloader. I went thru that helping my buddy root his ATT 337 S4. Almost bricked his phone.
I will be starting with a new phone, dont care about tripping knox. Just want root so I can use titanium backup to freeze/uninstall any of the bloat. I would get a costom rom after root eventually.
I will get a SH-G950F ordered. I just didnt want to get the phone and not be able to root. Almost ordered The SH-G950U and its got snapdragon, and I read thats not the best version if I have a choice.
I love my rooted S4 but its kind a turtle so need to move forward.
Thanks So much for your help sofir786 !!!!!
sofir786 said:
The process I've followed is as follows.
Now please take into account that I flash twrp and part of that process is that data partition needs to be formatted, so make sure anything that's needed back it up.
Have a look at some roms, download one to your memory card.
Flash twrp via Odin, you will need to wipe data in twrp and return to twrp.
Flash the Rom in twrp as normal.
Now if you want just root, flashing cf-autoroot via Odin is the of other choice, flashing magisk or supersu will involve twrp so like I said earlier you'll end up wiping data.
Hope this helps in some sort of way
Click to expand...
Click to collapse
Mrmezz
I rooted my s8 G950F on oreo with twrp magisk and dm verity. If u dont wipe data and flash dm verity after twrp your phone will boot sayin we cannot verify the integrity of this device please restart. I cant mind the ecact process i followed but it was onli them 3 i flashed