yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] loserskater:
Short answer: no.

The boot.img is essential in building a Rom. The current 4.3 roms are aosp based and don't contain the closed source libraries that TW uses. It would be a massive undertaking to try and get an aosp kernel to work on TW. And since this is the first 4.3 we've seen, we can't just pull the kernel from another device.

Sent from my SAMSUNG-SGH-I747
[T-Mobile, Samsung Galaxy SIII] fcortes626:
is it possible to make a rom using the 4.3 system dump a 4.1.2 boot.img?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Very, very, seriously doubt it. Never before has an old kernel been able to boot new firmware.
[T-Mobile, Samsung Galaxy SIII] scifan:
Just having a working knowledge of linux... Library version mis-matches will tend to break this sort of configuration

Effectively without the kernel and the libraries, this is something to look at and let us know for certain they're working on 4.3 for our phones... but it's not terribly useful to construct a kernel with.

And my guess is the guy who provided this can't really provide more without possibly causing himself pain....

I'm glad to see that the work is happening though... :D
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Agreed, and I hope everyone else understands that he did not have to even give us what he did. That alone was probably a bit of a risk for him. And I think everyone should consider how often people like to make similar claims and never back them up, and be thankful to him for going the extra distance and posting the actual /system for us to look at!

I personally don't have the time right now, but it is possible that some of the apps might be able to be ported to work on 4.1.2. It may be more difficult though considering we are skipping 4.2.2. But I'm sure someone will end up at least attempting to do so for the camera and gallery, maybe more.

Really though, at this point I'm mostly just curious to see if we are going to get any new features to play with. And also to find if the rumors are true that if you take the full update it will prevent you from being able to downgrade again if you decide you want to.
[T-Mobile, Samsung Galaxy SIII] scifan:
I'd be fairly surprised if there was anything past what 4.3 gives...

I hadn't heard that rumor... Considering 4.1 basically created a number of other avenue's whereby they could identify if a device had been altered... I wouldn't be too surprised if there were some other "features" cooked in...

I think I'll wait and not be one of the first people to update my device this time.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I don't plan on taking the full update initially either! It was briefly mentioned in one of the threads in General, but with the use of seLinux, apparently it may prevent the ability to downgrade. Like I said, it's just a rumor, but like you said, it wouldn't surprise me. I hate that Sammy seems to get less dev friendly with each new release....
[T-Mobile, Samsung Galaxy SIII] Adreaver:
+1 on skipping the update at first. Until somebody confirms that 4.3 doesn't have a locked bootloader, or somebody confirms you can Odin back to an exploitable version, I'll stick to the 4.3 I'm already running (PACman)

Sent from my T999L on PAC-man
[T-Mobile, Samsung Galaxy SIII] mohan_kr:
bootloader for sure is NOT locked at least on older revision of the 4.3 (MI1) per my source, and it is normally driven by carrier (T-MO does not). But for sure it is going to be SELinux "Enforcing".
[T-Mobile, Samsung Galaxy SIII] scifan:
There are some aspects of SELinux that are good... though it could have a significant impact in rooting future devices...
[T-Mobile, Samsung Galaxy SIII] mohan_kr:
For an unlocked bootloader it has no impact..yes the dev's need to get familiar with the concept as it is part of Android 4.3 onwards ;). You just have to muck around with the policy file (in kernel ramdisk) to give "root" user all roles for all domains. Unfortunately, it cannot be disabled as they have leaked the abstractions to the platform (part of KNOX, I believe)..
[T-Mobile, Samsung Galaxy SIII] fcortes626:
i just noticed the note3 is also UVUBMI7 just like the screenshot mohan posted. i wonder if the note 3 boot.img is any similar to the s3
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Wouldn't count on it.
[T-Mobile, Samsung Galaxy SIII] blackwing182:
nop, a complete diferent device, it can brick your s3
[T-Mobile, Samsung Galaxy SIII] scifan:
Yeah... no wouldn't try that... ;)
[T-Mobile, Samsung Galaxy SIII] fcortes626:
I know flashing it will brick but I keant like if it was similar maybe some one can use it to get something started for our device :D
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Also if you look at the build prop and a previous post, it appears he's been updated already to MI9, at least at the time of his pulling the files for us.

The boot.img (kernel+ramdisk) is specifically built for the device hardware, in particular the SoC. So unless the Note3 is using our hardware, it's not going to work, and as everyone is saying, don't even try it! And I'm pretty sure Sammy would've used newer hardware than the Note2, not older!
[T-Mobile, Samsung Galaxy SIII] rohit.bhosale:
I just formatted my internal storage and hence there is no ROM installed on the system now. It earlier was MIUI.

Now can I flash this stock rom using odin and the right firmwares you have listed?

will it work?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Why not just try it?
[T-Mobile, Samsung Galaxy SIII] ThaGreatest:
Ok so what am I doing wrong? I got a brand new phone but when I got install the root66 on odin it gets stuck in Getting PIT for mapping
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Check md5. You may have a bad download.

Sent from my T999L on PAC-man
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
What model is it? Look under the battery, you can't always trust what it says in Settings. If it's brand new, I assume you have a T999L?
[T-Mobile, Samsung Galaxy SIII] ThaGreatest:
Nah its not the newer model with LTE its just a brand new regular one which replaced my old one which broke.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ahhh, a refurb eh? Or is it really brand new?

Are you still having problems with Odin?

It could've been a corrupt download like adreaver said.

You could also try using LJC firmware instead of md5, just to see if it acts different.

Another thing you can try is to flash CWM or TWRP via Odin. (Files in my Sig)

Let me know if any of these help.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Probably obviously that this has came up. But why not use the AT&T kernel from the recent 4.3 leak?
[T-Mobile, Samsung Galaxy SIII] scifan:
Hmmm... Doc - any realistic possibility of frankensteining the system dump you were previously given, and the system boot from the AT&T leak... and create a functional 4.3 w/ wifi calling?!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No promises, but stay tuned! Been working on this stuff for a while now. ;)

Got my daughter this weekend, so time is limited till tomorrow night.
[T-Mobile, Samsung Galaxy SIII] scifan:
Well... focus on your daughter while you've got her...

I do have a spare phone to test with... so let me know... :D
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
^ +1. Also, I'd recommend no one tries this unless you're experienced or ready to brick your phone, or both.
[T-Mobile, Samsung Galaxy SIII] scifan:
Yeah... I've scared myself enough with previous phones to not get too excited doing that stuff... Though I think as long as I'm not putzing with the radio, I'm not in extreme danger...

Also, the AT&T kernel is probably lacking modules that would be necessary for Wi-Fi calling to work... but it's promising..
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
That's the thing. I've been doing some thinking that AT&T and T-Mobile S3s have interoperability minus modems. But here's what makes me not want to try it, 4.3 is including KNOX and SELinux who knows if this will change anything in the hardware or create some sort of check.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
As I understand it so far, Knox is a security feature which meets DoD requirements for use on an enterprise network. It detects any sort of modification you might do, including root, and logs it in much the same way as our current flash counter. If this is tripped, Knox security is permanently disabled. This normally would probably only matter to the few people who actually want Knox. But, I believe it matters to us for the same reason they didn't make Knox enabled devices separately available for business purchases. It basically can be used as a secondary flash counter to deny warranty claims. This still won't matter to most of us, but when we go to new devices such as the Note3, it'll matter. I'm not aware of anyway to reset this yet. I've heard they have ways around both Knox and seLinux for the S4, but I don't know what all this entails.

As for effect on hardware, I don't think we have to worry about that. Right now I am expecting to simply just follow the same precautions as before. Meaning the same compatibility between the T999, I747, and their variants as before. I don't promise this in any way, but I don't think we have much to worry about.

As for the modem, well, of course we cannot use any from other models, but this already doesn't matter!

Merry Christmas!

http://www.androidfilehost.com/?fid=23196940996969671

Thanks goes to an anonymous source!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ignore the device model. This is a T999.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
This modem cross compatible for T999L/N/V or just for the stock T999?

I'll test tomorrow if nobody has tried it yet, flashing the LJA modem did no permanent damage so I assume the same would be true here.

Sent from my T999L on PAC-man
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Be sure to tell him I said thanks on behalf of us all. Its probably someone we know well, so in that case thank you if you're reading this. Getting on the update now. Thanks Doc and company.

Also, I'm looking at the AT&T thread and it says we need to update bootloaders?

News :

