yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z General] Nospin:
No, I believe them that an OTA upgrade to ics would require a full wipe of the device, and that's not something that the average user would appreciate.

It all comes down to the custom rom community in Android. The minute an oem drops support for a device, they should open source EVERYTHING they have for that hardware. That way the minority of users that really care about being on the newest version of Android would have everything they need and zero blame could be placed on the manufacturer.
[G2 and Desire Z General] KyraOfFire:
But then, all they have to do is to give users a choice. I have plenty of friends who use SGS II, don't have a clue what is ICS and don't bother to update. They get to choose, update or don't update. They sure don't care about ICS, but they do appreciate being able to use the phone the way they do.

Giving users choices is completely different than telling them "We decided that this way is the best for your experience. You have no other choices". Sounds just like Steve Jobs' "Don't held the phone that way"... wait a minute... heck, even iPhone users get to choose either to update or not to.

I officially hate HTC now lol
[G2 and Desire Z General] Nospin:
Money. None of the carriers will approve an update that will wipe data, which leaves an optional PC update the only distribution model, and that isn't worth their dev hours.

Correct me if I'm off, but iPhone users only had a choice to update because it required itunes. Now that updates are ota, doesn't it eventually force the install?
[G2 and Desire Z General] KyraOfFire:
Most people agree that by "weigh a number of factors", they meant weighing the financial impact.

I place the bet that they loose customer (and thus money) in the long run.

Do you really need to tap the Accept button if the line above it says in red and bold "This will erase all of your data"?

I do believe the OTA update notification comes with two buttons, one of which accept it and the other one don't.
[G2 and Desire Z General] Deathmehr:
Check this out:

http://www.gsmarena.com/htc_to_shut_down_its_office_in_south_korea-news-4577.php

Looks like someone's policy turned against himself:

You do not gain clients by being an assh..e to owners of previous models.
[Samsung Galaxy Nexus] BryMerc:
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bear with me and consider using layman type language with me. :) Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.

Here's the bullet-point run-down of what happened:

- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.

- Read through a thread on here on how to flash to "yakju". Did so successfully.

- I then wanted to root since my device was already wiped from unlocking bootloader or flashing some partition or something

- Followed this thread (http://xdaforums.com/showthread.php?p=19583168#post19583168)

- Rebooted, saw the "Superuser" app and thought I nailed it.

- Saw an update for Jellybean, it requested a reboot before install

- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.

- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading around, downloaded SU Update Fixer from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.

So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.

** One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery on my phone just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assumed it was since I got the Superuser app.

Another thing that felt kind of wrong is that, when I flashed to yakju, it wiped my phone clean. I expected rooting to do the same thing, but it didn't (I think because my bootloader was already unlocked?). So I'm not sure if that has anything to do with it either.

Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing files from a directory, etc.

Thank you in advance.
[Samsung Galaxy Nexus] JaiaV:
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
[Samsung Galaxy Nexus] IINexusII:
you can also install the OTA manually, heres my method

1) grab the link for yakju IMM76i > 4.1.1 from here: http://xdaforums.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.

2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, press vol down twice in the bootloader and go straight into the recovery.

3) install the OTA zip you downloaded and placed in your sdcard

4) clear cache and fix permissions (might not be necessary but you can do it just incase)

5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.

6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.

7) reboot. should be all sorted now
[Samsung Galaxy Nexus] BryMerc:
Thanks for the fast response.

So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot?

Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?

Thanks.
[Samsung Galaxy Nexus] JaiaV:
Yes.

They only care that the recovery and /system are stock, and even then (as I said) don't care if you're rooted. Rooting doesn't matter. Having a custom recovery does. They are not the same thing. Also, read through ||Nexus|| response.
[Samsung Galaxy Nexus] BryMerc:
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
[Samsung Galaxy Nexus] IINexusII:
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.

edit: yes itll just be replacing the recovery, nothing else
[Samsung Galaxy Nexus] BryMerc:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
[Samsung Galaxy Nexus] IINexusII:
in clockwork mod recovery there should be a "Wipe Cache" option, and for fixing permissions go to "advanced" and "Fix Permissions"
[Samsung Galaxy Nexus] BryMerc:
Wait, actually I don't think the JB installed now that I'm staring at the screen properly.

It went Installing update...

assert failed: file .........blah blah

Installation aborted.

Also, the drivers I thought I had for my phone seem to be messing up and in device manager it says "Full" with an exclamation point. I'm not sure why.

Sorry for the late responses as a n00b I'm stuck with 5 minute intervals here.
[Samsung Galaxy Nexus] IINexusII:
which country are you from?
[Samsung Galaxy Nexus] BryMerc:
Canada.

