Database Users

A guide to tweaking your X2.

Disclaimer: I am not knowledgeable about phones. I do not code and nor do I usually do what I describe in this post. The contents herein was put together by me in order to avoid confusion for people with the same interest as myself, making my X2 work better/faster or just plain customized. Because of this, I've made a few assumptions and also only described the way that worked for me.
This guide is based on the collective work of forum users, I take no credit or responsibility for its accuracy other than the fact that it worked for me.
This is only the installation steps, they are not specific to my knowledge. There are other guides out there for changing your language and doing more advanced thing, but this is just the basics. At least they are to me. Let us begin.
-----------------
Hello and welcome, this post is meant to guide you through the process of customizing the installation of your Xperia X2. My hope is that it will make your phone more responsive, but more importantly give you the option of deciding what you want installed.
The first thing we're going to be doing is to get ahold of the right files to install on your X2. Thankfully these files have been made availiable to us by PavelX1 in his post "NEW ORIGINAL X2 ROMS + Extracted CABs update 14.6.2010"*
Don't let the number and letter jumble intimidate you, on your own X2 the information you need to find the right package is found at Settings -> System -> Unit Information**. Here you'll find a bunch of numbers and letter combinations, if you look closely some of these will correspond to the names of the files availiable by PavelX1. Find the one that corresponds to your unit.
In my case it said that the following:
Software ID: 1230-2397
Software Version: R3AA035
Customization ID: 1231-4911
Customization version : R20A
Language Region: GENERIC_SE
I therefore searched for the following file which matched my information :X2_1230-2397_GENERIC_SE_R3AA035_CDF1231-4911_R20A.rar. Below that file was the file we're interested in for this particular guide. The GENERIC_*your language*_*version*_CABS.rar which in my case was named GENERIC_SE_R3AA035_CABS.
Now what we're going to do is get your computer prepared. Please download the Sony Ericsson Update Service (SEUS) available at their website.
If this is the first time connecting your X2 to your computer it might want to install some drivers in order for your computer to communicate with your phone, this is irrelevant to this guide but I mention it in order to let you know that this is normal and you have done nothing wrong.
Once we can connect to our phone and use its memorycard (which I assume you have) we will open the GENERIC_*your language*_*version*_CABS.rar and extract its contents into it. It has been suggested that you throw in an extra file together with the others availiable in the post "Want a fix for the X2? Only us can do it." on page 3.
We may now move on.
If you already have SEUS installed it was suggested by royalbloodvi in his thread "[TESTED 100% WORKING] Quickest way to get MR2 for those of you who can't get it!" that you remove the following folder C:\Program Files\Sony Ericsson\Update Service\db from your computer. I haven't tried any other way so I'll leave that bit of info as is.
Now we can begin the install process, this will take a little while so don't be in a hurry. It's important that you do not do this on a phone with an empty battery as it may interrupt the install process and cause problems, charge it before you do this. You may also want to backup any files important to you on the phone as they will be removed in this step. As an extra precaution you may want to remove the sim card as well.
Now that we're ready, go to Settings -> System -> Clear phone memory and press it. You'll have reset your phone to its original, empty, state. Connect your phone to your computer, if you haven't already, and begin the update process. SEUS might tell you that your phone is already up to date, this may be true, but we don't WANT it to be up to date, we want to decide what it is updated WITH so click update anyway.
Your phone will reboot. Disconnect your phone from your computer and open the backside of your phone by sliding the lock switch and removing the cover. Remove the stylus and you will see a small depression at the top left that was shidden by it. This is the hard-reset button for your phone which we will be using in a moment. Untill then you wait. Your phone will ask you to calibrate it after the sony logo has shown up. Calibrate the screen and your phone will start installing .cab files. quickly go to the hard-reset we mentioned a moment ago and press the tip of the stylus to it. A click was heard on my X2 when I pressed it and I assume the same is true for yours.
Now your phone will reboot, you will notice that it looks markedly different from what it did before this procedure. Don't worry, we can fix that if you like, but first we must address the window that has popped up and asked if you wish to try the install again. No, no we don't. Click no.
We are now freed from the shakles of oppression that is preinstalled and unremoveable software and may begin installing the files we WANT.
GO to the file explorer and select Storage Card and you will see all of the files we extracted to it previously. In order for you to know which ones you want I suggest that you go to the second page in the thread "Want a fix for the X2? Only us can do it." to get an overview of what the individual files do. Installing them is as simple as clicking them and selecting to what part of the phone you want them installed, I choose to install all of these files to my phone and not my memory card.
Now, to get your phone looking like it did before you did this (assuming you didn't use a panel but a standard theme) you will spot three theme files called X2_Saturn.cab (which is the one I use that looks like the stock one) X2_Saturn_Light.cab (which I don't know what the difference is) and X2_Titan.cab (which I also don't know what it looks like).
And that's that, you're done and hopefully your phone is more to your likeing.
--------------
Here is a shorter step by step guide without the filling, unceremoniously "borrowed" from royalbloodvi and slightly reformatted. Please read the full guide and use this only as a quick procedure guide.
1) Reset your phone.
2) Unpack the GENERIC_*your language*_*version*_CABS.rar to your phones memory card and add the multifix.cab found on this site.
3) Open SEUS, start a new update. Even if it says you have the latest version you want to do it update anyway.
4) Once your phone reboots the calibrations screen will appear. After calibration it will start applying .cab files. Now push the reset button that is hidden behind your stylus and battery cover and it will reboot again.
5) You may now find the files you wish to install on your phones memory card in the file explorer.
*I, as I am a new member, am not allowed to post links, thus the name of the forums from which this information is gleaned is named instead of a direct link.
**If this informations isn't named exactly the same as I have described it, but is merely similar, it could be because I've done a literal translation from Swedish to English.
Edit: I just noticed a very similar guide is available on the General section, which I overlooked. I feel like an ass now. This thread may removed at moderators leisure.

