Root by Magisk
Click Here For MR0
Click Here For MR1
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
If you get this error
Your device is corrupt. It can’t be trusted and may not work properly.
Use a terminal app or use computer and type this.
su
reboot "dm-verity enforcing"
MR0 rooted to MR1 failed to install workaround
If you're already on rooted MR0 and OTA installation failed for the MR1 Update.
You must boot into fastboot mode and flash MR0 stock boot.img , vendor.img , system.img then check for update follow instructions below.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-global-3040.zip
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot reboot
Fixed link
I managed to capture the OTA... All I got was payload.bin. How do extract my own boot.img so I can patch it?
I googled how to extract bin files. Install python on your PC. There's a package that will unpack the payload.bin file.
Thanks for this! Was stuck at work when I pulled the OTA and couldn't do it myself. Saved me a few steps
This saves us time. Razer won't put the image on the developer portal for another week
The problem I have is it now says my device is corrupt even after side loading the whole OTA file. Still got the error right after the side loading.
Guys, the payload.bin doesn't contain the full images. It contains bdiff delta files. YOU CANNOT TYPICALLY FLASH THE IMAGES EXTRACTED FROM THE PAYLOAD.
You need to patch the previous factory images with the diff. I'm downloading the update now and will gladly post a stock boot image when I get it (and if nobody else does it before )
Not really needed now though thanks to OP
Edit: Major version upgrades do appear to have flat images, but that shouldn't be an expectation. Always check the patch method in the metadata (extractor programs should at least write this to the console) is image and not bdiff.
Flippy125 said:
Thanks for this! Was stuck at work when I pulled the OTA and couldn't do it myself. Saved me a few steps
Click to expand...
Click to collapse
th3cavalry said:
The problem I have is it now says my device is corrupt even after side loading the whole OTA file. Still got the error right after the side loading.
Click to expand...
Click to collapse
Use a terminal app or use computer and type this.
su
reboot "dm-verity enforcing"
i need erase user data? i get boot loop after flashing boot.img
FellpeSoares said:
i need erase user data? i get boot loop after flashing boot.img
Click to expand...
Click to collapse
are you sure that you are installing it on pie?
RKBD said:
are you sure that you are installing it on pie?
Click to expand...
Click to collapse
yes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is anyone having issues with Google Pay? I have been passing Safety Net with no issue. I even removed all of my modules and still can't make a payment with Google Pay. I noticed the only way to get it working is to go to Magisk Manager and check "Magisk Core Only Mode" so I can then use it. Anyone else having this issue?
Edit:
Razer Phone 2 Android 9
Magisk 18.1
Warrior1988 said:
Root by Magisk
https://drive.google.com/file/d/1eHBPo2YZBWPe6zIe5sTct5SfbHQZUPa5/view?usp=drivesdk
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
If you get this error
Your device is corrupt. It can’t be trusted and may not work properly.
Use a terminal app or use computer and type this.
su
reboot "dm-verity enforcing"
Click to expand...
Click to collapse
I did the same way but after flashing the patched boot its booting normaly but i am still stuck in bootanimation.
If i flash again stock boot img works normaly.
what can be the reason for that ?
Best Regards
SimpleGek
CurtisMJ said:
Guys, the payload.bin doesn't contain the full images. It contains bdiff delta files. YOU CANNOT TYPICALLY FLASH THE IMAGES EXTRACTED FROM THE PAYLOAD.
You need to patch the previous factory images with the diff. I'm downloading the update now and will gladly post a stock boot image when I get it (and if nobody else does it before )
Not really needed now though thanks to OP
Click to expand...
Click to collapse
I must of gotten lucky then. I extracted the boot.img from the payload.bin then used magisk to patch the boot.img for root. No issues so far.
rogeriskira said:
I must of gotten lucky then. I extracted the boot.img from the payload.bin then used magisk to patch the boot.img for root. No issues so far.
Click to expand...
Click to collapse
It is certainly possible from what I can tell. Most probably a guarantee when there's an OTA to the next version of Android(deltas would probably be bigger than a flat image). I'm more implying that this shouldn't be an expectation. If you tried to patch the boot.img extracted from the payload in the OTA for O-MR0 to O-MR2 there would most definitely have been problems, for instance.
So 'twas just a warning. That WAS lucky
Alright, so, I'm gonna be the one to ask the stupid question. All a completely stock user has to do to get root now (on an unlocked RP2) is... Update to Android Pie normally, unlock the bootloader, and then follow the OP?
CurtisMJ said:
It is certainly possible from what I can tell. Most probably a guarantee when there's an OTA to the next version of Android(deltas would probably be bigger than a flat image). I'm more implying that this shouldn't be an expectation. If you tried to patch the boot.img extracted from the payload in the OTA for O-MR0 to O-MR2 there would most definitely have been problems, for instance.
So 'twas just a warning. That WAS lucky
Click to expand...
Click to collapse
Do you working now with diff ? so how i understand diff means that we need merge RP2 with RP0 boot.img ?
simplegek said:
Do you working now with diff ? so how i understand diff means that we need merge RP2 with RP0 boot.img ?
Click to expand...
Click to collapse
Ok, so the OTA packages work like this:
The package has some metadata and a number of "payloads"(concatenated in a single file)
There is one sub-payload per partition in a firmware slot(A or B)
The metadata specifies the checksums, sizes etc of each payload, along with a patch method
The patch method tells the update engine how it should go about patching the matching partition with the payload.
Most of the time this patch method will be a bdiff(binary diff).
When its bdiff, the payload is not a full image, hence the previous image is required. This previous image can be extracted from a factory image, and the diff combined with it to form a flat image which you can flash directly (and patch with magisk)
SOMETIMES (like with a major upgrade where a diff will likely be larger than a image) the patch method is image, where the payload is a flat disk image of the partition which is simply written to the partition.
The Pie update evidently contained a flat boot image. So in this case, you DO NOT need to merge the images. But with with subsequent smaller updates, we likely will need to do that.
Thank you for the Intensive information.
Can you tell then , What propably can be my Problem , that i am stucking at the Bootanimation with patched boot.img(Magisk).
Related
There seems to be a little confusion on how to do this and I've written down how to in many posts now so I figure I'd just write it down in a little guide.
What you need:
Firmware update.zip from http://pro-teammt.ru/firmware-database/
Windows only: Huawei Update Extractor
Linux/Mac(?)/(Windows too): splitupdate perl script (requires perl)
Direct link: https://mega.nz/#!4PBknJrK!iZQDI4ti6ERmQJC6afgUGTSvHHKcm9KFz9okmwwez3I
Source: https://github.com/marcominetti/split_updata.pl/tree/f5f415262be3487de28321b49dcb69d947897bf1
(Or my 'special' version https://mega.nz/#!NS4VnL7Q!5GMn-soCf_WMW6fZANd-TDzxjQkZW2LynEQtJ_TlUdU which extracts
to the same folder as 'splitupdate' instead of 'output/', and includes a mount script (Linux only, maybe Mac?) for extraction of files of the different images)
Archive extractor of your choice (7zip, winrar, winzip and so on.)
Firmware build
First you need to determine what your current firmware is, this can be done by going to 'Settings -> System -> About Phone' on your phone. Check 'Build Number'.
Mine says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BLA-L29 8.0.0.132(C636) (Replace 8.0.0. with C636 and add a B infront of 132 )
This can be translated into BLA-L29C636B132.
Now we have our current firmware!
Info on Nougat -> Oreo
As of Oreo the partitions changed a little.
'Boot' partition was split into 'ramdisk' and 'kernel'.
'Recovery' partition was split into 'recovery_ramdisk', 'recovery_vendor' and 'recovery_vbmeta', and shares the 'kernel' partition with 'ramdisk'.
The one's you probably want to flash are 'ramdisk' and 'recovery_ramdisk'. (Ramdisk is where Magisk/SuperSU goes, recovery_ramdisk is where TWRP goes)
Firmware update.zip
In this example I will be using my firmware, BLA-L29C636B132.
First start by going to http://pro-teammt.ru/firmware-database/ and enter your full firmware in the 'Enter model', click on Find Model.
This is what it will look like after you have searched. Locate the row that says FullOTA-MF and click on the 'update' link in that row.
When it's downloaded, open update.zip in your choice of archive manager and extract UPDATE.app to your desktop or somewhere easy to find.
Huawei Update Extractor:
Download Huawei Update Extractor from the link above, it's attached to first post in that thread I linked to (v0.9.9.5).
Extract the zip to your desktop (Or Downloads folder).
Enter the newly created folder that should be named 'HuaweiUpdateExtractor_0.9.9.5', and run HuaweiUpdateExtractor.exe.
Start by going to the 'Settings' tab and uncheck 'Verify header checksum'.
(Something is wrong with the header of erecovery_ramdisk, also it's mispelled to erecovery_ramdis, or maybe character limit? The partition on phone is named correctly. This does not need to be unchecked on Nougat firmware)
Then go back to the 'Extract' tab and click on the button that says '...' and open your UPDATE.APP
Rightclick on the file you want to extract and click on 'Extract Selected', this will bring up a dialog where you choose where to extract to.
After this you can flash the file using fastboot. Take 'ramdisk' for example.
Make sure you have adb & fastboot installed (https://forum.xda-developers.com/showthread.php?t=2317790)
Open up a command prompt and connect phone, reboot to fastboot mode using: usb plugged in, power + vol down, release power when phone vibrates.
Or you can use the command 'adb reboot bootloader'.
Make sure phone is recognized in fastboot mode with the command: 'fastboot devices', it should show up as a fastboot device.
Next we can flash RAMDISK.img using: 'fastboot flash ramdisk RAMDISK.img'.
On Nougat you would extract 'BOOT' from UPDATE.APP and flash using:
'fastboot flash boot BOOT.img'
Linux/Mac(?)(and Windows with perl installed, I use Strawberry Perl)
First download the splitupdate zip from above.
Extract it and enter the extracted 'split' folder, open a terminal and:
'chmod +x splitupdate'
'chmod +x crc'
Now put your UPDATE.APP in the 'split' folder and open a terminal and use the following command:
'./splitupdate UPDATE.APP file_to_extract'. If you write 'file_to_extract' or anything that is or is not in the UPDATE.APP it will list all images in it.
Typing './splitupdate UPDATE.APP' will extract all files in UPDATE.APP
It will output files to the newly created 'output' folder. The filtering is not perfect. If you use './splitupdate UPDATE.APP RAMDISK', it will extract all images with RAMDISK in its name, so you will get RAMDISK.img and RECOVERY_RAMDISK.img. This is fine for me as the original script extracted everything, which takes long for the larger images.
And if you use the 'special' version:
'chmod +x simg2img'
'chmod +x mount.sh'
I edited the splitupdate script for the 'special' version just to make it easier for me as I like to check SYSTEM, VENDOR, PROCDUCT and those images for changes.
So it made it easier if it extracted directly to the root of 'split' folder instead of 'output', then I could run the mount.sh script directly.
To use mount.sh, first edit the script and replace YOUR_SUDO_PASSWORD_HERE with your password or remove 'echo YOUR_SUDO_PASSWORD_HERE | ' and input password manually when it asks.
Then simply extract SYSTEM.img (or Product, vendor, odm whichever you like) and './mount.sh SYSTEM' (yes, no extension).
This will convert SYSTEM.img to SYSTEM.raw and mount it to 'split_folder/SYSTEM/' as a loop device, it will also chmod 777 everything in SYSTEM/.
Linux ADB and Fastboot
Use google for this one. ADB usually works fine right away, Fastboot might get 'no permissions' and need to be run as sudo if it's missing udev permissions/entries.
You can make fastboot work without sudo but it's easier to google it as it might get lengthy and there are a lot of different distros of linux (I use Ubuntu)
Hi ante0, i have downloaded the bla a09 8.0.0.109 c567 which is the recent update for my US mate 10 pro version, i was using hisuite to update my phone which is failing but i was able to grab the update which it down loaded and it has the following files in it, bla-a09_hw_usa( which contains update_full_BLA-A09_hw_usa, public( which contains update_data_full_public), update.zip which contains update.app and other xml files, i have already bl unlocked and rooted with supersu but i wanted to install magisk and i installed twrp and tried sideloading magisk but it fails stating boot image already modified and advised flask stock boot, so which files do i need to flash and what are the fastboot commands to do so and i was also thinking about complete bl lock just to make it look like new phone and how do i do that, please direct me, thank you.
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
oslo83 said:
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
Click to expand...
Click to collapse
there lies my problem, i am trying to flash an updated stock firmware than the one that came with my phone, i have unrooted supersu and deleted supersu app and dont have root anymore confirmed by rootcheck apps, since my boot is already patched once magisk wont flash and advising me to flash stock boot image but i dont know which to flash as with oreo there seems to be different partitions and i dont know commands other than basic fastbbot commands to flash stuff.
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
lingarajug said:
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
Click to expand...
Click to collapse
If you can, use the HWOTA method instead. It's free and found: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
If you can't use HWOTA and have to use Funky:
You seem to be in normal Recovery. You should see a button that says 'Download latest firmware', the one you're describing is showing buttons that are in normal Recovery.
Are you booting using Usb plugged in + vol up + power?
For some reason my phone would only boot to revovery and not erecocery, anyway i used hisuite method and was able to flash new firmware. Thank you.
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
elviss0812345 said:
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Click to expand...
Click to collapse
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Pretoriano80 said:
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
Click to expand...
Click to collapse
elviss0812345 said:
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Click to expand...
Click to collapse
lol,i've read "bricked"... .I apologize for that!:good:
There is no way at least for the US version to find firmwares shipped with phone until now, i figured it out by connecting phone to hisuite on PC and it showed update available and i clicked update and waited until download part of update process completed and then i went to documents folder and hisuite and the app stores the download there and it will have 3 zip files, u can copy them to a different place because once the update completes those files are deleted. Might be the same for other models if supported by hisuite.
Here https://playstoreappinstall.com/play-store-for-huawei/ more info
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
oslo83 said:
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
Click to expand...
Click to collapse
US version firmware not listed, lots of international versions though.
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
lex71 said:
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
Click to expand...
Click to collapse
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
dark3bod said:
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
Click to expand...
Click to collapse
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
ante0 said:
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
Click to expand...
Click to collapse
@ante0
This man is a legend.........
I would like to express my gratitude in you answering my pms and assisting to get the device up and running.
If ever am in Sweden:silly: ill definitely buy you beeeeeeeeeeeeeeeeeeeeeeers
Thanks for the patience and the help you bring to us noobs bricking these bloody Mate 9's
Im now on lineage os. I didnt flash twrp and magisk. Can i only flash stock system.img to get fully stock. Or i have to flash ramdisk and boot first before system.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
System Image: https://drive.google.com/file/d/1cAcgP55upO6UuX-gecPIXA_xnO0IXvUO/view?usp=sharing
Flash System Image:
- Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
- Connect your Razer Phone to your computer over USB.
- Start the Phone in Download Mode with one of the following methods:
- Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
- Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
- If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
- Open a terminal on your computer and navigate to the unzipped system image directory.
- Execute the flash_all script. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
- Once the script finishes, your Phone will reboot.
- You should now lock the bootloader for security.
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
LSS4181 said:
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
Click to expand...
Click to collapse
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
JDBarlow said:
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
Click to expand...
Click to collapse
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
LSS4181 said:
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
Click to expand...
Click to collapse
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
JDBarlow said:
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
Click to expand...
Click to collapse
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
LSS4181 said:
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
Click to expand...
Click to collapse
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
JDBarlow said:
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
Click to expand...
Click to collapse
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
LSS4181 said:
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
Click to expand...
Click to collapse
/HavocOS/Ten/20200402-vanilla/Havoc-OS-v3.3-20200402-arm64-ab-vanilla-nosu.img.xz
If anyone can get havoc 3.3 to work on Verizon without the sim card issue please let me know. No gsi rom will work on Verizon. Its frustrating. Thanks.
Finally got the MR3 update extracted
I worked all night extracting/converting the stock img and got beat by minutes posting Lol... anyway I also have the stock ota for global variant of MR3 if anyone needs it. You can easily patch the boot img with magisk and fastboot flash boot_a with the patched boot img and you have root again on MR3 Update. Works flawless
i Take a copy Thank You
Flashed some stuffs from MR3: modem (both), bluetooth (both), dsp (both), vendor (both), boot (inactive B slot only), system (inactive B slot only). These seem to work.
However, when flashing system and vendor I saw it mentioned something about "invalid sparse file format at header magic", but the flashed stuffs (at least vendor) looks fine.
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Havoc 3.3 GSI works fine here (the SELinux fix may still be needed for it to boot). However, for some reasons (either due to recent Magisk canary update, or something else), I lost access to VoLTE and that after updating to the new GSI version, all my app's permissions were lost and I need to reassign them (maybe it's time I back things up and start over again, as the permission reset issue can indeed happen when dirty-flashing newer GSI versions).
LSS4181 said:
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Click to expand...
Click to collapse
Running Manjaro Linux here too and experience the same behaviour.
Peace.
Can you dirty flash the mentioned images? Don't really feel like reinstalling all my apps and data.
is there a new root method
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Those usb drivers didn't work for me. What did work however was the samsung usb drivers so I downloaded them and installed, however that wasn't enough. While in fastboot mode under device manager, I can't recall how I installed it but I forced the driver either from android device in list or added new legacy hardware and installed samsung android adb interface. After that when I typed fastboot devices in console from tools folder it reported back for me. I hope this helps.
Click to expand...
Click to collapse
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
Click to expand...
Click to collapse
I u forgot something....
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Xinfuzemodz said:
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
Click to expand...
Click to collapse
Are you serious? The link of the OP is the link to MR3. If you click the flash_all.bat file it will wipe your phone and you get a fresh copy of MR3 installed so yes it can be installed on other builds
I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)
You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.
Now install the Magisk Manager app on your phone.
Open the Magisk Manager app and click on the Install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.
The output file will be stored in the download folder with the name magisk_patched.img.
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.
fastboot devices
Now enter the below command to flash Magisk and root Redmi Note 10.
fastboot flash boot boot.img
After flashing the patched boot image. reboot your device to the system.
Install Magisk Manager if it’s not already installed.
Complete the in-app instructions, and the device will automatically reboot into the system.
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Or follow this page... https://mytechgyangadgets.com/how-to-root-redmi-note-10s-via-magisk-and-supersu/
Ali mohamed 96 said:
I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)
Click to expand...
Click to collapse
Theres 2 ways to do It explained up but i prefer first one
This is a questionable part I think:
1. If your phone doesn’t have A/B partition system:
fastboot flash boot boot.img
2. If your phone has A/B partition system:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Based on the Treble Check app, at least my phone, supported Seamless System Updates and is detected to have an A/B system partition => should be used 2?
This might be a reason of : "this partition doesn't exist" with 1.
Source: https://www.naldotech.com/root-xiaomi-redmi-note-10s-magisk/
#bosr you have to follow the second step pf your post yo success, It seems that note's 10 has an a/b system partition...
!! Success !!
The process I´ve rooted my Redmi Note 10s with V12.5.8.0.RKLEUXM ROM:
(besides all needed drivers, adbs, proper fasboot ROM version, unlocked bootloader, little bit of a fear that the phone could be hard bricked and a few more) :
- patched boot.img via magisk manager v23
- flashed empty vbmeta.img as decribed here https://forum.xda-developers.com/t/root-gained.4290689/
- flashed patched_boot.img (the latest platform-tools flashed it directly to boot_a)
- reboot
Voila, Redmi Note 10s is rooted and Magisk v23 installed
Ricardo 182 said:
You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.
Now install the Magisk Manager app on your phone.
Open the Magisk Manager app and click on the Install.
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.
The output file will be stored in the download folder with the name magisk_patched.img.
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.
fastboot devices
Now enter the below command to flash Magisk and root Redmi Note 10.
fastboot flash boot boot.img
After flashing the patched boot image. reboot your device to the system.
Install Magisk Manager if it’s not already installed.
Complete the in-app instructions, and the device will automatically reboot into the system.
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?
GildroY said:
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?
Click to expand...
Click to collapse
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img
GildroY said:
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img
Click to expand...
Click to collapse
You are searching in the wrong type of ROM. It must be the fastboot type.
for example: rosemary_global_images_V12.5.11.0.RKLMIXM_20210618.0000.00_11.0_global_06239807c1.tgz
Unpack (winrar, winzip, 7-zip ...) it, there is a folder images and boot.img in it
Do not forget to flash empty vbmeta.img first, see here
bosr said:
You are searching in the wrong type of ROM. It must be the fastboot type.
Unzip it, there is a folder images and boot.img in it
Click to expand...
Click to collapse
Yeah. Apologies. Just realized it.
I was able to successfully get root access using the additional step mentioned by @bosr (Thanks a lot for that). However post that I literally bricked my device trying to debloat the device by using debloater. Post removing few of the mi bloatware apps, when I rebooted and the device kept on going into default mi recovery (even with power + vol-). I was not able to access the fastboot mode at all, no matter what I do.
Then I did the ultimate blunder ... reset the device from mi recovery. Post that I lost adb privileges as well. Besides the phone would still not boot - MIUI logo flashed with sound, then a white setup screen for a sec and again reboot.
Searching online could not fetch anything. Then I tried moving the phone to mi assistance mode from mi recovery (which is nothing but sideload mode), connect to PC and used 'adb sideload'.
Voila, the phone was detected, from sideload mode, I was able to reboot to fastboot mode, and then flash the stock rom using miflashtool. Whole 4 hours of tussle.
Sharing here, just in case someone else, gets into the same situation.
!! BADLY WAITING FOR A CLEAN ROM FOR THIS DEVICE .... <Prayers>!!
It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.
bosr said:
It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.
Click to expand...
Click to collapse
Apologies for incorrect use of language. What I meant was that your instructions were 100% correct and accurate. However, post getting root access successfully and magisk installed, I tried to debloat the device using 'debloater' module under Magisk and ended up deleting some rogue apps which Mi wants us to keep. All the issues happened after that.
I have updated my original comment as well.
OK. Apology accepted
Hi Y'all,
I just got a new Note 10s and I'm willing to root device.
I'm still in the phase of waiting for the unlocked bootloader, but already trying to get all the necessary data for root.
While searching for the fastbbot Rom to extract the boot.img I discovered the follwing problem:
I can only find the fastboot Rom for the following SW: V12.5.8.0.RKLEUXM
But my Note 10s is already on V12.5.10.0.RKLEUXM. For this SW only the recovery ROM is available.
How long will it take for Xiaomi to upload the latest fastboot ROM? Or am I doing something wrong,
Any help really appreciated
Andreas
I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.
@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas
Agzyx said:
@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas
Click to expand...
Click to collapse
It should be possible with XiaoMiTool
Mac23 said:
I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.
Click to expand...
Click to collapse
Not sure, what you are looking for, but boot.img is in the fastboot rom:
Hello,
I'm trying to patch my boot image without using Magisk App.(via PC) Is there any way to do this?
This is because everytime I do security update every month, I have to:
1. Download factory image
2. Unzip and get boot.img
3. Put boot.img in my phone
4. Patch boot.img with Magisk App
5. Move boot_patched.img to my pc and flash via fastboot
I find this very unefficient, and I want to automate 1~4 by just doing all the process in my PC.
Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?
Andrologic said:
Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?
Click to expand...
Click to collapse
@Andrologic This is because I root for VoLTE(Voice over LTE) patch and after that, I assume that I cannot update my phone via OTA. Long ago I tried updating with OTA and for as long as I remember it failed. Ever since that happened, I usually unroot first, do an update with either sideload or OTA or factory image(very often), root again with all the steps above, and so on..
If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
Didgeridoohan said:
If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
Click to expand...
Click to collapse
Ah, this was what I was looking for. Thank you.
@Didgeridoohan Do you happen to know where I can get the essential magiskinit and magiskboot binary?
From magisk v22.0 I see that magisk core and magisk manager got merged into one, and now I can't find the latest executable. (x86 too)
They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.
Didgeridoohan said:
They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.
Click to expand...
Click to collapse
You are talking about these "lib<binaryname>.so" files right?
Yup
Didgeridoohan said:
Yup
Click to expand...
Click to collapse
Thank you for the answer. I really appreciate it.
After update, make a boot.img backup via twrp (copy in twrp folder and rename to boot.img) patch via Magisk and flash new patched boot.img.
Os. I do not like a new method too.
Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.
Sathors said:
Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.
Click to expand...
Click to collapse
Can you share your script?
Hey @eyal1izhaki , sorry for the late reply.
You can find the script I am using here: https://github.com/NicolasWebDev/reinstall-magisk-on-lineageos
If you find any problem or have a suggestion, please tell me!
Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script
eyal1izhaki said:
Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script
Click to expand...
Click to collapse
https://github.com/Taewan-P/crosshatch-magisk-generator
This is my automation script FYI.
It's mostly close to an automation workflow though...
Also, you should not use the x86 binaries to patch a boot img of an aarch64 device. Flashing the mispatched img will make you boot loop the device.
i have a big dum dum poopy brain i dont know how to do anything will one of you big brain gentlemen please tell me how to patch the boot.img file with the script you guys are talking about and which app do i use and where do i use it and how do i use it. i can't use magisk because it gets stuck on the splash screen with the logo so i'm trying to patch the boot.img file without it. also will it be a problem that the boot.img file has .lz4 at the end (boot.img.lz4). aight thanks im gonna try elongating my neck by tying it to a fan with a rope.
Hi. I am sorry for bumping this thread but I am finding a solution for patching multi-model boot to add Magisk root without a phone.
Will this be possible?
I read the @Sathors script but he pushes the boot file to the android system to patch it. Can this step work on any phone or must on the exact model of the boot.img
Hi @Tungtata . If you look at the boot_patch.sh script in Magisk (https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh), in the header it says the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it seems that to work it needs the corresponding binaries, scripts and files. Maybe you can find all of these files in the Magisk repo, maybe not, in my case it seemed too much hassle to try and find out, knowing that it is working when done on the phone.
But if you really need to do that, then here is a path you can follow.
As for needing the exact phone model to patch the boot image, I don't think so because the script in itself is generic, but it depends on the other files it requires. Anyway, doing a real-life test should be quick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customization's across all platforms you run Bliss on.
BlissRoms Download
Code:
-Make sure you are on the latest OOS 11
- Dump the BlissROM zipfile through payload_dumper
- flash the partition images with the following commands
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- Reboot and #StayBlissful
Create Bug Report on our Issues Tracker
BlissRoms Github
BlissRoms Gerrit
Kernel Source
| Website | Blog | Facebook | Twitter | Instagram | Telegram Group | Telegram Channel | Docs
If someone wants to donate, please do so via this PayPal link
Thank you for using BlissRoms! And as always: #StayBlissful
reserve
reserve too
How do i dump the BlissROM zipfile through payload_dumper?
This new way of flashing roms has caught me off guard.
What is a payload dumper anyway?
mrdreamers4u said:
How do i dump the BlissROM zipfile through payload_dumper?
This new way of flashing roms has caught me off guard.
What is a payload dumper anyway?
Click to expand...
Click to collapse
The following link will explain what it is and how to extract it.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Also you can flash with twrp if you use a flash drive to host the file since decryption no longer works.
srgrusso said:
The following link will explain what it is and how to extract it.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Also you can flash with twrp if you use a flash drive to host the file since decryption no longer works.
Click to expand...
Click to collapse
So I want to grab the payload.bin from the blissrom zip and "dump" that through payload dumper?
mrdreamers4u said:
So I want to grab the payload.bin from the blissrom zip and "dump" that through payload dumper?
Click to expand...
Click to collapse
Yes
srgrusso said:
Yes
Click to expand...
Click to collapse
I did it but the only file it did not dump was the odm.img from the installation list. did i do something wrong?
mrdreamers4u said:
I did it but the only file it did not dump was the odm.img from the installation list. did i do something wrong?
Click to expand...
Click to collapse
You should be ok. Those are generic instructions. I will update the instructions.
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
srgrusso said:
You should be ok. Those are generic instructions. I will update the instructions.
Click to expand...
Click to collapse
So pretend the odm.img is not in the installation list and do it in the order you still have it in?
mrdreamers4u said:
So pretend the odm.img is not in the installation list and do it in the order you still have it in?
Click to expand...
Click to collapse
Yes
srgrusso said:
Yes
Click to expand...
Click to collapse
Great thanks I'm going to try right now.
BTW if i screw up somehow can i still use my twrp backup to restore back to where i was?
mrdreamers4u said:
Great thanks I'm going to try right now.
BTW if i screw up somehow can i still use my twrp backup to restore back to where i was?
Click to expand...
Click to collapse
You still need to format data when switch android versions. If it doesn't work you can flash the rom with twrp but you need to use otg for the file.
srgrusso said:
You still need to format data when switch android versions. If it doesn't work you can flash the rom with twrp but you need to use otg for the file.
Click to expand...
Click to collapse
Can i flash this rom like this guy does in this video? (i wish i could just flash it in twrp the normal way LOL)
(starts at 5:17 in the video)
Sorry I'm new to this method i appreciate you patience with me.
mrdreamers4u said:
Can i flash this rom like this guy does in this video? (i wish i could just flash it in twrp the normal way LOL)
(starts at 5:17 in the video)
Sorry I'm new to this method i appreciate you patience with me.
Click to expand...
Click to collapse
You can try it. Basically the problem with twrp is decryption doesn't work with A13. The way I get around this is that I put the rom file on a flash drive and flash from the usb port. If you don't have a flash drive you can try formating data and put the rom file on the phone and flash. In the video they just disable encryption which may not matter to you.
srgrusso said:
You can try it. Basically the problem with twrp is decryption doesn't work with A13. The way I get around this is that I put the rom file on a flash drive and flash from the usb port. If you don't have a flash drive you can try formating data and put the rom file on the phone and flash. In the video they just disable encryption which may not matter to you.
Click to expand...
Click to collapse
You mean a flash drive dongle like in this pic?
and just flash in twrp almost like normal but with full wipe first?
im just confused because the instructions say fastboot flash img which make me think to use fastboot on pc like in the video.
mrdreamers4u said:
You mean a flash drive dongle like in this pic?
and just flash in twrp almost like normal but with full wipe first?
im just confused because the instructions say fastboot flash img which make me think to use fastboot on pc like in the video.
Click to expand...
Click to collapse
Yes, like normal. This is the way I flash roms for the fajita and guacamole.
srgrusso said:
Yes, like normal. This is the way I flash roms for the fajita and guacamole.
Click to expand...
Click to collapse
Ok now were cooking LOL!!
So do i take these individual img files i dumped from the rom and flash those in twrp each after a full wipe then reboot or do i just full wipe in twrp and flash the blissrom zip then reboot?
mrdreamers4u said:
Ok now were cooking LOL!!
So do i take these individual img files i dumped from the rom and flash those in twrp each after a full wipe then reboot or do i just full wipe in twrp and flash the blissrom zip then reboot?
Click to expand...
Click to collapse
Just flash the Blissrom zip like before. Everything is the same as before except the location of the rom zip.
Right on Thanks!!