I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!
Nobody? =\
Razor1973 said:
I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!
Click to expand...
Click to collapse
First of all, I'd say (from my experience) screw Kies. Go straight to flashing the STOCK ROOTED S3 files. Do NOT load any custom bootloaders or anything. This is step one, using Odin to get back to stock root. Here is a link to a tutorial (in case you need it, it has the files too): Click Here
Now once you finish that, go ahead and use Odin to flash the latest CWM or TWRP (up to your preference, I use TWRP). To get the latest TWRP for Odin, go HERE.
After you have the custom recovery, you should make a Nandroid backup in TWRP. Also, at this step, for the love of your sanity teach your dad how to make a backup. This might save you down the road
Now that you have a backup and are rooted, you can start flashing the roms. Make sure that you do NOT flash any bootloader OR modem unless they are the I747UCDMG2 ones. IF you flash those you will be fine.
Hope this helps!
Well, I had no choice by to use Kies because ODIN would always fail or crash. Only after I flashed using Kies could I use ODIN successfully. So I just flashed using Kies again, which allowed me to ODIN (3.07) the AT&T file in that thread you gave me. However, ODIN fails a few seconds into the flash with the following error. Any other ideas? Thank you for the help.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
By the way, phone won't boot up and ODIN will crash or any other attempt, as you can see in my second screenshot (same condition I was describing in my OP). It looks like it goes past the boot flash, but crashes on cache. So I need to flash via Kies again. It's been the only way I can start all this over.
In case it makes a difference, before the first ODIN attempt, the download mode read "CURRENT BINARY: SAMSUNG" and after it failed, download mode read "CURRENT BINARY: CUSTOM".
Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
xSharpi said:
Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Click to expand...
Click to collapse
These are flashabe through recovery, not ODIN. Both bootloader and ROM files are ZIP's and ODIN expects TAR, MD5, SMD, GZ or TGZ in the PDA section.
As I had mentioned, I cannot flash anything through a custom recovery (and I've tried several, including TWRP and CWM) because the recovery complains that the ROM is for a d2att and my device isn't. My device *is* a d2att, only that CM nightly flashed something to it that makes it identify itself as something different, it sounds like.
I really am stuck. So far, the only ROM I have been able to flash is stock 4.1.2 using Kies and nothing after that.
Any other ideas please???
Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
xXshur1kenXx said:
Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Click to expand...
Click to collapse
I just used Kies to flash to stock 4.1.2 successfully (which has always been the case) and then the S3 Toolkit 7.5 to root (screenshots). After the last step, the phone doesn't boot up (same thing always happens when I try to root), so I can't install GooManager or ROM Manager. However, I am able to get into stock recovery, so I will try to follow steps RockRatt recommends and report again. Thank you.
RockRatt said:
A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Click to expand...
Click to collapse
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.
Razor1973 said:
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.
Click to expand...
Click to collapse
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
xXshur1kenXx said:
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Click to expand...
Click to collapse
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).
Razor1973 said:
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).
Click to expand...
Click to collapse
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
xXshur1kenXx said:
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Click to expand...
Click to collapse
It's my dad's phone. LOL
RockRatt said:
Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Click to expand...
Click to collapse
What are you apologizing for??? God, no. It was me who bricked the phone, not you!
I'm about to leave the house and go to this really good cellular repair shop very close to me to see if they do JTAG repairs. I was going anyways to take my original Nexus 7 for a screen replacement. I tried to do it and screwed it up too. hahahaha
Razor1973 said:
It's my dad's phone. LOL
Click to expand...
Click to collapse
My mistake. Meant to say if he could haha. Sorry i couldn't help more. Hope the JTAG works!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
You have been very helpful. Guy doesn't do JTAG repairs. I will keep calling shops in town. If none does, I will ship it. Thanks!
For JTAG repair, have you checked this site? You still have to send the phone in, though.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii/
Let me just say I have been in this business long enough and it has been a while since I have been in a situation like this. So I'm running the project x port. And I want to upgrade to official 4.4. I download the tar and try to Odin it. I get this PIT error, like it requires the PIT file for something. Long story short I have been trying to flash the stock 4.3 rom and original PIT, stock 4.4 and kk Pit file. So they all keep failing and I tried ode and heimdall. Every time there is a Pit error and it won't go further.
I thought I had a 800 dollar brick with all this flashing but it boots up fine and works fine. I did not expect that to happen. And I can't boot to recovery.
So my question is:Anyone else have this experience?
Anyone have a solution?
Know why or what caused this?
How to go from project x to the newest ota?
Thanks
Sent from my SM-N900T using xda app-developers app
midnight93933 said:
Let me just say I have been in this business long enough and it has been a while since I have been in a situation like this. So I'm running the project x port. And I want to upgrade to official 4.4. I download the tar and try to Odin it. I get this PIT error, like it requires the PIT file for something. Long story short I have been trying to flash the stock 4.3 rom and original PIT, stock 4.4 and kk Pit file. So they all keep failing and I tried ode and heimdall. Every time there is a Pit error and it won't go further.
I thought I had a 800 dollar brick with all this flashing but it boots up fine and works fine. I did not expect that to happen. And I can't boot to recovery.
So my question is:Anyone else have this experience?
Anyone have a solution?
Know why or what caused this?
How to go from project x to the newest ota?
Thanks
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
It simple download stock 4.3 flash that. Wipe wipe wipe. Then download the official 4.4.2 then root and so forth. Don't cheat and get modded 4.4.2. Go to sammymobile and download original and install thru Odin. A few videos in threads show how
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
midnight93933 said:
Let me just say I have been in this business long enough and it has been a while since I have been in a situation like this. So I'm running the project x port. And I want to upgrade to official 4.4. I download the tar and try to Odin it. I get this PIT error, like it requires the PIT file for something. Long story short I have been trying to flash the stock 4.3 rom and original PIT, stock 4.4 and kk Pit file. So they all keep failing and I tried ode and heimdall. Every time there is a Pit error and it won't go further.
I thought I had a 800 dollar brick with all this flashing but it boots up fine and works fine. I did not expect that to happen. And I can't boot to recovery.
So my question is:Anyone else have this experience?
Anyone have a solution?
Know why or what caused this?
How to go from project x to the newest ota?
Thanks
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Go to dev section and download the tar. Put phone in download mode. Odin 3.7 or 3.9 your choice load the tar in the "AP" section and hit start. It may fail the first time. Did for me, and pretty much everybody else. Don't freak. If at first you don't succeed. So boot back into download mode and run the process a second time, this time it will go all the way through and you will have a nice clean Kitty Kat Phone.
When I flash in odin I NAND write start! then a big FAIL
So i think my phone is a zombie.. I can boot into recovery and into the system and actually do stuff its just really slow and bugs out. I have never seen a phne do this before help?
Alright I figured out my bonehead move. It flashed fine now.
I am trying to unroot and restore stock ROM so that I can sell my Note 2014 10.1.
I am using ODIN 3.09 and P600UEUCNK1_P600XARCNK1_HOME.tar.md5
ODIN keeps giving me a FAIL. Looks like "Cant Open Serial Port". I have attached a screen shot from ODIN.
Any ideas as to what I can do here?
Thanks
You need to extract the zip file, and edit .md5 off the end, leaving a .tar file to flash. Make sure you unroot via superuser, then factory reset, then download mode.....Will take 7-9 minutes. Wait for reboot, and removed to show in ODIN. Just did this myself, and device shows official, and recovery is stock, without even the Knox splash showing recovery bit! Easy breezy. I flashed on top of 4.4.4 bootloader the 4.4.2 .tar, and let it update OTA. T-Mobile P607-T Gluck!
Worked like a charm my friend...Thanks so much
Sent from my SM-N900P using Tapatalk
I followed these steps. Flashed same tar file, and successful install. Although i cant update software because says my version has been modified. Anyway to still get updates and be totally stock?
Flash updates from Kies instead OTA is never going to work again.
Sent from my SM-P600 using XDA Free mobile app
Please could anyone had the steps ... the same issue is faced with Note 10.1 Gt-8000
I' m using N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar with ODIN 3.07 which is detecting the com 3 or com 6 with it, and failing always and the device is stopped at either ODIN MODE if I used the volume down plus power or at Firmware upgrade encountered an issue. please select recovery mode in kies and try again... it would never enter to the recovery mode or Bootloader, please advise... thanks in advanced.
Dear all,
I just have a serious problem with my Note 2 N7105. I bought this phone with a rooted 4.3 androit and everything worked fine beside using the automatic update function (over the air update of android).
Therefore I downloaded the german 4.4.2 from Sammobile and flashed it with odin.
sammobile.com/firmwares/download/32565/N7105XXUFNE3_N7105DBTFNE1_DBT
Odin flashed completely with any errors . -> All threads completed. (succeeded: 1 / fail: 0)
But unfortunately it is not rebooting to androit nor reboot into recovery mode. After turning on the phone, I can see the samsung logo and after that it tried to boot and a red exclamation mark pops up and it's restarting again. The only possible thing is to get into the download mode again.
I also downloaded the german 4.3 version from sammobile and flased it with odin - but results stay the same.
I would be very happy about any help. Sorry in advance for my unprofessional explanation.
make sure you have downloaded the right tar file for your samsung
Anilkumar12345 said:
make sure you have downloaded the right tar file for your samsung
Click to expand...
Click to collapse
Could fix it meanwhile - it wasn't a problem of the tar file - the tar file was correct - but whyever the recovery was broken after downloading and installing the cwm recovery I was able to get into the recovery mode again and afterwards also successfully install the stock 4.4.2 tar file from sammobile.
Cheers,
mr_moods
My phone is broken. I rooted it and then installed a custom rom. After that it kept on randomly rebooting. I Then tries putting it back to stock with an md5 file, but it failed half way through. Now it just says firmware upgrade issue. Use recoverymode in kies. I tried but it says my phone is not supported. Now I keep on trying to install ota firmware updates but they keep failing. Please help get my phone up and running asap
Also telling me there is no pit binary
Go here to grab the zip file. Unzip and odin the tar file to bring your phone back.
That did not work it said auth fail
using a different kernel it succceeded
red2481 said:
using a different kernel it succceeded
Click to expand...
Click to collapse
For future reference. When this happens and Odin fails to flash official software you first need to make sure you odin the same software version that is currently running on your phone. If that fails then you can flash the stock unrooted kernel that matches your current software. Another tip, major software update's tar packages will include a sprint pit file. So if you are stuck and unable to flash the stock software with odin then try the first things I mentioned first and if that fails then odin an official rom tar that includes the sprint pit file. (incremental monthly security patches usually do not contain a pit file. Only the first release of a major update will include a pit) The tar packages do check the current kernel so that's the first thing you want to get back to stock when odin fails to flash stock software. I posted this for reference incase others have this problem in the future.