Related
As the title says, do not partition SD card using ClockworkMod or ROM Manager.
There has been multiple bricked devices already, all after partitioning SD in CWM. The device suddenly turns off while the partitioning is in progress, and never turns on again. We do not know what causes this issue yet, but I am sure that ClockworkMod team will look into it.
Update:
Koush said:
Looking into this. I don't have a DHD but I have an idea why this is happening.
Click to expand...
Click to collapse
Update 2:
Koush said:
I have a fix ready now. I will need to release a new recovery and new ROM Manager to address this.
Click to expand...
Click to collapse
Update 3:
New ClockworkMod 3.0.2.6 and ROM Manager 4.1.0.0 are out! There has been multiple confirmations of the problem being fixed, but also ONE brick. So take the fix with a grain of salt.
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
have another brick here from the same reason, be aware.
MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
Easy, partition the wrong partition, iow the NAND/eMMC.
does anybody know if it affects other devices also?
MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
HOLY SHT!!!!!!!
I partitioned my sdcard thru Clockword recovery 3 months ago back then with 2.5.0.7 htc desire
it hung for 1 hour so i pulled the battery but it was paritioned rite phewwwwww..
Cant imagine if i had a bricked phone now,would prolly pee on my pants....
Darn it. I was thinking about partitioning my SDCard today but postponed it. Thanks for the information.
Are there any other known issues that the CWM might cause to the device? Last year, when I had HTC Dream, I remember reading in forums at Cyanogen that some people didn't recommend using ROM Manager. I don't know what issues it used to cause because I used Amon_Ra back then.
Anyways, thanks for the information. I won't partition the SDCard using CWM.
Ok............
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.
Got another one here: http://www.android-hilfe.de/root-ha...t-nicht-mehr-nach-partitionierung-der-sd.html [German], thank goodness it wasn't mine
Bricked DHD
Hi There,
Had this a few days ago.
the device is indeed completely bricked, no matter what you do.
Luckily for me my HTC DHD was only 10 days old, so i went to the store and after inspection theyt gave me a new one. I must be very lucky i guess.
Thanks for the warning nevertheless.
hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((
All versions of CWM ? Or is it specific to a version ?
All the best,
Sharro
We do not exactly know at this point. At least 3.0.2.5 has the problem.
There is nothing you can do to fix a brick. That is why it is called a brick.
kilavuz said:
hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((
Click to expand...
Click to collapse
I believe you can still return it for manufacturer warranty. HTC phones has at least one year manufacturer. Just say to them you turn on your phone and it couldn't turn on....simplesssss
it is only 2 weeks old. : ((
Other solution
Hi guys,
I've also read somewhere, last november I think, that partitioning could be problematic. So I looked up on the internet and can recommand you what I use to partition my SDHC cards: Paragon partition manager 11 free , I used it on Win XP 32 bits without any problem with my 16gb and with my 3 other 8gb SDHC.
link: here
f.
M_T_M said:
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.
Click to expand...
Click to collapse
Thanks
Thanks for the warning, yesterday I had considered to partition my SD ..
best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.
2-die-4 said:
best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.
Click to expand...
Click to collapse
Yep. I contacted Koush about this issue, so hopefully we get a fix (someone dare to try..? ) or it gets disabled.
I heard this from a customer so take this with a grain of salt but he told me he was an Android Developer and had heard of an interesting "trick" concerning all HTC Android phones.
These phones apparently have a SECONDARY bootloader that is completely hidden and disabled by default and that all those phones are HARDCODED to immediately enter into it the moment they get connected to a specific USB cable.
The guy was looking for the cheapest possible, well, item really, to buy and then proceed to cannibalize as a test to its' validity (he bought an old Motorola handsfree) so it seems he wasn't sure of it either.
Apparently what needs to be done is that the PLUG needs to be completely stripped and either two resistors or two capacitors (I forget which) of specific values need to be soldered to two specific lungs of the plug.
I am sorry I am being this vague but that was all the information I got from him in the matter of the couple of minutes it took him to buy the handsfree.
Perhaps there's sth to be looked into by some people better equipped than I?
EDIT: On second thought, it makes more sense if what he said was to solder A resistor/capacitor to TWO specific lugs of the plug, perhaps?
I kinda remember him saying that the plug itself doesn't even really need to lead to anywhere but it's more like the means to connecting the resistor/capacitor to those two lugs...
He also said that that's how HTC themselves un-brick bricked phones. He didn't appear to be talking just for Dev phones either.
I am sorry I really do not know any details.
Well it seems that my internal SD is damaged or G Moto conclude that after trying many tutorials in order to recover and none work, despite installing stock rom, gpe, recovery, etc (all without error and apparently good) but it seems that so do not write install on the phone because no change, in fact I have tried to not think of brick and even that allows, there will be some way to fix this? even for hardware?
Or if there is any way to format the internal sd using adb, just as is done by a custom recovery
Note: this because it allows me to install a custom recovery
Your eMMC is fine, keep looking for solution or buy a new phone and don't fid with it anymore.
liveroy said:
Your eMMC is fine, keep looking for solution or buy a new phone and don't fid with it anymore.
Click to expand...
Click to collapse
I imagine that as the problem is not your answer so ...
Hopefully you never find yourself in a situation where you've tried almost everything and nothing works
angelgzg said:
I imagine that as the problem is not your answer so ...
Hopefully you never find yourself in a situation where you've tried almost everything and nothing works
Click to expand...
Click to collapse
It may not sound like it, but I'm actually trying to help you.
Anyway, let's hope the things work out in the [email protected]
liveroy said:
It may not sound like it, but I'm actually trying to help you.
Anyway, let's hope the things work out in the [email protected]
Click to expand...
Click to collapse
If you note, thanks
angelgzg said:
Well it seems that my internal SD is damaged or G Moto conclude that after trying many tutorials in order to recover and none work, despite installing stock rom, gpe, recovery, etc (all without error and apparently good) but it seems that so do not write install on the phone because no change, in fact I have tried to not think of brick and even that allows, there will be some way to fix this? even for hardware?
Or if there is any way to format the internal sd using adb, just as is done by a custom recovery
Note: this because it allows me to install a custom recovery
Click to expand...
Click to collapse
I had a similar issue, and I have bad news. If your warranty is still valid flash the original recovery back and try to ask for a replacement. I ended up with buying a broken Verizon branded Moto G as donor and replacing my logic board, of course the cellular network does not work but at least I can use my device for development. My problem was that the eMMC chip got some bad blocks (similar to bad sectors in HDDs) and it prevented the cache partition from mounting and some of other partitions became read only, for instance I could not update the recovery or install a new ROM while I could read the system files, while I was able to push files to the /data partition.
There is a tool called badblocks which can map these blocks and thus fix the eMMC theoretically (it generates a mapping file which can be used later by fdisk) but unfortunately this tool was left out from the Moto G's base system and I don't know if there is any ARM compatible version of it.
I asked around in GSM repair shops if there is any way to replace the eMMC chip with another one of the same model but all of them replied that they don't have the proper machinery to do such fine work and unfortunately there is no official Motorola service in Hungary so they couldn't even get a replacement logic board.
Funny thing that all the write operations were successful in fastboot, but later I found out that on most devices the eMMC controller is so primitive that it barely contains any error handling at all. It will only report trivial errors with a perfectly working eMMC chip, if the eMMc is broken and it cannot produce valid error messages the controller just assumes that everything was OK.
debaj said:
I had a similar issue, and I have bad news. If your warranty is still valid flash the original recovery back and try to ask for a replacement. I ended up with buying a broken Verizon branded Moto G as donor and replacing my logic board, of course the cellular network does not work but at least I can use my device for development. My problem was that the eMMC chip got some bad blocks (similar to bad sectors in HDDs) and it prevented the cache partition from mounting and some of other partitions became read only, for instance I could not update the recovery or install a new ROM while I could read the system files, while I was able to push files to the /data partition.
There is a tool called badblocks which can map these blocks and thus fix the eMMC theoretically (it generates a mapping file which can be used later by fdisk) but unfortunately this tool was left out from the Moto G's base system and I don't know if there is any ARM compatible version of it.
I asked around in GSM repair shops if there is any way to replace the eMMC chip with another one of the same model but all of them replied that they don't have the proper machinery to do such fine work and unfortunately there is no official Motorola service in Hungary so they couldn't even get a replacement logic board.
Funny thing that all the write operations were successful in fastboot, but later I found out that on most devices the eMMC controller is so primitive that it barely contains any error handling at all. It will only report trivial errors with a perfectly working eMMC chip, if the eMMc is broken and it cannot produce valid error messages the controller just assumes that everything was OK.
Click to expand...
Click to collapse
Well it seems to be almost the same, and I give my phone as lost
debaj said:
I had a similar issue, and I have bad news. If your warranty is still valid flash the original recovery back and try to ask for a replacement. I ended up with buying a broken Verizon branded Moto G as donor and replacing my logic board, of course the cellular network does not work but at least I can use my device for development. My problem was that the eMMC chip got some bad blocks (similar to bad sectors in HDDs) and it prevented the cache partition from mounting and some of other partitions became read only, for instance I could not update the recovery or install a new ROM while I could read the system files, while I was able to push files to the /data partition.
There is a tool called badblocks which can map these blocks and thus fix the eMMC theoretically (it generates a mapping file which can be used later by fdisk) but unfortunately this tool was left out from the Moto G's base system and I don't know if there is any ARM compatible version of it.
I asked around in GSM repair shops if there is any way to replace the eMMC chip with another one of the same model but all of them replied that they don't have the proper machinery to do such fine work and unfortunately there is no official Motorola service in Hungary so they couldn't even get a replacement logic board.
Funny thing that all the write operations were successful in fastboot, but later I found out that on most devices the eMMC controller is so primitive that it barely contains any error handling at all. It will only report trivial errors with a perfectly working eMMC chip, if the eMMc is broken and it cannot produce valid error messages the controller just assumes that everything was OK.
Click to expand...
Click to collapse
I'm having the very very same issue with an XT1032 Moto G. "Read-only" eMMC. At least I know I won't have to look for a service center in Budapest since there is none.
Hi Guys,
I have GT-P3100 (Samsung Galaxy Tab2), I recently flashed Mokee ROM 4.4.4 (biggest mistake). The ROM (worked for 5-6 months) keeps restarting in every 10-15 seconds. I have tried to re-flash the ROM, but nothing is happening, I have also tried to flash the other ROMs but for most of the time I am getting this error "E: Error executing updater binary in zip 'location of the ROM file'", and even any ROM successfully installs nothing happens (the old Mokee ROM starts again on reboot, I mean come on).
I have TWRP and I tried to flash a new recovery i.e. CWM through Odin, after a successful flash TWRP starts again like the Mokee ROM.
I have also tried to flash the stock ROM fro Samsung through Odin but it fails in the middle, i have tried it multiple times. I have tried to wipe my entire phone memory, but the data and the installed ROM is still there even after a successful memory wipe
My phone keeps rebooting, I can't flash the same or any other ROM. I can't wipe my data, I can't install any other custom recovery. Nothing is happening.
The installed corrupted Mokee ROM is kind of a sticky ghost i can't get rid of. I would highly appreciate if you guys can help me out here.
If have some logs, please feel free to have a look if required. Since I am a new member I am not allowed to share a link and something is stopping to paste the logs here ( detecting a web link in the logs)
Please feel free to ask me for logs, I am always reachable at [email protected]
Thanks in advance .. I love my device.
This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.
putr4s said:
This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.
Click to expand...
Click to collapse
Thanks for your help. I think now I am in deep trouble in terms of phone. My device is rooted so the service center will not help me out. Perhaps I should figure out a way to do this by my own or find someone who can do this for me.
If I can have some more information, I may be able to fix this. Your information is good I am following the lead. Please share any info your think I should know, I am sure with help I will be able to find a way.
Thanks, keep rocking.
You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.
bindasboy said:
You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.
Click to expand...
Click to collapse
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs
Lightracer said:
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.
[email protected] said:
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.
Click to expand...
Click to collapse
Maybe you could try asking for a solution in the ROM's thread.
Sent from my espresso3g using XDA Labs
[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
The problem was with the eMMC of p3100 and not the ROM.
The only fix is using jtag, replace eMMC or get new motherboard.
I agree with @bindasboy. The symptoms are exactly the same as the emmc brick bug.
Sent from my espresso3g using XDA Labs
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
If you can't get into download mode then you don't have much to lose by trying what the other thread suggested.
@sacnotsack, thanks for the response, and that is my intention, however I am missing 1 crucial part to that thread and that is the debrick.img
Can someone with the PIA (G930TUVU4APIA) rom please post a dump of a partial system img for me? If I'm not mistaken, you can dump it with these commands in ADB.
adb shell
dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128
Just to clarify...
sda20 should be the system partition. Any way that's what it is for me.
You can check yourself by doing typing this in ADB:
ls -al /dev/block/bootdevice/by-name
You will get something like this:
lrwxrwxrwx root root 2016-01-08 10:35 system -> /dev/block/sda20
And to get the block size you would type this:
blockdev --getbsz /dev/block/sda20
So the command
"dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128"
If I get this working, I'll compile a nice tut for S7 users and post all the results with files in case anyone else runs into this issue.
Thank you in advance
I don't mean to be an annoyance, but does anyone have any thoughts or could point me to some direction? I know there are a lot of you that are much more knowledgable in this than I am, and all I'm hoping I can get assistance for is if someone can just make a dump of the debrick.img file so I can try to load it on my SD card.
Thanks
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
MetalPhoenix45 said:
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
Click to expand...
Click to collapse
MetalPhoenix45, thanks for your response. I have a Windows computer as well and I am very familiar with ODIN. The issue is, that in your explanation my guess is you are thinking the phone is in a "soft bricked" mode. The difference between a hard brick phone and a soft brick phone is that in a hard brick phone nothing is recognized when plugged in, it doesn't power on and it also doesn't show any sign of charge when it's plugged into the power.
In a soft brick mode, your phone can be stuck in a boot loop, or at the very least it still shows signs of it getting power. In which case I can just force into download mode and do what you stated above. I don't think that the things you mentioned above would work for me because when I have my phone plugged in to my computer, in device manager it doesn't detect anything. It doesn't even say unknown device or unrecognized hardware. It doesn't see it at all, and I have loaded the Samsung drivers on my pc because ODIN recognized the device prior to my issue.
I do have the stock firmware and everything on my machine, but I just can't get my phone to power or on into download boot even with a JIG.
m0d hipp¥ said:
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
crazynate121 said:
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
Click to expand...
Click to collapse
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
bah double post, sorry I can't delete this
Funny you said nexus just ordered 2 two days ago older 7 but 4g and and what not strictly for experimental and ethical purposes of course was actually shocked at the still high priced note 5 Screen tbh but we live and learn!! SOMETIMES? LOL
m0d hipp¥ said:
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
Click to expand...
Click to collapse
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
PadsPCB said:
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
Click to expand...
Click to collapse
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
m0d hipp¥ said:
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
Click to expand...
Click to collapse
Then i think got stuck, beacause in these forums there is no one willing/able/interested in helping anyone.
I said i'm in the SAME boat == I got an SM-G930T (from T-Mobile) that has a SnapDragon cpu but HERE in my country THERE ARE NO Snapdragons only Equinoxes. If we had such phones here surely i would have done this already, but G930F's won't do, as i have already tried.
So, as you know how i feel about a brand new SM-G930T Bricked, you wold be my last hope. There is no way to send it back to Samsung beacause it was bought from a friend and surely no warranty.
Anyway, best regards and rest in peace
Oh sorry, I misunderstood you. I'd like to think that it's not so much people don't want to try to help out, it's just that there is nothing that can be done for users on the snapdragon device so no one bothers unfortunately. Sorry to hear about this, and it really is unfortunate that you had to go through the same thing I went through with no help. Trust me, if I was able to do anything to provide any guidance I would.
Good luck!
Hi to all of you.I got given an old samsung galaxy s4 mini(GT-I9192)and the person who gave it said it was broken if you can fix it you can keep/sell it.I tried opening it but it didnt respond to any keys even when i tried download/recovery/power on.As i researched online it seems to me that the device has been hardbricked.The guy who gave it to me said he had sent it to a store to repair and said that his cpu was not functioning anymore for both of his s4 minis which doesnt seem to happen just for the 2 phones that 1 person buys and because i live in Albania services arents so great.When i tried to install a custom rom from odin(latest to this date)it wouldnt recognise it but when i plugged the phone in windows made tge sound that something was plugged in and then shortly after it made the disconnecting sound whoch gives me a reason to think that the device may still be alive.I came here since this is the most know site for tech stuff.I havent seen any kind of bricking before but i read tgat the soft bricked devices just need a clean install and to wipe cache and dalvik which gives it the look when it was bought.Ive seen that you can pay for jtag or try a usb jig but i dont want to spend any money since i have a better phone (galaxy j5 2017) and i just wanted to see if i could use it to experiment with roms root and stuff on there.
Any help will be appriciated and if i have any mistakes in my languagee im sorry because as i said im from Albania and not USA/UK
NotABeast said:
Hi to all of you.I got given an old samsung galaxy s4 mini(GT-I9192)and the person who gave it said it was broken if you can fix it you can keep/sell it.I tried opening it but it didnt respond to any keys even when i tried download/recovery/power on.As i researched online it seems to me that the device has been hardbricked.The guy who gave it to me said he had sent it to a store to repair and said that his cpu was not functioning anymore for both of his s4 minis which doesnt seem to happen just for the 2 phones that 1 person buys and because i live in Albania services arents so great.When i tried to install a custom rom from odin(latest to this date)it wouldnt recognise it but when i plugged the phone in windows made tge sound that something was plugged in and then shortly after it made the disconnecting sound whoch gives me a reason to think that the device may still be alive.I came here since this is the most know site for tech stuff.I havent seen any kind of bricking before but i read tgat the soft bricked devices just need a clean install and to wipe cache and dalvik which gives it the look when it was bought.Ive seen that you can pay for jtag or try a usb jig but i dont want to spend any money since i have a better phone (galaxy j5 2017) and i just wanted to see if i could use it to experiment with roms root and stuff on there.
Any help will be appriciated and if i have any mistakes in my languagee im sorry because as i said im from Albania and not USA/UK
Click to expand...
Click to collapse
Download and install the full set of USB drivers for Samsung phones. This might be part of your connection/disconnection issue.
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
On your Windows system, go to Control Panel>Device Manager, then connect your device, when you connect it, watch the Device Manager window, if your device connects, it should have something appear on your list of devices. Try to see what the list shows when the device connects, even if it still just a momentary connection, then come back here and post what it says. This will give me a better idea of what is going on with the device.
If what your friend told you about the CPU's being bad is true, you won't be able to fix the device(s) unless you replace the motherboard(s).
Some Samsung devices with locked bootloaders also have a hardware component called a Q-fuse, if someone attempts to flash a custom recovery or anything else custom on the device, it trips Q-fuse which then "burns" the fuse, rendering the device inoperably hardbricked. This is probably what was attempted on the devices you have. If this is what happened, you won't be able to fix it, not even Samsung themselves can fix this, all they can do is salvage the device to reclaim any possible usable hardware components.
Sent from my LGL84VL using Tapatalk
Thanks for the reply.First things to start,my friend doesnt mess up with loading custom roms as he doesnt have much knowledge on technology.Next,when i connected the device the first time it showed me the name QSHUSB_DLOAD(or smth like that because i am not avaible to use the computer right now).I tried installing some drivers and i will edit the name that i got when i use the computer in a matter of a hour or two.
NotABeast said:
Thanks for the reply.First things to start,my friend doesnt mess up with loading custom roms as he doesnt have much knowledge on technology.Next,when i connected the device the first time it showed me the name QSHUSB_DLOAD(or smth like that because i am not avaible to use the computer right now).I tried installing some drivers and i will edit the name that i got when i use the computer in a matter of a hour or two.
Click to expand...
Click to collapse
Everything you're describing is exactly the results one gets when someone tries to flash something custom via Odin, or when trying to update the device via Odin but the wrong firmware is flashed.
Generally, the only to fix this is to send the device to a professional shop to have a JTAG service performed on the device(s) or replace the motherboard.
From what you describe, I believe the devices are permanently hardbricked, the only solution then is to replace the motherboard. Other than that, you're wasting your time.
Sent from my LGL84VL using Tapatalk
Well feom what i know he doesnt know anything about odin or flashing a new rom since he doesnt even know what a rom is.Then again he hasnt done a factory reset since he doesnt know how.And he has even said that hasnt done anything else than getting it out of the box putting a sim card and just using it.If there is anything we can try to bring it to life by trying to flash a new custom rom or the original rom from an sd card or a usb flash drive(since i have the converter from charging port to usb).Anyways i was just trying to see if i could bring it to life and idk maybe give it to someone else or sell it.
Thanks for your help for the tips you have given me amd for the help that you may give in advance
NotABeast said:
Well feom what i know he doesnt know anything about odin or flashing a new rom since he doesnt even know what a rom is.Then again he hasnt done a factory reset since he doesnt know how.And he has even said that hasnt done anything else than getting it out of the box putting a sim card and just using it.If there is anything we can try to bring it to life by trying to flash a new custom rom or the original rom from an sd card or a usb flash drive(since i have the converter from charging port to usb).Anyways i was just trying to see if i could bring it to life and idk maybe give it to someone else or sell it.
Thanks for your help for the tips you have given me amd for the help that you may give in advance
Click to expand...
Click to collapse
If you can find a "debrick.img" or "unbrick.img",(sometimes, these files are debrick.bin or unbrick.bin), there is a method that involves burning the .img or .bin file on an sdcard to create a type of "bootable disk" to restore the device. The only way to get a copy of this file is from a rooted device with the same model number as yours, try to find one that someone has already creates and made available or try finding someone in this forum that has a device like yours with the same model number and then have them pull a copy of debrick.img from their device and upload it for you to download and use for your device.
Here is a thread for doing this on a galaxy S3, if you can find the specific debrick file for your exact model number, you can try this method. Use the method and the tools as described in the thread, you just need to make sure that any device specific files used in the method are those files for your specific model number.
https://forum.xda-developers.com/showthread.php?t=2581166
Sent from my LGL84VL using Tapatalk
Ok so first,if i do it on a usb will it work and will it be able to be used again as normal and the same for the sd card,will it be able to be used again?
Edit:I forgot but is there a limit to the usb or sdcard size that i will use?And is it possible if i get another samsung phone os or the debrick.img?
NotABeast said:
Ok so first,if i do it on a usb will it work and will it be able to be used again as normal and the same for the sd card,will it be able to be used again?
Edit:I forgot but is there a limit to the usb or sdcard size that i will use?And is it possible if i get another samsung phone os or the debrick.img?
Click to expand...
Click to collapse
Use an sdcard, the thread that I linked has instructions for returning the sdcard to normal usage after you're done getting the device restored. No, you can not use a debrick.img or any other file from a device with a different model number, it has to be for YOUR SPECIFIC MODEL NUMBER I have told you that in every one of my replies here, that is a MUST, it is not "optional".
Stop looking for shortcuts, I know it isn't easy to find what you need but there are no substitutes, do it the right way or don't do it at all.
Sent from my LGL84VL using Tapatalk