Revive a dead s4 mini lte GT-I9195 - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Revive a dead s4 mini lte GT-I9195 - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Hello,
I had in the first place a hanging in the boot screen issue witouth the possibility to enter the recovery mode (only download mode) so I tried to flash the custom firmware (a lot of times) and in different ways ( Kernel first then firmware, then with PIT file ... anyway) ...
The last time a was flashing the phone it simply turn off during the flash. and since then it won't turn on ... It's not a battery issue because after that I charged the battery in another working phone and still no turn on.
When I plug the phone into the PC I still hear the usual sound. So I still believe there is hope.
After some research I found an official samsung document describing how to solve the very same problem for a galaxy s4 GT-I95100 ( the file is attached).
Did someone know if we can apply this to the mini or where we can find the specific document for my phone ?

Any Help please ? ... I just want to know if my phone still can be fixed
did anyone heard of reviving a phone that doesn't turn on ?

If it can't be turned on (no download or recovery mode), then it's hard bricked and needs to be serviced. It needs to be fixed by either replacing the main board or using a jtag box to repair boot.

arco68 said:
If it can't be turned on (no download or recovery mode), then it's hard bricked and needs to be serviced. It needs to be fixed by either replacing the main board or using a jtag box to repair boot.
Click to expand...
Click to collapse
Thanks for your response Arco ... dou you know if samsung repair center is supposed to have this jtag box to repair the boot?

I don't think all of them have it. I had to send in my Galaxy W two times for the same problem, and both times they replaced the complete motherboard.

arco68 said:
I don't think all of them have it. I had to send in my Galaxy W two times for the same problem, and both times they replaced the complete motherboard.
Click to expand...
Click to collapse
okay, from what I saw when googling about this jtag box ... I must dispose of a very updated jtag box to fix my phone. I hope I'll find a repair center having this.
Thank you anyway!

You could try this. No harm trying since it looks like you'll have to send it in to Samsung anyway.
http://forum.xda-developers.com/showthread.php?p=46318162

on russian 4pda forum was published one more method of reviving the phone (translation from russian):
initial situation:
- we have a brick with killed bootloader after unsuccessful flashing, not turning on, no reaction on buttons, no any mode available (recovery, download).
What is needed:
- any Linux, like Ubuntu, but more convinient is PartedMagic of any version;
- MicroSD card;
- working phone of the same model or dump of its first 139008 blocks (about 70MB).
How to make a dump:
- on rooted device download from Google Play app "TerminalEmulator" and run it;
- Enter su, appears "[email protected]:/ #", enter "dd if=dev/block/mmcblk0 of=sdcard/mmcblk0uptop7.img count=139008";
- after completion copy file "mmcblk0uptop7.img" from the phone to PC, for example to drive C:/.
How to revive the phone:
- insert MicroSD into PC and launch "PartedMagic";
- copy dump to MicroSD, for this open Terminal, we see "[email protected]:~#", enter "dd if=/media/WIN7/mmcblck0uptop7.img of=/dev/mmcblk0", where "/media/WIN7/" - it's your drive C:/, where stored a dump, and "/dev/mmcblk0mmcblk0" - your MicroSD in PartedMagic;
- wait for completion, remove MicroSD;
- put MicroSD to non-working phone, connect the phone to PC using USB;
- if all steps are done correctly, phone will boot by pressing the keys, using bootloader from external MicroSD;
- now it is possible to re-flash internal eMMC using Odin, to make a possibility to remove external card;
- that's all, phone completely revived.
Supported devices:
- tested on i9190, will work on i9192/i9195, should work on smartphones of other brands with new Qualcomm chips.
Technical details:
- details are too big to write. If you are interested - read about MSM8930 boot architecture and etc.
Some conclusions:
- Qualcomm has made a good modern chip, with a lot of feasibility, but not placing many information to open sources;
- Samsung - trying to complicate life of users by integrating of its own digital signature, what is leading to immediate bricking of devices when trying to modify bootloader. Be careful.
Click to expand...
Click to collapse

babuk123 said:
on russian 4pda forum was published one more method of reviving the phone (translation from russian):
Click to expand...
Click to collapse
can someone send me these files needed because I cannot find another working s4 mini. Thanks

if the phone can boot on download mode, you must flash debrick.img and stock firmware

Yes but my phone does not even boot... no mode

