yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
About this request, can you or someone find a cherry pick for this center clock so I can add it provided that it's a configurable option? I don't want to add it if it can't default to being normal and be optionally enabled in settings.

EDIT: Waiting to confirm this so I won't build tonight just so I can try to find this and add it in but if someone requests it they should provide a source I think.
[Samsung Galaxy Nexus] tiny4579:
From rootzwiki:

It makes me wonder if it's a good idea reading CM's comments about this especially about it potentially breaking functionality. At least with the battery bar, it was trivial to merge and didn't have the risk factor and it was just CM not liking it. Thanks for the info though.

I won't do this in it's current form do to the risk factor and future maintenance issues of this abandoned change.
[Samsung Galaxy Nexus] tiny4579:
New build up. No center clock as I initially thought earlier tonight but that's something I'll consider adding in a future build.
[Samsung Galaxy Nexus] kmcrane:
I knew you would still build, you really wanted to.. :D After all the I/O talk today, and a new build from Tiny, it's been a good day for Android. :beer: Profit!
[Samsung Galaxy Nexus] nitsua98:
Hey tiny, just flashed your build, buttery smooth. Just have a question: should I change my dalvik heap size to 384 as stated in that code edit or w/e it's called.
[Samsung Galaxy Nexus] tiny4579:
Leave it at 256. That is what it was on GNex on 4.1.2.
[Samsung Galaxy Nexus] zoomy942:
Does this build include your kernel? The previous one didn't if I remember right.
[Samsung Galaxy Nexus] bustedukulele:
It doesnt. But I wish it did.
[Samsung Galaxy Nexus] carpenter311:
I just noticed the same thing. ROM seems really good though. Thanks tiny.

---------- Post added at 06:56 AM ---------- Previous post was at 06:55 AM ----------

Fast!
[Samsung Galaxy Nexus] zoomy942:
Yeah. Its no big deal and easy enough to flash his kernel. Just curious about it not being included.
[Samsung Galaxy Nexus] tiny4579:
I switched to the CM kernel in the previous build as there were tethering issues in the build before that. Also in doing so, since I was including a hostapd file with the kernel with the newer WiFi drivers, when switching back to CM's kernel I can revert to the source built hostapd file. Also, this allows better compatibility for users on WEP.

Really if it weren't due to the tethering issues previously, I might have not switched to CM's kernel. What's funny though is I flashed my kernel on top of that build (same kernel as was included) and tethering worked (well at least it started up).
[Samsung Galaxy Nexus] zoomy942:
Thanks for the info. Awesome.
[Samsung Galaxy Nexus] parkson:
Is camera force-closing for anyone else when taking a picture? Clean flash, tried cache/dalv wipe, fix perm...
[Samsung Galaxy Nexus] omniatic:
Yup, camera f/c's for me, too.
[Samsung Galaxy Nexus] zoomy942:
You guys using gapps camera or the cm/built in one?
[Samsung Galaxy Nexus] parkson:
Used the package tiny posted in op/cm cam
[Samsung Galaxy Nexus] omniatic:
Gapps. Didn't have a problem with it up till now.

Sorry...stock 03/01 gapps.
[Samsung Galaxy Nexus] gkaurin:
FC on me as well, dirty from 5-6 to latest, using latest gapps. Did flash 4.01 old wifi kernel. Could this have anything to do with Google pushing updates through play, I know I had to use TB to remove talk just to get hangout because play showed hangout already installed. Just a thought.
[Samsung Galaxy Nexus] kmcrane:
Fc on me too. I used the gapps tiny has on goo with no camera and tiny's new wifi kernel. Same gapps and kernel I used on his previous build. No issues then.
[Samsung Galaxy Nexus] gkaurin:
Ended up wiping and reloading. Superwiped 3 times, loaded latest tiny CM, loaded gapps 0301. Tried camera FC when taking pic, reboot try again FC on taking pic. the FC is the gallery and when you go into Gallery you can see that the pics were taken but the pics are blank.

