Database Info

Root for NOF26W?

Is there a guide for rooting the Rogers Pixel on 7.1.1??
Sent from my Pixel using XDA-Developers Legacy app

christanya99 said:
Is there a guide for rooting the Rogers Pixel on 7.1.1??
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886 disregard anything about verizon as you do not have that model.
its for the XL but the exact same method applies, just make sure you get the TWRP RC1 zip and image from here
root is here 2.79 SR3

Great, thanks a ton!
Sent from my Pixel using XDA-Developers Legacy app

k.s.deviate said:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886 disregard anything about verizon as you do not have that model.
its for the XL but the exact same method applies, just make sure you get the TWRP RC1 zip and image from here
root is here 2.79 SR3
Click to expand...
Click to collapse
I just rooted successfully but didn't install TWRP. Can I just boot back in through fastboot and install it now?

christanya99 said:
I just rooted successfully but didn't install TWRP. Can I just boot back in through fastboot and install it now?
Click to expand...
Click to collapse
Yes, put the zip on your internal storage and boot into fastboot and then boot into the TWRP image and flash the zip.

k.s.deviate said:
Yes, put the zip on your internal storage and boot into fastboot and then boot into the TWRP image and flash the zip.
Click to expand...
Click to collapse
Uh oh! Just did this now it's booting straight to TWRP...

christanya99 said:
Uh oh! Just did this now it's booting straight to TWRP...
Click to expand...
Click to collapse
Put the TWRP RC1 zip on the internal storage
Fastboot boot TWRP RC1.img
*Might have to do that a couple times for TWRP to properly decrypt.
Flash TWRP RC1 zip to apply it
That's how to get TWRP.
Your saying you did this and when you reboot system from TWRP it just reboots to TWRP?

k.s.deviate said:
Put the TWRP RC1 zip on the internal storage
Fastboot boot TWRP RC1.img
*Might have to do that a couple times for TWRP to properly decrypt.
Flash TWRP RC1 zip to apply it
That's how to get TWRP.
Your saying you did this and when you reboot system from TWRP it just reboots to TWRP?
Click to expand...
Click to collapse
Exactly. I can't boot into the system anymore. Google logo pops up and then straight to TWRP every time.

christanya99 said:
Exactly. I can't boot into the system anymore. Google logo pops up and then straight to TWRP every time.
Click to expand...
Click to collapse
Almost sounds like you fastboot flashed TWRP instead of fastboot boot TWRP. Either way, I believe you will have to flash the factory image and start over. You could try fastboot flashing the stock boot image first to see if that helps.

k.s.deviate said:
Almost sounds like you fastboot flashed TWRP instead of fastboot boot TWRP. Either way, I believe you will have to flash the factory image and start over. You could try fastboot flashing the stock boot image first to see if that helps.
Click to expand...
Click to collapse
Ok, thanks! Will give it a try.
That did it. All is good now. Thanks!

BIG PROBLEM: Flashed TWRP twrp-3.1.0-0-kagura

Hello everyone.
So, i flashed twrp.310 with adb successfully.
and after fastboot reboot it sayd:
Your device is corrupt. It can't be trusted and may not work properly. and stayed so, didnt boot up. twrp still asking password
what should i do ?? very worried.
sorry for my bad english.

Did you unlock your bootloader, or just flash with a locked bootloader?

nzzane said:
Did you unlock your bootloader, or just flash with a locked bootloader?
Click to expand...
Click to collapse
I unlocked the bootloader

Petsthx said:
I unlocked the bootloader
Click to expand...
Click to collapse
did you "fastboot flash recovery TWRp.img"?
if you did "flash boot twrp.img" then they would be why its broken