Anopy45 said:
Yes but my phone does not even boot... no mode
Click to expand...
Click to collapse
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
oualibadr said:
Hello,
I had in the first place a hanging in the boot screen issue witouth the possibility to enter the recovery mode (only download mode) so I tried to flash the custom firmware (a lot of times) and in different ways ( Kernel first then firmware, then with PIT file ... anyway) ...
The last time a was flashing the phone it simply turn off during the flash. and since then it won't turn on ... It's not a battery issue because after that I charged the battery in another working phone and still no turn on.
When I plug the phone into the PC I still hear the usual sound. So I still believe there is hope.
After some research I found an official samsung document describing how to solve the very same problem for a galaxy s4 GT-I95100 ( the file is attached).
Did someone know if we can apply this to the mini or where we can find the specific document for my phone ?
Click to expand...
Click to collapse
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...

andreluigo said:
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...
Click to expand...
Click to collapse
Did you fix yours? Can you share the procedures and and the files if possible?

sarry86 said:
Did you fix yours? Can you share the procedures and and the files if possible?
Click to expand...
Click to collapse
Unfortunatelly, I couldn't fix it...
I sold it for taking of pieces!

andreluigo said:
Unfortunatelly, I couldn't fix it...
I sold it for taking of pieces!
Click to expand...
Click to collapse
You could have booted it like me but i am just stuck in a boot loop no matter what i am doing with odin

sarry86 said:
Did you fix yours? Can you share the procedures and and the files if possible?
Click to expand...
Click to collapse
The Russian method mentioned is just making a debrick image, search the debrck thread for file & procedure or internet for a debrick image for your phone

DarkJoker360 said:
if the phone can boot on download mode, you must flash debrick.img and stock firmware
Click to expand...
Click to collapse
How can i flash debrick.img my phone is booting on download mode

ArduinoPi said:
How can i flash debrick.img my phone is booting on download mode
Click to expand...
Click to collapse
Just put it in sdcard and boot normally

DarkJoker360 said:
Just put it in sdcard and boot normally
Click to expand...
Click to collapse
sorry I don't understand. Can you tell me more, please!

Related

[Q] Rogers SGH-I747M Hard Brick, JTAG only option?

Hello,
I just rooted my Samsung Galaxy S3 today. I copied several ROM zip files (i think there were 4) to my SD card to test out using MTP. As you may know, MTP (on Windows 7) is not the greatest experience. Since the copy was taking so long, I canceled it. I now know that when you do that MTP seems to leave the incomplete file there with the fill file size. I suspect the is the root of the issue.
I went to install the Omega v46.1 Jelly Bean 4.2.2 ROM after testing a different one that I was not happy with. Omega game up with its installer, everything seemed to work good. It asked to wipe the user data, and reboot the device. All looks good. I could not wait to try another ROM.
Blank screen.... waiting, waiting... Maybe they just have no boot logo.... waiting. Okay after waiting several hours for it to boot I thought maybe I would try to reboot and clear the user data and cache myself. Tried to reboot. Nothing happened. No vibration, no LED, not logo.
Cannot get into Download mode. Cannot get into Recovery.
Pull battery, wait. Put battery in while holding Volume key, Power button and Home. Nothing at all. Battery pull and waited a few hours. Tried again. Nothing. Panic starts.... I remembered the MTP file copy and checked the ROM zip files. Incomplete zip file.... Damn.
It is not easy to cover everything I have tried to fix it or all of the research I have done, but I'll try.
Researched bricked devices. Learned of hard vs soft. This does not appear to be soft to me, but why would my bootloader be damaged by installing this ROM?? I am new to this, but I think I understand the difference pretty good.
I spent the last few hours trying to find a micro USB cable that I could use to make a USB Jig. I did that using this guide and it did not help
http://forum.xda-developers.com/showthread.php?t=2121306
And this guide
http://forum.xda-developers.com/showthread.php?p=8822843
Researched the Jig more to make sure I got it right. Tested again with multimeter... It all looks good to me. Damn, it must be a real hard brick.
When I plug the phone into my PC without the battery in the phone I get a red LED.
When I plug it in with the battery in, I get no LED, no screen/logo, ect. Nothing. Windows does detect a device called "QHSUSB_DLOAD". I got the Qualcomm driver and QPTS hoping that there would be something that I could do... maybe backup my friend's bootrom and put it on my phone... The COM11 port from the device is not detected, so even if I could figure out a way to do what I said, I have no way to do it. Could be a Windows 7 unsigned drivers issue, but I have tried 3 different solutions to that without knowing how the device should look in Device Manager if the driver is accepted.
Looked for other solutions...
Old thread, HTC specific, not really any help... http://forum.xda-developers.com/showthread.php?t=822939
Bad news, need to send device back... http://forum.xda-developers.com/showthread.php?t=1651149
This looks possible, but I have not tried it yet because the steps are not that clear and it requires a Linux box, and I don't really want to dig into that can of worms right now. (which distro, which PC do I use, what software/packages are required, ect) http://forum.xda-developers.com/showthread.php?t=1916796
Possible solution with linux box... http://forum.xda-developers.com/showthread.php?t=2239451
Goes on to this one, a lot like the other linux option above... http://forum.xda-developers.com/showthread.php?t=2369125
If I am missing anything, please let me know. Is this Linux option really a possibility? Do I need a Rogers bootloader?
Perhaps I can use this idea to get my friend to back his up for me off his Rogers S3: http://forum.xda-developers.com/showthread.php?t=2374958
I could try the linux option tomorrow, or the JTAG tomorrow if I drive an hour away to a guy that can do it.

