yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ali.haris:
help..

boss something went wrong with me i have sucessfully install 4.3 and then 4.4 but i dont install recovery.img nor root and restart it

then the phone stuck on att logo then i reinstalled 4.3 it started but showing no emei no or bandbase then i again try to do 4.4 again and also do double wipe but no result

and also boot loader of 4.3 is not flashing it is giving a error
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ali.haris:
conti

also i have made a backup with TWRP recovey of 4.1.2

is it possible that i can restore it back

currently im on 4.3

and I747UCUFNE4 bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Sorry but you kinda lost me there. Please explain exactly what you flashed and how. Most boot hangs just need a factory reset, and you probably flashed an old modem causing your unknown baseband and imei.

And please try to use punctuation. It makes things hard to read and correctly understand otherwise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ali.haris:
Sorry for punctuation english is not my first language

Here is the thing

Firstly I have made backups with titnium and twpr recovery then

I flashed 4.3 with odin. Everything was working till then then I install custom recovery and flash ota 4.4 update.

Here I missed the step nither I did root nor flash stock revcovery , also I didn't wipe and did a reboot.it stucked in the boot loop. After that I have again flashed 4.3 with odin and that's it no signal . Missing bandbase imei null :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
OK, sounds like when you got stuck during boot you probably just needed a factory reset.

For your current issue, I have a feeling you just need to flash the NE4 modem. But let's be absolutely sure first.

Install and open Terminal Emulator and enter this:

getprop ro.bootloader

This will tell you your base firmware version. Whatever it says, flash that same modem and your baseband and imei should return.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ali.haris:
Thanks

it was saying I747UCUFNE4

and its work thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloopingarfe:
I thought I followed the instructions.

So I tried to follow the instructions, and well I ****ed it up somewhere.

I checked the bootloader on my phone before I did anything and confirmed that I already have the MJB bootloader and I also had TWRP 2.6.3.0 so I didn't bother flashing 2.6.3.1.

I booted into recovery and went ahead and flashed the OTA.zip and SuperSU.zip and now it hangs on the ATT logo. I have also performed Factory Reset before flashing and after flashing.

I don't know where I would have gone wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Try flashing the stock rom. Enewman17 has a thread with it in the development section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pragnesh087:
phon is in dad condition after following steps 4....no response from phon

after takin steps 4 my phone is not able to switch on what i can do? my phone is totally in dad. no function please help to recover it........

As i have to explain how i am proceed?

As i did directly step 4 without any verification of baseband version. but i am sure about my android version is 4.3.while following step 4 i am getting pass massage and after that phone has restart but after some time i could not found any function on screen. phone is in totally dead condition.no power on or power indication on displey. please help to get it back my phone with previous version.

Thanks in advance..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Plug into a computer and open device manager. If you see QHSUSB_DLOAD, it's hard bricked.

Did step 3 flash ok?

If so, Go to the how to debrick thread in Q&A and follow the directions there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdogg21:
enewman17 do i need to unzip file and place MD5 file and in pda slot? I couldn't access the link you posted it would state user not logged in. I setup a user account with sammobile, However it still would not let download that file. This is the zip I downloaded. http://www.sammobile.com/firmwares/?page=1&model=SGH-I747&pcode=0#firmware
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Yes. Extract and then put the resulting .tar.md5 file in odins pda slot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdogg21:
Thank You sir appreciate the help

Sent From Phone From Somewhere
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
I've been having several issues with my Android 4.4.2 so I decided to go back to post #1 and start over. The installation of bootloader and OTA fails. I am now on Android 4.3 and it does not recognize the SIM Card. I think there is a mismatch between 4.3 and its baseband. Any suggestions on how to proceed would be much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
You cannot flash older firmware or it'll brick your device! If something wasn't working right you need to only reflash the stock rom.

Open terminal emulator and enter this

getprop ro.bootloader

If it says NE4, go flash the NE4 modem to get things working again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
Thanks a lot. It says NE4. I guess it's a carryover from prior 4.4.2 install.

I just installed the NE4 modem and I've got the phone back working again. I'm now running the NE4 modem with Android 4.3 firmware. At this point I'd like to go back to 4.4.2. Will that be possible and if so how?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdogg21:
Thanks

Thank You enewman17 and DocHoliday77 and any and everyone that contributed to this Thread Updated From Old 4.1.2 Thank You Thank You!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
You can flash the stock rom from here.

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

