Database Info

[GUIDE] [HOW-TO] [N00b Friendly] Install OFFICIAL CM10 Nightlies NO KEXEC (8-18-12)

UPDATE 8-18-12: OFFICIAL CYANOGENMOD NIGHTLIES ARE UP.
Hey Guys, I haven't seen anyone post this yet so I figured I'd give it a shot. First and foremost, I take ABSOLUTELY NO CREDIT FOR ANYTHING IN THIS POST. Let it be known that none of this is my work and the purpose of this post is to consolidate information into an easy-to-follow guide. Also, I take no responsibility for any damage you do to your own phone. It's your responsibility to understand the risks involved and do your research before you make ANY modifications. If you'd like to use this guide for a project you're working on or another thread, that's fine with me. All I ask is that you give credit where it's due.
BEFORE WE START. If you cannot follow detailed instructions, please don't bother using this guide as you're only going to waste your own time as well as mine. I won't be answering any questions or providing support for problems that are clearly covered in the guide.
Now that we've achieved an unlocked bootloader, Cyanogenmod's team is already at work and has a build of CM10 up and running. (It's technically an alpha, but for me EVERYTHING works perfectly: data, wifi, bluetooth, GPS, MMS, camera, camcorder, the whole nine. The only thing I've found to NOT be working is NFC). The post can be found on both Cyanogenmod and Austen Dicken's Google+ page. Those can be found here:
https://plus.google.com/117962666888533781522/posts
A word of caution:
Since I'm not a Cyanogenmod developer, I have no control on the stability of their posted builds. So if you go through the guide and your MMS isn't working, there's not a whole lot I or anybody else can do for you at the moment considering these are still alpha builds. Although I mentioned everything works currently for me, I can neither guarantee this nor help you troubleshoot technical issues as I am not the developer of the ROM itself. On the other hand, if you have any questions or problems following the guide, I'm happy to help you out to the best of my ability.
For this to work, you must be ROOTED and have an UNLOCKED bootloader. I'm not going to make a super-detailed write up on how to achieve both of these, but here's a general outline of steps for those that are new here. If you're already rooted and have your bootloader unlocked, you can skip straight to step 4.
Pre-install:
First, BACKUP EVERYTHING. Do a nandroid backup and backup your apps and data in Titanium if desired.
Install the latest Samsung USB drivers so your phone and your computer don't have any connection problems. Those can be found here:
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
on the bottom under Manuals/Downloads and then Software.
I highly recommend backing up your IMEI incase something goes wrong. I'm not going to cover that here, all info can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1791291&highlight=backup
You have been warned.
You need to have your SD Card formatted to FAT32. exFAT WILL NOT WORK. So if you're like me and have a 64GB SD card, neither Android nor windows will let you format to FAT32 natively, so you have a few options.
Using command prompt within windows:
http://www.xoomforums.com/forum/mot...-format-sd-card-especially-64gb-fat-32-a.html
Use a disk management program like Acronis Disk Director (I think they may have a free trial but don't quote me on that).
http://www.acronis.com/homecomputing/products/diskdirector/
Then, you may want to Odin back to stock using the latest Samsung firmware. Now, you DO NOT need to Odin back to stock for the rest of this guide to work. But it should fix any 4G/3G data problems you may have been having on custom k-exec ROMs and I thought it was a good idea to start completely fresh now that we have total freedom. So if you were having bad experience on any custom ROMs with a flaky data connection or GPS taking a long time to lock, give it a try and see if it fixes things for you.
If you're going to give it a try, both the Odin program and stock Odin firmware can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1755386
Download the latest version of Odin and the latest stock firmware version. Extract the Odin zip and load it up. Click the PDA button, find the stock firmware you just downloaded. Boot into download mode on your phone by powering down, then powering back up while holding the home and volume down buttons. Click start in the odin window. This process should take a while. After your phone reboots, get through the setup and dial *2767*3855#. Your phone will reset and you'll be COMPLETELY back to stock and any radio/hardware connection issues should be fixed. If you're still having problems let me know.
Now, to the fun part.
1. Root your phone.
NoxiousNinja's GS3DebugFSRoot Tool is the easiest and most foolproof way I've found. Read the directions in the post and follow the instructions in the command prompt window. Very easy and lightweight.
http://forum.xda-developers.com/showthread.php?t=1792342
As you continue throughout this process, pay careful attention to the prompts as it will ask you for [y/n] responses that you must confirm. After finishing, go into the newly installed Superuser app and on the far left panel, click where it says "tap to check for updates." Then click "update" on the bottom EVEN IF YOU HAVE THE NEWEST VERSION. I don't know why it works, but it does.
2. Flash a custom recovery.
Download mmmeff's EZ Recovery flashing app from the play store. Just search for "EZ Recovery" and you'll find it. Once installed, make sure you allow root access, then select "CWM 6.0.1.0" from the dropdown (NOT THE TOUCH VERSION AND NOT TWRP . It just makes it easier on everyone if something goes wrong. I can personally confirm that the touch version is incompatible. Some users are reporting TWRP is working fine, so you can try that at your own risk but I can't provide any support if it doesn't work for you since I haven't tried it myself.), make sure you have the "Recovery" toggle selected on the left, and click "flash recovery". Don't worry about rebooting yet as we still have a few things to do. The thread for the app can be found at:
http://rootzwiki.com/topic/29698-72...-recovery-flashing-app-ya-dingus/page__st__10
3. Unlock your bootloader.
I've also chosen to use mmmeff's Bootloader unlocking app from the play store for this guide as it is universally acceptable no matter what operating system everyone is running. In the play store, search for "GS3 EZ Unlock". Once installed, again make sure you allow root access and then click the HUGE button in the middle. It only takes a few seconds and then you're done. Thread is here:
http://rootzwiki.com/topic/32456-app-ez-unlock-easiest-way-to-unlock-your-bootloader/
4. Flash Cyanogenmod.
First, you'll need some downloads. You can use the Cyanogenmod 10 Alpha build or a nightly CM10 build.
Cyanogenmod 10 ALPHA build:
http://goo.gl/RYzHT
MD5: 3662de3c8942f19dc95ca911207b1602
CM10 Nightlies can be found at:
http://get.cm/?device=d2vzw
Jellybean GAPPS:
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Mirror:
http://www.mediafire.com/?63l7wtwlc09923c
MD5: f62cfe4a827202899919fd932d5246d7
Put both of these zips on the root of your SD card.
Before you get all trigger happy, we need to do some things first.
For those of you who are new at this, I'll say it again, BACKUP EVERYTHING. This next step will wipe everything on your phone.
INSTRUCTIONS FOR FLASHING A NEW INSTALL OF CYANOGENMOD:
Now, boot into recovery (power off and then power back on while holding the home and volume up buttons) and wipe SYSTEM, DATA, CACHE (all can be found in Mounts/Storage menu), and DALVIK CACHE (can be found in advanced menu). A system wipe is not technically necessary but I did it just to make sure I didn't have any problems. Then, go into "install zip from SD card," then "choose zip from SD card". First, flash the Cyanogenmod zip, and after that finishes flash the Gapps zip. Go back a couple levels, click "reboot system now," and you're done!
INSTRUCTIONS FOR FLASHING AN UPDATED BUILD OF CYANOGENMOD
Now that you have a working install of Cyanogenmod, it gets a lot easier. If you're currently on the Alpha build and are switching to the new nightly builds, I would HIGHLY recommend you perform a FULL wipe including system, data, and both caches. Some people moved from the alpha to nightlies and were having problems so if you do a full wipe the first time you'll be fine. If you want to update from a nightly build to a newer nightly, all you should need to do is wipe both caches.
I hope this helped at least a few people, I tried to arrange it into as easy of a guide as I could. Please let me know if you see any problems or necessary changes and I'll try to keep this thread updated as new builds are upped. TO EVERYONE THAT IS NEW HERE, PLEASE DO NOT BUG DEVELOPERS WITH STUPID QUESTIONS REGARDING RELEASE DATES OR PROGRESS. I can assure you that they're working hard, we got a full release the day after our bootloader got unlocked. So be patient, nightlies and beta versions of CM and AOKP will come soon enough.
If you're interested, after you're done you can try flashing a new radio and/or kernel. Unless you're having problems, I wouldn't recommend you try this unless you know what you're doing because you could make things worse. Consider yourselves warned. Radios and instructions can be found in Invisiblek's thread here:
http://forum.xda-developers.com/showthread.php?t=1788313
Do some research on kernels, but at the time of writing I can recommend imoseyon's Leankernel. That and instructions are here:
http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v05-beta-81612/
N00bs, Both of ^these^ steps above are completely optional and if you do choose to try them THIS THREAD is NOT the place to ask for support. Realize that before you start messing with stuff you don't understand.
If this guide helped you out, please consider hitting the thanks button.
Thanks
As per request, here's some initial screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium

I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out. Also I could not get WiFi tether to work or the built in portable hotspot. It sucks too because I actually pay for the service
Sent from my SCH-I535 using Tapatalk

majmuni said:
Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
cell128 said:
I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?

snoshreddax21 said:
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?
Click to expand...
Click to collapse
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk

Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium

Flashed and currently booting hopefully I keep it for a whole day lol. Do love the stock experience better than touchwiz
Sent from my Nexus 7 using Tapatalk

cell128 said:
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
You might try reformatting your card in your computer, but if that doesnt work I had a similar problem a while ago. For me I had to dig around in the preferences of my music player to direct it to the right folder (it would be mnt/extsdcard/[music folder]). It might be trying to find your music/pictures in the phone's internal memory rather than its SD card.
majmuni said:
Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It was in the post on Cyanogenmod's Google+ page, OP updated. Sorry about that

hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha

digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
I'm almost postive TWRP is your problem. I first tried it with the CWM touch version and that didn't work for me either. I think CM10/CM9 are very picky about which recoveries are compatible. Let me know how it goes for you.

digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk

cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i used the unlock that was mentioned in the guide as people were reporting it was successful unlocks on the forums so i went ahead and used that.....im making my initial backup right now thru CWM non-touch and im gonna drop the zips for CM10 and gapps and will flash in the morn, im tired lol
one thing i did notice though is that for some reason my drivers are saying hardware id missing, and that only happened after root......i kept my imei but lost my hardware id lmao, i can still drag/drop files onto my phone but i have to switch from MTP to PTP mode for usb settings then switch it back to MTP to get access to the card/phone drives

digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Cell is correct, make sure you are using the "CWM 6.0.1.0" version. I'll update the OP so others don't get confused.

Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium

jaj6503 said:
Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
That's a very good point, and let's just clarify right now, I'm not a cyanogenmod developer and I don't have any control over how stable these builds come out. So if you flash and all is well except your MMS isn't working, I can't do anything for you and you're in the same boat as the rest of us. Thanks for bringing that up, jaj.
Sent from my SCH-I535 using xda app-developers app

I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium

digitalsynner85 said:
I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Glad to hear it worked out for you
Sent from my SCH-I535 using xda app-developers app

since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.

slick_shoes said:
since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.
Click to expand...
Click to collapse
If you download the EZ Recovery app from the play store and flash CWM as mentioned in the guide, it will just overwrite the preexisting TWRP image and you can continue on from there.

I'm not understanding why the version or type of recovery matters. What does 6.0.1.0 do that twrp doesn't do except for supporting kexec?
Maybe I misunderstood what recoveries are all about. I had 6.0.1.0 for kexec support. Now that the bootloader is unlocked I'm thinking of going back to twrp.
Flashing the cm10 build should write to system and place a boot.img with the kernel on the phone. I don't see how a recovery would make a difference in doing this.
Forgive me if I missed something. I'm not questioning your intelligence or anything, just a curiosity as I only switched to cwm to use lean kernel with kexec.
Perhaps I missed even more, I see there is an alpha build of cwm that explicitly states it's for unlocked phones. Color me confused.
Sent from my SCH-I535 using xda app-developers app

[GUIDE][ICS]How to root stock

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
presents....
A guide to root the new ICS UVLH5 firmware update.
This guide will try and make it very easy to root your stock firmware for those of you who are having
problems or don't want to wait for a stock rooted rom
anyways here goes the step by step assuming that you have a Samsung Galaxy S Blaze 4g T769 and are on ICS
UVLH5 firmware.
Before anything of course you'll need the files and here they are:
ClockWorkMod Recovery
Blaze Pit
Odin 1.8.5 Zip
SuperUser Zip
After downloading all the files first move the Superuser.zip to the root of your sdcard..not internal sdcard but the removable one. Then unzip the Odin zip and once unzipped:
Step 1:
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR for clockworkdmod you downloaded. Click PIT and select the Blaze PIT your downloaded.
DOUBLE CHECK THAT YOU HAVE REPARTITION UNCHECKED
Step 2:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down
Then while holding the voume keys plug in USB cable
You should now be in Download Mode
Step 3:
Make Sure repartition is still unchecked and click START in Odin.
Step 4:
When done the phone will reboot to the OS after this you have to reboot to recovery, here are a few ways.
1. adb command: adb reboot recovery
2. volume combo.
a. turn off phone.
b. hold volume + and volume -
c. while holding the volume buttons hold the power button for 10 seconds
d. after the 10 seconds release power button but keep holding volume buttons until you get into CWM recovery
Step 5:
Flash the SuperUser zip file
Step 6:
Reboot to System
Step 7:
Check whether root took or not.
Step 8:
If it did come back here and click thanks
Credits:
CWM (shabbypenguin)
Odin 1.8.5 (k0nane)
SuperUser (chainfire)
Hosting (gfx.myst)
TFQ ( cus we here to help )

Because I can lol

Do we need to update via kies first?
Sent from my SGH-T769 using xda app-developers app

Wait I did this a little earlier and I didn't flash the pit. Will this cause any problems down the road?
Sent from my SGH-T769 using xda app-developers app

shaikmonster said:
Do we need to update via kies first?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Yes or use the tar file a user uploaded around here a bit earlier.
KrimsonChin said:
Wait I did this a little earlier and I didn't flash the pit. Will this cause any problems down the road?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
If it flashed fine then I don't think it'll cause you any problems down the road.

Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app

Where in the process do we do the downloaded tar file?

im_awesome_right? said:
Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
nope just for windows as Odin is only windows compatible
shaikmonster said:
Where in the process do we do the downloaded tar file?
Click to expand...
Click to collapse
the TAR file is the CWM recovery

im_awesome_right? said:
Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I dont think there's a MAC version of Odin.... if you can somehow flash the CWM, you're golden. until then... ::shrugs::

Do I just drag the superuser zip to sd? gotta make sure..

erikmm said:
nope just for windows as Odin is only windows compatible
the TAR file is the CWM recovery
Click to expand...
Click to collapse
The ics tar file

Worked for me
Thanks erik! Looks like I've got root!

motez23 said:
Do I just drag the superuser zip to sd? gotta make sure..
Click to expand...
Click to collapse
you can. or download it. the important part is remembering whether its on your internal or external SD card when you go to flash it in CWM. as long as the MD5 is good, you're good as I figured out yesterday, my work computer messes with MD5's like a mutha******

I didn't expect to be able to do that so easily, but it all worked! Thanks much.

I had used the first stock root posted here, but didn't bother updating it to the minor patch that was released. I updated to ICS using Kies, knowing that I would lose root, and since my phone was rooted I was half expecting it to not work.
Well it did, and it almost worked too well. I was pleasantly surprised that I didn't even lose any apps or settings in the process. I lost root of course, although surprisingly superuser is still loaded on the phone. (I've confirmed the phone is not still rooted)
Anyways, my memory is a bit foggy, but doing this process is a total wipe on the phone right? I might even prefer that.

Cirkustanz said:
I had used the first stock root posted here, but didn't bother updating it to the minor patch that was released. I updated to ICS using Kies, knowing that I would lose root, and since my phone was rooted I was half expecting it to not work.
Well it did, and it almost worked too well. I was pleasantly surprised that I didn't even lose any apps or settings in the process. I lost root of course, although surprisingly superuser is still loaded on the phone. (I've confirmed the phone is not still rooted)
Anyways, my memory is a bit foggy, but doing this process is a total wipe on the phone right? I might even prefer that.
Click to expand...
Click to collapse
The first couple boots will be laggy. That's the nature with any rom
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

