Hello all, I am trying to make a custom recovery for my new phone, the realme gt me rmx3363. However this is my first phone that is A/B partitioned so I don't know what to do fully. I am trying to extract the recovery.img because that is whats needed in order to make a custom recovery. However, when I look into the device firmware the only image files I see are: boot, bootloader, dbto, radio, vbmeta, vbmeta_system and vendor_boot. The system files are all seperated into "sparsechunks".
On a non-A/B device getting the recovery was as easy as downloading the stock firmware, extracting, and then recovery.img was right there. Now it seems to be different and I don't know what to do, I couldn't find anything on google about how to do this. I am sure it is easy enough though. Thank you in advance.
{
"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"
}
NextB said:
Hello all, I am trying to make a custom recovery for my new phone, the realme gt me rmx3363. However this is my first phone that is A/B partitioned so I don't know what to do fully. I am trying to extract the recovery.img because that is whats needed in order to make a custom recovery. However, when I look into the device firmware the only image files I see are: boot, bootloader, dbto, radio, vbmeta, vbmeta_system and vendor_boot. The system files are all seperated into "sparsechunks".
On a non-A/B device getting the recovery was as easy as downloading the stock firmware, extracting, and then recovery.img was right there. Now it seems to be different and I don't know what to do, I couldn't find anything on google about how to do this. I am sure it is easy enough though. Thank you in advance.View attachment 5549789
Click to expand...
Click to collapse
I have the same proble with my tecno camon 17 pro mediatek mt6587 helio g95 on android11. let me know if you find a solution.. thanks
Try
https://github.com/twrpdtgen/twrpdtgen
It says supports Android 12.
"Create a TWRP-compatible device tree only from an Android recovery image (or a boot image if the device uses non-dynamic partitions A/B) of your device's stock ROM It has been confirmed that this script supports images built starting from Android 4.4 up to Android 12"
@NextB Having the exact same issue on my Blackview BV8800.
The recovery partition is nowhere to be seen. Here's an Interesting article mentioning this scenario from the android docs. Basically, it says that the recovery code is shipped in boot_vendor.img !
@retiredtab Pardon me if I do not follow, how can mapping out a device tree help us here?
I have a feeling that this tool might help us get done: https://github.com/cfig/Android_boot_image_editor.
Basically, the flow I am thinking about is:
1. Grab vendor_boot.img unpack with it.
2. Grab twrp.img unpack with it.
3. Replace recovery code in 1 with the one in 2.
4. Repack boot_vendor.img.
5. Flash boot_vendor.img with fastboot.
Now, in my case with a mediatek processor, it's more complicated as I have to "port" twrp first, and to do that, I first need a vanilla recovery.img, so I will have to reconstruct that too at some point.
Just found an interesting method with Carliv Image Kitchen tool, seems very promising, and maybe that it the solution we seek: Here's a video demo'ing the method:
And according to the video above, the recovery code is in boot.img not boot_vendor.img!
Related
So I kinda bricked my phone when trying to go back from Beta 9.0 to Latest Official. So I decided to give some kind of guide to try and assist the people Who also got stuck. Beware that I couldnt get ADB to work as it kept complaining about drivers which I couldnt make work but it was due toe phone being bricked. If you can get into ADB and have TWRP already loaded then you can simply transfer the three files from below to your phone and follow this guide with the below three files. It works perfectly : https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you have the same issue as me then follow the following procedure :
I have the Dual Sim EML-L29C185 (How do I know this?) Well at first I didnt so I had to figure out. So let look at the following :
EML-L29 - Dual Sim Model
C185 - South African Region Model which you can get from the following post : https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473
So now that you know the model number go to this site and type in the model number eg : eml-l29c185 and you will get a list of firmwares for your phone : https://pro-teammt.ru/firmware-database/?firmware_model=eml-l29c185&firmware_page=0
{
"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"
}
Click on the file list and in the example below you will see 4 files but only need three. The EM09 and L29 have the same update.zip and same update_data_full_public.zip but different EML-XXX_hw_meafnaf/update_full_EML-XXX_hw_meafnaf.zip files so get the three files you need for your model.
Now download the Huawei Multitool from here : http://4pda.ru/forum/index.php?showtopic=759172&st=0#entry51396624
and The update.zip extractor from here : https://forum.xda-developers.com/showthread.php?t=2433454
We need to manually flash all the broken image files in the phone with the Multitool but the files we need to flash are inside the update.zip file and thats why need the extractor.
So unzip the update .zip file. Then point the extractor to the folder so you can extract the files needed by the Multitool.
The following Three files need to be flashed
System [Called System.img]
Boot [Called Ramdisk.img]
Recovery [Called Recovery_Ramdisk.img] make sure it is in the folder and rename it correctly. Mine was recovery_ramdis.img without the K so had to rename it otherwise multitool wont flash it]
You can also flash it manually without multitool with the following commands :
fastboot flash ramdisk ramdisk.img
fastboot flash system system.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
Start your phone in Recovery mode : Switch off. Hold vol down and keep holding it and plug usb cable in. Or in TWRP reboot Bootloader.
Start multitool and click on the unbrick tab on top and follow the instructions. That worked for me.
After it was done I transfered the 3 downlaoded files to the phone and followed the procedure to make sure all 3 files are flashed because multitool only uses the update.zip file and i dont think it fixed all the region stuff but this procedure did :
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
One more
Hello everyone, VIPLightning here.
Today I introduce you the December firmware dump with patched boot img included for Android Q.
USE AT YOUR RISK
I am not responsible for what happens to your device! Make sure it is charged enough before flashing!
Procedure
1. Download the zip here
2. Extract the contents
3. Boot your phone into fastboot mode
4. Run the batch script and follow the prompt
5. Reboot and enjoy
Optional: If you wish to have root, copy/paste the command below.
Code:
fastboot flash boot magisk_patched_Y16fS.img
Credits
Asus - Providing source code and full OTA on their website for the Zenfone 6z
Mickey387 - Created the flash scripts. Thanks for giving me permission to pick it from the .68 firmware to use it in this zip.
vm03 - Used his fork of the payload_dumper from GitHub.
Note:
*If you are starting over fresh after flashing the images, you may encounter an issue such as not getting past the boot animation. If that is the case, reboot to recovery, factory reset, and then try rebooting again. After that should be smooth sailing!
{
"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"
}
Many thanks for sharing!
is there a way I can use this to upgrade firmware whilst retaining an existing custom ROM installation like LineageOS?
E: never mind, was able to use the `Update-partitions-fastboot.bat` do do the above just fine.
Thanks again!
vikashhero said:
Many thanks for sharing!
is there a way I can use this to upgrade firmware whilst retaining an existing custom ROM installation like LineageOS?
Click to expand...
Click to collapse
skip
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
1poweruser1 said:
boot twrp, format data, boot to bootloader
you can follow the post in this thread or my post
[Updated][GUIDE]: How to unbrick your Zenfone 6 Android P/Q (ZS630KL)
Hello. This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like. Note: Unlocked bootloader is not required to do any of the actions...
forum.xda-developers.com
to dump firmware (there's a newer version UL-ASUS_I01WD-ASUS-18.0610.2101.132-1.1.1-user) and then use the fastboot script
boot twrp, format data, flash lineage
I recommed full restore, both edl and fastboot script
[Updated][GUIDE]: How to unbrick your Zenfone 6 Android P/Q (ZS630KL)
Hello. This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like. Note: Unlocked bootloader is not required to do any of the actions...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, thanks for your reply.
My intention was to update the necessary partitions whilst retaining my existing LineageOS 17.1 installation. Looking at the contents of the firmware package, there seems to be a batch file (Update-partitions-fastboot.bat) allowing me to do just that.
Kind regards
I've got a 65-inch 4K Funai/Philips Android TV. Is this TV rootable or flashable? The OS is so laggy on this device it makes it almost unbearable to use. Opening specific screens takes seconds because of all the quirky animations. I'd much rather prefer flashing a different version of Android TV that doesn't lag any time I scroll to the next app on the home screen.
I have successfully unlocked the bootloader through fastboot. I'm not experienced to go any farther than that though.
Originally,
Code:
fastboot flashing get_unlock_ability
returned "(bootloader) lock"
After running
Code:
fastboot flashing unlock
it appears to unlock bootloader.
It factory resets tv after unlock, and persists through reboots.
{
"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"
}
I'd love nothing more than to get root working on this TV! Any suggestions on what to do next from people smarter/more experienced than me, throw it out there.
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
any idea how i go about grabbing the ota firmware or any firmware for my tv ? it's the phillips walmart 75 inch model, i was able to unlock bootloader but mtk client doesn't work with it, no way to get to brom mode to test. want a proper dump before i start essing with anything. Thanks much
vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
well, I find myself in a soft brick situation. I cannot get the OTA zip to load from USB, do you happen to have the file as it came or is this it ?
Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
{
"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"
}
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?
Same problem here. VBmeta is giving me a lot of trouble.
Loking foward for a solution...
Hi guys...
Anyone have any luck rooting this f.... android 12 on Samsung M21s? It sucks.
I cant hold it anymore...
A beg a little help .
A want my cell phone back. kkkk
Regards...
.
Hi! When you get that in magisk can you direct install?
ps. I do not have this device but I rooted Samsung so I may be able to help
RodrigoC82 said:
Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
View attachment 5700249
View attachment 5700251
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
View attachment 5700257
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?
Click to expand...
Click to collapse
Can I see the error? It may be because flashing just the ap in the first place shrunk your space.
Hello.
I need help or if anyone was able to fix this error root failed me and SP Flash didn't detect the device after that I searched the internet for my error it gave me and it said it would detect it if I gave it : "remove all+download" I made a copy of security with PBRP of the important sectors of the phone but they are encrypted, when I rebooted the device again I got the error 0x99256658Download not completed.
Looking for information, I need a file called oppo_custom.img from the device but unfortunately I can't find it on the internet.
I wanted to know if anyone has that file or knows someone who could repair it online, even if you have to pay
And if someone was able to solve it, could you help me by telling me how, I currently have another phone in use but I don't want to lose this one.
{
"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"
}
TOLL10 said:
Hello.
I need help or if anyone was able to fix this error root failed me and SP Flash didn't detect the device after that I searched the internet for my error it gave me and it said it would detect it if I gave it : "remove all+download" I made a copy of security with PBRP of the important sectors of the phone but they are encrypted, when I rebooted the device again I got the error 0x99256658Download not completed.
Looking for information, I need a file called oppo_custom.img from the device but unfortunately I can't find it on the internet.
I wanted to know if anyone has that file or knows someone who could repair it online, even if you have to pay
And if someone was able to solve it, could you help me by telling me how, I currently have another phone in use but I don't want to lose this one.
View attachment 5765767
View attachment 5765769
Click to expand...
Click to collapse
Remember that, usually, SPFT don't flash oppo_custom images, you should, need, firstly, edit the scatter file, where it names that partition, and set it from false to true, using some of your oppo_custom images, available on the ofp extracted ROM.
This was just a first attempt, just in case, one of those files can fix the issue.
Going to the next, as the probabilities to find, a specific modded oppo_custom image, specifically for your device, it´s unlikely, then you can pick up from some of the lot of them, available from the net, in case one of them can fix it. It doesn't matter for the model is coming from.
SubwayChamp said:
Remember that, usually, SPFT don't flash oppo_custom images, you should, need, firstly, edit the scatter file, where it names that partition, and set it from false to true, using some of your oppo_custom images, available on the ofp extracted ROM.
This was just a first attempt, just in case, one of those files can fix the issue.
Going to the next, as the probabilities to find, a specific modded oppo_custom image, specifically for your device, it´s unlikely, then you can pick up from some of the lot of them, available from the net, in case one of them can fix it. It doesn't matter for the model is coming from.
Click to expand...
Click to collapse
Thanks for the reply.
I have downloaded several roms and extracted the opf of this model and none of them brings the oppo_custom.img, I tried an oppo_custom that I found on the net but it didn't work, I don't know if when trying to flash the first time the bootloader was closed and SPFT cannot overwrite those partitions, I can't get into the bootloader to confirm it.