Petsthx said:
Hello everyone.
So, i flashed twrp.310 with adb successfully.
and after fastboot reboot it sayd:
Your device is corrupt. It can't be trusted and may not work properly. and stayed so, didnt boot up. twrp still asking password
what should i do ?? very worried.
sorry for my bad english.
Click to expand...
Click to collapse
After unlock bootloader is normal that appear "It can't be trusted bla bla bla"
to remove password: cancel and wipe data... or install twrp 3.0.2.4

esps said:
After unlock bootloader is normal that appear "It can't be trusted bla bla bla"
to remove password: cancel and wipe data... or install twrp 3.0.2.4
Click to expand...
Click to collapse
he is saying it won't boot up though?
Seems like he might have flashed over the wrong partition

nzzane said:
he is saying it won't boot up though?
Seems like he might have flashed over the wrong partition
Click to expand...
Click to collapse
It can be possible, but he is telling that can enter into twrp so, if he can get in, can flash kernel (AndroPlus for example)... In the worst case, will have to flash with Flashtool

Petsthx said:
Hello everyone.
So, i flashed twrp.310 with adb successfully.
and after fastboot reboot it sayd:
Your device is corrupt. It can't be trusted and may not work properly. and stayed so, didnt boot up. twrp still asking password
what should i do ?? very worried.
sorry for my bad english.
Click to expand...
Click to collapse
Sony combined recovery and boot partition ... (yes i know, kernel and fota kernel is separate)
You can not flash recovery without flash boot.img!!!
First you must flash a custom boot with disabled dm_verify then flash recovery.
For make your boot.img with drm fix, dm_verif disable and more use:
https://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Then flash any recovery you want.
Or
used this twrp_3.1.0 [it is patched but i did not test work without boot.img]
https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ
From this topic:
https://forum.xda-developers.com/xperia-xz/development/mod-sony-stock-patcher-xperia-xz-t3576493
Offical twrp can not unlock Encryption Key...
But unofficial 3.0.2 from @AndroPlus
& unofficial 3.1.0 from @AdrianDC not have this problem.
I patched my boot.img (fw: 442) and flashed, then flash AdrianDC twrp, then reboot to recovery and install SuperSU from chainfire... And work without problem.
For your solution: first flash stock ftf for fix your corrupt boot partition with flashtool. Completely back to stock, then follow the guide i told you above.

Cant Flash Custom Recovery j710f

Hello everyone,ive issue about flashing custom recovery to my phone after i flash it to stock rom
Its android version is 8.1.0
Baseband version j710fxxu5brc3
Tnx

Lelouch? said:
Hello everyone,ive issue about flashing custom recovery to my phone after i flash it to stock rom
Its android version is 8.1.0
Baseband version j710fxxu5brc3
Tnx
Click to expand...
Click to collapse
you need to wipe the data partition after flashing it in twrp, then you can boot it

Also the error that im getting is recocery image check failed...sorry for late reply

michaeladige said:
you need to wipe the data partition after flashing it in twrp, then you can boot it
Click to expand...
Click to collapse
Do i have to do that at twrp recovery or at stock recovery?...sorry for noob question

Lelouch? said:
Do i have to do that at twrp recovery or at stock recovery?...sorry for noob question
Click to expand...
Click to collapse
twrp recovery

michaeladige said:
twrp recovery
Click to expand...
Click to collapse
Im still at stock recovery...how will i flash a twrp because when i flash it errors with recovery image check failed

Lelouch? said:
Im still at stock recovery...how will i flash a twrp because when i flash it errors with recovery image check failed
Click to expand...
Click to collapse
have you checked the OEM unlock option in the developer options in the settings??

Flash magisk and dont allow system r/w thats dm verify

michaeladige said:
have you checked the OEM unlock option in the developer options in the settings??
Click to expand...
Click to collapse
Yes

ORIGINALNAME123 said:
Flash magisk and dont allow system r/w thats dm verify
Click to expand...
Click to collapse
How can i flash it?

When i flash the magisk zip it errors with signature verification
When i try to root it or flash the patched magisk patched boot it errors with boot image signature check failed...
Sorry for late reply