I'm rather confused by your quoting my reply, and not replying to it.

Cirkustanz said:
I'm rather confused by your quoting my reply, and not replying to it.
Click to expand...
Click to collapse
honestly, as am i, as my reply had nothing to do with your post perhaps a lack of sleep, perhaps a miss click, idk. but I guess we never will

I wish I read this thread sooner.
Here's my situation:
I had a rooted Gingerbread stock ROM that I upgraded to the official ICS update using Kies. I then used the same ODIN method to root the phone and now it won't boot up past the "Samsung Galaxy S" loading screen. Any ideas on where to go from here? I'm afraid if I do anything else haphazardly, I would only be digging myself deeper into this hole.
Thank you!

You flashed a GB kernel on ICS. If I were you, I would flash a GB .tar using Odin (unless you can find an ICS .tar somewhere?). Then, boot into recovery and wipe system and data, because you'll see a blue ICS menu flickering in the background upon booting up into the GB phone setup screen. At least, that is what happened to me. Then, upgrade to ICS using Kies.
Sent from my SGH-T769 using xda app-developers app

[Q] Rooted S3: How Do I get Verizon Update??

I generally don't root my phones but I needed to increase the size of my SD cache so I rooted it.
I have read the threads on what to do if you have rooted and installed a new rom but I only did a portion of this process.
To root the phone, I followed the guide on this forum and completed the following:
Enabled USB Debugging and Unknown Sources (Phone)
Double-clicked "RootDebugfs" on PC with phone connected to computer using OEM USB cable. It ran to completion.
Installed - ez_unlock.apk and rom_manager.apk
At this point SuperUser was supposed to install but it didn't. I downloaded and installed Superuser, updated the Superuser binaries, and I was rooted. I confirmed this with Root Checker.
I never unlocked the phone with Ez-Unlocker
I never used Rom-Manager either.
I did install SD Speed Increase and increased the SD cache size from 128kb to 1024 kb.
Now there is a Verizon update that I should probably get. In the near future I will need to update to Jelly Bean.
What do I need to do to install these Verizon updates?

