Related
**UPDATE RESOLVED**
For anyone who searches and has same problems.
I needed an sdcard to get the files onto the phone.
To recap - it was stuck in boot, TWRP would load and stated no OS installed.
1. In rooting guide as per Here download file linked in the guide and unzip.
2. From folder 3 of that zip file there is a folder called data containing stock.img - place this onto sdcard.
3. Then go to this thread and download the files as hosted on mega.nz - over 2 gig.
4. Extract that zip to the sd card so that on the card is a folder called 'dload'
5. To confirm, the dload folder should have update.app and 2 folders called dt and hw
6. Put sdcard into phone.
7 .Boot into TWRP
8. Goto install, select storage, select your sdcard then select stock.img, agree to install, ignore message about no os.
9.Once that has installed my phone just restarted, EMUI came up, read the dload folder automatically and ran.
Then once phone started it found a newer update and installed that.
Phone is now working, unrooted and bootloader is locked again.
All this was found on the XDA site, just across various posts.
Thanks again to all.
********ORIGINAL BELOW********
Hi all.
Please help, I'm a ****!
I unlocked bootloader with Huawi code from thier website.
Then I installed TWRP
Which in turn installed SuperSU
All rooted, jobs a fish. as per - This one and This thread.
Decided I dont need root anymore.
Tried to reset and wipe the phone.
Went into TWRP did a factory reset wipe.
Then went into TWRP again and did advanced wipe, and selected everything.
(yes yes i know, what a tit)
So after that i get the 'this phones is unsecured' message, press up vol 3 seconds, press power button to conti, wait 5 seconds etc.
so I wait, and it sticks on 'Your device is booting'
Restart, can get into stock recovery and hisuit will see the phone and try to restore it but fails and say my device is not supported??
Can get into erecovery and connected to wifi to try and update but does not find anything to download.
can get into twrp.
I have downloaded a stock rom as per -- This ROM
Perhaps this is not the correct ROM, but then how do i find out the correct ROM needed now I can not access phone details?
Forced that onto SD card but TWRP will not run it and says it is corrupt.
I can see it with ADB and device manager so my question really is....HELP??
How can i get just stock rom back onto it and then un-root and re-lock the bootloader?
Cheers in advanced.
fabgav said:
Hi all.
Please help, I'm a ****!
I unlocked bootloader with Huawi code from thier website.
Then I installed TWRP
Which in turn installed SuperSU
All rooted, jobs a fish. as per - This one and This thread.
Decided I dont need root anymore.
Tried to reset and wipe the phone.
Went into TWRP did a factory reset wipe.
Then went into TWRP again and did advanced wipe, and selected everything.
(yes yes i know, what a tit)
So after that i get the 'this phones is unsecured' message, press up vol 3 seconds, press power button to conti, wait 5 seconds etc.
so I wait, and it sticks on 'Your device is booting'
Restart, can get into stock recovery and hisuit will see the phone and try to restore it but fails and say my device is not supported??
Can get into erecovery and connected to wifi to try and update but does not find anything to download.
can get into twrp.
I have downloaded a stock rom as per -- This ROM
Perhaps this is not the correct ROM, but then how do i find out the correct ROM needed now I can not access phone details?
Forced that onto SD card but TWRP will not run it and says it is corrupt.
I can see it with ADB and device manager so my question really is....HELP??
How can i get just stock rom back onto it and then un-root and re-lock the bootloader?
Cheers in advanced.
Click to expand...
Click to collapse
you can find the model (for me it's vns-l31) on the back of the phone, just find the corresponding oeminfo file and the update file. flash the oeminfo file, put the update file from the rom zip in the dload folder and reboot using the 3 button combo till it says something about installing update
here's a list of update files: https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124
and here you can find the oeminfo files, there's a google drive link under oemfiles, at least for the vns-l21, 22 and 31: https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873
mjz2cool said:
you can find the model (for me it's vns-l31) on the back of the phone, just find the corresponding oeminfo file and the update file. flash the oeminfo file, put the update file from the rom zip in the dload folder and reboot using the 3 button combo till it says something about installing update[/url]
Click to expand...
Click to collapse
Hi, thanks for the reply.
All of those links refer to the P9 Lite - is this the same internals and software as the normal P9?
On the back of my phone it has - Model- EVA - L09 FCC ID: QISEVA-LO9 - IC: 6369A-EVALO9
I do not see how this relates to specific oeminfo file?
Lasatly, can you provide details on how to flash the oeminfo file to device and do you mean the following for the update:
So in rom sip there is a update.app file - extract this to sdcard in a new folder called dload? then install that via twrp?
Cheers
fabgav said:
Hi, thanks for the reply.
All of those links refer to the P9 Lite - is this the same internals and software as the normal P9?
On the back of my phone it has - Model- EVA - L09 FCC ID: QISEVA-LO9 - IC: 6369A-EVALO9
I do not see how this relates to specific oeminfo file?
Lasatly, can you provide details on how to flash the oeminfo file to device and do you mean the following for the update:
So in rom sip there is a update.app file - extract this to sdcard in a new folder called dload? then install that via twrp?
Cheers
Click to expand...
Click to collapse
first of all, no, p9 is a different phone, but you posted on the p9 lite forum. i'd suggest posting this question on the p9 forum.
i don't know exactly how it works for the p9, but it shouldn't be much different.
for the rom zip: inside that zip there's an update.app file, that file should indeed be put in a new folder called dload, but it won't be installed through twrp.
on the p9 lite it works like this: you flash the oemfile through twrp, and after that push and hold both volume buttons and the powerbutton till the phone reboots and shows an update progress screen, then you can release the buttons. now the update file will be installed. but then again, i don't know the procedure for the p9 so be sure to post your question on the correct forum.
edit: i've taken a look on that link to the stock rom you tried installing, it's a zip file that contains the dload folder, just put that folder on the root of your sdcard. do make sure it's the correct version.
you will have to flash the stock recovery for your phone however, and if the p9 works the same way as the p9 lite you should find an oeminfo file and flash that with twrp.
So sorry, I didn't realise I was in the lite forum!
I'll ask a mod to move, sorry and thanks for you help.
fabgav said:
So sorry, I didn't realise I was in the lite forum!
I'll ask a mod to move, sorry and thanks for you help.
Click to expand...
Click to collapse
here's a link to the oeminfo for eva -l9: https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903 i think that one should be flashed in twrp, and after that you can use the 3 button combo
no problem at all
fabgav said:
Hi, thanks for the reply.
All of those links refer to the P9 Lite - is this the same internals and software as the normal P9?
On the back of my phone it has - Model- EVA - L09 FCC ID: QISEVA-LO9 - IC: 6369A-EVALO9
I do not see how this relates to specific oeminfo file?
Lasatly, can you provide details on how to flash the oeminfo file to device and do you mean the following for the update:
So in rom sip there is a update.app file - extract this to sdcard in a new folder called dload? then install that via twrp?
Cheers
Click to expand...
Click to collapse
Hello
Here it is p9 lite.
Section p9 is here. https://forum.xda-developers.com/p9
I think you are looking for this.
https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
Yes the steps are.
Bootloader
Twrp
Flash Cxxxoeminfo
DLOAD Bxxx
SOLVED
First post updated with fix.
Thanks for all the help here on XDA
deleted by user
Any other place i can download the "dload" file beisides mega...please any help...
Yureka 2 :NO OS installed .Do you want to reboot ? Clicked reboot.Mobile hangs
Hi,
I tried to install Lineage OS 15.1 custom ROM using TWRP recovery in my Yureka 2 YU5551. I wiped out the data before flashing. During flashing I faced Error 7 and unable to install custom ROM.Twrp asked this- NO OS installed. Do you want to reboot? I Clicked reboot and my mobile not even booted properly. Still hangs. I tried to open recovery mode using the power button and volume up and volume down button. I am unable to go to recovery mode. When I connect my mobile to my laptop its not recognizing as the phone is not restarting.
Can someone plz help me how to install an OS and start my phone. Thanks in advance.
Thanks
Thinagharraj
Hello sir, please notice me. Can I possibly get another link to get the stock.img because the link that you gave was already not available. Hoping for your response. Thanks
I have sticker in recovery no OS installed + no backup + locked bootloader
What can I do
----------------------/----------------------
Any one please help me
Hi
I have searched through just about every thread and tried just about every trick in the book to make my Honor 5c/7 Lite/NEM-L21 to work again but nothing works for my problem. I'll try to describe what I did, what I have tried and what I am able to do with it.
What I did
Unlocked bootloader the official way with code from Huawei.
Flashed twrp recovery
Installed SuperSU from twrp and rooted the phone
Tried to install some custom roms and some stock roms, eventually I tried to install something that apparently wasn't for my specific model and twrp started to throw errors at me
The main error whenever I tried to do something in twrp was "can't mount /cust.." and some more error message which I can't remember
After that I tried to reboot my phone and hoping that it would somehow heal magically, which, of course, it didn't
What I did not do
Take a backup before I started to mess with my phone, stupid, yes I know, but tell me if you have to
What I am still able to do
E-recovery: can boot into E-recovery and connect to wifi and search for package info but then it fails with an error message stating that something is wrong with the package
Stock recovery dload method: Starting to install the package but halts at 5% and then the phone reboots and boots with error stating that I should update again, not sure about what package is loading since I think I have a dload folder both on the internal and the external sd card, but I cant see the internal sd card anywhere (loading the external sd card through another phone)
Fastboot: can boot into fastboot with volume- and power button and do almost all the fastboot commands, but adb does not detect my phone.
What I have tried
Googled, looking here and searching deep inside myself for answers (without any luck, needles to say)
Tried downloading a stock rom NEM-L21***B132, Android 6.x Emui 4.1 and extracting boot.img, system.img, recovery.img and cust.img and while boot and recovery flashes fine with this extracted images everything goes ape**** when trying to flash cust and system, with cust I get a partition error while writing and with system I get a sparse flash write failure, I have no idea why this rom fails while I'm able to flash above mentioned files perfectly fine with a stock nougat rom (Nougat is the reason I started this adventure to begin with). When I flashed all the files fine and try to dload the whole update.app I get nowhere anyway, just a bootloop.
Tried to erase and reformat cust and system but when I try that in fastboot I get a remote: command not allowed.
Tried to flash twrp recovery and the flashing succeeds but I cant boot into it, tried several different versions designed for both 'nougat and marshmallow.
What I need
Someone to point me in the right direction because I am totally lost and almost going crazy after trying everything.
All the help and tips I can get from you guys is much appreciated, I'm willing to try everything you throw at me and answer any questions regarding my issue!
Thanks in advance, Jeremias
dload method, use B100 package.
thelous said:
dload method, use B100 package.
Click to expand...
Click to collapse
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.
jerre84 said:
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.
Click to expand...
Click to collapse
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)
thelous said:
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)
Click to expand...
Click to collapse
Found it, crossing my fingers that it will work this time.
Unfortunately I can't get it to update with the B100 package and the dload method. I can start the stock recovery and the update starts but it freezes at 5% and then the phone reboots with no error message and the bootloop continues.
Any more ideas?
Still no luck for me, anyone got any ideas?
jerre84 said:
Still no luck for me, anyone got any ideas?
Click to expand...
Click to collapse
what was your phone build number before all these? EMUI 4 or 5?
shashank1320 said:
what was your phone build number before all these? EMUI 4 or 5?
Click to expand...
Click to collapse
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.
jerre84 said:
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.
Click to expand...
Click to collapse
I had same issue on mine. I updated to nougat manually with few bugs and then flashed custom arsenic ROM
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
after over 10 hours of fiddeling around a found a really easy solution:
most of you know HWOTA helps with this, but the "normal" version wont work after flashing oreo. but this version is flashed via twrp and is still working!
but you will need a oreo compatible twrp, which you can find here
i know the links are to mate 9 software, but since the p10 and mate 9 are nearly identical, it works on the p10 as well
can you post the step by step guide?
i am on oreo 8.0.0.046 and want to flash another version, or downgrade to nougat because few things don't work on this version
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
failed install twrp- error find twrp 3.0.3, and i replaced to oero mate 9 recovery....
EDIT: success - problem was on the computer
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
i did sucsses to install twrp but on the second step, when i press on install on twrp, the phone restart to erocovey and failed to find the files. what am i doing wrong?
i think that i am stuck with that version forever....
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
johdost said:
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
Click to expand...
Click to collapse
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
t.h.i said:
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
Click to expand...
Click to collapse
EDIT : the process is sucsses, but its the same version.... 8.0.0.046
Bricked, no TWRP access, any ideas?
Hi.
I know this about a P10, I have a P10 Plus (VKY-L29C605), but the process should be similar, I think.
I bricked my phone after succesfully upgrading from B174 to B321 using HWOTA. After which I decided, since I was at it, to flash the Hyperplus Kernel. This led to a bootloop. To fix it I decided to just go ahead and HWOTA B321 all over again and get over it, and would have probably gone just fine, except I decided to rebrand (C605 > C432) while I was doing that, silly (no, stupid) mistake. This led to the brick I am currently expriencing, I have no recovery access, erecovery or TWRP.
So now I am left trying to unbrick the phone. I extracted the UPDATE.APP for both update_all_hw.zip and update.zip using the Huawei Extractor Tool with no difficulty, except unbricking methods ask for boot.img, which I could not find, so I went along without it and flashed: cust.img, recovery_ramdisk.img (using fastboot recovery_ramdisk command for Oreo), and system.img. All of the commands completed succesfully, but no shebang, still bricked and no recovery access. I figure this has to do with the rebrand as the result after executing the command "fastboot getvar vendorcountry" shows the rebrand pulled through (hw/eu 432).
I am currently downloading HWOTA8.zip (3GB worth of download) to see if I can do something it. I am also downloading the L29C432B360 OTA-FULL, since I believe I am not getting any progress becuase I used the updates for L29C605B321.
The kind people at funkyhuawei told me they could fix it with their tool, but I don't have the money for that right now.
I will post updates, but any ideas would be greatly appreciated.
Many of us have posted over this in the last couple of days. Seems like Funky Huawei unbrick tool was the mehtod to get it work for me. You could try that!
or use dc-phoenix for me it worked (= in the moment i try to capture the usb ports kommunikation so i have the tool with the aktual firmware longer for 3 days :silly:
would first give dc a try 20 bucks for 3 days is ok i think (=
johdost said:
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
Click to expand...
Click to collapse
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
So I was able to get the C432B360 firmware and I flashed it, but no I can't enter recovery mode because the battery is low (red lightning bolt/red led flash). Anybody know how to charge or force recovery mode boot from fastboot?
If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm
Greting
ure3808 said:
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
Click to expand...
Click to collapse
Greeting,
Can you explain the procedure of how to do it?
Thank you
I wanted to enable OTG on my NMO-L31 . So i had to root it and thought if i wanted to go that far i could use a rom as well and tried installing EliteRom . I unlocked the bootloader installed a custom twrp recovery by EliteRom ' s author and flashed it . Surprisingly any kind of audio playback doesn't work and now i want to go back . But i couldn't do it well and now stuck with EliteRom . I only have a full backup of my EliteRom and can only recover it using twrp .
To get the stock firmware i searched forums and found Huawei Firmware Finder , Huawei Update.app Extractor and Huwaei Multi Tool . There was numerous results with NMO-L31 so i had to find my region . The naming scheme was clear and after looking into available languages of changelogs for each firmware i detected my region.My plan was to get boot.img , system.img , cust.img and recovery.img . I couldnt find a cust.img and downloaded all firmwares of my locale overnight . I extracted everything they had and lastly found two cust.img to use . Here is the list :
NMO-L31C10B140
NMO-L31C10B140 OTA-Mf
NMO-L31C10B152
NMO-L31C10B351
NMO-L31C10B351 FullOTA-MF-PV
NMO-L31C10B355
NMO-L31C10B355 FullOTA-MF-PV
NMO-L31C10B357
I dont know meaning of MF or PV.
To use the unbrick opinion from Multi Kit i used :
system.img and boot.img of latest FullOta
EliteRom's custom TWRP as recovery.img
and used both cust.img seperatly in two seperate cases
But in both combinations the phone booted Android to show a encryption error and demanded me to factory reset and kicked me back to TWRP . TWRP has no factory reset opinion and i am afraid to flash original recovery.img to keep TWRP/my backup . If i flash stock recovery and the threre isn't a factory reset opinion there i cant flash anything again . I don't know a way to open up fastboot without pairing adb and adb pairing only happens when phone boots to Android . Maybe there is a way that i am not aware of.
Long story short i want to go back to stock rom and have handful of system,boot,recovery,cust images . I dont know which combination to use. I don't even know if it will work out or show that encryption error again . I don;t know if i can flash back twrp after flashing stock recovery . That would be the worst because i only have one backup and can only recover it from twrp . And i dont know if i have to format /data to ext4 before attempting to flash images . Wouldn't flashing an image handle filesystem releated parts of memory ?
What would be the best way out of this ? Can anyone with more experience help me ? Thanks in advance .
After some reading i used the unbrick method and selected originial recovery the log said it "Error! You are trying to flash the wrong image! " when trying to flash cust.img but said "All images are flashed succesfully" . Weirdly now phone booted to android and after getting the encryption error booted back to now stock recovery and did a factory reset . After booting back to Android i am surprised once again. I still have ElitreRom and everything is the same from model number to my home screen . What even happened ? :crying:
Shouldnt flashing the big system.img have solved everyting ? I thought it had everyting needed to bring back stock apps since it was the main file and the largest.
And now i have tried going with dload method . I put the big update.app file to dload folder on sd card and tried to force update with vol up + vol down + power button method . It failed at %5 saying
"Software install failed!"
"Incompatibility with current verison. Please download the correct update package"
Does it check the build and model number before installing anything ? They are still incorrect because EliteRom
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.