Database Users

is it possible to lock/relock emui5.0 B336?

my phone original model name is vns-dl00
i upgrade it to emui5.0 by these steps
1. use twrp to change model to VNS-L31C432 and dload method to install VNS-L31C432B201
2. use twrp to flash B336(1.3G)+(0.66G)
3. now my phone's model name is HUAWEI VNS-L31, "about" is normal without error
my question is
after step2, phone state is unlock. how to relock/lock bootloader?
a. erecovery could not find any firmware. so it's not possible to use erecovery to lock
b. will factory reset remove 0.66G part?
c. adb relock command need a factory reset
d. could "dload method to reinstall B336 1.3G part" lock bootloader and keep 0.66G part?
THANKS!!

i think i have solved the problem:
i was in B336
i put 1.3G B336 part in dload folder
*#*#2846579#*#* update from SD card
after process, build is still B336 ,bootloader is locked and no data/app is lost

i am on PRA-LX1C432b106, i've unlocked the boot loader and receive your device is unlocked and cannot be trusted . to learn more visit... your device is booting now, but he do not boot. After a complete drain of the battery with the charger plugged in i can boot in software. but i do not have a keyboard option and any google play store account. cannot format wipe because miss of the keyboard . the question it is OK to install VNS-L31 software firmware on my device? And what version to put ?

No Recovery

I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:

NikkoVicedo said:
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
Click to expand...
Click to collapse
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_

daner[email protected] said:
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
Click to expand...
Click to collapse
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.

NikkoVicedo said:
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
Click to expand...
Click to collapse
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_

[email protected] said:
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
Click to expand...
Click to collapse
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.

NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
Hi guys, i Got the SAAAAAME Problem, this is all about what i PMd to you danerrickcuba FRP lock and bootloader unlocked. can't go to recovery, but has access to fastboot and wasn't able to do anything to fastboot.

Already fixed my phone. Had to pay 15 euros for DC Phoenix (this software saved me from bringing my phone to huawei service center to have it fix. Thank god!) so I can fix my phone. Recovery, eRecovery, Dload method working, and relocked bootloader. Currently updating my phone through OTA. Tnx danerrickcuba for suggesting methods to fix my phone....

NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
i have the same problem
bootloader unlock and frp lock ,bootlooping,rec&e-rec destoryed
if you do not log out google /shut down "find my phone"/check oem-unlock in developer mode before downgrading or flashing ,you will get "frp lock" warning
bootlooping may come from wrong update.app. eg. i use dload method to flash rollback(5.0-B300) pkg in EMUI4.1 , my rec and e-rec are destoryed
however, i think fastboot command could do nothing to "bootloader unlock ,frp lock,rec and e-rec destoryed ". i do not know how DC-phoenix fix this and i pay a new motherboard for my mistake

try https://forum.xda-developers.com/showpost.php?p=71338813&postcount=29

bricked device don't know how to fix (L31)

first off i cant use erecovery because im in unofficial nrd90m so it wont find anything, i accidently put the wrong oem info onto my device and i cant even boot into twrp, i have access to fastboot but i dont know enough about it to fix my issue unlocked boot loader and rooted if possible i want to downgrade to mm and get the official latest nougat update for uk(L31 single sim) i tried flashing stock recovery (nougat) and it says remote command not allowed.

bghyt said:
first off i cant use erecovery because im in unofficial nrd90m so it wont find anything, i accidently put the wrong oem info onto my device and i cant even boot into twrp, i have access to fastboot but i dont know enough about it to fix my issue unlocked boot loader and rooted if possible i want to downgrade to mm and get the official latest nougat update for uk(L31 single sim) i tried flashing stock recovery (nougat) and it says remote command not allowed.
Click to expand...
Click to collapse
Hello,
This thread will help you:
-Unlock bootloader (you must have the unlock code)
-flash oeminfo
-put the rollback package in dload folder (a little xda search)
-put B160 in dload
and you will get MM.

Besstheone said:
Hello,
This thread will help you:
-Unlock bootloader (you must have the unlock code)
-flash oeminfo
-put the rollback package in dload folder (a little xda search)
-put B160 in dload
and you will get MM.
Click to expand...
Click to collapse
I tried that yesterday after i posted this and it says FAILED stat does not match or somthing simular i will try again tommrow but that is probaly what it said.

Flashed oeminfo. Phone not booting