I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
[Samsung Galaxy Nexus] BryMerc:
After selecting "Install zip from sdcard" I see an option "apply /sdcard/update.zip". Is that anything maybe I need to do or something?
[Samsung Galaxy Nexus] IINexusII:
check your PM
[Galaxy S III Q&A, Help & Troubleshooting] 1Android:
I turn off my background data when I'm not using it. After turning background data back on, I am able to go into google play but my email errors out no matter how long I wait. The only way I can get into my email is if I remove the account in my settings under accounts and sync and then add it back in.

Turning my background data off I:

-settings/data usage/limit mobile data/select options and turn off background data.

Turning it back on I:

"same steps" but turn background data back on.

At that point everything should work just fine right? Am I missing a step to turn it back on? I have even scrolled down to "email" under the data section and double check the background data on that specific app and it shows it is on.

What am I missing here!?
[Samsung Galaxy Nexus] superevilllama:
When you first hit the power button and choose silent or vibrate an option comes up that asks you do you want to automatically restore the audio profile after a certain amount of time or something like that. It only came up once and not since, and whatever setting I chose is messing up my other volume profiles app. Any suggestions to access that option again or what app (maybe framework) to clear out that may make it display again?

Thanks guys

Yes I am on the gnex just haven't updated profile yet.
[Verizon Samsung Galaxy S III] john9:
Nice GUIDE and very helpful informations!
[Verizon Samsung Galaxy S III] tjac357:
I can't extract the file. there isn't an option for it and it stays as a 650 mb file

nvm figured it out
[Verizon Samsung Galaxy S III] hrffd:
Useless information.

...

Only because I don't have the phone.

Good work.
[Verizon Samsung Galaxy S III] faehsemc:
Now what happens if i ever want to unroot? Say dev edition comes out and yiu cant be rooted to do the new unlocking method found... i know what if what if... but still want to know
[Verizon Samsung Galaxy S III] CBMC:
Flash the stock rom with kernel. The thread that contains them is linked in the op.
[Verizon Samsung Galaxy S III] tpike:
Flash stock files in op is the normal method.

Not personally tried it:D

Thanks for the collection and the easy instructions.

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] blade7840:
WIFI Hack

How do you install the wifi hack? And if I use this VZW GS3 EZ-Recovery apk . I must download the recovery I want to use to sdcard first to use the VZW GS3 EZ-Recovery to install a custom recovery.
[Verizon Samsung Galaxy S III] faehsemc:
Ok ya.. i was dumb. Appreciate the help. I was thinking that was stock rooted thread from invisible k. . Misread
[Verizon Samsung Galaxy S III] Cvballa3g0:
The Wi-Fi hash instructions are in that thread.

If you use the EZ recovery, you do not have to add the recoveries to your phone, they are included in the app.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] neyenlives:
need to add the goomanager method to getting TWRP recovery, once rooted install goomanager, launch it and hit menu button and select launch open recovery script and then it will find the latest version for your device and it will install it from there for you
[Verizon Samsung Galaxy S III] chocolate8175:
Thanks for the guide, I would probably suggest adding that you need to rename the "root_66.tar" file before flashing. I had to rename mine "rooted.system.image.tar" for ODIN to recognize it, thanks again though
[Verizon Samsung Galaxy S III] shimp208:
Great guide maybe add information about kernel kexec
[Verizon Samsung Galaxy S III] Cvballa3g0:
i flashed mine without changing the file name... weird.

I would it i knew how to use it. I'm not familiar with it.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] shimp208:
Another suggestion for a piece of information you could add is for adding init.d boot scripts and busybox using this guide

http://xdaforums.com/showthread.php?t=1762378
[Verizon Samsung Galaxy S III] Cvballa3g0:
updated the OP, added the kexec method to the guide and added more bonuses towards the bottom.
[Verizon Samsung Galaxy S III] walkingagh:
I followed all the directions to a T but my flashing just failed what should I try to do now?
[Verizon Samsung Galaxy S III] Cvballa3g0:
What do you mean "to a T?"

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] walkingagh:
I mean exactly as written. I am trying to re-flash now and hoping that takes. I have tried rebooting the phone and essentialy it says there was a bad flash. It might be a corrupt download? Is there an MD5 anwhere?
[Verizon Samsung Galaxy S III] Cvballa3g0:
for which files? what are you trying at get? root, roms, kernel?
[Verizon Samsung Galaxy S III] walkingagh:
I am trying to flash the root66.tar file. The flashing proceeds all the way until the very end and then fails while flashing the cache. Is there a way to boot into recovery and wipe data/cache first?
[Verizon Samsung Galaxy S III] CreationArt:
Thanks! Worked like a charm. -Brad
[Verizon Samsung Galaxy S III] Cvballa3g0:
the MD5 = be4350a56e739eaf7a4184352d653a7b is the root_66

