[Q] Unbrick hard brick gt-i9100 omnirom 4.4.2 - General Omni Discussion

good evening everyone at xda-developers,
I would like to start by explainig my actual issue then give details of the tested solution and their result.
First of all my issue is like following, I have a galaxy s2 model gt-i9100 hard bricked :crying: the reason is still unknown after it was running an OMNIROM ROM 4.4.2, one night the phone got frozzen at the home screen then putted it off to see what was the issue in the morning but surprise the phone won't boot anymore.
I test the USB JIG solution to get into download mode and flash the rom or another one,
Tested also a debrick file .img and Win32DiskImager and a 16g class 10 memory card but no luck, maybe the issue is that this .img file is intended for ice cream version .
What i would like to know and want some help to try is:
want to know if the .img file need to be created for the right version used to run on the device before hard brick
want some help to if the answer of the previous is yes, i would like the help of someone who have the same device model gt-i9100 with the same rom installed to create an image debrick for me to test.
and thank you everyone for your help

maxpain2009 said:
good evening everyone at xda-developers,
I would like to start by explainig my actual issue then give details of the tested solution and their result.
First of all my issue is like following, I have a galaxy s2 model gt-i9100 hard bricked :crying: the reason is still unknown after it was running an OMNIROM ROM 4.4.2, one night the phone got frozzen at the home screen then putted it off to see what was the issue in the morning but surprise the phone won't boot anymore.
I test the USB JIG solution to get into download mode and flash the rom or another one,
Tested also a debrick file .img and Win32DiskImager and a 16g class 10 memory card but no luck, maybe the issue is that this .img file is intended for ice cream version .
What i would like to know and want some help to try is:
want to know if the .img file need to be created for the right version used to run on the device before hard brick
want some help to if the answer of the previous is yes, i would like the help of someone who have the same device model gt-i9100 with the same rom installed to create an image debrick for me to test.
and thank you everyone for your help
Click to expand...
Click to collapse
If the "brick" occurred after a random freeze (as opposed to being bricked immediately after flashing something) - you likely have had a hardware failure.
You probably can't unbrick it because based on what you've said, it isn't bricked, it's DEAD.
I have no idea what you're talking about with debrick images and SD cards. This device has never been able to boot from external SD.

Entropy512 said:
If the "brick" occurred after a random freeze (as opposed to being bricked immediately after flashing something) - you likely have had a hardware failure.
You probably can't unbrick it because based on what you've said, it isn't bricked, it's DEAD.
I have no idea what you're talking about with debrick images and SD cards. This device has never been able to boot from external SD.
Click to expand...
Click to collapse
Thanks you very much for ur reply, but i would love to have the chance to test that as i read in this post it's possible : http://forum.xda-developers.com/showthread.php?t=2439367 for more info: my last running stock rom was android 4.1.2

Related

