Please assist! P10 lite (WAS-LXA1) bricked. - Huawei P10 Lite Questions & Answers

Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s

korval said:
Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s
Click to expand...
Click to collapse
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.

eldorado999 said:
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.
Click to expand...
Click to collapse
Thanks for your reply but the phone is permanently stuck on a totally black screen with fastboot. Pressing power+vol keys do nothing. I can't get to erecovery or the normal white screen/bootloader/fastboot screen. I am still able to send fastboot commands.
:crying:
C:\Windows\system32>fastboot oem get-product-model
...
(bootloader) WAS-LX1A
OKAY [ 0.003s]
C:\Windows\system32>fastboot oem get-build-number
...
(bootloader) :WAS-LX1AC432B198
OKAY [ 0.003s]
finished. total time: 0.003s
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.001s

If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!

korval said:
If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!
Click to expand...
Click to collapse
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.

Tiagohsoares said:
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.
Click to expand...
Click to collapse
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...

korval said:
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...
Click to expand...
Click to collapse
If you can flash and boot recovery try with hwota7 to install to install stock rom...

Related

[Q] Bricked? No Bootloader and no Sytem

Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
- Wiped everything
- Forgot to copy the .zip files - so thats the point where everything went wrong
- Tried to upload it via adb push - failed when I wanted to install the zip
- Startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
GedBlake said:
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
Click to expand...
Click to collapse
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
I see the charging animation and holding the power button for 30 second didnt help.
wtherrell said:
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Downloads/nakasi-jwr66y » sudo ./flash-all.sh
Password:
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.577s]
finished. total time: 0.577s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.026s]
finished. total time: 1.026s
erasing 'recovery'...
OKAY [ 0.852s]
finished. total time: 0.852s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.488s]
finished. total time: 0.488s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.493s]
finished. total time: 6.493s
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
FAILED
Device version-bootloader is '4.18'.
Update requires '4.23'.
finished. total time: 0.139s
Click to expand...
Click to collapse
hd21337 said:
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Click to expand...
Click to collapse
Maybe not... the v4.23 bootloader from Jellybean 4.3 build JWR66Y is known to cause issues when fastboot flashing back to factory stock. For this reason, it is recommended you replace that version of the bootloader with the one from build JWR66V. It's still, ostensibly, the same bootloader, but seems to fastboot flash OK.
As build JWR66V is now no longer available on the Google Developers website, somebody has extracted and uploaded the old bootloader from build JWR66V here. (You might have to scroll down a little for the link).
Oh.... and ADB devices doesn't work when you're in the bootloader... it requires a fully booted Android OS to work.
The command I think you're looking for is fastboot devices
Rgrds,
Ged.
hd21337 said:
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
Click to expand...
Click to collapse
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
jkkk88 said:
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
Click to expand...
Click to collapse
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...that suggested to me, the known issue with the bootloader from build JWR66Y as detailed here (in red letters, at the very top of the first post in the thread), and discussed here... as being the likely cause of the problem.
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Good luck.
Rgrds,
Ged.
GedBlake said:
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Click to expand...
Click to collapse
My concern was that OP could not start (deleted ) recovery from bootloader menu. He should look into stickies. Nexus is still alive and should get new bootloader as you recommended from another build.
Hi guys (@GedBlake and @jkkk88),
sorry for the late answer.
I just tried to run the flash-all.sh with the other bootloader image... but its worse than before.
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.580s]
finished. total time: 0.580s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.769s]
finished. total time: 0.769s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.854s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.489s]
finished. total time: 0.489s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.494s]
finished. total time: 6.495s
sending 'bootloader' (2100 KB)...
OKAY [ 0.267s]
writing 'bootloader'...
OKAY [ 9.376s]
finished. total time: 9.643s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
Click to expand...
Click to collapse
So and at this point, he stuck for about 20 minutes - I aborted it because he didnt move on. And now the N7 is dead. No power charging icon and animation and I cant turn it on (30 seconds holding power button etc.).
So I think I just killed it
Any ideas if there is an another reset trick etc.?
Thanks!

brick?

