Related
I've been reading these forums in my spare time for the last week or so but I'm still a bit confused or just overlooking something. According to the CM 10.1 thread install instructions are
Install instructions:
1. Install ClockworkMod Recovery for "I927". Sorry, CM cannot provide support for other recoveries, although they may work fine.
3. Reboot into recovery and install
Click to expand...
Click to collapse
and a few people in some of the guide threads have basically stated the same. Is it really this simple now or do I still need to follow the guide from a year ago or the one in this thread http://forum.xda-developers.com/showthread.php?t=1962633 ?
So far all I have done is install CWMR Touch 6.0.1.2 Recovery and run backup in both blob and tar formats. Actually does this even work properly without rooting first?
You don't need root, but you can't quite go straight either. The current SOP is:
Flash TW-ICS, meaning UCLG9 or UCLH2 or UCLJ3, using the respective OneClick
Flash CWMR using Odin (the previous step overwrites recovery so you will have to do this again even if you flashed CWM previously)
Boot into CWM
Flash your AOSP-JB ROM of choice
Flash the correct gapps for your ROM
Format /data (aka factory reset)
Reboot into ROM and enjoy
Step 1 may or may not be necessary -- nobody's tried going from TW-GB straight to AOSP-JB yet. If you're feeling adventurous, try it and let us know how it goes.
Once you've flashed a TW-ICS once, you won't need to do it again -- at that point flashing a new TW-ICS or AOSP-JB ROM is as simple as flash-format-boot.
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
Nope no zips or Odin just use one click the first time. So for step 1 above follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/. Can't get easier then this.
Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
Click to expand...
Click to collapse
TW == TouchWiz. Basically official Samsung stuff and ROMs based directly on such.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
Click to expand...
Click to collapse
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Bram Skull said:
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Click to expand...
Click to collapse
I just took a peek... ooh. Looks like pretty much everything is in there. You should be good.
*Question aswered *
Hi, am I the only one to be really confused about this new bootloader thing that we need to flash certains roms? Theres is no guide at all on our T999(v) to explain what
-are the benefits to install this R: Install newer CM and AOSP Roms without random reboots and to actually boot them
-how to install it R: Follow the guide on the link providen in this post below
-what are the risk R: If you dont instal the right bootloader for the right device = brick. But the proccess is the same to flash a ROM
-is there any issues known with this bootloader R: Still waiting
-can we flash old roms that worked on the old bootloader on this one R: YES !
-how do we know if we need the new bootloader before flashing a rom. R: Open a terminal emulator and run those commands : su *enter*
getpro ro.bootloader And check if you have the newest booloader referred to the guide on the link below
As you can see all those questions are not really understood from our T999(v) forum. I've researched on the forum for any information and I've found only this guy that provide MD5 bootloader with a few instructions http://forum.xda-developers.com/showthread.php?t=2282603 but really this is confusing. I do not want to make a fatal mistake and brick my S3 so this is why i'm asking all those questions to you guys. For info I own the SGT-T999v.
kruse1944 said:
Hi, am I the only one to be really confused about this new bootloader thing that we need to flash certains roms? Theres is no guide at all on our T999(v) to explain what
-are the benefits to install this
-how to install it
-what are the risk
-is there any issues known with this bootloader
-can we flash old roms that worked on the old bootloader on this one
-how do we know if we need the new bootloader before flashing a rom.
As you can see all those questions are not really understood from our T999(v) forum. I've researched on the forum for any information and I've found only this guy that provide MD5 bootloader with a few instructions http://forum.xda-developers.com/showthread.php?t=2282603 but really this is confusing. I do not want to make a fatal mistake and brick my S3 so this is why i'm asking all those questions to you guys. For info I own the SGT-T999v.
Click to expand...
Click to collapse
In the thread you linked, there is a T999v link. So you'll want to take that. Do not flash our bootloader on your phone. Must be T999v bootloader.
We don't have access to a changelog. Need to do it to flash newer AOSP ROMs. Why? Because the older ones were causing rebooting issues.
There is no risk as long as you get the bootloader for your device.
You can flash old ROMs.
Aerowinder said:
In the thread you linked, there is a T999v link. So you'll want to take that. Do not flash our bootloader on your phone. Must be T999v bootloader.
We don't have access to a changelog. Need to do it to flash newer AOSP ROMs. Why? Because the older ones were causing rebooting issues.
There is no risk as long as you get the bootloader for your device.
You can flash old ROMs.
Click to expand...
Click to collapse
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Just flash the zip through CWM or TWRP. The guy says in the OP he made the flashable files so you don't have to use a computer for this process.
If you get bad 4g, then just flash the modem you're on. There's a modem sticky thread in the development section.
Bootloader and modem/baseband are not the same thing.
I have the DLJA modem and the MD5 bootloader. I haven't had any issues at all.
Remember, if you have a T999v, only flash modems and bootloaders made for that specific device. It will clearly say in the op when you read it.
Goodluck.
Sent from my SGH-T999 using xda app-developers app
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Bootloader shouldn't cause signal issues. But flashable over recovery is correct.
Sent from my SGH-T999 using xda premium
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Stop talking about MD5. That firmware is not for your phone. I want to be certain you aren't going to flash that. As for battery life, I had to revert to LJC because of battery drain. The AOSP ROMs only require LJA or newer for us. I don't remember your firmware versions.
Safe to use recovery to flash this stuff. You could make an Odin package, but it would be a waste of time.
IXChicharitoXI said:
Just flash the zip through CWM or TWRP. The guy says in the OP he made the flashable files so you don't have to use a computer for this process.
If you get bad 4g, then just flash the modem you're on. There's a modem sticky thread in the development section.
Bootloader and modem/baseband are not the same thing.
I have the DLJA modem and the MD5 bootloader. I haven't had any issues at all.
Remember, if you have a T999v, only flash modems and bootloaders made for that specific device. It will clearly say in the op when you read it.
Goodluck.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Great thank you! So i've looked for my actual bootloader on my S3 with those commands : su getpro ro.bootloader I was surprised, it told me that I already have the T999VVDLL1 bootloader required for newer AOSP CM roms.
All of this is correct.
You also do have the option of flashing the latest firmware for your model device using Odin.
As long as you've upgraded to VLDLL1 via OTA, Kies or Odin you don't need to do anything.
Sent from my SGH-T999L using xda premium
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
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.
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