Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality
Clarification
Should I have to flash DRM Fix every time I flash TWRP?
andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?
panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!
To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:
epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions
Related
When I saw that I could upgrade to Lollipop I was interested. Then I realized there probably was no root for this yet. So I went about figuring out a way to root it before going to it. Technically this isn't a root once you have already gone to Lollipop.
THIS WILL ONLY WORK IF YOU ARE STILL ON KITKAT, ROOTED, WITH RECOVERY (TWRP is what I use via NUT's Dual Recovery for the Z1).
Requirements:
PRFCreator - Creates pre-rooted firmware - Click Here to Download
Flashtool - Allows you to flash the FTF - Click Here to Download
The FTF for the upgrade - C6916_14.5.B.0.236_T-mobile_US.ftf - Click Here
The latest SuperSU zip from ChainFire - Click here to Download
I'm assuming you have adb, drivers installed and a general understanding of how to navigate the tools above, if not read up on how they work.
Create a pre-rooted flashable firmware with PRFCreator. Install/Download PRFCreator and put the FTF and the latest SuperSU binary zip in the spot labeled SuperSU Zip. Make sure to check the box next to kernel in the include box on the top right side. See screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Congrats you have just created a flashable zip with SuperSU loaded into it. You might ask why you're not gonna add NUT's XZDualRecovery into there. Reading on the forms at the time of this post and it apppears that PRFCreator and/or Nut's recovery doesn't play well with Lollipop and causes bootloops. So run NUT's Z1xzdualrecorvery installer via bat or sh after the fact and not during via PRFCreator until they can work it out.
Make sure you have the original C6916_14.5.B.0.236_T-mobile_US.ftf in the firmwares folder either C:\Flashtool\Firmwares or C:\User\[username]\.flashtool\firmwares
Now take the flashable zip you created via PRFCreator and put it on your phones internal storage, sdcard etc.
Now that you have the flashable zip with SU preinstalled and ready to fire, reboot your phone into recovery. adb reboot recovery etc.
Once your phone has rebooted into recovery you will need to flash the flashable zip you created with PRFCreator.
After flashing the zip I'd suggest wiping the cache/dalvik. And then you will want to go to the reboot screen and power off the device.
Once the device is powered off open Flashtool.
After it loads and syncs the devices (takes a second) you'll want to double click C9XX from the list (Z1).
Next click the BOLT icon in the top left navigation that has a tooltip that says "Flash"
When the flash screen comes up select the right firmware based on the FTF location, check SYSTEM and BASEBAND under the exclude section and uncheck DATA under the wipe section, I unchecked APPSLOG but you don't have to uncheck it (to be honest I think it slowed my initial bootup by upgrading my apps) via this screenshot:
Now click the "Flash" button with your device disconnected and powered off. Follow the directions. For your Z1s you'll want to hold the "DOWN VOLUME" button and then plug the USB connector into it.
Next you will see Flashtool flashing away. Once it's complete you can unplug your phone and then power it up.
Your device is now rooted and running Lollipop. In terms of installing a custom recovery, again all of that is untested and you'll need to play around with the latest XZdualrecovery from NUT to see how it works.
REMINDER: This doesn't solve killing ric etc. Which is important to note for being able to mount the system etc. You can kill ric via tasker and an .sh script like I do or via a flashable kill ric (seen a few floating around) if you get recovery installed after the fact etc.
Thanks to:
Chainfire for his SUPERSU
zxz0O0 for his PRFCreator tool
Androxyde for keeping flashtool going
greatremix for posting up the FTF
I'll be uploading the flashable zip that I made from PRFCreator. It's over a gb obviously so it might be just as easy for you all to create it yourself.
Reserved
To solve most issues with not being able to write to the system which most root apps need. Install NUT's latest xzdualrecovery which can be found at this address under xzdualrecovery. I installed 2.8.15 via the installer (not the flashable)
http://nut.xperia-files.com/
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Lavievn said:
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Click to expand...
Click to collapse
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Yazuken1 said:
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Click to expand...
Click to collapse
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
joedeveloper said:
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
Click to expand...
Click to collapse
i'm stuck now, do you have a C6902 stock kernel, or any way to change phone infomation by flashtool ?
it's show that my phone is C6902 in flash tool now, so i can't flash any rom or back to stock now
@joedeveloper I'm currently on 4.4.4, rooted with baseband .59, but noticed by your directions with "prfcreator" that you do not have us "check" modem when building the flashable zip. Would it hurt to include the modem so as to get the updated baseband to .69?
Also being deodexed, will that cause issues?
Thanks for the help
Not to distract from joedevelopers hard work, but I think its important for me to inform you guys that if you have already upgraded to lollipop through sony pc companion, or ota, King root does in fact work just fine. It will give a screen saying that it could not find that xperia z1s is rootable, but it will also give an option to try to root anyway. After pressing it, it will tell you the device was sucessfully rooted. And if you check with root verifier it will let you know root was successful. So you're still good if you upgraded to lollipop.
@joedeveloper Settings>About Phone reports baseband .69 after update, so that answers that.
I went back to tft .37 and did a fresh install so I have no information if one with a deodexed phone will be effected.
Many thanks to this update method.
SOLVED
Anyone get xposed to work after this update?
Can you clarify the ric thing?
So far so good, got recovery installed, now im going to try to install the audio mod, cause i desperately need that lol
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
throonis said:
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
Click to expand...
Click to collapse
This is what I'm referring to as the issue with sony ric being enabled. It's sony's way of preventing you from writing to the system, and most root apps need this. If you were to run:
adb shell
then
su
then
mount -o remount,rw /system
What does it tell you? "Denied"?
In order to prevent sony ric from blocking it, try installing NUT's xzdualrecovery version 2.8.15. Z1-lockeddualrecovery2.8.15-RELEASE.installer.zip
http://nut.xperia-files.com/
It has a built in ric killer and will solve your issues.
So all I have to do is flash the zip on my z1s to have.recovery correct I have root supersu
Got root, thanks.
Okay, got root. Thank you. The trick is to keep doing the ADB root until it works. It doesn't work the first couple of times. I gave it 20 minutes each time before trying to install again.
Jellybean
I tried your steps from Jellybean but got no root on lollipop but I can't get root from 4.4.4. Is there a 4.4.2 firmware floating around and could that be the problem? I did the steps twice and followed it exactly. The only difference is 4.3.
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
HOW TO INSTALL CWM AND ROCKZ1L KERNEL ??? STEP BY STEP ! MY Z1S IS ON STOCK 5.0.2, BOOT LOADER UNLOCKED : YES.
SORRY , MY ENGLISH IS VERY BAD ! THANKS SO MUCH .
If your stupid like me :silly: and you blindly follow the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide you may be trying to figure out how to fix your phone.
The beginner guide linked above is amazing to say the least but the OP has not updated it yet to reflect the 6.0 update. If your phone has Marshmallow 6.0 and you follow the instructions you will render your Nexus 6 unusable. Not bricked, just not functional. You will get an error that states Your device is corrupt. It can't be trusted and may not work properly. (seen below) Followed by a blank screen. But don't worry, its very easy to fix with just a few extra steps. :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are here, it is assumed that you have already done the following steps:
Step 0.1 Download and install the Android SDK tools (adb and fastboot), as well as the Google USB drivers. This is step 2 in the beginner guide and there is a great write up here on these tools. [noob-read] adb and fastboot. What is it? How can it help you?
Step 0.2 Unlocked the Bootloader.
Step 0.3 Ran the CF-Root tool. The file name is CF-Auto-Root-shamu-shamu-nexus6.zip
If you watched the CMD window closely this is where the problem happened. There will be a couple errors thrown. You will wait to see the big red Android on your phone but instead you will see the above warning message flash briefly followed by a black screen. If this is the case, proceed to step 1
Please Note: Parts of these steps are copied and pasted from other instructions. Consider this a grouping of other instructions for the purpose of simplification.
Step 1 - Install a Custom Recovery (taken from the original guide)
Go HERE to download the latest TWRP recovery for the Nexus 6. At the time of this write-up, I used 2.8.5.0
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img
Move the recovery.img file to C:\Program Files (x86)\Android\android-sdk\platform-tools
Open command prompt and run the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it.
After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Power off the phone
Step 2 - Install the Modified boot.img (Original steps HERE)
Download the modified boot.img from http://downloadmirror.co/android/sx/shamu-mra58k-boot.zip
Unzip the file and move it to C:\Program Files (x86)\Android\android-sdk\platform-tools
Boot the phone back into bootload mode using Power + volume down.
Open a command prompt and enter the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash boot boot.img
Power off the phone
Step 3 - Flash the SuperSU zip via TWRP Recovery v2.56 beta (original steps HERE)
Downlaod SuperSU x2.56 from http://downloadmirror.co/android/u1/SuperSU-v2.56-20151030013730.zip
Boot your phone into the bootloader mode with Power + volume down
Enter recovery mode. This will open TWRP Recovery
After TWRP Recovery is open, connect your phone to your computer.
Open My Computer where youc an see the C: drive, and other connected drives. You should see your Nexus 6 listed. Open it.
Move the SuperSU zip onto your phone. I placed mine in the TWRP folder.
On your phone, select Install, then navigate to the folder that contains the SuperSU zip. Click on the zip file.
Swipe to Confirm Flash and begin the flash.
Once SuperSU is flashed, select the Reboot System option.
And that's it, your phone should now boot back up to your fresh rooted copy of Android Marshmallow 6.0. You can download a root verification app to confirm the root. :victory:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
simms22 said:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
Click to expand...
Click to collapse
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
For those of us who have been down this road a time or two, this guide will not help them at all. Its really just directed to newbie's who are now stuck because of the beginner guide above.
K!ngpen said:
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
Click to expand...
Click to collapse
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
simms22 said:
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
Click to expand...
Click to collapse
I'm right there with you. My first rooted device was a motorola xt720 sometime in 2010 I think. It was a company phone and like most very young IT folk I was curious lol. New versions of Android started rolling out but the phone wasn't going to get the update. So i was suck on Eclair. I stayed after work and tried the root, and it didn't work to say the least... I stayed at work until 2am trying to get that darn thing to work. 3 days later I got it to flash cyanogen. It was buggy as hell but i didn't care because I didnt have to explain to my boss that I broke my phone by trying to "hack" it lol. That was a win in my book. I later worked up the courage to get it back on a rooted version of Froyo. Pretty bumpy start to my rooting career to say the least. Now I'm a die hard Nexus follower just looking for an excuse to root the next device.
K!ngpen said:
You followed the correct instructions haha...
Click to expand...
Click to collapse
Everyone who is trying to help other users earns respect.
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Noopguy said:
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Click to expand...
Click to collapse
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
K!ngpen said:
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
Click to expand...
Click to collapse
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Noopguy said:
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Click to expand...
Click to collapse
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
K!ngpen said:
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
Click to expand...
Click to collapse
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Noopguy said:
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Click to expand...
Click to collapse
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Noopguy said:
I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp.
Click to expand...
Click to collapse
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
sjgore said:
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
Click to expand...
Click to collapse
That's strange, I sideloaded that for MRA58K, MRA58N and MRA58R and I don't think I was ever prompted to update the binaries. I'm not sure you are being asked to.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
Thanks guys, this really helped. Flashing 2.52 did the trick and i didnt need to update the binaries after i flashed it. I am also on MRA58R
I was going to say as well, SuperSU v2.52 is what needs to be installed via TWRP, not v2.56. I believe v2.56 is for the new systemless root option but it sounds less stable and buggy.
Does this wipe any data? I have been looking to root and actually followed that guide myself, got the same issue and fixed by reflashing a factory image.
EDIT: I'm assuming I don't have to break my phone again to do this correct? Can I just pick up from step 1 to flash the recovery and go from there?
Something weird happened to me after flashing TWRP and I thought I'd share. So my N6 wasn't corrupted at all, but I decided to root my phone and I started by flashing TWRP. I went into boot loader and then recovery to make sure it worked and it did. When I went to reboot the system, I got the the "your device is corrupt screen." I pressed the power button and the screen turned black for a few seconds and then it rebooted normally. I went back into recovery to try and reproduce this and it happened again, Not sure why this happened but everything is functional.
New to rooting and I want to root my Nexus 6
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
atvisic said:
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
Click to expand...
Click to collapse
Lol why break it first. I didn't read through the op here but all you need to do is unlock the bootloader. Flash twrp with fastboot. Reboot to recovery without booting the phone, if you boot the phone before going into twrp it will get overwritten and you will need to reflash it. Flash a custome kernel in twrp, flash SuperSU 2.52 or higher in twrp.
The instructions in the op are more complete naturally. But when it has you flash the boot.img, you can use a custom kernel instead.
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
Firstly, I do not take any responsability in case anything happens to your device or your files. You decided to follow this guide at your own risk.
THIS WORKED FOR ME FOR MAGISK v14.3
ALSO WORKS ON MAGISK v14.5
I highly not recommend to use this guide for a different device other than the Xperia Z2 D6503.
All that aside, I managed to install magisk on my Stock Xperia Z2 and still keep ctsProfile and basicIntegrity: true.
HIGHLY RECOMMEND TO BACK EVERYTHING UP BEFORE PROCEEDING
You will need:
(OPTIONAL)Marshmallow FTF Firmware Here
(OPTIONAL)Flashtool Here
Magisk Manager Here
Rootkernel_v4.31_Windows_Linux.zip Here
ADB and Fastboot Here
Advanced Stock Kernel Here
TWRP Sirius Here
(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above. It worked on this version but I can't really guarantee it will work on others. Can't really guarantee it will work on this either.(after you select the file there are 2 versions. pick the modified one).
1) Extract the Rootkernel_v4.31_Windows_Linux.zip and extract from the advanced stock kernel the boot.img (Rename it from boot.img to Old_boot.img)
2) Open cmd and use cd to reach the folder in which you extracted rootkernel.
Use the command "rootkernel Old_boot.img New_boot.img"
Say Yes to everything except installing TWRP.
3) Install Magisk Manager on your phone and copy "New_boot.img" to the phone.
4) Go to Magisk Manager settings , scroll to Update Channel and select Beta
5) Select install Magisk and select modify boot image. Select "New_boot.img" from the folder you copied it to
6) Extract adb to a folder
7) After patching the boot image at step 6, copy "patched_boot.img" from internal storage/MagiskManager to the folder in which you extracted adb
8) Copy TWRP to the adb folder and rename it to TWRP.img
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
10) While still in fastboot, type "fastboot flash recovery TWRP.img"
11) Disconnect your phone from the pc. Wait a few seconds and then boot into TWRP (hold power button and Volume Down). A notification will pop up and select to "Keep System Readonly" (I think something like that). Reboot into system.
If everything worked as intended, a safetynet check will reveal everything in green, allowing you to both have root access and also run apps like Netflix and Android Pay
NOTE: Magisk Modules should be flashed via TWRP. For some reason, Magisk Manager is unable to install them.
EDIT: I tried to install xposed systemlessly but Safetynet was triggered. Don't think I can figure this out.
DahakePL tried with elite kernel and it didn't work. Writing this just in case anyone tries.
This worked for me but I can't guarantee it will work for you. (Photos at the end)
Did this guide help you? If you need any help, I will do my best to answer your questions.
I am not a developer and I do not really understand why or how everything works. I came across this method that worked for me and I thought I'd share it since I couldn't find a guide for my xperia phone when I needed it.
IN CASE SAFETY NET IS TRIGGERED, the only way to restore to everything in green is to reflash the stock rom (you don't have to format everything).
Did it work out for you? Just leave a reply saying that so I can figure out if everything works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Thank you man
Great job
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
fribriz said:
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
Click to expand...
Click to collapse
Well, this worked on this exact version. If you don't use it, i can't guarantee it will work.
Well, can't either way
But it worked on that one. I believe you don't have to reinstall your stuff if you already have the stock rom. You can just flash it over without deleting anything
Works fine thank you
Adriano-A3 said:
Thank you man
Great job
Click to expand...
Click to collapse
Awesome
I'm actually surprised.
Doesn't work on elite kernel, just tested, no root and no safetynet
DahakePL said:
Doesn't work on elite kernel, just tested, no root and no safetynet
Click to expand...
Click to collapse
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
IceGordol said:
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
Click to expand...
Click to collapse
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Modified the post in order to specify this. Also credited you. Thanks for this addition.
Where is modified FTF?
Sent from my D6503 using Tapatalk
Why do I need to flash TWRP? It is already included into advanced stock kernel.
After flash magisk, can't mount otg drive in twrp
Sent from my D6503 using Tapatalk
I am running a phone with KK 4.4.4 rooted and xposed installed. What should I do first to use it?
If I want to keep few apks data?
May I install Cyberian Camera MOd after it?
Thanks you! Working finally!
609125 said:
Thanks you! Working finally!
Click to expand...
Click to collapse
How u make it working? I got no clue about step 2... rootkernel old_boot.img new_boot.img? I really have no idea about the instructions...
---------- Post added at 04:10 PM ---------- Previous post was at 04:03 PM ----------
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Guys, I once rooted my Z2 with SuperSU in locked bootloader condition (already unroot it). Im interested with magisk and want to try it. Is it possible for me even my device is bootloader locked? Thank you
IceGordol said:
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
Click to expand...
Click to collapse
Perfect for me. Thank you very much!
But your step 9 is wrong. should be "fastboot flash boot patched_boot.img"
My ROM is Marshmallow_Stock_575_ROM_Ultraslim
must remove SuperSU (root) before installing, use UPDATE-unSU-signed.zip
Can't get this to work at all. I'm on Customised UK stock ROM.
No matter what I do, I get bootloops once Magisk is installed. If I use the Magisk Uninstaller from TWRP the phone works fine again.
EDIT: I should have said, I've tried with Magisk 16.0 and 16.7 Beta. No luck with either. I've also tried patching the advanced stock kernel boot.img and I've tried installing via TWRP with Bootloader-SonyELF. No luck again, just the same bootloop!
UPDATE: I managed to fix this by using the latest version of the RootKernel patching tool (v5.23) instead of v4.31 and following the rest of the instructions using the boot.img from advanced stock kernel with Magisk 16.7 installed successfully.
Work fine with Magisk 18
okay after two soft brick, red blinking light and the device wont turn on, i finally succeed installing this. the first issue i'm getting is adb command not found when running the "fastboot flash boot patched_boot.img", so i tried to use TWRP to install the img, which refuse saying it need bootbridge, so i install through the recommend option in magisk manager (installing directly) which cause the first brick
the first brick is restored by using flash tool
the second brick can't be restored by flash tool due to the usb debugging is off causing flash tool to said "device connected but using old drivers", luckily xperia companion software (now called emma) restored it succesfully
and i finally figured what causing the soft brick, since emma said the bootloader is locked and magisk can't be used with locked bootloader and that bricked the device.
anyway finally unlocked the bootloader since emma needed it to unbrick the device. and after unlocking the bootloader and follow again the procedure here i finally succeed installing magisk on my z2
TLDR: YOU NEED UNLOCKED BOOTLOADER TO FOLLOW THIS PROCEDURE. to check easily if your bootloader is locked or not is just by running Emma (xperia updater replacement) or use "fastboot oem device-info".
finally can try magisk, since many apps detect supersu now and refuse to work with it. i didn't unlocked the bootloader the first time since supersu can work with locked bootloader >_>
Hello,
My goal is to get an Android 11 Stable version with TWRP recovery and magisk root.
I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG
Does anyone managed to install twrp recovery and root with Android 11 stable?
Thanks
BenoMosko said:
Hi!
First Thanks for the reply.
Second, I opened a thread just for that, maybe you can share your wisdom with us over there
Stable Oxygen OS/Android 11 fastboot boot twrp.img lead to Qualcomm Crashdump
Hello, My goal is to get an Android 11 Stable version with TWRP recovery and magisk root. I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG Does anyone managed to install twrp...
forum.xda-developers.com
I dont have a T-Mobile OP6T i have a global device.
"it could work to set up a rooted OOS 10 (which should give you less trouble) and then use the method I described above to upgrade."
Can you share and give us step by step instruction please?
Which version should i be on with installing twrp recovery and root using magisk?
10.3.8?
10.3.12?
cant i do it straight from 11?
thanks.
Click to expand...
Click to collapse
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
scorpio76r said:
Yes, I have the T-Mobile which is internationally converted
Click to expand...
Click to collapse
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
You are so correct. I will never purchase a carrier branded device again.
Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
This would also be helpful to people who are just purchasing this device which most likely will have the 11 update already
BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.
Timmmmaaahh! said:
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.
Click to expand...
Click to collapse
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.
BenoMosko said:
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.
Click to expand...
Click to collapse
I already did
Timmmmaaahh! said:
That makes SafetyNet pass? I did the classic routine:
Install full zip (OnePlus6TOxygen_34.J.60) via 'Local upgrade' - no rebooting
Flash TWRP installer (I had 3.4.0-11) via Magisk - no rebooting
Flash Magisk via Magisk to other slot
Reboot! All done.
Click to expand...
Click to collapse
Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.
Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?
Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?
shreyas.kukde said:
Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?
Click to expand...
Click to collapse
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch
BenoMosko said:
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.
Click to expand...
Click to collapse
Libraplum76 said:
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?
Click to expand...
Click to collapse
I really don't think versions are all that important. Try the latest one and work your way down from there? Best practice IMHO is just revisiting the TWRP thread when preparing to flash and check for any anomalies in OP and last 2 or 3 pages of the thread. Do the same for anything you need to flash (Magisk, OOS or custom ROM thread, etc.). More reading lowers the chances of failure.
Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.
ppajdek said:
Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.
Click to expand...
Click to collapse
You just brung hope, thank you. I will definitely go on the hunt for that recovery image*Edit, just found the link https://forum.xda-developers.com/t/...1-open-beta-2-and-open-beta-3-latest.4316563/
This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
scorpio76r said:
This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present. View attachment 5384313View attachment 5384315
Click to expand...
Click to collapse
Great! Worked for me too. Thought I could never get Root or Twrp again.
scorpio76r said:
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch
Click to expand...
Click to collapse
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..
shreyas.kukde said:
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..
Click to expand...
Click to collapse
Shocking, lol
scorpio76r said:
Shocking, lol
Click to expand...
Click to collapse
Can you provide the TWRP zip that you flashed?