Related
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...
Hurray! Finally, I fix the touch calibration issue; many many thanks to God who showed me the right path.
After suffering hard in last 15 days, even not getting any help from YU Officials, finally God bestowed upon me his blessings and provided me the hint to fix the issue.
What caused the Issue?
YU Televentures recently released a new batch of Yureka Plus (YU5510A-LP) devices with VoLTE feature. This created a storm in Yureka /Plus section of the forum. Some users even bricked after flashing the new firmware since it was totally different from the previous Yureka firmware. I got the backup of /system and /boot from a YU5510A-LP user. I deodexed the files and made a ROM out of it and flashed on my device to test whether it boots or not (a common process of ROM porting). It didn’t boot but it went beyond the boot logo and since the Kernel of YU5510-A didn’t have the correct display drivers for AO5510, I was getting strange characters on the screen. After that I rebooted to TWRP recovery. I was shocked the touch was malfunctioning. If I touch up it was working down, it was totally a mess.
This issue is much dangerous than bricking the device. Even if we brick, we may recover it by following @ricks guide, but with malfunctioning touchscreen phone is utterly useless. It can’t be fixed even after flashing the EMMC backup.
After that I reported to the YU Officials about the touch calibration issue, they didn’t provide any fix, but created a Warning thread regarding it. So sad.
They were even not ready to provide me the touch firmware of Yureka AO5510. They told me that they are also trying to find the cause of touch calibration issue and don’t have the required files. Here is the quote of the reply from YU Officials:
I am afraid that we don't have any files for fixing the issue. To make sure that such thing does not happen we internally test every case before releasing the software. In your case, you got the software from unknown sources and flashed it on your device with your own consent and understanding. Yes, we have devs but they work on cases which have higher reproducibility rate like the proximity sensor issue.
Click to expand...
Click to collapse
After that I analysed the YU5510A-LP VoLTE firmware and found that it was created by Coolpad, a Chinese Smartphone Company. So YU Televentures has imported not only the smartphone (YU5510A-LP) but also the firmware from Coolpad. That’s why it has some unknown bugs which the YU Offical Devs don’t know because they haven’t made the firmware. That’s why the devs didn’t have fix for touch calibration issue. YU is spending very less on service and devs, which very much disappointing. YU, an Indian brand made Yureka for tech freaks and that’s why so many devs engaged in it and even some noobish users like me became devs to raise the company above cheap Chinese brands. But now it’s status is deteriorating, it broke its partnership with Cyanogen and lost the support of so many great devs; and now it is left with some official noobish devs who are taking time like hell to provide a VoLTE patch for other users, this shows how irresponsible is the YU Company. And now it has already been provided by a YU Forum user. Even the Official YU OS is provided by our friend dev @AudioGod.
I hope my above words reaches to the YU Company and they take this criticizing in the right way and improve itself. I want to see this Indian Company rise beyond heights.
After lot of analysis and research I found that the cause of touch calibration issue was the kernel of YU5510A-LP ROM. It changed the TP-Firmware version and touch parameters of Yureka AO5510 (HD) according to Yureka YU5510A-LP (FHD) device and messed up the calibration.
This TP firmware is different in Yureka and Yureka Plus and it never changes after flashing any firmware (fastboot or ROM).
Yureka AO5510 : Each:GT970:0x1039:0x46
Yureka Plus YU5510 : Ofilm:GT970:0x1039:0x48
And mine was : Each:GT970:0x1039:0x47
Yureka (Plus) Touch Panel is manufactured by Goodix, a Chinese Touch Panel and Fingerprint Sensor company.
What didn’t fix the issue?
These are the things which didn't fix the calibration issue:
[/SIZE]
Flashing stock COS 12.1 ROM through recovery
Flashing COS 12.0/12.1 fastboot firmware
Flashing COS 12.0 CPB using YGDP tool (which threw an error of incompatible device before flashing)
Flashing all other partitons (=EMMC backup)
Using Annabathina’s Yureka Unbricking Tool
How did I find a Fix?
While surfing through internet I found a way to check the touch firmware version. Then I checked mine and also asked about it from other Yureka users. Then I searched about the firmware version and got an XDA Thread and also got to know about Goodix Touch Firmware and Goodix Firmware Upgrade Tool (GTP ADB Tool) from Elephone (another Chinese company) forum which I didn’t get from YU.
I read the XDA thread learned about the whole thing and created a Goodix TP Firmware/Config myself.
How to Fix Yureka AO5510 Touch Calibration Issue?
STEP 1: Download GtpAdbToolV1.7_20140424.zip and GT970_1039_AO5510-TP-Firmware.zip on your Windows PC and extract it. Go to the extracted folder of Gtp Adb Tool and run the GtpAdbTool.exe application. Then connect you YUREKA AO5510 to your PC (be sure USB debugging is enabled in your device). You will see the GTP ADB Tool window similar to the screenshot below:
STEP 2: Now click on the button as indicated in the screenshot below and navigate for the GT970_1039_AO5510-TP-Firmware.cfg file (that you extracted in Step 1) and select it.
STEP 3: Then click on the button indicated in the screenshot below to execute firmware upgrade process. Once completed, you can unplug your device and reboot. Voila touchscreen issue fixed!
NOTE (Important):
If the GTP ADB Tool doesn't detect your device or TP firmware, then flash any of the following ROMs:
Official Lineage OS ROMs
Hexagon ROM by @MoreSushant48
Or any other ROM
OR
Go to TWRP Recovery and mount all the partitions. Then connect your phone to the PC. It should detect.
If any of the above methods doesn’t work then try flashing
CoolUI 6.0 for YUREKA (Test build): https://www.androidfilehost.com/?fid=457095661767103935
(After flashing this ROM you may see a 'root' indication on YU LOGO, but you can fix that using Annabathina's Tool)
Important Files
GTP ADB Tool: https://www.androidfilehost.com/?fid=385035244224387037
YUREKA AO5510 TP Firmware: https://www.androidfilehost.com/?fid=385035244224387256
More information: https://www.osbusters.net/2016/10/fix-yureka-ao5510-touch-calibration-issue.html
Credits
Special thanks to @iamreal2 (XDA member) and @Ethan (Elephone forum member)
Special thanks to @darshan1205, @ricks and @Men_in_black007 who supported me in bad times
Special thanks to @manis99 for providing me YU5510A-LP VoLTE Firmware
Special thanks to @prasoon Mehra for providing me original Yureka AO5510 TP Config.
And finally thanks to me for making this fix.
Original TP Firmware Files for Different Devices
These are Original Stock Touch Panel Firmware/Configs for users who are suffering calibration issue not due to VoLTE firmware but due to other unknown causes.
YUREKA (AO5510) : https://www.androidfilehost.com/?fid=457095661767104421 (Thanks to @Prasoon Mehra)
YUREKA PLUS (YU5510) : https://www.androidfilehost.com/?fid=385035244224388338 (Thanks to @darshan1205)
Users of other YU Devices may share their working TP Firmware to help others....
Mirror Links
https://mega.nz/folder/Z4ckFbDA#bw4HnjUntLbiOLcdT-qpLQ (MEGA)
[Guide] How to Backup or Edit Touchscreen Firmware using GTP ADB Tool (For all devices with Goodix touchscreen)For users of all devices. Backing up the current TP-firmware is useful for saving the device from any future accident.
STEP 1: Download GTP-ADB-Tool Zip on your Windows PC and extract it. Go to the extracted folder and run the GtpAdbTool.exe application. Then connect your smartphone to your PC (be sure USB debugging is enabled in your device). You will see the Gtp Adb Tool window similar to the screenshot below:
STEP 2: Now click on the Menu item as indicated in the screenshot below:
STEP 3: Now you will see a window similar to the screenshot below. Click on the indicated button to read the current TP configuration from your connected device.
STEP 4: Hereafter you will see a window similar to the screenshot below. Take a screenshot of your current window and click on the button indicated to export your current config. Save the resultant config file to your preferred place. Thereafter, if required, you can also edit the firmware by playing with the Hex values.
STEP 5: Upload the Screenshot and your exported config file and save it in a safe place. That's it.
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
shailesh1985 said:
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
Click to expand...
Click to collapse
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
shailesh1985 said:
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
Click to expand...
Click to collapse
I am glad that it worked for you...
BTW you better use TWRP Recovery to flash newer ROMs. CWM Recovery is very old and is abandoned and deprecated.
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
dhrtlockeroo9 said:
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
Click to expand...
Click to collapse
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
nitesh9
nitesh9 said:
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
dhrtlockeroo9 said:
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
Click to expand...
Click to collapse
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
dhrtlockeroo9 said:
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
Click to expand...
Click to collapse
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
nitesh9
nitesh9 said:
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
nitesh9 said:
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
dhrtlockeroo9 said:
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
Click to expand...
Click to collapse
Tried using OTG mouse?[emoji15]
nitesh9 said:
Tried using OTG mouse?[emoji15]
Click to expand...
Click to collapse
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
dhrtlockeroo9 said:
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
Click to expand...
Click to collapse
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
nitesh9 said:
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
Click to expand...
Click to collapse
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
dhrtlockeroo9 said:
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
Click to expand...
Click to collapse
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
nitesh9 said:
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
Click to expand...
Click to collapse
No it's KitKat version.
dhrtlockeroo9 said:
No it's KitKat version.
Click to expand...
Click to collapse
Still you are getting bricked now and then?
What are you flashing actually?
Discussion on problems faced by Miflash tool.
*So when used for the first time I was able to unlock phone without any problem.
*But after that when I used it for second time to unbrick my phone I was constantly getting errors like not enough memory,some errors like x800000 blah blah...
*I almost went through every solutions mentioned in miui forum and XDA...But I was unable to get it working...
So if anyone faced any problem like that comment your problem below..
Aftef a lot of research I was able to find a solution for that..
Hopefully it will be shared with you all as soon as possible. I have to finish touching up some final things..
As soon as I finish the work I will be releasing alpha version..
Will update the thread when I release it
Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group
Murshad007 said:
Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group
Click to expand...
Click to collapse
Hopefully I was able to make alpha version of the software...worked fine for me on fastboot mode..want some testers
Edit..was able to boot up successfully..once confirmed by some testers I will release stable one
I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).
exce1ia said:
I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).
Click to expand...
Click to collapse
Yeah I faced it many time...not enough memory, buffer size0000 error blah blah blah...hopefully I was able to develop an app for to unbrick via fastboot... tried by me 2 times worked smooth but need some testers
Mi Flash & Nougat
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much
cleo1986 said:
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..
No fastboot
adithyan25 said:
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..
Click to expand...
Click to collapse
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can recognize it as Qualcomm device.
cleo1986 said:
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can
recognize it as Qualcomm device.
Click to expand...
Click to collapse
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then
Already TRIED
adithyan25 said:
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then
Click to expand...
Click to collapse
I already tried many times to flash in EDL via miflash but I have error 0x000..., hello packet, etc etc
PLEASE LET ME KNOW WHEN YOU HAVE EDL Tool!
Thank you very much
Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?
Rapalax said:
Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/how-to/fix-bootloop-redmi-note-3-recovery-edl-t3521297
This will work for a complete clean flash via edl
Yep.. I managed to do something similar with a newer FB ROM and the modded twrp so there is less chance to relock my BL.
Thanks for providing the post.. it makes me feel more comfortable knowing that this info is available in case I need it again
Hi Guys.
This is a Mediatek Helio X25 Redmi Pro and it came to me bricked from its owner who tried to root it the wrong way. I managed to flash an official rom and bring it back to life but as apparently is the case with these phones, the nvram has been corrupted/rewritten and there's no Imei numbers on the phone, which means no calls and stuff. WiFi works fine. I've already had permission to unlock the bootloader but obviously I can't do anything about it since the software won't ID the device. I believe I might be able to flash a backup of nvram.bin, but I don't have one from this phone, which is why I am posting this here, hoping that maybe one of you can help me by sending me a copy of his own Redmi Pro nvram.bin file. Of course I only need it to get the thing back in the system, after which I can unlock it and use the original Imei numbers. Or if someone has another suggestion, I would greatly appreciate it.
Thanks in advance.
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Binnylaw said:
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Click to expand...
Click to collapse
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
nsterjo said:
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
Click to expand...
Click to collapse
Tried this method?
http://en.miui.com/thread-411112-1-1.html
Sent from my Redmi Note 4 using Tapatalk
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Binnylaw said:
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Click to expand...
Click to collapse
I have tried maybe 3 different versions of Sp Flashtool, including this one. I usually get a timeout message. But I will try again. Is there any specifics I should observe regarding the mdb files I need to use? I have tried all the ones that come with the roms I've tried, but without luck.
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
No, you understood fine; it was me who typed SP Flashtool instead of SN Writer, which was what I meant. Everything else is as I wrote. I have tried 3 different versions of SN Writer, I connect fine and it starts the procedure following the same instructions you mentioned, but it stops half way, giving me an error message. I have tried different combinations of MDB and APDB files from several different ROMs I've downloaded, but they all fail. I'm not very familiar with these things but I can follow instructions and am quick to learn. Still, I have no idea why SN Writer or Maui Meta are not working. I tried to download an nvram.bin file I got from the internet with SP Flashtool, but it would not accept it as it was for Helio X20 I believe, which is why I was hoping someone would make available a copy of nvram.bin for this particular phone. I will also try to make a deepflash cable, hoping that might get me into EDL after which I can use MiFlash to reflash a new official Rom, but I don't know if it will work.
help please
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
Hi there, please can you tell me where I find the files (mdb and adb)? Are they somewhere on the phone's firmware? Or somewhere in the rom i flashed?
I'm a beginner having a very similar issue having flashed a rom in rescuing a bricked phone and now have invalid IMEI numbers.
Thanks so much
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.