Gave my 2012 N7 to my nephew, a month later it's frozen 'Google' in the center and a green arrow / start up top. Using the vol. keys I can cycle between start/reboot bootloader/recovery mode/power off, selecting anything but power off loops.
Also, I had to reinstall the sdk but 'adb devices' shows nothing. Any hope of bringing this back to life?
joe2262 said:
Gave my 2012 N7 to my nephew, a month later it's frozen 'Google' in the center and a green arrow / start up top. Using the vol. keys I can cycle between start/reboot bootloader/recovery mode/power off, selecting anything but power off loops.
Also, I had to reinstall the sdk but 'adb devices' shows nothing. Any hope of bringing this back to life?
Click to expand...
Click to collapse
If you are in fastboot, adb commands will not work, you need to use "fastboot devices" to see if you are connected. If you are flash a recovery from fastboot and you can work fairly easily from there. Is the bootloader locked or unlocked?
EpJoker said:
If you are in fastboot, adb commands will not work, you need to use "fastboot devices" to see if you are connected. If you are flash a recovery from fastboot and you can work fairly easily from there. Is the bootloader locked or unlocked?
Click to expand...
Click to collapse
Yep, agreed...
joe2262 said:
Gave my 2012 N7 to my nephew, a month later it's frozen 'Google' in the center and a green arrow / start up top. Using the vol. keys I can cycle between start/reboot bootloader/recovery mode/power off, selecting anything but power off loops.
Also, I had to reinstall the sdk but 'adb devices' shows nothing. Any hope of bringing this back to life?
Click to expand...
Click to collapse
Hi, joe2262...
'adb devices' will not show anything if the device is booted into fastboot mode.
The command you need is 'fastboot devices'...
This will confirm you have a working FASTBOOT connection... and from which you can run fastboot commands... such as fastboot flashing a Custom Recovery (CWM or TWRP).
Or alternatively, fastboot flashing back to factory stock.
Either way... I suspect your Nexus 7 is likely recoverable.
At worst, it's just 'softbricked'.
Rgrds,
Ged.
Yes, it's unlocked but I want to go to a stock install.
C:\Users\joe\Desktop\android\android-sdk-windows\nakasi-jdq39>flash-all
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.016s]
finished. total time: 0.016s
sending 'bootloader' (2096 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.262s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.640s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
Press any key to exit...
??????????????????????
It worked fine months ago when I went back to stock. Damn kids!
Do I need to format boot, recovery and system, is that the proble,m?
Sent from my SM-T310 using xda premium

Nakasi - dead for good ?

Hello people,
I think, I've killed my nexus7 nakasi - 16GB model for ever today. Could you please help me try to resurrect it, or did I really kill him ?
Before, I was using unlocked, SuperSU rooted, KK 4.4.4 with TWRP bootloader and disabled some services (to stop stupid ota notifications coming up).
Today I wanted to try 5.1.1 (LMY47V), so I downloaded the ota, unzipped it, loaded adb, reboot into bootloader and ran flash-all.bat, as usually (I have already done it coulpe times before and never had any problems), until now.
Everything was running fine, until rebooting into bootloader ... ok.. waiting for device. The command line has stuck, so I removed table, terminated job, and tried booting bootloader by volume- & power. Nothing.
Please find my log output below.
Code:
D:\temp\adb>adb reboot bootloader
D:\temp\adb>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.022s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 0.033s]
finished. total time: 0.036s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.270s
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.039s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.319s]
finished. total time: 0.322s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.775s]
finished. total time: 8.778s
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
OKAY [ 1.249s]
finished. total time: 1.524s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
^CTerminate batch job (Y/N)? y
Is there anything I can do to revive him ? Or is he dead now ?
I have tried:
VOL+ VOL- POWER
VOL- POWER
Disconnecting battery + combination of previous before & after battery removal
Connecting power + combination of previous before & after battery removal
When i connect it to my pc now, I can hear sound of new device connected - in APX mode.
Holding POWR VOL+ VOL- for 15 sec, causes tablet to disconnect and connect again in APX, but bootloader won't start.
Plugging it on charger does nothing, battery indicator doesn't show up.
Please help !
remusator said:
Hello people,
I think, I've killed my nexus7 nakasi - 16GB model for ever today. Could you please help me try to resurrect it, or did I really kill him ?
Before, I was using unlocked, SuperSU rooted, KK 4.4.4 with TWRP bootloader and disabled some services (to stop stupid ota notifications coming up).
Today I wanted to try 5.1.1 (LMY47V), so I downloaded the ota, unzipped it, loaded adb, reboot into bootloader and ran flash-all.bat, as usually (I have already done it coulpe times before and never had any problems), until now.
Everything was running fine, until rebooting into bootloader ... ok.. waiting for device. The command line has stuck, so I removed table, terminated job, and tried booting bootloader by volume- & power. Nothing.
Please find my log output below.
Code:
D:\temp\adb>adb reboot bootloader
D:\temp\adb>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.022s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 0.033s]
finished. total time: 0.036s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.270s
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.039s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.319s]
finished. total time: 0.322s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.775s]
finished. total time: 8.778s
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
OKAY [ 1.249s]
finished. total time: 1.524s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
^CTerminate batch job (Y/N)? y
Is there anything I can do to revive him ? Or is he dead now ?
I have tried:
VOL+ VOL- POWER
VOL- POWER
Disconnecting battery + combination of previous before & after battery removal
Connecting power + combination of previous before & after battery removal
When i connect it to my pc now, I can hear sound of new device connected - in APX mode.
Holding POWR VOL+ VOL- for 15 sec, causes tablet to disconnect and connect again in APX, but bootloader won't start.
Plugging it on charger does nothing, battery indicator doesn't show up.
Please help !
Click to expand...
Click to collapse
Hi, remusator...
Sorry to be the bearer of bad news, but it sounds like your Nexus 7 is hardbricked. Both APX mode and the lack of the battery charging animation are classic hallmarks of a bootloader that may have have become corrupted, erased or accidentally overwritten.
APX mode is the state the N7 defaults to in the absence of a working bootloader, and with the expectation that somebody with the necessary software tools and knowledge will be able to nvFlash a replacement bootloader.
Unfortunately, there is no universal nvFlash tool available for the Nexus 7. The only way of accessing nvFlash on the Nexus 7 is, if you had, at some previous point, created your own unique Nexus 7 device dependant 'wheelie' blobs via the Flatline procedure.
So, without a working bootloader, the Nexus 7 cannot boot, nor can it be reflashed via fastboot commands (since it's the bootloader that 'accepts' those commands).
The only option (other than via nvFlash with previously generated Flatline 'wheelie' blobs, and which I suspect you don't have) is to have the motherboard replaced.
I have read accounts here on XDA of people sourcing Nexus 7 replacement motherboards from various online sources, and performing the replacement themselves. I don't know how easy or difficult it is, or how much it might cost (probably not much), but with a dead bootloader, it's likely the only way of resurrecting your Nexus 7.
Good luck...
Rgrds,
Ged.
Addendum: I assume you've tried all of these (that might be applicable)...
[REF] Nexus 7 Button Combinations
http://forum.xda-developers.com/showthread.php?t=2133986
----

Help p9 lite, black screen how to fix it

Good afternoon to all, I need a lot of help. I have a p9 lite VNS-L23 C605B120, try to install the rom revolution nougat, unlock the bootloader, install the recovery and from there an update file, when I finish, I reset and the phone left with the black screen, I connect it, the PC and I recognize it: Android bootloader interface, do not enter with the 3 buttons: vol + vol - and button on.
I need help on how I can flash it, with some program or how I can fix it, and what are the necessary files ... Thank you very much already.
Pd: the HiSuit of hawei is opened every time I connect the phone to the PC, but it does not allow me to recover the system, at the beginning it leaves: it is acceded to the system recovery mode, I click to recover system and then leaves, the device Does not support system recovery.
Same here unfortunately
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Potato997 said:
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Click to expand...
Click to collapse
This is in flashboot mode, and yes unlock bootloader, but black screen, allows to restart with commands, but unfortunately I do not have much knowledge about this, I hope help, what steps can I take to be able to turn it on.
Try to flash again TWRP and boot to recovery.
By fastboot I can reset, install twrp, reboot, but still black screen, there is no vibration, but when connecting the phone, appears in android bootloader interface. What else can I do with commands
As I said, can you boot to TWRP?
Potato997 said:
As I said, can you boot to TWRP?
Click to expand...
Click to collapse
See
hanzox5 said:
See
Click to expand...
Click to collapse
....
But no reboot in recovery
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13810 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.788s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.143s]
finished. total time: 1.862s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (331661 KB)...
OKAY [ 7.077s]
writing 'cust'...
OKAY [ 8.053s]
finished. total time: 15.149s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (452763 KB)...
OKAY [ 10.992s]
writing 'system'...
OKAY [ 11.640s]
sending sparse 'system' (458056 KB)...
OKAY [ 10.877s]
writing 'system'...
OKAY [ 11.137s]
sending sparse 'system' (459104 KB)...
OKAY [ 11.816s]
writing 'system'...
OKAY [ 12.201s]
sending sparse 'system' (457466 KB)...
OKAY [ 11.096s]
writing 'system'...
OKAY [ 11.214s]
sending sparse 'system' (460756 KB)...
OKAY [ 11.049s]
writing 'system'...
OKAY [ 11.190s]
sending sparse 'system' (135249 KB)...
OKAY [ 3.234s]
writing 'system'...
OKAY [ 3.302s]
finished. total time: 119.793s
C:\Program Files (x86)\HiSuite\hwtools>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\HiSuite\hwtools>
Reboot to recovery in this way: shut down the phone, press volume up + power button
Factory reset
Reboot
Do not enter recovery, still on black screen, can tell me which software I can flash it
I already told you like three times.. try both TWRP and stock recovery..
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
hanzox5 said:
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
Click to expand...
Click to collapse
fastboot boot recovery.img
Try that.
Also you should try the three buttons method now.
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
hanzox5 said:
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
Click to expand...
Click to collapse
ಠ_ಠ
Weird.
479/5000
Several times I installed TWRP and stock recovery, and I can not enter any of the 2 forms and even with the three buttons, I even purchase a micro SD of 32gb class 10, with this saying that the SD was the one that did not work.
Please, let's go again, I recommend doing from 0 to try to solve this blessed problem. That I should be doing, it will be possible to clean the cache and user data from fastboot, and from there to do something more.
Have you tried three button method with update.app in dload folder in SD card?
If yes, did it gave you some error/did the update started/when did it stopped?
If I have the sd, and inside the Dload folder, update.app, but it does nothing.

Can't flash TWRP with unlocked bootloader

Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
roelprincen said:
Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
Click to expand...
Click to collapse
same with me ?
Try to relock and then unlock. I've had this problem too after downgrade to mm by official Huawei rollback package. Then phone and other tools shows than phone is unlocked and it was unable to flash recovery.
if it says wrong password it means you got the wrong password. it will say it's already unlocked if you try unlocking it while it's unlocked
My phone was unlocked with Potato v2.0.1, with working TWRP, rooted etc...
I solved this problem that arose after unsuccesfully install custom Rom, restore backup of stock rom, install update through dload and many many other attempts at improvement of my smartphone :-( No more time again!!!
Probably installing update through Dload will relock bootloader, but in the fastboot mode it says bootloader still unlocked.
Before I did all this, I had an original stock rom.
1: Relock bootloader with PotatoNV v2.0.1 (You need to open case and connect tespoint by wire - look on Youtube, i´ve find it there, also you need "Huawei testpoint drivers")
2: Factory reset
3: Install any update stock rom with Dload (Vol up + Vol down + power)
4: Factory reset
5: Developer options-turn on OEM unlock and USB debbuging
6:Unlock bootloader with PotatoNV v2.0.1 - keep password generated by Potato
7:Multitool 8 for Huawei - in the bootloader state unlock bootloader again - use password generated by Potato
8:Multitool 8 for huawei - install TWRP - it says "Succesfully installed" - TWRP works, root is possible. Yeah!!!
May be this is not right way to solve this, but for me it workś..

Categories

Resources