yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] sbaeder:
I am also trying this even after reading things. I was originally on the S3Rx rom (based on the most recent MD5) http://xdaforums.com/showthread.php?t=2326763

Rebooted into download, and odin'd the test file listed above. Rebooted it, and to my surprise, all the apps and even the fact I use Holo Launcher was there in tact. Not sure things were properly rooted at that point, since SuperSU was gone...

But decided to flash the latest ODIN TWRP I had (2.6.3.0 I got yesteday I think somwhere here on XDA)... So shut off phone, bootoed into download, and added it. Reboot when as expected into phone. At that point, manually shut down and rebooted into recovery, and TWRP came right up.

Loading some new ZIPS on the sd card as I type...going to first try the SuperSU zip and then MAY go to Docs rom image or the DeKnox script...Not sure yet...

More later.

[edit 1] - installed the zip of SuperSU I found here on XDA (1.65) using TWRP - it died on the boot, but started to be updated from the PLAY store. Seems to be working just fine...

Scott
[T-Mobile, Samsung Galaxy SIII] ortind200:
so MrRobinson's latest 4.3 rom works for u.. sounds good.. but u mentioned the DeKnox script.. wat does that script do exactly?
[T-Mobile, Samsung Galaxy SIII] allendj81:
So if I Odin flash the stock 4.3 OTA update released by Tmo:

-It would also flash stock recovery or would it keep CWM?

-Would I lose root?

-Is there a way to root 4.3 official Tmo's update from scratch (meaning not having a back up or using any other method to keep root)?

I'm sorry if this questions are redundant, but with so much sharing of knowledge these post are really hard to follow :angel:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Re read the op. The sole purpose of root66 is to gain root.

Flashing recovery should be just fine.

I do agree that its hard to follow. Weve tried to reorganize thongs to make it easier, but it seems we msy need to repost about it every couple of days. Lol!

General 4.3 questions - q&a thread

4.3 opinion and discussion -General section thread

Rom questions go in rom threads as usual.

Info is scattered but I've been working on getting it gathered to put everything relevant in one place. Hopefully ill have it ready later tonight.....hopefully.
[T-Mobile, Samsung Galaxy SIII] ortind200:
so has anyone installed this rooted rom yet? any issues?
[T-Mobile, Samsung Galaxy SIII] rbarcenaslp:
If I flash this md5 4.1.2 on my parents gs3s will that take away their tmobile features? Itll stay the same right?
[T-Mobile, Samsung Galaxy SIII] ortind200:
why wont MrRobinson post a link to the latest 4.3 rom on the 1st page?
[T-Mobile, Samsung Galaxy SIII] anil2653:
I feel still it is to be tested and checked for properly working before he updates this link to OP
[T-Mobile, Samsung Galaxy SIII] truckerdewd:
So far, so good

I updated my wife's phone with this. After I installed it and it rebooted and started, I went back into download mode and used Odin to install newest TWRP recovery after installation and a reboot into the system then rebooted into TWRP and flashed SuperSU then rebooted. after the phone was up and running, got a message that SuperSU force closed so I tried to open it again and got the same message then another message saying it was downloading the SuperSU update from the Play Store. After it installed, I opened SuperSU and it told it needed to update binary so I accepted it and it installed fine then said I should reboot. Rebooted and everything seems to be running fine. Checked some apps that require root such as Titanium Backup and all seems to be working fine. I'm sure if any problems pop up, she will let me know immediately.
[T-Mobile, Samsung Galaxy SIII] ortind200:
sounds good. but can u try to install CWM to see it it works too?
[T-Mobile, Samsung Galaxy SIII] anil2653:
Thanks bro

That means updates provided by Mr Robinson is correctly working only with twrp because two successful installation done but cwm not succeeded
[T-Mobile, Samsung Galaxy SIII] Qverse:
As time go by

But of course. Times have change alot but NOt that far from what we see Hollywood movie . Try to recognize that Android Development is Free in a world where Freedom is challenged every second . I am one that still believe that if I PAID $600.00 - $700.00 for cell phone . I have the right to do as I please with it . XDA development to me Represent the FREE World

And The mention of Knox script (Customizable Secure Boot ensures that only verified and authorized software can run on the device) and SELinux provides an implementation of the Flask Flux Advanced Security Kernel for Linux. SELinux started as a kernel patch which was presented by the NSA to kernel developers during the 2001 kernel summit.

