Develop Bugs

Installing TWRP Problem

I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy (SS) I drop SS with Adb comand prompt too
{
"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"
}

Domol™ said:
I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy[/IMG]
Click to expand...
Click to collapse
Hey I had this exact same problem just a few moments ago. I didn't necessarily fix it but I found a different way of installing TWRP:
Basically what I did was temporarily boot into the recovery image I had (instead of properly flashing it) and then flashed a zip version of the recovery which works permanently.
To do that, go into the bootloader as normal (adb reboot bootloader) and then use [fastboot boot {filename}.img] (so replace filename with whatever file you have) to boot into the recovery temporarily, then flash the recovery zip.
Here's the link to the zip I used: https://www.androidfilehost.com/?fid=24407100847292484
UPDATE: OK turns out after a few reboots the recovery went back to not working, but I did try another method which definitely works. Temporarily boot into the recovery image as above, but this type install a Supersu zip. This will root the phone. Then boot into the phone as normal, install Flashify from the Play Store and use that to install the recovery image (which you should move onto the phone).
Here are some links:
Supersu zip I used: http://download.chainfire.eu/supersu-stable
Flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB

Samsung SM-T211: Checking PIT partition

*Current behaviour of the device*
When trying to power it on, the device displays several text, it looks like it's debugging itself:
{
"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"
}
Now, while this device displays this texts, I push the following button to get to odin mode, "volume down+home+power button". It should have displayed a warning about entering odin mode, (to which pressing volume up continues going to odin mode and volume down cancels it), but it displays nothing-just blank. But even though it displays blank, I pressed volume up, to which I got then to odin mode.
Now, I have already downloaded the firmware for this device. I have attached BL_*tar.md5, AP_*tar.md5, CP_*tar.md5, CSC_*tar.md5 to the fields of odin, and unchecked "auto reboot", but then itt failed to flash, Odin failed writing the PBL.bin from BL_*tar.md5, but this failure did not gave me up!
AP_*tar.md5 consist of:
boot.img
NVM.img
recovery.img
system.img
I have extracted the files from AP_*tar.gz and tried flashing each of *img from it.
Extracting system.img from AP_*tar.md5, compressing it with `tar` and flashing it returned success from odin but it did not saved the device. No good news.
Extracting NVM.img from AP_*tar.md5, compressing it with `tar` to `NVM.tar.gz` and flashing it returned success from odin but it did not saved the device. No good news.
Other *img, (boot.img and recovery.img) failed to flash.
As a last resort, I would like to write a firmware that displays, "Hello world".
If you find ambiguities in this post, feel free to write.

On a side note: Is there a post about compiling boot.img, system.img, recovery.img?

Mi 9SE cant install twrp

Hi, I wanted to install TWRP to install miui eu, since my battery life is very bad (60 to 90 minutes). Im following instructions, but I get this error message
Code:
FAILED (Write to device failed in SendBuffer() (Too many links))
Ive also tried using XiaomiToolV2 but it also didnt work:
{
"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 should I do? Im using a usb 2.0 port since I got told it works better (i also tried 3.0)
Any help is apreciated

iYannos said:
Hi, I wanted to install TWRP to install miui eu, since my battery life is very bad (60 to 90 minutes). Im following instructions, but I get this error message
Code:
FAILED (Write to device failed in SendBuffer() (Too many links))
Ive also tried using XiaomiToolV2 but it also didnt work: View attachment 5304465
What should I do? Im using a usb 2.0 port since I got told it works better (i also tried 3.0)
Any help is apreciated
Click to expand...
Click to collapse
Try it manually with console as admin (CMD)...
I made it yesterday with adblink:
Command:
Fastboot flash recovery twrpxxxxx.img

made-in-tirol said:
Try it manually with console as admin (CMD)...
I made it yesterday with adblink:
Command:
Fastboot flash recovery twrpxxxxx.img
Click to expand...
Click to collapse
Hi, I forgot to market the thread as solved. What worked form me was to execute the flash command, and then plug in my phone. Ryzen is weird

Custom ROM for Huawei y6 (2018)

I unlocked the bootloader of my Huawei y6 (atu-l21) 2 days ago. Now the problem is that I can't get working custom roms for twrp.
I had downloaded many .ZIP files but the zip file always contained only one image. When I wanted to download the ZIP file via twrp bottles, I always got a red message "invalid zip file format!
Does anyone have working custom ROMs for the Huawei y6 (atu-l21)
{
"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"
}

By you meaning by one file contains img file, you are trying to flash compressed gsi/treble image.
The installation procedure is different for treble devices. Instead do:
First you must uncompress it & do "adb reboot bootloader" & "fastboot flash system [UNCOMPRESSED_IMG_FILE]", wipe data by "fastboot -w", final reboot ur device "fastboot reboot"

do you think I should e.g. extract the customrom.zip to customrom.img and then the image with the commands Flash

Yes, Only if zip archive contains one *.img file like aonly, ab... etc

can I also flash the .IMG file via twrp. because when i try dan i don't know which partition to select.

System-Image

I just tried it and the message "Image is too large for the device" appears

You may read THIS POST about your device custom rom.
And if ab image doesn't work for you try aonly

Jannikoks06 said:
I just tried it and the message "Image is too large for the device" appears
Click to expand...
Click to collapse
Try with fastboot method

I'll do it later I'll report if it worked

Danielisko said:
Try with fastboot method
Click to expand...
Click to collapse
I did it but the phone doesn't boot, only the screen appears where it says that the bootloader on the phone has been unlocked

Root Realme 9 4G (RMX3521) Without Custom Recovery

Hello,
As we all know there is no Custom Recovery available yet for our device. I decided to root the device with patched_boot.img.
I am able to root my Realme 9 4G successfully. I am sharing the procedure if someone like me, who cannot use a android mobile without root can follow the steps to root his Realme 9.
Before starting Make sure you are on RMX3521_11_A.31.
As the attached boot.img files are only for RMX3521_11_A.31.
To check your OS version Go to Settings > About device > Version and Match your Build Version. It should be RMX3521_11_A.31
First of all you have to unlock the bootloader.
Follow this Guide to unlock your bootloader.
Once your Bootloader is Unlocked. Follow the steps below
1. Download the magisk_Patched_boot.img from attachment and move it your PC.
2. Reboot your device into bootloader.
3. Open cmd in adb & fastboot directory and type the command
Code:
fastboot flash boot <drag magisk_patched_boot.img here>
And press enter.
4. Now restart your device by entering the command
Code:
fastboot reboot
5. Download the Magisk Manager and install it.
Your Device is Rooted Now. Make sure to disable the auto software update to avoid getting bootloop.
{
"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"
}

Btw there is an unofficial custom recovery for this device. It works and is tested. Here's the github link; https://github.com/cd-Crypton/custom_recovery_tree_realme_messi