I played a bit around and extracted the E5603 Scatter file from my phone and converted it with MTK Studio. I hope this will help some of you
freeskyler said:
I played a bit around and extracted the E5603 Scatter file from my phone and converted it with MTK Studio. I hope this will help some of you
Click to expand...
Click to collapse
How did you do this??
Let me know
Tell me step by step method in order to get E5663 SCATTER
altmash mirza said:
How did you do this??
Let me know
Tell me step by step method in order to get E5663 SCATTER
Click to expand...
Click to collapse
I could not send the firmware.info through message
I zipped it and attached there please use it
Thnks for your efforts:angel:
Alright, the output is the same like on the E5603. So the Scatter file is based only on the Mediatek MT6795 Chipset. I will change the Thread topic that all that need the scatter file can find it here.
I really would like to test a briked phone, to unbrick it. May someone would send me for this a bricked Xperia M5?
freeskyler said:
Alright, the output is the same like on the E5603. So the Scatter file is based only on the Mediatek MT6795 Chipset. I will change the Thread topic that all that need the scatter file can find it here.
I really would like to test a briked phone, to unbrick it. May someone would send me for this a bricked Xperia M5?
Click to expand...
Click to collapse
Your work is good for many peoples who bricked there phones
Peoples who are going to try this
I have an advice for them
Sp flash tool also has an option for battery
As with battery, without battery
You can try with chek and unchek them
Cause m5 has non removable battery
Scatter does not download to phone...
[/COLOR]
freeskyler said:
I played a bit around and extracted the E5603 Scatter file from my phone and converted it with MTK Studio. I hope this will help some of you
Click to expand...
Click to collapse
That's a great starting point !!! Thanks indeed for that scatter file!
Anyway, SP Flashtool does not download the scatter to the bricked M5.
It keeps trying but never gets to the progress bar that should appear.
I followed this guide:
https://forum.hovatek.com/thread-159.html
The phone appear as "USB Serial Device (COM42)" in the device manager. And meanwhile, the "Mediatek PreLoader USB VCOM Port (COM26)" remains unchainched.
After a while, the "USB Serial Device" disappears again from the Device manager - but nothing at all happens in SP Flashtool.
Any useful hint???
There are a lot other MTK Tools that you can try to use like S-Droid toolkit 2.5. Its really not easy to manage all this. there are much .ini files like in SP Flashtool that could be tweaked to recognize our phone probebly. I just made a manualle partition backup of my phone and play now a bit around
freeskyler said:
There are a lot other MTK Tools that you can try to use like S-Droid toolkit 2.5. Its really not easy to manage all this. there are much .ini files like in SP Flashtool that could be tweaked to recognize our phone probebly. I just made a manualle partition backup of my phone and play now a bit around
Click to expand...
Click to collapse
I believe that the problem is, that my bricked M5 is only identified as "USB Serial Device", and Windows connects it to its native driver. However, it should appear as "mediatek Preloader Usb Vcom", according to http://www.yomitech.com/2015/04/how-...preloader.html
So MTK-Tools do not recognize that this the device that they are supposed to flash to... or maybe they are unable to use this windows interface and are looking for a device connected over the MTK VCOM interface driver. However, this does not happen...
I have not found any way to disable or uninstall that Windows naitive driver or any other way to make Windows connect the M5 through the VCOM Driver.
Any hint?
Updated the scatter file, seems there were some errors on it. now it should be correct.
I watched a bit around the logfiles from MTK Droid Sp Flashtool etc. It seems, that wen need yaffs2 support in the kernel, for that the tools can read correct our device.
Im a beginner of compiling a kernel. There are still some erors in my build environment.
Maybe here is someone who could compile the kernel with yaffs2 support?
Some update progress.... MTK Droid Tools
- Use SeLinuxModeChanger to set SeLinux mode to permissive.
- Use adbd insecure app
Now connects the phone correctly and the field gets green
Sadly the DTK Droid crashes when I start the backup and I get the error message that the sd card couldnt be find.
Scatter file for E5633
freeskyler said:
Updated the scatter file, seems there were some errors on it. now it should be correct.
Click to expand...
Click to collapse
Hello,
My device is E5633 and i need a scatter file for that also,,,, anyone help me please :crying::crying::crying:
nasarino4978 said:
Hello,
My device is E5633 and i need a scatter file for that also,,,, anyone help me please :crying::crying::crying:
Click to expand...
Click to collapse
Apparently, the Scatter-file is the same. If you device is bricked, just try that one out... anyway the device can't be more bricked.
I tried - but I did not succeed. SP Flash tool did just not download the information to the phone, even though the drivers were installed correctly and the phone was recognized as Mediatek USB port on the computer.
If you succeed, please let us know how you did!
diegopanther said:
Apparently, the Scatter-file is the same. If you device is bricked, just try that one out... anyway the device can't be more bricked.
I tried - but I did not succeed. SP Flash tool did just not download the information to the phone, even though the drivers were installed correctly and the phone was recognized as Mediatek USB port on the computer.
If you succeed, please let us know how you did!
Click to expand...
Click to collapse
It didn't work for me, i tried the scatter file with the SP Flash Tool and nothing happened when i pressed on Download i had chosen the android file and nothing changed.
Any suggestions .....
Test point in Xperia M5
nasarino4978 said:
It didn't work for me, i tried the scatter file with the SP Flash Tool and nothing happened when i pressed on Download i had chosen the android file and nothing changed.
Any suggestions .....
Click to expand...
Click to collapse
Please can anyone help me about the test point in Xperia M5 and how to use s1tool and if there are any files to be added in this application.
I had the set of tools attached here in other topic but i tried to figure out about the test point and i couldn't know what to do ?
hope to have some assistance about that ????? :crying::crying::crying:
nasarino4978 said:
It didn't work for me, i tried the scatter file with the SP Flash Tool and nothing happened when i pressed on Download i had chosen the android file and nothing changed.
Any suggestions .....
Click to expand...
Click to collapse
that it's because you don't have linked the files that are described in the scatter file.
i flashed a zte smarthphone in the past and the scatter file is only a map for the memory adress of the files that you could have , but i don't see any similar in the firmwares that i have downloaded , and yes i have a bricked M5 too .
i hope that the efforts of the comunity works, and one day all the red lights dissapear xD
sorry for my english , i hope that you understand
Related
I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355
Nit3H8wk said:
I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355
Click to expand...
Click to collapse
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.
ThePagel said:
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.
Click to expand...
Click to collapse
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142
Nit3H8wk said:
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Yeah that's probably your best option I have a partitions dump from the tot if yours are not working for some reason. Instead of installing twrp If I was you I would boot into download mode after and flash the tot. I did do a debrick dump with the script that I can get to you tomorrow some time and if that doesn't work tell me and I can give you a link that has 250-500mb range for the dumps from when I was helping the other guy. They weren't made with a script but with terminal emulator but they should be the same thing just bigger because the smaller dumps weren't working for him. Any way here are the partitions just in case https://www.androidfilehost.com/?fid=23622183712472493
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
Oh and before I go to bed another thing you can try if you can send the images over but they don't seem to work. Hunt down the fastboot laf.img send that over then do the rest of the partitions via fastboot instead. Good luck!
Dead phone
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.
Nit3H8wk said:
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.
Click to expand...
Click to collapse
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.
ThePagel said:
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.
Click to expand...
Click to collapse
Yeah i will have to wait then can't afford the $175 deductible right now. Thanks for the help. I don't mind waiting just hope i can find a less costly solution know what i mean?
QPST
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.
Nit3H8wk said:
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.
Click to expand...
Click to collapse
Yeah I got ready to do it last night but got side tracked hopefully tonight
qpst
ThePagel said:
Yeah I got ready to do it last night but got side tracked hopefully tonight
Click to expand...
Click to collapse
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
Ill be able to tell you tomorrow afternoon if I can do it.
Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
I cant seem to get into diag mode or field test mode so I cannot create the files for you :crying: BUT before you completely give up on fixing it take a look at this http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/
Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.
cesarandres_8911 said:
Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.
Click to expand...
Click to collapse
I just did the same thing tonight, I'll let you know if I fix it.
mxpxboi said:
I just did the same thing tonight, I'll let you know if I fix it.
Click to expand...
Click to collapse
Hello,
What is your phone and variant model? Do you have D851 model?
Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"
mxpxboi said:
Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"
Click to expand...
Click to collapse
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.
cesarandres_8911 said:
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.
Click to expand...
Click to collapse
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.
cesarandres_8911 said:
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.
Click to expand...
Click to collapse
Thank you SOOO much for your help so far.
I installed Qualcomm Drivers and touched the points and it connected.
But it says that the Drivers are blocked due to not being digitally signed.
And it's showing up in Device Manager as "Qualcomm HS-USB QDLoader 9008" with an exclamation point.
I am posting screen shots.'
You didn't have this issue?
What steps do I do in the BoardDiag exactly? Just add the directory with the file and hit start?
@mxpxboi it seems you're using windows 8/above, you have to disable driver signature, here is how to do it https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Sent from my LG-D801 using Tapatalk
I'm wondering, when going through the different boot modes, bootloader and recovery, there is a third option that shows up on the pc called Moorefield. It's an unknown driver, which leads me to believe there is some sort diagnostic functionality to it. I guess it's just a matter of figuring out what drivers work. I was wondering if anyone has had this experience, and/or knows how to work with it.
Moorefield is the name for intel processor. It will come handy when all other option to recover phone are not working. But for that we need drivers and image file to jumpstart.
harpreet.s said:
Moorefield is the name for intel processor. It will come handy when all other option to recover phone are not working. But for that we need drivers and image file to jumpstart.
Click to expand...
Click to collapse
how ?
Ex search for intel phone tool which allows to flash images. I have not used it till now however i am pretty sure it will help recovering phone when fastboot , recovery , adb are unable to.
rikkxzzz said:
how ?
Click to expand...
Click to collapse
We've been looking into that over here: http://forum.xda-developers.com/zenfone2/general/unbricking-research-unbricking-method-t3162848
i rooted my lg g3 d 855 lollipop and tried to install TWRP
but it was not a success i lost recovery + download mode but it boots perfectly into android system and can use it normally
to install twrp again i tried to flash it again and again but no success
then i flash aboot.img and it all went blank not booting not rrecovery etc
i tried board diag method to unbrick it shows up in my system as qcomm hs usb 9008
but when using board diag it says DEVICE NOT FOUND IN DLOAD MODE
plz help this is my first android phone after months of hardwork
i dont think i have enough money to replace the mobo or buy a new one:crying:
Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.
halekhonza said:
Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.
Click to expand...
Click to collapse
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc
adilismail62 said:
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc
Click to expand...
Click to collapse
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
yes im using the r8 port it shows in device manager and in board daig also i gave port 14
before my phone was going to get bricked its battery was low
is it affecting the procedure i think my battery is not charging
when i remove battery and connect to pc phone shows battery not inserted sign when i insert the batery it disappear and no sign of charging
i thought this might help:good:
You have to use the original LG usb cable. Dont try with fake china cables because its a lot possible to have troubles with them.
Hi,
Can anyone share the scatter file of Sony M5 Dual E5663. The only way to revive my bricked phone is scatter file. I can use these file in SP Flash tool.
If anyone can extract it from there phone it will be very helpful.
Here is the guide to extract the scatter file from Sony M5
http://www.droidgyan.com/scatter-file/
Is this still a possibility? Will it work? I hope someone can still do this for us.
try to figure out first if you can manage that sp flash tool recognizes your bricked device via connected usb com port. you have to install mediatek vcom drivers (google for it). this is essential before you can go further...
btw. you can download full firmware for your device via androxyde's flash tool. you can extract any .ftf rom with winrar but you will see that it does not contain any scatter file for your device. i've tried a random scatter file only to see if my bricked E5603 getting recognized as preloader vcom usb device in sp flash tool and it does not. it seems that this option is not working and my conclusion is that, after all that i've found so far, only a mainboard replacement is the solution as mentioned already by our experts.
Requesting Scatter File for Xperia M5 dual E5663
Hi!
I have a bricked M5 dual E5663 featuring an MTK-Chipset, and I hope to be able to revive it with SP Flashtool. However, I need a scatter file as a starting point, too...
THANKS if anyone can extract the scatter-file from the phone. In the downloadable firmware-images, there is unfortunately no scatter file included, so it would have to be copied from a "living" device...
THANKS, cheers!
diegopanther said:
Hi!
I have a bricked M5 dual E5663 featuring an MTK-Chipset, and I hope to be able to revive it with SP Flashtool. However, I need a scatter file as a starting point, too...
THANKS if anyone can extract the scatter-file from the phone. In the downloadable firmware-images, there is unfortunately no scatter file included, so it would have to be copied from a "living" device...
THANKS, cheers!
Click to expand...
Click to collapse
I had try with mtk droid tools to get scatter
But it is not working with m5 dual i dont no why
I am not an expert
But i will do this if someone can guide to get scatter through mtkdroid tool
It was showing as connected but scatter option was greyed
So i could not pull the scatter you need
altmash mirza said:
I had try with mtk droid tools to get scatter
But it is not working with m5 dual i dont no why
I am not an expert
But i will do this if someone can guide to get scatter through mtkdroid tool
It was showing as connected but scatter option was greyed
So i could not pull the scatter you need
Click to expand...
Click to collapse
Hi there! Thank you very much for trying! I am not an expert either, so I can't tell, why the option was greyed out.
Hopefully someone will be able to help!
diegopanther said:
Hi there! Thank you very much for trying! I am not an expert either, so I can't tell, why the option was greyed out.
Hopefully someone will be able to help!
Click to expand...
Click to collapse
Aircatcher and ih8redsn0w
They both know very well about these things
You should try to talk with them
diegopanther said:
Hi there! Thank you very much for trying! I am not an expert either, so I can't tell, why the option was greyed out.
Hopefully someone will be able to help!
Click to expand...
Click to collapse
You should try this scatter
https://forum.xda-developers.com/xperia-m5/help/e5603-scatter-file-t3605269
altmash mirza said:
You should try this scatter
https://forum.xda-developers.com/xperia-m5/help/e5603-scatter-file-t3605269
Click to expand...
Click to collapse
Thanks! I tried. Anyway, it looks like SP Flashtool does not connect to the M5. IMO the MediaTek VCOM Driver does not associate to the M5 for some reason.
The M5 is identified as "USB Serial Device" using a native Windows Driver. However, it should appear as "mediatek Preloader Usb Vcom", according to http://www.yomitech.com/2015/04/how-to-install-mediatek-usb-preloader.html
I have not found any way to disable or uninstall that Windows naitive driver or any other way to make Windows connect the M5 through the VCOM Driver...
Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?
Hi @fede91it,
Sorry for the late answer - I have been quite inactive on xda recently
Unfortunately I don't have a solution for you right away, but I got a working X Pro with stock rom (+twrp and magisk) and a bit of experience with the "standard" tools like adb and fastboot. Never worked on such a low level like you though.
Does the tool you mentioned (QFIL) offer the possibility to grab contents from the phone instead of downloading it to it?
Maybe we can get the missing data from my phone?
Sorry for the dump/obvious question, but: What happens in the current bricked state when you turn the phone on? You can't enter fastboot and unlock..?
Another approach: have you tried contacting BQ? Maybe via their forum https://www.mibqyyo.com/. Possibly the missing files are device specific and you would need bqs help..
Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick
fede91it said:
Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick
Click to expand...
Click to collapse
Hey, did you recover your paperweight? I'm in the same situation but with the BQ X PRO
I could not solve it. There are some files missing for the compilation, and I can't find them
Have you tried this method by only using the firehose? forum.hovatek.com/thread-31505.html
Hey, did you recover? I made the same mistake as you. I managed to repair ...
What I did was:
- I removed the battery cable (I did not remove the battery completely)
- I pressed on VolDown button and connected the phone via usb to the pc and immediately went into fastboot mode
- I opened the BQ app on the pc, I loaded the rom and put it to install the rom. It asked to unlock the bootloader (which is what we want) ... The ROM could not be flashed, but it is not important ... As soon as you unlocked the bootloader, the phone started up without a problem
fede91it said:
Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?
Click to expand...
Click to collapse
Hello! Maybe it's too late, but I have the same problem as you and I found this post that talks about our mobile! In it you can find a lot of information, but also the links to download the stock ROMs and the flashing tool to get back to the factory Rom and unbrick the phone! I leave you the links below! Hope it also helps others with the same problem as we! Greeting
Post:
[HOW-TO] BQ Aquaris X Pro | [Stock-ROM] Unlock,Recovery,Root,Upgrade (TWRP/Magisk)
Hi everyone. :) This Post (post #1) shows the complete process of unlocking, flashing, rooting etc. in general, it may refer to old firmware and/or tool versions but the steps remain the same for newer versions. The chapters rely on each other...
forum.xda-developers.com
Link of stock ROMs and the flashing tool:
Support - Aquaris X Pro
web.archive.org
Hi,
Have you ever successfully got it to work again?
Thanks
rufus.wilson said:
Hi,
Have you ever successfully got it to work again?
Thanks
Click to expand...
Click to collapse
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above
MigSantosPT said:
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above
Click to expand...
Click to collapse
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
It is strange because it usually shows something on the screen right away ... Pressing the Power button also does not appear anything?
Did you install the ADB drivers? After the ADB drivers are installed, the BQ program recognizes the smartphone
and it also opens doors to use the command line to do almost anything.
rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
the number 9008 sounds like the EDL mode and NOT the wanted fastboot mode which is required by the usual way of flashing via bq tool or fastboot/adb tools.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
sorry, no solution, only confirming..