If you're rooted, stock recovery and not unlocked you can take any OTA but it will break root. But as far as I've seen you can root again.
If you're unlocked with custom recovery you need to flash back to full locked stock and stock recovery to accept OTA.
Sent from my SCH-I535 using xda app-developers app

As long as u have stock recovery then just take the ota and re root. If u don't have stock recovery the gym flash it with ez recovery app. That's how I updated my phone this morning
Sent from my SCH-I535 using xda premium

You could also just wait until someone creates a flashable zip and flash through CWM or TWRP.

Thank you for the replies.
I did not change anything regarding recovery. I only did whats indicated in my initial post.
If I do the OTA update will I just root again using the same process I did initially?
If so, is that just "double-click "RootDebugfs" on PC with phone connected to computer using OEM USB cable and run it to completion."?
I appreciate the support provided and appreciate all responses.

chinook9 said:
Thank you for the replies.
I did not change anything regarding recovery. I only did whats indicated in my initial post.
If I do the OTA update will I just root again using the same process I did initially?
If so, is that just "double-click "RootDebugfs" on PC with phone connected to computer using OEM USB cable and run it to completion."?
I appreciate the support provided and appreciate all responses.
Click to expand...
Click to collapse
Exactly. That's how I did it.
Sent from my SCH-I535 using xda premium

