Develop Bugs

CM nightly did something to my dad's phone

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/

Have I bricked my phone :( - Experts plz help!

Guys,
!!!!! N00B Alert - I am not an expert in what I am doing. Just following instructions from experts like you. I will try to be as technically articulate as possible !!!
I had recently (about a month ago) rooted my phone to install CM 10.2. I love CM.
In an attempt to unlock my phone I wanted to get back to stock ROM. So I googled and bumped into a way to do it from Kies (not sure if it was a good idea). I followed the instructions and boom the firmware initialization failed half way through. Now when I turn my phone on I get this error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So I tried again multiple times but it won't work.
Then I thought may be there is another way and googled and found this thread - http://forum.xda-developers.com/showthread.php?t=2186967
Followed the instructions to the word, but I see the dreaded FAIL message in ODIN.
Below is the log. (I tried twice in one stretch).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Another thing is I am not able to get to recovery mode. When I try I can only get to the Firmware error screen I mentioned above.
Any help to get out of this mess would be great!

did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

andrewjae04 said:
did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I didnt know I have to have the LK3 bootloader, may be I missed in the instructions.
Anyway, how do I flash Clockworkmod from Odin? if I can do that I can get back to CM 10.2 and then try paying for unlock code.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

andrewjae04 said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank You!
andrewjae04 said:
http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I am on AT&T.
After I read your post about flashing CWM with ODIN I researched and found a method. I tried it and it PASSED!. Then my phone restarted and boom it booted directly into CM 10.2. Not sure how, felt a bit creepy. Then I updated to latest Nightly CM 11 build and brough back all my apps and my phone has LIFE right now. Thanks for the tip! :good:

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
I believe if you were originally on 4.1 then you still have that bootloader. I dont think OTA updates the bootloader so you should be able to downgrade with the root66 if that is the case.

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
This is why your flash to stock failed, lucky for you. The MJB bootloader is not downgradable and if 'successful' is bad news...aka brick, requiring serious hacking if not JTAG service to repair. As far as ROM's go as long they do not attempt to change the bootloader (none i've seen do, but you never know) the worst that could happen is a 'status 7' fail in recovery and no change to your firmware, pertaining to the bootloader that is. There are any number of other reasons why something could go wrong during the process. MJB has been around long enough most customs ROM's have probably adapted their updater-script to include it. If not there are ways around this I (and several others) have documented elsewhere. My advice moving forward, make sure to educated yourself thoroughly before attempting anything that can brick your device and if you are not sure, ask first flash later.

dmplus said:
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.
Click to expand...
Click to collapse
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233

audit13 said:
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233
Click to expand...
Click to collapse
I had tried to flash that via odin without success. What I was able to do to fix the issue was to flash a custom recovery via odin (TWRP). Then use the custom recovery to blind flash (no signature or md5 check) the ATT modem, and then I was able to flash the link you sent. After that it still didnt boot, so i had to reboot in TWRP, dump caches, reboot again, wait, literally like 5 minutes and it came back to life. Whew, what a day.

Can't boot / Odin won't work/No recovery

Hi everyone, looking for some guidance here. Ive checked different solutions but I think I've got a unique combination of "dun goof'd"
History:
I have a Canadian (Bell) SGH-I747M that is rooted and was running the latest cyanogen.
Wanted to lend it to a friend who lost his job and needed a phone but he had a deal through rogers and my phone was locked to Bell.
I tried a few of the unlock code steps but I needed to be 4.1.2 or lower for it to work I heard so I tried installing 4.1.2 and thats where it went wrong. I did a firmware update to back it down and mid update it failed.
I can get it into download mode but not recovery. Letting it boot normally gives the message "Firmware upgrade encountered an issue. Please select recovery mode in Keys and try again" I don't think Keys works with cyanogen and even if it did, there is no serial # sticker behind the battery and since I can't boot into settings, I don't know the SN.
When I put it in download mode and try Odin using stockROMS.net oldest or newest image, Odin fails and the phone message is:
ODIN SW REV CHECK FAIL : Fused 2 > Binary 0
So long story short, any help is sincerely appreciated, my ideal state would be a working phone thats unlocked so my buddy can use it. IF that means an older OS, all good. Can I even fix this?? If you need more info I'll keep checking in... THANKS!

You cannot downgrade if your phi e has ever had the 4.3 or higher bootloader.
Fix the phone by booting into download mode and flashing the latest stock rom from sammobile.com.

