[Recovery][OFFICIAL][UBL] TWRP 3.5.0 Touch Recovery for Xperia T/TX/V

[Recovery][OFFICIAL][UBL] TWRP 3.5.0 Touch Recovery for Xperia T/TX/V - Sony Xperia T, TL, TX, V

{
"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"
}
TWRP 3.5.0 - Based upon Android 6.0 :
* Whole new TWRP 3 interface
* Flashable to FOTA for permanent recovery
* Bootable recovery image if required
OFFICIAL DOWNLOADS FOR XPERIA BLUE :
https://twrp.me/sony/sonyxperiat.html
https://twrp.me/sony/sonyxperiatx.html
https://twrp.me/sony/sonyxperiav.html
twrp-3.x.x-x-x.img : Official TWRP image
How to install : All informations available on TWRP.me
DEVELOPMENT DOWNLOADS FOR MINT (Xperia T) :
https://mega.nz/#F!3t0yyCia!HjUIl4o_TnOSWZzq3uWV1g
twrp-3.x.x-x-fota-mint.zip : Flashable TWRP 3 to FOTA installer
twrp-3.x.x-x-boot-mint.img : Fastboot bootable TWRP 3 image
cleaner-fota-mint.zip : Flashable FOTA formatter (optional)
DEVELOPMENT DOWNLOADS FOR HAYABUSA (Xperia TX) :
https://mega.nz/#F!egUHyCKQ!W-DNbBzdz1_OEatVQuuk0A
twrp-3.x.x-x-fota-hayabusa.zip : Flashable TWRP 3 to FOTA installer
twrp-3.x.x-x-boot-hayabusa.img : Fastboot bootable TWRP 3 image
cleaner-fota-hayabusa.zip : Flashable FOTA formatter (optional)
DEVELOPMENT DOWNLOADS FOR TSUBASA (Xperia V) :
https://mega.nz/#F!71EGkRpY!B3PQP3GjL8H-AMeR-XfwFw
twrp-3.x.x-x-fota-tsubasa.zip : Flashable TWRP 3 to FOTA installer
twrp-3.x.x-x-boot-tsubasa.img : Fastboot bootable TWRP 3 image
cleaner-fota-tsubasa.zip : Flashable FOTA formatter (optional)
HOW TO INSTALL EASILY TO FOTA :
Installing to FOTA will make it "permanent" and kept with ROM flashes
* (Optional) : Download the TWRP bootimage and flash it to boot
fastboot flash boot twrpfilename.img
* Boot to recovery : Enter the Recovery as usual
* Flash to FOTA : Install the TWRP FOTA zip
* (Optional) : Flash the ROM you want
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push /path/to/recovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
ABOUT THE USERDATA UNIFICATION :
Due to the unification, you will see 3 partitions in Mount.
* Data is the "UserData" partition, used for apps and user settings
* Internal storage is a portion of the "UserData" partition, used for medias
* Legacy SDCard is the old "Internal Storage", to support and access old ROMs
INFORMATIONS ABOUT TWRP 3 :
* Installation : Only flash the zip with a working TWRP or CyanogenRecovery
* Known issues : No major issue remaining, but sources open to improvements
* Usage : Built for Marshmallow, works for Lollipop based ROMs too
* More here : http://www.xda-developers.com/twrp-3-0-0-has-arrived/
ADDITIONAL LINKS :
* Easy ADB and Fastboot for unexperienced users :
http://forum.xda-developers.com/showthread.php?p=48915118
Thanks to the TWRP Team
Current local manifest of the TWRP build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/AdrianDC/twrp_development_sony -->

wow nice with material style :good:

Adrian DC said:
TWRP 3.0.0 - Based upon Android 6.0.0 :
Click to expand...
Click to collapse
Hey Adrian,
When you get a chance could you bump the TWRP blue build up to 3.0.2? There were all sorts of buglets in all the first 3.0 release. But 3.0.2 now works great with your SP builds
Thanks for all your work on the Sony stuff,
KC

Done !

Adrian DC said:
Done !
Click to expand...
Click to collapse
Could I get some instructions on how to install this on a stock device?

Adrian DC said:
Done !
Click to expand...
Click to collapse
It's working on Xperia T just fine I think. I flashed few zip fixes and gapps and that went fine. I haven't tried to flash a ROM so I don't know if it's ok, or it will show up some error like that error 7

A new more official release specific to the devices will be coming soon but I need to confirm they work for the moment.

