yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] swipermusic:
I have just updated my I9300 to XXELL4 through Kies and of course it has unrooted my phone. I used CF6.4/Odin to root before, do I do this or is this new root better or different? Any help appreciated.
[Galaxy S III Original Android Development] HellcatDroid:
Different, yes; Better, no (this one actually tends to kill my /data due to it being encrypted, it just did it again - I still want an answer to why it needs to touch /data at f*cking all, but CF doesn't seem to care too much).

The only real difference is that it doesn't come with CWM recovery anymore.
[Galaxy S III Original Android Development] swipermusic:
Think I may root with 6.4 again thanks for answer

If I did try the new root would I have to factory reset first to remove 6.4?

Forget that question have done some more reading!
[Galaxy S III Original Android Development] swipermusic:
Just one question. My binary count is now 0 and custom official. The only thing is my status is still modified. Can I get this back to "normal" and will it stop me getting OTA updates in the future?
[Galaxy S III Original Android Development] Zam1000:
Are you rooted? If there be any root files there will be modified. Unroot flash official ROM, factory reset.

I think is was like this, correct me of I'm wrong. You can read it in several thread.

Sent from my GT-I9305.

---------- Post added at 04:59 PM ---------- Previous post was at 04:56 PM ----------

http://xdaforums.com/showthread.php?p=29496282

Sent from my GT-I9305.
[Galaxy S III Original Android Development] Jumbo78:
In my opinion is factory reset enough. I have rooted through CF auto root, then triangle away - still modified >factory reset and everything OK. If he has counter 0, then kernel is STOCK. Maybe, has another modem or CSC file. For Normal status everything must be as STOCK
[Galaxy S III Original Android Development] 30adi:
I had same problem, status was modified because i installed setcpu. After uninstal and reboot status was normal. So...some apps may be the problem
[Galaxy S III Original Android Development] Tyrigi:
how can i install cwm after used this cf auto root?
[Galaxy S III Original Android Development] rugolt:
Try PhilZ Touch Recovery (Extended CWM). You can flash it to the recovery partition of your S3 with Odin or Mobile Odin.

See my signature for link.
[Galaxy S III Original Android Development] strikoo:
http://xdaforums.com/showthread.php?t=1719744
[Galaxy S III Original Android Development] thegh0sts:
this ok with S3s with 4.1.2?
[Galaxy S III Original Android Development] strikoo:
Yes, tested
[Galaxy S III Original Android Development] DeHAWK:
Samsung just made an OTA update on my GT-I9305. Now it's JB v4.1.2...Nice:)

Lost root...SU and BusyBox still present but no root permissions. Used CF-Auto-Root before and might need to flash it again using PC Odin. Has anyone done this with this new OTA update?

Mobile Odin says unknown device...

My best regards to all of you.
[Galaxy S III Original Android Development] rugolt:
Just use Exynos Abuse for rooting purposes... could'nt be easier.
[Galaxy S III Original Android Development] vasp3690:
id like to add, practically a baby in rooting,

just did this auto root installed all the nice apps, like mobile odin, triangle away, root explorer and i have now rooted my S3 to get rid of that dispicable keyboard which was causing me problems. On 4.1.2

still too afraid to do anything more though! Great stuff

quick question: Still can update through Kies i suppose and i would just have to re-root again after the update, right?

Does that also mean that to root again i would have to wait for an update on the md5 file to put to odin?
[Galaxy S III Original Android Development] DeHAWK:
Worked perfect. thx.:)
[Galaxy S III Original Android Development] strikoo:
Yes. You didn't hove to root, you could just install another keyboard
[Galaxy S III Original Android Development] BlackMonkey:
nice! working perfect with 4.1.2 XXELL5 official vodafone rom. :)
[Galaxy S III Original Android Development] vasp3690:
My phone had a problem that every after restart the keyboard switched back to the samsung one and samsung technical support told me that this os the way it is! So I got rid of it! Since samsung cannot fix my phone. I know others don't have this issue but it seemed to me that samsung would be unable to help.

Funnily enough I went and bought a new phone, updated it to 4.1.2 with kies and it did exaclty the same!
[Galaxy S III Original Android Development] Tovagulet:
Worked great!

UBDLI2
[Galaxy S III Original Android Development] vasp3690:
Did you just read what I wrote? Installing another keyboard meant nothing as everytime I restarted I had to go back and re choose the default...

I'm having to repeat myself so much we are getting off topic here...
[Galaxy S III Original Android Development] WarioNeila86:
Working fine!!

