Database Info

[Q] Phone bricked and fastboot connected but fails every time to transfer anything

My Nexus S is stuck on the google screen.
I have downloaded the drivers for Android ADB and have gotten fastboot talking to the device but for some reason ADB doesn't talk to the device (though it does with my HTC HD2).
The phone is still locked and has no custom bootloader on it.
I can list devices attached with Fastboot and it shows the Nexus's serial number but when I try to do "Fastboot oem unlock" it comes on the phones screen to unlock the bootloader and when I select yes it hangs there and cmd says:
Code:
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I am running windows 7 64bit.
The only difference I notice from the tutorials and mine is that the driver says
{
"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"
}
Instead of Samsung Android Device.
I had to install the drivers manually as PDAnet couldn't pick up the device and I found the drivers on one of the many topics on this.
Any idea's would be much appreciated, I have been trying to fix this for over a week

inode86 said:
My Nexus S is stuck on the google screen.
I have downloaded the drivers for Android ADB and have gotten fastboot talking to the device but for some reason ADB doesn't talk to the device (though it does with my HTC HD2).
The phone is still locked and has no custom bootloader on it.
I can list devices attached with Fastboot and it shows the Nexus's serial number but when I try to do "Fastboot oem unlock" it comes on the phones screen to unlock the bootloader and when I select yes it hangs there and cmd says:
Code:
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I am running windows 7 64bit.
The only difference I notice from the tutorials and mine is that the driver says
Instead of Samsung Android Device.
I had to install the drivers manually as PDAnet couldn't pick up the device and I found the drivers on one of the many topics on this.
Any idea's would be much appreciated, I have been trying to fix this for over a week
Click to expand...
Click to collapse
If fastboot recognises your phone, have you tried flashing latest cwm.img recovery through it? (fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img) from your sdk tools folder? It could be that you never had USB debugging ticked in settings!

I have tried flashing the latest recovery .img to it but it comes up with the exact same error.
I don't think USB debugging was enabled before it bricked. I have no idea where to do from here as the phone was bought second hand so no warranty.

bump........

[RECOVERY][UNOFFICIAL]TWRP Recovery Project UMIDIGI A7 Pro 3.5.2

