Related
I have a note 3, that I'd like to root and install a non Att OS.. it's no longer a covered phone..and I don't care about tripping knox.. Searching for Root and Note 3 and ATT find all kind of way to root and install safestrap.. is that the only way to custom rom this phone?
crysallis said:
I have a note 3, that I'd like to root and install a non Att OS.. it's no longer a covered phone..and I don't care about tripping knox.. Searching for Root and Note 3 and ATT find all kind of way to root and install safestrap.. is that the only way to custom rom this phone?
Click to expand...
Click to collapse
What are you running right now Kitkat, Lollipop? If you are on N900AUCUCNC2, you can use Towel root https://towelroot.com/ or Kingo root http://www.kingoapp.com/ The only way to install custom rom is to have Safestrap install as the bootloader is locked.
Rooted i747 said:
What are you running right now Kitkat, Lollipop? If you are on N900AUCUCNC2, you can use Towel root or Kingo root
Click to expand...
Click to collapse
I'm not the OP, but I have the same question: I have a stock Note 3 with Lollipop (N900AUCUEOC1). I'd love to root it. Is there a step-by-step guide, or better yet a tap-and-go app to achieve root?
Hiram_Q_Pustule said:
I'm not the OP, but I have the same question: I have a stock Note 3 with Lollipop (N900AUCUEOC1). I'd love to root it. Is there a step-by-step guide, or better yet a tap-and-go app to achieve root?
Click to expand...
Click to collapse
You can't root OC1, but you can use Odin to downgrade to NC2 and root it. Odin v.3.10.6 http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613. Once you Odin back you can use Towel root or Kingo root (links are posted above your post). Then install Supersu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and run it, install Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en open and install it, then Safestrap http://forum.xda-developers.com/devdb/project/dl/?id=7216. (You should make a backup once Safestrap is installed before you flash any Roms). Once you're done you can pick a Rom for your Note 3 http://forum.xda-developers.com/note-3-att/development Now you ever use Odin? http://www.samsungodindownload.com/odin-tutorial/ (The site only shows flashing the All-In-One file so you know). Use all 4 Odin files, N900AUCUCNC2 ODIN Files, BL https://www.androidfilehost.com/?fid=96042739161891602 AP https://www.androidfilehost.com/?fid=96042739161891890 CP https://www.androidfilehost.com/?fid=96042739161891603 CSC https://www.androidfilehost.com/?fid=96042739161891604
Brilliant! I'm rooted on Lollipop, and loving my Note 3 all over again. Thanks for the easy-to-follow instructions, that made it a breeze!
lil differant way
To shorten the process, I downloaded Chainfires app called FlashFire, Then Downloaded full OC1 odin tar and Full N2 Odin tar. I flashed Note 3 back to N2 with pc odin, I then transferred OC1 to my sd card installed Flashfire and used flash Fire to do a complete flash to OC1 while choosing to inject everroot. Saved tons of time and in my mind a lot cleaner. I also have ROM PRO TOOL BOX and Chainfires CF-Bench after installing all the apps I wanted and setting up my personal settings on the phone all together, I installed BusyBox Pro and did a smart install, then rebooted and performed a benchmark. Then opened Rom Pro Tool box and went to cpu and then the benchmark it recognized the benchmark from chainfires cf-bench app so I choose it and also clicked apply at boot. Rebooted and this Note is fast as light and reliable. FlashFire will make back ups for you if your worried about recovery and always a good Idea to have Helium and or Titanium to make a nandriod and a completed setup back up to store on your pc and cloud just in case. :fingers-crossed:
Does anyone know if Rooting directly from OC1 without a wipe is being worked on? :fingers-crossed: or should I just stop whining and just do one of the above options? :victory:
debugrr said:
Does anyone know if Rooting directly from OC1 without a wipe is being worked on? :fingers-crossed: or should I just stop whining and just do one of the above options? :victory:
Click to expand...
Click to collapse
Do from post #4
Help! Stuck on AT&T load screen after Odin
Followed post 4 instructions, but after Odin (which said PASS!), phone is now stuck on white boot screen with AT&T logo. Checked md5, everything checks out. What do you think went wrong?
camkatastrophe said:
Followed post 4 instructions, but after Odin (which said PASS!), phone is now stuck on white boot screen with AT&T logo. Checked md5, everything checks out. What do you think went wrong?
Click to expand...
Click to collapse
What was you running before, Lollipop? If you was, you need to do all four files not the All-In-One to change your boot loader back to NC2.
so much simpler
Thanks for making this simpler! If all goes well then you will be donated to good sir! now if you could just get someone on my at&t s5 active!
dwillimon said:
now if you could just get someone on my at&t s5 active!
Click to expand...
Click to collapse
I have a s5active and just love the hell out of it. I'm still kinda green with the rooting but have done several successful roots, but development is way out of my wheelhouse. Unfortunately I haven't found a developer that had been working on the active. I'm still looking though. Thanks for doing the outstanding organization you did for the note 3. I'm going to be doing it as soon as the laptop comes back from the shop. My wife will like fire cat I think. I just found the thread I needed for my active lol only one rim but better than nothing.
Hey all, I've been away since the Skyrocket days. For ODIN, what state does the phone need to be in. I have USB debugging Enabled, but the ODIN says Failed. I downloaded all 4 files. Nevermind, had to put the phone in download mode.
i used KingoRoot to "root" it said it was sucessful, but when i try SuperSU it said "SuperSu Binary needs to be updated. Continue"? when i click continue, i click on normal and it says "Installing, please wait" then it returns failed.. SuperSu binary is not updating what is the fix for this?
Kid27085 said:
i used KingoRoot to "root" it said it was sucessful, but when i try SuperSU it said "SuperSu Binary needs to be updated. Continue"? when i click continue, i click on normal and it says "Installing, please wait" then it returns failed.. SuperSu binary is not updating what is the fix for this?
Click to expand...
Click to collapse
I would install Root Checker https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en to see if your root is properly installed. You might have to use KingoRoot again. I usually stick with Towelroot.
i tried superuser and that said it might not have installed properly. I tried flashing the ODIN files again and now it says failed. I think i've bricked my phone and now im really frustrated
Kid27085 said:
i tried superuser and that said it might not have installed properly. I tried flashing the ODIN files again and now it says failed. I think i've bricked my phone and now im really frustrated
Click to expand...
Click to collapse
Can you get into download mode?
Rooted i747 said:
Can you get into download mode?
Click to expand...
Click to collapse
ok i have just gotten mad and constantly click on the start button in ODIN until it seemed to have worked. Well.. glad to say, my phone is up and running with 4.4.2 , rooted with TowelRoot, Installed SuperSu and installed BusyBox... now to find a cool rom to run it on. Thanks for all the help guys.
Rooted i747 said:
You can't root OC1, but you can use Odin to downgrade to NC2 and root it. Odin v.3.10.6 http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613. Once you Odin back you can use Towel root or Kingo root (links are posted above your post). Then install Supersu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and run it, install Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en open and install it, then Safestrap http://forum.xda-developers.com/devdb/project/dl/?id=7216. (You should make a backup once Safestrap is installed before you flash any Roms). Once you're done you can pick a Rom for your Note 3 http://forum.xda-developers.com/note-3-att/development Now you ever use Odin? http://www.samsungodindownload.com/odin-tutorial/ (The site only shows flashing the All-In-One file so you know). Use all 4 Odin files, N900AUCUCNC2 ODIN Files, BL https://www.androidfilehost.com/?fid=96042739161891602 AP https://www.androidfilehost.com/?fid=96042739161891890 CP https://www.androidfilehost.com/?fid=96042739161891603 CSC https://www.androidfilehost.com/?fid=96042739161891604
Click to expand...
Click to collapse
Thanks for this.
My note 3 is on OC2 and running Android 5.0.
Does this instruction work for my phone?
Thanks
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.
I'm a bit slow to realize this, but after updating to T mobile's latest 20b firmware (lollipop 5.0x), it lost root. I then tried to root it, using the three methods mentioned here: http://forum.xda-developers.com/showthread.php?t=2732311.
Towelroot clearly doesn't work anymore. The zip file in the above thread couldn't be flashed since there's no recovery operation possible (just showing an android with ! in a triangle sign). I also tried the purpledrake, but the script doesn't run when the phone is connected with all drives installed and adb devices showing the phone. I then tried to get fastboot mode back (to install twrp/cwm recovery to flash the zip file) by following http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825 which I have done successfully before, but then couldn't do it because it requires root (doh!).
So it seems that I just lost my ability to root, unless I downgrade to a stock kitkat (10e?) from tmobile, and then towelroot/etc. assume those work.
Anyone with experience on the stock 20b firmware? Can you root it and how? I'd love to use the beautiful 12.1 Cyanogen that's available here, but the camera doesn't work right on mine. Thus stock 5.0 seems to be the best option. Many thanks.
I got a bit further on the purpledrake method, in that I had to do a clean restart on the phone and connect to usb before the script will recognize. However, it ends up giving a really quick error message after trying a temp root: "your phone is not running a compatible software version. No vulnerable mode detected. Rebooting phone."
Anyway, many thanks to @brossovitch I followed http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/ and it works like a charm. I can't seem to delete this very short thread so I thought I'd wrap it up with a solution. If it seems a bit useless please remove the thread (or tell me how to do it since I can't find the "easy button"). Thanks.
So, today I upgraded to 6.0 and had a hell of a time (took me 7 hours) and the problem was that when I installed su from twrp it'd soft brick my phone, anyway, that's not the problem, the problem is everything is saving to /storage/emulated and I can't access it without root. I noticed this when I was on OGInsta and I wanted to download a picture, it gave me an error code about how it couldn't find the directory, so I went to my file manager, everything was fine but I accidentally hit up instead of home and it brought me to an empty page. I started messing with the settings of my file manager assuming something went wrong with it, new version etc, and I found it had a root option. I clicked it and gave it root access and went back and I could see the files where I was previously. To make sure I tried to save something on kik, didn't work. I tried accessing my storage from the rar app and it wouldn't. I don't know what's going on or how it even got this way.
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
scryan said:
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
Click to expand...
Click to collapse
Also, to clearly, I have 2 storage paths. One is "sdcard/" and the other is "storage/emulated/0" I'm not sure if the "storage" folder is new in 6.0, I know 4.+ and 5.+ used "sdcard/". Too see "storage/emulated/0" I need to grant root access to the file manager. And any app the does not have root, cannot access that directory.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
Click to expand...
Click to collapse
you might have knowledge in making apps, but you are missing lots of knowledge when modding your phone. you are going to have to use an app like root explorer, and find where your storage was placed, then move it to the right location. or you can reflash the factory image. ive always just moved my storage back when its happened to me. anyways, flash the factory image the right way, not through a toolkit. then flash any custom kernel(if flashing marshmallow), and supersu.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat.
Click to expand...
Click to collapse
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
YoureVexing said:
So then I used adb, flashed boot.img and then recovery.
Click to expand...
Click to collapse
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
scryan said:
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
Click to expand...
Click to collapse
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
YoureVexing said:
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Click to expand...
Click to collapse
/sdcard is a simlink, its the same folder.
internetpilot said:
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
Click to expand...
Click to collapse
The rootkit wasn't working for me, it's been a charm for my nexus 5 and from 4.+ and nexus 6 on 5.+, on 6.0 it wasn't working so I tried to flash it on fastboot and I still got the same thing. I'll try it once more I suppose, thank you.
Preface
I understand this tablet is old but the ability to 'possibly' obtain root opens up a modicum of options for enthusiasts looking to prolong their investment.
Summary
Was experimenting tonight (3/27/18) and found it IS possible to change models from T818A (AT&T) to T818W (Canadian variant).
This is significant because, to my knowledge and research, no foolproof method exists to introduce root access to T818A (and possibly T818T and T818V).
By changing T818A to T818W, we can hopefully forgo the need to utilize engineering boot images or Kingroot. We can simplify the root process by utilizing Odin and injecting CF-Root.
A_H_E said:
Preface
I understand this tablet is old but the ability to 'possibility' obtain root opens up a modicum of customization for enthusiasts looking to prolong their investment.
Summary
Was experimenting tonight and found it IS possible to change models from T818A (AT&T) to T818W (Canadian variant).
This is significant because, to my knowledge and research, no foolproof method exists to introduce root access to T818A or T818V.
By changing T818A/V to T818W, we can forego the need to utilize engineering boot images or Kingroot. We can simplify the root process by utilizing Odin and injecting CF-Root.
Current Status
The device is recognized as 'T818W' after multiple restarts and factory resets.
Unfortunately CSC is hit or miss.
Originally, on first flash, there was no CSC listed and as such, every single CSC option was available under 'Settings'. I was able to finally introduce 'RWC' (Rogers) successfully and that eliminated duplicate options.
In addition to the firmware change, in Android Recovery, both 'product.name' and "ro.product.device' reflect the alteration.
On the AT&T Tab S2 9.7", prior to the software flash, the following is seen:
samsung/gts210velteuc/gts210velteatt
After the firmware flash, the syntax is replaced with the following:
gts210veltevl/gts210veltecan
Next Steps
I want to ensure I can go back to T818A from T818W and vice-versa.
I'd also like to see if I can go from T818A to T818V and then to T818W.
If I can do these steps without any alterations to the EFS Partition (e.g, IMEI), I will then attempt root.
If all these methods come back without error, I will provide the necessary steps to use at your discretion.
Misc.
This research was inspired by @ashyx and his efforts to procure root on the AT&T and Verizon versions of the Tab S2 9.7.
Click to expand...
Click to collapse
What parts were you able to flash with odin? The important part is the bootloader.
Also I think I remember someone posting something similar before, may have even been this model, whereby the firmware from one model successfully flashed to the other. As I recall this was Verizon to Rogers, but as it turned out both had locked bootloaders, so it looked like the bootloader images were the same regardless of carrier.
I'm not 100% on this as it's a while ago.
There's a fairly safe way to determine if the bootloader will allow anything to flashed by simply flashing an unsigned recovery image.
One thing I would like to know is how picky the bootloader is with flashing unsigned cache images.
Anyway keep us posted.
@ashyx
Thanks for the response,
When going from T818A to T818W, BL, AP, and CP load successfully however I have to use Prince Cosmy's build of Odin. I found that CSC will sometimes fail when using Rogers, so I keep it set to AT&T.
When reverting back to T818A, I am using the 3.12.7 build of Odin and all four combination files load successfully (BL, AP, CP, and CSC).
A_H_E said:
@ashyx
Thanks for the response,
When going from T818A to T818W, BL, AP, and CP load successfully however I have to use Prince Cosmy's build of Odin. I found that CSC will sometimes fail when using Rogers, so I keep it set to AT&T.
When reverting back to T818A, I am using the 3.12.7 build of Odin and all four combination files load successfully (BL, AP, CP, and CSC).
Click to expand...
Click to collapse
Well at least the bootloader flashes OK. When flashing the CSC is it cache.img that fails?
It's strange.
Prince Cosmy will install CSC without error.
It's during the reboot, and the subsequent 'Installing System Update..." that it will sometimes error out at 34%.
But it's not consistent behaviour.
However, after using CF-Auto-Root-gts210veltecan-gts210veltevl-smt818w.zip, and on T818W after flashing from T818A via Prince Comsy, I have root.
In the process of testing SuperSU to confirm it works.
A_H_E said:
It's strange.
Prince Cosmy will install CSC without error.
It's during the reboot, and the subsequent 'Installing System Update..." that it will sometimes error out at 34%.
But it's not consistent behaviour.
However, after using CF-Auto-Root-gts210veltecan-gts210veltevl-smt818w.zip, and on T818W after flashing from T818A via Prince Comsy, I have root.
In the process of testing SuperSU to confirm it works.
Click to expand...
Click to collapse
Excellent, the fact that CFautoroot even flashed without being rejected is good news. The fact that the script ran is even better news!
I just hope it boots up and is rooted.
Which version of SuperSU did you flash?
Okay, just repeated the process from scratch.
I factory reset the device.
Installed the February 2018 build of Nougat from AT&T via Odin.
Both 'product.name' and "ro.product.device' reflect the alteration:
samsung/gts210velteuc/gts210velteatt
Confirmed that the model name in 'Download Mode' and in Android states 'T818A'.
Factory reset the device again.
Launched Prince Comsy's Odin and loaded Roger's February 2018 build of Nougat via Prince Comsy Odin (including CSC which took without error).
Now 'product.name' and "ro.product.device' is replaced with the following:
gts210veltevl/gts210veltecan
Confirmed that the model name in 'Download Mode' and in Android states 'T818W'.
For SuperSu, I used 2.82-SR3.
(https://download.chainfire.eu/1129/...Root-gts210veltecan-gts210veltevl-smt818w.zip)
Rebooted three times before loading into 'Welcome screen".
Everything else works flawlessly.
I even managed to change CSC to XAC, which wiped root, and I flashed SuperSU again.
See screenshots.
I'm off to work now.
If you need anything else tested or answered, I'll get back to you later this afternoon (I'm in EST).
I'd like to revert back to T818A and test T818T and V (provided I can get proper combination sets).
I'm thinking since T819 is the same hardware, it should work as well but having custom recovery would work wonders so I can do a proper NANDroid backup before something goes to bullocks.
A_H_E said:
For SuperSu, I used 2.82-SR3.
(https://download.chainfire.eu/1129/...oot-gts210veltecan-gts210veltevl-smt818w.zip)
Rebooted three times before loading into 'Welcome screen".
Everything else works flawlessly.
I even managed to change CSC to XAC, which wiped root, and I flashed SuperSU again.
See screenshots.
Click to expand...
Click to collapse
Unbelievable, you've discovered a major thing here!
It seems you've managed to flash an unlocked bootloader over the locked bootloader.
Is SuperSU running in systemless or system mode?
Congrats on actually doing this and taking the risk.
From the system details, under 'Settings', looks like 'system-less root mode'.
Attached is another screenshot.
A_H_E said:
From the system details, under 'Settings', looks like 'system-less root mode'.
Attached is another screenshot.
Click to expand...
Click to collapse
Yep systemless. Which means that a custom recovery can be flashed also.
This is the first time I've ever heard of a Samsung bootloader being overwritten by an unlocked one.
Amazing stuff and you may have opened doors for other devices too.
Given your experience, is this something you can create recovery for or do we need to involve other parties?
Thanks!
A_H_E said:
Given your experience, is this something you can create recovery for or do we need to involve other parties?
Thanks!
Click to expand...
Click to collapse
Recovery no problem, but I doubt there's any need. TWRP for the T819 should work fine.
Restored back to stock T818W using Odin (3.12.7).
Bootloader is unlocked under 'Developer Options'.
TWRP for T815 (twrp_3.1.0-1_sm-t819_14417n) will not boot. See attached screenshot.
TWRP for T819 (twrp_3.1.0-1_sm-t815_13317) works however I've run into a few issues.
Reboot Into Recovery
Whether or not you select the option 'Allow Modifications', if you go to 'Reboot' and attempt to reboot into 'Recovery', the device restarts and proceeds to load into Android.
MTP
Once you 'Allow Modifications', format data and power off, you have the option to mount 'System' on restart.
The problem is that even though MTP is enabled, the device does not appear under 'File Explorer' in Windows.
The Device shows under 'Device Manager' and 'AutoPlay' provides you the option to disconnect but you cannot access the file store.
See screenshots 1 & 2.
ADB does, however, work.
TWRP aside, it appears we can now unlock the T818A bootloader by flashing the T818W bootloader through PrinceComsy.
I only have access to two T818A devices so I can only verify this works for AT&T.
If anyone else is reading this and is on Verizon, T-Mobile or have a T819, you may also have the same luck if you are willing to flash the T818W bootloader.
If there is interest, I can provide the software/steps for the community to further investigate.
A_H_E said:
TWRP aside, it appears we can now unlock the T818A bootloader by flashing the T818W bootloader through PrinceComsy.
I only have access to two T818A devices so I can only verify this works for AT&T.
If anyone else is reading this and is on Verizon, T-Mobile or have a T819, you may also have the same luck if you are willing to flash the T818W bootloader.
If there is interest, I can provide the software/steps for the community to further investigate.
Click to expand...
Click to collapse
Just out of interest did you ever try flashing CFautoroot with Prince comsey odin when it had the T818a bootloader?
Unfortunately not but I understand what you are inferring.
I have one untouched device (locked bootloader) left to test with.
I am happy to try this after the Holiday weekend.
A_H_E said:
Unfortunately not but I understand what you are inferring.
I have one untouched device (locked bootloader) left to test with.
I am happy to try this after the Holiday weekend.
Click to expand...
Click to collapse
I will be trying to flash a VZ model later on. Will update thread with results.
Any chance you can share the files used to do this? I would like to attempt it on my T818A as well.