to boot into recovery, its the (volume up + home + power) combo when the phone is off. you can wipe there.

Did you download the drivers and the Odin 3.07 too?

just double checking.
[Verizon Samsung Galaxy S III] walkingagh:
Yeah I did download everything from the OP. No idea what is going on. It has failed 3 times now, and I checked the md5. I just wiped data/cache, so we will see if that works.
[Verizon Samsung Galaxy S III] Kipland007:
Thanks for such a great guide. Booted custom kernel with kexec successfully!

Two questions:

I've noticed that anytime I flash something I get the "android is upgrading" thing. Anyway to avoid this?

Also, just to be clear, whenever I reboot now I have to flash the zip that's given with the kexec method?

Thanks.
[Verizon Samsung Galaxy S III] faehsemc:
May have to do a factory reset... otherwise check you cable. Or try a different pc. In the past i couldnt do anything related to transferring files... only on my phone though. But no issues using my wifes.
[Verizon Samsung Galaxy S III] Cvballa3g0:
The android is upgrading happens when the system apps are modified, but it should only happen one.

And you have to flash that zip every time on boot if you want to run the custom kernel.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] walkingagh:
So in the end, no idea what went wrong. I was able to flash back the stock roms without trouble so no real loss.
[Verizon Samsung Galaxy S III] jmorton10:
I've been flashing with Odin since I had my Droid charge and I've never had to rename a file.
[Verizon Samsung Galaxy S III] seang:
giving it a shot.. always a bit nerve-wracking rooting your shiny new phone :)
[Verizon Samsung Galaxy S III] Cvballa3g0:
Updated OP. Added the dual boot video i made

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] aj8600:
would it be benificial for me to upload the .zip with the added line in the script and then img inside it?
[Verizon Samsung Galaxy S III] pdinphx:
Awesome guide, Cvballa3g0 ... thanks for all your hard work.

PJ

Phoenix AZ
[Verizon Samsung Galaxy S III] droidstyle:
very nice guide!!!
[Verizon Samsung Galaxy S III] Cvballa3g0:
I never thought of that. Sure, upload the zip =)

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] newuser134:
Is the root66 stock root image posted in the OP here the same as the stock rooted image on the invisiblek original root and recovery thread, posted here, under "OR.....stock"?

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

If not, what's the difference?

Thanks
[Verizon Samsung Galaxy S III] Cvballa3g0:
No, they're different. Some people wanted a remake of the image because the one in Invisiblek's thread had some stuff of Sprint on the phone. So the root_66 is bug free.
[Verizon Samsung Galaxy S III] Cmotion:
Sorry if this is a dumb question, I looked through the whole thread and didn't find any mention of it. I live in an "all-Mac" household. Is it possible to root on something other than a PC/Linux machine? Thanks for the guide!
[Verizon Samsung Galaxy S III] cyiwin:
sorry im new to this i download the stock.vzm_root66.tar file is says and when i extract it it says file is broken. Any suggestions on how i can get around this
[Verizon Samsung Galaxy S III] itsmefu:
I had to download that file twice. First time it didn't work, downloaded again and it worked fine.
[Verizon Samsung Galaxy S III] Cvballa3g0:
Try checking in the checking in some other root threads. I heard of the program heimadel or something like that, but i think it was for Linux.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] 4FatSno:
Thanks a million for this guide.

Yay...I'm free (rooted)!!!

:D

