[Q] Samsung galaxy SIII hard bricked will not boot but ODIN can recognize it - T-Mobile, Samsung Galaxy SIII

Samsung galaxy SIII hard bricked will not boot no power, but ODIN 1.85 can recognize it, (not the new Odins), when I try to re-flash it with Odin I get stuck at setupConnection..
any help? can I use the small USB mod

If you don't mind me asking, how you brick your phone?
Sent from my SGH-T999 using xda app-developers app

i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it

You're not hard bricked if Odin can read your phone. Reboot your computer then reconnect and flash a stock rom to be safe.

chubby1_8888 said:
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
Click to expand...
Click to collapse
If I'm not wrong ODIN uses TAR files and not ZIP files. Try unziping and see if there is a TAR file if there is then thats what you have to use in ODIN.

Same as OP's phone
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help

Kevinreid1 said:
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Click to expand...
Click to collapse
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!

serio22 said:
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
Click to expand...
Click to collapse
followed the guides about it just removed from top to quotes dealing with checking versions of device.

Kevinreid1 said:
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Click to expand...
Click to collapse
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case

serio22 said:
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
Click to expand...
Click to collapse
The roms I have downloaded are supposed to be for Sprint s3 I was running stock JB 4.3 if that makes any difference, any help on what to do know, thinking of trying the unbrick mmc card trick .... idk what else to do... thanks : ) and something went wrong somewhere for sure... lol I also found out my exact model number if that helps. SPH-L710MBBSPR again thanks for you responses..

Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!

DocHoliday77 said:
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
Click to expand...
Click to collapse
Thank you.. I knew I was in the wrong forum and that is why I said my s3 was a Sprint device... My problem however was the same exact problem. I got it fixed with file from another forum, while follow info from yet another forum, the file that worked for me was HomefixSprint_S3_L710.img the debrick_sph_l710.img would not work for me. I used win32diskimager and burned .img file to class 10 32gb card, stuck it in went in to download mode and used odin to write firmware file... Anyway back up any running.. I didn't download any t-mobile roms or anything that wasn't for the Sprint S3, what I did do was try and load an older JB rom that was under V4.3, it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade? Anyway thanks for taking the time to respond. : ) Cause no one has in the Sprint S3 forum yet.

Kevinreid1 said:
it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade?
Click to expand...
Click to collapse
No, Samsung is not turning into apple, there is a reason you cannot downgrade from a Knox bootloader. And to downgrade, with this device we can just flash an older ROM and it will work, maybe its different with the Sprint variant? Try to search in their forums if you haven't already

Related

