[GUIDE] How to root without tripping knox - Kitkat and Lollipop, Locked bootloader - Galaxy Tab S General

I take no responsibility for what happens to your device if you follow this guide. Rooting or modifying carries risks, however I have tested this procedure many times with 100% success on my SM-t805. It should work for any device, but I can't confirm, so feedback please if it works for your device.
1. Firstly you need to downgrade your device to a XXU1ANF8 or earlier firmware suitable for your particular model. This is available at http://samsung-updates.com/ or you can use this one XSG-T805XXU1ANF8-20140625 which is for the T805 model only.
https://www.androidfilehost.com/?fid=23501681358555496 T800 only
Download and then install the firmware on your device with ODIN.
If you are still on Kitkat then there is no need to wipe the data partition. However if you are running Lollipop after successful installation you will need to boot into recovery POWER + HOME + VOL UP then select WIPE DATA/RESET -
YOU WILL LOSE ALL YOUR USER DATA SO BACK UP ANYTHING YOU NEED TO THE SD CARD FIRST!
NOTE: IF THE INSTALL FAILS AT HIDDEN.IMG OR CACHE.IMG SIMPLY BOOT INTO RECOVERY AFTERWARDS AND WIPE CACHE THEN CARRY ON WITH THE REST OF THE PROCEDURE.
2. Once booted into Android, set up your wifi and google account and skip everything else (this wont be needed if you didn't wipe the data partition)
3. Next we need to install a Few apps, so go ahead and install these apps from Play Store:
System app remover(root)
Root Validator
Terminal Emulator For Android
KINGROOT 4.1
Kingroot updates and earlier versions if posted version doesn't work:
http://androidxda.com/download-kingroot-application
Kingroot 4.5 (latest version)
We also need to download the package from this LINK
4. Using the built in File Manager extract the zip package to your internal SD card. Once extracted, inside the extracted folder is another folder called MRW.
THIS FOLDER NEEDS TO BE MOVED TO THE ROOT OF YOUR INTERNAL SD CARD OR THIS WON'T WORK.
5. Next go to Settings set your display timeout to 10 mins.
Now Run KINGROOT then wait for it to do it's thing. If it reboots part way through the process then after rebooting unlock your device, but don't touch anything for a couple of mins. The app should restart and continue. If you are successful you can move to the next step. If not, exit the app and run it again, it may take several attempts before you eventually achieve root.
6. After success uninstall the KINGROOT app (NOT KINGUSER) (not required with v4.5) and the other blue app with Chinese writing.
Now reboot - DO NOT RUN THE KINGUSER APP
7. Let your device fully boot then run the Terminal Emulator and wait for the command prompt
NOTE: IF AT ANY POINT YOU SEE A POP UP BOX WITH CHINESE WRITING ASKING YOU TO UPDATE THE KINGUSER APP SELECT CANCEL.
Now type or copy and paste the following command into the Terminal window:
su
It will ask for root permission, so select ALLOW.
Without closing the terminal emulator window, hit the HOME button and run the SYSTEM APP REMOVER app. (The app is red and simply called UNINSTALL)
The app will ask for root permission, hit ALLOW.
Look for the KINGUSER app then select it and uninstall it. Exit from the app.
Re-open the terminal emulator window and type the following:
sh /sdcard/mrw/root.sh
This will run a script, you will see a bunch of warnings, just ignore them .At then end of the script the SUPERSU app will run.
8. Hit CONTINUE then NORMAL.
Next you may see another message that 'Samsung knox has been detected'. When you see this message select CANCEL.
Once completed you should see a message saying that installation has been successful. Hit OK.
If you see the message again 'Samsung knox has been detected' select CANCEL then exit the SUPERSU app.
9 . Now check with ROOT VALIDATOR that you have root and everything looks ok.
DO NOT REBOOT.
The root is only temporary, if you reboot you will lose root.
10. The next step is to install our ROM of choice with Flashfire.
For more info on FLASHFIRE see here: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
11. Run FLASHFIRE and grant it root.
12. Agree to the disclaimer and then hit the Red circle with a white +.
Next select 'Flash firmware package' and then navigate to the firmware you want to install (in this case the stock tar package) and select it.
Wait until it finishes scanning the archive.
Next you will see the list of partitions to be flashed, all that is really required is BOOT, RECOVERY and SYSTEM. You can flash the others if you wish.
When you're happy hit the TICK and then you will see a list of what will be flashed. If you tap any one of them you will be able to change the options. Tap the REBOOT option then select DOWNLOAD from the list. This is so we can boot into download mode after the flashing process to flash the Lollipop BOOTLOADER. If not upgrading to lollipop just select REBOOT
I'd advise to leave the rest as is and then hit FLASH
NOW WATCH CHAINFIRES MAGIC!
13. After reboot it should boot directly into DOWNLOAD mode or REBOOT if not updating to Lollipop.
If updating to Lollipop we need to flash a Lollipop BOOTLOADER. I have provided a link below for the T800 and T805. If you have a T700/705/T807/T707 or if the ones provided don't work then you will have to extract it from the Lollipop stock ROM and then TAR it up.
T800XXU1BOCC_BOOTLOADER.tar
T805XXU1BOCC_BOOTLOADER.tar
Latest T800 boot loader thanks DUHasian skillz.
T800XXU1BOE3 bootloader
Flash the BOOTLOADER with ODIN.
If successful then after reboot you should have a rooted version of Lollipop or whatever rom you decided to install and an untripped Knox counter(hopefully)
Good luck and please give feed back.
If you wish you can give feedback to Chainfire at the link posted at the beginning of this post.
NOTE: If you wish to change roms or update and wish to keep root you will have to use the same procedure with Flashfire.
Also note that if you flash a custom KERNEL or BOOTLOADER then it may trip KNOX. Custom ROMs with stock KERNEL and BOOTLOADER should be OK(but don't hold me to that)
CREDITS TO CHAINFIRE FOR FLASHFIRE AND SUPERSU, KINGTEAM FOR ROOT AND WOLFDROID FOR THE KINGROOT REMOVAL SCRIPT.

My god I've been waiting for a thread like this one for a long time.
I don't have time to try it today but I'll give you feedback in a day or two.
Feedback here http://forum.xda-developers.com/showpost.php?p=61296003&postcount=12
Moderators, this thread should be sticked

Just so that I understand the limits of this method I need to ask. Is this method specific to achieve rooted (SuperSU) Lollipop 5.0.2 without tripping Knox or can further changes be made? For example:
1) Remove system apps (removing bloat).
2) Adding system apps such as Viper4Android, busybox, which must be installed in /system/priv-app
3) The Lollipop/Samsung compatible XPosed framework and modules
4) Installing a Tab S model compatible recovery (e.g. TWRP) as I would really like nandroid backups.
I only ask as in the Tab S Kingroot thread there was a post which mentioning that despite Kingroot having successfully achieved root without tripping Knox if you messed with the /system partition files there was the possibility of tripping Knox.
The comment in step 12 "... then navigate to the firmware you want to install ..." suggests that you could install one of the model compatible custom ROMs (e.g. CM). Is that a correct assumption or right now are you restricted to Lollipop stock? Some of those ROMs are from Lollipop 5.1.1 AOSP source (e.g. CM 12.1) which may be going too far with this method and still not trip Knox.
One last question, if I did implemented this could I go back to a pure unrooted stock kitkat/lollipop using Odin or Flashfire without tripping Knox? Odin would be fine.
I greatly appreciate the effort and quality of your post. I had hoped that a "Knox off" SuperSU lollipop root would be found for my month old Tab S 10.5 as I'm used to the low risk flashing on the Nexus devices and have had a mean itch to root without obvious risk to my warranty.
Thanks again