Just be aware that it's not unheard of for the root exploit to get blocked in the new OTA. It doesn't sound like that has happened here, but just FYI. That's part of why the common mantra is to just wait for someone to post a rooted version of the stock rom... or go with a custom rom (shout out to CleanRom here).

ponyboy82 said:
Just be aware that it's not unheard of for the root exploit to get blocked in the new OTA. It doesn't sound like that has happened here, but just FYI. That's part of why the common mantra is to just wait for someone to post a rooted version of the stock rom... or go with a custom rom (shout out to CleanRom here).
Click to expand...
Click to collapse
Yes you are correct about that. Luckily this didn't happen here. I also re locked the bootloader before I accepted the ota
Sent from my XT907 using xda app-developers app

musclehead84 said:
Yes you are correct about that. Luckily this didn't happen here. I also re locked the bootloader before I accepted the ota
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot for the information. I'm sure I can handle that. I'm considering not doing the update and then either waiting for the Verizon update to Jelly Bean or find a Jelly Bean ROM and take that route.
Thanks again.

Ota rootkeeper ???

Has any one perhaps used this app
Essentially ist an app that allows you to back up and restore your root access therefore allowing you to take updates over the air and then afterwards allowing to restore your root. I saw a couple videos on you tube but they were all dated months ago I was wondering if any one had any comments or feedback based on there own experience using this tool cause in theory it sounds pretty awesome
Sent from my SCH-I535 using xda app-developers app
Sent from my SCH-I535 using xda app-developers app