Anderusk said:
There is an assumption that I have a slightly different display. TWRP by Grarak does not work correctly with stock drivers. On LOS driver through a certain time, too, dies. I have A JDI screen, the device works correctly with stock ROM. I hate EMUI, and like LOS, but cant use it.
I already thought to install LOS and never reboot the device. 7 times i had died screen drivers on LOS and AOSP, and always it was happen in the first minutes after reboot.
@Axan,https://cloud.mail.ru/public/78UN/jSQ7mjhWT
I have stock ROM L11C432B394 flashed by 3 buttons, but device was AL-10 changed to Can-L11 with HUC, Vendor - hw, Country - eu.
Click to expand...
Click to collapse
I've flashed this oeminfo to my Can-L01 phone, phone does not boot (stuck at red huawei logo on boot) 3 button recovery wont start just a boot loop on 3 button... VolUP+Power does not open recovery... VolDown+Power opens fastboot mode but immediately reboots (there's a strange thing on screen that it started to say Phone Locked FRP Unlocked instead of Phone Unlocked or Relocked) my phone is totaly bricked now...

giraygokirmak said:
I've flashed this oeminfo to my Can-L01 phone, phone does not boot (stuck at red huawei logo on boot) 3 button recovery wont start just a boot loop on 3 button... VolUP+Power does not open recovery... VolDown+Power opens fastboot mode but immediately reboots (there's a strange thing on screen that it started to say Phone Locked FRP Unlocked instead of Phone Unlocked or Relocked) my phone is totaly bricked now...
Click to expand...
Click to collapse
I have finally get into a stable Fastboot mode, but unfortunately my phones serial number has changed to the oeminfo shared by our friend so my unlock code does not work anymore. Since the phone can not boot i cannot set Manufacture mode so i cannot unlock using paid apps. I am at the hands of our friend who shared oeminfo twrp backup to share his Unlock code inorder to recover my phone back to my oeminfo backup file. Or my phone is total brick

giraygokirmak said:
my phone is totaly bricked now...
Click to expand...
Click to collapse
You need to know what you're doing. in my country, changing IMEI is a criminal offense.
It is possible to raise locked phone using the firmware with three buttons, in this case I think you need to try a can-l11, because oeminfo is from can-l11 model

giraygokirmak said:
I've flashed this oeminfo to my Can-L01 phone, phone does not boot (stuck at red huawei logo on boot) 3 button recovery wont start just a boot loop on 3 button... VolUP+Power does not open recovery... VolDown+Power opens fastboot mode but immediately reboots (there's a strange thing on screen that it started to say Phone Locked FRP Unlocked instead of Phone Unlocked or Relocked) my phone is totaly bricked now...
Click to expand...
Click to collapse
Anderusk said:
You need to know what you're doing. in my country, changing IMEI is a criminal offense.
It is possible to raise locked phone using the firmware with three buttons, in this case I think you need to try a can-l11, because oeminfo is from can-l11 model
Click to expand...
Click to collapse
In my country it is illegal too besides i lost my own serial and imei because of this i think because my serial was different before flashing this oeminfo image backup of yours. I was only expecting to change country and vendor info to flash european firmware not trying to change my imei. And also phone does not boot just shows red huawei logo and thats all no recovery no erecovery and no button combination works like 3 button reboot...

I previously wrote in the subject that changed the location of the device through Huawei Unlock Client. Why u decided change it by flashing oeminfo i dont know. For firmware through three buttons need stock recovery, not erecovery.
Once i tryed flash by three buttons with stock erecovery and twrp in recovery, it was failed. But i many times flash stock firmware with stock recovery and twrp in erecovery and locked bootloader.

Anderusk said:
I previously wrote in the subject that changed the location of the device through Huawei Unlock Client. Why u decided change it by flashing oeminfo i dont know. For firmware through three buttons need stock recovery, not erecovery.
Once i tryed flash by three buttons with stock erecovery and twrp in recovery, it was failed. But i many times flash stock firmware with stock recovery and twrp in erecovery and locked bootloader.
Click to expand...
Click to collapse
I didnt have credit and thus i couldnt use HCU Client, How did you managed to flash many times stock recovery and twrp while having locked bootloader? I read that this is impossible... When i try flashing stock firmware or recovery fastboot only says
FAILED (remote: Command not allowed)
finished. total time: 0.018s

With a locked bootloader, you can flash through three buttons. You cannot flash TWRP or other partitions.

