Database Users

Help need BLU STUDIO C (D830U) SPFlash tool ROM Version..

ATT MOD: Please delete this post as I was totally off on what I was looking for: http://forum.xda-developers.com/studio-5/general/help-blu-studio-c-hd-model-d870u-t3244227
Hey All,
I've totally Bricked my Blu Studio C, as I'm completely new to the BLU product line, I totally screwed up....
What I need Is a COPY of the Stock Blu Studio C (D830U), Made with SPFlash Tools, I need the Scatter file, Preloader, Everything I can to basically restore a totally bricked phone, It is still recognized in SPFlash Tools and MTK. Just won't start....(Red Charge Light)
They do have the ROM at Needrom but It's an ADB/Fastboot Flash Setup and Won't work as I can't get to Flashboot...I've Also read that you can convert that ROM version to SPFlash Tools but I haven't a clue how, read other places that if you don't have the scatter.txt your screwed anyhow and that doesn't come with this ROM Version....
CAN ANYONE Help me out (and alot of others Judging by Google+) and put out a Complete copy of the ROM??
It would be much appreciated as of my reading this WILL unbrick my phone....
Thanks for any help,
Mike

D802 no recovery after failed TWRP install on 5.0.2

i have experimented with custom ROMs on this phone in the past but have been using the stock lollipop 5.0.2 ROM for a while now after reverting back with a KDZ and so i figured i knew what i was doing.
i found out about the recent stability of cm13 nightlies on this device and wanted to give one a try so i decided to root the device with super su, which went well and then attempted to install TWRP with autorec for lollipop. It stated that the installation was a success and to reboot but when i did, it booted to a black screen.
i found this thread http://forum.xda-developers.com/showthread.php?t=2582142 which seems to say that i should be able to fix it if my device shows qualcomm 9006 in the ports menu, however my device shows up as marshall london HS-USB Diagnostics 9006, and i don't know what jellybean version this device was running so i dont know what images to use to to attempt this method anyway. I'm hoping someone more experienced with this **** that me will be able to tell me how to fix this. thanks for the help, King of Hard Bricks

try to see if skr tools works .. if not see in no download no recovery thread.. or post in back to stock thread.
not sure if that error is the one you need to short circuit your motherboard.. but search fisrt those places...cause i think somone suggested to do another step instead of the short circuit way..

raptorddd said:
try to see if skr tools works .. if not see in no download no recovery thread.. or post in back to stock thread.
not sure if that error is the one you need to short circuit your motherboard.. but search fisrt those places...cause i think somone suggested to do another step instead of the short circuit way..
Click to expand...
Click to collapse
I used the unbrick tool and my phone is working, thanks man

KINGOFHARDBRICKING said:
I used the unbrick tool and my phone is working, thanks man
Click to expand...
Click to collapse
Am glad you sort it out, now pass the knowledge to other is same situation. :good:

Total brick. Wiped the wrong things in fastboot.

DELETED

4llerbuntu said:
Hello.
PLEASE HELP ME.
I totally bricked my device. completely dead. i wiped the wrong partitions in fastboot, now it won't get detected at all. it won't even come on.
I'm in a country where its not possible to send it in to Asus for repairs.
computer still sees it as Qualcomm HS-USB QDLoader 9008
but i don't have the necessary tools or files to recover it. PLEASE HELP ME>.
Click to expand...
Click to collapse
Start saving money for new phone :^)
BTW just out of curiosity, what did you wipe?

DELETED

does your phone boot

4llerbuntu said:
The firmware partitions, modem, hyp, sbl1, recovery.
Forgot to flash them back before reboot.
Ive since learnt one can recover with QPST and some files. Problem is i cant find them for Asus.
Click to expand...
Click to collapse
you didn't wipe aboot, abootbak, hypbak? right? Our phone has a backup partition for each partition (abootbak, hypback, sbl1bak, modembak, etc), asus included these, so there must be some way to use them to unbrick. Are you able to reboot to fastboot mode? ( i guess not, but still to confirm)
You can unbrick with QFIL ONLY if you manage to find your device's RAM IMAGE (usually MPRxxxx.mbn) and BOOT IMAGE (usually xxxx_msimage.mbn). Other flash files are included in asus fota, only these two are not. @shakalaca might help to find these files or the entire service ROM. I have been searching for asus service but to no avail . I have flashed many lenevo and xiomi phones with QFIL. Here's is a very nice guide http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
You can request for ZF2 laser's service ROM on that website/blog. GSM FORUM is also a good forum to request service ROMs

DELETED

mohamedelkholy said:
does your phone boot
Click to expand...
Click to collapse
No it doesn't boot. It won't even power on
But it still gets detected as Qualcomm device when plugged in to pc

4llerbuntu said:
No i didnt wipe those.
Will the MPRxxx.mbn and msimage.mbn for another phone but similar processor and chipset work? I found those for MSM8916 for another device and im hoping i can use those.
Click to expand...
Click to collapse
I never cross flashed ram image. Be patient. Don't flash other device's ram image, it may worsen conditions. Keep this as the final solution, but NOT NOW. Also, you need boot image (.mbn) too.

DELETED

DELETED

deleted

Deleted

deleted