dege13 said:
Hello,
I just rooted my Samsung Galaxy S3 today. I copied several ROM zip files (i think there were 4) to my SD card to test out using MTP. As you may know, MTP (on Windows 7) is not the greatest experience. Since the copy was taking so long, I canceled it. I now know that when you do that MTP seems to leave the incomplete file there with the fill file size. I suspect the is the root of the issue.
I went to install the Omega v46.1 Jelly Bean 4.2.2 ROM after testing a different one that I was not happy with. Omega game up with its installer, everything seemed to work good. It asked to wipe the user data, and reboot the device. All looks good. I could not wait to try another ROM.
Blank screen.... waiting, waiting... Maybe they just have no boot logo.... waiting. Okay after waiting several hours for it to boot I thought maybe I would try to reboot and clear the user data and cache myself. Tried to reboot. Nothing happened. No vibration, no LED, not logo.
Cannot get into Download mode. Cannot get into Recovery.
Pull battery, wait. Put battery in while holding Volume key, Power button and Home. Nothing at all. Battery pull and waited a few hours. Tried again. Nothing. Panic starts.... I remembered the MTP file copy and checked the ROM zip files. Incomplete zip file.... Damn.
It is not easy to cover everything I have tried to fix it or all of the research I have done, but I'll try.
Researched bricked devices. Learned of hard vs soft. This does not appear to be soft to me, but why would my bootloader be damaged by installing this ROM?? I am new to this, but I think I understand the difference pretty good.
I spent the last few hours trying to find a micro USB cable that I could use to make a USB Jig. I did that using this guide and it did not help
http://forum.xda-developers.com/showthread.php?t=2121306
And this guide
http://forum.xda-developers.com/showthread.php?p=8822843
Researched the Jig more to make sure I got it right. Tested again with multimeter... It all looks good to me. Damn, it must be a real hard brick.
When I plug the phone into my PC without the battery in the phone I get a red LED.
When I plug it in with the battery in, I get no LED, no screen/logo, ect. Nothing. Windows does detect a device called "QHSUSB_DLOAD". I got the Qualcomm driver and QPTS hoping that there would be something that I could do... maybe backup my friend's bootrom and put it on my phone... The COM11 port from the device is not detected, so even if I could figure out a way to do what I said, I have no way to do it. Could be a Windows 7 unsigned drivers issue, but I have tried 3 different solutions to that without knowing how the device should look in Device Manager if the driver is accepted.
Looked for other solutions...
Old thread, HTC specific, not really any help... http://forum.xda-developers.com/showthread.php?t=822939
Bad news, need to send device back... http://forum.xda-developers.com/showthread.php?t=1651149
This looks possible, but I have not tried it yet because the steps are not that clear and it requires a Linux box, and I don't really want to dig into that can of worms right now. (which distro, which PC do I use, what software/packages are required, ect) http://forum.xda-developers.com/showthread.php?t=1916796
Possible solution with linux box... http://forum.xda-developers.com/showthread.php?t=2239451
Goes on to this one, a lot like the other linux option above... http://forum.xda-developers.com/showthread.php?t=2369125
If I am missing anything, please let me know. Is this Linux option really a possibility? Do I need a Rogers bootloader?
Perhaps I can use this idea to get my friend to back his up for me off his Rogers S3: http://forum.xda-developers.com/showthread.php?t=2374958
I could try the linux option tomorrow, or the JTAG tomorrow if I drive an hour away to a guy that can do it.
Click to expand...
Click to collapse
I had the exactly same thing as you . I flashed the omega 4.1.2 rom and got the black screen.....
what can we do now?

