Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Any help.. please?
Khaled125 said:
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Click to expand...
Click to collapse
probably QHSUSB_DLOAD, which is a hard brick, you might be able to fix with a debrick image
Sent from my Galaxy S4 Mini using XDA Labs
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Khaled125 said:
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Click to expand...
Click to collapse
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Click to expand...
Click to collapse
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Khaled125 said:
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Click to expand...
Click to collapse
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
Wanderful, Thank you! should I mark this as solved?
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Khaled125 said:
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Click to expand...
Click to collapse
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Just found it, Though if your link would have directed to page 8 rather than 10 that would have been fantastic! I thought You ment the main post which also helped me alot. How ever do I really have to downoad monster legands to be able to download the foking file?
oh never mind, Just a damn ad
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
And please pardon me if my questions are spammy or annoying, There are a whole lot of steps through it and neither google nor the forum seem to be answering it so I might just consult you for that.
From what I understand, You flash the debrick file to the sd card using this 32 bit sd flasher thing and then it just works because the booting files are on the sd card but it will not boot without it. So how can you fix the corrupted boot loader AND how can I restore my sd card back to normal, I have seen a video for it but he is using ubuntu and command lines and stuff.
Khaled125 said:
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
Click to expand...
Click to collapse
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Click to expand...
Click to collapse
Yes, that was what I understood already but thank you anyway! My question was How? on both creating the debrick file and restoring both sd card (too make it work as a readable card rather than a booting device if it does not already) and fix the phones internal memory without actually reseting the whole phone and if there are no way else to fix internal memory... to back up the whole thing.
thank you!
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
WANDEFUL! My phone actually viperated and showed color!
however.. it gives this on a black screen.
boot recovery
check boot partitions
copy from t flash
boot recovery
write 139008
reboot
and obviously reboots, thoughts?
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Khaled125 said:
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Click to expand...
Click to collapse
I think the important thing is the bootloader (& pit must be the same) that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
I think the important thing is the bootloader, that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
Thats great! good luck at your work, when you are back though I need to tell you this
I have another device of the exact same model that is kikkat not rooted (kitkat will have bootloader version 2 right?) if only I knew how to get the file out and then do all the stuff again, ill keep searching since you are at work now, will keep you updated. please help about it though if you can*
so if someone say for example has android 5 on an s4 mini, he will never get his phone back to work unless some one made a debrick file for it? if the previous statments were true?
My questions are:
Extract that file from the other phone, if I managed to answer it ill tell you.
To get my SD card back to work and fix my emmc
Iam not giving up on my emmc yet though, iam sure there is a way to solve it, if not then how to fix that failed emmc?
thanks again!
Related
So Ive had my GS3 for a few weeks now and no issues, been stock rooted with the 6.0.1.2 CWM (non touch).
Was browsing around on the General forum and noticed this sticky called "[INDEX] AT&T GS III - I747 {ROMs/Root/Recovery.. etc}"
In there was a 6.0.1.4 CWM, I noticed both were CWM flashable. One for touch and nontouch.
So I downloaded it directly to the phone, booted into CWM, flashed the touch version, and told it to reboot recovery. And since then the phone is basically bricked. It never turned back on, screen remains black. Nothing happens. Cant force it into Download mode either. I took the battery out and put the USB cable in and all I get is the RED LED for about 1min. I get a qhsusb_dload driver that doesnt load on the computer, nothing else. So the phone is basically bricked.
I then decided to see what happened, i downloaded the flash file that was in that thread which is here
http://dl.dropbox.com/u/31151290/CWM/CWM_Touch_6.0.1.4.zip
When I open it and look at the updater-script, I see a problem. This is flashing the recovery to mmcblk0p8
The i747's recovery partition is mmcblk0p18
So this thread that is referencing these two CWMs probably should be pulled or fixed, cause p8 partition is tz. Not sure what that is, but it almost looks like its completely screwed the bootloader part.
Any way to recover this or is JTAG service the only option for my paper weight?
Dixit
I've heard on another thread someone installing CWM Touch had the same problem, vaguely light yours.
All I can say from what knowledge I have is Odin or getting a Jig. Last resort's are better than Service, lol.
Goodluck :]
Jig won't work. You are hard bricked sorry for your bad luck!!! I had a hard brick and had to send mine for jtag repair. If you live in the states you could send your phone to get repaired and get it back in 4 business days average. (varies).
If you still have warrenty... go that route!!
Sent from my Desire HD using Tapatalk 2
http://forum.xda-developers.com/showthread.php?p=32113899
Check this thread
Sent from my SGH-I747 using xda app-developers app
What sucks is the thread is a sticky and points to these two CWM files to use and technically both are wrong. The moderators need to pull those two links. As I mentioned earlier, those two zips are flashing to pEIGHT (p8) when it whould be pEIGHTEEN(p18). Thats why it got bricked.
Dixit
I did the same thing. It was for the Galaxy Nexus. The person linked to a single post, so it was to hard to tell what that recovery was for. I still wonder if that person did it on purpose.
Sent from my SAMSUNG-SGH-I747 using xda premium
dixit said:
What sucks is the thread is a sticky and points to these two CWM files to use and technically both are wrong. The moderators need to pull those two links. As I mentioned earlier, those two zips are flashing to pEIGHT (p8) when it whould be pEIGHTEEN(p18). Thats why it got bricked.
Dixit
Click to expand...
Click to collapse
If you feel that strongly about it, report the thread. In Web view or on your pc, look to the right of a post, next to the post count for that thread. Little yellow triangle. Press that. I usually mark 99.9% of the stuff i report as post/thread maintenance. After that, you'll get a pm from the moderator handling the report. Then you'll get another when the report is considered to be handled.
ouch.. good luck man
mrhaley30705 said:
If you feel that strongly about it, report the thread. In Web view or on your pc, look to the right of a post, next to the post count for that thread. Little yellow triangle. Press that. I usually mark 99.9% of the stuff i report as post/thread maintenance. After that, you'll get a pm from the moderator handling the report. Then you'll get another when the report is considered to be handled.
Click to expand...
Click to collapse
Thanks, forgot to come back in here and update it, the moderators did get in touch with the OP of that thread and I talked to them and he did already pull the links for those files. He has been trying to get in touch (about 4 messages now) to the original developer but cannot so for now he is just going to leave them off as he agreed with me, it should NOT be flashing p8 when in fact its p18.
Thanks to the moderators on moving on this when we reported it.
Dixit
dixit said:
Thanks, forgot to come back in here and update it, the moderators did get in touch with the OP of that thread and I talked to them and he did already pull the links for those files. He has been trying to get in touch (about 4 messages now) to the original developer but cannot so for now he is just going to leave them off as he agreed with me, it should NOT be flashing p8 when in fact its p18.
Thanks to the moderators on moving on this when we reported it.
Dixit
Click to expand...
Click to collapse
What will you do with your bricked S3 ?
jorioux said:
What will you do with your bricked S3 ?
Click to expand...
Click to collapse
Tried a bunch of things, no go. Only QPST tools sees it but we dont have enough information from anyone on how to use this tool on the S3, we dont have all the files (or no one has developed them yet) like they have on some of the other threads like the HTC one where they can entirely bring the phone back in a hard brick (where it just shows up as QHSUSB download mode).
So probably send it into get JTAG'ed.
Dixit
OP EDIT: AS MANY OF YOU HAVE NOTICED, I HAVE MOVED ON TO A NEW DEVICE SINCE I POSTED THIS GUIDE. I CAN NO LONGER PROVIDE SUPPORT FOR SPRINT GS3 AS (1)I DO NOT HAVE THE DEVICE ANY LONGER AND (2)I HAVEN'T KEPT UP WITH DEVELOPMENT AND STOCK ROM RELEASES FOR THE GS3. SORRY FOR THE INCONVIENIENCE. THIS GUIDE CAN STILL BE OF HELP TO PEOPLE AS THE PROCESS HAS BEEN DRASTICALLY IMPROVED (LAST I SAW, YOU DIDN'T NEED A DUAL BOOT). PLEASE MAKE SURE YOU SEARCH THIS THREAD FIRST BEFORE SENDING ME A PM ASKING FOR HELP. THANK YOU!
Okay. So I hard bricked (yes, I know a noob mistake... we all slip up some times ) my S3 by flashing an Illusion ROM for the i9300. My device was totally unresponsive. No boot screen, no dl mode, no recovery... nothing. This is a total unbrick for those of you who have done the same as I did. There is already a thread on this by gTan64 but it seemed a little vague and it took me awhile to figure it out. So here is my version.
DISCLAIMER: I DO NOT GUARANTEE THIS TO WORK. DO NOT COME TO ME IF YOUR PHONE EXPLODES OR SOME HOW GOES INTO A WORSE STATE THAN A HARD BRICK (If that's even possible)
CNexus said:
You should also add that this is for the Sprint S3 only. It was made using the aboot from my emmc dump which may or may not fail on other devices.
Click to expand...
Click to collapse
What you will need:
A 16GB SD (preferably a Class 10)
A hard bricked S3
A USB cord
A Linux/Windows dual boot computer (Or go use a Linux Live CD)
Stock tar for ODIN
This was all done on Ubuntu 12.04 LTS and you will need to be familiar with Terminal and its processes.
You will need this file (thanks to billard412 for pointing this out to me and gTan64 for the DL link ) [gTan64's thread ]
http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz
Okay. Let's Begin.
Assuming that you are already on a Linux machine, here's what you need to do.
1. Make sure you have no external USB/HDDs attached to your machine. Insert your SD card to a reader. You will need to identify the letter of the SD card. You can do that by opening up Terminal and enter the following
>>>Sudo su
(Enter your password here)
>>>dmesg | tail
Click to expand...
Click to collapse
You only need to use the part that says "sd[your card letter]". That is the your SD card's letter. DO NOT USE THE ONE THAT HAS THE NUMBER. For example: sdc1 <<< That is a partition of the SD card, not the actual root of the SD card itself. If you use the wrong letter, YOU COULD WIPE YOUR HARD DRIVE.
Or go use GParted (Just look for it in the Applications drawer in Ubuntu) for an easier method.
2. Unzip the s3 unbrick file on to your desktop. Now go back to the Terminal. You should still have root privileges so there is no need to enter "Sudo Su" again. Enter the following.
WARNING: THIS WILL ERASE THE ENTIRE SD CARD.
>>>dd if=[drag the unzipped unbrick img onto the terminal] of=/dev/sd[your card letter]
Click to expand...
Click to collapse
This should write the img file to the SD.
3. After it's done writing the img, take out your SD card and put it into your phone. With the battery in the phone, insert the SD card, plug the phone into your machine, and try to boot to DL mode via the usual method. This WILL take several tries and possibly rewriting the img file to SD card again to work.
4. If you were lucky enough to boot to DL mode, boot back to Windows and then I suggest you go and download a stock MD4 (as of 18July2013) tar file and ODIN yourself back to stock and go on from there. Btw, if you don't ODIN back to stock, your phone WILL STILL BE BRICKED. This is because the phone is using the SD card to boot to DL mode.
I suggest that you keep that SD card as your "OH SH*T, I HBRICKED" rescue card.
If you were successful, don't forget to hit up that thanks button and buy me a cheap coffee!
LINKS:
STOCK Firmwares: http://samsung-updates.com/device/?id=SPH-L710
STOCK(Rooted or Unrooted Exe/.gz): http://www.sxtpdevelopers.com/showthread.php?t=233
Special Thanks to:
billard412 for linking me to the thread
gTan64 for the unbrick img
CNexus for helping me edit this guide and giving me advice.
And the many others whose usernames I've forgotten that have tried to help me in my quest for a solution for a Hard Bricked S3
If you know who you are, PM me and I'll add you to the Thanks list.
You should put to the link to the original thread, you didn't come up with this.
Aaron Swartz, Rest in Pixels.
This is the Original post on this method, it appears that there have been 2 successful attempts with this method. http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
edfunkycold said:
This is the Original post on this method, it appears that there have been 2 successful attempts with this method. http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Been looking for that link. I saw this method last night. I couldn't make heads or tails out of it because it was so vague. I just revamped it a lil. His method says that you don't need to plug your phone in to the computer. I guess that's the only difference. Thanks!
edfunkycold said:
This is the Original post on this method, it appears that there have been 2 successful attempts with this method. http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Edited OP to include the said thread, various links for the TARs and added a Special Thanks at the bottom.
You should also add that this is for the Sprint S3 only. It was made using the aboot from my emmc dump which may or may not fail on other devices.
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
You should also add that this is for the Sprint S3 only. It was made using the aboot from my emmc dump which may or may not fail on other devices.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
I should probably add that to the title, but I can't seem to find the edit button for it (I haven't started a lot of threads)
deBricker said:
I should probably add that to the title, but I can't seem to find the edit button for it (I haven't started a lot of threads)
Click to expand...
Click to collapse
Edit your post and it will be at the top (mobile). Click edit then advanced and it will take you to another screen where you can edit the title if on a computer.
Sent from my S3 on Sense 5 (you jelly?)
This should help some of the people on Sprint GS3 forums who are constantly bricking their phones. But then again, not everyone here knows how to use Linux or how to search.
CNexus said:
Edit your post and it will be at the top (mobile). Click edit then advanced and it will take you to another screen where you can edit the title if on a computer.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Got it. OP updated. Yet again. This thread has gotta be one of the most updated threads in one day. lol
joeyhdownsouth said:
This should help some of the people on Sprint GS3 forums who are constantly bricking their phones. But then again, not everyone here knows how to use Linux.:good:
Click to expand...
Click to collapse
That's why I included the information on how to get the SD card letter. (It took me a while to find it myself, but Google was my friend )
deBricker said:
That's why I included the information on how to get the SD card letter. (It took me a while to find it myself, but Google was my friend )
Click to expand...
Click to collapse
I suggest that you suggest for the user to install and use GParted to find the device block instead. People in a rush may accidentally flash this image to their hard drives and brick their computers (the irony).
Sent from my S3 on Sense 5 (you jelly?)
Thanks for sharing and more so for your service. +100000
Thanks
Thanks for this. Glad I'm not the only person who forgots to check ROMs properly before flashing.
You gave me hope that all is not lost yet.
Going to try this tonight.
And if this works I am going to push you to market this...
sell and ship a SD card to those silly brick makers.
That would not be reasonable as this is not the OP's method.
Sent from my buttered S3
Would this work for either size SGS3? either way cool guide gives me a little more hope if i ever do brick
do this work on windows
the debricker said:
do this work on windows
Click to expand...
Click to collapse
No
Sent from my SPH-L710 using xda app-developers app
Question
Question OP, when you bricked, did phone respond at all?
Only output I get is when I plug phone in to charger without battery. Red LED
Other then that, no response. No buttons respond at all.
I created SD as stated. Verified image created on SD. Inserted SD into phone, installed battery.
I get no response when trying to power on, enter DL mode.
Any other info would be greatly appreciated.
jaymaj said:
Question OP, when you bricked, did phone respond at all?
Only output I get is when I plug phone in to charger without battery. Red LED
Other then that, no response. No buttons respond at all.
I created SD as stated. Verified image created on SD. Inserted SD into phone, installed battery.
I get no response when trying to power on, enter DL mode.
Any other info would be greatly appreciated.
Click to expand...
Click to collapse
If memory serves me right, the op was in the same boat. Took a few attempts as well. Try to reformat and reflash the SD image.
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
the debricker said:
do this work on windows
Click to expand...
Click to collapse
I believe this can be done with cygwin too
Hey guys,
I messed up.. I flashed a modem for the updated version of S3RX, not my current version (4.2.1) and that resulted in a pretty hardcore brick.The only response its giving is the red light with the charger plugged in and battery removed, as well as the QHUSB_DL message on the computer when connected.
I tried imaging a debrick image onto a SD card, and doing that but it didn't work but I'll outline what I did anyway just encase I'm doing it wrong.
1. Using Patriot LX 32gb MicroSDHC card
2. Imaged a debrick file another user provided from their phone (4.2.1) using win32imager
3. Put the SD card in, no battery, power cord removed
4. Put battery in
5. Did button combination for download mode
6. Phone didn't respond
So is there anything else I can try or do I need to get someone to jtag it for me :/
Yumz said:
Hey guys,
I messed up.. I flashed a modem for the updated version of S3RX, not my current version (4.2.1) and that resulted in a pretty hardcore brick.The only response its giving is the red light with the charger plugged in and battery removed, as well as the QHUSB_DL message on the computer when connected.
I tried imaging a debrick image onto a SD card, and doing that but it didn't work but I'll outline what I did anyway just encase I'm doing it wrong.
1. Using Patriot LX 32gb MicroSDHC card
2. Imaged a debrick file another user provided from their phone (4.2.1) using win32imager
3. Put the SD card in, no battery, power cord removed
4. Put battery in
5. Did button combination for download mode
6. Phone didn't respond
So is there anything else I can try or do I need to get someone to jtag it for me :/
Click to expand...
Click to collapse
Can you try it with a 16GB card? Ive had some people report failure(except one) with cards larger than 16GB and thus far everyone who has tried it with a 16GB have been succesful. (that I am aware of or atleast the ones who didnt flash a bootloader from a different device model)
Also I was told by -Mr. X- who is where I learned of this process that sometimes you may have to flash the IMG file on the sd card several times and try to access download mode several times before you obtain success.
theramsey3 said:
Can you try it with a 16GB card? Ive had some people report failure(except one) with cards larger than 16GB and thus far everyone who has tried it with a 16GB have been succesful. (that I am aware of or atleast the ones who didnt flash a bootloader from a different device model)
Also I was told by -Mr. X- who is where I learned of this process that sometimes you may have to flash the IMG file on the sd card several times and try to access download mode several times before you obtain success.
Click to expand...
Click to collapse
I have a 32gb one, I'd have to buy a 16gb but I'm more than willing to do that
So when you say flash the IMG file on the sd card several times, do you literally mean do it once, twice, ect.. all in a row?? Because I've only been doing that once each time. I have tried the second part of what you were saying though, I did try many accessing download mode at least seven times
Yumz said:
I have a 32gb one, I'd have to buy a 16gb but I'm more than willing to do that
So when you say flash the IMG file on the sd card several times, do you literally mean do it once, twice, ect.. all in a row?? Because I've only been doing that once each time. I have tried the second part of what you were saying though, I did try many accessing download mode at least seven times
Click to expand...
Click to collapse
Yes exactly write the file several times in a row then try again. - Mr. X- has successfully used a 32GB card so try again. There is still some hope
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Yes exactly write the file several times in a row then try again. - Mr. X- has successfully used a 32GB card so try again. There is still some hope
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I see, okay I'll try that!
Thank you for your advice so far by the way
edit: No luck with doing that :/ What's the chances a 16gb would work instead do you think? Also, would partitioning it work?
I
Yumz said:
I see, okay I'll try that!
Thank you for your advice so far by the way
edit: No luck with doing that :/ What's the chances a 16gb would work instead do you think? Also, would partitioning it work?
Click to expand...
Click to collapse
Is it possible you flashed the 4.3 bootloader? Perhaps something in the modem file is preventing the phone from debrick in with the older file? Here is a debrick for the SGH - I747M from 4.3 courtesy of - Mr. X- I mirrored it with permission. https://www.dropbox.com/s/4n2b6l32iv9udow/debrick-SGH-I747M-UEMK5.img perhaps it might do what you need it to? Although I shall not be responsible if you actually need a Jtag after that when it could possibly have been recovered with the debrick files?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 11:47 PM ---------- Previous post was at 11:36 PM ----------
I suppose it is possible that you have a bad debrick file? Bad downloads happen all the time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
help me please
I have a problem ...
CM want to install 10.2 on my samsung galaxy s3 sgh i747m but can not find any rom or tutorial for phone CM.10.2 decided install that of ATT but it is a mistake to frame this
assert failed: GetProp ("ro.product.device") == d2att "\ GetProp (" ro.build.product ") == 'd2att" E: error in / emmc/0/cm-10.2-20131125-NIGHT-d2att
(State 7)
installation aborted
I have CWM Recovery v5.5.0.4
I need help
theramsey3 said:
I
Is it possible you flashed the 4.3 bootloader? Perhaps something in the modem file is preventing the phone from debrick in with the older file? Here is a debrick for the SGH - I747M from 4.3 courtesy of - Mr. X- I mirrored it with permission. *link removed* perhaps it might do what you need it to? Although I shall not be responsible if you actually need a Jtag after that when it could possibly have been recovered with the debrick files?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 11:47 PM ---------- Previous post was at 11:36 PM ----------
I suppose it is possible that you have a bad debrick file? Bad downloads happen all the time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay, so I was in disk management to format the SD card so I could start fresh and the imagine file you linked, but I noticed like 14 partitions on it (That werent there before I should add).. I deleted them and went back to formatting, but left me with 29.26gb unallocated that I couldn't reformat.. I've only got 60mb on it now, and that's not even enough for the image
Any ideas what's going on?
Yumz said:
Okay, so I was in disk management to format the SD card to try the imagine file you linked, and I noticed like 14 partitions on it (That werent there before I should add).. I deleted them and went back to formatting, but left me with 29.26gb unallocated that I couldn't reformat.. I've only got 60mb on it now, and that's not even enough for the image
Any ideas what's going on?
Click to expand...
Click to collapse
GET a copy of mini partition wizard from here http://www.partitionwizard.com/free-partition-manager.html Delete all the partitions on it then try to flash the .IMG file again.
when you get ready to use it in the phone again delete all partitions the phone will recognize it as unformatted and prompt you to format it.
when you write The .IMG file it formats and partitions the card to mirror the phones internal sd card.
Same boat
Hey guys! This seems like quite a coincidence to me, but last night I was flashing a new ROM and now my phone is doing the exact same thing as YUMZ. So, I just wanted to say thanks (YUMZ for getting this thread started and theramsey3 for providing the help). I really hope you get this figured out. I was pretty sure after hours of trying to fix it last night that I'd need a new phone.
YUMZ, have you tried using odin3? In v1.83 (only v1.83) I get a yellow com signal from the phone, but when trying to use it, it always hangs at SetupConnection. I don't know if this helps any.
theramsey3 said:
GET a copy of mini partition wizard from here *link delete* Delete all the partitions on it then try to flash the .IMG file again.
when you get ready to use it in the phone again delete all partitions the phone will recognize it as unformatted and prompt you to format it.
when you write The .IMG file it formats and partitions the card to mirror the phones internal sd card.
Click to expand...
Click to collapse
Okay, thank you. I'll try this tonight
edit: So I followed all your instructions and used the img you provided, but still nothing
skippin07 said:
Hey guys! This seems like quite a coincidence to me, but last night I was flashing a new ROM and now my phone is doing the exact same thing as YUMZ. So, I just wanted to say thanks (YUMZ for getting this thread started and theramsey3 for providing the help). I really hope you get this figured out. I was pretty sure after hours of trying to fix it last night that I'd need a new phone.
YUMZ, have you tried using odin3? In v1.83 (only v1.83) I get a yellow com signal from the phone, but when trying to use it, it always hangs at SetupConnection. I don't know if this helps any.
Click to expand...
Click to collapse
I don't know if it's a good or a bad thing others are in the same boat as me But if this thread helps more people than me, and you than that's awesome.
I haven't tried doing that, I'll also do that tonight and post back if it does the same thing. Maybe if it does that'll have some significance that it can be fixed? Not sure
edit: I plugged it in with v1.83 open and it didn't recognize it. No yellow signal or anything
So I think my phone is hard bricked. I was on G+ ealier today, clicked on a link that opened Chrome. got through a third of the web page and my phone freezes then the screen goes black... I have tried every troubleshoot trick provided by tmobile and samsung and the phone wont respond in any way. Just a black screen. Is it possible to brick your phone with out trying to flash a custom ROM??? The only thing new I have done in the past week was install "graph ti89" and "aviate." I dont know if this has anything to do with it but tmobile has being try to get me to install the kitkat OTA for the last week and I keep ignoring it.
just update
jcampana28 said:
So I think my phone is hard bricked. I was on G+ ealier today, clicked on a link that opened Chrome. got through a third of the web page and my phone freezes then the screen goes black... I have tried every troubleshoot trick provided by tmobile and samsung and the phone wont respond in any way. Just a black screen. Is it possible to brick your phone with out trying to flash a custom ROM??? The only thing new I have done in the past week was install "graph ti89" and "aviate." I dont know if this has anything to do with it but tmobile has being try to get me to install the kitkat OTA for the last week and I keep ignoring it.
Click to expand...
Click to collapse
Hi,
Do the update or factory reset your phone. You can always use KIES also.
Ms. K
Ms. K said:
Hi,
Do the update or factory reset your phone. You can always use KIES also.
Ms. K
Click to expand...
Click to collapse
Thanks for your input but the phone won't turn on at all. Can'T turn it on to update. Won't go into safe mode by pressing vol. up&home&power. When I plug it into the computer it says it needs drivers for "QHSUSB_BULK." Kies doesn't see it as a connected device...
If you haven't done anything to the phone why not call Tmobile and get a replacement..
Sent from my bad ass Kryon infused Note 3
deeznutz1977 said:
If you haven't done anything to the phone why not call Tmobile and get a replacement..
Sent from my bad ass Kryon infused Note 3
Click to expand...
Click to collapse
because i'd like to recover the data that is on the phone.
jcampana28 said:
because i'd like to recover the data that is on the phone.
Click to expand...
Click to collapse
A few threads down you would have found this... http://forum.xda-developers.com/showthread.php?p=47555043
My recovery image is here: http://www.mediafire.com/view/?6nu61z43y51v3k4
You need a 32 GB sd card and some luck. Also reading is a requirement.
Yours may be a special case though, as you claim nothing was going on besides you clicked a link. Should have absolutely nothing to do with ota, and everyone else who had done this was messing with their phone. This definitely works for 4.3, but no one had reported working on 4.4 (you were on 4.3 anyways). Good luck.
Sent from my SM-G900T using Tapatalk
noobtoob said:
A few threads down you would have found this... http://forum.xda-developers.com/showthread.php?p=47555043
My recovery image is here: http://www.mediafire.com/view/?6nu61z43y51v3k4
You need a 32 GB sd card and some luck. Also reading is a requirement.
Yours may be a special case though, as you claim nothing was going on besides you clicked a link. Should have absolutely nothing to do with ota, and everyone else who had done this was messing with their phone. This definitely works for 4.3, but no one had reported working on 4.4 (you were on 4.3 anyways). Good luck.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Mr Noobtoob, has anyone reported un-bricking a N900t running 4.4.2 (1st release, believe it ends in N94 or similar, NOT NE6)?
If so, did they do anything different?
Be well.
golfcartguy said:
Mr Noobtoob, has anyone reported un-bricking a N900t running 4.4.2 (1st release, believe it ends in N94 or similar, NOT NE6)?
If so, did they do anything different?
Be well.
Click to expand...
Click to collapse
I have not seen a successful report back of the nb4 firmware. Doesn't mean it doesn't work, just don't have confirmation.
Fusionized tweaking tapatalker here...
Thanks for the quick response!
Going to try, and will report back.
To clarify, it must be a Class 10 microsd card, and must be the same size (32gb), 1st formatted to exfat, correct?
Sent using XDA Free mobile app
golfcartguy said:
To clarify, it must be a Class 10 microsd card, and must be the same size (32gb), 1st formatted to exfat, correct?
Click to expand...
Click to collapse
Those are the magic ingredients!
Frank
Frank Westlake said:
Those are the magic ingredients!
Frank
Click to expand...
Click to collapse
Got it! So, to be clear;
1st - Format class 10 card to Exfat file system or structure
2nd - Using Win32Diskmapper, just point to the file (in my case kk900tunbrick image) and write to card. *Nothing special, should I verify Md5 sum, or just leave it as default settings?
3rd, Proceed to attempt to Unbrick (Battery at 100%, Put Sd card in slot, Then Add Battery, Connect cable - some say, some say doesn't matter, to computer, then attempt to boot with button sequence to download mode, or may boot by itself?)
Also, if the 1st image I downloaded does not work, can I reformat or wipe the sd card and start again with the other file (I believe a Pit file??)
Hello users, I have my Mi Max Hydrogen 3/32 bricked since time ago, I tried all the threads out there to revive my device, as a hard bricked no fastboot, no download mode responsive, of course no recovery.
I guess that bootloader is messed due to a bad flashing of a file uploaded by error.
I found a method, idea is to force device to enter to download mode restoring bootloader or turn on responsive again to allow a new flashing cycle.
I´m now using a Redmi 5 Plus and I did this method to prevent any trouble in the future, one never knows.
If some user wants to help just I need that this zip should be flash it through recovery and the file just will dump/backup the first 125MB aproximately of system and it will kept in sdcard with the name of debrick.img and kindly can upload it to the cloud. This will be greatly appreciated and I hope that also can help to other users with same/similar issue now. If things go fine I´ll explain in details to accomplish that
View attachment Partial_Sys_Dump_for_debrick.zip
Reserved.
A brief explanation:
I have found this tutorial https://forum.xda-developers.com/showthread.php?t=2369125 (applying concerning to this model) among several of the same type, the idea behind this is that in a cell phone bricked because the bootloader is damaged and trying to boot it does not find that partition readable, so burning/writing the first lines of the operating system in a sdcard, then putting it in the device then it will search these files to try to boot. If the emmc/motherboard is not totally damaged or the measurement of the files is sufficient for it to do it then after this it will come to turn on, stay or spend a little more of the bootlogo and that will indicate that it is in a condition of flashing all the system files again through the fastboot or MiFlash to make it functional back and bring it back to life.
In my case I have damaged the buttons, the back cover opened in the repair shop and this may have a negative influence to try it properly, therefore I could not recover it yet, or the size of the files is not completely sufficient since the tutorial is based on a Galaxy S3 with a memory lower than This device or plainly emmc is definitely damaged.
However, each case is different and I think that this explanation can help others who are in similar cases.
There you go: deleted
Please, explain what you are doing even if it didn't work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
A great thanks, my device has sleeping maaaany time. I will try it and I´ll report even if this doesn´t work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
If you want to give me a second chance, I explained the idea behind this. It´s based on a device the half of ram/rom than this so I think that maybe it´s needed at least 200 mb to find working files to let it run. i´m not sure that if you are running in a custom rom and non miui rom it works anyway.
Your help is greatly appreciated and I recommend any user that can keep the zip dumper and Debrick image in a safe place just in case in the future could need it.
View attachment Partial_Sys_Dump_for_debrick-200MB.zip
hydrogen_3-32_debrick.img
Don't think this is going to work...
nijel8 said:
hydrogen_3-32_debrick.img
Don't think this is going to work...
Click to expand...
Click to collapse
Why do you think so? difference in sizes between 128 and 200 doesn´t matter? or plainly this method can´t work in this device in your opinion? I saw this method in other non Samsung devices like Lenovo totally bricked and cause is a similar device I thought that maybe..... and of course one don´t want resign.
Google sent a confirmation to grant access to your file. Thanks for support.