I want to know oneplus 7t beta 3 patched boot image will work in beta 4 ?
I want candy!
gauravkapoor99150 said:
I want to know oneplus 7t beta 3 patched boot image will work in beta 4 ?
Click to expand...
Click to collapse
Don't mix them. It could work but it could also break some thing.
gauravkapoor99150 said:
I want to know oneplus 7t beta 3 patched boot image will work in beta 4 ?
Click to expand...
Click to collapse
Why do you want to do that?
Just boot with the beta 3 patched boot img, don't flash it.
And patch with magisk after booting.
thank you sir for
i update 7t beta3 rooted devices to beta4 but when i take a backup of magisk restore image error show magisk stock backup does not exist i cant take restore image then i update device in beta 4 now i want to again root my oneplus 7t....
Aswin08 said:
Why do you want to do that?
Just boot with the beta 3 patched boot img, don't flash it.
And patch with magisk after booting.
Click to expand...
Click to collapse
thank you sir for
i update 7t beta3 rooted devices to beta4 but when i take a backup of magisk restore image error show magisk stock backup does not exist i cant take restore image then i update device in beta 4 now i want to again root my oneplus 7t....
gauravkapoor99150 said:
thank you sir for
i update 7t beta3 rooted devices to beta4 but when i take a backup of magisk restore image error show magisk stock backup does not exist i cant take restore image then i update device in beta 4 now i want to again root my oneplus 7t....
Click to expand...
Click to collapse
Why do you do backup and restore!
Please follow the some tutorial steps provided in XDA threads or ask for help.
You shouldn't restore the beta 3 boot image in beta 4.
In short -
Get a recently magisk patched boot image (either beta 3 or beta 4 or latest stable build patched boot image)
Connect your phone to PC
now reboot to bootloader and run this command,
fastboot boot magisk_patched.img
Don't flash boot image
Install Magisk manager and from it select Install > Direct install
Reboot
Aswin08 said:
Why do you do backup and restore!
Please follow the some tutorial steps provided in XDA threads or ask for help.
You shouldn't restore the beta 3 boot image in beta 4.
In short -
Get a recently magisk patched boot image (either beta 3 or beta 4 or latest stable build patched boot image)
Connect your phone to PC
now reboot to bootloader and run this command,
fastboot boot magisk_patched.img
Don't flash boot image
Install Magisk manager and from it select Install > Direct install
Reboot
Click to expand...
Click to collapse
Thank you so much sir now i rooted my device thanks...
Related
Hi... Can anyone in XDA suggest a functional way to get root access on Pixel xl running 7.1.1 NOF27B (March security update). I don't see any recent posts here.
Ginsokdboy said:
Hi... Can anyone in XDA suggest a functional way to get root access on Pixel xl running 7.1.1 NOF27B (March security update). I don't see any recent posts here.
Click to expand...
Click to collapse
Hello... I think the method hasn't changed.
Download SuperSU 2.79 sr3 on your internal storage.
Download TWRP 3.0.2 RC1 IMG
1 - Reboot into bootloader
2 - Boot into rc1 TWRP IMG with fastboot boot TWRP img
3 - Select install in TWRP and navigate to the SuperSU zip. Select it and swipe to install. Let it reboot. It will boot loop 2 or 3 times. Let it do its job, it will reboot. Done.
Good luck...
5.1 said:
Hello... I think the method hasn't changed.
Download SuperSU 2.79 sr3 on your internal storage.
Download TWRP 3.0.2 RC1 IMG
1 - Reboot into bootloader
2 - Boot into rc1 TWRP IMG with fastboot boot TWRP img
3 - Select install in TWRP and navigate to the SuperSU zip. Select it and swipe to install. Let it reboot. It will boot loop 2 or 3 times. Let it do its job, it will reboot. Done.
Good luck...
Click to expand...
Click to collapse
Will try..Thanks
After Root open beta 17 stook on boot logo
Any solution
Amar5373 said:
After Root open beta 17 stook on boot logo
Any solution
Click to expand...
Click to collapse
Well is it really too hard to explain your problem in proper sentences? So you wanted to root your phone. What did you use? Magisk? SuperSU? Which version? I can't help you if you don't provide information..
I have the same problem. Neither SuperSu nor Magisk works.
persa2011 said:
I have the same problem. Neither SuperSu nor Magisk works.
Click to expand...
Click to collapse
supersu not working please help
Use SuperSu 2.82
2.82 works fine for me! Many thanks!
My Steps For Stock OB17 Zip *Same Steps for Magisk V12 Or SuperSu V2.82*
Code:
Flash latest TWRP From Blu_Spark V35 Or Stock TWRP
Format Data Reboot TWRP
Wipe All
Copy [URL="http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_17/"]OB17[/URL], [URL="https://forum.xda-developers.com/devdb/project/dl/?id=25000"]TWRP V35[/URL], [URL="http://www.supersu.com/download"]SuperSU V2.82[/URL] To Internal Storage
Flash OB17
Select Flash IMG, Install TWRP Reboot TWRP (So Stock Rom Doesn't Replace With Stock Recovery)
Wipe Cache/Dalvik
Flash SuperSU
Reboot = Profit
*Optional*
Take A Backup Of Rooted Boot IMG (If You Flash A Custom Kernel And Run Into Issues You Can Restore Rooted Boot IMG With Ease)
Flash Kernel Of Choice (Beware Because Of No Source Code And Kernel Changes Might Be Some Issues With Custom Kernels)
TO root latest beta an stable version you can follow this guide:
I updated TWRP in TWRP via zip flashing and now whenever I try to reboot my phone, it only boots back into TWRP.
Previously, I was unlocked bootloader and rooted on stock.
Would appreciate any help. Thanks
I've never installed TWRP on this phone, but here is one thread Google returns that seems to be similar.
https://forum.xda-developers.com/pixel-xl/how-to/twrp-bootloop-flashing-twrp-t3533765
One relevant thing that has changed since the time of that discussion is that the May and newer bootloaders require a signed boot image. When I installed the May update with SuperSU without signing the boot image my phone simply ended up switching to the other slot, but again I didn't have TWRP installed. There is a zip for signing the boot image and further discussion here.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Thanks for the response. Looks like I have to flash factory image and then the verified boot signer. I'll give it a shot and report back.
Fixed this rather easily using the June factory images. Flashed using flash-all.bat (and removed the -w) and things are updated and back to square one. Interestingly, I didn't need to sign the boot image.
Thanks for the help.
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
TonikJDK said:
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
Do you need to use the signed boot image file if you are flashing an unrooted custom Rom? I thought you needed to use it when flashing anything that changed the boot image from stock, including flashing TWRP if it's going to be installed on the phone.
Actually now that I thought about it the signed boot image is SuperSu specific, isn't it?
Click to expand...
Click to collapse
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
alluringreality said:
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
Click to expand...
Click to collapse
yeah i am stock rooted with twrp on june 7.1.2. I had to flash the verifiedbootsigner-v8 when rooting with magisk and twrp. I did NOT have to flash it when flashing elementaX 1.12
We're can I download v8?
Sent from my Pixel XL using Tapatalk
The first post from the following link has the latest version of the Verified Boot Signer attached.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
335Deezl said:
We're can I download v8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is Pixel XL forum.
Slowclap
Phalanx7621 said:
Slowclap
Click to expand...
Click to collapse
I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.
Hi there!! Is it possible to root the Poco F3, keeping stock MIUI and still get OTA updates, without any problem (no data loss, no app auth removal, etc)
With rooted stock rom, you still get OTA updates. The smaller incremental OTA update will refuse to install, and the phone will download the full rom instead. Once the full update installed, you will have to apply root again (eg. flash the patched boot.img from the new update).
kurtschmeichel said:
With rooted stock rom, you still get OTA updates. The smaller incremental OTA update will refuse to install, and the phone will download the full rom instead. Once the full update installed, you will have to apply root again (eg. flash the patched boot.img from the new update).
Click to expand...
Click to collapse
In case you're using Magisk, would you flash the OTA update and magisk in TWRP?
What about internal data, and 2FA or banking apps? Do I need to re-authorize everything after OTA update?
I found this video
which shows that you could OTA update by "disabling magisk" for a moment. Is this procedure good?
As said, I let the phone update itself automatically. Since the smaller incremental update will not work, the phone will ask to download the bigger (±3 GB) updater. Once downloaded, it will overwrite the previously patched (rooted) boot.img.
So, when the update has finished and the phone has rebooted, you won't have root access anymore. In order to restore root access, you will have to flash a new patched boot.img.
There are different ways. I always use fastboot on my Mac. On a mac or pc, download the fastboot or recovery file of the new update that was just installed. Extract boot.img from that file. Send the file to the phone and patch it with Magisk. Send the patched boot.img back to the mac or pc and flash it to the phone (both a and b partitions) with fastboot.
Yeah, the only problem really is that, the boot-partition gets replaced with an update. So with every update you have to re-flash the patched boot.img
Magisk can patch TWRP Backups too, you can then restore the patched Boot-partition in TWRP!
So this is what I do to get Root again after an Update:
1. Boot into Fastboot Mode
2. Boot into TWRP SKKK
3. Backup Boot-partition
4. Boot Android
5. Open Magisk & patch /sdcard/TWRP/Backups/boot.emmc.win
6. Rename /Downloads/magisk_patched_xxx.img to "boot.emmc.win"
7. Move (and replace, when asked) to /sdcard/TWRP/Backups/boot.emmc.win
8. Boot TWRP SKKK and restore patched Boot
cyanGalaxy said:
Yeah, the only problem really is that, the boot-partition gets replaced with an update. So with every update you have to re-flash the patched boot.img
Magisk can patch TWRP Backups too, you can then restore the patched Boot-partition in TWRP!
So this is what I do to get Root again after an Update:
1. Boot into Fastboot Mode
2. Boot into TWRP SKKK
3. Backup Boot-partition
4. Boot Android
5. Open Magisk & patch /sdcard/TWRP/Backups/boot.emmc.win
6. Rename /Downloads/magisk_patched_xxx.img to "boot.emmc.win"
7. Move (and replace, when asked) to /sdcard/TWRP/Backups/boot.emmc.win
8. Boot TWRP SKKK and restore patched Boot
Click to expand...
Click to collapse
Thanks so much!
What about for the OTA procedure instead?
lillo9546 said:
Thanks so much!
What about for the OTA procedure instead?
Click to expand...
Click to collapse
Yup my instructions are for updates!
Unfortunately there is no "automatic way" to regain Root after an Update, at least AFAIK.
If you mean you want the small incremental updates to work, I'm not sure due to the altered Boot-partition. Might be best to use the Full Updates. ^^
You could also just flash Magisk.apk in TWRP or OrangeFox because it's also a Flashable ZIP-file, instead of manually having to patch Boot-partition.
I personally haven't done that in a long while, and the official FAQ-page of Magisk says, that that method is outdated and unsupported now, but apparently still works!
I forgot to mention OrangeFox in my previous post, but seems like a newer, better Custom Recovery than TWRP. You can also use that instead of TWRP. But make sure to use the latest Beta instead of Stable from the official Website because only the Beta can view /data (Android 12 Encryption Support). Stable TWRP also doesn't yet support A12 Encryption, only TWRP SKKK (Beta-version).
cyanGalaxy said:
Yeah, the only problem really is that, the boot-partition gets replaced with an update. So with every update you have to re-flash the patched boot.img
Magisk can patch TWRP Backups too, you can then restore the patched Boot-partition in TWRP!
So this is what I do to get Root again after an Update:
1. Boot into Fastboot Mode
2. Boot into TWRP SKKK
3. Backup Boot-partition
4. Boot Android
5. Open Magisk & patch /sdcard/TWRP/Backups/boot.emmc.win
6. Rename /Downloads/magisk_patched_xxx.img to "boot.emmc.win"
7. Move (and replace, when asked) to /sdcard/TWRP/Backups/boot.emmc.win
8. Boot TWRP SKKK and restore patched Boot
Click to expand...
Click to collapse
Can i do this procedure to dirty flash miui updates?
1. Boot twrp using Power button + Volume Up
2. Flash the ota update zip.
3. Reboot.
Can i do this?
gigavolthavoc07 said:
Can i do this procedure to dirty flash miui updates?
1. Boot twrp using Power button + Volume Up
2. Flash the ota update zip.
3. Reboot.
Can i do this?
Click to expand...
Click to collapse
Yes but make sure to use a Full OTA zip, not an incremental update zip. (the ZIP files in range of ~1-3 GB, not the ~300 MB incremental update-files)
cyanGalaxy said:
Yes but make sure to use a Full OTA zip, not an incremental update zip. (the ZIP files in range of ~1-3 GB, not the ~300 MB incremental update-files)
Click to expand...
Click to collapse
thanks man
Which custom recovery is MIUI OTA enabled?
I can't find it in Orangefox, show me!
Dirt.
orangefox version: [email protected] . 1_1_A12
user2332 said:
Which custom recovery is MIUI OTA enabled?....
Click to expand...
Click to collapse
Probably none. There is no point in trying to do that.
If you say so, I'll believe it. Thank you very much! I don't even bother with it anymore.
my way is to backup stock boot vendor_boot dtbo from twrp before flashing twrp and whenever i want to ota update i restore the backup and reboot
magisk will be gone
twrp will be gone
i start the ota update, it'll flash the small incremental update instead of using the entire 3gb rom