Related
I'm at my wits end here. I copied the contents the emoji zip from https://android.gadgethacks.com/how-to/get-android-nougats-all-new-emojis-right-now-0170328/ for Android N emojis on my L02 (Telstra Australia variant ALE-L52) on 5.0.1 into my system folder and caused it to bootloop, then I got TWRP installed and actually flashed it which let it boot but with a different font and Messaging and Phone among other things weren't working. So I reflashed with 5.1 variants of those files in that zip and flashed a 6.0 stock recovery and did a factory reset and now it won't even let me log in to a Google account so I can restore my app backups which means I'm locked out of several apps I need authenticators for.
Is there anywhere I can download the full image for ALE-L02C451B280? I have access to a second device but I do not want to void the warranty on that by unlocking the bootloader and replacing the recovery just to fix my phone, so is there a way to create a flashable backup of the system without root or an unlocked bootloader
Edit: Great, flashed the official 6.0 image like suggested in the updating thread and now it won't even get past the bootloader, can't even boot to fastboot or recovery. It's officially f**ked
Well, if you can't boot to bootloader/fastboot to install TWRP, repair the phone then your phone is kinda bricked
I see the same symptoms as mine
https://forum.xda-developers.com/p8lite/help/help-bricked-p8-lite-t3522136
Any new suggestions?
What does your bootloader say? Enter it and unpack the UPDATE.APP using Huawei Update Extractor. Then flash System, cust, boot and mybe recovery with fastboot.
Vinnipinni said:
What does your bootloader say? Enter it and unpack the UPDATE.APP using Huawei Update Extractor. Then flash System, cust, boot and mybe recovery with fastboot.
Click to expand...
Click to collapse
That's how it ended up bricked in the first place
mercom said:
I see the same symptoms as mine
https://forum.xda-developers.com/p8lite/help/help-bricked-p8-lite-t3522136
Any new suggestions?
Click to expand...
Click to collapse
I ended up fixing it by doing a nandroid backup of another L02 running the original Telstra firmware and restored that, fixed it with a few minor bugs (gave me the Balong bug, so I can't even download any Huawei apps anymore, and I can't disable the stock music app for some reason, and the lock screen is weird, I can't swipe to unlock anywhere it has to be from the circle in the middle). I've just given up hope that I can get the official 6.0 on my L02
Hello,
I tried to flash the RessurectionRemix ROM and it was working well except the LTE so I decided to get back to EMUI.
Problem, i took the backup of bluesmoothie and flashed it but the phone never finish to boot.... (I didn't wipe anything, i thought that the restore function of TWRP was doing everything, am I wrong ?)
Moreover, the TWRP recovery can't access the content of my ext sdcard where the RR ROM is located and even if i put this rom to internal storage, i got the ERROR 7 (this is for deive: can; you have generic_a53)
Do you know what can I do to :
- Come back to EMUI
- Unroot the phone
- Re-lock the bootloader
The files of the TWRP backup are located on the sdcard, if i wipe data/system/cache, will it delete these files ?
Infos :
- Bootloader unlocked
- TWRP of Garak (but still have ERROR 7 now)
Thank you very much
First you need to flash the stock recovery in fastboot. After that you need to put the update.app in a folder called dload in your internal storage.
wangdaning said:
First you need to flash the stock recovery in fastboot. After that you need to put the update.app in a folder called dload in your internal storage.
Click to expand...
Click to collapse
Okay but where can I find the stock recovery ?
Then, do i have to flash it via ADB like i did with TWRP ?
After that, where can I find the "update.app" that you are talking about ?
If i'm right, you're telling me that i can't go back to EMUI without flashing the stock recovery ?
That is correct. First use firmware finder to get the update.app. There is a firmware extractor tool for Huawei firmware. Use it to extract the recovery.img and flash with fastboot.
wangdaning said:
That is correct. First use firmware finder to get the update.app. There is a firmware extractor tool for Huawei firmware. Use it to extract the recovery.img and flash with fastboot.
Click to expand...
Click to collapse
First of all, thank you very much for your anwser, it's very kind of you.
If i understood everything, that's what i have to do :
- Download one of the Huawei firmwares with Huawei Finder (Better get the B100 or another one ?)
- Extract the recovery.img with the update.app from Huawei Finder
- Flash the stock recovery with ADB
Then :
- I put the update.app that i get through the Huawei Finder in the dload folder of the internal storage (If i flash the stock recovery, will I be able to put files in the storage ?)
- I reboot the phone in recovery and normally, it should install the EMUI rom
At the end, my phone will no longer have a custom recvery, bootloader unlocked and root status ?
iSpeeX said:
First of all, thank you very much for your anwser, it's very kind of you.
If i understood everything, that's what i have to do :
- Download one of the Huawei firmwares with Huawei Finder (Better get the B100 or another one ?)
- Extract the recovery.img with the update.app from Huawei Finder
- Flash the stock recovery with ADB
Then :
- I put the update.app that i get through the Huawei Finder in the dload folder of the internal storage (If i flash the stock recovery, will I be able to put files in the storage ?)
- I reboot the phone in recovery and normally, it should install the EMUI rom
At the end, my phone will no longer have a custom recvery, bootloader unlocked and root status ?
Click to expand...
Click to collapse
Yes, that's correct. But you have to put update.app in dload folder on your SD card as far as I know. That's how I did it.
I couldn't find B100 on Firmware Finder and I've got relocked bootloader on Nougat.
Yes, you will need to copy the update.app to internal storage in TWRP, then flash the stock recovery. After flashing you need to hold all three buttons when booting (just like getting into TWRP. After update you will have no custom recovery, no root, and it should lock bootloader.
wangdaning said:
Yes, you will need to copy the update.app to internal storage in TWRP, then flash the stock recovery. After flashing you need to hold all three buttons when booting (just like getting into TWRP. After update you will have no custom recovery, no root, and it should lock bootloader.
Click to expand...
Click to collapse
I did everything, now it's booting but it's VERY VERY LONG... I'll wait and pray
iSpeeX said:
I did everything, now it's booting but it's VERY VERY LONG... I'll wait and pray
Click to expand...
Click to collapse
If it doesn't boot, then boot in recovery and do a factory reset and then it should boot. It happened to me and that's what I did.
#Henkate said:
If it doesn't boot, then boot in recovery and do a factory reset and then it should boot. It happened to me and that's what I did.
Click to expand...
Click to collapse
I still have the warning message "your phone is unlocked", is it normal ?
When i boot into recovery it's displaying "eRecovery" and ask me to download the new update of recovery but it fails when getting the package. I can only reboot and turn off :/
Thank you as always
iSpeeX said:
I still have the warning message "your phone is unlocked", is it normal ?
When i boot into recovery it's displaying "eRecovery" and ask me to download the new update of recovery but it fails when getting the package. I can only reboot and turn off :/
Thank you as always
Click to expand...
Click to collapse
You shouldn't have that message anymore.
Are you sure that the update.app got installed? @wangdaning told you to put it on dload folder in internal memory. I don't know if that is right or if it works, but I've put it in dload folder on sdcard when I've installed update.app.
#Henkate said:
You shouldn't have that message anymore.
Are you sure that the update.app got installed? @wangdaning told you to put it on dload folder in internal memory. I don't know if that is right or if it works, but I've put it in dload folder on sdcard when I've installed update.app.
Click to expand...
Click to collapse
Well i wasn't in front of it when it finished and I just did it : the update stops at 5% and then the phone reboot....
Do you know what do I have to do ? I took the recovery from the last B350 on huawei firmware finder
EDIT1 : but this time in recovery i can Reboot, Wipe factory reset, Wipe cache
iSpeeX said:
Well i wasn't in front of it when it finished and I just did it : the update stops at 5% and then the phone reboot....
Do you know what do I have to do ? I took the recovery from the last B350 on huawei firmware finder
EDIT1 : but this time in recovery i can Reboot, Wipe factory reset, Wipe cache
Click to expand...
Click to collapse
You can read in this post the steps I've used to relock the bootloader and get update (official I guess) through Settings > System update. Just "click to show content".
#Henkate said:
You can read in this post the steps I've used to relock the bootloader and get update (official I guess) through Settings > System update. Just "click to show content".
Click to expand...
Click to collapse
The problem is that the phone doesnt finish to but anymore... i can't do things in menu.
When you talk about SD card, it's the external sd card ? Because i don't have access to it anymore, but i have the partition SD Card
When you installed the B340 update, you seen the percent growing up and had a "success" message ? Because, for me, the update is stuck at 5% and then it reboot the phone
iSpeeX said:
The problem is that the phone doesnt finish to but anymore... i can't do things in menu.
When you talk about SD card, it's the external sd card ? Because i don't have access to it anymore, but i have the partition SD Card
When you installed the B340 update, you seen the percent growing up and had a "success" message ? Because, for me, the update is stuck at 5% and then it reboot the phone
Click to expand...
Click to collapse
Yes, I mean external sdcard.
Reinstall TWRP and restore bluesmoothie's backup and then flash the stock recovery again.
I didn't have any issues with installing the B340 firmware. It was installed successfully.
Try to follow the steps I've used. You shouldn't have any problem.
#Henkate said:
Yes, I mean external sdcard.
Reinstall TWRP and restore bluesmoothie's backup and then flash the stock recovery again.
I didn't have any issues with installing the B340 firmware. It was installed successfully.
Try to follow the steps I've used. You shouldn't have any problem.
Click to expand...
Click to collapse
Okay i'm going to try it right away
My external sd card doesnt show up anymore when i connect it to my PC, i don't know why
I mentioned internal SD card because you said your external was not recognized, but you might try putting the dload folder on external. I have done it both ways. Sometimes the update through stock recovery is finicky. If it doesn't finish run it again. Also, make sure your USB is disconnected, as may Huawei users have mentioned this causes it to freeze. If it still fails, try dloading a different update from firmware finder.
Did it work?
I didn't have so much time these days but I did it and it worked for the 1st part (flash bouesmoothie's backup). Tomorrow I'll do the final step! Thank you again
Here I am :
1 : flashed stock recovery from B350 and i don't have the "unlocked" message anymore !
2 : The update B350 made it, "update success"
3 : It doesn't boot for now
4 : The boot doesn't end
-----
1 : flashed TWRP recovery, launched a factory reset in the same time
2 : Phone booting again on B100
-----
1 : flashed stock recovery from b350
2 : flashed b350 update
3 : Everything is fine !
Thank you for your help !!!
[SOLVED] Hi i was on l-31c432b381 firmware with emui 5.0 and android 7.0, i have unlocked the bootloader for install magisk 12.0 and have root permissions, after months i saw an update for my phone (b389) so i tried to upgrade but i had twrp so error 1 or 7, i flashed the stock recovery, redowload the update and the install failed at 5%, so i tried to unistall magisk before update, but nothing it wont update, after few tries the upgrader says that the update now is not 300mb but is full and is 2gigs, so i think is the time.. but no. so i tried to force the update with 3 buttons recovery dload method but it doesn't work at all 5% at every try. so i searched for support and i found that the ota connot be installed on unlocked devices, so i tried to relock my bootloader with oem relock and the unlock number but it says root type is risk... so i can't even relock my bootloader.. other says that i have to install to relock or can relock... but is b381 the stock? or they instend the mm version? i don't remember what version p9 lite ships. i tried to flash imgs through fastboot but even if i flash system and boot of the b389 the system boot and the info are of the b381, unisatlling app system crash, so i restored my previous backup made through twrp recovery, i immidiatly noticed that the huawei boot animations was gone and was an android stock animation. i thinked it was fine and all was working properly, i give up o upgrade and i was fine but sad. after few hours i tried to make a paper copy with my printer that have nfc but my phone keep shows and hide nfc symbol like on off on off on off over and over even after reboot, after a call i understand that the audio doesn't was working, every type of audio not work even the mic. i don't see any other problems but without sounds is unusable as a phone or mulimedia things... sorry for bad english please HELP i tried all i founded ...
Franseven said:
Hi i was on l-31c432b381 firmware with emui 5.0 and android 7.0, i have unlocked the bootloader for install magisk 12.0 and have root permissions, after months i saw an update for my phone (b389) so i tried to upgrade but i had twrp so error 1 or 7, i flashed the stock recovery, redowload the update and the install failed at 5%, so i tried to unistall magisk before update, but nothing it wont update, after few tries the upgrader says that the update now is not 300mb but is full and is 2gigs, so i think is the time.. but no. so i tried to force the update with 3 buttons recovery dload method but it doesn't work at all 5% at every try. so i searched for support and i found that the ota connot be installed on unlocked devices, so i tried to relock my bootloader with oem relock and the unlock number but it says root type is risk... so i can't even relock my bootloader.. other says that i have to install to relock or can relock... but is b381 the stock? or they instend the mm version? i don't remember what version p9 lite ships. i tried to flash imgs through fastboot but even if i flash system and boot of the b389 the system boot and the info are of the b381, unisatlling app system crash, so i restored my previous backup made through twrp recovery, i immidiatly noticed that the huawei boot animations was gone and was an android stock animation. i thinked it was fine and all was working properly, i give up o upgrade and i was fine but sad. after few hours i tried to make a paper copy with my printer that have nfc but my phone keep shows and hide nfc symbol like on off on off on off over and over even after reboot, after a call i understand that the audio doesn't was working, every type of audio not work even the mic. i don't see any other problems but without sounds is unusable as a phone or mulimedia things... sorry for bad english please HELP i tried all i founded ...
Click to expand...
Click to collapse
Hi, my english is bad too , B389 is an OTA update, its impossible upgrade via fstboot or via TWRP (error 7). IMO the right way to fix your problems - downgrade to MM , then back to Nougat etc. (remove pattern Lock , Fingerprint lock, root etc. before installing downgrade). It will erase all your phone data!!!
Download official rollback package for your VNS-L31C432
http://download-c1.huawei.com/download/downloadCenter?downloadId=93789&version=373429&siteCode=sk
and download MM firmware VNS-L31C432B161 (Single SIM)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66022/f1/full/update.zip
1) Create a new folder dload in root directory of SD card (root directory : it means dont put it in any folder .) Now unpack the rollback package and copy its contents “UPDATE.APP” to the “dload” folder. Use the 3 button combo installation. After your firmware version should now be on “B300” or "test-keys".
2) Remove from dload folder rollback package, extract the ZIP file with MM firmware to the dload folder and use 3 combo button installation.
Or you can use this method : on your phone launch the phone dialer app and dial *#*#2846579#*#*. Next, select Project Menu – > Software upgrade – > SDcard upgrade – > and confirm the flashing process that is about to be initiated.
Good luck!
bozka1 said:
Hi, my english is bad too , B389 is an OTA update, its impossible upgrade via fstboot or via TWRP (error 7). IMO the right way to fix your problems - downgrade to MM , then back to Nougat etc. (remove pattern Lock , Fingerprint lock, root etc. before installing downgrade). It will erase all your phone data!!!
Download official rollback package for your VNS-L31C432
http://download-c1.huawei.com/download/downloadCenter?downloadId=93789&version=373429&siteCode=sk
and download MM firmware VNS-L31C432B161 (Single SIM)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66022/f1/full/update.zip
1) Create a new folder dload in root directory of SD card (root directory : it means dont put it in any folder .) Now unpack the rollback package and copy its contents “UPDATE.APP” to the “dload” folder. Use the 3 button combo installation. After your firmware version should now be on “B300” or "test-keys".
2) Remove from dload folder rollback package, extract the ZIP file with MM firmware to the dload folder and use 3 combo button installation.
Or you can use this method : on your phone launch the phone dialer app and dial *#*#2846579#*#*. Next, select Project Menu – > Software upgrade – > SDcard upgrade – > and confirm the flashing process that is about to be initiated.
Good luck!
Click to expand...
Click to collapse
Ok i'm posting in real time now. i'm copy update.app in dload folder (rollback)
it have completed ... wow
same android boot animation, the version says is nrd90m test keys (still no audio)
now i'm copying full mm firmware
its installing 40% i'm loving you.. 50% 60% 70%80%90% SUCCESS
user reset... OK
huawei boot animation with audio!!!!!!!!!!!!!!! and there is not unlocked text like (......can't be trusted...)
ok wifi connected skip.skip skip.... start
song... AUDIO WORKING
recording, its working, nfc ok
i'm on b161 and it shows update, now, can i update to the latest version?
THANK YOU SO MUCH
Franseven said:
Ok i'm posting in real time now. i'm copy update.app in dload folder (rollback)
it have completed ... wow
same android boot animation, the version says is nrd90m test keys (still no audio)
now i'm copying full mm firmware
its installing 40% i'm loving you.. 50% 60% 70%80%90% SUCCESS
user reset... OK
huawei boot animation with audio!!!!!!!!!!!!!!! and there is not unlocked text like (......can't be trusted...)
ok wifi connected skip.skip skip.... start
song... AUDIO WORKING
recording, its working, nfc ok
i'm on b161 and it shows update, now, can i update to the latest version?
THANK YOU SO MUCH
Click to expand...
Click to collapse
Yes, you can. Via OTA, or you can use TWRP (Meticulus 3.0.2.0 only ! ) and flash both .zip files. You must download two files:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v80474/f1/full/update.zip
and
http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_VNS-L11_hw_eu.zip.
In TWRP set Install, then select memmory SD card, and klick on
update.zip, confirm installation. After, STAY in TWRP, go back to Install, find file ...hw_eu....zip , confirm installation. Then select rebot system. Done!
bozka1 said:
Yes, you can. Via OTA, or you can use TWRP (Meticulus 3.0.2.0 only ! ) and flash both .zip files. You must download two files:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v80474/f1/full/update.zip
and
http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_VNS-L11_hw_eu.zip.
In TWRP set Install, then select memmory SD card, and klick on
update.zip, confirm installation. After, STAY in TWRP, go back to Install, find file ...hw_eu....zip , confirm installation. Then select rebot system. Done!
Click to expand...
Click to collapse
i've done b371 thrugh updater now it doesn't show newer versions but i'm using b389 dload and it should go ok right? (full b389 update.app)
Franseven said:
i've done b371 thrugh updater now it doesn't show newer versions but i'm using b389 dload and it should go ok right? (full b389 update.app)
Click to expand...
Click to collapse
Try it, but I think, you will get a message "not compatible" . Via dload its impossible, IMO use rather Huawei firmware finder or wait for OTA update.
bozka1 said:
Try it, but I think, you will get a message "not compatible" . Via dload its impossible, IMO use rather Huawei firmware finder or wait for OTA update.
Click to expand...
Click to collapse
yes it failed with b389 dload full
i'm on b371, i've to download and flash manually the b381 and after b389? where i can find otas?
Franseven said:
yes it failed with b389 dload full
i'm on b371, i've to download and flash manually the b381 and after b389? where i can find otas?
Click to expand...
Click to collapse
If I said, it's impossible manually update to 381 or 389 using OTA firmware, trust me . Try Firmware finder. GL!
bozka1 said:
If I said, it's impossible manually update to 381 or 389 using OTA firmware, trust me . Try Firmware finder. GL!
Click to expand...
Click to collapse
i tried full ota (firmware finder) flashes from twrp but gives error 7
e:unknown command [errno]
update_huawei_pkg_from_ota_zip: failed
Franseven said:
i tried full ota (firmware finder) flashes from twrp but gives error 7
e:unknown command [errno]
update_huawei_pkg_from_ota_zip: failed
Click to expand...
Click to collapse
https://m.youtube.com/watch?v=s5hHTZ4LGMM
bozka1 said:
https://m.youtube.com/watch?v=s5hHTZ4LGMM
Click to expand...
Click to collapse
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Franseven said:
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Click to expand...
Click to collapse
FF works with proxy fine, but you must first download and install Firmware finder proxy apk. On Nougat use TWRP 3.1.0-2.
---------- Post added at 21:03 ---------- Previous post was at 20:59 ----------
Franseven said:
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Click to expand...
Click to collapse
FF works with proxy , but you must download and install Firmware finder proxy apk. On Nougat use TWRP 3.1.0-2.
OMG, sorry !
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
hexahive said:
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
Click to expand...
Click to collapse
http://www.meticulus.co.vu/p/hi6250-custom-rom-installation.html
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
hexahive said:
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
Click to expand...
Click to collapse
You must already be on EMUI 5 to install EMUI5 based ROMs.
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..