There are several other stock based ROMs you may be interested in as well in the Development section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
Thanks again. I attempted to flash this file from the link you provided and it failed?

I747UCUFNE4_Stock_Rooted_Odex.zip

I have attached my About Device screen. I just noticed, I can no longer turn on WiFi. I have the phone working, but without WiFi. Any suggestions much appreciated on how to proceed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
What was the error msg? Try again, but after it fails, go to the advanced menu and copy log to SD. Then attach the log here.

What recovery are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
Thanks for your response.

When attempting to install the zip file it fails and the screen says:

I've attached the log file (with extension changed to txt) as instructed. I'm using TWRP v2.8.0.1

Update: after reading the error message, I decided to copy the zip file to the intsdcard and flash it from there. It worked :) Thanks for all your help. It seems like I'm good to go although I don't understand why it wouldn't load from extsdcard.

2nd Update: I've installed Titanium Backup Pro and it claims not to be able to create a backup folder since it's not writable. I'm using the default location: storage/emulate/legacy/TitaniumBackup. I can write to the intsdcard in other ways such as taking screenshots so not sure why Titanium Backup Pro has a problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
No OS

hey , I had sgh-I747 on official 4.1.1 ( rooted ) , I followed this thread and I successfully updated to 4.4.2.

However , I recently had a problem and had to wipe data , and I removed all system data ( by fault ) , and now when I hit reboot system on the custom recovery it says no OS found.

I tried to reflash the 4.4.2 zip but It said FAILED.

can you help me please ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I think thats one of the seLinux issues.

Try installing selinux mode changer from the store and set to permissive. Then try again.

Try flashing a rom instead.

Stock ROMs here: http://xdaforums.com/showthread.php?t=2788357
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
what do you mean ?

can I install stock rom 4.1.1 through odin ? then refollow these steps ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
please a little help , I am stuck here .

I tried flashing stock 4.1.1 rom through odin but It failed again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Flash the stock rom in the link I posted. Flash in recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
thanks for the response :) after I wiped internal storage , IS my phone still on MJB bootloaders ?

another thing , can you please explain to me why flashing 4.1.1 through odin did not work ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I thought you said you updated to 4.4.2?

Factory resets/wiping data won't touch the system or firmware (bootloader).

You cannot flash older firmware or it'll brick. Odin protected you by failing when it didn't pass the sw rev check.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
Yes after following this thread I updated to 4.4.2 , then I accidentally wiped internal storage . I tried to flash stock 4.1.1 through odin but it failed.

So the firmware you gave me , it will work ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Just flash either the odexed or deodexed rom with recovery. Or you could try one of the custom ROMs base on the same build if you like. That's entirely up to you though.

Do not ever try to flash any firmware older than what you currently have. Only ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
thank you , hope this will work :)

in the thread you gave me it said :

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.

Do I have to follow step 3 ? thanks for your great help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Nope. You've fully updated to 4.4.2 firmware, which includes the bootloader. You can flash kt747 if you want, but its not a requirement. If you're interested in the kernel, check out its thread in original development.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
DocHolliday you're a life saver ! thank you so much :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
Is this a common problem or it's just me : the data connection is extremely slow (this is the reason why I tried to factory reset from the first place ).

another problem is that I cannot send pictures via whatsapp or viber ..

this is really weird.any help will be appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
AFAIK, the data issue isn't a common one. The other one I've not heard about before. You may want to ask in Q&A if you haven't already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackdragoon:
Disregard. Realized MJB modem was for i747. I have a i747m.

Boo-urns
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
If you want a way to update to 4.4.2 via recovery on the I747M, check here: http://xdaforums.com/showthread.php?t=2856914