This method can be used to root any Rom.
Once you have root you can practically do what you please.
As for tripping Knox if you mess with the system partition, that's the whole point of root it already messes with the system partition. It shouldn't trip Knox, but never say never.
Just ensure once you have root you remove everything Knox related.
I can't confirm if a custom Rom will trip Knox, but as already stated as long as the bootloader and kernel are stock I believe it won't trip Knox.
Custom recovery may trip Knox.
You can go back to stock any time you wish.

ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again

3DSammy said:
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
Click to expand...
Click to collapse
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4

shayind4 said:
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
Click to expand...
Click to collapse
Firstly, nowhere does it state to flash the kitkat bootloader on a lollipop Rom in step 12 or 13.
By step 13 you should be running a lollipop Rom.
Secondly Knox should not trip when flashing a stock bootloader. The bootloader can be flashed independently in Odin.
Lastly Flashfire does NOT flash bootloaders.
If you don't flash the bootloader your Rom won't boot.
I suggest you digest the guide again.

3DSammy said:
In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
Click to expand...
Click to collapse
It doesn't state to flash the boot loader in step 12? :what:
Your boot loader will be replaced when you downgrade to kitkat via Odin.
You need to reflash the lollipop boot loader after using Flashfire to install your Lollipop Rom or it won't boot.

Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?

Paddiii said:
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Click to expand...
Click to collapse
No, this is the whole point of the post. Flashfire will root for you.

ashyx said:
It doesn't state to flash the boot loader in step 12? :what: ...
Click to expand...
Click to collapse
My bad, I saw the word "Boot" in step 12 and incorrectly assumed that was referring to a bootloader image.
Thanks for correcting me and your patience.

Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !

bibihub said:
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
Click to expand...
Click to collapse
The hidden.img failure is because its carrier/region related.For some it will flash ok, for others it will fail. It isn't actually required at all. Even if it fails to flash the rest of the Rom will.
All that needs to be done after that failure is to wipe cache in recovery.
As regards flashing custom roms. Remember your Rom is already custom as you have modified it.
I would say a good chance custom stock roms won't trip Knox as long as it's build properties reflect its a stock Rom.
However something like Cyanogen probably would trip Knox as its not based on stock.
I won't say this is for sure, but I think it's the general consensus.

Over one thousand views and literally only one person has bothered posting feed back.

ashyx said:
Over one thousand views and literally only one person has bothered posting feed back.
Click to expand...
Click to collapse
OK now two. I successfully applied your instructions yesterday. I really appreciate your guide.
What I did, differently is flashed with Odin using a Virtualbox Windows guest VM from my Ubuntu 14.04 host PC. It took a few days of false starts to get that working. Here is a "[How-To] Linux, Virtualbox and ODIN for your Samsung device", that I just posted to help others who do not have access to Windows machines.
Of the whole procedure the scariest moment was after flashing 4.4.2 stock with Odin over my devices 5.0.2 install. The reboot was too fast for me to get into recovery to wipe user data. I could not power off the SM-T800 and holding POWER + VOL DOWN just rebooted where it would hang displaying "SAMSUNG".
Booting into recovery ( POWER + VOL UP + HOME) had no effect what so ever. Finally I found that if I was fast enough I could reboot (POWER + VOL DOWN) and as soon as the screen went blank hold down the "POWER + VOL UP + HOME" buttons, then the tablet booted into recovery where wiping user data worked as described in your guide.
After completing your guide I am on stock Android 5.0.2 with Knox 0x0000.
My root apps so far:
Busybox
Titanium backup
GMD Gestures.
ES File Explorer with RW access to all partitions
System Uninstall Pro
Universal init.d
See Update below: "Unfortunately so far Viper4Android is not working as I cannot get SELinux permissive enabled either by the SELinux app or an init.d shell script using the "setenforce 0" command. From what I've read that is due to the Samsung stock bootloader."
V4A now works, see: "[HOW-TO] Installing Viper4Android (V4A) Audio on a Lollipop Tab S"
I took the high road and only froze the following KNOX related apps using titanium backup:
com.sec.enterprise.knox.attestation
KLMS Agent
KNOX
KNOX
KNOX II
KNOX SetUpWizardClient
So far I debloated 117Mgs of other apps using System Uninstall Pro. I bought the pro version of Flashfire just to show respect for Chainfire's development efforts. I have not tried to see if Flashfire's backups can be successfully restored yet.
Thanks again for your guide.:good:

Thanks for the feedback, it's constructive and encouraging for others to know It's successful.
For future reference you can disable auto reboot in Odin then manually reboot with POWER + VOL DOWN + HOME then as soon as it restarts switch to VOL UP while continuing to hold the other buttons.
The above procedure can be used at any point and will restart the device and get you into recovery every time.

just registered to suport OP, it works
I thought I did not need to run the su script as I could use kinguser w/o problems. But the flashfire is not compatible with other kinguser. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.

vancities said:
I thought I did not need to run the su script as I could use kinguser w/o problems. But the fireflash is not compatible with other root authorization app. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.

ashyx said:
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
Click to expand...
Click to collapse
I had success. What I mean is the step 6 7 8 9 are not necessary if flashfire could work with kinguser.
Also kingroot only works on XXU1ANF8 and maybe lower. I mentioned this because in other thread about kingroot, someone got success but most did not.

So my feedback . everything was great , was a little confused about Odin at first but like you said everything can be found on xda. Need to be on the most recent Odin which I believe is 3.10. Kingroot took forever to root but I believe it has something to do with connectivity to the servers. So my tab s is rooted no Knox counter. I'm hoping the custom tw rom doesn't revert all the hard work ? thanks again op.

Related

Step-by-step guide to Root, SafeStrap and ROM your ATT Galaxy S4 Active SGH-i537

