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.
Related
Hello Guys,
Now it s finally here
working root for ze550kl, a very big thanks to @shakalaca,
he developed this, full credit goes to him. :fingers-crossed:
Version 1.13.40.496
original thread source
http:// www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=111151&extra=page=1
Steps to Root
1- Download the full version of firmware patch:
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
2- Descompress system.img.7z with 7zip program
3- Copy the boot.img / system.img / recovery.img to (adb/fastboot) folder.
4- Execute this commands in sequence:
-adb device
-adb reboot bootloader
-fastboot devices
-fastboot erase userdata
-fastboot erase cache
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
-fastboot flash system system.img
-fastboot reboot
system will take some time to ready, if stuck at asus splash screen, restart in recovery, wipe cache, format data partition, restart mobile.
install any super user you wish.
Enjoy,
@shakalaca thanks again
Tried adaway working well.
HOLY!!! Thank you very much
thanks to @shakalaca
and you for information
http://zenfonlaser.blogspot.in/
How to Root ASUS Zenfone 2 Laser ZE550KL/Z00LD
How to Flash:
turn on usb debugging in mobile
connect your mobile to pc
after detecting your mobile in pc discconect it
All files link:
https://drive.google.com/folderview?id=0B_j7tYFbJZThclhsZnRPOEFUWXc
Download Flashtool and Extract it to a folder
Download system.img move it to Flashtool folder
( download all parts then put inside one folder then use 7zip software to extract system.img by opening system.img.7z.001 )
Download recovery.img and move it to Flashtool folder
Download boot.img and move it to Flashtool folder
1) now enter in to fast boot mode
methode 1: Turn Off Zenfone 2 Laser and Enter fastboot Mode (Power+Volume up)
methode 2: go to recovery and there enter boot loader mode
methode 3: by adb shell
Connect Zenfone 2 Laser with PC/Laptop
At Flashtool/fastboot folder press shift+Right Click then Open Command Here
-adb device
-adb reboot bootloader
if use methode 1 or 2 Connect Zenfone 2 Laser with PC/Laptop
At Flashtool/fastboot folder press shift+Right Click then Open Command Here
2) Enter this command:
fastboot flash boot boot.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24545 KB)...
OKAY [ 0.828s]
writing 'boot'...
OKAY [ 0.625s]
finished. total time: 1.453s
3) Enter this command:
fastboot flash recovery recovery.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (26507 KB)...
OKAY [ 0.891s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.453s
4) Enter this command:
fastboot flash system system.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 6.953s]
sending sparse 'system' (259338 KB)...
OKAY [ 13.109s]
writing 'system'...
OKAY [ 5.765s]
sending sparse 'system' (257277 KB)...
OKAY [ 13.093s]
writing 'system'...
OKAY [ 5.625s]
sending sparse 'system' (257278 KB)...
OKAY [ 12.843s]
writing 'system'...
OKAY [ 5.781s]
sending sparse 'system' (257277 KB)...
OKAY [ 12.906s]
writing 'system'...
OKAY [ 5.656s]
sending sparse 'system' (262102 KB)...
OKAY [ 13.312s]
writing 'system'...
OKAY [ 6.312s]
sending sparse 'system' (257122 KB)...
OKAY [ 13.390s]
writing 'system'...
OKAY [ 6.625s]
sending sparse 'system' (260005 KB)...
OKAY [ 13.171s]
writing 'system'...
OKAY [ 7.218s]
sending sparse 'system' (252193 KB)...
OKAY [ 12.390s]
writing 'system'...
OKAY [ 5.734s]
sending sparse 'system' (258041 KB)...
OKAY [ 12.859s]
writing 'system'...
OKAY [ 6.156s]
sending sparse 'system' (258041 KB)...
OKAY [ 12.953s]
writing 'system'...
OKAY [ 5.937s]
sending sparse 'system' (261502 KB)...
OKAY [ 13.187s]
writing 'system'...
OKAY [ 6.593s]
sending sparse 'system' (139273 KB)...
OKAY [ 7.109s]
writing 'system'...
OKAY [ 3.890s]
finished. total time: 653.488s
5) Enter this command:
fastboot oem reboot-recovery
u will see in cmd window:
G:\asus\FlashTools>fastboot oem reboot-recovery
...
OKAY [ 0.016s]
finished. total time: 0.016s
6) Wipe data/factory reset from recovery menu
use volume key for up and down
and power key for select press yes in second menu
now reboot form recovery menu
Done your Zenfone 2 Laser is Rooted.
Thank you again.. it's working and this is my feedback
How big is the patch??
---------- Post added at 01:03 PM ---------- Previous post was at 12:53 PM ----------
Btw the original image is for zenfone selfie. Will it work on 550KL
caldent said:
How big is the patch??
---------- Post added at 01:03 PM ---------- Previous post was at 12:53 PM ----------
Btw the original image is for zenfone selfie. Will it work on 550KL
Click to expand...
Click to collapse
No, this is not for selfie, this is for ze550kl.
build nos of zenfone laser and selfie are different.
This one based on latest version of zenfone laser ze550kl.
Thank you @rajiki for the news and thx to @shakalaca ....will tey this soon
Sent from my ASUS_Z00LD using Tapatalk
Superb work
I am new to Zenfone laser Ze550kl. I have two queries below
1.We need to unlock Boot-loader to execute this?
2.and this is void warranty?
Thanks for your work.
eugineprakash said:
I am new to Zenfone laser Ze550kl. I have two queries below
1.We need to unlock Boot-loader to execute this?
2.and this is void warranty?
Thanks for your work.
Click to expand...
Click to collapse
You don't need to unlock the bootloader and I'm not sure about warranty but it is usually safe to assume that you will void your warranty.
The good thing is that you can always reflash the stock rom and that should return it to factory condition but can't guarantee your warranty won['t be voided. Someone else might be able to confirm for sure.
when you flash stock firmware that will re-flash everything & your warranty would not be void.
Hey Buddy, I am in Big Trouble this time. While Flashing System.img file, i am getting the following error
Command - fastboot flash system system.img
error - cannot load system.img
Can you tell me what's the issue here? or can you provide me your Fastboot ADB Zip file will be great helpful
waiting for your answer
ArshArora said:
Hey Buddy, I am in Big Trouble this time. While Flashing System.img file, i am getting the following error
Command - fastboot flash system system.img
error - cannot load system.img
Can you tell me what's the issue here? or can you provide me your Fastboot ADB Zip file will be great helpful
waiting for your answer
Click to expand...
Click to collapse
Just wait & let command got completed,it will take some times as file too big to send.
it will sparse & send in parts, whole process will complete around 15 minute.
rajlko said:
Just wait & let command got completed,it will take some times as file too big to send.
it will sparse & send in parts, whole process will complete around 15 minute.
Click to expand...
Click to collapse
command is not starting at all. just showing error like screenshot i attached
what is the size of image size, did you extract file correctly ?
actual size of system image is 2.84 GB (3,05,09,60,328 bytes).
other commands executed or not ?
ArshArora said:
command is not starting at all. just showing error like screenshot i attached
View attachment 3524359
Click to expand...
Click to collapse
go in the extracted folder where system.img.7z.001-006 file is. click on anyone of these six files and decompress with 7-zip file manager.
now u will get a single file SYSTEM.img of about 2.4 gb. put this system.img in the adb and fastboot folder.
now flash the system.
happened the same with me a few hours ago.
I experienced that same error on that system.img and solved it by
1st: Not using administrative cmd C:\Users\(pcname)> on cmd
2nd: I just put those 3 files on C:\Users\(pc name)\
only recovery and boot img work when on adb folder.. dunno if it's on windows 10 but I got it working on above directory
just xposed needed now
can we flash xposed zip file in stock recovery?via adb or any other way?
though there is some method of flashing xposed framework without recovery which we used on 551 ML..via adb only..
anyone shed some light on this?
sausuke said:
I experienced that same error on that system.img and solved it by
1st: Not using administrative cmd C:\Users\(pcname)> on cmd
2nd: I just put those 3 files on C:\Users\(pc name)\
only recovery and boot img work when on adb folder.. dunno if it's on windows 10 but I got it working on above directory
Click to expand...
Click to collapse
Awesome dude ! that worked for me finally
ArshArora said:
Awesome dude ! that worked for me finally
Click to expand...
Click to collapse
glad that worked... I hate that system.img problem
followed all guide. Finally the system error was solved and it got flashed . Now the phone is stucked on Asus logo and below bufferring type symbol is going on from past 15 mins. I removed battery and inserted it and pressed power button + vol up continuously still it directly goes to fastboot boot. No options of normal boot or recovery option please help.
Hello everyone,
I'm trying to install TWRP + Boot on my Mi5 in order to install Xiaomi.eu rom later.
I have been following these steps: https://xiaomi.eu/community/threads...r-xiaomi-mi5-unlocked-bl-only-released.31231/
All went well:
Code:
C:\Miflash_tool_gemini\Google\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (40072 KB)...
OKAY [ 0.977s]
writing 'recovery'...
OKAY [ 1.815s]
finished. total time: 2.795s
C:\Miflash_tool_gemini\Google\Android>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (37248 KB)...
OKAY [ 0.918s]
writing 'boot'...
OKAY [ 0.341s]
finished. total time: 1.260s
C:\Miflash_tool_gemini\Google\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.995s]
booting...
OKAY [ 1.180s]
finished. total time: 2.177s
Until the moment to reboot to TWRP.
It just displays the mi logo forever and doesn't boot. It's been 10min now.
Is that normal?
Should I continue to wait?
Thx
After 30min with no progress I decided to stop the phone.
I pressed the power button for few seconds. The mi logo disappeared. I stopped pressing. But straight away the phone is trying to reboot and displays again the mi logo forever
F*********************ck!
Managed to enter in Fastboot mode! Don't ask me how.
No I guess, from what I read in various places I need to flash a fastboot DEV ROM using MiFlash?
Seem to be the procedure when you are in bootloop.
I guess I'll have to unlock again the phone once this ROM will be flashed?
Ok I'm back on track. I've downloaded the last Mi5 Global DEV fastboot ROM (gemini_global_images_6.5.30_20160516.0000.22_6.0_global_9cee9512c7.tgz)
I flashed it using MiFlash. But I kept the storage. I probably should have flashed all because now it keeps on say it can't find the device ID and I get some java stack trace errors complaining about SQLite access problems.
Tomorrow I'll try again to flash TWRP. We will see if it does the same :-/
That's it I've managed to flash TWRP + xiaomi.eu stable rom.
I think the part that generated the bootloop was the fact that I didn't run the following command after flashing TWRP:
Code:
fastboot reboot
I rebooted manually using power button + vol. up.
Now everything is working fine.
Foobrother said:
Hello everyone,
I'm trying to install TWRP + Boot on my Mi5 in order to install Xiaomi.eu rom later.
I have been following these steps: https://xiaomi.eu/community/threads...r-xiaomi-mi5-unlocked-bl-only-released.31231/
All went well:
Code:
C:\Miflash_tool_gemini\Google\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (40072 KB)...
OKAY [ 0.977s]
writing 'recovery'...
OKAY [ 1.815s]
finished. total time: 2.795s
C:\Miflash_tool_gemini\Google\Android>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (37248 KB)...
OKAY [ 0.918s]
writing 'boot'...
OKAY [ 0.341s]
finished. total time: 1.260s
C:\Miflash_tool_gemini\Google\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.995s]
booting...
OKAY [ 1.180s]
finished. total time: 2.177s
Until the moment to reboot to TWRP.
It just displays the mi logo forever and doesn't boot. It's been 10min now.
Is that normal?
Should I continue to wait?
Thx
Click to expand...
Click to collapse
my phone also got stuck on the logo when i flashed supersu which i think was quite old..
i then flashed a newer zip and everything went back to normal.happy to see that you were able to fix your phone. iwas devastated for the 15min that my phone wasnt working
---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------
Foobrother said:
Ok I'm back on track. I've downloaded the last Mi5 Global DEV fastboot ROM (gemini_global_images_6.5.30_20160516.0000.22_6.0_global_9cee9512c7.tgz)
I flashed it using MiFlash. But I kept the storage. I probably should have flashed all because now it keeps on say it can't find the device ID and I get some java stack trace errors complaining about SQLite access problems.
Tomorrow I'll try again to flash TWRP. We will see if it does the same :-/
Click to expand...
Click to collapse
have you figured out why this error came in the first place??
Hello my hope :3
actually i cannot access my recovery or the os, if i start the device, its just a bootloop.
Fastboot is possible, but bootloader is locked and im not able to tick something in the develeloper settings because there is no os anymore.
C:\adb>fastboot flash recovery recovery_OBT7.img
target reported max download size of 442499072 bytes
sending 'recovery' (22237 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.529s
Click to expand...
Click to collapse
i tried the Snapdragon tool(MsmDownloadTool) also but only get this error: FirehoseWriteData Failed, do you have any suggestions? :c
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.
hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
model : lld-l21
lilolahcen said:
hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
Click to expand...
Click to collapse
help meeeeeeee please
lilolahcen said:
help meeeeeeee please
Click to expand...
Click to collapse
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal
villapark75 said:
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal
Click to expand...
Click to collapse
no, i can't get into recovery because the device does'nt boot
i can use a terminal but , when i write fastboot reboot , the device reboots and returns to fastboot
What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?
Sparkrite said:
What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?
Click to expand...
Click to collapse
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )
lilolahcen said:
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )
Click to expand...
Click to collapse
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:
lilolahcen said:
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:
Click to expand...
Click to collapse
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.
Leeban Joseph said:
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.
Click to expand...
Click to collapse
Very late to the party, but wanted to thank you for a comprehensive, helpful answer.
The fact lilolahcen didn't respond is hopefully because his phone is working once again.
Good post ?
Thanks. I myself have gone through many guides available here at xda. So I hope I can be of some use for someone who is facing the same problems I have faced.