Leaving on vacation tomorrow morning and any help with this before leaving would be great. If it isn't figured out I will just go back to 0506 or to mmuzzy. Love the ROM and as far as I know nothing else is not working. I know that 0506 camera was working for me.

Thanks for all the hard work!
[Verizon Samsung Galaxy S III] kgirlx:
Thanks might have to do this on my wife's phone
[Verizon Samsung Galaxy S III] ostap027:
I think that the easiest way to root any Samsung Devices - Samsung Toolkit
[Verizon Samsung Galaxy S III] scheirere:
I'm not having any luck with this. I've followed the instructions step by step and when I flash a custom ROM, I get the dreaded yellow triangle of death apon rebooting. There were some other files mentioned in the links. Do I need to unzip those at some point?
[Verizon Samsung Galaxy S III] droidshadow:
sorry i have been away

Okay i am so sorry for the late response I have been away and very busy. This tutorial is how to root your samsung galaxy s3 (verizon) model sch-i535 because you need to unlock the bootloader for that specific model.

Now you mentioned that when you try to flash a custom rom you get a yellow triangle of death....

Have you unlocked the bootloader?

Is your phone already rooted? Are you trying to flash a custom rom or are you still trying to root your phone?

I hope you have already resolved your issue but if you haven't I would be more than happy to try and help you out.
[Verizon Samsung Galaxy S III] jmxc23:
How is it any easier then the other guides for jelly bean? Here you added the cf-auto root which is one extra step . Also with auto root there is a possibility of bricking the phone since it supports a lot of devices and as you are well aware that a lot of people new to flashing tend to flash the wrong files even if you give them a step by step guide. While this guide is helpful and does work it isn't as idiot proof as the other guide you linked on your post.
[Verizon Samsung Galaxy S III] benbrown:
This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!
[Verizon Samsung Galaxy S III] jmxc23:
This guide is different in that it uses cf-auto root so I highly doubt you even tried this method.
[Verizon Samsung Galaxy S III] benbrown:
I finally did get it. All rooted now.
[Verizon Samsung Galaxy S III] faehsemc:
The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done

Sent from my MIUI powered S3 thanks to StrumerJohn
[Verizon Samsung Galaxy S III] droidshadow:
maybe i should have been more clear...

Hey everyone,

Well i guess everyone has their own favorite way of rooting their phone/device. I did not mean for this small tutorial to be the *absolute easiest* way to root a verizon samsung galaxy s3 model i535 i just thought that I could do people a favor by elaborating a bit more on certain steps to make the rooting process a bit easier.

On certain tutorials i found I didn't seem them clearly state that the VRLAC BOOTCHAIN file needed to go in the boot loader section of ODIN to unlock the phone's bootloader.

On other tutorials that show you how to use CF-AUTOROOT I didn't see any that told you that you needed to install SUPERSU from the google play store manually in order to fully utilize your phones rooted status.

Yes there are other ways too root a SGS3, the Samsung Toolkit is a good option, or using a custom root such as Cyanogenmod is another great option as well...

All of those options you will have to research for yourself and ultimately decide for yourself.

However, if you want to keep your phone's stock ROM and you just want to root your Verizon SGS3 model SCH-I535 then I like using ODIN + CF-AUTOROOT exploit.

All i wanted to do was assist and do my part on this great forum which has helped me so much in the past...

I hope it helped someone...

Thanks for everyone who replied and shared your thoughts on other rooting options.

-DroidShadow
[Verizon Samsung Galaxy S III] mlev1987:
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .

The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.

Anything you can help me with? I''m going crazy here.

Thanks
[Verizon Samsung Galaxy S III] Sushruton:
Rooting and installation on S3 GTI9300

I rooted my S3 2 days back (i think so), now i want to install a custom rom (mostly xperia Z) and I am new to this world, so can you plz help me??

I followed your instructions there was no such msg as Andriod is Updating, and how should i do install the rom??

