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
Step :
Install driver adb
USB Debugging - ON
Root device
Install Rootexplorer-3.3.8.apk
Install Rebootmanager.apk
Take the file system/bin/install-recovery.sh from stock rom.zip
Customize with its version Flyme
Copy the file install-recovery.sh to sdcard (mmc internal)
Rename root/system/ recovery-from-boot.bak
Into root/system/recovery-from-boot.p
Seting permission recovery-from-boot.p into rw-r-r
Execution using adb
adb shell
sh /sdcard/install-recovery.sh
reboot recovery
Or execution with terminal emulator.apk
su
sh /sdcard/install-recovery.sh
reboot recovery
Finished :laugh:
Install Custom Recovery with fastboot, flashify, etc.
Bootloop solution after unlock the bootloader because the data can not be mounted:
Press and hold the key (vol+ & power) a bit longer to actually able to enter recovery mode (twrp/cwm/philztouch/etc)
Wipe factory reset
Flash stock rom.zip
Finished
* Thanks to Allah SWT.
zround said:
Step :
Install driver adb
Root device
Install Rebootmanager.apk
Customize with its version Flyme
Rename root/system/ recovery-from-boot.bak
Seting permission recovery-from-boot.p into rw-r-r
Or execution with terminal emulator.apk
su
sh /sdcard/install-recovery.sh
reboot recovery
Press and hold the key (vol+ & power) a bit longer to actually able to enter recovery mode (twrp/cwm/philztouch/etc)
Flash stock rom.zip
Finished
* Thanks to Allah SWT.
Click to expand...
Click to collapse
in terminal command it shows that recovery.sh not found
My mini M2 condition:
1. It's UBL
2. Custom recovery TWRP
3. Custom ROM Lineages 14.1
Problem: GAPPS error. Google play services keep stopped.
Steps you've tried:
1. install GAPPS with OpenGapps for Lineages 14.1
2. install using f-droid (Gapps replacement)
3. install Google installer.apk with ROM Flyme 6
the problem remains the same as above.
is it can solve my problem wanna get back to Flyme Os and also GAPPS problem?
or flashing use the firmware via flashtool?
I tried looking at the XDA Forum, and Google has not found it.
.
thank you
zround said:
Step :
Install driver adb
USB Debugging - ON
Root device
Install Rootexplorer-3.3.8.apk
Install Rebootmanager.apk
Take the file system/bin/install-recovery.sh from stock rom.zip
Customize with its version Flyme
Copy the file install-recovery.sh to sdcard (mmc internal)
Rename root/system/ recovery-from-boot.bak
Into root/system/recovery-from-boot.p
Seting permission recovery-from-boot.p into rw-r-r
Execution using adb
adb shell
sh /sdcard/install-recovery.sh
reboot recovery
Or execution with terminal emulator.apk
su
sh /sdcard/install-recovery.sh
reboot recovery
Finished :laugh:
Install Custom Recovery with fastboot, flashify, etc.
Bootloop solution after unlock the bootloader because the data can not be mounted:
Press and hold the key (vol+ & power) a bit longer to actually able to enter recovery mode (twrp/cwm/philztouch/etc)
Wipe factory reset
Flash stock rom.zip
Finished
* Thanks to Allah SWT.
Click to expand...
Click to collapse
By the way,you don't need to do all these. If you need to replace twrp to stock. Just flash flyme update.zip inside twrp or any recovery you have now. It may get replaced to stock automatically.
Guys, you can just flash the stock recovery using fastboot
This guide is primarily intended for rooted users, since stock users can just take the OTA.
Key points
User data and applications are kept intact
You do not have to remove your PIN, password, or fingerprint
You do not have to remove TWRP, Magisk, your custom kernel, dtbo, or anything
This is intended for monthly security updates; developer previews and beta releases may or may not work with this method. You're welcome to try, but all may not work as expected
Installing Update:
Make sure you have the latest Google SDK Platform Tools. Extract the archive to a location of your choosing (creates platform-tools folder)
Get the latest walleye Factory Image (not OTA) from Google's Developer Page and save to a location of your choosing
Extract the archive, and open the extracted folder. You should see a list of files:
bootloader-walleye-[version string].img
flash-all.bat
flash-all.sh
flash-base.sh
image-walleye-[version string].zip
radio-walleye-[version string].img
Open the flash-all script (flash-all.bat for Windows, flash-all.sh for Linux/OSX) in your favorite text editor.
Find the line that reads "fastboot -w update image-walleye-[version].zip and remove "-w" (the wipe user data switch). Save and close the flash-all script.
Move (cut and paste, etc) all of these files to the platform-tools folder.
Enable USB Debugging from the Developer Options menu on your device (press "Build Number" 7 times if not already visible)
With your device plugged into the computer, open a command prompt in the platform-tools folder
Windows: Open the folder, hold down Shift and right click inside the folder, "Open Command window here"
Linux: If you're on Linux you already know how to do this
OSX: Open a folder in a terminal
Reboot to bootloader:
Code:
adb reboot bootloader
Execute update script in terminal:
Windows:
Code:
flash-all.bat
Linux/OSX:
Code:
./flash-all.sh
The device will reboot a few times while updating
Restoring root and/or a custom recovery
Download latest:
TWRP image
Magisk zip
TWRP zip
(Optional) Custom kernel zip
Place all files in the platform-tools folder
Reboot to bootloader
Boot TWRP image.
Code:
fastboot boot [twrp image filename].img
Push zip files to /tmp
Code:
adb push [magisk filename].zip /tmp
Optional: TWRP persistent installation + custom kernel:
Code:
adb push [twrp filename].zip /tmp
adb push [custom kernel filename].zip /tmp
Install Magisk:
Code:
adb shell twrp install /tmp/[magisk filename].zip
Optional: TWRP persistent installation + custom kernel:
Code:
adb shell twrp install /tmp/[twrp filename].zip
adb shell twrp install /tmp/[custom kernel filename].zip
adb shell twrp install /tmp/[magisk filename].zip
Reboot to system
[ Reserved ]
[ Reserved Post ]
Thanks for the guide
Sent from my Pixel 2 using Tapatalk
Thanks for that, but do not forget to mention to enable usb debugging mode, to account for people who are new to this community.
I'm having trouble Installing Magisk on Step 6. Every time I enter the code it says it can't locate the Magisk file for some reason.
Pianobeats said:
I'm having trouble Installing Magisk on Step 6. Every time I enter the code it says it can't locate the Magisk file for some reason.
Click to expand...
Click to collapse
Oops, my instructions were to push to /tmp but the flashing portion left that directory out. I updated the original post.
atifaslam7 said:
Thanks for that, but do not forget to mention to enable usb debugging mode, to account for people who are new to this community.
Click to expand...
Click to collapse
My thought was that if someone is following this guide, they're already rooted, so would already know to have USB Debugging enabled. I'll add it though for completeness sake.
ehi guys! i have one last doubt before updating to the latest factory image: i have a verizon pixel 2, bootloader unlocked, magisk installed on OPM1.171019.013, will i be able to keep my bootloader unlocked after i flash the latest factory image? i definitely don't want to lock it as i read the unlock command is not working anymore..
thanks a lot!
Thanks for the guide. Worked flawlessly!
daede86 said:
ehi guys! i have one last doubt before updating to the latest factory image: i have a verizon pixel 2, bootloader unlocked, magisk installed on OPM1.171019.013, will i be able to keep my bootloader unlocked after i flash the latest factory image? i definitely don't want to lock it as i read the unlock command is not working anymore..
thanks a lot!
Click to expand...
Click to collapse
Relocking your bootloader is not necessary to flash this. Bootloader will remain unlocked after flashing.
Telperion said:
Note: As of the February security update, TWRP 3.2.1-0 cannot decrypt the /data/ partition. When prompted for your PIN, cancel. You can keep /system/ read-only.
Click to expand...
Click to collapse
TWRP 3.2.1-1 and 3.2.1-2 are able to decrypt /data and /sdcard. MTP still doesn't work, but you can place files on the sdcard via USB in system.
socal87 said:
TWRP 3.2.1-1 and 3.2.1-2 are able to decrypt /data and /sdcard. MTP still doesn't work, but you can place files on the sdcard via USB in system.
Click to expand...
Click to collapse
This is hit and miss, for example 3.2.1-2 won't decrypt /data/ for me on P DP1. Others though have no problem decrypting data.
I kept the instructions the same, but took out the decryption note. Even if your TWRP can decrypt /data/ it's not strictly necessary for this process, so there's consistency in the guide in spite of inconsistent TWRP behavior.
Telperion said:
This is hit and miss, for example 3.2.1-2 won't decrypt /data/ for me on P DP1. Others though have no problem decrypting data.
I kept the instructions the same, but took out the decryption note. Even if your TWRP can decrypt /data/ it's not strictly necessary for this process, so there's consistency in the guide in spite of inconsistent TWRP behavior.
Click to expand...
Click to collapse
This honestly doesn't surprise me in the least; I would expect that Android P might use a different security scheme, so the decryption mechanism that works with Oreo may not be forward compatible.
For persistent twrp don’t you need to fastboot flash the recovery partition with the twrp image?
floepie said:
For persistent twrp don’t you need to fastboot flash the recovery partition with the twrp image?
Click to expand...
Click to collapse
There is no recovery partition, the recovery is now part of the boot image. You have to boot the TWRP image, then flash the TWRP zip which will patch the boot image in both slots.
Right I meant the boot partition. But this contradicts the main guide here where it indicates the necessity to flash both the twrp image to the boot partition (not just boot to the image on your PC), AND flash the twrp zip to make it persistent.
You don’t need to worry about the twrp zip at all if all you want to do is fastboot boot the twrp image.
floepie said:
Right I meant the boot partition. But this contradicts the main guide here where it indicates the necessity to flash both the twrp image to the boot partition (not just boot to the image on your PC), AND flash the twrp zip to make it persistent.
Click to expand...
Click to collapse
Not sure which guide you're referring to, but nathanchance's guide as far as I saw lined up with mine.
Sorry delete
Has there been a workaround created for those of us who can't unlock bootloader because OEM can't be unlocked? Wiping the phone and skipping wizard did not work for me. I'm just trying to root so I can delete apps I don't want.
Can someone tell me about the installing OTA.zip without unrooting or uninstalling the magisk. Is it possible to update through OTA on rooted stock ROM? Or what if we update using the OTA which comes automatically from Google?
Sent from my Pixel 2 using Tapatalk
nickporwal said:
Can someone tell me about the installing OTA.zip without unrooting or uninstalling the magisk. Is it possible to update through OTA on rooted stock ROM? Or what if we update using the OTA which comes automatically from Google?
Click to expand...
Click to collapse
That's not possible, which is why this process exists.
Flashing for Dummies
In this guide we'll go over how to flash custom ROMs with root and TWRP in addition to updating
this guide will always be updated
Read the ENTIRE guide before you start
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
things to keep in mind:
1- when you flash a ROM through TWRP, it will flash to your inactive slot, that's why you need to switch slot after flashing it and then flash everything else, think of it like an OTA update except you need to switch active slot yourself
2- when you change your active slot in TWRP, it will only change after you reboot, your active slot will always be the one you're currently booted on
3- the order of flashing anything that modifies boot is
1) TWRP
2) custom kernel
3) noverity
4)Magisk
if you're not sure, flash stock boot of your rom and do it again, flashing TWRP will break Magisk, flashing a custom kernel will break magisk, flashing TWRP after flashing a custom kernel will most likely get you a bootloop
Before you begin
you need to unlock your bootloader first https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
It is no longer required to be on stock Oreo before flashing, but I currently still recommend you do so as there might be some minor bugs on some custom roms, but otherwise everything will work just fine.
get latest platform-tools if you haven't already, using an older one WILL result in errors
platform-tools
extract it and open the folder
hold shift then right click on an empty space then click "open command window here"
if you're on windows 10, doing that will open power shell instead, inside power shell, type "cmd" and press enter, use cmd for everything below
if you're coming from stock, you need to do this first
type the following command (data and files will be wiped)
Code:
fastboot -w
fastboot set_active b
Notes:
Pixel Experience includes Gapps, do not flash them after the rom
many roms include TWRP, such as Havoc, AICP and many others, check ROM thread first, if it includes it then don't flash TWRP.
Flashing custom ROMs and other stuff
download latest TWRP img and zip from https://twrp.me/xiaomi/xiaomimia2.html and place it in the same folder you extracted platform-tools to
NOTE: if you are on stock then use TWRP 3.2.3 img, not 3.3
note: if you're having issues with official TWRP, I've built an unofficial one with F2FS support which you can try here
be careful if you switch to F2FS, it will only work with a recovery that supports it and a ROM that supports it, no stock.
rename the img to twrp.img
in cmd, type
Code:
fastboot boot twrp.img
if you get a bootloop, force shutdown (power + volume down) and try again
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
after you got the files on your phone, it's time to flash
remember that when flashing a ROM, it will flash to your inactive slot, in this guide I'll assume your active slot is B, use "fastboot set_active b" in fastboot if you'd like to follow along
First go to wipe > advanced and select System and Data then wipe, then you can start flashing
1- flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC (ONLY if the ROM doesn't include it already)
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
5- flash Gapps if required by the ROM you're flashing, Opengapps nano is recommended, you can get it here http://Opengapps.org
6- (optional) flash a custom kernel if desired/needed
7- (optional) flash DM-VERITY & FORCEENCRYPT DISABLER zip , this will disable DM verity and encryption in vendor, this is not required by most custom ROMs as they will disable encryption anyway, it is most useful on stock, and in the possibility that the ROM you're flashing does not disable encryption
8- flash Magisk
9- reboot to system
IMPORTANT, if you get an error while flashing ROM zip, do the following
use latest official TWRP, if you're already using it, then the ROM you're flashing is one of the older ROMs
previously, ROMs and TWRP used Jasmine as a codename for our device, while the real codename is Jasmine_sprout, this caused some issues, newer ROMs and TWRP now use the correct codename, but that means new TWRP can not flash older ROMs, and so you will need some simple modifications to the ROM zip:
1- open the ZIP using WinRAR on PC or X-plore on phone
2- go to META-INF/com/android/metadata and open it as text
3- on the last line, edit 'pre-device=jasmine' to 'pre-device=jasmine_sprout'
4- save it and try flashing again
Switching between custom ROMs
follow the same flashing instructions, you can boot directly to TWRP by holding power + volume up, wipe data and system first then flash ROM and the rest.
Updating Custom ROMs
For OFFICIAL ROMs which support A/B OTA it's very easy
1- once you get a notification that an update is available, download and install with the system updater but don't reboot (If the ROM includes TWRP then don't do any of the following steps, just reboot)
2- go to Magisk, Downloads, search for "TWRP A/B Retention Script" and install it
3- on the main Magisk page, click install > install > Install to Inactive Slot (After OTA)
4- once Magisk finishes, reboot, you will now be on the opposite slot with both Magisk and TWRP installed.
for Unofficial ROMs with no OTA or Official ROMs that don't support A/B OTA, you'll need to use TWRP, do not wipe anything:
1- boot to TWRP
2- flash the ROM zip
3- flash TWRP zip (ONLY IF the ROM doesn't include TWRP)
4- switch your active slot (to A if you are on B and to B if you were on A)
5- reboot recovery
6- flash Gapps if required by the ROM you're flashing, Opengapps nano is recommended, you can get it here http://Opengapps.org
7- (optional) flash a custom kernel if desired/needed
8- (optional) flash DM-VERITY & FORCEENCRYPT DISABLER zip , this will disable DM verity and encryption in vendor, this is not required by most custom ROMs as they will disable encryption anyway, it is most useful on stock, and in the possibility that the ROM you're flashing does not disable encryption
9- flash Magisk
10- reboot to system
Very good and very well detailed guide. This guide will be useful to those who are not so familiar with Flashing ROMs especially in our device with partitions.
Thank you for making this, as many users were asking this thing. Keep it up!
does rebooting to twrp gets stuck on twrp logo after flashing twrp zip?
its been an issue on stock or maybe i have been doing to wrong...
after wipe commands and setting active slot b,
i reboot into fastboot boot twrp.img and flash the rom and Im getting mount failed /system
is that normal?
Edit: NVM, it is normal. I successfully flashed Carbon ROM in my device. Thanks for this awesome guide.
This is great thank you. Going to try it once I get bored of stock rom.
@AxL said:
after wipe commands and setting active slot b,
i reboot into fastboot boot twrp.img and flash the rom and Im getting mount failed /system
is that normal?
Edit: NVM, it is normal. I successfully flashed Carbon ROM in my device. Thanks for this awesome guide.
Click to expand...
Click to collapse
Yes it's normal because you wiped system
levai_spencer said:
does rebooting to twrp gets stuck on twrp logo after flashing twrp zip?
its been an issue on stock or maybe i have been doing to wrong...
Click to expand...
Click to collapse
twrp.zip has a bootloop for TWRP when it is flash
Candy_Pineapple said:
twrp.zip has a bootloop for TWRP when it is flash
Click to expand...
Click to collapse
No, if you follow the instructions it works
coming from stock to pE I followed exacty the steps.
then flash CR. Here what Ive done
i-wipe cache,data,system for both partition using twrp
ii- set partition to B in twrp and flash zip
iii- set partition to A in twrp and reboot into bootloop
iv- set partition to B in twrp and reboot successfully
so what partition is my CR now?
which partition should i install gapps,kernel and magisk?
Thanks.
notJimz said:
coming from stock to pE I followed exacty the steps.
then flash CR. Here what Ive done
i-wipe cache,data,system for both partition using twrp
ii- set partition to B in twrp and flash zip
iii- set partition to A in twrp and reboot into bootloop
iv- set partition to B in twrp and reboot successfully
so what partition is my CR now?
which partition should i install gapps,kernel and magisk?
Thanks.
Click to expand...
Click to collapse
It's in B, because you didn't reboot after switching slot initially in twrp, stay in B and boot recovery then flash Gapps and the rest
Nebrassy said:
It's in B, because you didn't reboot after switching slot initially in twrp, stay in B and boot recovery then flash Gapps and the rest
Click to expand...
Click to collapse
You are right. I miss the first bl reboot.
I follow the step back and reboot after switch partition.
Only now i got the concept for A/B flashing. And my os in A now.
Thanks for the guide. Really helpful.
notJimz said:
You are right. I miss the first bl reboot.
I follow the step back and reboot after switch partition.
Only now i got the concept for A/B flashing. And my os in A now.
Thanks for the guide. Really helpful.
Click to expand...
Click to collapse
No prob, keep connected and click the tx button
Matteo (AIO Project Founder)
Hello,
after make adb push file.zip /data/media/0
I receive the next message
adb: error: failed to get feature set: no devices/emulators found
Please advice.
Thanks
Roviva said:
Hello,
after make adb push file.zip /data/media/0
I receive the next message
adb: error: failed to get feature set: no devices/emulators found
Please advice.
Thanks
Click to expand...
Click to collapse
What's the output of adb devices?
Nebrassy said:
What's the output of adb devices?
Click to expand...
Click to collapse
I entered in fastboot mode,:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>.\adb devices
List of devices attached
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>
If I enter the command "adb devices" in normal mode (no fastboot) appear:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
a341410 device
Roviva said:
I entered in fastboot mode,:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>.\adb devices
List of devices attached
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>
Click to expand...
Click to collapse
Adb devices
While in twrp, adb won't work while in fastboot, follow the guide carefully
Nebrassy said:
Adb devices
While in twrp, adb won't work while in fastboot, follow the guide carefully
Click to expand...
Click to collapse
Hello,
In your guide I dont understand the next part:
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
If I made the step 1 above: I enter in the TWRP, select wipe, then, select wipe, advance wipe, select data and then swipe to wipe. After this reboot system, the telephone start but in normal mode, like restored.
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
I follow the step 2, in data/media appear a folder TWRP then i dont created a folder called 0
Then I go to advanced >> adb sideload and in the pc i wrote "adb sideload twrp.zip.
You write file.zip, I dont understand what is this file?
I dont understand what do you mean in the step 3: "try using PBRP for MTP, then go back to TWRP PBRP"
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
Roviva said:
Hello,
In your guide I dont understand the next part:
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
I follow the step 2, in data/media appear a folder TWRP then i dont created a folder called 0
Then I go to advanced >> adb sideload and in the pc i wrote "adb sideload twrp.zip.
You write file.zip, I dont understand what is this file?
I dont understand what do you mean in the step 3: "try using PBRP for MTP, then go back to TWRP PBRP"
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
Click to expand...
Click to collapse
File.zip, as in the file you want to copy, you change that to the name of the file you want to copy
PBRP is another recovery, you can try booting it if twrp doesn't work to copy
Nebrassy said:
File.zip, as in the file you want to copy, you change that to the name of the file you want to copy
PBRP is another recovery, you can try booting it if twrp doesn't work to copy
Click to expand...
Click to collapse
hello,
I dont know how to follow:
flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
I wiped data and storage then I press back.
I flashed the PBRP that I pushed to data/media/TWRP
After flash I returned to the menu of PBRP
I switched to A
When I reboot, a warning message that "NO OS SYSTEM IS INSTALLED" appear.
I reboot to recovery but after this, the telephone does not restart. the screen "androidone" appear and dont advance...
How can I install the PBRP and magisk?
I succesfull push the files to the telephone but when flash the PBRP I cannot follow......
Roviva said:
hello,
I dont know how to follow:
flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
I wiped data and storage then I press back.
I flashed the PBRP that I pushed to data/media/TWRP
After flash I returned to the menu of PBRP
I switched to A
When I reboot, a warning message that "NO OS SYSTEM IS INSTALLED" appear.
I reboot to recovery but after this, the telephone does not restart. the screen "androidone" appear and dont advance...
How can I install the PBRP and magisk?
I succesfull push the files to the telephone but when flash the PBRP I cannot follow......
Click to expand...
Click to collapse
You didn't flash a rom, obviously it won't boot
tested and working
DP1 no wipe, run TWRP skip password if it asks, push latest magisk canary build to /mnt and flash
you will have root though i cant seem to update magisk.apk or zip through the app cheers guys
EDIT
Just uninstalled magisk that flashed with canary build from telegram chat and downloaded lastest apk from github canary. and working fine!!!
attached is an updated installer should work fine!!
Anyone?
ne0ns4l4m4nder said:
Anyone?
Click to expand...
Click to collapse
Yep can confirm that the latest canary build is working great. John Wu pulls through again in record time.
And just an extra disclaimer for the sake of clarity this is only working on the previous gen Pixels. The 3/3 XL are still a work in progress for the time being.
couldnt install says invalid zip format
mysara saad said:
couldnt install says invalid zip format
Click to expand...
Click to collapse
Yeah that zip has an extra folder inside of it for some reason. Just use the one from the magisk canary thread.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
I had to remove lock screen security first too since TWRP wasn't decrypting properly with it on. GL
You don't need to decrypt, just skip and push the magisk.zip to /mnt and install
Here's how I got to rooted q from the latest rooted stock p without wiping my internal memory. Please note that I do not have any passwords or patterns on my phone, so this works if you do not have encryption. Just make sure you back your phone up to your computer first just in case something goes wrong :
0. With your phone hooked to the computer, boot into bootloader and type "fastboot devices" to make sure your phone shows up. This is optional and just something I do to make sure everything is working as it should.
1. Download the factory image from here: https://developer.android.com/preview/download.html
2. Download and install the canary magisk manager from here: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337. Go to settings and change the update channel to canary. There will now be a new update, tap install but select "download only".
3. Unzip the factory image.
4. Open the "flash-all.bat" file in a text editor and remove the -w flag after the fastboot command near the bottom of the file.
5. Obtain the STOCK boot.img and dtbo.img of the system rom you are CURRENTLY running.
6. Type "adb devices" with your phone hooked up to the computer to make sure that you have a good connection and your phone has debugging on and authorized.
7. Reboot into TWRP and wipe Dalvik/ART cache, System, and Data.
8. Reboot into bootloader.
9. Take a command prompt to where your current stock boot.img and dtbo.img files are.
10. Command: fastboot flash boot {name_of_your_stock_boot.img}
11. Command: fastboot flash dtbo {name_of_your_stock_dtbo.img}
12. Now take your command prompt to where your unzipped q rom is.
13. Command: flash-all
14. When it's finished, your phone will reboot.
15. Download the latest twrp img and zip here: https://dl.twrp.me/taimen/
16. Once your phone is rebooted, go into settings and enable usb debugging.
17. Open a command prompt where you downloaded the twrp image.
17. Command: adb reboot bootloader
18. Command: fastboot boot {name_of_twrp_image_you_downloaded.img}
19. Flash the TWRP zip and the canary magisk zip you downloaded earlier and reboot.
19. uneseesery steps that dont work...
hanschke said:
19. uneseesery steps that dont work...
Click to expand...
Click to collapse
That is exactly what I did to get on rooted q from rooted p, without losing anything on my internal storage, and it does work. If you can tell me any "uneseesery" steps here I'm all ears.
hanschke said:
19. uneseesery steps that dont work...
Click to expand...
Click to collapse
I don't think so..I rooted through that step only..