Related
This should work on all Qualcomm Snapdragon based Samsung galaxy SIII's, if it doesn't, PM me the model and I'll try and find a solution.
WHILE THIS IS VERY LIKELY TO WORK FOR ANY BOOTLOADER/MODEM/FIRMWARE BRICKED PHONE, THERE IS NO UNCONDITIONAL GUARANTEE THAT THIS WILL WORK FOR YOUR PARTICULAR SITUATION, THERE IS A POSSIBILITY THAT THERE ARE SOME BRICK STATES THAT THIS WILL NOT WORK FOR, but in my experience, almost all cases can be resolved by rewriting the sdcard with correct partitioning.
Disclaimer out of the way, let us begin.
Needed Materials and Files:
EDIT: if you have another phone or know someone else with the same phone have them run this and the output will be a debrick image you can use: busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=200 if it does not work then change the last number (count=) to something larger and try it. If you create an image please upload it so I can put it into a repository I'm creating
16GB or 32GB class10 microSD card
A hard bricked Samsung galaxy S3 US Cellular
The debrick image for your device:
[[Here is the drive image for a folder containing all the debrick images that I currently have uploaded, more will be coming: https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing ]]
If you have any images that I missed, please send me a link or, better yet, upload them to drive, make them publicly shared, and share them with me at [email protected], I will put them in this folder for all to use
US Cellular R530: ftp://sdbruington.us/d2usc/SCH-R530_ALIVE_MJA_200MB_16GB.bin
Sprint L710: http://www.mediafire.com/download/23...ph_l710.img.xz
AT&T I747: http://d-h.st/iEy
T-mobile T999: http://www.mediafire.com/download/gr...k_SGH-T999.img
---I did not upload these images, I have simply collected the links over time, please thank Cnexus for his help in finding these and
---helping me to originally unbrick my S3
Your computer
A card reader that will accept the card (another phone will not work as this is an image, and it needs to repartition the SD card)
Either a partition editor (I've heard that you can use dd or something on linux, but I haven't tried) or this: View attachment win32diskimager-v0.9-binary.zip
A wall charger (computer charging isn't as reliable)
Procedure:
1. Take the sdcard and insert it into your computer
2. Download the mentioned image and the software to put it onto the sdcard
3. Use your computer to pull the data already on the card onto your computer hard drive, as the sdcard will be wiped when the image is put onto it
4. use the software that you downloaded earlier to burn the image to the sdcard
5. Remove the battery from the SGS3
6. insert the sdcard into the S3
7. Put the battery into the S3
8. The S3 may boot automatically, or you may have to manually boot it by holding down the power button for 5< seconds
9. If the update that bricked your phone also messed up /system, then you'll have to coerce Odin mode to shove a stock firmware image to your phone, though I've had more than just SOME trouble with that in the past (in other words I haven't been able to get back to stock yet...), if you simply had a radio update or something go wrong, then proceed to the next step.
10. Do a victory dance with your phone in your pocket not the repair bench, or on second thought, make sure you don't drop it, don't create another problem.
11. After that, you can just use your device normally with the sdcard in it without worry of bricking it, though it will not be able to boot if you remove the sdcard;
the only known method of getting it to boot without the sdcard is reflashing stock firmware, which completely wipes the phone and resets everything back to complete stock. Also, Odin mode has, at least for me, objected when I've tried to flash the stock image back onto it, and even if Odin mode was sure of working, backing up ~16GB of data isn't a fast process, especially with the most reliable means being ADB. If you try to flash a stock image and it fails, your device will almost definitely come up with a version of dmode when you try to turn it on with the sdcard (still bricked otherwise) that says something about Kies update failure, the only way of correcting this that I've had success with is flashing an image that won't do much, such as the same recovery that you already had, over odin mode from that special dmode, as while that won't correct the actual brick, it will at least make you able to boot from the sdcard again. I will provide links to the stock images in a little while, once someone gets that far, as I will have to find all but the one from the US Cellular version.
I am currently looking for firmware images that will only flash the bootloader/modem, if anyone knows of an odin file that could do that, please let me know as soon as possible, in the meantime, I will try and create an update.zip that will flash the necessary files; as most bricks are likely cause by an update.zip that was meant for a different device, I am very confident that it can be fixed with another .zip file.---Stay tuned!
---Don't forget, that thanks button won't bite your finger off if you push it:fingers-crossed:
If any of the links are not fully functional, PM me to let me know, and if you have the link to another debrick image for another device, send me the link so I can include it here!
Please note: While there is a similar procedure for Xynos based S3's, they apparently require a physical modification that requires an amount of soldering, so it is most likely best for them to simply take them in for Jtagging and then just not brick them after that.
EDIT: here is the link to a full youtube tutorial that I made, just for those of you who like watching a video instead of getting lost in a written guide https://www.youtube.com/watch?v=-RTAbLBVfMI
EDIT AGAIN: I'm sorry about both of the mediafire links being down, I will try and find some more and upload them to my google drive, along with the others just to make sure they exist somewhere safe.I'm downloading the images now and uploading some that I already have, they will be available in this folder (https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing) on google drive and will be available by email upon request
here is a sprint image that should work, sorry I haven't tested it http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz
for the t999 4.1: https://www.copy.com/s/xSAswQZbhQX8/t999_debrick.zip for the t999 4.3: https://www.copy.com/s/7ICfKXMC3ccr/T999_4.3_debrick.zip
I know this is becoming a mess of links but here is a link to an xda post that has t999 variant images http://forum.xda-developers.com/showthread.php?t=2439367
here is a sprint 4.4 debrick image: http://www.androidfilehost.com/?fid=23329332407591176
If you want to get your phone to operate without an sd card in there for every boot, stay tuned, I'll have a guide to return to stock soon, though a quick google search shouldn't be that hard if you're desperate
I will clean up this guide in a little bit but currently I have school and such to attend to so it may not be immediate
I know this is getting unwieldy but (big thanks to youdoofus) I have a way to completely debrick and fix it so it doesn't require even the sd to boot.
"Restoring stock bootloader
1) You were able to boot into the ROM
2) Plug your phone into a computer and use MTP mode
3) Move the debrick file onto your internal sdcard (/sdcard/debrick.bin)
4) Disconnect your phone
5) Open up a Terminal Emulator on your phone and input this code
Code:
su
dd if=/sdcard/debrick.bin of=/dev/block/mmcblk0
6) Reboot"
Of course this should be modified for the different versions and types of debrick image as some are img, some are bin, I think there might even be an ISO hanging around somewhere
EDIT: As of October 10th I'm working on a tool that will get an image directly from a stock rom/tar and put it on the SDcard. This is pretty complex so it will probably take a little while, but it should make it easier to get images if all that's required is a stock tar.
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.
Thanks for sharing this
derget1212 said:
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.
Click to expand...
Click to collapse
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.
polobunny said:
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.
Click to expand...
Click to collapse
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.
polobunny said:
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.
Click to expand...
Click to collapse
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.
derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
It really sounds a lot like the BRICKBUG to me, anyone know how to tell if a chip is insane without it working? And did you have the 4.3 bootloader? If you got that you should have been safe, but if you didn't then the kernel may have burned out the chips from the "bug" (it really doesn't seem too much like a "bug", more like an issue worthy of recall)
Sorry I don't know exactly what's wrong off the top of my head
derget1212 said:
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.
Click to expand...
Click to collapse
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.
polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
Exactly
This image gets you in the clear if the ONLY thing screwed up is the boot partition, meaning modem/firmware/bootloader, it does NOT get you fixed if you got your rom F***ed up, and do not expect it to, this will get you into dmode so you can use odin or something like fastboot to flash a /system image or a FULL stock rom if you want to get your bootloader fixed without the SD card being in all the time.
dreamwave said:
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.
Click to expand...
Click to collapse
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.
derget1212 said:
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.
Click to expand...
Click to collapse
Is there any way at all to get into dmode? What is windows recognizing it as?
Thanks for sharing.
EvangelineX said:
Thanks for sharing.
Click to expand...
Click to collapse
no problem, I hope it helped!
derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
If you bricked the /system partition AND the boot partition you will need a stock rom as well, just use Odin or something if possible after using a 4.3 image, a 4.4 image is more or less the same as a 4.3 as far as I know, I mean I bricked mine after using cm11 by flashing the wrong rom, it's just that the rom you tried tried to flash a 4.1 bootloader, and thus tripped the eFUSE or something in the Knox bootloader, what you need is a 4.3 unbrick image, as 4.4 didn't really change the modems/bootloader from 4.3, and the unbrick image isn't really that much more than a collection of pieces from the boot partition that are used as an autoboot by the phone when the eMMC fails to load properly.
This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.
halfdead1993 said:
This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.
Click to expand...
Click to collapse
I believe it will work on basically anything, as in I haven't seen a case that can't be cured at least somewhat by this, I think it works like an alternative boot, as if the bootloader on the eMMC is corrupted, it seems to remove the boot flag, thus making it so that the phone does not detect a bootable partition, the unbrick image has a partition layout mirroring the one that is supposed to be on the phone, so it is used as the boot partition but then redirects control back to whatever is on the eMMC after the bootloader, think of it as a liveCD on windows, just one that hands control back to the system after it has gotten past booting the BIOS.
Hi,
I bought a bricked Galaxy Note 10.1 GT-N8000 and managed to flash stock firmware and booted correctly except for a strange Watermark on screen which showed device specs. Then I tried flashing German Kitkat version thru ODIN which failed, now the device is stuck on Galaxy Note 10.1 screen even though I have tried flashing ODIN many times and it has shown PASS but doesn't go beyond that. It can't even go get into recovery (only can get to ODIN mode). Please help me as i can't go beyond that even though i have searched a lot google, no one seems to have gotten any solution.
34 views but no suggestion!!! It seems mighty developers never bought this phone to suggest something. It's strange ODIN can flash and shows success (firmware or any recovery) but nothing seems to install and make it boot. Pl someone got some idea?
usman3206 said:
34 views but no suggestion!!! It seems mighty developers never bought this phone to suggest something. It's strange ODIN can flash and shows success (firmware or any recovery) but nothing seems to install and make it boot. Pl someone got some idea?
Click to expand...
Click to collapse
Have you tried flashing a custom rom?.
Just realised you said it wouldn't go into recovery.
Try flashing from another pc
Which version of ODIN are you using?.
No haven't tried custom ROM but probably this device was never rooted but can give that a try. Yes it won't go into recovery at all. I will give try from another PC. I have tried ODIN v. 1.85 and v3.09.
usman3206 said:
No haven't tried custom ROM but probably this device was never rooted but can give that a try. Yes it won't go into recovery at all. I will give try from another PC. I have tried ODIN v. 1.85 and v3.09.
Click to expand...
Click to collapse
I think it might be a driver issue with your pc if it won't work with v1.85.
Trying reinstalling the Samsung drivers on your pc.
I flashed stock firmware before with the same PC and it worked and I have tried to use same ODIN and same stock firmware which worked before. Even now ODIN says PASS, infact there is no failure at all but device itself is stuck on "Samsung Galaxy Note 10.1" splash screen. I have tried restarting PC, using different USB ports but ODIN always says PASS without problem but device condition is same. I think may be i should change firmware/ stock recovery even though previously the same worked. I am at a loss, don't know what to do?
P.S: Edit: as i was writing these comments I thought of trying out same german kitkat version which earlier broke my device and this time it succeeded and at least device has come out of that splash screen though it is still stuck samsung animation screen. so i will try more and will update. any suggestions are welcome. thanks
ok, now it's possible to get into stock recovery at least, although it shows "E:failed to mount /efs (Invalid argument)" and " Applied the CSC-code : unknown". What to do now? kindly advise
Finally managed to ODIN a stock firmware to work correctly and device is able to boot but show "Broadband: Unknown". Thanks for your help
usman3206 said:
Finally managed to ODIN a stock firmware to work correctly and device is able to boot but show "Broadband: Unknown". Thanks for your help
Click to expand...
Click to collapse
Can you check your IMEI if its available in setting/device? If its not your EFS is missing or corrupt.
yes, IMEI is Unknown! that means EFS is corrupt! I know the IMEI, I have the box, how can i restore it?
usman3206 said:
yes, IMEI is Unknown! that means EFS is corrupt! I know the IMEI, I have the box, how can i restore it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2111485
Thanks a lot for the link. I will go through it deeply and try it out and will come back.
Just some food for thought! Since i bought this device bricked and never knew which firmware it came with and tried different firmwares randomly until i found one that could work only with "Factory Mode". My question;
1. Could it be that I flashed a wrong firmware causing this thing to go Factory Mode?
2. Or must it be corrupt EFS folder?
I am asking because now i rooted my device, it is showing one EFS folder and when i tried to flash Philz recovery over TWRP it gave me error that " This package is for 'c).p4noterf.n8000.GT-N8000' devices; this is a 'p4notewifi'.
E:Unable to mount '/efs'.
Any suggestions? Please
I think this efs folder is generated automatically by the android when it can't find one because when i checked it was an empty folder, nothing inside. so may the issue is of broken efs system folder. Can't create my own IMEI since i have the box and IMEI is written on it.
Does this device use SIM to make calls or just for data download? Couldn't figure out! Is there a simple way to get rid of the "Factory Mode"? may be i don't need all that SIM functionality after all but certainly want to get rid of that "Factory Mode".
Can I try this one
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Any suggestions, kindly do suggest if i should do whatever is described in the above post or the ones suggested before written below
http://forum.xda-developers.com/showthread.php?t=2111485
Please advise which method should i try. Awaiting eagerly for input
Is it possible to use following tool to repair EFS?
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
Please suggest me something if someone out there know something?
Finally fixed it by using the thread shown above but i have a fake IMEI but factory mode is no longer there and everything is working normally. Is it possible to change IMEI to my own by using methods i have seen on net including youtube? please advise
usman3206 said:
I flashed stock firmware before with the same PC and it worked and I have tried to use same ODIN and same stock firmware which worked before. Even now ODIN says PASS, infact there is no failure at all but device itself is stuck on "Samsung Galaxy Note 10.1" splash screen. I have tried restarting PC, using different USB ports but ODIN always says PASS without problem but device condition is same. I think may be i should change firmware/ stock recovery even though previously the same worked. I am at a loss, don't know what to do?
P.S: Edit: as i was writing these comments I thought of trying out same german kitkat version which earlier broke my device and this time it succeeded and at least device has come out of that splash screen though it is still stuck samsung animation screen. so i will try more and will update. any suggestions are welcome. thanks
Click to expand...
Click to collapse
Hi there.
The Note is a tablet 10.1 wifi version?
Is that I have exactly the same problem as you and I do not know what to do to get my tablet.
Could you give me the link of the rom with which you solved the problem? Thank you
spider1371 said:
Hi there.
The Note is a tablet 10.1 wifi version?
Is that I have exactly the same problem as you and I do not know what to do to get my tablet.
Could you give me the link of the rom with which you solved the problem? Thank you
Click to expand...
Click to collapse
Mine is wifi+3G version, its called GT-N8000. Mine was bricked before and I flashed it using ODIN (its available everywhere almost) and stock firmware (you need to use the one installed on it from factory, you can find download link from sammobile site but be careful download the one that is specific for you model no.). Then describe your problem may be i can help you.
first I'd read several topics about what should be done in these cases, but until now I still have the same problem.
The info:
I received yesterday a N8013ZW in a bootloop, read several sites and tried to reflash the tablet.
With Odin 3 v1.85 [just auto reboot option selected] installed the file KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.tar.md5 but from a bootloop passed to a bricked state in the Samsung logo.
Went to the Internet and read that I need to clean up the Cache, so I should install a recovery that allow me to do this.
With Odin again, with auto reboot and f.reset time, installed philz_touch_6.00.8-n8013.tar.md5 but after trying to boot to recovery didn't work.
So can please somebody help me to figure it out what I'm doing wrong here.
Maybe my files are incorrect or I should select another option.
Please someone point me in the right direction.
Regards
Tried last night with TWRP 2.8.7.0 touch and the same, the installation when just alright but not new recovery installed. Power button + volume up.
In 99.9% of cases it's not possible to boot into recovery mode is a hardware problem. Probably faulty controller or died flash memory. You need to contact the service center to replace the motherboard.
Tried this guide as per AndriiG suggestion, but did not worked.
Let's see if I can find something else.
Nehemoth said:
Let's see if I can find something else.
Click to expand...
Click to collapse
Well, if you want yourself to continue attempts to recover a tablet, try a SERVICE firmware. First, it has the pit file, and secondly, in the CSC-file laid a full wipe of the device. Download directly from Samsung servers can program SamFirm (note highlighted):
ViAlexSt said:
Well, if you want yourself to continue attempts to recover a tablet, try a SERVICE firmware. First, it has the pit file, and secondly, in the CSC-file laid a full wipe of the device. Download directly from Samsung servers can program SamFirm (note highlighted):
Click to expand...
Click to collapse
Indeed I will try, thank you.
I just followed the instructions provided by codified in this thread and proceed to download the file GT-N8013_XAR_1_20130927111406_k23qt8fzd7.zip.enc2, the I'd proceed to select Check CRC32 and Decrypt automatically and got the file GT-N8013_XAR_1_20130927111406_k23qt8fzd7.zip and the uncompressed this file to have KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5 which looks like the first file that I tried with some subtle differences KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_u ser_low_ship.tar.md5
I will try this tonight as soon as I arrive home.
Thank you @ViAlexSt
N8013UEALI3_N8013XARALI3 -> Android 4.0.4
N8013UEUCMI3_N8013XARCMI3 -> Android 4.1.2
I guess now to find the service firmware 4.0.4 is hardly possible. And to revive the tablet it doesn't matter
But I still think hardware problem......
Update
The day before last night I tried the Prerooted UEALH2 Firmware Package by Entropy512 with the same result as before, stuck at Samsung Logo.
Today I'd just tried the method recently provided by @ViAlexSt and sadly the result was the same.
So, I supposed that this is a hardware issue as specified before.
Thank you
Nehemoth said:
this is a hardware issue as specified before
Click to expand...
Click to collapse
Unfortunately, you're not the first with this problem. On the Russian forum 4PDA enough of your "brothers in misfortune". The key point of the problem is inability to boot into recovery mode. And one solution - replace the motherboard.....
I don't really know why my phone is stuck in a bootloop to begin with. I've tried EVERYTHING I could possibly think of!
Here's What I've tried :
WipeData/Factory Reset and I also wiped Cache.
I tried to use ODIN to flash the original stock ROM to the device but the bootloader is locked so its impossible to flash any ROM to the devices (Even if it's official).
I tried to apply the Lollipop 5.0 update in recovery using a external SD card.
I tried using ADB sideload.
(Bonus points if you can give me away to unlock the bootloader! because i'll know what to do if it's unlocked.)
So...If anyone has suggestions, I'll happily take any!
Also Please! Leave links so I have quick access!
Hi,
I can't find a relevant thread on your device and issue, but you can ask for help here,
http://forum.xda-developers.com/android/help
Good luck!
Hello,
I did something rather stupid. I downloaded stock firmware from samsung-firmware.org for this build TMB-G930TUVU2APC8_G930TTMB2APC8-20160325.
Using heimdall, I tried to flash all the partitions to my T-Mobile S7. The boot, cache, aboot, recovery, system, and a few other partitions failed during flash due to not passing the checksum. I thought it would be a good idea to remove each partition that failed and just try to flash the partitions that would flash. I believe the partitions that did not flash failed because this firmware build was not the proper baseband version for my phone. I kind of just guessed which firmware build to pick. I guessed because my phone was already softbricked from improper flashing before. I could not obtain the baseband version. That would explain why the locked partitions did not pass checksums.
My half-assed plan to flash only the partitions that would go through worked... kinda. I managed to get a bunch of partitions to flash including modem, keymaster, cmnlib, cmblib64, persist and some others. Immediately after flashing, the device just went black. It is now not responding to any inputs or turning on. I cannot boot to recovery or download. It's completely bricked.
I heard it should be near-impossible to brick due to having a locked bootloader, but this is pretty bricked to me. I have let it sit, not plugged in for half an hour now in hopes that I can get it to turn on after a few hours of discharging or something.
Any way to fix this? Can I take it in to a local repair store to get it unbricked? Any help would be greatly appreciated.
Thanks.
Use Odin3 v3.13.1 It is a windows based program to flash Samsung phones.
ff-racer said:
Use Odin3 v3.13.1 It is a windows based program to flash Samsung phones.
Click to expand...
Click to collapse
Thank you for your reply. It doesn't matter now what tool I use.
At this point, my phone is bricked. No software can pick up the phone now.
I noticed you are trying to flash a Marshmallow OS? Why not try one of the newer roms listed in this forum. I am using Oreo.
Link: https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-g930tuvu4cri2-t3864700
ff-racer said:
I noticed you are trying to flash a Marshmallow OS? Why not try one of the newer roms listed in this forum. I am using Oreo.
Link: https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-g930tuvu4cri2-t3864700
Click to expand...
Click to collapse
Hi again. The stock S7 T-Mobile variant has a locked bootloader so I wouldn't even be able to flash anything except stock...
That's still not the point. My phone is bricked so I would not be able to flash anything at the moment. The point of this thread is to search for an answer about maybe why my phone is bricked and if there's any way to fix it without a JTAG.