I've tried to install this for Xperia T (mint), running with the final cm12.1 build of WhiteNEO, but unfortunately neither flashing the twrp.img via fastboot flash recovery, nor flashing the zip via twrp succeeded.

All three devices are now considered working fine with TWRP 3.0.2
so I invite you to test it all on your own device.
Bootimage is fully bootable and usable.
FOTA fully working too, if your current ROM doesn't support it,
know CM13 new releases will soon.

New releases for all 3 devices, stable & considered fully ready.
TWRP (and MultiROM TWRP) upgraded, like CyanogenRecovery, for proper performance and heat control.

Hi guys. have downloaded the twrp3 Tsubasa for my xv device. Now I want to install them.my android version is 4.3 JB with 9.2.A.2.5 built number.
Can you plz explain the installation step by step, or a video tutorial.???
it's my first time I don't know what to do at all.
I really need help.
And by the way how can I reboot into twrp3 recovery after the installation finished? Tnx
By the way my device doesn't reboot into recovery cwm or twrp. I don't know the reason.
Reply sooner please

Some body answer please.
My android version is 4.3 JB can i install this twrp3 on my device????

Younes_vd said:
Some body answer please.
My android version is 4.3 JB can i install this twrp3 on my device????
Click to expand...
Click to collapse
Read man... Read!!! - http://forum.xda-developers.com/showthread.php?t=2090268 This topic on XDA are pinned so people can see them and read them before posting everywhere

krasimiretov said:
Read man... Read!!! - http://forum.xda-developers.com/showthread.php?t=2090268 This topic on XDA are pinned so people can see them and read them before posting everywhere
Click to expand...
Click to collapse
i have already unlocked my bootloader .so you read and see what i have asked for
---------- Post added at 06:35 AM ---------- Previous post was at 06:33 AM ----------
im askimg if it is possible to install twrp3 on xv with 4.3 jb android .

Younes_vd said:
i have already unlocked my bootloader .so you read and see what i have asked for
---------- Post added at 06:35 AM ---------- Previous post was at 06:33 AM ----------
im askimg if it is possible to install twrp3 on xv with 4.3 jb android .
Click to expand...
Click to collapse
Download the .img file from OP and flash it with Flashtool(fastboot). its meant to use on MM or LP if you consider using it.

krasimiretov said:
Download the .img file from OP and flash it with Flashtool(fastboot). its meant to use on MM or LP if you consider using it.
Click to expand...
Click to collapse
ok thank you
---------- Post added at 07:10 AM ---------- Previous post was at 06:42 AM ----------
krasimiretov said:
Download the .img file from OP and flash it with Flashtool(fastboot). its meant to use on MM or LP if you consider using it.
Click to expand...
Click to collapse
hey are you there i installeed a twrp recovery now when i turn on my phone it directly goes into twrp. how shoud i reboot into system ???
in twrp i press reboot into system but again it goes into recovery menu .whats wromg?
---------- Post added at 07:29 AM ---------- Previous post was at 07:10 AM ----------
i cant boot into system help me plz.
i have a custom rom 5.5.9 in my sdcard if i install that via twrp, will my phone load up into system insteead twrp or not .
im waiting

Latest build is working without any problems, I already flashed your last CM13 build +gapps with it

@Adrian DC: You've build this using Omni 6.0, not CM-13.0 - right?

I tried rebuilding the Recovery for the Xperia V on a Debian8 system using the minimal omni build tree from here and the local_manifest posted by Adrian DC in the OP.
When trying to make the bootimage target, I run into the following build error:
Code:
Install: /home/defier/twrp-test/twrp/out/target/product/tsubasa/root/init
Target ram disk: /home/defier/twrp-test/twrp/out/target/product/tsubasa/ramdisk.img
/bin/bash: / 2048 * (2048+64): syntax error: operand expected (error token is "/ 2048 * (2048+64)")
Target boot image: /home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img
/bin/bash: (((21626880 / 100) - 1) / img_blocksize + 1) * img_blocksize: division by 0 (error token is "img_blocksize + 1) * img_blocksize")
build/core/Makefile:580: recipe for target '/home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img' failed
make: *** [/home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img] Error 1
make: *** Deleting file '/home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img'
#### make failed to build some targets (02:32 (mm:ss)) ####
I tried removing squashfstools, replacing them with a newer version and other things, but the issue still persists. Can someone help me, please?

Hi
Can someone explain what the cleaner does what is its purpose and how to use safely in Twrp?

Related

[MOD][UNOFFICIAL] MultiROM v31 [WIP] [UNDER PROGRESS]

Reserved

