Related
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
ilatimer1 said:
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
Click to expand...
Click to collapse
Kernel, TWRP and Magisk get overwritten by the OTA. You need to reinstall.
Also I'd recommend to disable all Substratum themes before flashing - for me this led to a Bootpool...
ilatimer1 said:
Hello everyone, So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)? If someone has an idea on the process to do this please let me know. Thanks!
Click to expand...
Click to collapse
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
peoplesindian said:
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
Click to expand...
Click to collapse
Yes, OTA's fail to execute if you have modified the boot or system partition. An OTA is an incremental only update that selectively writes certain files and is (usually) much, much smaller. This is appropriate for a stock, unmodified device. Lots of people get tired of waiting for the OTA to come, and so they just update manually by sideloading the OTA through the stock recovery (over adb). Nothing wrong with that, and it this will sometimes bring a phone back from bootlooping or other serious problems like FC's and crashing.
A full image contains the full partition images and they are written to the device fully and unconditionally via fastboot. You can only flash a full image if your bootloader is unlocked. It essentially erases the partitions by overwriting the entire contents from beginning to end. Some would argue this more "complete" method is less likely to result in errors, or corrupt files. Removing the -w switch from the batch file script prevents the script from overwriting the userdata partition where all your media, user apps and settings are. Some call this "dirty" flashing.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
did exactly this, and all is fine.
otonieru said:
did exactly this, and all is fine.
Click to expand...
Click to collapse
Same
trim81 said:
Same
Click to expand...
Click to collapse
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
xclub_101 said:
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
Click to expand...
Click to collapse
That article is quite dubious with no source about google confirming the issue :silly:
v12xke said:
Then just execute that file from a fastboot prompt.
Click to expand...
Click to collapse
REALLY dumb question, but how do you execute a .bat from fastboot? Or do you mean with the phone in bootloader/fastboot mode, run the modified .bat?
EDIT: Never mind... put the phone in Bootloader/fastboot mode. Ran the modified .BAT from command prompt within the Platform-tools folder.
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
I followed this and everything is installed perfectly with root.
Thank you ??
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
Slow internet here, you mind uploading the boot and dtbo.img?
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
I like this idea better than the flash all, but forgive me as I haven't flashed any Android 8.1 devices yet.
Is dtbo the new name for what used to be called system?
Hi,
I'm a noob trying to root my Huawei Watch (to be able to read BTLE messages). I used egalite_kernel_HW_dffc4c0-2.0 which should be rooted (and indeed I see su.sh and busybox.sh script in the /setup folder)
I did the following:
sudo adb reboot bootloader
sudo fastboot reboot-bootloader
# Unzip TWRP_3.1.1.-0_Unofficial-Sturgeon.zip => recovery.img
sudo fastboot boot recovery.img
#In the phone, using TWRP, set to ADB sidleoad (wipe data and wipe cache)
sudo adb sideload negalite_kernel_HW_dffc4c0-2.0.zip
TWRP loaded fine and the rom installed fine to, but when opening the "Advanced Settings" it says that the phone is not rooted.
Any hint of what I did wrong?
Thanks
ruscull said:
Hi,
I'm a noob trying to root my Huawei Watch (to be able to read BTLE messages). I used egalite_kernel_HW_dffc4c0-2.0 which should be rooted (and indeed I see su.sh and busybox.sh script in the /setup folder)
I did the following:
sudo adb reboot bootloader
sudo fastboot reboot-bootloader
# Unzip TWRP_3.1.1.-0_Unofficial-Sturgeon.zip => recovery.img
sudo fastboot boot recovery.img
#In the phone, using TWRP, set to ADB sidleoad (wipe data and wipe cache)
sudo adb sideload negalite_kernel_HW_dffc4c0-2.0.zip
TWRP loaded fine and the rom installed fine to, but when opening the "Advanced Settings" it says that the phone is not rooted.
Any hint of what I did wrong?
Thanks
Click to expand...
Click to collapse
You keep saying your phone. Are you trying to root a phone or a watch? I'll assume you're talking about your watch.
adb sideload is for applying OTA updates. What you want to do is flash that zip.
While in TWRP, do the following:
sudo adb push [path to kernel zip] /sdcard
In the TWRP menu, select install. Navigate to /sdcard and select the zip. Install it.
If you can't get that working, just flash the supersuwear.zip I've attached to this post using TWRP: https://forum.xda-developers.com/hu...aw-1-5-build-m9e42c-to-downgrade-2-0-t3607859
Also, use the advanced wear settings from the play store. I've had issues with the one that negaman includes in his thread.
TheSt33v said:
You keep saying your phone. Are you trying to root a phone or a watch? I'll assume you're talking about your watch.
Click to expand...
Click to collapse
Yes! I just want to root the watch.
Thanks, for the reply. I'll try it and report back
I installed TWRP_3.1.1.-0_Unofficial-Sturgeon and then I tried to install negalite_kernel_HW_dffc4c0-2.0.zip
sudo adb push negalite_kernel_HW_dffc4c0-2.0.zip /sdcard
and Installed using TWRP.
Unfortunately I got the error below:
--
set_perm: some changes failed
Updaterrocess ended with ERROR:
Error installing zip failed
--
Trying to fix the problem I started wiping parts and I screw-up and delete the system. Wonderful.
I then tried to find ROMs and finally I found Huawei-Rom-NX-v2.7.zip and successfully installed (with Root)
https://forum.xda-developers.com/hu...-negalite-huawei-rom-nx-root-bb-v1-6-t3406813
Unfortunately I find out I need a specific build NWD1.171016.002 (Stock ROM from December 2017).
Any idea were to find it?
Or shall I open a new thread?
ruscull said:
I installed TWRP_3.1.1.-0_Unofficial-Sturgeon and then I tried to install negalite_kernel_HW_dffc4c0-2.0.zip...
Click to expand...
Click to collapse
Why do you need that? You're running a rooted rom, right? Wasn't that the goal?
If your goal is actually to be on a rooted rom AND be on the latest system software, I think it would probably be best to start from scratch since you've done so much flashing and I'm really not sure what state your watch is in at this point. This is how you do that:
1. Download this factory image: https://www.androidfilehost.com/?fid=745425885120748838
2. Extract output.tar from that package. If you need software to do this, I recommend 7zip.
3. Extract the contents of output.tar.
4. Copy flash-all.sh, image-sturgeon-m6e69f.zip, flash-all.bat and bootloader-sturgeon-m6e69f.img to the same folder where you have installed fastboot.exe.
5. Boot your watch in bootloader mode (aka fastboot mode), connect it to the computer and double click on flash-all.bat. This will bring your watch to a 100% stock state.
6. Setup the watch and keep taking OTAs until you are on NWD1.171016.002 (there should only be 1 or 2 that you have to take).
7. Boot into bootloader mode and do one of the following steps:
If you want to keep the stock recovery menu and only use TWRP temporarily, perform the command fastboot boot [path to TWRP image].
If you want to have TWRP permanently installed on your watch, replacing the stock recovery menu, perform the command fastboot flash recovery [path to TWRP image]. Then select reboot to recovery in the bootloader menu.
8. Download the supersuwear.zip package that I linked to in my previous post.
9. While in TWRP, adb push [path to supersuwear.zip] /sdcard
10. Install supersuwear.zip using TWRP menu.
And there you go. Latest firmware version, rooted. Download advanced wear settings from the play store if you want it.
Youre the man.
TheSt33v said:
Why do you need that? You're running a rooted rom, right? Wasn't that the goal?
If your goal is actually to be on a rooted rom AND be on the latest system software, I think it would probably be best to start from scratch since you've done so much flashing and I'm really not sure what state your watch is in at this point. This is how you do that:
1. Download this factory image: https://www.androidfilehost.com/?fid=745425885120748838
2. Extract output.tar from that package. If you need software to do this, I recommend 7zip.
3. Extract the contents of output.tar.
4. Copy flash-all.sh, image-sturgeon-m6e69f.zip, flash-all.bat and bootloader-sturgeon-m6e69f.img to the same folder where you have installed fastboot.exe.
5. Boot your watch in bootloader mode (aka fastboot mode), connect it to the computer and double click on flash-all.bat. This will bring your watch to a 100% stock state.
6. Setup the watch and keep taking OTAs until you are on NWD1.171016.002 (there should only be 1 or 2 that you have to take).
7. Boot into bootloader mode and do one of the following steps:
If you want to keep the stock recovery menu and only use TWRP temporarily, perform the command fastboot boot [path to TWRP image].
If you want to have TWRP permanently installed on your watch, replacing the stock recovery menu, perform the command fastboot flash recovery [path to TWRP image]. Then select reboot to recovery in the bootloader menu.
8. Download the supersuwear.zip package that I linked to in my previous post.
9. While in TWRP, adb push [path to supersuwear.zip] /sdcard
10. Install supersuwear.zip using TWRP menu.
And there you go. Latest firmware version, rooted. Download advanced wear settings from the play store if you want it.
Click to expand...
Click to collapse
Bro Thanks!!!!!
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Thanks so much! Will try this out! Nice work!
Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Please report back your success and how it goes for you!
SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP
Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out
I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532
Tested and 100% working! Recommended
smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?
PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.
Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode
It's normal that the patched boot.img is smaller.
PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing
Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.
where can i find the pre patched boot img of 10.0.12.0?
Just use the one for 10.0.11.0.
nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA
I had trouble finding this information, and since we have no working TWRP yet, here is a way to get low-level access to al lot of files.
Full credits go to: @s3axel, Source
So you flashed a module that is now causing a bootloop?
Follow these steps:
0. check if you can boot using stock boot.img, if that does not work, then you have a bigger problem then I had and this guide may not work for you.
1. Get the stock recovery.img by extracting it from the same OTA file as your current build, using payload_dumper
2. Follow s3axel's guide to get adb to work in recovery mode (after you unlock the drive)
s3axel said:
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Click to expand...
Click to collapse
3. rename the image_new.img to unsecure_adb_recovery.img
4. flash usecure recovery
Code:
fastboot flash recovery unsecure_adb_recovery.img
5. get into the adb shell
Code:
adb shell
then find the magisk module folder
Code:
cd /data/adb/modules
6. remove the module
Code:
rm -rf name_of_module
7. exit shell
8. reboot back to fastboot (See notes below)
9. flash stock recovery
Code:
fastboot flash recovery recovery.img
10. boot patched boot image to try if magisk worked
Code:
fastboot boot patched_magisk.img
Hopefully, if it boots again with root and Magisk
This worked very well and was very easy to do.
11. Use Magisk apk to install magisk to boot img. Or flash your patched magisk.
Notes:
DO NOT try adb reboot fastboot, I was hoping this would work (I was tired, ok...)
I got stuck in a bootloop (it kept asking me to unlock my device)
to break out of this loop, I used the forced off method: hold power + volume up & down until screen blacks out
From power off to bootloader:
press & hold volume down and power
and hold down until you get back to recovery, reboot to fastboot then flash stock recovery back to secure your ADB and return to as much stock as possible :good:
Here is my patched prop.default
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
grandpajiver said:
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Click to expand...
Click to collapse
The Recovery.img is from stock, so not a per-device thing.
I was just too lazy to find a place to upload large files.
I am currently on 10.0.4 but with 10.0.5 showing up, it would need updating later on.
I am not sure if you can flashboot boot recovery, certainly worth a try? Not sure how all this works, so I just flashed recovery and then flashed stock after I was done.
I also tested the TWRP build by not flashing it but booting it directly, but that was not very productive given it's current state.
hafiz.hasan said:
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
Click to expand...
Click to collapse
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
If only I didn't have tons of crap at work. This may be the gateway to v4a.
I have the images but not the extractor. Hmmmmm.
FreezyExp said:
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
Click to expand...
Click to collapse
Nice.. So are you gonna help building core only boot img for our device.?
hafiz.hasan said:
Nice.. So are you gonna help building core only boot img for our device.?
Click to expand...
Click to collapse
Nope sorry, not at this time.
There is a pull request on the magisk github that allows us to build Core-Only, so I will be waiting for that.
This guide contains the information that solved my immediate issue with not being in possesion of core-only.
Without having to deal with a lot of unknowns, just download some tools, extract some files, edit a few lines then patch it back up.
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
grandpajiver said:
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
Click to expand...
Click to collapse
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
This isn't fun to work on through a locked down Windows 10 pc. gonna try again on my chromebook after I get the 1.0.0.6 build.
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
grandpajiver said:
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
Click to expand...
Click to collapse
I got updated to 1.0.0.6.. I went from the '0' version to 'I'. Shrug.
fastboot boot recovery.img nor fastboot boot recovery recovery.img works... sigh.
I do have the full OTA. OnePlus7TOxygen_14.I.08_OTA_008_all_1911061912_10a180d3.zip. Dunno if anyone needs it.
I am on Linux. I used mktool to unpack and repack. I set all the flags properly between entered fastboot and Flash the new image to recovery as specified. device immediately hangs. I hold the keys to enter fastboot mode again and of course I can't run shell as ADB is not available in fastboot.
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
morback said:
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
Click to expand...
Click to collapse
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
morback said:
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
Click to expand...
Click to collapse
I have not fiddled around with fastboot ROMs. But you should be able to download your OOS rom with Oxygen Updater.
If someone else haven't uploaded the stock recovery, you'll need to use a tool like this to extract the payload bin inside the zip. The recovery is named recovery.img
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
When finished type
Code:
fastboot reboot
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version
Tapatalk via OnePlus 7T
Thank You
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
If u r already on 10.0.12 EU u dont need the rom
If u r on previous OOS then use the oxygen updater app from Play store to update
ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
One guy already upload this file here :
https://drive.google.com/file/d/1-_3fL5HkWS9cplro7iNiIzqlL_AGTz2B/view?usp=drivesdk
Tapatalk via OnePlus 7T
Hm, I have HD65AA India and after boot (not flash) via fastboot attached here patched boot.img I don't have internet (gsm and wifi).
Do you have India's version of that patch ?
KyoshiDev said:
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
Click to expand...
Click to collapse
4. and 5. Step isn't needed.
When you boot your image and check if you have root you just klick: Install --> Install --> direct install. It will automatically patch your actual boot.img and you will permanently have a rooted phone.
I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing
Did not work for me on reboot after root check says not rooted?
---------- Post added at 06:54 PM ---------- Previous post was at 06:44 PM ----------
Nope did not work for me say I do not have root on root check?
=dgim= said:
I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing
Click to expand...
Click to collapse
I have updated to 10.3.4.HD65AA yesterday. Have been rooted since much earlier version with Magisk Canary. Now I want to change to stable but not sure of the process.
How do I uninstall Canary version? There does not seem to be any uninstall option in Magisk Manager Canary version. Can I just uninstall as I would any other app?
Is the file you uploaded correct for my version? Would it install Magisk Stable version?
After going into fastboot do I have to connect to PC and give commands there or in the phone itself. Have done it earlier but I forgot. If from PC, which software to use for ADB?
Edit : Will this wipe data?
You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
=dgim= said:
You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Click to expand...
Click to collapse
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.
jesrani said:
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.
Click to expand...
Click to collapse
Booting and flashing TWRP on recovery partition, I suppose, is working.
I didn't flash Magisk install or unistall via TWRP on OP7T.
Are you sure that, after flashing new rom, your device is rooted ?
Even you have installed Magisk Canary, but - SatetyNet etc, is passed in your device after flashed stock 10.3.4 ?
If not, you can just unistall apk (Magisk Manager), clear cache, flash patched boot.img and install stable Magisk (I didn't test stable on 10.3.4).
I'm lost somehow.
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory.
I reboot the bootloader. Fine. I fastboot the patched image. Fine. Check for root. Fine
I reboot the bootloader. Fine. Comes up with a menu. The top of the menu says Start.
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
KyoshiDev said:
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing
Click to expand...
Click to collapse
davekaye said:
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory. .
Click to expand...
Click to collapse
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
davekaye said:
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
Click to expand...
Click to collapse
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
davekaye said:
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
Click to expand...
Click to collapse
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.
KyoshiDev said:
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.
Click to expand...
Click to collapse
Thanks. My fault. Since I don't have a working TWRP I haven't been playing around with any ROMs and I guess I'm rusty. So I tried to put your upgrades on the wrong version of Oxygen (11 not 12) and ran into a bootloop. I could not boot into EDL mode (another issue I have to follow up) and it took me some time to finally boot back to 11 and then do the OTA upgrade to 12. All is working now, so thanks again.
Hello, is SafetyNet supposed to fail or I've messed something up?
1nikolas said:
Hello, is SafetyNet supposed to fail or I've messed something up?
Click to expand...
Click to collapse
Safetynet should pass
So i put this on my US version. HD1905. I should have been more careful. Anyway, everything works well except netflix., which is now a system app and will not run or uninstall.
PS: Do you have US version patched boot file ?