[Q][ASAP]Is this a soft brick or a hard brick?

Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710. I am on a MacBook Pro running 10.7.5 OSX. Recently, I followed the steps as listed by h tt p:// epic4gtouchroot .com /epic-4g-touch-root/ how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
I was so confused so I spent about 3 hours on xda looking for an answer. Next, I downloaded Odin and packaged it for Mac. Then I downloaded the Samsung drivers just in case, and the stock ROM for my particular phone. I went through and tried to use Odin. Much to my dismay, Odin would not recognize my phone at all.
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
I tried to boot to Download mode but it says that the battery is too low. So now I am trying to charge it. However, it tries to load the charging battery icon that is normally shown when charging a powered off phone, and flashes to black. From this black screen it again slowly turns gray then white. Once it reaches the white screen, it turns back to the charging icon, and starts the stupid cycle over again. Its been doing that for the past 30 minutes.
UPDATE: My battery is not charging AT ALL. Whether plugged in to computer or wall it continues the cycle.
UPDATE 2: I made a video so that you can see what the phone actually does. I still can't post links, so please remove the spaces. http :// youtu .be /4LW60EknFWw
Remove the battery first, then try charging it. After, get windows onto your Mac or borrow a friend's, and use the windows Odin to get back to stock.
Sent from my SAMSUNG-SGH-I747 using xda premium
christykientzler said:
Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710.
<snip>
Click to expand...
Click to collapse
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
christykientzler said:
Recently, I followed the steps as listed by http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
Click to expand...
Click to collapse
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
christykientzler said:
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
Click to expand...
Click to collapse
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.
Oh my goodness...
ctomgee said:
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.
Click to expand...
Click to collapse
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?
christykientzler said:
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?
Click to expand...
Click to collapse
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.
Will do
ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
Ok :good: Will do. I was wondering what I'd tell them if I went to a Sprint store Thanks again.
TheATHEiST said:
TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.
Click to expand...
Click to collapse
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100
Again, there is no such thing as a "soft brick". There is just "bricked" and the term is used too loosely by n00bs.
If you can simply re-flash a rom your device is not bricked at all.
"Soft brick" is just a n00b term that is used because they think their device is bricked if they can't get it to boot.
Your device is only "bricked" if all you can do is JTAG or mobo replace.
Sent from my GT-I9100 using xda premium
ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
boki9999 said:
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100
Click to expand...
Click to collapse
Is there a one-stop resource for "Jtag or M/B replacement"? I'm having trouble searching forums for some reason, otherwise I would look for it myself.
You need to get it into download mode and then reflash a ROM appropriate for your device. Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.
postfatal said:
You need to get it into download mode and then reflash a ROM appropriate for your device.
Click to expand...
Click to collapse
Thank you, will do.
postfatal said:
Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.
Click to expand...
Click to collapse
LMAO, that's true. I don't blame anyone but myself for my mistakes.
If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2
Curiousity killed the cat...
ssCISengineer said:
If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Because I am curious. This is where it often times gets me, but I like to learn new things by doing. In my eyes it's usually worth the risk. I will admit this was a stupid mistake, but I have certainly learned a lot about rooting in the process
Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.
Thank you
Dr. Fed said:
Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.
Click to expand...
Click to collapse
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!
christykientzler said:
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.
Wait what..?
Dr. Fed said:
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.
Click to expand...
Click to collapse
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.
christykientzler said:
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.
Click to expand...
Click to collapse
The one clicks are full "images" flashed through Odin. I recommend this because a one click will reflash your stock rom, modem, and recovery partition. This is what you need to do to repair your phone. If you try to flash something in recovery, it will repair your rom but not necessarily your modem/radio/firmware, and this could be a problem. I'm not sure exactly what you flashed before, so I think its best if you fix it all with a One Click.
As far as using a Mac goes, I am not sure. I'll look into it, you should too. Odin used to be only for PCs, Heimdall for Macs. Maybe its changed now?
---------- Post added at 08:30 PM ---------- Previous post was at 08:19 PM ----------
You must have some schmo friend that will let you borrow his or her PC laptop for 10 minutes. Install Odin , install the proper drivers. Go into Odin mode, connect phone, once recognized... click.
Look up QBKing77 on YouTube, search on YouTube "QBking77 Epic 4g Touch" and you will see instructional videos with appropriate download links.
Why have you lot continued to answer this thread ? It's in the wrong place. More to the point, why hasn't anyone asked mods to move it to Epic 4G Q&A ? (Which I've just done)

odin fail sytem.img.ext4

I had a beautifully running dlk3 at&t SGH-I747. had problems with battery so I flashed odin to stock DLK3. then I took the OTA from at&t and let it complete. at the end I told cwm not to let it lose root or lock boot loaders, I answered 2 questions about preserving root and secured or some thing like that. rebooted and I have the jb4.1.2 . all good.
you know I gotta see if I am missing out on any thing by using cwm to preserve root ect.
so I start over clean DLK3 take the OTA form At&t . this time I have cwm not interfear. ok great i'm jb 4.1.2 again works good.
I used CF-Auto-Root-d2att-d2uc-samsungsghi747 and now I get fail at system. as you can tell i'm still learning and learning my lessons, but if some one could direct me to what step I should try i'd appreciate it.
edit:
after I tries keis to fix it it failed and after a battery pull and retrying odin to DLK3 stock. open oden , plug phone in com does not light up but it lists the top 0 failed threads. so I un plug and plug in and retry DLK3 and end up taking screen shots
I have lost my recovery all together I only have download mode
Start with the basics...try a different micro usb/usb cable. Then if that doesn't work, try a different usb port on the pc. Don't use a hub. Make sure the phone's micro usb port is clean of debris, as well check the ends of the cable and usb port to make sure they are clean.
The cable is usually the cause of the failure in urs and other similar instances. :thumbup:
Sent from my SAMSUNG-SGH-I747 using xda premium
4-2ndtwin said:
Start with the basics...try a different micro usb/usb cable. Then if that doesn't work, try a different usb port on the pc. Don't use a hub. Make sure the phone's micro usb port is clean of debris, as well check the ends of the cable and usb port to make sure they are clean.
The cable is usually the cause of the failure in urs and other similar instances. :thumbup:
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
thankx for your reply I broke out the original usb cable and tried different portsand stilo the same.
I here searching the forums now looking for a clue as what to do to get my stock recovery back.
Just for giggles, try using Odin v3.07. Several people say the version your using is ok, but I've always used 3.07 on the s3 with no problems.
that's the version I'm using. I found a pit file reset it and got a recovery flashed. it allows flashing from external storage, but when I try to do that it sends me to the internal storage where I cannot put a file yet.
I'm thinking about sending it to get jtag repaired but then I wouldn't have gotten to fix it my self.
as I know see I flashed cf auto root on locked boot loaders ( the method of checking for locked boot loaders I used was dumb) and I got bit.
can any one tell me of how they handled this?
thankx
Bootloaders on this device, I747/m, are not locked, afaik. And the screen shot you posted was from Odin 1.81.
---------- Post added at 09:40 AM ---------- Previous post was at 09:28 AM ----------
Try flashing lg1 stock, not rooted. It will o wipe your internal sd, but may get you fixed up. Lg1 is the only full wipe stock package we have.
oh crap i now know what happened. th file that had odin 1.81 in it. i knew better but it was in the pre packaged auto root for the at&t sgh-I747.
after you pointing out i didn't use the rite one for the auto root (even tho i uves 3.07 sgs3 odin rite after i didn't notice that i used 1.81.
thats why i posted the errors in full scren shot just ncase i did some thing stupid hopping some one would point it out.
so i can get in to download and if i work at it i can now get into a buggy but usable stock recovery.
i was using stock not rooted DLK3 from the same place as the Lg1. i tried but still only barley alive.... but i believe i can fix it. no proof yet tho.
i already bought a brand new sgh-I747 off of swappa and it will be here about the 9th. so now i have time to fix it. it'll be a project / testing phone.
now that i know that the http://forum.xda-developers.com/showthread.php?t=1963790&highlight=autoroot where i downloaded http://autoroot.chainfire.eu/ sgh-I747 file using odin 1.81 packed in with it, and followed all the instructions.
i am using odin 3.07 galaxy 3 odin.
can any one help me on what i could do with my testing phone to fix it if i can adb in?
and suggestions will be considered.
i don't post much. i'm a reader but i had to speak out as i'm running out of options.
i read this forum more than the news. i'm always a little behind the development thats going on and i follow as a student.

Unbricked Galaxy S3 but now cannot flash stock firmware

Hey guys, I have a Samsung Galaxy S3 for Tmobile SGH T999 and I had cyanogen on it until it crapped out and got hard bricked. AFter following these links, http://forum.xda-developers.com/showthread.php?t=1949687 and http://forum.xda-developers.com/showthread.php?t=2439367, I was able to unbrick my phone and get into boot recovery mode. However, when i try to flash the stock firmware in odin, I get an error (the error is shown in the attachment). Can anyone please help me? Sorry if im posting something wrong, I am new to this forum. Thank you!
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
DocHoliday77 said:
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
Click to expand...
Click to collapse
I tried this still doesnt work.
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
DocHoliday77 said:
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
Click to expand...
Click to collapse
Sorry i meant failure not error. I bricked it because my cyanogenmod was having problems and i tried to restore it, after i did it completely bricked. Sorry can you please elaborate what is TWRP, MJC or NC2 firmware, im dont have much knowledge about these kind of things. Thank you so much for helping me, it means alot to me and I will do my best to follow your directions.
Ok, ill explain better when I get to my computer. It'll be too much to try to type on this tiny device im using right now!
But for now, TWRP is a custom recovery, like CWM. You use it when flashing roms like CM.
MJC and NC2 are just the different firmware builds you can flash in Odin. We shorthand it by just using the last 3 letters of the build version. T999UVUENC2 is what im referring to when I say NC2.
Take a look at my firmware thread. Its stickied at the top of development. Linked in my sig too.
Let me know if this helps your understanding at all. Ill explain more in what to do shortly.
Thanks for that, it gave me a better understanding. I tried to install flash and this happens when i try to flash twrp or MJC on odin
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
DocHoliday77 said:
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
ojhasha said:
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Click to expand...
Click to collapse
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
ojhasha said:
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
Click to expand...
Click to collapse
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
DocHoliday77 said:
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
Click to expand...
Click to collapse
It was invisibleK's link that was unsafe. I used your 16GB Pit file in here, http://www.androidfilehost.com/?w=files&flid=6471 and i got the same result. I dont remember where i got the other pit. I got stuck on Leave CS on the odin 3.09 and when i click start it failed again with the repartition failed.
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
DocHoliday77 said:
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
Click to expand...
Click to collapse
sorry i didnt respond in a while, I was really busy with homework. I tried what you said and still no sign of success. I brought my phone to a repair shop and they said the motherboard is damaged and it needs to be replaced for 150$. I hope this guy is just bull****ting me, can anyone confirm? I really hope there is still light at the end of the tunnel right now.
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
DocHoliday77 said:
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
Click to expand...
Click to collapse
do you recommend me doing it? or are there more alternatives.
If the memory itself has gone bad, that's your best option. It is possible to change just the memory chip, but the part is probably hard to find and it requires a higher level of soldering skills.
There's a video of this, if I can find it again ill post the link.
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
yellowonion said:
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
Click to expand...
Click to collapse
did you have my symptoms? did you ever fix your phone? if so please share, i want to get my phone back in the cheapest way possible.
PS. I charged my phone today and the red led light showed up, that means my motherboard isnt broken right?
Not necessarily. It means there is a problem and requires special drivers and programs to fix, (or the debrick sd card). It basically just means the computer sees something is plugged in. If the memory has gone bad it could very well still give the red led and/or boot from the sd.
The only good way to verify the board (or memory) needs replacing would be to go to a second shop and ask them to attempt a jtag repair. If they tell you the same thing as the first shop, ask if they can be more specific about what happened when they attempted the jtag repair. At this point though, its a pretty good guess that the memory has gone bad.

[HELP THREAD] Ask ANY Question. Noob Friendly.

How do i get a rom on my note 4 i have sprint running N910PVPS4DPE
peterogg said:
How do i get a rom on my note 4 i have sprint running N910PVPS4DPE
Click to expand...
Click to collapse
Did you try Samsung Kies on. PC?
jimmbomb said:
Did you try Samsung Kies on. PC?
Click to expand...
Click to collapse
Hey I always use TWRP to flash Supersu to root but I was wondering cause Ive been asked several times what easiest way to root. My question is = Does CF Auto Root still work for our device or is it just for older firmware? Thanks in advance!
What's the best way to update to the latest OTA on a rooted phone without losing data or root?
Sent from my SM-N910P using XDA-Developers mobile app
skanndelus said:
What's the best way to update to the latest OTA on a rooted phone without losing data or root?
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
With systemless root can't we just flash back stock kernel and recovery, to accept ota. Or does phone still not pass system check for ota. I've never tried myself so I was wondering.
My phone is on PD1 via OTA update.
Unrooted and stock as bones in a bag.
Yet, Now it refuses to check for updates anymore.
Manually or auto update checks via wifi.
Im locked out of latest updates.
Any ideas?
Even keis says up to date, even though the PE1 has been out for a while.
Any id
Thanks.
peterogg said:
How do i get a rom on my note 4 i have sprint running N910PVPS4DPE
Click to expand...
Click to collapse
First step is to use Odin to flash twrp or cwm ( I use twrp)
After that boot to twrp and create a back up (always do a back up)
Then go to wipe, advanced wipe and wipe dalvik, system,data, and cache.
From there go to install and select the rom you want to install and swipe to to install. Make sure your phone is on the correct baseband and firmware version to run the rom otherwise you will have issue like WiFi not turning on and camera not focusing! Reading the OP of the rom is very important. Being on PE1 you would probably have to downgrade to OK1 or PC1/PD1 for majority of roms for now. Freeze has a page where he has all the firmwares and their baseband, you can just dl them and flash them through Odin. Let me know if you need anything explained. If you mean how to literally get the rom onto the phone, I usually will just download or put the SD card into my computer. Another good option is samsung side sync/android file transfer
---------- Post added at 12:23 AM ---------- Previous post was at 12:21 AM ----------
jimmbomb said:
My phone is on PD1 via OTA update.
Unrooted and stock as bones in a bag.
Yet, Now it refuses to check for updates anymore.
Manually or auto update checks via wifi.
Im locked out of latest updates.
Any ideas?
Even keis says up to date, even though the PE1 has been out for a while.
Any id
Thanks.
Click to expand...
Click to collapse
Did you manually unroot? Or did you flash back to a stock? You need to completely flash a stock firmware to take an OTA.
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
aaron74 said:
Hey I always use TWRP to flash Supersu to root but I was wondering cause Ive been asked several times what easiest way to root. My question is = Does CF Auto Root still work for our device or is it just for older firmware? Thanks in advance!
Click to expand...
Click to collapse
I would say go with manually flashing root. CF auto root hasn't worked for me in a long time. Besides majority if roms you'll find are prerooted anyway so there's no reason to really have to flash a root. Unless of course you're rooting stock.
I have never rooted. Always bone stock since new and always have OTA the updates. 3 maybe so far.
Still cant OTA anymore
hi every one
i have a question
i just bought a sprint galaxy note 4 and im living outside USA and my problem is that i have this annoying message of handsfree activation and i cant also select cdma or lte i just can use gsm
my android version is marshmallow 6.0.1
and my device isnt rooted
so please help me to unlock my phone and what is the best way to root it safely
Hi, mine it's the same situation, anybody can help us with that because the gsm speed is to slow for navigate, thanks in advance.
I don't know if this thread is still active.
Okay,
So I have a Sprint 32gb model Note 4 SM-N910P UD, I was experiencing the random reboot issue so I removed the sim card, thought it was fixed and tried to install a sprint pushed update via the phones normal process. It power cycled in the update and now it's pretty bricked, I can't do a factory reset or clear cash. If I turn it on it goes straight into the "Firmware upgrade encountered an issue screen"
Now I try to be pretty self sufficient so I did some reading and downloaded two versions of Kies (both of which don't recognize my device) I downloaded three versions of Odin and have been attempting to restore with stock platforms. This is where I ran into my problem, I know nothing about this stuff and I am completely lost. I tried to go to Best Buy and their Samsung techs couldn't help me.
I've tried searching the site, but all the links people provide are to multiple versions of TWRS and basebands, but I don't know what those are or which ones I am supposed to download or what slot or order they are supposed to go into in Odin to re-flash this device, I keep getting "need PIT file" or other errors.
So I am throwing myself at the mercy of the court, is there an idiots guide to how I get this phone back up and running in a basic configuration? I don't need the latest update, or to even save the data that was on it before, I just need it to run like normal and I'll never download an update again. If you can link me to the thread of just tell me "look dummy download this files and install them in this order" I will be forever in your debt.
The_Malhavoc said:
Okay,
So I have a Sprint 32gb model Note 4 SM-N910P UD, I was experiencing the random reboot issue so I removed the sim card, thought it was fixed and tried to install a sprint pushed update via the phones normal process. It power cycled in the update and now it's pretty bricked, I can't do a factory reset or clear cash. If I turn it on it goes straight into the "Firmware upgrade encountered an issue screen"
Now I try to be pretty self sufficient so I did some reading and downloaded two versions of Kies (both of which don't recognize my device) I downloaded three versions of Odin and have been attempting to restore with stock platforms. This is where I ran into my problem, I know nothing about this stuff and I am completely lost. I tried to go to Best Buy and their Samsung techs couldn't help me.
I've tried searching the site, but all the links people provide are to multiple versions of TWRS and basebands, but I don't know what those are or which ones I am supposed to download or what slot or order they are supposed to go into in Odin to re-flash this device, I keep getting "need PIT file" or other errors.
So I am throwing myself at the mercy of the court, is there an idiots guide to how I get this phone back up and running in a basic configuration? I don't need the latest update, or to even save the data that was on it before, I just need it to run like normal and I'll never download an update again. If you can link me to the thread of just tell me "look dummy download this files and install them in this order" I will be forever in your debt.
Click to expand...
Click to collapse
Sounds like you need the 4 file repair firmware. At least this is where i would start. I'll try to find you the links and guide. Give me some time and I'll get back to you.
aaron74 said:
Sounds like you need the 4 file repair firmware. At least this is where i would start. I'll try to find you the links and guide. Give me some time and I'll get back to you.
Click to expand...
Click to collapse
I really appreciate it, take as much time as you need I'm just happy to have help from someone more experienced than me.
@The_Malhavoc
Ok, so this is what i would try first, since you said Odin gives Pit file error.
To start, uninstall all Samsung software (like kies) from your pc. Also uninstall Odin. I guess Odin don't install, but use the one in this post.
Download and install Samsung drivers from here to your pc.
Now download Odin 3.11.1 from here!
Unzip odin to your desktop.
Download the N910P repair firmware here! You'll need to unzip this. See below.
Ok now I provided all the files here. But now continue to this post and read carefully and follow directions!
https://forum.xda-developers.com/showpost.php?p=68854735&postcount=1
I hope this helps and all you have is a software issue!
---------- Post added at 08:35 PM ---------- Previous post was at 08:26 PM ----------
The_Malhavoc said:
I really appreciate it, take as much time as you need I'm just happy to have help from someone more experienced than me.
Click to expand...
Click to collapse
Fyi, i can't guarantee this will work. I personally have never needed to use it, or try it. But i know it has the pit file in this. So i figured it'd might help.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
@The_Malhavoc
Before you try this, respond back to me. So i know You didn't start yet. I'm trying to find you another solution.
aaron74 said:
@The_Malhavoc
Ok, so this is what i would try first, since you said Odin gives Pit file error.
To start, uninstall all Samsung software (like kies) from your pc. Also uninstall Odin. I guess Odin don't install, but use the one in this post.
Download and install Samsung drivers from here to your pc.
Now download Odin 3.11.1 from here!
Unzip odin to your desktop.
Download the N910P repair firmware here! You'll need to unzip this. See below.
Ok now I provided all the files here. But now continue to this post and read carefully and follow directions!
https://forum.xda-developers.com/showpost.php?p=68854735&postcount=1
I hope this helps and all you have is a software issue!
---------- Post added at 08:35 PM ---------- Previous post was at 08:26 PM ----------
Fyi, i can't guarantee this will work. I personally have never needed to use it, or try it. But i know it has the pit file in this. So i figured it'd might help.
Click to expand...
Click to collapse
I understand completely about no guarantee it'll work, but its more than I had so I'll give it a go. I wasn't expecting a reply so quickly and left my stuff at the office. Ill get it a shot tomorrow and report back, thank you so much for taking the time to help out a lost newbie have a great day!
The_Malhavoc said:
I understand completely about no guarantee it'll work, but its more than I had so I'll give it a go. I wasn't expecting a reply so quickly and left my stuff at the office. Ill get it a shot tomorrow and report back, thank you so much for taking the time to help out a lost newbie have a great day!
Click to expand...
Click to collapse
Ok great. Cause I'm trying to find you an easier firmware to try first. So don't try that just yet. I'll post back shortly.
Edit. What's your current firmware?
The_Malhavoc said:
I understand completely about no guarantee it'll work, but its more than I had so I'll give it a go. I wasn't expecting a reply so quickly and left my stuff at the office. Ill get it a shot tomorrow and report back, thank you so much for taking the time to help out a lost newbie have a great day!
Click to expand...
Click to collapse
Ok Im back. Before You do what I first told you. I want you to follow this guide. It will download you a firmware with a pit file. I actually have the file but it will take 8 hours for me to upload. so just do this.
First, All these links are from this post here. Its an old program "SamFirm" but it still works.
But Im providing shortcuts here for you. To simplify this process.
1. Download Samfirm0.3.6.zip Here!
2. It requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
3. So Download and Install above Links!
4. Unzip samfirm into its own directory.
5. Open it up and run as an Admin!
Now in Samfirm put in following info: (check pics)
Model== SM-N910P
Region== XAS (or if you want sprint default logo at boot then use SPR)
Check the box== Auto
and also box== Binary Nature
Then Click Check Update
It should show it found firmware SM-N910P/XAS/N910PVPS4DPK1/N910PSPT4DPK1/N910PVPS4DPK1/N910PVPS4DPK1
Make sure both boxes == Check CSC && Decrypt are both selected and Click Download!!!
IT'LL Download and Decrypt a special binary firmware, that will contain a PIT file. When you flash this file with Odin, It will completely wipe your device.
When its done just unzip the file. And then you will have a TAR.MD5 file to use with Odin!!
In Odin, Load this file to AP slot. Only select 'F.Reset Time' & 'AutoReboot' the first time, just like a normal flash.
Hope This Helps Ya!!! If This file doesnt solve your problem, you could try that other file from previous post, if you wish!
But just try this and let me know what happens!!
Good Luck!!
No luck,
I downloaded ALL_SPT_N910PVPS4DPK1_N910PSPT4DPK1_CL9120850_QB11420407_REV00_user_low_ship_MULTI_CERT.tar .md5 from Samfirm then extracted it.
Downloaded and installed odin 3.11.1 from the above link and ran as administrator.
Checked the AP box and linked it to the extraced md5 file, made sure autoreboot and f. reset time were the only things checked.
Started phone in download mode using vol down + home + power, then pressed up to enter download mode and plugged the usb into the computer.
Once Odin registered my phone with the "added" notification I clicked start.
Odin read:
<id:0/003> Odin engine v(ID:3.1101)...
<id:0/003> File analysis..
<id:0/003> SetupConnection..
<id:0/003> Initialization..
<id:0/003> Set PIT file..
<id:0/003> DO NOT TURN OFF TARGET!!
<id:0/003> FAIL!
<id:0/003>
<id:0/003> Re-Partition operation failed.
<OSM> ALl threads completed. (succed 0/ failed 1)
Meanwhile my Note read:
ddi: mmc_read failed
ODIN MODE (High Speed)
etc. etc.
Secure download: enable
UDC Start
ODIN: flash read failure
Error: There is no pit binary.
so barring any failure on my part (which I'll be the first to admit is very likely) I may have to try again using the first message you suggested. I'll hold off for now just to see if I did anything wrong, considering I've heard that if I manually try flashing a PIT I could hard brick my phone permanently and it should only be as a last resort.
In any case no matter how it works out, thanks again Aaron for taking the time to help me out. I just saw how to add thanks to the posts, so I'll be doing that now.
The_Malhavoc said:
No luck,
I downloaded .
Click to expand...
Click to collapse
Ok, well it definitely sounds like you got the emmc problem that i see floating around here.
I don't have any experience with it. But a couple more suggestions.
1. Try this file again. But in Odin select 'F.Reset' & 'Re- partition'. And don't select ' auto reboot '. Let it flash, and if successful, when done pull battery and reboot to recovery then wipe and reset.
2. If that is no go. Try the first solution i pointed you to.
If neither these work. Then its beyond me. Sorry.
Hope you get one of these to work for you. :fingers-crossed:
Edit. I should have mentioned, if your phone has twrp and you can boot to it. You should make a complete backup especially the efs. And copy and save it off phone.
Edit 2. You could try posting your question to that first thread i mentioned to you.
Why my SM-N910P the FRP couldn't activated.
I did a lot of factory resets but that FRP didn't activated at all.
I am on 6.0.1 PJ1 and bought it as a second hand device not new.
Why this happened... Could somebody explain this weird thing to me?

Note 7 SM-N930F bricked / / need help!

I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD
bill340 said:
I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD
Click to expand...
Click to collapse
try to download the firmware from http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/ and try to flash via odin.
Never ever try to flash anything till the time there is no evidence of success.
I tried that, but the problem is that I always get this error in Odin when trying to flash...
Did you check OEM unlock before you flash as per the instructions? not doing so will result in a boot loop.
Try different cable and USB port. I had trouble with both that had me running in circles.
Sent from my SM-N910T using Tapatalk
Yes, I did OEM unlock before the flash.
Different cable and USB port makes no difference...
Usually when I have issues I try to uninstall all drivers related to phones and only install the one I need. Then after a restart and forcing the phone into Odin I'm able to flash without issues.
It might be failing because of a Partition size error. Have you tried the Samfirm Tool to download a firmware from your region?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Also, I'm doubtful whether this is a new trick up from Samsung's sleeve. This Phone is still new, so it's quite a learning process. Maybe Samsung has implemented something to block these unofficial flash attempts. However I thank you taking the risk and trying the recovery first.
Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
bill340 said:
Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Click to expand...
Click to collapse
Download and install SmartSwitch for PC. Then follow this Video.
I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...
I dont think theres a fix for this issue yet. There's also no subtantiated literature in the larger cummunity pertaining to rooting the Note 7.
I am guessing this is an additional precaution taken by Samsung therefore the rooting process needs a very specific set of steps in order to circumnavigate the systems Sammy has put in place. The thread itself says WIP, so I applaud you for your courage.
Nonetheless my suggestion is to instead of waiting for an answer which no one can provide, go to Sammy and bull**** to them that u plugged in the computer and it became a brick.
Theres is no possible senario whereby the internet can help you because we know next to nothing about Note 7.
I sincerely hope that you can come out of the situation with a working Note 7 in your hands whilst not burning a hole in your wallet due to the repairs. God-speed my friend, God-speed.
bill340 said:
I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...
Click to expand...
Click to collapse
This seems to be an issue in your drivers, Please uninstall all samsung related and flash box related (if exists) in your PC and try installing it again.
Alternatively, you can just walk into a Samsung Care store and get it done while you wait.
I did that already... No luck. I will try on a different pm next.
Bill sad to see this happened to you
I am exactly coming for the same forum and was following the same steps thought u were, but u took one more step forward and flashed the vitanamese firmware, your phone just messed up there. Was actually about to do the same thing but then read your comments. My phone starts but with errors and has battery drainage , i havent lost anything as it is still virgin and havent transfered anything to it yet. Will wait probably 4 to 5 days more for the official firmwares to release and fire it in.
Sorry to say but u had become the test subject...
---------- Post added at 11:07 AM ---------- Previous post was at 11:03 AM ----------
The recovery mode cannot be accessed, no matter how hard you try
Sent from my SM-N920C using XDA Free mobile app
I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.
Well tht will be a good choice
But if u give it three more days and wait for the official firmwares to release would save you some time.
I am still following up with it.
Sent from my SM-N920C using XDA Free mobile app
I really doubt, that this will help, since I cannot flash anything in odin. After initialization I always get the error "FAIL (DeviceInfo)"
bill340 said:
I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.
Click to expand...
Click to collapse
Same here in (Dubai) Mate, They don't even have the parts, or Tools to open the device up. If you remember me, I screwed up my Note 7 a week back, Just after two days from launch, and I still didn't receive it. They are still unable to sort it out.
I'm sure when a proper firmware for XSG (Dubai - Same as your device) and a proper ODIN is released to flash the Note 7, this will be a piece of a cake. Just hope for the best, As just like you - I too took a leap of faith and did something stupid.
Anyway, Wishing you luck !
I am not sure if this will help....
What happens when you try a older version of Odin?
Its worked for me in the past, with my s6 edge.

Categories

Resources