I'm want to use Android Commander to transfer some files back and forth to the PC for development. AC needs root access... I've used WugFresh's excellent toolkit to unlock and root the device. All worked fine; SuperSU is present, BusyBox installed. But AC still reports no root access, and the FAQ briefly mentions the difference that not all rooting gives root access to adb.
Can anyone explain in simple terms (I'm pretty new to android) how to get full root access to the device so that I can use Android Commander? Googling for instructions to root the device seems to pretty much always lead back to WugFresh's toolkit, which I've already done.
Stuart
Try the link below .I remember having a similar problem on a Galaxy Note. I ain't certain but I think its to do with ADB insecure/secure. I could be completely wrong of course!!
http://www.xda-developers.com/android/run-adbd-in-root-mode-with-adbd-insecure/
ScottArten said:
Try the link below .I remember having a similar problem on a Galaxy Note. I ain't certain but I think its to do with ADB insecure/secure. I could be completely wrong of course!!
http://www.xda-developers.com/android/run-adbd-in-root-mode-with-adbd-insecure/
Click to expand...
Click to collapse
Many thanks, yes, that seems to have worked. Strange that there isn't more info about this out there.
This says that it only persists until a reboot - I would still be interested in anyone knows a way of doing this permanently without installing a custom ROM
Stuart
Just letting everyone know that is does work for this device as well. Not sure if it's been mentioned already or not. If so and it's old news, sorry but didn't see anything posted about here although I didn't look very hard either
On the latest 4.4.4 update. So far so good. Did it's thing in less than 5sec's. Root Check was good, Installed SU from the playstore, said something about the SU Binaries or something, rebooted and bam, that msg doesn't show up anymore and all looks to be good.
Thank you geohot!
Bricking and Boot Loops on Nexus 7 2013 WI-FI
Demmonnixx said:
Just letting everyone know that is does work for this device as well. Not sure if it's been mentioned already or not. If so and it's old news, sorry but didn't see anything posted about here although I didn't look very hard either
On the latest 4.4.4 update. So far so good. Did it's thing in less than 5sec's. Root Check was good, Installed SU from the playstore, said something about the SU Binaries or something, rebooted and bam, that msg doesn't show up anymore and all looks to be good.
Thank you geohot!
Click to expand...
Click to collapse
I actually have encountered problems on two separate Nexus 7 2013 editions both in less the a day of using towelroot. One tablet with a custom kernel bricked and the other tablet while rooted with towelroot is without a custom kernel and whenever encountering a force close will reboot itself and boot loop 20-30 times before eventually booting back into Android 4.4.4. I have no definitive 'proof' that towelroot is causing these errors but I find it all a little too coincidental. I hope your device fairs better then mine.
Not sure I see the point of towelroot on a N7, one just has to flash supersu in twrp.
Edit: I guess if you don't have a pc(really? in this day and age?) or don't wanna wipe? Meh, to each their own.
Captain_FSU said:
I actually have encountered problems on two separate Nexus 7 2013 editions both in less the a day of using towelroot. One tablet with a custom kernel bricked and the other tablet while rooted with towelroot is without a custom kernel and whenever encountering a force close will reboot itself and boot loop 20-30 times before eventually booting back into Android 4.4.4. I have no definitive 'proof' that towelroot is causing these errors but I find it all a little too coincidental. I hope your device fairs better then mine.
Click to expand...
Click to collapse
Haven't had a single issue so far. Did the towel root thing and then unlocked the boot loader then flashed clean ROM and this thing has been amazing so far on all aspects. I would start from scratch fresh and clean and see if that helps anything. Good luck but if u can give a step by step on what u did first through the last step and what version of towel root u used I might be able to help
mdamaged said:
Not sure I see the point of towelroot on a N7, one just has to flash supersu in twrp.
Edit: I guess if you don't have a pc(really? in this day and age?) or don't wanna wipe? Meh, to each their own.
Click to expand...
Click to collapse
1. My computer's a desktop and 100+ miles away
2. Don't want to wipe
I tried the latest towel root on Lollipop and it says "This device is not supported"
I tried the OS 4.5.2 rooting from the forum and that did not work. I tried KingRoot and its works. Can someone test this on OS 4.5.3 or higher OS please
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Sent from HDX 7 OS 4.5.2 Rooted
Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.
Sometimes you have to tried several times the last time I fail too but the second works. I dont know what cause it
Sent from HDX 7 OS 4.5.2 Rooted
PsymH said:
Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.
Click to expand...
Click to collapse
From what I've heard, 4.5.4 can't be rooted. If you have a 3rd generation HDX, then you have to first downgrade to 3.2.8 and then manually update to 4.5.2.
Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.
rabaker07 said:
Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.
Click to expand...
Click to collapse
You obviously understand the risk and assume you tried alternate (Moto) drivers along with different cables and host ports to confirm diagnosis. Note cables/ports that work on one device may not on another - especially finicky HDX hardware.
You're probabky not going to get a high confidence response to your KingRoot question as most take the full step of unlocking. Plus age of device and waning interest. Good luck.
Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul. The risks come in when you attempt to flash a ROM and it fails by partially loading and overwriting/erasing critical files without completing (loss of power mid flash!) or if the ROM is incompatible in some way and you are unable to flash your previous ROM. That's where bootloader recovery software comes in (TWRP and the like). So that you can access the system before loading (or failing to load) the ROM, and flash over it or flash a backup.
Moral of the story is that YES, Kingroot works on HDX 3rd Gen on 4.5.5.3. I tried it last night and it worked. I now have access to the root directory. Oh, the places you'll go!!
Sent from my Pixel 2 XL using Tapatalk
rabaker07 said:
Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul.
Click to expand...
Click to collapse
Nope; root attempts can yield a bootloop or otherwise dysfunctional device. Glad all worked out for you.
Ouch. I didn't realize that. It always seemed very benign and I've never had it go wrong. I guess I'm used to devices that are designed to be accessible. Fortunately my HDX rooted without a hitch.
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.
I have many devices but with the galaxy tab 4 8 inch t337a running "lollipop" . I am in a temporary root. I deleted a bloat ware an when I went to restore the app it never came back. Weird but also Kind've good because it's a app I never wanted. But I have seen people downgrade their stock roms. Since I'm in a temporary root an if theirs a hard boot then I get the at&the unauthorized screen . Would it be possible to downgrade to kitkat ???? If so it would make things easier an plus get to enjoy the joy of custom boot image because I may have root but since it's temporary until the kernel sees it in a haRd boot then it's useless but I have seen downgrade before if done right with the right tar file an stuff. Just wondering if someone can help me with downgrade or find a way to get past the kernel recognizing without softboot