yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KennyG123:
Thanks for this! I had rooted stock 4.3 and did step 6 and 7 with CWM...I got a lot of unknown command errors but it seemed to work and only needed to install Supersu from Play as it seemed to not install from step 7. But I see no problems other than my green battery is now white..lol, but setup and data is intact! Nice job!

This is the work phone they gave me so thanks for making it easy this time...that whole Odin in 4.3 last time was a PITA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Just so ypu guys know, Towelroot does work on the NE4 firmware. Its much easier than any other root method I've ever seen. I believe it is also safer since you don't have to flash anything. It should also allow rooting without tripping the Warranty Bit. (I can't remember for sure about that though).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cadizftp:
brick

step 4 bricked my phone odin said it all passed is there a way to wake it up. phone is totally unresponsive no life of any kind with buttons

<ID:0/004> 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/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> boot.img

<ID:0/004> NAND Write Start!!

<ID:0/004> cache.img.ext4

<ID:0/004> NON-HLOS.bin

<ID:0/004> recovery.img

<ID:0/004> rpm.mbn

<ID:0/004> sbl1.mbn

<ID:0/004> sbl2.mbn

<ID:0/004> sbl3.mbn

<ID:0/004> system.img.ext4

<ID:0/004> tz.mbn

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Removed!!

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

box said pass
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerokewl22:
Wifi ?

Will flashing the Kernel fix the Wifi problem? The original procedure everything works great but the WiFi.

Thanks....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Did you skip checking your bootloader version? I also assume you skipped step 3. The tar file is not official and will only restore and is not meant to update. You had to update your bootloader prior to installing the tar, that is why it was the step before flashing the tar.

All is not lost. look for the debrick guide in the Q&A section if you can boot into download mode and flash recovery via odin then you can flash one of these to restore your bootloaders.

if you use a 4.3 debrick image flash this. http://www.androidfilehost.com/?fid=23269279319197285

if you use a 4.4.2 debrick image flash this. http://www.androidfilehost.com/?fid=23578570567720263
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cadizftp:
Well this is why I went to step "If your already on MJB bootloaders continue to step 4"

I was running task650 4.4.4 I know I missed something an I read like 8 times to me 2 hours to decide to do it.the phone booted for about 3 seconds then was black never came on. only life it has is when i remove battery and hook up charger red ligh

The files above are not image files and I cannot boot phone into anything. I found a debrick.img which doesnt work yet But i will work on has be be something on here just take a while to find it thanks for the fast reply
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Running a custom room doesn't guarantee you that you have the latest bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cadizftp:
Hope I didn't sound like I was blaming anyone I was the only one here and I done it all, missed read something and well here I am.

Debrick images don't seem to work and now not even sure which one to use. I do have a nan back up. At least I have a upgrade coming Tuesday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cadizftp:
ok i used the debrick256.img and now it is in android system recovery <3e>. I have only a guess what to do now.do need some help.

One thing i need to know is this img for 4.3 or 4.4

PS I got it booting on its on with the ota 4.4.2 zip not sure yet what it is had a error in system install unknown command but it still installed and is running and wifi seems to work 4.4.2 baseband i747UCUFNE4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wigglebit:
Kudos on your excellent work [MENTION=2972841]enewman17[/MENTION]. I'm a noob to Android but not Linux so you don't have to hold my hand too tightly.

My question concerns step 7. What am I supposed to do with the SuperSU zip? Flash it from recovery? This would mean it needs to be on the external card, right?

I was comparing your modified 4.4.2 OTA to the one I downloaded from AT&T. I notice that you removed a bunch of sha1 checks. Is that prudent?

Thanks for starting this thread,

Wigglebit

---------- Post added at 12:27 PM ---------- Previous post was at 11:29 AM ----------

From my own experience the update failed because a sha1 check sum failed on a file. One of the bad files was /system/bin/ddexe. SuperSU messes with this. The other file was /system/bin/kiesexec which gets messed with by Triangle Away for some reason. The original files are there, just renamed. I didn't try uninstalling SuperSU or TA to see if that helped. I just replaced the files with their originals.

BTW I was able to see these errors while installing from stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Benzmaffia:
Thanks for the instructions.

But I followed through to step 3

then did a one click root (towel root) then installed supersu

Then use twrp to install ota and that's it.

Was having trouble with step 4 So I skipped it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SSJ_Gomike:
Ok, I just tried this on my son's s3 and I got the same result as you. I did skip step 3 as I'm sure I had the correct bootloader.

How did you save yours??? Mine is completely unresponsive as yours was.

Thanks.

---------- Post added at 08:55 PM ---------- Previous post was at 08:51 PM ----------

I just tried connecting charger to phone with battery out and I get the red light too. So whatever happened to your phone, happened to mine. I'm still trying to wake it with no luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
You cannot flash an ota if you are running a custom rom. Step 4 restores your system partition to stock MJB, which is the ONLY way you can flash the ota.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psi1978:
Bricked my phone...Help please...

Dear XDA-developers,

After having done step 6, I rebooted my phone (I747 AT&T) and it became bricked. Does not respond to anything.

I tried to debrick with SD card with the debrick images provided by enewman17, but the phone does not boot into recovery or download mode. It keeps trying to boot on its own and never passes Samsung Galaxy S3 logo.

Please help! Thank you in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Factory resetting should fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cadizftp:
at&t debrick images

It took me 12 hours using different debrick images before I found one that worked. I also noticed I had to repartition the sd card on each different image back to fat32 (this might be optional)I used a 32g sandisk sd. Enewman17 has files I used here and one did work for me.I used minitool partition wizard home edition and win32diskimager. After that i used towelroot to root the sd and rebooted and installed supersu and then rom manger then recovery then the file enewman17 said to use earlier.

PSI did swap the sd card after the phone booted up to install the apps had all my apps on sd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I think I misread this before. If you see anything on the screen, its not hard bricked. But what you're describing sounds like the power button gone bad.

Remove and replace battery. If it tries to turn on by itself, its the power button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psi1978:
No, it's not power button. My phone does not turn on without SD card with debrick image on it. The power button still works if I put SD card with debrick image in it. The problem is I cannot boot into recovery or download mode.

Thank you anyways for your help.

---------- Post added at 03:25 AM ---------- Previous post was at 03:17 AM ----------

Which one of the Enewman17's files worked for you? If I partition into 16GB (I am using 32GB SD card), flashing debrick image just destroys the partition. Do you mean I should repartition, after writing image to it? Just in case, I bought a new 16GB SD card. The problem is I cannot boot into recovery or download mode. If I cannot do that, I cannot do any of root/spersu/rom thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psi1978:
Another question: should I use debrick image from 4.3 or 4.4.2? Since I was on 4.3 (I flashed 4.3 bootloader in step3) before I flashed the 4.4.2 OTA (step 6), should I use 4.3

or should I use 4.4.2 because I already flashed 4.4.2 OTA(step 6)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
lol! Sorry about that! Im not going to read the post again or I might interpret it differently yet again!

If you attempted the ota and it ran through partially before failing, or if it fully updated, you will need the 4.4.2 image most likely. (Won't hurt to try 4.3 first if you wish, but it may not work.)

If the ota failed w/o doing anything, either one should do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RayEdmondson:
Just to verify before I try this. I have the correct bootloader and am running stock 4.3. I only need to do steps 2 & 6?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Are you absolutely certain you are using MJB firmware/bootloader/modem? And you are running a full stock build, never rooted, nodded, debloated etc?

If so, that would probably be ok. Personally, I think everyone should follow each and every step though. Its the safest possible way. It seems quite a few who tried to take shortcuts have ended up with some major problems recently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RayEdmondson:
I had to send the phone to Mobile Tech Videos to have it returned to stock after I bricked it. Now, though, it won't install the OTA update. Still debating whether or not to do it myself, but if I do I'll follow steps 1-6. Thanks for the advice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cadizftp:
debrick256.img Here you write the file to sd then place it in your phone see if it starts up might be automatic you might have to press the power button if it doesn't work then you have repartition the sd card back to fat32 in order to write another image to the sd card till you find one that works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RayEdmondson:
Had not problem with downloading and installing the 4.3. However, I downloaded the 4.4.2 and TWRP keeps telling me failed to find md5. I downloaded and copied the zip file from my computer to my SD card and tried the install from it. Should I download on my phone and attempt to install it that way?

---------- Post added at 09:40 PM ---------- Previous post was at 09:30 PM ----------

Seems to be working, so far. I'll let you know if I created an expensive paperweight or not. lol

---------- Post added at 09:49 PM ---------- Previous post was at 09:40 PM ----------

SUCCESS!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yhenks:
Excellent

This was very easy to follow. Had a bad flash thru Odin with JB on the first try (phone wouldn't boot past the at&t logo) but on the second try, it was perfect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
Same exact experience here too. Came from 4.2.2 AOKP on DLK3, and I used Clockworkmod recovery in place of TWRP no problem. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Martin Neil:
Hello !

I'm having a problem with my phone right now and i hope that you can help me.

I acccidentally deleted system and data using twrp and now my phone wont continue to boot. It is stocked on the samsung galaxy s3 logo

I used this rom a month ago and it is working perfectly well.

Anything that i can do so i can fix this problem?

Im using Samsung Galaxy S3 SGH-i747

I will appreciate any response that you can give me.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Martin Neil:
Im wondering if i can follow this process if im already on this kitkat rom.

can i dowgrade back to 4.3 and downgrade my bootloader as well so i can make my phone work since i accidentally wiped my system in TWRP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Don't do it... Downgrading bootloaders will cause a brick. Just flash the stock ne4 Rom I have in the development thread. http://xdaforums.com/showthread.php?t=2788357

[ROM] I747UCUFNE4_AT&T 4.4.2 Stock ROM & System Dump
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Martin Neil:
Thanks Man

One question, Do i need to follow all this steps and download all the file here:

Prerequisites include a minimum of a 4.3 bootloader and modem.

If you are not on the official 4.4.2 bootloaders and modem then you will need to flash ktoonsez kernel. http://xdaforums.com/show....php?t=1756776

Directions:

1. Factory data reset

2. Flash ROM

3. If your still on 4.3 bootloader flash ktoonsez kernel immediately after the rom.

4. Let phone boot up, go through start up etc...

5. Open SuperSU, Let it disable Knox. If it gets stuck, press the home button and reboot the phone and try it again. It will work the 2nd time.

6. Nothing else to see here.

Flash in custom recovery.

Stock Odex

http://www.androidfilehost.com/?fid=23501681358550126

Stock Deodex

http://www.androidfilehost.com/?fid=23501681358550125

Stock Kernel, insecure, init.d, sdcard R/W, selinux permissive

http://www.mediafire.com/?oooglrsrna0vony

I747UCUFNE4 debrick.img

http://www.androidfilehost.com/?fid=23501681358549813
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
If you had previously updated to 4.4.2, just flash the rom and disable knox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ccsanchezg:
Help!!

Hey guys I had the same problem as moporoco, i just want to know the exact steps for doing the extSD card debrick, thanks in advance, I really need my phone back as I start a new semester this week
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
There's a thread dedicated for debricking in Q&A
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ccsanchezg:
Hi Doc, mind sending me the link?, I found one that didn't help at all. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
This is the one I was referring to.

http://xdaforums.com/showthread.php?t=2549068

You should be able to restore functionality using the 4.3 debrick.img.

To be certain this will work though, plug into the computer as-is and open device manager. If it shows as QHSUSB_DLOAD, its hard bricked and the solution in that thread should work.

Just don't give up if it doesn't work the first time. Many, including myself, had to run through the process several times before it worked. Also try different sd cards if available. The main requirement is it must be at least 16gb. Preferred to be class 6 or better. I have seen class 4 work though. Also, its no guarantee, but I personally believe the better the card quality the better the chance of it working. I prefer Samsung, Kingston and Transcend, but others, even generics have worked before.

If you need further help with it though, please post in that thread. We don't want to take this one off track and there are already too many individual debrick threads. (It makes a lot of extra and recent information hard to find). Finally, good luck!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Martin Neil:
Do i need to flash all of this 4 at the same time?

Flash in custom recovery.

Stock Odex

http://www.androidfilehost.com/?fid=23501681358550126

Stock Deodex

http://www.androidfilehost.com/?fid=23501681358550125

Stock Kernel, insecure, init.d, sdcard R/W, selinux permissive

http://www.mediafire.com/?oooglrsrna0vony

I747UCUFNE4 debrick.img

http://www.androidfilehost.com/?fid=23501681358549813
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
If you are already on the 4.4.2 firmware/bootloader, just flash the rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liujeffqi:
i am stuck on this step i am not sure what to do

how do i flash the bootloader though the recovery?

i see "Install, wipe, backup, restore, mount, setting , advanced, reboot" which one i choose?

i chooses the install tab but only sees the super user 2.0 update nothing else i don't see the d2att_I747UCUEMJB_bootloader_modem_4.3.zip file even i have put it in my sd card

ps i am currently in 4.1.1

never mind it is dumb of me, i keep searching in SDcard folder while i should search external_sdcard folder problem solved
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Its in the same folder as superSU and its not showing up? Did you check the md5 on the download? Maybe it was corrupted. Try unmounting/re-mounting the sd card too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liujeffqi:
thanks man, i was dumb enough search in the wrong folder. i search in SDcard folder which is really my phone HD, I should have look into external_sdcard. now i got my 4.4.2 yay...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jhutch825:
**Nevermind** my internet at work sucked, just a corrupt download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SGTDude:
I'm charging up my phone in preparation to take the plunge. I'm currently running CM11 M9, and it's encrypted. Because of this, I'm going to go ahead and reformat /data and do a "factory reset" (wipe data, cache, dalvik) to try to get my phone as close to "normal" as possible before starting.

Here's what my phone says:

dude@d2att:/storage/emulated/legacy # su
root@d2att:/storage/emulated/legacy # getprop ro.bootloader
I747UCUEMJB
root@d2att:/storage/emulated/legacy #
root@d2att:/storage/emulated/legacy # getprop | grep I747
[gsm.version.baseband]: [I747UCUEMJB]
[ril.product_code]: [SGH2I747MBBATT]
[ril.sw_ver]: [I747UCUEMJB]
[ro.boot.bootloader]: [I747UCUEMJB]
[ro.bootloader]: [I747UCUEMJB]
[ro.build.description]: [d2uc-user 4.3 JSS15J I747UCUEMJB release-keys]
[ro.build.fingerprint]: [samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB:user/release-keys]
[ro.product.model]: [SAMSUNG-SGH-I747]
root@d2att:/storage/emulated/legacy # getprop | grep NE4
1|root@d2att:/storage/emulated/legacy #

So it looks like everything is MJB, and there's no sign of any NE4 nastiness (yet).

From what I can tell, this is true for me, but I've seen several people skip steps and end up with bricks. I know attempting to downgrade a bootloader will brick, but if I flash MJB over MJB...

Has anyone heard of bricking a phone by flashing a MJB bootloader on a phone that's already on MJB? If it sounds safe, I'll go ahead and follow every single step. It sounds like following all the steps is more likely to work than skipping some, right?

P.S. My job requires that I encrypt my phone. Has anyone successfully rooted, then encrypted this TW 4.4.2 system? If no one's tried, I'll be happy to post my results, but if someone's tried and failed, I may as well stick with CM11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
You can safely flash the same as your current build.

Havent heard about anyone trying encryption on kk yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SGTDude:
Ok, followed the instructions precisely, and got my phone updated to TouchWiz KitKat 4.4.2. :)

Encryption doesn't work... From what I remember, it's doing the same thing it did to me on 4.3. It thinks about encrypting (I get the green wireframe Android Man for about 10 minutes), then it reboots and all I have is a pin/password lock, no encryption...

I tried loading the Samsung recovery (Thanks, BTW), and that didn't fix it.

I tried factory-resetting from Samsung's recovery (which should get rid of root, right?), and that didn't fix it either.

As far as I know, this is the closest I can get it to a "virgin" state. I think the fact that Knox has been tripped is what's preventing it from encrypting (or rather the script that encrypts the phone checks for Knox first...)

I really wanted MHL and the HDR camera to work, but I guess I'll have to go back to CM11. :(

Thanks for posting though, everyone. I'm sad that I can't stay on this ROM, but my phone's not bricked or anything, so I can't really complain too much.

UPDATE: I found an app called "Divider" in the play store, and that took care of my corporate e-mail issue.

I can't get my HDMI/MHL cable to work on this phone, though. The cable is working fine on a Sprint Galaxy S III on stock 4.4.2, though, so I'm pretty sure it's my phone. Has anyone gotten an HDMI / MHL cable to work on this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
I know this has probably been beaten to death, but I just want to ask it in my own words to be 100% sure. I'm about to sell my phone in a month or so when the new note 4 comes out, want to revert to stock 4.4.2 before it (no root). Once upon a time I had stock 4.3, but have flashed numerous custom ROMs since then, so I am on MJB bootloaders and I'm guessing MJB modem. So starting from step 4 in the OP is the correct path right? Also, is there step where triangle away could be used to set the counter back to 0? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
That should be ok, but if you are not absolutely 100% certain you are fully running MJB firmware, start from the beginning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chivas1311:
Is it safe to update my device? is the i747M with bootloader I747MUMUEND3 from Telcel, Mexico.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Not with this thread. Its for the I747 only, not the I747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RAFELO1:
brick my i747

I brick my s3 i747 after i flashed Flash stock tar file( I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5).. i was on 4.0.4... what i can do???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
If its hard bricked, go to the debrick thread in Q&A. If soft bricked, factory reset. 4.0.4 to 4.3 is a pretty good jump so id expect theres data from before that is incompatible with the newer build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chivas1311:
Thanks for responding. There a Stock ROM which I can update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
check http://sammobile.com/firmwares
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Great guide, worked perfect, thanks. Man is Android System destroying my battery :eek: It's taking up more battery than my screen time. Hope this isn't going to be a problem when I upgrade my phone next month. Guess I'll probably ending up rooting anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Some people reported battery life significantly improving after a few cycles. If it doesnt, consider factory resetting and only restoring essential data. Start clean with everything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
That's good to know, I guess I'll see what happens. I actually factory resetted immediately after I upgraded anyway, started from a clean slate. On Pwns 4.4.4 ROMS I was getting maybe 5 or 6% Android OS, now I'm at 20%. Disabled as much bloat as I could too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juni1:
restore to 4.3

sir ,plz guide me here,I updated my s3 using ur method above to 4.4.2 and worked fine except battery drain.So my bootloader was updated to latest kitkat ver.When i restored again to 4.3 tar it did not read my sim.so kindly tell me some method to restore fully to 4,3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
You can only flash the rom. You cannot downgrade firmware