yaoll78 said:
I had the exactly same thing as you . I flashed the omega 4.1.2 rom and got the black screen.....
what can we do now?
Click to expand...
Click to collapse
You guys flashed a ROM for the international S3. Check the forum you got that ROM from.
Quite sure JTAG is a good place to start now.

SD CARD
hi there
i have an SDcard of 4GB i tried on 4 S3 i747M hard bricked phones its worked ....this card let them alive to download mode by pressing volume down key +home key + power. i want to share this image but when ever i connect this card to my PC (windows) its shows (need to format your card)
is there any software so i can make image and share...to help those who hard-bricked their phones.
regards

rasgula said:
hi there
i have an SDcard of 4GB i tried on 4 S3 i747M hard bricked phones its worked ....this card let them alive to download mode by pressing volume down key +home key + power. i want to share this image but when ever i connect this card to my PC (windows) its shows (need to format your card)
is there any software so i can make image and share...to help those who hard-bricked their phones.
regards
Click to expand...
Click to collapse
Unplug and plug till pc recognize it with your files on it. I need that image so if you could share it, it would be appreciate.

I want to share but how to extract the image from sd card?
Sent from my C6506 using Tapatalk

rasgula said:
I want to share but how to extract the image from sd card?
Sent from my C6506 using Tapatalk
Click to expand...
Click to collapse
By Mr.X ''If you want to create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command''

Hello, i have the same problem with an i747m, i'd appreciate if some one can share the SD image to fix this thx all for your help and i hope it wont take to long,

Cerisan said:
Hello, i have the same problem with an i747m, i'd appreciate if some one can share the SD image to fix this thx all for your help and i hope it wont take to long,
Click to expand...
Click to collapse
You flashed the wrong image too? Your phone also doesn't go into download or recovery?

