Related
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Same problem here. Already tried to boot every version of TWRP without success.
abrahammurciano said:
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
But there's no button to flash, I open the app, select flash recovery, select device, but theres no button to flash it.
See screenshot
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Denkai said:
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Click to expand...
Click to collapse
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
super odd. maybe your boot image is corrupt? still doesn't explain why fastboot boot isn't working though... Try bluSpark's TWRP image. it's a solid build and I am not having issues with it.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page17
or you can also try swapping to the other partition by typing 'fastboot --set-active=_a' (or fastboot --set-active=_b) and booting to that recovery.
if that doesn't work for ya, try and restore stock via fastboot is my only suggestion:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
[/COLOR]
abrahammurciano said:
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
Click to expand...
Click to collapse
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Does it work for Android 10?
oneplus 6 running oxygen os beta 30 with magisk 20.1 without twrp
Borat38 said:
[/COLOR]
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Click to expand...
Click to collapse
Please I need TWRP for Blackview BV9600 pro please share with me if you have a link to a webpage I may find it
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
Hello I'm having magisk root access and official TWRP app but can't use it for NAndroid backup, how can I use the app for backup and fishing custom ROM?
I used a rooting guide from the website theandroidsoul.com/oneplus-6-root, in which i followed the second method. Upon installing the patched bootfile my phone got stuck in the fastboot mode. Is there some way to repair it ? Thank you for your help in advance.
Best regards
Max Knobelsdorf
Flash stock not image & try to boot it if not works
Flash blu twrp and flash full zip throught twrp
If you are near a PC, you can use this guide. Very easy to use. Needless to say, it will delete your data. Use Flash All option once you download and unzip the downloaded file.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Max Knobelsdorf said:
I used a rooting guide from the website theandroidsoul.com/oneplus-6-root, in which i followed the second method. Upon installing the patched bootfile my phone got stuck in the fastboot mode. Is there some way to repair it ? Thank you for your help in advance.
Best regards
Max Knobelsdorf
Click to expand...
Click to collapse
I was in a similar situation just like you before. I did some search in Google and download this stock rom : OS 9.0.2 PIE which included with a flash-all command file. Just unzip the downloaded file and run the batch command while your phone is in Bootloader mode. Wait for it to complete and reboot, then your OP6 will be in stock mode again.
After your OP6 successfully restored to normal stock rom, you can install TWRP and Magisk in the following steps :
1. Download Magisk 17.1.zip and copy to the OP6 internal storage.
2. Download the twrp image and zip file (installer) from blu_spark ( thread ) and
copy the twrp zip file (installer) into your OP6 internal storage.
3. Turn your OP6 in bootloader mode, and then perform the following command in your PC to boot the phone in TWRP mode:
fastboot boot twrp-3.2.3-x..xxxxxxx.img
4. When you get into the TWRP screen, click "INSTALL" and find the twrp installer zip file and install it.
5. After the twrp zip file is installed, exit the current page and back to the first page. Click "ReBoot" and then choose "Recovery" and your phone will boot into TWRP recovery mode again.
6. Click "INSTALL" and select "Magisk 17.1.zip" from internal storage to install. After this, you may choose to reboot your phone again.
Do not manually reboot your phone until all the steps are completed. In fact, the only "soft reboot" is in step 5 and 6 !
Hope the above information helps !:laugh:
I accidentally updated to beta 2 with the oos updater and lost root / twrp.
i'm unable to boot / flash twrp now.
bootloader is unlocked. confirmed.
steps
go into fastboot.
fastboot boot twrp.img
phone is detected and screen changes to "FASTBOOT" but nothin happens.
tried several times. no luck
any ideas?
mlkemac said:
I accidentally updated to beta 2 with the oos updater and lost root / twrp.
i'm unable to boot / flash twrp now.
bootloader is unlocked. confirmed.
steps
go into fastboot.
fastboot boot twrp.img
phone is detected and screen changes to "FASTBOOT" but nothin happens.
tried several times. no luck
any ideas?
Click to expand...
Click to collapse
Those command don't work on Android 10.
These are steps to follow 1: flash patched boot img.
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
2: Once you boot into android, open magisk and in the modules section flash twrp instaler zip file (make sure it is the installer) find it here https://forum.xda-developers.com/on...covery-unofficial-twrp-recovery-t3931322/amp/
3: boot into recovery and flash magisk from recovery
I was able to flash the patched boot.img but now on a normal boot the screen will go black after about 1 second and will not turn on.
i can boot in safe mode properly.
GUGUITOMTG4 said:
Those command don't work on Android 10.
These are steps to follow 1: flash patched boot img.
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
2: Once you boot into android, open magisk and in the modules section flash twrp instaler zip file (make sure it is the installer) find it here https://forum.xda-developers.com/on...covery-unofficial-twrp-recovery-t3931322/amp/
3: boot into recovery and flash magisk from recovery
Click to expand...
Click to collapse
Thank you for the information.. this put me in the right direction.
i had to follow these steps for it to work properly. apparently the size of boot.img is different for some users.
https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6
mlkemac said:
Thank you for the information.. this put me in the right direction.
i had to follow these steps for it to work properly. apparently the size of boot.img is different for some users.
https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6
Click to expand...
Click to collapse
Glad you sorted it out.
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
akin03 said:
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
Click to expand...
Click to collapse
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
akin03 said:
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
Click to expand...
Click to collapse
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Tab E said:
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Click to expand...
Click to collapse
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
akin03 said:
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
Click to expand...
Click to collapse
Yes. Compress the file to '.tar' and flash it
Tab E said:
Yes. Compress the file to '.tar' and flash it
Click to expand...
Click to collapse
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
akin03 said:
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
Click to expand...
Click to collapse
Ap
Tab E said:
Ap
Click to expand...
Click to collapse
Hi does not get errors on odin. Do I just need to flash the patched file or other files.
Request for help.. Have flashed the whole ap file about magisk after a guide now I have bootloop and the device restarts after 3 min. I don't get the device rooted
Hi. Is n'one who can help me...! It's important...?!
akin03 said:
Hi. Is n'one who can help me...! It's important.
Click to expand...
Click to collapse
Hi, if you send me the exact ROM of your device I can create a Root-AP file (boot.tar) for you which you flash through Odin (AP). Note that after flashing the Root file your phone will be factory reseted.
akin03 said:
Hi. Is n'one who can help me...! It's important...?!
Click to expand...
Click to collapse
Or you can follow this guide, it is the exact same process of rooting newer samsung devices.
How to root Samsung Galaxy X Cover 4s Enterprise Edition (SM-G398F)
Hey there, is there a way to root a Samsung Galaxy X Cover 4s (SM-G398F)? The phone is from June 2019 and runs Android 9.0. I haven't found anything on the forum. Here's a link to the Samsung website...
forum.xda-developers.com
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
hatl said:
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
Click to expand...
Click to collapse
How to Root via Magisk Patch:
1) Download and open the stock ROM
2) Extract the boot.img.lz4 and convert it to boot.img with a program like lz4_win64
3) Convert the boot.img to boot.tar with 7zip or winRAR
4) Copy boot.tar to your mobile phone and patch it with Magisk, so you will get magisk-patched.tar
5) Rename the patched magisk-patched.tar to boot.tar
6) Flash it with Odin in AP mode and you are rooted!
Only this method worked for me, if you try it differently it may not work! (Xcover4s)
Should work on all Samsung phones with Android 9 or higher.
I did this with the latest ATO firmware: https://samfw.com/firmware/SM-G525F/ATO
and ended up in a boot loop.
Maybe it's an issue with the latest Android 11 version - or the Xcover 5
I have the same issue . Stuck on boot screen after flashing. Works fine after I re-flash original boot or do a complete re-flash with original firmware. I can successfully root my s9 so am not a complete noob. My region is NEE
One more weird thing is that i cant seem to get it in recovery after the rooted boot flash. Any ideas for checking relevant logs?
There is a extra file in the boot.img called vmbeta compared to the s9 boot.img. Is it possible that this is the issue or am i completely wrong?
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
[CLOSED] What is "vbmeta.img" ?
What is "vbmeta.img" and why it is needed? How it works? Does anybody knows?
forum.xda-developers.com
ive tried like evverything but get stuck on a message sayying my phone isnt running on offical firmwire or something like that. But now i have another problem. When in fastboot adb cant find my device. If my phone is just on and im not in fastboot adb finds it. Why is that happening?
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
When my phone is in fastboot mode it cant find it.. WHen its on adb devices finds it but not when in fastboot mode.
A search for "root xcover 5" brings up plenty of ways to achieve this, but most of those sites are click bait, with identical instructions for any device you can think of. Other people are more helpful, like those who replied above, but I would like to know if anyone has ACTUALLY ROOTED A XCOVER 5 SUCCESSFULLY. And yes, if so, I'd like to know how it was done.
I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Okay, I see you can't install incremental OTAs with an unlocked bootloader. Disappointing. Guess I am waiting for full updates.
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
0No said:
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
Click to expand...
Click to collapse
Well I followed the same procedure when I flashed the full zip of 11.2.2.2, and it worked. So I don't see how I am doing it incorrectly.
Slikkster2k said:
I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Click to expand...
Click to collapse
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
toyanucci said:
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
Click to expand...
Click to collapse
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Slikkster2k said:
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Click to expand...
Click to collapse
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
toyanucci said:
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
Click to expand...
Click to collapse
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Slikkster2k said:
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Click to expand...
Click to collapse
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
toyanucci said:
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
Click to expand...
Click to collapse
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
The only boot image I haven't tried yet so far is 11.2.4.4 as I haven't been able to find a copy of that. I don't know why that would work when nothing else has though.
Slikkster2k said:
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
Click to expand...
Click to collapse
Try the instructions here to get payload dumper working
toyanucci said:
Try the instructions here to get payload dumper working
Click to expand...
Click to collapse
Okay that worked. I should've just tried that version first instead of the 'newer' one I found.
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Maybe try just flashing the boot partition
Slikkster2k said:
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Click to expand...
Click to collapse
Maybe try just flashing the boot partition
toyanucci said:
Maybe try just flashing the boot partition
Maybe try just flashing the boot partition
Click to expand...
Click to collapse
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Slikkster2k said:
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Click to expand...
Click to collapse
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
toyanucci said:
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
Click to expand...
Click to collapse
Thanks, didn't work unfortunately.
Slikkster2k said:
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
Click to expand...
Click to collapse
I had a similar situation with the 7T (and 8T lol) and used the info from the link as a guide to flashing every partition. I did have to wipe the phone though but in the end it booted up which was the biggest concern I had