Warning 10.1" CWM incompatibility - BRICKED!

Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Bec07 said:
Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Click to expand...
Click to collapse
At least its only a soft brick...
Definitely good to know...sorry you went through the hassle to find out.
Thanks for sharing with us, lets hope someone can get a recovery working soon so I can be more dangerous!!!!
Sent from my GT-P7310 using xda premium
http://forum.xda-developers.com/showthread.php?t=1133590
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Bec07 said:
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Click to expand...
Click to collapse
Be careful. Sometimes it clears your SD card as well (depending on what exactly you're doing).
To be safe, make a backup of you SD card on your computer.
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
Click to expand...
Click to collapse
Sweet bro.
Sure wished I'd seen this message last night.....
Well, now to see if I can fix mine.
-dana
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Amateur Geologist said:
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Click to expand...
Click to collapse
A hard brick is when nothing shows up no matter what. Screen stays black no matter what you do, power button doesnt work, you cant get into any recovery or bootloader or anything..
I was a little iffy to install it...so glad I didn't. Had some issues with it on my GS2..pfft
i think i have bricked mine new P 7500
but there is nothing wrong i did with this device
tab is now in only conecting in APX
NVIDIA USB Boot-recovery driver for Mobile devices
no sign of charging and no light on display
is there any way to recover it back??????????
this is semi or hard bricked?????
How? this thread is meant for the 8.9 tabs...
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Click to expand...
Click to collapse
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Dunbad said:
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Click to expand...
Click to collapse
Trapped myself in this lobster pot too. Probably hold the record for purchase to soft brick in 10 hrs!
there is a link in second post from op which has the roms and the flashing software (Odin)eunfortunately they only had a 7310 rom when I looked. You need a 7300 rom for your phone to work. Please read as many forums as you can on this first. I ended up flashing an Asian image just to get back on my feet, then ended up flashing overcome and over clocking which works very well. Wish you luck!
same
same thing happened to me .I should of looked here before trying a backup. Used Odin to install this and its all good, and 3.2. megaupload.com/?d=0KYNVV4Z
FYI, I was stupid yesterday and allowed ROM manager to update my recovery partition (it told me there was an update available). Of course the update was for a Tab 10.1 and soft bricked my tab (it went into a boot loop). I recovered by going into download mode and using odin to flash only Tab 8.9 clockwork recovery image.
So, if anyone else bricks their tab by using an incompatible recovery, you should be able to recover back to where you were by just flashing a compatible recovery instead of using a full odin ROM.

Bricked ace keeps restarting (cannot go into recovery/CWM)

Hello all!
First of all, I would like to thank the entire XDA for all the help and great developers for all their hard work and everything! You're THE BEST REALLY!
I hope you could help me with my problem :/
A few days ago, I flashed a custom rom (i've changed a lot of them already and this has never happened to me before). After flashing the phone the android system worked perfectly fine but after rebooting, phone just keept (and still is) restarting every 3 seconds. I cannot go into CWM recovery, only into Download mode. I've tried flashing stock rom with odin and in the end when it says > Close serial port and wait until rebooting, phone just keeps rebooting again. (Black screen, flash for a second and then again reboot). I've found someone on YT who has recorded the same problem so that you would understand what am I trying to say.
Type SAMSUNG GALAXY ACE (NEED HELP IT WON'T BOOT!) into YT and you will see the problem. ( i cannot paste the link)
What could i do? Btw, i've searched the forums for solutions but i didn't find a single 1 that would help me I cannot do it even with odin
PLEASEE HELP ME
R: Bricked ace keeps restarting (cannot go into recovery/CWM)
Hi! I think your rom (read only memory) got demaged so nobody can help you now
MeltingSnowman said:
Hi! I think your rom (read only memory) got demaged so nobody can help you now
Click to expand...
Click to collapse
Hello! So the only option would be to change the motherboard I guess?:/ Phone is in warranty unitil 17th of February but I don't know if they will repair it because I don't have stock rom on it anymore :/. I've changed many roms and the latest installed is CM10. Do you think that they will see which ROM and other stuff is on if It doesn't even boot? Is there a change that I could format the intrernal storage to cover up my previous installations? (hope you understand what I am trying to say)
R: Bricked ace keeps restarting (cannot go into recovery/CWM)
I understand what you mean, don't worry I think you should try the recovery procedure to unbrick the Ace as last thing you can do to use it back again. If EVRYTHING you can do (or you want to do) doesen't work send your device to service and hope that Samsung repair it for free because covered by warranty. Probably they will never know what you've done on it because memory is demaged. Some time ago I was too lazy to flash an original stock rom and I could not find the one I needed on the web so I sent my device to service with CWM on and no rom (formatted partition) and got it back with stock rom for free (was in warranty time). Best whishes
Inviato dal mio GT-S5830
Ok was afraid that you wouldn't hehe Yea well I tried like 10 times already with Odin but the problem is when Odin is kind of finished and it's time for phone restarting, phone just gets into a bootloop again (or how is it called). So I don't know :/ Maybe I need a new boot file? I can only enter download mode but unable to enter any recoveries modes although I have CWM. Ok I hope so, will probaby take it to the service tomorrow. Btw, do you know any other recovery procedures besides Odin? And thanks a lot for replying to my problem
If you have download mode still try kies to see if it will flash stock again
Sent from my GT-S5830
Ok thank you! Haven't tried that yet. Gonna try it right now.
Or try a different rom downloaded for xda and reflash, sometimes some roms get corrupted
Sent from my GT-S5830
Tried to use KIES but it says that the phone is unsupported :S Could the problem be that I'm using Win8? I've tried other roms already but I think that MeltingSnowman is right, it's damaged and I guess it's only fixable at service.
Nothing to do with win8 really and what method are you using on odin ? One package method or are you using all options
And try using a diff sd card as i had a damaged one that effected my flashing a while back
Sent from my GT-S5830
Oh ok I just thought that the compatibility could be the problem. I'm using one package method because I cannot find other single files :/. I've serched google already but all I ever found ware one packages. Sd card is fine. Do you maybe know where I could find single files? Please don't think that I am lazy but I really haven't found them
Your single files are in your rom you already have downloaded you just untick one package then apply them one by one which rom are you trying to flash ?
Sent from my GT-S5830
I've downloaded some stock 2.3.6 from SamFirmware but it's only 1 file (.tar )S5830DXKT7_S5830OLBKT3_S5830DXKT5_HOME.tar.md5.
It most likely to be a corrupt file, iv heard all sorts of stories from that site, find a stock rom on here thats flashable through odin and try your one package method again and also download the cooper ops file again, if you go to stickies at the top of this forum you will find what you need and hopefully get your ace to boot up again
http://forum.xda-developers.com/showthread.php?t=1034145
Sent from my GT-S5830
R: Bricked ace keeps restarting (cannot go into recovery/CWM)
1) Kies can't flash firmwares because you need an operative phone connected to PC and if you have anything different from stock rom on your mobile will obiviously say "Uncompatible Device", no matter wich SO you're running
2) A corrupted file from internet is almost impossible to get
3) A demaged bootloader would cause bootloops so if someone knows a way to load a new one to your device you'll be alright
4) One package or 100000 files can't cause a demage like that so the problem is sure not that
Inviato dal mio GT-S5830
Why cant there be a corrupt or faulty file ?
Sent from my GT-S5830
Didn't find any of these files. :/ Only ZIP files which are, If I am not mistaken, only supported by CWM.
MeltingSnowman said:
1) Kies can't flash firmwares because you need an operative phone connected to PC and if you have anything different from stock rom on your mobile will obiviously say "Uncompatible Device", no matter wich SO you're running
2) A corrupted file from internet is almost impossible to get
3) A demaged bootloader would cause bootloops so if someone knows a way to load a new one to your device you'll be alright
4) One package or 100000 files can't cause a demage like that so the problem is sure not that
3) I already tought of that but I couldn't find a way to install it, nor the bootloader itself. Hope some1 could provide this.
Click to expand...
Click to collapse
Did you download the coopers ops file again from the link i sent you and try and get stock XWKTR firmware from samfirmware site i flashed it today and im currently using it and put your phone in download mode and try and flash again ill keep looking around to see if i can help you further
Sent from my GT-S5830
---------- Post added 24th January 2013 at 12:03 AM ---------- Previous post was 23rd January 2013 at 11:56 PM ----------
Here is a link for cwm recovery via odin http://forum.xda-developers.com/showthread.php?t=1465599
Sent from my GT-S5830
Still can't access CWM. Bootloops continue. I don't know what to do anymore. I've tried almost everything really. Will probaby sent it to repair tomorrow, I don't see any other option :/

