Related
Hi,
I made a mistake with flashing QTEK S200 with wrong file.
Bootloader was modified. Device can not start at all.
It can not even go to bootloader screen (red-green-blue).
As consequence, no USB connection can be established.
What is the solution? I guess utilities can not be used, because they assume connection to USB, but there is no connection.
Not big deal, because it was not working well anyways, but would be interesting to know a solution in this case. Many ppl. would be happy to know how to manage this situation, I guess.
later.
Not very good news, service center said they don't know how to fix it, but kept the device to make few things with it.
Clearly, bootloader was overwritten.
Will see. Somehow they manage to identify type of rom is installed from i-mate.
So, think before you make any flashing
re: another service said they will do whatever needed, up to replacing chip with flash. I am not ready to go that far yet.
feel like i am missing something
It appears to be a real problem with flash.
No connection to computer with USB.
With power supply connected blue-green-?? screen, but I cannot connect to PC of course.
With USB cable connected blue-green-?? screen does not come up.
I figured out that pins 4 and 5 are shorten when power supply is connected. I did this with USB connection to PC, but still not connected.
For sure, USB is not functioning on device.
Will get new device, but very interested on how to repair this one. I disassembled it completely. There is no way to replace the flash chip at home, you need specific equipment and chip, of course.
What I need is surcuit diagram for S200 or similar, particularly part of diagram related to flash, radio module is not needed. Is there any possibility to get it? If I have it, I think can reprogram chip.
Thanks.
Hm. It looks like extreemly difficult to get pins layout on motherboard.
JTAG is the only solution left to access chips direct. But we need to know where JTAG pins on motherboard.
Recovered S200.
Finally very good news!
Prophet S200 was succesfully recovered with help of Arc.
He managed to discover JTAG pins, afterwards re-flashed SPL and ROM.
REALLY GOOD JOB!
Want to say special THANKS to Arc!!!
Device go live again.
Until next experiment....
But procedure to recover is in place.
Regards,
fdp24
i have a dead one too
Hi there,
I have a dead one too can you tell me how to fix it please?
dead, as in my ppc k-jam is dead
basically it hangup and i soft restarted, tried hard reset. it didnt help either. i tried restoring to factory default same thing it hangup. now it doesnt shows any signs of life . i lost my life, my buddy.
My Orange SPV M2000 will not start anymore after update. I only see Serial (on top)............ V2.07 (underneath)
I tried to update my ORANGE SPV M2000 to Tmobile's newest rom by extracting the exe. file and using maUpdateut. It started well and all of a sudden gave error "country code................"
You will not be able to fix it yourself.
Equipment and phone required physically in order to connect jtag interface and re-flash DOC.
Sorry, but this is the only solution if your bootloader is damaged.
Of course, you can try to ship it to service center. If you are lucky they will change your device. This might more simple.
Good luck.
fdp24 said:
You will not be able to fix it yourself.
Equipment and phone required physically in order to connect jtag interface and re-flash DOC.
Sorry, but this is the only solution if your bootloader is damaged.
Of course, you can try to ship it to service center. If you are lucky they will change your device. This might more simple.
Good luck.
Click to expand...
Click to collapse
I know how to open device and solder some wires to testpoints. Do you have any information where the pins are located and what software and what JTAG adapter you used? I really need to get my phone working again. It was quite expensive to purchase and to ship it to my country. Please don't destroy my hope.
hello friends,
my cousin recently buy O2 XDa ( wallaby ) for cheap one, i check on device it seems cann't boot to windows but if i hard reset and came up red, green, blue and if i press ok it came up with test all thing i confuse all the test is OK, can you all tell me how to repair the phone and waht is the problem?
thank you
dead device hope on the horizon
note my device and troubles is on the xda2
hi - i have had exactly the same issue - i have managed to reload the rom i was trying to swop and here is what i did .... it took ages and lots of patience and it is not an exact work of science but if you try my method 2 or three times it actually comes back to life ... honest !!
down load an xda2i ( yes xda2i )rom extract it using winrar or zip on your pc place dead xda2 into cradle regardless of whats on screen run himupgradenoid - the rom will run and start to load onto your device it will fail once it has failed remove xda but do nt reset - take copy of original rom which was on the device prior to your failed upgrade and extract as above. replace xda into cradle might be detected or not dont worry - run the himupgradeut from your previous working rom and wait it takes ages to connect but eventually heypresto ... you will have a working device. i know cos i done it !!! - i have not resolved all my problems yet - i still want to load latest 02 rom but even after entering correct device data into nbfs using batch file method the device crashes saying incorrect counry id. - i accidently created my problems by accidently running the wrong upgrade rom and i guess it changed somthing on my device " country code" however when i use method above to get original rom inplace and working when i extract device data into windows folder on device i still see the wwe ( world wide english) so i am still in a pickle - can anyone help me .
hello
i'm working on the project of flashing the bootloader into a totally erased and dead phone. can you send us the test points from the prophet please? and if you know their location on a WIZARD. thank you..
Somebody here Please tell what soft to use with JTAG to recover da bootloader!!!!!!!!!!!!!
get the JTAG pins for me, I will send you soft.
Wizard and Charmer pins are both needed.
hi, i've succesfully wrecked my Blueangel PH20B by flashing a modded wm6-universal-rom... i've got all the hw & sw to resurrect the phone but the jtag pins on the BA-PCB...
can someone give me a hint where i may find them? (i'm not wanting to bake the pcb as i know i'll wreck it comletley)
thanks in advance,
mario
Same problem here
Hi,
I believe I'm having the same problem
Please help me
Thax a million
so can you help me i need to write the wizard(g4) bootloader or thell me how can i do this
T-Mobile USA SDA II
Me also, i'm i need of re-writing boot-loader of T-Mobile USA SDA II
well, ok I understand that you can get the Jflash_mm working with PXA systems, you can write the definition for yourself, as for the CPU.
but I have serious doubts that inspire me to suggest you will have tiny chance to actually program a DiskOnChip Millennium series (or familiar) chip used in many platforms (actually I believe most HTC devices).
after all this means that if you are not working for (or in affiliation or partnership with) SanDisk, you are not in position to program bootloader to (not limited to) UNIVERSAL, WIZARD, PROPHET, and CHARMER (and if I remember well, BLUEANGEL and HIMALAYA) devices over JTAG.
any news............
Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.
randallstevens said:
I was feeling adventurous and started messing with the partition table
Click to expand...
Click to collapse
Hi,
On other forum one user followed suggested by me same theory of remapping paritions as described here to shrink so large /system and increase /userdata
He gotta same brick because deleted 3 partitions and then they was cannot created by any commands, so seems this method not applicable to our phone.
Next he very early quited from recovery without restoring partition table from backup.
Surprisingly, in un-offical service center phone was quickly fixed, seems with JTAG-device.
QHSUSB_DLOAD – this is fall-back low-level mode of CPU that allow access to all partitions just like fastboot
Needed to repair / writing stock ROM at factory.
Can be enabled manually by connecting to PC with holding both volume buttons. How to exit – don't know.
QPST utility not useful because we not have dump in it's proper format. So only Linux our hope.
That user tried to manage with Ubuntu but phone was not recognized. Very likely he went into something wrong.
That's very great that you created backup of whole NAND.
Maybe will be enough restore GPT (partition table), I have one and own per-partitions dump too.
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.
Bonoboo said:
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.
Click to expand...
Click to collapse
Hi Bonoboo, thank you for replying.
Unfortunately, Ubuntu isn't able to detect the emmc and therefore, I'm unable to find the "/dev/sdX" node for the device. The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
I've seen some threads wherein QPST is first used to enable the partitions detection of emmc. However, as you mentioned, we do not have the necessary MSM8227 HEX file for this.
A windows app called "s1tool.exe" can be used to flash the bootloader files from the FTF, Link to thread. However, a testpoint combination is needed to access the emergency mode. I was unable to find a testpoint for Xperia M.
Is JTAG the only way forward here? Thanks again for the help.
EDIT: Looks like the s1tool I mentioned is device specific, may not work with XM.
randallstevens said:
I'm unable to find the "/dev/sdX" node for the device.
The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
Click to expand...
Click to collapse
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
just connect your phone to PC (at this time your /var/log/kern.log should update and ttyUSB0 should be added), in terminal, cd to your download folder and run './qd.pl --check', or run 'perl ./qd.pl --check'.
Click to expand...
Click to collapse
Bonoboo said:
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
Click to expand...
Click to collapse
Hello Bonoboo,
I've tried using the qd.pl script but I'm not sure which file needs to be sent to the device when using the "qd.pl --pfile X" and the other parameters. The script detects the Qualcomm modem. I've tried uploading the first 256 kilobytes of the dump which should include the partition table but this results in an "Invalid Response" error from the script. Tried uploading the TA and some other partitions, but received the same error. No eMMC access yet. What file do you think the script requires?
randallstevens said:
What file do you think the script requires?
Click to expand...
Click to collapse
Was mentioned some *.hex, that maybe relates with same from QPST.
In threads more info.
Very likely script just not compatible with M.
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).
Bonoboo said:
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).
Click to expand...
Click to collapse
Hi, I tried long-pressing the volume key, it does not seem to work. Thanks for the confirmation about the hex file. It looks like I'll need the right files for the handset, as using hex files of similar chipsets did not help. I'll keep working on it and write back with an update if I'm able to fix it.
I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).
fakier said:
I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).
Click to expand...
Click to collapse
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.
randallstevens said:
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.
Click to expand...
Click to collapse
Thanks, a backup of my TA partition I do have...
Update
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:
randallstevens said:
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:
Click to expand...
Click to collapse
Dude what was the point of this thread and when you tried to fix your phone did you re flash stock ROM?
Reply to Piravinthb's comment
Piravinthb said:
Dude what was the point of this thread..
Click to expand...
Click to collapse
The point of this thread, dude, was to see if the device could somehow be taken out of the "Qualcomm HS-USB QDLoader 9008" mode, a (very) low-level interface meant for vendors to flash bootloaders and system images on their devices.
..and when you tried to fix your phone did you re flash stock ROM?
Click to expand...
Click to collapse
Had you googled this, you'd know that this mode isn't the same as the Flashtool flash mode or fastboot. No rom, stock or CM, can be flashed before fixing the bootloader itself, which is needed to start the device.
Not much progress could be made here since the bootloader hex files for Qualcomm's OEM tools (QPST) would be needed to fix such a hard brick. Also, the QDloader scripts mentioned earlier were written for a different chipset from the one used in Xperia M.
Cheers, RS.
randallstevens said:
Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.
Click to expand...
Click to collapse
hi i have same problem with same adventure , but i was using stock rom with customized kernel with cwm.
i think the solutions are 2
repair hard brick with JTAG or test point and s1tool what is not implemented for xperia m
see http://forum.xda-developers.com/showthread.php?t=2646405 for Z1
my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx
rafik23 said:
my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx
Click to expand...
Click to collapse
Buy a nexus 4 off amazon for 140€
It only takes 2 taps to thank somebody here.
Dear All,
I tried to restore from CM11 and did a sideload of latest amazon bin and that corrupted boot and device wont boot and to complicate the i some deleted the partitions with latest bin so the phone is stuck in Qualcomm HS-USB QDLoader 9008 mode. Please can some one upload image of 32GB version US phone so i can boot this phone. There is no mode adb or fastboot mode as we corrupt. Only way is to use Qualcomm tools to restore partition table and image.
Please someone help with this.
Any help is much appreciated.
Regards
Sudhakar J
@ggow can you help him? @pipataki
I think that is the same problem I had with my first fire phone broken... but I didn't know how to restore it and finally, I left to use as restore any broken component of new one...
If I could do something, tell me... I don't have 32GB to share in Google Drive, but in pipataki.com I can use what I need... the problem is that is a local web server, so the internet speed is the same I have at home... about 1 mega of upload speed (100 kB/second)
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
Is this what ar you trying to do? ...
Amazon Firephone Stuck in Qualcomm HS-USB QDLoader 9008
Dear Pipataki,
Yes that is what i am trying to do.
1. Is there a possibility of posting partition table and boot only
2. I can arrange for google drive if that will make it easy for you.
I checked in local stores no one has the same phone.
Regards
Sudhakar J
jsudhams said:
Dear Pipataki,
Yes that is what i am trying to do.
1. Is there a possibility of posting partition table and boot only
2. I can arrange for google drive if that will make it easy for you.
I checked in local stores no one has the same phone.
Regards
Sudhakar J
Click to expand...
Click to collapse
I think that if I do a Factory Reset and try to copy and paste the the / dir, maybe you could have it... but the problem is how to copy.
With the shell beeing root user would be possible, I supose...
jsudhams said:
Dear All,
I tried to restore from CM11 and did a sideload of latest amazon bin and that corrupted boot and device wont boot and to complicate the i some deleted the partitions with latest bin so the phone is stuck in Qualcomm HS-USB QDLoader 9008 mode. Please can some one upload image of 32GB version US phone so i can boot this phone. There is no mode adb or fastboot mode as we corrupt. Only way is to use Qualcomm tools to restore partition table and image.
Please someone help with this.
Any help is much appreciated.
Regards
Sudhakar J
Click to expand...
Click to collapse
Do you need only /boot partition or all partittion tree?... I ask you because in my last ROMs, there is no boot.img , all is in a folder... so if you need the boot partition only unzip the rom and you have it, I supose...
I tried this morning to copy all the partition tree... but was inpossible, i have no idea how it could be done... but maybe using the folders of my ROM like partittion items would solve it... (I don't know another way to restore)... if you solve it, let me know... for try to repair the other fire phone broken I have...
Same Here
pipataki said:
I tried this morning to copy all the partition tree... but was inpossible, i have no idea how it could be done... but maybe using the folders of my ROM like partittion items would solve it... (I don't know another way to restore)... if you solve it, let me know... for try to repair the other fire phone broken I have...
Click to expand...
Click to collapse
I have the same problem, trying to change the rom with ADB, never woke up again.
I thing the solution may be with something like this...
http://www.androidbrick.com/ultimat...s-are-unbrickable-qhsusb_dload_qpst_qfil_edl/
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
I am not an expert, but there seems to be some programs from Qualcomm to flash the entire system. I guess that there must be some program also to extract the system from a working phone...
I will post any news.
gastonfama said:
I have the same problem, trying to change the rom with ADB, never woke up again.
I thing the solution may be with something like this...
http://www.androidbrick.com/ultimat...s-are-unbrickable-qhsusb_dload_qpst_qfil_edl/
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
I am not an expert, but there seems to be some programs from Qualcomm to flash the entire system. I guess that there must be some program also to extract the system from a working phone...
I will post any news.
Click to expand...
Click to collapse
The problem is that doesn't work sahara protocol to recover... I just try, but sahara fails...
it would work changing the battery and/or screen?...
I had the same thing
I have bricked two phones now trying to get out of this situation.
Under Linux all the Partitions are available for viewing and some are even RW enabled like system and boot etc etc
Pushing via dd a stock system.img and boot.img does not seem to get you out of this "emergency mode" for want of better wording
Sadly the sdcard is NOT RW but is RO and forcing RW only cause the phone to bootloop back to this "emergency mode" so I could not push the the stock update.bin thinking maybe it would automatically install it then reboot.
Since I did have a backup of most partitions using dd I flashed what I could and that blow the fuse so now I get nothing at all from the phone totally dead, not even seen or detected by the PC.....
So the score is 2 - 0 to Amazon so far.
Maybe everyone who's phone is warranted should brick them and send em back to Amazon for repair and keep doing it over and over so they will eventually release the proper tools, firmware and just maybe unlock the bootloader when they are sick of spending $10000's on repairs and shipping. :fingers-crossed:
bigrammy said:
I have bricked two phones now trying to get out of this situation.
Under Linux all the Partitions are available for viewing and some are even RW enabled like system and boot etc etc
Pushing via dd a stock system.img and boot.img does not seem to get you out of this "emergency mode" for want of better wording
Sadly the sdcard is NOT RW but is RO and forcing RW only cause the phone to bootloop back to this "emergency mode" so I could not push the the stock update.bin thinking maybe it would automatically install it then reboot.
Since I did have a backup of most partitions using dd I flashed what I could and that blow the fuse so now I get nothing at all from the phone totally dead, not even seen or detected by the PC.....
So the score is 2 - 0 to Amazon so far.
Maybe everyone who's phone is warranted should brick them and send em back to Amazon for repair and keep doing it over and over so they will eventually release the proper tools, firmware and just maybe unlock the bootloader when they are sick of spending $10000's on repairs and shipping. :fingers-crossed:
Click to expand...
Click to collapse
If i was millionaire, i will buy all amazon fire phone's for 100$, but just who are in warranty. to brick them and send in warranty to [email protected] amazon company budget
ozan2 said:
If i was millionaire, i will buy all amazon fire phone's for 100$, but just who are in warranty. to brick them and send in warranty to [email protected] amazon company budget
Click to expand...
Click to collapse
Ok... That's the problem, you are saying the pure true... If we had the bootloader unlocked at least we could repair by ourselves...
In my case, as not having support of Amazon in my country, I don't have another way that only buy pieces and pray... Because the shipment to send and return to reseller cost the same...
My amazon fire phone is left in the amazon logo
My amazon fire phone is left in the amazon logo, it does nothing more, than there will be a solution. Thank you. Greetings from Venezuela
rafael_79 said:
My amazon fire phone is left in the amazon logo, it does nothing more, than there will be a solution. Thank you. Greetings from Venezuela
Click to expand...
Click to collapse
I have to replace motherboard, (and lower sensors, but these ones is because in the dissasembly broke)... so i think the only solution if is this type of brick is to buy a new moterboard, I hope to receive on monday the sensors, and fire again... but I will not spend more money with this phone...
(the motherboard is about 25$ more or less)
pipataki said:
I have to replace motherboard, (and lower sensors, but these ones is because in the dissasembly broke)... so i think the only solution if is this type of brick is to buy a new moterboard, I hope to receive on monday the sensors, and fire again... but I will not spend more money with this phone...
(the motherboard is about 25$ more or less)
Click to expand...
Click to collapse
I currently have 2 Firephones 32GB unlocked, and I would like to just change the motherboard to get 64GB, so I would like to know where you bought this motherboard at such a cheap price of $ 25.00?
Also I would like to know if it is very complicated or difficult to change the motherboard of the Amazon Firephone?
ulises.rodriguez said:
I currently have 2 Firephones 32GB unlocked, and I would like to just change the motherboard to get 64GB, so I would like to know where you bought this motherboard at such a cheap price of $ 25.00?
Also I would like to know if it is very complicated or difficult to change the motherboard of the Amazon Firephone?
Click to expand...
Click to collapse
in ebay, shipmentt not included... I only say the price without additional suplements like shipment or others (my motherboard is 32 GB)
seller:fine-part-gallery fire phone motherboard
put this in ebay app or via browser, and you have it... now is about 15$+11$(shipment)...
I think the fire is only in 16 or 32 GB, there isn't 64GB
about replacing it will do my cousin, who is the expert in electronik things of my family...
but is a bit complicated, openning first time, the lower sensors crash..
pipataki said:
in ebay, shipmentt not included... I only say the price without additional suplements like shipment or others (my motherboard is 32 GB)
seller:fine-part-gallery fire phone motherboard
put this in ebay app or via browser, and you have it... now is about 15$+11$(shipment)...
I think the fire is only in 16 or 32 GB, there isn't 64GB
about replacing it will do my cousin, who is the expert in electronik things of my family...
but is a bit complicated, openning first time, the lower sensors crash..
Click to expand...
Click to collapse
Fire Phone is avaible in 32gb and 64gb only. Dynamic perspective sensors are problem because are sticked
In my position I'm having bricked HTC M9 which need to recover user data (Photos of new born kid which don't have backups)
Symptoms :-
NO power LED (Even charger connected)
NO HTC Logo
NO boot menu
NO vibrations
Power On button do nothing
Power + Volume down nothing
But when it connected to PC it shows Qualcomm service port "Qualcomm HS-USB QDLoader 9008 (COM8)"
After spending long time on reading I figure out If I'm able to fix the partition table & connect Qualcomm HS-USB QDLoader 9006 interface,
Then the eMMC can be mounted to local PC via USB. then I can recover my data,
So I'm planing to use Qfil to flash required data to mobile
So I downloaded Qfil from here
Downloaded stock firmware from here or here
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
prog_emmc_firehose_8994_lite.mbn file found & attaching
I'm still unable to find above three files any where from internet,
Please can some one help me to find this files (or extract the from some where)
I'm attaching some Images of device manage view, Qfile & stock ROM I have respectively
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.
shivadow said:
Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi My Friend, thanx for take your time,
Yep I read it, but the problem is
1. to use this tool we need "prog_emmc_firehose_8994_lite.mbn" file
2. we can only get "rawprogram0.xml" file from this, still need "patch0.xml"
Any one could help me with this will be a great help.
Thanx Mate
Good news , I have found the programmer for MSM8994 "prog_emmc_firehose_8994_lite.mbn"
I'm attaching it above for any one who is in the same boat as me.
Please some one help me to find "rawprogram0.xml and patch0.xml" files for HTC M9
https://drive.google.com/file/d/0BzypAwIfVp1gV1Vjc2FSQlhlaHM/view?usp=sharing
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR
war357 said:
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR
Click to expand...
Click to collapse
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.
Sneakyghost said:
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.
Click to expand...
Click to collapse
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br
Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
Actually these phones are pain to me ? taking them apart and reassembling them isn't easy at all. Sadly. And the new HTC U isn't much better
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
war357 said:
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br
Click to expand...
Click to collapse
It's m possible Right now. Or I don't know any way. We don't have the resources for that. I could be wrong, but it gets harder getting these Files
Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.
war357 said:
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
Click to expand...
Click to collapse
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml
shivadow said:
Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.
Click to expand...
Click to collapse
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR
For info: https://forum.xda-developers.com/showpost.php?p=68390222&postcount=11
Bro, that was a great help,
That was a huge favor.
That was a huge favor.....
Thanx bro, thanx a lot
One more file & I'm goor to go
See you mate!
Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
and converted to rawprogram0.xml
Click to expand...
Click to collapse
war357 said:
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR
Click to expand...
Click to collapse
Thanx a lot bro, taking your time for me is much appreciated,
If possible please help me to get patch0.xml also
Thanx again
Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml
Click to expand...
Click to collapse
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR
war357 said:
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR
Click to expand...
Click to collapse
Try to use the zeroed file (empty content)
Golv said:
Try to use the zeroed file (empty content)
Click to expand...
Click to collapse
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G
gda_scooby said:
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G
Click to expand...
Click to collapse
Hi,
No Bro, Still no luck,
I don't know exact way to extract patch0.xml,
Normally it should come with firmware file,
But no sign of that on internet,
Seems really bad luck,
Any way Bro, thanx for your support,:good:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.
deleted
***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.