S3 LTE i9305 Dead Brick Syndrome aka EMMC Failiure - Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help &

My S3 4G didn't wake up a couple of years ago. I've been trying since to find a way to revive it and had a glimmer of hope when I saw the youtube presentation of Oranav reviving a standard S3.
Recently, I came across the instructions to revive using a PC running Windows, i9300-EMMC Guide at https://toomoch.github.io/i9300-EMMC-GUIDE/. I have a type 1 brick i.e. totally dead so I followed the type 1 procedure in the hope that it might just work on my phone.
I followed the steps of preparing the environment using the i9300 EMMC toolbox, prepared the SD card, inserted the SD into the phone and tried to turn on as per instructions getting a white screen but no 'funky stuff'. Connected USB cable but was unable to low level format as python kept giving access errors.
I assume the reason I couldn't proceed was because the sbootsdcard.bin, exploit and fw.bin from the i9300 EMMC toolbox aren't compatible with the i9305. That being the case is there anyway of modifying these files or getting the correct ones for the i9305 and following the same procedure?

Related

Any HELP at all?

Sent from my HTC Wildfire using XDA App-put out a post about half hour ago but I never stated my problems...got sim free,unlocked sgs I bricked it I could only d/load via jig,so I flashed it using odin but I must've done it wrong as I got no network connection, incoming + outgoing wasn't viable,I tried flashing it again (infinity),then it bricked again,as of now my galaxy is "dead",if any 1 can help me it would b appreciated,I do not have much knowledge apart from basics so please don't be smart as I am only asking for help here,oh I have to use a jig as I can't get 3 button mode,also I formatted my internal + external memory (8gb + 16gb)....that was the last advice I got + think this Is where my problem started from?thank you....
pmb6177 said:
Sent from my HTC Wildfire using XDA App-put out a post about half hour ago but I never stated my problems...got sim free,unlocked sgs I bricked it I could only d/load via jig,so I flashed it using odin but I must've done it wrong as I got no network connection, incoming + outgoing wasn't viable,I tried flashing it again (infinity),then it bricked again,as of now my galaxy is "dead",if any 1 can help me it would b appreciated,I do not have much knowledge apart from basics so please don't be smart as I am only asking for help here,oh I have to use a jig as I can't get 3 button mode,also I formatted my internal + external memory (8gb + 16gb)....that was the last advice I got + think this Is where my problem started from?thank you....
Click to expand...
Click to collapse
OK so if you can get into download? If you can then its a matter of getting Odin to see the phone - which really means getting windows to recognize the phone. This would mean that odin does not light up in one of the com ports.
If this assumption is right, make you have the latest drivers (see other posts - I had a link in another post so if you look for my posts you'll find it), reinstall kies (but do not have it open), clean the usb port/cable on the phone and computer with alcohol just to be sure (that was my old issue and it takes forever to troubleshoot), then put into download with jig (I assume you start with a battery pull?). If you've done the kies/drivers thing (good chance if your asking on this forum - just try the cleaning).
You can also try various different usb ports - the theory is the one at the back of a desktop work best but my laptop ones seem fine (now - see cleaning above).
I know this is not that step by step it sounds like your trouble is the connection not the steps as you have already attepted the flash.
If still not working , try to vary the connect order (odin first, then connect or reverse etc).
From there follow a good odin guide and flash a full stock firmware to start (presumably your official one).
I believe you are only truly dead when you cannot get to download mode.
Good luck!
Thank you for taking the time to send that post ; one last thing ... any thoughts on getting my sgs to "day 1" , like before all the trouble I was stock eclair 2.1,Vodafone,blah,blah ; how do I get back after formatting both my internal + external , I'm presuming I've erased my stock FW?
Sent from my HTC Wildfire using XDA App
I think you also got similar advice to mine on another post. Don't worry about going to day 1 with eclair. If you flash a stock froyo firmware with odin you'll have a phone like it came out yesterday. Now, it will also likely be unrooted and maybe locked (I'm not unlocked so I'm not sure about that part).
So once you get to the stock firmware you'll need to root again and maybe unlock (stock is stock after all). You may want to just try Darky's resurection rom (for Odin use)
, link here, which should make your phone faster and keep you rooted and unlocked.
If you don't care about root etc, then I think stock is fine as long as it doesn't lock the phone to another provider (use the search function in the forums). One warning is once you know how to change things (and recover) you might spend hours trying to play with the custom roms just because you can .
Good luck in the AM

[Q] Unbrick hard brick gt-i9100 omnirom 4.4.2

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

[Q&A] [GUIDE]How To Unbrick Your Galaxy Tab!

Q&A for [GUIDE]How To Unbrick Your Galaxy Tab!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE]How To Unbrick Your Galaxy Tab!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Galaxy Tab 3 T210R / Bricked?
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Bricked, or not bricked? Samsung Galaxy T210R
gtcreative said:
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
___________________________________________
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Click to expand...
Click to collapse
____________________________________________
Update 07/07/2015
I let the tablet's battery run down (as was suggested in one of the threads), and when I plugged it in to the AC power, I got the Samsung Galaxy logo!
I was then able to restart in download mode, and reinstall the md5 file via Odin. Not sure why letting the battery run down works, but at this point, I don't really care. I'm glad that the tablet could be resurrected from the dead, in spite of my mistake.
I hope this is helpful! :victory:
tab not showing up in ODIN
I have my galaxy tab soft bricked, but when I plug it in to ODIN, the pc does not recognise the tablet and therefore I can't reinstall the firmware, although the tablet is connected to the pc, as it gets charging when plugged in.
I've tried reinstalling samsung drivers, killing every samsung keys program running in background, another cable and even three different ODIN versions (v.1.7 // v3.07 // v.3.09), but it is not showing up in any version.
I have been looking for a solution since last year. last year I had windows 8 and it didn't work; then I upgraded to win 8.1. again nothing, and with windows 10 the same story. can anyone help me please?
thank you very much.
internal memory read only my p3100
hi ..
thanks in advance
i dont know what happened to my tab p3100, i am not able place any files in internal memory.
it will get into the main screen and gives bunch of errors like process google play is not working... bla bla bla...
i can uninstal the function but after reboot it will be there in the phone. i am bit tensed what is this is this a bricked one or?
please help me out i tried odin, through odin i installed omia rom 5.1 after that this error i am getting please help me out to solve this.
my phone already rooted..
Once again thanks hooping for the fix.
please mail the fix to [email protected]

