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?
It's very simply!
We have 2 recovery partition. First - Recovery, Second - eRecovery. eRecovery isn't useful.
I tested flashing TWRP in second partition. Its work!
Fastboot flash recovery2 yourTWRP. Img
For enter to eRecovery power off the Honor, hold vol up and connect to pc
Or type adb reboot erecovery
Cons and pros
+ you have both recovery and can flash OTA updates.
- entering via root and terminal command: reboot erecovery
You have stock recovery and TWRP forever! [emoji6] Before you do full software update
Usefull app from @m_esser - http://forum.xda-developers.com/showpost.php?p=67463880&postcount=6
good news! good idea!
But without pc connection not usable. No way to recover a backup if you are not near a pc!
What is the trigger to identify a pc connection? 5Volt signal? Bridget contacts?
maybe it will be possible to create a little usb-adapter?
non-toxic said:
good news!
Click to expand...
Click to collapse
I see only one con. Entering in erecovery without pc.
Sent from my HONOR 7 via TapaTalk
good morning sir! nice to meet you here!
inside!out said:
I see only one con. Entering in erecovery without pc.
Click to expand...
Click to collapse
yes, this seems to be right!
btw: there is a w-lan network inside too, but i was not able to connect to the huawei server or to dl a rescue file, so i think you are right and we can ignore them.
Info: If necessary, you can find the stock erecovery.img as recovery2.img in the v121 full rom. It seems to be unchanged since v121.
non-toxic said:
Info: If necessary, you can find the stock erecovery.img as recovery2.img in the v121 full rom. It seems to be unchanged since v121.
Click to expand...
Click to collapse
I have PLK-L01 debranded to TL01H and now it run in Android 6.0 (B634 6.2.1)
i'm too can't put any firmware in eRecvery ever. Also my eRecivery in Сhinese
inside!out said:
I see only one con. Entering in erecovery without pc.
Click to expand...
Click to collapse
Hi,
I am using a dual recovery configuration since several weeks. My personal preference is to install the stock recovery on /recovery and to install TWRP on /recovery2.
In order to get rid of the con mentioned above I have used Tasker and Tasker App Factory to make a small program for that purpose.
This APK is definitively not a masterpiece of software engineering (more a q&d solution) but it does what it should (at least for me) ... it shows a (re-)boot menu with some options the reboot the device into several modes including into eRecovery.
A Screenshot and the APK file itself are attached below.
Requirements:
To use this APK
the phone must be rooted (and therefore the bootloader must be unlocked)
root access must be granted to the app
Other Honor / Huawei devices:
Originally this app was intented to be used only on the Honor 7 phone. In the meantime several users on android-hilfe.de have tested it successfully on other Huawei devices as well. As far as I know by now the app is also working fine for the following devices:
Huawei P8 (GRA-LO9)
Huawei P9 (EVA-L09)
Additional comments:
There is no warranty for this app => you will use it on your own risk!
Due to very restricted spare time I will not provide any kind of support and I don't make any promise to continue development
The app does not check which recovery console is installed on both partitions - that's something you have to keep in mind by your own
The APK was developed on a Honor 7 with west-european firmware PLK-L01C432B330 by using Tasker and Tasker App Factory (decompiling will probably not work)
Credits:
Thanks to
@Sminki for the implementation of TWRP 2.8.7 for the Honor 7
@paulobrien for the implementation of TWRP 3.0.2 for the Honor 7 (the only aspect I am still missing is the option to reboot into /recovery2 from TWRP )
Crafty Apps EU for the powerful and easy to use tools Tasker and Tasker App Factory
AlicaFabienne on android-hilfe.de for testing the app on the above mentioned Huawei devices
Best regards
m_esser
---------- Post added at 02:56 PM ---------- Previous post was at 02:36 PM ----------
Hi,
in addition to the above mentioned con I see another weakness regarding dual recovery configurations.
Whenever the current configuration does not meet your needs you have to re-flash the recovery partitions manually by using adb and fastboot on a PC ... and that's quiet difficult if you are not at home or on travel without a PC.
Because of that I have created a flashable zip file for this purpose. When loading the zip file using TWRP you will be able to choose
recovery configuration
- /recovery: stock recovery + /recovery2: TWRP
- /recovery: TWRP + /recovery2: stock erecovery
- /recovery: stock recovery + /recovery2: stock erecovery
- to install the app "Reboot for Huawei & Honor devices" optionally
The only weakness of this approach is the fact that you need TWRP on one of both recovery partitions because the zip file cannot be flashed with the stock recovery .
For those of you who might be interested the zip file can be downloaded <here>.
Requirements:
To use this flashable zip file
the phone must be rooted for using the integrated apk file (and therefore the bootloader must be unlocked)
TWRP must be installed on one of both recovery partitions
TWRP's screensaver should be disabled to avoid issues with Aroma Installer
the flashable zip file can only be executed on Honos 7 devices with firmware versions PLK-L01C432B313 to PLK-L01C432B330 (no other device and currently no other firmware)
Additional comments:
There is no warranty for this zip file => you will use it on your own risk!
Due to very restricted spare time I will not provide any kind of support and I don't make any promise to continue development
The zip file was developed on a Honor 7 with west-european firmware B330 by using amarullz's Aroma Installer
Credits:
Thanks to
@Sminki for the implementation of TWRP 2.8.7 for the Honor 7
@paulobrien for the implementation of TWRP 3.0.2 for the Honor 7 (the only aspect I am still missing is the option to reboot into /recovery2 from TWRP )
amarullz for the awesome Aroma Installer
Best regards
m_esser
It's very useful，Thanks for sharing
Just to let you know - I have just made the flashable zip file B370 compatible.
It can be downloaded using the above mentioned link. The zip file has the name "H7-Recovery-Configurator-0.2beta.zip".
Best regards
messer
Just to keep you in the loop - I have just made the flashable zip file B371 compatible.
It can be downloaded using the above mentioned link. The zip file has the name "H7-Recovery-Configurator-0.4beta.zip".
Best regards
messer
question
inside!out said:
I have PLK-L01 debranded to TL01H and now it run in Android 6.0 (B634 6.2.1)
i'm too can't put any firmware in eRecvery ever. Also my eRecivery in Сhinese
Click to expand...
Click to collapse
hi , I want to debrand my huawei honor 7 to china firmware because it have more feature than Europe firmware but is it worth it ?
is it stable ?
The flashable zip will not work with TL01H ... and the integrated recovery images might be flashable directly but I don't know whether the recovery images will fit to your firmware.
Only for the rebooting apk it is very likely that it will work.
Best regards
m_esser
AHMD92 said:
hi , I want to debrand my huawei honor 7 to china firmware because it have more feature than Europe firmware but is it worth it ?
is it stable ?
Click to expand...
Click to collapse
I'm on B380 now (EMUI 4.0.1) Its perfect!!!
inside!out said:
I'm on B380 now (EMUI 4.0.1) Its perfect!!!
Click to expand...
Click to collapse
No problem with Google play services? Or any app compatibility ?
I'm getting excited ?
AHMD92 said:
No problem with Google play services? Or any app compatibility ?
I'm getting excited
Click to expand...
Click to collapse
No. I have solution w/o installing GAPPS
inside!out said:
No. I have solution w/o installing GAPPS
Click to expand...
Click to collapse
Great. Last question if you don't mind . It is safe to simply push the new rom using Fastboot. Now I'm using b371 eu
AHMD92 said:
Great. Last question if you don't mind . It is safe to simply push the new rom using Fastboot. Now I'm using b371 eu
Click to expand...
Click to collapse
its no safety. You need to debrand to CN model in android 5.0
inside!out said:
I'm on B380 now (EMUI 4.0.1) Its perfect!!!
Click to expand...
Click to collapse
If you don't mind, can you define the perfect? For example; compare with B371.
And what are the differences between TL01H and UL00 rom?
One of them is Dual 4G version, the other is 4G Mobile Edition... I couldn't understand.
Edit: Actually I need 4G+ or 4.5G, whatever you calling.. so CA support is important.
.
Martin213 said:
After de-brand 4g working in europe?
Sent from Paris with love
Click to expand...
Click to collapse
if your hardware work on 4G before debramd it will work after debranding. It deep in SOC, not in FW
memht said:
If you don't mind, can you define the perfect? For example; compare with B371.
And what are the differences between TL01H and UL00 rom?
One of them is Dual 4G version, the other is 4G Mobile Edition... I couldn't understand.
Edit: Actually I need 4G+ or 4.5G, whatever you calling.. so CA support is important.
Click to expand...
Click to collapse
it does not matter! All laid in SOC. Put UL00 . Honor 7 is havn't dual 4G models. one sim 4G, second 2g
on 380 phone is sleep, safe power and recieve push message fine. 34 hour from 1 charge (4 hour of screen time)
Warning : I am not responsable for any bricked devices, dead sd cards, or other issues, I just wanted to share this, because I know, there are many Honor 5x KIW-L21 C185 users, and this, in my case, worked.
Warning :
***This will turn your device into a single sim phone.***
This WILL CHANGE your CUST version to 432.
Because I couldn't wait anymore for the official MM update from Huawei. I managed to install EMUI 4.0 Android 6.0.1 on my KIW-L21 C185, Middle East Version following this steps here: http://forum.xda-developers.com/showpost.php?p=67851428&postcount=2 .
1. You need to install TWRP, obviously . http://forum.xda-developers.com/devdb/project/dl/?id=19454
2. Download mm-update from here http://forum.xda-developers.com/devdb/project/dl/?id=19446 and extract files, you should be seeing 2 image files : TZ.img and MODEM.img .
3. Download and install Huawei Update Extractor http://forum.xda-developers.com/showthread.php?t=2433454 .
4. In my case, I downloaded this firmware here http://download-c.huawei.com/download/downloadCenter?downloadId=84663&version=327467 .
5. Now, using the Huawei Update Extractor, open the downloaded firmware and extract BOOT.img , CUST.img , SYSTEM.img on your computer.
6. Reboot phone in recovery mode and make a full TWRP backup.
7.Wipe data/factory reset and then wipe system, Data, Cache, Cust, Dalvik/Art Cache.
8. Install, and in the bottom of the screen, choose install image as following:
I. BOOT.img install to Boot.
II. CUST.img install to cust_image.
III. SYSTEM.img install to system_image.
IV. TZ.img install to tz_image.
V. MODEM.img install to modem_image.
9. After installing all of the above files, just reboot and there it is.
Untill now, I haven't found any bugs or issues, except that in the 'About Phone' panel at Model Number it doesn't say anymore KIW-L21 , but says 'MSM8916 for arm64'.
Screenshots
Is it stable and all options working
Sent from my KIW-L21 using Tapatalk
kevoxy said:
Is it stable and all options working
Click to expand...
Click to collapse
So it seems, in my case,everything is working, no FC's , camera working fine in professional mode, extends battery life.
Only thing I didn't try is going back to stock C185 Rom.
Also,didn't try flashing others rom,because I really like how it's working on EMUI 4.0
hi boro Im flash this rom in honor 5x kiw-l21c185b140 everything good just rom one sim card not dual sim???
mammadpsy said:
hi boro Im flash this rom in honor 5x kiw-l21c185b140 everything good just rom one sim card not dual sim???
Click to expand...
Click to collapse
Never tried using dual sim mod,as I only use one sim, that I didn't check.
cosminvr27 said:
Warning : I am not responsable for any bricked devices'.
Click to expand...
Click to collapse
Hi, i flashed cm13 and i wanna do flash for this build because of change tz number to get newer builds of cm.
Is it work on cm 13 or i must have stock rom before doing flash, accidentally i removed my stock rom i think, and twrp backup didn't restored my previous rom.
Pls help. Tnx.
Sent from my KIW-L21 using XDA-Developers mobile app
najafi.ali.68 said:
Hi, i flashed cm13 and i wanna do flash for this build because of change tz number to get newer builds of cm.
Is it work on cm 13 or i must have stock rom before doing flash, accidentally i removed my stock rom i think, and twrp backup didn't restored my previous rom.
Pls help. Tnx.
Click to expand...
Click to collapse
I'm not sure, I would try going back to stock rom first , as I not know how would it affect flashing over CM. Try to revert to stock first , than do update,than flash CM again.
cosminvr27 said:
I'm not sure, I would try going back to stock rom first , as I not know how would it affect flashing over CM. Try to revert to stock first , than do update,than flash CM again.
Click to expand...
Click to collapse
You're right, I'll do that, but i didn't get back tu stock rom in my life, if i wanna do that how? Its like flashing cm? I didn't find KIW-L21 C185 VERSION stock rom for download anywhere, i don't know why.
Thanks again for your help ?
Sent from my KIW-L21 using XDA-Developers mobile app
najafi.ali.68 said:
You're right, I'll do that, but i didn't get back tu stock rom in my life, if i wanna do that how? Its like flashing cm? I didn't find KIW-L21 C185 VERSION stock rom for download anywhere, i don't know why.
Thanks again for your help ?
Click to expand...
Click to collapse
Here it is
http://click.xda-developers.com/api...d 5.1_EMUI 3.1_C185B130_Kuwait_Channel-Others
You have to put it on the sd card in dload folder than hold volume - , volume + and power , and the rest does it by itself..also, after , make sure you update to b140 , as it will ask for it after you configure the phone.
Tried installing twrp but didn't boot
And in twrp 3-0-0 doesn't have option to flash images in cust or tz partitions
cosminvr27 said:
e.
8. Install, and in the bottom of the screen, choose install image as following:
I. BOOT.img install to Boot.
II. CUST.img install to cust_image.
III. SYSTEM.img install to system_image.
IV. TZ.img install to tz_image.
V. MODEM.img install to modem_image.
9. After installing all of the above files, just reboot and there it is.
Untill now, I haven't found any bugs or issues, except that in the 'About Phone' panel at Model Number it doesn't say anymore KIW-L21 , but says 'MSM8916 for arm64'.
Click to expand...
Click to collapse
Hi, when.i wanna flash cust.img its not a cust partition to flash on to it, what is wrong? Is sth with my phone or my twrp version (3.0.2.0)?
najafi.ali.68 said:
Hi, when.i wanna flash cust.img its not a cust partition to flash on to it, what is wrong? Is sth with my phone or my twrp version (3.0.2.0)?
Click to expand...
Click to collapse
What partitions do you see ?
cosminvr27 said:
What partitions do you see ?
Click to expand...
Click to collapse
Boot and recovery, it can be fixed?
najafi.ali.68 said:
Boot and recovery, it can be fixed?
Click to expand...
Click to collapse
But you did revert to stock , right ?
cosminvr27 said:
But you did revert to stock , right ?
Click to expand...
Click to collapse
Yes, i flashed cm build of 18july @crpalmer, for newer builds and FP i need mm base because of tz number, i revovered my twrp.backup to stock and when i want to do your steps i see this problem.
It could be because of version of twrp? I donno how to change twrp.
Thanks for your help.
najafi.ali.68 said:
Yes, i flashed cm build of 18july @crpalmer, for newer builds and FP i need mm base because of tz number, i revovered my twrp.backup to stock and when i want to do your steps i see this problem.
Thanks for your help.
Click to expand...
Click to collapse
Yes,but you got back to stock using the update.app or your recovery ? If You did recovery try force updating stock using the dload folder and the update.app.
cosminvr27 said:
Yes,but you got back to stock using the update.app or your recovery ? If You did recovery try force updating stock using the dload folder and the update.app.
Click to expand...
Click to collapse
I said that i got back to stock with twrp restore,that i think it means recovery you said and now
im on kiw-l21 c185.
I dont get that, you mean that i put stock rom in dload forder then what? Use local update in updater? It will work?
d
najafi.ali.68 said:
I said that i got back to stock to stock with twrp restore,that ithink.it means
recovery you said and now im on kiw-l21 c185
I dont get that, you mean that i put stock rom in dload forder then what? Use local update in updater? It will work?
d
Click to expand...
Click to collapse
Yes.
Download this https://mega.nz/#!Q0YQmIQD!KSwQvGymMUf-YA4A5oDFBvg12UwQlPDm5dIOdTDsEjc
You should be seeing either an archive either the update.app file, wich is the stock b130 rom.
Now, copy the update.app on the sd card into a folder called dload ( If you don't see it, just create it ).
Power off the phone, then press at the same time volume +, volume - and power and it should install the stock b130 rom. Next just do the update to b140 through the updater and reinstall twrp and try again .
If while updating you encounter any errors , try reinstalling stock recovery first.
cosminvr27 said:
Yes.
Download this https://mega.nz/#!Q0YQmIQD!KSwQvGymMUf-YA4A5oDFBvg12UwQlPDm5dIOdTDsEjc
You should be seeing either an archive either the update.app file, wich is the stock b130 rom.
Now, copy the update.app on the sd card into a folder called dload ( If you don't see it, just create it ).
Power off the phone, then press at the same time volume +, volume - and power and it should install the stock b130 rom. Next just do the update to b140 through the updater and reinstall twrp and try again .
If while updating you encounter any errors , try reinstalling stock recovery first.
Click to expand...
Click to collapse
Ok when i got home i'll do.that and tell what happened.
Thank you so much
After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.
since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.
HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset
medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:
MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?
Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.
Hello
I did this, I would like to understand, if it is possible to finish c432b380.
1_ I am l31c432b370.
2_with adb me flash boot.img, recovery.img and system.img. Of c432b380.
3_reboot.
4_recovery huawei, wipe rest factory and wipe cache. reboot.
5_ it restarts, the phone is functional but the developer parameters and security parameters are bugged.
6_adb flash twrp 3.1.0.2, install hwdatafull c432b370 (it is full) .reboot.
7_parameter works.
8_twrp installs root v5.2 (boot b380) .reboot.
9_twrp installs small file 10,80 MB hwdatafullc432b380, v83108. Http://update.hicloud.com:8180/TDS/...1/full/VNS-L31_hw_eu/update_VNS-L31_hw_eu.zip .rebboot.
10 everything works.
But it must over smear optimization ?? I'm not dev, just curious to understand.
Chisetdel31260 said:
Hello
I did this, I would like to understand, if it is possible to finish c432b380.
1_ I am l31c432b370.
2_with adb me flash boot.img, recovery.img and system.img. Of c432b380.
3_reboot.
4_recovery huawei, wipe rest factory and wipe cache. reboot.
5_ it restarts, the phone is functional but the developer parameters and security parameters are bugged.
6_adb flash twrp 3.1.0.2, install hwdatafull c432b370 (it is full) .reboot.
7_parameter works.
8_twrp installs root v5.2 (boot b380) .reboot.
9_twrp installs small file 10,80 MB hwdatafullc432b380, v83108. Http://update.hicloud.com:8180/TDS/...1/full/VNS-L31_hw_eu/update_VNS-L31_hw_eu.zip .rebboot.
10 everything works.
But it must over smear optimization ?? I'm not dev, just curious to understand.
Click to expand...
Click to collapse
Need to know something's before do that
Otg is activated
App twin and privet space is officially in update ??
radwan020 said:
Need to know something's before do that
Otg is activated
App twin and privet space is officially in update ??
Click to expand...
Click to collapse
No, none of this is enabled since you can not install update.zip from c432b380. I just have the boot, recovery and system and a version.img file.
(Crc, curver, dts, efi, product, teeos, trustfirmware, vendor, verlist ..).
flash Elite Kernel v5.2 at last always
So there is App twin and Private Space on OFFICIAL B380 or not?
Chisetdel31260 said:
Hello
I did this, I would like to understand, if it is possible to finish c432b380.
1_ I am l31c432b370.
2_with adb me flash boot.img, recovery.img and system.img. Of c432b380.
3_reboot.
4_recovery huawei, wipe rest factory and wipe cache. reboot.
5_ it restarts, the phone is functional but the developer parameters and security parameters are bugged.
6_adb flash twrp 3.1.0.2, install hwdatafull c432b370 (it is full) .reboot.
7_parameter works.
8_twrp installs root v5.2 (boot b380) .reboot.
9_twrp installs small file 10,80 MB hwdatafullc432b380, v83108. Http://update.hicloud.com:8180/TDS/...1/full/VNS-L31_hw_eu/update_VNS-L31_hw_eu.zip .rebboot.
10 everything works.
I'm not dev, just curious to understand.
Click to expand...
Click to collapse
Hello
So it is not good as no one gives me his opinion.
Chisetdel31260 said:
Hello
So it is not good as no one gives me his opinion.
Click to expand...
Click to collapse
Hi,
I would give a try later this week with this upgrade method on my European L31C432B370 firmware based P9 Lite (L31C432 Dual SIM version, 3GB RAM model).
Only problem is that I see in it is just moments when you need to *again* unlock boatloader to flash TWRP image and finalize install of add-on software.
Otherwise method is just fine afaik and as far I can see as member of Service Center for multiple bigger brands like *cough* Apple *cough* , Huawei, LG, Samsung and Sony in Zagreb.
Peace
Sent from Google Chrome on Lenovo Laptop
Anyone can tell how is the battery behaving on 380 ? cause on 370 it sucks big time.
Does it have App Twin and Private space?
Is the battery drain fixed?
No, there is not all its.
Since I can not install the rest of the files, (crc, curver, dts, efi, ect ....)
All I flash from b380 is boot.img, recovery.img, system.img and the zip version b380.
I admit that double appl and private space, DLOADDDD, I do not care. It serves no purpose for me.
I just wanted to understand android, and how huawei does to send ota.
It's useful.
Hi to test again, i just returned to b336 and hisuite offers me update for b370. So I do it to know where he writes the update.
I think HiSuite useful files b370 full ota mf.
It does not use full ota mf pv.
So I wonder if it is possible to replace the files by b380?
And how to tell him that it must be installed?
What is a .dbk file?
There is no news ??
Sent from my P9 lite using XDA Labs