I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium

ota rootkeeper
Firealoha said:
I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
is there any chance you could list the steps you did involving ota rootkeeper....i still have ics 4.0.4, stock rooted unlocked. didnt take the jb update cause i didnt want to lose everything....thanks

Both times I used it I was running CM10 stable and CWM touch 6.0.2.3. I then did a full wipe, restored my stock back up, downloaded voodoo and hit "protect root", and then accepted the OTA. It was that easy.
The first phone I carelessly forgot to re-unlock my bootloader using ez-unlock and when I rebooted I got the dreaded triangle. Learned my lesson with the second one. I remember something about having to answer some ?'s during the reboot process about keeping my custom recovery, but I don't remember exactly what they were. The answers were pretty obvious.
Also, I just tried ez unlock now and it says device status unknown. After the update I remember getting that msg too for some reason. I just locked the bootloader and then unlocked it for good measure, making sure to get the "your bootloader has been successfully unlocked“ msg.
Good luck and lmk how it turns out
Sent from my SCH-I535 using xda premium

So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app

MIKEYSAKZ said:
So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry was to busy watching the Super bowl and didnt have acces to a computer on my last post. Hopefully this is a little easier to follow.
1) Return to stock rooted/unlocked ics (in my case it was the backup I made of my phone straight out of the box)
2) Download the app and when you run it, it should have all but one of the boxes checked (you'll see what I mean when you open the app). Click on "protect root" and the final box should now be checked (indicating that a protected su copy is available)
3) I did not select temp unroot as an option, so I cannot attest to what selecting this will do. Once I selected "protect root", I went and initiated the OTA download. I did this with two gsIII's following the above sequence and had zero problems (well, except for forgetting to re-unclock my bootloader).
4) After the phone has downloaded the update it will ask you if you want to allow CWM (or whatever your recovery is) to install the unsigned.zip - select YES and answer YES to keeping root.
5) Once the phone is done booting up go into ezunlock and re-unlock your bootloader before booting into recovery or rebooting the device.
I think most people will agree that this is kind of a waste of time as their are a number of debloated Stock JB ROMS on this forum that you can flash without having to go through all the hassle of doing all this. I chose to do it as more of a learning tool. This is my first Samsung device having owned and rooted/S-Off''ed two previous HTC devices. I am by no means an expert, but this community has been so helpful to me over the last few years,that I figured it's about time I started spreading the Aloha. Good Luck!

[Q] Bad Recovery flash? (SOLVED)

I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich

Anyone?
Sent from my SCH-I535 using xda premium

Never mind...

Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.

david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium

Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app

stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!

I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app

stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium