Related
Hello there, I was trying to root my OnePlus 2 (Oxygen OS 3.0.2) using TWRP & SuperSU method.
After Successfully replacing stock recovery with the TWRP in my phone, I take a backup in of my whole system in TWRP.
After that I installed SuperSU.zip from TWRP, clear Dalvik Cache and reboot the phone. Phone was not starting. It was showing to boot animation for 15-20 min, I restarted my phone for 3-4 times but still the same thing. In technical term, after I install SuperSU from TWRP my device ran into BootLoop issue.
After I recover my backup, everything is fine, again I tried with a different version of SuperSU and encountered the same problem.
Tried SuperSU Version: 2.76 & 2.67
TWRP Version: 3.0.2-2
OS: Android Marhmallow
Oxigen OS: 3.0.2
Any help how can I root my phone successfully would be a great help! Thank you! :crying:
From recovery, open terminal with in recovery or connect over ADB, type the following command before flashing SuperSU:
echo SYSTEMLESS=true > /data/.supersu
The above command will create a file that tells SuperSU to use systemless approach and do the right thing
hackworks said:
From recovery, open terminal with in recovery or connect over ADB, type the following command before flashing SuperSU:
echo SYSTEMLESS=true > /data/.supersu
The above command will create a file that tells SuperSU to use systemless approach and do the right thing
Click to expand...
Click to collapse
Thanks Man. this Systemless command worked fine and get my device rooted. You're great! Thanks for your time.
hackworks said:
From recovery, open terminal with in recovery or connect over ADB, type the following command before flashing SuperSU:
echo SYSTEMLESS=true > /data/.supersu
The above command will create a file that tells SuperSU to use systemless approach and do the right thing
Click to expand...
Click to collapse
Thanks for the command:good:. Before the command, only supersu installer would run till placing files but now Boot image patcher is also running till
unmounting/system
-Done
Updating partition details...
-done
Then I wipe cache and get
Formatting Cache using make_ext4fs...
-done
I am using Huawei honor 6 H60-L01 with a rom provided by Chinese user, it came with supersu and kingroot installed but had no root access because of Marshmallow (they were using some exploit to root earlier versions). First time I ran the above process, preinstalled supersu disappeared and could not locate the supersu I just flashed, so I flashed supersu again but still can not find supersu app on my phone.
Thanks for your help.
my oneplus2 is also stucked on the boot animation after Rooting. I am unable to do anything the animation is going on and on. I am unable to enter in fastboot or recovery also. what should I do?
Maybe try flashing the su zip in systemless mode
faraz13 said:
my oneplus2 is also stucked on the boot animation after Rooting. I am unable to do anything the animation is going on and on. I am unable to enter in fastboot or recovery also. what should I do?
Click to expand...
Click to collapse
Long press the power button till phone shuts off (about 10 seconds) and enter recovery by power & volume down, once in recovery you go to advanced option, terminal and enter:
echo "SYSTEMLESS=true" > /data/.supersu
If correctly applied the shell would return no answer or anything, if you flash supersu now it's installed as forced systemless and your phone should boot normally, you can also search for a forced systemless supersu zip, as alternative.. Good luck
Sent from my OnePlus 2 using XDA Labs
Hi, I'm posting this as kind of another way to install Magisk onto your MIUI Stock ROM, This Method is a way to not flash MIUI again and not lose your data, I mainly found this method while messing around with some files and another guide, By the way, I cannot guarantee OTA not breaking, but OTA I think should be OK because Magisk Root is Systemless, and this method DOES NOT INSTALL TWRP, We will be merely be booting into TWRP to root.
The Installation will indeed fail if you have a pirating application SUCH AS Lucky Patcher, please remove those before you install Magisk or it will fail!
This will take multiple requirements:
1. Red Wolf TWRP - https://forum.xda-developers.com/redmi-note-4/xiaomi-redmi-note-4-snapdragon-roms-kernels-recoveries--other-development/recovery-red-wolf-recovery-project-t3653704
2. A PC
3. 15 Seconds ADB Installer (You can use any ADB/Fastboot utility you like) - https://forum.xda-developers.com/showthread.php?t=2588979
4. Magisk - You can use the latest version off of XDA's Magisk Forum
5. Unlocked Bootloader on your phone
After you've installed 15 Seconds ADB Installer onto your PC and Unlocked your bootloader, It is time to do your thing! Boot your phone into Fastboot mode with Power Button + Volume Down and connect it to your PC to USB, Open an administrator mode CMD in the ADB folder wherever you installed it, Plop your Red wolf image that you have downloaded into the ADB folder, and run:
Code:
fastboot devices
Code:
fastboot boot (whatever the .img file is called).img
and hit enter, after you've done that, You should see TWRP has booted onto your device, Now Swipe to allow modifications and this should put you into a Menu, after that, Connect your phone to your PC again, and the device and it's storage should be detected, Now pull the Magisk zip file and put it wherever you desire on your phone, Unplug the phone from the PC, Go to install, Select the Magisk zip file you put onto the phone and tap it, It should install, Tap wipe cache, then reboot to your system.
and tada! You should have the Magisk Manager! That's it! Your data and apps are still there, Modules install perfectly, and Safetynet passes for the people who are gonna be playing Pokemon Go for Pokemon Let's Go!
CREDIT:
Red Wolf TWRP Developers and/or related people - dadi11, ATG Droid, Devil7DK
15 Seconds ADB Developers and/or related people - Snoop05
If you have any issues with this post, I'm sorry about it, Please inform me!
UPDATE: I have tested OTA with an update that came yesterday, MIUI boots even after doing this method, but for every OTA update, you will need to reinstall Magisk.
Dear readers,
I've no idea what happened but after trying to root my phone with Supersu I got stuck into this bootloop.
So what happened?
I flashed TWRP on my phone.
Once in TWRP I tried to install Supersu but unfortunately I couldn't find the zip file.
I restarted my phone.
This time I downloaded Supersu and put it in a location I would be able to find.
Once again flashed TWRP.
Got into TWRP.
Had to decrypt by password which I was unable to do.
So now TWRP was unable to read my internal storage (0mb internal storage).
Reading the forums I ended up backingup my device.
Then used the formatting function in TWRP.
Restored back my backup.
Still couldn't find the Supersu file.
Rebooted to stystem.
Now whatever I do I can't get out of Fastboot Mode.
Tried adb command: Fastboot reboot
No results.
I believe that I somehow should get the stock ROM (?) on my phone?
Fixed it!
Used adb to push the Supersu download to my phone in recovery. After that everything worked!
Just today I found a way to reboot into safe mode on my Fire TV Stick 2 through a quick reboot application with a list of options of how I can boot my device into recovery, fastboot, or simply a reboot of my operating system.
Here's a link to an application called Quick Reboot Pro! Be sure to access root privileges before even rebooting into safe mode. Unfortunately I haven't found a way to tell my device through adb to reboot into safe mode.
Link (apk install on Fire TV device with Root): https://www.apkmirror.com/apk/antar...reboot-pro-root-1-5-1-1-android-apk-download/
Hi everyone
Already done:
"New" OnePlus 6t, bootloader unlocked (confirmed), successfully flashed via adb "fastboot boot twrp.img" (=temp TWRP), installed twrp.zip via twrp file explorer (persistent twrp), installed magisk.zip.
Then reboot into recovery, reboot system, android gui ok, reboot into bootloader (fastboot), wipe Dalvik/Cache, Data, System (accidentally).
Then:
adb sideload lineage-18.1-20220303-nightly-fajita-signed.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Again adb sideload lineage-18.1-20220303-nightly-fajita-signed.zip
Total xfer: 1.00x
When I try to boot android-gui I get the message that there is no system installed (obviously, because of wiped system and not successfully installed lineageos).
adb push /z/Downloads/Android/System/OnePlus-6T/ROM-Flash/lineage-18.1-20220303-nightly-fajita-signed.zip /storage/Download/lineage-18.1-20220303-nightly-fajita-signed.zip
(584355703 bytes in 15.260s)
TWRP > file explorer > install > lineage-18.1-20220303-nightly-fajita-signed.zip without success.
How can I fix this?
Try flashing the lineage recovery image via
fastboot flash boot lineage-18.1-20220303-recovery-fajita.img
After that, boot into your new recovery and go to the adb update option and I think you should be good from there.
If you wiped the system, I think you'll have to use msm tool to get oos installed again, unlock bootloader again, then flash lineage