Evo shift on metropcs/Cricket With MMS

OKay i was having some major problems with an evo shift on metropcs.
The problem was that i could not get qpst to recognize my phone. basically it is a surf-msm7830 and it draws a blank when you try to re-provision. It only shows banner and phone state waiting for cdma or something like that.
So after a month of messing with it, i finally got a good version of qpst that works with evo shift 4g/speedy.
The secret is qpst 2.7.366, i got it from conflipper, the guy who does cricket stuff at ppcgeeks.
You have to remove the old qpst then install the new one.
Just follow bloodykiller86's tutorial and youre set to go.
I would make a modified bloody killer tutorial but i dont have the time to make screenshots.
Bloodykiller86 tutorial
http://forum.xda-developers.com/showthread.php?p=8395950#post8395950
and here is qpst, please please make some mirror 4shared, hotfiles, and file sharing accounts.
Here is qpst
http://thepiratebay.org/torrent/6388346
I am uploading at 2mb so anyone should be able to get it, but i wont seed for ever.
I cant post on any other xda threads because of my low post count, stupid rule.
So feel free to move my post to anywhere it is suitable, also please add to a sticky or make this a sticky. It took me for ever to find this information and yes dont bring up the lame "search" question. It gets old and my response is, what makes you think PEOPLE DON'T KNOW HOW TO search? Just answer the question and you have more ways for answer to be indexed.
And all you people that make money from the evo shift flashing and dont want to share information, SCREW YOU!!!
I HOPE YOU LOOSE SOME MAJOR MONEY NOW THAT THIS IS OUT!!!!!!!
Almost forgot, dont forget to root. Shiftrr worked good for me. The hard part was getting the drivers and adb to work.
Then once that worked you just have to apply shiftrr about 2-3 times and see if you get root.
http://www.addictivetips.com/mobile/root-and-install-recovery-on-htc-evo-shift-4g-one-click-root/
Another tip, if you cant install android sdk because of java dependency (%programfiles%\Java\jdk1.6.0_25\jre and you know you have it installed already.
Just download the zip and extract anywhere, it should work just fine with out the installer.
EDIT: MMS is now working good
Here is the link to a known working mms solution for the evo shift.
"Also wana add that if you do wipe cache and data or restore apns to default after doing my fix YOUR MMS WILL STILL WORK this makes metropcs your default setting"
http://team-nocturnal.com/showthread.php?393-evo-shift-metropcs-mms-fix

Thanks for sharing. But Im having issues. The link that you provided with the qpst tool......well, when you download it, there is nothing in the file box. Its an empty torrent. So could you plz give us a hotlink, rapidshare, megaupload or any re-link to the tool.
Im trying to flash back to sprint, and have been searching on-and-off for 2 weeks for this tool. Thanks
Edit:
Oh, and you dont have to put it in torrent format again, as we would have to depend on a very few seeders, so to eliminate that potential problem, uploading it to some dedicated file spot would be the way to go. Im sure u are well aware of that.
And if you do re-torrent it, im willing to help out for a month or two as i have a 10mb upload. (60mb down )

oh, last question. The usual versions I locate are 2.7.323, however I just found a 2.7.355, my question is did you try the .355 version and was not successful with that or was it the .323 version?
Guess I will hang tight til you send me a copy of the .366 one. thanks in advance!!

Oh i am sorry for not replying, been really busy at work.
Also just to let you know.
I am always seeding, its just that my kids tend to turn of the computer from time to time.
So sit tight if it doesnt start.

missingxtension said:
Oh i am sorry for not replying, been really busy at work.
Also just to let you know.
I am always seeding, its just that my kids tend to turn of the computer from time to time.
So sit tight if it doesnt start.
Click to expand...
Click to collapse
Thank you for your awesome thread.
Can you please upload the file to www.multiupload.com and www.mediafire.com please?
Also please check the boost mobile thread in Q&A.

[Guide]Dell streak flashing guide

Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are

Great job!
Sent from my Inspire 4g using XDA Premium App

I have added some comments on the talk/discussion page on the wiki. If there is any specific topic you need help on in the wiki let me know.

TheManii said:
Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are
Click to expand...
Click to collapse
Thanx!

[WIP] [DEV] Any dev know where BT config is stored within i9505G?

Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.

KrossX said:
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
KrossX this is the second time you have posted questions in the development forum. As I stated before these are for Q&A NOT here. Please refrain from posting your questions here and READ the XDA users guide and forum rules again. There is a reason for this. I am glad your part of the community and your questions and comments are noteworthy you just need to put them in the right place. We read those threads as well! MJ
This is for Development ONLY

Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I thought that since I was aiming this more at the devs it would've been in the Dev forums. Sorry for having you move yet another thread of mine.
Didn't mean to cause a ruckus; never really got a chance to read the post by deaffob above before it was edited by the mod so no offense from whatever name-calling was done, haha.
Thanks MJHawaii; I will search for logcat and see what I can pull up.

Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4

KrossX said:
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.

xHausx said:
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
Click to expand...
Click to collapse
Good news and bad news.
Bad news: I am unable to run logcat; I am unable to access my device via USB ever since the root and when I tried doing the logcat steps, yet again it couldn't connect to my device.
Good news: I believe the solution to this issue (being unable to access my device via USB) may also lie in the logs along with the bluetooth issue. The reason why is because of this error message I received while trying to reinstall the USB driver (attached pic); it points to not being able to "start" a device. I think this will all eventually tie-in with some services not running correctly on my phone.
So, is there another way for me to post a log for you kind folks to review on here via my phone directly?
If I can do that via catlog app on my device, let me know what sort of log (which options) I'd need to run and post. Thanks!

Well, did a restore to stock + root. That didn't help. It changed the Baseband, Kernel, and Build versions but did nothing to fix my issues with BT and USB connectivity.
I think I am going to start researching ways to start from scratch. Like a factory reset/wipe back to first-use condition. If anyone can point me towards some reading material on how to do that safely and wisely, it would be much appreciated!

I just ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Bluetooth issue is resolved; tested it just now and it works just fine again. As is the USB issue; as soon as the phone was connected to the same exact PC as before, it was recognized and showed up as a device that I could open and explore.
My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting too.
Thanks to all those who attempted to help!

Unbricking and QPST - All Snapdragon / Qualcomm devices

Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.

What made your device hard brick
Sent from my SM-N910G using Tapatalk

Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.

can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot

AlexanderDAB said:
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
Click to expand...
Click to collapse
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G

Update:
So far I have contacted Qualcomm, Intrinsyc (they sell Snapdragon development boards), and a Samsung retail outlet.
All have come back as a negative - the closest I could get was the Samsung retail outlet where a dude used to work in the repair centre and had access to the files then.
Unfortunately, Samsung revoked his permissions now that he only works in a retail outlet.
He knew what I was talking about, but due to Samsung and their encryption etc, he couldn't provide me with the files.

C_dog_1 said:
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
Click to expand...
Click to collapse
I have the same problem and also looking for a solution. I will contribute to this post as I find something.
There is a similar post here:
http://forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
---------- Post added at 07:10 PM ---------- Previous post was at 06:30 PM ----------
Try this manual.
http://dl-1.va.us.xda-developers.co....rar?key=yrJPiZgu63c6RxNIbU_xVA&ts=1474829412
I've found it earlier today but haven't had a chance to try it yet.

Says the file is gone
Sent from my SM-N930W8 using XDA Labs

It's just the pdf and .pit that i used here: http://forum.xda-developers.com/note-4/help/hard-brick-phone-off-long-help-fellow-t3468792

yashthemw said:
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Click to expand...
Click to collapse
it won't boot at all
i was messing around with the system on the factory binary firmware
yes, it is
nope, it will not boot

i have same problem does any one sucess with this process ?

Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.

yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
Click to expand...
Click to collapse
can you get me a dude with an AT&T note 4?

same boat with my N910F
C_dog_1 said:
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
Click to expand...
Click to collapse
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers

Lofhario said:
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3488114
Tried this?
Reporting Via N910G.

Hi, got a Phicomm Energy M+ (E551). It turned off as the battery was empty, so I charged it overnight.
But:
-Switching it on only shows the phicomm logo
-Trying to enter recovery, shows phicomm logo for a second and then the screen stays lit. Nothing else happens.
-On Windows 7 device manager shows it as "RELINK HS-USB QDLoader 9008 (Com3)" (VOL Up+VOL Down + Power)
-fastboot/adb wont find it
-I tried this http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I dont have a emmc backup but an unzipped Stock ROM of the E551L which support told me to use. (put on SD card and reboot into recovery, but I cant get into recovery)
Hence I use the unzipped ROM with the Qualcomm FLasher :S (http://na.phicomm.info/release/E551L...TA package.zip)
-It starts the process but then says "Failed to enter EDL" (Emergency) mode
Another thing I stumbled across is :
E551L has Qualcomm MSM8916 and Android 4.4.2
E551M has Qualcomm MSM8915 and Android 4.4.4
Will I have to quire a deepflash cable or am I missing something here ?

yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Click to expand...
Click to collapse
tried but not working
waiting for other solution