Related
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
I have the same problem but with a different firmware.. now only thing i can do is use dc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
MobileTechArena said:
I have the same problem but with a different firmware. now only thing i can do is usedc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
Click to expand...
Click to collapse
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
barnabaXXX said:
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
Click to expand...
Click to collapse
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Thanks for making it clear. Please tell me if it worked or not. Thanks.
barnabaXXX said:
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
Click to expand...
Click to collapse
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
barnabaXXX said:
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
Click to expand...
Click to collapse
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
barnabaXXX said:
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
Click to expand...
Click to collapse
Unfortunately I can't help you further than what I already posted.
But keep updating in case someone more knowledgeable peeks in.
similar problem....I was fairly good but play store was stuck in pending download....
I did a wipe in TWRP, and ended with a black screen...
I can boot to eRecovery, but it fails.and also to TWRP.
when attached to PC it keeps being seen and unseen as if its stuck in a power on cycle
Any help would be greatly appreciated.
Already Tested
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Hello did you already test ???
Here is the solution for every PRA-LX1: [http : // www . htcmania . com / showthread . php ? t=1326478] (sorry for the spaces, but I don't have enough posts written to post external links )
Unfortunately, it's from a spanish forum. I didn't found any problem to follow this tutorial, but maybe for someone it could be a little difficult.
Anyway, it works!
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Where did you find the C432 firmware? I can't succees to find it
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Iocere said:
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Click to expand...
Click to collapse
Yeah, that's the way! It worked for me too!
juanmemo said:
Yeah, that's the way! It worked for me too!
Click to expand...
Click to collapse
Also i noticed everytime a OTA fails you get the full version offered on next boot. So you should get a full B164 aswell after it failed
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
how can you boot into recovery ? i can only boot into twrp or fastboot & rescue or if i plug the huawei to the pc erecovery ???
---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------
i have an huawei pra-lx1 c530 it used to boot into pra-lx1c530b111 rooted and twrp but now it doens't boot anymore, i'd like to flash to c530b160 but i can't find the firmware images
tiagoggama said:
Hello did you already test ???
Click to expand...
Click to collapse
Thanks men
I CONFIRM IT WORK PERFECTLY
For the second part go to this link for more detail :
https://boycracked.com/2016/03/14/h...-unbrick-firmware-any-huawei-android-devices/
Hi!
I see the large number of requests concerning the roolback of a custom rom to a official and untouched EMUI 4, i decide to create this thread.
After follow that methode, you able to rest on official EMUI and get the new update automatically on OTA (directly on your phone) OR try to install custom rom with a clear and good base version.
1. You ave access on TWRP?
-If not, pleas unlock your bootloader (again) and flash TWRP recovery for you actual version (marshmallow or nougat).
-perform a full wipe and restore your partitions on "ext4" format, shutdown phone.
2. Get a "oem_info.zip" for your model phone (dont extract the .zip) and push it on your internal or external sd.
-This archive contain cust and oem info for patched your phone at the correct manufacture information.
-I have a link for VNS-L31 (c432, but is not very important) HERE LINK
-If you have other model (VNS-L31) pleas find a correct patch for you (VNS-L21, ...).
3. Find and download a EMUI marshmallow official full-ota update.
-for a VNS-L31 i advice choice a VNS-L31C432B160 full-ota update.
4. Unpack your update archive.
5. Create "dload" folder on your internal or external sd and put it UPDATE.APP
6. Reboot phone on TWRP recovery and flash "oem_info.zip"
7. Use dload methode for update (hold 3 buttons phone and dont release before "dload screen" appears)
8. Unlock your bootloader again (important!) And make a factory reset
9. Your phone reboot (please wait ) and done!
Ok now you are on official version, please update on setting menu >> update and choice, rest on official or flash a custom rom..
P9 lite brick precision:
In my personal experience the "p9 lite" is very easy to flash, mod or other tips and the risk of HARD brick is very very tiny.
If you see this page and your phone bootloop, relax, keep calm at 99,999% you have a little and ridiculous brick
Good luck and flash happy!
hi! i'm on 381, on my phone i have root, twrp and elite kernel...this guide is good for me???why after dload method i have to re-unlock my bootloader??
thank you and sorry for my english XD
macao1989 said:
hi! i'm on 381, on my phone i have root, twrp and elite kernel...this guide is good for me???why after dload method i have to re-unlock my bootloader??
thank you and sorry for my english XD
Click to expand...
Click to collapse
Yes, is good for you.
Not necessary to re-unlock bootloader.
Therand said:
Hi!
I see the large number of requests concerning the roolback of a custom rom to a official and untouched EMUI 4, i decide to create this thread.
After follow that methode, you able to rest on official EMUI and get the new update automatically on OTA (directly on your phone) OR try to install custom rom with a clear and good base version.
1. You ave access on TWRP?
-If not, pleas unlock your bootloader (again) and flash TWRP recovery for you actual version (marshmallow or nougat).
-perform a full wipe and restore your partitions on "ext4" format, shutdown phone.
2. Get a "oem_info.zip" for your model phone (dont extract the .zip) and push it on your internal or external sd.
-This archive contain cust and oem info for patched your phone at the correct manufacture information.
-I have a link for VNS-L31 (c432, but is not very important) HERE LINK
-If you have other model (VNS-L31) pleas find a correct patch for you (VNS-L21, ...).
3. Find and download a EMUI marshmallow official full-ota update.
-for a VNS-L31 i advice choice a VNS-L31C432B160 full-ota update.
4. Unpack your update archive.
5. Create "dload" folder on your internal or external sd and put it UPDATE.APP
6. Reboot phone on TWRP recovery and flash "oem_info.zip"
Click to expand...
Click to collapse
I can do everything up to point 6... won't enter to twrp... stays on Your device is now booting...
Update: I can now reach point 7 but now won't do dload (3 buttons) method... Huawei logo all the time. Can't even turn off the phone
In my other thread you post the same problem but is not entirely the same..
You succeeded to enter on fastboot mode? Flash recovery?
If you follow the steps 1-5 is impossible to fail the 6 point..
You have acces on fastboot mode or not?..
Therand said:
In my other thread you post the same problem but is not entirely the same..
You succeeded to enter on fastboot mode? Flash recovery?
If you follow the steps 1-5 is impossible to fail the 6 point..
You have acces on fastboot mode or not?..
Click to expand...
Click to collapse
I did update the post... 3 hours ago I wasn't able to enter TWRP, some way I did managed, now I can enter fastboot, I did flash custOEM (sorry I don't remember exactly the name but it's the one of your post) .zip file. Now I can't do dload method, stuck on huawei logo. If I try to go to recovery, I got red message "phone fail validation"...
I know, I post on both but I was trying to do everything...
just tried... validation red error message won't let me go to TWRP now...
You have a VNS-L31C432?
Your phone does not enter at dload mode?
Wipe all partitions an retry flash a oeminfo for your model phone (if not C432 you need right oeminfo).
Therand said:
You have a VNS-L31C432?
Your phone does not enter at dload mode?
Wipe all partitions an retry flash a oeminfo for your model phone (if not C432 you need right oeminfo).
Click to expand...
Click to collapse
How can I wipe all partitions if stuck in Huawei logo? Is there a way to do everything from adb command line? (I'm using Mac and cannot use all the tools I've found here XDA neither hiSuite which is basically a backup photo/video only the Mac version).
Thank for helping, really appreciate
To answer your question in the other thread, yes bootloader is unlocked and I am on C432.
What's your rom have before the bootloop?
You have the right version of TWRP for your rom?
If you have a MM version Don't flash a TWRP for N.
Send me a link to TWRP version used (thread forum)
Therand said:
What's your rom have before the bootloop?
You have the right version of TWRP for your rom?
If you have a MM version Don't flash a TWRP for N.
Send me a link to TWRP version used (thread forum)
Click to expand...
Click to collapse
Before the bootloop I was on L31C900 (on the phone) but I did actually flashed C432B160 because I did rollback. TWRP used I've found in the other post where there's a OEMfile to flash (but for this I need to double check because I did look so many pages which I am not 100% sure.
I not have experience on other model that C435.
But i suggest to find a oeminfo for your variant (C900?)
For TWRP you need flash a version for MarshMallow HERE
Flash it and pas return here (fastboot flash return and first enter to new recovery)
Hi, found Windows emulator for MacOs so I extract from update.app boot.img and flash.
I did format all partitions as told using a proper twrp this time.
What's next step, system says NO OS INSTALLED?
islandman75 said:
Hi, found Windows emulator for MacOs so I extract from update.app boot.img and flash.
I did format all partitions as told using a proper twrp this time.
What's next step, system says NO OS INSTALLED?
Click to expand...
Click to collapse
Flash partitions on .img files is not needed.
Just find a corect oeminfo for your model phone.
Flash it on TWRP recovery.
Use dload methode to update on basical version (MarshMallow b160).
After that, unlock bootloader again and make a factory reset.
Switch on your phone (the first boot make long time).
Update on last emui on OTA.
Done!
After that you able to install a custom rom.
Therand said:
Flash partitions on .img files is not needed.
Just find a corect oeminfo for your model phone.
Flash it on TWRP recovery.
Use dload methode to update on basical version (MarshMallow b160).
After that, unlock bootloader again and make a factory reset.
Switch on your phone (the first boot make long time).
Update on last emui on OTA.
Done!
After that you able to install a custom rom.
Click to expand...
Click to collapse
Done!
Thanks again you're saving my life!
IT won't turn off so been always on it won't keep the charge... Writing so because apparently it won't go to download mode (dload) if plugged in. On the other way if I unplugged from power it won't even start. Shall I force to download mode using console ADB or FASTBOOT? I had looked but can't find anything...
islandman75 said:
Done!
Thanks again you're saving my life!
IT won't turn off so been always on it won't keep the charge... Writing so because apparently it won't go to download mode (dload) if plugged in. On the other way if I unplugged from power it won't even start. Shall I force to download mode using console ADB or FASTBOOT? I had looked but can't find anything...
Click to expand...
Click to collapse
I not understand.
You not able to switch on your phone without connected charger?
Therand said:
I not understand.
You not able to switch on your phone without connected charger?
Click to expand...
Click to collapse
Correct. Because I'm not able to switch it off it won't keep the charge. When discharged, the minute I do plug on charge it wakes up... That's the loop...
My main question is: does a command exist to enter download mode using terminal?
islandman75 said:
Correct. Because I'm not able to switch it off it won't keep the charge. When discharged, the minute I do plug on charge it wakes up... That's the loop...
My main question is: does a command exist to enter download mode using terminal?
Click to expand...
Click to collapse
You have a hardware bug?
No abd command to enter dload mode..
Try flash a update.zip with twrp (not guaranted)
After that unlock bootloader again and make factory reset.
Therand said:
You have a hardware bug?
No abd command to enter dload mode..
Try flash a update.zip with twrp (not guaranted)
After that unlock bootloader again and make factory reset.
Click to expand...
Click to collapse
I'll try. Thank you
Hi, I followed this guide to go back to stock from elite rom. I flashed my oeminfo.img on twrp and then went to dload combination. Do I have to unlock the bootloader after the reboot? Thanks!
Hi,
I followed your guide and it works perfectly thanks!
Today, I had successfully updated my L09-C432 (rebranded to L29) to Oreo. I decide to keep going and try to root using the magisk method present in the guide section.
During that process, I had several error, so I decided to flash the ramdisk. I all went downhill from there, impossible to restore any of the images I had on TWRP. Eventually I tried following HWOTA but for some reason. TWRP for oreo is not recognize by ADB on my system, I then decided to launch the upgradeoreo.zip according to this method as I had the files on my SD-card prior. Which led me to be unable to get into fastboot.
I am now left with the following error>
ERROR MODE:
Attention!
Please update system again
green android of death
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
All I have left at this point is a functional fastboot,
I have tried:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash ramdisk ramdisk.img
All of which complete successfully but none of them help me get forward. I am left with the same error.
All of which were extracted from the UPDATE.APP of the OREO update I had successfully completed on my phone.
Concerning TWRP:
fastboot flash recovery twrp.img (nougat version) fails.
fastboot flash recovery twrp.img (oreo version) succeeds but I am left with the same error.
fastboot flash recovery twrp.img (HWOTA8 version) succeds but left with the same error.
I have wandered the forums and tried a diversity of suggestion none of them seemed to work in my case.
What are your suggestion to fix this problem?
Any help you can provide is much appreciated.
I can probably find a way to pop my SD_Card into my laptop if necessary.
Same problem here, I have tried multi_tool 8 without any success. Maybe someone you can share a TWRP backup?
I was wondering if the dload method could be an option? Which firmware to use in that case?
There is Huawei official service ROM for P10 Lite and P10 Plus. Cannot find for P10.
Do you think the Funky Huawei unbrick tool would resolve this (($$$, but cheaper than a non-warranty repair...)
If so would I just use the circa 4 GByte update.app file from the update.zip firmware file, rather than the smaller update.app from update_all_hw.zip?
grockstar said:
Do you think the Funky Huawei unbrick tool would resolve this (($$$, but cheaper than a non-warranty repair...)
If so would I just use the circa 4 GByte update.app file from the update.zip firmware file, rather than the smaller update.app from update_all_hw.zip?
Click to expand...
Click to collapse
I tried the dload method that is a no go. Besides the other option DC-phoenix (which is a pay mehtod as well ) I feel like these are our last resort.
grockstar said:
Do you think the Funky Huawei unbrick tool would resolve this (($$$, but cheaper than a non-warranty repair...)
If so would I just use the circa 4 GByte update.app file from the update.zip firmware file, rather than the smaller update.app from update_all_hw.zip?
Click to expand...
Click to collapse
And yes you should use the 4.3GByte update.app file. Are you trying the tool? If so, let us know how it works out! It is the next step for me.
martindoublem said:
And yes you should use the 4.3GByte update.app file. Are you trying the tool? If so, let us know how it works out! It is the next step for me.
Click to expand...
Click to collapse
Well, I coughed up the cash to FunkyHuwawei and have made some progress....
After using their unbrick tool, I now have access to eRecovery, and am pondering the best way to fully flash the ROM.
The Funky Huawei eRecovery method doesn't seem to work (I did change my router's DNS as instructed), and I'm hesitant to try the manual update method again given the issues people seem to be having with it.
Any suggestions?
grockstar said:
Well, I coughed up the cash to FunkyHuwawei and have made some progress....
After using their unbrick tool, I now have access to eRecovery, and am pondering the best way to fully flash the ROM.
The Funky Huawei eRecovery method doesn't seem to work (I did change my router's DNS as instructed), and I'm hesitant to try the manual update method again given the issues people seem to be having with it.
Any suggestions?
Click to expand...
Click to collapse
Well I guess I am going to fork up the cash too. ($100 in one day for him, not bad eh?)
Can you restore TWRP? maybe you can follow the HWOTA method without the first couple of steps? Also, can you not recover using the dload method then or just download the software from the recovery?
Well I can confirm, the fix worked splendidly, it got me in erecovery where I was able to delete the userdata (unfortunate but perhaps necessary).
Then a couple of reboots and I am back in an Android. So happy!
martindoublem said:
Well I guess I am going to fork up the cash too. ($100 in one day for him, not bad eh?)
Can you restore TWRP? maybe you can follow the HWOTA method without the first couple of steps? Also, can you not recover using the dload method then or just download the software from the recovery?
Click to expand...
Click to collapse
So it looks like the unbrick tool actualy installed the full ROM correctly - I can't have been giving it enough time to boot.
However the first time it booted the DPI was screwy just as it was after I mistakenly flashed the P10+ Oreo ROM (maybe the data partition hadn't been wiped). But a quick factory reset and all's well, and I'm over the moon to have rescued my phone with a little (i.e. lot) of help from FunkyHuawei - and a bit of cash.
Now to decide whether I want/need to risk rooting again...
grockstar said:
So it looks like the unbrick tool actualy installed the full ROM correctly - I can't have been giving it enough time to boot.
However the first time it booted the DPI was screwy just as it was after I mistakenly flashed the P10+ Oreo ROM (maybe the data partition hadn't been wiped). But a quick factory reset and all's well, and I'm over the moon to have rescued my phone with a little (i.e. lot) of help from FunkyHuawei - and a bit of cash.
Now to decide whether I want/need to risk rooting again...
Click to expand...
Click to collapse
Rooting is where it all went to **** for me. I am staying the hell away from it until a lot of people confirm it works fine!
Are you having only limited functionality as well? It seems like we have to reinstall the update data file as well as the update hw file?
martindoublem said:
Are you having only limited functionality as well? It seems like we have to reinstall the update data file as well as the update hw file?
Click to expand...
Click to collapse
Limited in what respect? Mine seems fine so far - the radios work (cellular, WiFi, Bluetooth) and the system and the few apps I've tried so far are working as expected.
The notification toolbar is gone? Is that normal? Did i miss out on android removing them?
martindoublem said:
The notification toolbar is gone? Is that normal? Did i miss out on android removing them?
Click to expand...
Click to collapse
Nope, my notification toolbar is working.
A factory reset fixed some weirdness for me, but you said you'd wiped userdata in eRecovery which I guess has the same effect?
used the dc-phoenix tool with the one part Update and now my phone is back (= it is worth it 20 bucks because i have now 3 days for testig and rebuilding (=
martindoublem said:
Today, I had successfully updated my L09-C432 (rebranded to L29) to Oreo. I decide to keep going and try to root using the magisk method present in the guide section.
During that process, I had several error, so I decided to flash the ramdisk. I all went downhill from there, impossible to restore any of the images I had on TWRP. Eventually I tried following HWOTA but for some reason. TWRP for oreo is not recognize by ADB on my system, I then decided to launch the upgradeoreo.zip according to this method as I had the files on my SD-card prior. Which led me to be unable to get into fastboot.
I am now left with the following error>
ERROR MODE:
Attention!
Please update system again
green android of death
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
All I have left at this point is a functional fastboot,
I have tried:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash ramdisk ramdisk.img
All of which complete successfully but none of them help me get forward. I am left with the same error.
All of which were extracted from the UPDATE.APP of the OREO update I had successfully completed on my phone.
Concerning TWRP:
fastboot flash recovery twrp.img (nougat version) fails.
fastboot flash recovery twrp.img (oreo version) succeeds but I am left with the same error.
fastboot flash recovery twrp.img (HWOTA8 version) succeds but left with the same error.
I have wandered the forums and tried a diversity of suggestion none of them seemed to work in my case.
What are your suggestion to fix this problem?
Any help you can provide is much appreciated.
I can probably find a way to pop my SD_Card into my laptop if necessary.
Click to expand...
Click to collapse
Go to rescue mod, you plug in your device in computer, and hold vol down and pow button, than you go in rescue mod, and use fastboot to repair your device.
Can confirm DC-Phoenix and only for 20eur.
ure3808 said:
Go to rescue mod, you plug in your device in computer, and hold vol down and pow button, than you go in rescue mod, and use fastboot to repair your device.
Click to expand...
Click to collapse
Ha! you are funny! Several of us mentioned here that fastboot didn't work in our case to repair the device.
How many people bricked specifically hardbricked their phone after 2018-04-16 updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if they see we are bunch of people.
Edit: Just comment only if you solved the issue with this tool or any other tool that is not mentioned,here we are seeking help.
reza6d said:
How many people bricked specifically hardbricked their phone after 2018-04-16 noxloader updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if the ysee we are bunch of people.
Click to expand...
Click to collapse
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
ante0 said:
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
Click to expand...
Click to collapse
maybe i recall wrong but after first time seeing these noxloaders,somethings changed,anyway i edited the post.thanks.
My BLA-L29 is still on the black screen and I can not even revert to DC-Phoenix. After upgrading to 138.
Used funky
mikaole said:
Used funky
Click to expand...
Click to collapse
i think your phone was in fastboot or bootloop,we are talking about hardbrick bro,black screen not even charge led in our devices.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
durc12 said:
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
Click to expand...
Click to collapse
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Carnage! said:
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Click to expand...
Click to collapse
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
I see. I only tried flashing the recovery_ramdisk and system.img. I will try it later and I will let you know if it worked.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
durc12 said:
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
Click to expand...
Click to collapse
No, first he has to recover the current OS, and my advise was only for that.
Then he will need to use a TWRP + NoCheck combo, to get back to Oreo.
HuRUpdater can't get you back to Oreo so you guys should stop using that with Pie.
Mate 10 Pro BLA-L09
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
diowil4 said:
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
Click to expand...
Click to collapse
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Pretoriano80 said:
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Click to expand...
Click to collapse
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
diowil4 said:
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Click to expand...
Click to collapse
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Pretoriano80 said:
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Click to expand...
Click to collapse
After flashing It cannot boot to recovery.
diowil4 said:
After flashing It cannot boot to recovery.
Click to expand...
Click to collapse
So you can only boot to fastboot, no matter what?
Pretoriano80 said:
So you can only boot to fastboot, no matter what?
Click to expand...
Click to collapse
Yes.
Similar to the previous threads for OnePlus 5, OnePlus 5T or OnePlus 6, here are the necessary packages to unbrick/revive a hard bricked OnePlus 7 Pro.
The following hardware revisions are supported:
GM1910: China
GM1911: India
GM1913: Europe
GM1917: Global/US Unlocked
Download: https://www.androidfilehost.com/?w=files&flid=294744
guacamole_21_H.04_190416_unlocked.zip
After using it, the phone will be restored to HydrogenOS aka Chinese firmware.
Click to expand...
Click to collapse
guacamole_21_E.08_190515_unlocked.rar
After using it, the phone will be restored to OxygenOS 9.5.4.GM21BA aka European firmware.
Click to expand...
Click to collapse
guacamole_21_O.07_190512_unlocked.zip
After using it, the phone will be restored to OxygenOS 9.5.3.GM21AA aka global firmware.
Click to expand...
Click to collapse
In every case, it is possible to upgrade to latest OxygenOS by using full signed zip from this thread via Local Upgrade.
With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.
Use the most updated signed driver (2.1.2.2 at this moment) to avoid potential issues..
For detailed procedures, please consult the linked threads above. There is no reason to repeat the same thing again.
Make sure the path of the extracted files doesn't contain any non-English character. The tool isn't unicode aware.
Source:
HydrogenOS package: 人艱不拆 (OnePlus China forum thread), @trollavin & @Some_Random_Username for the help in mirroring
OxygenOS (EU) package: @MrVoshel
OxygenOS (global) package: @Lucifer6
Reserved for future.
Thank you for this!!
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
LLStarks said:
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
Click to expand...
Click to collapse
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
jkyoho said:
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
Click to expand...
Click to collapse
Well, that's the perfect explanation.
:highfive:
Can you turn TMobile to int'l with this ?
HtcOnekid said:
Can you turn TMobile to int'l with this ?
Click to expand...
Click to collapse
What he said
When i start MsmdownloadtoolV4.0.exe it says :
Packet image not exist!
Take out the Chinese characters in the file name and then try
joemossjr said:
Take out the Chinese characters in the file name and then try
Click to expand...
Click to collapse
Yep that's i though, but i finaly looking for EU version. Because i think with OTA upgrade to GMBA EU modem will not contain the good modem right ?
---------- Post added at 12:59 AM ---------- Previous post was at 12:27 AM ----------
failed to install on EU model : param preprocessing and stop at 5 ou 7 sec before flashing. I tryed using anothere patched tool and not working :s
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
what is your device OOS 9.5.3/4/5/6 ?
flash the co-responding stock boot.img from twrp with magisk zip together, and see if you can boot
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
thebigtross said:
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
Click to expand...
Click to collapse
Thanks for your replies! I was on OOS 9.5.5 and I tried flashing the twrp/magisk zips but that didn't work either. I also tried applying the stock boot.img to the active slot, but still got the recovery bootloop.
So as my last hope, I wiped all data in recovery mode, rebooted to fastboot and sideloaded the complete stock image from here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I reconfigured my phone from scratch, rooted with the patched boot image like before and everythings works now. Guess I will not bother with TWRP any time soon.
Added global and EU packages.
Titokhan said:
Added global and EU packages.
Click to expand...
Click to collapse
Will global work for 1911 (India)
Mr.Crucial said:
Will global work for 1911 (India)
Click to expand...
Click to collapse
Yes, the packages are interchangable.
[/COLOR]
Titokhan said:
Yes, the packages are interchangable.
Click to expand...
Click to collapse
But I think that these packages will not work on T-mobile 1915!
When I reboot into edl mode, it recognizes the "Qualcomm HS-USB QDLoader 9008", but then 10 seconds later, the phone automatically boots the the battery display, which disables edl. The same this happens whether I use the vol up+down and plug in, or `adb reboot edl`.
Edit: "How I learned to stop worrying and risk a brick"
Selecting the right COM and hitting start in MSMtool in that 10 second window kept it in edl mode for the duration of the flash.