I can no longer boot into EMUI on my Huawei Honor Note 8 - Huawei Honor Note 8 Questions & Answers

I unlocked the bootloader, installed TWRP. Everything was fine. I put SuperSU.zip into the phone, booted into TWRP, installed SuperSU.zip, and then selected wipe cahe/dalvik before exiting. Now I only get the erecovery. I then did a factory reset within TWRP and now I just get the Chines erecovery. Is there anything I can do?
Thank you
edit: I can see about 2GB of data in my system folder as well as others. It looks like the EMUI is there. My phone just doesn't know how to boot to it.
edit 2: I was able to sideload KangVIP but I'd rather have the stock ROM. Does anybody know where one is available?

Hello, as you have unlocked the bootloader? With the dc-unlock software?
Thanks

flint24 said:
I unlocked the bootloader, installed TWRP. Everything was fine. I put SuperSU.zip into the phone, booted into TWRP, installed SuperSU.zip, and then selected wipe cahe/dalvik before exiting. Now I only get the erecovery. I then did a factory reset within TWRP and now I just get the Chines erecovery. Is there anything I can do?
Thank you
edit: I can see about 2GB of data in my system folder as well as others. It looks like the EMUI is there. My phone just doesn't know how to boot to it.
edit 2: I was able to sideload KangVIP but I'd rather have the stock ROM. Does anybody know where one is available?
Click to expand...
Click to collapse
How did you install TWRP if you only see the erecovery?
My adb was working earlier today, but now, when I "adb reboot bootloader", it just says "error: device '(null)' not found"
EMUI isn't loading now.
That last thing I did was run "flash_all.bat" in "EDI-AL10-C233B027_6.0" from https://mega.nz/#!VRN2AICD!HqTY2ai1XAl-bOoCFW_YfBoyhOr6GhoiWXL68l7QNhg
The flashing was successfull but after it rebooted, I just encountered bootloops.

MarkAndroid said:
Hello, as you have unlocked the bootloader? With the dc-unlock software?
Thanks
Click to expand...
Click to collapse
Yes I unlocked the bootloader. I think when I went back into TWRP, ran the SuperSU.zip file and then wiped the cache/dalvik, that's what did it. Before I did that, after I unlocked my bootloader, I was able to reboot and boot back into EMUI no problem.

jetherson said:
How did you install TWRP if you only see the erecovery?
My adb was working earlier today, but now, when I "adb reboot bootloader", it just says "error: device '(null)' not found"
EMUI isn't loading now.
That last thing I did was run "flash_all.bat" in "EDI-AL10-C233B027_6.0" from https://mega.nz/#!VRN2AICD!HqTY2ai1XAl-bOoCFW_YfBoyhOr6GhoiWXL68l7QNhg
The flashing was successfull but after it rebooted, I just encountered bootloops.
Click to expand...
Click to collapse
So this is the stock Honor Note 8 image? I think I'll just do an adb sideload within TWRP with this badboy and be ok. I'm going to backup beforehand.

flint24 said:
Yes I unlocked the bootloader. I think when I went back into TWRP, ran the SuperSU.zip file and then wiped the cache/dalvik, that's what did it. Before I did that, after I unlocked my bootloader, I was able to reboot and boot back into EMUI no problem.
Click to expand...
Click to collapse
For unlocking the bootloader you followed the step by step instructions to the topic:
http://forum.xda-developers.com/general/general/huawei-honor-note-8-unlock-bootloader-t3488142
You're forced to buy the key (4 euro) on the site:
https://www.dc-unlocker.com/how-to-r...er-unlock-code
Thanks

flint24 said:
So this is the stock Honor Note 8 image? I think I'll just do an adb sideload within TWRP with this badboy and be ok. I'm going to backup beforehand.
Click to expand...
Click to collapse
No! That's NOT the stock note8 image.
That came from http://forum.xda-developers.com/showpost.php?p=70055340&postcount=658

MarkAndroid said:
For unlocking the bootloader you followed the step by step instructions to the topic:
http://forum.xda-developers.com/general/general/huawei-honor-note-8-unlock-bootloader-t3488142
You're forced to buy the key (4 euro) on the site:
https://www.dc-unlocker.com/how-to-r...er-unlock-code
Thanks
Click to expand...
Click to collapse
Yes. I actually bought 7 credits but yes I did that. My backup failed and I continued anyway.

jetherson said:
No! That's NOT the stock note8 image.
That came from http://forum.xda-developers.com/showpost.php?p=70055340&postcount=658
Click to expand...
Click to collapse
Ok got it. But is it safe to use on my HN8 anyway? This KangVIP rom sucks so bad.

flint24 said:
Ok got it. But is it safe to use on my HN8 anyway? This KangVIP rom sucks so bad.
Click to expand...
Click to collapse
The B017 stock honor note 8 is EDI-AL10C233B017CUSTC233D002_Firmware_China_Chann.zip
Try searching for that file.
BTW, I solved my problem awhile ago. I actually used that file. I had to extract the UPDATE.APP from it.
This phone is very difficult to brick.

jetherson said:
The B017 stock honor note 8 is EDI-AL10C233B017CUSTC233D002_Firmware_China_Chann.zip
Try searching for that file.
BTW, I solved my problem awhile ago. I actually used that file. I had to extract the UPDATE.APP from it.
This phone is very difficult to brick.
Click to expand...
Click to collapse
What about the B022 stock honor note 8 firmware? I believe that's the exact one that came with my phone.
Thank you very much for the help!

Nevermind. Everything is fine now. I loaded the firmware you have in your post saving the data on my sdcard. Everything works beautifully. Thank you very much. Consider this case closed.
Sent from my EDI-AL10 using Tapatalk

Related

Bootloop Help After Trying To Root 7.1.1

So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.

How to fix DM-VERITY issue for 7.0 flashed updates

Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.

Axon 7 root help!!!

I tried to root my Axon 7 using the "Axon7toolkit" method and everyting looked like it was going well, installed twrp and unlocked bootloader with fastboot but now it get stuck at the splash screen where it says wait 5sec but it never moves from that screen. when I go into twrp I cannot install anything i get failed error 7 everytime. this is about the 3rd phone i have rooted and i don't know what to do from here... any help would be appreciated, I have the a2017u model which was running the lastest nougat
Which rom are you trying to flash?
JKSurf said:
Which rom are you trying to flash?
Click to expand...
Click to collapse
lineage os 14
i figured it out, thanks for help
jjallday said:
i figured it out, thanks for help
Click to expand...
Click to collapse
Old TWRP, right?
Probably wrong bootstack
Choose an username... said:
Old TWRP, right?
Click to expand...
Click to collapse
idk how the problem occured I followed the root instructions perfectly . I had the latest twrp out so couldn't have been that. os was missing and nothing i tried could get it back installed, so following more instructions led me to downgrade the twrp and install b29 stock then i just did the whole root process over following the same instructions that sent the phone into a loop but this time everything worked correctly. i updated twrp and installed super su and now i have full root. axon7toolkit provided majority of the tools needed.

Missing emoji when returning to stock