Lelouch? said:
How can i flash it?
Click to expand...
Click to collapse
Look, i had this issue too i already said what to do.
1. Enable OEM unlock and USB debugging in developer settings
2. flash twrp (but don't boot into it)
3. boot up your phone to system
4. then boot to twrp and where it asks you to like enable system r/w or no select no
5. wipe data
6. from your laptop/pc move magisk.zip to phone
7. flash magisk
8. done

ORIGINALNAME123 said:
Look, i had this issue too i already said what to do.
1. Enable OEM unlock and USB debugging in developer settings
2. flash twrp (but don't boot into it)
3. boot up your phone to system
4. then boot to twrp and where it asks you to like enable system r/w or no select no
5. wipe data
6. from your laptop/pc move magisk.zip to phone
7. flash magisk
8. done
Click to expand...
Click to collapse
i flashed the twrp 3.2.3.0 after i boot up and boot to recovery it still the stock recovery

HELP - Xiaomi Mi note 3 I can't take ROOT

HELP!
sorry for my english
I can't take ROOT on my Xiaomi Mi Note 3
I was able to unlock the Bootloader With Minimal ADB and Fastboot I control the phone in Fastboot mode
With the command, I can flash the phone:
Code:
fastboot flash recovery recovery.img
I can access TWRP recovery (version 3.5.0_9-0) with the command:
Code:
fastboot boot recovery.img
Because when I holding down Vol + and Power start the custom recovery (and I think this is the problem).
From TWRP recovery (booted from PC) I can install SuperSU without error but when I start the phone it is not rooted
Can anyone help me?
P.S. I made several attempts to install SuperSU in different versions (always without success) some of these caused the phone to stop booting and I always solved with this instruction. source
Code:
Reboot into TWRP, allow system changes... if your not prompted, in TWRP go to Mounts and make sure Mount System Read-Only is NOT checked, then from the main menu go to Advanced - Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu (exactly as entered, only space is between echo and SYSTEMLESS)

Hi,
which rom are you trying to root? Also try use Magisk not supersu.

zaqm said:
Hi,
which rom are you trying to root? Also try use Magisk not supersu.
Click to expand...
Click to collapse
Hi zaqm,
thanks for your support
I never change rom on my Xiaomi Mi Note 3

scasser said:
Hi zaqm,
thanks for your support
I never change rom on my Xiaomi Mi Note 3
Click to expand...
Click to collapse
Flash recovery twrp 3.2.3.0 and then install trough it magisk 20.1

zaqm said:
Flash recovery twrp 3.2.3.0 and then install trough it magisk 20.1
Click to expand...
Click to collapse
I try thank's

I have Flash recovery twrp 3.2.3.0 and now recovery start with Vol + and Power
I have try install magisk 20.1 but I have take this error.
One strange things(for me) the system was restored and erase all data

Your data was erased when you unlocked the bootloader. The magisk gives that error because you flashed supersu. You'll have to either reflash stock rom with miflash but without locking the bootloader or flash custom rom.

zaqm said:
Your data was erased when you unlocked the bootloader. The magisk gives that error because you flashed supersu. You'll have to either reflash stock rom with miflash but without locking the bootloader or flash custom rom.
Click to expand...
Click to collapse
I will try !!
thank's

zaqm said:
Your data was erased when you unlocked the bootloader. The magisk gives that error because you flashed supersu. You'll have to either reflash stock rom with miflash but without locking the bootloader or flash custom rom.
Click to expand...
Click to collapse
You recommend me a stable custom rom?
Thanks

scasser said:
You recommend me a stable custom rom?
Thanks
Click to expand...
Click to collapse
Xiaomi.eu, CrDroid 7, Aospa and others. Join the telegram group - there you can find more info https://t.me/MiNote3Chat

zaqm said:
Xiaomi.eu, CrDroid 7, Aospa and others. Join the telegram group - there you can find more info https://t.me/MiNote3Chat
Click to expand...
Click to collapse
In the end, now everything working
I have crDroid thanks zaqm and Telegram group

Guide for installing TWRP on OOS 11 Open Beta(Upto closed release 11)

Backup first, that's a must as always.
If coming from OOS 10 base -
1. Flash OOS 11 OB1/hotfix, after its completion do not reboot
2. Install official/unofficial twrp recovery image to ramdisk from advance menu in TWRP
3. Reboot to recovery
4.a. install magisk(optional) and reboot
4.b. repeat 1 and 2, reboot again then, 4.a.
If already on OOS 11 OB1/hotfix-
1. Flash the attached boot.img from bootloader
2. Reboot to recovery from bootloader itself(booting to system at this point will result in bootloop)
3. Follow the process as mentioned for OOS 10
Thx to Soft_M for boot image
NOTE: Above method is not compatible with OB2
OB2,OB3, closed release users directly flash official latest TWRP zip
NOTE: Installing TWRP on OB3 with any given method will cause safety net to fail

man thanks, that saved me from a bootloop from magisk...

Does this work with the HOTFIX build for OB1?

sw1tchback said:
Does this work with the HOTFIX build for OB1?
Click to expand...
Click to collapse
Yes it does, actually I tested this method on hotfix

Whats your widevine status on OOS11? Mine is l3 on unlocked bootloader.

parthrathore said:
Whats your widevine status on OOS11? Mine is l3 on unlocked bootloader.
Click to expand...
Click to collapse
For unlocked bootloader, l3 always

So you have tested official TWRP 3.5.2-9.0 on OOS Open Beta 2 and it works fine? Interesting

CrysisLTU said:
So you have tested official TWRP 3.5.2-9.0 on OOS Open Beta 2 and it works fine? Interesting
Click to expand...
Click to collapse
I confirm

I flashed oos beta2 and try to boot into twrp image through bootloader.but got to crushdump screen

What do I need to do on Beta 2 to get magisk and twrp installed? Currently none of them installed, magisk patched boot.img causes loop

romanuks said:
What do I need to do on Beta 2 to get magisk and twrp installed? Currently none of them installed, magisk patched boot.img causes loop
Click to expand...
Click to collapse
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.

megaslx said:
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.
Click to expand...
Click to collapse
Patching magisk from bootloader leads me to a bootloop though

megaslx said:
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.
Click to expand...
Click to collapse
flash the above attached image and reboot to recovery directly, then follow the given procedure

voske15 said:
flash the above attached image and reboot to recovery directly, then follow the given procedure
Click to expand...
Click to collapse
so,on ob2 and 3, the pure twrp img will boot into crush dump,but patched boot partition won't?

megaslx said:
so,on ob2 and 3, the pure twrp img will boot into crush dump,but patched boot partition won't?
Click to expand...
Click to collapse
After testing it out, seems that is the case

edit: deleted

I had OB3 than I tried to "fastboot boot" latest TWRP to use PixelExperience. I got the QUALCOM message.
So I did the stupid thing to "fastboot flash boot" the latest TWRP. Now I'm bricked.
I will try to flash this one and see what happens. I was trying @mauronofrio unbrick guide, but it goes only until 10.3.8.

Julianocas said:
I had OB3 than I tried to "fastboot boot" latest TWRP to use PixelExperience. I got the QUALCOM message.
So I did the stupid thing to "fastboot flash boot" the latest TWRP. Now I'm bricked.
I will try to flash this one and see what happens. I was trying @mauronofrio unbrick guide, but it goes only until 10.3.8.
Click to expand...
Click to collapse
It worked. I've manage to get into TWRP and flash the stock O11. Thanks.

any actual guide to get twrp working on B3?

TheUndertaker21 said:
any actual guide to get twrp working on B3?
Click to expand...
Click to collapse
Just use FKM to flash a twrp and magisk. it should freakinglish work.