Is my version able to flash ROMs from the OnePlus 8 ROMs section?
I have gone through the process on unlocking my bootloader and installed a recovery but every time i try to flash/sideload a .zip ROM it just states "Error installing zip file ......."
I would really appreciate knowing this as well. My OnePlus 8 basically useless at this point. I think the only fix is going to be the flash the ROM
If ROM won't install in recovery try payload_dumper method
1. Download payload_dumper.zip and extract
2. Extract payload.bin file from ROM you want to install, and move it to the payload input folder inside payload_dumper
3. Run payload dumper.exe
4. Once the command prompt window closes, copy ALL files from "payload output" to where your fastboot files are located
5. Boot phone into fastboot and plug into PC, run "flashall.bat" inside your fastboot folder to install the ROM
6. Reboot to recovery after and factory data reset.
Related
My daily driver is AOSCP (CypherOS project) P20 pro ROM, but sometimes I flip back to stock every time there is a new Huawei P20 Pro update. Recently they released (9.0.0.213) so I removed the custom ROM and installed stock (9.0.0.213) without issues, just to see how it feels, whats new and such then jump back to custom. These steps helped me when I bricked my phone.
(Bootloader must be unlocked)
- Use at your own risk.
To jump to stock.
1) Go HERE and type in your phone model and click FIND MODEL button. Then click Filelist, copy and paste the first two links to your browser, this will download the main packages.
2) Extract the update.app file from the Update.zip file you just downloaded.
3) Use EMUI extractor application to extract the image files from the Update.app file.
4) Download Re-Flash, place all the images in the Re-Flash folder and flash as many images as you can. (This step simply puts your phone in enough working order for the update to complete)
Open the "cmd-here" file and start flashing:
Example:
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash cust cust.img
fastboot flash recovery_vbmeta.img recovery_vbmeta.img
fastboot flash kernel kernel.img
(Keep going - some will flash others won't)
5) type: Fastboot reboot, quickly unplug your phone and hold the volume up button, this will boot into EMUI recovery, now format data, format cache.
6) Now the two main packages you downloaded in step one, place those zip files in the folder called ZIPS-HERE, located in the Re-flash folder. Rename update_full_CLT-L29_hw_eu to update_all_hw
7) In the cmd-here window, type flash.bat
follow the steps.
Note:--------------------------------------------------------------------------------------------------------------
if the update fails you'll need a userdata.img, this image file isn't in most update.zip files. You can find it here.
Redo the steps again except this would be the last thing to do in step 4.
- fastboot flash userdata userdata.img
Okay, so I have CLT-L09C782, I updated it to 9.0.0.168 using the FunkyHuawei service. I opened Firmware Finder a while ago and I have seen some new versions of firmware there. Can I manually update from there?
aka.petteri said:
Okay, so I have CLT-L09C782, I updated it to 9.0.0.168 using the FunkyHuawei service. I opened Firmware Finder a while ago and I have seen some new versions of firmware there. Can I manually update from there?
Click to expand...
Click to collapse
I tried Firmware finder in the past, hadn't had any real luck with it whereas other have. So I really can't comment on it.
For those who would like to root, but not install any version of TWRP, here is a guide I put together. Hopefully it's easy enough and specific enough to understand:
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues. Find it under SETTINGS, SYSTEM, ABOUT PHONE, BUILD NUMBER. The region is in parenthesis and the firmware version is the last three digits.
2. Extract the RAMDISK.img file using this Huawei Updater Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into ***FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5. There may be other versions that work, but this version worked every time for me.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x. To avoid any issues with Magisk Manager, don't exit out of the application until you install 7.1.x.x.
7. Click INSTALL on the first option next to the word MAGISK in Magisk Manager to patch your freshly extracted RAMDISK.img file from Step 2. Magisk Manager does not allow for direct installation of the Magisk zip file any longer so you need to patch a stock RAMDISK file to be flashed in Step 9.
8. Copy that RAMDISK.img file to your PC and place the file in your ADB tools folder. It would be good to save a copy of this file for later if you need to re-root. By doing so, you can avoid steps 1-3.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!
***FASTBOOT
To boot into FASTBOOT, turn off phone, hold down the VOLUME DOWN button for a few seconds, and while still holding it plug your charging cable into the phone. The screen should turn on with a white background indicating you are in FASTBOOT mode.
Hi good guid, I flashed version 9.0.0.252 and had a lot fc. back to 215, everything works, any idea what the latest European working version clt-lgrp2-ovs 9.0.0??
Hello, I'm new here, so if I'm doing something wrong have mercy .
My 1+7Pro GM1913 is unlocked, rooted with Magisk (I think 22.1), TWRP 3.5.0_9-0-guacamole and OOS (last flashed version was 10.0.11.GM21BA considering I still have on the phone the OnePlus7ProOxygen_21.E.32_OTA_032_all_2101280020_c39273ef1f205b6.zip).
Last time I've flashed something I think was about a month ago, with the last update. No problem so far, until today. This morning my phone had problems with wifi, so I rebooted it.
From that moment on, it boots only to Fastboot Mode. I can get to TWRP and I can access my phone directories from the pc only from TWRP, every other mode makes my phone unreachable from usb, and installing or updating drivers doesn't work.
I would love to avoid any data loss or anything related to having to reinstall every 2FA I have.
I tried deleting everything from /data/adb/modules but nothing changed.
I looked around on XDA but I usually get people stuck on Fastboot only and accessible via usb, which is not my case.
So I was thinking about flashing the latest available OTA, then TWRP, then Magisk from TWRP but I'm not sure if it will works or just worsen my problem.
Has anyone had this problem before? Any idea about how to solve this?
Thanks for anyone willing to help me.
Have a nice day!
EDIT:
Solved flashing the full OTA.zip, twrp.zip, reboot and Magisk.zip after renaming the apk.
I think this will help you:
Twrp --> flash your boot.img (with "payload dumper" it can be extracted from the full OTA update file)
Then flash twrp.zip, reboot in to twrp, flash magisk.zip, wipe dalvik cache
Reboot and provit ;-)
Being a monday and everything, I'll write down what I've done so far, this way if anyone find this post with the same luck as mine maybe it will be less painful for him\her.
I followed this guide on XDA in merit of the "payload dumper" suggested by Ghost323 and followed the instruction on the Github page, which are:
google protobuf for
Code:
python pip install protobuf
Make you sure you have Python 3.6 installed.
Download payload_dumper.py and update_metadata_pb2.py
Extract your OTA zip and place payload.bin in the same folder as these files.
Open PowerShell, Command Prompt, or Terminal depending on your OS.
Enter the following command:
Code:
python -m pip install protobuf
and being my zip a full OTA
When that’s finished, enter this command:
Code:
python payload_dumper.py payload.bin
This will start to extract the images within the payload.bin file to the output folder you are in.
Click to expand...
Click to collapse
All good until the
Code:
python payload_dumper.py payload.bin
gave me a "no module named bdsiff4" error.
So I used
Code:
pip install bsdiff4
and turns out I'm missing Microsoft Visual C++ 14.0, which is absurd because I'm staring at it in my programs and I used it last week.
Anyway, one vs_BuildTools.exe, 12Gb downloaded and a reboot later, this time
Code:
pip install bsdiff4
works and the
Code:
python payload_dumper.py payload.bin
command finally starts.
Once that's done in the output folder I found the boot.img and made a copy into my phone root folder /.
At this point, I was looking for a flashable zip of Magisk, but I found out in a tweet dated 11:55 AM · Jan 22, 2021 that "the Magisk Manager APK *itself* is a custom recovery flashable zip", so back to Github to download the Magisk-v22.1.apk and copy that on the same root folder on my phone, following the instruction under the Magisk v22.0 updated installation guide. Under "Custom Recovery" it is written to rename the .apk into .zip.
On TWRP, Install, Install Image, and selected boot.img.
At that point I can choose between Boot, System Image, Vendor Image and Install Recovery Ramdisk.
But on the installation guide of Magisk is written "Never, ever try to restore either boot or recovery partitions back to stock! You can easily brick your device by doing so, and the only way out is to do a full Odin restore with data wipe."
So now I'm stuck. Please help.
Later I'll flash twrp-installer-3.5.2_9-0-guacamole.zip, reboot to TWRP and flash the Magisk-v22.1.zip.
You can install your full OTA update file in TWRP. Then install TWRP.zip. Restart into TWRP, install Magisk.zip (rename Magisk 22.1.apk to Magisk 22.1.zip). Wipe dalvik cache and reboot into the system.
That should work the same way. The main thing is that your Boot.img is fine again.
Both ways of mine should lead to the same success.
I wish you success.
Yes, flashing the full OTA, twrp, reboot and Magisk gave me back my phone.
However now my SafetyNet is having problems.
Thanks for the help!
While I was trying to install GApps for Lineage OS 18.1 on my Nokia 7.2, I always lost my wi-fi. This is apparently due to flashing TWRP as boot image, which replaces the stock boot messing with wi-fi as the boot image has thee kernel.
Although, I did figure it out, it took me three days to get a proper solution from multiple sources. Here, I will explain how to install Lineage OS 18.1 on Nokia 7.2 with Gapps and Magisk. This can be applied to other ROMs as well. I am assuming you are on stock firmware.
Requirements:
Any custom ROM without GApps
vbmeta file
vendor image
Gapps zip file of your choice
platform-tools
twrp image
magisk file
payload dumper tool
Preperation:
The wifi stops working because we change the boot image. To prevent this, we must flash the boot image of the rom after we are done with our work with TWRP
For this, we ,ust get the boot image for the ROM. As this is not available readily, we must extract it from the ROM zip
Install latest python on your pc
Get the payload dumper tool from the link given below. Extract the contents into the root directory of python. It should be in C:\Users\USER-NAME\AppData\Local\Programs\Python\Python <version number>
Extract the ROM zip into any folder. Copy the payload.bin file and paste it in the folder where you put the payload dumper tool
Open a command prompt in the python root folder and type
Code:
python -m pip install -r requirements.txt
Then type
Code:
python payload_dumper.py payload.bin
After it finishes, go to the folder named Output inside the python folder. Here there will be a file named boot.bin. Rename this as lineage_boot.bin and paste it into the platform tools folder
Installation:
Download the twrp image, rename it to twrp.img and place it in the platform-tools folder. Connect your phone to the computer, switch on usb debugging on your phone.
Open command shell in the platform-tools folder and type
Code:
adb reboot bootloader
. In the bootloader, type
Code:
fastboot flash boot_b twrp.img
.
Next, type
Code:
fastboot --set-active=b
and then reboot to recovery using volume buttons and selecting using power button
In TWRP swipe to allow modifications. Copy your ROM and vendor image files to your SD Card. Now, click wipe, format data and type yes. Go back to home screen and the press install. Select your ROM file and install it. Sometimes it is required to flash vendor image. In that case flash that too. This step is required for Lineage OS 18.1
Now on the twrp home screen, tap on reboot. At the bottom, the current slot should be B. Tap slot A. THis changes the active slot to A. Now go back and tap on bootloader, this should boot you to the bootloader.
Take your vbmeta.img file and place it in the platform tools folder. Now, while in the bootloader mode, type,
Code:
fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Next type
Code:
fastboot flash boot_a twrp.img
and boot to recovery using volume buttons
Now, press install in TWRP and select install and install the GApps file and reboot to bootloader
Next, in the bootloader type
Code:
fastboot flash boot_a lineage_boot.img
. Now start your phone. You should have lineage os with GApps
Installing Magisk:
Copy the lineage_boot.img into your phone. Download magisk.apk file from the link given below
Install the magisk app and open it. If it asks for additional setup select no. Beside the magisk option select install. Under options, if Recovery Mode is selected, deselect it and click next.
Now click on Select and patch a file under method. Select the lineage_boot.img
The patched image will be saved in downloads folder. Rename this file to lineage_magisk.img and copy it to the platform tools folder on your computer. Reboot your phone to bootloader mode
On your computer in the command window opened in the platform tools folder, type,
Code:
fastboot flash boot lineage_magisk.img
Reboot and you will have a rooted lineage os with GApps
Files:
Lineage OS 18.1 and vbmeta.img
TWRP
vendor
NikGApps
Payload Dumper tool
platform tools
Magisk
Guides that I Followed:
Extracting boot.img from ROM zip
Installing magisk using patched boot image
Credits:
Raghu varma for Lineage OS 18.1 port and twrp
Providers of the guides mentioned above
Hi @Ujwal2000 thanks for the guide.
I am using the stock android 10 rom and magisk patch method.
This also leads to non working wifi and magisk does not recognize that its installed.
Which steps of your guide apply to the stock rom?
i do not need gapps nor twrp I guess I only wanted to root the stock rom with magisk.
For stock, use this guide. They maintain a repository if patched boot images
Guide - How to root the Nokia 7.2 and Nokia 6.2 using Magisk
Nokia 7.2 and Nokia 6.2 come with an unlockable bootloader. The thing that compliments unlocked bootloader best is root access. So, this guide will help you in rooting the Nokia 7.2 or Nokia 6.2. You have a choice between Magisk patched boot images and TWRP recovery. I’d recommend going the...
www.techmesto.com
@Ujwal2000 , can you please look at my posting here? Thank you.
after fallowing the steps(except installing lineageOS with twrp flash everything was encrypted even tough i have the bootloader unlocked, managed to install it via adb sideload) the wifi doesnt work at all. When i try to turn it on is switches off on its own. Do anyone know a fix?
i had problem with latest version of python (3.10), version 3.7 was working for me
after the latest apdate 13.0.3 i lose my magisk
and when i want to install it using adb it gives me a boot loop and i shoold to flash the original boot.img
Nb : ramdisk yes
Uninstall it thn flash it using Twrp
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
souhail39 said:
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
Click to expand...
Click to collapse
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
pl1992aw said:
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
Click to expand...
Click to collapse
This is what i did
The original boot run finely but the patched one give me a boot loop
Miui 13 doesn't support yet unless you patch the boot img. Just revert to 12.5.9
souhail39 said:
This is what i did
The original boot run finely but the patched one give me a boot loop
Click to expand...
Click to collapse
The safe way is to not flash boot image with TWRP or Orangefox custom recoveries. Flash with fastboot mode with PC is better to prevent issue.
What version of Magisk?
If you are using the latest Magisk v24.X but it bootloop, you may report issue to Magisk author in his github.
If you used Magisk v23, it is said not working on Android 12, so will not work on MIUI 13.
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
VD171 said:
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
Click to expand...
Click to collapse
thx for your answer but always the same problem with patched img files