I wish to install from:rolleyes: this http://xdaforums.com/showthread.php?t=2174644 :rolleyes:
[Verizon Samsung Galaxy S III] bgenchel:
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL
[Verizon Samsung Galaxy S III] droidshadow:
hello everyone

bgenchel: what kind of phone do you have? Are you 100% sure that you downloaded the correct CF-autoroot file for your specific phone model?
[Verizon Samsung Galaxy S III] droidshadow:
Did you run the Odin with the VRLAC bootchain file then you unplugged your phone before a full restart could take place? This is a very sensitive issue because that bootchain file unlocks your bootloader on your verizon phone. Your bootloader is everything to your phone. It controls how your phone starts and your phone can not work correctly if your bootloader became compromised in any way. I really hope you figured it out, and if you didn't maybe you could call your insurance company (if you have one) and get a new phone. If you are worried about rooting your phone again you could look on craigslist, there are always people/professionals willing to do it for very reasonable prices $10-$20. Again i really hope you figured this out and if you give me some more details maybe we can figure this out together.
[Verizon Samsung Galaxy S III] ohemetophobia:
Phone Rebel Method

This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg

What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/

to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.

At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.
[Verizon Samsung Galaxy S III] ohemetophobia:
UPDATE

You can use method 1 outlined in the droidviews link i posted yesterday to root the phone and when you get to the point where you're flashing the second bootchain you can flash VRBMB1 instead of needing VRBMF1 and it will work just fine! I also believe this method will truly unlock the bootloader for flashing custom roms, to avoid the yellow triangle of frustration, but I have no oversight on this as it was not my plan to do so.
[Verizon Samsung Galaxy S III] BKSinAZ:
VRBMF1??

I must admit that I am new to rooting.

I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............

For VRBLK3 (Jelly Bean 4.1.1) Link

MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A

For VRBMB1 (Jelly Bean 4.1.2) Link

MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1

For VRBMD3 (Jelly Bean 4.1.2) Link

MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF

I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.
[Verizon Samsung Galaxy S III] ohemetophobia:
Yes, the instructional post was created prior to you getting an S3. So, if you got into Settings> About Phone and look at your baseband version you'll probably see I535VRBMF1 and you'll probably see it again in another field just below it. This indicates that you're running the VRBMF1 firmware. That is JB 4.1.2 with multi-window. When using the root process in the droidviews article it outlines flashing VRALEC, then CWM touch, then using CWM to flash the supersu file, then flashing either VRBLK3, VRBMB1, or VRBMD3. Since none of those bootchain files match your firmware and there is no VRBMF1 bootchain on the forums, I flashed VRBMB1 since it was the the bootchain from the previous firmware. It worked. I successfully achieved root with no problems. Hope this helps.
[Verizon Samsung Galaxy S III] droidshadow:
Hello again everyone!

Well i can't thank you all enough for your responses on this thread, all of the responses have been quite informative and interesting. Now my brother just got a Verizon Samsung Galaxy S3 model SCH-i535 and I was able to root his phone following the steps I outlined in my tutorial with no problems.

One thing now that I am very curious about is if i correctly unlocked the bootloader? The VRLAC.bootchain file is designed to unlock the bootloader right?

I would not be able to root the phone without unlocking the bootloader first since Verizons SGS3 model SCH-i535 comes with its bootloader locked by default.

Also when I ran "Rom Manager Pro/Premium" it first asks me to install a recovery manager and I choose Clockworkmod Recovery and it was able to flash the recovery manager with no problems" I could not do that without the bootloader being unlocked first right?

For the person that is getting the ugly yellow triangles, I believe you are getting this because Samsung devices come with a counter that keeps track of how many times you are flashing a custom rom. There are a couple of apps on the google play store that are designed to get rid of the yellow triangle and to reset your rom counter so you can flash as many custom roms as you want. The yellow triangles you are getting may not be because of your bootloader.

Here is a link about the yellow triangles and hopefully this will help you out...

http://xdaforums.com/showthread.php?t=1494114

If i am missing something please let me know so i can update my tutorial...

I thank you all for your responses and please keep them coming!

-droidshadow
[Verizon Samsung Galaxy S III] ohemetophobia:
I think the yellow triangles that I am getting are a bit different from the ones that Triangle Away are meant to prevent. Using the CF Auto Root method every time I tried to flash a custom rom, the phone would not fully boot. Only the yellow triangle with a message that Verizon has detected an unauthorized software. It also disabled my custom recovery forcing to recover via Odin. The general consensus amongst the SGS3 group on G+ is that the bootloader was not unlocked. How that works, I'm not sure but CF auto root has proved unsuccessful for me. I tried the alternate root method with intentions to flash a custom rom, but have decided to stay stock rooted. My only real reason for rooting was Google wallet which is functioning now.

I could be wrong about the triangles, but I'm not willing to find out.
[Verizon Samsung Galaxy S III] droidshadow:
Wow that seems really harsh...

Am i correct in saying that the even using CF-AUTOROOT that with Verizon phones the rooting process would not work unless the bootloader was unlocked properly?

To be extra cautious just 5 minutes ago i went ahead and flashed the VRBMB1 bootchain file with Odin which flashed successfully but I am still not sure if the bootloader is unlocked 100%

Does anyone know of a way to check 100% if the bootloader is unlocked properly/successfully?

There is an app called EZ-Unlock that used to be available from the google play store but is no longer available (not sure why) but it is specifically for verizon sch-i535 phones and it supposedly unlocks the bootloader. Here is a link:

http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/

You can try that to make sure that your bootloader is unlocked..

Maybe that will help out, but again i am not sure that your bootloader being locked is your problem. If you successfully flashed the VRLAC boothcain file and the VRBMB1 file then your bootloader should be unlocked fully.

How did you try flashing the custom rom?

Maybe you should try using something like Rom Manager or Rom Toolbox.

If you try that EZ-Unlock please let me know how it worked for you...

-droidshadow

***UPDATED***

i just tried EZ-Unlock Version 1.2 was recommended on the site and that is the one that I downloaded, and I will tell you what, i think you may be right. I think maybe the bootloader was unlocked during the rooting process and may have been locked again but after running that app and clicking "unlock" its that simple I can tell that the bootloader had been unlocked. After a reboot the samsung logo flashes by in an instant 1-2 seconds and I have been told that is a sign of an unlocked bootloader.

Give EZ-unlock a try it is very simple. After installation you just have to run it and click "unlock" and you will hear "that was easy" and on the reboot you will see the samsung logo go by very fast. Also don't forget to give EZ-Unlock root access with SuperSU.

Try it out... and maybe flashing your custom roms will now work for you.

Hope it helps...

-Droidshadow
[Verizon Samsung Galaxy S III] droidshadow:
about the bootloader...

One last thing to say about unlocking the bootloader...

I watched that video on youtube you posted about how that guy used the same rooting process as me. Well on the video he pointed out how you would see a the word "CUSTOM" with a unlocked lock icon. In the video he said "don't worry we will take care of that" and what i am sure he meant by that is that after you successfully unlock the bootloader that icon will disappear. Well after flashing the VRBMB1 bootchain file with Odin that icon still appeared on my boot up screen.

However, after running EZ-Unlock here is the link one more time: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/

That icon has disappeared and the Samsung logo flashed by very fast within 1-2 seconds.

So download the app if you want to unlock your bootloader successfully and easily.

And if you used CF-AutoRoot and you want to flash a custom recovery such as ClockWorkMod Recovery you can use the app Rom Manager from the google play store to do it, it is very easy to do with that app.

Thanks so much for bringing this to my attention, i was about to flash Cyanogenmod 10.1.2 and i could have easily damaged my device.

I can't thank you enough...

-droidshadow
[Verizon Samsung Galaxy S III] ohemetophobia:
Sounds like you caught something I missed. My phone always had the custom logo up at every boot, so whatever I did, didn't complete the process which probably caused all of my issues. With the root method I posted in here, it seems that the custom logo went away and after I softbricked the phone installing google wallet and restored with a pre-rooted rom it's gone away. so I could possibly successfully flash a rom now, but I'm content as is.

