Related
Here is the stripped version of ICL53F.
FLASH AT YOUR OWN RISK
Changelogs are not fully known yet, but I do know this is Android 4.0.2 and USB host is now working
Stripped meaning no bootloaders, no recovery (so you keep your current CWM), and no wipe (so you keep your data).
IMPORTANT: No wipe is only if your device has been previously OEM unlocked. If your device is NOT OEM unlocked, this WILL wipe your data !
It does include kernel, system and modem, and it's an ODIN tar because ... just because !
YAKJU (GSM): http://www.multiupload.com/7C78MDUQG9
MYSID (LTE): http://www.multiupload.com/3ZZ79I7057
In doubt which one you want ? ADB the following commands:
adb shell getprop ro.product.name
adb shell getprop ro.build.description
adb shell getprop ro.build.fingerprint
The full original Google images can be found here:
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
ODIN ?!
The (Windows) software is attached. USE THE ATTACHED VERSION. DO NOT USE AN OLDER VERSION. A lot of you will be familiar with ODIN from other Samsung devices... well, it works exactly the same on this device.
Turn off your device, turn it on again by holding volume-down and power to enter ODIN download mode.
Launch the ODIN software, press the PDA button and select the .tar file you extracted from the .zip file you downloaded.
Make sure in the ODIN program "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
Connect the Android device with your computer and you should see a yellow box in the ODIN program. Press the "Start" button, wait a minute or so, and your device will be booted with this firmware.
Also see the attached image, which has every box you need to look at circled in red
For both GSM and LTE compatibility ? ?
Nice !
Could you please tell me how to use it with Odin (used to use Odin with SII or Ace but not with Nexus version..)
Thanks for your explanations
imfloflo said:
For both GSM and LTE compatibility ? ?
Click to expand...
Click to collapse
Yeah there are two separate links in OP. One for GSM, and one for LTE.
@zephiK after OP edited #1 i found my answer thanks
@Chainfire can you add the mac OSX step by step too plz.
Thanks for sharing this
Hi Chain fire
First of all its nice to see you on the Nexus section. Don't know what I would have down without your fantastic rooted kernels on the SGS2.
Do you loose root and boot loader is locked again if you flash this 53F?
Sent from my Galaxy Nexus using xda premium
OP update now with Odin & how to answers my request,
Thank you
Hey Chainfire good to see you here!
I heard that the new bootloader might solve the charging issue...can you confirm?
Also really would like to see cf-root kernels...used them alot on my sgs1 and sgs2...always the best kernels for me.
Good to see Odin is back too...its the best thing to use to flash youre phone
Sent from my Galaxy Nexus using xda premium
Any chance that I can flash it on to yakjuux and have no problems?
imfloflo said:
@zephiK after OP edited #1 i found my answer thanks
@Chainfire can you add the mac OSX step by step too plz.
Thanks for sharing this
Click to expand...
Click to collapse
I have no idea what the steps are on Mac OSX.
schrickm5 said:
Hi Chain fire
First of all its nice to see you on the Nexus section. Don't know what I would have down without your fantastic rooted kernels on the SGS2.
Do you loose root and boot loader is locked again if you flash this 53F?
Click to expand...
Click to collapse
You will lose root. If you have CWM recovery installed you can just flash a Superuser package through recovery, as CWM is not overwritten by this flash.
This flash does not include bootloaders, and will not re-lock your bootloaders.
(It even appears ODIN will unlock your bootloader if it was locked)
D_Magic said:
Hey Chainfire good to see you here!
I heard that the new bootloader might solve the charging issue...can you confirm?
Also really would like to see cf-root kernels...used them alot on my sgs1 and sgs2...always the best kernels for me
Click to expand...
Click to collapse
Can't confirm because I don't know. I have only had the charging issue when using custom kernels, the stock kernel had no issue for me.
Not sure if I will release a CF-Root... as this device has a separate recovery partition, there is not that much need for CF-Root... It's still handy though, of course.
Should the bootloaders prove needed and/or helpful, I will release a separate bootloader package so you can flash those later.
AfzalivE said:
Any chance that I can flash it on to yakjuux and have no problems?
Click to expand...
Click to collapse
Nobody knows.
To be fair, I don't even know which model I have. I flashed the Google provided stock image of ITL41F within an hour of getting my Nexus last week, due to soft-bricking it (yeah, that quick).
It may work, it may not.
Chainfire said:
Nobody knows.
To be fair, I don't even know which model I have. I flashed the Google provided stock image of ITL41F within an hour of getting my Nexus last week, due to soft-bricking it (yeah, that quick).
It may work, it may not.
Click to expand...
Click to collapse
Alright then, I'll just flash the provided ICL53F images then...just to switch over to yakju.
Nice to see you here Chainfire. Thanks for this, I will flash it now as I'm looking for a stock ROM, or just stock in its own. I find custom ROM's cause too much battery drain with all the features that are adding.
Chainfire said:
Should the bootloaders prove needed and/or helpful, I will release a separate bootloader package so you can flash those later.
Click to expand...
Click to collapse
Thanks but it turns out the new bootloader doesn't fix the issue
So if i flash this with odin then i keep the unlocked bootloader and cwm but i loose root....what do you mean with flash a superuser package? ( i wanna go back to stock for now cause on every custom rom/kernel i get a really bad battery drain )
Sent from my Galaxy Nexus using xda premium
D_Magic said:
Thanks but it turns out the new bootloader doesn't fix the issue
So if i flash this with odin then i keep the unlocked bootloader and cwm but i loose root....what do you mean with flash a superuser package? ( i wanna go back to stock for now cause on every custom rom/kernel i get a really bad battery drain )
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Maybe the new bootloader fixes the RF interference (debounce time) on the volume buttons (that was only patched in the kernel in the last update)?
I guess someone who lives in a region that had that problem would have to check.
Here are the changes from 4.0.1 --> 4.0.2
Device features
Optimized Mobile Hotspot when used with VPN
Optimized 3G/4G data sessions for faster response times
Fixed an incorrect notification that “data was disconnected due to roaming”
WiFi now automatically reconnects when returning to a known Access Point
Improvements to special visual effects feature when using front-facing camcorder
Visual improvements to the lock screen
Email and Messaging
Fixed an issue where some email attachments would not open correctly
Apps and Widgets
DivX support has been removed and will be supported in a future upgrade
Improved audio volume in Google navigation turn-by-turn directions
Anyone know if I can use this tar file with Heimdall?
madj42 said:
Anyone know if I can use this tar file with Heimdall?
Click to expand...
Click to collapse
Don't know for sure, but I don't see why not ...
Chainfire said:
mysid variant has not been tested by me. Please let me know if the radio flashes properly... if not I'll update the package.
Click to expand...
Click to collapse
Radio flashed flawlessly here
Did anyone of you get the Update ota? On the gsm nexus?
Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this
Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened
Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems
:good:
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*
buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app
Hey guys, how are you?
Sorry my bad english! But I need your help ...
I recently installed the Rom LiquidSmooth 4.2.2 Android 4.2.2 to test itself, not LiquidSmooth, found it very nice and everything. But back to the factory settings with the stock ROM 4.0.4 and I upgrade by Kies and pff, my phone can not do updates by Kies. Samsung tried my country (Brazil) but they can not support (or paying for and also not aware of devices outside) for my I747 ... I did the emergency recovery firmware and now it's on 4.1.1 but it still remains unrecognized by Kies (NOTE: It is recognized rather as SGH-I747, however, can not do updates or anything, just back of the device; NOTE 2: I bought it at AT & T in the United States and I can not take you there to support). The mesangem is: "Your device does not support firmware upgrade via kies".
After getting well pissed off with this bull****, or my **** (haha) decided to find out what was wrong and found that some of the things LiquidSmooth is still in the system, such as ringtones, facebook layout and stuff ... (Print the end of the topic) .
So I come here asking for help to you, to completely reset it and go back to having all functions and patterns of manufactures, so that in future I can sell it or give it to my mom and she does not get lost as I am today ...
Is there any way I can do this completely and return it to factory defaults?
attempts:
- I went back to stock rom several times and still the same thing;
- I tried the firmware recovery Kies and nothing;
- I tried several tutorials on the internet and nothing.
Can anyone help me?
I literally am going crazy because of it ...
Diego.
DiegoEvangelista said:
Hey guys, how are you?
Sorry my bad english! But I need your help ...
I recently installed the Rom LiquidSmooth 4.2.2 Android 4.2.2 to test itself, not LiquidSmooth, found it very nice and everything. But back to the factory settings with the stock ROM 4.0.4 and I upgrade by Kies and pff, my phone can not do updates by Kies. Samsung tried my country (Brazil) but they can not support (or paying for and also not aware of devices outside) for my I747 ... I did the emergency recovery firmware and now it's on 4.1.1 but it still remains unrecognized by Kies (NOTE: It is recognized rather as SGH-I747, however, can not do updates or anything, just back of the device; NOTE 2: I bought it at AT & T in the United States and I can not take you there to support). The mesangem is: "Your device does not support firmware upgrade via kies".
After getting well pissed off with this bull****, or my **** (haha) decided to find out what was wrong and found that some of the things LiquidSmooth is still in the system, such as ringtones, facebook layout and stuff ... (Print the end of the topic) .
So I come here asking for help to you, to completely reset it and go back to having all functions and patterns of manufactures, so that in future I can sell it or give it to my mom and she does not get lost as I am today ...
Is there any way I can do this completely and return it to factory defaults?
attempts:
- I went back to stock rom several times and still the same thing;
- I tried the firmware recovery Kies and nothing;
- I tried several tutorials on the internet and nothing.
Can anyone help me?
I literally am going crazy because of it ...
Diego.
Click to expand...
Click to collapse
How did you go back to stock? You'll get errors from kies and ota updates by remaining rooted.
By the sounds of it it just needs a proper wipe the unroot.
This video will get you back to 100% stock unrooted.
https://www.youtube.com/watch?v=WzydHUG7XZE&feature=youtube_gdata_player
Also check out this link. The second post has a paragraph on unrooting to go with the video. It also contains the proper links for all the files you'll need to do it.
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
How did you go back to stock? You'll get errors from kies and ota updates by remaining rooted.
By the sounds of it it just needs a proper wipe the unroot.
This video will get you back to 100% stock unrooted.
https://www.youtube.com/watch?v=WzydHUG7XZE&feature=youtube_gdata_player
Also check out this link. The second post has a paragraph on unrooting to go with the video. It also contains the proper links for all the files you'll need to do it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
best unroot video ever.
OP, to accompany the video guide, you'll need:
- Triangle Away installed
- The official stock firmware for your device
- Odin installed on your PC
- Your Samsung USB cable, if possible
- Samsung drivers installed on PC
xBeerdroiDx said:
best unroot video ever.
OP, to accompany the video guide, you'll need:
- Triangle Away installed
- The official stock firmware for your device
- Odin installed on your PC
- Your Samsung USB cable, if possible
- Samsung drivers installed on PC
Click to expand...
Click to collapse
An shoot thanks. Forgot to link the thread. Was half asleep.
Sent from my SGH-I747 using xda app-developers app
Thanks for everything so far guys, but without success ... Still the same thing.
All I have to follow these steps before and still have the same problem.
Anything else? :/
I'll try again, maybe...
Thx a lot.
-----
TraingleAway not reset my phone and boot him, his reset counter and no more... is this the problem wrong?
DiegoEvangelista said:
Thanks for everything so far guys, but without success ... Still the same thing.
All I have to follow these steps before and still have the same problem.
Anything else? :/
I'll try again, maybe...
Thx a lot.
-----
TraingleAway not reset my phone and boot him, his reset counter and no more... is this the problem wrong?
Click to expand...
Click to collapse
Did you unroot?
You need to do that before anything else
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
Did you unroot?
You need to do that before anything else
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, but my TriangleAway is a v2.99 and not reset my device after reset the flash counter...
I reset manual.
Obs: this screen is not active...
Diego.
I tried the tip of the video, however, was the same thing ...
I'm looking for a fix to kies, but I do not think any status or anything ...
DiegoEvangelista said:
I tried the tip of the video, however, was the same thing ...
I'm looking for a fix to kies, but I do not think any status or anything ...
Click to expand...
Click to collapse
So when I went back to stock:
1. I just flashed a rooted stock firmware in odin
http://forum.xda-developers.com/showthread.php?t=1739426
(just so I was back on a 4.1.1 stock rom. I didn't want to odin from a custom rom)
2. Then used triangle away
3. Then flashed the stock unrooted 4.0.4 from here in odin
http://www.sammobile.com/firmwares/
(This gets rid of custom recovery)
4. Booted in stock recovery and then did a factory reset because you sometimes get a simple bootloop
5. Rebooted and I was back to stock.
I've noticed sometimes you have to switch the order around some to get it unrooted and the flash counter reset. Triablge away is for right before you unroot. You have to flash a stock .tar rom in odin to get rid of the custom recovery as well. It replaces the system, kernel, and the recovery.
hednik said:
So when I went back to stock:
1. I just flashed a rooted stock firmware in odin
http://forum.xda-developers.com/showthread.php?t=1739426
(just so I was back on a 4.1.1 stock rom. I didn't want to odin from a custom rom)
2. Then used triangle away
3. Then flashed the stock unrooted 4.0.4 from here in odin
http://www.sammobile.com/firmwares/
(This gets rid of custom recovery)
4. Booted in stock recovery and then did a factory reset because you sometimes get a simple bootloop
5. Rebooted and I was back to stock.
I've noticed sometimes you have to switch the order around some to get it unrooted and the flash counter reset. Triablge away is for right before you unroot. You have to flash a stock .tar rom in odin to get rid of the custom recovery as well. It replaces the system, kernel, and the recovery.
Click to expand...
Click to collapse
Thank you bro, but my problem is Kies. I can't upgrade for him.
He did not let me update or related ...
I've done everything, often ...
- Unroot flash rom;
- Factory reset in recovery and in phone;
- All things.
I do not know what else to do.
I can do the emergency recovery firmware but it keeps saying that my device does not support updates via kies.
DiegoEvangelista said:
Thank you bro, but my problem is Kies. I can't upgrade for him.
He did not let me update or related ...
I've done everything, often ...
- Unroot flash rom;
- Factory reset in recovery and in phone;
- All things.
I do not know what else to do.
I can do the emergency recovery firmware but it keeps saying that my device does not support updates via kies.
Click to expand...
Click to collapse
Are you sure you did the steps in the right order ? Kies won't do that unless you are still rooted or have a custom recovery. I
Kies has no use here to be honest but I know some people like to use it to upgrade from time to time or transfer data.
What exactly is the emergency recovery firmware ? (Your name for it might be different than mine)
hednik said:
Are you sure you did the steps in the right order ? Kies won't do that unless you are still rooted or have a custom recovery. I
Kies has no use here to be honest but I know some people like to use it to upgrade from time to time or transfer data.
What exactly is the emergency recovery firmware ? (Your name for it might be different than mine)
Click to expand...
Click to collapse
Y, bro. I followed all the steps... All right!
--
Recovery Emergency Firmware in Kies:
-> Tools
-> Firmware upgrade and initialization
-> Model
-> Serial Number
-> Download Mode in s3.
I tried all tutorials, but, not successful
More sugestions?
Diego.
Any other tips to reset the device completely and again be recognized by Kies?
:/
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.
[Firmware] [Odin] [Official] Firmware / Kernel / Modem / Recovery [M919UVUFOK3] TW 4.4.4
This is a Odin-flashable official firmware, kernel, modem & recovery for T-Mobile Samsung Galaxy 4 (M919)
How to install:
1. Extract the *.tar.md5 file using 7-Zip
2. Extract Odin v3.09 & open it
3. Reboot to Download Mode (press and hold Home + Power + Volume Down)
4. Connect phone and wait until you get a blue sign in Odin
5. Add the *.tar.md5 file to AP / PDA
6. Make sure re-partition is NOT ticked
7. Click the start button, sit back & wait a few minutes
Full Firmware:
https://www.androidfilehost.com/?fid=24338798368260486
Stock Kernel : Flash via Recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260505
Stock Recovery: Flash via Recovery, only needed if you want to go back to stock recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260507
Modem : ODIN Flashable
link removed as so many people are having issues with it
IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..
reilus said:
IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..
Click to expand...
Click to collapse
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk
a103 said:
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...
reilus said:
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...
Click to expand...
Click to collapse
You will need to flash TWRP first and then supersu.
Sent from my GT-I9505 using Tapatalk
Is the bootloader the same as the previous one?
Hmm....it looks like Xposed no longer works with this update. This is the error when you try to install it:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
Click to expand...
Click to collapse
Update: The Xposed_v2.6.1_by_SolarWarez_20151129.apk variant works with this release! Search for it on Google if the stock versions wouldn't run on your phone!
Arkain2K said:
Hmm....it looks like Xposed no longer works with this update.
Click to expand...
Click to collapse
Can anyone else confirm? Thanks
Sent from my SGH-M919 using XDA Free mobile app
Use the old Xposed Installer v2.6.1 with TW 4.4.4, and you can directly install the xposed framework within the app.
Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.
technut said:
Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.
Click to expand...
Click to collapse
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk
a103 said:
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I forgot to list that I did that also. For me at least this S4 was very stubborn to take on this flash. I was mostly posting so if anyone else ran into this so they wouldn't panic. All is well now though. It came around eventually.:good:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Sent from my SGH-M919 using Tapatalk
timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.
pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.
Click to expand...
Click to collapse
So it should be a fairly straightforward process? The issues technut experienced are unusual? Has anyone else installed and rooted using this ROM? Please report on how it went.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
a103 said:
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Click to expand...
Click to collapse
a103, when you say "flashed a custom ROM", do you mean a different ROM than the one in the OP of this thread? (since this one isn't really custom) If a different ROM, which did you flash? I didn't find many options that contained the OK3 firmware.
pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
Click to expand...
Click to collapse
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
I read in another place that the firmware contains the Modem so I wouldn't need to flash the modem in addition to the full firmware (M919UVUFOK3_M919TMBFOK3_TMB.zip). Is that true in this case? Does it include both modem and kernel?
Edit - After searching out how to open tar.md5 files I can now see that the full firmware does include the kernel and modem files. So installing that one should sufficient to update everything.
timg11 said:
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
Click to expand...
Click to collapse
Just flash the firmware, it has the kernel and modem in it.
Sent from my GT-I9505 using Tapatalk
a103 said:
Just flash the firmware, it has the kernel and modem in it.
Click to expand...
Click to collapse
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.
timg11 said:
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.
Click to expand...
Click to collapse
I didn't encounter any issues.
Sent from my GT-I9505 using Tapatalk