(Finally got it working right! Thanks for your help [MENTION=2972841]enewman17[/MENTION]!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackdragoon:
Thanks. I was actually able to figure how to flash PA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davenrai:
[MENTION=2972841]enewman17[/MENTION]

This is a stupid question but

if I'm already on CWM with 4.3 MJB bootloaders and modem can I just dirty flash the OTA straight up?

Don't want to mess up. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rough company:
4.4.2 boot loaders

i have these loaders on my phone but my phone isnt booting up and i have no back up of my phone rom can i re-install this rom to restore my phone?i can get into recovery and download mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorey03:
im already rooted and running custom kit kat rom. i guess all i have to do is flash that zip in part 6 and then flash super su and im good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailindawg:
Quick question, has KNOX been removed from the OTA that enewman posted?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Benzmaffia:
Is this OTA a stock 4.4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
NO, you need to follow the instructions in the OP percisely. If your on a pure stock but rooted TouchWiz I747UCUEMJB 4.3 Jellybean you could skip to step six.

No, the only thing I did was modify the install script so it will bypass some checks so that it will flash. Knox and all the firmware hasn't been messed with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Its TouchWiz 4.4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chispas109:
In step 4 you mention to check box repartition, however i failed to check it and everything was successful. So is repartition a must? Do i have to re do it again or why does it have to be checked? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
If it worked for you then don't worry about it. The repartition will format and data reset, only reason I suggest is so everything is clean to eliminate any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jfishel:
I used the ODIN image to roll back to Stock 4.3, but then accepted the OTA update from the AT&T servers as it was detected immediately after booting the phone to 4.3. My warranty bit was previously tripped and the phone still installed the update as expected.

1. I'm having an issue flashing a custom recovery though. Unable to flash TWRP via Odin. See screen cap below:

Seems to flash ok, but when I try to boot into recovery, it is still the stock recovery.

2. Noticed the OTA flashes a new bootloader, haven't seen any mention of that yet in this thread yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evisser4:
Any idea if this will work with MJ2 bootloader?

And just to be clear, the end result is a full stock AT&T 4.4.2 Touchwiz Rom (NE4) with root and you retain custom recovery (TWRP). Am I understanding this correctly?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nehc_rm:
I was on Android 4.1.2 I747UCDMG2 and followed the instruction. It worked perfectly! my SAMSUNG-SGH-I747 is on Android 4.4.2 I747UCUFNE4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Warranty bit shouldn't have any effect on whether or not you can update. The important thing is Device Status. If it says custom it won't flash, unless its the modded ota of course!

When you update via ota, it includes two files, install-recovery.sh and recovery-from-boot.p. if these are present they will reinstall stock recovery at every boot. Either delete or rename before flashing recovery, or after the recovery flash, pull battery and boot directly to the custom recovery. It should them take care of that for you.

It should be already known if you are messing with this stuff that an ota will FULLY update your firmware. This includes bootloaders.

I doubt it will update MJ2 unless your rom, kernel and modem are all stock 4.3. And no this does not end with root or custom recovery. Full stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
I forgot about the install-recovery.sh.... Like Doc said it installs recovery on boot. So right after you flash recovery with Odin be ready to hold the button combo when it reboots it will boot into the recovery you just flashed. Then if you install Supersu "link for SuperSu 2.0 is in the op" it will disable the install-recovery.sh form installing the stock recovery. Now chainfire uses this install-recovery.sh in a very genius way. So every time you boot the kernel's init.rc executes that script and instead of installing recovery it loads the supersu daemon. For custom roms you can edit the install-recovery.sh with more script commands like "run-parts /system/etc/init.d/" now you can enable init.d without modifying the boot.img :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jooosty:
Perfect. Phone is now awesome

HTC M8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
I have an issue: my instagram feeds won't refresh and it force closes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jfishel:
276

Thanks for the info Doc and enewman. Happy flashing everyone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Hey all! I am back to try this again! I have started with enewman17's modded OTA, and modified it further. If this works as intended, it will update you to 4.4.2, but will preserve root and your current recovery, and will prevent it from overwriting your recovery with the stock one when you reboot.

As with my previous attempts, if it doesn't work, it should just fail before actually doing anything at all, so it should be perfectly safe to try. Let me know how it goes!

Samsung_SGH-I747_4.4.2_OTA_update-2.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TylerMarshall256:
For some reason since I updated. I can't seem to send MMS. I've went threw about 5 different APN'S. Am I the only one who is having this problem?I'm on Straight Talk too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Optomechanical:
I updated to 4.4.2 successfully using instructions in the op... Thank you enewman!

Can I re-perform the steps to get a clean 4.4.2 without bricking the phone? My concern is that using Odin to flash the 4.3 firmware is going to try to "downgrade" flash the MJB bootloader over the NE4 bootloader , causing bricks like when folks were trying to downgrade to 4.1.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
since your on the new bootloader no need to do it again. I suggest you make a nandroid of your set-up or I do have a completely stock odex Rom in the development thread that would be the same as trying to install this again. only thing that would be missing is stock recovery but I can make a flashable of that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bprewf:
i followed all these steps to the T, after the finalization of step 6, it told me update failed, so i rebooted to try again, and im now holding a brick that wont power on again. be weary, im pretty technologically savvy, and my phone is now absolutely dead not responding to any sort of power up combination. when i plug my phone into my pc usb cable, i get that notification the recovery program gives, but no power indicators on or screen. i can get it to react with noise when pressing the power button for longer than 7 seconds, but again, screen is totally dead along with not a power indicator at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
You just need the stock rom, flash in recovery. https://www.androidfilehost.com/?fid=23501681358550125
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ClevAndroidxx:
Just a little question i've been waiting to ask..

Ok, so ive been wanting to ask this.

I am thinking of installing this from a aosp custom rom; Is it even Possible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjacobs00:
My bootloader is ucalh9 and I can't flash over it using CWM or TWRP. I did the mod here a while ago which got me at ucalh9: http://xdaforums.com/showthread.php?t=1896773

How can I get my bootloader updated?

---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------

My bootloader is ucalh9 and I can't flash over it using CWM or TWRP. I did the mod here a while ago which got me at ucalh9.

How can I get my bootloader updated?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buck1952:
Remove encryption from 4.4.2 UCUFNE4

This worked great in removing encryption from S3Rx 4.0 - UCUFNE4.

Ran steps 3 through 5 and my data/media partition was no longer encrypted.

Had tried adb shell commands with no luck.

I started getting unable to connect to google servers and need to reload a clean S3Rx4

S3Rx 4 had been running fine with encryption. I think the google server issue was result of to many dirty flashes.

Thanks for the post, it’s a keeper.

Mike
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Razor1973:
enewman17, I was on the leaked MJ2 build which didn't allow me to find OTA upgrades to KitKat (since it had to me MJB) and ended up finding reply #4 to your original post after googling a little. Apparently, that's what your original post looked like, but you have since changed it, which I didn't realize until now.

I went ahead and got ODIN 3.10 (which seems to be the latest), downloaded "I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5.z ip" from step 4 of that reply, put my i747 in download mode and flashed successfully (with the attached options) on the first attempt. PASS. No problem. Except my phone won't wake up or show any sign of life. None. Looks like, somehow, I bricked it and my only possible solution will be a jig.

Any ideas? Can a successful ODIN flash of that file cause this?

EDIT: Just in case, I did go ahead and buy a jig on eBay and should have it in 3 days. Sucks. =\
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] befreewv:
Quick Question

