Related
Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?
is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images
theyau said:
is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Its always locked, if I unlock the bootloader its automatically re-locking after reboot
Bump
any one has any idea please ?
deadwolf666 said:
Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?
Click to expand...
Click to collapse
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.
If simply flashing factory images, an unlock should not be necessary. Is customer wanting you to try and preserve data?
efrant said:
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.
Click to expand...
Click to collapse
Thanks for the answer but the wierd problem is that after I unlock the bootloader and try to flash any thing I get":
sending 'bootloader' (2188 KB)... FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
and after I reboot it shows that the bootloader is locked
I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img" and I get adb access.
ant thing I can do from here ?
deadwolf666 said:
I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img"
Click to expand...
Click to collapse
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
efrant said:
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Click to expand...
Click to collapse
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
deadwolf666 said:
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
deadwolf666 said:
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Have a look here.
efrant said:
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
Have a look here.
Click to expand...
Click to collapse
Procedure #1 is not working I get FAILED command write failed unknown error
Procedure #2 I tryed a few times on different pc (also different OS) and never got the software to recognize the phone (any way Ill try again and update)
thanks for the link will read it soon ^^
Cant make the NPST recognize the phone ;\
while booting custom recovery I cant mount any partition and the bootloader remains locked after reboot.
Any thing else to try ?
Team Win Recovery Project 3.0.2
WARNING: The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
NOTICE: The LG G5 H830 currently has flashing locked!
You will need to use a tool to get around this limitation. At the moment, Team Win nor myself cannot provide anything for this.
The community, and user @tungkick has however provided an alternative method of flashing, which can be done via a full firmware flash using a TOT file.
See here for instructions: http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
A message to those with other variants of the G5:
Should there be a time where your flashing mechanisms get cracked, simply mention my name on this thread or via private message and I would be happy to create a thread with TWRP for your device.
I have device trees ready for ALL variants of the G5, pending their unlock!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://twrp.me/devices/lgg5h830.html
CHANGES
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
LG encryption is not supported yet in TWRP 3. Your device will hang for a while when trying to enter a password. Skip it.
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
Device tree: https://github.com/jcadduono/android_device_lge_h850 (International)
Device tree: https://github.com/jcadduono/android_device_lge_h830 (T-Mobile)
Kernel sources: https://github.com/jcadduono/nethunter_kernel_g5/tree/twrp-6.0 (recommend using stock-6.0 branch for your custom kernels!)
TWRP: https://github.com/omnirom/android_bootable_recovery
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - LG G5, Tool/Utility for the T-Mobile LG G5
Contributors
jcadduono, The Team Win Recovery Project team
Source Code: https://github.com/jcadduono/android_device_lge_h830
Version Information
Status: Testing
Created 2016-04-01
Last Updated 2016-05-23
I'll be able to test at about 7PM tonight.
I'm interested in assisting.
i may be able to do it in a few hours as well but until then, I wanted to ask, is it not possible to fastboot boot <img> without flashing it? Only asking because that's what i've been doing lately with my huawei watch for testing without overwriting my recovery.
tried it get unknown command
joemossjr said:
tried it get unknown command
Click to expand...
Click to collapse
Same
Code:
fastboot flash recovery twrp-3.0.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (19560 KB)...
OKAY [ 0.488s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.516s
I wonder if we need to put the phone into download mode for it to take the flash... Not sure how to get there. The old hold volume up and insert usb cable trick from the G4 isn't working for me.
joemossjr said:
tried it get unknown command
Click to expand...
Click to collapse
Awesome, anyone else? Looks like they really did lock it.
fastboot flash returns unknown command
fastboot boot returns unknown command
It seems that attempting to send an unsigned boot image returns in unknown command. I'm assuming that's just a generic error code returned by qualcomm secure flash due to invalid signature, rather than the command actually being unknown. (maybe fastboot does not have "invalid signature" return codes?)
im getting the same cant flash it apparently they put us in a cage and only unlocked one out of two locks
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
This sucks
Sent from my LG-H830 using Tapatalk
joemossjr said:
im getting the same cant flash it apparently they put us in a cage and only unlocked one out of two locks
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
This sucks
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
does fastboot flash:recovery twrp.img work?
EDIT: nm gives syntax error
bigbiff said:
does fastboot flash:recovery twrp.img work?
Click to expand...
Click to collapse
Ill try hold on
Sent from my LG-H830 using Tapatalk
bigbiff said:
does fastboot flash:recovery twrp.img work?
Click to expand...
Click to collapse
Or:
fastboot flash recovery recovery.img
fastboot flash recovery twrp.img didn't work. Fails with the unknown command error.
fastboot flash:recovery twrp.img doesn't work because it doesn't like the syntax.
mhhh, very strange, it seems a "custom unlocked" bootloader like Meizu products....
I hope to be wrong
But the command to unlock bootloader hasn't changed? In the 6P its "fastboot flashing unlock"
https://source.android.com/security/verifiedboot/verified-boot.html
No visible recovery partition available
Take a look at this post, and see where would recovery be hiding (actually hiding, or new name)
http://forum.xda-developers.com/showpost.php?p=66121499&postcount=35
Killua96 said:
But the command to unlock bootloader hasn't changed? In the 6P its "fastboot flashing unlock"
https://source.android.com/security/verifiedboot/verified-boot.html
Click to expand...
Click to collapse
I was already unlocked and tried to run that command earlier and it didn't work at all, as in, didn't like the syntax at all. I updated my fastboot and ran it just now on my already unlocked device:
Code:
fastboot flashing unlock
...
(bootloader) Device already : unlocked!
OKAY [ 0.020s]
finished. total time: 0.021s
Locking / unlocking with the newer fastboot won't yield any different results will it?
spanky34 said:
I was already unlocked and tried to run that command earlier and it didn't work at all, as in, didn't like the syntax at all. I updated my fastboot and ran it just now on my already unlocked device:
Code:
fastboot flashing unlock
...
(bootloader) Device already : unlocked!
OKAY [ 0.020s]
finished. total time: 0.021s
Locking / unlocking with the newer fastboot won't yield any different results will it?
Click to expand...
Click to collapse
Still it's strange that both commands work, in 6P the other one doesn't work givingi the unknown command error.
this is a custom bootloader by LG ...
Nothing real unlocked here....
wolfgart said:
this is a custom bootloader by LG ...
Nothing real unlocked here....
Click to expand...
Click to collapse
I'm beginning to fear the same. :\
need to dm-verity OFF
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
anujagraj said:
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Click to expand...
Click to collapse
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone's bootloader logs, I can see: "Mismatched partition size (recovery).
Please help!
Lennyz1988 said:
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
Click to expand...
Click to collapse
Hi,
Safe mode is not helping. Same loop is continuing.
Also, I am not able to flash TWRP custom recovery. I am getting the following message:
(bootloader) Preflash validation failed
FAILED (remote failure)
In phone bootloader logs I can see: "Mismatched partition size (recovery).
bablu048 said:
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
Click to expand...
Click to collapse
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
anujagraj said:
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
Click to expand...
Click to collapse
is the bootloader unlocked, did you input the code to unlock??just checking
Yes. Bootlader is unlocked with input code to unlock.
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
anujagraj said:
Yes. Bootlader is unlocked with input code to unlock.
Click to expand...
Click to collapse
or simply run
fastboot boot <enter twrp name>
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
anujagraj said:
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
Click to expand...
Click to collapse
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Lennyz1988 said:
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Click to expand...
Click to collapse
Clear /cache in the stock recovery didn't help. Also, I am trying to flash TWRP recovery 2.8.7.
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
bablu048 said:
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
Click to expand...
Click to collapse
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
anujagraj said:
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
Click to expand...
Click to collapse
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
bablu048 said:
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
Click to expand...
Click to collapse
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
anujagraj said:
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
Click to expand...
Click to collapse
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
bablu048 said:
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
Click to expand...
Click to collapse
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
anujagraj said:
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
Click to expand...
Click to collapse
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
bablu048 said:
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
Click to expand...
Click to collapse
Hi,
I have an Indian model and got the following error on flashing contents of XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1_cid7_subsidy-DEFAULT_CFC.xml using fastboot:
AP Fastboot Flash Mode (Secure)
failed to validate system image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
Please help!
My p9 lite is stuck on the huawei logo, its been a week now. it all started when I flashed a wrong update.app (i mistakenly flashed the rollback update.app while i was on b161)
now I cannot use the device anymore, i can only get to bootloader mode but cant flash anything
help
I had the exact same problem. I got out of that situation by rooting the phone, and re-flashing it.
However I already had the unlock code handy. If you don't have that then you are mostlikely f'ed.
My bootloader is unlocked yet I am unable to fastboot flash anything as i get errors.
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
elliotn said:
My bootloader is unlocked yet I am unable to fastboot flash anything as i get errors.
Click to expand...
Click to collapse
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
ugh
I'm stuck at "6. Hold Shift + right right mouse button "Open the command line here"" I have no idea what to do
You have to hold the "Shift" button on your keyboard (under Caps lock), and click on the right mouse button in the folder. Then in the menu, choose "Open the command line here"
help
BaXeL said:
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
Click to expand...
Click to collapse
I KEEP GETTING THIS ERROR: error: cannot load 'RECOVERY.img' HELP ME I AM DESPERATE
firmware
BaXeL said:
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
Click to expand...
Click to collapse
I neeeeed firmware for vns-l22
ughhead said:
I KEEP GETTING THIS ERROR: error: cannot load 'RECOVERY.img' HELP ME I AM DESPERATE
Click to expand...
Click to collapse
Did you unlock your bootloader first?
hey
BaXeL said:
Did you unlock your bootloader first?
Click to expand...
Click to collapse
I'm no longer getting the error I mentioned but now my phone wouldn't respond to the three button boot... it gets stuck on the logo again and doesn't do anything. I don't think I have the correct firmware. I need for VNS-L22C636B101 and I cant find it anywhere :crying: my phone is done for
You have to flash custom oeminfo.img to debrand your phone (it's fully legal). You'll find it on htcmania
thanks but..
BaXeL said:
You have to flash custom oeminfo.img to debrand your phone (it's fully legal). You'll find it on htcmania
Click to expand...
Click to collapse
if you don't mind can you explain this further and how it will help my situation?
ughhead said:
if you don't mind can you explain this further and how it will help my situation?
Click to expand...
Click to collapse
Yes, you can't flash C432B160 if your phone is branded by operator, the flashing will always end at error. Flashing oeminfo.img and Huawei firmware is fully legal and you don't loose warranty. And debranding is a good thing because (in future) you can download faster official Nougat.
okay
BaXeL said:
Yes, you can't flash C432B160 if your phone is branded by operator, the flashing will always end at error. Flashing oeminfo.img and Huawei firmware is fully legal and you don't loose warranty. And debranding is a good thing because (in future) you can download faster official Nougat.
Click to expand...
Click to collapse
Alright so let me explain my situation properly (I'm a big dumb-doofy-doo so i'm not even sure if my phone is branded) I bought my phone off amazon last year and 2 days ago I made the mistake of trying to update it to Nougat using http://www.droidviews.com/update-huawei-p9-lite-manually-official-android-7-0-nougat-emui-5-0/ and the files for build number VNS-L22C636B360 however my build number is VNS-L22C636B101 (Huawei P9 Lite). using the first file called "update.zip" I tried upgrading but it said software update failed. I turned on OEM and tried using "update_data_full_VNS-L22_hw_spcseas.zip" to update. it worked but I don't think this was the full update as it rebooted and I was greeted by Huawei eRecovery which had three options: "Download latest and recovery" "reboot" and "shut down" so naturally I chose the first option. It however ended with "Getting package info failed". I tried it over and over but it didn't change. so this is where I because frustrated, and stupid, and factory reset my phone. it didn't make a difference. same eRecovery prompt (but did the reset take off OEM??) I took out my SD Card and replaced the Update.app with another one (I cant remember which I was sad but I definitely complicated matters more by doing this) and I came upon the same problem the person who made this post: stuck on Huawei logo. if I power it off it will vibrate and boot back up on it's own to get stuck on the Huawei logo thing (it wouldn't even do the pretty flowy smoke thing) so because of this it does not respond to the 3-button force update anymore idk why the only mode I can get it into successfully is fastboot mode but even after following the step by step answer I cant get it to respond to the 3-button force update (I also dont have the exact firmware for my build number) I did skip the bootunlocker steps because I dont have a product id or IMEI to generate a code from the Huawei website. in fastboot mode however it says "Phone Unlocked" and "FRP Unlock"
I dont know what to do... I think I need the firmware but I cant find it specific to my build number VNS-L22C636B101
First of all you must have your bootloader unlock code...
You wrote that you get error on flashing by fastboot probably "Command not allowed" because, your bootloader is locked (Yes it's only display "unlocked" I also got on that )
If you don't have code you can't do anything, sorry. You must send your phone to huawei store on warranty.
You don't have phone box?
ya
BaXeL said:
First of all you must have your bootloader unlock code...
You wrote that you get error on flashing by fastboot probably "Command not allowed" because, your bootloader is locked (Yes it's only display "unlocked" I also got on that )
If you don't have code you can't do anything, sorry. You must send your phone to huawei store on warranty.
You don't have phone box?
Click to expand...
Click to collapse
ya I got that error.. and yes I have the box but I bought it off amazon so idk where to send it
ughhead said:
ya I got that error.. and yes I have the box but I bought it off amazon so idk where to send it
Click to expand...
Click to collapse
Ask your seller, hope you'll get a working phone
Mine was solved by booting to fastboot and did fastboot OEM unlock "unlock code" then fastboot flash recovery TWRP.img
Even though my bootloader was unlocked it worked
tq
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
BaXeL said:
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
Click to expand...
Click to collapse
.....................................
C:\WINDOWS\system32>fastboot oem unlock xxyourfastbootunlockcodexx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\WINDOWS\system32>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
error: cannot load 'recovery.img': No error
C:\WINDOWS\system32>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
error: cannot load 'boot.img': No error
C:\WINDOWS\system32>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
error: cannot load 'cust.img': No error
error: cannot load 'SYSTEM.img'
Sorry you guy for such a long thread, but my phone, Huawei P9 Lite VNS-L31 has exactly the problem in this thread and when i follow the lead on #4, every step are working well until the: "fastboot flash system system.img" on step 9, I got "error: cannot load 'SYSTEM.img' ". All other flash working well but i don't know why it returned an error on that step, could you guy please help me to get over it, thank you very much!
my log:
>fastboot oem unlock (my code)
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.002s
>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (33112 KB)...
OKAY [ 0.707s]
writing 'recovery'...
OKAY [ 0.775s]
finished. total time: 1.482s
>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.299s]
writing 'boot'...
OKAY [ 0.324s]
finished. total time: 0.623s
>fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (428162 KB)...
OKAY [ 9.108s]
writing 'cust'...
OKAY [ 5.520s]
finished. total time: 14.629s
>fastboot flash system SYSTEM.img
error: cannot load 'SYSTEM.img'
A brand new LE Pro 3, LEX 727.
EUI Version 5.8.021S
This is what I did:
Enable the Developer Option. Enable OEM Unlocking and USB Debugging
boot phone to fastboot mode, then connect to PC.
> fastboot oem unlock-go
> fastboot format userdata
> fastboot boot twrp-3.2.1-0-zl1.img
The phone enter TWRP, then in TWRP, I did
(1) backup,
(2) wipe (advanced wipe, select system, data, dalvik/ART cache, cache)
(3) Restore using backup created in step 1
After restore and reboot, the phone back to original.
Then I did:
1. Enable the Developer Option.
2. Enable OEM Unlocking and USB Debugging
3. ReBoot Phone to fastboot mode (Volume Down + Power button) and connect to PC.
4. fastboot oem unlock-go
Weird, this time it failed:
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
How can this happen? How to fix it???
Thanks!
rogerxda2018 said:
A brand new LE Pro 3, LEX 727.
EUI Version 5.8.021S
This is what I did:
Enable the Developer Option. Enable OEM Unlocking and USB Debugging
boot phone to fastboot mode, then connect to PC.
> fastboot oem unlock-go
> fastboot format userdata
> fastboot boot twrp-3.2.1-0-zl1.img
The phone enter TWRP, then in TWRP, I did
(1) backup,
(2) wipe (advanced wipe, select system, data, dalvik/ART cache, cache)
(3) Restore using backup created in step 1
After restore and reboot, the phone back to original.
Then I did:
1. Enable the Developer Option.
2. Enable OEM Unlocking and USB Debugging
3. ReBoot Phone to fastboot mode (Volume Down + Power button) and connect to PC.
4. fastboot oem unlock-go
Weird, this time it failed:
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
How can this happen? How to fix it???
Thanks!
Click to expand...
Click to collapse
Roger, I thought that I messaged you earlier but I see that it wasn't posted. I just answered your PM
So check your messages
Edit: It failed, because you restored the locked emmc_appsboot.mbn
after you prepare the phone for unlocking the bootloader, make sure that you remove any passwords, this way you will not have any storage encryption issues.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
tsongming said:
Roger, I thought that I messaged you earlier but I see that it wasn't posted. I just answered your PM
So check your messages
Click to expand...
Click to collapse
This is message 2.
The Pie Rom that you choose is a bad choice > It's not longer supported. We can talk on the phone if your timezone is close to mine . For me its 11:30pm Est.
I will be awake for about another hour. Otherwise, I can help you tomorrow. If you get this message tonight, message me ASAP
Next: Here is a link with the essential steps ( some of which you have found)
https://forum.xda-developers.com/showpost.php?p=75009966
Your Rom is an Alpha build. If You want Android 9.0 Pie > choose something recent such as Lineage 16.0, or AICP 14 These are great Roms and the developers currently have working Le Pro 3's.
If you still want or need help, I can help you on the phone or maybe use Team-Viewer.
Have these things ready
Your Rom of Choice
Recent Gapps ( Ex: open_gapps-arm64-9.0-nano) Here: https://opengapps.org/
TWRP : ( This One twrp-3.2.3-1-zl1 : https://dl.twrp.me/zl1 )
Magisk 17.3 ( https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Thank you!!! I sent you a PM, I will download the software you mentioned before we connect.
tsongming said:
Roger, I thought that I messaged you earlier but I see that it wasn't posted. I just answered your PM
So check your messages
Edit: It failed, because you restored the locked emmc_appsboot.mbn
after you prepare the phone for unlocking the bootloader, make sure that you remove any passwords, this way you will not have any storage encryption issues.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
This is message 2.
The Pie Rom that you choose is a bad choice > It's not longer supported. We can talk on the phone if your timezone is close to mine . For me its 11:30pm Est.
I will be awake for about another hour. Otherwise, I can help you tomorrow. If you get this message tonight, message me ASAP
Next: Here is a link with the essential steps ( some of which you have found)
https://forum.xda-developers.com/showpost.php?p=75009966
Your Rom is an Alpha build. If You want Android 9.0 Pie > choose something recent such as Lineage 16.0, or AICP 14 These are great Roms and the developers currently have working Le Pro 3's.
If you still want or need help, I can help you on the phone or maybe use Team-Viewer.
Have these things ready
Your Rom of Choice
Recent Gapps ( Ex: open_gapps-arm64-9.0-nano) Here: https://opengapps.org/
TWRP : ( This One twrp-3.2.3-1-zl1 : https://dl.twrp.me/zl1 )
Magisk 17.3 ( https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse