Stuck on fRomFuture B201 - Help! - Huawei P10 Plus Questions & Answers

Hey guys! Been running fRomFuture build 201 on my VKY-L09 and haven't updated in like one year.
Right now the phone is on the june 2018 security patch and I cannot update. I would like to go back to stock.
I have tried like a dozen methods last night: HWOTA, HURUpdater, HiSuite, FunkyHuawei's unbrick tool etc. I think I am missing something here.
FH's unbrick tool does not go past the "wait 5 minutes" step, it just hangs.
The HWOTA... Well I changed the script a bunch of times for it to work properly but it seems that it flashes TWRP, then boots to it and waits for ADB and hangs. If I interfere with ADB and kill-server and start-server, the daemon cannot start any more. I tried like 3 separate twrp versions because of that and think it might actually be my adb to blame.
Saw a bunch of guys explaining how to do the dload method, but didn't manage to actually try it out.
The secret menu code method just does not see the UPDATE.APP file.
I am lost and desperate.
Can anyone please let me know what I am missing? Am I using the right build? Or is there a specific build I should be flashing to replace this old rom I am stuck on? FirmwareFinder said that most of the ones I tried were approved for install. For instance B185
P.s. the DNS method fails because my router is PPPoE and has the upstream WAN settings all greyed out. The FH Connectify method is utter crap and won't work. Traffic gets routet to a dead end if I change any dns settings.
Also HiSuite says that it can't fix my phonr lmao.
Phone can boot in fromfuture, I can install twrp on it, I just dunno how to get back to stock.

Solved with HWOTA.

Related

Audio drivers went missing during update

I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.

Recovery bricked after Nougat update?

First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I canĀ“t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.
nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.
kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.
Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.

HUAWEI P9 LITE VNS-l31 is it possible to go from b414 to b416 with firmware finder?

Hi All,
I'm trying to update the p9 lite VNS-L31C432B414 dual sim to the latest version B416.
The phone is always officially updated, but i tryed all 3 versions from firmware finder, with the *#*# 2846579#*# *
Select Project Menu > Software upgrade > SDcard upgrade method.
But when the phone restarts it begin to update and after a little progress it failed.
The same thing happens when i try it with the firmware finder app from playstore with erecovery, or dns method.
Any help would be appreciated, thanks!
Davidoff80
Davidoff80 said:
Hi All,
I'm trying to update the p9 lite VNS-L31C432B414 dual sim to the latest version B416.
The phone is always officially updated, but i tryed all 3 versions from firmware finder, with the *#*# 2846579#*# *
Select Project Menu > Software upgrade > SDcard upgrade method.
But when the phone restarts it begin to update and after a little progress it failed.
The same thing happens when i try it with the firmware finder app from playstore with erecovery, or dns method.
Any help would be appreciated, thanks!
Davidoff80
Click to expand...
Click to collapse
Firmware Finder
DNS/VPN method should be the best way to try this update.
The other only method that i know is to use Huawei Recovery Updater
but you should unlock the bootloader and flash a custom recovery first.
In the end it will be a bit difficult to re-lock the bootloader, never tried to do such a thing,
but you can keep it unlocked...
Good luck dude.
Cheers
Hi Dadditz,
Thank's for your response.
Last night i have tryed with a extra wifi router to change the dns number but even when the Firmware Finder app giving me the message that the B416 is registered for my phone, when booting in erecovery it installs the B414 FULL package again.
And with in the app proxy and dns method with firmware finder, the system update app from huawei gives me the sign that a update is ready to B416 with the release notes and all but when it starts it shows a checksum error or download fail.
I have registered the IMEI but do you know if it's maybe the problem with that its a dual sim so there a 2 IMEI numbers? or is the first one enough to register?
The tip for unlocking the bootloader i have searched on, but huawei has taking the unlock service down i understand, so the dc-unlocker2client program for 4 euro is the only option i think?
The main reason that i want to try the latest firmware is that people can't hear me good with this phone, i send the phone 2 times for repair and contacted the provider but the signal looks good.
Now i have factory reset the phone for the tenth time, i was thinking maybe the eset virusscanner interferes with the build in huawei/avast scanner but im not sure if that could cause it.
Thanks and have a nice day.
Hi all
I just unroot and unlock BL my phone yesterday. First i make downgrade (rollback 6.0) via dload method. Everything going very smooth and when my phone was version VNS-L31C432B160, then i'll get all newer updates via OTA (Finland), now my phone is B416
Davidoff80 said:
Hi Dadditz,
Thank's for your response.
Last night i have tryed with a extra wifi router to change the dns number but even when the Firmware Finder app giving me the message that the B416 is registered for my phone, when booting in erecovery it installs the B414 FULL package again.
And with in the app proxy and dns method with firmware finder, the system update app from huawei gives me the sign that a update is ready to B416 with the release notes and all but when it starts it shows a checksum error or download fail.
I have registered the IMEI but do you know if it's maybe the problem with that its a dual sim so there a 2 IMEI numbers? or is the first one enough to register?
The tip for unlocking the bootloader i have searched on, but huawei has taking the unlock service down i understand, so the dc-unlocker2client program for 4 euro is the only option i think?
The main reason that i want to try the latest firmware is that people can't hear me good with this phone, i send the phone 2 times for repair and contacted the provider but the signal looks good.
Now i have factory reset the phone for the tenth time, i was thinking maybe the eset virusscanner interferes with the build in huawei/avast scanner but im not sure if that could cause it.
Thanks and have a nice day.
Click to expand...
Click to collapse
Hey dude it's like you somehow downloaded B414 firmware and putted into
the internal memory or the SD card.
Check if you have that files and delete them, then try again with the update.
Don't know about your two IMEI, you have to check by yourself wich one would work...
About unlocking the bootloader, yes it is possible with the tip you wrote (dc-unlocker).
Before attempting to do anything try first with another sim and see if is the same as now
because if nothing changes maybe it's a hardware issue...
As suggested by @oltsuboy it's possible to downgrade to MM and re-upgrade
to N android version, you only need the correct packages..
I'm here to help you...
Have a good day..
Cheers
Hi guys,
I have tryed to downgrade to android 6, and that works, and then i get OTA to B370 and then B380 so i am android 7.0 again.
But now the OTA update find nothing, it stays on B380.
Before when i checked system update with HiSuite it says B414 is the latest official firmware, but now it says B380 is??
As far as i know i used only official updates with this phone, and i have wiped partion and system a lot of times.
And mostly there where 2 sim cards in it, i only put in SD card formatted first for the update.app
So i don't think B414 is floating somewhere, but i don't understand where it went wrong.
It's a non provider linked phone with a sim only abbo from the netherlands, i already asked a new sim card from the provider to test if the voice quality improves but it makes no difference.
I'm gonna wait a little maybe a update comes, when i put the B416 update on the sd card now and do force update VL+ VL- PW. the update fails after ten procent.
Maybe tommorow im gonna look to unlock the phone for 4 euro.
Thanks for the help!
Update: I have tried the DC Unlocker program.
And obtained the bootloader code, but what do do with it now?
Something says i did something wrong, because the options where:
Read unlock codes
Read bootloader code
Lock Bootloader
Erase Huawei ID
But no unlock bootloader, so i did read bootloader and copied the code.
Davidoff80 said:
Hi guys,
I have tryed to downgrade to android 6, and that works, and then i get OTA to B370 and then B380 so i am android 7.0 again.
But now the OTA update find nothing, it stays on B380.
Before when i checked system update with HiSuite it says B414 is the latest official firmware, but now it says B380 is??
As far as i know i used only official updates with this phone, and i have wiped partion and system a lot of times.
And mostly there where 2 sim cards in it, i only put in SD card formatted first for the update.app
So i don't think B414 is floating somewhere, but i don't understand where it went wrong.
It's a non provider linked phone with a sim only abbo from the netherlands, i already asked a new sim card from the provider to test if the voice quality improves but it makes no difference.
I'm gonna wait a little maybe a update comes, when i put the B416 update on the sd card now and do force update VL+ VL- PW. the update fails after ten procent.
Maybe tommorow im gonna look to unlock the phone for 4 euro.
Thanks for the help!
Update: I have tried the DC Unlocker program.
And obtained the bootloader code, but what do do with it now?
Something says i did something wrong, because the options where:
Read unlock codes
Read bootloader code
Lock Bootloader
Erase Huawei ID
But no unlock bootloader, so i did read bootloader and copied the code.
Click to expand...
Click to collapse
Hi dude,
DLOAD aka three button method won't anyway work on android 7 versions...
Sorry did you tried with your brother/sister/friend sim and seen if it's the same behaviour ? ( about the weird quality voice ).
Keep your unlocking code safe and before attempting any unlock re-try to update via Firmware Finder, checking this way...
Obviously turn on and connect with the WIFI...
After installing the app open it and add your variant (VNS-L31C432).
Find the firmware you're looking for (VNS-L31C432B416 FULLOTA-MF 2,2GB) and tap on it.
Now check the availability, register it with IMEI for the update and use the dns change / vpn method.
Once the vpn started, check repeatedly into the stock inbuild updater for a update and the B416 version should come. If will be disponible tap and download your update (should be approssimatively 2,2GB).
When it'll be at 5% pause it for a while and stop the vpn service.
Go back and re-active the download of the B416.
If all will go well you'll have the latest firmware.... :laugh:
Let me know how it went.
Cheers
Hi Dadditz,
No i don't have tryed another sim yet, the provider has said that if i give to more telephone numbers from the same provider they can do a scan for the quality.
So maybe that's something to try.
Later at night there came 3 more updates and the latest is now B414, so i am back on the same build
Yesterday i have unlocked the bootloader, with this guide: https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Yes sorry i couldn't wait so i think let's try
When i was at the TWRP part, when i must reboot to recovery mode it stays on the screen that the phone was not safe.
So that part i still want to proceed.
So i rebooted and go to sleep.
I just have tryed your tips, but i see the same behaviour, the download fails, the extra wifi router which i changed the dns to was not more in my network, so i tryed without it.
With my own wifi router at home, they don't allow the change of the DNS, can that be the problem? or if you put a extra wifi router to it it's no problem?
I attached some screenshots, do you see that the buildnumber is displayed 2 times after a row?
I maybe think that's because i tryed to register both the IMEI? so maybe that's a problem?
Sorry i don't know how to attach the screenshot's below.
So i put them in a album called B414 with my profile, i hope you can see them, sorry this is the first forum i post on.
Thanks a have a nice day :good:
Davidoff80 said:
Hi Dadditz,
No i don't have tryed another sim yet, the provider has said that if i give to more telephone numbers from the same provider they can do a scan for the quality.
So maybe that's something to try.
Later at night there came 3 more updates and the latest is now B414, so i am back on the same build
Yesterday i have unlocked the bootloader, with this guide: https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Yes sorry i couldn't wait so i think let's try
When i was at the TWRP part, when i must reboot to recovery mode it stays on the screen that the phone was not safe.
So that part i still want to proceed.
So i rebooted and go to sleep.
I just have tryed your tips, but i see the same behaviour, the download fails, the extra wifi router which i changed the dns to was not more in my network, so i tryed without it.
With my own wifi router at home, they don't allow the change of the DNS, can that be the problem? or if you put a extra wifi router to it it's no problem?
I attached some screenshots, do you see that the buildnumber is displayed 2 times after a row?
I maybe think that's because i tryed to register both the IMEI? so maybe that's a problem?
Sorry i don't know how to attach the screenshot's below.
So i put them in a album called B414 with my profile, i hope you can see them, sorry this is the first forum i post on.
Thanks a have a nice day :good:
Click to expand...
Click to collapse
Hey mate,
you're such as educated guy and i really apprecciate that !
Well... i saw inside your profile the B414 album and maybe i found the mistake...
damn ... seems you didn't read carefully what i wrote !!!
Look in previous post, you need the FULLOTA-MF package 2,2gb !!!
not the OTA-MF (incremental) one !!
Repeat again the procedure, register one only IMEI, hope this time
you'll be able to update correctly
Let me/other members know.. :fingers-crossed:
note: if the update will end correctly, it will re-lock the bootloader too.
Cheers
Hi Dadditz,
Thanks i didn't even finished my school so my english is not good, but i hope u understand.
I always tryed to install the full package mf B416 2.2gb but when i was testing it with the extra router it always shows a checksum error or download fail, tonight im gonna try that again, and let you know how it went and describe the steps that i tryed so maybe you can see where it goes wrong.
I also tryed the firmware finder windows version to register the IMEI, so maybe i make a mistake there.
This afternoon i was trying to attempt to proceed with the TWRP installation, but when i was booting with VL+ and power it won't go to recovery mode, on the xda forum i was reading more people with the same problem, the phone stays on booting
But the phone is working now so im glad i can whatsapp and watch netflix, so i will not try to go further with that, and focus on the B416 full update.
Thanks:good:
Davidoff80 said:
Hi Dadditz,
Thanks i didn't even finished my school so my english is not good, but i hope u understand.
I always tryed to install the full package mf B416 2.2gb but when i was testing it with the extra router it always shows a checksum error or download fail, tonight im gonna try that again, and let you know how it went and describe the steps that i tryed so maybe you can see where it goes wrong.
I also tryed the firmware finder windows version to register the IMEI, so maybe i make a mistake there.
Can you describe maybe how i can insert screenshots in a post?
When i try to insert a image in a post it is asking for a link, can i upload pictures at XDA or do i must use another image upload server?
This afternoon i was trying to attempt to proceed with the TWRP installation, but when i was booting with VL+ and power it won't go to recovery mode, on the xda forum i was reading more people with the same problem, the phone stays on booting
But the phone is working now so im glad i can whatsapp and watch netflix, so i will not try to go further with that, and focus on the B416 full update.
Thanks:good:
Click to expand...
Click to collapse
Dude,
sorry if i wrote something that someway hurted you,
english isn't my main language too...
Attachments aren't allowed to junior member, you need to post many times
in order to be authorized.
Let's go to the main problem...
If you want to try to flash the B416 version with the TWRP
you first need the correct TWRP version...
If you followed the link you posted above,
you tried to install the marshmallow version,
that's because it won't boot.
Your device are running android 7 ( nougat ) and you need a working recovery
in order to use Huawei Recovery Updater ( HuRu ) and flash that B416 firmware.
All files ( firmware apart ) you need are present on XDA, so just download and install
what i wrote you here.
Be sure you have installed Hisuite on your PC and it works.
Be sure you have enabled developer options then open it and
disable screen lock, enable oem-unlock and usb-debugging.
HERE to download and install Minimal ADB & Fastboot on your PC.
Connect the device to the PC, make sure PC recognize it allowing permissions if needed.
Then on the PC open a prompt (CMD) with admin rights and type "adb devices".
Below you should see your device as a serial of numbers and characters like
THIS screenshot. If that worked go next step.
Type "adb reboot bootloader" and it will reboot into fastboot/bootloader mode.
Now type "fastboot devices" and you should see your device as a serial of numbers and characters like
the screenshot i posted above except you'll see authorized/unauthorized section.
If your device are now authorized you're ready to go.
Type "fastboot reboot" and it will reboot into system.
HERE the link to download HassanMirza01's 3.1.1-1 EliteTWRP, flah it with fastboot command
( past a copy of TWRP into the adb & fastboot main folder )
( into fastboot mode ( see above ) type "fastboot fash recovery name_of_recovery_you_downloaded.img" )
When finished type "fastboot reboot recovery" or reboot with vol+ and power buttons.
Once you'll have a working TWRP installed reply me here
and i'll indicate the next steps.
note: with CMD prompt write without quotes " "
Cheers
Dadditz said:
Dude,
sorry if i wrote something that someway hurted you,
english isn't my main language too...
Attachments aren't allowed to junior member, you need to post many times
in order to be authorized.
Let's go to the main problem...
If you want to try to flash the B416 version with the TWRP
you first need the correct TWRP version...
If you followed the link you posted above,
you tried to install the marshmallow version,
that's because it won't boot.
Your device are running android 7 ( nougat ) and you need a working recovery
in order to use Huawei Recovery Updater ( HuRu ) and flash that B416 firmware.
All files ( firmware apart ) you need are present on XDA, so just download and install
what i wrote you here.
Be sure you have installed Hisuite on your PC and it works.
Be sure you have enabled developer options then open it and
disable screen lock, enable oem-unlock and usb-debugging.
HERE to download and install Minimal ADB & Fastboot on your PC.
Connect the device to the PC, make sure PC recognize it allowing permissions if needed.
Then on the PC open a prompt (CMD) with admin rights and type "adb devices".
Below you should see your device as a serial of numbers and characters like
THIS screenshot. If that worked go next step.
Type "adb reboot bootloader" and it will reboot into fastboot/bootloader mode.
Now type "fastboot devices" and you should see your device as a serial of numbers and characters like
the screenshot i posted above except you'll see authorized/unauthorized section.
If your device are now authorized you're ready to go.
Type "fastboot reboot" and it will reboot into system.
HERE the link to download HassanMirza01's 3.1.1-1 EliteTWRP, flah it with fastboot command
( past a copy of TWRP into the adb & fastboot main folder )
( into fastboot mode ( see above ) type "fastboot fash recovery name_of_recovery_you_downloaded.img" )
When finished type "fastboot reboot recovery" or reboot with vol+ and power buttons.
Once you'll have a working TWRP installed reply me here
and i'll indicate the next steps.
note: with CMD prompt write without quotes " "
Cheers
Click to expand...
Click to collapse
Hi Dadditz,
No problem mate , i'm new to this phone flashing and was insecure if my english was good enough to communicate on the xda forum.:good:
I was just to let you know that my second try with the second router is maybe succesful for the B416 FULL update part.
I now connected my pc to it and when i changed the DNS i changed the second DNS to 1.2.3.4 and when the firmware app says registered to this ip:......, i took that ip in the second router.
And then boot in to huawei Erecovery and now the B416 2gb is downloading, why the DNS and PROXY in the app only provide the 700mb update all the time even if i registred the 2gb version i don't know.
Maybe the DNS or ip setting had something to do with it, my understanding of network settings is limited.
The download is 42 procent after a hour but it's a old wifirouter.
So i was now about to ask if it's succeed i could undo the TWRP and lock the bootloader and just read your message, so i don't know if it hurt's anything if i let the update install
I wait and see :good:
edit: i did see you message that the update will relock the bootloader but i was asking because i was not sure because i messed up the TWRP part. edit
The update to B416 was succesfull! :good:
I haven't see the warning that the device isn't save when booting and Netflix appears in Google Play store again, so i guess i don't have do anything more to disable TWRP and locking the bootloader
Thanks for the help Dadditz and sorry that i was impatient to wait on your message, in the future i ask and wait patiently, but hey i didn't bricked the phone
If the voice quality improves i now must test, and the next step is to ask a network scan from the provider on 2 more telephone number in my town.
Thanks :good:
Davidoff80 said:
The update to B416 was succesfull! :good:
I haven't see the warning that the device isn't save when booting and Netflix appears in Google Play store again, so i guess i don't have do anything more to disable TWRP and locking the bootloader
Thanks for the help Dadditz and sorry that i was impatient to wait on your message, in the future i ask and wait patiently, but hey i didn't bricked the phone
If the voice quality improves i now must test, and the next step is to ask a network scan from the provider on 2 more telephone number in my town.
Thanks :good:
Click to expand...
Click to collapse
I suggested, you did. :good:
All is well that ends well.
If you had TWRP recovery installed,
you wouldn't be able to update with Firmware Finder,
as you would have needed stock recovery ...
And yes now the device is 100% stock.
Thanks for your feedback dude.
All the best

A series of unfortunate events. Stuck in eRecovery

I was going to update my P10+ (VKY-L29C626B124) to Oreo. It's unlocked and rooted, but the updater wasn't working normally.
Started with FirmwareFinder and found an early Oreo for my phone. I was going to set up the proxy download in eRecovery. In the meantime, I backed everything up and decided to pony up the 4 euros to get the unlock code again because I figure this was going to put me back in stock. After I got the code, I was going to copy my backup over to my sdcard, but there was a crash in DC Unlocker and my phone rebooted.
Now I am stuck with eRecovery trying to do something and failing all the time. I can get to fastboot, but not TWRP. I am 99.9% sure nothing was flashed (because nothing was downloaded to begin with) but it seems that eRecovery is engaged in a way that it can't be overridden.
Is there a way to get back to either TWRP or the OS so I can move my backups off the phone and try this again? I was going to flash a stock rom via the Huawei Updater on my PC and a proxy, but I am open to other suggestions. So uh... h---e---l---p ? ? ? ?
Okay I managed to push the updates through so now I am on B172. Just need to find the right build to start onto Oreo...

[LG-H872]LG G6 Bricked/Stuck in DL Mode

Hello XDA. I recently revived my G6 after it sat in my drawer for years and was delighted to see HavocOS on Oreo still running on it. I popped in my T-Mobile SIM and voila, service. My only issue was horrible data speeds. I tried every network settings and apn fix that is relevant to my device but I was still stuck with virtually no 4G data. So, my last resort was to flash back to stock. Now, I dont know if there is a specific method for this device as I forgot how complicated the root exploit was. But I went ahead and downloaded the latest stock .kdz (20g), LGUP and the drivers and proceeded as normal to flash the kdz over. I had SEVERAL issues getting my device model to be recognized and finally grabbed the right LGUP version that worked. I proceeded to flash the kdz when it gave me an error round 31%. I did much troubleshooting research and came up empty, finally decided to try flashing the stock version it was on (20a) to just restore it.
This worked. I thought I was saved until the phone froze on the T-Mobile logo while booting and didnt budge for an hour. Much more googling and I found a thread that looked promising and seemed to help. At first. It flashed the kdz, gave me the error, and when I tried to flash the dz, nothing. I retried LGUP with 20a stock, unknown model. I tried to go back through the whole rooting process again and stick it out with minimal service. The FWUL/lglaf portion of the guide is where I got stuck. My device would not be recognized in FWUL, I couldnt get wifi so plugged in my ethernet. And then I kept getting "USB configuration not set" and "input/output" errors, and I noticed that while booting FWUL, the step "Loading Kernel Modules" fails. So I assumed that FWUL was not loading any modules, including USB's (which explained the errors), so I booted up my own Manjaro install and cloned the same project there. Knowing all my modules work now, I still get the "Input/Output" error.
So now I'm led to believe this phone is hard-bricked. It registers as a port in Window's Device Manager, "LG AndroidUSB SerialNet" or something like that. I tried following the unknown model guide again to no avail. I'm at a loss. Whatever info is needed for debugging I'll provide. I'm dualbooting Win10 and Manjaro so any methods are viable.
Which specific stock KDZ(s) did you try to flash on your phone (full kdz name)? You need to seperate flashing and rooting as two separate tasks because from your post I can't tell if you are able to boot after flashing stock kdz or not. First, if your phone is not booting, you gotta recover from that and flash a stock kdz.
Also, try using the Dev patched LG UP from this post (thank the dev while you are there): https://forum.xda-developers.com/lg...ssflashing-t3780969/post76510671#post76510671
Try the 'Partition DL' option when you flash and select all partitions in the next window.
Once you are able to boot a stock rom, you can try using a VMWare such as virtual box, install/mount FWUL in a virtual environment and use that to root the phone. I think the process is somewhere here on the runningnak3d's guide or on another post, I will try find a link later.

Categories

Resources