Hi,
i want to install twrp-3.2.3-0-whyred.img recovery on my Xiaomi and later xiaomi.eu_multi_HMNote5Pro_V10.0.1.0.OEICNFH_v10-8.1.
But I always get some errors. I never had this with my mi max 2.
I am afraid to brick this Redmi Note 5. Please help me
Redmi Note 5 Global Version RED (dual camera)
Miui version: miui global 9.6 stable 9.6.4.0 (OEIMIFD)
model name: M1803E7SG
Bootloader Unlocked by http://en.miui.com/unlock/
USB Debugging Enabled
Using latest platform-tools
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\Users\Marija\Desktop\platform-tools> adb kill-server
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
*Numbers* fastboot
PS C:\Users\Marija\Desktop\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
Sending 'recovery' (36324 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: Anti-rollback check failed)
Finished. Total time: 0.906s
cassinni said:
Hi,
i want to install twrp-3.2.3-0-whyred.img recovery on my Xiaomi and later xiaomi.eu_multi_HMNote5Pro_V10.0.1.0.OEICNFH_v10-8.1.
But I always get some errors. I never had this with my mi max 2.
I am afraid to brick this Redmi Note 5. Please help me
Redmi Note 5 Global Version RED (dual camera)
Miui version: miui global 9.6 stable 9.6.4.0 (OEIMIFD)
model name: M1803E7SG
Bootloader Unlocked by http://en.miui.com/unlock/
USB Debugging Enabled
Using latest platform-tools
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\Users\Marija\Desktop\platform-tools> adb kill-server
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
*Numbers* fastboot
PS C:\Users\Marija\Desktop\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
Sending 'recovery' (36324 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: Anti-rollback check failed)
Finished. Total time: 0.906s
Click to expand...
Click to collapse
First, copy the twrp image onto internal storage. After you connect it in the fastboot mode, boot into twrp (fastboot boot twrp-3.2.3-0-whyred.img), then after you booted into twrp, flash the twrp image within twrp.
attitude12 said:
First, copy the twrp image onto internal storage. After you connect it in the fastboot mode, boot into twrp (fastboot boot twrp-3.2.3-0-whyred.img), then after you booted into twrp, flash the twrp image within twrp.
Click to expand...
Click to collapse
I copied the same twrp.img into internal storage that is in platforms-tools folder and fastboot devices is showing the phone number and i get this:
...\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
< waiting for any device >
Different attept: platform-tools> fastboot boot twrp.img
Downloading 'boot.img' FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.024s
cassinni said:
I copied the same twrp.img into internal storage that is in platforms-tools folder and fastboot devices is showing the phone number and i get this:
...\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
< waiting for any device >
Different attept: platform-tools> fastboot boot twrp.img
Downloading 'boot.img' FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.024s
Click to expand...
Click to collapse
Are you sure ur doing everything right?
Is usb debugging on?
Stock twrp is a hustle to install you need to unlock the fastboot using dummy.img and use lazy flasher...
Just use redwolf recovery find it and
Fastboot boot redwolf.img
Install redwolf.img as recovery
Reboot to recovery
Enable USB Debugging (security settings) and then try
fastboot boot twrp.img
Then once again flash twrp.img within twrp recovery
t0per666 said:
Stock twrp is a hustle to install you need to unlock the fastboot using dummy.img and use lazy flasher...
Just use redwolf recovery find it and
Fastboot boot redwolf.img
Install redwolf.img as recovery
Reboot to recovery
Click to expand...
Click to collapse
There is no redwolf for this modell
SunilSuni said:
Enable USB Debugging (security settings) and then try
fastboot boot twrp.img
Then once again flash twrp.img within twrp recovery
Click to expand...
Click to collapse
USB Debugging is enabled under developer mode
\platform-tools> fastboot flash recovery twrp.img
< waiting for any device >
cassinni said:
There is no redwolf for this modell
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...t/recovery-red-wolf-recovery-project-t3766997
Next time use search function sir
Doesn't work even with redwolf. Adb is installed, twrp.img is in root storage of phone and in adb folder. usb debugging enabled, phone unlocked by xiaomi (during booting and in settings it says unlocked). tried usb 2 and 3.0 ports on pc. windows 10 x64.
PS C:\Users\marija\Desktop\platform-tools> adb reboot bootloader
PS C:\Users\marija\Desktop\platform-tools> fastboot flash recovery twrp.img
sending 'recovery' (37592 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: -0.000s
cassinni said:
Doesn't work even with redwolf. Adb is installed, twrp.img is in root storage of phone and in adb folder. usb debugging enabled, phone unlocked by xiaomi (during booting and in settings it says unlocked). tried usb 2 and 3.0 ports on pc. windows 10 x64.
PS C:\Users\marija\Desktop\platform-tools> adb reboot bootloader
PS C:\Users\marija\Desktop\platform-tools> fastboot flash recovery twrp.img
sending 'recovery' (37592 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Waiting for device means you haven't installed required Xiaomi drivers in your PC, install drivers and then try
There are two types of USB DEBUGGING in Xiaomi phones
USB DEBUGGING
USB DEBUGGING (Security settings)
You have to enable these two options
If you still face problem maybe you can try different PC/Laptop
SunilSuni said:
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Waiting for device means you haven't installed required Xiaomi drivers in your PC, install drivers and then try
There are two types of USB DEBUGGING in Xiaomi phones
USB DEBUGGING
USB DEBUGGING (Security settings)
You have to enable these two options
If you still face problem maybe you can try different PC/Laptop
Click to expand...
Click to collapse
Both USB Debugging are enabled. Also the right drivers are installed. I have done this several times for other Xiaomi
devices, but this Redmi Note 5 Global Version (Dual Cameras) Red is crazy.
Maybe this cannot work because this is not Global Rom. It is Global Version and there is no twrp that supports Version.
I want to install twrp so i can flash xiaomi.eu 10 on it. Everything is stock on the phone and it does not work.
Sometimes it finds the phone and says file size too large and wont flash, or it gets stuck while flashing for 30mins and nothing happens or i get this error i just posted. I dont want to downgrade firmware, i want to update from 9 to 10.
I tried now on the laptop and it shows the device but it will not work.
PS C:\adb> adb kill-server
PS C:\adb> adb start-server
* daemon not running; starting now at tcp:5027
* daemon started successfully
PS C:\adb> adb devices
List of devices attached
60dbr4g2 device
PS C:\adb> fastboot boot twrp.img
< waiting for any device >
SunilSuni said:
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Click to expand...
Click to collapse
The antirollback was the issue. Now I am in TWRP. Do i have to wipe something? Please give exact command lines and where I enter them.
I flash twrp successfully. Then i went to wipe Dalvik, Cache, Data, System, Vendor.
Then Installed xiaomi.eu_multi_HMNote5Pro_8.8.30_v10-8.1.zip. At the end of install it had an error
for Vendor. E2001 Failed to update vendor image. Updater process ended with error 7.
I rebooted and now everytime i reboot it takes me to Fastboot screen?
Please help
cassinni said:
I flash twrp successfully. Then i went to wipe Dalvik, Cache, Data, System, Vendor.
Then Installed xiaomi.eu_multi_HMNote5Pro_8.8.30_v10-8.1.zip. At the end of install it had an error
for Vendor. E2001 Failed to update vendor image. Updater process ended with error 7.
I rebooted and now everytime i reboot it takes me to Fastboot screen?
Please help
Click to expand...
Click to collapse
Once again fastboot boot twrp.img and flash twrp
You have to avoid erasing vendor partition just system data cache dalvik cache is enough
I was in fastboot and used in adb fastboot boot twrp.img, then i got to twrp.
Now I should reflash twrp-3.2.3-0-whyred.img as recovery or vendor image?
I did already as recovery and then wiped data, cache, delvik and system as you said
then installed xiaomi.eu rom but i got the same vendor error.
Hello.
The problem is arb4 in this version of miui
follow the order of operations marked here:
https://androidfilebox.com/tips/root-redmi-note-5/
just add between step 10 and step 11 the unlocking of the arb4 ; this is possible with "toolkit flasher" that you find there:
http://en.miui.com/forum.php?mod=viewthread&tid=3282063&extra=page=3&mobile=2 (4 flash unlock anti roll back)
everyone tells me something different
the phone is not on miui 10. it was on stock stable miui 9. the flashing of 10 failed. The bootloader is already unlocked by xiaomi.
I believe my problems come from wiping vendor before i tried to flash miui 10 in twrp. I wasnt trying to downgrade (roll back), so arb4 should be irrelevant.
cassinni said:
everyone tells me something different
Click to expand...
Click to collapse
do as you like.
I rooted yesterday my note 5 (same model) which also turns on 9.6.4.0.
Hello,
I have a Nokia 6.1 that bricked itself over a system update last year.
Symptoms
Turns on and goes into "Download Mode" screen. Does not turn off. Keeps rebooting.
Had to run
Code:
fastboot oem HALT
to put it to sleep.
Phone details
Android 8.1
Bootloader Locked
Output of
Code:
fastboot oem device-info
`
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.016s]
finished. total time: 0.016s
Goal
Somehow recover critical data stored on the phone. Data wiping is not an option.
What I've tried
1. Key combos
Multiple key combinations fails to take it to a recovery screen.
2. ADB & Fastboot
On windows 10 I've installed the minimal ADB&Fastboot drivers.
Code:
adb devices
shows nothing.
Code:
fastboot devices
shows the device.
The following set of commands takes it to a recovery (?) mode
Code:
fastboot devices
fastboot reboot
fastboot getvar current-slot
fastboot --set-active=b
fastboot --set-active=a
fastboot reboot
This screen only shows 2 options "Try again" and "Factory Reset"
Also says "Can't load android system. Data my be corrupt." (sth similar)
I've tried installing TWRP with
Code:
fastboot boot twrp.img
but since the bootloader is locked I'm unable to do so.
I have not tried unlocking the bootloader as it supposedly wipes the data, even though it supposedly doesn't have to.
After some time I'd discovered something called an EDL mode and tried to jerry rig a USB-C cable with shorted green and black wires to get the phone to boot into that mode. I'm not sure what the proper sequence of actions here should be as the phone turns on and goes into "Download Modes" the second I plug the USB cable in and nothing shows up on Device Manager.
Would it be possible in any way to recover the data or at least take a dump of the userdata partition in the storage. Thanks a lot in advance.
Hi guys,
I'm trying to install LineageOS to XZ2 Compact but I have some issues. I was following this guide. (NOTE: Bootloader unlock was done by owner of phone, not sure if he did something wrong)
As said in guide, I should connect phone to PC and reboot to bootloader using command
Code:
adb reboot bootloader
This works. However, when trying to flash boot partition with LineageOS recovery I'm getting fastboot errors. Here are commands and their verbose output (output is same for all these partitions - boot, boot_a, boot_b, boot__a, boot__b):
Code:
fastboot flash boot lineage-17.1-20201225-nightly-xz2c-recovery.img
fastboot: error: cannot get boot partition size
fastboot version is 30.0.5
Any ideas?
Have you tried fastboot devices to see if your device shows up? If that does work, can you try "boot a" with no underscore(s)?
I managed to install Lineage OS to phone. Problem was (strangely) with linux fastboot. It detected device normally but something was not right. Done same steps on windows pc and it worked.
I forgot to update thread.