Hey there people!
I just registered thus this is my first post here. I read quite a lot in preparation for this fallowing objective of mine and im still really overwhelmed.
Judging from the amount of super useful guides and comments on this forum I figured I could need a little of that xda community power to help me get this done .
In the past I had a few encounters with flashing custom roms on the Galaxy S5 and Oneplus One, however I found doing this with the Axon 7 is way more complicated and I dont know where to begin.
My Problem:
Ever since I switched to oreo I had situations where my device just became completely unresponsive and only the volume keys and the standby button worked however the device could't be turned off except via adb using my pc.
I figured there may be a connection to the current kernel or ROM coming with the b03 oreo update on my A2017G.
As I dont want to buy another phone and keep my Axon 7 as long as possible, I figured it would be best to try flashing LOS on it, as I used it myself and flashed it on every of my family members Galaxy S5's.
I ended up choosing this guide https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
but realised I got a little overwhelmed by it.
I installed and prepared the Axon 7 EDL tool on my C drive https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
...which mentions I need to install the original Axon 7 drivers. When connecting the phone to my pc I choose the option to install the drivers and an install wizard appeared which i clicked through. With that I figured that part is done, however the EDL tool says inside device Manager my phone should be defined as "Qualcomm HS-USB QDLoader 9008" and "ZTE Handset Diagnostic Interface(DFU), instead it is listed as "ZTE Handset ADB Interface" under Android Device.
That made me suspicious so while being connected via usb to the Pc i ran cmd and checked if fastboot devices would even show me anything which it somehow didn't.
To check for it I used the same commands as shown by LinusTechTips in his Pocofone f1 video https://www.youtube.com/watch?v=BsHtfLh6azw at 04:10.
In the end I stopped the procedure because I did not want to ruin my only phone, being the helpless fool I am.
Do you have any more detailed step by step instructions for me in that regard, or maybe a more detailed guide to another popular ROM?
The first part of it being unlocking the bootloader and installing TWRP is the main thing here. Within TWRP I mostly haven't had any trouble in the past.
As far as I understand with that LOS 15.1 guide, all I have to do within TWRP is flashing the universal bootstack, then the Modem for A2017G, then the ROM and then GAPPS in one setting in that order.
However its kind of confusing that the TWRP step is taking place after doing these steps, as it should be a precondition to do so.
All I'm looking for is at least Oreo and the more stable + customizable the better.
Or maybe you have had a similiar problem with your axon 7 and know where the problem lies here?
Thank you so much for reading,
have a nice day!
(If I posted this at the wrong location I'm very sorry)
Hey man, glad that you asked before doing anything more. There's never anything wrong with asking for help. First things first, if you're trying to install the Axon 7 Drivers on your PC, these are actually the Qualcomm EDL Drivers. You can find these very simply by googling for 'qualcomm edl drivers' and then clicking either the first or second link. Install these, and after that you will want to install the ADB drivers. I assume you already have these, and know how to use ADB as per implying in your post. I'll still link them if you need them.
- After installing both drivers, reboot your PC and connect your phone to the PC. Enable USB Debugging and OEM Unlocking from Developer Options on the phone.
- Since you have already extracted the Axon 7 EDL Tool to the base of your C:/ drive (should be C:/Axon 7 EDL Tool), simply launch it by right-clicking the .bat file inside the folder and running it as administrator. The tool will show up, and you will see a warning. Press Y and agree to it, and your phone will automatically be switched off and put into EDL mode.
- At the top you will see 'Device connected!' in green. Now you can select the option 'Unlock' and then 'Bootloader Unlock'. Follow the steps on screen, and then you should have an unlocked bootloader. You can tell it's unlocked because it will show up everytime you start your device; "Your bootloader is unlocked".
- That was basically the hard part. Now you can simply just download a TWRP image, I would recommend this one. Download it, and rename it to 'recovery.img'. Place it in C:\Axon7_EDL_Tool\flash\recovery folder. Open up the EDL Tool again (make sure device is connected to computer and shows up as "Connected!" at the top of the tool), and select 'Flash' and then 'Recovery'. It will flash the TWRP image you downloaded.
- Once finished, you can reboot to your system on your phone, and download the latest LOS 15 .zip (your choice between Official builds or Unofficial), the Universal Bootloader, your device's modem (Flash depending on your phone model, here's A2017U and here's A2017G), and Opengapps to access the playstore. Make sure to download ARM 64 8.1 gapps. You can pick whichever size package you want, I would recommend Micro or smaller.
- Once downloaded, move all your stuff to your phone, and reboot to your TWRP (Volume Up + Power Button). Select Wipe, and slide the toggle at the bottom. Then go back and select Wipe again, but this time select Advanced and Wipe everything except your Internal storage. Now you can go into Flash, and flash in this order: Universal bootloader, modem, los15 zip, gapps. Simply reboot to system, and you're good to go. PS If you end up getting an error when you flash the los 15 zip, ignore it and flash the zip again.
IF you want to try some other Oreo rom, you can find plenty on the forums and even try a GSI. For the most stable, I recommend trying out LiquidRemix which is 9.0 Pie, OmniROM, which is also Pie, or DotOS/crDroid/ViperOS which are Oreo and you can find on our forums. You do not need to flash a vendor with DotOS/crDroid/ViperOS because they already come with one. Just follow the steps in each respective thread. There is no VoLTE, Wifi Calling and the camera flash is not synced on any rom that isn't LOS or Stock. You'll need to wipe all your partitions except Internal and External Storage, and then flash a vendor (Use either NFound vendor, Kranoner vendor, or the LOS Vendor. Each vendor has it own differences, but essentially do the same thing. LOS Vendor will be the fastest out of all 3, but does not work on some roms/gsi (will not boot). After flashing your vendor, flash your system.img and then flash your gapps. Now you can reboot.
runninghamster said:
Hey man, glad that you asked before doing anything more. There's never anything wrong with asking for help. First things first, if you're trying to install the Axon 7 Drivers on your PC, these are actually the Qualcomm EDL Drivers. You can find these very simply by googling for 'qualcomm edl drivers' and then clicking either the first or second link. Install these, and after that you will want to install the ADB drivers. I assume you already have these, and know how to use ADB as per implying in your post. I'll still link them if you need them.
- After installing both drivers, reboot your PC and connect your phone to the PC. Enable USB Debugging and OEM Unlocking from Developer Options on the phone.
- Since you have already extracted the Axon 7 EDL Tool to the base of your C:/ drive (should be C:/Axon 7 EDL Tool), simply launch it by right-clicking the .bat file inside the folder and running it as administrator. The tool will show up, and you will see a warning. Press Y and agree to it, and your phone will automatically be switched off and put into EDL mode.
- At the top you will see 'Device connected!' in green. Now you can select the option 'Unlock' and then 'Bootloader Unlock'. Follow the steps on screen, and then you should have an unlocked bootloader. You can tell it's unlocked because it will show up everytime you start your device; "Your bootloader is unlocked".
- That was basically the hard part. Now you can simply just download a TWRP image, I would recommend this one. Download it, and rename it to 'recovery.img'. Place it in C:\Axon7_EDL_Tool\flash\recovery folder. Open up the EDL Tool again (make sure device is connected to computer and shows up as "Connected!" at the top of the tool), and select 'Flash' and then 'Recovery'. It will flash the TWRP image you downloaded.
- Once finished, you can reboot to your system on your phone, and download the latest LOS 15 .zip (your choice between Official builds or Unofficial), the Universal Bootloader, your device's modem (Flash depending on your phone model, here's A2017U and here's A2017G), and Opengapps to access the playstore. Make sure to download ARM 64 8.1 gapps. You can pick whichever size package you want, I would recommend Micro or smaller.
- Once downloaded, move all your stuff to your phone, and reboot to your TWRP (Volume Up + Power Button). Select Wipe, and slide the toggle at the bottom. Then go back and select Wipe again, but this time select Advanced and Wipe everything except your Internal storage. Now you can go into Flash, and flash in this order: Universal bootloader, modem, los15 zip, gapps. Simply reboot to system, and you're good to go. PS If you end up getting an error when you flash the los 15 zip, ignore it and flash the zip again.
IF you want to try some other Oreo rom, you can find plenty on the forums and even try a GSI. For the most stable, I recommend trying out LiquidRemix which is 9.0 Pie, OmniROM, which is also Pie, or DotOS/crDroid/ViperOS which are Oreo and you can find on our forums. You do not need to flash a vendor with DotOS/crDroid/ViperOS because they already come with one. Just follow the steps in each respective thread. There is no VoLTE, Wifi Calling and the camera flash is not synced on any rom that isn't LOS or Stock. You'll need to wipe all your partitions except Internal and External Storage, and then flash a vendor (Use either NFound vendor, Kranoner vendor, or the LOS Vendor. Each vendor has it own differences, but essentially do the same thing. LOS Vendor will be the fastest out of all 3, but does not work on some roms/gsi (will not boot). After flashing your vendor, flash your system.img and then flash your gapps. Now you can reboot.
Click to expand...
Click to collapse
Thank you very much for your quick reply!
I tried to follow your very detailed guide, but within the first step with using the EDL Tool I already seem to have failed my attempt.
My device was connected as you suggested shown at the top and I choose "Unlock" and after "Bootloader Unlock". However in doing so when I choose flash, the phone had a different green ZTE startup animation and launched me into fastboot mode (at least I think thats what it is).
From there I have the option to "Start", "Power off", "Recovery mode" and "Restart bootloader. I can't access the system anymore or launch into FTM, however I still have access to the stock recovery.
The EDM tool states it cant find ADB device and that I should check if I unlocked the oem unlocking and usb debugging which i double checked before.
So I'm stuck here and pretty lost again. Is this a szenario of a hardbricked device or did I just miss the next step until now?
Im open for suggestions and hoping this isn't as bad as it would seem to a casual like me.
Again a big thank you for your detailed guide
RandomHelplessFool said:
Thank you very much for your quick reply!
I tried to follow your very detailed guide, but within the first step with using the EDL Tool I already seem to have failed my attempt.
My device was connected as you suggested shown at the top and I choose "Unlock" and after "Bootloader Unlock". However in doing so when I choose flash, the phone had a different green ZTE startup animation and launched me into fastboot mode (at least I think thats what it is).
From there I have the option to "Start", "Power off", "Recovery mode" and "Restart bootloader. I can't access the system anymore or launch into FTM, however I still have access to the stock recovery.
The EDM tool states it cant find ADB device and that I should check if I unlocked the oem unlocking and usb debugging which i double checked before.
So I'm stuck here and pretty lost again. Is this a szenario of a hardbricked device or did I just miss the next step until now?
Im open for suggestions and hoping this isn't as bad as it would seem to a casual like me.
Again a big thank you for your detailed guide
Click to expand...
Click to collapse
That's pretty unusual. Could you try powering off the device, and then holding both volume buttons whilst plugging in the cable (make sure to have the USB side already plugged into the computer).
This will take you into EDL Mode. From here, launch Device Manager and under 'Ports' , it should say Qualcomm QDLoader 9008 COM3 or something similar. Once you have confirmed this, launch the A7 EDL Tool (make sure to run it as administrator), and then try unlocking your bootloader once more. If it still doesn't seem to work, You'll have to downgrade your version to 7.1.1 and then unlock.
Download the 7.1 Nougat stock firmware which can be found here: https://androidfilehost.com/?fid=1322778262903993129
After its downloaded, extract the zip and copy all the contents of the folder into C:/Axon 7 EDL Tool/flash/full
Now again, go into EDL Mode, and make sure your device shows connected. Select 'Flash', and then 'Full'. It will prompt a warning, just press Y and agree. It'll flash 7.1 Nougat. After its finished, you can boot to system on your phone, and then follow my guide again to try unlocking the bootloader.
It seems that in general it should work, as my device is correctly noticed by windows and the EDL Tool recognises the phone being in EDL mode being connected succesfully to the pc.
However during the flashing process the procedure wont continue in both cases. After I push flash, its
"Loading the programmer:" "prog_ufs_firehose_8996.ddr.elf >>>"
and then it stays that way. In the beginning when I first attempted unlocking the device it went further than that.
Edit: Is it normal that EDL mode is just a blank black screen that won't allow you to turn off the device via standy button?
Here are parts of the log file after attempting to flash the 7.1.1
Version 2.15
Did not receive Sahara hello packet from device
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Status: 6 (null)
01:20:15: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Axon7_EDL_Tool\tools\fh_loader.exe --port=\\.\COM7 --sendxml=rawprogram0.xml,patch0.xml,rawprogram1.xml,patch1.xml,rawprogram2.xml,patch2.xml,rawprogram3.xml,patch3.xml,rawprogram4.xml,patch4.xml,rawprogram5.xml,patch5.xml --search_path=C:\Axon7_EDL_Tool\flash\full,C:\Axon7_EDL_Tool\tools --mainoutputdir=C:\Axon7_EDL_Tool\logs --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
************************************************
01:20:15: DEBUG: Binary build date: Nov 21 2017 @ 02:53:33
01:20:15: DEBUG: Build Version: 17.11.21.02.53.33
01:20:15: INFO: Current working dir (cwd): C:\WINDOWS\system32\
01:20:15: INFO: Showing network mappings to allow debugging
01:20:15: DEBUG: Neue Verbindungen werden gespeichert.
01:20:15: DEBUG:
01:20:15: DEBUG: Es sind keine Eintr„ge in der Liste.
01:20:15: DEBUG:
01:20:15: INFO:
01:20:15: INFO: Trying to store 'rawprogram0.xml' in string table
01:20:15: DEBUG: ==================================================================================
01:20:15: DEBUG: ==================================================================================
01:20:15: INFO: Looking for file 'rawprogram0.xml'
01:20:15: DEBUG: 1. Calling stat('C:\Axon7_EDL_Tool\flash\full\rawprogram0.xml')
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\rawprogram0.xml') with AccessMode='rb'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: DEBUG: Found 'C:\Axon7_EDL_Tool\flash\full\rawprogram0.xml' (3271 bytes)
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\rawprogram0.xml') with AccessMode='r'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: INFO:
01:20:15: INFO: Trying to store 'patch0.xml' in string table
01:20:15: DEBUG: ==================================================================================
01:20:15: DEBUG: ==================================================================================
01:20:15: INFO: Looking for file 'patch0.xml'
01:20:15: DEBUG: 1. Calling stat('C:\Axon7_EDL_Tool\flash\full\patch0.xml')
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\patch0.xml') with AccessMode='rb'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: DEBUG: Found 'C:\Axon7_EDL_Tool\flash\full\patch0.xml' (6259 bytes)
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\patch0.xml') with AccessMode='r'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: INFO:
01:20:15: INFO: Trying to store 'rawprogram1.xml' in string table
01:20:15: DEBUG: ==================================================================================
01:20:15: DEBUG: ==================================================================================
01:20:15: INFO: Looking for file 'rawprogram1.xml'
01:20:15: DEBUG: 1. Calling stat('C:\Axon7_EDL_Tool\flash\full\rawprogram1.xml')
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\rawprogram1.xml') with AccessMode='rb'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: DEBUG: Found 'C:\Axon7_EDL_Tool\flash\full\rawprogram1.xml' (1012 bytes)
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\rawprogram1.xml') with AccessMode='r'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: INFO:
01:20:15: INFO: Trying to store 'patch1.xml' in string table
01:20:15: DEBUG: ==================================================================================
01:20:15: DEBUG: ==================================================================================
01:20:15: INFO: Looking for file 'patch1.xml'
01:20:15: DEBUG: 1. Calling stat('C:\Axon7_EDL_Tool\flash\full\patch1.xml')
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\patch1.xml') with AccessMode='rb'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: DEBUG: Found 'C:\Axon7_EDL_Tool\flash\full\patch1.xml' (6227 bytes)
01:20:15: DEBUG: 2. Calling fopen('C:\Axon7_EDL_Tool\flash\full\patch1.xml') with AccessMode='r'
01:20:15: DEBUG: Trying get filesize, calling fseek()
01:20:15: INFO:
[...]
01:20:39: {ERROR: WritePort:5164 Could not write to '\\.\COM7', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times
@RandomHelplessFool: Yes, it is normal that the screen is black when in EDL mode. You can use VolUp+Power to get out of EDL. DFU mode also uses the same black screen, nothing can be flashed in that mode. You should rely on MiFlash, Axon 7 EDL Tool and Windows Device Management to reliably determine what mode the device is in. If in DFU, use the DFU MultiDL Tool to get out of it and switch to EDL.
Yeah, was about to say try MiFlash. Use the 2016 version (search on Google).
Use MiFlash and select the folder with the 7.1 Nougat files in it, and flash. Then try EDL Tool again for unlocking bootloader.
runninghamster said:
Yeah, was about to say try MiFlash. Use the 2016 version (search on Google).
Use MiFlash and select the folder with the 7.1 Nougat files in it, and flash. Then try EDL Tool again for unlocking bootloader.
Click to expand...
Click to collapse
Thank you both for you recommandations!
Obviously in my case, it would be too convenient to have it work in the way its expected to.
I searched a while and found these two links to the Miflash tool :
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20161222
http://en.miui.com/thread-345974-1-1.html
I choose to install the second version, as the first ones installer is entirely in chinese which made me a bit skeptical.
However with the english version from 30.08.2016, I had no luck as my device didn't show up.
I selected the folder where I have extracted the Nougat B12 Rom runninghamster suggested to me earlier.
Before and after the procedure I checked via device Manager and EDL Tool that my device is connected and still in EDL Mode, which it was / is, at least the EDL Tool claims that.
Also I tried to get out of EDL mode in hopes of restarting it, which in my thought process might be useful, as I tried several operations in it already.
Yet Volume Up + Power isn't doing much the device just seems to stay in EDL mode, as the EDL tool still claims that.
I found a log file in the Miflash folder which might show something interestening to you guys, so here is a part of it
[09:10:58]:copy C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Qualcomm\Driver\serial\i386\qcCoInstaller.dll to C:\WINDOWS\system32\qcCoInstaller.dll
[09:10:58]pen RegistryKey Software\XiaoMi\MiFlash\
[09:10:58]:create RegistryKey Software\XiaoMi\MiFlash\
[09:10:59]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver\android_winusb.inf to ,result False,GetLastWin32Error Unknown error (0xe000024b)
[09:10:59]:mkdir "C:\Users\Marius PowerPC\.android"
[09:10:59]utput:
[09:10:59]: echo 0x2717 >>"C:\Users\Marius PowerPC\.android\adb_usb.ini"
[09:10:59]utput:
[09:10:59]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:00]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:11:00]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:00]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:11:00]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:00]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:11:00]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:22]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\WINDOWS\INF\oem60.inf,result True,GetLastWin32Error
[09:11:22]:set RegistryKey value:qcser.inf--oem60.inf
[09:15:56]ie angegebene Umwandlung ist ungültig.
[09:15:56]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:20:16]ie angegebene Umwandlung ist ungültig.
[09:20:16]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:20:18]ie angegebene Umwandlung ist ungültig.
[09:20:18]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:23:19]ie angegebene Umwandlung ist ungültig.
[09:23:19]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:51:51]:copy C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Qualcomm\Driver\serial\i386\qcCoInstaller.dll to C:\WINDOWS\system32\qcCoInstaller.dll
[09:51:51]pen RegistryKey Software\XiaoMi\MiFlash\
[09:51:53]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver\android_winusb.inf to ,result False,GetLastWin32Error Unknown error (0xe000024b)
[09:51:53]:mkdir "C:\Users\Marius PowerPC\.android"
[09:51:53]utput:
I also checked the DFU Tool AnonVendetta mentioned and came up with that link
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229/page2
but I figured as the EDL Tool still claims my phone is in edl mode and device manager is showing if my device is connected or not,
there shouldn't be any need for it in theory.
As always, I'm looking foreward for you recommandations, thank you for helping me thus far! :fingers-crossed:
RandomHelplessFool said:
Thank you both for you recommandations!
Obviously in my case, it would be too convenient to have it work in the way its expected to.
I searched a while and found these two links to the Miflash tool :
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20161222
http://en.miui.com/thread-345974-1-1.html
I choose to install the second version, as the first ones installer is entirely in chinese which made me a bit skeptical.
However with the english version from 30.08.2016, I had no luck as my device didn't show up.
I selected the folder where I have extracted the Nougat B12 Rom runninghamster suggested to me earlier.
Before and after the procedure I checked via device Manager and EDL Tool that my device is connected and still in EDL Mode, which it was / is, at least the EDL Tool claims that.
Also I tried to get out of EDL mode in hopes of restarting it, which in my thought process might be useful, as I tried several operations in it already.
Yet Volume Up + Power isn't doing much the device just seems to stay in EDL mode, as the EDL tool still claims that.
I found a log file in the Miflash folder which might show something interestening to you guys, so here is a part of it
[09:10:58]:copy C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Qualcomm\Driver\serial\i386\qcCoInstaller.dll to C:\WINDOWS\system32\qcCoInstaller.dll
[09:10:58]pen RegistryKey Software\XiaoMi\MiFlash\
[09:10:58]:create RegistryKey Software\XiaoMi\MiFlash\
[09:10:59]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver\android_winusb.inf to ,result False,GetLastWin32Error Unknown error (0xe000024b)
[09:10:59]:mkdir "C:\Users\Marius PowerPC\.android"
[09:10:59]utput:
[09:10:59]: echo 0x2717 >>"C:\Users\Marius PowerPC\.android\adb_usb.ini"
[09:10:59]utput:
[09:10:59]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:00]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:11:00]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:00]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:11:00]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:00]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:11:00]pen RegistryKey Software\XiaoMi\MiFlash\
[09:11:22]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\WINDOWS\INF\oem60.inf,result True,GetLastWin32Error
[09:11:22]:set RegistryKey value:qcser.inf--oem60.inf
[09:15:56]ie angegebene Umwandlung ist ungültig.
[09:15:56]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:20:16]ie angegebene Umwandlung ist ungültig.
[09:20:16]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:20:18]ie angegebene Umwandlung ist ungültig.
[09:20:18]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:23:19]ie angegebene Umwandlung ist ungültig.
[09:23:19]: bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 99.
bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 101.
bei XiaoMiFlash.code.Utility.UsbDevice.GetScriptDevices(List`1 UsbItems) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 89.
bei XiaoMiFlash.code.Utility.UsbDevice.GetDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\UsbDevice.cs:Zeile 47.
bei XiaoMiFlash.MainFrm.RefreshDevice() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\MainFrm.cs:Zeile 298.
[09:51:51]:copy C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Qualcomm\Driver\serial\i386\qcCoInstaller.dll to C:\WINDOWS\system32\qcCoInstaller.dll
[09:51:51]pen RegistryKey Software\XiaoMi\MiFlash\
[09:51:53]:install driver C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver\android_winusb.inf to ,result False,GetLastWin32Error Unknown error (0xe000024b)
[09:51:53]:mkdir "C:\Users\Marius PowerPC\.android"
[09:51:53]utput:
I also checked the DFU Tool AnonVendetta mentioned and came up with that link
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229/page2
but I figured as the EDL Tool still claims my phone is in edl mode and device manager is showing if my device is connected or not,
there shouldn't be any need for it in theory.
As always, I'm looking foreward for you recommandations, thank you for helping me thus far! :fingers-crossed:
Click to expand...
Click to collapse
https://mega.nz/#!N0ZUiKID!-qdyCaiZJTeCoWSQKiQ9dwzrrtmI1HunPgI7bqEtIeI
Download this version of MiFlash and try it again. There's no theoretical reason why it shouldn't be able to flash the 7.1 EDL.
runninghamster said:
https://mega.nz/#!N0ZUiKID!-qdyCaiZJTeCoWSQKiQ9dwzrrtmI1HunPgI7bqEtIeI
Download this version of MiFlash and try it again. There's no theoretical reason why it shouldn't be able to flash the 7.1 EDL.
Click to expand...
Click to collapse
is ther a reason you say to use miflash 2016 version? i like to know because i always use the latest now and the flashing goes without problems
Okay so I downloaded the 2016 Version provided by runninghamster, after extracting and opening the exe as an admin, I get an error message called "RunDLL" which say that a certain "qcCoInstaller.dll" was missing.
With the latest version of the miflash tool https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
it states that it "Could'nt find flash script" after I choose the Nougat folder where I extracted the zip into. With the previous version I tried (http://en.miui.com/thread-345974-1-1.html)
there was just an installer which provided me with an executable at the desktop after it was done. Is there an installer in these other versions too that I have to go through first?
Also my phone by itself left the EDL Mode again and is back in what appears to be the fastboot mode, where I have the option to "Start", "Power off" "Recovery mode" and "Restart boodloader".
Do you guys have any idea what I can do to make either of the miflash versions running?
Do I need to be in EDL Mode to use Miflash or can I use it in that fastboot Mode too?
I hope we can get to the bottom of this eventually thank you very much for the patience!
Best regards
RandomHelplessFool said:
Okay so I downloaded the 2016 Version provided by runninghamster, after extracting and opening the exe as an admin, I get an error message called "RunDLL" which say that a certain "qcCoInstaller.dll" was missing.
With the latest version of the miflash tool https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
it states that it "Could'nt find flash script" after I choose the Nougat folder where I extracted the zip into. With the previous version I tried (http://en.miui.com/thread-345974-1-1.html)
there was just an installer which provided me with an executable at the desktop after it was done. Is there an installer in these other versions too that I have to go through first?
Also my phone by itself left the EDL Mode again and is back in what appears to be the fastboot mode, where I have the option to "Start", "Power off" "Recovery mode" and "Restart boodloader".
Do you guys have any idea what I can do to make either of the miflash versions running?
Do I need to be in EDL Mode to use Miflash or can I use it in that fastboot Mode too?
I hope we can get to the bottom of this eventually thank you very much for the patience!
Best regards
Click to expand...
Click to collapse
Ignore the "couldn't find flash script" error and try flashing it. You can only use MiFlash in EDL Mode. I know you must be frustrated at this point, but I have experienced all the same things that you have said. Try changing which USB Port you are plugged into, try changing your USB C wire, and make sure that you're running MiFlash as administrator. Try moving the folder with the Nougat files to your desktop, and reselect it again in MiFlash. If it gets stuck at "trying to communicate with port" etc. , try plugging your phone into another USB port.
runninghamster said:
Ignore the "couldn't find flash script" error and try flashing it. You can only use MiFlash in EDL Mode. I know you must be frustrated at this point, but I have experienced all the same things that you have said. Try changing which USB Port you are plugged into, try changing your USB C wire, and make sure that you're running MiFlash as administrator. Try moving the folder with the Nougat files to your desktop, and reselect it again in MiFlash. If it gets stuck at "trying to communicate with port" etc. , try plugging your phone into another USB port.
Click to expand...
Click to collapse
Hey there,
I'll keep trying for sure
However there is yet another problem with the latest Miflash version, aside from the "could'nt find flash script" thing.
Im getting this error when pushing refresh as my device isn't found.
I had to translate some parts of the error from german to english, if something looks weird it probably wasnt properly translated or I missed it.
Should it really work directly after extracting miflash and open the executable without any installer?
Thank you for your time!
System.IO.DirectoryNotFoundException: Part of the path "C:\Users\Marius PowerPC\Desktop\Nüuscht\Miflash\MiFlash20181115(1)\MiFlash20181115\log\[email protected]" wasnt found.
bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
bei XiaoMiFlash.code.Utility.Log.w(String msg, Boolean throwEx)
bei XiaoMiFlash.code.Utility.Log.w(String msg)
bei XiaoMiFlash.MainFrm.RefreshDevice()
bei XiaoMiFlash.MainFrm.btnRefresh_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3362.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
XiaoMiFlash
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///C:/Users/Marius%20PowerPC/Desktop/N%C3%BCuscht/Miflash/MiFlash20181115(1)/MiFlash20181115/XiaoMiFlash.exe.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3324.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3362.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3190.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
MiUSB
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///C:/Users/Marius%20PowerPC/Desktop/N%C3%BCuscht/Miflash/MiFlash20181115(1)/MiFlash20181115/MiUSB.DLL.
----------------------------------------
System.Management
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3190.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3324.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3362.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3190.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3190.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.3190.0 built by: NET472REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------
************** JIT-Debuggen **************
in order to activate JIT-Debuggen (Just-In-Time) you need to activate the configure data
and set the computers executable
(machine.config) of the jitDebugging-Value in system.windows.forms.
The application with the active debugger has to be compiled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When the JIT-Debugger is activated, not all of the given exception are sent to the JIT-Debugger,
which is registert on the Pc, and isnt treated in the dialogfield.
Breaking News
So out of disbelief and frustration, I just attempted to do the EDL full Nougat Rom flash once more, and somehow this time it actually did something...
I really couldn't believe this is a thing, but as it seems I am right now setting up a fresh nougat install...This is an unbelievable feeling :victory:
Thank you very much for your seemingly never ending patience @runninghamster ! I am very glad you were there for me.
Ill celebrate this a little longer and then think hard about the futur of my Rom life on this phone.
After all I'm probably needing a break before I sit in another rollercoaster like this again, and probably a spare phone..
I hope I'm not celebrating too fast, we will see hehe
RandomHelplessFool said:
So out of disbelief and frustration, I just attempted to do the EDL full Nougat Rom flash once more, and somehow this time it actually did something...
I really couldn't believe this is a thing, but as it seems I am right now setting up a fresh nougat install...This is an unbelievable feeling :victory:
Thank you very much for your seemingly never ending patience @runninghamster ! I am very glad you were there for me.
Ill celebrate this a little longer and then think hard about the futur of my Rom life on this phone.
After all I'm probably needing a break before I sit in another rollercoaster like this again, and probably a spare phone..
I hope I'm not celebrating too fast, we will see hehe
Click to expand...
Click to collapse
Hahahahaha, that's brilliant. I guess the perseverance paid off. Whenever you're ready, you can attempt the bootloader unlock using the EDL Tool. If you're still sceptical on it, try out the Axon 7 Toolkit which should be a little more interface friendly, but I've found it doesn't work all the time.
runninghamster said:
Hey man, glad that you asked before doing anything more. There's never anything wrong with asking for help. First things first, if you're trying to install the Axon 7 Drivers on your PC, these are actually the Qualcomm EDL Drivers. You can find these very simply by googling for 'qualcomm edl drivers' and then clicking either the first or second link. Install these, and after that you will want to install the ADB drivers. I assume you already have these, and know how to use ADB as per implying in your post. I'll still link them if you need them.
- After installing both drivers, reboot your PC and connect your phone to the PC. Enable USB Debugging and OEM Unlocking from Developer Options on the phone.
- Since you have already extracted the Axon 7 EDL Tool to the base of your C:/ drive (should be C:/Axon 7 EDL Tool), simply launch it by right-clicking the .bat file inside the folder and running it as administrator. The tool will show up, and you will see a warning. Press Y and agree to it, and your phone will automatically be switched off and put into EDL mode.
- At the top you will see 'Device connected!' in green. Now you can select the option 'Unlock' and then 'Bootloader Unlock'. Follow the steps on screen, and then you should have an unlocked bootloader. You can tell it's unlocked because it will show up everytime you start your device; "Your bootloader is unlocked".
- That was basically the hard part. Now you can simply just download a TWRP image, I would recommend this one. Download it, and rename it to 'recovery.img'. Place it in C:\Axon7_EDL_Tool\flash\recovery folder. Open up the EDL Tool again (make sure device is connected to computer and shows up as "Connected!" at the top of the tool), and select 'Flash' and then 'Recovery'. It will flash the TWRP image you downloaded.
- Once finished, you can reboot to your system on your phone, and download the latest LOS 15 .zip (your choice between Official builds or Unofficial), the Universal Bootloader, your device's modem (Flash depending on your phone model, here's A2017U and here's A2017G), and Opengapps to access the playstore. Make sure to download ARM 64 8.1 gapps. You can pick whichever size package you want, I would recommend Micro or smaller.
- Once downloaded, move all your stuff to your phone, and reboot to your TWRP (Volume Up + Power Button). Select Wipe, and slide the toggle at the bottom. Then go back and select Wipe again, but this time select Advanced and Wipe everything except your Internal storage. Now you can go into Flash, and flash in this order: Universal bootloader, modem, los15 zip, gapps. Simply reboot to system, and you're good to go. PS If you end up getting an error when you flash the los 15 zip, ignore it and flash the zip again.
IF you want to try some other Oreo rom, you can find plenty on the forums and even try a GSI. For the most stable, I recommend trying out LiquidRemix which is 9.0 Pie, OmniROM, which is also Pie, or DotOS/crDroid/ViperOS which are Oreo and you can find on our forums. You do not need to flash a vendor with DotOS/crDroid/ViperOS because they already come with one. Just follow the steps in each respective thread. There is no VoLTE, Wifi Calling and the camera flash is not synced on any rom that isn't LOS or Stock. You'll need to wipe all your partitions except Internal and External Storage, and then flash a vendor (Use either NFound vendor, Kranoner vendor, or the LOS Vendor. Each vendor has it own differences, but essentially do the same thing. LOS Vendor will be the fastest out of all 3, but does not work on some roms/gsi (will not boot). After flashing your vendor, flash your system.img and then flash your gapps. Now you can reboot.
Click to expand...
Click to collapse
Hey @runninghamster what is the point of the vendors? So far I've only switched from stock to LOS (which I wish I asked for help on here), but I don't think I ever installed a vendor.
Blankisblank said:
Hey @runninghamster what is the point of the vendors? So far I've only switched from stock to LOS (which I wish I asked for help on here), but I don't think I ever installed a vendor.
Click to expand...
Click to collapse
A vendor is essentially just a partition that allows GSI (Generic System Image) to be installed without the manufacturer having to completely change too many things. Think of it as a space where information about your device is stored, separate of your OS. If you're on LOS 15, it creates a vendor partition automatically when you install it. It also has it's own vendor, which we call LOS vendor (aptly named lol). We have 4-5 separate vendors because each vendor works differently with GSI, and so far LOS vendor is the most recently updated and best working one, however it doesn't boot with all GSI, and thus why we have other vendors.
You can have a read of this article if you want to know more https://www.androidauthority.com/project-treble-818225/
Related
I’m stuck with a minor problem and have spent more than a week trying to fix it. :?
STORY
To replace an O2 3.20 Eng on PCC 2002, I have cooked a French Rom based on 3.16 Qteck and included the freeware I liked, one of them being a freeware named POI (Point Of Interest) to be used with Tom-Tom Navigator.
ORIGINE
My problem is that I think, installing POI on ROM, was a silly choice of me as I cannot save any modified settings of POI such as setting for Speed cameras. :evil:
PROBLEMS
Pb N° 1. : I cannot save my POI settings. I get no really error messages, but all is gone next time I open it. Does any one have a clue?
PB N°2: As I had no clue, I decided to cook a French ROM without POI in it. But I failed to reinstall the newly cooked ROM after downloading the EXE file and running it, my PC opened DOS windows with an error message saying ERROR UNSUPORTED LANGUAGE ‘FRA’ prior to opening the Program A window. Then Program A gives me an Error 007 No Rom Image File … Cannot find ROM image to upgrade you Pocket PC.
PB N° 3: I decided to build an English ROM on 3.20 UK. as it seemed that French language may be the source of PB N°2. But after downloading it and running the exe file on my PC , a DOS windows opens and close then nothing would happened.
PB N°4: I decided to use XDAtools to flash my original XDA ROM (saved in the first place on my PC) back to my XDA, but XDAtools refuses to write to my XDA memory through Program A saying error opening c:\...\English\ for writing Access refused. Error opening the target device. “
I have no idea what XDATools tried to open so I cannot either go that root neither.
I now quite perplex on how to solve question N°1, or at best getting BP N°2 to work.
Any hint :?:
kommst Du ins Recovery? Dann brauchst Du ja keine RUU sondern nimmst das was auf Deiner internen Speicher ist ( ROM ) und spielst es wieder ein oder gar die Backup. LG
Gesendet von meinem Transformer Prime TF201 mit Tapatalk 2
After Flash ROM by use SD-Card. Although CheckSUM is OK!
I reset and nothing work. I can't do anything, enter bootloader, hard-reset, soft-reset, connect with PC, nothing.
Help me plz.
I really need it for my job.....!
My device is O2-xdaI
Thank
Which ROM did you use ?
Where did you get it from ?
I used xdatool to build bootloader and winCE to SD-Card.
It's xda-developers Special Edition.
I don't know which version.
I used xdatool to build bootloader and winCE to SD-Card.
It's xda-developers Special Edition.
I don't know which version.
Kavin,
I'm not the most experience guy on this forum for this. I'll not be able to diagnose right away what you may have done: What has happened.
Let me summarise what you said with the missing information ?: )
You had a working XDA1 using the following:
- Bootloader version: :?:
- Rom version : :?:
You tried an upgrade getting the pre-cooked Special Edition ROM based on PPC 2002. You :
- Dowladed the ROM in the format :?: (exe, Nbf, Nb1)
- copied it on an SD card using XDATools
- Flashed it to your XDA using XDA Bootloader mode version :?:
and now your XDA seems to be dead.
After your clarified the missing point, I have one more question :
- Can you enter into bootloader mode at present ?
Yearh........! exactly!
Thank Tanguy so much.
Anh previous bootloader is v5.15. Maybe ROM version is v3.12.00.
Now I can't enter booloader.
I tried to tap and hold Power Button then press Reset. So, nothing happen.
I can't lost my xda. I't very very Important device for my job.
Kevin,
Again, I'm not the most expert on this.
What looks surprising to me is that you have lost access to Boot Loader after a ROM upgrade. I'm confident you'll bring your XDA back to work as I never seen post like this which did not get resolved.
My advices are:
- Search this forum on this topic (dead boot loader) to understand why. I'm confident you will be able to correct this situation.
As a start point, try this http://forum.xda-developers.com/viewtopic.php?t=3274&highlight= or http://forum.xda-developers.com/viewtopic.php?t=12991&highlight= http://forum.xda-developers.com/viewtopic.php?t=12925&highlight=
Possible next step, in the XDATools there is an option to Fix Boot loader. I have never used it. It may solve your case. If that were for me, I'd spend what ever time is necessary to understand what has gone wrong before trying various tools to fix it.
Tanguy
i don't mean to be be a jackass, but if you unscrew your stylus, and stick the little plastic end into the little hole next to the headset jack, it should turn on. most people don't know that the device needs this to turn on after a romflash. it's called a hard reset, btw. hope this helped!
were can i download the xda-tool?
at first sorry, but my english is´nt the best.
i have a littel Problem:
DOS-box from C:\WINDOWS\system32\cmd.exe
print
ERROR: GetDeviceData - Eine vorhandene Verbindung wurde vom Remoehost geschlossen.
error getting devicedata
PROGRAMME A v1.09
break down
print
ERROR 011: EXECUTE REMOTE COMUNICATION PROGRAM ERROR
Cannot execute the remote communication program.
Please make sure that the USB/Serial cable is properly connected.
In the search i found that i need for this Problem the SD-card methode.
for this way i need the xda-tool?
but even link doesnt work.
Can anybody help?
Thanks
Re: were can i download the xda-tool?
witzvolk said:
at first sorry, but my english is´nt the best.
i have a littel Problem:
DOS-box from C:\WINDOWS\system32\cmd.exe
print
ERROR: GetDeviceData - Eine vorhandene Verbindung wurde vom Remoehost geschlossen.
error getting devicedata
PROGRAMME A v1.09
break down
print
ERROR 011: EXECUTE REMOTE COMUNICATION PROGRAM ERROR
Cannot execute the remote communication program.
Please make sure that the USB/Serial cable is properly connected.
In the search i found that i need for this Problem the SD-card methode.
for this way i need the xda-tool?
but even link doesnt work.
Can anybody help?
Thanks
Click to expand...
Click to collapse
Do you have an T-mobile ROM? If yes, you can only flash ROM via SD-card if you have a T-mobile ROM.
Download XDA-tool
I know, that i have to flashing ROM via SD-card, but i think i need for this the
XDA-tool!
And i can not find a correkt link for download this tool.
And i also dont know exactly how to use this.
Sory but i am a greenhorn :wink:
all will be o.K. :
i have found this link:
http://www.xs4all.nl/~itsme/projects/xda/OsImageTool.html
and with this tool i have flashed my rom.
greatings
VW
Hi,
this is about the VPA IV from Vodafone Germany.
I have hard resetted the device and that brought me deeper into trouble:
- Most of the Vodafon applications are gone, the neat SIM Manager, MIDLet Tool ...
- I can not install or run new programs. Most installations simply say "failed", Copied programs like SpAddCert do not start anymore. The erros message mentions that correct certificates are missed or parts of the program might not be installed correctly. Bull****. I figured out that there is a tool Default_Signed_DisableSecurity.CAB which might fix this issue, but I can not install it. Everything ran before I hard resetted the device.
Vodafone told me, I should request a Rom Update from Qtech.ch (I guess they meant Qtek.ch), however those people only provide roms for their own customers.
Can anybody help? The device is German and I would prefer to keep it that way.
Any help is appreciated!
The exact error message is:
Die Datei "SpAddCert" kann nicht geoeffnet werden. Es ist entweder nicht mit einem vertrauenswuerdigen Zertifikat signiert, oder eine ihre Komponenten kann nicht gefunden werden. Versuchen Sie die Datei neu zu installieren oder sie wiederherzustellen.
Re: Hard Reset changed security Settings, only MS Programs w
I continued investiagting this issue.
This seems not to be related to anything in Extended_Rom. If I rename to config file anything else, autorun does not do anything, anymore. So only the plain WM5 installation boots and will not get branded.
The support told me, that I'd better send the device in for an exchange.
Anything else I could do?
To sum the issue up:
- Some thread starts a few seconds after the device is booted. And it will change the security configuration in a way that the device does not allow to run even the shipped applications like Camera.exe
- this thread (or whatever) does not come out of the extended rom. If this is not executed the issue is present as well
- It will not be easy to update the rom. The update runs a small programm on the target device (as far as I know). This programm will not start, therefore the updating tool on XP says: Can not connect to device.
after I recovered my XDA and did a restore I cannot enter ACTIVESync anymore. Neither USB nor Bluetooth :-(
Windows-Systemprotocoll tells me that there is an error with the PNRP service.
on USB the following error occurs, its in german, but translated:
[Die Peer Name Resolution-Protokoll-Cloud wurde nicht gestartet. Fehler bei Standardidentität. Fehlercode: 0x80630801.]
"the PNRP cloud could not be started. Error in standard-identity. Errorcode 0x80630801"
--
the xda shows a errror window POCKET PC NETWORKING "cannot obtain a server-assigned IP address. Try again later or enter an IP address in Network settings"
--
Der Dienst "Peer Name Resolution-Protokoll" wurde mit folgendem Fehler beendet: %%-2140993535
"the service PNRP-Protokoll terminated due to following error %%-2140993535"
--
Der Dienst "Peernetzwerk-Gruppenzuordnung" ist vom Dienst "Peer Name Resolution-Protokoll" abhängig, der aufgrund folgenden Fehlers nicht gestartet wurde: %%-2140993535
says that service "group-assignment" is terminated due to dependecy to PNRP-Protokoll service which could not be started due to error %%-2140993535
update:
managed BT by deleting connection in ACTIVE-SYNC settings in XDA
and re-initiating connection.
So far so good
Flash Lite 3.0 application cab file cration using the visual studio2005
Hello friends,
i am flash developer i need to create the CAB file of Flashlite application.
I have created the flashlite 3.0 application.
i want to create the CAB file of this application for WM5.0.
its reallty helpful if anyone provides details how to create the flash lite application CAB file using .NET.
Thanks in advance
Looking for positive reply.
Flashlite CAB file cration uisng 2005 .NET
hi all,
Please let me know how to create the CAb of Flash lite application
uisng .NET(Visual studio 2005)
A friend has asked me to look at this Nokia Lumia 520, apparently it turned on one day and displayed this error message "unable to find a bootable option. Press any key to shutdown"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nokia Software Update for Retial recognises the phone and says software can be installed:
This downloads fine and starts the install process, however always fails with the message "phone not supported by nokia software updater retail"
I have also tried using NaviFirm+, searching for the product code 059S3T5 which lets me download the RM914_3058.50000.1425.0006_RETAIL_eu_euro1_327_06_452364_prd_signed firmware.
However i'm unable to flash this with the Nokia Care Suite, it states: 0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed for this device.
Has anyone got any suggestions on what else i can try to flash this firmware? or to try fix the phone?
I was following the tutorial here Flash/unbrand Lumia devices thinking if the firmware was re flashed all would be fine.
Cheers for any advice
Have you try with this
http://www.microsoft.com/en-us/mobile/support/faq/?action=singleTopic&topic=FA142987
Thanks for the suggestion, I have tried that, it will download the firmware too, however fail before flashing it stating the device is not supported.
InsaneNutter said:
Thanks for the suggestion, I have tried that, it will download the firmware too, however fail before flashing it stating the device is not supported.
Click to expand...
Click to collapse
I think win partition is crash. (like memory damage/corruption)
Hardware related problems.
InsaneNutter said:
A friend has asked me to look at this Nokia Lumia 520, apparently it turned on one day and displayed this error message "unable to find a bootable option. Press any key to shutdown"
Nokia Software Update for Retial recognises the phone and says software can be installed:
This downloads fine and starts the install process, however always fails with the message "phone not supported by nokia software updater retail"
I have also tried using NaviFirm+, searching for the product code 059S3T5 which lets me download the RM914_3058.50000.1425.0006_RETAIL_eu_euro1_327_06_452364_prd_signed firmware.
However i'm unable to flash this with the Nokia Care Suite, it states: 0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed for this device.
Has anyone got any suggestions on what else i can try to flash this firmware? or to try fix the phone?
I was following the tutorial here Flash/unbrand Lumia devices thinking if the firmware was re flashed all would be fine.
Cheers for any advice
Click to expand...
Click to collapse
Hi,
Have you sorted your phone out yet?
BruceKDallas said:
Hi,
Have you sorted your phone out yet?
Click to expand...
Click to collapse
Hi,
Nope i could never fix the phone, I spent loads of time messing about with it however think it was a hardware related problem.
I've given it back to my friend and shes since got a new phone.
I am into the same situation... NOKIA 520 RM-914 Code 059S7H0
"ERROR: Unable to find a bootable option. Press any key to shut down". Any button I push, the phone is going in bootloop ending with this ERROR...
I have tryed first with Windows Device Recovery Tool (WDRT) 3.1.4 to repair it, but no success...
In WDRT my Lumia is not detected automatically, so i must choose manually device manufacturer. To be detected I must restart the Lumia when DWRT is trying to detect it.
The Phone is detected as LUMIA phone, firmware version: unknown, Software available on server: 3058.50000.1425.003.
When I try to install the software after I download the package, the result is:
"Operation ended with failure. The software is not correctly signed or not signed for this device."
The NOKIA driver is seen as NOKIA BOOTMGR.
Then I've search on the internet about this problem and I've found this thread.
I tried the advanced mode with thor2.exe, I downloaded manually the firmware for my device Lumia 520, RM-914, Code 059S7H0
I opened Command Prompt as administrator, then used the command:
cd c:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
I used the command line to extract gtp0.bin from ffu image:
thor2 -mode ffureader -ffufile "C:\rm-914\RM914_3058.50000.1425.0003_RETAIL_eu_hungary_422_03_447211_prd_signed.ffu"
The result was 2 files, gpt0.bin and GPT1.bin. I renamed gpt0.bin as msimage.mbn.
RKH of the device is:
RKH of SBL1: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
RKH of UEFI: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
I've downloaded the hex file for my Lumia RM-914 to have the 2 files HEX.hex and msimage.mbn for the command line:
thor2 -mode emergency -hexfile "C:\TEMP\HEX.hex" -mbnfile "C:\TEMP\msimage.mbn" -orig_gpt
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.1
thor2 -mode emergency -hexfile C:\TEMP\HEX.hex -mbnfig_gpt
Process started Sun Dec 06 23:12:08 2015
Debugging enabled for emergency
Initiating emergency download
Operation took about 10.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
The Phone is still in NOKIA BOOTMGR mode...
If I try to disconnect the phone and restart, it goes into the the same message:
"ERROR: Unable to find a bootable option. Press any key to shut down", not showing me the RED screen like it should be.
If I go into the next step for flashing the device with the command line:
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile "C:\RM-914\RM914_059S7H0_3058.50000.1425.0003_037.vpl"
the screen changes into a big NOKIA logo, the driver goes from NOKIA BOOTMGR into NOKIA FLASH...
Thor2 is running on Windows of version 6.1
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\RM-914\RM914_059S7H0_3058.5
0000.1425.0003_037.vpl
Process started Sun Dec 06 23:22:20 2015
Logging to file C:\Users\Marta\AppData\Local\Temp\thor2_win_20151206232220_Threa
dId-3864.log
Parsing VPL file C:\RM-914\RM914_059S7H0_3058.50000.1425.0003_037.vpl
Successfully parsed VPL
Flashing .ffu file RM914_3058.50000.1425.0003_RETAIL_eu_hungary_422_03_447211_pr
d_signed.ffu (SW version 3058.50000.1425.0003)
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Boot Manager detected
Check status of battery
State of charge 8, charging current 282
Protocol version 1.1 Implementation version 1.16
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 8, charging current 266
Protocol version 1.1 Implementation version 1.16
Booting to FlashApp
Reboot to FlashApp command sent successfully.
DetachFrom connection
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Size of one transfer is 2363392
Size of buffer is 2359296
Number of eMMC sectors: 15269888
Platform ID of device: Nokia.MSM8227.P6036.1.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0019
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file C:\RM-914\RM914_3058.50000.1425.0003_RETAIL_eu
_hungary_422_03_447211_prd_signed.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 1.15 Implementation Version 1.28
DevicePlatformInfo: Nokia.MSM8227.P6036.1.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 19
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU async version 3 supported.
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 15269888
CID: Samsung, Size 7456 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
Unable to send ECHO REQ or ECHO REQ not supported
Get security Status...
Security Status:
Platform secure boot is enabled.
Secure eFUSE is enabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get RKH of the device...
RKH of the device is F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C
868FD
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 524288 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
Clearing the backup GPT...SKIPPED!
Successfully parsed FFU file. Header size: 0x000e0000, Payload size: 0x000000006
2900000, Chunk size: 0x00020000, Header offset: 0x00000000, Payload offset: 0x00
000000000e0000
RKH match between device and FFU file!
Option: Skip CRC32 check in use
Start sending header data...
FlashApp returned reported error in SecureFlashResp!
Status: 0x1106, Specifier: 0x8000000E
FA_ERR_FFU_SEC_HDR_VALIDATION_FAIL
Send of FFU header failed!
[IN] programSecureFfuFile. Closing C:\RM-914\RM914_3058.50000.1425.0003_RETAIL_e
u_hungary_422_03_447211_prd_signed.ffu
programming operation failed!
0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not co
rrectly signed or not signed for this device.
Operation took about 3.00 seconds.
THOR2_ERROR_FA_SIGNATURE_FAIL
THOR2 1.8.2.18 exited with error code -100658938 (0xFA001106)
Here, after this step, if the flash is 100% succesful, the screen must change in Green,
mine finished with the same error: "The FFU file is not correctly signed or not signed for this device..."
I guess the most of us are into the same situation, I can't make the device to skip the signature check... Any sugestions?
have you jtag?
As far as I read, JTAG is a toolbox for repairing Phones which have the same problem, but what we are trying to do is without this toolbox, we have a dead phone at home. Microsoft said is a hardware failure and they must change complete motherboard, but with Jtag Toolbox can be repaired without change anything, just a complete writing of the bootloader and software. I don't want to buy the toolbox just to repair my Lumia 520, I don't need it, I'm just a home user not a repairing company...
melhisedec said:
As far as I read, JTAG is a toolbox for repairing Phones which have the same problem, but what we are trying to do is without this toolbox, we have a dead phone at home. Microsoft said is a hardware failure and they must change complete motherboard, but with Jtag Toolbox can be repaired without change anything, just a complete writing of the bootloader and software. I don't want to buy the toolbox just to repair my Lumia 520, I don't need it, I'm just a home user not a repairing company...
Click to expand...
Click to collapse
are you should to find testpoint for qcom9008. and flashing phone.
Mine was running everything give I install windows 10 just give the battery does not know dai was appearing this message (Erro Unable to find a bootable option error. Press any key to shut down,) Lumia 925 Brazil
---------- Post added at 03:41 AM ---------- Previous post was at 03:36 AM ----------
Mine was running everything give I install windows 10 just give the battery does not know dai was appearing this message (Erro Unable to find a bootable option error. Press any key to shut down)
Usually, is the main problem with Lumia Software update and stupid engineers from Microsoft does not fix it...
you deleted header partition, and lumia don't power on. help you only jtag.
I didn't know anything about this problem of almost any Lumia device until my phone has done the automatic software update from Win8 to 8.1 or 10, I don't know which one... And the the phone restarted with this stupid problem:
"ERROR: Unable to find a bootable option. Press any key to shut down"...
I have one week of searching over the internet to fix this but i couldn't make it...
If i can remove or unlock the bootloader, maybe I can force the phone to be Flashed with WDRT 1.34 and no more error:
"The FFU file is not correctly signed or not signed for this device."
melhisedec said:
I
Click to expand...
Click to collapse
Only you can help the programmer and all) nokia, wpinternals not flashing it. pins or seek to enter the 9008 regime (disassembly required).
partition table got off
i know this problems on my lumia 720(1 motheboard- After the firmware is not those files, 2 motherboards- After stitched sbl3 not true - died).
jtag helped to you, and me.
InsaneNutter said:
Hi,
Nope i could never fix the phone, I spent loads of time messing about with it however think it was a hardware related problem.
I've given it back to my friend and shes since got a new phone.
Click to expand...
Click to collapse
Cool. I had the same issue and many other issues with my 520. I have a very cool way of fixing this and all other issues if you struggle to start the phone up. If you are interested, let me know and I will explain to you. Very easy and process takes about 5 minutes.
Cheers
BruceKDallas said:
Cool. I had the same issue and many other issues with my 520. I have a very cool way of fixing this and all other issues if you struggle to start the phone up. If you are interested, let me know and I will explain to you. Very easy and process takes about 5 minutes.
Cheers
Click to expand...
Click to collapse
How did you do ?
melhisedec said:
As far as I read, JTAG is a toolbox for repairing Phones which have the same problem, but what we are trying to do is without this toolbox, we have a dead phone at home. Microsoft said is a hardware failure and they must change complete motherboard, but with Jtag Toolbox can be repaired without change anything, just a complete writing of the bootloader and software. I don't want to buy the toolbox just to repair my Lumia 520, I don't need it, I'm just a home user not a repairing company...
Click to expand...
Click to collapse
Did you follow http://forum.xda-developers.com/showthread.php?t=2515453 correctly?
InsaneNutter said:
A friend has asked me to look at this Nokia Lumia 520, apparently it turned on one day and displayed this error message "unable to find a bootable option. Press any key to shutdown"
Nokia Software Update for Retial recognises the phone and says software can be installed:
This downloads fine and starts the install process, however always fails with the message "phone not supported by nokia software updater retail"
I have also tried using NaviFirm+, searching for the product code 059S3T5 which lets me download the RM914_3058.50000.1425.0006_RETAIL_eu_euro1_327_06_452364_prd_signed firmware.
However i'm unable to flash this with the Nokia Care Suite, it states: 0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed for this device.
Has anyone got any suggestions on what else i can try to flash this firmware? or to try fix the phone?
I was following the tutorial here Flash/unbrand Lumia devices thinking if the firmware was re flashed all would be fine.
Cheers for any advice
Click to expand...
Click to collapse
hy bro try this...... http://forum.gsmhosting.com/vbb/f67...mc-error-unable-find-bootable-option-1931094/ i have sucses
feherneoh said:
I have seen this error millions of times on 520, and could fix it always
what you'll need:
PC
micro USB cable
WPInternals
.hex loader for 520
.ffu for 520
T4 screwdriver
Small wire
All you have to do is to short the resistor on eMMC clock lane, and connect USB, phone will be in emergency mode. You can either select unlock or relock in WPInternals, but for unlock, be sure to use an SBL3, because that won't fix the problem on its own.
The best would be selecting relock, then flashing the ffu, so EFIESP gets fixed
If you need help finding that resistor, PM me
Click to expand...
Click to collapse
Ok, so I found the resistor on a picture in another forum - so I just short it out and connect to USB while still shorted?