Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash cust C:\Users\prajw\Desktop\CUST.img
target reported max download size of 532676608 bytes
sending 'cust' (219374 KB)...
OKAY [ 5.394s]
writing 'cust'...
FAILED (remote: size too large)
finished. total time: 5.425s
ploosond said:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash cust C:\Users\prajw\Desktop\CUST.img
target reported max download size of 532676608 bytes
sending 'cust' (219374 KB)...
OKAY [ 5.394s]
writing 'cust'...
FAILED (remote: size too large)
finished. total time: 5.425s
Click to expand...
Click to collapse
Well, it's telling you right there what's the problem: the size of CUST.img is too big for your phone's partition (cust).
A little background into what you are doing, what happened, etc might get more help.
#Henkate said:
Well, it's telling you right there what's the problem: the size of CUST.img is too big for your phone's partition (cust).
Click to expand...
Click to collapse
I got that after few googling and came to conclusion not to mess up with partition. I am stuck on erecovery due to wrong recovery and ROM. Please, would you mind passing me stock recovery and cust for CAN-L11 4.1 marshmallow?
I don't have those, but they will be in the update.app. Once you get the update.app you can use Huawei extractor tool to extract recovery.img. Once you have stock recovery you can follow guides about updating huawei devices. It involves entering stock recovery with the update.app in a folder called dload or something. Haven't touched that in a while. I think it is the same for most Huawei devices.
wangdaning said:
I don't have those, but they will be in the update.app. Once you get the update.app you can use Huawei extractor tool to extract recovery.img. Once you have stock recovery you can follow guides about updating huawei devices. It involves entering stock recovery with the update.app in a folder called dload or something. Haven't touched that in a while. I think it is the same for most Huawei devices.
Click to expand...
Click to collapse
Hey, do you have any idea that how can I unlock frp without accessing developer mode? My frp is lock and bootloader too so why I cannot flash custom recovery to restore twrp backups.
did you try to install the mm img after upgrading to nougat? Because this is what happens when you try that. Nougat has different partition sizes (because the new way of updating that google implemented) and you will not be able to rollback to mm that way (you need mm partition table, which we don't have).
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
ploosond said:
Hey, do you have any idea that how can I unlock frp without accessing developer mode? My frp is lock and bootloader too so why I cannot flash custom recovery to restore twrp backups.
Click to expand...
Click to collapse
dc-unlocker can do the trick, but you have to pay for it.
Vinnom said:
did you try to install the mm img after upgrading to nougat? Because this is what happens when you try that. Nougat has different partition sizes (because the new way of updating that google implemented) and you will not be able to rollback to mm that way (you need mm partition table, which we don't have).
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
dc-unlocker can do the trick, but you have to pay for it.
Click to expand...
Click to collapse
Yeah, I did like that and paid 15 euro.
Vinnom said:
did you try to install the mm img after upgrading to nougat? Because this is what happens when you try that. Nougat has different partition sizes (because the new way of updating that google implemented) and you will not be able to rollback to mm that way (you need mm partition table, which we don't have).
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
dc-unlocker can do the trick, but you have to pay for it.
Click to expand...
Click to collapse
Now I did unlock frp and bootloader and flashed boot.img, cust.img, system.img and recovery.img and reboot device. Now keyword is missing on my device. Do I need to flash other cust.img ?
ploosond said:
Now I did unlock frp and bootloader and flashed boot.img, cust.img, system.img and recovery.img and reboot device. Now keyword is missing on my device. Do I need to flash other cust.img ?
Click to expand...
Click to collapse
did you mean keyboard or keyword is an app you had and now you don't have anymore? For the first case, I think I had the same problem and I just downloaded and installed gboard (my fav) via adb. If you're looking for an app (service) named keyword, I don't know how to help you =/
Related
So, you've unlocked your bootloader and are enjoying some rooted goodness on your phone. You then realise you've got an issue with the phone and forgot to make a backup of your stock ROM! Not to fear, this guide is for you! This will reset the phone back to it's out-the-box state, locked bootloader and all, running the latest ZNH2KAS3P0 build so you can return it for RMA/sell it. This also works to go back to CM13.1.2 from Oxygen OS.
It's recommended that you have adb/fastboot in your System Path. This makes it easier to run commands as you don't always have to 'in' your adb/fastboot folder to run the commands. This guide should help you with this but if you don't want to do this, please copy/extract any files into your adb/fastboot folder before continuing...
1. Download the factory image
Cyanogen released the factory image for the OPO but didn't include any batch files to automate the process. I've repackaged the images into two seperate ZIPs:
ZNH2KAS3P0 16GB: DOWNLOAD
md5: be471f6bfc707f86a0af1eb175ec9aad
ZNH2KAS3P0 64GB: DOWNLOAD
md5: c371bc0cb4ef67999d21f5275c5a587b
*** These ZIPs are not flashable so cannot be flashed via TWRP ***
2. Extract the factory image
Using your favourite file extraction program to extract the package to your Desktop (I use 7-ZIP). *** Remember, if you don't have adb/fastboot in your Path, extract the image into your adb/fastboot folder ***
3. Flash the factory image
Once you've unlocked the bootloader, and rebooted the phone, turn the phone off and back on into fastboot mode and reconnect it to the PC. You can now run the flash-all.bat (Windows) or flash-all.sh (Linux) file. These automate the flashing process. Once complete, the phone will reboot.
*** Some users have had issues using the script in Linux so in these cases extract the ZIP file and flash each IMG individually ***
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img (the filename is the same in both ZIPs so make sure you're using the right one for your device)
fastboot reboot
4. Reset the tamper flag/lock the bootloader
There is a flag/bit on the phone that is triggered when you unlock the bootloader and even relocking it won't change this flag back to standard. Luckily, @Mnt-XDA has a script that you can flash which resets these flags so OP/anyone else is none the wiser! To do this, read and follow THIS thread
5. Reboot the phone
Says it all really - you're done!
EddyOS said:
3. Unlock the bootloader on your OPO
Click to expand...
Click to collapse
And why do you need to unlock the bootloader to flash the factory image ????
RalphLauren said:
And why do you need to unlock the bootloader to flash the factory image ????
Click to expand...
Click to collapse
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
EddyOS said:
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
Click to expand...
Click to collapse
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
RalphLauren said:
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
Click to expand...
Click to collapse
I know what you mean, but it's the same with Nexus devices - you cannot flash the image unless the bootloader is unlocked
indesisiv said:
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
Click to expand...
Click to collapse
Yeah was looking to add that in at some point, this is still a work in progress as it were...I'll add it in when I get a chance
EDIT: Added
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
lemonspeakers said:
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
Click to expand...
Click to collapse
To be fair, of someone doesn't know how to do that they really shouldn't be here in the first place!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
This should be a sticky!
banjotrold said:
This should be a sticky!
Click to expand...
Click to collapse
I agree! This definitely should be a sticky.
Sent from my One using XDA Premium 4 mobile app
Which one of these files would be the kernel? I am having wifi issues and am wondering if I would be able to reflash and fix it.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock (if you wish to relock the bootloader. If not, ignore this part)
fastboot reboot
boot.img
EddyOS said:
boot.img
Click to expand...
Click to collapse
Thank you. Any reason why I can't just fast boot the boot.img file only (ala carte)? I am on CM11s rooted with TWRP.
I fastboot flashed the boot.img file sucessfully. It did not fix my wifi problem. So, I tried fastboot flashing the NON-HLOS.bin file. It appears to have an error code. Here is the result.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kevin work>cd desktop/android-sdk-windows/platform-tools
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot devices
9f66970a fastboot
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot flash mo
dem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56241 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.306s
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot reboot
< waiting for device >
^C
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>
Any idea as to why it failed?
reboot time
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Xeon_IV said:
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Click to expand...
Click to collapse
As you can see from my command prompt script mine did not want to reboot. I ended up unplugging the phone and rebooting.
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
Click to expand...
Click to collapse
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Click to expand...
Click to collapse
Is your phone the Chinese OPO or the CM OPO?
CM OPO coming from paranois android
Hi, I need help, I have the Chinesse version of mate 8( NTX AL10), and I installed the 577 version in HiCare, but Im having too many problems and I want to rollback to Android 6.
Someone can show me the way? I tried to install twrp recovery (I have the bootloader unlocked), and I couldnt format data because I couldnt access to internal storage in the recovery.
Thanks
janrck said:
Hi, I need help, I have the Chinesse version of mate 8( NTX AL10), and I installed the 577 version in HiCare, but Im having too many problems and I want to rollback to Android 6.
Someone can show me the way? I tried to install twrp recovery (I have the bootloader unlocked), and I couldnt format data because I couldnt access to internal storage in the recovery.
Thanks
Click to expand...
Click to collapse
try to use dload method by copying UPDATE.APP to dload folder on the root, or extract UPDATE.APP and flash recovery.img, boot.img, system.img, cust.img using fastboot command :
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash system system.img
I tried the dload method and I got an instalation error, I will try yo extract the update.app files. Thanks!
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
azyounes said:
try to use dload method by copying UPDATE.APP to dload folder on the root, or extract UPDATE.APP and flash recovery.img, boot.img, system.img, cust.img using fastboot command :
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
I tried that, but I was able to flash boot, cust and recovery, but with the system.img crash and show me this error:
target reported max download size of 471859200 bytes
sending sparse 'system' (458765 KB)...
OKAY [ 10.915s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.970s
Im desperated...
janrck said:
I tried that, but I was able to flash boot, cust and recovery, but with the system.img crash and show me this error:
target reported max download size of 471859200 bytes
sending sparse 'system' (458765 KB)...
OKAY [ 10.915s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.970s
Im desperated...
Click to expand...
Click to collapse
maybe u have to do a factory reset first. if u cant do it with twrp try to enter the stock recovery and do it before flashing. hope that it works this time.
about me, i was on nougat beta, twrp gives me too much errors when i want to format data and system, i installed stock recovery and did a factory reset and i used dload folder, now im on EMUI 4.0 (B180)
dont worry every problem have a solution. good luck
Posted from Mate 8.
Or with Rollback UPDATE.APP.
My Mate 8 is L29C636,i convert to AL 10 with B577 and go Back to L29 C636B211 without any Problem.
I can upload the UPDATE.APP later 92mb.
Use HiSuite via PC and roll back by updating to earlier versions! It's simple
azyounes said:
maybe u have to do a factory reset first. if u cant do it with twrp try to enter the stock recovery and do it before flashing. hope that it works this time.
about me, i was on nougat beta, twrp gives me too much errors when i want to format data and system, i installed stock recovery and did a factory reset and i used dload folder, now im on EMUI 4.0 (B180)
dont worry every problem have a solution. good luck
Posted from Mate 8.
Click to expand...
Click to collapse
I tried everything, I think maybe the problem is the Recovery, you knoq a twrp recovery that works fine with nougat?
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
bluheart said:
Use HiSuite via PC and roll back by updating to earlier versions! It's simple
Click to expand...
Click to collapse
I tried, but I couldnt do it, the Hisuitr shows me an Instalation error...
letschky said:
Or with Rollback UPDATE.APP.
My Mate 8 is L29C636,i convert to AL 10 with B577 and go Back to L29 C636B211 without any Problem.
I can upload the UPDATE.APP later 92mb.
Click to expand...
Click to collapse
And how did yo do? Can you explain please?
Copy the Rollback UPDATE.APP in dload Folder in Micro SD.
Change oem.info and custom.bin from AL10 to L29.
Boot in Bootloader and Flash Stock Recovery and reboot
This make Automatic a Factory Reset and Lock my Bootloader
Go to dailer and use this code *#*#2846579#*#* and go to 4.Software Upgrade.
After this Procedur copy my Original Firmware for c636B211 in dload Folder and make the same Procedur with *#*#2846579#*#*
After flashing the Firmware i am on L29C636B211
But you have a AL10,i think you flash the Rollback Update App
This Roll Back flash to Emui 4.0 and not to 4.1
After flash the Rollback,Download a Firmware for your AL10 with Emui 4.0 and flash this Update App via dload *#*#2846579#*#* here
This Methode can use with locked bootloader
Download Rollback
I think this works
If not take what was described above
Quote:
Originally Posted by azyounes
try to use dload method by copying UPDATE.APP to dload folder on the root, or extract UPDATE.APP and flash recovery.img, boot.img, system.img, cust.img using fastboot command :
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash system system.img
but your Bootloader must be unlocked!
and sorry for my bad english!
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
bluheart said:
Use HiSuite via PC and roll back by updating to earlier versions! It's simple
Click to expand...
Click to collapse
Yes this Method works only on AL10
Thank you all! Finally I decided to try again with Hisuite and I dont know why but finally works and Im with 386 version.
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
I erased everything in an attempt to unbrick it but that was a mistake. What I have tried and results:
-twrp recovery tried to install the latest stock firmware but got error with mounting system.
-fastboot flash update update.zip didn't solve it
-fastboot seperatly flashing each image, extracted by the update extractor tool. Result:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (451240 KB)...
OKAY [ 23.882s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 23.958s-fastboot -w to reformat and try again. Result:
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.012sOEM is unlocked, I have tried updating from the SD and using the three buttons but I get the wrong format error. Downloaded the MM version as well but I get the incompatible error. Can't download from the erecovery or Hi-Suite. Help please
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.
Badwolf9 said:
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.
Click to expand...
Click to collapse
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.
I believe ur in nougat beta... Just flash oem info and flash again the nougat from there you can start again and downgrade peacefully
your bootloader is locked
Sh0m1 said:
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.
Click to expand...
Click to collapse
Thank you! I followed the instructions here with a slight variation. Because trying to install the update.zip file always gave me errors I extracted the update.APP with the update extractor tool and flashed cache,system,boot with fastboot. Then I opened the custom recovery, installed the other zip file and continued as instructed.
mjz2cool said:
your bootloader is locked
Click to expand...
Click to collapse
No it wasn't. This was my first thought as well.
Badwolf9 said:
No it wasn't. This was my first thought as well.
Click to expand...
Click to collapse
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked
mjz2cool said:
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked
Click to expand...
Click to collapse
fastboot oem device-info
Also if it was locked I wouldn't be able to flash anything.
d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
where can I find the oeminfo file?
islandman75 said:
where can I find the oeminfo file?
Click to expand...
Click to collapse
This is the L21 - SingleSIM:
https://www.dropbox.com/s/97uad8vc3pwppnq/oeminfoORIGINAL.img?dl=0
And the L21 - DualSIM:
https://www.dropbox.com/s/fq99atzszg2sq1y/oeminfoDUAL.img?dl=0
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'
This is my first time posting on XDA, so sorry if the formatting is bad.
I've tried to root my P9 lite installing TWRP and Magisk, everything went fine, until the last reboot that caused a bootloop.
Trying to fix this I mistakenly wiped the System partition (instead of Data), reading online people adviced to flash the update.zip, when i tried it I had "unable to mount /vendor" and "unable to mount /product".
I tried the update.app method and the eRecovery tool, but still nothing.
I read that the problem was probably caused by en error in boot.img or recovery.img, so i extracted those files from the firmware and flashed them using TWRP. By doing so i deleted TWRP itself leaving me unable to flash system.img.
I tried to flash it using fastboot, but every time i try to write a command regarding flashing i get a FAILED (remote: command not allowed).
Now i have a bricked phone, i can access fastboot but it doesnt seem to be working. I cant access adb since i can't access the recovery (at least i dont know how to ).
Any advices?
Do you have bootloader unlock code?
Dino_S said:
Do you have bootloader unlock code?
Click to expand...
Click to collapse
Yes I do.
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Dino_S said:
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Click to expand...
Click to collapse
I can't, whenever I try using a fastboot command I get "FAILED (remote: command not allowed)
How much is internal data memory in twrp
Dino_S said:
How much is internal data memory in twrp
Click to expand...
Click to collapse
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
TinkyWinkyJr said:
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
Click to expand...
Click to collapse
It is showing in fastboot mode unlocked both
Dino_S said:
It is showing in fastboot mode unlocked both
Click to expand...
Click to collapse
Bootloader unlocked and FPR locked (or is it FRP?)
I have same prob yesterday,and showing me same thing,but i flashed twrp again and format data and system to ext4,and from fastboot flash system and boot img and it booted,it is confusing to undestand yours problem
---------- Post added at 01:15 AM ---------- Previous post was at 01:14 AM ----------
TinkyWinkyJr said:
Bootloader unlocked and FPR locked (or is it FRP?)
Click to expand...
Click to collapse
Mine showing FRP unlocked
hey guys
i have the same problem, had rr marshmallow on my p9 lite and tried to flash the new recovery for nougat by old droid. since then i cant enter nowhere without fastboot. phone unlocked and frp unlocked. does anybody have another idea. flashing stock recovery did not work, flashing twrp did also not work. need more ideas, erecovery and dload method do not work, i have acces to fastboot
Try to flash the correct oem.info.I've had the same problem with my P9(EVA-L09).