I am sure that as time going on We will see more of these things to come. This is nothing new :cool:

Sorry People , Just Ranting :cool:
[T-Mobile, Samsung Galaxy SIII] anil2653:
I too agree with you and we have to face lots of changes.

But to deny warranty oem can use efuse to blow up etc but in any case they should not cause any damage to system or software

It's a clear indication that Samsung is now on destructive attitude towards own customers who made it no 1
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
So directly after flashing the root66 you are sure you didn't have root?
[T-Mobile, Samsung Galaxy SIII] truckerdewd:
I didn't check. It didn't give me any notifications about root apps not working. After it updated SuperSU, I checked the root apps and everything was fine.

Sent from my wickedly awesome Galaxy Note 2 using my fingers. Duh!!!
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I didn't try root66, but I had the same issue with SuperSU fcs when I Odin'd 4.3 and attempted to root it.
[T-Mobile, Samsung Galaxy SIII] ThC23:
So this is through Odin right?

Confused, because people are talking about different recoveries on here.

Thanks

Powered by the SGSIII
[T-Mobile, Samsung Galaxy SIII] truckerdewd:
Yes it is through Odin.

Sent from my wickedly awesome Galaxy Note 2 using my fingers. Duh!!!
[T-Mobile, Samsung Galaxy SIII] sbaeder:
Same for me. With flash of the file using Odin, SuperSU had FCs. Odin'd a new version, let Play update it, and GOLDEN!...
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
But what file? The stock or root66. Root66 has the latest so there would be no newer version.
[T-Mobile, Samsung Galaxy SIII] LordPhong:
I didn't have time to look at the latest root66 file. Is the recovery replaced with the older version at all? Is the newer recovery the reason why we can't flash older ROMs?
[T-Mobile, Samsung Galaxy SIII] sbaeder:
Yes, the root66 version you posted above for us to test...While it may have the latest, something about it isn't quite right, and as soon as it boots, it would force-close. And IF I recall correctly, root didn't work... I recalled reading that someone else had similar issue, and odin'd an older version 1.65. So I tried that, and it didn't force close on boot, but PLAY wanted to do an auto update, so I let it. After next reboot, SuperSU new it had an update it could apply, and asked if it was ok to do that - I said yes, and things have been working well since then.

Not sure at all why the initial boot after the odin of your root66 version of 4.3 had the FCs on SuperSu...

---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------

no...there are changes in the bootloader and lower level firmware...you can replace the stock recovery...remember, that there are layers upon layers as well as alternate branches of code to make the phone "work"...
[T-Mobile, Samsung Galaxy SIII] LordPhong:
Sorry, I meant to say boot loader. I wonder if it's possible to just "recreate" Doc's leaked ROM by simply replacing the boot loader in the md5 tar file.

The only reason why I would want this is for warranty purposes since the old boot loader allows you to flash older firmwares and thus avoiding the warranty bit and use Triangle Away.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
If anyone can logcat that maybe I could see why root doesn't work on initial boot.
[T-Mobile, Samsung Galaxy SIII] rapatelrocky:
I had previously rooted using root66 method for 4.1.2 and installed OTA Rootkeeper. I upgraded to 4.3 via OTA. At first I installed CF-Auto-Root to try to root it, however SuperSU did not work as others mentioned. I ended up flashing the root66 test file and was able to successfully install it, however supersu continued to fail - finally re-flashed CF-Auto-Root again since the root66 image does not have Knox in it, and it worked!

My main reason for rooting was to use the Treve-mod wifi-tether but that still has issues even after re-installing.

Thanks for all the effort/work done to provide everyone all these capabilities - we do appreciate all the hard work put in!!
[T-Mobile, Samsung Galaxy SIII] Richcar:
Confirmed super su 1.43 and 1.75 not playing nice only super super su 1.65 seems to work well without problems
[T-Mobile, Samsung Galaxy SIII] ortind200:
hey, rapatelrocky.. u said u upgrated to 4.3 via OTA.. i did the same but my phone isnt rooted. in the same way u rooted ur phone, do u suggest that i first install root66 then use CF-Auto Root in order to get SuperSU to work?

is there any big difference between SuperSu 1.65 and 1.43/ 1.75?
[T-Mobile, Samsung Galaxy SIII] rayne127:
I didn't get a FC from SuperSU, but when I opened it, I got a binary not installed error and it told me to reroot. No root apps will run. I'm going to install the older version and see as that seems to be working for others. I did save a logcat when I opened SuperSU, it's rather large. Would you still like to see it?

