Develop Bugs

TWRP 3.0.0-0

Hi,
PLEASE VISIT THE CORRECT AND OFFICIAL THREAD HERE. THIS THREAD WILL NO LONGER BE UPDATED.
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
{
"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"
}
-Jev

Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?

jevtheboss said:
Hi,
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
-Jev
Click to expand...
Click to collapse
Not sure if -i 0x2970 is needed for fastboot think its only for fastboot oem
No need for battery removal there is a fastboot command ........fastboot reboot......... that does the same thing

dnahc said:
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
Click to expand...
Click to collapse
Hi,
Please could you visit the thread here and ask the question there. I think TWRP 3.0.1 will fix the issue. :good: If not, on the TWRP website, 3.0.2 has been released which is supposed to fix some decryption issues so please wait for the thread (the one I linked to earlier) to be updated

Fastbooting android whose recovery is not opening.

While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
{
"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"
}

akshat2119 said:
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
Click to expand...
Click to collapse
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.

vicky romero said:
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
Click to expand...
Click to collapse
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?

akshat2119 said:
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
Click to expand...
Click to collapse
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.

Thank you
vicky romero said:
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Click to expand...
Click to collapse
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader

akshat2119 said:
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
Click to expand...
Click to collapse
Flash this firmware before installing the rom. It'll fix the bootloops.
https://www.androidfilehost.com/?fid=24052804347850305
Thanks @fefifofum for this flashable zip.

i need help to flash twrp recovery on RN5 pro

i just need to flash twrp recovery on my redmi note 5 last miui 11.0.3 android version is 9
i just follow the steps but i didnt flash to twrp recovery when i write the command in adb//
some peoples telling me that the last twrp img recovery contain password or something like this any one can help me

Unlock bootloader first

Re: @wickednight
TWRP is a custom recovery. Flash it need an unlocked bootloader.
If your bootloader is locked, go to https://en.miui.com/unlock/ to apply for unlocking permissions. Download Mi Unlock Tool and proceed to unlock. A waiting period and instruction will then be displayed in Mi Unlock Tool. Use your phone actively during the waiting period.
More information about unlocking: https://c.mi.com/thread-2262302-1-0.html
Once you successfully unlocked the bootloader, in theory, you can flash any file as you want. However, Xiaomi has enabled ANTI_ROLLBACK feature on the Redmi Note 5 (whyred). Check the anti level first so you can choose the right flashing method.
Install all drivers needed on your computer and connect your phone to PC. Hold POWER and VOLUME DOWN for about 11s to enter fastboot mode. Open a command prompt window in the adb tool folder, type this command to check the anti level of your phone:
fastboot getvar anti
Look for the number after "anti:" in output imformation in order to know about the anti level of your phone. The flashing steps is a little different for anti3 devices and anti4 devices.
If the anti level is 3 or lower, you can flash the twrp recovery img file using fastboot command directly. Make sure the twrp img file has been placed in the adb tool folder, and has been renamed to "twrp.img".Type this following command to flash twrp recovery easily:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
If the anti level is 4 or higher, the steps is more complicated. You must bypass the ARB first. Download the whyred-arbpass.img and flash it to antirbpass partition or the ARB will block all your flashing commands. All needed files I will put their links at the end of the post. Type this command to bypass the ARB for one time. You need to use the whyred-arbpass.img to bypass the ARB everytime you want to flash. Make sure the whyred-arbpass.img is placed in the adb tool folder.
Command to bypass ARB and allow you to flash the recovery:
fastboot flash antirbpass whyred-arbpass.img
Check the output, make sure "sending antirbpass" and "writing antirbpass" are all OK. Now you can flash the recovery like anti3's devices:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
All needed files:
1. TWRP recovery img files for whyred:
https://dl.twrp.me/whyred/
2. ANTI_ROLLBACK bypasser file (need to flash it to antirbpass partition):
https://drive.google.com/open?id=1cbHeULrh62R0COSD-RU9OwsWFR2zyfmc
MD5:
{
"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"
}
If you find it useful, please click thanks.

Question Booting GSI's

hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers

stevendeb25 said:
hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers
Click to expand...
Click to collapse
I really don't know much about GSI's, but don't you have to disable AVB before flashing one? Basically disabling vbmeta verification and verity (which would require a factory reset afterwards)? Not sure if you've done or tried this, so just throwing it out there.
{
"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"
}
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com

Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com

Morgrain said:
Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
The bootloader has nothing to do with the bootanimation. If you see the bootanimation, the bootloader has done it's work ages before.

From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Nothing data corrupted
Rebooted back to bootloader
Fastboot reboot recovery
Data reset
=Google logo
Fastboot reboot bootloader
Fastboot flash boot magisk_patched.img
Fastboot reboot
=Bootanimation
ADB ain't enabled in boot.imgs so can't pull logcats to try to see why no boot.
Tried lineage, octativeos, LeOS, phusson, same with all GSI's
P.s phone is intact and easily put back to stock

stevendeb25 said:
From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Click to expand...
Click to collapse
As @Lughnasadh said, it looks like you're missing the disabling of AVB by flashing Google's custom vbmeta.img before installing the GSI image.
Note: If your device has adopted Android Verified Boot (AVB), download and flash the following image to disable AVB before flashing a GSI: vbmeta.img
Click to expand...
Click to collapse
As above, see here: https://developer.android.com/topic/generic-system-image#flash-gsi (blue box).

hi thanks for that, flash vbmeta
still stuck on bootanimation.
i have tried a number of gsi's does this error matter when flashing gsi? "Invalid sparse file format at header magic" still installs fine

Question Stock boot image - Realme GT Master Edition - RMX3363

Hello!
Can somebody provide a stock boot.img file? (current firmware i have installed is stock RMX3363_11_A.13)
Is it possible to use the boot.img from a higher version for rooting via Magisk Manager (without TWRP).
OTA Update doesn't go higher than A.13 version. I can't find a rom for A.13 version online to download. (so i need boot.img from A.13 version if i can't use it from a higher version number)
Thanks for your support!
Edit: I managed to update and don't need the file anymore.
For update see this thread: https://forum.xda-developers.com/t/rmx-3360-3363-full-ota-c-08.4470035/
Many thanks to Przemek212 for posting this.

i have rmx3363 realme gt master edition android 13 f06 update do you have boot.img file and magisk flash patch to do root ? instead of ADB I use bugijaeger with a second smartphone via USB cable.

piotras3566 said:
i have rmx3363 realme gt master edition android 13 f06 update do you have boot.img file and magisk flash patch to do root ? instead of ADB I use bugijaeger with a second smartphone via USB cable.
Click to expand...
Click to collapse
You have to put .img files into phone, install Magisk-25.2.apk, patch .img files with Magisk then flash .img patched files with fastboot.

Robro86 said:
Hello!
Is it possible to use the boot.img from a higher version for rooting via Magisk Manager (without TWRP).
Click to expand...
Click to collapse
No, you have to use the stock .img files from your installed ROM. You can find A13 ROM here : https://androidfilehost.com/?fid=15664248565197202925, but I don't know if that's the correct ROM for you so use at your own risk !

So I can flash boot.img via magisk and from older Android 12 even though I have Android 13 F06 now and then this file RMX3363_F06_IMG-TO-PATCH.tar.gz flash to fastboot via CMD fastboot flash RMX3363_F06_IMG-TO-PATCH.tar. gz
???

piotras3566 said:
So I can flash boot.img via magisk and from older Android 12 even though I have Android 13 F06 now and then this file RMX3363_F06_IMG-TO-PATCH.tar.gz flash to fastboot via CMD fastboot flash RMX3363_F06_IMG-TO-PATCH.tar. gz
???
Click to expand...
Click to collapse
you need to extract boot.img from Full OTA, fix in Magisk and install via fastboot.

piotras3566 said:
So I can flash boot.img via magisk and from older Android 12 even though I have Android 13 F06 now and then this file RMX3363_F06_IMG-TO-PATCH.tar.gz flash to fastboot via CMD fastboot flash RMX3363_F06_IMG-TO-PATCH.tar. gz
???
Click to expand...
Click to collapse
NO ! Sorry, but I don't think you've mastered the rooting procedure...
In the tar.gz archive, you'll find original stock F06 boot.img and vendor_boot.img + Magisk-25.2.apk. You have to install Magisk, patch the 2 img files with Magisk on your phone, then copy patched img files to your PC and flash them using fastboot (only if you have Android 13 F06 installed on your phone !) :
fastboot flash boot patched-by-magisk-boot.img
fastboot flash vendor_boot patched-by-magisk-vendor_boot.img
(But if you don't really understand what you are doing, don't do it)

{
"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 extracted this 51mb file and there are 3 files

piotras3566 said:
I extracted this 51mb file and there are 3 files
Click to expand...
Click to collapse
Ok. Install Magisk then patch the img files

these are 2 files patched and I have to flash them via fastboot?

piotras3566 said:
these are 2 files patched and I have to flash them via fastboot?
Click to expand...
Click to collapse
Yes, as mentioned above

what fastboot command in cmd? fastboot flash boot file name ?

piotras3566 said:
what fastboot command in cmd? fastboot flash boot file name ?
Click to expand...
Click to collapse
I posted the commands at 1:23PM. Replace "patched-by-magisk-boot.img" and "patched-by-magisk-vendor_boot.img" with your correct names.

still please make TWRP work for rmx3363. the marmalade is not working properly

piotras3566 said:
still please make TWRP work for rmx3363. the marmalade is not working properly
Click to expand...
Click to collapse
Sorry but I don't use TWRP (I'm on lunaa LOS recovery which works perfectly for RMX3363) and you're off topic (rooting via Magisk).

one question befor i start flashing the patched files i must do this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
i am on Original Realme firmware and only want root.

unfortunately, rmx3363 has become a brick and is bricked, go to the realme logo and enter the fastboot state. is the realme repair tool?