Unbrink was successful
audit13 said:
You flashed the wrong image too? Your phone also doesn't go into download or recovery?
Click to expand...
Click to collapse
Hello, i hardbricked my phone with other method, but it had the same symptoms as your bricked phones, here is a link to a SD image that worked like a charm for me, tested with a 64GB micro SD, and used win32diskmanager so i can create the SD in windows, cheers and good luck unbriking your phone
www(mediafire(com/download/0vg9sgcvk4zuwm0/debrick-SGH-I747M-UEMK5.img
PS The unbrink was successful , i really dont remember all the posts where i get those files but here's the file for this thread

salam i downloaded 4.4.2 rom from sammobile.com and flashed it with mobile odin everything was cool it installed sucessfully but my sim was not detected so i reebooted it but nothing happened instead it was hard bricked so i request you to give a debrick file for 4.4.2 as 4.3 debrick file does nothing for me thanks in advance waiting for ur reply
---------- Post added at 11:22 AM ---------- Previous post was at 11:15 AM ----------
rasgula said:
hi there
i have an SDcard of 4GB i tried on 4 S3 i747M hard bricked phones its worked ....this card let them alive to download mode by pressing volume down key +home key + power. i want to share this image but when ever i connect this card to my PC (windows) its shows (need to format your card)
is there any software so i can make image and share...to help those who hard-bricked their phones.
regards
Click to expand...
Click to collapse
sir i downloaded 4.4.2 rom from sammobile.com and flashed it with mobile odin everything was cool it installed sucessfully but my sim was not detected so i reebooted it but nothing happened instead it was hard bricked so i request you to give a debrick file for 4.4.2 as 4.3 debrick file does nothing for me thanks in advance waiting for ur reply

Try this
www(mediafire(com/download/0vg9sgcvk4zuwm0/debrick-SGH-I747M-UEMK5.img
Sent from my SM-N900W8 using Tapatalk

Just fyi, in case you didn't see my other posts about it, updating from 4.3 to 4.4.2 using Mobile Odin will brick the device. MO cannot flash the full firmware so your brick was caused by flashing the modem onto 4.3 firmware.

rasgula said:
Try this
www(mediafire(com/download/0vg9sgcvk4zuwm0/debrick-SGH-I747M-UEMK5.img
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
plz provide ur cell no so that we can discuss it easily this file didnt worked for me
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
DocHoliday77 said:
Just fyi, in case you didn't see my other posts about it, updating from 4.3 to 4.4.2 using Mobile Odin will brick the device. MO cannot flash the full firmware so your brick was caused by flashing the modem onto 4.3 firmware.
Click to expand...
Click to collapse
sir what to do now? as 4.3 debrick img above didnt worked for me

Do you have an I747M? If you have the I747 that image won't work.
I just posted two 4.3 images to try in the debrick thread. This should probably be discussed there anyway just so all of the info is easy to find.

DocHoliday77 said:
Do you have an I747M? If you have the I747 that image won't work.
I just posted two 4.3 images to try in the debrick thread. This should probably be discussed there anyway just so all of the info is easy to find.
Click to expand...
Click to collapse
its i747m rogers bricked it by flashing 4.4.2 with mobile odin

Mobile odin cannot flash the full firmware, so you ended up with the 4.4.2 modem on 4.3 firmware which we know will brick.
You will need to use a debrick.img from another I747M, probably from another Rogers one specifically. Not sure if it'll work or not from another carrier.
Note that we have yet to get it working for any device that bricked by flashing the modem. Watch the debrick thread for updates.

[Q] Bricked Galaxy W (What I did, What I get)

Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks

nemli said:
Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks
Click to expand...
Click to collapse
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can

sujithar37 said:
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.

nemli said:
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.
Click to expand...
Click to collapse
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can

sujithar37 said:
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
Thanks for your valuable responses. I will try what is recommended in those two links, and of course will give the feedback to here to help the (potential) brickers.

full brick
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks

nemli said:
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks
Click to expand...
Click to collapse
same problem as me
usb does not recognize my phone
if u find a solution contact me please

Solved by JTAG
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.

nemli said:
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.
Click to expand...
Click to collapse
How much did he charge you for the JTAG? I am looking to JTAG few phones

MayB4ck said:
How much did he charge you for the JTAG? I am looking to JTAG few phones
Click to expand...
Click to collapse
Nearly 20€ per JTAG.

If someone need QHSUSB_DLOAD solution...
Maybe I can help him...
You need Qualcomm Drivers... forgotten which one exactly I have used...
QPST Version Build 411
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9
Procedure looks similar to this:
forum.xda-developers.com/attachment.php?attachmentid=2754655&d=1400627472
In this Thread I have tried many things...
http://forum.xda-developers.com/showpost.php?p=52808706&postcount=282
I could prepare files for testing for I8150...
Not tested by me nor confirmed with I8150... as only S8600 for me available...
If someony want test... PM me.
Next few hours or days I could upload files for QPST...
Code:
MBR from I8150
DBL from I8150
OSBL from I8150
Need testers and feedback please.
Best Regards

Will check my HD for Qualcomm drivers...
Maybe upload later...
Here are test files... because untested...
Risk to reach other bad status... So you could need JTAG...
Short description...
DBL and OSBL are taken from JTAG dump...
It seems chinese Version could be different...
But MBR... first 512 Bytes are 1:1 same in all I8150 JTAG dumps I have on my HD...
partition.mbn is MBR from I8150... 512 Byte
DBL and OSBL have size from partition... extracted from JTAG dump...
DBL is in partition 2
OSBL in partition 3...
Settings for QPST are hopefully visible in Screenshot...
It is mandatory to use QPST Build 411... older Versions not accept MBR as partition.mbn without header...
Header in MBR not deadly but could be bring other trouble...
For testing now only correct drivers "missing"...
I have so many stuff downloaded...
Will try to find correct one.
Again, I have only S8600 for test...
Maybe with I8150 not possible...
But before you buy JTAG you can try.
Good luck.
Best Regards
Edit 1.
Qualcomm driver to find should be not impossible... use magic search word: QHSUSB_DLOAD... for instance here:
http://forum.xda-developers.com/showpost.php?p=40072841&postcount=1
or try this one:
http://forum.xda-developers.com/showpost.php?p=40195799&postcount=7
And here again Link for working confirmed QPST Version Build 411... tested successfully by me with S8600:
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9

[Q] Dead I9082 - I can't turn on my Phone

Dear Friends,
I have Samsung Grand I9082 that was stuck on logo screen.
I tried to flash it many times but I failed because I had the problem of "VHX_21nm_3bitMLC_8GB_p10"
So I downloaded the full flash files from this post in "http://forum.gsmhosting.com/vbb/f684/help-samsung-i9082-hank-logo-1780647/".
In the download mode I selected all files ((except the pda file)).
The download process is completed successfully and the phone restarted then screen became blank.
Now the phone is dead I can't open it in any mode even it doesn't be charged and the pc can't recognize it.
:crying:
Please I need your help.
Thanks in advance.

Go through the flashing guides again.
The pda file is which is the ROM file.

DMJoh said:
Go through the flashing guides again.
The pda file is which is the ROM file.
Click to expand...
Click to collapse
The problem that I cann't open my phone in any mode download or recovery mode.
PC cann't recognize the phone if i connected it

Did I lose my phone??

agsao said:
Did I lose my phone??
Click to expand...
Click to collapse
If it doesn't start then
Be prepaid to buy a new device.

Preshak said:
If it doesn't start then
Be prepaid to buy a new device.
Click to expand...
Click to collapse
I think the problem is software problem so it could solved.
When I connect the phone to PC it is recognized as unknown device not as previous which I could recognize it by Odin.

agsao said:
I think the problem is software problem so it could solved.
When I connect the phone to PC it is recognized as unknown device not as previous which I could recognize it by Odin.
Click to expand...
Click to collapse
Same thing happened with me last year...!!!!
I flashed a firmware using odin on my note...
I flashed wrong firmware for my note.
Aftr many attempts Odin was saying unrecognised device...!!!
I hard bricked my note...!!!!
Screen was blank..!!!
Ask help from dev.!! Pm them..!!
Hope dev can save your mobile...!!!
Try using heimdell..!!!
Its a software For bricked samsung mobiles...!!!

I think that the following post may help:
http://forum.xda-developers.com/showthread.php?t=2369125
But I need experts help.

hmm
its easy open odin connect your phone with pc in switched off mode ( remove battery before connecting to pc & when connected insert battery ) press vol down + home + power hopefully that should work for you cause the issue is windows don't install proper drivers & pc keeps showing unknown usb device connected or similar bla bla bla i don't know what this does but i am in similar situation almost 5-7 times till now with diff samsung models & this always worked for me hopefully for you too may work good luck ! :fingers-crossed:

BEingNiCK said:
hmm
its easy open odin connect your phone with pc in switched off mode ( remove battery before connecting to pc & when connected insert battery ) press vol down + home + power hopefully that should work for you cause the issue is windows don't install proper drivers & pc keeps showing unknown usb device connected or similar bla bla bla i don't know what this does but i am in similar situation almost 5-7 times till now with diff samsung models & this always worked for me hopefully for you too may work good luck ! :fingers-crossed:
Click to expand...
Click to collapse
Good to see you back.

BEingNiCK said:
hmm
its easy open odin connect your phone with pc in switched off mode ( remove battery before connecting to pc & when connected insert battery ) press vol down + home + power hopefully that should work for you cause the issue is windows don't install proper drivers & pc keeps showing unknown usb device connected or similar bla bla bla i don't know what this does but i am in similar situation almost 5-7 times till now with diff samsung models & this always worked for me hopefully for you too may work good luck ! :fingers-crossed:
Click to expand...
Click to collapse
Dear,
Thanks for your reply.
I've tried many times but I failed, the phone can't be detected by Pc nor ODIN.
I went to maintenance store and they told me that it need the bootloader to be installed and they failed to flash it using JTAG box.
What Can I Do!!!!!

akiratoriyama said:
Good to see you back.
Click to expand...
Click to collapse
not yet bro still busy with personal
---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------
agsao said:
Dear,
Thanks for your reply.
I've tried many times but I failed, the phone can't be detected by Pc nor ODIN.
I went to maintenance store and they told me that it need the bootloader to be installed and they failed to flash it using JTAG box.
What Can I Do!!!!!
Click to expand...
Click to collapse
oops that hurts there is only 1 way you can make it work again i had same issue yesterday with s7562 just a few minutes before got known how to fix this & the only thing that worked for me was this thread
http://forum.xda-developers.com/showthread.php?t=2317311
don't forget to press thanks for OP, if it works for you :highfive: good luck !

BEingNiCK said:
not yet bro still busy with personal
---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------
oops that hurts there is only 1 way you can make it work again i had same issue yesterday with s7562 just a few minutes before got known how to fix this & the only thing that worked for me was this thread
http://forum.xda-developers.com/showthread.php?t=2317311
don't forget to press thanks for OP, if it works for you :highfive: good luck !
Click to expand...
Click to collapse
What is the specific post number do you think it will solve my problem??
I think that this thread is about flashing phone under Ubuntu, but I can't start my phone!!!

agsao said:
What is the specific post number do you think it will solve my problem??
I think that this thread is about flashing phone under Ubuntu, but I can't start my phone!!!
Click to expand...
Click to collapse
previously you didn't mentioned that your phone don't even start, as per your later post you said it is recognized as unknown device that means device is able to response to your computer
& if all above is correct then flashing through ubuntu or any linux distro is only your last option cause there is no such thing as unknown device in ubuntu
i had a similar phone that won't boot in recovery nor download mode only blank black screen i tried many option but ubuntu was life saver for me, try it its worth :good:

Dear Friend,
Thanks for your reply.
BEingNiCK said:
previously you didn't mentioned that your phone don't even start, as per your later post you said it is recognized as unknown device that means device is able to response to your computer
Click to expand...
Click to collapse
If you read the title of my thread and the first post you will discover that my phone can't be turn on.
Anyway should I have Ubuntu or could I try this on PartedMagic live cd?

agsao said:
I think the problem is software problem so it could solved.
When I connect the phone to PC it is recognized as unknown device not as previous which I could recognize it by Odin.
Click to expand...
Click to collapse
this .

BEingNiCK said:
this .
Click to expand...
Click to collapse
Yes, Phone doesn't start (no screen, no download mode, no recovery mode, and can't be recognized by ODIN)
But when I connect it to the PC I hear the sound of the connected USB (from windows themes) and in the devices manager it's found as unknown device

agsao said:
Yes, Phone doesn't start (no screen, no download mode, no recovery mode, and can't be recognized by ODIN)
But when I connect it to the PC I hear the sound of the connected USB (from windows themes) and in the devices manager it's found as unknown device
Click to expand...
Click to collapse
seems hard bricked
here are few option the best is USB JIG buy it from ebay or amazon USB JIG costs no more then 200Rs ( 3-4 dollar )
second alternative ways am attaching links this helped me few times so i always have them bookmarked may work for you too but i still prefer USB JIG method
http://forum.xda-developers.com/showthread.php?t=1242466
http://en.miui.com/thread-14903-1-1.html

BEingNiCK said:
seems hard bricked
here are few option the best is USB JIG buy it from ebay or amazon USB JIG costs no more then 200Rs ( 3-4 dollar )
second alternative ways am attaching links this helped me few times so i always have them bookmarked may work for you too but i still prefer USB JIG method
http://forum.xda-developers.com/showthread.php?t=1242466
http://en.miui.com/thread-14903-1-1.html
Click to expand...
Click to collapse
Dear friend,
Thanks for your concern.
I have created a USB JIG and it doesn't work, then I've bought a new and it also doesn't work.
I've to check the links that you've post.
Regards,

Unbrick bricked by writing boot.img to wrong mmcblk

Hello community members,
TL;DR no adb, no fastboot, no flashmode, no QDloader (or similar) ... how to unbrick it?
I was trying to force Android to allow lower lcd backlight brightness levels by patching framework-res.apk and I had the edited zip file ready to flash. Then I realized that my Android 7 Ressurection remix ROM (thread) flashed Cyanogenmod recovery, which I don't like. So I decided to reflash TWRP 3.0.2 (link) ( edit: using "fastboot flash boot twrp.img", which was almost fatal mistake) and it has gone almost well. The phone started to boot into recovery mode everytime (and took a long time doing so). So I googled a bit and found this thread which lead me to this thread. I was looking forward to seeing my display brightness at lower than default values, so I probably skipped some security checks and texts with red color, so I flashed the zip with the boot.img replaced. After flashing I chose reboot and nothing happened since.
The problem is I flashed something that was not for my device (extracted boot.img to wrong mmcblk). The command that bricked my phone is (from META-INF/com/google/android/updater-script):
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p6");
After that it doesn't boot, doesn't light up LED (even when charging), doesn't get detected by PC in any state.
So I have no adb, no fastboot and no flashmode and not even a QDloader or similar mode.
Is there a way to unbrick it?
EDIT: How to unbrick it using JTAG interface? If I find somebody that has the required equipment, what data do I need to give them?

Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone

valkata752 said:
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
Click to expand...
Click to collapse
Nope, I found no solution ... even some kind of Qualcomm flashing mode via COM (serial port over USB) does not show up nowhere. I gave up and bought a used S5 mini, which is full of features I appreciate.
I'm gonna keep this Xperia M for some time if some solution comes up.

hi , can you boot into recovery ? ..if yes, i can maybe help

olibub said:
hi , can you boot into recovery ? ..if yes, i can maybe help
Click to expand...
Click to collapse
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-

olibub said:
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
Click to expand...
Click to collapse
Nice looking tutorial, but I cannot find any download link for that One Click Unbrick Tool in that article. I doubt it would work, they are not explaining what it does.
Nicklas Van Dam said:
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
Click to expand...
Click to collapse
No, as I said. The partition that got overwritten was /dev/block/mmcblk0p6. It was overwritten by boot.img from LG OPTIMUS 3D that I link to in the main post.

here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310

olibub said:
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I don't think this has any chance that it will work.
"This Software:
Will work on all Samsung devices which use Odin3"

Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?

PhoenixTwoFive said:
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
Click to expand...
Click to collapse
I know what Flashtool is. I know what ftf is. I used it once I think.
But the phone does not boot into flashmode as I mention in the main post.

[Urgent!] I need help immediately with a hard-brick device (I have limited time)

First of all, sorry if you do not use the forum, but I'm in a hurry and desperate for the problem I have with a phone of a relative of mine
If some mod sees this and I'm breaking some rule, please let me know but do not close the account or delete the post please </ 3
today my cousin wanted to change his phone for another, for this he had to change the imei but by mistake I have brickead (it was not for the change of imei, keep reading)
for this, you should have the device rooted, and proceeded to do it (it was not for this either, keep reading)
many will think, you have done wrong the change of imei, because no, I have not arrived at that, maybe I have rooted badly? no, it does not reach that either, the device has been in HARD BRICK state after using odin to install the original firmware.
the steps I followed this video and all worked, only my phone decomposed:
watch?v=3HWUs_GN02 (add youtube url before)
I had installed kingroot but the adaptation was not finished so nothing happened, the em was unlocked and I did it with odin 3.7.10 with the firmware _G532MUMU1APK4_CL9809978_QB11561696_REV00_user_low_ship_MULTI_CERT (I do not know if it is the stock or not, but the owner of the video said that yes)
symptom:
- the device does not turn on or show the charging animation
- the device does not enter the downloader mode or the recovery
- the pc does not detect the device
additional note:
the OEM was unlocked
phone:
J2 Prime SM-G532M :crying:
sorry my english im spanish

symptom:
- the device does not turn on or show the charging animation
- the device does not enter the downloader mode or the recovery
- the pc does not detect the device
Click to expand...
Click to collapse
does not enter the downloader mode
Click to expand...
Click to collapse
Impossible to fix i guess?
Lots of problem with your process to <Insert what you've done> !
odin 3.7.10
Click to expand...
Click to collapse
IS WAY TOO OLD. Recent version is 3.12.3.
_G532MUMU1APK4_CL9809978_QB11561696_REV00_user_low _ship_MULTI_CERT
Click to expand...
Click to collapse
Specifically, the "APK4". According to Updato this dates wayyy back to December 2016.
watch?v=3HWUs_GN02 (add youtube url before)
Click to expand...
Click to collapse
Video not available on my side? Also, don't 100% trust YouTube video. Most instructions on XDA are clear enough to <insert what you've done>.

Video not available for me too. You basically trusted your phone to a random guy, instead of searching the proper firmware for your phone in trusted websites (like SamMobile).
GalletitaOreo said:
- the device does not enter the downloader mode or the recovery
- the pc does not detect the device
Click to expand...
Click to collapse
Luck trying to unbrick it but, if not detected by pc and can't go into download mode, i think you killed it.

TBM 13 said:
Video not available for me too. You basically trusted your phone to a random guy, instead of searching the proper firmware for your phone in trusted websites (like SamMobile).
Luck trying to unbrick it but, if not detected by pc and can't go into download mode, i think you killed it.
Click to expand...
Click to collapse
I've already taken it to the technical service u.u I hope it has a solution

Develop Bugs

welcome