Here is my step-by-step guide to converting your Stock Samsung Galaxy S4 Active i537 into a Rooted, Google Edition 4.2.2 SGS4 Active. After reading a lot of posts and receiving some questions directly, I feel this information is available, but must be dug up from posts within long threads, see the following two post references below:
Instructions from @TreyLWalker:
http://forum.xda-developers.com/showpost.php?p=45739405&postcount=53
I'm a new user who can't post in development yet, but I wanted to let everyone know this procedure worked for loading a custom ROM (NOT flashing / bootloader crask) and all hardware working AFAIK) for my S4 Active i537 with the MF3 Kernel using Safestrap:
Procedure for my Samsung S4 Active i537 MF3 - I537UCUAMF3 - US, AT&T:
Installed Safestrap Recovery v3.5x - Safestrap-JFLTEATT-ACTIVE-3.5x-B08.apk
Installed Recovery, Rebooted into Recovery, Pressed Settings Key on Splash Screen Load
Created ROM Slot-1, Set it to active, Installed with the following:
AOSP Port GT-I9295 - Official 4.2.2 - I9295-PORT-GoogleEdition-V1.zip (worked for i537 despite saying otherwise, I still wouldn't flash stock ROM....)
MF3 Kernal Modules - jflteatt-active-MF3-modules.zip - MF1 Modules found in the same thread if you need them.
LeJay's S4 Active Camera Patch - SGS4A_CamPatch.zip
Reboot System, pressed continue at Flash.
Everything appears to work "OOTB": Phone, Bluetooth, Wifi, Stock Camera App /w Flash (video-recording preview is low-res, but records normal) and SuperSu Root.
Click to expand...
Click to collapse
As well as Instructions from @Hashcode:
Posted specific instructions by @TreyLWalker for flashing Safestrap + Google Play Edition ROM and the camera patch in #3 post:
http://forum.xda-developers.com/showpost.php?p=45694084&postcount=3
Procedure for my Samsung S4 Active i537 MF3 - I537UCUAMF3 - US, AT&T:
Installed Safestrap Recovery v3.5x Safestrap-JFLTEATT-ACTIVE-3.5x-B08.apk
Installed Recovery, Rebooted into Recovery, Pressed Settings Key on Splash Screen Load
Created ROM Slot-1, Set it to active, Installed with the following:
AOSP Port GT-I9295 - Official 4.2.2 - I9295-PORT-GoogleEdition-V1.zip (worked for i537 despite saying otherwise, I still wouldn't flash stock ROM....)
MF3/MF1 Kernal Modules - jflteatt-active-MF3-modules.zip / jflteatt-active-MF1-modules.zip (in same downloads area)
LeJay's S4 Active Camera Patch - SGS4A_CamPatch.zip
Working Phone, Bluetooth, Wifi, Stock Camera App /w Flash (video-recording preview is low-res, but records normal)
Click to expand...
Click to collapse
I felt that these posts are great tutorials, thank you guys for the information and links! However, I just felt some details needed to be written for the unexperienced Android users out there, who are either just switching over from iPhone's or this is their first time getting into rooting and ROM'ing and are looking for an exact step-by-step guide, without leaving any holes for questions. Basically a n00b guide , I mean that in the nicest way possible.
So here's my rendition of what was written above by both TreyLWalker and Hashcode, but a little more n00b friendly. P.S. Thanks again guys for the above guides, I used those as base for mine, as well as thank you for all the work you've put into the Galaxy S4 Active (this goes for all the other members out there who've helped with dev on this device, like @br0adband, @Devo7v, @LeJay, @my-blue-snog-box, @Darkman and anyone else I forgot). Hope you enjoy!
================================Below this line is my step-by-step guide================================
The following instructions are a step-by-step guide to getting your Galaxy S4 Active (i537) from stock to rooted and running GoogleEdition AOSP 4.2.2.
First, determine if your device stock is running MF1, MF2 or MF3. To do this tap the Menu button -> Settings -> About Phone and look at your Baseband Version, it will end in either MF1, MF2 or MF3. Write down which one you have for later reference.
Next, make sure you have the following settings set on your device, go to Settings -> Security and make sure "Unknown sources" in CHECKED, and "Verify Apps" is UNCHECKED.
Next you will need to Root your phone, this is a very simple process outlined in this video. But if for any reason you are unable to watch the video, all you need to do is load this website on your phone's web browser, then download the Activeroot APK file, install it and open it. Once this is ran, your phone is now rooted, now you need to open the Google Play Store and download SuperSU, this allows you to approve apps to access root.
Next, we want to install SafeStrap, which allows us to install a second custom ROM, alongside our stock one. To install SafeStrap follow these instructions:
Download the newest version of Safestrap APK from here
Find the APK using a Filemanager tool and open it on your device, then click "Install".
Once installed, open up the Safestrap application as you would any other app.
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Now, download the ROM from here. Save this .zip file to your phone's internal storage or MicroSD card, you can install from either one within SafeStrap.
Also, download the MasterPatch from here and copy this file to your internal storage or MicroSD card as well, again this file can be on either one, just remember where you put it. You can copy these files over through USB or via a file share service such as Google Drive.
Now, reboot into recovery, this can be done by rebooting your phone, when it reboots you will see the SafeStrap boot screen, press the option for recovery (touch your screen on the button or just below the button, you will feel a vibration when it is chosen).
Once in SafeStrap Create ROM-Slot 1, DO NOT delete, wipe or Install over the Original ROM Slot, as that is your stock ROM that you will need to keep. Be sure to create a new ROM Slot then activate the new ROM Slot with the Activate button. When creating the new ROM slot, I chose to give it 2GB of data storage, this ended up being a little lower than I needed, but it helps me remove apps that I don't use, as I will run out of space. I have about 75 apps installed (not counting the Google apps).
Now that you have created a ROM Slot and set it to Active, you can now install the Google Edition AOSP ROM (.zip file) we downloaded earlier. Please install this file, followed by installing the MasterPatch next, during the MasterPatch install you will be prompted with a few questions. Please be sure to install the following options;
Camera Fix
Speaker-Phone Fix
Edited "gps.conf"
I537 build.prop
apns-conf.xml file (install this option if you will be using your phone on AT&T in the United States)
Then lastly, choose the proper MF1, MF2 or MF3 Kernel Modules based on which MF version you wrote down earlier. (see Step 1 if you've forgotten which version)
If you have any questions as to how to use SafeStrap, refer to this post, which outlines each option within SafeStrap.
Once you have installed the ROM and MasterPatch you should be all ready to boot up into your new Google Edition AOSP ROM. Go ahead and choose the reboot system option within SafeStrap and let your phone boot. This process may take a few moments as it's the first time you're booting up the new ROM. Once booted up you can set up your Google Account and start downloading/configuring your apps. Also, be sure to check out the settings menu as there are a lot of cool new options you can use compared to the stock ROM you were on before.
Here's the cliff notes, or the TL;DR version:
Root your phone with Geohot Active Root
Install SafeStrap
Download your ROM and MasterPatch
Create a ROM Slot, install ROM and MasterPatch with your Kernel Modules
Boot into the new ROM and enjoy!
And as always, don't forget to make a backup of your running and configured ROM when all done, this can be done in SafeStrap or with apps like OBackup.
I use jb+ camera and you get HQ video preview. Also I had bad luck with master patch on mf1 random reboots... Not hard to flash 4 files
Sent from my GT-I9295 using Tapatalk
Globel said:
I use jb+ camera and you get HQ video preview. Also I had bad luck with master patch on mf1 random reboots... Not hard to flash 4 files
Sent from my GT-I9295 using Tapatalk
Click to expand...
Click to collapse
Do you have a link to that camera app? Maybe it could be compiled to see what is making it work properly and then include those files in the MasterPatch.
https://play.google.com/store/apps/details?id=com.moblynx.camerajbplus
Its a paid app but there is a free one out there too. I orginaly bought it for a phone on 4.4 and the SD card storage options .. Bonus high deff video on aosp
Sent from my GT-I9295 using Tapatalk
i537 screen flashes the reboots to android recovery
Diablo2424 said:
Here is my step-by-step guide to converting your Stock Samsung Galaxy S4 Active i537 into a Rooted, Google Edition 4.2.2 SGS4 Active. After reading a lot of posts and receiving some questions directly, I feel this information is available, but must be dug up from posts within long threads, see the following two post references below:
Instructions from @TreyLWalker:
http://forum.xda-developers.com/showpost.php?p=45739405&postcount=53
As well as Instructions from @Hashcode:
I felt that these posts are great tutorials, thank you guys for the information and links! However, I just felt some details needed to be written for the unexperienced Android users out there, who are either just switching over from iPhone's or this is their first time getting into rooting and ROM'ing and are looking for an exact step-by-step guide, without leaving any holes for questions. Basically a n00b guide , I mean that in the nicest way possible.
So here's my rendition of what was written above by both TreyLWalker and Hashcode, but a little more n00b friendly. P.S. Thanks again guys for the above guides, I used those as base for mine, as well as thank you for all the work you've put into the Galaxy S4 Active (this goes for all the other members out there who've helped with dev on this device, like @br0adband, @Devo7v, @LeJay, @my-blue-snog-box, @Darkman and anyone else I forgot). Hope you enjoy!
======================================Below this line is my step-by-step guide======================================
The following instructions are a step-by-step guide to getting your Galaxy S4 Active (i537) from stock to rooted and running GoogleEdition AOSP 4.2.2.
First, determine if your device stock is running MF1, MF2 or MF3. To do this tap the Menu button -> Settings -> About Phone and look at your Baseband Version, it will end in either MF1, MF2 or MF3. Write down which one you have for later reference.
Next, make sure you have the following settings set on your device, go to Settings -> Security and make sure "Unknown sources" in CHECKED, and "Verify Apps" is UNCHECKED.
Next you will need to Root your phone, this is a very simple process outlined in this video. But if for any reason you are unable to watch the video, all you need to do is load this website on your phone's web browser, then download the Activeroot APK file, install it and open it. Once this is ran, your phone is now rooted, now you need to open the Google Play Store and download SuperSU, this allows you to approve apps to access root.
Next, we want to install SafeStrap, which allows us to install a second custom ROM, alongside our stock one. To install SafeStrap follow these instructions:
Download the newest version of Safestrap APK from here
Find the APK using a Filemanager tool and open it on your device, then click "Install".
Once installed, open up the Safestrap application as you would any other app.
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Now, download the ROM from here. Save this .zip file to your phone's internal storage or MicroSD card, you can install from either one within SafeStrap.
Also, download the MasterPatch from here and copy this file to your internal storage or MicroSD card as well, again this file can be on either one, just remember where you put it. You can copy these files over through USB or via a file share service such as Google Drive.
Now, reboot into recovery, this can be done by rebooting your phone, when it reboots you will see the SafeStrap boot screen, press the option for recovery (touch your screen on the button or just below the button, you will feel a vibration when it is chosen).
Once in SafeStrap Create ROM-Slot 1, DO NOT delete, wipe or Install over the Original ROM Slot, as that is your stock ROM that you will need to keep. Be sure to create a new ROM Slot then activate the new ROM Slot with the Activate button. When creating the new ROM slot, I chose to give it 2GB of data storage, this ended up being a little lower than I needed, but it helps me remove apps that I don't use, as I will run out of space. I have about 75 apps installed (not counting the Google apps).
Now that you have created a ROM Slot and set it to Active, you can now install the Google Edition AOSP ROM (.zip file) we downloaded earlier. Please install this file, followed by installing the MasterPatch next, during the MasterPatch install you will be prompted with a few questions. Please be sure to install the following options;
Camera Fix
Speaker-Phone Fix
Edited "gps.conf"
I537 build.prop
apns-conf.xml file (install this option if you will be using your phone on AT&T in the United States)
Then lastly, choose the proper MF1, MF2 or MF3 Kernel Modules based on which MF version you wrote down earlier. (see Step 1 if you've forgotten which version)
If you have any questions as to how to use SafeStrap, refer to this post, which outlines each option within SafeStrap.
Once you have installed the ROM and MasterPatch you should be all ready to boot up into your new Google Edition AOSP ROM. Go ahead and choose the reboot system option within SafeStrap and let your phone boot. This process may take a few moments as it's the first time you're booting up the new ROM. Once booted up you can set up your Google Account and start downloading/configuring your apps. Also, be sure to check out the settings menu as there are a lot of cool new options you can use compared to the stock ROM you were on before.
Here's the cliff notes, or the TL;DR version:
Root your phone with Geohot Active Root
Install SafeStrap
Download your ROM and MasterPatch
Create a ROM Slot, install ROM and MasterPatch with your Kernel Modules
Boot into the new ROM and enjoy!
And as always, don't forget to make a backup of your running and configured ROM when all done, this can be done in SafeStrap or with apps like OBackup.
Click to expand...
Click to collapse
I have done all described steps and after flashing roms and masterpatch phone flashes screen 3 times then reboots in android recovery. Plesse help. Thank you
I537-rooted-safestap installed
i537 user said:
I have done all described steps and after flashing roms and masterpatch phone flashes screen 3 times then reboots in android recovery. Plesse help. Thank you
I537-rooted-safestap installed
Click to expand...
Click to collapse
Is it rebooting to stock recovery or SafeStrap recovery?
I did the exact guide as said I appreciate the guide.
But my wifi does not work...what should I do?
JaY iZz BaKk said:
I did the exact guide as said I appreciate the guide.
But my wifi does not work...what should I do?
Click to expand...
Click to collapse
Start by trying to flash the modules.
Hey thanks for the advice I got the wifi working on a i9505 rom. My only issue now is the camera, I flashed the camerafix but still no go. Does anyone have the stock s4 active apk with aqua mode flashable or installable? Thanks
Diablo2424 said:
Here is my step-by-step guide to converting your Stock Samsung Galaxy S4 Active i537 into a Rooted, Google Edition 4.2.2 SGS4 Active. After reading a lot of posts and receiving some questions directly, I feel this information is available, but must be dug up from posts within long threads, see the following two post references below:
Instructions from @TreyLWalker:
http://forum.xda-developers.com/showpost.php?p=45739405&postcount=53
As well as Instructions from @Hashcode:
I felt that these posts are great tutorials, thank you guys for the information and links! However, I just felt some details needed to be written for the unexperienced Android users out there, who are either just switching over from iPhone's or this is their first time getting into rooting and ROM'ing and are looking for an exact step-by-step guide, without leaving any holes for questions. Basically a n00b guide , I mean that in the nicest way possible.
So here's my rendition of what was written above by both TreyLWalker and Hashcode, but a little more n00b friendly. P.S. Thanks again guys for the above guides, I used those as base for mine, as well as thank you for all the work you've put into the Galaxy S4 Active (this goes for all the other members out there who've helped with dev on this device, like @br0adband, @Devo7v, @LeJay, @my-blue-snog-box, @Darkman and anyone else I forgot). Hope you enjoy!
================================Below this line is my step-by-step guide================================
The following instructions are a step-by-step guide to getting your Galaxy S4 Active (i537) from stock to rooted and running GoogleEdition AOSP 4.2.2.
First, determine if your device stock is running MF1, MF2 or MF3. To do this tap the Menu button -> Settings -> About Phone and look at your Baseband Version, it will end in either MF1, MF2 or MF3. Write down which one you have for later reference.
Next, make sure you have the following settings set on your device, go to Settings -> Security and make sure "Unknown sources" in CHECKED, and "Verify Apps" is UNCHECKED.
Next you will need to Root your phone, this is a very simple process outlined in this video. But if for any reason you are unable to watch the video, all you need to do is load this website on your phone's web browser, then download the Activeroot APK file, install it and open it. Once this is ran, your phone is now rooted, now you need to open the Google Play Store and download SuperSU, this allows you to approve apps to access root.
Next, we want to install SafeStrap, which allows us to install a second custom ROM, alongside our stock one. To install SafeStrap follow these instructions:
Download the newest version of Safestrap APK from here
Find the APK using a Filemanager tool and open it on your device, then click "Install".
Once installed, open up the Safestrap application as you would any other app.
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Now, download the ROM from here. Save this .zip file to your phone's internal storage or MicroSD card, you can install from either one within SafeStrap.
Also, download the MasterPatch from here and copy this file to your internal storage or MicroSD card as well, again this file can be on either one, just remember where you put it. You can copy these files over through USB or via a file share service such as Google Drive.
Now, reboot into recovery, this can be done by rebooting your phone, when it reboots you will see the SafeStrap boot screen, press the option for recovery (touch your screen on the button or just below the button, you will feel a vibration when it is chosen).
Once in SafeStrap Create ROM-Slot 1, DO NOT delete, wipe or Install over the Original ROM Slot, as that is your stock ROM that you will need to keep. Be sure to create a new ROM Slot then activate the new ROM Slot with the Activate button. When creating the new ROM slot, I chose to give it 2GB of data storage, this ended up being a little lower than I needed, but it helps me remove apps that I don't use, as I will run out of space. I have about 75 apps installed (not counting the Google apps).
Now that you have created a ROM Slot and set it to Active, you can now install the Google Edition AOSP ROM (.zip file) we downloaded earlier. Please install this file, followed by installing the MasterPatch next, during the MasterPatch install you will be prompted with a few questions. Please be sure to install the following options;
Camera Fix
Speaker-Phone Fix
Edited "gps.conf"
I537 build.prop
apns-conf.xml file (install this option if you will be using your phone on AT&T in the United States)
Then lastly, choose the proper MF1, MF2 or MF3 Kernel Modules based on which MF version you wrote down earlier. (see Step 1 if you've forgotten which version)
If you have any questions as to how to use SafeStrap, refer to this post, which outlines each option within SafeStrap.
Once you have installed the ROM and MasterPatch you should be all ready to boot up into your new Google Edition AOSP ROM. Go ahead and choose the reboot system option within SafeStrap and let your phone boot. This process may take a few moments as it's the first time you're booting up the new ROM. Once booted up you can set up your Google Account and start downloading/configuring your apps. Also, be sure to check out the settings menu as there are a lot of cool new options you can use compared to the stock ROM you were on before.
Here's the cliff notes, or the TL;DR version:
Root your phone with Geohot Active Root
Install SafeStrap
Download your ROM and MasterPatch
Create a ROM Slot, install ROM and MasterPatch with your Kernel Modules
Boot into the new ROM and enjoy!
And as always, don't forget to make a backup of your running and configured ROM when all done, this can be done in SafeStrap or with apps like OBackup.
Click to expand...
Click to collapse
I just wanted to say great job, I'm sure this will help many folks out there. Also, for anyone having camera, button or wifi issues, I am far from a pro, but I have installed several ROM's and I have had a couple times where when I finished, I had issues with those options and re-flashing the masterpatch always fixed the issue for me.
Devo7v said:
Is it rebooting to stock recovery or SafeStrap recovery?
Click to expand...
Click to collapse
It reboots to stock recovery. Has this happened to anyone else. Am I missing something. Im new to flashing roms and android os all together but can follow instructions. Been jb-ing apple products for years and am open to any inout or help. I bought this gs4 and was bummed to find out the bootloader was locked. Hope renewed with this safestrap method but is still giving me issues.
i537 user said:
It reboots to stock recovery. Has this happened to anyone else. Am I missing something. Im new to flashing roms and android os all together but can follow instructions. Been jb-ing apple products for years and am open to any inout or help. I bought this gs4 and was bummed to find out the bootloader was locked. Hope renewed with this safestrap method but is still giving me issues.
Click to expand...
Click to collapse
the same happened to me, i tries flashing the recommended rom and cm and both times it turns on, gets to the part where the screen says samsung galaxy s4 active and reboots into stock recovery (stock recovery deletes the safestrap rom slots that i made but doesn't remove safestrap)
I just rooted with ML2. Several people in the ML2 root thread have said they got safestrap working. However no matter which version of safestrap I use I do not get a different splash screen nor do I get safestrap recovery. What do I do? Did I do something wrong?
sobertillnoon said:
I just rooted with ML2. Several people in the ML2 root thread have said they got safestrap working. However no matter which version of safestrap I use I do not get a different splash screen nor do I get safestrap recovery. What do I do? Did I do something wrong?
Click to expand...
Click to collapse
After installing safestrap you have to manually open the app and install recovery
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I followed your instructions last night and the install went perfect. Thanks for putting this together. I only have two issues, the first is the camera doesn't work but I'm going to try flashing the masterpatch again and see if that fixes it. The second issue is that it will randomly give me the google splash screen that you see when you turn on the phone, it doesn't seem to actually re-boot the phone just interrupts whatever you are doing. Any ideas on why that is, should I perform a dirty flash maybe?
Hi, I have an AT&T SGH-i537 rooted upon ML2 and wondered what are the more popular ROMs that are worth looking at and which aren't, which work the best etc. new to ROMs here and have Safestrap up and running to try a few, thanks.
I was pretty heavy into using Safestrap last year when I had my first Active and iirc you have to use a ROM that features a 4.3 stock kernel - pretty sure about that but it's been awhile and things may have changed in my "absence" I suppose.
Was just wondering the same thing earlier as I've got my second Active now, with 4.3 rooted and running great but I'm always interested in seeing how something else might work just the same.
Wouldn't mind doing some testing with a custom 4.4.2 ROM but I don't think it's possible at this time - wish Samsung and AT&T would get off their damned keisters and put out the update for the Active and be done with it.
Of course an unlocked bootloader would be pretty awesome too but, oh well...
br0adband said:
I was pretty heavy into using Safestrap last year when I had my first Active and iirc you have to use a ROM that features a 4.3 stock kernel - pretty sure about that but it's been awhile and things may have changed in my "absence" I suppose.
Was just wondering the same thing earlier as I've got my second Active now, with 4.3 rooted and running great but I'm always interested in seeing how something else might work just the same.
Wouldn't mind doing some testing with a custom 4.4.2 ROM but I don't think it's possible at this time - wish Samsung and AT&T would get off their damned keisters and put out the update for the Active and be done with it.
Of course an unlocked bootloader would be pretty awesome too but, oh well...
Click to expand...
Click to collapse
Hi br0adband, I rooted mine with Sunderwear's method here:
http://forum.xda-developers.com/showthread.php?t=2690133
So we still cannot as yet use custom ROMs? I was under the assumption we could since we flash back to the originalkernel with that method, can anyone elaborate on this?
jkeuclid said:
Hi br0adband, I rooted mine with Sunderwear's method here:
http://forum.xda-developers.com/showthread.php?t=2690133
So we still cannot as yet use custom ROMs? I was under the assumption we could since we flash back to the originalkernel with that method, can anyone elaborate on this?
Click to expand...
Click to collapse
Once Hashcode fixes SafeStrap you will be able to flash 4.3 TouchWiz-based ROMs. Unfortunately since we have a locked bootloader you cannot flash a different kernel so you can only use ROMs that are compatible with your stock kernel.
Devo7v said:
Once Hashcode fixes SafeStrap you will be able to flash 4.3 TouchWiz-based ROMs. Unfortunately since we have a locked bootloader you cannot flash a different kernel so you can only use ROMs that are compatible with your stock kernel.
Click to expand...
Click to collapse
Thanks Devo, so nothing out there worth flashing until he fixes this?

[How-To] Root and unlock the bootloader of the Nexus 4/5 without wiping data

This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Devices you can root using this app:
- Nexus 4: 4.4.3, 4.4.4
- Nexus 5, 4.4.3
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done
noob clarifications
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding
salxtai said:
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding
Click to expand...
Click to collapse
1. To flash a kernel you have to unlock your bootloader, that's right. You just flash it using your PC and fastboot, there are many guides on how to do that
2. If your phone is rooted and you have SuperSU installed there'll be a popup and it'll tell you to update the binary before using the app. You are able to select the "normal" way then without a recovery
3. You can install CWM/TWRP using your PC in fastboot mode!
No problem, just ask :good:
Can the usual commandline methods for other things be used after this?
PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
If you mean fastboot commands for example to flash another kernel/recovery/etc, yes! There's no difference between unlocking using this method or another "old" one, but this one doesn't wipe data
PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
yes. can also be used flashify to flash recovery.img without PC
I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?
PGvossman said:
I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?
Click to expand...
Click to collapse
Check the OP, there are already the steps given to unroot and relock
mihahn said:
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Click to expand...
Click to collapse
I tested this on Android 4.4.4... it works fine!
Note: with TowelRoot v3 it isn't necessary reboot, but when I've tried to update SuperSu it fails so reboot and that's all
Thanks so much!
I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?
PGvossman said:
I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?
Click to expand...
Click to collapse
It updates the superuser binary that got installed by Towelroot I guess
will this method work on the nexus 5?
mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
F
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done
Click to expand...
Click to collapse
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks
anees167 said:
will this method work on the nexus 5?
Click to expand...
Click to collapse
Yes, it should work fine. Try it
dodgebizkit said:
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks
Click to expand...
Click to collapse
These two are basically the same, as they are apps to manage the superuser permissions of other apps. You may use the one you like
That was easy
Of course I don't see this thread unitl after I spent the last hour setting everything up in Ubuntu to root the old fashioned way! Used this and was rooted in no time.
ota updates affected or not?
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...
ashutoshchauhan211 said:
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...
Click to expand...
Click to collapse
see towelroot only roots your device.
You can get OTA PROVIDED - You dont change any of the stock files.. Nothing should be changed.
mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
Click to expand...
Click to collapse
Hi, I have rooted Nexus 4 4.4.4 with towelroot app (and I have SuperSu app).
Now, If I install custom recovery, I will lost data? With custom recovery, I will get OTA update?
Thank you
blank nexus 4 without ROM
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......
nexusfans said:
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

[How-To] Update to I537_OC7 - 5.0.1 and KeepRoot

**You can begin the following process from 4.4.x Build/ROM or higher but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Caution!** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Download:
- I537_OC7_Stock_Rooted_ROM
- I537_OC7_Stock_Rooted_Deodexed_ROM
Pevious Builds:
- I537_OC6_Stock_Rooted_ROM
- I537_OC6_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to "Download."
6. Press the lightning bolt then "Ok" to begin the flash.
7. Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- I537_OC7_TetherAddOn
- I537_OC6_TetherAddOn (Flash using FF's "Flash zip or ota" option.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@thisisapoorusernamechoice - for capturing the ota update and for his system dump.
@Chainfire
muniz_ri said:
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Attention** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Instructions:
Click to expand...
Click to collapse
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix
thisisapoorusernamechoice said:
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix
Click to expand...
Click to collapse
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon
Joe-Tech said:
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon
Click to expand...
Click to collapse
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option
thisisapoorusernamechoice said:
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option
Click to expand...
Click to collapse
Only way im thinking to boot the new LP ROM, is to use @muniz_ri method so we can upgrade and keep root. So now we going to be on the OC6 kernel and baseband, since the gpe can boot without flashing the kernel. Then we can flash the GPE 5.x ROM, either with safestrap or FlashFire, and we can also use Odin to flash the stock kernel/partitions. But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.
Joe-Tech said:
But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.
Click to expand...
Click to collapse
Were other rooted apps able to get root permission?
thisisapoorusernamechoice said:
Were other rooted apps able to get root permission?
Click to expand...
Click to collapse
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.
delete
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Joe-Tech said:
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.
Click to expand...
Click to collapse
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question
thisisapoorusernamechoice said:
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question
Click to expand...
Click to collapse
I don't think it will make any difference.
@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
Extract the tar from the rar. Leave the zip as is. Copy the tar and the zip to your phone's internal memory or external SD card, somewhere it'll be easy for you to find
Devo7v said:
@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.
Click to expand...
Click to collapse
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.
mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
If all of the above is beyond your level of understanding I strongly suggest you reconsider attempting to modify your phone.
muniz_ri said:
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.
Click to expand...
Click to collapse
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.
Devo7v said:
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.
Click to expand...
Click to collapse
Did not bother to try since it has not worked on any 5.0 release so far.
muniz_ri said:
Did not bother to try since it has not worked on any 5.0 release so far.
Click to expand...
Click to collapse
Any chance I can implore you to try it since there will inevitably be a bunch of people already on the OC6 firmware asking how to root it and will get pissed when they find they have to wipe their phone? Or maybe you could just provide the stock OC6 kernel and I can convince @thisisapoorusernamechoice to give it a shot?
For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.
bobbylx said:
For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.
Click to expand...
Click to collapse
A couple questions:
What firmware were you coming from?
How long did you wait?
Did you have Xposed enabled?

[Q] First Time Rooter, Gs6 SM-G920T, need help intresting problem cant find fix.

#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!
#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.
How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated
Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!
Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues
thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.
Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6
CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002

[How-To] Update to G870A(Active Model)_OJ3 - 5.1.1 (Unrooted Stock ROM)

**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Note** Rooting all Samsung 5.1.x builds currently requires a modified kernel therefore, due to the locked bootloader, achieving root on this build/device is not currently possible.
Downloads:
- G870A_OJ3_Stock_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to *"Download."
6. Press the lightning bolt then "Ok" to begin the **flash .
7. Once the flash is complete and the device reboots into "Download" mode, flash the G870A_OC5_Bootloader using Odin's PDA/AP slot.
*If you are already on the OC5 bootloader, set "Reboot" setting to "Normal" and skip Step 7.
**The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
Once complete your device will reboot and pause on the AT&T splash screen for about 1 - 2 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Recommended: Package Disabler Pro to disable unwanted bloatware (root access not required).
Known Issues:
- None!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery. The bootloader will not be flashed in order to allow for downgrading to previous firmware versions.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Sweet! I have been anxiously waiting for this for my active. Thank you!
Sent from my SAMSUNG-SM-G900A using Tapatalk
I want to try it so bad, but I need my root!
Could everybody tell us what you think performance/battery wise though?
Thanks a lot!
Awesome gna do some flashn!
Thanks @muniz_ri.
Sent from my SAMSUNG-SM-G870A using Tapatalk
Followed the directions and it worked fine.
Used the suggested package disable pro with the defaults and then updated everything. Phone seems to be working fine so far.
I did read in one of the other threads that the battery life and such might not be as good as expected because we are still on the old bootloader, is this true or does the bootloader have nothing to do with the operating system?
Oh man....now do I...or don't I....
Install went well. Now to test.
Sent from my SAMSUNG-SM-G870A using Tapatalk
AnarchoXen said:
Oh man....now do I...or don't I....
Click to expand...
Click to collapse
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk
If it requires root to flash... I would hope that I could then keep root after the flash.
I'm holding off on 5.1.1 until root is available. Just can't do without it I don't think.
Well i went ahead and did it, no problems at all. Now to see if I really can live without root!
Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.
Very good. Running smooth and fast. I do miss some root features.
SM-G870A Peace
Teranode said:
Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.
Click to expand...
Click to collapse
You can save yourself some time, or not, but all that has already been tried. No current way to root 5.1.1 on locked bootloader devices.
Meh I have a bunch of nexus and 2 one plus phones I just wanted to see of I can get this working on a s5 model. Att still committed to their locked bootloaders
berniesteven said:
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
I am! Now...at the ATT logo screen currently.
Well that was quick.
So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!
orion2323 said:
So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!
Click to expand...
Click to collapse
Odin back to ne4. See the op.
SM-G870A Peace
berniesteven said:
Odin back to ne4. See the op.
SM-G870A Peace
Click to expand...
Click to collapse
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it but needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...
orion2323 said:
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it buy needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...
Click to expand...
Click to collapse
Glad it worked out well for you. If I helped, don't forget to hit thanks.
SM-G870A Peace

Categories

Resources