I heard that the T999 works with the AT&T build, it does NOT.
[T-Mobile, Samsung Galaxy SIII] scifan:
Interesting... seems rather promising... :)
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Working on something, at best if this doesn't WORK, we will have a very debloated, sick as hell base with tons of SE and KNOX removed.
[T-Mobile, Samsung Galaxy SIII] pappuhathi:
GPS Not Working

I was running a custom 4.1.1 rom (sprint port) and then flashed the stock rom via odin. Since then my phone cannot detect any GPS satellites (I tried different apps). I even re-flashed the custom rom but it still isn't working. I read somewhere that this could be because of a different kernel.

Can someone held me please?

Remember, god helps those who help the NOOBS.

The Kernel under settings is as follows:

3.0.31-178444

se.infra@SEP-95 #1

SMP PREEMPTT Sun Sep 16 13:57:17 KST

2012

Is this the correct one? If not, how do I rectify this?
[T-Mobile, Samsung Galaxy SIII] CQCmaster:
Since I am on WIND Mobile, what would I have to do to go from VLALE6 (Original ICS) to VLALI3 (Jellybean update for Videotron)?

Do I go..

1st) Wind VLALE6 - VLALH2

2nd) Videotron VLALH2 - VLALI3

If so, since I am only updating through recovery, will I lose root?

BTW, I am on unmodified Original ICS (VLALE6) with root.

I would gladly appreciate for any input...

Thanks in advance

P.S.

I forgot to mention, will the recovery update to Videotron jellybean leak change my modem too?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It'll be a bit mor complicated than that actually. Not a lot more I don't think, but the videotron package will check if your phone is videotron, and it'll fail. Would likely have to edit the otas script or your build.prop to trick it. But also if any part of the system is different between the two it'll also cause it to fail.

We can give it a shot later on if you like.

Or if you know someone on here with videotron that's willing to do the update, then either get me a nandroid of just the system and boot partition, or adb pull the system and boot, I can try to throw together a quick rom for you guys.

Just an option!

Ill look at the updates later and see what we can do.
[T-Mobile, Samsung Galaxy SIII] md1008:
I am no expert but have you tried flashing a different kernal?
[T-Mobile, Samsung Galaxy SIII] warlock257:
I am in Canada, with Mobilicity, but I bought a T-mobile branded S3 today (T999)

It's currently on the version from August.

Am I able to flash the Mobilicity updated firmware?

I'm not as concerned with the various ICS versions, but I definitely want my Jelly Bean update when it is released.

Any advice?

Thanks
[T-Mobile, Samsung Galaxy SIII] tdizzle404:
Looks like 4.2 has begun hopefully well see it soon!

http://m.androidcentral.com/pre-release-nexus-4-and-nexus-10-devices-getting-ota
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Its in the op. Im hosting it as well so itll be a faster download.

OTA will be up soon.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
OP Updated!

Added OTA from UVALJ4 to UVDLJA!

Will post mirror soon.
[T-Mobile, Samsung Galaxy SIII] Minker17:
Flashing is failing. Error Code 7. Stock/Root. CWMTouch.

Any ideas? Maybe a build.prop error?
[T-Mobile, Samsung Galaxy SIII] gaww:
I am restoring nandroid of UVALJ4 and modem, Is the below the correct file from the OP to Odin over it? If so, is this pre-rooted (hard to tell from the OP).

Official SGH-T999 Firmware (for use with Odin)

UVDLJA

PDA: T999UVDLJA

CSC: T999TMBDLJA

Version: 4.1.1 JB

Date: Nov. 14, 2012
[T-Mobile, Samsung Galaxy SIII] manolodf:
Would any of the flashing methods like Mobile Odin Pro or any others allow me to keep all my apps/settings/home screens intact for the update (Obviously root as well)? That is what I have the hardest time with when doing an update is starting from scratch on everything and it annoys me. I was wondering if there was an easier way, and I am not talking titanium backup because that does not restore homescreens and sometimes is not as great as expected, I'm talking easy like iOS update easy where everything is just how you left it.
[T-Mobile, Samsung Galaxy SIII] DigitalUnderground:
Doc,

I downloaded the new t999 ota... The fw version to use in odin. Opened mobile Odin pro, selected ota/update, and selected it and it said that it wasn't an ota and needed to be extracted. I extracted it and have SS_DL.dliii and T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar

Is that right? If so, which do I flash?

Thanks

