Some background here. My son has screwed up his phone.
S3 i747 AT&T
was rooted using Kingo Root.
No custom ROM.
He tried to update to 4.3 OTA a couple days ago. Now it will boot to the Galaxy SIII logo then go black. I can get to ODIN mode and stock recovery mode. I am just at a loss as to what to do next. Reading the forum has gotten a little overwhelming as to exactly what I need to do to get it back.
Can someone give me some instructions as to what to do?
If you need more info I will check this thread and provide it. As far as any specifics that can be found in the 'About phone' menu, I cannot remember what the specs were so that isnt possible for me to provide.
Thank you very much for any help.
First of all, don't panic. If you still have download mode and recovery working the phone is very fixable. Second of all, don't start flashing stuff willy-nilly. You have to be a little careful with this phone once it is on 4.3 and later firmware, and from what you've posted it is not entirely clear how far the update proceeded.
I don't think download mode or stock 3e recovery will tell you what firmware your phone is running, and it is important to know that before proceeding. Do you see anything about "warranty bit" when you're in download mode? If you see warranty bit then you successfully updated to a 4.3 (or higher) bootloader. Definitely don't try to use Odin to flash any full firmware updates if you see warranty bit in download mode. It would probably just fail, but if it actually proceeded it would attempt to downgrade the bootloader and hard brick the phone.
At this point, my recommendation is to use Odin to flash the latest TWRP recovery on the phone. Just in case, don't let the phone auto-reboot after flashing with Odin, uncheck everything but f.reset time in Odin. Upon success unplug the USB cable and pull the battery. Replace the battery and boot straight to recovery by pressing and holding vol up + home + power and releasing when you see the blue text in the upper left that says recovery booting.
Once up in TWRP go into Advanced -> Terminal and enter:
Code:
getprop ro.bootloader
Report back the output of that command here, and that will set what to flash next to fix the phone.
Another thing you can do with the phone booted in TWRP is connect it to a PC via USB and transfer files from the phone to the computer in case anything needs backed up. The PC should automatically mount the phone as a media device. It might end up being necessary to format the phone's internal storage to get it booting a ROM normally again, so this wouldn't be a bad pre-planning step.
How do I download the recovery file from the TWRP link you provided? I cant really tell how to download but I can see the file I need.
Here is what is displayed in Odin mode
Odin mode
Product name: sgh-i747
Current binary: custom
System status: custom
Qualcomm secureboot: enable
Warranty Bit: 1
Bootloader rp swrev: 3
peckaldee said:
Here is what is displayed in Odin mode
Odin mode
Product name: sgh-i747
Current binary: custom
System status: custom
Qualcomm secureboot: enable
Warranty Bit: 1
Bootloader rp swrev: 3
Click to expand...
Click to collapse
Since you see warranty bit, you're definitely on a 4.3+ bootloader. Do not download and try to flash the full firmware file from sammobile.com to restore the phone. It would either fail or or hard brick the phone if it did proceed due to attempting to downgrade the bootloader.
Download this TWRP https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar. Flash the tar file using the PDA menu from Odin. Most people recommend Odin 3.07 for use with this phone. If you've never used Odin before, you'll have to get the samsung USB drivers working on the PC too.
Get Odin and the samsung drivers from this thread if you need them.
It would be nice if you could just restore the phone using Odin, but AT&T never let a firmware past jellybean 4.1.1 be released. And since you now appear to be on a 4.3 bootloader you cannot downgrade.
I will try this when I get home from work in the morning and report back. Thanks for the detailed help!
jason2678 said:
Once up in TWRP go into Advanced -> Terminal and enter:
Code:
getprop ro.bootloader
Report back the output of that command here, and that will set what to flash next to fix the phone.
Click to expand...
Click to collapse
It outputs:
I747UCUFNJ2
I would like to flash this ROM if possible.
S3Rx 4.0 TouchWiz 4.4.2 UCUFNE4 (11-9-14) || UCUFNJ2 (10-04-15)
http://forum.xda-developers.com/gal...x-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080
peckaldee said:
I would like to flash this ROM if possible.
S3Rx 4.0 TouchWiz 4.4.2 UCUFNE4 (11-9-14) || UCUFNJ2 (10-04-15)
http://forum.xda-developers.com/gal...x-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080
Click to expand...
Click to collapse
That ROM should be a good choice. This is easiest if you have a microSD you can use with a PC adapter to store the ROM on, but it can be done without a microSD if need be. If you don't have a microSD you'll have to copy the ROM zip to the phone from PC via USB.
To get it running, first go into Wipe -> Advanced Wipe and tick Dalvik Cache, System, Data, and Cache and wipe them. Then go to Install, flash the ROM zip and reboot. Since you're coming from a stock ROM that should be all you have to do. First boot will be long, maybe 10 minutes or so.
Sometimes touchwiz ROMs are a bear to get to boot. If it hangs on boot for more than 15 or 20 minutes its not going to boot. Pull the battery and boot back into TWRP. Repeat the wipe of dalvik, system, data, and cache. Then go into Wipe -> Format Data and type "yes" to confirm formatting the internal storage. At this point you'll have to copy over your ROM zip again unless it is stored on an external microSD. Flash the ROM and reboot again. Usually formatting the internal storage is enough to get touchwiz ROMs to boot, but there are a few more tricks if it still hangs.
jason2678 said:
That ROM should be a good choice. This is easiest if you have a microSD you can use with a PC adapter to store the ROM on, but it can be done without a microSD if need be. If you don't have a microSD you'll have to copy the ROM zip to the phone from PC via USB.
To get it running, first go into Wipe -> Advanced Wipe and tick Dalvik Cache, System, Data, and Cache and wipe them. Then go to Install, flash the ROM zip and reboot. Since you're coming from a stock ROM that should be all you have to do. First boot will be long, maybe 10 minutes or so.
Sometimes touchwiz ROMs are a bear to get to boot. If it hangs on boot for more than 15 or 20 minutes its not going to boot. Pull the battery and boot back into TWRP. Repeat the wipe of dalvik, system, data, and cache. Then go into Wipe -> Format Data and type "yes" to confirm formatting the internal storage. At this point you'll have to copy over your ROM zip again unless it is stored on an external microSD. Flash the ROM and reboot again. Usually formatting the internal storage is enough to get touchwiz ROMs to boot, but there are a few more tricks if it still hangs.
Click to expand...
Click to collapse
Following that ROM thread is confusing. Not sure if I need to install the recommended bootloader in the first post of that thread. It mentions NJ1 but not NJ2. I assume my NJ2 will work since it is the newer version but I'm still unsure.
peckaldee said:
Following that ROM thread is confusing. Not sure if I need to install the recommended bootloader in the first post of that thread. It mentions NJ1 but not NJ2. I assume my NJ2 will work since it is the newer version but I'm still unsure.
Click to expand...
Click to collapse
At NJ2 you seem to have updated to the newest bootloader for the AT&T S3. Never ever try to downgrade it. You're stuck :silly:
enewman rebased his ROM to NJ2 shortly after it came out. Download this one https://www.androidfilehost.com/?fid=24052804347829298
That ROM is up and running. Cannot imagine how grateful I am for your help in this matter.
peckaldee said:
That ROM is up and running. Cannot imagine how grateful I am for your help in this matter.
Click to expand...
Click to collapse
No problem. Happy to help. Hope it works out well for you.
Related
About a year ago, I unlocked my phone to use it overseas. Recently, I intended to factory reset it and sell it as I go an upgrade, and upon factory resetting, I discovered it is now soft-bricked.
I can get to download mode, and my computer sees it when I connect it, but when I tried to "restore firmware" using Kies, it wen through all the motions but still gets stuck on the pulsing Samsung icon screen.
It's been awhile since I did any flashing with roms. Can someone recommend a method for how I'd flash my rom back to stock using Odin?
My download mode screen is currently showing:
ODIN MODE
Product Name: SGH-T999
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
Current Status: Custom
Qualcomm SecureBoot: Enable
Warranty Bit: 0
BootLoader AP SWREV: 1
Please go to recovery and then wipe cache and possibly Dalvik if its an option. See if that boots normal.
Post here otherwise. There are ways to restore stock but I want you to try the simple option first.
Perseus71 said:
Please go to recovery and then wipe cache and possibly Dalvik if its an option. See if that boots normal.
Post here otherwise. There are ways to restore stock but I want you to try the simple option first.
Click to expand...
Click to collapse
So went into Recovery Mode and it launched into TWRP2. I was able to wipe cache, but it would fail when I tried to specifically wipe Dalvik cache or do a factory reset. With the cache wiped, I am still stuck at the "pulsing Samsung logo" screen. What would be the next step?
I would flash it with a stock rom through TWRP
Potentially that's caused by secureboot. Please flash root66 firmware version UVUEMJC via Odin. After that, flash TWRP. Make sure to uncheck Auto-Reboot in Odin.
Once done, get into recovery, wipe dalvik and cache. Then boot.
WARNING - BE VERY SPECIFIC to choose UVUEMJC version. Any other version will give instant paperweight.
Perseus71 said:
Potentially that's caused by secureboot. Please flash root66 firmware version UVUEMJC via Odin. After that, flash TWRP. Make sure to uncheck Auto-Reboot in Odin.
Once done, get into recovery, wipe dalvik and cache. Then boot.
WARNING - BE VERY SPECIFIC to choose UVUEMJC version. Any other version will give instant paperweight.
Click to expand...
Click to collapse
OK awesome. So I flashed UVUEMJC via Odin and it now is operating as if it was factory reset, with all the prompts one receives when first starting the phone (google acct details, wifi password, etc.)
I have not continued on with flashing TWRP and then doing the wipes. Is this necessary? I intend to simply sell this phone now that it is operating correctly, and would prefer to not go down any further paths that couple possibly jeopardize the phone working. What are your thoughts?
@MentosMan
Yes I think it is safe to say you are all set. If you are really picky. you can connect to a PC in its current state and see if there are any photos on the internal SD card or anything in the download folder.
Perseus71 said:
@MentosMan
Yes I think it is safe to say you are all set. If you are really picky. you can connect to a PC in its current state and see if there are any photos on the internal SD card or anything in the download folder.
Click to expand...
Click to collapse
Perfect. Absolutely thanks for your help!
I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung
The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?
nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.
brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.
nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.
-Deleted-
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
rohanr014 said:
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
Click to expand...
Click to collapse
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Larry2999 said:
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Click to expand...
Click to collapse
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
rohanr014 said:
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
Click to expand...
Click to collapse
First you will need to download and extract the Odin tool. Odin is Samsung's tool for flashing (installing) firmware. You can download Odin v3.07 via the link below ...
http://www.mediafire.com/download/772dlmuaxfgm0x2/Odin307.zip
Once you have downloaded it, extract the files and look for the executable file (*.exe). That's the one you will need to run to open Odin.
We also need to identify the appropriate firmware to flash. You did not answer the earlier question on what Android version your device was on prior to flashing the custom firmware. This is important to let us know which official version you can safely revert to (4.1.1 or 4.3). If you were an older version than 4.3, you should flash 4.1.1 but if you were already on 4.3, then you should stick to this. Either way, you can download the 4.1.1 file via this link .. http://rapidgator.net/file/681a28a5...ATT_I747UCDLK3_I747ATTDLK3_Original.zip.html?
Download the files to your PC and extract.
To flash via Odin, open Odin.exe on your PC
Click on the PDA tab and navigate to the file you just extracted. Select the file ending in *.tar.md5 (For 4.1.1, this would be I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5). Make sure this file is showing in the PDA tab.
Boot your phone into download mode and connect to your computer with a good quality micro-USB cable. Make sure your phone is recognized by Odin. You should see the message Added in the left pane.
Do not check or uncheck any boxes other than the defaults.
Click on start and waiting for firmware flashing to end and you see Pass. Your phone will reboot at this stage. You can disconnect from your PC
However, for 4.3, it looks like the Odin flash-able file has been taken offline so you would need to this via custom recovery. That's a different process so please revert on your Android version first so we'll know whether this is required or not
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
rohanr014 said:
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
Click to expand...
Click to collapse
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Larry2999 said:
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Click to expand...
Click to collapse
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
rohanr014 said:
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
Click to expand...
Click to collapse
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
I have done everything you said, I flashed the TWRP file via Odin, and then i copied the stock zip file to my microSD and put it back into my phone.
I am able to boot into recovery, and everytime I go to flash the stock rom, midway through the flash my phone starts rebooting. Even if I try to clear dalvik cache and cache first, once they are cleared my phone automatically starts rebooting. What do I do now? The zip file is there and I can reach TWRP recovery, but the flash wont complete because my phone starts rebooting. I am at a 100% battery right now so I do not know what the cause of this could be. Please help, I cannot tell what I did wrong if I did do anything wrong.
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Larry2999 said:
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
Click to expand...
Click to collapse
Ok, something very strange has occured.
Since my phone would not flash the original stock rom, I decided to go ahead and flash CM10.2 and its gapps to see if it the problem was with my phone or with the file. Everything worked fine and my phone booted and ran CM10.2, but then I had absolutely no signal anywhere. I could confirm something was wrong because there were multiple AT&T users near me that had good signal. So then I went to flash the stock rom, and it worked. I cleared dalvik and cache like normal after all these flashes and performed factory resets, however when I flashed this stock rom, it worked but 1) I could not connect to Wifi 2) I could not use apps with root requirements, and Root Checker said I did not have root access, even though I had definitely rooted my phone earlier when I first ran CM11 and CM10.2
Should I root again? Please help, my phone is working and I can go into download, stock recovery, and normal mode.
audit13 said:
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Click to expand...
Click to collapse
The whole idea was to get your phone back to working state. Thereafter, you can build up on the food chain. The stock file you flashed restores the phone to near factory settings including a complete stock (official) firmware, stock recovery, resetting the flash counter. Unfortunately, it also removes root as well. You can, however, re-root in a number of ways. You may also do as Audit advised and reflash Philz Touch custom recovery which would allow you flash any custom ROM of your choice. You do not necessarily need to root to flash custom ROMs if you have custom recovery. However, if you need to use apps which require root, I would recommend you try SafeRoot (http://forum.xda-developers.com/showthread.php?t=2565758). Very easy to use and worked quite well for me.
Finally, you should be able to restore your Wi-Fi from settings. Wi-Fi setup should have happened during the set-up process upon reboot after the firmware installation but sometimes this step is skipped. If you go to Settings, you should be able to enable and set up Wi-Fi.
I apologize in advance if this is in the wrong thread or section, I'm new to this and am kind of stuck on what to do next. If it is in the wrong section can you let me know where to post?
I'm not sure what the previous version my phone was on but in the recovery menu I see KOT49H.I747UCUFNE4 so I assume it was 4.4.2
Over the weekend I tried to update my stock I747 (no root) through menus using check for update and when it completed my phone would no longer boot.
It gets stuck on the ATT logo and when I try to wipe it in recovery mode it still gets stuck on the same screen.
I have also tried to use Kies but the devise does not show up under the emergency recovery option even though my phone can connect to the computer.
However I have no problems connecting to Odin in download mode.
So what would be the best option for me if I dont want to root my device? Can I use Odin or should I be using a different program?
If I have to root should I follow enewman17 tutorial? If so what step should I start at?
Thanks!
Are you running a stock recovery? Did you wipe everything in recovery?
yep stock recovery, tried to wipe everything but i get the same problem.
If I were in your situation, I would install a custom recovery and custom rom such as cm10.2 to get the phone up and running to verify the bootloader and modem currently on the phone.
Should I be installing the recovery through odin or an sd card? Do you have a link for a tutorial, I've looked through t3chn0s1s's sticky but most instructions seem like they are for phones that can boot.
The method I see using an sd card needs a terminal but i don't think i can get one because I can't boot my phone, is that correct?
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Copy the latest CM10.2 or CM11 to your SD card. Place the SD card in the phone.
Flash Philz in the PDA section of Odin 3.07 and don't check anything except F.Reset Time. When you see "Reset" in the status window, disconnet the USB cable, pull the battery, replace the battery, boot into recovery, wipe cache, data, Dalvik, system, flash CM from the SD card, and reboot.
Thanks got it working last night!
If you want to run the latest CM11 or AOSP ROMs, you may have to update to the latest bootoader and modem.
I'm having a very hard time figuring which PAC-man ROM to download for my s3. I've got the thing rooted via towel root and have the free version of ROM manager, but don't know where to go from there. The model number is SAMSUNG-SGH-I747 if it matters.
There are hundreds of threads and post regarding loading roms... ill give you a quick run-down though....
First you need to find & flash a aftermarket recovery program.......(flash via odin) Team Win Recovery (TWRP) or Clockword Mod Recovery(CWMR) I personally like TWRP alot more, and there are a couple other ones, but those are probably the most common.
Once you do that, try booting into recovery mode.... ( turn phone off, then press volume up, power, and menu all at the same time, hold until you see the samsung logo and in top left you will see recovery booting, wait till this screen has past, then let go)
Once done, MAKE A BACK UP!!! Very important step and save it to where you will remember, i personally like to store it on my external SD card.
Load phone back up, download rom and recomended Gapps (google apps) onto computer, connect phone, and transfer onto the phone. (again i prefer to put on my external SD card)
Here is the pac-rom you want. ----> https://s.basketbuild.com/devs/pacman/d2lte/release - choose the .zip not the .zip.md5sum
you will have to look up what Gapps they recomend for their rom... i personally like PA Gapps.
Once loaded, turn phone off, boot to recovery, factory reset, wipe data/clear cache/dalvik cache. Install rom and specified gapps from location you saved on your phone.
I suggest your do a bit more research before you attempt so you are 100% sure you know what you are doing.... i did give a pretty thorough guideline but always double check!!!
Also, i have not tried using pacrom, so i dont know what its like, but i have tried around 4-5 roms and so far my favorite is dirty unicorns, here is the link for the newest stable rom. I am using PAGAPPS stock package with this rom.
https://www.androidfilehost.com/?fid=95784891001604479
I AM NOT RESPONSIBLE FOR DAMAGED PHONE FROM YOUR MIS-USE OR PERSONAL INJURY!
coyotefiveoh said:
First you need to find & flash a aftermarket recovery program.......(flash via odin) Team Win Recovery (TWRP) or Clockword Mod Recovery(CWMR) I personally like TWRP alot more, and there are a couple other ones, but those are probably the most common.
Click to expand...
Click to collapse
I've downloaded Odin but have no idea of what to do with it. As for TWRP, the download links appear to either be very well hidden or just down completely, and when I tried to install Clockword Mod Recovery via ROM manager, I get a message saying "unsupported device".
BlackGuyRX said:
I've downloaded Odin but have no idea of what to do with it. As for TWRP, the download links appear to either be very well hidden or just down completely, and when I tried to install Clockword Mod Recovery via ROM manager, I get a message saying "unsupported device".
Click to expand...
Click to collapse
http://teamw.in/project/twrp2
top right of screen it says "Get TWRP for your device"
find device and download to computer. Make sure you are running odin v3.09
turn phone off, boot into download mode. (volume down, power & menu all at same time)
open odin
plug into computer
odin will recognize
click pa and find TWRP file.
start and wait till odin says PASS!
Unplug and boot into recovery and continue as per previous instruction.
MAKE SURE TO MAKE A BACKUP WHEN IN TWRP!!!!!
If you still cant figure it out, do some more googling. its out there..... i learned how to do it last week for my first time and all i used was google.
again, i am not responsible for a damaged device from improper use and hold no liability what so ever.
coyotefiveoh said:
top right of screen it says "Get TWRP for your device"
find device and download to computer. Make sure you are running odin v3.09
turn phone off, boot into download mode. (volume down, power & menu all at same time)
open odin
plug into computer
odin will recognize
click pa and find TWRP file.
start and wait till odin says PASS!
Unplug and boot into recovery and continue as per previous instruction.
MAKE SURE TO MAKE A BACKUP WHEN IN TWRP!!!!!
If you still cant figure it out, do some more googling. its out there..... i learned how to do it last week for my first time and all i used was google.
again, i am not responsible for a damaged device from improper use and hold no liability what so ever.
Click to expand...
Click to collapse
I forgot to add, when I did find my device in that search bar and clicked on "direct download", I was taken here,( cant type URL, but it should say "/devs/s0updev/gooinsideme/") but there was nothing there so I clicked on "s0updev", but I'm not sure of where to go.
When I clicked on "Market Link", I got a message saying no app found.
Before flashing anything, you should determine which bootloader and modem version is on your phone.
If you run into problems installing the ROM, you need to know the bootloader and modem version on your phone when trying to get back to a stock or working ROM.
audit13 said:
Before flashing anything, you should determine which bootloader and modem version is on your phone.
Click to expand...
Click to collapse
How do I do that? Also, I'm going to purchase a sim card with a prepaid service for my phone. If I get it activated first, can I still add a custom rom later and not lose anything?
Sorry for asking so many questions, I just wanna be careful.
Is your phone sim unlocked? If not, I recommend unllocking it before installing a custom ROM.
To find out about your bootloader and modem, install the Samsung Phone Info app from the play store. Run it and it will tell you what you need to know.
audit13 said:
Is your phone sim unlocked? If not, I recommend unllocking it before installing a custom ROM.
Click to expand...
Click to collapse
The place where I bought it from claimed it was completely unlocked. I have no idea of how to check for myself other than a couple of shady payware apps on the playstore.
You can test it by trying a couple of sim cards in the phone. The sim cards do not need to be active and they should from two completely different carrier, rather than a carrier and its sub brand.
audit13 said:
You can test it by trying a couple of sim cards in the phone. The sim cards do not need to be active and they should from two completely different carrier, rather than a carrier and its sub brand.
Click to expand...
Click to collapse
OK, I've downloaded the Samsung edition of Phone INFO and found my Bootloader info, but have no idea of where the modem info is. Also, I went back to the store I bought the phone and had them test with an T-Mobile card, and confirmed the phone was unlocked.
Okay, after getting ClockworkMod Recovery successfully flashed, I think I'm finally close to getting this thing going after coming across two tutorials from teamandroid. ("How to Install Android 4.4.2 KitKat on AT&T Galaxy S3 SGH-I747 with PAC-man Custom Firmware" being one of them) I've run into another problem though-
TeamAndroid said:
Complete Step-By-Step Instructions:
Step 1 - Download PAC-man Android 4.4.2 ROM and Google Apps for Galaxy S3 to your computer.
Click to expand...
Click to collapse
The download link provided for the ROM is dead. I'm not sure of where to get the latest rom and the matching Google Apps download. If I can get these, I should finally get this thing installed.
There are great ROMs here: http://forum.xda-developers.com/galaxy-s3-att/development
In order to flash a custom ROM, boot into recovery, format system, Dalvik, data, and cache. Install ROM, install Gapps, done
audit13 said:
There are great ROMs here: http://forum.xda-developers.com/galaxy-s3-att/development
In order to flash a custom ROM, boot into recovery, format system, Dalvik, data, and cache. Install ROM, install Gapps, done
Click to expand...
Click to collapse
I'm going to install
[ROM][OFFICIAL][KitKat 4.4.4][d2lte] PAC-man 4.4.4.RC-1
Where can I find Gapps?
Gapps link here: http://forum.xda-developers.com/showthread.php?t=2015607
During the ROM install, I got an error and it aborted the installation-
What was the error? The phone needs to be running the latest Philz, CWM, or TWRP.
audit13 said:
What was the error? The phone needs to be running the latest Philz, CWM, or TWRP.
Click to expand...
Click to collapse
Formating system
Exracting system files...
Making symlinks
set_metadata_recursive: some changes failed
E: Error in /sdcard/pac_d2lte-RC-1-20140831.zip
(Status 7)
Installation aborted
I'm running CWM-based Recovery v5.5.0.4
Your recovery is too old.
audit13 said:
Your recovery is too old.
Click to expand...
Click to collapse
https://www.clockworkmod.com/rommanager
I found "Samsung Galaxy S3 (AT&T)- 6.0.4.7" Do I need to go back into download mode and flash this with Odin? Do I run the risk of bricking when powering off my phone since I already went trough these steps-
“wipe data/factory reset”
“wipe cache partition”
“wipe dalvik cache”