qhsusb_bulk hard bricked my Shamu,how can i unbrick it?

Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
no one?
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
This updates been a nightmare
synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.
This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys
randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.
I'm still stuck. Any progress ?
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked
I had to RMA
randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.
Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA
im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.

[Q] Help Me Fix a Hard Brick! [SOLVED]

I have no clue what the hell happened. The Note 4 locked up earlier today and refused to reboot at first. Eventually it did come back on. I came home and unplugged it then the screen went black. I figure I bumped the power button getting it, well, apparently not.
I've tried pulling the battery and every button combination. It doesn't do ****. I plugged it in to the PC and found that it shows "QHSUSB__BULK". Did some hunting and apparently that means it isn't totally dead. I found some info here talking about recovering from a brick on the Note 3. Problem is I don't have an unbrick image.
So.... uhh basically what do I do now?
I need a unbrick.img from COD6 so if someone could please help with that. According to the Note 3 thread:
Just run this Unbrick Image Creator in recovery & it'll create "/sdcard/Unbrick_Files" in your internal SD card.
Click to expand...
Click to collapse
That is for the Note 3 so I have no idea if it will make a proper image for the Note 4.
EDIT: According to shabbypenguin that ought to give the proper unbrick image. So can someone here running the COD6 bootloader please run that and upload the file for me?
So for future reference, anyone that may need this can try. I take no credit for this. Most of this is a copy/paste from the Note 3 thread.
What do you need?
DO NOT TRY THIS ON ANOTHER NOTE 4 MODEL WITHOUT THE PROPER UNBRICK IMAGE!
- Hard Bricked Device: T-Mobile Samsung Galaxy Note 4 (N910T)
- Micro SD Card: 4/8/16/32 GB micro SD card
- Unbrick Image: working dump with the same bootloader/version
- Image Writer: native commands on Linux/MacOSx or Win32 Disk Imager on Windows
How to recover?
1- Download Unbrick Image for the COD6 bootloader from here or here
2- If you're using Windows, download Win32 Disk Imager
3- Backup all files on the micro SD card you're using
4- Write the Unbrick Image to your micro SD card using Win32 Disk Imager or Linux/MacOSX commands
5- Remove battery, Insert micro SD card & then the battery
6- Hold Power + Home + Volume Down to enter Download Mode by bootloader on SD card
7- Flash Stock firmware via Odin
YOU MAY NEED TO TEST MICRO SD CARDS WITH DIFFERENT TYPES/SIZES & FORMAT AS EXFAT BEFORE WRITING AN UNBRICK IMAGE ACCORDING TO YOUR BOOTLOADER!
I'd charge it for a while. Take out the battery now and then and try to get into download mode.
DarkStarr said:
I have no clue what the hell happened. The Note 4 locked up earlier today and refused to reboot at first. Eventually it did come back on. I came home and unplugged it then the screen went black. I figure I bumped the power button getting it, well, apparently not.
I've tried pulling the battery and every button combination. It doesn't do ****. I plugged it in to the PC and found that it shows "QHSUSB__BULK". Did some hunting and apparently that means it isn't totally dead. I found some info here talking about recovering from a brick on the Note 3. Problem is I don't have an unbrick image.
So.... uhh basically what do I do now?
I need a unbrick.img from COD6 so if someone could please help with that. According to the Note 3 thread:
That is for the Note 3 so I have no idea if it will make a proper image for the Note 4.
EDIT: According to shabbypenguin that ought to give the proper unbrick image. So can someone here running the COD6 bootloader please run that and upload the file for me?
Click to expand...
Click to collapse
To be honest that has yet to work for anyone. Call up and replace the phone.
10-K said:
I'd charge it for a while. Take out the battery now and then and try to get into download mode.
Click to expand...
Click to collapse
The battery was at 100% it isn't that. It is quite obviously a hard brick. It won't do anything besides show a black screen, no response at all.
BACARDILIMON said:
To be honest that has yet to work for anyone. Call up and replace the phone.
Click to expand...
Click to collapse
Obviously it hasn't helped anyone with a Note 4, we don't have an unbrick image. Now if you're trying to say it hasn't helped anyone, including those with other devices, you're full of crap. This method has unbricked numerous devices that actually have an unbrick image.
If you were not going to help by simply running the file and uploading the results then don't bother responding.
DarkStarr said:
The battery was at 100% it isn't that. It is quite obviously a hard brick. It won't do anything besides show a black screen, no response at all.
Obviously it hasn't helped anyone with a Note 4, we don't have an unbrick image. Now if you're trying to say it hasn't helped anyone, including those with other devices, you're full of crap. This method has unbricked numerous devices that actually have an unbrick image.
If you were not going to help by simply running the file and uploading the results then don't bother responding.
Click to expand...
Click to collapse
Are you not in the note 4 thread.. Why would I give a crap about another device. So again does not exist.
I just ran it for you but have no idea if it will work.
Unzip it to use.
Note4_910T_Unbrick_IMG.zip
Link Removed
I'm curious to know if this works just in case i ever hard brick my note 4. Please update us on if it worked or not OP.
DarkStarr said:
I have no clue what the hell happened. The Note 4 locked up earlier today and refused to reboot at first. Eventually it did come back on. I came home and unplugged it then the screen went black. I figure I bumped the power button getting it, well, apparently not.
I've tried pulling the battery and every button combination. It doesn't do ****. I plugged it in to the PC and found that it shows "QHSUSB__BULK". Did some hunting and apparently that means it isn't totally dead. I found some info here talking about recovering from a brick on the Note 3. Problem is I don't have an unbrick image.
So.... uhh basically what do I do now?
I need a unbrick.img from COD6 so if someone could please help with that. According to the Note 3 thread:
That is for the Note 3 so I have no idea if it will make a proper image for the Note 4.
EDIT: According to shabbypenguin that ought to give the proper unbrick image. So can someone here running the COD6 bootloader please run that and upload the file for me?
Click to expand...
Click to collapse
I think everyone has missed asking the most important question.....
What Rom were you running when this happened?
I don't think you have a hard brick.
---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------
Hardware failure maybe.
chipworkz said:
I just ran it for you but have no idea if it will work.
Unzip it to use.
Note4_910T_Unbrick_IMG.zip
https://www.androidfilehost.com/?fid=24052804347758591
Click to expand...
Click to collapse
First, thanks for taking the time to run it and upload it. Unfortunately thanks to your unbrick image along with another guys I have determined that either:
A. The phone hates like all of my SD cards
B. Something else is wrong with the device than even just a hard brick.
XBlackChaosX said:
I'm curious to know if this works just in case i ever hard brick my note 4. Please update us on if it worked or not OP.
Click to expand...
Click to collapse
Unfortunately it didn't boot. I think something further is wrong with the device, ie hardware. I do know when plugged in it was showing the "QHSUSB__BULK" when plugged in. When the SD was installed and I attempted to go to DL mode it disappeared so it was trying to do SOMETHING. Again I think it is hardware.
Jammol said:
I think everyone has missed asking the most important question.....
What Rom were you running when this happened?
Click to expand...
Click to collapse
I was running CM12. Whatever the latest nightly was, IIRC 6/10. It was either that or 6/6. I was also running the Xposed for 5.1 6/9 version that fixed it with CM versions after ~ 6/3.
Android_Monsters said:
I don't think you have a hard brick.
---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------
Hardware failure maybe.
Click to expand...
Click to collapse
I think it was. Even with the unbrick image it wouldn't boot. It did try to do something but I think because of some hardware failure it wouldn't even boot that.
DarkStarr said:
First, thanks for taking the time to run it and upload it. Unfortunately thanks to your unbrick image along with another guys I have determined that either:
A. The phone hates like all of my SD cards
B. Something else is wrong with the device than even just a hard brick.
Unfortunately it didn't boot. I think something further is wrong with the device, ie hardware. I do know when plugged in it was showing the "QHSUSB__BULK" when plugged in. When the SD was installed and I attempted to go to DL mode it disappeared so it was trying to do SOMETHING. Again I think it is hardware.
I was running CM12. Whatever the latest nightly was, IIRC 6/10. It was either that or 6/6. I was also running the Xposed for 5.1 6/9 version that fixed it with CM versions after ~ 6/3.
I think it was. Even with the unbrick image it wouldn't boot. It did try to do something but I think because of some hardware failure it wouldn't even boot that.
Click to expand...
Click to collapse
I definitely suggest just flashing the stock Rom in Odin and then calling in to get a replacement.
Good ole cm12 strikes again.
Pp.
Thats what happens when you venture away from TW to long on a Samsung device! [emoji38] [emoji38] [emoji38]