---------- Post added at 11:06 AM ---------- Previous post was at 11:06 AM ----------

It is NOT pre-rooted
[T-Mobile, Samsung Galaxy SIII] WarlockW:
Suggestions ?

Hmmm .. No Luck ..

Tried to update using : CWM and TWRP

OTA_T999_UVALJ4_UVDLJA.zip

Both fail .. Need to have stock Kernel ? Temp Un-root? Or?

Suggestions ?
[T-Mobile, Samsung Galaxy SIII] DigitalUnderground:
Read post 3

ALL STOCK if flashing in recovery

Edit... Also says can be flashed in cwm 6.0.1.2... I'm trying now

Edit... Flashing in cwm failed and installation aborted... I think I need help here lol :o

Edit: I downloaded the ota to be flashed in recovery and tried with mobile Odin (hope and prayer) didn't work either
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
If you are on stock LJ4 you can flash the OTA zip i have in my thread to get to latest. But everything except for the recovery has to be stock as it patches the files and so checks their md5sums to patch correctly. If files are missing or don't match, it'll fail. Same with kernel, bootloader, etc. I just removed the recovery checks so you can use CWM or TWRP and I've made it so it won't squash root.
[T-Mobile, Samsung Galaxy SIII] warlock257:
tried flashing the OTA one in clockwork, but got:

assert failed: getprop("ro.product.device") d2tmo" ||

getprop ("ro.build.product") "d2tmo"

error in /emmc/otc_t999_uvalj4_uvdlja.zip

(status 7)

installation aborted
[T-Mobile, Samsung Galaxy SIII] DigitalUnderground:
Thanks man. You and Doc are the best!

I was hoping for some way to do it via mobile without odining back to stock but I guess I will break out the dusty laptop when I get home :/

---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------

You have to be stock... Read quote above your post
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Youve gof to be 100% stock save for cwm. Any mods, bloat removal will fail. If you are deodexed it will fail.

always nandroid to be safe!

All methods should preserve your data and apps, but it sometimes does hang at boot and force a factory reset, so nandroid!

in mobile odin, select the ota/update part only if using the ota. Otherwise oress chhose file

Did you extract the .tar.md5?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ill post a collection of tools such as Odin and recovery/odin flashable recoveries shortly.
[T-Mobile, Samsung Galaxy SIII] scifan:
If it does work, I'm one of those sicko's who actually use a few off the apps generally considered bloat... some, not all.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Disregard what I posted here, like an idiot.
[T-Mobile, Samsung Galaxy SIII] scifan:
I thought they had a set with KNOX disabled...
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Yeah they do. SeLinux is still being enforced however. No root probably but the good news is, I've got 4G working on the 4.3 AT&T leak with the new modem. It's a little slower though, but it DOES work. Screenie coming soon.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
A picture of the home screen and 4g loading Google.

Gonna go flash the root kernel now. Let's see how this goes.
[T-Mobile, Samsung Galaxy SIII] saranhai:
Everything working fine and dandy on my end. Even 4G data. Expect a possible ROM coming from me soon! :D
[T-Mobile, Samsung Galaxy SIII] saranhai:
Whoops forgot to add picture...
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Protip if you need root... Choose no knox build, boot successfully one time and flash the insecure kernel and boot up and you'll have working superuser.
[T-Mobile, Samsung Galaxy SIII] scifan:
So, this sounds very promising...

