Hello guys
Sorry about my bad english.
I aready flashed twrp, philz,CM recovery but I still got the original recovery instead.
The CMD windows says OK.
My phone is stuck in the aqua splash logo, looping the splash.
"C:\Users\Guilherme\Downloads\New folder>fastboot flash recovery twrp-2.8.5.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9694 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.527s"
ghtmiyashiro said:
Hello guys
Sorry about my bad english.
I aready flashed twrp, philz,CM recovery but I still got the original recovery instead.
The CMD windows says OK.
My phone is stuck in the aqua splash logo, looping the splash.
"C:\Users\Guilherme\Downloads\New folder>fastboot flash recovery twrp-2.8.5.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9694 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.527s"
Click to expand...
Click to collapse
Download the latest TWRP: https://dl.twrp.me/titan/
Here is the link for the motorola fastboot: https://www.androidfilehost.com/?fid=95916177934532795
"TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."
so boot to recovery: mfastboot.exe boot recovery twrp-2.8.6.0-titan.img Don't forget to run CMD as admin
then flash the .img recovery
I can't boot twrp.
tried flashing and boot directly from fastboot( mfastboot boot twrp.img) but got a flashing screen.
the only recovery i can boot from fastboot is the CM.
Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head
iblda said:
Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head
Click to expand...
Click to collapse
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me
cxyqqz said:
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me
Click to expand...
Click to collapse
I paid 15 € !!
I have this message on DC phoenix
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
and the mobile is on fastboot & rescue mode ..
if i try to pass the mobile with flight + & power, it shows me the same screen as the departure:
Error!
Func NO: 10 (boot image)
Error NO: 1 (security verify failed)
this morning another test with DC phoenix
error 10
error 1
iblda said:
this morning another test with DC phoenix
error 10
error 1
Click to expand...
Click to collapse
try : https://www.youtube.com/watch?v=8E43DkUQGMM
cxyqqz said:
try : https://www.youtube.com/watch?v=8E43DkUQGMM
Click to expand...
Click to collapse
dc unlocker does not detect my mobile
only DC phoenix detects it
using the tab "update oeminfo" on DC Phoenix 0.0.0.63, I manage to put the mobile in "PHONE UNLOCKED"
from there I take the opportunity to try to flash BOOT, RECOVERY, SYSTEM with ADB commands.
everything goes smoothly and without error but by restarting the mobile always the same screen with the error in red.
message ADB:
Microsoft Windows [version 10.0.17134.407]
(c) 2018 Microsoft Corporation. Tous droits réservés.
C:\Users\José>cd c:/adb
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.021s
c:\adb> fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22688 KB)...
OKAY [ 0.539s]
writing 'boot'...
OKAY [ 0.683s]
finished. total time: 1.227s
c:\adb>astboot flash recovery recovery.img
'astboot' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
c:\adb> fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36166 KB)...
OKAY [ 0.894s]
writing 'recovery'...
OKAY [ 1.079s]
finished. total time: 1.981s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 18.360s]
writing 'system'...
OKAY [ 8.003s]
sending sparse 'system' (442517 KB)...
OKAY [ 20.055s]
writing 'system'...
OKAY [ 7.675s]
sending sparse 'system' (459746 KB)...
OKAY [ 17.637s]
writing 'system'...
OKAY [ 7.992s]
sending sparse 'system' (444901 KB)...
OKAY [ 18.492s]
writing 'system'...
OKAY [ 7.729s]
sending sparse 'system' (438286 KB)...
OKAY [ 17.082s]
writing 'system'...
OKAY [ 7.612s]
sending sparse 'system' (150611 KB)...
OKAY [ 5.483s]
writing 'system'...
OKAY [ 2.622s]
finished. total time: 138.805s
c:\adb>
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie
iblda said:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie
Click to expand...
Click to collapse
Boot into eRecovery (Volume up whilw connected to PC, or when it shows "bootloader unlocked" warning, hold volume up.) Update to lates firmware
also if you get opportunity to update via HiSuite or from phone settings update it. Try as many times as you can to succed. It will aventually flash latest and greatest firmware.
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck
aciupapa said:
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck
Click to expand...
Click to collapse
this method does not work
the mobile does not exceed 5% and then displays SOFTWARE INSTALL FAILED
Try using HurUpdater. Flash twrp, the download all these files.
1. http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1727/g1647/v146015/f1/full/update.zip dont change name
2.For dualsim
http://update.hicloud.com:8180/TDS/...l/PRA-L31_hw_eu/update_full_PRA-L31_hw_eu.zip (change filename to update_all_hw.zip)
For single sim http://update.hicloud.com:8180/TDS/...l/PRA-L11_hw_eu/update_full_PRA-L11_hw_eu.zip (change filename to update_all_hw.zip)
3. http://update.hicloud.com:8180/TDS/...15/f1/full/public/update_data_full_public.zip (change filename to update_data_public.zip)
4. http://www.mediafire.com/file/ze5z78dq7zu3sxb/HuRUpdater_0.3.zip dont change filename
put all thesw files in one folder on an external sdcard
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd. Flash the HuRupdater_0.3.zip file and confirm flashing by pressing
volume down. After flashing is complete Reboot your phone. ic everything works, it works. If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)
aciupapa said:
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd.
Flash the HuRupdater_0.3.zip file and confirm flashing by pressing volume down.
After flashing is complete Reboot your phone. ic everything works, it works.
If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)
Click to expand...
Click to collapse
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s
my big problem is the installation of a recovery custom.
I can not install it.
the mobile is good in fastboot with bootloader unlocked
but there is no way to flash the recovery:
c: \ adb> fastboot flash recovery twrp-2.8.7.1-p8.img
target reported download size of 471859200 bytes
sending 'recovery' (25880 KB) ...
OKAY [0.676s]
writing 'recovery' ...
FAILED (remote: image verification error)
finished. total time: 0.707s
this is the message I have for all recovery.
EDIT:
and now I have no access unlocking the bootloader with DC phoenix.
Looking for a device in fastboot mode
Device found: 9DCDU17124012020
05/12/2018 23:00:16 Starting to write device in FASTBOOT mode...
Device found: 9DCDU17124012020
IMEI: 862551034926948
Build number: RA-LX1C432B211
Product model: PRA-LX1
Batery state: 4279mv
Not enough credits
he was talking about 72 hours, the time is over.
it's really stealing this dunking thing. the mobile never finally landed, when it was back again it was blocked again.
really **** these huawei as soon as it's bricked.
RIP
[emoji34][emoji35][emoji34][emoji35][emoji34][emoji35]
thanks anyway for your help, even if it did not work ..
Envoyé de mon MHA-L29 en utilisant Tapatalk
iblda said:
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s
Click to expand...
Click to collapse
------------------------
In your command line you write: fastboot flash recovery TWRP-3.2.1-0.img
just write: fastboot boot TWRP-3.2.1.0.img.. Then TWRP will open.
Now in TWRP you can install TWRP recovery, after reboot you will be able yo use it.
I hope this help you.
i have another huawei device, but not honor play.
Now the display can't show me anything even if I press the power button.
Then i connected my phone to my computer and i found that my phone had automatically booted bootloader without showing me anything on its display
i entered fastboot flash recovery recovery.img
it said failed remote command not allowes
i entered fastboot oem relock (password)
it said OKAY
i entered fastboot oem unlock (password)
it said OKAY
i entered fastboot flah boot boot.img
it said failed remote partition length get erro
i used hisuit but it failed when flashing recovery
So i can hardly do anything
how to deal with the problem?
pls help me
thank u
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Can you enter erecovery??
Nwereonye said:
Can you enter erecovery??
Click to expand...
Click to collapse
No. the phone cant show me anything. if i try to turn it off, it will restart.(according to my computer)
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
I'm busy these days. I'll post the log some days later
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
Today I download a package for my device from Firmware finder for Huawei. Then I used Huawei Update Extractor to extract some of the files and tried to flash them to my phone. But failed.
Here's the log
PS C:\WINDOWS\system32> fastboot devices
3CG4C16817019572 fastboot
PS C:\WINDOWS\system32> fastboot flash boot C:\Users\yyche\Desktop\update\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15494 KB)...
OKAY [ 0.400s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.430s
PS C:\WINDOWS\system32> fastboot flash crc C:\Users\yyche\Desktop\update\CRC.img
target reported max download size of 471859200 bytes
sending 'crc' (161 KB)...
OKAY [ 0.006s]
writing 'crc'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update
error: cannot load 'C:\Users\yyche\Desktop\update'
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update\FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'fastboot' (3128 KB)...
OKAY [ 0.081s]
writing 'fastboot'...
FAILED (remote: Command not allowed)
finished. total time: 0.092s
PS C:\WINDOWS\system32> fastboot flash recovery C:\Users\yyche\Desktop\update\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35540 KB)...
OKAY [ 0.914s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.946s
PS C:\WINDOWS\system32> fastboot oem unlock 1**************4
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Do not flash the latest version, it seems u r tying to flash Android Pie. Try to flash Oreo (8.0) version of rom or the one that comes factory installed.
So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.
It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.
Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.
I've got to unbrick my phone, I think.
I can't boot into system or recovery cause my phone is bricked.
What should I do?
When I start fastboot and try to flash twrp, ther comes this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery 4_twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.532s]
writing 'recovery'...
FAILED (remote: This partition doesn't exist)
finished. total time: 1.563s
This is an a/b device , use fastboot flash boot instead of fastboot flash recovery