Related
Hi there,
I recently got a Note from work, coming from two years of a Galaxy S, I understood most of the "scene" for the Note, but learned new stuff such as the dreaded 0x19 eMMC bug and Yellow Triangle (counter) when flashing via ODIN. Those things were new to me until now.
So, last night, I've spent it whole (from 2 AM to 7 AM) trying to make this work, figuring out a safe way to wipe a ICS that was filled with unsuccessful roots and left overs from previous flash. After searching, reading a lot, understanding and connected all together logically, I did it this way. Here it goes, hope it helps, since I've seen a lot of people having trouble to root this.
The premise is to start fresh with a wiped phone and go as straight as possible to ICS LQ3. If you don't want to wipe, you could avoid those steps and work around them. I wanted to share what I did so others could do it easier.
All these steps are just because LQ3 is too big to directly root (0 MB left in ROM, acording to Titanium Backup), so you have to work your way towards that.
Let's begin:
1) Flash N7000XXLC1_N7000OXALC1 Open Europe WIPE, Pre Rooted from this thread from bodivas via ODIN PC. Look for "LC1" and download it from HotFile.
What this achieves is to go back to a safe GB stock ROM & Kernel where you can safely wipe the phone via Recovery, plus it's a wipe ROM that'll do that too just when installed. This wont give you the yellow triangle or increase your custom flash counter, so don't worry.
2) Configure Play Store to download or side load the Mobile ODIN from ChainFire. I think you'll need the paid version, since I'm using the EverRoot option here, available only there.
3) Flash N7000XXLQ3 from this thread by dr.ketan or directly from SamMobile.com with Mobile ODIN with settings: Enable EverRoot, Inject Superuser (SuperSU), Inject Mobile ODIN and (optionally) Wipe data and cache and Wipe Dalvik cache for a "cleaner" migration to that new LQ3
* I've noticed that sometimes, after wiping data with Mobile Odin, you might get the "null null" error when typing with the keyboard, since it messes the CSC. What you have to do is reflash CSC (called "Cache" in Mobile Odin) without wiping again
This will flash the new LQ3 version while mantaining a partial root from the previous firmware.
4) Now if you go and open SuperSU it would say that there's a problem with the SU binary and can't be solved. What this means is that there's 0 space left in the ROM for it to update, so we need to solve this.
What you have to do is get Titanium Backup or a similar app to remove some system app and make space. What I've chosen to delete is "Setup Wizard 1.3" that is the wizard you first saw when you flashed your new firmware, so surely you won't be needing it again. It frees about 2 MB of space, but you could be deleting any other app instead of that one if you wanted.
5) Flash CF-Root-SGN_XX_SEB_LQ3-v5.6-CWM5 from this thread from ChainFire, or any other kernel of your choice, to install CWM and the latest SuperSU.
6) When the phone starts again, open SuperSU and it wil prompt it to update the binary.
Voilá! Everything is done: now you are in LQ3 with full root, SuperSU correctly working and with CWM installed. From now on, any new firmware that has a fully loaded ROM should work the same way to root.
Enjoy and hope this helped somebody out there Any questions, please let me know.
Regards,
Or http://forum.xda-developers.com/showthread.php?t=1647148. I tried it in lq3.
That obviously didn't work, was the first thing to try and there was not enough space for the Binaries to install, so at best you get a partial root, as worst (me) get no root at all and no chance to free any space for further rooting
Why not flashing CSC, CF-Kernel and LQ3 simultaneously? I did this and didn't need to inject or delete something. Just a sidenote
You could combine those flashes, that's correct, but what I wrote was what I did, each step producing one result in order to be able to trace the errors and know (if something) was working incorrectly or producing good results, and be able to pinpoint what it was.
I thought of this after several tries of other methods that failed, so this is a step by step (as title says) to root it, for people who stumbles upon the same problems I and many other have.
Partial Root?
There is not such thing as partial root. In the event that you have trouble pasting into /system, you have a corrupted /system partition. (not partial root)
To fix it:
Connect your phone to the computer via usb.
Ensure that your phone is recognized by ADB in command prompt by typing adb devices (ADB should respond with your device info)
Enter adb shell
Then enter the following syntax in adb shell:
#dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
*ensure there is no typos when inputting code as it could cause damage to the device.
Reboot your device into CWM (make sure you are on a safe kernel/recovery!, preferably Abyss 4.2)
Now format /system under Mounts and Storage (/system will not mount automatically which will allow you to format your corrupted /system partition properly.)
Then perform Full Wipe (Factory Reset, Wipe Cache, Wipe Dalvik Cash)
Flash your desired Rom (let it settle) and you will be able to edit your /system again!!!
**** This info was provided by Entropy somewhere on the forum *****
Thanks for your comments,
By partial root I meant that root could be achieved but the SuperSU apk would give the error because of the lack of space. Maybe the term used wasn't the best
Dan_Aykroyd said:
That obviously didn't work, was the first thing to try and there was not enough space for the Binaries to install, so at best you get a partial root, as worst (me) get no root at all and no chance to free any space for further rooting
Click to expand...
Click to collapse
someone else figured the same thing as mentioned here:
http://forum.xda-developers.com/showpost.php?p=27527694&postcount=1811
which lead to this advise from the wise old Dr...
http://forum.xda-developers.com/showpost.php?p=27532325&postcount=1813
which in turn lead to this but some kind soul
http://forum.xda-developers.com/showpost.php?p=27533257&postcount=1814
Ok. I had DDLB2,
Downloaded XXLQ3 - Flashed over PC odin
Downloaded Chainfire CF-ROOT LQ3 Kernel from the Thread
Flashed that over PC Odin as well
Switched ON the Phone
Downloaded Triangle Away, Said it needed a Support file, Downloaded it,
- Rebooted in a special mode, Cleared status.
Switched ON phone, did a Factory Reset.
So far Everything is Good, and I have Root Access as well.
I have edited post and added modded SuperSu busybox installer
Read This
http://forum.xda-developers.com/showpost.php?p=26455511&postcount=2475
(edited at end of rooting instruction)
dr.ketan said:
I have edited post and added modded SuperSu busybox installer
Read This
http://forum.xda-developers.com/showpost.php?p=26455511&postcount=2475
(edited at end of rooting instruction)
Click to expand...
Click to collapse
Was post #3 of that thread also updated Dr.?
The reason I asked was that there was no msg in the post #3 mentioning a
18june12 update.
Thanks
i hav updated at two place, bith place i hav mentioned date. rest are old.
Sent from my GT-N7000 using xda premium
dr.ketan said:
I have edited post and added modded SuperSu busybox installer
Read This
http://forum.xda-developers.com/showpost.php?p=26455511&postcount=2475
(edited at end of rooting instruction)
Click to expand...
Click to collapse
I've saw the SuperSU Market update today, saw the "Fix some installation problems" log and wondered if it was related to this.
I don't need to try it now again, but I'm glad this was worked out. Hopefully it installs OK now but, what does it do to free space?
what i underatand by reading script
it moves google map and youtube before installing su binarry, then again it replaces map n youtue, now if space will remain low, map or youtube or both won't get install, then you can install it from market.
Sent from my GT-N7000 using xda premium
Hi everyone,
it's my first post on the xda-developers forum, so if the kind of my posting mismatches any rules, please let me know!
I'm using this forum for quite long time now, but so far all of my questions were answered by search & read... Some weeks ago I had another question, for which I colun't find an explicit answer yet. So based on some hints from different sources (thanks to google!) I did some experiments aka try and error and would like to share my experience with you (to give something back to the comunity, who helped me a lot in the past) and see whether I finally found the answere to my question... So please let me know, whether it worked for you as well or whether you know a different / better way to solve this kind of problem.
As usual: Use this guide at your own risk!
Problem statement:
I wanted to have my SM-P900 (stock rom) both rooted and encrypted (using device encryption). I've already done this for GT-I9100 (Galaxy S II) and GT-I9192 (Galaxy S4 Duo) in the past and it worked like a charme. But for some reason I couldn't get it working on the SM-P900...
Trial log (for short version see below):
I have successfully rooted this device via the CF-Auto-Root method by Chainfire (many thanks for the greate job!). When I later tried to activate the device entcryption, it first looked like the process has started (I got a black screen with a green android manikin), but after some time (~1min) the device just re-started and booted in normal mode. I tried it several times with the same end of story - no success, no harm either.
After some time of googling I found a hint, that on KitKat devices Superuser should be temporarily de-activated in order to get the device encryption starting properly and activate it after the encryption process has finished. So I tried that and indeed, this time the encryption process started after the reboot. I let it finish and after a reboot it looked like I was where I wanted to be at. But then I realized that I wasn't able to activate the Superuser back (SuperSU said "Can't find the su binary... You need to restore it manually" or something similar). Damned! I thought "OK, let's try CF-Auto-Root again". The root process itself seemed to work, but after that the device just hang at boot... Soft-brick... :crying:
Taking a more deeper look at the script source of an Update-Super-SU package from Chainfire I realized that it also does some writes to the /data partition. Well, I guess this broke the partition, since it was encrypted... (If anyone has a better explanation for this, please let me know!)
So everything back to the start: I flashed the stock rom, did a factory reset and re-ran CF-Auto-Root... Now the device was operating properly and was rooted, but no encryption. Before starting another try of encryption, I wanted verify that the temoprary un-root wasn't broken by the encryption. So I did a temorary un-root (by removing the tick at the option "Activate Superuser" in SuperSu settings) and then activated it back right away. This worked fine. I rebooted (just to confirm everything is still working) and Superuser still worked as expected. Then (to try one more thing) I "de-activated" su again and rebooted. Trying to activate it back after the reboot, I realized that I now was at the same situation as just after the encryption, but without the encryption. I.e. the problem was not the encryption itself, but kind of a bug in SuperSU - it was not able to activate su back after a reboot (I'll try to check it via a bug report to Chainfire).
So I digged a bit deeper into this and realized that SuperSU was simply deleting the su binary in /system/xbin on de-activation and writing it back on activation. And it looked like it wasn't able to write it back after a reboot (probably because of missing permission).
Knowing that, I decided to go a step further: I flashed the TWRP (many thanks to the TeamWin guys!), booted into recovery, mounted /system and copied the su binary manually to /system/xbin. After a reboot I tried once again open SuperSU, but it still said, it couldn't find the su binary. Hmmm... There must be something more... Having another look at the script source of the Update-Super-SU package I found that at the end it was calling the su binary with the option "-install". So I booted back to recovery and tried that as well... Hurra!!! After a reboot SuperSU was finally starting and the root-apps were able to get su access... So this seemed to be the desired solution.
I deactivated su again, rebooted and started the encryption. It ran and finished successfully, as expected. After that I booted to recovery and installed su manually, as I've done it before... Reboot... finger crossed... Tadaa!!! System is back, encrypted and root is working! :good:
Solution approach:
Device is not rooted and not encypted (if already rooted, scip 2; if already encrypted, decrypt or do a factory-reset - don't try CF-Auto-Root on an encrypted device, it'll soft-brick)
Root the device (e.g. using Auto-Root-CF by Chainfire (it'll trigger the Knox-counter)
Temporarily un-root the device (when using SuperSU: go to Settings and remove the tick at the option "Activate Superuser")
Reboot
Activate the device encryption (the battery must be at least at 80% and the device must be plugged in the wall charger)
The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
After the encryption is finished the device will reboot and ask for the password, just log in
If not yet done, flash a custom recovery where you have a console access or can use ADB as root (I used TWRP)
Boot into recovery
Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
Open the console or ADB shell
Copy the su binary (if you use SuperSU: cp /system/xbin/daemonsu /system/xbin/su)
Execute the installation (if you use SuperSU: /system/xbin/su --install)
Reboot
You should be done
Thank you for the info and the simple steps. I was considering something similar to what you wanted with your device.
bruzzy,
I've followed your steps and managed to re-enable SuperSU after encryption! (used twrp)
Thank you!!!!!
Hello Bruzzy,
Thanks so much for the awesome post!
I am just having difficulty with the final steps. I am a complete newbie in regards to rooting and using these android tools.
Everything else was quite clear in your post except for these final steps.
Could you please simply a bit more step by step how I proceed to do the final steps listed below?
[*]Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
[*]Open the console or ADB shell
[*]Copy the su binary (if you use SuperSU: cp /system/xbin/daemonsu /system/xbin/su)
[*]Execute the installation (if you use SuperSU: /system/xbin/su --install)
[*]Reboot
Thanks so much!
EndlessAdventurer
bruzzy said:
Hi everyone,
it's my first post on the xda-developers forum, so if the kind of my posting mismatches any rules, please let me know!
I'm using this forum for quite long time now, but so far all of my questions were answered by search & read... Some weeks ago I had another question, for which I colun't find an explicit answer yet. So based on some hints from different sources (thanks to google!) I did some experiments aka try and error and would like to share my experience with you (to give something back to the comunity, who helped me a lot in the past) and see whether I finally found the answere to my question... So please let me know, whether it worked for you as well or whether you know a different / better way to solve this kind of problem.
As usual: Use this guide at your own risk!
Problem statement:
I wanted to have my SM-P900 (stock rom) both rooted and encrypted (using device encryption). I've already done this for GT-I9100 (Galaxy S II) and GT-I9192 (Galaxy S4 Duo) in the past and it worked like a charme. But for some reason I couldn't get it working on the SM-P900...
Trial log (for short version see below):
I have successfully rooted this device via the CF-Auto-Root method by Chainfire (many thanks for the greate job!). When I later tried to activate the device entcryption, it first looked like the process has started (I got a black screen with a green android manikin), but after some time (~1min) the device just re-started and booted in normal mode. I tried it several times with the same end of story - no success, no harm either.
After some time of googling I found a hint, that on KitKat devices Superuser should be temporarily de-activated in order to get the device encryption starting properly and activate it after the encryption process has finished. So I tried that and indeed, this time the encryption process started after the reboot. I let it finish and after a reboot it looked like I was where I wanted to be at. But then I realized that I wasn't able to activate the Superuser back (SuperSU said "Can't find the su binary... You need to restore it manually" or something similar). Damned! I thought "OK, let's try CF-Auto-Root again". The root process itself seemed to work, but after that the device just hang at boot... Soft-brick... :crying:
Taking a more deeper look at the script source of an Update-Super-SU package from Chainfire I realized that it also does some writes to the /data partition. Well, I guess this broke the partition, since it was encrypted... (If anyone has a better explanation for this, please let me know!)
So everything back to the start: I flashed the stock rom, did a factory reset and re-ran CF-Auto-Root... Now the device was operating properly and was rooted, but no encryption. Before starting another try of encryption, I wanted verify that the temoprary un-root wasn't broken by the encryption. So I did a temorary un-root (by removing the tick at the option "Activate Superuser" in SuperSu settings) and then activated it back right away. This worked fine. I rebooted (just to confirm everything is still working) and Superuser still worked as expected. Then (to try one more thing) I "de-activated" su again and rebooted. Trying to activate it back after the reboot, I realized that I now was at the same situation as just after the encryption, but without the encryption. I.e. the problem was not the encryption itself, but kind of a bug in SuperSU - it was not able to activate su back after a reboot (I'll try to check it via a bug report to Chainfire).
So I digged a bit deeper into this and realized that SuperSU was simply deleting the su binary in /system/xbin on de-activation and writing it back on activation. And it looked like it wasn't able to write it back after a reboot (probably because of missing permission).
Knowing that, I decided to go a step further: I flashed the TWRP (many thanks to the TeamWin guys!), booted into recovery, mounted /system and copied the su binary manually to /system/xbin. After a reboot I tried once again open SuperSU, but it still said, it couldn't find the su binary. Hmmm... There must be something more... Having another look at the script source of the Update-Super-SU package I found that at the end it was calling the su binary with the option "-install". So I booted back to recovery and tried that as well... Hurra!!! After a reboot SuperSU was finally starting and the root-apps were able to get su access... So this seemed to be the desired solution.
I deactivated su again, rebooted and started the encryption. It ran and finished successfully, as expected. After that I booted to recovery and installed su manually, as I've done it before... Reboot... finger crossed... Tadaa!!! System is back, encrypted and root is working! :good:
Solution approach:
Device is not rooted and not encypted (if already rooted, scip 2; if already encrypted, decrypt or do a factory-reset - don't try CF-Auto-Root on an encrypted device, it'll soft-brick)
Root the device (e.g. using Auto-Root-CF by Chainfire (it'll trigger the Knox-counter)
Temporarily un-root the device (when using SuperSU: go to Settings and remove the tick at the option "Activate Superuser")
Reboot
Activate the device encryption (the battery must be at least at 80% and the device must be plugged in the wall charger)
The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
After the encryption is finished the device will reboot and ask for the password, just log in
If not yet done, flash a custom recovery where you have a console access or can use ADB as root (I used TWRP)
Boot into recovery
Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
Open the console or ADB shell
Copy the su binary (if you use SuperSU: cp /system/xbin/daemonsu /system/xbin/su)
Execute the installation (if you use SuperSU: /system/xbin/su --install)
Reboot
You should be done
Click to expand...
Click to collapse
@EndlessAdventurer,
I'm sorry, but I don't know, what you mean with "more step by step". There are no more steps in between, the steps are as granular as possible. If you use TWRP, there is a menu "Mount" (go there and tick /system) - you should have seen it already (if not, have a look at the TWRP documentation). But you could also mount your system from the console or ADB shell.
If you don't know, what "mount", "console" or "ADB" is and are not able to use google to lern it yourself, then you should really not use this guide and even avoid rooting your device...
Beeing a newbie is not an excuse, it's completely up to you to spend some time and change this!
Please avoid quoting the whole post! If you want to reference some part of a post, pick only the relevant part and quote that.
Alternative Method
Hi,
I have used another method that also works. It worked with my Galaxy S4, Note 10.1 and now with Note Pro. Hope this can help:
1-Root your device and install/update SuperSu;
2-Convert SuperSu to system app (there is an option in SU config). Reboot.
-OBS: If your root method has already installed SuperSu as a system app, this step can be skipped;
3-As SuperSu is now a system app, it can be deactivated through Applications Management in settings. Deactivate it;
-OBS: does NOT use deactivate in SU own config;
4- Reboot in Safe Mode. This can be done pressing both Volume Up/Down while rebooting;
5-Start encryption the normal way and wait until it finishes. Enter your password and wait device boot normally;
6-Go to Applications Management in settings and activate SuperSu;
7-Reboot one more time and your system is encrypted with SuperSu working normally.
I was able to follow all of the posted solutions through but for some reason my phone insists on just booting back into Android instead of actually encrypting my phone. Any ideas?
I have a SM-G900T, TWRP, SuperSU
m33rkat said:
I was able to follow all of the posted solutions through but for some reason my phone insists on just booting back into Android instead of actually encrypting my phone. Any ideas?
I have a SM-G900T, TWRP, SuperSU
Click to expand...
Click to collapse
There is some more things that you can try with the solution I´ve posted:
1-Put original recovery instead of TWRP. I have never tried to encrypt with custom recovery;
2-When you boot in "Safe Mode", go to Application Management, running applications and stop as much processes as you can (do not stop google services).
OBS: To ensure that you have booted in Safe Mode, look at the bottom left corner of the screen an see if it shows “Safe Mode”.
rooting and encrpytion
The alternative method worked like charm....Thanks guys
NB:My tab got soft bricked after I did the factory reset and tried to root. I had to install a stock rom b4 proceeding with the guide.
Sorry to resurrect this thread but I just ran into this issue for the first time. (Thanks for posting this, btw, it's encrypting as we speak). A couple questions....what happens if we apply an OTA update after doing this? Will that cause any problems when we try to re-root it? I'm guessing after doing this CF Auto root won't be much of an option without soft bricking, right? I can always install custom recovery and fix root manually after an OTA. I'm just wondering what happens when (you know, some year) we eventually get 5.0. Thanks again!
To be on the safe side, I always unencrypt my device before a FW update with ODIN or Kies or OTA, because I root again after the update.
If you use OTA or Kies you can do the update with the device encrypted, BUT, as you are going to root again, when you install CFAutoroot your device won´t boot, because of the difference in kernel. This is the reason that I unencrypt before FW updates and proceed with encryption again after I check that everything is working as expected.
I may just fully unroot it temporarily, install the update, and then root after with custom recovery. We shall see. I suspect since we're still on 4.4.2 on the Note 10.1 2014 I got quite some time before I have to worry about it. LOL
P.S. I asked because 5.0 is going to turn encryption on by default, so decrypting may not be an option going forward.
After hours of trying to get encryption an root at the same time for my Galaxy Note 10.1 (2014), temporary disabling SuperSU just worked. Thanks! :good: (I even could skip the part with copying the su binary, probably chainfire has fixed the bug. Just tried enabling SuperSU did it perfectly.)
Hi there
I'm facing a similar problem like you on my Samsung Galaxy Tab S 10.5 LTE.
I have my device:
- rooted
- twrp recovery installed
- run custom ROM
However even when I disable SuperSU and reboot the device and then start encrypting. I only see the Android Logo and no progress. AFter a while (10 minutes or so), it reboots the tab and I end ab at screen lock login and devices is not encrypted. Any ideas?
Thank you for your great effort to help!
But, none of the methods, including the alternative from Nickfreedom did not help me...
I have a Sony Xperia Z1 with rooted Lollipop and SuperSU.
I tried to kill daemonsu with ADB before encrypting, I tried to disable the SuperSU app and I always booted into safe mode before starting encryption.
Nothing helped.
In previous times I had Xposed framework on my device, but as far as I can see, Xposed framework is no longer on my device, I installed a fresh, clean Sony ROM from scratch, I think this has erased Xposed.
Does anyone has a hint?
Thanks to everyone for the posts on this topic. I too have struggled to get my Sprint Note 4 to encrypt after rooting. I was able to encrypt with the stock unrooted ROM but I flashed the Noterized ROM and was not able to get encryption to work. I have verified the following:
1) Busybox is installed and is the latest version
2) SuperSU is deactivated. I tried this through terminal emulator and also the process defined in this thread within the SuperSU app itself. I also verified through Root Checker that SU was not active.
3) Tried in normal and safe mode with the same result
I am getting the Android screen for a few minutes and then the phone reboots. Each time I was hoping to see the encryption start but it just reboots the phone and never works. I am at a total loss for what could be causing this as the reason is beyond my capability. If anyone has ideas let me know because I am willing to try anything.
As a longshot I tried to flash back to stock ROM and encrypt which worked fine. I then tried to flash the Noterized ROM back on the phone and that didn't work. I froze on the Sprint yellow screen of death for over 6 hours.
Simplified steps for rooting &encrypting your device.
Thanks Bruzzy, I took your instructions and applied them to the Note 4. I also simplified them. I will make a universal instructions set for pretty much ALL DEVICES! Will let you guys know here when i take the time to do that.
Here is the SIMPLIFIED INSTRUCTIONS:
http://forum.xda-developers.com/not...sk-encryption-root-easy-steps-how-to-t3197425
bruzzy said:
Solution approach:
Device is not rooted and not encypted (if already rooted, scip 2; if already encrypted, decrypt or do a factory-reset - don't try CF-Auto-Root on an encrypted device, it'll soft-brick)
Root the device (e.g. using Auto-Root-CF by Chainfire (it'll trigger the Knox-counter)
Temporarily un-root the device (when using SuperSU: go to Settings and remove the tick at the option "Activate Superuser")
Reboot
Activate the device encryption (the battery must be at least at 80% and the device must be plugged in the wall charger)
The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
After the encryption is finished the device will reboot and ask for the password, just log in
If not yet done, flash a custom recovery where you have a console access or can use ADB as root (I used TWRP)
Boot into recovery
Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
Open the console or ADB shell
Copy the su binary (if you use SuperSU: cp /system/xbin/daemonsu /system/xbin/su)
Execute the installation (if you use SuperSU: /system/xbin/su --install)
Reboot
You should be done
Click to expand...
Click to collapse
Did you solve your problem whit encryption on t805 ?
sjau said:
Hi there
I'm facing a similar problem like you on my Samsung Galaxy Tab S 10.5 LTE.
I have my device:
- rooted
- twrp recovery installed
- run custom ROM
However even when I disable SuperSU and reboot the device and then start encrypting. I only see the Android Logo and no progress. AFter a while (10 minutes or so), it reboots the tab and I end ab at screen lock login and devices is not encrypted. Any ideas?
Click to expand...
Click to collapse
Did you solve your problem whit encryption on t805 ?
I have the same problem on T800 on 5.0.2.
On 4.4 encryption whit CFroot works good, but on 5.0.2 its not work
Vitaly_G said:
Did you solve your problem whit encryption on t805 ?
I have the same problem on T800 on 5.0.2.
On 4.4 encryption whit CFroot works good, but on 5.0.2 its not work
Click to expand...
Click to collapse
Hi guys,
there is an alternative instruction from Nickfreedom in my original thread: http://forum.xda-developers.com/showpost.php?p=54679223&postcount=6
I used for several devices and it works like charme (and is much simpler)...
Hey guys this is probably a dumb question but what is the advantage of encryption and does it matter if the knox is tripped since these notes are out of warranty or is it due to resale? I found a cf autoroot link that supposedly wont trip knox which is the odin method since towelroot wont work.
yesterday i successfully rooted my Tab 4 using CF Root matissewifi-matissewifizs-smt530 - then spent the entire remainder of the day trying to understand the difference between 'recovery mode' and 'ROM' and 'recovery' 'img', 'tar', 'zip' and 'nandroid' and backup and TWRP the app and TWRP the recovery and Rom Manager and Clockworkmod and why the apps don't want to download the roms I want and why my Tab 4 10.1 isn't listed in the TWRP devices so...
i attempted to install a recovery in about 50 different ways and got my Tab stuck in reboot loop about 50 times -
WHEN I DID get what i thought was TWRP (or GooIm-whatever) to download the correct recovery and reboot into the proper recovery mode i ALWAYS saw the usual recovery options: Reboot, something using ADP, something using external, Factory Reset, wipe cache, something using cache.
nothing related to TWRP or ANY custom recovery.
I'm not quite sure that all of the directions i can ever find about how to do this are written on the assumption that the user knows half of what's going on here. there are some of us who do NOT know what "Flash" means, and other terminology.
******* Can someone please tell me what i need to do to install ANY custom recovery so that I CAN create a Nandroid Backup?
I'm trying to install the new Magazine UX theme or whatever it is. (apparently this replaces the TouchWiz theme? Mine came with TouchWiz?)
glennnall said:
yesterday i successfully
rooted my Tab 4 using CF Root matissewifi-matissewifizs-smt530 - then spent the entire remainder of the day trying to understand the difference between 'recovery mode' and 'ROM' and 'recovery' 'img', 'tar', 'zip' and 'nandroid' and backup and TWRP the app and TWRP the recovery and Rom Manager and Clockworkmod and why the apps don't want to download the roms I want and why my Tab 4 10.1 isn't listed in the TWRP devices so...
i attempted to install a recovery in about 50 different ways and got my Tab stuck in reboot loop about 50 times -
WHEN I DID get what i thought was TWRP (or GooIm-whatever) to download the correct recovery and reboot into the proper recovery mode i ALWAYS saw the usual recovery options: Reboot, something using ADP, something using external, Factory Reset, wipe cache, something using cache.
nothing related to TWRP or ANY custom recovery.
I'm not quite sure that all of the directions i can ever find about how to do this are written on the assumption that the user knows half of what's going on here. there are some of us who do NOT know what "Flash" means, and other terminology.
******* Can someone please tell me what i need to do to install ANY custom recovery so that I CAN create a Nandroid Backup?
I'm trying to install the new Magazine UX theme or whatever it is. (apparently this replaces the TouchWiz theme? Mine came with TouchWiz?)
Click to expand...
Click to collapse
Follow these instructions and you will have a custom recovery installed on your SM-T530. Yes I know the title of the post is root your tablet, but this is accomplished by installing a custom recovery. Nobody here is going to take much pity on you for not understanding the terminology, we all took it upon ourselves to learn it at some point or another, it just kind of comes with the territory. XDA University can be very helpful if you feel lost or overwhelmed
thanks -
2 of the problems i encountered yesterday were:
Run Odin. Disable the "Auto-Reboot" and "Re-Partition" options... Auto Reboot and F-Reset options were grayed-out, unchangeable.
Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file... there IS no AP button, just the PDA button. everything else is grayed-out (i ran it as Admin)
not optimum conditions for new people who are TRYING to learn how this stuff works. (I'm a Web programmer and not incapable of grasping Android technology, assuming i'm reading from the correct 'literature'.) The link looks promising - but these hurdles need to be crossed first.
yesterday, CF Auto Root installed SuperSU already, so i don't know which of the following promising instructions to follow... can i just run these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
glennnall said:
thanks -
2 of the problems i encountered yesterday were:
Run Odin. Disable the "Auto-Reboot" and "Re-Partition" options... Auto Reboot and F-Reset options were grayed-out, unchangeable.
Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file... there IS no AP button, just the PDA button. everything else is grayed-out (i ran it as Admin)
not optimum conditions for new people who are TRYING to learn how this stuff works. (I'm a Web programmer and not incapable of grasping Android technology, assuming i'm reading from the correct 'literature'.) The link looks promising - but these hurdles need to be crossed first.
yesterday, CF Auto Root installed SuperSU already, so i don't know which of the following promising instructions to follow... can i just run these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
Click to expand...
Click to collapse
Yes this will install safely over your current configuration. PDA button is the correct option, on newer versions of Odin it is renamed AP, sorry. You should be using at least Odin 3.07
Since you're already rooted, you shouldn't have to worry about the auto reboot, but do install that newer version of superSU at some point, it's designed for lollipop, works better than old versions.
can I run this on top of my rooted Tab, or do i need to "unroot" it?
yesterday, CF Auto Root installed SuperSU already, so i don't know which of these following instructions to follow... can i just run all of these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
sorry, reposted in my impatience. thanks for the help.
ok, great - worked as advertised.
SuperSU updated normal, reboot, now i'm sitting on "Samsung" ... hmmm...
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
I'm currently running Stock Android, Marshmallow version 6.0.1 with the 1 November 2016 Security Patch.
The model of my phone SM-G900I (Australian edition).
So I've come across the following links with the instructions on how to root and install recovery, though quite confusing.
http://forum.xda-developers.com/show....php?t=2699648
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
If neither of the above methods work I have seen mentions of "flashing root" via TWRP.
Are there any known instructions on how to do that on XDA or any other website?
Or is it just a matter of obtaining the superSU zip file from https://download.chainfire.eu/696/supersu/ and flashing it?
The other information seems straight forward re using the Samsung Tool to backing up the device and the EFS .
Any help would be much appreciated.
Thank you.
just flash the .img file in download mode, and dont use the asc file at all. also dont use twrp 3.0.2-2, just use 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they can be pretty buggy). Towelroot has long since become irrelevant back in the 5.0 days unfortunately so all you need to do is find the appropriate supersu.zip file and put it on your phones sd card (either internal or external), boot into recovery an install that zip via TWRP then reboot. Should be good to go. The classic "root via recovery" method
Paul_Lunardi said:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
.
.
Click to expand...
Click to collapse
1. Plug in your phone and let the drivers load.
If phone unrecognized then head to Playstore you can find loads of apps for drivers
2.unplug your phone and turn it off
3.Load odin.
Some versions of Odin are outdated. So watch for that.
4.Holding your turned off phone. Hold the volume down power and home buttons. Done correctly it should bring you to a page saying custom Roms can damage your blah blah. Volume up to continue down to reboot. Plug your phone in then Push volume up if you feel ready to Join us Oh Padawan.
Now I am sorry for the lengthy information, most likely you have already gotten to this point, but I just want to make the same page for you and future readers. No point in asking a bunch of potentially irrelevant questions when one explanation is sufficient.
5. Odin should find your phone which will be represented by a lit up colored square on the left side indicating a Com:value# which number is of little consequence just tells you which port it found it at. Do not dwell on this.
6. Using an extraction program such as .7z take your CF auto root .Tar file, not the .Asc, and extract. You should be able to find an file with ap in the extension.
7.Take the path from the URL bar of this window including the name of the ap file and copy it over to Odin. In Odin you will see the place to put it is represented by AP.
8. CLICK START AND WAIT WITH JEOPARDY MUSIC.
9. IT MAY REBOOT A FEW TIMES BUT UNTIL IT SAYS success OR FAIL IN ODIN DO NOT TOUCH.
10. Repeat steps 7-9 for twrp.img
10. Now taking this was a success turn your phone off. Unplug and holding volume UP power and home Gets you into twrp recovery. If all is well you can reboot into system. Ignore the kernel warning.
^^^^^ theres the long explanation LoL ^^^^^^^^ i disagree with step 9, but meh
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Paul_Lunardi said:
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Click to expand...
Click to collapse
the cf auto root file usually isnt necessary, nor is flashing supersu really as the newer twrps have the root function built right in. Itll ask you if you want to enable superuser rights the first time you boot into it. Just swipe right and its rooted. Alternatively, flashing supersu from within twrp or the cf auto root also work. CF is the acronym for the dev ChainFire, he is the man (or she, and conversely "the woman" or whatever LOL)!! But the crux of what you need is twrp installed, from there youre usually set. Get rooted, make a nand of your stock setup and flash away. Also, id make sure to download the stock tar.md5 file of your phones firmware in case all goes awry (or to hell in a handbasket or enter clever euphemism for stuff going bad here) so you can flash the stock tarball in Odin if you get stuck in an endless bootloop and your stock restore file doesnt work. Also, when resoring from AOSP to TouchWiz or vice versa, does require a few boxes to be checked for it to work, but it happens all the time. Happy flashing and feel free to ask away if you run into anything man!
Thanks all for clarifying.
I did have some difficulties along the way though I did successfully install twrp.
So I downloaded one of the latest versions of odin on mums computer. Laiche the twrp tar file in the ap section. Loaded it then restarted the device. Ran recovery though it was still the default android recovery ie it appeared as though nothing had changed. I looked at another forum which suggested to turn ooff the auto reboot option in odin and perform a battery pull and then launch directly into twrp. This actually worked after much agony.
I then loaded a superuser zip and flashed it onto the phone.
Rebooted confirmed that the phone was rooted.
I then relaunched the twrp recovery and ran a nand? backup of my device. Then I attempted to install a custom rom ie resurrection remix. Unfortunately it did load though the screen appeared to freeze after boot and was therefore unusable. Thank goodness the restoring of the backup worked.
I'll reattempt the installation of a custom rom very soon. Fingers crossed.
Thanks.
Starting from a non-rooted SM-G950W with a locked version 7 bootloader, what does it take to make a disk image backup (like with `dd` or `adb pull`) of the /data/media, without first destroying the data that's there? Is it even possible?
I ask because I did something dumb that truncated (not deleted) all files in shared storage to 0 bytes. If I could take a disk image of /data/media, I'd be able to use offline recovery programs (like PhotoRec) to restore what was on there, but I'm currently blocked from doing that since my phone isn't rooted.
I could root my phone, but it looks like most options for rooting involve wiping out /data/.
After having done some research, it appears that I may have the following options:
Install a custom recovery like TWRP, which will grant me root access in Recovery Mode that I can use to make a disk image. The problem is that my bootloader (version 7) is locked, meaning I'd need to use Safestrap, but that apparently requires root. Is it possible to install an additional custom recovery with a locked bootloader (as opposed to replacing the built-in one) without rooting first, or am I out of luck?
Install an additional custom ROM that has root, leaving the phone's original ROM intact as opposed to replacing it, if that even makes sense.
I think I've gone in circles about what the requirements are for installing a custom recovery or ROM. This post in a G950 rooting thread says it's possible to install a custom recovery image that has root access (at least on the S8+):
https://forum.xda-developers.com/showpost.php?p=81922221&postcount=9
The linked instructions are for installing a custom ROM with Safestrap:
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
But the link for G950W leads back to the G950 rooting thread, which requires wiping /data/:
https://forum.xda-developers.com/galaxy-s8/development/root-t4060701
Also, the Safestrap install guide says that root is a requirement:
https://forum.xda-developers.com/galaxy-s8/development/recovery-locked-nougat-7-0-safestrap-t3772760
Is there a solution here, or are all options locked out?
Thanks in advance!