The question is... can you mux that build with the leak from above in this thread to also provide wifi calling?
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
One step at a time grasshopper. Maybe not though. I'm releasing a ROM in an hour.
[T-Mobile, Samsung Galaxy SIII] scifan:
Hey... I want it all... (live in a fringe area, and I really need to have wifi calling when I'm at home...)

Question is... what's broken (if anything) in the 4.3 leak...
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
As far as I can see, nothing lol. We just don't have Wi-Fi calling on 4.3 until it officially comes to our phones in the third week of November.
[T-Mobile, Samsung Galaxy SIII] calexchelse:
But will it be just for lte in November

---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------

And also, what's the chances of it leaking early of it is
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
And it wouldn't be just for LTE, unless they wanted to piss EVERYONE with a SGH-T999 off. Regardless, we're gonna get 4.3 lol.

Another leak happening? Not likely, we already have the t999 system dump thanks to mohan_kr he just couldn't release boot.img for safety reasons. AT&T idk how that happened, but it was a full leak without the modem. We d2tmo'ers have a modem. We have a fully working 4.3 build before AT&T did, which is kind of funny because it's their ROM. I do hope they get their modem soon though.
[T-Mobile, Samsung Galaxy SIII] calexchelse:
hate to say it but that is almost funny. oh well just a few weeks and then wifi on tw 4.3
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Wi-Fi on 4.3? It works fine for me...?
[T-Mobile, Samsung Galaxy SIII] calexchelse:
Sorry, meant wifi calling. My bad need new keyboard on computer and more sleep. Lol
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Lol all is good, I'm tired too. Can't stop playing with this ROM.
[T-Mobile, Samsung Galaxy SIII] calexchelse:
Have to be at work early but gonna stay up a little while and flash it
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Lol! You guys ain't wasting no time! Props for getting those At&t ports out so fast!

I've got a few more things I MUST catch up on,, but I will be resuming work on my end shortly. Again no promises. Haven't been able to get the T-Mobile one working yet and am not completely sure I will be able to.

Couple of things to clear up real quick:

The modem I posted is for the T999 only.

Will we get any T999V/L/N leaks? Who knows, only if we are lucky tbh. If anyone out there testing the leaked builds for any of our variants is interested, feel free to PM me and I can help get what we need pulled.

I think I should mention that the modem I posted is not from mohan_kr. I don't want him to get in trouble or anything because someone assumed it was him or gives false credit.

Wish me luck on getting something working for you guys! I'll keep you updated. :cowboy:
[T-Mobile, Samsung Galaxy SIII] calexchelse:
Thanks doc, last side kick, and the rest for your work.
[T-Mobile, Samsung Galaxy SIII] anil2653:
Very much thanks Doc

Wish you all the best for all new works on our devices
[T-Mobile, Samsung Galaxy SIII] gaore:
T-mobile S3 Android 4.3 release date will be Nov 25
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Source?

Sent from my T999L on PAC-man
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nov 24 per the thread in General.
[T-Mobile, Samsung Galaxy SIII] gordies.swc:
Im getting a "failed" when flashing UVDMD5. Im using twrp recovery.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Have you copied the recovery.log to sd after the failure? Please do so then post here.

Did you check the md5 to make sure the download isn't corrupt? Try redownloading.
[T-Mobile, Samsung Galaxy SIII] kingston73:
I'm currently trying to use this to restore my phone back to md5. I followed all the directions and odin'd the root66 file and Odin said it passed and everything seems like it worked, but it's now been 10 mins and it's still at the samsung logo and the led is blue and lit. Is this normal, should I just let it sit until it finalizes or could something have gone wrong?
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Is it still at the logo?
[T-Mobile, Samsung Galaxy SIII] kingston73:
It's been at the logo for nearly 30 minutes now. Something's definitely not right.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Sounds like a hard brick, except you can turn your phone on. Try UVDLJC firmware next? If not, I have no clue.

If ODIN didn't work, not sure what will.

Any ideas [MENTION=4081205]DocHoliday77[/MENTION] ?
[T-Mobile, Samsung Galaxy SIII] kingston73:
I'm redownloading the md5 root66 file and I'll try that again, and I'm also downloading the earlier ljc file and I'll try that if the md5 doesn't work again. I don't know WTF is going on with this.

EDIT: just got off the phone with tmobile, they are going to send me a replacement. Odin didn't work again, it says it works but the phone won't get past the samsung logo and it won't boot into recovery at all.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Did you wipe data after the Odin process finished?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Factory reset. Reboot. All you need.
[T-Mobile, Samsung Galaxy SIII] kingston73:
I can't get into recovery so I can't factory reset, unless there's a way to do it through Odin. Like I said, Odin gave me the green Pass, the phone started to boot and went through the Samsung logo , the green android rocket/T-Mobile animation, and then freezes on the last Samsung logo. I left it sit 30 mins the first time and did the Odin process a second time after pulling the battery and it still froze at the same spot.

So is there a way to factory reset I can use if it won't go into recovery? Or is it possible to flash twrp using Odin? Or some other option I don't know?

Edit: seriously, FML, I took my microsd card out so I could at least recover my pictures and managed to drop it into my couch. So now if I want it I'd have to rip open the bottom of the couch. This is just not my day...