Very good job Chainfire!!!

Regards.
[Galaxy S III Original Android Development] dwmw2:
My phone no longer boots

I have a GT-i9300, which was running Jelly Bean 4.1.1. I upgraded it to 4.1.2 (I9300XXELL) and it booted happily, accepted the password for the encrypted storage and was working fine... except for not being rooted of course.

I then installed CF-Auto-Root from CF-Auto-Root-m0-m0xx-gti9300.zip, which happily restarted, showed me the scary red droid... and if I read it correctly it told me it was *formatting* my data partition. Now when the phone boots up, it doesn't like my password for the storage. It just keeps telling me to 'try again'.

Did it *really* format my data partition without asking me? Or do I have some chance of recovering? Yes, I did a full backup before attempting this, but restoring from that is *painful*...
[Galaxy S III Original Android Development] Serdxx:
well, is it normal that super su not shown on desktop?

it just shown on application manager..
[Galaxy S III Original Android Development] furious_88:
I used Odin 1.85 and follow the instructions to root my phone, it says pass. But when it reboot , I can see smsung, then it hangs and only shows blue led ,and 2 bottom white led.

What hppen , what should I do? Btw mine is GT-i9300 first batch. Jelly bean 4.1.1
[Galaxy S III Original Android Development] Gainn:
try flashing it again, and if not then flash your regions stock version from the thread in general section.

boot it once and then retry auto-root.

http://xdaforums.com/showthread.php?t=1646610
[Galaxy S III Original Android Development] confar:
i have root with this method, but system is modificated

exists anothet method?
[Galaxy S III Original Android Development] Serdxx:
anyone please?
[Galaxy S III Original Android Development] Gainn:
install it from the play store.
[Galaxy S III Original Android Development] vasp3690:
I have a question.

I reflashed the stock firmware and unrooted the phone.

However the mobile Odin pro alk is now permanently logded in my apps and wont delete even after a hard reset. I do have the official Samsung firmware now and counter zero.

Is there any way to remove the mobile odin? I used it to unroot.

Thanks
[Galaxy S III Original Android Development] jonny68:
My phone died a sudden death and is in for repairs but whenever i get it back I'll have to root again , last time I rooted I had a laptop but now I just use Nexus 7,is it still handy enough to to root because I've noticed some of the instructions mention using computer too.
[Galaxy S III Original Android Development] OrangeRafi:
can I use CF-Auto-Root to root a device running on Samsung stock 4.1.2 LLA (BTU) firmware? they say the new ROM has a new bootloader included.
[Galaxy S III Original Android Development] Taptapdude:
Yes u can
[Galaxy S III Original Android Development] Gainn:
Just updated to 4.1.2 ELLA and then CF-Auto Root + Triangle Away and all is good. :)
[Galaxy S III Original Android Development] vasp3690:
Can I root a locked phone to a network?
[Galaxy S III Original Android Development] strikoo:
Ofc.
[Galaxy S III Original Android Development] vasp3690:
Thanks
[Galaxy S III Original Android Development] siavash_Skh:
Dose triangle away work on ELLA ? Some people report problem with it. Did you try it ?
[Galaxy S III Original Android Development] Gainn:
had no issues so far.. device still shows as modified, but its always done that since jelly bean came out. counter shows as 0 though.

Apparently there is a way to get rid of the modified status, but you have to use titanium to freeze something. not got around to trying that yet.
[Galaxy S III Original Android Development] siavash_Skh:
If after using triangle away, I directly go to download mode and flash official ELLA the counter stay az 0 and show official?
[Galaxy S III Original Android Development] Gainn:
after a reboot it shows as 1 now, but all says official. device status is still showing as modifed in the settings.

Guess we'll have to wait till someone figures out how to bypass SysScope at boot.
[Galaxy S III Original Android Development] siavash_Skh:
I think this should be the only way for now.

Maybe in future the new version bypass the this checking.
[Galaxy S III Original Android Development] hanaxxaru:
can i just flash cwm recovery and flash this to gain root?
[Galaxy S III Original Android Development] briteway:
OK, how long does the flashing procedure take after plugging the phone and clicking start in Odin?

It seems like it's stuck on the green Android saying "Downloading... Do not turn off target!!" It's been sitting there now 15min.

I have an I9300T and rooted it a long time ago, then updated the firmware few months back via phone and lost root. Now on the download page my phone reads GT-I9300 without the T at the end and flash counter is 1. I wanted to install CF-Auto Root so I could gain root access again and run Triangle Away so I could return the phone for warranty purposes (crackling speaker while on a call).

