Hi, since yesterday I have a big problem with my le pro 3, while charging the phone suddenly turned off. The system did not want to turn on, so I went into recovery (TWRP) and tried to format and upload a new rom, unfortunately during the flashing, a blue screen appeared. When changing the kernel, the flashing of the rom was done, but with the installation of the gapps it hung. I tried to install another rom, but it also spilled, with this addition, that I can not enter recovery, because artifacts appear or reboots.. Only fastboot works. With it, I tried to flash the kernel, recovery, but it did not do anything. I also used (TOOL ALL in ONE) and uploaded the stock rom, but the phone still does not work. Do you know what else could help, or is buying a new phone? Thanks for help
If you can use fast boot, your phone is not hard bricked. A brick is when you can not do anything , you will have a black screen and a red blinking light if a usb cable is connected.
Try pushing Twrp ( newest version) to the phone. If that is successful boot to recovery, fully wipe your phone, reboot to recovery and install you Rom> Gapps, and Magisk. I would suggest initially flashing Lineage 15.1. Once your phone is restored, flash whatever you would like.
If it doesn't work try another cable, or another port, or another computer. Computer needs to be up to date and you may need to temporarily disable antivirus, if the All in One tool isn't working its likely that your computer is blocking the install. especially if you are using Windows 10. All the program to be open within your firewall settings. Make sure its up to date and use AIO to update android drivers and adb.
I'm not giving anything, I still can't get into recovery
miichus said:
I'm not giving anything, I still can't get into recovery
Click to expand...
Click to collapse
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4
tsongming said:
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4
Click to expand...
Click to collapse
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot
miichus said:
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot
Click to expand...
Click to collapse
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?
tsongming said:
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?
Click to expand...
Click to collapse
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.
miichus said:
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.
Click to expand...
Click to collapse
For the second time I tried to use flashOne
Click to expand...
Click to collapse
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
tsongming said:
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Click to expand...
Click to collapse
I am using flashone 2.0 and flashing from your link, the file "le_zl1_qfil_ufs_fix.zip". Port 9008 is open. After three flash in 2.0 flash, I could enter recovery, but when flashing custom rom, a blue screen appeared.
Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs
tsongming said:
Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.
miichus said:
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.
Click to expand...
Click to collapse
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
tsongming said:
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Click to expand...
Click to collapse
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance
mavelino said:
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance
Click to expand...
Click to collapse
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.
tsongming said:
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.
Click to expand...
Click to collapse
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance
mavelino said:
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance
Click to expand...
Click to collapse
All I have is in the link you just responded to.
if that doesn't work try unpacking the Qfil and and see if you can just extract them.
I will look further when I get back home.
i also have an bricked LEX 3 Pro . i bought it as an X722 but of cause iam not shure . could also be an X720. i can not find the difference.
so Phone has only fastboot.
when i plug in usb cable it just reboot every 10 sec . no charging sreen appears
i flash Qfil, but not helped it stay the same
Related
Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.
brownbullet said:
Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.
Click to expand...
Click to collapse
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.
Download the whole Rom and flash it
Sent from my LG-D802 using XDA Premium 4 mobile app
brownbullet said:
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.
Click to expand...
Click to collapse
you are a fxxxing genius thnx you so much
im going through the same thing
bigpappapuff said:
you are a fxxxing genius thnx you so much
Click to expand...
Click to collapse
Can you help me out? The same thing with my G2 and i have no idea how to fix it.
Chris2312 said:
Can you help me out? The same thing with my G2 and i have no idea how to fix it.
Click to expand...
Click to collapse
More info please.
bender_007 said:
More info please.
Click to expand...
Click to collapse
my g2 was was rooted and got an over the air update so now its just stuck in twrp and all of the memory got wiped so i dont know if its possible to fix it or if i have to get a new phone.
There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go
bender_007 said:
There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go
Click to expand...
Click to collapse
Thank you
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Hi,
Was stuck with my HTC Butterfly x920d with the same. Thanks for your guidance, was able to recover.
Foolishly, I had SIMULATE option checked in the recovery settings. Though was able to boot into system but no account, no google & reset stuck into recovery.
Thanks a ton
(I was trying to reset this device for my father)
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
How do you get into settings when it goes straight to simulating actions?
Hi there,
I recently was going to install a new rom on my phone... I ended up doing a system restore on settings... And now the phone will not update the MTP driver, I tried it on another computer nothing so far. It also wiped my back up file in recovery!
I also tried going into the registry do to the "UPPERFILTERS" fix but it did not work for me!
Any suggestions on how I can somehow fix this!
Thanks.
ZishanMohiuddin said:
Hi there,
I recently was going to install a new rom on my phone... I ended up doing a system restore on settings... And now the phone will not update the MTP driver, I tried it on another computer nothing so far. It also wiped my back up file in recovery!
I also tried going into the registry do to the "UPPERFILTERS" fix but it did not work for me!
Any suggestions on how I can somehow fix this!
Thanks.
Click to expand...
Click to collapse
anyone?
reflash with odin does it reset philzrecovery?
I am about to reset my phone with odin as I cant connect the USB, the recovery will still be there after?
ZishanMohiuddin said:
the phone will not update the MTP driver
Click to expand...
Click to collapse
The phone won't update the MTP driver? You must mean PC. I can only assume that you are allergic to Google searches as good solutions are easily found.
Google search: reinstall MTP driver
Try disabling WMP temporarily as it often interferes. And if necessary you can remove the previous driver install in the registry. There are often two entries, one under HKLM and another under HKCU.
.
ZishanMohiuddin said:
I am about to reset my phone with odin as I cant connect the USB, the recovery will still be there after?
Click to expand...
Click to collapse
That depends on what you do with Odin. If you flash a full firmware, only your user files in the /data partition will persist. Your recovery would be wiped.
And a factory reset would delete user files.
.
fffft said:
The phone won't update the MTP driver? You must mean PC. I can only assume that you are allergic to Google searches as good solutions are easily found.
The link you provided didn't work. Could you provide me with a step by step guide. I tried two steps using the registry and watched various videos it didn't help. I am very new to this lol.
how do you remove previous driver driver?
if does not work, I got firmware files from sammobile to unbrick. Would my own back up from Philz be able to be used by odin?
Click to expand...
Click to collapse
ZishanMohiuddin said:
The link you provided didn't work.
Click to expand...
Click to collapse
The link worked in the post preview, but XDA likes to automerge posts and apparently that broke the hyperlink as well. I've fixed the link. But all you would have had to do was copy and paste the link.
That concerns me because if you don't notice /can't correct a minor formatting error in a link then your phone is at substantial risk. What I mean is that Odin is dangerous if you don't pay close attention to details. Be careful.
It's not hard to reinstall a driver. Just uninstall the old driver and realize that WMP can interfere with the reinstallation. If only a step by step guide will do, you will find lots of spoonfed guides in the Google search results.
I don't use Philz, I find TWRP to be much better. But I doubt that you could use Odin to restore a Philz backup. You'd need to reinstall Philz. Then restore your backup from recovery mode.
.
Decided to re-flash stock rom using odin with recovery file from sam-mobile website and up and running again. Thanks for help anyways!
.
The link you provided didn't work. Could you provide me with a step by step guide. I tried two steps using the registry and watched various videos it didn't help. I am very new to this lol.
how do you remove previous driver driver?
if does not work, I got firmware files from sammobile to unbrick. Would my own back up from Philz be able to be used by odin?[/QUOTE]
fffft said:
The link worked in the post preview, but XDA likes to automerge posts and apparently that broke the hyperlink as well. I've fixed the link. But all you would have had to do was copy and paste the link.
That concerns me because if you don't notice /can't correct a minor formatting error in a link then your phone is at substantial risk. What I mean is that Odin is dangerous if you don't pay close attention to details. Be careful.
It's not hard to reinstall a driver. Just uninstall the old driver and realize that WMP can interfere with the reinstallation. If only a step by step guide will do, you will find lots of spoonfed guides in the Google search results.
I don't use Philz, I find TWRP to be much better. But I doubt that you could use Odin to restore a Philz backup. You'd need to reinstall Philz. Then restore your backup from recovery mode.
.
Click to expand...
Click to collapse
I did check out your hyperlink lol I just googled searched it. I thought you sent a link not a google search. I went into three different step by step guides regarding the issue, it was just one of those days where basics things just didn't work out lol.
I got fed up so I did I ended up doing a full recovery I just wanted to avoid that process since I know there was a simpler method.
NOTE-1:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources like this & this & this and many others.
It's according to best of my knowledge and I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing. Whole device will be wiped.
NOTE-2:
If you have a custom recovery, install Stock ROM (v2.1.0.13 or v2.1.0.12) instead.
If you don't have a custom recovery, you may get one here or here.
If your device is bricked and can't boot into recovery or bootloader mode (read here what it is), proceed.
NOTE-3:
Given firmware link is v2.1.0.13 for device 059V782. There are some variants of Nokia X2DS (other product codes) which were officially updated from 2.1.0.11 to 2.1.0.12, so they dont support version 2.1.0.13.
Make sure your device supports 2.1.0.13 by googling your product code (written on back of device, see by removing back cover) or you may get in trouble. In case if you need 2.1.0.12, download it from some other link and follow the instructions given here.
NOTE-4:
Hard-bricked devices (with no buttons working, no Download Mode) may also be recovered by this method but with a slightly different procedure.
QFIL can also be used instead of NCS, but NCS feels a kinda little bit official way
REQUIREMENTS:
A PC with Windows and uninterrupted power supply. (I used Dell Inspiron 15R with Windows 8.1 and 10).
A USB data cable.
Fully charged phone, soft-bricked at maximum i.e. no recovery, no boot accessible
STEPS:
Download and Install NCS to your PC.
Copy UserGroupsConfiguration.cfg to "C:\Program Files (x86)\Nokia\Nokia Care Suite\Product Support Tool For Store 5".
Download Firmware and extract to "C:\ProgramData\Nokia\Packages\Products\RM-1013".
Launch NCS > Product Support Tool for Store 5.
At Sign-In screen, click Work Offline.
Disable Automatic Product Selection.
Go to File > Open Product and select RM-1013.
Click Programming > Recovery. Downloaded Firmware must be listed there.
Click Start and follow instructions. DO NOT INTERRUPT FLASHING PROCESS OR IT MAY HARD BRICK YOUR PHONE LEAVING IT USELESS.
Wait a few minutes and done. You have a newly purchased phone in your hands if all goes well.
Thanks for making a proper post for this.:good:
Devnikolus said:
Thanks for making a proper post for this.:good:
Click to expand...
Click to collapse
There are many others​ but mine is simple and solid
mirfatif said:
NOTE:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources and according to best of my knowledge.
I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing. Whole device will be wiped.
REQUIREMENTS:
A PC with Windows and uninterrupted power supply. (I used Dell Inspiron 15R with Windows 8.1 and 10).
A USB data cable.
Fully charged phone, soft-bricked at maximum i.e. no recovery, no boot accessible
STEPS:
Download and Install NCS to your PC.
Copy UserGroupsConfiguration.cfg to "C:\Program Files (x86)\Nokia\Nokia Care Suite\Product Support Tool For Store 5".
Download Firmware and extract to "C:\ProgramData\Nokia\Packages\Products\RM-1013".
Launch NCS > Product Support Tool for Store 5.
At Sign-In screen, click Work Offline.
Disable Automatic Product Selection.
Go to File > Open Product and select RM-1013.
Click Programming > Recovery. Downloaded Firmware must be listed there.
Click Start and follow instructions. DO NOT INTERRUPT FLASHING PROCESS OR IT MAY HARD BRICK YOUR PHONE LEAVING IT USELESS.
Wait a few minutes and done. You have a newly purchased phone in your hands if all goes well.
Click to expand...
Click to collapse
Bro, i got an error with
Initializing WinUSB with device handle. The parameter is incorrect
Exception:
System.ComponentModel.Win32Exception (0x80004005): Initializing WinUSB with device handle. The parameter is incorrect
at Nokia.Merak.UsbDeviceIo.WinUsbIo.CheckError(Boolean expression, String message)
at Nokia.Merak.UsbDeviceIo.WinUsbIpen()
at Nokia.Merak.UsbDeviceIo.UsbDeviceIo..ctor(String devicePath)
at Nokia.Delta.Messaging..ctor(ConnectionDetails details)
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.ChangeDeviceMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
please help phone not booting
himanagendra said:
Bro, i got an error with
Initializing WinUSB with device handle. The parameter is incorrect
Exception:
System.ComponentModel.Win32Exception (0x80004005): Initializing WinUSB with device handle. The parameter is incorrect
at Nokia.Merak.UsbDeviceIo.WinUsbIo.CheckError(Boolean expression, String message)
at Nokia.Merak.UsbDeviceIo.WinUsbIpen()
at Nokia.Merak.UsbDeviceIo.UsbDeviceIo..ctor(String devicePath)
at Nokia.Delta.Messaging..ctor(ConnectionDetails details)
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.ChangeDeviceMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
please help phone not booting
Click to expand...
Click to collapse
You followed instructions 100%? Install NCS from my given link. It contains all necessary drivers including Emergency Driver. Use some other USB port on your PC. Try reinstalling NCS or try on different PC / different OS. You may also try QFIL if NCS doesn't work.
mirfatif said:
You followed instructions 100%? Install NCS from my given link. It contains all necessary drivers including Emergency Driver. Use some other USB port on your PC. Try reinstalling NCS or try on different PC / different OS. You may also try QFIL if NCS doesn't work.
Click to expand...
Click to collapse
thank god you are still there. okay here is the result.
Phone is not responding.
charging - > no indication, no screen
Volume down/up + power -> nothing. no response.
Do you know any softwares which can flash my phone without using volume up/down + power .
tnzzz for help
himanagendra said:
thank god you are still there. okay here is the result.
Phone is not responding.
charging - > no indication, no screen
Volume down/up + power -> nothing. no response.
Do you know any softwares which can flash my phone without using volume up/down + power .
tnzzz for help
Click to expand...
Click to collapse
Hmm it's hard bricked. No problem. Follow this thread. Things are explained more clearly there.
mirfatif said:
Hmm it's hard bricked. No problem. Follow this thread. Things are explained more clearly there.
Click to expand...
Click to collapse
thank you very much for your help but unfortunately it didn't work bcz as i told, nothing will comeup and even the buttons don't work.
In that case, please follow this thread
himanagendra said:
thank you very much for your help but unfortunately it didn't work bcz as i told, nothing will comeup and even the buttons don't work.
In that case, please follow this thread
Click to expand...
Click to collapse
Good. I suggested you to use QFIL already For me, both NCS and QFIL work but I didn't try any other product code firmware except 059V782 which is my device code.
What's your product code? 059V787 or 059V782? I'm gonna add a warning to my thread about this.
There are some devices which were officially updated from 2.1.0.11 to 2.1.0.12, so they don't support 2.1.0.13 as per my understanding.
mirfatif said:
Good. I suggested you to use QFIL already For me, both NCS and QFIL work but I didn't try any other product code firmware except 059V782 which is my device code.
What's your product code? 059V787 or 059V782?
Click to expand...
Click to collapse
Yeah...i thought you would give me a direct link. Anyways thanks for u help.
But bro, please mention that v2.1.0.13 don't suit for every Nokia x2 device. It doesn't suit the Indian version.
himanagendra said:
Yeah...i thought you would give me a direct link. Anyways thanks for u help.
But bro, please mention that v2.1.0.13 don't suit for every Nokia x2 device. It doesn't suit the Indian version.
Click to expand...
Click to collapse
Yes.
mirfatif said:
Good. I suggested you to use QFIL already For me, both NCS and QFIL work but I didn't try any other product code firmware except 059V782 which is my device code.
What's your product code? 059V787 or 059V782? I'm gonna add a warning to my thread about this.
There are some devices which were officially updated from 2.1.0.11 to 2.1.0.12, so they don't support 2.1.0.13 as per my understanding.
Click to expand...
Click to collapse
mirfatif said:
Yes.
Click to expand...
Click to collapse
Bro, do you know how to solve the sim 1 issue? i mean, my sim network is being recognized by the nokia x2 but, there is no signal for that.
himanagendra said:
Bro, do you know how to solve the sim 1 issue? i mean, my sim network is being recognized by the nokia x2 but, there is no signal for that.
Click to expand...
Click to collapse
Well, personally I never faced this issue. But you can try flashing @yoAeroA00 Custom Firmware. It flashes radio as well as other related partitions.
Quote:
Originally Posted by mirfatif
i cant find "C:\ProgramData\Nokia\Packages\Products\RM-1013".plz help me...
shuvo.khan97 said:
Quote:
Originally Posted by mirfatif
i cant find "C:\ProgramData\Nokia\Packages\Products\RM-1013".plz help me...
Click to expand...
Click to collapse
Create it if not found
Thx a lot, its helped me
Sent from my MI 5 using XDA-Developers Legacy app
For me please rm-1013:
2.0.0.11
059WOWO
thank you
how to connect mobile with pc in recovery mod or fast mod or normal mode i have custom rom and my sims are not working i want to stock rom again but when i select progmramming then recovery then there is no file shown in box for your information i attached img plz check and tell me the solution
lovegrw said:
how to connect mobile with pc in recovery mod or fast mod or normal mode i have custom rom and my sims are not working i want to stock rom again but when i select progmramming then recovery then there is no file shown in box for your information i attached img plz check and tell me the solution
Click to expand...
Click to collapse
Just flash stock rom zip before installing whole firmware
not able to get .xml file while flashing nokia x2
when i click on load xml in QFILL then i get new window but it shows no raw program file.
In reality it exist in extracted folder 'rm-1013 ' . When i type .xml in window it shows no file match.
please tell how to get this to proceed further.
Well, I f*cked up.
Fastboot works, I can flash stock rom via Xiaomi Flash. Flashing completes without any problems. A notification about encypting phone shows up, at 3% it jumps to 100% and resumes boot. Now after each boot, phone freezes at "input your sim pin" and reboots. Over and over again. What can I try, please help :
edited
twister26 said:
There is an reward for whoever helps me solve this issue
Click to expand...
Click to collapse
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
dfranco51207 said:
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
Click to expand...
Click to collapse
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
twister26 said:
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
Click to expand...
Click to collapse
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Let me guess. From Pie to Oreo or Nougat?
Mercoory said:
Let me guess. From Pie to Oreo or Nougat?
Click to expand...
Click to collapse
yes, exactly is there a thread already open somewhere here and i missed? last time TWRP was working, I even got a message "your system has been destroyed" or something like that.
sipollo said:
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Click to expand...
Click to collapse
will try!
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
ccalixtro said:
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
will give it a read, it it works, I'll PM you and you'll give me your paypal address. Fair is fair.
can't unlock OEM, because I can't boot up to developer tools. great, just great. will try to fix that first.
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
fdc77 said:
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
Click to expand...
Click to collapse
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
twister26 said:
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
Click to expand...
Click to collapse
i had a problem like yours, but i have flashed stock rom in non EDL mode and everything had start to work apart LTE band missing that i restored with qualcomm's tools
which stock rom have you try to flash? are you downgrading from oreo? bootloop on android one logo after downgrading is a common issue due to ARB (anti rollback protection)
twister26 said:
Whoever saves my precious Mi A1 gets 10$ on his paypal.
Click to expand...
Click to collapse
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
tropbel said:
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
Click to expand...
Click to collapse
reward is cancelled from this point on i will reward the one who helped me so far tho. still working on solving the problem so winner has not been decided yet.
you don't understand.
There are no winners and no loosers.
You are free to donate to anyone you want, but your post boost and encourages a bad attitude.
If people start to solve only paid problems, the spirit of the community will be destroyed.
The problem is with the Pie specific partition table
I write the whole guide from memory, so it can differ a bit.... I skipped some steps ( erasing, reboot, fastboot mode, TWRP loading via fastboot, OEM unlock )
From previous writings I think you can know the skipped steps.
Keep in mind: It is dangerous, you can loose your IMEI ( it will only work again with Pie - or there are some writings at forum how can you manually change it. ).
Steps:
1 - Backup with TWRP (fastboot) efs,persist,modem & make copy to your computer and or to your cloud provider.
2 - Create a new folder in Internal Storage -> TWRP -> BACKUP -> With a new date directory ( the backup already made one, make a new folder, with different date )
3 - Download someone's older TWRP backup from xda (I cheated, I copied the following links ) :
(I'm still a new user, so can't directly write url's )
Mediafire : https COLON SLASH SLASH bit.ly SLASH 2QU5NtC
Mirror: Google Drive : https COLON SLASH SLASH bit.ly SLASH 2UN1DTo
4 - Unpack, and copy EFS to the folder created 2 point
5 - Fastboot TWRP -> Restore EFS
6 - Flash the Official latest firmware from en.miui.com ( If you want to make sure go with EDL mode )
7 - Now, the IMEI & Mac addresses are missing. Don't panic! Download update with System Updates.
8 - When you are on Pie again, restore your first TWRP (fastboot) persist partition
9 - One more System restore
At this time, you will have IMEI & Mac addressees, and hopefully a working phone.
Hope this helps. The same thing happened with me 2 weeks ago. This is how I solves it.
Thank you, I solved it yesterday. Hopefully this post will come in handy for other people!
Hi, everyone I tried to flash a new recovery on X00T but before I did this I Wiped all the data except internal storage. I Flashed the new recovery (completely forget about there being no OS) I rebooted to recovery and ignored the no OS message as the device rebooted I came on a black screen even the fast boot mode screen was black. I had no idea what to do so I tried to install the old TWRP from power shell/Adl so I could have a recovery and then install Custom rom again from recovery.
But there when I try to flash a file with command
-> Fastboot flash Recovery ....(..= file name)
It is shown completed on pc but on android even after rebooting I can't get anything except the black screen. This is what I get when I enter the following commands
-> fastboot devices
My devices number is shown
but if I type.
-> adl devices
My device is not shown.
But when I press the recovery buttons on device adl devices Is able to recognise device as a recovery screen device.
And the extra bonus on this is when I try to flash rom or fimware from adl. It says unable to read zip file.
So can anyone tell me if there is a way to fix this unable to read zip file problem. (I have tried uninstalling and reinstalling drivers from device manager & tried installing 64 bit files also)
Is there a command to flash rom from recovery. Or any way to fix this black screen
Thanks to everyone for reading any advice would be really helpful at this time.
Try using Asus Flash Tool to flash stock ROM
Tianhe said:
Try using Asus Flash Tool to flash stock ROM
Click to expand...
Click to collapse
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?
Xda user 101 said:
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?
Click to expand...
Click to collapse
I am not sure if posting external links (except hosting sites) is permitted. A simple google search or search within XDA will give you the results. In case you face difficulty, PM me.
Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though
Vysair said:
Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though
Click to expand...
Click to collapse
Bro tried as you said but didn't worked but finally found a solution. Now device is on and working again.
If anyone else face this issue I followed this thread https://forum.xda-developers.com/as...uide-revert-to-stock-rom-lock-t3798420/page46
It worked on my phone it is on again. Will have to root again but learned my lesson will never try new twrp when there is no os installed. :laugh:
thanks you Tianhe and Vysair for your advice for solving the issue.