Anderusk said:
With a locked bootloader, you can flash through three buttons. You cannot flash TWRP or other partitions.
Click to expand...
Click to collapse
You dont understand... 3 button does not work! It just reboots endlessly while pressing 3 buttons at the same time. I've been using 3 button eRecovery menu before, i know how to enter to it. But after flashing your TWRP Backup phone stuck at boot logo red huawei logo and these combinations do not work, i repeat do not work!
VolUp + Power On --> This should bring recovery menu but it doesnt.
VolUp+VolDown+Power On --> This should bring force flash application but it just reboots to huawei logo endlessly...
VolDown+USB Plug --> This should bring Fastboot but it just shows fastboot then reboots immediately.
VolDown+PowerOn + USB Plug --> This brings Fastboot but i cant flash anything because PHONE Locked status and unlock you've provided does not help.
In the end, i have a total brick. I will try to forcefully flash through DC-Phoenix software but i lost hope with the phone completely plus i'll have to pay 15euro just to try... It was perfect before your oeminfo twrp backup file. I just wanted to change vendor/country info thats all and didn't want to use HCU Client to change it
All CAN-L11 or L01 owners DO NOT, DO NOT use any other person's oeminfo partition backup in any way!!!!!!!

giraygokirmak said:
VolUp+VolDown+Power On --> This should bring force flash application but it just reboots to huawei logo endlessly...
Click to expand...
Click to collapse
3 buttons work, but u dont know how use it.
I say again, u can flash with VolUp+VolDown+Power On if u have stock recovery and locked/unlocked bootloader and locked/unlocked FRP. I know because i did it.
Do you know how to use Google search? Look for information on how to flash with three buttons. And go to relevant topic.

Anderusk said:
3 buttons work, but u dont know how use it.
I say again, u can flash with VolUp+VolDown+Power On if u have stock recovery and locked/unlocked bootloader and locked/unlocked FRP. I know because i did it.
Do you know how to use Google search? Look for information on how to flash with three buttons. And go to relevant topic.
Click to expand...
Click to collapse
Dude, in order to restore your oeminfo twrp backup one has to be on TWRP recovery not Stock recovery. So in TWRP recovery if you restore the file oeminfo twrp backup of yours and reboot phone gets into my situation. I know how to use 3 button force flash (its been written trillion places on web including this forum) i wrote here as a warning because you have shared your OEMINFO twrp backup on this thread not any other and i wanted to warn people not to get into a situation like mine.
I' am in a very bad situation here

giraygokirmak said:
Dude, in order to restore your oeminfo twrp backup one has to be on TWRP recovery not Stock recovery.
Click to expand...
Click to collapse
This is why I recommend stock recovery and TWRP in erecovery. Now you have one way - DC Phoenix

Anderusk said:
This is why I recommend stock recovery and TWRP in erecovery. Now you have one way - DC Phoenix
Click to expand...
Click to collapse
Please remove your oeminfo twrp backup before anybody else gets hurt. right now you have 2 dead bodies... @Axan just wrote that his phone become bricked just like the same way as mine. Yea i know we had the responsibility but there's something wrong with the file you provided...

giraygokirmak said:
Please remove your oeminfo twrp backup before anybody else gets hurt. right now you have 2 dead bodies... @Axan just wrote that his phone become bricked just like the same way as mine. Yea i know we had the responsibility but there's something wrong with the file you provided...
Click to expand...
Click to collapse
Victims reached 3 unfortunately, a guy with the nickname @lazy_prodigy also bricked his phone with the file you shared that oeminfo backup. His serial number became just like mine

Test attached oeminfo from eu version, you can replace file in twrp by path /dev/block/platform/soc/7824900.sdhci/by-name, it's not twrp flash archive.

Thanks, is this OEMINFO C432 dual sim or single sim?
Great that finally someone shared it!

trol_sg said:
Thanks, is this OEMINFO C432 dual sim or single sim?
Great that finally someone shared it!
Click to expand...
Click to collapse
Dual SIM can-l11

Temanyan said:
Test attached oeminfo from eu version, you can replace file in twrp by path /dev/block/platform/soc/7824900.sdhci/by-name, it's not twrp flash archive.
Click to expand...
Click to collapse
Thanks For Sharing Sir
Sir Need Help To Read oeminfo Partition
Adb Commands Or Any Tool ?
I Have Rooted CAN-L12
Want To Read/Backup oeminfo
But Not From TWRP
Will Be Grateful To You
Thanks Anticipation

Need help raising it from the graveyard

Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?

Mairtrus said:
Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?
Click to expand...
Click to collapse
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers

Dadditz said:
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers
Click to expand...
Click to collapse
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...

Mairtrus said:
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...
Click to expand...
Click to collapse
Yep, factory reset + wipe cache did the work..
Cheers