I recently flashed my 6T to stock from EvolutionX and locked the bootloader, and somehow in the process, it seems my keyboard isn't able to display or type any emojis. The steps I followed are:
HTML:
1. fastboot reboot bootloader
2. fastboot boot twrp
3. flash latest OOS
4. reboot bootloader
5. fastboot boot twrp
6. flash OOS
7. boot system
8. reboot bootloader
9. fastboot oem lock
10. boot system and setup (sign in to google, etc)
Is there any step that I missed, or any way to recover this without rooting/unlocking again?
Neontc said:
I recently flashed my 6T to stock from EvolutionX and locked the bootloader, and somehow in the process, it seems my keyboard isn't able to display or type any emojis. The steps I followed are:
1. fastboot reboot bootloader2. fastboot boot twrp3. flash latest OOS4. reboot bootloader5. fastboot boot twrp6. flash OOS7. boot system8. reboot bootloader9. fastboot oem lock10. boot system and setup (sign in to google, etc)
Is there any step that I missed, or any way to recover this without rooting/unlocking again?
Click to expand...
Click to collapse
Reflash your ROM through stock recovery ..
You're missing the reserve partition cause you've flashed through twrp..
If you still dont have emoji
root your phone and flash this module
https://androidfilehost.com/?fid=1899786940962618515
That would be this link here, correct?
https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156215016
Neontc said:
That would be this link here, correct?
https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156215016
Click to expand...
Click to collapse
Yes
cultofluna said:
Yes
Click to expand...
Click to collapse
Maybe I'm missing something? The only options I see when I'm recovery are reboot and wipe data/cache
Neontc said:
Maybe I'm missing something? The only options I see when I'm recovery are reboot and wipe data/cache
Click to expand...
Click to collapse
Yes you're missing the essential you evidently need TWRP to do that...
Neontc said:
Maybe I'm missing something? The only options I see when I'm recovery are reboot and wipe data/cache
Click to expand...
Click to collapse
Local upgrade
You could also just run msmdownloadtool, it will reset the device to full stock. There is a version for 10.3.0, just run it and upgrade.
Striatum_bdr said:
Yes you're missing the essential you evidently need TWRP to do that...
Click to expand...
Click to collapse
I thought I had to use stock recovery to flash this. Can I just fastboot boot twrp and flash it from there?
cultofluna said:
Local upgrade
Click to expand...
Click to collapse
From the settings menu in the os right? I tried that and it kept asking me to move the upgrade file to the root of the internal storage, like it didn't see it or something
efex said:
You could also just run msmdownloadtool, it will reset the device to full stock. There is a version for 10.3.0, just run it and upgrade.
Click to expand...
Click to collapse
This is a T-Mobile device that has been converted to international fw. Would I use the international 10.3.0 msm file?
Neontc said:
I thought I had to use stock recovery to flash this. Can I just fastboot boot twrp and flash it from there?
From the settings menu in the os right? I tried that and it kept asking me to move the upgrade file to the root of the internal storage, like it didn't see it or something
This is a T-Mobile device that has been converted to international fw. Would I use the international 10.3.0 msm file?
Click to expand...
Click to collapse
Nope, Tmob MSM, international one won't run anyway in your case.
Neontc said:
I thought I had to use stock recovery to flash this. Can I just fastboot boot twrp and flash it from there?
From the settings menu in the os right? I tried that and it kept asking me to move the upgrade file to the root of the internal storage, like it didn't see it or something
This is a T-Mobile device that has been converted to international fw. Would I use the international 10.3.0 msm file?
Click to expand...
Click to collapse
Yes just move it to the root of the internal storage..
And install it..
You will have the reserve partition back..( and working emojis)
efex said:
You could also just run msmdownloadtool, it will reset the device to full stock. There is a version for 10.3.0, just run it and upgrade.
Click to expand...
Click to collapse
Msm 10.3.0 ?? Link please
cultofluna said:
Local upgrade
Click to expand...
Click to collapse
No luck using the latest official fw from OnePlus website. Is there anything else left to try?
Neontc said:
No luck using the latest official fw from OnePlus website. Is there anything else left to try?
Click to expand...
Click to collapse
You've flash it but still no emojis?
cultofluna said:
You've flash it but still no emojis?
Click to expand...
Click to collapse
Correct. Flashed using local upgrade from inside the os and still didn't fix it.
Edit: after uninstalling updates for Gboard they returned. Thanks everyone for all the replies!
clubhouse00 said:
Msm 10.3.0 ?? Link please
Click to expand...
Click to collapse
I found it here on xda, but seem unable to do so now.. I have the files on my work PC, I could upload it tomorrow if you want it. It's for the international OP6T
Edit: Uploading now, will provide link when finished
Edit2: Mega link

Looking for EMUI 5 (VNS-L21)