I have Many questions...
Works with Multirom TWRP 2.7.1?
Boot Lollipop ROM's?
Need to reflash hardboot kernel?
Thanks

Need Testing
SrDesalmado said:
I have Many questions...
Works with Multirom TWRP 2.7.1?
Boot Lollipop ROM's?
Need to reflash hardboot kernel?
Thanks
Click to expand...
Click to collapse
I have not used this MultiROM v31 with MultiROM TWRP 2.7.1.1.
I tested with a KitKat ROM. Now making a lollipop ROM especially for testing this MultiROM and for the ROM itself.
This was built based on the latest kernel that was used to boot cm-12.0 for our device. You needn't reflash hardboot kernel.
But if you get something wrong, use the uninstaller and let me know the log. It will help me fix the problem.

Is tested on soak test 5.0.2 and CM12
I want to keep disk test 5.0.2 and CM12 will this multirom work....

Yaay! Nice and keep it up! Gonna try it in couple of hours.

Well, works with MultiROM TWRP 2.7.1 :good:
Didn't need to flash hardbood hexec kernel :good:
But... Unfortunately won't boot up Lollipop ROM's, i got "error executing update binary" on installation process... I think it isn't a MultiROM problem, but a outdated Recovery... I will test with new recovery later...
---------- Post added at 07:22 PM ---------- Previous post was at 06:26 PM ----------
Tested with new TWRP 2.8.5.0 and nope, it's really a MultiROM incompatibility with lollipop mounts, i think...

SrDesalmado said:
Well, works with MultiROM TWRP 2.7.1 :good:
Didn't need to flash hardbood hexec kernel :good:
But... Unfortunately won't boot up Lollipop ROM's, i got "error executing update binary" on installation process... I think it isn't a MultiROM problem, but a outdated Recovery... I will test with new recovery later...
---------- Post added at 07:22 PM ---------- Previous post was at 06:26 PM ----------
Tested with new TWRP 2.8.5.0 and nope, it's really a MultiROM incompatibility with lollipop mounts, i think...
Click to expand...
Click to collapse
Well, it should be ROM problem I think. Can you give me link to the ROM you wanna flash?

GeekyDroid said:
Well, it should be ROM problem I think. Can you give me link to the ROM you wanna flash?
Click to expand...
Click to collapse
Here you go
CM12 by percy_g2
And
Stock Debloated TWRP Nandroid
And that's it, i think these is only lollipop based ROM's avaliable for install on MultiROM for now... I tested both ROMs and nope, but if you want try

Well seems Good but I have an question.. Different between previous one ? And one thing more our internal storage is way too low for mutirom using don't know who can help us !

rajit said:
Well seems Good but I have an question.. Different between previous one ? And one thing more our internal storage is way too low for mutirom using don't know who can help us !
Click to expand...
Click to collapse
May be installation to SD card help us...
Sent from my XT1022 using xda premium

Problem no touch
#buzz said:
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch (will be there in future ) or Desktop alongside with Android, without the need of device formatting
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. First Flash MultiROM zip via Recovery [Link Given Below]
2. Reboot to bootloader
3. Fastboot MultiROM TWRP Recovery (Terminal Command "fastboot flash recovery twrp2.8.5.0-multirom-recovery.img" ) [Link Given Below]
4. Reboot recovery.
Bugs: Layout Problems (Will be fixed soon)
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.4 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Downloads
MULTIROM v31: https://mega.co.nz/#!QVJzHYCQ!XXc5o1MrCoE-y9qbmvcNqB5ZkXR1Nkadaxf2s-qQrP4
https://www.dropbox.com/s/p9ed2oi4bql0pu7/multirom-20150217-v31-UNOFFICIAL-condor.zip?dl=0
TWRP MULTIROM RECOVERY: https://mega.co.nz/#!sdRzQLhK!k3d2qgY72q9Rh7bZbG6a-zcWZbJbPpnrbbOygDNZfZw
https://www.dropbox.com/s/tf7zbgjwzp531mu/twrp2.8.5.0-multirom-recovery.img?dl=0
UNINSTALLER: https://mega.co.nz/#!4BxznIib!c4m7HOO5Z4HCsZDfdQrxkxXI9mgYujbnadTAdvIb_J0
https://www.dropbox.com/s/k83bhaponxlci01/multirom_uninstaller.zip?dl=0
XDA:DevDB Information
MultiROM v31, Tool/Utility for the Moto E
Contributors
#buzz, percy_g2
Source Code: https://github.com/percy-g2?tab=repositories
Version Information
Status: Testing
Created 2015-02-17
Last Updated 2015-02-17
Click to expand...
Click to collapse
MultiROM v28 installed and was working normally after updated to v31 and did not install any rom and I have more in touch roms menu, then unistall and went back to using the v28 , but still continue without the touch , how to fix it ? I can no longer use the MultiROM or uninstalling and reinstalling .
I do not know English and I'm using google translator , excuse me errors .

