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.
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
I have a Advent Tegra Note 7
Upgraded to kitkat and OTA 2.4.1
Used Tomsgt supertool 2.4.1 tool to root, installed TWRP (and made a backup image of my freshly installed system)
I've since added some games and apps and spent a fair bit of time customizing the system, but when I attempt to run Titanium Backup it tells freezes when "asking for root rights" so I ran "root checker basic" from playstore, which tells me I don't appear to have proper root access..
Here's a break down of what I've done, I've tried to keep it conscise...
I have tried installing a SuperSU, SuperUser and SU Update fixer, Also reinstalling the SuperSU-v1.94.zip using both cwm and twrp... Still no proper root access.
Ideally I'd like to try some other things to get root access before reflashing and having to reinstall my apps and settings, can anyone help or suggest anything else I could do.? I can't think of anything I could of accidentally done to break root access, this is still quite a clean system just setup in the past two days.
P.S.When using the supertool impacter tool and scan for usb driver I get a "no such device" error, even though the device is listed in the previous screens.. also I suspect the correct drivers are there as ADB seems to work fine
they flashing SuperSU-v1.99r4.zip from http://download.chainfire.eu/447/SuperSU/. I haven't had issues with root via either method.
If that fails you can use the n7root.img which is downloadable here: https://github.com/linux-shield/shield-root/blob/master/root_tn7.img?raw=true then go into fastboot mode and then type fastboot boot root_tn7.img. DO NOT USE FASTBOOT FLASH BOOT with this image as it will make it bootloop, just use fastboot boot command.
SOLVED
Thanks for the pointers hacktrix2006.. I tried supersu-v1.99r4.zip also v2 no luck. Had a quick look for how to get into fastboot mode.. couldn't access it from the bootloader.. so decided to take a backup image and restore to stock kitkat 4.4.2 via tomsgt latest tool 2.4.1 including doing Wipe data. then reinstalled TWRP then applied root.... AND noticed a screen saying something like ROOT ACCESS MAY BE FAULTY.. WOULD YOU LIKE TO FIX THIS.. I also think there was a warning about "be careful this action is irreversable" - I suspect the previous time I hadn't understood this properly and selected NO !! Anyway this time I said yes and now have ROOT YAY!
Now I start a re setup of the system and installation of apps etc.. I guess it's often a bit smoother 2nd (or 3rd 4th etc) time around
OK thx again for the encouragement, plus now I have a little more experience to offer someone else who may be struggling in this area.
no problem!
I have a UK XT1604 Retail device which is running the current TWRP and is rooted with the stock rom.
The device was rooted with the guide from here, but at the time I didn't realise device encryption was not enabled...
Now I'm trying to enable to device encryption, but the process never starts (by the looks of it) the phone reboots to the Moto/Lenovo logo and just sits there. A manual reboot brings back the normal OS with no changes. I've seen some other posts which say I need to un-root, and other which say I just need to re-flash the boot.img file
Can someone tell me the correct process for enabling device encryption and re-rooting the device after.
I was unable to find the stock UK Retail image for this phone, but I have found a o2 version - can I use any .img files I need from that safely ? My other option is - I have an identical none-rooted device, if I fastboot TWRP (rather than install) can I extract and use the .img files from that device on mine? - This has been uploaded this morning - but its not 100% clear is this is UK and for the XT1604
Can anyone confirm the current 3.1.1-0 supports encrypted file systems and can access them?
Very new to all this Android stuff so any help is very welcome.
You should be able to unroot from the SuperSU app (at least that's what I did) and then encryption will work normally.
bsevcenk said:
You should be able to unroot from the SuperSU app (at least that's what I did) and then encryption will work normally.
Click to expand...
Click to collapse
I'd seen the option but wasnt sure if I needed the full un-root, or just 'disable super user' I presume once I've encrypted I just need to re-flash the SuperSU zip file?
iam-q said:
I'd seen the option but wasnt sure if I needed the full un-root, or just 'disable super user' I presume once I've encrypted I just need to re-flash the SuperSU zip file?
Click to expand...
Click to collapse
You'll need to do a full un-root, encrypt, and then you can flash the SuperSU zip again.
So the encryption worked fine & is set with a password. Now I'm unable to access TWRP in recovery mode as it won't accept the known working password.
I Changed the password to a PIN and that allows me to access TWRP - but if I change it back to a password TWRP flat refuses to accept it. I've seen old issues relating to earlier versions to TWRP where people had the same issue, but nothing relating to the current version. Any ideas?
I updated to 9.0.11 today, reflashing TWRP and Magisk 18.
Upon reboot, I get a vague semblance of the screen where I enter my PIN, then IMMEDIATELY the notification "Power Off - Shutting Down."
I have reinstalled the update, can still boot into TWRP.
The only time I have had a similar experience was when I screwed things up playing with substratum. I finally gave up trying to master that, and today I removed the substratum program from my phone.. Thinking this might be the problem, I tried the Rescue Tool for Substratum but it made no difference.
What steps do I need to take to get the phone to boot into the operating system, instead of just shutting down.
Thanks so much for any insights and assistance.
Robert
Flash magisk in twrp
Flashing Magisk in TWRP will not fix the issue i believe, I tried it, it happened to me to when I moved to v9.0.11. You have to uninstall Magisk using the Magisk uninstaller first, reboot TWRP then flash TWRP again.
BeachNYC said:
I updated to 9.0.11 today, reflashing TWRP and Magisk 18.
Upon reboot, I get a vague semblance of the screen where I enter my PIN, then IMMEDIATELY the notification "Power Off - Shutting Down."
I have reinstalled the update, can still boot into TWRP.
The only time I have had a similar experience was when I screwed things up playing with substratum. I finally gave up trying to master that, and today I removed the substratum program from my phone.. Thinking this might be the problem, I tried the Rescue Tool for Substratum but it made no difference.
What steps do I need to take to get the phone to boot into the operating system, instead of just shutting down.
Thanks so much for any insights and assistance.
Robert
Click to expand...
Click to collapse
I would flash the nandroid you created before you began altering everything. You did make a back up nandroid with TWRP right?
Jimi Mack said:
I would flash the nandroid you created before you began altering everything. You did make a back up nandroid with TWRP right?
Click to expand...
Click to collapse
I did indeed make a Nandroid backup on Sunday, and I am transferring it to the phone right now. I hope it works, it is my first attempt to restore a backup with the new TWRP on the 6T.
With every upgrade I follow this procedure:
1) boot to TWRP
2) flash the update (full update, no partial update)
3) flash TWRP again
4) flash magisk again
5) reboot to system
6) If magisk fails, reboot to twrp again en flash magisk again. Then it's all ok
Simple solution:
Remove all existing magisk modules in recovery by using "Magisk Manager for recovery" (search for it on XDA). This works 100%.
1. Download the latest version of the tool
2. Flash it though TWRP.
3. Go to Advanced > Terminal and enter "mm"
4. Choose "uninstall" (u)
5. It will print out your current modules. Continue to enter the name of the first and press enter for 2 times to confirm removal.
6. Do this for every module, also remove the module "mm" itself as last one
6. Reboot and install your modules.
I had this issue for several times and this fixed it effectively.
Sieth said:
With every upgrade I follow this procedure:
1) boot to TWRP
2) flash the update (full update, no partial update)
3) flash TWRP again
4) flash magisk again
5) reboot to system
6) If magisk fails, reboot to twrp again en flash magisk again. Then it's all ok
Click to expand...
Click to collapse
Thank you for the very succinct lesson on how to handle these updates. Much appreciated.
Lartsch said:
Simple solution:
Remove all existing magisk modules in recovery by using "Magisk Manager for recovery" (search for it on XDA). This works 100%.
1. Download the latest version of the tool
2. Flash it though TWRP.
3. Go to Advanced > Terminal and enter "mm"
4. Choose "uninstall" (u)
5. It will print out your current modules. Continue to enter the name of the first and press enter for 2 times to confirm removal.
6. Do this for every module, also remove the module "mm" itself as last one
6. Reboot and install your modules.
I had this issue for several times and this fixed it effectively.
Click to expand...
Click to collapse
I'm glad to hear that I'm not the only one this has happened to. I wish I knew exactly what I did wrong, but I really followed the rules regarding uninstalling Magisk, doing the OTA, going back to Magisk and installing again, and selecting the right option as to where it should be installed. Regardless, I am going to follow this right now and hopefully return my 6T (which is an AWESOME phone, IMHO) to service.
So I successfully restored my TWRP backup from Sunday. "Successful" in the sense that it was restored with no errors, but now the phone will not boot, I get the "Your device is corrupt" warning. When I push the power button to continue, it reboots to the same screen.
Suggestions for how to proceed from this point?
BeachNYC said:
So I successfully restored my TWRP backup from Sunday. "Successful" in the sense that it was restored with no errors, but now the phone will not boot, I get the "Your device is corrupt" warning. When I push the power button to continue, it reboots to the same screen.
Suggestions for how to proceed from this point?
Click to expand...
Click to collapse
the next time the issue occurs you should really just delete your modules from TWRP to fix it. Much easier.
From that point... Have you made another TWRP backup after you installed the update? If so please restore and continue to remove your modules as described in my last post
If not it could turn out tricky... Which partitions did the backup contain? All?
Lartsch said:
the next time the issue occurs you should really just delete your modules from TWRP to fix it. Much easier.
From that point... Have you made another TWRP backup after you installed the update? If so please restore and continue to remove your modules as described in my last post
If not it could turn out tricky... Which partitions did the backup contain? All?
Click to expand...
Click to collapse
Backup contained all partitions.
So I followed the procedure you outlined for removing the modules, and the phone booted! It still gives me the red warning that my device is corrupt, but does in fact boot. Thank you so much for the help. You guys are amazing.
BeachNYC said:
Backup contained all partitions.
So I followed the procedure you outlined for removing the modules, and the phone booted! It still gives me the red warning that my device is corrupt, but does in fact boot. Thank you so much for the help. You guys are amazing.
Click to expand...
Click to collapse
The sure fire way to get rid of that device corrupt screen is the MSM Download Tool and then starting over. It's drastic, I know, but WILL work.
EDIT: Should add, that tool locks your bootloader, so you'll have to unlock it again, much like it was when you took your 6t out of the box.
Same thing happened here but I'm on magisk no twrp and it only happened after reenabling the BusyBox ndk module.
Did the usual method, disabled all modules, uninstall, ota, etc. Worked fine til I reenabled that one module, then it began powering off like OP described.
Factory reset from stock recovery did the trick and root somehow still stuck afterwards. Titanium backup is quite the lifesaver, still a pain setting everything up but at least it didn't brick.
Lartsch said:
Simple solution:
Remove all existing magisk modules in recovery by using "Magisk Manager for recovery" (search for it on XDA). This works 100%.
1. Download the latest version of the tool
2. Flash it though TWRP.
3. Go to Advanced > Terminal and enter "mm"
4. Choose "uninstall" (u)
5. It will print out your current modules. Continue to enter the name of the first and press enter for 2 times to confirm removal.
6. Do this for every module, also remove the module "mm" itself as last one
6. Reboot and install your modules.
I had this issue for several times and this fixed it effectively.
Click to expand...
Click to collapse
Can you remove the modules from the Substratum app itself before applying the update from TWRP? (instead of removing modules from recovery)
zickler_malta said:
Can you remove the modules from the Substratum app itself before applying the update from TWRP? (instead of removing modules from recovery)
Click to expand...
Click to collapse
Well this has nothing to do with substratum app? I guess you mean the Magisk app.
Of course, the best and safest way to install an update is to delete modules and overlays before updating. If you do so, you will not see the issue described in this thread (which is caused by modules and not overlays btw).
In my case, I like to update with my modules and overlays still enabled. If the update works without any problems - great, and if the issue occurs I just delete the modules from TWRP.
You just gotta know where to look if anything goes wrong. And I'm that lazy type
---------- Post added at 02:27 PM ---------- Previous post was at 02:25 PM ----------
Artnig said:
Same thing happened here but I'm on magisk no twrp and it only happened after reenabling the BusyBox ndk module.
Did the usual method, disabled all modules, uninstall, ota, etc. Worked fine til I reenabled that one module, then it began powering off like OP described.
Factory reset from stock recovery did the trick and root somehow still stuck afterwards. Titanium backup is quite the lifesaver, still a pain setting everything up but at least it didn't brick.
Click to expand...
Click to collapse
same for you then... Next time just delete all modules by using "Magisk manager for recovery".
No resets needed.....
same for you then... Next time just delete all modules by using "Magisk manager for recovery".
No resets needed.....
Click to expand...
Click to collapse
Thx, but I am on stock recovery. This would only work in twrp if I read the thread I found correctly right?
I think the best solution is to use the 6T MsmDownloadTool v4.0 .
I think you will use everything but at least the phone will work again.
Greetings
Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.
Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.
Confirmed, it works on the cube (stark) as well...
That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.
Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.
2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.
How may I get the "su". It said, I don't have permision.
eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?
eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work
Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.
moving it to the right place.
anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?