Related
Hello Everyone, I have ALE-L21 and my current firmware is C185B130 (apparently C185 is UAE region but i live in pakistan). Device is bootloader unlocked, rooted with TWRP installed.
I have a TWRP backup of current rom. I wanna try the 5.1 beta released for Europe but it says here ( http://forum.xda-developers.com/p8lite/general/beta-firmware-p8-lite-ale-l21-c432b008-t3243228 ) that i need C432B132 to upgrade to this. So I downloaded this firmware(C432B132) from Huawei website. There were two folders in it, dload and CUSTOM(not sure what that for). I extracted system.img, recovery.img, CUST.img, boot.img from UPDATE.APP given in the dload folder. So here is what i'm thinking.
1) Flashing the extracted system.img, recovery.img, CUST.img, boot.img would get me to C432B132?
2) After i install B132 can I upgrade to 5.1 using EMUI local update?
3) If something goes wrong, can I just flash TWRP and restore the backup?
-
Or this whole idea is foolish and i would screw up my phone after flashing system, cust and boot of some other firmware designed for some other region???
SobanAmin said:
Hello Everyone, I have ALE-L21 and my current firmware is C185B130 (apparently C185 is UAE region but i live in pakistan). Device is bootloader unlocked, rooted with TWRP installed.
I have a TWRP backup of current rom. I wanna try the 5.1 beta released for Europe but it says here ( http://forum.xda-developers.com/p8lite/general/beta-firmware-p8-lite-ale-l21-c432b008-t3243228 ) that i need C432B132 to upgrade to this. So I downloaded this firmware(C432B132) from Huawei website. There were two folders in it, dload and CUSTOM(not sure what that for). I extracted system.img, recovery.img, CUST.img, boot.img from UPDATE.APP given in the dload folder. So here is what i'm thinking.
1) Flashing the extracted system.img, recovery.img, CUST.img, boot.img would get me to C432B132?
2) After i install B132 can I upgrade to 5.1 using EMUI local update?
3) If something goes wrong, can I just flash TWRP and restore the backup?
-
Or this whole idea is foolish and i would screw up my phone after flashing system, cust and boot of some other firmware designed for some other region???
Click to expand...
Click to collapse
No this is wrong
1. You need to downgrade to B052
2. Install B136a
3. Install B008(Android 5.1.1)
After each install is recommended to make wipe
Thanks
sokkoban said:
No this is wrong
1. You need to downgrade to B052
2. Install B136a
3. Install B008(Android 5.1.1)
After each install is recommended to make wipe
Click to expand...
Click to collapse
I dont think that you need to go all the way to B052 and then flash the required version
This is what i did:
1) Flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( I dont remember exactly :silly: ).
2) I flashed the UPDATE.APP file that was in the CUSTOM folder (that came with B132 rar file) via EMUI and it restored my build to B132.
3) Tried updating to 5.1 via EMUI but failed.
4) To give it a last try, I downloaded and flashed my phone with CUST, recovery, system, boot.img of B136a and then the update worked. My phone is now 5.1.1 B006
Thanks for the reply mate :good:
Confirmation ?
sobanamin said:
i dont think that you need to go all the way to b052 and then flash the required version
this is what i did:
1) flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( i dont remember exactly :silly: ).
2) i flashed the update.app file that was in the custom folder (that came with b132 rar file) via emui and it restored my build to b132.
3) tried updating to 5.1 via emui but failed.
4) to give it a last try, i downloaded and flashed my phone with cust, recovery, system, boot.img of b136a and then the update worked. My phone is now 5.1.1 b006 :d
thanks for the reply mate :good:
Click to expand...
Click to collapse
i also have p8 lite c185b130 is this confirmly working ?
wahaj0892 said:
i also have p8 lite c185b130 is this confirmly working ?
Click to expand...
Click to collapse
yeah its working fine. I think the battery life has improved a little bit or maybe it is just because i haven't installed much apps after flashing this rom compared to when I was using the B130. The only thing i miss from B130 is that small 2g, 3g written on the signal bars. This one only shows the 2g or 3g network type when the mobile data is turned on. Huawei cloud is also not present in it so you may wanna backup your contacts and stuff
SobanAmin said:
yeah its working fine. I think the battery life has improved a little bit or maybe it is just because i haven't installed much apps after flashing this rom compared to when I was using the B130. The only thing i miss from B130 is that small 2g, 3g written on the signal bars. This one only shows the 2g or 3g network type when the mobile data is turned on. Huawei cloud is also not present in it so you may wanna backup your contacts and stuff
Click to expand...
Click to collapse
thanks for the reply ...
some more question do i need a unlock bootloader ?
secondly i have a wired problem while typing my phone has a double tap issue is that gone ?
Hello,
Double tap issue still present in beta
sokkoban said:
Hello,
Double tap issue still present in beta
Click to expand...
Click to collapse
I dont use it often so I cant tell for sure
please im on b130 (5.0.1)
can you tell me (step by step) how can i get (5.1.1) my (bootloader unlocked with stovk recovery) please please
mimoriich said:
please im on b130 (5.0.1)
can you tell me (step by step) how can i get (5.1.1) my (bootloader unlocked with stovk recovery) please please
Click to expand...
Click to collapse
Hello,
Read this post, will help you http://forum.xda-developers.com/showpost.php?p=63993458&postcount=3
sokkoban said:
Hello,
Read this post, will help you http://forum.xda-developers.com/showpost.php?p=63993458&postcount=3
Click to expand...
Click to collapse
please tell me how u flash it i putted dload file to sd card & i reeboted (home + vol down + vol up ) its said error
SobanAmin said:
I dont think that you need to go all the way to B052 and then flash the required version
This is what i did:
1) Flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( I dont remember exactly :silly: ).
2) I flashed the UPDATE.APP file that was in the CUSTOM folder (that came with B132 rar file) via EMUI and it restored my build to B132.
3) Tried updating to 5.1 via EMUI but failed.
4) To give it a last try, I downloaded and flashed my phone with CUST, recovery, system, boot.img of B136a and then the update worked. My phone is now 5.1.1 B006
Thanks for the reply mate :good:
Click to expand...
Click to collapse
Can I apply this process for my ALE-L21C636B150...?
mimoriich said:
please tell me how u flash it i putted dload file to sd card & i reeboted (home + vol down + vol up ) its said error
Click to expand...
Click to collapse
If you are in stock recovery and have B132 try to put dload folder in internal memory and use software updater
Rifat Nurr said:
Can I apply this process for my ALE-L21C636B150...?
Click to expand...
Click to collapse
No, you can't. This beta is only for B136a(may be work also in B132)
sokkoban said:
Hello,
Double tap issue still present in beta
Click to expand...
Click to collapse
what about b170 ??
SobanAmin said:
I dont think that you need to go all the way to B052 and then flash the required version
This is what i did:
1) Flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( I dont remember exactly :silly: ).
2) I flashed the UPDATE.APP file that was in the CUSTOM folder (that came with B132 rar file) via EMUI and it restored my build to B132.
3) Tried updating to 5.1 via EMUI but failed.
4) To give it a last try, I downloaded and flashed my phone with CUST, recovery, system, boot.img of B136a and then the update worked. My phone is now 5.1.1 B006
Thanks for the reply mate :good:
Click to expand...
Click to collapse
can i flash c136a direcly over c185b130
MAYBE
wahaj0892 said:
can i flash c136a direcly over c185b130
Click to expand...
Click to collapse
Give It a try. If i doesn't work then you can just flash 132->136 and then apply update. But there maybe some problem with the version number changing to "BALONG". I faced this problem when I flashed 132 over my 130 but then I applied UPDATE.APP file(the small file in the custom folder) via EMUI Updater and it fixed the version number. But the 136a rom did not had any UPDATE.APP in custom folder so I dont know what to do if you get a version number problem. You can try flashing the 5.1 update via EMUI and maybe it will fix the version number problem (if it happened in the first place) or you can always goto 132->136 and apply 5.1
wahaj0892 said:
thanks for the reply ...
some more question do i need a unlock bootloader ?
secondly i have a wired problem while typing my phone has a double tap issue is that gone ?
Click to expand...
Click to collapse
yes you need to unlock the boot loader. What exactly do you mean by double tap issue? are you talking about the double tap to wake feature not working sometimes? Yes the DoubletapToWake dont works sometime which can be very annoying so I just disabled that feature and using the power button ever since. As for the typing issue, No I'm not facing any typing issues, never did on the B130 and not on this 5.1 version. Try using someother keyboard app?
SobanAmin said:
yes you need to unlock the boot loader. What exactly do you mean by double tap issue? are you talking about the double tap to wake feature not working sometimes? Yes the DoubletapToWake dont works sometime which can be very annoying so I just disabled that feature and using the power button ever since. As for the typing issue, No I'm not facing any typing issues, never did on the B130 and not on this 5.1 version. Try using someother keyboard app?
Click to expand...
Click to collapse
it is related to typing .. fast typing cause this issue .. i tired many apps nothing fix the issue
wahaj0892 said:
can i flash c136a direcly over c185b130
Click to expand...
Click to collapse
I tried to install b132 and b136a on my c185b130 but it failed both times.
---------- Post added at 06:27 PM ---------- Previous post was at 06:22 PM ----------
SobanAmin said:
Give It a try. If i doesn't work then you can just flash 132->136 and then apply update. But there maybe some problem with the version number changing to "BALONG". I faced this problem when I flashed 132 over my 130 but then I applied UPDATE.APP file(the small file in the custom folder) via EMUI Updater and it fixed the version number. But the 136a rom did not had any UPDATE.APP in custom folder so I dont know what to do if you get a version number problem. You can try flashing the 5.1 update via EMUI and maybe it will fix the version number problem (if it happened in the first place) or you can always goto 132->136 and apply 5.1
Click to expand...
Click to collapse
I have c185b130, there is c185b131 update on consumer.huawei.com for UAE region uploaded on 31-12-2015, will it work on my device? What are the changes in c185b130 and c185b131?
Hi guys
I was looking to upgrade my firmware on ALE-L02 to B150 via this thread:
http://www.carbontesla.com/2015/09/huawei-p8-lite-l02-c636b150-lollipop-firmware/
The update went though just fine, phone rebooted, relogged all apps. But now the device Build is now C50B311 (hi6210sft) I have found that my LTE is disabled on my nano sim, which usually worked via the old build. Is there a way to upgrade to 5.1? Or move away from this update (BalongC50B311)?
Device is not rooted etc. Stock.
Thanks guys!
Hello, it's because you have to downgrade to a build with two folder's (update and vendor ) and flash the two folder's for don't have this trouble named balong bug.
It's easy look in the zip update if you have the two and use the second folder like the previous .
I can't tell you because for look in I have to download this build .
Not all the update have it (the vendor folders)and you have to downgrade to the good version for don't have the balong trouble. This step factory reset and format your internal memory
Hello fellows. I am in a deep sh&*. Maybe someone can help.
I have a p10+ L09 converted to L29, rooted, bootloader unlocked. It was on rooted stock rom. Yesterday, tried to make the update, and something went wrong. Now, I can't install any rom exept future rom or something found here. I've tried rayglobe knife, Huawei multi tool, eRecovery, dload, and no way to install an official rom. I am barely able to install twrp, format data, and install future rom before rebooting.
Tried to extract boot, cust, system from the original rom, but it says finished and bootloop just after the unlocked message. On latest versions, I cant even find them in the update.app..
Any help, any downloadable file or link is really appreciated. Please help...
dj_varizes said:
Hello fellows. I am in a deep sh&*. Maybe someone can help.
I have a p10+ L09 converted to L29, rooted, bootloader unlocked. It was on rooted stock rom. Yesterday, tried to make the update, and something went wrong. Now, I can't install any rom exept future rom or something found here. I've tried rayglobe knife, Huawei multi tool, eRecovery, dload, and no way to install an official rom. I am barely able to install twrp, format data, and install future rom before rebooting.
Tried to extract boot, cust, system from the original rom, but it says finished and bootloop just after the unlocked message. On latest versions, I cant even find them in the update.app..
Any help, any downloadable file or link is really appreciated. Please help...
Click to expand...
Click to collapse
What error/behaviour are you getting from erecovery?
Plop
Hello mate. Thanks for your time.
ERecovery crash everytime at 5%. If I try to download via erecovery, it doesn't download.
I've tried to extract the files from update. App, and inject them via fastboot. It goes to the end of the operation, but once rebooted, it bootloop before the Huawei logo..
I don't understand what happens.. It's like if the phone don't want the original firmware anymore..
If you have any files to propose me, I really want to try tonight...
Can you somehow recover your original oeminfo with TWRP and retry erecovery? That's how I got out of a similar situation, although I can't say for sure whether I really had the same root cause.
Hmm not sure that the oem info is ok or corrupted...
That's what I am affraid of..
I will try in a moment to see..
If it's corrupted, that means the phone is dead?
In that case you could try funkyhuawei, they provide their own oeminfo and erecovery connection. They do cost money though.
May I ask what makes you want to go away from the fromfuture ROM?
This... Android 5.1, emui 3.1
I don't know if iam becoming stupid with age, but can't find any more recent... And with the kids yelling on my back.... Lol
Well, I found a recent rom from future. Had some troubles with Android locking magisk, but now it's working ( update magisk before putting your Gmail account and restore). For now it's working fine. Just had a few freezes here and there but since this morning it's going fine. I think I'll stay with it for now.
Thanks for the people who tried to help me.
XDa rules!
[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, I met some problems with my Nova plus mla-al10.
In short, the phone cannot boot and I need help with getting the offical emui5.0 dload upgrade package. (probably)
Below is the whole story:
1. The phone is unlocked.
2. Upgraded emui4 180 to emui5 in the emui4 system. The system indicated the target version is emui5 352. After updated, my version turned into NRD 90M test-keys without many huawei custom apps. ( I think it's because of the lack of data-update package, but it's too late now)
3. I tried to solve the version problem and I flashed the phone through fastboot with RECOVERY, BOOT, SYSTEM & CUST extracted from the downloded update packages. ( First 358, later I tried several other versions, same failing)
4. Then I cannot boot my phone. Just enter erecovery after 2nd reboot, and I cannot get the Rom downloaded through erecovery. Error reported.
5. Then I tried the dload update mode with a certain emui4 dload rom which I can only got from the internet for the MLA version. I cannot make sure what the ROM version was, like b122 or b133, emui4. I failed during update in the official recovery. 5%, 45% ,several times.
6. So I tried to use the twrp and both lineage and asop rom from #Henkate. Thank you #Henkate, the phone booted again. The system worked fine, except for one problem: When I use the China mobile(TD-LTE) and China unicom(WCDMA/LTE), I cannot dial out or dial in ( busy line). The sms and data(internet) worked fine. The signal is good. The sim card seemed to be successfully registered. China telecom seems worked fine(FDD-LTE) with dialing, sms and network. By the way, the china telecom simcard is the first card I used in the first lineage's first boot. I just found it abnormal with the problem above recent days.
7. Then I flashed the asop from #Henkate after wiping the system, cache and data. The same problem.
8. Now I cannot get where the problem is. I guess maybe the baseband software got wrong, so I wanted to flash the modem.img into the phone. The only way I think possible is to flash the dload package with version above 358 (or 360 which I also flashed through fastboot)through the huawei official recovery. The question is where I can get the package and is it the right thing to do? If not, how can I get back to the offical EMUI or other roms functioning normally?
Please help!
Thank you in advance!