{
"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"
}
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.
*/Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers./*
Click to expand...
Click to collapse
Flash Guide :
1. Unlock your bootloader
2. Download TWRP 3.5.2
3. Enable USB debugging
4. vbmeta from stock firmware
5. Run this Following Command
1. adb reboot bootloader
2. fastboot --disable-verification flash vbmeta vbmeta.img
3. fastboot flash recovery recovery.img
4. fastboot reboot recovery
Click to expand...
Click to collapse
Download
Device tree
Working
• MTP
• fastbootd
• adb
Bugs
• Decryption
• spam me in support group
Changelog
• Initial Build
• Updated to 3.5.2
• Fix some bugs in previous Builds
Credits
• TEAM WIN FOR TWRP
Support Group
Here

Hello mastersenpai05, how are you?
I finally managed to flash a GSI on the Umidigi A7 pro. Flashed PHH's GSI AOSP, version 411 - Android 12.
The problem is that when flashing your TWRP, I can't boot, it's in a loop.
I flashed like this:
[email protected]:~/Documentos/A7pro/twrp 352 Sempai$ sudo su
[sudo] senha para edupaz:
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# adb devices
List of devices attached
A7PRO205020712 device
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# adb reboot fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot devices
A7PRO205020712 fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.014s]
Finished. Total time: 0.027s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot flash recovery recovery.img (I renamed the image)
Sending 'recovery' (23168 KB) OKAY [ 1.389s]
Writing 'recovery' OKAY [ 0.330s]
Finished. Total time: 1.732s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.052s
Click to expand...
Click to collapse
Can you give me an idea how to fix the problem?
Now, after writing this message, which I called myself, that this version of TWRP is for Android 10. Do you have any predictions to launch for Android 12?

N
edufpaz said:
Hello mastersenpai05, how are you?
I finally managed to flash a GSI on the Umidigi A7 pro. Flashed PHH's GSI AOSP, version 411 - Android 12.
The problem is that when flashing your TWRP, I can't boot, it's in a loop.
I flashed like this:
Can you give me an idea how to fix the problem?
Now, after writing this message, which I called myself, that this version of TWRP is for Android 10. Do you have any predictions to launch for Android 12
Click to expand...
Click to collapse
Twrp A7 Pro will not work in android 12

mastersenpai05 said:
N
Twrp A7 Pro will not work in android 12
Click to expand...
Click to collapse
BIG mastersenpai05!
Thanks for the feedback. Is it possible to have development for Android 12?

Question Unlock bootloader failes with 'remote failure'

I have a new Moto G100. I would like to root the phone using Magisk. In order to be able to do that I used the procedure to get an unlock key from Motorola. When boot into the bootloader and try to send the key to the phone using
fastboot oem unlock <key>
I get the following response:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.060s
Developer settings are enabled. When I go to Android Settings > Developer and check 'OEM unlocking', the setting is grayed out. It looks like the setting is set to On.
The phone is eligible for unlocking according to the information from Motorola (cid variable is 0032).
Why is the unlock command failing? What can I do to fix it?

gewe said:
I have a new Moto G100. I would like to root the phone using Magisk. In order to be able to do that I used the procedure to get an unlock key from Motorola. When boot into the bootloader and try to send the key to the phone using
fastboot oem unlock <key>
I get the following response:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.060s
Developer settings are enabled. When I go to Android Settings > Developer and check 'OEM unlocking', the setting is grayed out. It looks like the setting is set to On.
The phone is eligible for unlocking according to the information from Motorola (cid variable is 0032).
Why is the unlock command failing? What can I do to fix it?
Click to expand...
Click to collapse
You need to connect to the internet, and wait 3 days or so, till oem unlocking is not grey
Edit does it look like this?
{
"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"
}

sd_shadow said:
You need to connect to the internet, and wait 3 days or so, till oem unlocking is not grey
Edit does it look like this?
Click to expand...
Click to collapse
Do this and update to latest OTA

After about 72 hours the option was magically enabled.

Rooting on MIUI 13.0.3.0

Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!

ashirviskas said:
Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!
Click to expand...
Click to collapse
Did you try with Magisk manager?

That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A

ashirviskas said:
That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A
Click to expand...
Click to collapse
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20

NOSS8 said:
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20
Click to expand...
Click to collapse
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.

ashirviskas said:
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.
Click to expand...
Click to collapse
I had this phone but I don't remember if it has RAMDISK?
{
"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"
}

NOSS8 said:
I had this phone but I don't remember if it has RAMDISK?
Click to expand...
Click to collapse
It does.

And no vbmeta

ashirviskas said:
It does.
Click to expand...
Click to collapse
Surely you did everything correctly but just in case, check.(Possibly post a screenshot of the CMD with the result)
Copy the boot/recovery image to your device
Press the Install button on the Magisk card
If you are patching a recovery image, make sure “Recovery Mode” is checked in options.
In most cases, it should already be automatically checked.
Choose “Select and Patch a File” in the method, and select the stock boot/recovery image
The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
Copy the patched image to your PC with ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot/recovery image to your device.
For most devices, reboot into fastboot mode and flash with the command:
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image
Reboot and voila!
Or use the twrp to flash the modified boot.img

Though I do see it when I run `adb shell ls -l /dev/block/by-name` I will try repatching and reflashing, maybe this is what has been missing.

Here's my latest attempt with vbmeta.img included:
sudo fastboot flash boot magisk_patched-25200_VvhFg.img
[sudo] password for mati:
Sending 'boot' (131072 KB) OKAY [ 3.275s]
Writing 'boot' OKAY [ 2.315s]
Finished. Total time: 5.600s
sudo fastboot flash vbmeta --disable-verity --disable-verification lmi_global_images_V13.0.3.0.SJKMIXM_20220620.0000.00_12.0_global/images
/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.024s
sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.201s
Opening magisk app it still says `Installed: N/A`

Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.

ashirviskas said:
Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.
Click to expand...
Click to collapse
Better than stock(more options, call recorder)and play store certified without root.
https://xiaomi.eu/community/threads/miui-13-stable-release.64441/

Question Unable to install TWRP after rooting Redmi Note 11 Pro 5Gv(veux)

Hello all
I have used the information on here to successfully root my phone (Redmi Note 11 Pro 5G - veux) via magisk but I would like to put TWRP on it however whenever I try to boot the recovery image it does not work. Below I will include the mod el and info of my phone and also the output message of powershell, if anyone can tell me what I am doing wrong that will be great.
{
"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 did my flashing with the official mi flash tool to root with magisk but this screenshot from a different author seems to show the information you may need to help me nicely.
Here is the output from powershell when I try to boot the unofficial version I found named "360 pissarro RN 11 Pro+ pjgowtham" which says its for veux but I'm not getting much success.
I have flashed successfully and the drivers seem to be ok and list the device in "fastboot devices" and it is in USB developer mode but other than that I can't figure out why it wont't boot the recovery img so I can install TWRP
I will be eternally grateful if someone can tell me what I am doing wrong or what the actual correct file is
PowerShell Output:
PS C:\Users\Steve\Desktop\platform-tools> fastboot boot C:\Users\Steve\Desktop\recovery.img
downloading 'boot.img'...
OKAY [ 1.086s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.101s
PS C:\Users\Steve\Desktop\platform-tools>

Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img

No Sir, but I will try it right now

friend.evil said:
Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!

tehnooks said:
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!
tehnooks said:
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!
Click to expand...
Click to collapse
EDIT: AGAIN
Click to expand...
Click to collapse
Didn't actually work now it's just stuck on the FASTBOOT screen
Heres what I got:
C:\Users\Steve\Desktop\platform-tools>fastboot flash boot recovery.img
Sending 'boot_a' (38418 KB) OKAY [ 1.031s]
Writing 'boot_a' OKAY [ 0.147s]
Finished. Total time: 1.454s
Am I using the wrong set of adb files to flash it with? Im using the platform tools from the android sdk

friend.evil said:
Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Tried flashing both boot_a and boot_b but still just ended up stuck on the fastboot screen

Had the same problems first, use command Prompt instead of powershell and make sure drivers are updated.
If you need twrp to install a new Rom follow these steps.
First type: fastboot getvar unlocked to check if it's unlocked.
Second Step is to download 2 Firmwares ( one updated and one slightly older ) from here
Flash up to date Firmware ( Slightly older is downloaded incase there are issues ) and boot to system, enable adb in developer options then use magisk to root phone, flash patched boot img with: fastboot flash boot patchboot.img
Edit: To flash a firmware follow this link and look at 2nd post if software isn't opening ( copy adb files to folder before using flash_all.bat )
After your phone is rooted and you made sure it was functional flash twrp: fastboot flash boot twrp12.img
Go to recovery mode, if the phone doesn't respond with touch display insert a usb c hub and add a mouse.
Download Encryption Disabler from Here and go to adb sideload and install it with adb sideload, next step is to install a Rom.
Mount Everything and wipe data then install Rom with ADB Sideload. ( ArrowOS is good ). Flash ROM then Gapps.

friend.evil said:
Had the same problems first, use command Prompt instead of powershell and make sure drivers are updated.
If you need twrp to install a new Rom follow these steps.
First type: fastboot getvar unlocked to check if it's unlocked.
Second Step is to download 2 Firmwares ( one updated and one slightly older ) from here
Flash up to date Firmware ( Slightly older is downloaded incase there are issues ) and boot to system, enable adb in developer options then use magisk to root phone, flash patched boot img with: fastboot flash boot patchboot.img
Edit: To flash a firmware follow this link and look at 2nd post if software isn't opening ( copy adb files to folder before using flash_all.bat )
After your phone is rooted and you made sure it was functional flash twrp: fastboot flash boot twrp12.img
Go to recovery mode, if the phone doesn't respond with touch display insert a usb c hub and add a mouse.
Download Encryption Disabler from Here and go to adb sideload and install it with adb sideload, next step is to install a Rom.
Mount Everything and wipe data then install Rom with ADB Sideload. ( ArrowOS is good ). Flash ROM then Gapps.
Click to expand...
Click to collapse
Which is the most suitable twrp image to use? I cant find one for veux or one named twrp12.img
Thanks!
EDIT: found it at https://drive.google.com/file/d/1-2_8YAfnWgvoRxIecDtN6JBRYWRKq8Ii/view
Thanks a lot it boots the twrp fine now