Hi, let me first begin if there is any problem with my threads. And I want to thank XDA for letting me ask this question, im pretty much a noob from the start..
So, I recently got a replacement S4 (surprisingly from a faulty device on swappa that had warranty) and it was already updated with 4.3 MK2, I have used chainfire's CF-Auto Root and have gotten root and also have installed a custom recovery (CWM.) My problem lies when I want to flash a Custom 4.3 Rom. I have downloaded HyperDrive RSL12 (Mostly because of the note 3 features) and the required files for it. But when I go into recovery and try to flash the rom, the recovery would take a couple of minutes to do something and then say that I can't flash this rom (I saw something under the line of "bad" but I have tried again and again to redownload the rom, so I honestly don't think thats the issue) but this happens to all of the roms I want to install, and I'm not sure if it has something with the KNOX bootloader that came with the phone, but honestly, any help I get is much appreciated! I would gladly give more info to who will help me and I would do almost everything to either install custom rom or 4.2.2 stock!
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm.....i mean that is a possibility, i'll try rerooting again, but say if the problem doesn't lie in rooting, what other problem would be associated this?
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
baseballfanz said:
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
Click to expand...
Click to collapse
I'll be honest,I have no knowledge about md5 in general, but normally would the mk2 bootloader prevent me from installing a modified stock 4.3 rom or a 4.3 custom rom in general?
Android_Monsters said:
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
LancerEvoDrifter said:
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
Click to expand...
Click to collapse
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
lordcheeto03 said:
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
Click to expand...
Click to collapse
I think I was using the newest version of TWRP. I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
LancerEvoDrifter said:
I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
Click to expand...
Click to collapse
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
LancerEvoDrifter said:
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
Click to expand...
Click to collapse
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
lordcheeto03 said:
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
Click to expand...
Click to collapse
yea, usually when I have a bad download, Winrar would tell me the archive had a unexpected end, but that is not the case in this situation, the file has worked on my dad's s4, but i guess the problem lies in my own device
Tried to delete but don't know how
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
Thanks for the info about using 2.5.0.2. I was finally to install a custom 4.2.2 ROM without a status 7 error.
David
Related
Whenever I try to flash it in TWRP, I get
updating partition details...
installing /sdcard/roms/cm-10.1.0-d2att.zip
checking for md5 file...
skipping md5check: no md5 file found
assert failed: getprop("ro.product.device") == "
E: error executing updater binary in zip "/sdcard/roms...
error flasing zip "sdcard/roms/cm10.1.0-d2att...
updating partition details...
YES, my bootloader is up to date according to http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716
YES, I wiped cache dalvik system
YES, i am rooted
Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm
It is because your recovery is saying you have a d2can recovery. Download Rom Manager from the market and flash the d2att recovery and then flashing it will not be an issue.
So I need CWM, not TWRP? Btw, I am sure that I got d2att cm.
mrhaley30705 said:
Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 I747M.
Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
Already tried that.
What he's saying is your recovery needs to match the version you dl'd, I think
mrhaley30705 said:
What he's saying is your recovery needs to match the version you dl'd, I think
Click to expand...
Click to collapse
Please provide me to the required links
Is it OK to install ATT CWM?
TimeAndroid said:
Is it OK to install ATT CWM?
Click to expand...
Click to collapse
Nvm, it worked. Please lock this thread!
could you tell me how that worked!!??
aleks1987 said:
could you tell me how that worked!!??
Click to expand...
Click to collapse
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^
TimeAndroid said:
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^
Click to expand...
Click to collapse
Ok thanks for the answer. I have a dout, i have i747m like you I think. I want to flash with d2att, Just Need the recovery for that rom?
You need root and recovery. If you have any problems, feel free to PM me.
Thanks let me try
Sent from my SGH-I747M using xda app-developers app
Oh Bummer
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?
Alias18 said:
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?
Click to expand...
Click to collapse
Not until we know what the error is.
Most likely out of date bootloader. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app
Got it!
KorGuy123 said:
Not until we know what the error is.
Most likely out of date toothpaste. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Somehow my US-Att S3 had the Canadian boot loader (or a slightly corrupt, or an outdated bootloader<--most likely). So I found another guy with the same issue. I went to this thread and re-installed my bootloader through ODIN. Found newer versions of them from here:
http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716
Hey guys im still new to this but one thing i did figure out is i am on 4.1.2 (i assume you guys are too) and the bootloader seems to not be compatible with CM 10.1 and i am in the progress of flashing back to 4.1.1 for the old bootloader in hope that it will work ill keep updated!
***EDIT*** I just flashed back to 4.1.1 and low and behold cm 10.1.2 worked like a charm so i guess Alias18 method would be easier and quicker not sure if theres anymore risks that way though. if anyone would like the 4.1.1 firmware with root injected let me know.
I'm trying to downgrade my i747 from CM11 back to stock AT&T firmware but I'm unable to. I've done hours of searching and reading posts, coming up with dead ends.. I'm hoping someone can point me in the right direction.
I can't seem to find an official original AT&T image, I did find a "rooted leaked" image.. but when I try to flash it with Oden it fails and the phone says "SW New Check Fail: Fused 2 > binary 0"
I ran the triangle away, tried a few different roms... I can re-image CM but not anything older. Is there a thread that explains where I can find the proper AT&T stock rom and roll back from CM11?
If you have the stock 4.3 bootloader, you cannot use Odin to flash a stock AT&T 4.3 ROM because AT&T never made a flashable 4.3 ROM available. AT&T only made 4.3 available as an OTA update to an existing ROM.
Thanks, so what are my options if any? I installed the CM11 through their http://get.cm site so I'm not sure what exactly they're doing but the end result is I have CM11, ODIN for the updater, and CWM. Can I downgrade to an older version then and just perform carrier updates to 4.3? If not is it safe to flash some other third party ROM? Or am I stuck on CM11?
-Keith
Boot into download mode and let us know what it says on the screen. This will help us determine if you have the 4.3 bootloader on your phone.
Download mode says:
ODIN MODE
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary: Custom
System Status: Official
Qualcom Secureboot: Enable
Warranty Bit: 1
Bootloader AP SWREV: 2
audit13 said:
Boot into download mode and let us know what it says on the screen. This will help us determine if you have the 4.3 bootloader on your phone.
Click to expand...
Click to collapse
I'm thinking of trying the approach that I found here:
http://forum.xda-developers.com/showthread.php?t=2658486
Unless any reason's why I shouldn't, it seems people have been successful with that pseudo 'stock' build.
Based on your download info screen, you have the 4.3 bootloader and the link you provided would be a good choice.
If you didn't have the 4.3 bootloader, you could have flashed a stock 4.1.1 ROM via Odin. With a 4.3 bootloader, you cannot use Odin.
I tried that link but the flash failed..
format() expects 3 args, got 5
E:Error in /external_sd/ATT_i747_UCUEMJB_StockRestore_CWM_2282014.zip
(Status 7)
Installation Aborted.
Ugh..
Status 7 errors can be caused by using an outdated recovery.
I have 6.0.4.7 installed and downloaded the ZIP that says it's for that version but I keep getting the same error.
Maybe the ROM download is corrupt?
kelkin said:
I have 6.0.4.7 installed and downloaded the ZIP that says it's for that version but I keep getting the same error.
Click to expand...
Click to collapse
Did you verify the MD5 of the zip you downloaded? I haven't seen any other report of this not working as it is the definitive solution for returning to stock 4.3.It's possible your download wasn't complete or, as Audit suggested, the zip was corrupted in some way.
I downloaded a different recovery as suggested and was able to flash that way. I'm finally back on the pseudo-stock AT&T firmware and aside from one strange popup everything seems to be working great. Thanks for the help everyone,
-Keith
Larry2999 said:
Did you verify the MD5 of the zip you downloaded? I haven't seen any other report of this not working as it is the definitive solution for returning to stock 4.3.It's possible your download wasn't complete or, as Audit suggested, the zip was corrupted in some way.
Click to expand...
Click to collapse
kelkin said:
I downloaded a different recovery as suggested and was able to flash that way. I'm finally back on the pseudo-stock AT&T firmware and aside from one strange popup everything seems to be working great. Thanks for the help everyone,
-Keith
Click to expand...
Click to collapse
Hey guys I am in pretty the same situation but I can't any other recovery to stick. I can flash and get the pass but it always boots back into cwm 6.0.3.6. Any ideas?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Hey guys I am in pretty the same situation but I can't any other recovery to stick. I can flash and get the pass but it always boots back into cwm 6.0.3.6. Any ideas?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you flashing via Odin or from CWM? Philz Touch can be flashed from either (i.e. the zip for flashing from an SD card and tar for Odin).
audit13 said:
Are you flashing via Odin or from CWM? Philz Touch can be flashed from either (i.e. the zip for flashing from an SD card and tar for Odin).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2824065
This is currently where im at and what I've tried.
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2824065
This is currently where im at and what I've tried.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I assume you can boot into download mode so use the latest tar version of Philz to flash recovery. Philz is based off the latest CWM.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Place the file in the PDA box, don't check anything except F.reset. Flash the file, once you see reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery.
audit13 said:
I assume you can boot into download mode so use the latest tar version of Philz to flash recovery. Philz is based off the latest CWM.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Place the file in the PDA box, don't check anything except F.reset. Flash the file, once you see reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery.
Click to expand...
Click to collapse
I tried this as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
I tried this as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're able to flash and you still don't have the right recovery? What do you see in the recovery screen? Is it the stock recovery?
audit13 said:
You're able to flash and you still don't have the right recovery? What do you see in the recovery screen? Is it the stock recovery?
Click to expand...
Click to collapse
No it's cwm 6.0.3.6, I tried every possible way, I think, of flashing a new recovery but it keeps loading back to this.
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Syst3m Deadlock said:
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Click to expand...
Click to collapse
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
BWolf56 said:
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
Click to expand...
Click to collapse
I have an S3 now, just havent updated my sig.
And I was trying to root. I was on the latest stock 4.4.2 and flashed the wrong file by mistake. Forgot what it was. So now I cant flash any files in recovery or odin. It just fails each and every time. I know all these files cant be bad
So root wasnt successful and now I cant even revert back to stock
Kies interferes with odin. Uninstall it from your computer and try odin again.
DocHoliday77 said:
Kies interferes with odin. Uninstall it from your computer and try odin again.
Click to expand...
Click to collapse
Still didnt work. Odin let me install a recovery file, but it just wont let me install files to restore back to stock. Same with recovery, I'm still getting the status 7 error. It doesnt make any sense. Ive downloaded and redownloaded from different places, so I highly doubt that all these files are bad
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
audit13 said:
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
Click to expand...
Click to collapse
I'm running 6.0.5 - no I haven't tried TWRP
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
DocHoliday77 said:
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
Click to expand...
Click to collapse
I was running official 4.4 unrooted. I'm trying to install Likewise S5.
Install terminal emulator from the play store and enter this:
getprop ro.bootloader
If it returns I747UCUEMJB you should be ok to flash likewise and something else is preventing it. If its anyway but that, you probably need to update your base firmware/bootloaders first.
If you're still unable to boot anything, the build should be shown on the Download Mode screen. You can probably reflash your previous rom and boot to that for right now though.
I was able to get a custom ROM installed, but now I have no reception. Im guessing the bootloader needs to be updated. So I tried updating it via odin. That failed. I also tried flashing it in recovery and still got a status 7 error. Im at my whits end here
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
DocHoliday77 said:
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
Click to expand...
Click to collapse
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Syst3m Deadlock said:
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Click to expand...
Click to collapse
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
BWolf56 said:
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
Click to expand...
Click to collapse
I cant seem to find the 1747UCUFNE4 baseband,
Syst3m Deadlock said:
I cant seem to find the 1747UCUFNE4 baseband,
Click to expand...
Click to collapse
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
BWolf56 said:
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
Click to expand...
Click to collapse
Thanks a bunch, it worked!!!
I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?
Follow one of enewman17's how to update threads in General.
4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks
bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse
jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse
jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse
jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse
jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse
Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk
[Firmware] [Odin] [Official] Firmware / Kernel / Modem / Recovery [M919UVUFOK3] TW 4.4.4
This is a Odin-flashable official firmware, kernel, modem & recovery for T-Mobile Samsung Galaxy 4 (M919)
How to install:
1. Extract the *.tar.md5 file using 7-Zip
2. Extract Odin v3.09 & open it
3. Reboot to Download Mode (press and hold Home + Power + Volume Down)
4. Connect phone and wait until you get a blue sign in Odin
5. Add the *.tar.md5 file to AP / PDA
6. Make sure re-partition is NOT ticked
7. Click the start button, sit back & wait a few minutes
Full Firmware:
https://www.androidfilehost.com/?fid=24338798368260486
Stock Kernel : Flash via Recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260505
Stock Recovery: Flash via Recovery, only needed if you want to go back to stock recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260507
Modem : ODIN Flashable
link removed as so many people are having issues with it
IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..
reilus said:
IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..
Click to expand...
Click to collapse
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk
a103 said:
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...
reilus said:
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...
Click to expand...
Click to collapse
You will need to flash TWRP first and then supersu.
Sent from my GT-I9505 using Tapatalk
Is the bootloader the same as the previous one?
Hmm....it looks like Xposed no longer works with this update. This is the error when you try to install it:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
Click to expand...
Click to collapse
Update: The Xposed_v2.6.1_by_SolarWarez_20151129.apk variant works with this release! Search for it on Google if the stock versions wouldn't run on your phone!
Arkain2K said:
Hmm....it looks like Xposed no longer works with this update.
Click to expand...
Click to collapse
Can anyone else confirm? Thanks
Sent from my SGH-M919 using XDA Free mobile app
Use the old Xposed Installer v2.6.1 with TW 4.4.4, and you can directly install the xposed framework within the app.
Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.
technut said:
Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.
Click to expand...
Click to collapse
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk
a103 said:
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I forgot to list that I did that also. For me at least this S4 was very stubborn to take on this flash. I was mostly posting so if anyone else ran into this so they wouldn't panic. All is well now though. It came around eventually.:good:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Sent from my SGH-M919 using Tapatalk
timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.
pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.
Click to expand...
Click to collapse
So it should be a fairly straightforward process? The issues technut experienced are unusual? Has anyone else installed and rooted using this ROM? Please report on how it went.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
a103 said:
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Click to expand...
Click to collapse
a103, when you say "flashed a custom ROM", do you mean a different ROM than the one in the OP of this thread? (since this one isn't really custom) If a different ROM, which did you flash? I didn't find many options that contained the OK3 firmware.
pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
Click to expand...
Click to collapse
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
I read in another place that the firmware contains the Modem so I wouldn't need to flash the modem in addition to the full firmware (M919UVUFOK3_M919TMBFOK3_TMB.zip). Is that true in this case? Does it include both modem and kernel?
Edit - After searching out how to open tar.md5 files I can now see that the full firmware does include the kernel and modem files. So installing that one should sufficient to update everything.
timg11 said:
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
Click to expand...
Click to collapse
Just flash the firmware, it has the kernel and modem in it.
Sent from my GT-I9505 using Tapatalk
a103 said:
Just flash the firmware, it has the kernel and modem in it.
Click to expand...
Click to collapse
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.
timg11 said:
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.
Click to expand...
Click to collapse
I didn't encounter any issues.
Sent from my GT-I9505 using Tapatalk