Develop Bugs

Bootloader dead / Recovered

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............

VS-985 lg g3 demigod pain!

I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.

still no results
To no avail I have tried everything! I have seen some changes but nothing that tells me that its fixed! I have tried qpst, but either I don't know how to run it or it wont connect properly, as a matter of fact I dont think it connects properly to any of the programs I run on it. It doesn't help that the only way the computer recognizes it is when it is on demigod mode.has anyone out there in android land had some experience or any idea of how to format the internal sd and start over from scratch?

shiftykidd said:
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
Click to expand...
Click to collapse
You managed to fix it?
am facing the same issue.

Not yet i am thinking about just sending it back to lg. It's mixed up partitions, due to power surge from unauthorized power cords.

Do you have your phone rooted and with a custom recovery?
If yes,
Give this a try:
1.Enter recovery
2.Wipe data
3.Wipe cache
4.Wipe dalvic cache
5.Reboot
I've had the same problem with an LG L9 ii and this one fixed it.
So i really hope this will help. Inform me after doing this.
Greetings.

About five months ago I was able to access recovery but nothing was functional, now I cant even turn it on, if you left it on a different charger, kernal crash handler popped up half the time. Before it quit turning on the lg boot logo started going fuzzy, logic leads me to believe its a messed up Q C mother and the partitions are scrambled due to me using a non-oem charging cord and block, I also suspect the power button mounted to the back, on top of mother might have caused some hw problems. But those are just theories, it could simply be a bad battery!

Amazon Firephone Stuck in Qualcomm HS-USB QDLoader 9008

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

Another hard brick ?

So i got one of these vs985s. and nothing. screen lit up but nothing else.
so i had a unknown or damaged usb device .long story short
got it in 9008 i follow all the guides emmc and ap test past.
but when i to the sd ram test i get a error of
========DDR TEST START
Test level = 0(check data/address line)
sbl1 partition write FAIL.. senctor 0x28000
WRITE FAIL During ddr test..
Aborted..........
Also everytime i click a restore boot image in any version of board diag tool whatever partition im trying to restore write fails....
Now i remeber back on my g2 i got the 9006 mode i was able to zero all the partitions in linux when it mounted 30 somthin drives.
Is there any info any one could give me as i have followed all the guides.. But might be missing something somewhere.
any help is greatly appreiciated

I have the exact same problem here with my father in law's D852. The phone was never rooted. I was trying to unbrick it but it didn't reboot after flashing sbl1. So I decided to try a stock rom form another source and that's when this happened. Trying to go back to the first rom didn't work, even after erasing the entire emmc. My guess is somehow, we activated permanent paper weight mode. I hope someone more qualified than us can help us, or at least confirm our phones are good for recycling...

S4 Mini i9195 only vibrates, ODIN mode boots, data recovery

Hello,
my Galaxy S4 Mini GT-i9195 died last weekend out of nothing. Battery was empty, I started it, it boots and switched off again. After I tried to charge it, nothing happens but when I longpress the power button it vibrates one time and the screen stays black.
The phone has TWRP and LineageOS on it and worked fine for some years.
What I've done and what I know:
1) Changed all but the main pcb, I have the same device again and switched all other parts. Same issue, so I'm sure the issue is on the motherboard.
2) Meassured battery current when off 0mA, when on 130-180mA
3) Meassured voltages, 1.8v and 3.0v are there when I switch the phone on
3) Meassured CMD pin on eMMC, the CPU is alive and tries to access the eMMC
What I don't know currently
1) Is the eMMC working correctly
2) Is any other hardware defect?
3) Is there some data corruption on any part of the eMMC?
Before I try to solder something on the phone I would like to test all other ways to recover my data.
The hardware itself is not important, but it would be nice to get the data. The SDcard that was used looks like the data is encrypted, so I suppose the userdata on the eMMC is encrypted as well. This means I hope to get the phone to boot to decrypt all this again.
I've seen that it could be possible to boot the phone from SDCard. Does anyone know how this oculd work?
I have a universal eMMC reader that supports the eMMC used, but don't know if it will work as long as the CPU is powered on.
Has anyone a idea what could be defect or how I can do a further diagnose of the phone to resuce my data?
Hope someone can help. Thanks!

@krater42 Welcome to XDA. When you joined, you agreed to follow the Forum Rules. Please take a moment to review them now, with special attention paid to Rule 5:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Click to expand...
Click to collapse
The duplicate post you created will be removed.

Sorry for that, read the 5. rule too late. What do you think, were is the best place for this topic? Which one should I delete?

krater42 said:
Sorry for that, read the 5. rule too late. What do you think, were is the best place for this topic? Which one should I delete?
Click to expand...
Click to collapse
Your question is on a Galaxy S4 Mini. This is the right place. We have already removed the duplicate.

Okay, new information. I ****ed up the key combination and now as I do it right, I can boot into ODIN mode.
I tried to read out the pid with heimdall and this doesn't works. On the other phone I tried the same and it works. So I suppose it's not a issue of my setup.