Solution
Layker25 said:
MultiROM v28 installed and was working normally after updated to v31 and did not install any rom and I have more in touch roms menu, then unistall and went back to using the v28 , but still continue without the touch , how to fix it ? I can no longer use the MultiROM or uninstalling and reinstalling .
I do not know English and I'm using google translator , excuse me errors .
Click to expand...
Click to collapse
Goto fastboot mode and flash the twrp 2.8.5.0 recovery and use it to flash the Multirom uninstaller first, do some wipes of caches and then (if you want), then install it again. If you have any trouble, feel free to PM me anytime.

installed as told, already have pac rom installed, tried installing a secondary rom but failed message came, any idea what went wrong?

#buzz said:
Goto fastboot mode and flash the twrp 2.8.5.0 recovery and use it to flash the Multirom uninstaller first, do some wipes of caches and then (if you want), then install it again. If you have any trouble, feel free to PM me anytime.
Click to expand...
Click to collapse
I found out what was the problem of v28 , was the kernel that was not installed, but the v31 not figured out , I could do the work again v28 v31 but not , so I can not install any rom the v31 and v28 can not install roms up version 4.4.x as a second rom , know how to solve this problem?
Thank you in advance !

@#buzz
coping zip to /tmp...
erasing incomplete rom
tried to install cm11 :/ please help me not abloe to install on external

Links Not Working...
#buzz said:
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch (will be there in future ) or Desktop alongside with Android, without the need of device formatting
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. First Flash MultiROM zip via Recovery [Link Given Below]
2. Reboot to bootloader
3. Fastboot MultiROM TWRP Recovery (Terminal Command "fastboot flash recovery twrp2.8.5.0-multirom-recovery.img" ) [Link Given Below]
4. Reboot recovery.
Bugs: Layout Problems (Will be fixed soon)
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.4 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Downloads
MULTIROM v31: https://mega.co.nz/#!QVJzHYCQ!XXc5o1MrCoE-y9qbmvcNqB5ZkXR1Nkadaxf2s-qQrP4
https://www.dropbox.com/s/p9ed2oi4bql0pu7/multirom-20150217-v31-UNOFFICIAL-condor.zip?dl=0
TWRP MULTIROM RECOVERY: https://mega.co.nz/#!sdRzQLhK!k3d2qgY72q9Rh7bZbG6a-zcWZbJbPpnrbbOygDNZfZw
https://www.dropbox.com/s/tf7zbgjwzp531mu/twrp2.8.5.0-multirom-recovery.img?dl=0
UNINSTALLER: https://mega.co.nz/#!4BxznIib!c4m7HOO5Z4HCsZDfdQrxkxXI9mgYujbnadTAdvIb_J0
https://www.dropbox.com/s/k83bhaponxlci01/multirom_uninstaller.zip?dl=0
XDA:DevDB Information
MultiROM v31, Tool/Utility for the Moto E
Contributors
#buzz, percy_g2
Source Code: https://github.com/percy-g2?tab=repositories
Version Information
Status: Testing
Created 2015-02-17
Last Updated 2015-02-17
Click to expand...
Click to collapse
Links are not working. Please Update Them...

meakshay_mishra said:
Links are not working. Please Update Them...
Click to expand...
Click to collapse
No Issue with Download Link..Its working..
If you are accessing from mobile then Try "Request Desktop Site" option :good:

Links Need to be Checked.
mrpkarthik said:
No Issue with Download Link..Its working..
If you are accessing from mobile then Try "Request Desktop Site" option :good:
Click to expand...
Click to collapse
I Think that'as not true. I tried opening on desktop and on browser requesting desktop site. Still not working Links.
See screenshot.

meakshay_mishra said:
I Think that'as not true. I tried opening on desktop and on browser requesting desktop site. Still not working Links.
See screenshot.
Click to expand...
Click to collapse
Check my screenshot.. No issues with Download LINK

[EXPERIMENTAL][TESTING][29-3-17] MultiRom Latest For kenzo/kate

