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.
Related
Hi there,
I am pretty new with this stuff, as I just got this phone today. It came with Froyo2.2 so I unrooted it back to the original JFK.
It did not come with a sim card, so I do not have a sim inside the phone as of now. But I do have a bell sim that I will use after to put the unlock key in... Is that okay?
I Connected the vibrant through Mini Kies and the MTP application says its connected.
I just re rooted from J16 back to the original.
I have the 64 bit drivers installed.
When I try to run Generate Unlock Windows Script I get the following error message saying...
Copy nv_data.bin
*daemon not running. Starting it now *
*daemon started succesfully *
error: device not found
error unable to find file <.\nv_data.bin>
could not find C:\documents and settings\1\desktop\key\generateunlockwindows\nv_data.bin
Anyone know what this means?
Or know what to do in this situation?
I am not sure if I should try installing the 32bit drivers or what.
how did you downgrade the phone from android 2.2?
I just bought the phone through ebay with the OS already at 2.2, and the phone is locked to t-mobile. I've heard it is not possible to unlock it with the 2.2 update. Is that true?
molson24 said:
Hi there,
I am pretty new with this stuff, as I just got this phone today. It came with Froyo2.2 so I unrooted it back to the original JFK.
It did not come with a sim card, so I do not have a sim inside the phone as of now. But I do have a bell sim that I will use after to put the unlock key in... Is that okay?
I Connected the vibrant through Mini Kies and the MTP application says its connected.
I just re rooted from J16 back to the original.
I have the 64 bit drivers installed.
When I try to run Generate Unlock Windows Script I get the following error message saying...
Copy nv_data.bin
*daemon not running. Starting it now *
*daemon started succesfully *
error: device not found
error unable to find file <.\nv_data.bin>
could not find C:\documents and settings\1\desktop\key\generateunlockwindows\nv_data.bin
Anyone know what this means?
Or know what to do in this situation?
I am not sure if I should try installing the 32bit drivers or what.
Click to expand...
Click to collapse
Yup, having exact same problem. If you find a fix let me know.
Make sure your usb setting is on debug and you have all of the files for the unlock on your pc. You also need java installed.
That method worked for me from stock.
can someone answer my question?
mbison83 said:
how did you downgrade the phone from android 2.2?
I just bought the phone through ebay with the OS already at 2.2, and the phone is locked to t-mobile. I've heard it is not possible to unlock it with the 2.2 update. Is that true?
Click to expand...
Click to collapse
I don't know whether the unlock methods work with Froyo but you can download a 2.1 stock Odin in the forum.
pvspencer22 said:
I don't know whether the unlock methods work with Froyo but you can download a 2.1 stock Odin in the forum.
Click to expand...
Click to collapse
where can i get it at and how do i do the rollback?
mbison83 said:
can someone answer my question?
Click to expand...
Click to collapse
...... please?
koooba said:
...... please?
Click to expand...
Click to collapse
very funny.
mbison83 said:
very funny.
Click to expand...
Click to collapse
Wasn't meant to be. Usually please and thanks goes a long way when asking for something. Shows appreciation.
^ Hence the THANKS button.
koooba said:
Wasn't meant to be. Usually please and thanks goes a long way when asking for something. Shows appreciation.
Click to expand...
Click to collapse
it also shows sarcasm and in this case thats what is seems like.
Read the stickies in the forum. If you can't figure it out ill grab the links tonight.
For the unlock this worked for me.
pvspencer22 said:
The windows tool worked for me from stock.
It doesn't generate a code though you input one.
Edit: link
http://forum.xda-developers.com/showthread.php?t=822008&page=11
Scroll down for instructions.
Click to expand...
Click to collapse
For going to stock. (From the general stickie)
draikz said:
Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO JUSTANOTHERCROWD):
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.[/S
Click to expand...
Click to collapse
I unlocked my phone w Galaxy_S unlock 2 days ago. It's in the market and I was running Bionix V when I did it.
draikz said:
^ Hence the THANKS button.
Click to expand...
Click to collapse
Pretty soon we'll have apps that'll say hi and thanks and apps in general will replace everything we say, so much for what our parents taught us huh?
koooba said:
Pretty soon we'll have apps that'll say hi and thanks and apps in general will replace everything we say, so much for what our parents taught us huh?
Click to expand...
Click to collapse
Technology > your parents.
Anyday.
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
franjess said:
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
Click to expand...
Click to collapse
Poor with a few hundred dollars worth of phone. Lol
Did you try the PRO SGS app?
franjess said:
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
Click to expand...
Click to collapse
If you want help you are going to have to be a lot more specific. What have you actually tried?
Just a tip, people will not help you on these forums if you ask for help without showing you've tried to solve the problem and know how to search.
There are loads of unlock threads. Almost everyone get one method to work eventually.
Hello There!!
I was trying to get back to stock rom
And Always Getting this no space error 5069 While Flashing
After searching i found that format will fix this and i can flash like a charm
But after formatting my Device Is dead
no boot, no charging, no recovery
I'm Trying TO whole flash but I'm there is no option for that only Getting without bootloader one
Then i've checked it memory in memory test option now i'm getting
Nand Flash Not Detected
Plz!!! tell me what i can do to take my phone back to life
The Phone is out of warrenty
Same thing happend with me.
Use format+download all in SPFlashTool (with the same stock ROM), then do a firmware upgrade in SPFT with the same ROM.
Shahbaz23 said:
Use format+download all in SPFlashTool (with the same stock ROM), then do a firmware upgrade in SPFT with the same ROM.
Click to expand...
Click to collapse
Thanks for replying, i almost lost my hope of fixing this problem
Now after trying it says:
1) after format+download it says no space error
2)then i tried firmware upgrade i'm getting " Failed to get PMT info " and "Invalid partition table" error in spft v3.xx
I've found many users are facing this problem, if it will fix here it will be great help for them
Just tell me what to do next
lexileone said:
Thanks for replying, i almost lost my hope of fixing this problem
Now after trying it says:
1) after format+download it says no space error
2)then i tried firmware upgrade i'm getting " Failed to get PMT info " and "Invalid partition table" error in spft v3.xx
I've found many users are facing this problem, if it will fix here it will be great help for them
Just tell me what to do next
Click to expand...
Click to collapse
K, Try this for a change...
Assuming u already have all the required drivers installed (get it via google search, if not), use the latest sp flash tool (it does matter), browse your scatter file (i recommend u use the Stock JB/KK/LP) and goto the format tab (next to the download tab) and do an auto format. Now goto the download tab and do a format all+download and finally firmware upgrade (all this without the battery)... Now start your phone. This works fine for me when my phone get soft-bricked. However u must remember that formatting all may have risk of your NVRAM getting formatted and so loss of IMEI, but you can always have it fixed via AT command.
Shahbaz23 said:
K, Try this for a change...
Assuming u already have all the required drivers installed (get it via google search, if not), use the latest sp flash tool (it does matter), browse your scatter file (i recommend u use the Stock JB/KK/LP) and goto the format tab (next to the download tab) and do an auto format. Now goto the download tab and do a format all+download and finally firmware upgrade (all this without the battery)... Now start your phone. This works fine for me when my phone get soft-bricked. However u must remember that formatting all may have risk of your NVRAM getting formatted and so loss of IMEI, but you can always have it fixed via AT command.
Click to expand...
Click to collapse
Thanks for replying :cyclops:
I was using spft ver 5.1516.00
while auto format i was getting errors, in v5 it says BROM ERROR: S_DL_READ_PT_FAILE(5073), only v3.1328 can format it successfully while others v3 are getting invalid range error[I think this place will give some clue of what's happening]
ok then in format+download section( using spft V5)
format 100%
boot loader 100%
just after few seconds again no space error
Now in firm-upgrade section
again error failed to get pmt info
thanks for trying mate
now I have some hope for this device to be fixed
i'm not worrying about imei
anybody there plz bring my phone back to life
Help Guys I'm waiting for Ur Replies
PLzz!!
lexileone said:
Help Guys I'm waiting for Ur Replies
PLzz!!
Click to expand...
Click to collapse
Given your desperate condition, go with this:
Re-install the drivers and spftool from here: http://d-h.st/7CL
Use a different USB wire (maybe your I/O port of USB wire is damaged, happened with me once).
Then retry the method listed above of formatting, downloading and upgrading.
Hope this helps.
P.S.: I am not an expert so I couldn't understand the errors, but looks like these are common errors so you should get your phone back alive. :good:
Shahbaz23 said:
Given your desperate condition, go with this:
Re-install the drivers and spftool from here: http://d-h.st/7CL
Use a different USB wire (maybe your I/O port of USB wire is damaged, happened with me once).
Then retry the method listed above of formatting, downloading and upgrading.
Hope this helps.
P.S.: I am not an expert so I couldn't understand the errors, but looks like these are common errors so you should get your phone back alive. :good:
Click to expand...
Click to collapse
still getting invalid Pmt error on firm upgrade
and no space in download
plz help
Facing the exact same problem with my phone too.. Someone please help.
Is there any senior members who can help us?
Make full format (including calibration data & boot loader) then flash with jellybean
Auto format not make full format some data is not earse . make full format then flash with jellybeam stock rom
(Use latest sp flashtool
Without battery
Check Usb pin & cable are rightly connected )
Chinmayhegde said:
Auto format not make full format some data is not earse . make full format then flash with jellybeam stock rom
(Use latest sp flashtool
Without battery
Check Usb pin & cable are rightly connected )
Click to expand...
Click to collapse
But how
i can't see format with bootloader option in format tab
Is there Any other way to do this(may be manual format will work, but dont Know How to do)
This problem needs to be solved
Well thanks for trying
I hope we will get rid of this problem soon
lexileone said:
But how
i can't see format with bootloader option in format tab
Is there Any other way to do this(may be manual format will work, but dont Know How to do)
This problem needs to be solved
Well thanks for trying
I hope we will get rid of this problem soon
Click to expand...
Click to collapse
are you triad manual format including calibration data?
Chinmayhegde said:
are you triad manual format including calibration data?
Click to expand...
Click to collapse
Yes, the format was successful but still get same errors while downloading
PLz guyz Help !!!
lexileone said:
Yes, the format was successful but still get same errors while downloading
PLz guyz Help !!!
Click to expand...
Click to collapse
Change your stock rom for flashing kitkat or jellybean / wiko_rainbowlollipop official stock rom
use older spflash tool
then also u get same error service center is a batter option
Chinmayhegde said:
Change your stock rom for flashing kitkat or jellybean / wiko_rainbowlollipop official stock rom
use older spflash tool
then also u get same error service center is a batter option
Click to expand...
Click to collapse
In service center people are saying its board fault and it have to be replaced (pricing 3K)
But i'm sure the board is working
its any other problem
Have u tried both versions of sptools .format and download should work.try a different cable.if nothings working try adb from pc
micromax a120 1931 said:
Have u tried both versions of sptools .format and download should work.try a different cable.if nothings working try adb from pc
Click to expand...
Click to collapse
Thankz tell me more about adb from pc
lexileone said:
Thankz tell me more about adb from pc
Click to expand...
Click to collapse
1. Download SP flash tool (I think you already have) and Smartphone multiport download tool = http://www.mediafire.com/?1ycvu9ywv7vjnhv.
2. Open and run as admin - SPMultiPortFlashDownloadProject.
3. Click file, open download agent name' and add 'MTK_AllInOne_DA.bin'.
4. Open factory database and select the .mdb file.
5. Click scatter file - and select the .txt scatter file.
6. Then the 'top three boxes (LCD and camera driver) . You click last - ???????? button and unlock it for changing driver parameters.
7. Remember the 1st box for back camera, 2nd box for front camera, 3rd box for display driver.
8. My recommended :
under sensor 1 selectv5647_raw
under sensor 2 select:hi704_yuv
under sensor 3 select:T050UWV014NS or if it doesnt work LM050AMYBO1E
(if doesnt work change again and again)
9. Select high speed and no battery (I think no need to do).
10. Simply close the Tool. then open, SP flash tool
11. Select scatter loading, and load the same 'scatter file' , which you previously opened in the 'multiport download tool'
12. SELECT 'UBOOT' ONLY AND NOT SELECT OTHER ALL PARAMETERS. THEN CLICK DOWNOAD.
Then reboot your phone and check... display is ok ?
If not ok, Then again open smartphone multiport download tool and change the display driver and do the same all things previously.
You have to do repeatly, until, you are getting display normal.
The same thing for camera's working also. Do this ..I doubt adb will work just temme if it fixes it...
I've been trying almost everything for days. When I turn on the phone the bootloader enters in a loop.
I can't access to recovery (vol up + power), not even in update mode(vol up & vol down + power).
The only thing I can access is the fastboot but my phone is locked and I don't the have the imei to unlock via calculator or the oficial huawei page.
If someone have any suggestions.
Instalar ROM vía fastboot
Sent from my ALE-L21 using XDA-Developers Legacy app
VicenteR93 said:
I've been trying almost everything for days. When I turn on the phone the bootloader enters in a loop.
I can't access to recovery (vol up + power), not even in update mode(vol up & vol down + power).
The only thing I can access is the fastboot but my phone is locked and I don't the have the imei to unlock via calculator or the oficial huawei page.
If someone have any suggestions.
Click to expand...
Click to collapse
If getting your IMEI is your only concern then you can get that from the box... But you'll need Product ID too, and for that you'll need to have your phone booted up...
amageek said:
If getting your IMEI is your only concern then you can get that from the box... But you'll need Product ID too, and for that you'll need to have your phone booted up...
Click to expand...
Click to collapse
There is a program for that. Huawei product id generator. You can find this program very easy.
amageek said:
If getting your IMEI is your only concern then you can get that from the box... But you'll need Product ID too, and for that you'll need to have your phone booted up...
Click to expand...
Click to collapse
when you mean the box. Is the box where I bought the phone? 'Cause I don't have it anymore and is not even behind the battery.
VicenteR93 said:
when you mean the box. Is the box where I bought the phone? 'Cause I don't have it anymore and is not even behind the battery.
Click to expand...
Click to collapse
Yes that box.. There may be other way too, I'll look into it and share is I find anything
Fedroid said:
Instalar ROM vía fastboot
Sent from my ALE-L21 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I downloaded the official ROM from huawei and is the recent version but when I tried to install it with "fastboot update file.zip" is asking for an android-text.txt and I been searching to re-create that file manually and then is asking for another file and so on.
I've been searching if I can install the oficcial ROM by fastboot even if is not unlocked and find this guide but it is not usefull for me 'cause I can't access into the download mode or use adb.
This is the information I could extract from my phone.
Firmware : ALE-L21C109B130
I couldn't fint this version of firmware.
If you could light my way if you have another method.
VicenteR93 said:
I downloaded the official ROM from huawei and is the recent version but when I tried to install it with "fastboot update file.zip" is asking for an android-text.txt and I been searching to re-create that file manually and then is asking for another file and so on.
I've been searching if I can install the oficcial ROM by fastboot even if is not unlocked and find this guide but it is not usefull for me 'cause I can't access into the download mode or use adb.
This is the information I could extract from my phone.
Firmware : ALE-L21C109B130
I couldn't fint this version of firmware.
If you could light my way if you have another method.
Click to expand...
Click to collapse
Extract files and flash it one by one using fastboot commands
I recommend you watch this video even if it is in Spanish, it can help you
,is from
EloYGomeZTv:good:
Sent from my Huawei P8lite/P8 Lite using XDA Labs
Fedroid said:
Extract files and flash it one by one using fastboot commands
Click to expand...
Click to collapse
Everything failed when tries to write 'cause the bootloader is locked.
davidlikeandroid23 said:
I recommend you watch this video even if it is in Spanish, it can help you
,is from
EloYGomeZTv:good:
Sent from my Huawei P8lite/P8 Lite using XDA Labs
Click to expand...
Click to collapse
I already saw a tutorial like this one but my bootloader is locked and I don't have the imei to unlock it. But thanks anyway.
VicenteR93 said:
I already saw a tutorial like this one but my bootloader is locked and I don't have the imei to unlock it. But thanks anyway.
Click to expand...
Click to collapse
Ok i searched for ways to find an IMEI number and found couple of ways...
1) Look under/in the sim tray. It may be there (I didn't check this out)
2) Find the IMEI/MEID using Google Dashboard. This is Google's control center that can be accessed from any computer with a web browser. You will need to log in with the Google account associated with your Android phone.You can access Google Dashboard by visiting www.google.com/settings/dashboard Expand the "Android" section by clicking the "Android" heading.Locate your phone in the list. If you have multiple devices associated with your account, all of the devices will be displayed. Find the device that you are trying to retrieve the IMEI/MEID number for. (This works)
3) At last, you can try to remove the back case and remove the battery. This can help you in 2 ways. Firstly, there should be IMEI code present under the battery. Secondly, this may cause you to get out of bootloop
amageek said:
Ok i searched for ways to find an IMEI number and found couple of ways...
1) Look under/in the sim tray. It may be there (I didn't check this out)
2) Find the IMEI/MEID using Google Dashboard. This is Google's control center that can be accessed from any computer with a web browser. You will need to log in with the Google account associated with your Android phone.You can access Google Dashboard by visiting www.google.com/settings/dashboard Expand the "Android" section by clicking the "Android" heading.Locate your phone in the list. If you have multiple devices associated with your account, all of the devices will be displayed. Find the device that you are trying to retrieve the IMEI/MEID number for. (This works)
3) At last, you can try to remove the back case and remove the battery. This can help you in 2 ways. Firstly, there should be IMEI code present under the battery. Secondly, this may cause you to get out of bootloop
Click to expand...
Click to collapse
You're the best Sir, the holy ruler!!!
I finally found it. With the option 1.
I checked to the second option and it was there too. Didn't know that option.
Thank you so much.
VicenteR93 said:
You're the best Sir, the holy ruler!!!
I finally found it. With the option 1.
I checked to the second option and it was there too. Didn't know that option.
Thank you so much.
Click to expand...
Click to collapse
Cheers... Now you may proceed further.. Do tell us about your methods/steps/processes for future reference...
Did you try installing hisuite to a windows machine there is a recovery option on it it will install the LATEST emui ROM to your phone and recover it.
http://consumer.huawei.com/minisite/HiSuite_en/index.html
Edit: if I remember correctly you just have to be in fastboot to recover it
ndg_2000 said:
Did you try installing hisuite to a windows machine there is a recovery option on it it will install the LATEST emui ROM to your phone and recover it.
http://consumer.huawei.com/minisite/HiSuite_en/index.html
Edit: if I remember correctly you just have to be in fastboot to recover it
Click to expand...
Click to collapse
I tried but at the end it tells me that I need to take the phone to the nearest center.
I downloaded a lot of ROM to try but I'm still trapped in the boot loop.
I tried all the solutions that has been posted before.
VicenteR93 said:
I downloaded a lot of ROM to try but I'm still trapped in the boot loop.
I tried all the solutions that has been posted before.
Click to expand...
Click to collapse
Have you managed to get the boot loader unlocked if not you need to tackle that first then your recovery options open up some what
ndg_2000 said:
Have you managed to get the boot loader unlocked if not you need to tackle that first then your recovery options open up some what
Click to expand...
Click to collapse
I already unlocked the bootlooader but I still have the boot loop even after pass cust, system, recovery, boot.
VicenteR93 said:
I already unlocked the bootlooader but I still have the boot loop even after pass cust, system, recovery, boot.
Click to expand...
Click to collapse
Stupid question but I will ask it anyway did you md5 check all of the files you have downloaded as I have had issues with another device and it was because of bad files
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
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.