UPDATED 2013/11/21: Added more warnings.
This is for US SGH-T999 devices ONLY. If there is ANY letter after your model such as 'L' or 'V' DO NOT FLASH THIS OR YOU WILL DEFINITELY BRICK YOUR PHONE! For SGH-T999V VLDLD1 firmware, please see this thread: http://forum.xda-developers.com/showthread.php?p=41701398
DO NOT flash this if you are running latest 4.3 (*MJC) firmware. It WILL brick your device. Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release.
Currently I don't have a SGH-T999L firmware update script, sorry. If someone would like to work with me on guinea pigging it and has heimdall installed, PM me and we'll get it done in no time.
This is the latest firmware update for US T-Mobile (SGH-T999) that flashes the UVDMD5 radio and bootloader with a convenient update.zip. Flashing it on anything other than the US SGH-T999 is strongly not advisable. It will likely brick your phone. It CANNOT be used on the Canadian T999V variant.
This script flashes all of the firmware that comes with the UVDMD5 OTA -- this upgrades the firmware as if you had just flashed the whole package through Odin, but without actually touching system, recovery, kernel, etc. There are two versions of the script -- one just does the bootloader+firmware, the other does bootloader+firmware+modem.
What are these firmware files?
rpm.mbn - Resources and Power Manager
sbl2.mbn - Part of Secondary Bootloader
sbl3.mbn - Part of Secondary Bootloader
aboot.mbn - AP Bootloader
tz.mbn - Trust Zone
NON-HLOS.bin - Modem / Radio
Why do I want this?
If your phone has old enough firmware, newer CM10.1 builds will no longer install on it. It is unknown if updating to UVDMD5 from UVDLJC, for example, has any noticeable positive effects. No known negative effects have been reported and the Odin method ends up upgrading all this stuff anyway.
Note that you can flash the above files via heimdall but this updater below is handy as you don't need heimdall, download mode, etc. All you really have to do is flash it in recovery.
Flashable UVDMD5 Bootloader / Firmware / Modem update.zip: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_firmware_v4.zip (md5: d040ea4193234cbe9a36f95ffa780086)
Above flashable update without modem: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_noradio_v4.zip (md5: 4c4aa065ee7c86dccea92ec7856a7af4)
OLDER UVDLJC Firmware update.zip script (w/modem) -- only if you specifically need it for some reason.: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999UVDLJC_firmware.zip (md5: 537b69ec54ce6a3580a9c56ca379e72c)
Instructions:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
NOTE: If you plan to flash anything else, please at least reboot recovery or it won't pick up the bootloader change.
Changes:
v1: Initial release. Modified someone's UVDLJC firmware update.zip script to update to UVDMD5.
v2: Removed certs from a previous update.zip that could've been causing signature verification errors with some recoveries.
v3: Updated Edify script courtesy of @Aerowinder
v4: Corrected a derp in package_extract_dir() (my fault) that prevented v3 from working at all. I've since tested v4 personally and verified it.
Many thanks to whomever put together the original update.zip and to Khaytsus and invisiblek for pointing me in the right direction. Also many thanks to all who've tested it and provided feedback. There is no greater enjoyment than in helping people.
I've also hacked together a firmware backup script that works for both T999 and T999V: http://forum.xda-developers.com/showthread.php?p=41548550
DISCLAIMER: I do not take any credit for this stuff, I just put it together. I am not liable for your device if you break it, etc etc. READ THE WARNINGS BEFORE PROCEEDING.
Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2
I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2
re: bootloader
OhhCoreey said:
I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?
Misterjunky said:
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?
Click to expand...
Click to collapse
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2
itzsmokey said:
Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
OhhCoreey said:
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.
Misterjunky said:
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.
Click to expand...
Click to collapse
FWIW, I'm getting much better radio performance after switching to UVDMD5 modem. YMMV but I'm definitely getting better up/down and stronger signal indoor where I had terrible signal. But you you can just flash the modem separately from this .zip -- there's a thread in the d2tmo dev forum with the modems and their recovery flashable update.zip files.
The OP of said thread also undertook a project to allow people to post on some shared Google Map what modem they're using and their results, so you might want to look into what works best for your area too if you care about getting better signal or speed.
Cyanogen pushed the assert for newer bootloaders in the 5/14 nightly I believe as there were lots of people complaining about random crashes and supposedly much fewer reports on newer firmwares. I actually wasn't having this problem very much with LeanKernel, though it did seem to be happening like crazy at some point.
I actually didn't know about all the bootloader versions for our phones until today, it was interesting diving into all this stuff. I discovered at the beginning I was running with the same firmware the device had shipped with and if Cyanogen hadn't pushed for the newer bootloaders, I might have let things be. But since he pushed for it, I decided might as well have the latest stuff.
Cheers
mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
Seen this after I flashed it.....it works perfect, I did a clean install just to have things fresh.
Sent from my SGH-T999 using Tapatalk 2
I don't know if I have a newer bootloader or not but flashed cm 10.1 and it runned perfect how do I know if I have it.
mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
NM
Sent from my SGH-T999 using xda app-developers app
I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.
Aerowinder said:
I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.
Click to expand...
Click to collapse
It is just DD which is what basically Odin would do anyway. The filenames are irrelevant. It's what data goes to which mmcblk0 partition. The file names are what they are as they are taken from the T999 UVDMD5 Odin .zip and for clarity. Why would I rename aboot.mbn to some random file name?
Just run heimdall print-pit some day and you can see how your eMMC is partitioned and what goes where. I could've flashed all these files with heimdall using the correct named partition identifiers rather than numeric identifiers, but I found it more convenient to make a flashable update.zip.
Update however you want, but as someone who doesn't use Windows and doesn't like screwing around with heimdall / Download Mode much, just dd'ing the files to the correct partitions was the most elegant solution I could find.
Nice work!
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.
mondokat said:
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.
Click to expand...
Click to collapse
Thanks though I can't take credit for writing the script. I just extracted the UVDLJC firmware updater script written by another dev, substituted the UVDMD5 files in, updated the script with the new SHA1 sums, and re-zipped it, thus making a flashable UVDMD5 updater script.
It does not flash the system -- it just flashes aboot, rpm, tz, modem, and some sbl files. I run CM10.1 and was able to just flash this without killing any of my system stuff. Recovery, system, kernel, etc. are all preserved. You can make a backup (as anyone should anyway), but you shouldn't need to do any restore or even a cache wipe after flashing either UVDLJC or UVDMD5 updater since it's just bootloader, modem, and some other pieces unrelated to system/kernel.
In retrospect, it would've been trivial to extend the script to create backups of the current partitions on the phone. In fact, I'm pondering a "firmware flasher" script that gives one a menu of different firmwares and ability to backup/restore for fun. Then again, I've never touched these firmware bits until Cyanogen necessitated a newer bootloader in CM10.1.
Anyway, I modified this script for myself at first and I had spent the whole day trying to research the topic without too much info. I saw S3s from other carriers had update ZIPs and was frustrated at the lack of one for d2tmo. After testing it on myself successfully and realizing how safe it is, I decided to just release it so people can benefit from it by upgrading their firmware or ripping it apart and learning how it works and/or making it better.
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.
Thanks for putting this together it has made a huge difference for me with the new radio I have gained 7 mb down and 3 mb up from this I'm running jovy stockoaroma rom right now :thumbup: great idea I was going to odin so I could update that now I don't have to...
Sent from my SGH-T999 using Tapatalk 2
How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium
mnasledov said:
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.
Click to expand...
Click to collapse
Here's what I found:
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess
SBL = Secondary Boot Loader
According to the article, the sbl is something like an efi bios, basically it turns on a bunch of hardware bits and then hands off to the next stage of booting. So I guess now we know. :silly: I'd think if you are updating the boot loader, you'd want to include the secondary bootloader as well. Probably your zip file is correct in that if you update any of those pieces, you should PROBABLY update all of them to the same revision, just in case.
Which means EXTRA thanks to you, for doing the work. Now when people say "why can't I flash the latest CM10?" we can just point to this thread and say "flash that first".
:highfive:
Thanks op so much for this. Running the latest cm nightlies again
Sent from my SGH-T999 using xda premium
djtheraven said:
How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Just open up a shell either in your ROM or CWM Recovery (adb shell) and run:
Code:
$ getprop ro.bootloader
It should print out something like "T999UVDMD5"
I had T999UVALG1 before I upgraded the firmware.
EDIT: If you're going to do it in CWM Recovery, you might have to do it as root. Make sure to adb kill-server as root to kill any adb servers that may be running and a subsequent adb shell should grant you access.
Related
So I'm hoping I'm posting in the appropriate place, and if not please feel free to point me in the right direction. There may be threads that already exist that are what I need, but I find it so hard to find the right thread on this website so after lots of trying I figured I'd just post.
I have Samsung Galaxy S III on WIND Mobile (SGH-T999V) which is said to be identical except in name to the T-Mobile Variant. I tried a few different ways to get root, and since the first which involved CWM weren't working I ended up using Odin to install (flash?) a file called root66.tar from god knows where. I acquired root, but every time I go to flash any Mod (through recovery > apply zip from sd), whether its CM9 or an update pushed to my phone from Wind, i get a status 7 report (I think it's checking for my devices product name to see that it matches whatever the thing is designed for and it doesn't check out?)
I've heard that this is a problem with CWM and all I need to do is flash the latest CWM or a different CWM. I've tried downloading the CWM app, and manually flashing, etc etc, none of it seems to actually change my recovery. Maybe I'm just missing something, but I'm quite sure the recovery simply is not being flashed.
So I found this thread for T-Mo variant that sed to get on root explorer and delete a couple files, which I'll probably try if nobody responds quickly, and hopefully nothing bad will happen, but I wanted to confirm that this will be safe for Wind variant.
Also, I'm freaking out a little inside and want to revert back to my stock ROM, which I found. The thing is it's in zip file and i'm unable to flash .zip. My Windows computer is out of commission and I only have Linux Mint, for which Odin doesn't work, so I have this program called Heimdall. I'm wondering how to package a tar.gz file, what is a tar.gz file? Why not just use a .tar file? or a .gz file? What's the difference. Basically, when I give Heimdall my tar.gz file, whats it gonna do with it?
Any thread-pointing or explanation would be super appreciated! Thank you in advance
edit: In regards to Heimdall, I've looked at some guides, they all site older versions, which appear to be different? the only flashhing I can do is either thru a Heimdall Firmware Package, which I don't know how to make but I'd like to learn, or with a PIT, which I dont have or understand, so any help there would also be good
The files you are supposed to delete are safe to do so. Or you can rename them. Either way will work. Once you do this you can now install recovery from rom or goo manager. Use the app to reboot recovery as well. Very easy.
You don't flash zip files from the computer. You do that in recovery.
There are also other ways to flash. I suggest you read through my firmware thread here:
http://forum.xda-developers.com/showthread.php?t=1949687
Pay attention to Mobile Odin, it may be your easiest and safest way to flash stock firmware.
You got root66.tar from god knows where???
Don't take this the wrong way but it sounds like you are getting a little careless and could cause more problems than you started with.
Do not flash anything except what you find in this forum. Aside from custom roms you should find everything you need in that thread.
Id also suggest reading the stickied threads in this section as well.
Good luck!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
The files you are supposed to delete are safe to do so. Or you can rename them. Either way will work. Once you do this you can now install recovery from rom or goo manager. Use the app to reboot recovery as well. Very easy.
You don't flash zip files from the computer. You do that in recovery.
There are also other ways to flash. I suggest you read through my firmware thread here:
http://forum.xda-developers.com/showthread.php?t=1949687
Pay attention to Mobile Odin, it may be your easiest and safest way to flash stock firmware.
You got root66.tar from god knows where???
Don't take this the wrong way but it sounds like you are getting a little careless and could cause more problems than you started with.
Do not flash anything except what you find in this forum. Aside from custom roms you should find everything you need in that thread.
Id also suggest reading the stickied threads in this section as well.
Good luck!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Haha, I know you flash .zip from recovery. I meant I'm unable to flash .zip through recovery, and I can't use Odin to flash any .tar for example, so I thought if I could learn how to use Heimdall, learn how to package a 'Heimdall Firmware Package', that'd be safest.
Anyhow, Thank you, I will be more careful
Edit: checking back in, I went to delete the files
/system/recovery-from-boot.p
/system/install-recovery.sh
They're nowhere to be found. I looked around other places like /root/system, and /mnt/system, still nothing. Any ideas?
dudds4 said:
Haha, I know you flash .zip from recovery. I meant I'm unable to flash .zip through recovery, and I can't use Odin to flash any .tar for example, so I thought if I could learn how to use Heimdall, learn how to package a 'Heimdall Firmware Package', that'd be safest.
Anyhow, Thank you, I will be more careful
Edit: checking back in, I went to delete the files
/system/recovery-from-boot.p
/system/install-recovery.sh
They're nowhere to be found. I looked around other places like /root/system, and /mnt/system, still nothing. Any ideas?
Click to expand...
Click to collapse
Sorry I really font know anything about heimdall. That's why I suggested looking into mobile odin. It will let you flash the firmware from the phone itself. The free version here on xda won't root the fw during flash like the paid version will.
If those files aren't on your phone then don't worry about them. They rewrite stock recovery every boot.
You can try this to get flashing to work in recovery:
Open /system/build.prop and wherever it says d2can, change it to d2tmo. And change T999V to just T999.
Make a copy of the original first and save to your external sdcard.
Now reboot recovery and try to flash again.
Sent from my SGH-T999 using xda app-developers app
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.
T999 JB 4.3 update - UVUENC2 Firmware
Samsung And T-Mobile have released the next update UVUENC2 for SGH-T999.
EDIT - @mrRobinson has a Root66 version of UVUENC2. That version is KNOX Free. So my recommendation is to visit his thread and using that firmware instead.
WARNING - The following steps are only for those who had accepted the previous 4.3 Update UVUEMJC or flashed it from Root66 thread.
Essentially with the newer updates to the Odin, version 3.09 makes the process pretty easy to those who are familiar. This does work even if you have custom Rom and Custom Recovery. Both of which will be destructively replaced by the new firmware. So take a Nandroid!!! Those with Stock firmware UVUEMJC, please take a Titanium Backup of all the essential stuff to external SD. You have been warned.
1. Obtain the Stock update UVUENC2 from SamMobile Link.
2. Download the CF-AutoRoot zip file for D2TMO by @Chainfire.
3. Obtain Odin 3.09 from here. Do not run Odin.
4. Take a backup of important stuff and put the phone in Download Mode.
5. Connect the phone to the PC and let the drivers install if not installed already.
6. Execute Odin as System Admin and then choose the Stock Firmware as AP (AKA PDA in prior versions).
7. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
8. Complete the Odin flash process.
9 Once that's successful, make sure the phone is still in Download mode.
10. Again Click AP (AKA PDA) and choose the CF-AutoRoot zip previously downloaded.
11. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
12. Complete the Odin Flash process.
13. When it is successful, Disconncect the phone and pull the Battery. Boot the phone to Stock Recovery and wipe Cache as well as Dalvik if there's an option for Dalvik. (My Phone does not have stock so don't remember)
14. Let the phone boot normally and enjoy Rooted Stock update. Profit !
You can use Root Checker App from Play store to confirm Root. If for some reason it failed, update the binaries of the Super user app. Upon launching that app, it may prompt for the same.
CREDIT - Nasirtech Tutorial from over here.
This is perfect, bro! Thanks for the guide!
Is there a flashable file for just the modem?
Sent from my SGH-T999 using XDA Premium 4 mobile app
Yes There is. @Synthetic.Nightmare Posted in this post.
Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem
pp085ster said:
Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem
Click to expand...
Click to collapse
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: [REMOVED FOR NOW]
EDIT: This one works: modified UVUENC boot.img
Totally agree
Is very frustrating dont have ROOT on T999UVUENC2.
My T999 was updated from 4.1.2 to 4.3 T999UVUENC2 directly and was a big mistake I alredy loose my root and cant instal CM11 by any way since I cant disable KNOX.
Heeeelp
Solved
Synthetic.Nightmare said:
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: UVUENC2 boot.img
Click to expand...
Click to collapse
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha
pp085ster said:
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha
Click to expand...
Click to collapse
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk
Synthetic.Nightmare said:
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It installs the modules but then gets stuck at extracting boot.img. The exact error is:
assert failed: write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7")
Does that help? :good:
Yes. That's exactly what I needed.
Went ahead and decided to just go ahead and install TW for some time just to get it working right.
This one should work. Tested and tried on the latest DanDroid.
I've repacked the ramdisk so that androidboot.selinux=permissive (you can check this via terminal by entering
cat /proc/cmdline
after "su"...without quotes), though the settings still seem to show selinux as enforcing.
[LINK REMOVED FOR ANYONE DIRECTED HERE]
EDIT:
Latest T999 boot.img with selinux permissive and init.d support by @enewman17
http://www.mediafire.com/download/v57ka148accbky8/T999_UVUENC2_boot-img_init.d.zip
That works great thanks! let me repost it for the other users that had problems with it too ok? thanks again!
Sent from my SGH-T999 using xda app-developers app
problem with UVUENC2 update
I am on T Mobile, and received the UVUENC2 update on my SGH-T999 Samsung Galaxy SIII. But I believe that resulted in my S3's wifi radio becoming unstable-- on multiple hotspot sites (including my very reliable SSID at home), it is regularly reporting that is disconnected due to "the internet connection on this wifi site is unstable/slow" when in fact, I know that is not the case, at all. What I have to do now to correct this temporarily, is to restart my S3. But it will eventually repeat this annoying (and erroneous) "unstable/slow" wifi error reporting & disconnection. Just thought I would pass this along, since I noticed this problem with mine, specifically and only after I got this update-- the wifi connection on my S3 was working fine historically, til then.
Would this work on the videotron gs3? the baseband is different
Yoddel_Hickory said:
Would this work on the videotron gs3? the baseband is different
Click to expand...
Click to collapse
No it will not. Even the bootloader is different.
Damn well thank you, i'll try something else
I updated to 4.3 UVUENC2 from the OTA upgrade I got from tmobile, but I can't flash a root66 version of this because it's not released yet.
My question is, I thought you couldn't just use CF-Auto-Root with a knox-enabled firmware? I thought the root wouldn't stick? Or am I misinformed?
I'm debating whether I should wait for root66 of UVUENC2 or just do your method...
Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app
masondoctorjt said:
Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
I suggest reading the thread title and the first post. A single search can do wonders.
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
Links removed while investigating the cause of a couple of bricks. Sorry, but don't want to have any more of these happen!
I747 and I747M 4.4.2 Firmware
NE4 / NE6 / NF2 / NH2
For use with TWRP, CWM or Philz Recoveries
The following packages will flash the base 4.4.2 firmware to your device. This can be used to update to the latest build, or in the event that you need to reflash it for whatever reason. The following partitions will be flashed:
aboot - AP Bootloader
NON-HLOS - Modem/Baseband
rpm - Resource and Power Management
sbl2 - Secondary Bootloader 2
sbl3 - Secondary Bootloader 3
tz - Trust Zone
This will NOT flash the system, cache, recovery or boot (kernel) partitions, so it will preserve your current Rom, Recovery and Kernel. There is no requirement that you be on a certain build prior to flashing this, though I will not make any guarantees you will not encounter some issues if making a large jump in versions, such as going from 4.0.4 or 4.1.1 straight to 4.4.2. It should be fine, but I'm just not making any promises.
General Disclaimer
As with everything you use here on XDA, you use this at your own risk. I would not release this if I felt it were unsafe, but things do go wrong, even with fully tested and vetted projects.
How It Works
Flash in the custom recovery of your choice. (Initially tested on TWRP 2.8.0.1)
Once the flash is initiated, it will run the "assert" checks we should all be getting used to by now. This is to prevent downgrading and bricking your device!
Next, each of the firmware files are checked for any corruption using the sha1 checksum. If it fails any of these checks the flash will abort without actually flashing anything.
After passing these checks, the flashing begins! The modem is flashed last! This is in case anything goes wrong, there is no way to end up with a 4.4.2 modem on 4.3 bootloaders!
Once complete, reboot and you are done!
I747M Unified Packages"One Package To Rule Them All!"
You may notice that each I747M build is for each of its relevant carriers, rather than having individual packages for every build, every carrier. While rebuilding these packages, I noticed that they are identical regardless of the carrier. For example, the base firmware in Bell's NE6 is identical to Koodoo's, Sasktel's and Telus'. The same is true for both NF2 and NH2! So we only need one flashable zip for each version! In other words... One Package To Rule Them All!!
REMEMBER!!!Once you update, there is no going back! You cannot flash older firmware, so once you flash to 4.4.2, that is the only firmware you can flash from now on!
DOWNLOADS
I747
UCUFNE4 - AT&T
I747M
VLUFNE6 - Bell, Koodoo, Telus
VLUFNF2 - Fido, Rogers
VLUFNH2 - Bell, Koodoo, Telus
I hope these prove useful for some of you! Good Luck!
Thanks to:
@Aerowinder - for his script I borrowed from a similar project for the T999 and helping fix some issues!
@enewman17 - for everything he does around here, and helping me to solve some problems along the way!
@mnasledov - for doing this the first time for the T999
everyone - for their patience while I got this working!
Reserved
never before, so here goes...
1st.
thank you doc
will ride this huckleberry-special from Fort Dodge to the end of the line. (still on mj2). had just downloaded the S3Rx from @enewman17
err on the side of kindness
Cool! Let me know how it goes!
flashed on my brothers S3 i747(my old S3). flawless.
:good:
err on the side of kindness
Right on! Thank you for trying it out and reporting back! Very much appreciated!
Corrupt
Been flashing the Koodo one and all I get is a corrupt error...
Did you check the md5 on the download?
If that matches up and youre still having issues copy the recovery log to sd and then attach it to your post.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Did you check the md5 on the download?
If that matches up and youre still having issues copy the recovery log to sd and then attach it to your post.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
DLed multiple times, checked the Md5 on my PC and the phone. Can't get the log as a file, this device has been hell. Koodo is an awful company, I've gotten two phones from them and they've both had countless hardware issues and incompatibilities with otherwise standard files, I don't know if they pay discount for Samsung's dropped merchandise or what. TWRP doesn't work at all, only CWM, when I boot TWRP it just can't find any storage medium whatsoever.
Anyway, all it says when I show it is that it verifies the checksum, finds corruption,and aborts. There's a bit below it as well, copied everything meaningful:
minzip: extracted "/tmp/sb12.mbn",
minzip: extracted "/tmp/sb13.mbn",
minzip: extracted "/tmp/tz.mbn"
verifying checksums...
FILE CORRUPTION DETECTED!!! Script result was [7]
aborting
cleaning up
Ok, ill double check it shortly. I know in twrp's advanced menu there is an option to copy log to sd. Are you sure cwm doesnt have the same? Id be surprised if it didnt.
Sorry for the trouble though. It is possible i made a simple mistake somewhere. If so i will find and fix it.
Everything checks out so far on my end. Im downloading the firmware again in case something went wrong there.
In the meantime, what recovery are you using? Maybe try using a different one ir a different version?
Ok, ive checked everything on the Koodoo firmware and i couldnt find anything wrong. Picked it apart twice, re-downloaded the original firmware and checked that nothing was corrupt. Other than the recovery, i cant think of any other reason itd be failing like that.
Might be best for you to flash the full firmware with odin if using a different recovery doesnt work.
mrrocketdog said:
flashed on my brothers S3 i747(my old S3). flawless.
:good:
err on the side of kindness
Click to expand...
Click to collapse
What recovery did you use?
twrp 2.6.3.1(att)
err on the side of kindness
Thanks. Kinda suspected as much. The update binary may not be compatible with the latest version.
DocHoliday77 said:
Everything checks out so far on my end. Im downloading the firmware again in case something went wrong there.
In the meantime, what recovery are you using? Maybe try using a different one ir a different version?
Click to expand...
Click to collapse
CWM 6.0.4.7. TWRP doesnt work for me.
JohnHorus said:
CWM 6.0.4.7. TWRP doesnt work for me.
Click to expand...
Click to collapse
So are you saying CWM worked for you then?
DocHoliday77 said:
So are you saying CWM worked for you then?
Click to expand...
Click to collapse
No, TWRP doesn't work AT ALL for me. It can't even locate my internal SD.
CWM 6.0.4.7 is all I've tried with.
I dont use cwm so im not sure about the version right off hand. If thats the latest, try a slightly older one, or if its older try the latest.
I got file corruption error in at&t i747. Did not tried to flash again. Using latest twrp recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app