EDIT: Flashing SuperSU 1.65 through TWRP works. Allowing the app to auto-update from the play store caused the app to install the updated binary which is now working fine for me.
[T-Mobile, Samsung Galaxy SIII] calexchelse:
This installs stock recovery correct?

Also, has any one found what recovery works best to Odin to ?
[T-Mobile, Samsung Galaxy SIII] rayne127:
This does install stock recovery. I've always used TWRP. It installed and worked fine for me just now through Odin.
[T-Mobile, Samsung Galaxy SIII] rapatelrocky:
Yes, I would use root66 first then CF-Auto-Root to get SuperSU working. I had the same issue as Rayne127 who mentioned SuperSU would say it is not installed. I could not uninstall it or install an older or newer version or the same version. Would not work until I did both root66 w/ test image and then installing CF-Auto-Root to get a working SuperSU.

Unfortunately the main purpose for rooting was wifi tethering and neither Treve-mod-wifi-tether nor the Wifi Tether Router will work.. (though the latter developers are very responsive, not sure whether they would be able to help).

EDIT: Important note - device status is "custom" now instead of "normal".
[T-Mobile, Samsung Galaxy SIII] xiehaibo:
yes supersu 1.65 can work now
[T-Mobile, Samsung Galaxy SIII] ortind200:
so let me get this right.. after u installed root66 and CF-Auto Root, u were then able to install supersu. being that the case, u still cant uninstall ur version of supersu and u cant install a newer version.. is this wat ur saying?
[T-Mobile, Samsung Galaxy SIII] rapatelrocky:
No - _before_ using combination of root66 and CF-Auto-Root in that order, I had the same situation as rayne127 (I had version 1.75) after OTA update. After that SuperSU is fine - version 1.75 is installed and working properly.

Order of things:

4.1.2 - rooted via Root66 - SuperSU working fine - 1.75 after updates working fine.

4.3 OTA update - SuperSU stops working with "not installed" error - same as Rayne127 (Rayne27?)

CF-Auto-Root instaleld - root sort of there - but not fullly SuperSU still gives same error. root checker fails.KNOX still there.

root66 test image installed - SuperSU still gives same error. root checker still fails.KNOX gone.

Re-installed CF-Auto-Root - SuperSU works , root checker clean

EDIT: Important note - device status is "custom" now instead of "normal".
[T-Mobile, Samsung Galaxy SIII] Perseus:
Good for you! Straigh out of Flash, Root66 didn't have supersu ? Can you describe bit more ?

Yes that's what I wondered earlier. May not be possible otherwise [MENTION=3355398]mrRobinson[/MENTION] would have commented on it.

All. Please note, I believe, after you flash this version you should not try to flash prior versions of Root66 or any other older firmware containing older bootloader. That has bricked the S3 of a friend of mine.
[T-Mobile, Samsung Galaxy SIII] ortind200:
hey rapatelrocky.. just to let u kno, i got the 4.3 update via OTA but im not rooted yet. so do u suggest that i install root66 and then CF-Auto Root, or, install CF-Auto Root then root66 then CF-Auto Root again like u did?
[T-Mobile, Samsung Galaxy SIII] rapatelrocky:
If you are ok with having no knox and status going to "custom", then I would do:

Flash root66 test image

then flash CF-Auto-Root

validate using root checker. That will get you working root - depending what you need it for. My only purposes were for disabling built-in apps and for wifi tethering, but wifi tethering still does not work.
[T-Mobile, Samsung Galaxy SIII] calexchelse:
Just to let op know, root 66 test works great. Supersu don't work. Spent 2 hours flashing and reflashing docs deodexed ROM. Finally worked. Cf-auto-root didn't work for me and I flashed it 3 times with odin.

And cwm recovery works great might I add
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Likely you've seen it, but I caught this article on our XDA hompage regarding fixing permission issues with custom recoveries: http://xdaforums.com/showthread.php?t=2532300
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
I'd like to try to get root working right out of the box.. So I'll post up one more test maybe today/tmr.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
That would be great. Thanks!
[T-Mobile, Samsung Galaxy SIII] ortind200:
i got a dumb question.. if u get ur phone rooted, why would u need supersu?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
SuperSU controls root.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Test 2

Again, use at your own risk. After flash this or the prior, do NOT flash back to an older version it seems to create bricks from phones. That being said:

Download :: root66_TMO_T999UVUEMJC_2.7z
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Tried this on someone elses phone and as far as I could tell it worked perfectly! Root immediately worked fine on both a dirty and clean install! Outstanding work as usual [MENTION=3355398]mrRobinson[/MENTION]! Thanks!

I understand that people who have not updated will want to stay away from this, but if you've already updated, and are willing, please give it a test run and report back.

What I'd really like to know, is if rooting like this will keep from tripping the warranty bit in the same way it doesn't trip the flash counter. The only way this can be tested is for someone who has not updated, but is willing to anyway even though you can't go back to 4.1.2. (Or if you've updated and can verify the counter and bit are zero)

So if you are going to update anyway, and you understand all that this means, I hope you'll consider flashing the above root66 firmware and share some information for us!

Namely, you'd need to check the flash counter is zero, then after flashing, boot straight into download mode and let us know exactly what you see.

Thanks!
[T-Mobile, Samsung Galaxy SIII] rakeshchn:
I am ready to try but i am still on the original 4.0.4 firmware with root and TWRP. Does it matter?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Yes a couple more reports back and I'll add to OP.

Should be fine as this will fully replace TWRP and the 4.0.4. This isn't like an OTA upgrade. After flashing you will want to boot to the stock recovery and do a full factory reset otherwise it won't boot coming from 4.0.4
[T-Mobile, Samsung Galaxy SIII] rapatelrocky:
I had flash counter 2 after the original root66 test + CF-Auto-Root install. Used triangleaway to reset counter to 0. It stayed 0 and after flashing this newer root66, it stayed 0. Warranty bit is 1 though. The update works fine however. Note I had wiped before trying this 2nd test file and the wiping had helped fix some issues of slowness and battery issues. The wipe was well before flashing the 2nd image though - was using the phone for various things before flashing this 2nd image. This 2nd image is nice and fast and stable so far.

Off topic but FYI after wipe in 1st test image, I got wifi tether router working and it continues to work fine after 2nd image.
[T-Mobile, Samsung Galaxy SIII] ortind200:
hi rapatelrocky.. 2 questions here:

1) i'll install root66 + CF Auto Root in that order. u mentioned wiping. i havnt flashed in yrs, so much of wat i knew is gone. when should i wipe? and wheres the option to wipe?

2) i dont understand when u say the counter was 0 but the warranty was 1. if the counter was 0, why is the warranty 1? i never messed with a counter before since im new to this. but does "warranty" show up on it?
[T-Mobile, Samsung Galaxy SIII] sbaeder:
Don't think the CF Auto Root works (or is necessary) the whole warranty bit is the whole bane of this update - READ (I know there are a lot of posts) the full thread to see what it is and why it is a PITA
[T-Mobile, Samsung Galaxy SIII] rapatelrocky:
Just to be clear, I am new to flashing - beyond flashing root66 originally for 4.1.2 to use tethering, I had not done much (though being extremely unix/linux technical, I could do more if I had the info).

I am no expert on wiping - this is the first time I wiped, but that is basically just going back to the clean installation of the ROM that you have installed - as if you installed it new with nothing else for the first time. What I can say is that wiping definitely will help speed and let you re-install apps that you only want and can help clean up slowness issues from bad apps. If you are on a fresh 4.3 install and have not installed much at all, wiping may not help much, but almost all the custom ROM install instructions say to wipe data.

I would only use root66 with the 2nd test image at this point - that should work perfectly if you need root and want to stay on stock firmware. Others confirmed this 2nd version works well. No need to odin the CF-Auto-Root after that. i am very happy with the speed now (the wiping helped for me since I never wiped in the year+ I have had it).

About the counter/warranty - I wasn't concerned about that but I checked since it was asked about. The root66 (2nd test image) should not increment the counter given it stayed at 0. Warranty bit I am not sure how it is used but I went to download mode and checked as doc mentioned just to provide the information. Not sure when it went to 1 instead of zero, but it is 1.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
No, Just do the root66, boot to recovery, and chose the option to factory reset/wipe. Reboot phone. Profit.
[T-Mobile, Samsung Galaxy SIII] ortind200:
thanks man.. will do.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you don't mind, after flashing boot back into download mode and let us know if the Warranty bit is tripped to 1?

Thanks!
[T-Mobile, Samsung Galaxy SIII] Wicked68:
So, is it ok,to install the new root66 with Odin or what?

