Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Joshywooful1 said:
Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Click to expand...
Click to collapse
For the beginning, let's see which firmware your phone thinks it is on. Execute in Fastboot and copy back results (omit output of the first line - serial number):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
zgfg said:
For the beginning, let's see which firmware your phone thinks it is on. Execute in Fastboot and copy back results (omit output of the first line - serial number):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Code:
fastboot devices
fastboot
fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.002s]
Finished. Total time: 0.006s
fastboot oem get-product-model
(bootloader) EVA-AL10
OKAY [ 0.003s]
Finished. Total time: 0.006s
fastboot oem get-build-number
(bootloader) :EVA-AL10 8.0.0.535(C00)
OKAY [ 0.003s]
Finished. Total time: 0.007s
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :EVA-AL10C00B398
OKAY [ 0.005s]
Finished. Total time: 0.008s
fastboot getvar vendorcountry
vendorcountry: all/cn
Finished. Total time: 0.003s
The phone itself is a European model Huawei P9 EVA-L09, rebranded to EVA-AL10 using HWOTA7.
Joshywooful1 said:
The phone itself is a European model Huawei P9 EVA-L09, rebranded to EVA-AL10 using HWOTA7.
Click to expand...
Click to collapse
Do you want to go back to EVA-AL10c00 (b540 Oreo) or you want to downgrade to EVA-L09c432 (b504 Nougat)
zgfg said:
Do you want to go back to EVA-AL10c00 (b540 Oreo) or you want to downgrade to EVA-L09c432 (b504 Nougat)
Click to expand...
Click to collapse
I'm wanting to go back to EVA-AL10c00.
Joshywooful1 said:
I'm wanting to go back to EVA-AL10c00.
Click to expand...
Click to collapse
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
zgfg said:
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
There's no installation guide in the ReleaseDocs folder. It only has several documents in Chinese (including one that tells me to use HiSuite to update my system which I'll not be able to follow as I'm unable to boot into the system). There are no documents that have DLOAD specific instructions.
zgfg said:
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
Never mind what I said before. I've found the installation guide. It's all in Chinese so I had to put it through Google Translate so I could read it.
Joshywooful1 said:
Never mind what I said before. I've found the installation guide. It's all in Chinese so I had to put it through Google Translate so I could read it.
Click to expand...
Click to collapse
Strange, a year ago I downloaded such EVA-AL10c00b528 package from the same site and successfully unbricked.
It did have Installation guide in English
You should create DLOAD folder on your SD card, copy into the file and folder as found in the Software folder (see my screenshot), then make sure battery is 50% or more full, disconnect from USB, switch off, press and keep pressing both Vol+ and Vol-, boot
For your reference, see a similar guide from another service repair package:
https://mega.nz/#!F8UGyYQR!hOeQJyRyb13sKViCPL0XNK-cY5obHetUcvfNqHMJjTg
zgfg said:
Strange, a year ago I downloaded such EVA-AL10c00b528 package from the same site and successfully unbricked.
It did have Installation guide in English
You should create DLOAD folder on your SD card, copy into the file and folder as found in the Software folder (see my screenshot), then make sure battery is 50% or more full, disconnect from USB, switch off, press and keep pressing both Vol+ and Vol-, boot
For your reference, see a similar guide from another service repair package:
https://mega.nz/#!F8UGyYQR!hOeQJyRyb13sKViCPL0XNK-cY5obHetUcvfNqHMJjTg
Click to expand...
Click to collapse
I've just tried to enter the DLOAD mode and it just boots into the screen with a green background and 2 rectangles, a red one near in the upper portion of the screen and a blue one in the lower portion of the screen, as shown in this photo. It stays on this screen for a short amount of time before rebooting into the same screen.
Joshywooful1 said:
I've just tried to enter the DLOAD mode and it just boots into the screen with a green background and 2 rectangles, a red one near in the upper portion of the screen and a blue one in the lower portion of the screen, as shown in this photo. It stays on this screen for a short amount of time before rebooting into the same screen.
Click to expand...
Click to collapse
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
zgfg said:
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
Click to expand...
Click to collapse
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
zgfg said:
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
Click to expand...
Click to collapse
I've attempted to use DC-Phoenix to unbrick my phone and it always fails, saying
Code:
Cannot enter in Recovey mode
. I don't have the right screwdriver to remove the screws from my phone, so I can't do the testpoint method either. Is there anything else I could do?
Joshywooful1 said:
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Click to expand...
Click to collapse
Per your previous Fastboot results, Bootloader is unlocked.
On the Chinese firmware FRP is unlocked by default, there was even no OEM Unlock option in Developers menu
So what is blocking your Fastboot to flash - on the Fastboot screen, bottom part, what does it say, Phone locked (green) or Phone unlocked (red), and similarly, FRP locked or unlocked?!
zgfg said:
Per your previous fastboot results, Bootloader is unlocked.
On the Chinese firmware FRP is unlocked per default, there was even no OEM Unlock setting in Developers menu.
So what is blocking Fastboot to flash - on Fastboot screen, bottom part, what does it say, Phone locked (green) or Phone unlocked (red), and similarly FRP locked or unlocked?!
Click to expand...
Click to collapse
It says
Code:
PHONE Unlocked
and doesn't say anything about FRP lock/unlock.
Joshywooful1 said:
It says Phone unlocked and doesn't say anything about FRP lock/unlock.
Click to expand...
Click to collapse
Yeah, Phone=Bootloader and I just checked, Chinese AL10 does not even display FRP status on the Fastboot screen
Joshywooful1 said:
... I don't have the right screwdriver to remove the screws from my phone, so I can't do the testpoint method either. Is there anything else I could do?
Click to expand...
Click to collapse
Yes, a shame, it's a pentalobe screwdriver but the same is used for iPhones, hence not really so hard to find
And two other options were given in one of my previous answers:
zgfg said:
...
Otherwise, there are on-line services providing paid unbrick support:
...
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
...
Click to expand...
Click to collapse
Btw, it might be valuable for the others to prevent a similar brick, if you describe what you were doing to get such a serious brick where phone can not boot to Recovery or eRecovery, and that flashing (although Bootloader and supposedly FRP are unlocked) and even DLOAD fail
Joshywooful1 said:
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Click to expand...
Click to collapse
What were you doing before the brick? Did it suddenly reboot into the "RGB" screen like the other reported case over here, or were you installing some ROM or kernel? Those "RGBricks" seem to be pretty rare but fatal. How old is your phone?
Let's hope you still have enough write cycles in your eMMC judging from that log...because if that happens it means your phone finally kicked the bucket and needs a eMMC or board change. But let's be optimistic. Try wiping /system with fastboot and check if it fails. Try the testpoint method too
Joshywooful1 said:
Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Click to expand...
Click to collapse
If chinese oreo b540 ROM is installed in your phone and you can boot into bootloader then try extracting recovery_ramdis, kernel, system and Ramdisk from Update.app and flashing it through Fastboot.
I would suggest you to follow this article https://openkirin.net/user_guide/how-to-flash-extracted-partition-images/
and this
https://openkirin.net/user_guide/how-to-extract-partition-images-from-stock-emui-firmware/
Related
So this is my problem
i tried to install Xposed installer and ****ed up
at the end i wiped everything on my phone using twrp
and then (like a total idiot) i flasht the wrong boot.img and recovery.img
my phone now only can boot into rescue mode ( which is useless) and fastboot mode
NOW THE BIGGEST PROBLEM
i cant falsh anything using fastboot and i tried every driver i could find
apperently it must be a special fastboot 2.0 driver
thast btw the same ways my device is listet in device manager in windows 7
PLZZZZZZZ Help
ladres said:
So this is my problem
i tried to install Xposed installer and ****ed up
at the end i wiped everything on my phone using twrp
and then (like a total idiot) i flasht the wrong boot.img and recovery.img
my phone now only can boot into rescue mode ( which is useless) and fastboot mode
NOW THE BIGGEST PROBLEM
i cant falsh anything using fastboot and i tried every driver i could find
apperently it must be a special fastboot 2.0 driver
thast btw the same ways my device is listet in device manager in windows 7
PLZZZZZZZ Help
Click to expand...
Click to collapse
normaly i would say "you fu***** it up because you didn´t read the other threads before you do some random s***" but i´m not going to write it today.
There are no special drivers for fastboot. the "Minimal ADB & Fastboot" package has everything needed.
If you phone isn´t recognized as android device:
- delete the drivers in the device-manager from windows. (Sometimes a restart solve problems)
- disconnect your phone from the computer first.
- boot your phone into fastboot mode.
- reconnect it.
then you should be able to flash via fastboot.
If fastboot shows something like "command not allowed", your device is probably FRP locked right now.
Tuerkay said:
normaly i would say "you fu***** it up because you didn´t read the other threads before you do some random s***" but i´m not going to write it today.
There are no special drivers for fastboot. the "Minimal ADB & Fastboot" package has everything needed.
If you phone isn´t recognized as android device:
- delete the drivers in the device-manager from windows. (Sometimes a restart solve problems)
- disconnect your phone from the computer first.
- boot your phone into fastboot mode.
- reconnect it.
then you should be able to flash via fastboot.
If fastboot shows something like "command not allowed", your device is probably FRP locked right now.
Click to expand...
Click to collapse
well the FRP locked is absolutly true do you know how i can unlock it ?
btw when i uninstall the fastboot driver for my phone and reconnect it only says
driver not found
thx for replay
ladres said:
well the FRP locked is absolutly true do you know how i can unlock it ?
btw when i uninstall the fastboot driver for my phone and reconnect it only says
driver not found
thx for replay
Click to expand...
Click to collapse
you have to search the drivers manualy. path should be minimal adb folder.
the frp unlock can be removed vie developer settings but you can´t access them.
which boot.img and recovery.img did you flash? if it´s from a mate s rom, then it shouldn´t affect your phone.
you could also try something else. take a micro sd card. place the dload folder with your current update.app in it. then boot your phone with vol+ (or vol + and vol-) and power. it then should do an force update.
Tuerkay said:
you have to search the drivers manualy. path should be minimal adb folder.
the frp unlock can be removed vie developer settings but you can´t access them.
which boot.img and recovery.img did you flash? if it´s from a mate s rom, then it shouldn´t affect your phone.
you could also try something else. take a micro sd card. place the dload folder with your current update.app in it. then boot your phone with vol+ (or vol + and vol-) and power. it then should do an force update.
Click to expand...
Click to collapse
I have a CRR L09
I restored everything using a twrp backup from a CRR L00 version
and since i wante to keep my hand off root and everything i decidet to falsh the boot.img and recovery.img
that i extracted from an original UPDATE.APP
i did that all with falshify
btw it seems that i have the right fastboot driver but fastboot wont let me falsh
eaven tho i falshed befor without FRP Unlock
and just so you know
i have sam os x and windows 7 and both give me the same error
lols-Mac-Pro:~ lol$ fastboot devices
UBE0215923001497 fastboot
lols-Mac-Pro:~ lol$ fastboot flash recovery /Users/lol/Desktop/recovery-B303.img
target reported max download size of 471859200 bytes
sending 'recovery' (28226 KB)...
OKAY [ 0.596s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.596s
lols-Mac-Pro:~ lol$
ladres said:
I have a CRR L09
I restored everything using a twrp backup from a CRR L00 version
and since i wante to keep my hand off root and everything i decidet to falsh the boot.img and recovery.img
that i extracted from an original UPDATE.APP
i did that all with falshify
btw it seems that i have the right fastboot driver but fastboot wont let me falsh
eaven tho i falshed befor without FRP Unlock
and just so you know
i have sam os x and windows 7 and both give me the same error
lols-Mac-Pro:~ lol$ fastboot devices
UBE0215923001497 fastboot
lols-Mac-Pro:~ lol$ fastboot flash recovery /Users/lol/Desktop/recovery-B303.img
target reported max download size of 471859200 bytes
sending 'recovery' (28226 KB)...
OKAY [ 0.596s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.596s
lols-Mac-Pro:~ lol$
Click to expand...
Click to collapse
well... i already wrote it in other threads that using an twrp backup, which is not yours can FRP lock you device. since you can´t boot your device, you also can´t remove the FRP lock. with the FRP Lock you can´t flash any files.
so you need an uncorrupted TWRP backup from someone with the same mate s model you have.
if you´re on stock recovery, try what i wrote the last post. Place dload folder with the Update.app for you model on an sd card and boot into update mode with VOL+ (and VOL- depending on the recovery version) and Power button at the same time.
Tuerkay said:
well... i already wrote it in other threads that using an twrp backup, which is not yours can FRP lock you device. since you can´t boot your device, you also can´t remove the FRP lock. with the FRP Lock you can´t flash any files.
so you need an uncorrupted TWRP backup from someone with the same mate s model you have.
if you´re on stock recovery, try what i wrote the last post. Place dload folder with the Update.app for you model on an sd card and boot into update mode with VOL+ (and VOL- depending on the recovery version) and Power button at the same time.
Click to expand...
Click to collapse
no the werid thin is
when i restored the twrp backup it actually booted thats when i tried to falsh the stock recovery and boot image
and i already tried with the hardware buttons
Vol+ gets me to Huawei eRecovery (tries to download firmware over wifi but failes)
Vol- gets me to fastboot mode
and btw that only works when i turn the phone off and hold the button and connect the usb cable
without the cable i automaticly get into rescue mode
with eiter
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed!)
or
Error!
Func NO : 11 (boot image)
Error NO : 2 (load failed!)
You have Ton press vol+ and vol- and power button all at the same time with the cable Unplugged. If you have an Update.App on your SD Card it will automatically Start the process without asking any questions.
Tuerkay said:
You have Ton press vol+ and vol- and power button all at the same time with the cable Unplugged. If you have an Update.App on your SD Card it will automatically Start the process without asking any questions.
Click to expand...
Click to collapse
i already tried that it only takes me to rescue mode
ladres said:
i already tried that it only takes me to rescue mode
Click to expand...
Click to collapse
with how much % does it fail and which reason does it show?
Tuerkay said:
with how much % does it fail and which reason does it show?
Click to expand...
Click to collapse
i get eiter
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed!)
or
Error!
Func NO : 11 (boot image)
Error NO : 2 (load failed!)
an thats it
can you make a photo of the screen this message appears?
it looks like you haven´t done what i have said since these aren´t messages which appear in the update mode.
Here you go
Sent from my HTC One using XDA Free mobile app
ladres said:
Here you go
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
well i don´t know where to start. just give an short explanation about the Huawei Recovery system.
The Huawei Mate S hast 2 ("TWO") recoverys installed. Recovery.img and Recovery2.img. just for safety reason if someone or something f***s up the primary recovery.img (first recovery). the first one is also the one you normaly swap with the TWRP backup.
The Huawei Mate S can be booted in 4 ("four") different modes
1. normal boot into android
2. boot into fastboot&rescue mode
3. boot into reset mode (twrp recovery if you swap recovery.img)
4. boot into update mode
you can reach menu 2-4 with vol+ and/or vol-. As long as you haven´t replaced bot recovery images. the button combinations vary depending on the flashed recovey(2).img version.
mode 4 only starts if you have an FULL UPDATE file in an dload folder in your internal or sd storage.
the update mode is the one that takes up to 30 seconds to start after the vibration. Keep holding the associated buttons and the power button until the device vibrates. then relase the powerbutton but keep holding the other buttons. then wait. after a while a cirlce with "EMUI update" will appear and install the update file you placed into the dload folder.
this method worked for me when i f****ed up and i also found some other thread with the same problem you have. did the same thing i just explained
Tuerkay said:
well i don´t know where to start. just give an short explanation about the Huawei Recovery system.
The Huawei Mate S hast 2 ("TWO") recoverys installed. Recovery.img and Recovery2.img. just for safety reason if someone or something f***s up the primary recovery.img (first recovery). the first one is also the one you normaly swap with the TWRP backup.
The Huawei Mate S can be booted in 4 ("four") different modes
1. normal boot into android
2. boot into fastboot&rescue mode
3. boot into reset mode (twrp recovery if you swap recovery.img)
4. boot into update mode
you can reach menu 2-4 with vol+ and/or vol-. As long as you haven´t replaced bot recovery images. the button combinations vary depending on the flashed recovey(2).img version.
mode 4 only starts if you have an FULL UPDATE file in an dload folder in your internal or sd storage.
the update mode is the one that takes up to 30 seconds to start after the vibration. Keep holding the associated buttons and the power button until the device vibrates. then relase the powerbutton but keep holding the other buttons. then wait. after a while a cirlce with "EMUI update" will appear and install the update file you placed into the dload folder.
this method worked for me when i f****ed up and i also found some other thread with the same problem you have. did the same thing i just explained
Click to expand...
Click to collapse
ok first of all the for all you help so far
secendly i did not whipe the recovery2 file since i never had the option
method 4 didnt work but maybe ist because my micro sd card is in exfat mode
ill try fat32
and one thing i havent mentiond yet is that i cant turn my phone off
i also only can enter fastboot and Huawei eRecovery mode by pressing the volume buttons and then plug the
phone into my computer
ladres said:
ok first of all the for all you help so far
secendly i did not whipe the recovery2 file since i never had the option
method 4 didnt work but maybe ist because my micro sd card is in exfat mode
ill try fat32
and one thing i havent mentiond yet is that i cant turn my phone off
i also only can enter fastboot and Huawei eRecovery mode by pressing the volume buttons and then plug the
phone into my computer
Click to expand...
Click to collapse
you don´t need to power it off. you can also reboot into the updatemenu from fastboot menu. just hold all buttons long enough and wenn the screen goes black, release the powerbutton after vibration.
sd card musst be fat32 i think
Tuerkay said:
you don´t need to power it off. you can also reboot into the updatemenu from fastboot menu. just hold all buttons long enough and wenn the screen goes black, release the powerbutton after vibration.
sd card musst be fat32 i think
Click to expand...
Click to collapse
didnt work
sd card is in fat32
i tried it exsactly like you toled me
and it took me to rescue mode again
btw the Vol up and vol down methoid used to take me to twrp
ive never seen the upadte mode
can you do an factory reset in the eRecovery?
if not, try
fastboot erase userdata
fastboot erase cache
in fastboot&rescue mode.
it´s possible that there is an incremental update file in your internal storage.
which update. app did you use? should be the last working version you used.
Tuerkay said:
can you do an factory reset in the eRecovery?
if not, try
fastboot erase userdata
fastboot erase cache
in fastboot&rescue mode.
it´s possible that there is an incremental update file in your internal storage.
which update. app did you use? should be the last working version you used.
Click to expand...
Click to collapse
eRecovery is aperently just for falshing using huawei server
but mate s seems not to be supportrd
fastboot gives me the same error as usual
sh-3.2# fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2#
i tride B115
and B114
ladres said:
eRecovery is aperently just for falshing using huawei server
but mate s seems not to be supportrd
fastboot gives me the same error as usual
sh-3.2# fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2#
i tride B115
and B114
Click to expand...
Click to collapse
CRR-UL00 or L09?
the eRecovery differs depending on the version used. i for example can factory reset via eRecovery.
It´s also strange that you can´t access the force update mode. this is an basic function you can´t erase.
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....
Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.
oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX
Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!
I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.
Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.
My phone is stuck in boot screen since last night. Powering it off it just boot and stuck again. I've never modded the phone. It's stock with 2 months of life. I can access EMUI recovey menu to wipe cache or factory reset and connecting it to a pc and pressing volumkey down+bootkey It enter in FASTBOOT&RESCUE mode.
Is there something I can do to access phone memory? I really need to save some files.
I thought I could use adb to pull the files I need but I suppose I've usb debug disabled so the device is not recognized. It's recognized by fastboot.
Try to extract the following partitions: boot, recovery, cust & system with Huawei Updater Extractor and flash them manually by.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Of course you need to download the right firmware for your variant.
haky 86 said:
Try to extract the following partitions: boot, recovery, cust & system with Huawei Updater Extractor and flash them manually by.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Of course you need to download the right firmware for your variant.
Click to expand...
Click to collapse
What is the purpose in doing this? And What do u mean with right firmware for your variant?
(my bootloader is locked)
canaio said:
What is the purpose in doing this? And What do u mean with right firmware for your variant?
(my bootloader is locked)
Click to expand...
Click to collapse
I guess you can flash stock images even if your bootloader is locked.
about firmware variant: something like pra-lx1c432b115
try to reflash stock boot.img only if fastboot is recognized, I've the phone about 2 week and no issues for now.
haky 86 said:
I guess you can flash stock images even if your bootloader is locked.
about firmware variant: something like pra-lx1c432b115
try to reflash stock boot.img only if fastboot is recognized, I've the phone about 2 week and no issues for now.
Click to expand...
Click to collapse
Is there any way I can access files on my phone? I really need some recordings
I dont understand why the phone is not seen as adb device. I think usb debug is enabled because I used hisuite some days ago and I think that software needs it enabled
My phone is also stuck at the boot screen, I guess I have the same issue. My phone is also about 2 months old, not rooted, not unlocked, original software. I cannot boot into recovery mode, I can only boot into fastboot&rescue mode while holding the power button and volume down button when attach to the computer by a USB cable. The screen on my phone says the following:
-------
FASTBOOT&RESCUE MODE
Please Connect Usb Cable to
Your Computer and Open Hisuite
Android reboot reason:
AP_S_ABNORMAL
NA
volumekey_down_press_process_func
[android logo]
PHONE Locked
FRP Lock
rescue mode enter..
-------
I tried to flash boot.img and recovery.img (extracted from an update.app through HuaweiUpdateExtractor) but I get the following message in Minimal ADB and Fastboot:
-------
target reported max download size of 471859200 bytes
sending 'boot' (15498 KB)...
OKAY [ 0.625s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time 1.375s
-------
I assume that I'm not able to flash anything because my phone is locked and USB-debugging is not enabled on the phone through settings (and I cannot get there since the phone doesn't boot into Android). When I connect my phone to the PC the Hisuite does open automatically but it doesn't show any phone, nor cannot recover it through that software.
If only I could flash anything on the phone, that would be a step forward in reviving this phone. Does anyone have ideas?
FaceBeppy said:
My phone is also stuck at the boot screen, I guess I have the same issue. My phone is also about 2 months old, not rooted, not unlocked, original software. I cannot boot into recovery mode, I can only boot into fastboot&rescue mode while holding the power button and volume down button when attach to the computer by a USB cable. The screen on my phone says the following:
-------
FASTBOOT&RESCUE MODE
Please Connect Usb Cable to
Your Computer and Open Hisuite
Android reboot reason:
AP_S_ABNORMAL
NA
volumekey_down_press_process_func
[android logo]
PHONE Locked
FRP Lock
rescue mode enter..
-------
I tried to flash boot.img and recovery.img (extracted from an update.app through HuaweiUpdateExtractor) but I get the following message in Minimal ADB and Fastboot:
-------
target reported max download size of 471859200 bytes
sending 'boot' (15498 KB)...
OKAY [ 0.625s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time 1.375s
-------
I assume that I'm not able to flash anything because my phone is locked and USB-debugging is not enabled on the phone through settings (and I cannot get there since the phone doesn't boot into Android). When I connect my phone to the PC the Hisuite does open automatically but it doesn't show any phone, nor cannot recover it through that software.
If only I could flash anything on the phone, that would be a step forward in reviving this phone. Does anyone have ideas?
Click to expand...
Click to collapse
Unlock fastboot. Google it.
p8tgames said:
Unlock fastboot. Google it.
Click to expand...
Click to collapse
I guess you mean unlock bootloader? I emailed Huawei with the question if I could get Unlock Bootloader code. To get that I need the phone's serial number, IMEI number and product ID. The first two I have, the product ID I can't get, because I cannot boot into Android and dial *#*#1357946#*#*. I read somewhere that there is an algorithm to figure out the product ID, there's even an Huawei Product ID Generator.exe, but the P8 lite 2017 isn't supported. If I know the product ID I can get the Unlock Bootloader code, unlock the bootloader and hopefully flash a new recovery and boot and rom.
i have the same issue. how did you fix yours?
haky 86 said:
Try to extract the following partitions: boot, recovery, cust & system with Huawei Updater Extractor and flash them manually by.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Of course you need to download the right firmware for your variant.
Click to expand...
Click to collapse
sir haky no cust.img was in there CRC.img and CURVER.img was only in there
EXE bahotin said:
sir haky no cust.img was in there CRC.img and CURVER.img was only in there
Click to expand...
Click to collapse
Is your bootloader unlocked if yes give a try with above method.
If no go to the nearest service center as it is happening to many devices.
miststudent2011 said:
Is your bootloader unlocked if yes give a try with above method.
If no go to the nearest service center as it is happening to many devices.
Click to expand...
Click to collapse
yes i unlock my bootloader
I am having the same problem I can't flash anything using the ADB & Fastboot and my device is stuck at loading. Can't even access the TWRP =/
Hi, i have the same issue : phone stuck on Huawei Logo, original firmware, bootloader locked.
I cannot unlock bootloader since Huawei unlock plugin has closed.
I can only access fastboot mode but flashing commands seems to be "not allowed".
How did you managed to solve this ?
https://forum.xda-developers.com/p8...on/guide-unbrick-huawei-p8-lite-2017-t3766678
YoussefR said:
https://forum.xda-developers.com/p8...on/guide-unbrick-huawei-p8-lite-2017-t3766678
Click to expand...
Click to collapse
Hi YoussefR, thanks for the answer.
But I cannot enter the eRecoery mode, when I try the phone is still stuck on Huawei Logo
Obviously i cannot access to the playstore neither
Avorsan said:
Hi YoussefR, thanks for the answer.
But I cannot enter the eRecoery mode, when I try the phone is still stuck on Huawei Logo
Obviously i cannot access to the playstore neither
Click to expand...
Click to collapse
Press The Vol.UP+VOL.DOWN+PowerButton at the same time even if the phone is on it will reboot and try to install a frimware it will fail the reboot to eRecovery
If it doesn't
Connect the phone to a USB cable and press the VOL.UP+PowerButton
YoussefR said:
Press The Vol.UP+VOL.DOWN+PowerButton at the same time even if the phone is on it will reboot and try to install a frimware it will fail the reboot to eRecovery
If it doesn't
Connect the phone to a USB cable and press the VOL.UP+PowerButton
Click to expand...
Click to collapse
Like I said, the combination doesn't work, it stuck on huawei logo and it doesn't go futher . The only mode i can access is fastboot with cable + vol down + power.
Avorsan said:
Like I said, the combination doesn't work, it stuck on huawei logo and it doesn't go futher . The only mode i can access is fastboot with cable + vol down + power.
Click to expand...
Click to collapse
Sorry, But these combinations got me into eRecovery
YoussefR said:
Sorry, But these combinations got me into eRecovery
Click to expand...
Click to collapse
I believe you, surely we don't share the same problem. I didn't flash anything on my phone, it just stop booting without a reason, like the original poster said.
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
I've gone through that before, but ended up using DC-Phoenix to unbrick it when it's FRP and bootloader locked. Cost me about $15. There is a post on how to do this but I'll have to search for it again.
Here is the post I used:
https://forum.xda-developers.com/showpost.php?p=71767614&postcount=7
I guess you enter fastboot by Vol- and Power?
Not sure if the following method could help you with, but you can analyze before you go for dc-phoenix:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
scammander said:
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
Click to expand...
Click to collapse
So you can not update via dload method? Did you try booting into recovery (not Recovery)? And you can't update with Update.app, you need to flash update.zip and full_update.zip via TWRP or Recovery. What wanted the owner of this phone to do, that he bricked it ?
Thank you all for your answers. Like I tried to describe: I was not able to access any other mode than fastboot.
"was able": I used DC-Phoenix now and it worked just fine.
Little confusing is that in all tutorials, even the on on the DC site, the UI of the tool is different.
But that's now Problem. The current Version is lot easier. Just "Standard Mode", select Update.app (full), Click Update.
The Phone gets flashed with fastboot, DC will restart it to update mode and will flash again. All automatic.
Really easy.
so you paid 15 USD ?
DallasCZ said:
so you paid 15 USD ?
Click to expand...
Click to collapse
Yes I did, and it worked.
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone.
IMPORTANT: ON XDA-LABS APP THIS POST IS KINDA BROKEN IDK WHY SO LOAD IT IN BROWSER!!!!
If the guide worked for you, please hit thanks button! If you are generous and want to donate pm me
What this can fix:
When booting, you get this error:
Func NO : 10 (boot image)
Error NO : 2 (load image)
When booting to recovery, you get this error:
Func NO : 11 (recovery image)
Error NO : 2 (load image)
Bootloops
Can't boot into fastboot
Can't boot into recovery for other reasons
Can't boot to system for other reasons
ETC...
First thing first, there really isnt a way to keep your data so expect it all to be gone, unless it is saved on an external sd card. Also, this guide is specifically for the PRA-LX1 model, however it might work with other p8 lite 2017 models and a similar method may work with other huawei phones.
Requirements:
The device boots in to fastboot mode. (If it does not, scroll down to problem 1)
You have a pc with a usb port and fastboot/adb installed
You have a micro usb to usb cable.
Unlocked bootloader and oem unlock.
Micro sd card
Problem 1: Can't boot into fastboot?
Try this:
1. Make sure device is fully powered off
2. Connect device to any pc.
3. Press and hold volume- and power button at the same time until your screen turns on.
If this doesn't work then unfortunately i can't help...
Problem 2: Only fastboot boots, but not recovery or os:
Lets start by flashing TWRP...
If your device was on android nougat (7.x.x) or the rom you were flashing was nougat based then do this:
Download this file:
https://drive.google.com/file/d/1TjNHI9FNdwQS2HphsjGfQCHKephibiKn/view
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery *Nameofrecovery.img*
-----------------------------------------------------------------------------------------------------------------
If your device was on android oreo (8.x.x) or the rom you were flashing was oreo based then do this:
Download this file: https://drive.google.com/file/d/190zqju8ZmwZCzI4WXtujgKLFXvvuWTk8/view?usp=sharing
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery_ramdisk *Nameofrecovery.img*
https://www.mrviking.co.uk/440246340
Problem 3: You can only boot into fastboot and TWRP recovery:
Thats OK! Heres how to restore the phone:
IMPORTANT: THE FILES LINKED HERE ARE ONLY FOR PRA-LX1 DEVICES! If your device has a different model number, or these files did not work for you, follow this guide to get files for your device: https://www.mrviking.co.uk/440246340
This will also update your device to android oreo!
Put the micro sd card in your pc.
On your pc download these files:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 (Download 0.3)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1194/g104/v148634/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...altice_all/update_full_PRA-L11_altice_all.zip
http://update.hicloud.com:8180/TDS/...34/f1/full/public/update_data_full_public.zip
Now Rename update_full_PRA-L11_altice_all.zip to update_all_hw.zip
Also rename update_data_full_public.zip to update_data_public.zip
Put all four files: update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater_0.3.zip into one folder on the external sdcard.
Take sdcard out of pc and put it into phone.
Boot into twrp tap on mount and select all partitions
Make sure 'mount system read only' is NOT checked.
Go back to twrp home
Go to install, find the huruupdater zip file
Flash ONLY hurupdater, DO NOT FLASH ANY OTHER ZIPS.
Follow instructions on screen.
Reboot to system and wait for the device to boot.
If it didnt boot, dont worry:
Go back to fastboot mode on your phone and pc, and download this file: https://drive.google.com/file/d/1daIos0yagHk9Kg-5hXLDwNYDHjP_N0EM/view?usp=sharing
Flash it with fastboot using:
fastboot flash recovery_ramdisk *Nameofrecovery.img*
now boot into recovery wipe cache wipe date/factory reset reboot to system
If none of this worked, try this last resort. (Likely won't work but it is worth a shot)
Firstly, place your micro sdcard into your pc. Create a folder called 'dload' in the root of it.
Now, locate the firmware files you downloaded from firmware finder.
Open the main update.zip file and extract the 'UPDATE.APP' file to the 'dload' folder in your sdcard.
Place sdcard back in phone
Make sure phone is powered off. (Can't power it off? Unplug anything connected (charger, pc, etc...) and hold the power button until screen goes black)
Hold all three function keys (VOL+,VOL- and POWER) until screen turns on.
Hope it works and wait
If it worked, please hit thanks button! If you want to donate pm me.
If it DID NOT work, post a reply here and either me or someone else will try and help.
Thanks!
tringo24 said:
I've got the same problem - I can boot to TWRP and bootloader.
I've wiped Dalvik/ART Cache, Cache, Data, System and formatted Data
When I try to flash HuRUpdater_0.4.zip I get:
Error finding input device
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/HuRUpdater_0.4.zip'
I've tried copying UPDATE.APP to 'dload' folder on external SD card, and EMUI hangs at 5%.
Is there anything else I can try? What does "Updater process ended with ERROR: 1" actually mean? I've googled it but haven't found anything useful.
Any help would be really appreciated!
Click to expand...
Click to collapse
Top tip - always follow all of the instructions. the version of TWRP listed in the instructions is the only one to use. I was using an incomaptible version. My phone if fixed!
tringo24 said:
I've got the same problem - I can boot to TWRP and bootloader.
I've wiped Dalvik/ART Cache, Cache, Data, System and formatted Data
When I try to flash HuRUpdater_0.4.zip I get:
Error finding input device
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/HuRUpdater_0.4.zip'
I've tried copying UPDATE.APP to 'dload' folder on external SD card, and EMUI hangs at 5%.
Is there anything else I can try? What does "Updater process ended with ERROR: 1" actually mean? I've googled it but haven't found anything useful.
Any help would be really appreciated!
Click to expand...
Click to collapse
Always use TWRP from OP
And if its not working, try Flashing Stock recovery and boot it and do tap some options e.g. reset/ clear cache etc. ( I got my mobile fixed via this method as Internal Memory got corrupted because of incompatible TWRP )
For problem 1 fix : Fully shutdown , connect the phone to via usb to pc , and fast hold down the volume - . Cheers
Edit : or the same : usb , power and volume - till you see the huawei logo , then just hold volume -
Frp and boot locked. dload/UPDATE.APP in fat32 formatted sd still error At 5%. Any way to recovery?
Thank you !!!
You saved my phone :victory:
lupastro82 said:
Frp and boot locked. dload/UPDATE.APP in fat32 formatted sd still error At 5%. Any way to recovery?
Click to expand...
Click to collapse
Force shut down the device (Hold power button) if it is on.
Connect to a pc
Hold down POWER and VOL- buttons untill screen turns on
If you see a screen with an android robot saying FASTBOOT at the top let me know, if not tell me that :good:
MrViking said:
Force shut down the device (Hold power button) if it is on.
Connect to a pc
Hold down POWER and VOL- buttons untill screen turns on
If you see a screen with an android robot saying FASTBOOT at the top let me know, if not tell me that :good:
Click to expand...
Click to collapse
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
I'm exactly in ur same situation
I need ****ing help to unlock frp then i can solve the rest by my own.
lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
Have you tried flashing stock recovery img from fastboot?
MrViking said:
Have you tried flashing stock recovery img from fastboot?
Click to expand...
Click to collapse
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Code:
Attention!
Please update system again
Error NO : 10 (boot image) / or
Error NO : 2 (load failed)
if i reboot/power on with both volume button, check dload recovery, but still failed (damned huawei!!!).
now i check to work via fastboot. thanks.
---
[email protected]:~$ sudo $(which fastboot) flash recovery ./Scrivania/twrp-3.2.1-0-twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.152s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.158s
[email protected]:~$ sudo $(which fastboot) oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
[email protected]:~$
[email protected]:~$ sudo $(which fastboot) flash recovery_ramdisk ./Scrivania/recovery.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (11204 KB)...
OKAY [ 0.362s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
[email protected]:~$ sudo $(which fastboot) boot ./Scrivania/recovery.img
downloading 'boot.img'...
OKAY [ 0.378s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.381s
[email protected]:~$
Click to expand...
Click to collapse
lupastro82 said:
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Code:
Attention!
Please update system again
Error NO : 10 (boot image) / or
Error NO : 2 (load failed)
if i reboot/power on with both volume button, check dload recovery, but still failed (damned huawei!!!).
now i check to work via fastboot. thanks.
---
Click to expand...
Click to collapse
Wow thats a pretty bad brick. First try to boot to recovery like this:
1. Make sure phone is off.
2. Hold power and volume up until screen goes on.
3. When screen goes on quickly take fingers off buttons.
If it does not work, I think your only hope is to use funky huawei.
Do what this guy did (read the bottom of the first post)
https://forum.xda-developers.com/honor-7x/development/frp-lock-help-to-unbrick-honor-7x-t3769345
lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
Can you update to stock through erecovery via wifi? I had my phone frp locked + bl locked + bricked system. eRecovery was the only way out to get into a working system.
The unlock tool that costs too much is b.s and only works if it was locked because of Google Play account (tried it, did not unlock my frp).
After erecovery update and having a system, google play account was also locked because of stock firmware, this time I used the unlock tool. I used firmware finder afterwards for forcing an oreo update (because bl unlocking was grayed out). After oreo update, i enabled bl unlock from dev options and unlocked my bl again through fastboot. frp got unlocked along the way, i forgot when.
i can access in eRecovery, but when i check to download by wifi i still receive: "Getting package info failed" :/
-
via dload (8gb sd in fat 32 with only dload folder and old release UPDATE.APP inside it - but tested with more...) stuck for minuts at 5%, then reboot!
lupastro82 said:
i can access in eRecovery, but when i check to download by wifi i still receive: "Getting package info failed" :/
-
via dload (8gb sd in fat 32 with only dload folder and old release UPDATE.APP inside it - but tested with more...) stuck for minuts at 5%, then reboot!
Click to expand...
Click to collapse
Did you try what I mentioned?
MrViking said:
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Wow thats a pretty bad brick. First try to boot to recovery like this:
1. Make sure phone is off.
2. Hold power and volume up until screen goes on.
3. When screen goes on quickly take fingers off buttons.
If it does not work, I think your only hope is to use funky huawei.
Do what this guy did (read the bottom of the first post)
https://forum.xda-developers.com/honor-7x/development/frp-lock-help-to-unbrick-honor-7x-t3769345
Click to expand...
Click to collapse
sure yes, ill try, and enter in dload mode (but still fail) :/
MrViking said:
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone.
If the guide worked for you, please hit thanks button! If you are generous and want to donate pm me
What this can fix:
When booting, you get this error:
Func NO : 10 (boot image)
Error NO : 2 (load image)
When booting to recovery, you get this error:
Func NO : 11 (recovery image)
Error NO : 2 (load image)
Bootloops
Can't boot into fastboot
Can't boot into recovery for other reasons
Can't boot to system for other reasons
ETC...
First thing first, there really isnt a way to keep your data so expect it all to be gone, unless it is saved on an external sd card. Also, this guide is specifically for the PRA-LX1 model, however it might work with other p8 lite 2017 models and a similar method may work with other huawei phones.
Requirements:
The device boots in to fastboot mode. (If it does not, scroll down to problem 1)
You have a pc with a usb port and fastboot/adb installed
You have a micro usb to usb cable.
Unlocked bootloader and oem unlock.
Micro sd card
Problem 1: Can't boot into fastboot?
Try this:
1. Make sure device is fully powered off
2. Connect device to any pc.
3. Press and hold volume- and power button at the same time until your screen turns on.
If this doesn't work then unfortunately i can't help...
Problem 2: Only fastboot boots, but not recovery or os:
Lets start by flashing TWRP...
If your device was on android nougat (7.x.x) or the rom you were flashing was nougat based then do this:
Download this file:
https://drive.google.com/file/d/1TjNHI9FNdwQS2HphsjGfQCHKephibiKn/view
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery *Nameofrecovery.img*
-----------------------------------------------------------------------------------------------------------------
If your device was on android oreo (8.x.x) or the rom you were flashing was oreo based then do this:
Download this file: https://drive.google.com/file/d/190zqju8ZmwZCzI4WXtujgKLFXvvuWTk8/view?usp=sharing
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery_ramdisk *Nameofrecovery.img*
https://www.mrviking.co.uk/440246340
Problem 3: You can only boot into fastboot and TWRP recovery:
Thats OK! Heres how to restore the phone:
IMPORTANT: THE FILES LINKED HERE ARE ONLY FOR PRA-LX1 DEVICES! If your device has a different model number, or these files did not work for you, follow this guide to get files for your device: https://www.mrviking.co.uk/440246340
This will also update your device to android oreo!
Put the micro sd card in your pc.
On your pc download these files:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 (Download 0.3)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1194/g104/v148634/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...altice_all/update_full_PRA-L11_altice_all.zip
http://update.hicloud.com:8180/TDS/...34/f1/full/public/update_data_full_public.zip
Now Rename update_full_PRA-L11_altice_all.zip to update_all_hw.zip
Also rename update_data_full_public.zip to update_data_public.zip
Put all four files: update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater_0.3.zip into one folder on the external sdcard.
Take sdcard out of pc and put it into phone.
Boot into twrp tap on mount and select all partitions
Make sure 'mount system read only' is NOT checked.
Go back to twrp home
Go to install, find the huruupdater zip file
Flash ONLY hurupdater, DO NOT FLASH ANY OTHER ZIPS.
Follow instructions on screen.
Reboot to system and wait for the device to boot.
If it didnt boot, dont worry:
Go back to fastboot mode on your phone and pc, and download this file: https://drive.google.com/file/d/1daIos0yagHk9Kg-5hXLDwNYDHjP_N0EM/view?usp=sharing
Flash it with fastboot using:
fastboot flash recovery_ramdisk *Nameofrecovery.img*
now boot into recovery wipe cache wipe date/factory reset reboot to system
If none of this worked, try this last resort. (Likely won't work but it is worth a shot)
Firstly, place your micro sdcard into your pc. Create a folder called 'dload' in the root of it.
Now, locate the firmware files you downloaded from firmware finder.
Open the main update.zip file and extract the 'UPDATE.APP' file to the 'dload' folder in your sdcard.
Place sdcard back in phone
Make sure phone is powered off. (Can't power it off? Unplug anything connected (charger, pc, etc...) and hold the power button until screen goes black)
Hold all three function keys (VOL+,VOL- and POWER) until screen turns on.
Hope it works and wait
If it worked, please hit thanks button! If you want to donate pm me.
If it DID NOT work, post a reply here and either me or someone else will try and help.
Thanks!
Click to expand...
Click to collapse
Cheers Bruh Thank u so MUCH
Blackblock92 said:
Cheers Bruh Thank u so MUCH
Click to expand...
Click to collapse
No problem! Glad to hear it works
I've made a tutorial 1 day before you ^^
Hello i've made a tutorial on my thread for my solution to unbrick it so if you need to unbrick your phone with a different method
you can use my tutorial it has worked perfecty on my p8 lite 2017 and now he's on oreo
my phone personnaly was totaly broken i flashed some random things on my phone etc this is working 100% cause you are about to clear all the old android system for the new oreo one so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash dts DTS.img
fastboot flash efi EFI.img
(i'm not putting erecorery imgs cause we cannot touch them it's an ultimate security from os :) )
fastboot flash fastboot FASTBOOT.img
fastboot flash hifi HIFI.img (only if you are the wifi is not working ;) )
fastboot flash kernel KERNEL.img
fastboot flash modem_fw MODEM_FW.img
fastboot flash modemnvm_update MODEMNVM_UPDATE.img
fastboot flash odm ODM.img
fastboot flash package_type PACKAGE_TYPE.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash sensorhub SENSORHUB.img
fastboot flash system SYSTEM.img
fastboot flash teeos TEEOS.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash verlist VERLIST.img
fastboot flash xloader XLOADER.img
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29!
btw that my first tutorial tell me if it's good ^^
RedFiredu29 said:
Hello i've made a tutorial on my thread for my solution to unbrick it so if you need to unbrick your phone with a different method
you can use my tutorial it has worked perfecty on my p8 lite 2017 and now he's on oreo
my phone personnaly was totaly broken i flashed some random things on my phone etc this is working 100% cause you are about to clear all the old android system for the new oreo one so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29!
btw that my first tutorial tell me if it's good ^^
Click to expand...
Click to collapse
That's interesting, never heard of that method!
However there are many good working twrps for oreo, especially the one by Dil3mm4.
MrViking said:
That's interesting, never heard of that method!
However there are many good working twrps for oreo, especially the one by Dil3mm4.
Click to expand...
Click to collapse
Yes i love searching for new solutions on this device but i never heard good unbrick methods for this phone
until our methods ^^
If you read this on XDA labs then please load it in the browser as for some reason lots of text is missing in xda labs.
Thanks ?