Hi all. I'm new to the S3 world, but I've previously had a Samsung Cappy that I flashed with MIUI, DarkyROM, CM, and others, so I'm comfortable with rooting, Odin, flashing, etc. I now have an S3 (for about a year) that I updated to NE4 earlier this year (Feb/Mar?) using TWRP and the OTA update zip that was posted here in the AT&T XDA forums somewhere. I've kept stock 4.4.2 the entire time since. All was well until I decided to do a soft reset (using the reset option from the rom menu) on my phone because it was getting laggy. I decided to try the latest CM11 nightly build, but when I attempted the flash using CWM, the flash failed (didn't write down the reason provided), and the phone booted back into the stock ROM. Now, I've noticed a difference. TiBu will not work because the folder /storage/emulated/legacy/TitaniumBackup cannot be found and in fact it doesn't exist. I've used Root Checker to confirm root and I have SuperSU installed and updated. I've attempted to modify the platform.xml file (recommended in other places on XDA) but without success. I've tried to create the folder using ES File Explorer, but the operation always fails (no explanation provided by ES File Explorer). I've tried changing the TiBU backup location, but it states that the main file folder is not writeable. I've even used one of the apps from the Play store to fix the r/rw issue, but to no avail. I've also noticed that some other apps aren't acting quite right (Instagram pictures don't always load and it's constantly force closing; Tumblr pics never load.) I tried flashing the stock deodexed 4.4.2 from from the OP (success) but ran into a problem when I flashed the stock recovery zip using CWM (the CWM emblem came up and the swipe instructions appeared at the bottom, but then the install stopped and the phone rebooted).

So, what should I do? Given that CM11 failed to flash, I'm hesitant to try it again, even using the CM Installer. The phone and data still functions normally with the exception of those couple of apps that won't work. Do I need to go from 4.4.2 back to 4.3 and then update? Or do I need to try flashing 4.4.2 again? This is my main phone, so I want to avoid bricking it. I typically can figure things out on my own, but I'm stuck. Any insight would be greatly appreciated and I'm happy to provide any info that might be helpful to a dev to figure this out. Many, many thanks