Zapped form Samsung Galaxy S3, Rooted (Stock)
[T-Mobile, Samsung Galaxy SIII] J3ffG1:
Fashed root66_TMO_T999UVUEMJC_2.7z

Used Odin as op instructs. Seamless from rout66 412. No warnings or errors, all seems good.

Thanks
[T-Mobile, Samsung Galaxy SIII] Wicked68:
It's fine to flash from 4.1.1 right? I never updated to 4.1.2

Zapped form Samsung Galaxy S3, Rooted (Stock)
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes shouldn't be an issue. Just check your baseband after all said and done. It should reflect UVUEMJC
[T-Mobile, Samsung Galaxy SIII] ortind200:
but were u able to install the latest version of supersu? thats wat seems to be the problem.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Its been real, but I got a Note 3 today, so won't see much of me in this section of the forums anymore. Still gonna update my S3 to 4.3 before I sell it, for a little profit. Now on to root my Note 3
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Unlock it first! Will be able to sell to a larger consumer base.

Have fun with the note3! (Thinking bout that myself since its zero down!)

---------- Post added at 05:56 AM ---------- Previous post was at 05:56 AM ----------

Don't update SuperSU for now.
[T-Mobile, Samsung Galaxy SIII] ortind200:
but as rapatelrocky suggested, CF Auto Root should be installed after root66 test image in order to get supersu working.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
That was probably on the first test build, he confirmed its not needed in the new one. If you are having problems you may want to try, but it will likely go back to the point where root would randomly stop working if you do.
[T-Mobile, Samsung Galaxy SIII] rapatelrocky:
As we keep saying - the 2nd root66 works fine - no other install is needed and would probably cause more problems. Otherthan DocHolidays suggestion to wipe after installation, nothing else should be needed. Very happy with the 2nd image. It is very smooth and fast.
[T-Mobile, Samsung Galaxy SIII] ortind200:
sounds good! as long as supersu works with no probs.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
quick question guys. im gonna flash this a little later on, but ive never flashed root66 before and dont see it mentioned regarding this latest 4.3 release; has knox been removed or is root injection the only thing done to this rom? is it still a no go to update su?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
With the latest image in the OP:

knox has to be removed for root to work. So knox is gone and root is there (otherwise stock). There should be no reason to update su or SuperSu after flashing the latest in the OP.
[T-Mobile, Samsung Galaxy SIII] reapur:
Thanks MrRobinson and everyone who made another release happen smoothly.

I installed this last night just like all the other images and it worked fine. A caution to the newbs, this takes a little longer to boot the first time, kinda makes your heart beat a little faster for a few minutes :)

The amount of bloat that samsung has included is truly sickening. is there a faq on which sammy apps I absolutely need, I'd like to remove them all.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
just an update guys...was on 4.1.2, reset counter via TA, flashed root66...warranty bit is 0

EDIT: supersu updated from the play store to 1.80 before i could stop it (forgot to turn off auto-update). confirmed after reboot su still working fine
[T-Mobile, Samsung Galaxy SIII] calexchelse:
Yes the warranty won't trip until you odin custom recovery
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Keep an eye on it. I think the problem was after a while root apps would no longer have root.

I think there is more than a recovery that can trip this bit. But is good to know root66 on its own does not!
[T-Mobile, Samsung Galaxy SIII] calexchelse:
True, I think cf-auto root trips it also

---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------

Of course, it don't matter if warranty is tripped on mine, screen has major issues
[T-Mobile, Samsung Galaxy SIII] ortind200:
just to make sure, the working root66 image that actually works is on the 1st page, correct? so as to not be mistaken by the test file posted like 6 or 7 pages back... right?

root66_TMO_T999UVUEMJC_2.7z is the working image, right?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
correct. Use the one in the OP, labeled as _2 as you showed.
[T-Mobile, Samsung Galaxy SIII] TheArtiszan:
So the new root66 file does not have Knox in it?

But still has the new bootloader that will have the flag in it?
[T-Mobile, Samsung Galaxy SIII] calexchelse:
Right
[T-Mobile, Samsung Galaxy SIII] matrixzone:
[MENTION=3355398]mrRobinson[/MENTION] any plans for updating the Root ROM for d2att devices?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Is there a new stock image up somewhere?
[T-Mobile, Samsung Galaxy SIII] ortind200:
installing CWM will not trip the counter?? are u sure abt this? i thought that installing any custom recovvery will.