Hello, i’m looking for the update file for my phone. I’m currently on EMUI 4.1, to which i foolishly downgraded to last weekend. I would like to update with the SD Card and dload folder method, but i can’t find the stock EMUI 5 rom anywhere.
Marko787 said:
Hello, i’m looking for the update file for my phone. I’m currently on EMUI 4.1, to which i foolishly downgraded to last weekend. I would like to update with the SD Card and dload folder method, but i can’t find the stock EMUI 5 rom anywhere.
Click to expand...
Click to collapse
hi try this, maybe it will work for you
P9 lite VNS-L31 flash file, try it maybe it will work for you
ebholoria said:
P9 lite VNS-L31 flash file, try it maybe it will work for you
Click to expand...
Click to collapse
Installing vns-l31 firmware on vns-l21 will cause soft brick, with model "generic a-15".
Marko787 said:
i’m looking for the update file
Click to expand...
Click to collapse
What is your build number? (full).
Hi try to check her, you will find yours but note that I'm not trying to brick your phone.
5261979
forum.xda-developers.com
click on find all thread and try than scroll to it, you will find yours, https://forum.xda-developers.com/m/5261979.8631980/
-Alf- said:
What is your build number? (full).
Click to expand...
Click to collapse
my build number is VNS-L21C432B160
Marko787 said:
my build number is VNS-L21C432B160
Click to expand...
Click to collapse
Okay, download B370 (two files) and follow instructions , use method 3 for locked bootloader (or method 1 for unlocked BL & TWRP)
Here you go
-Alf- said:
Okay, download B370 (two files) and follow instructions , use method 3 for locked bootloader (or method 1 for unlocked BL & TWRP)
Here you go
Click to expand...
Click to collapse
Thanks, i tried method 3 first but it failed (i have an unlocked bootloader though), so then i tried method 1 (i had twrp from meticulus already installed) first went to install only the update.zip in twrp, it failed, but when i rebooted, the phone is now updated to emui 5. Also my build number is now the test keys nonsense, but that happened to me before and i know how to fix that.
Thanks, your guide worked.
Marko787 said:
test keys
Click to expand...
Click to collapse
I'm in the exact same soup, please help...
Rumburak1 said:
I'm in the exact same soup, please help...
Click to expand...
Click to collapse
I installed an update.zip from a video about downgrading to Emui 4.1 with the hold down all buttons method, and the test keys thing disappeared, but it wiped my whole phone and installled a version of Emui from a different country I think because everything was just different.
Rumburak1 said:
I'm in the exact same soup, please help...
Click to expand...
Click to collapse
Install TWRP for Nougat, e.g. this one:
3.1.0.2
Install it over eRecovery with command
fastboot flash recovery2 xxxxxxx.img
Copy to the SD card the second file - hw_eu.zip from B370.
Boot into TWRP, click WIPE, then FORMAT DATA , after REBOOT SYSTEM.
The smartphone will start rebooting: as soon as the technical menu appears on the screen (yellow warning) press and hold Volume Up up to 3 sec, and here you are in TWRP again.
Click INSTALL and flash update_data_full_VNS-L21_hw_eu.zip.
Reboot into stock Recovery and do factory reset.
-Alf- said:
Install TWRP for Nougat, e.g. this one:
3.1.0.2
Install it over eRecovery with command
fastboot flash recovery2 xxxxxxx.img
Copy to the SD card the second file - hw_eu.zip from B370.
Boot into TWRP, click WIPE, then FORMAT DATA , after REBOOT SYSTEM.
The smartphone will start rebooting: as soon as the technical menu appears on the screen (yellow warning) press and hold Volume Up up to 3 sec, and here you are in TWRP again.
Click INSTALL and flash update_data_full_VNS-L21_hw_eu.zip.
Reboot into stock Recovery and do factory reset.
Click to expand...
Click to collapse
Does that mean I'm missing the second (smaller) file? Okay, I'll try it. Thank you!
Rumburak1 said:
Does that mean I'm missing the second (smaller) file? Okay, I'll try it. Thank you!
Click to expand...
Click to collapse
Yes, yes, yes! Thanks a lot, -Alf- !

Categories

Resources