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?
Related
Hey Guys,
I hardbricked my phone by flashing 5.0 with flashfire...
Can someone help me, and give me a clear instruction what to do?
I can´t boot it; Recovery/Download Mode doesnt work.
In my device manager it only shows " QHSUSB_BULK ".
The firmware i flashed: usp-forum.de/downloads.php?do=file&id=2431
Thank you
i hardbricked my phone the same way lol..did you found fix? i hate samsung when it comes to flash new rom....
Kristijan4o said:
i hate samsung when it comes to flash new rom....
Click to expand...
Click to collapse
Just lol. Definitely not Samsung's fault. The 9005 is hard to brick, only user error is the culprit.
Sent from my Galaxy Note 8 using XDA Labs
User needs to post information if any progress is to be made.
Download mode ??
Recovery mode ??
Nandroid backup ??
NO roms on here say use Flashfire do they ??
i've flashed devices before, htc, lg and other brand, but samsung are the hardest one to understand lol...
btw no download mode, there is no recovery, no backups..just dead phone..my windows 7 reads the phone in device manager like: qhsusb_bulk...cant find any drivers for that...cant pass in odin too..i tried debrick.img method, nothing worked so far..last i was using twrp with 5.0.wont..i think its eMMC...
If the following approach works, un-brickable Note3 can be claimed.
https://forum.xda-developers.com/ga...cked-n9005-t3548946/post76958736#post76958736
I don't want to be rude but I am starting to get a little annoyed with same questions repeating over and over on all threads so i decided to post some answers here where they could be easily accessed.
1. Q:""Can i flash this Marshmallow/Lollipop/Nougat rom over my stock KitKat?"
A:The answer in most cases is that you cant (except in ED300 CM12.1 Rom but its still preferred that you flash stock Lollipop firmware separately).For those who don't want to waste their time flashing Stock rom there is an alternative flash-able zip could be found here
- http://forum.xda-developers.com/len...itkat-lolipop-firmware-base-switcher-t3249046 - for A6000
- http://forum.xda-developers.com/lenovo-a6000/how-to/firmware-base-switcher-a6000-plus-t3411914 - for A6000 Plus.
2.Q:"Where can i find TWRP recovery for my firmware?"
A:Here you go
- http://forum.xda-developers.com/lenovo-a6000/how-to/twrp-development-wt86518-t3498524 - Lollipop/Marshmallow/Nougat recovery developed by TingyiChen
- https://drive.google.com/drive/folders/0B2xkkOmw_M2NNXlVYnFYZnRIZHc?usp=sharing - made by SevenMaxs
TWRP 2.8.6.1 Is KitKat only compatible recovery
TWRP 2.8.7.7 Is Lollipop only compatible recovery
TWRP 3.0.2.0 Is Lollipop/Marshmallow/Nougat compatible recovery
*I couldn't find official links so i uploaded files to my google drive if any developer has a problem with this he can DM me and i will update the links *
3.Q:"Does this rom support VoLTE?"
A:So long there isnt a rom that supports VoLTE (As far as i know).There is some lib or source code problem with VoLTE (idk i am not a developer).There is a thread about this topic here - http://forum.xda-developers.com/lenovo-a6000/help/lenovo-a6000-plus-volte-support-t3418004 -
4.Q:"Does this rom/kernel support OTG?"
A:No there is not.OTG support is a kernel feature that isnt available for our device.Maybe devharsh1998 is working on this maybe he isnt who knows be patient.
5.Q"Which rom is the best?"
A:Answer for this question is subjective you can always easily try couple of them.I like mshoaib7 ports i am currently on Nexus Experience ROM but i plan on switching to nougat soon.
6.Q"ED300 links aren't working?"
A:ED300 isn't developing for our device anymore and his thread links are not working but you can try some of the files that are on his androidfilehost folder
https://www.androidfilehost.com/?w=files&flid=96089
This isn't tested by me and since the development stopped they are not recommended since bugs can't be fixed anymore.
7.Q"My phone is bricked heeeellllppppp?!?!"
A:If you are stuck on a splash screen/bootlogo
Can you enter recovery by restarting your phone and holding vol+ and vol-.If answer is yes just reflash the rom or try different one.If you cant enter recovery mode but can enter fastboot mod by holding vol - when restarting the device then follow this quide :
https://forum.xda-developers.com/lenovo-a6000/how-to/how-to-bring-phone-to-life-fastboot-t3561070
If your phone is showing only black screen or isnt booting at all you can try QFIL unbricking method
Disclaimer:
Nothing of this is my work all credits go to the developers i am just trying to make it easier for the developers and to try and answer noobier questions that are flooding the development threads.If you think some answers need further explanations or you have some more questions feel free to PM me.Enjoy roms and happy flashing
Click to expand...
Click to collapse
Reserved
8.Q:How to change cache and data to f2fs
A:You need to have a recovery that supports f2fs thats burgexx and tingychan 3.0.3.0 and 3.0.2.0 twrp
Be ware all your data will be wiped!
Step 1: go to wipe format data type yes and wipe all
Step 2: Comeback slide the option "Slide to do factory Reset"
Step 3: Go to Advanced Wipe Section Select all Partitions "Expect SD-Card/External Storage"
Step 4: Wipe them all
Step 5: after wipe is complete select cache "Click on change file system type" and you will find f2fs option there hit it
Step 6: Do same for data that is Select "data " click "Change File System type" hit f2fs
Step 7: Flash Latest Rom & Gapps Reboot enjoy
Thanks to @somnath pal for his short but clear tutorial
Also you need to be sure that rom that you plan on using suports f2fs (dev harsh roms and some of the mshoaib ports)
And also kernel (for now only Phantom-Reborn)
9.Q:My IMEI is lost what should i do??!
A:Follow this guide
https://forum.xda-developers.com/lenovo-a6000/how-to/fix-signal-imei-lenovo-a6000-a6000-via-t3421021
10.Q:How to flash official firmware/rom?
A: Go to this thread,https://forum.xda-developers.com/lenovo-a6000/how-to/lenovo-a6010-plus-stock-rom-t3407963
find ROM for your device download it.Unpack zip transfer system.zip and yourregion.zip (yourregion.zip is optional and if you live in india its probably india.zip) and flash it in TWRP recovery.Go to wipe, swipe to factory reset then go to install and select system.zip ,swipe to install it then select yourregion.zip and swipe again,reboot.If you are having problems with TWRP flash stock recovery via fastboot or flashify etc..
Thanks for this thread but there are still a lot of noobs asking for volte
Hi, phone water damaged 2 days ago..
I tried and saved it. But now Camera and flash not working.
Whenever I open camera it says "stopped working".
Is there still water inside out? Camera?
What I can do?? I tried clean flashing latest RR ROM.
But it says the same thing.
Anything hardware related repair can be done from home?
How much it will cost for camera and flash repair? For a6000+
Thank you.
Can anyone pls make a latest miui rom for lenovo a6000 plus???pls,pls
When will you Create Android OREO 8.0 Based Custom ROM
For Lenovo a6000, Im very Excited about Android OREO ???
Im facing this network dropping issue in my lenovo a6000+. whenever i call someone network drops or sometimes when i try to load insta video.and its also effects second slot sim.pleasss help me im sick of this problem.any solution? Im using miui 8.2 stable custom rom .
amit.tiger12 said:
Hi, phone water damaged 2 days ago..
I tried and saved it. But now Camera and flash not working.
Whenever I open camera it says "stopped working".
Is there still water inside out? Camera?
What I can do?? I tried clean flashing latest RR ROM.
But it says the same thing.
Anything hardware related repair can be done from home?
How much it will cost for camera and flash repair? For a6000+
Thank you.
Click to expand...
Click to collapse
Its probably hardware problem.Camera or flat cable died from water.
Muzzamil Zamil said:
When will you Create Android OREO 8.0 Based Custom ROM
For Lenovo a6000, Im very Excited about Android OREO ???
Click to expand...
Click to collapse
I am not a developer i am just helping them.Dont spam threads with this question.Developers have life outside xda and when they manage to get it working they will share it with us
JovanSijacki said:
Its probably hardware problem.Camera or flat cable died from water.
Click to expand...
Click to collapse
I tried replacing other device camera..
I tried replacing it with Lenovo vibe p1m camera.
When opened camera application it shows front camera without any problem but does not show back camera.
How can I root my phone?
pampiii21 said:
How can I root my phone?
Click to expand...
Click to collapse
Install a custom recovery and flash a root solution from the recovery like magisk.
What is the safe overclocking value in lenovo a6000 1 GB variant (GPU..CPU)
Dennyave1
How do I install without the Android 9 PC and everything related to this process on the Lenovo A6000 with Android 5.0.2? Is this possibility of installation at all real (possible) ??? ... I am technical since birth technical antitalent, if possible I ask for a description of how to process to be successful answere !!! ?
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
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.
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.