[XT1068] Hard Bricked again, currently working for fix...(hope)

Hello Guys,
so my Moto G2 had a little MAC Address failure... Every reboot I had a new MAC Address.
So I just DOWNGRADED(AGAIN), but without flashing the bootloader(motoboot, gpt..) and then I upgraded, because I was on CM13. But it doesn't matter if you don't downgrade the bootloader or not(FFS).
I have a full image dump with 8 GB on my GDrive Folder, and I posted it here.
I "burned" the image with "dd" on my linux machine to my external SD, it was successfully burned, but the phone won't start.
If anyone knows which partitions I should extract for creating a blank flash file(I don't know how to do this), PLEASE TELL ME.
The phone is blinking as well, without reaction. It connects and disconnects always as the Qualcomm HQ Loader Interface in my Device Manager, but I don't know what I should do next.
Maybe any key sequences??? Please, let us all know what you tried.
I have the technical understanding in Linux and Windows. You just have to say me anything I can do.
Regards
inFiniTyz_Z
You can do a "DD" from linux to your device without problem again?
No.. dd to my sdcard.
But it doesn't matter. I threw the phone away and then I had a really hard brick how it sounds(full broken screen and the case was damaged). Now I give up and buy a new phone.
The phone will not boot from sdcard if you write the full backup image to the card.
inFiniTyz_Z said:
No.. dd to my sdcard.
But it doesn't matter. I threw the phone away and then I had a really hard brick how it sounds(full broken screen and the case was damaged). Now I give up and buy a new phone.
The phone will not boot from sdcard if you write the full backup image to the card.
Click to expand...
Click to collapse
Ohhh man!
Is more easy stock your phone, or buy a new board, a low cost for you. but if is done, is done
M4rQu1Nh0S said:
Ohhh man!
Is more easy stock your phone, or buy a new board, a low cost for you. but if is done, is done
Click to expand...
Click to collapse
Yes I know, my emotional stress was in the way. But **** off, I don't want to have 3 times the same phone.
So, go for the Moto G4 Plus. It's no problem

Categories

Resources