Good catch, though. I'm glad something that i posted helped you on the road to successfully flashing a custom rom.
[Verizon Samsung Galaxy S III] droidshadow:
Ohemetophobia,

I just wanted to let you know that I flashed Cyanogen Mod rom 10 .1 .2 last night on my samsung galaxy s3. I use ROM Manager to flash the custom ROM. It works great without any issues so if you were having issues before flashing a custom ROM it had to be because of the bootloader be blocked. Just wanted to let you know in case you were thinking about flashing a custom ROM again. Thanks so much for bringing that bootloader being locked to my attention.

Hope all is well...

Droidshadow
[Verizon Samsung Galaxy S III] Painterface:
edit: nevermind, I figured it out.

Thanks for all the info!
[Verizon Samsung Galaxy S III] HorribleTech:
Great Man!!!
[Verizon Samsung Galaxy S III] kwak123:
Phone isn't booting

After step 4, I followed all the instructions explicitly, but even after installing all the drivers, it made the "failed to install drivers" sound and the phone isn't rebooting. I used the VRALEC bootchain into the bootloader option, and now the phone is bricked. It will not power on. What do!

It does request QHSUSB_DLOAD... I think the phone is hard-bricked. May want to throw a warning in that step that this is a possibility.

Also, should F. Reset not be unchecked? You said to only have auto reboot checked, but reading around makes me feel this was also supposed to be checked.
[Verizon Samsung Galaxy S III] ohemetophobia:
I've never unchecked F.Reset in Odin, when rooting. You can't boot into download mode?
[Verizon Samsung Galaxy S III] vmm1:
Thank You for this very USE FULL post. Everything went smooth, except unlocking the boot loader.

I have a verizon S3 and my baseband is I535VRBMA2 . I could not find this bootchain, and I was getting this Custom sign while reebooting phone. I kept on reading and find that You mentioned an EZ Unlock. Downloaded one from links thet You posted, although it can be not found on Google Play.

Now, the phone keeps Samsung sign only 1-2 seconds while booting.

With Rom manager I installed CWM recovery and everything is working fine.

Thank You once more!.
[Verizon Samsung Galaxy S III] kwak123:
Lethaeus entchai

The phone won't boot at all :/ it seems the bootloader corrupted because of it. I just assumed that only needing auto reboot meant I didn't need anything else, and I'm quite the noob at rooting, haha. Oh well lesson learned.
[Verizon Samsung Galaxy S III] crashineyes:
easy with transroot
[Verizon Samsung Galaxy S III] jackthomas251:
agree, it's actually quite common.
[Verizon Samsung Galaxy S III] prozpris:
Thank you

Thanks so much for this tutorial, droidshadow! It made things fairly straightforward for me!
[Verizon Samsung Galaxy S III] droidshadow:
your very welcome

I am glad that you found the tutorial useful...
[Verizon Samsung Galaxy S III] mikewanda1971:
I was wondering which method if any i am to use for rooting an sg3 from alltel. I have searchrd and searched but have found nothing pertaining to alltel branded sg3. Any help would be greatly appreciated.
[Verizon Samsung Galaxy S III] ohemetophobia:
Try searching by model number. Go into Settings>About Phone and then search by whatever is displayed under model number.
[Verizon Samsung Galaxy S III] Rottwild:
BRICK

Followed your steps to the tee up to step four every thing went fine, said it was successful and all, now phone will not even power on to continue to step five. So my brand new phone not even 24 hours old is a big BRICK. Same model as what you have S3 SCH-I535. I have rooted many other phones with no problem. Have a solution?
[Verizon Samsung Galaxy S III] stolo:
rooting on s3 so easy now

rooting on s3 so easy now!!

---------- Post added at 07:13 PM ---------- Previous post was at 07:08 PM ----------

Just use odin to install stock rom and start over. Find it hard to believe you bricked it if you followed instructions.