Hello all,
This may seem like a stupid question, but I want to make sure that I know what i'm doing before I mess something up and become
So I'm running a Samsung Galaxy S5 (G900V ovbiously), and it has the tobisha emmc chip
Is the only way to gain root on Marshmallow/Nougat or whatever is by reverting to Lollipop, gaining root access, installing TWRP, and then flashing LineageOS/some ROM?
Directions For Users With CID 11 Toshiba eMMC
1. Download EMMC_11_ Root S5_QB2_PB1.zip
2. Unzip
Copy the following to your External SD card:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and the TouchWiz ROM you want to install.
3. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
4. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
5. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
6. If you do not have an External SD Card, copy the following NOW to your Internal Storage:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and whatever TouchWiz ROM you want to install.
7. Use the File Manager in the app drawer of the phone and install Apex_Lancher.apk press home button and set Apex as the default launcher.
Install Superuser.apk, Busybox.apk and SafeStrapKK.apk do not open anything yet.
8. Now Install tr_v2.apk.
Open TowelRoot and CLICK MAKE IT RAIN . It should tell you you have succeeded.
9. Now Open Superuser app and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot. You can skip doing this. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
10. Now open the BusyBox app, grant SuperSU access and install BusyBox.
11. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed) if not click "install" again, reboot phone and open SafeStrap and try to install recovery again
12. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
13. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
14. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember, you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
15. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something bad goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
16. Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
Get the needed files at https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Related
I cannot get root back on 4.4.2 at all on FNB8 (after OTA update)
Tried using Odin 3.07 and 3.09 with CF-Auto-Root-jflte-jfltexx-gti9505
There are no errors, it reboots, goes through the small setup, reboots again yet no root. Also tried installing SuperSU zip through recovery. Still no errors but no super su on phone.
Anyone know where I'm going wrong?
EDIT: Also, just to confirm - I have checked with a root checker - there is no root
i always just use the option in philz recovery to restore root, then either install supersu app through recovery zip or install it form the play store.
it's under philz settings, then restore root
Gloris said:
i always just use the option in philz recovery to restore root, then either install supersu app through recovery zip or install it form the play store.
it's under philz settings, then restore root
Click to expand...
Click to collapse
I have CWM touch, is it OK to just install over it or do I need to remove it first somehow?
just flash the latest philz using odin. whenever you flash a recovery it replaced the whole recovery partition i believe.
Tried rooting with Philz, it went through OK. Booted into OS, downloaded Super SU. Still not root
EDIT: Sorry Gloris, I got philz working, edited just before you made that next reply.
weird, i've never had that so not sure what to suggest. just to be clear, you got to download mode and flashed philz and all went fine in odin?
and just to be sure....try removing battery for 30 seconds, then insert battery and press and hold home key and volume UP while pressing power button (I tend to keep all 3 buttons pressed until i see the "se android is not enforcing" message and it's booting into recovery.
::EDIT::
no problem, did you get root working also? i've attached the zip that i flash after choosing restore root option in philz......i didn't make this zip, so not takign any credit or anything, jsut sharing it because it might be useful.
i generally prefer my device non rooted, but i use this method to quickly restore root to apply any rom changes then full unroot from within super su app. I found it's the easiest way to gain root access (works for me even from a fresh rom install too).
Follow this ROM Installation Guide.
Root it with KingoRoot.
Flash patched aboot.img by typing "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7" command in Android Terminal Emulator App, I don't like to use PC.
Then download ChainFire SuperSU from GooglePlay.
On first application start it will ask to install su Binary, say Yes.
Wait about 5 minutes or until it fails…
If so, don't worry, be happy.
Reboot…
Try again.
It must ask for Root Authorization!
Continue Rebooting and tying again and again, until you see su binary installed successfully!
Now you can dance, you Switched to SuperSU
After that you can remove all KingoRoot sh**t and install SuperSU like System app in application options…
I'm still experimenting with this rom, so I'm keeping KingRoot and SuperSU apps, for reroot my device if I will reflash KDZ.
Since now we have Working TWRP…
Simply flash it via recovery.
There are two ways available : System(by system partition) and Systemless (by Repacking and flashing Modified Kernel Image)…
Google it to know more ?
(1) Download this: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
(2) Place it in /sdcard/
(3) Reboot to TWRP.
(4) Select "Install" and go to the folder where you had placed the SuperSu zip and select the zip.
(5) Swipe to confirm flash.
(6) Reboot to system.
(7) Remove kingoroot's supersu.
D_Vovan_238 said:
Follow this ROM Installation Guide.
Root it with KingoRoot.
Flash patched aboot.img by typing "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7" command in Android Terminal Emulator App, I don't like to use PC.
Then download ChainFire SuperSU from GooglePlay.
On first application start it will ask to install su Binary, say Yes.
Wait about 5 minutes or until it fails…
If so, don't worry, be happy.
Reboot…
Try again.
It must ask for Root Authorization!
Continue Rebooting and tying again and again, until you see su binary installed successfully!
Now you can dance, you Switched to SuperSU
After that you can remove all KingoRoot sh**t and install SuperSU like System app in application options…
I'm still experimenting with this rom, so I'm keeping KingRoot and SuperSU apps, for reroot my device if I will reflash KDZ.
Since now we have Working TWRP…
Simply flash it via recovery.
There are two ways available : System(by system partition) and Systemless (by Repacking and flashing Modified Kernel Image)…
Google it to know more
Click to expand...
Click to collapse
I rebooted like +10 times and still nothing. Also it doesn't ask for root authorization after reboot
Krystiannnnnn said:
I rebooted like +10 times and still nothing. Also it doesn't ask for root authorization after reboot
Click to expand...
Click to collapse
Follow this:
(1) Download this: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
(2) Place it in /sdcard/
(3) Reboot to TWRP.
(4) Select "Install" and go to the folder where you had placed the SuperSu zip and select the zip.
(5) Swipe to confirm flash.
(6) Reboot to system.
(7) Remove kingoroot's supersu.
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
For Users who want to remain Encrypted:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Click to expand...
Click to collapse
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
.........
-Calling user ramdisk patch script
---Failure, aborting
-Unmounting /system and /vender
-Done
Click to expand...
Click to collapse
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
netsonic said:
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
Click to expand...
Click to collapse
Just use the latest universal codeworks recovery and flash it via fastboot.
For root i suggest use of Magisk over Su, the latest 15.3 works fine for me.
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
netsonic said:
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
Click to expand...
Click to collapse
No, it's the -universal- one from here https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
I can flash universal TWRP and Magisk 15.3. But Magisk show "SafetyNet API Error"? How to fix it?
Is there a way to update system to .14 and preserve TWRP?
I know that I can preserve Magisk, but I don't want to lose TWRP because I need to flash few more things.
Two more constraints:
I don't want to lose data
I don't have access to pc
In what steps I can achieve it, if any?
Yes, just go to TWRP with your OTA file, install the OTA file (in TWRP!), don't restart and install the ZIP file of the TWRP, reboot to recovery, flash magisk and reboot. Done. You'll still with your TWRP, rooted and updated.
MatheusPimentel said:
Yes, just go to TWRP with your OTA file, install the OTA file (in TWRP!), don't restart and install the ZIP file of the TWRP, reboot to recovery, flash magisk and reboot. Done. You'll still with your TWRP, rooted and updated.
Click to expand...
Click to collapse
Exactly. But make sure to only use the full OTA and not the incremental one.
Full guide
1. Go to TWRP
2. Flash FULL ROM
3. Flash TWRP INSTALLER (if u fail to u will lose TWRP)
4. Reboot your device. (yes boot it...and access your phone)
5. Reboot back to TWRP
6. Flash Magisk
Working method...tried nd tested 50+ times
The following also works. Follow it precisely.
> Install the update through the OS Update UI.
> Open Magisk Manager and find the module that preserves TWRP. Flash it. It won't appear in the module list. Don't restart yet, you'll lose Magisk if you do.
> Open Magist Manager and click "install". Install to inactive slot (OTA)
> Reboot!
Done this a few times now, it's actually more convenient than booting to TWRP.
I use always that way. The module is called TWRP_A_B_Retention_Script-Magisk.zip.
Open Magisk Manager > Downloads and it's called : TWRP A/B Retention Script.
To find it easy order by name. Default it's by last update.
https://forum.xda-developers.com/showpost.php?p=79358976&postcount=2012
Done.
Thank you all.
I tried to root my samsung s8 (SM-G950F) by flashing the super su zip file. i installed twrp and everything. and when i flashed the zip file it said that it was flashed successfully but when i went to check if my phone was rooted or not, it said "root isnt properly insyalled on this device." is there some extra step that i'm missing? Here was my method.
1: Download latest twrp file for my device.
2: Flash the twrp file using Odin.
3: Flash force-dm-verity from twrp because it wasnt flashing the usual way.
4. Boot up my device and download the supersu.zip
5. flash the supersu.zip from twrp.
6. it flashes successfully.
after flashing it still says that my device isn't rooted. is there a mistake that i made or is there an extra step.