Related
Hi,
I new to this so i`m a newbie for now.
Phone info:
System Version
81.5.39001.XT890.Retail.en.GB
Android Version
4.0.4
Build Number
8.7.1l-110_IFW-39
The problem.
Today a pop up appear and said I have a new update for my phone.
I downloaded the app and pressed the install button.
The phone rebooted in CWM and start to install.
Something about signature missing cam up and asked me to install untrusted app.
I selected yes and an error came again and installation stopped.
Installing update...
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error in /cache/Blur_Version.81.5.39001.XT890.Retail.en.GB.zip
(Status 7)
Installation aborded
My phone has bootloader unlocked and rooted (RAZRiRoot2)
I checked for that file but it is present in system folder.. I think something is wrong with it or I do something wrong ?
Please advice.
Regards
You have to flash the Stock Recovery back, to install the OTA. With CWM it won't work.
Or just flash the GB JB Fastboot > clean start into JB :thumbup:
Gesendet von meinem XT910 mit Tapatalk 2
Hi,
Well the RSD Lite wont install on my pc.. win 7 64bit.
and can you point me somewhere to read about how to "Or just flash the GB JB Fastboot" ?
Regards
Here's the How To
http://forum.xda-developers.com/showthread.php?p=33712189
Make sure you're using RSD 6.1.4 (Google it)
And here's your Fastboot File (Retail UK)
http://forum.xda-developers.com/showthread.php?p=40417328
If RSD won't install, you got issues on your PC. I used it with Win7 & 8 (64bit) without Problems.
Gesendet von meinem XT910 mit Tapatalk 2
Hi,
This is the error I receive when I try to install RSD
Regards
All done
Thanks for help.
Regards
Hello all,
I want to get back to a "normal system" in order to upgrade to B830. What I did so far:
- When B830 wasn´t out, I changed vendor on B621 to "custc02_vodafone_za" in order to flash B817 --> went fine
- Planning to update to B830, tried to revert trough B800 transition package to B6xx, but got an error
- Few days later flashed B830 boot.img, then tried to flash B830 through dload (someone posted that that works – but not for me)
- Flashed MiUi 5.10.17, but android.system force closed
- Tried MyRom 3.3, but errors both in cwm and twrp
- Tried Se7en Rom 3.8 (based on B602), flashing went fine. But downgrade as in the description doesn´t work.
- Flashing of B609 through dload when on Se7en-Rom/ MiUi also fails
- Flashing flashable B609.zip worked finally
So, I am now on B609, but unable to flash B621/MyRom or whatever. The Update fails immediately.
Does anybody have an idea what I could do? I would really appreciate any help!
Best wishes!
try to replace the twrp/cwm recovery with stock b609 recovery..
then force upgrade b609 again..
after that maybe the b621 update may be flashed through local or force update..
finally the b623 should appear and then the b830 (if not then flash them through local update - especially the b623)..
hope this helps
Gesendet von meinem HUAWEI P7-L10 B830
Thanks for your reply! Unfortunately I already tried that without success, but forgot to mention. The same with 3.0to2.3-downgrade-package/B830/B817..
I assume that by changing the cust following this (http://forum.xda-developers.com/ascend-p7/general/b817-vodacom-users-cust-error-changing-t3211386) guide, something went wrong. Before I did this, all was fine.
@majcomtech sorry for asking so directly, but could you imagine what my problem is? Or what else I could try to revert?
I thought a while about what I´ve done so far and came to the conclusion that downgrading using B800 transition pack failed due to my root access. Flasing Miui (based on Android 4.4) was a mistake and made things complicated.
So I thought about flashing system.img/cust.img/userdata.img/boot.img/recovery.img of B817. Is that a bad idea?
I just don´t want to make things worse and ask first.
Thank you!
I finally made it by flashing system.img/cust.img/userdata.img/boot.img/recovery.img of B817, flashing boot.img(of B830) then updating through dload to B830. B830 had some bugs (no motion control etc.) -->B800-->B621-->cust change back to eu-->reflash B621-->B623-->B830. Maybe this will help anyone, if in a similar situation..
l3Nni said:
I thought a while about what I´ve done so far and came to the conclusion that downgrading using B800 transition pack failed due to my root access. Flasing Miui (based on Android 4.4) was a mistake and made things complicated.
So I thought about flashing system.img/cust.img/userdata.img/boot.img/recovery.img of B817. Is that a bad idea?
I just don´t want to make things worse and ask first.
Thank you!
Click to expand...
Click to collapse
1. Reboot to bootloader
2. Flash CWM 3.0
3. Reboot to recovery mode
3.1 Install from SDCARD1
a. Find My-RoMv3.3.zip
3.2 Back
3.3 Wipe data/factory reset.
3.4 Advance
3.5 Reboot to Bootloader
4. Flash stock recovery for 3.0
5. Flash B621
6. Flash vendor version you want
Now all are normal.
As i wrote above, I was able to solve the problem.. I already tested the way you described , but it didn´t work since I got alway errors in CWM/TWRP.
But now all is fine and thanks for your reply anyway!
l3Nni said:
I finally made it by flashing system.img/cust.img/userdata.img/boot.img/recovery.img of B817, flashing boot.img(of B830) then updating through dload to B830. B830 had some bugs (no motion control etc.) -->B800-->B621-->cust change back to eu-->reflash B621-->B623-->B830. Maybe this help anyone, if in a similar situation..
Click to expand...
Click to collapse
Hi how did you change back to European cust in B621? I'm unable to have the right cust. Thanks
Sent from my HUAWEI P7-L10 using Tapatalk
You can find the cust files here (http://forum.xda-developers.com/showthread.php?t=3211386) in Post #1. Flash them through dload on B621 and you should get back.
Im having something similar.
I have installed the s7ver rom, based on 602.
I changed the recovery to the base one.
Now i tried flashing the update.app from the 609.
tried by force update (Vol+ + Vol- + Power) and via updade from file.
both, give a "Software Update failed" just at start.
It boots normally
Any idea????
Thanks
Look in the Se7en-Rom-3.8 Thread, there is the process oft getting back described. It's because the Rom is based on B602, a beta which is not meant for L10 devices..
l3Nni said:
Look in the Se7en-Rom-3.8 Thread, there is the process oft getting back described. It's because the Rom is based on B602, a beta which is not meant for L10 devices..
Click to expand...
Click to collapse
Found it .... ><
Thanks
http://forum.xda-developers.com/showpost.php?p=56860553&postcount=2
Hi!
I have got a second hand P9 from UK, know using in Germany. For any reasons the last build ID was International (EVA-C900B136) and I did not get any updates.
After some discussions with Huawei support I eventually unlocked the device and flashed twrp successfully.
Then I tried to install a current version for Europe (C432).
I needed to try several ways but in the end my CUST was C432, unfortunately I didn't notice the buildnumber.
However, something went wrong because now I'm always asked for decryption password, which I never had. After typing in some random keys I get the message that the password is correct but the file system is damaged a reset has to be done. After rebooting the same again, and again etc.
Trying to solve this by recovery mode is no help, system reboot with twrp also end again in twrp.
Maybe I flashed somehow wrong or too much and the file system is damaged.
I hope you have a clue and you could give me a suggestion how to solve!!!
Many thanks in advance!!
tib465
p.s. may it is important that in twrp I get the message "failed to mount '/data' (invalid argument)'
if last was c432, trhy this Pres Here
No success
Arnys said:
if last was c432, trhy this Pres Here
Click to expand...
Click to collapse
no install possible. TWRP tells me "invalid zip file format"
tib465 said:
no install possible. TWRP tells me "invalid zip file format"
Click to expand...
Click to collapse
You need to install it via dload
tib465 said:
no install possible. TWRP tells me "invalid zip file format"
Click to expand...
Click to collapse
jeah. use it with dload method. you need memory card, put thease files unziped in memory card dload folder, card in phone, then restart phone presing volume +- keys, till you are in huawei software update screan , circle with % in it. Read on page i give you, how properly instal that package, read things before try to use things!
I did so with dload. startet well, in the end after 99% I got a failure message.
After reboot again need to input decryption password.
After entering any key, button for reset, which then worked ok.
Now finally build version B136 installed und phone ist starting.
Not how I expected but seems ok.
Thank you for advice!
Next task is upgrade to a current android 7 version...
have you tried boot into recovery and do a factory reset of the phone?
if not working, then do factory reset + wipe cache.
please read through this post,
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
I was having the same problem"ask for encryption pw" and I solved my problem by a factory reset.
The best way to solve and get the phone totally on fit is to downgrade to MM then b136 full and go ahead with the updates but ensure your cust is 432
Enviado desde mi EVA-L09 mediante Tapatalk
jcalderonv74 said:
The best way to solve and get the phone totally on fit is to downgrade to MM then b136 full and go ahead with the updates but ensure your cust is 432
Click to expand...
Click to collapse
my phone once was cust 900. I somehow managed to get to 432. but when installing via in TWRP there are still messages like "Target: Huawei/EVA-L19/HWEVA:6.0/HUAWEIEVA-L19/C900B182"
do you know an easy and secure way to change cust in full and proper way?
P.s. I just saw the link above, I will try and tell you...
tib465 said:
my phone once was cust 900. I somehow managed to get to 432. but when installing via in TWRP there are still messages like "Target: Huawei/EVA-L19/HWEVA:6.0/HUAWEIEVA-L19/C900B182"
do you know an easy and secure way to change cust in full and proper way?
P.s. I just saw the link above, I will try and tell you...
Click to expand...
Click to collapse
I own L09c432 Sorry i dont want to tell you Wrong steps for your model
Enviado desde mi EVA-L09 mediante Tapatalk
Hi guys,
got a little problem on my VTR-L09C432.
I got Oreo running like explained right here: http://www.stechguide.com/install-android-8-0-oreo-on-huawei-p10/#comment-12332
After that, Oreo bootet fine. But to get a clean install, I did a factory reset.
After that my Version is 8.0.0.046(01BN) and not 8.0.0.311.
There are a few little bugs so I decided to flash once again. I tried to flash TWRP in fastboot mode. -> No success
I tried to flash with the following command: fastboot flash recovery_ramdisk twrp***.img -> SUCCESS!
BUT no i get an Error message when trying to boot into recovery:
Attention! Please update system!
"- picture of the little green guy-"
Error!
Func No 11 (recovery image)
Error No 2 (load failed)
gettin into eRecovery is no Problem. System boots fine and runs better than Nougat, better battery life, with a fews little bugs.
How do I get a TWRP running?
In case if no chance, how do I get system oreo Recovery flashed an running?
Will it be possible to get official updates, when I will get back to original recovery?
One big bug is that my screen won't turn on when receiving notifications... even not with the help of a third party app Any idea how to fix it anyway?
If TWRP will be flashed successfully, is there a Chance to flash these 3 Update-Files through twrp?
Thx a lot!
You have flashed a C900 and you have a C432. So your device didnt find all needed files.
Try to flash this twrp (its in a MEGA Folder) and report .
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729
Thx for your reply. You mean there are files, which I need to flash again for my c432 device?
I flashed the twrp from your link.
Flashing was fine but no chance to get into twrp. Still the same error.
Can I flash the RAMDISK or Recovery Ramdisk from your mega-source?
UPDATE: I flashed STR_Stock_Recovery from your Mega-Folder and got success. Now I can boot into stock recovery and into Erecovery. But still no TWRP is working...
UPDATE2: I got a working TWRP by flashing this one: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
Now my question...can i flash the Supersu from your mega-folder onto my P10? Or will it be bricked?
Gesendet von meinem VTR-L09 mit Tapatalk
SOLVED!
Hi Guys,
Problem is solved! For those who got the same problem, follow these steps:
You need this link for all following steps(thx to blackball!): https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729
If you haven't got fastboot error, start at point 2.!
1. To get Fastboot Error removed, flash Stock Recovery from link above (in fastboot mode)
2. boot in fastboot mode (shutdown, restart by pressing power&vol- with usb cable attached)
3. Flash TWRP Recovery from link above fastboot flash recovery_ramdisk TWRP***.img
3.1. if this doesn't work, flash TWRP attached below this link
4. boot in to twrp recovery (shutdown phone, restart by pressing power & vol+)
5. Flash supersu.zip from link above
6. reboot
7. install root browser or similar from playstore
8. get root privileges to root browser
9. reboot
10. navigate to /cust/hw/
11. rename "normal" folder to "eu" (without the quotes)
12. navigate to /version/special_cust/STF-L09/hw
13. rename "normal" folder to "eu" (without the quotes)
14. reboot
15. that's it!
Thx to blackball for the help!
TWRP link:
https://drive.google.com/drive/folders/1twgKVop02omG9vuVyc8ELwMxtB6nCko1
Thx for this guide, i will try it later!!! But whats the main change now???
When i see it clearly, then you still have the 8.0.0.046 Version on your device... But you have a working TWRP.... And you will receive official updates?
I am wondering, becaus i did the same with my P10 ( i am on 8.0.0.046 too) and i am not sure, if this is an official version with official updates... If it isnt, i will try to go back to Nougat...
stefan.irmen said:
Thx for this guide, i will try it later!!! But whats the main change now???
When i see it clearly, then you still have the 8.0.0.046 Version on your device... But you have a working TWRP.... And you will receive official updates?
I am wondering, becaus i did the same with my P10 ( i am on 8.0.0.046 too) and i am not sure, if this is an official version with official updates... If it isnt, i will try to go back to Nougat...
Click to expand...
Click to collapse
After these steps, you have 8.0.0.311 version, themes working, screen on notification working and so on.
Gesendet von meinem VTR-L09 mit Tapatalk
Hey cologne83!
First of all, thanks for this helpful guide, now i see finally 8.0.0.311 on my phone
But you dont actually need the root browser, because you can change those folders in twrp too!
Secondly i have a question:
cologne83 said:
5. Flash supersu.zip from link above
Click to expand...
Click to collapse
how did you do this? everytime i boot in twrp it shows me only gibberish until i go one directory up.
Root on Oreo would be super nice
Put zip file on external SD card. Your internal is encrypted.
Gesendet von meinem VTR-L09 mit Tapatalk
ok, i hoped it is on Android O not encrypted anymore.
But anyway thank you works likes new now!
just a little bit off topic question: is there any new version available? when i check systemupdates it says that that my Version (8.0.0.311) is the latest available. just wanna be sure
deleted
8.0.0.046(04vt)
Does someone has a solution for the 8.0.0.046(04VT) version? If I navigate to /cust/hw/ I find now two folders: eu and normal. In /version/special_cust/VTR-L09/hw I find the eu. folder. So what to change here? Thx
anabolic_guy said:
I have upgraded from Nougat to Oreo following the guide written at the beginning of this post.
Oreo now is installed, phone is not rooted and when I go to fastboot mode to flash Oreo TWRP, this happens:
C:\adb>fastboot flash recovery_ramdisk twrp_oreo.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (20336 KB)...
OKAY [ 0.474s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.498s
Bootloader and frp are both opened and RED in fastbooot mode.
The build number is: System 8.0.0.046(01UV)
EMUI version: 8.0.0
Android version: 8.00
Some ideas ?
Thanks for th attention.
Click to expand...
Click to collapse
This guide is my last chance to save phone. Afther update to b360 my phone brick, no recovery, no eRecovery, no TWRP.... I can flash all but nothing change
urbanboymne said:
This guide is my last chance to save phone. Afther update to b360 my phone brick, no recovery, no eRecovery, no TWRP.... I can flash all but nothing change
Click to expand...
Click to collapse
Which guide? If you are able flash you get access to phone so it should work in some way
kwaichang said:
Which guide? If you are able flash you get access to phone so it should work in some way
Click to expand...
Click to collapse
Yes i'm able some recovery images or twrp, also all system.img i can flash withouth problem, cust.img... But nothing change. Somethimes stay in boot black screen, somethimes reboot to ERROR MODE, and also i'm able to get into fastboot mode, unlock/relock bootloader but always says me no recovery image - load fail in error mode
urbanboymne said:
Yes i'm able some recovery images or twrp, also all system.img i can flash withouth problem, cust.img... But nothing change. Somethimes stay in boot black screen, somethimes reboot to ERROR MODE, and also i'm able to get into fastboot mode, unlock/relock bootloader but always says me no recovery image - load fail in error mode
Click to expand...
Click to collapse
same for me after hwota and rebrand fail. And I don't find the STR_stock just 2 STR_recovery but even if android say flash sucessfully i can't acces to recovery nor ercovery.
P.S: I was using OREO rom when I try to rebrand
It can works on Huawei P10 EMUI 8.0.0? How to root that model? I stuck on how to install twrp,. Please help me.....
my system is saying im on 8.0.0.046(0BZC and i can't even get the erecovery or twrp to work at all. nobody around here wants to help or pin point me in any direction either
I have exactly the same problem, but the locations mentioned here don't even exist on my phone, so I can't rename them
10. navigate to /cust/hw/
11. rename "normal" folder to "eu" (without the quotes)
12. navigate to /version/special_cust/STF-L09/hw
cust does not contain a "hw" folder, just a "lost+found" one.
version/special_cust/VTR-L09/hw does exist, but when I try to rename "hw" I get "operation failed".
Very annoying!
I stuck also inside the 8.0.0.046 !
And i dind´t found any solution for this.
This is what i allready tried:
- official eRecovery : download from huawei. But didn´t worked after download. Stucked at 0%
- TWRP oreoupdate ( https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286 )
- TWRP HuRuUpdate ( https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279/ )
- TWRP HWOTA8 ( https://www.******.com/huawei-hwota-tool-for-huawei-devices/ )
Just to answer my pre-writers:
You need to "mount" the folders "cust" and "version" to see something inside. Only then you are able to change things. In my case this changes
didn´t affect something positive to my version number.
Not sure what i did wrong. Maybe my false was
- Wipe all with TWRP instead with eRecovery
or because
- i flash my (C02) witth (C432) version
So i tried 4x different ways to solve my issue (mostly with TWRP). With no success. If somebody read this, it would be great to get some tips or a complete solution. Would appretiate it.
Okay.
Somehow i found a solution by myself. I have to guess, that the issue is / was of a wrong build nr. In my case i got a previous vers. VTR-L09 8.0.0.382(C02)-FULL. So i updatet to a different build (C432). After
this my Themes disappeared, no file manager and the vers. no. was 8.0.0.046 , somehow. So i tried to go back to VTR-L09 8.0.0.382(C02)-FULL which i downloaded before. Tried both methods: dload, TWRP. No
success. In the end i downloaded VTR-L09 8.0.0.389(C02)-FULL and this worked with the TWRP update method: oreoupdate (check my previous post). After the Update with TWRP before it boots into the
system i was triggering eRecovery to do a "wipe chache / factory reset". Finaly, after all of this, i got a working device as it should ! I hope it can help maybe some people. If everything doesn´t work, just try a different update build number.
Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again
Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?
I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?
NEM-L51C432 or NEM-L51C10 ?
NEM-L51C432 and I'm sure of that ^^
Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there
I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.
I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.
I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...
Dload the next firmware now and see if it works. Then set the phone
I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.