Develop Bugs

[Q] How to work with windows adb to root phone?

Hello!
Well, I've followed your tutorials and installed android SDK which came in a .zip and I just extracted it to my C:\ directory.
But the phone just doesn't connect! See the image below please.
{
"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 have usb debbuging enabled in my nexus and I am freaking out with this eheh. Little help please xd

Did you boot into the bootloader?
Sent from my Galaxy Nexus using Tapatalk 2

Assuming you've already unlocked the bootloader.
Turn off your cell phone, press Vol+ & Vol- while holding both keys press and hold PowerButton you'll boot into bootloader, now connect your devices to PC and run the command "fastboot devices" if you have all drivers correctly installed you should see something like:
List of Devices
"Devices: xxxxxxxxxx"
Click to expand...
Click to collapse
if you don't see any devices that means either drivers are not installed or you're not booted into the bootloader, but if you see your devices connected use the "fastboot flash recovery recovery.img" once the installation is finished boot into recovery and flash the SuperSU(root).zip
Peace,
L4.1

Rayaxe said:
Hello!
Well, I've followed your tutorials and installed android SDK which came in a .zip and I just extracted it to my C:\ directory.
But the phone just doesn't connect! See the image below please.
I have usb debbuging enabled in my nexus and I am freaking out with this eheh. Little help please xd
Click to expand...
Click to collapse
Try using "fastboot devices" to see if it lists your phone. Fastboot only works when you're in bootloader mode. "adb devices" will list your phone when bored into the os.
Sent from my Galaxy Nexus

thanks guys, it worked ^^

su: inaccessible or not found or target didn't report max-download-size

Got a MI max3 64gb and I cannot
Code:
adb shell > su
which results in
Code:
/system/bin/sh: ext: inaccessible or not found
Also I am not able to fastboot flash recovery twrp-3.3.1-0-nitrogen.img which either get stuck on sending the rom or gives me
Code:
target didn't report max-download-size
My phone says
Code:
unlocked
on boot but when I use MI unlocket to see the status it says phone is not connected.
What have I done so far ?
Latest USB driver is installed as I have android composite ADB interface.
Latest Minimal ADB and Fastboot.
Latest TWRP for mi max3 img is downloaded and placed in the folder of ADB.
I see fastboot logo upon power button + volume up. Also the phone is unlocked.
Enabled soft buttons on the phone and exited the swipe from edges.
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS / bcdedit.exe -set TESTSIGNING ON and reverse are tested.
USB 3 and USB2 port both tested with 2 different quality cables.
Execute fastboot command without connecting your phone , and once it says ( waiting for device ) plug in your cable .
I have flashed TWRP with the same pc a few days ago.
I really want to flash recovery TWRP but I am not anble to do so.

Problem is solved by purchasing
{
"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 could flash it without any issues.

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

Question my mi 11x is not flash twrp , when i was flash my phone my cmd is stop

{
"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"
}

Wrong CMD.
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/

i am not able to download from your link.. please give me another link of twrp for mi 11x
please

manish1012 said:
i am not able to download from your link.. please give me another link of twrp for mi 11x
please
Click to expand...
Click to collapse
the link tells you how to flash the twrp
twrp
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/alioth/

manish1012 said:
View attachment 5823123
Click to expand...
Click to collapse
Look at the path - "platform-tools_r33.0.3___SPACE____ (1)\platformtools"
Cmd should work regardless I think...
But still remove that " (1)" from the platform tools folder name , it might cause you issues down the road.
( Mi flash doesn't work if you place it in a path that has spaces like this )
Now , check again - open cmd and type
Code:
fastboot devices
Does your device show up? Did you press enter after typing fastboot devices?
If it shows up , to flash twrp :
Command is
Code:
fastboot boot "twrp.img"
Open twrp website to learn how to do a permanent flash.
Xiaomi Poco F3
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Next time you wanna flash something do some research first... Flashing it with the command you found on YouTube for a different device than what you're using is an easy way to break the device...
To recover you'd have to extract boot.img / vendor_boot from your rom and flash it ( Unless you're using miui you'll have a pretty bad time ... )

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