CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 16 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
Download
flo (Nexus 2013 Wi-Fi): CF-Auto-Root-flo-razor-nexus7.zip
deb (Nexus 2013 LTE): CF-Auto-Root-deb-razorg-nexus7.zip
Very happy to see you here too. Thx for your work.
Sent from my Nexus 7 using xda premium
Chainfire said:
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
Click to expand...
Click to collapse
For Flo, bootloader is volume down and power.
Newbie question - Once rooted with this method will I still get OTA updates? If so will it retain root?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
User_99 said:
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
Click to expand...
Click to collapse
Thats not true... I got the 4.3.1 update for my deb and had root+twrp. After hit install it boot to twrp and installs the ota after boot up root is still there. No Problems here
Great that it works fine for you!
But that will work not for all customers. Some reported that after they recived and downloaded the OTA they got an error while installation in custom recovery.
I rooted my Nexus 7c LTE..
now i can see an unlock logo in startup... anywhere i can remove it?
thanks!
No, that's normal for unlocked bootloader. Only not shown when you close the bootloader again.
Thank you!
any idea how to close the bootloader?
http://www.wugfresh.com/nrt/
Nexus Toolkit - easy way to lock the bootloader. But, for Root, you need an Unlock Bootloader...
decide...
THANKS!!!
is the auto-root still working on new kit-kat update?
ritz_cal78 said:
is the auto-root still working on new kit-kat update?
Click to expand...
Click to collapse
Nope. Already tired twice.
so if i want to install TWRP recovery, i have to flash it after i install CF-auto root?
how do i get to the steps u mentioned using mac?
xdviper said:
Nope. Already tired twice.
Click to expand...
Click to collapse
It worked perfectly for me first try. I should say that I had just rooted my Nexus 7 LTE with Chainfire's method before I updated my N7 OTA. After the update, root was lost. I simply went through the steps again and re-rooted it. I should also state that I did not lose any of my data on during the 2nd root.
I'm going to donate to Chainfire.
same here, only difference,
I came from a factory image fash. Auto root worked
Send from the N7²
Will this work a stock n7 2 running KK?
xbs said:
Will this work a stock n7 2 running KK?
Click to expand...
Click to collapse
Worked OK for me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
Hi!
This kernel enables custom boot animations (/system/media/sanim.zip), adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter, which is presumably used by Samsung as a reason to decline warranty service (not aware of any reports of this occuring yet...?)
Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Thanks, Good job.
Sent from my LG-P925 using xda premium
nice work Da_G
Nice work!!! Im just waiting my Note...
Sent from my SGH-I727 using Tapatalk
Dang what a beast!
Sent from my Galaxy Nexus using Tapatalk
Da_G said:
Hi!
This kernel enables custom boot animations, adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter. Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Click to expand...
Click to collapse
This should work on the Canadian versions, right? Or would this be AT&T specific?
excellent job! Here a little something
Confirmation number: 0P6459745L809882G
@goalcam:
The kernel is built from AT&T source. I haven't examined the Canadian source yet, I'll take a look and see if it'll work.
@bkeaver:
Appreciated!
Any chance a jig from the SG2 will reset the counter?
More than likely not, due to the bootloader revision.. however since my counter is already up in the dozens I can look at putting some time into finding where the counter is stored, so that we can wipe it at will
OK what am I doing wrong. I installed super user from the market and this is what I am getting....
Sent from my SAMSUNG-SGH-I717 using xda premium
OK, followed directions precisely. Installed Superuser from Market and get the following:
su binary vnull
When trying to update:
Checking installed version = legacy
Fixing database... okay!
Checking for busybox... not found
Downloading custom busybox... okay!
Checking md5sum... okay!
Checking current install path... fail!
Failed to find currently installed su binary. Update cannot continue.
Checked, and the flash count shows 1 with new image, and the new boot animation is showing up.
If I can screw something up, I will.
Any ideas?
oops, let me revert my current root and try again, i'll have a fixed v2 up in two shakes!
in the mean time, if you are familiar with adb you should have root access in adb.
Odin
Thanks Gabe !
Thanks Da_G Works Perfectly.
eoh7678 run DoomLord's root after installing the kernel it installs superuser correctly.
Ajairola
ajairola said:
Thanks Da_G Works Perfectly.
eoh7678 run DoomLord's root after installing the kernel it installs superuser correctly.
Ajairola
Click to expand...
Click to collapse
Confirmed! Running doomlord's root correctly installed su/busybox.
Awesome job!
ajairola said:
Thanks Da_G Works Perfectly.
eoh7678 run DoomLord's root after installing the kernel it installs superuser correctly.
Ajairola
Click to expand...
Click to collapse
Thanks for the idea. This worked perfectly...
Sent from my SAMSUNG-SGH-I717 using xda premium
Ok, it was a simple typo in the root script that prevented su and busybox from being installed properly, oops!
Fixed now in the first post, back to regularly scheduled programming.. look for Overclock/Undervolt soon
Da_G said:
Hi!
This kernel enables custom boot animations, adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter. Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Click to expand...
Click to collapse
What does increasing a flash counter do? Forgive a noob.
@SPtheALIEN: Replied in first post.
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 9.5 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download: CF-Auto-Root-mako-occam-nexus4.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
The Android God has arrived
Thanks you @Chainfire god job
I've just added this to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Awesome!
Also, No source availible?
I feel tinker-y
And so it began ...
updates
Sounds good!
If you auto-root your device, will you still get official nexus updates O.T.A. ?
appreciate the hard work
really appreciate your hard work and gonna buy u a beer
This is different from Nexus 4 toolkit how? Just a safer and easier method???
trter10 said:
Awesome!
Also, No source availible?
I feel tinker-y
Click to expand...
Click to collapse
Source from what?
There are no kernel or framework changes...
heymil said:
Sounds good!
If you auto-root your device, will you still get official nexus updates O.T.A. ?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 4 using xda premium
franciscofranco said:
Source from what?
There are no kernel or framework changes...
Yes.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Just wanna see how it works
Sent from my Nexus 4 using Tapatalk 2
What would be the easiest/best way of putting TWRP or CWM on my Nexus after rooting from this method?
ajaffarali said:
What would be the easiest/best way of putting TWRP or CWM on my Nexus after rooting from this method?
Click to expand...
Click to collapse
Download the root kit from wug or mskip.
Sent from my Evo 3D GSM using XDA
ajaffarali said:
What would be the easiest/best way of putting TWRP or CWM on my Nexus after rooting from this method?
Click to expand...
Click to collapse
Download rom manager from play store.
Or goo manager will install twrp.
Sent from my Nexus 4 using Tapatalk 2
will I loose all my data/configs after rooting by this method ??
thanks
danimod said:
will I loose all my data/configs after rooting by this method ??
thanks
Click to expand...
Click to collapse
Uhh as the OP stated in red letters, YES, if you have not previously unlocked the boot loader.
Sent from my Nexus 4 using xda app-developers app
Fantastic only thing that could root my phone in no time
Sent from my Nexus 4 using xda premium
Really appreciate your hard work...
Redundant post....deleted
I really like the way my OneMax w/verizon is and am not really interested in updating. The automatic firmware downloads is eating up my data daily. I just accepted to install it so it would stop, but it won't install due to error (it's a rooted device). I have S-Off on the phone right now and used the SuperSu unroot feature to try and let the update do it's thing just so it would stop downloading. Now, the root checker apps say I'm not rooted (but i think i still am). I tried the virtuous manual stock update but it gives me a installation aborted message while in recovery mode. Any help would be appreciated!
I think you need to have stock recovery & stock rom installed to accept the ota.
jerrycycle said:
I think you need to have stock recovery & stock rom installed to accept the ota.
Click to expand...
Click to collapse
so i have to fully unroot, update my phone then root again?
FrankieTheSqueeler said:
so i have to fully unroot, update my phone then root again?
Click to expand...
Click to collapse
Yes, if you want the update you will.
one last question, my device won't pop up on ABD devices on my PC anymore. Am I still rooted?
FrankieTheSqueeler said:
one last question, my device won't pop up on ABD devices on my PC anymore. Am I still rooted?
Click to expand...
Click to collapse
you only need to have stock recovery installed AND 100% stock system files. no system mods whatsoever.
assuming you enabled USB debugging under the developer options on the phone....you may need to update your version of adb/fastboot.
The root question....are you s off? If so that question is irrelevant as you only need to flash a custom recovery and flash the latest su zip from there to root any ROM...even the stock ota.
Sent from my SM-T320 using Tapatalk
dottat said:
you only need to have stock recovery installed AND 100% stock system files. no system mods whatsoever.
assuming you enabled USB debugging under the developer options on the phone....you may need to update your version of adb/fastboot.
The root question....are you s off? If so that question is irrelevant as you only need to flash a custom recovery and flash the latest su zip from there to root any ROM...even the stock ota.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply!
Yeah I have S-off on the phone. I will update the ADB version and retry. I don't know why I thought the su would be able to do a one-click unroot. All it ended up doing was just confusing me. I'm new to rooting and flashing, and it's fun figuring these things out. You guys are really helpful around here. I'll look for a tutorial on how to flash a custom recovery.
Q&A for Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Nexus 9 root
I'm a newbie so can't post in Chainfire's root thread; but thought I'd post an issue with rooting my N9 in case it helps anyone.
When trying to boot inject.img, it returned "FAILED (data transfer failure (Unkown error))". Tried multiple times, rebooted, etc. Confirmed connection by fastboot devices command.
Not sure exactly what caused it to work, but I rebooted my PC, tried it, it failed, so I unplugged USB connector, plugged it back in to a different port on PC, and SUCCESS! (Maybe just bad USB connection??)
Hopefully this helps someone out there.
Cheers,
Is autoroot working in 25L, the New update?
thebrainkafka said:
Is autoroot working in 25L, the New update?
Click to expand...
Click to collapse
The new update is Q. Some have gotten auto root to work, others have not. You can do the manual root method and flash the elemental x kernel. That was updated with the latest commits.
Sent from my Nexus 9 using Tapatalk
Flash LRX21Q manually. You will need to unzip the package and fastboot flash all img files manually (see this thread: http://forum.xda-developers.com/nexus-9/help/factory-image-flash-t2929019). After that Auto CF will work.
Sent from my Nexus 9 using XDA Free mobile app
I have learnt so many things from your artic,thank you.
---------------------------------------------------------------------------------
I don't know how you guys got it working. I'm on the latest factory image. I ran CF auto root just fine, but then I rebooted and went to flash the SuperSu update to 2.25 via TWRP, and apps just freeze when I try to grant them root now. SuperSu itself will open and I can configure it, but it never comes up when I should be getting an access prompt from using an app requesting root. The app and SuperSu just seem to freeze.
I'm on the latest TWRP as well. I had some issues and went into fastboot and rewrote the system image from the factory image and my device booted again, but updating SuperSu via TWRP says it works but I still get freezing on every app I attempt to grant root. So basically I cannot use root at all.
Moved the above here from Chainfire's root thread. I don't have a clue what's causing the freezing.
EDIT: It gets odder. It's as if the prompts are the problem. I changed SuperSu to grant by default and an app worked. But if I set it to prompt, nothing comes up. Logs only appear when I set it to allow by default.
MikeRL100 said:
I don't know how you guys got it working. I'm on the latest factory image. I ran CF auto root just fine, but then I rebooted and went to flash the SuperSu update to 2.25 via TWRP, and apps just freeze when I try to grant them root now. SuperSu itself will open and I can configure it, but it never comes up when I should be getting an access prompt from using an app requesting root. The app and SuperSu just seem to freeze.
I'm on the latest TWRP as well. I had some issues and went into fastboot and rewrote the system image from the factory image and my device booted again, but updating SuperSu via TWRP says it works but I still get freezing on every app I attempt to grant root. So basically I cannot use root at all.
Moved the above here from Chainfire's root thread. I don't have a clue what's causing the freezing.
EDIT: It gets odder. It's as if the prompts are the problem. I changed SuperSu to grant by default and an app worked. But if I set it to prompt, nothing comes up. Logs only appear when I set it to allow by default.
Click to expand...
Click to collapse
I lost root somehow. Probably kernel. I just reflashed stock recovery and R boot image, ran CFAR again, flashed TWRP and then 2.25. All good now.
Maybe I need to do a complete wipe. Or perhaps I could wait - if anybody knows what I should do. I would log it, but how do I get logs without root? Chainfire may be interested.
MikeRL100 said:
Maybe I need to do a complete wipe. Or perhaps I could wait - if anybody knows what I should do. I would log it, but how do I get logs without root? Chainfire may be interested.
Click to expand...
Click to collapse
I just wiped recovery, boot and reflashed those stock images. Ran CFAR. Flashed TWRP. Flashed 2.25 in TWRP. All good now.
prdog1 said:
I lost root somehow. Probably kernel. I just reflashed stock recovery and R boot image, ran CFAR again, flashed TWRP and then 2.25. All good now.
Click to expand...
Click to collapse
There's a few lines in init.rc that need to be changed to get root working if flashing a factory google boot.img. Kernel itself doesn't just the kernel zimage won't break root, but flashing a boot.IMG will unless you make a small edit to the ramdisk.
For those having problems after flashing 2.25 go into SU settings aand uncheck and recheck the Enable SU checkbox. Worked for me. Working as should now.
Yes I mentioned that in a thread earlier. Must have not been the only one with the problem.
Latest beta 2.27
I'd wait before rooting, seems Chainfire may be able to root without the kernel patches soon: https://plus.google.com/u/0/+Chainfire/posts/K7n4e1q5SMD
Diesel779 said:
I'd wait before rooting, seems Chainfire may be able to root without the kernel patches soon: https://plus.google.com/u/0/+Chainfire/posts/K7n4e1q5SMD
Click to expand...
Click to collapse
Seems to be working. Reports are good.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
prdog1 said:
Seems to be working. Reports are good.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Things are moving along quickly I'm going to hold off from rooting for a few days maybe longer. Give Flar2 time to do some more work on his kernel too.
SU 2.27
I was on R unlocked and rooted w/CFAR using su 2.25 and TWRP 2.8.2.1. Here is what i did - uninstalled/deleted SU, fastboot erased recovery and boot, fastboot flashed stock R boot and recovery. Rebooted all was ok NO ROOT. Then -> fastboot erase recovery -> fastboot flash TWRP -> flashed SU 2.27 w/TWRP -> wipe dalvik/cache -> reboot -> BAAAM ROOT. Thank you Chainfilre!!!!!!
After root dont get updates
After root my tablet nexus 9, I don't get updates. The device detect that there is a update, download it, try to install and then say error!!!
I have did the CF-auto root flasheable. Do you have any solution for that???
Algruista said:
After root my tablet nexus 9, I don't get updates. The device detect that there is a update, download it, try to install and then say error!!!
I have did the CF-auto root flasheable. Do you have any solution for that???
Click to expand...
Click to collapse
Read this forum http://forum.xda-developers.com/nexus-9/orig-development/root-t2929118
or try this one http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
OP, is it okay if I don't have original factory sync cable in hands?
volibyro said:
OP, is it okay if I don't have original factory sync cable in hands?
Click to expand...
Click to collapse
Yeah its ok you just run into less issues with original cable.
**Working on updating links I have a slow upload speed though.
HideTheCookies said:
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
Click to expand...
Click to collapse
If u want to switch to SuperSu from KingoROOT, the best and easiest method would be backing up ur phone and performing a soft reset. Afterwards simply install SuperSu, the superuser binary is already installed from kingroot - no worries, just update it normally via SuperSU and disable KNOX after the update is complete.
That switch idea of yours might get you bricked
Confirmed it works now we need a recovery so we can just flash su
SuperSUme works really really well lol, this phone is 32bit only any1 wanna try 4 a recovery?
Thxx bro
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
gravyd316 said:
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
Click to expand...
Click to collapse
Agreed about flashing the recovery, but you need to be rooted with KingOroot to get SuperSUme to work, & it helps to just keep the screen timeout turned off thru this process , after it says "complete" I downloaded SuperSU & installed, updated, "disabled" knox, & I can also use flashfire although its pretty worthless for anything other than backups, as the little AROMA shell emulator thingy does run after the verizon logo is showing, which indicates to me yea its locked down pretty solid lol.
I tried Safestrap & it gave me a /SS folder in my /etc so I looked into that but I can't manage to figure out how I should go placing the files to make it work lol. But i do know this thing is 32bit ONLY, so compiling the j100H twrp for instance will NOT flash no matter what we do to the bootloader, it will bootloop since the architecture is for a 64bit SoC, we need someone to compile the j100H twrp in a 32bit only compatible architecture, & then you can easily flash it like cake, & TWRP should do the rest like all other Samsung phones O.O
its gotten to the point these are all the apps I have when i restore haha, if you wanna PM me about working together to get this thing a little more flexible I'm always open to ideas . I only use this thing as a hotspot but would totally like to see a recovery at least make it over & from there I could definitely start the ROM bringup
Will I get bricked by doing this with Verizon
Weegee1 said:
Will I get bricked by doing this with Verizon
Click to expand...
Click to collapse
you cant hard brick this device, restore with ODIN start over.
LilAnt530 said:
you cant hard brick this device, restore with ODIN start over.
Click to expand...
Click to collapse
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
LilAnt530 said:
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
Click to expand...
Click to collapse
THANKS! sorry last noob question, will I lose root if I turn my phone off
Weegee1 said:
THANKS! sorry last noob question, will I lose root if I turn my phone off
Click to expand...
Click to collapse
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
LilAnt530 said:
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
Click to expand...
Click to collapse
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Weegee1 said:
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Click to expand...
Click to collapse
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
LilAnt530 said:
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
Click to expand...
Click to collapse
And with SuperSU, is that one more stable