Samsung Galaxy Tab 8.9 LTE unbricking

I have a Galaxy Tab model SGH-I957D (Telus) that I got from a friend who tried to unlock it to work on any SIM card and managed to totally brick it. It will not turn on (or vibrate) at all but the processer section does get warm indicating it is doing something. When I connect it to the computer it shows up as 24! separate drives (which windows cant mount due to them being a Linux format). If I connect it to a Linux computer 5 of the drives will auto mount. Under windows it shows up as a marshall london composite usb device 9006 and I tired following this guide: forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/page-5 (see post #84) but when I tried installing the drivers under windows 10 it said they were the wrong ones. I did manage to install the Qualcomm USB Composite Device 9006 by downloading this file: yuplaygod.com/files/YUPHORIA/YUPHORIA_drivers-v1.0.zip but that is as far as I got. Since Linux can see the partitions could I somehow recover them manually with the stock firmware image that is meant to be flashed with odin? I can attach a log file I found on one of the partitions if that would help. You can look at all the steps that I have so far taken in this other forum: eevblog.com/forum/repair/samsung-galaxy-tab-8-9-lte-unbricking/
Anyone have a root method for the SGH i957 att lte version running 4.0.4 ICS? I have been looking everywhere for a solution. There are tutorials on the 7300 7310 7320 and 7320t but nothing on the i957. From what I have read this requires a different rooting process than the 7300 series. I believe the 7320 and 7320t are lte versions but the kernels and methods will brick this one. Am I right? Can anyone point me in the right direction? I am new here to XDA. I have leaned a ton in the short time I have been here thanks to forums, threads, and responses from members of the community. What a huge resource of helpful people and information! Thank you!

G870 soft bricked, No USB Comm, stuck in boot with logo - need help please

I've been running NG3 rooted for 2 years w/ T-Mobile. Due to recent changes on the Tmobile network (they dropped 1900 and switched to b12 = 700a which the 870 can't acquire) I've been forced to move to ATT. When their SIM was loaded I could get 4gLTE so data and text worked, but couldn't make or receive any calls. The signal would drop entirely - no 4gLTE or bars.
I decided I'd try to reload the full NE4. The PC wouldn't recognize the phone via USB (new and old drivers tried). I tried 3 PC's same issue device unknown regardless of Samsung driver age. My wife has the same phone and same issue. Since USB wasn't being recognized (nor on my wifes 870) ODIN was out so I booted and tried loading via the SD card. Well I apparently bricked my phone attempting this. It won't boot beyond the SAMSUNG logo (thereabouts). I can't access the phone via USB. I can however use the bootloader (?) (v-up + pwer + home) and attempt to load from the SD card. I have several stock roms but I receive errors attempting to load these - " footer wrong" and " signature verification failure". I tried Downloading them again but md5 is good on them all
I'm not having fun... . Does anyone know how I can get my phone to load from the boot screen without these errors? I need to get my wife's 870 working too. Her phone can text but no calls (same scenario only I didn't mess here's up just yet). The boot screen on my phone still shows last up date NG3.
I 'm not concerned about being rooted or which version I land on anymore, I'd just to get it working again. Any help is much appreciated - thank you
for what it's worth talking to myself ... the USB cable I've been using for years and has always worked. Tried it on my wife's phone and didn't work but still thinking it's the PC unable to load the USB drivers. Bought 2 new phones. Tried the cable on the new phone - no drivers. Tried the new USB cable that came with the new phone and it worked fine. Used the new USB cable on my soft bricked phone and drivers loaded. I was able to use Odin to upload the OF3 revision to my G870 successfully. Now I'm looking for a way to root it.
any links please?
You can search for "wonder share mobile go" and find how to root with it.
OMG - That was amazing. It rebooted a few times but "SUCCESS". I can't believe all the steps we go through on XDA (and I love XDA) to root a phone but this was 1 click = done. The OF3 can easily be rooted with this software. I uninstalled it (cause I don't trust it) but the root remained and I'm rocking and fat happy.... AND the KNOX = 0
ON THE OTHER HAND - the software soft bricked my Moto G5 Plus. It's not all it's cracked up to be. I contacted the company and it really seemed to me the person responding couldn't read English. Their responses were incoherent and didn't approach the subject at all. Like they were from another country. Yeah.. one of those companies who rely on foreigners to handle their tech support. I'll never use that software again - not trust worthy and the techs are clueless
Thank you very much

Categories

Resources