This is what's on Odin:

<OSM> CF-Auto-Root-m0-m0du-gti9300t.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> recovery.img

Now it's been 20 minutes and nothing has "moved." Any help is appreciated.

---------- Post added at 05:29 PM ---------- Previous post was at 04:56 PM ----------

Went back reading some posts and found this one by Drew. Perhaps it should be included in the first post. Big THANKS Drew.

I ended up disconnecting the phone after 30 mins on download page, pulling out battery and restarting, tried 3 times before finding the above post. Did all that and tried again, worked flawlessly, flash counter at 0. Just to let everyone know (if you're having same issues), it only takes a few seconds to flash so if it sits there for longer than a minute after clicking START in Odin, something's wrong.

Now I'll upgrade the firmware to the latest stock JB, back up everything with My Backup, factory wipe and take it back and hopefully this speaker issue is sorted out.
[Galaxy S III Original Android Development] andreivibefm:
hello.. pls help me. I have this error when I try to root my phone:
[Galaxy S III Original Android Development] Taptapdude:
Which version of odin is this
[Galaxy S III Original Android Development] andreivibefm:
Odin3 v1.85

EDIT: oh.. my bad. Kies was open when I tried to root.
[Galaxy S III Original Android Development] Taptapdude:
Ahhh
[Galaxy S III Original Android Development] shahar2k9:
LLA stock?

Does ir have the new bootloader?

Does the cf-root works on the new bootloader?

Thanks...

EDIT:

CONFIRMED, works like a mother...
[Galaxy S III Original Android Development] siavash_Skh:
Hi

AndreiLux Said that the recoveries has bug for Sudden Death. If I flash CF-Auto-Root on the XELLA stock ROM, It wont change anything about stock recovery ?
[Galaxy S III Original Android Development] 0mega007:
Yes, CF-Auto-Root includes a SDS non fixed stock recovery and will replace your fixed one, maybe Chainfire will change the recovery to the fixed one in the next version.
[Galaxy S III Original Android Development] itfast:
i've followed the second procedure.... everything went fine. the phone has been restarted properly but suddenly after the root permission, the phone restarts itself twice... first time it returns on the screen, second time, the phone remains black. with the 2 buttons at the bottom (left menu/right "return") highlighted.

what happened ? how do i come back ?

thanks
[Galaxy S III Original Android Development] itfast:
I've downloaded my stock rom and flashed it back and lost the root. should i try the first procedure ? thank you for your help and support. if you wish i can send the picture of my rom .
[Galaxy S III Original Android Development] ZaKaTRoN:
There is an important bug en emmc, and stock kernel after ELLx fix this issue.

So, my question... is safe to use CF-Auto-Root?

I don't want to root my kernel with this root and lost the emmc fix.

I think is safe this kernel... but i want to be sure.

Thanks!
[Galaxy S III Original Android Development] heara:
+1
[Galaxy S III Original Android Development] skorzo:
+1
[Galaxy S III Original Android Development] wooptarik:
+1
[Galaxy S III Original Android Development] ZaKaTRoN:
I think the only one who can answer is Chainfire ...

I have ask this question on Chainfire's twitter...

I'll write his answer
[Galaxy S III Original Android Development] 0mega007:
All that is needed is that Chainfire replaces the recovery in CF-auto root with the new ROM fixed one
[Galaxy S III Original Android Development] skorzo:
So .. is there any way to flash only the new recovery via ODIN and replace the recovery included in autoroot ?
[Galaxy S III Original Android Development] ZaKaTRoN:
Perka said me this answer on I9300XELLC thread.

I thought the root was in the kernel... So, if root is on system, root is safe.

What do you think?
[Galaxy S III Original Android Development] trionic:
I was about to post that answer too. Then the sudden death solution is still working i suposse
[Galaxy S III Original Android Development] ZaKaTRoN:
I hope that...

You and me are spanish, and speaking english on forums "¡Manda huevos!", hehe.
[Galaxy S III Original Android Development] trionic:
Jaja cierto. I hace just read in another forum that as the recovery used on this autoroot is previous to the fix released the sudden death issue is still there. according to what i have read there should appear a new autoroot with the new stock recovery.

Sorry if it does not make sense! My english is what it is
[Galaxy S III Original Android Development] 0mega007:
Not in recovery, Cf auto root overwrites with an old recovery
[Galaxy S III Original Android Development] ZaKaTRoN:
Then... any way to root and be safe?

Or we've to wait for chainfire update cf-auto-root?
[Galaxy S III Original Android Development] :
Flash Cf auto root, then philz recovery, then perseus kernel.... This is a "safe" combo apparently, and what I use.
[Galaxy S III Original Android Development] montage mahal:
Or try this. Its the best solution i've found.

http://xdaforums.com/showthread.php?t=1347899&page=238
[Galaxy S III Original Android Development] skorzo:
Good idea

Please find my reply on that thread.

Regards....

---------- Post added at 11:11 PM ---------- Previous post was at 11:08 PM ----------

Why do you flash perseus kernel?

I thought that stock LLA or LLC kernels were safe too ....

Thanks
[Galaxy S III Original Android Development] suspktu:
Why do you guys say that the CF-Auto-Root changes the stock recovery? Iask this question because in the first post Chainfire writes :

Installation and usage

Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Andr
[Galaxy S III Original Android Development] beardymarrow:
Cf-auto-root will install a stock recovery. If you've updated to a different non-stock recovery or a newer stock recovery (if such a thing exists?) it will get over-written by the version of stock recovery that is included in cf-auto-root.

Click thanks if I've helped. Sent from my GT-I9300 using xda premium.
[Galaxy S III Original Android Development] luka_w:
+1
[Galaxy S III Original Android Development] sathkartha:
It does say "modified".
[Galaxy S III Original Android Development] jb.traveller:
You could use Toolkit 5 to do a nandroid backup / retore.
[Galaxy S III Original Android Development] kaynpayn:
Confirmed, followed instructions, got root, a +1 counter and plenty of info saying "custom" and "modified". Not a yellow triangle in sight though :D

triangled away and my download mode now says:

"Odin mode

Product name: GT-9300

Custom binary download: no

current binary: Samsung Official

Syste status: Official"

Rooted on stock ICS.

Thank you, will donate as soon as my banking system allows it (they give me hell with any online related stuff)

Quick question plz:

I found this .eu.chainfire.triangleaway.flashkernel.i9300 file in my /sdcard folder. Do i still need it or can i delete it?
[Galaxy S III Original Android Development] Gainn:
Just got the 4.1.1 JB OTA update (JRO03C.I9300XXDLJ4) and wanted to make sure this is ok to use as all the other posts are referring to ICS.

thanks.
[Galaxy S III Original Android Development] cbeckstein:
What is Toolkit 5?

Probably a PC / adb solution that I cannot use on the go, right?
[Galaxy S III Original Android Development] DroidRevenge:
It is not confusing if you know a liitle about this argument.

Sorry if you are so susceptible, but 1st post is more then clear. Chainfire is not a noob (ABSOLUTELY!!!!) and he explain well what he does.

Try to learn before become so susceptible.

bye
[Galaxy S III Original Android Development] saintsinner25:
-_-.

Sent From My GT-i9300 ;)
[Galaxy S III Original Android Development] jb.traveller:
I should have said Samsung Galaxy S 3 V 5.0 toolkit . Goto the sticky here.
[Galaxy S III Original Android Development] MIKEMON:
NO!!!!
[Galaxy S III Original Android Development] donalgodon:
I really, really miss the CWM app!

