Hello, i want to root my device with SuperSU but i can't.
Now there is:
bootloader: unlocked
fastboot: working
recovery: TWRP 3.3.1-0
rom: stock B12
I try to root through axon7toolkit, device boot to fastboot, then app shows:
HTML:
Checking ADB\Fastboot Connectivity...
ADB device connected!
Rebooting to bootloader...
Checking Fastboot Connectivity...
Fastboot device connected!
Booting TWRP...
downloading 'boot.img'...
OKAY [ 0.326s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.348s
Tap 'Keep read-only'" on startup!
then app shows error "ADB recovery device is not connected". I manually select Recovery mode from fastboot. TWRP launch without "Keep read-only" option. I click mount, selecting all options and checking "Keep read-only" option. Then I click OK in axon7toolkit error message and TWRP make a script. After that device boot twice. SuperSU app says SU is not installed.
I try to click OK in axon7toolkit error without mounting with "Keep read-only" (just clicking OK when TWRP launch) but it's the same.
I try to root by install SuperSU v2.82 SR5 through TWRP, script working and says done, but after confirm there is the same as above.
I must flash special bootstack or maybe B12 is possibile to root?
EDIT:
I try to download terminal, then type
HTML:
adb shell reboot disemmcwp
then device was rebooting. After that I type in emulator
HTML:
su
and SuperSU asks for root permission. I allow that, but terminal no go to root mode and typing
HTML:
reboot disemmcwp
don't change anything.
ColorfulPoland said:
Hello, i want to root my device with SuperSU but i can't.
Now there is:
bootloader: unlocked
fastboot: working
recovery: TWRP 3.3.1-0
rom: stock B12
I try to root through axon7toolkit, device boot to fastboot, then app shows:
Checking ADB\Fastboot Connectivity...ADB device connected!Rebooting to bootloader...Checking Fastboot Connectivity...Fastboot device connected!Booting TWRP...downloading 'boot.img'...OKAY [ 0.326s]booting...FAILED (remote: unknown command)finished. total time: 0.348sTap 'Keep read-only'" on startup!
then app shows error "ADB recovery device is not connected". I manually select Recovery mode from fastboot. TWRP launch without "Keep read-only" option. I click mount, selecting all options and checking "Keep read-only" option. Then I click OK in axon7toolkit error message and TWRP make a script. After that device boot twice. SuperSU app says SU is not installed.
I try to click OK in axon7toolkit error without mounting with "Keep read-only" (just clicking OK when TWRP launch) but it's the same.
I try to root by install SuperSU v2.82 SR5 through TWRP, script working and says done, but after confirm there is the same as above.
I must flash special bootstack or maybe B12 is possibile to root?
EDIT:
I try to download terminal, then type adb shell reboot disemmcwp
then device was rebooting. After that I type in emulator su
and SuperSU asks for root permission. I allow that, but terminal no go to root mode and typing reboot disemmcwp
don't change anything.
Click to expand...
Click to collapse
i always just ask, why SuperSU?
Don't use "Keep read only" on TWRP, that's useful when you have DM-verity enabled but SuperSU, Magisk, or the no verity zip disable that. I don't know if this is your problem but it might as well be.
Also, issue "reboot disemmcwp" from the TWRP terminal or via adb in TWRP. it might do the trick
When I type the post, I use SuperSU because Magisk no work. Now I know Magisk works to 16.7 but now the problem is because I have a problem with "corrupted SD card" after flashing (I have read and many other people have this problem). I don't know how to fix it, because formating don't help, so I still be with SuperSU
When I go home I try use terminal from TWRP, thank for your help
EDIT:
TWRP not recognize my commends
ColorfulPoland said:
When I type the post, I use SuperSU because Magisk no work. Now I know Magisk works to 16.7 but now the problem is because I have a problem with "corrupted SD card" after flashing (I have read and many other people have this problem). I don't know how to fix it, because formating don't help, so I still be with SuperSU
When I go home I try use terminal from TWRP, thank for your help
EDIT:
TWRP not recognize my commends
Click to expand...
Click to collapse
lol. Try using Magisk, then get all of your stuff out of the SD card and format it. If your files aren't bigger than 4gb you can use fat32, otherwise try formatting it from the phone
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
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
xNotta said:
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
Click to expand...
Click to collapse
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
jacksummers said:
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
Click to expand...
Click to collapse
If I sideload the Ota, do I need to flash the stock boot first?
xNotta said:
If I sideload the Ota, do I need to flash the stock boot first?
Click to expand...
Click to collapse
Nope. After the flash and reboot, u gotta re root though
jacksummers said:
Nope. After the flash and reboot, u gotta re root though
Click to expand...
Click to collapse
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
xNotta said:
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
Click to expand...
Click to collapse
I got the same error, but haven't had any issues.
I have been using this thread as my reference for how to take updates so I wanted to add some instructions and links that I found useful/necessary for completing the process.
Hopefully someone else can find this useful.
IMPORTANT! Remove screen lock pin before continuing!
TWRP will prompt for a password if you do not remove your lockscreen pin/pattern! There is no password!
This is caused due to Android encrypting the /data/ partition.
Settings > Security & Location > Device Security section > Screen Lock. Set it to None.
You can also search in settings for "Screen Lock"
Stock boot images:
https://drive.google.com/drive/folders/1iayS6YHYZvqkD1Y8oYV3ewzW5aAPe8C2
TWRP (twrp-mata_11.img) images:
https://download.invisiblek.org/mata/
Essential Phone downloads:
Download the OTA file for Sideloading
https://www.essential.com/developer/current-builds
Sideloading using stock recovery(my preferred method):
Ensure USB debugging is enabled on your Essential Phone. To do so, follow step four above.
Plug your Essential Phone into your computer with a USB cable.
Open a command window in the folder where you have ADB and fastboot installed.
In your command window, type adb devices and press enter. Your device’s serial number should appear in the command window.
If you see a notice on your phone asking if you’d like to allow USB debugging on this computer, check the box and select OK.
Reboot your phone into recovery mode. To do so, type adb reboot recovery into your command window. Your phone will reboot into recovery mode. You should see a little green bugdroid with a caution symbol. Despite your gut reaction, this is good.
Open the recovery menu on your Essential Phone. To do so, hold the power button and press the volume-up button once.
Scroll down to Apply update from ADB with your volume-down button, then press the power button to confirm.
Ensure that your phone is still being recognized by your computer. To do so, type adb devices in your command window and press enter. Your device’s serial number should appear in the window.
In your command window, type adb sideload update.zip (or whatever you named your file).
Source: https://www.androidauthority.com/how-to-install-android-p-essential-phone-863668/
Sideloading using TWRP:
Reboot your Essential Phone into Fastboot mode by restarting the phone and pressing and holding volume down and the power button at the same time. Once you’re in Fastboot mode, flash TWRP with the following ADB command: fastboot flash boot twrp.img
From within the Fastboot menu, select and boot into “recovery mode.” Once TWRP has booted up, type in: adb shell twrp sideload
Then type in: adb sideload magisk.zip
Once Magisk finishes installing completely, reboot back to Fastboot. You can do this via: adb reboot-bootloader
When you’re back in Fastboot mode, grab the modified boot.img (making sure to select the right one) and flash it via fastboot flash boot boot.img
Now reboot! You should now have root via Magisk!
Source: https://www.xda-developers.com/how-to-root-essential-phone-ph-1/
Running on a stock Pie with latest security update, I want to root my phone in order to utilize some Magisk modules, but I'm really concerned about all the "System has been destroyed" TWRP issues, it messed up my phone twice in the past.
I was wondering, could I flash Magisk just by temporarily fastbooting TWRP from the computer? Will that provide me a root access and prevent any future soft-bricking caused by the A/B partition issues?
Thanks in advance.
You can install magisk manager and patch boot image (kernel) as file from that. Than you fastboot that kernel and get temporary magisk root. After that, install permanent root from magisk manager and reboot. You dont need twrp for that.
Thank you for a suggestion, but that doesn't answer my question.
If the root is what you want, this is the best way to install magisk imho.
Hello,yes,you can temporary boot TWRP.
1.Make sure to have your bootloader unlocked
2.Make sure to have platform-tools on your PC
3.Download the latest .img file from TWRP Official Site and copy it in the platform-tools folder
4.Put your phone in Fastboot Mode(Volume Down+Power)
5.On your PC,in the platform-tools folder,hold Left Shift and press Right Click;it should appear an option namedpen a Powershell window here
6.Click on that
7.Write "fastboot devices" or ".\fastboot devices"
8. If your device appears there,you can write:fastboot boot "name of the file".img
9.It should boot in TWRP;if it asks you to swipe to allow modifications,don't do it,instead,press on Keep Read Only
From this point,you can install whatever you want.
I'm trying to root my OnePlus 6T, and i've got to the point of trying to fastboot with the twrp img file. when i type ./fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img into powershell, while the device is the unlocked bootloader, the device disconnects from my pc and just sits on the "Fastboot Mode" screen with the OnePlus logo. if i try to enter ./adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip, powershell gives me the following error message: "adb: sideload connection failed: no devices/emulators found". i've tried all sorts of different combinations but nothing works. i even added the zip file to my devices root folder to try and manually update it, but the file doesn't show in the update screen, only saying "please add the update file to the root folder". what does the "Advance, ADB sideload" part of this article mean: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ this is what i've been following, but i have clearly done something wrong, but i can't tell what that is.
Hmm... Now I have never used blu_spark but as you said your using the version for the 6 on a 6t is it compatible.. have you tried https://forum.xda-developers.com/on...ficial-twrp-touch-recovery-t3861482?nocache=1
@ikako
I use the themed TWRP from here https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752
But I suggest booting twrp using fastboot from your pc then flashing the twrp installer zip and magisk. That's how I've always installed recovery on my 6t and never an issue.
I did see an xda thread a few days ago specifically for installing Blu Spark TWRP. Let me see if I can find a link real quick ..brb
Hallo,
I installed lineage-19.1-20230606-UNOFFICIAL-dreamlte on my SM-G950F and the NikGapps-basic-arm64-11-20210501-signed with TRWP.
The installation was successfull.
Then I tried to install no-verity-opt-encrypt-6.1.zip and Magisk with TWRP. It does end with error1.
Tried several ways to repair, but everything had failed.
Then I tried to root with that guidance:
https://www.rootmeguide.com/samsung-galaxy-s8-plus-rooting-guide-magisk/
Installed the magisk.apk
Installed Minimal+adb+fastboot+v1.4.3-stup on my PC.
I took the boot.img from the linage file.
Step 3: Flash Magisk patched boot image.
On the command line window, type the below command and hit Enter.
fastboot devices -> show no devices
Enter “adb devices”
List of devices attached -> ce12171c7a2eab4005 device
Enter “adb reboot bootloader”
Shows “Downloading … Do not turn off target
Enter “fastboot flash boot boot.img”
<waiting for any device> Nothing happened.
Can someone help?
If you flashed a custom ROM, then your device is already patched and rooted, at least in TWRP.
So you only need to download latest magisk.apk, rename it to magisk.zip and install it with TWRP.
Then reboot to system and wait 3 minutes. If you can't open the magisk app, then again rename to magisk.apk and install it. After that, just follow the instructions from the magisk app.
Custom rom install SPD Upgrade Tool ....checked better...working any zip refresh file ...if install together root acces etc...logic ? if the custom rom isnt rooted etc...+ almost present devices no sd update = no need twrp refresh because its working from the stock service menu etc...nowhere device specific refresh file etc..
PS: your problem : custom rom isnt rooted and not working twrp root ..