sent from outerspace
[Verizon Samsung Galaxy S III] Cvballa3g0:
No problem! =)

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] slick_shoes:
Would we still get OTA updates if we decide to stay stock rooted? I don't want it to update and mess up my phone. Thanks.
[Verizon Samsung Galaxy S III] flamus:
Yes unless you either flash custom recovery or custom kernel. If you don't want to have to do that then there is a fix floating the forms.
[Verizon Samsung Galaxy S III] bucsfann20:
Any reason why my phone would not reboot midway through the kexec custom recovery and Kernel option? (Method #3) I can't seem to get the kexec working.
[Verizon Samsung Galaxy S III] flamus:
Read here :

http://www.s3forums.com/forum/galaxy-s3-help/829-how-properly-disable-ota-updates-verizon-s3.html

Not sure if this will work, but keep a backup of current system ROM and flash back using Odin.
[Verizon Samsung Galaxy S III] ErylFlynn:
Complete failure, first step should have been know where your towel is.
[Verizon Samsung Galaxy S III] Kc0r8y:
2 noob questions:

Is this a 100% stock rom? I don't want to deal with the bugs of new roms, but may want to flash custom rom later when they have been cleaned up.

Will this wipe all my apps and stuff? It's a pain in the ass starting over.

Thanks for your time and the guide.
[Verizon Samsung Galaxy S III] e_droid:
For Step 4, I can confirm that the Device Profile also works with 'Samsung Galaxy Nexus (CDMA/LTE)' setting for VZW GSIII. Thanks for the write-up. :good:
[Verizon Samsung Galaxy S III] cyiwin:
i downloaded it three times but its still telling me the same thing. Is there anything link i should try or just try it with the file that is giving me an error because after it give me an error it does change into the file stated in the instructions. i just dont want to run it and it mess up the phone.
[Verizon Samsung Galaxy S III] Cvballa3g0:
You have to be running cwm touch.

Did you rename the kernel to boot.img? And does your computer show file extensions? You might of saved it as boot.img.img if not, then you placed the files in the wrong directory.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] bucsfann20:
CWM touch. There's my problem. Thank you sir.

Sent from my Precious.
[Verizon Samsung Galaxy S III] Cvballa3g0:
No problem

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] d1ez3:
Noob question. If I'm rooted on root 66 and want to go back to stick but rooted, basically wipe all data. Can Ijust wipe in clockwork recovery and reboot my phone? Or do I need to flash the Rom again? Thanks
[Verizon Samsung Galaxy S III] Cvballa3g0:
You can factory reset and wipe data to get a clean rooted phone.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] Muckrak3r:
What about going back to 100% stock, with a reset flash counter? I'm asking in case I ever need to send my phone in for an insurance replacement.

Sent from my locked bootloader Verizon GSIII. :(
[Verizon Samsung Galaxy S III] Cvballa3g0:
Then you flash the kernel and stock image that i linked to in the OP in red. And no one has tried the flash counter yet.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] JoeyBert:
Can someone point me in the direction of the instructions for Unrooting?
[Verizon Samsung Galaxy S III] Cvballa3g0:
The first link in my OP, the red stock image link, download the kernel and stock image. Flash those two in Odin in the PDA slot.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] silver04v:
Just wanted to confirm my steps here. But had a couple questions, I know the steps I need to take to root and install cwm. I'm going to just root66 and then use the app to install CWM. Using that cwm, is the date in backups correct or am I better off using Rom Manager to install CWM?

Last thing, if I root and install CWM like this does it trip any of the counters at all? Or should I be pushing cwm with adb to not trip counters? Just want to be able to go back to stock with no counters saying something else after. Thanks in advance.
[Verizon Samsung Galaxy S III] Cvballa3g0:
Idk if the backup dates are alright.

And this doesnt trip the counter.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] trevoryour:
alright maybe i'm confused but it seems like this thread contains way to root, flash a rom, and flash a new kernel. I thought with the boot loader locked it wasn't possible to flash a rom or kernel. What is the locked boot loader actually preventing us from doing?
[Verizon Samsung Galaxy S III] joka10:
What about Unrooting

Maybe I am wrong but i have not seen any back to stock threads or videos for this phone.
[Verizon Samsung Galaxy S III] Cvballa3g0:
a locked bootlaoder doesnt allow us to flash kernels, not ROMs. We have work arounds to get custom kernels.

The first link im the thread. The stocks images. In big red.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] JoeyBert:
For returning to stock, If I've only rooted my phone, didn't install any custom roms, do I still have to flash the kernel as well as the Stock image? or can I just flash the image?
[Verizon Samsung Galaxy S III] Cvballa3g0:
Id flash the kernel to be on the safe side.

Sent from my locked Verizon Samsung Galaxy S III
[Verizon Samsung Galaxy S III] neyenlives:
thats because all you have to do is Odin the stock unrooted original untouched ROM in this thread
[Verizon Samsung Galaxy S III] JoeyBert:
Can I ask for someone to post the Stock Kernel version as it appears in the 'About Device' section? Also, should the kernel be flashed before or after the image? And through Odin as well?
[Verizon Samsung Galaxy S III] droidstyle:
Just flash the image
[Verizon Samsung Galaxy S III] dragon1357:
will rooting wipe data?
[Verizon Samsung Galaxy S III] Mr Lime v2:
I rooted last night and I still had everything. :)