i have my friends phone and he's galaxy s3 is stuck on download mode and its looping there everytime
it happened out of nowhere, he wasn't playing around with it it just happened
now its stuck on downloading and wont go to recovery for me to initialize the device through kies or smartswitch
NO ACCESS TO RECOVERY MODE AT ALLL
i tried numerous ways to retrieve the phone into working condition but no success at all
thru odin i get the pit error and when i place a pit to repartititon with the stock tar file or the cwm recovery tar i failed
it says complete write operation failed and it takes a long time to set up connection with the device before showing me the fail
its a tmobile sgh-t999 prob 16 gb
any genius here got any ideas?
What firmware build was on the device and what build did you try to flash using Odin?
Did you try different versions of odin?
Different driver versions?
Different USB cable?
Different USB port?
If kies is installed on the computer, get rid of it. It interferes with Odin.
If none of that helps it may be a hardware failure.
Sent from my SGH-T999 using Tapatalk
The same thing has happened to my wife's phone and I have done almost the same steps to fix it with similar results.
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
OK, uninstalled Kies and tried to flash T999UVUEOH1_T999TMBEOH1_TMB rom with odin again and got there is no pit partition error. Would post some pictures of the boot screen and a screenshot of the odin program but need 10 posts. Well not sure what version was on phone before all this happened.) Also the ODIN bootloader screen says SYSTEM STATUS: NONE Warrenty Bit: 0 BOOTLOADER AP S?AEV: 1 among other things...forgot to mention I used ODIN v3.10.6 because v3.10.7 gave me a win32 error when I tried to run it on my Windows XP PC.
Here's my suggestion to at least get the phone running a ROM:
download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...5QWImOPDJboTA_V3D5S9eA&bvm=bv.107763241,d.dmo
download the tar version of TWRP 2.8.6.0 from here: https://dl.twrp.me/d2tmo/
download the latest cm12.1 for the phone from here and save it to a micro SD card: https://download.cyanogenmod.org/?device=d2tmo&type=nightly
place the micro SD card into the phone;
boot the phone into download mode;
open Odin 3.07 and uncheck everything except f. reset time;
click on PDA and browse to the tar TWRP file and select it;
connect the phone and it should show up as a com port in Odin;
flash TWRP;
when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
perform a full wipe of system, data, and cache;
flash CM12.1 from the micro SD card;
reboot the phone.
Hopefully, the above steps will get the phone booted so you can confirm the installed bootloader and modem.
Followed your guide step by step but flash failed in odin Get Pit for mapping..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1):crying: BTW thank for all your help.
You got the pit error flashing twrp in Odin? Any other errors? What model number is shown at the top of the screen when the phone is in download mode?
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Wow, thanks Doc for replying. I was hopeful for a better result. BTW it does say SWREV I just couldn't quite make out the W at the time so I put ? to indicate that. I do have a little experience working on these phones (replaced the entire LCD/screen and USB port on my Note2) The model of the phone is listed as SGH-T999 in ODIN mode and it is a T-mobile phone. How much is motherboard and what should I look for as far as part number?
Found this with a quick ebay search: http://m.ebay.com/itm/Samsung-Galax...Board-Motherboard-s3-/221940485670?nav=SEARCH
I searched for "galaxy s3 T999 motherboard". That one is 68.50 obo.
It's been a while since I've looked, and it looks like there's a lot fewer of them available now. (Used to get tons of results).
You can also look for an I747 (AT&T) board. The I747 and T999 are fully compatible. No other models will fit into the case. (The T999V and I747M would probably also work. I'm not sure about the T999L or T999N models though. I'm guessing they would, but really have no idea for sure.)
Some terms to search for would be: Galaxy S3 T999 motherboard, I747 motherboard, mainboard, etc.
Also search for the same models with broken screens. Many times people sell these cheap and everything inside works perfectly. Might be cheaper too.
Watch out for certain words and phrases in the listing though. Some sellers will try a little wordplay to make it sound better than it is. If i find an example, I'll post it. Stuff like cracked screen won't power on can be changed to sound like it's only the screen won't come on, when it's really the whole device. Either ask for clarification, or move on.
I like the ones that are very specific, like cracked screen, but does appear to boot up and gives boot sounds.
Ask the seller for the imei number and check it yourself on swappa. I'd also call t-mobile and verify with them.
I hope that helps. Feel free to ask if you're wondering about a specific listing or anything else.
Oh and if buying from an eBay store, make sure they've got very good ratings. Individual people often won't have many ratings, but can sometimes be more trustworthy and more willing to give specifics. Sometimes....
You can also check places like Swappa and Craigslist.
Sent from my SGH-T999 using Tapatalk
The simplest way to get a replacement motherboard would be to look in the used market for a t999 that has smashed or defective screen with working internals.
If it is not too expensive, a jtag repair centre may be able to force flash a rom.
Related
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)
My SGH-T999 ids itself as SGH-i747 in download mode. Is this typical/normal? I'm having trouble flashing full ROM tars with Odin. I can flash other things with it, like CM, but never a full ROM. I'd appreciate it if one or more people could check theirs and report back, or if you just know this is normal (or isn't!) if you could please just let me know.
If you're curious and want more background, look in this thread here where we're trying to troubleshoot:
http://forum.xda-developers.com/showthread.php?t=2672790&goto=newpost
Thanks, all.
UPDATE:
Just thougth I'd update this for anyone who stumbles on this thread in the future.
While everything about the phone from the outside and most of the stuff shown by Device Info indicated it was in fact a T999, apparently it did have an SGH-i747 bootloader. I overwrote that bootloader with an SGH-T999 bootloader, and hardbricked it.
So don't do that.
Talked to a JTAG-er who said that if the download screen says SGH-i747, it has an i747 motherboard.
Word of caution to others who end up with a refurb frankenphone.
Well, it looks like it happens sometimes, anyway.
But this solution won't help me, as the problem is bigger than this.
http://forum.xda-developers.com/showthread.php?t=2088220
What is the Model Number Listed behind the Battery on the White Sticker ? Also which TAR packages you have been trying to flash ?
Sticker says SGH-T999
When you say its i747 in Download mode, did you mean the "Downloading" screen on the phone ? If that's not it, then please specify.
Perseus71 said:
When you say its i747 in Download mode, did you mean the "Downloading" screen on the phone ? If that's not it, then please specify.
Click to expand...
Click to collapse
Sorry, I didn't see this thread update. I thought we were talking on the other thread once I saw you posting over there.
Yes, that is the screen I mean. The downloading screen. (vol down, center-button, power, little android guy, yellow "you've modified this puppy" triangle, flash count=1, QUALCOM SECUREBOOT, etc etc) That's the ONLY place I see i747. Sticker and build.prop file both say t999.
The build.prop file that came with it also identified it as a t999, but I got that replaced when I flashed a TMO image with CM. Did NOT change what shows up in download mode.
My theory is that the previous owner flashed an ATT image to the phone since the settings in the "original" build.prop file were for ATT in Canada, region was set to CN, and the language was set to zl or something similar. That file is on my machine at work ... don't have access to it right now, but point being, that build.prop also had the device properties set to a t999, i747 appeared nowhere in the file.
So, something on the phone is causing the download screen to show up as an i747. I'm thinking -- but I'm looking for alternate theories if someone doesn't think this is right -- that it's in one of the initial boot files. I don't know where the binaries are that run the download screen, but I think it's a good bet it's in aboot or one of the sbl files. I'm hoping someone can help confirm or deny or say "nobody knows, let's have a beer" or whatever.
I've tried to flash the TMO-UVDMD5 firmware (which does replace those files -- or it *would* if it would flash) from a zip file in CM ... but it fails on the assert(getprop... which is checking for d2tmo in either one of two properties. It's obviously not getting d2tmo. Whatever it's getting can't be getting it from the build.prop file, as both of those properties are set to d2tmo in /system/build.prop
My bet is that the Odin flashes are failing for the same/similar reason. There is something in the binaries on the phone that the flashing software doesn't like. I know it's safety checks trying to save me from myself, but this is not a normal situation - good chance the programmers did not anticipate this.
Now ... the long of it is, my IMEI was wiped and I need to restore it. But the IMEI restoring software won't talk to my phone because it uses RMNET and the RMNET driver loads and then dies within a minute after the phone connects. I suspect for the same/similar reasons that Odin won't flash a whole ROM and CM scripts cack out on checking to see what kind of phone it is through getprop.
I'm looking to build the phone from as low a level as I can to its original state as an SGH-T999. And then restore my IMEI.
Just thougth I'd update this for anyone who stumbles on this thread in the future.
While everything about the phone from the outside and most of the stuff shown by Device Info indicated it was in fact a T999, apparently it did have an SGH-i747 bootloader. I overwrote that bootloader with an SGH-T999 bootloader, and hardbricked it.
So don't do that.
Talked to a JTAG-er who said that if the download screen says SGH-i747, it has an i747 motherboard.
Word of caution to others who end up with a refirb frankenphone.
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.
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you
Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck
Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps
Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.
Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.
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.