{
"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"
}
For kenzo/kateSupports all Roms (SHOULD)
NOTE:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this Kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
What is MultiRom?
MultiRom is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiRom can boot from USB drive connected to the device via OTG cable. The main part of MultiRom is a boot manager, which appears every time your device starts and lets you choose ROM to boot. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiRom even has its own installer system, which can be used to ship other Linux-based systems.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
Test and Report
SUPPORTED DEVICES:
kenzo
kate
Please Test it in other Similar SD Variants and Report it Below.
Bugs:
You tell me
SCREENSHOTS:
All Screenshots HERE
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:This is the easiest way to install everything MultiRom needs... Just follow the Below Instructions:
Install the app (Links Below)
Select MultiRom and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
DONE! MULTIROM IS READY TO ROCK!
You current rom will not be erased by the installation.
Download link is in the second post.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.
Updating/changing ROMs:
1. Primary Rom (Internal)
Flash Rom's zip File as Usual, Do factory reset if needed (it won't erase secondary Roms)
Go to MultiRom in recovery and do Inject curr. boot sector.
2. Secondary Android Roms
If you want to change the Rom, delete it and add new one. To update the Rom, follow these steps:
Go to MultiRom -> List Roms and select the Rom you want to update.
Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Download something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam Kernel), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.
GitHub Source Codes:
MultiRom Organization for Xiaomi DevicesKenzo/Kate MultiRom Device TreesMultiRom Manager App Source Codes
Current Status:
Test and Report...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to kenzo/kate
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, IN TESTING, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For kenzo/kate, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-xiaomi
Version Information
Status: Testing
Current Beta Version: v33
Beta Release Date: 2017-03-29
Created 2017-03-29
Last Updated 2017-03-30

1.Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4

Download Links:
MultiRom Manager App 2.4-rishabhrao

Guys please test this in your Kenzo/Kate and Please tell me how it works

Will it work on 16 gb

pdpmoto said:
Will it work on 16 gb
Click to expand...
Click to collapse
All devices which support TWRP 3.1 official for kenzo or kate should definitely support this
Well try it out, definitely won't harm your device....
Also, uninstaller inckuded
Sent from my LeEco Le 2 using XDA Labs

Will test after exam
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Everything is ok as of now twrp flashed but will check more if i am in my town because If something go wrong then i will fix with my pc

Does it support the sailfish os?

Is f2fs supported?
Because I can't inject current boot sector

Anyone know if MIUI works?

Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....

SMYM said:
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
Click to expand...
Click to collapse
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Sent from my LeEco Le 2 using XDA Labs

午夜听雪 said:
Does it support the sailfish os?
Click to expand...
Click to collapse
try it !

Rishabh Rao said:
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Click to expand...
Click to collapse
I can't add any rom and the mltrm menu hasn't been shown up...

SMYM said:
I can't add any rom and the mltrm menu hasn't been shown up...
Click to expand...
Click to collapse
Let me check it out once...
EDIT: Can anyone try on some Rom other than miui?
So i can get a sure idea if it's a problem only with Miui or with all Roms...
Sent from my LeEco Le 2 using XDA Labs

I tried installing a few different ROMs and it always gave an error..
Hope this helps

Doesn't seem it is able to install roms to the sd card

4I-I said:
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Click to expand...
Click to collapse
I have exactly the same error...

SMYM said:
I have exactly the same error...
Click to expand...
Click to collapse
Download links

[email protected] said:
Download links
Click to expand...
Click to collapse
Download via the app attached to first post