Deleted

Deleted

4llerbuntu said:
hmmn, i'm so sad. so nobody is willing to help me at all?
Click to expand...
Click to collapse
not really, I think we're all (ok, just me) don't have that knowledge to help you, or simply can't
4llerbuntu said:
i always assumed all the people who post on this board had the device.
Click to expand...
Click to collapse
Yes, all people there should have laser, and no, i dont have your type, and someone maybe just lurking around, want to buy this laser phone if they feel like it
4llerbuntu said:
Surely i can't be the only person who will ever have this problem.
Click to expand...
Click to collapse
Yes, me too, I think someone will do this thing, don't know why, just feel like it?
4llerbuntu said:
i hope someone is willing to help when it happens to another person.
Click to expand...
Click to collapse
I'm hope we got that knowledge too
4llerbuntu said:
Maybe i should just give up. i'm so down right now.
alright bye.
Click to expand...
Click to collapse
Sorry to hear that
Sent from my ASUS_Z00RD using XDA Labs

4llerbuntu said:
computer still sees it as Qualcomm HS-USB QDLoader 9008
but i don't have the necessary tools or files to recover it. PLEASE HELP ME>.
Click to expand...
Click to collapse
Are you sure msimage is same as gpt? I have attached my ze550kl msm8916 gpt dump. Seems there are three- gpt, gpt1, and gpt2. Try your luck with each one by one.
And please stick to one thread, b7mping the forum is not a solution to your problem. Update your OP by mentioned.ing the workarounds you have tried till now and useful links you have visited for fixing the issue. I know a friend who is a mobile repairer. He might have the service rom for your device. I am waiting for his reply

sziraqui said:
Are you sure msimage is same as gpt? I have attached my ze550kl msm8916 gpt dump. Seems there are three- gpt, gpt1, and gpt2. Try your luck with each one by one.
And please stick to one thread, b7mping the forum is not a solution to your problem. Update your OP by mentioned.ing the workarounds you have tried till now and useful links you have visited for fixing the issue. I know a friend who is a mobile repairer. He might have the service rom for your device. I am waiting for his reply
Click to expand...
Click to collapse
Thank you. I will do that

4llerbuntu said:
Hello.
PLEASE HELP ME.
I totally bricked my device. completely dead. i wiped the wrong partitions in fastboot, now it won't get detected at all. it won't even come on.
I'm in a country where its not possible to send it in to Asus for repairs.
computer still sees it as Qualcomm HS-USB QDLoader 9008
but i don't have the necessary tools or files to recover it. PLEASE HELP ME>.
Click to expand...
Click to collapse
Read this and see if any if it applies.
www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants
I'm not sure how the tool works, but maybe you can pull your backups and write back your partitions from the backup.
Sent from my ASUS_Z00TD using Tapatalk

Mods please help close this thread. ........

Mediatek SP Flash Tool

Hey,
Has anyone succes in unbricking a Meizu device with the mediatek sp flash tool?
I personally have a bricked MX5 (thanks to the A**hole who made the MX5 BT unlock topic)

nope... still cannot bypass the secure base-band chip problems... the only available method is to program the boot to load the original source code and to creat a
1 - android-info.txt
2- android-product.txt
specific for mx5.. im still experimenting this though.. so far no progress yet..

If we can get this working, hard bricked devices can get recovered with fastboot I think?
Is there a way I can help you?

killerbie said:
If we can get this working, hard bricked devices can get recovered with fastboot I think?
Is there a way I can help you?
Click to expand...
Click to collapse
yes, hardbrick can be recovered if only we can bypass the secure baseband chip.. im still learning the code to creat those 2 files that i mentioned earlier.. so far no good.. still need time to identify which code that can match the baseband chip pass code. i convert update.zip to aboot.img with android file.txt that i creat. but still the code are not match. there is 1 way to reset the baseband chip, but need usb tongled and removed emmc card to reset all.. thats hell of a way to do becoz its include hardware modifications. and also need few device that only availble in chinesse , not mention the language though.. for now lets hope for master yus to bring the miracles to us..

I've found another flash tool, it seems to be provided by meizu themselves with a chinese manual called: MultiUpgrade 4.8.5 bundled with MultiUpgrade 4.8.5

killerbie said:
I've found another flash tool, it seems to be provided by meizu themselves with a chinese manual called: MultiUpgrade 4.8.5 bundled with MultiUpgrade 4.8.5
Click to expand...
Click to collapse
have u tested it yet?

need help,
did anyone can help me to solve my problem with flashtool?i try to flash my homtom ht 20 pro using flashtool, but my flashtool can not download or detect my phone i try to instal media tek usb vcom but stil can not work,cos my win 10 said that driver not digitaly signed,so anyone have solution for my problem, it will greatfull if you give me a link to download another driver so i can start flash my homtom ht 20 pro, thanks

You can install unsigned drivers in windows by shift clicking while reseting windows. You will be prompted later on on various options of reboot. One of them is going to be to not enforce signed drivers. If you have any trouble finding this option, look it up "reboot not enforcce signed drivers". You will find what you need.

[GUIDE] [FIX] YUREKA (AO5510) Touchscreen Calibration Issue

​
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?