It was so nice to be able to use it to name a backup and start the process and walk away and have the phone completely reboot on its own when finished!

Manually, naming backups isn't so easy, and your phone stays in recovery when nandroid backups complete. I know you've said that you rely on Titanium Backup for your backup needs, but there are times when this won't be a complete solution for restoration in the event of corruption from experimenting with a flashed .zip or mod, etc. Nandroid restores have saved my bacon lots of times from tinkering around with mods.

Is there any chance you could update the CWM app to work with JB ROMs, Chainfire?

Make it a paid app, if you need to. I'd buy it in a heartbeat! I'm sure I'm not alone here. The ability to simply launch the app, name your backup, and have it boot into recovery for you, start the backup, and then reboot when finished was just too perfect!

I miss it, and I'd gladly pay to have that convenience back again. :)

If there's any way it's feasible for you, I hope you will consider updating the CWM app.
[Galaxy S III Original Android Development] saintsinner25:
Caeser? :P

Sent From My GT-i9300 ;)
[Galaxy S III Original Android Development] KennyLegend:
Dude... CF root v6.4 works with jelly bean. It contains cwm recovery and app.

Chainfire just means he won't be updating that version with cwm.
[Galaxy S III Original Android Development] donalgodon:
Are you saying that the CWM app actually works with JB?! :confused:

I've not seen it work properly. If you mean that this one works:

http://xdaforums.com/showpost.php?p=27049380&postcount=3

I disagree.

Did I miss something?
[Galaxy S III Original Android Development] Dreamweaver:
Chainfire saved my life. Will buy you some beer now :o :p [GT-I9305] works perfect, also Triangele Away
[Galaxy S III Original Android Development] saintsinner25:
Yeah it doesn't work.

Sent From My GT-i9300 ;)
[Galaxy S III Original Android Development] IamIrene:
Get supersu + stock recovery

But I don't understand why need stock recovery ?
[Galaxy S III Original Android Development] ShironLive:
CF root v6.4 does work with Jelly Bean if you do it this way :

http://xdaforums.com/showpost.php?p=33124569&postcount=1300
[Galaxy S III Original Android Development] donalgodon:
Nobody said that CF-Root does not work.

I said that the CWM App does not work. If you use it, you get this warning:

I'm asking Chainfire if he'd consider updating it so that it will work properly, even if he's gone away from permanent recovery support, etc. (as the OP clearly states) because the features that the CWM app offered are worth paying for, IMO.
[Galaxy S III Original Android Development] ykkfive:
for the modified status thing, it is not due to rooting your devices solely. i had studied the app Samsung uses to identify the status and found that if any rule specified occurred then it will report as modified. one of the rules they use is to check if there are any process running by root. so most likely if u rooted the phone and have init.d supports, or if u mounted the system partition as rw, etc, then the status will become modified.

so rooting doesnt necessarily means modified. also the identification process or result can be hacked/prevented if u wish
[Galaxy S III Original Android Development] donalgodon:
How can it be prevented? I read that it was a background process that Samsung implemented. I figured it could be frozen or killed, but I've not seen how.
[Galaxy S III Original Android Development] brouwerchris:
Info from RootSu thread on SDS : Recovery has its own kernel that has been updated by Samsung in XXELLA release.Use of this stock XXELLA recovery is required to be SDS safe.If CF-Auto-Root installs an older sock recovery,how/where to identify your stock recovery version.

After installing XXELLA ROM through Odin PC version, I rooted through CF-Auto-Root,after that I flashed stock XXELLA recovery through Mobile Odin Pro. Where to find your stock recovery version. In Cache > Recovery > Last-Log?:confused:
[Galaxy S III Original Android Development] 0mega007:
Does any 32GB S3 has VTU00M 0xf1?
[Galaxy S III Original Android Development] skorzo:
That sounds VERY good.

But, How did you flashed stock XELLA recovery through Mobile Odin Pro?

I dont understand what you say about Cache>Recovery etc....

Can you please explain how to get and flash the XXELLA recovery?

THANKS
[Galaxy S III Original Android Development] trionic:
I am interested too...

Thx.

Pd: by the way, any plan to update cf autoroot with the new stock recovery?
[Galaxy S III Original Android Development] brouwerchris:
Download stock XXELLA ROM on Sammobile,place it on your internal or external card.Use Mobile Odin Lite/Pro to flash only the stock XXELLA recovery by clicking recovery and selecting XXELLA ROM (want the stock XXELLA kernel as well? Click on kernel and select XXELLA ROM ),then click flash firmware,this way Mobile Odin will only flash the XXELLA recovery ( and kernel if required )

.
[Galaxy S III Original Android Development] trionic:
Thanks, I'll do that. I hope to keep root. I will tell later

Thx again!
[Galaxy S III Original Android Development] luka_w:
guys, maybe I don't get it, but is it the Samsung's bug is in the old/prev stock recovery?
[Galaxy S III Original Android Development] confar:
In htcmania says that default restoring change system to normal and then ota works.

Enviado desde mi GT-N8000 usando Tapatalk 2
[Galaxy S III Original Android Development] danarama:
No. The bug is in the eMMC firmware, but the fixes (workaround) are in the Android Kernel and the Recovery kernel.

Unfortunately the recovery with CF-Auto-Root, predates these "fixes".

I've attached the most recent (I think) ELLC Recovery for Chainfire, if he wants to update.

dan@dan-Latitude-E6410:~/Documents/Boot$ grep -a -i VTU00M ELLC_recovery
VTU00M<4>%s: movi operation is failed
dan@dan-Latitude-E6410:~/Documents/Boot$ md5sum ELLC_recovery.img
97fdda63a5e00c56f11ca104c6f810fc ELLC_recovery.img