[Official][RECOVERY][tissot] TWRP 3.2.1-2 (Oreo)touch recovery [2018-03-06]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
What's new in 3.2.1-1:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
What's new in 3.2.0-0:
* Allow restoring adb backups in the TWRP GUI (bigbiff)
* Fix gzip backup error in adb backups (bigbiff)
* Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
* Better support for installing Android 8.0 based zips due to legacy props (nkk71)
* Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
* Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
* Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
* v2 fstab support (Dees_Troy)
* Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
* Various other minor bugfixes and tweaks
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
whats working?
[*]All paritions are mounting
[*] Can change Slot A/ Slot B on twrp its self
[*]Everything as usual.. (Backup/restore)
[*]recovery booting after rebooting to system also
[*]sdcard working
[*] USB-OTG working
[*] Add system_image mount point to flash system images
[*] Add update_engine_sideload
Instructions:
Steps:
Download required files from downloads
Unlock your bootloader( u must be unrooted)
Reboot to bootloader
fastboot boot recovery-xx.img
Boot into Recovery
Change Partition slot using twrp[Reboot--> Change_Slot]
(for example, if you're in slot A, change it to Slot B and Vice versa)
flash twp-installer.zip
Flash Magisk{Use Latest} for Root Access(If Neccessary)
Success
Workaround: As pixel devices come up with A/B partition, its quite similar to our device and we use of them to get root access.
thanks to @goodwin_c and @ravinder0003 for testing
Kernel Source :
tissot
Downloads :
For Nougat:
recovery-3.1.1-1
twrp-Installer
recovery-3.2.1-1
twrp-3.2.1-1-installer
For Oreo:
recovery-3.2.1-2-oreo
Twrp-recoveryInstaller-3.2.1-2-oreo.zip
Special thanks to :good:
 @Dees_Troy and Twrp Team
 @topjohnwu
 @ravinder0003
 @talk2indrajit
 @Rohan Taneja
 @subhujoshi007
 @goodwin_c
 @mohancm
Note:
1. Don't flash it via fastboot , just boot into it.
2. if accidentally flashed via fastboot, flash stock boot.img
XDA:DevDB Information
[Official][RECOVERY][tissot] TWRP 3.2.1-2 (Oreo)touch recovery [2018-03-06], Tool/Utility for the Xiaomi Mi A1
Contributors
mohancm
Source Code: https://github.com/mohancm100
Version Information
Status: Stable
Current Stable Version: v1.2
Stable Release Date: 2018-03-06
Created 2017-10-14
Last Updated 2018-03-06

Reserved
twrp v1.1
Changelog:
added A/B OTA updater support
corrected mount point regarding system partition
you can set Slot A/ Slot B on twrp itself
twrp v1.2
Changelog:
sdcard working
USB-OTG working
Add system_image mount point to flash system images

Reserved

Finally something official...
Thanks a lot dear...

Will flashing installer via flashify result in a working recovery (as an alternative to method described above)?

Are there some boot combinations to boot straight into twrp?
I've tried vol up+power, there's only text ,,no command"...

Not working.... Stuck on the bootloop

Vatumb said:
Not working.... Stuck on the bootloop
Click to expand...
Click to collapse
the same here..... follow the instruction but cannot enter the OS, keep entering twrp every time tried to reboot....

@mohancm
Great work bro
Do u own a a1 or u builded via testers...

antimatter.web said:
Will flashing installer via flashify result in a working recovery (as an alternative to method described above)?
Click to expand...
Click to collapse
Flash installer only via twrp

Vatumb said:
Not working.... Stuck on the bootloop
Click to expand...
Click to collapse
Follow the instructions properly!!

mohancm said:
Follow the instructions properly!!
Click to expand...
Click to collapse
Done the same as per the instruction.
fastboot boot recovery.img
done
flashed the TWRP zip file
Reboot
and Stuck in the Bootloop

Oves786 said:
@mohancm
Great work bro
Do u own a a1 or u builded via testers...
Click to expand...
Click to collapse
I bought A1 recently, still bootloader locked
I tested via testers

Wow..after k4, now A1
Good job mohan

cool mate i too hav a a1 but its my bro's
u can easilty unlock it as it uses fast boot google method to get unlocked
so not mi verification i own a redmi note 4
and im a samsung j7 16 dev porter
still unknows to mi port source stuff
---------- Post added at 04:03 AM ---------- Previous post was at 04:02 AM ----------
Vatumb said:
Done the same as per the instruction.
fastboot boot recovery.img
done
flashed the TWRP zip file
Reboot
and Stuck in the Bootloop
Click to expand...
Click to collapse
try booting twrp if suceedded format data in twrp and flash magisk and see up

Vatumb said:
Done the same as per the instruction.
fastboot boot recovery.img
done
flashed the TWRP zip file
Reboot
and Stuck in the Bootloop
Click to expand...
Click to collapse
flash twrp zip with boot_b partition
it triggers

Oves786 said:
cool mate i too hav a a1 but its my bro's
u can easilty unlock it as it uses fast boot google method to get unlocked
so not mi verification i own a redmi note 4
and im a samsung j7 16 dev porter
still unknows to mi port source stuff
---------- Post added at 04:03 AM ---------- Previous post was at 04:02 AM ----------
try booting twrp if suceedded format data in twrp and flash magisk and see up
Click to expand...
Click to collapse
Magisk not working for me.... Some Error 7
---------- Post added at 09:43 AM ---------- Previous post was at 09:41 AM ----------
mohancm said:
flash twrp zip with boot_b partition
it triggers
Click to expand...
Click to collapse
How??

vatumb said:
magisk not working for me.... Some error 7
---------- post added at 09:43 am ---------- previous post was at 09:41 am ----------
how??
Click to expand...
Click to collapse
detail eror or pic

mohancm said:
flash twrp zip with boot_b partition
it triggers
Click to expand...
Click to collapse
do you means to flash it to the active partition? or it has to be boot_b partition?

Oves786 said:
detail eror or pic
Click to expand...
Click to collapse

[RECOVERY][Realme 6 Pro] TWRP Recovery [Stable]

Reserved

Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done

Richardo87 said:
The same issue i was getting with the previous TWRP versions, cannot access MTP storage. Also while phone on, cannot copy anything on storage.
Click to expand...
Click to collapse
Please provide screenshots of your problem. I assume that you are trying to copy files to an encrypted internal storage. Decrypt /data or copy files to SD card

Is this compatible with build number RMX2061_11_A.35? Thank you!
Sent from my RMX2061 using XDA Labs

ByinAlbirt said:
Is this compatible with build number RMX2061_11_A.35?
Click to expand...
Click to collapse
Yes

Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
No need i guess. Try 'Disable Replace TWRP' and reboot ...

debdeep98 said:
Yes
Click to expand...
Click to collapse
Thank you so much! I have successfully installed TWRP Recovery in my realme 6 Pro build number RMX2061_11_A.35.
Sent from my RMX2061 using XDA Labs

Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
All you need is vbmeta.img from your stock ROM.
I used above instructions and everything work just fine, including decryption of internal storage.
@Kevin Saiza thank you for your good work.
Everything's working as expected.
Right now I'm using:
Firmware A.35
LR.TWRP 3.4.1B_30.09
Magisk 21.0 (pass safety net check)

Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!

Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!

neoxcool said:
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Click to expand...
Click to collapse
Coming Soon

Andres88z said:
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
Click to expand...
Click to collapse
Yes why not .

Kevin Saiza said:
Yes why not .
Click to expand...
Click to collapse
Some problem with RMX2063. You try whit RMX2061
Sorry Is 2063
thank's

LR.TWRP 3.4.2B_05.10 for RMX2061 Ported from Xiaomi Black Shark 3 by Ctapchuk & logotoy73
Change extention to .img
https://anonfiles.com/hfcehcd1p9/LR.TWRP_3.4.2B_05.10_for_RMX2061_img
Changelog:
• Port from Xiaomi Black Shark 3
• Upgrade to version 3.4.2
• Fixes in Russian language
• Changed the font for English language
• Fixed fastbootd
• A/B table selection Disabled
• Correct display of the status bar

If i only boot, i need flash vbmeta?

I need urgent help please the twrp does not recognize my otg it only recognizes the sd but the otg does not what should I do to make it recognize it please help

:good:

Can't delete file from phone with root explorer so i tried with TWRP as usualy and for the first time IT DOESNT WORK!! Never seen that before. Though system's not mounted as read only. What to do..?

Do nothing. vendor, product and system partitions are R/O, because they are part of new type partition named "super". It is dynamic partition that is not editable.
Take a look here for details
Implementing Dynamic Partitions | Android Open Source Project
source.android.com

[RECOVERY][OFFICIAL]PitchBlack Recovery v3.1.0 [m21]

{
"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 to expand...
Click to collapse
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
- Based on TWRP version: 3.5.2
- PitchBlack version: 3.1.0
- Maintainer: Nazim @naz664
- For device: M21/M215f
- PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject/manifest_pb
- Device tree: https://github.com/PitchBlackRecoveryProject/android_device_samsung_m21-pbrp
- Kernel tree:
https://github.com/naz664/android_kernel_samsung_m21
- PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
- Fully native android like UI
- Up-to-date kernel, built from sources
- Full dark theme with changeable accents
- Reorganized menus
- Disable DM Verity
- Use AromaFM as default file manager
- Various tools are included
- Many bug fixes & optimization & much more
Installation Instructions
From previous version or other recovery
- Download the PitchBlack zip to your device
- Reboot to your current custom recovery
- Flash the PitchBlack zip
- After installation reboot the recovery
- Enjoy
* If you are getting vbmeta error flash null vbmeta
From PC
- Download PitchBlack Recovery flashable zip from bellow
- Extract the PBRP zip
- Tar the recovery file and flash via odin in Ap block
- Enjoy
changelog
PBRP Side Changelog
Code:
v3.1.0
- Bump to 3.1.0
- Based on TWRP 3.5.1
- Redesigned homescreen
- Fixed minor glitches
- Added more languages support
Device Side Changelog
Code:
- Initial release
- Added support to directly flash images in logical partition
- Added dtbo,vbmeta partition backup and restore support
- Disabled dm verity by default
- Fixed MTP
- Fixed flashlight
Credits:
- @Yilliee for the base tree
- @Chaitanya_Yeranagula and PBRP team for all your help
- And all the testers for their reports
Downloads
Samsung Galaxy M21 | m21 - PitchBlack Recovery Project
PBRP Version: 3.1.0 Maintainer: Nazim
pitchblackrecovery.com

Nice job!!

Awesome work dev!

Clutchmaster_OP said:
Nice job!!
Click to expand...
Click to collapse
Thankz bro

Daniel~007 said:
Awesome work dev!
Click to expand...
Click to collapse
Thankz

Tried to flash (both trough TWRP & Tar file flash) but booting into Download Mode only. Its for M21/M215F, is that why its not working on M215G?
Its showing some red error msg like Custom Binary Invalid & vbmeta, something like that.

OldNoobOne said:
Tried to flash (both trough TWRP & Tar file flash) but booting into Download Mode only. Its for M21/M215F, is that why its not working on M215G?
Its showing some red error msg like Custom Binary Invalid & vbmeta, something like that.
Click to expand...
Click to collapse
Try flashing null vbmeta via Ap block of odin

naz664 said:
Try flashing null vbmeta via Ap block of odin
Click to expand...
Click to collapse
Same error repeats :
ODIN MODDE (AVB Fail)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
I even tried flashing another vbmeta zip file (906kb) which had worked before during flashing GSI but even after that I got same error.

OldNoobOne said:
Same error repeats :
ODIN MODDE (AVB Fail)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
I even tried flashing another vbmeta zip file (906kb) which had worked before during flashing GSI but even after that I got same error.
Click to expand...
Click to collapse
Flashing gsi doesn't need null vbmeta.
* Extract the zip
* Flash recovery.img into recovery partition using any other recovery
* And check if ure getting vb meta error or not
If yes try flashing the vbmeta file i attached before
* If the problem still persist contact me on telegram @naz664

naz664 said:
Flashing gsi doesn't need null vbmeta.
* Extract the zip
* Flash recovery.img into recovery partition using any other recovery
* And check if ure getting vb meta error or not
If yes try flashing the vbmeta file i attached before
* If the problem still persist contact me on telegram @naz664
Click to expand...
Click to collapse
1) Actually null vbmeta was the issue I was facing on SM-M215G (while flashing GSI) and as per Dev GuruPrasadAH, he gave me null vbmeta file which solved the problem and after that GSI booted.
2) I already had done that, when i had flashed recovery img to recovery partition, same error was showing.
3) Now the phone only boots to download mode, so I think I should flash stock ROM again.

OldNoobOne said:
1) Actually null vbmeta was the issue I was facing on SM-M215G (while flashing GSI) and as per Dev GuruPrasadAH, he gave me null vbmeta file which solved the problem and after that GSI booted.
2) I already had done that, when i had flashed recovery img to recovery partition, same error was showing.
3) Now the phone only boots to download mode, so I think I should flash stock ROM again.
Click to expand...
Click to collapse
Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664

Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH

GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
Click to expand...
Click to collapse
GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Does that recovery working for you ?

naz664 said:
Does that recovery working for you ?
Click to expand...
Click to collapse
As stupid as this may sound, I dont have the phone anymore. Upgraded to redmi note 10 pro max. But, I do have some experience and can help out after honework and classwork.
I'm not a leech who spampings for eta lol

GuruPrasadAH said:
As stupid as this may sound, I dont have the phone anymore. Upgraded to redmi note 10 pro max. But, I do have some experience and can help out after honework and classwork.
I'm not a leech who spampings for eta lol
Click to expand...
Click to collapse
Ooh kk can anyone confirm that ?

naz664 said:
Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664
Click to expand...
Click to collapse
Thanks no problem naz664

GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Oh Dev GuruPrasadAH, nice to meet you again
My phone only booting to Download Mode , so after I restore from backup I will have ADB access again then i'll run the above command and paste it here.

OldNoobOne said:
Thanks no problem naz664
Click to expand...
Click to collapse
Unified orangefox recovery for exynoss9611 working for you ?

naz664 said:
Unified orangefox recovery for exynoss9611 working for you ?
Click to expand...
Click to collapse
OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad

OldNoobOne said:
OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad
Click to expand...
Click to collapse
Ok thankz for the report.
I used ofox tree as base if it didn't boot then no hope for this one too lol

Database Develop

welcome