I can boot into download mode but Odin is erroring out.
I tried the sam mobile stock rom and another, I tried another usb cable and different port.
SGH-I747M (Canada) Bell 4.4.2 KitKat I747MVLUFNH2 2014 July
The error on ODIN is:
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
Error on the phone is SW REV CHECK FAIL : FUSED 2 > Binary 0

You must be flashing an older bootloader because it fails when it gets to aboot.mbn.

Im following this thread... Odin still errors out and I'm using the most current bootloader (I think) for the S3 I747M on Bell
http://forum.xda-developers.com/showthread.php?t=2549068

Are your trying to flash a 4.1.1 or 4.1.2 rom? Can't be done if you have a 4.3 or newer bootloader.

audit13 said:
Are your trying to flash a 4.1.1 or 4.1.2 rom? Can't be done if you have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
4.3 ROM, newest one.

The newest ROM is 4.4.2.
What bootloader version is on your phone?

How do I tell??

Try flashing a stock 4.3 ROM from sammobile.com for your i747m.
If Odin fails when flashing aboot.mbn, it's probably because the 4.3 ROM you are trying to flash has an older bootloader that the one currently on your phone.
If flashing the 4.3 ROM via Odin fails, copy the latest CM11 ROM and the corresponding Gapps to your internal or external memory, flash the latest Philz Touch recovery for the d2lte via Odin, boot into recovery, flash CM11, Gapps, boot, install Samsung Phone Info App, run app, look for the bootloader and modem version.

audit13 said:
Try flashing a stock 4.3 ROM from sammobile.com for your i747m.
If Odin fails when flashing aboot.mbn, it's probably because the 4.3 ROM you are trying to flash has an older bootloader that the one currently on your phone.
If flashing the 4.3 ROM via Odin fails, copy the latest CM11 ROM and the corresponding Gapps to your internal or external memory, flash the latest Philz Touch recovery for the d2lte via Odin, boot into recovery, flash CM11, Gapps, boot, install Samsung Phone Info App, run app, look for the bootloader and modem version.
Click to expand...
Click to collapse
I tried Philz and I can boot into recovery now Progress!
That being said the CM11 is stuck on the boot logo animation, tried re-installing as well as the CM Nightly same result.
Did full wipe etc still stuck.

Are you wiping the cache, system, and data before flashing CM11 for the d2lte? Are you running the latest version of Philz?
Try CM12 if CM11 doesn't work.

Samsung s3 odin problem

hey guys
im trying to update my s3 firmware from 4.1 to 4.3 using odin
i followed this guys tutorial
https://www.youtube.com/watch?v=eJkHx0zb-Bc
i literally have the exact same tech except i didnt start with 4.3, i started with 4.1
i used the odin to flash on the 4.3 thing, and when my phone restarted it showed an andoid robot with its chest open with blue circles and a blue progress bar
then after that just nothing. its completely black and no matter what i do it doesnt turn on or do anything
the only activity i can sense is that when i plug in the USB into the phone, the computer detects it
please help!!
heres the odin log thing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> NON-HLOS.bin
<ID:0/005> recovery.img
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> system.img.ext4
<ID:0/005> tz.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

You have the i747m or i747? Where did you get the 4.3 ROM?

audit13 said:
You have the i747m or i747? Where did you get the 4.3 ROM?
Click to expand...
Click to collapse
Im not sure how to determine that
i got the 4.3 ROM from the youtube guide
I747UCUEMJB_2024954_REV04_user_low_ship
this is the file

Does your computer detect the phone in device manager as "qusbload" or something similar? If it does, you will need to try and debrick your phone using a debrick image and an sd card (http://forum.xda-developers.com/showthread.php?t=2549068).
Were you running stock 4.1.1 before you flashed?
Under the battery is a label attached to the phone. What is the model #? Is your s3 from AT&T?

audit13 said:
Does your computer detect the phone in device manager as "qusbload" or something similar? If it does, you will need to try and debrick your phone using a debrick image and an sd card (http://forum.xda-developers.com/showthread.php?t=2549068).
Were you running stock 4.1.1 before you flashed?
Under the battery is a label attached to the phone. What is the model #? Is your s3 from AT&T?
Click to expand...
Click to collapse
SGH I474
it IS from At&t
i dont remeber specifically which version
but it WAS 4.1
yes it says
qusbload

The phone is bricked because something seems to have gone wrong during the flash process. Most likely, something to do with the bootloader.
I read the comments on YouTube and it looks like a few people hard bricked their phone using this method.
Your phone is probably hard bricked since it does not boot at all. I assume you tried pulling and re-inserting the battery and charging the battery.
A USB jig, Odin, or Kies will probably not help. You will have to try the debrick method I linked or have it repaired via jtag.

audit13 said:
The phone is bricked because something seems to have gone wrong during the flash process. Most likely, something to do with the bootloader.
I read the comments on YouTube and it looks like a few people hard bricked their phone using this method.
How is your phone detected in Windows device manager?
Click to expand...
Click to collapse
it says qusbload
which guide do you recommend following to update my firmware correctly?

You can try this: http://forum.xda-developers.com/showthread.php?t=2549068 or this: http://forum.xda-developers.com/showthread.php?t=2660566
I have never used a de-brick method because I have never had to de-brick an s3.
I found this on youtube: https://www.youtube.com/watch?v=-RTAbLBVfMI

audit13 said:
You can try this: http://forum.xda-developers.com/showthread.php?t=2549068
I have never used a de-brick method because I have never had to de-brick an s3.
Click to expand...
Click to collapse
Can you explain to me what you think happened?
i mean i thought you werent supposed to go from 4.3 to 4.1 i thought i was going up
also im asking how you UPgrade fro 4.1 to 4.3 correctly
Thanks

Did you confirm the bootloader on your phone before upgrading? Maybe the phone needed to have a particular bootloader before applying the update.
Some people did brick their phones according to the youtube comments. Also, it looks like the 4.3 file that was on xda has been pulled because of possible bricking.
Try the debrick method as it is the only choice available unless you want to pay and have it repaired via jtag.

audit13 said:
Did you confirm the bootloader on your phone before upgrading? Maybe the phone needed to have a particular bootloader before applying the update.
Some people did brick their phones according to the youtube comments. Also, it looks like the 4.3 file that was on xda has been pulled because of possible bricking.
Click to expand...
Click to collapse
i dont know what "confirming bootloader on phone before upgrading" means
ahhh im so lost, someone save me T_T
im reading the link you sent me but the its not organized well in a way i know what is i474m or i474

The i747 is the AT&T version of the s3. The i747m is the Canadian version of the s3.
You need debrick images for the AT&T i747.
Before flashing anything to the s3, it is important to know the bootloader version of your phone. If the bootloader on your phone before the flash was newer than the 4.3 mjb version you flashed, this will brick the phone.
The debrick threads can be confusing which is why it is important to read and understand how your phone works with its software components.
Follow the instructions for the AT&T i747.

audit13 said:
The i747 is the AT&T version of the s3. The i747m is the Canadian version of the s3.
You need debrick images for the AT&T i747.
Before flashing anything to the s3, it is important to know the bootloader version of your phone. If the bootloader on your phone before the flash was newer than the 4.3 mjb version you flashed, this will brick the phone.
The debrick threads can be confusing which is why it is important to read and understand how your phone works with its software components.
Follow the instructions for the AT&T i747.
Click to expand...
Click to collapse
so the debrick brought my phone back to download mode! yay!
next i have to put the 4.3 bootloaders, a 4.3 rom, a 4.3 kernel and a 4.3 modem
im not sure how i should do this

Find the tar version of mjb bootloader and mjb modem in the general section of this forum and flash them using Odin.
Bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
Then flash the latest TWRP custom recovery for the d2lte. Then flash the latest cm11 for your phone via TWRP.
This will hopefully get your phone up and running with a custom ROM.

audit13 said:
Find the tar version of mjb bootloader and mjb modem in the general section of this forum and flash them using Odin.
Bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
Then flash the latest TWRP custom recovery for the d2lte. Then flash the latest cm11 for your phone via TWRP.
This will hopefully get your phone up and running with a custom ROM.
Click to expand...
Click to collapse
im following the instructions for the link you gave me
im stuck on this step:
When I first got mine booting again it would only boot with the micro SD card that has the .IMG file on it in the phone and only after a battery pull. What I did was boot back to recovery, remove my SD card and I had a spare SD card I used to flash the files with, I inserted it told TWRP to mount the new SD card, flashed the bootloader again and it seems to have cured my phones malfunctions. It now boots on its own like nothing ever happened. It may not happen like this for you???
my phone wont boot without the debrick SD card.
im not sure what this is trying to tell me to do
whats your take on it?
also in recovery mode, there is a option for factory reset.
is factory reset going to help at all with this?

I would not think that a factory reset would help since it only wipes the data and cache partitions.
So everything works again? Sounds like it was a bootloader issue.

audit13 said:
I would not think that a factory reset would help since it only wipes the data and cache partitions.
So everything works again? Sounds like it was a bootloader issue.
Click to expand...
Click to collapse
hey so i did the phones software update in about devices and it put me up to 4.4.1 kitkat
so im where i want to be.
if i want to install cyanogen mod, do you think following this link is good?
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
Thanks for the help

The latest is 4.4.2.
The easiest way would be to install a custom recovery usi Odin, backup the existing rom, wipe cache, data, system, install cm and gapps.
Use ROMs for the d2lte.

audit13 said:
The latest is 4.4.2.
The easiest way would be to install a custom recovery usi Odin, backup the existing rom, wipe cache, data, system, install cm and gapps.
Use ROMs for the d2lte.
Click to expand...
Click to collapse
can you give me a reputable URL that shows me how to do this?

Hopefully, the links still work: http://forum.xda-developers.com/showpost.php?p=60813687&postcount=3

Upgrade to 6.0 help?

Hello all, I have not been on this site in a long time and was wondering if i can be pointed in the right direction to upgrade to 6.0? Currently, I am on OJ7 5.1 with hacker kernel, TWRP. I dont even know how many updates have been made since 0j7. I did find this, http://forum.xda-developers.com/sprint-galaxy-s6/general/sprint-galaxy-s6-sprint-mm-6-0-odin-t3333530 but will i just flash this and i'll be good? do i need to flash a different kernel, radio, etc? Also I am looking to try out a different kernel, so any suggestion would be great. thank you in advance.

Everything that you need (files, instructions) is here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862

koop1955 said:
Everything that you need (files, instructions) is here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks for the quick reply, finally just finished downloading all files needed, haha. Using my 4G hotspot. so just flash the PG3 tar and I'll be golden? No need to flash a separate kernel, or anything like that besides the recovery and Super Su?

P1_e85 said:
Thanks for the quick reply, finally just finished downloading all files needed, haha. Using my 4G hotspot. so just flash the PG3 tar and I'll be golden? No need to flash a separate kernel, or anything like that besides the recovery and Super Su?
Click to expand...
Click to collapse
It all depends on what you want. Flash the TAR in Odin, then BEFORE you root or install TWRP, take the update to PI3 if you like. (Some people have reported faster battery drain and it is only a minor security update, so decide what you want.) You'll be 6.01 either way.
Flash the CG-auto root file and then TWRP and you will have Root and Recovery.
Renegade is the only current ROM (even that is no longer supported) and SkyHigh the only kernel, but neither are really necessary. Look in the Android Development section and make up your own mind.

Well hopefully someone can help me, figured i'd ask in same thread first. The upgrade to 6.0 was successful also rooting and hotspot mod which was m main concern. but after all that was done I tried to flash Magisk v7, according to the thread it said to flash two files the v7 and phh zips. After that it would not boot up, just stuck on Samsung Galaxy S6 powered by android screen. I already tried to reflash 6.0 tar file but it gives error.
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any help much appreciated, I am still searching for a fix. As now i can still go into recovery and download mode, tried to restore a old 5.1 back up I had and same thing happens stuck at Samsung screen.

P1_e85 said:
Well hopefully someone can help me, figured i'd ask in same thread first. The upgrade to 6.0 was successful also rooting and hotspot mod which was m main concern. but after all that was done I tried to flash Magisk v7, according to the thread it said to flash two files the v7 and phh zips. After that it would not boot up, just stuck on Samsung Galaxy S6 powered by android screen. I already tried to reflash 6.0 tar file but it gives error.
any help much appreciated, I am still searching for a fix. As now i can still go into recovery and download mode, tried to restore a old 5.1 back up I had and same thing happens stuck at Samsung screen.
Click to expand...
Click to collapse
First thing to try, since you can get into recovery, is a factory reset.
Big note: After any version update (5.x to 6.x) never try to restore any earlier version.

koop1955 said:
First thing to try, since you can get into recovery, is a factory reset.
Big note: After any version update (5.x to 6.x) never try to restore any earlier version.
Click to expand...
Click to collapse
Already tried the factory reset, any advanced wipe maybe? I tried the restore after the wipe did nothing.

Try flashing the new PI3 TAR file here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862

koop1955 said:
Try flashing the new PI3 TAR file here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks after flashing multiple files and such and no luck I finally tried renegade rom and it booted. Yipee, not sure if i'm going to mess around a lot more haha, probably will though. Might try to flash back to stock touch wiz with the provided tar. and hopefully 7.0 comes for the s6. thenf or sure flashing that.