[Q] Noob questions re: Auto Update - Verizon Samsung Galaxy S III

Last night, I read the posts re: the auto-update and the potential havoc it can wreak on my phone. As a Noob (I did my first root, this weekend), I'm concerned and would appreciate any help understanding the jargon and my situation.
I just got a SCH-I535 and despite "having no business" rooting it, curiosity got the better of me and I followed eMpTy43's [GUIDE] For beginners - Root Verizon Samsung Galaxy S3 SCH-i535/d2vzw. Per those instructions, I rooted using "Root Debug FS", unlocked using "EZ-Unlock", I installed "ROM Manager" and flashed "Clockwork Mod Recovery". On that last step, I had some problems due to the formatting of my external SD card. I think I successfully created a Nandroid backup to both my internal SD and, finally, to my external SD. Subsequently, I purchased Titanium Backup Pro. I ran "Batch Backup/Restore All" to my external SD.
If I understand correctly, I now have a "rooted", "unlocked", "stock ROM" SCH-I535 with a "custom recovery". Is that right?
My device reads that it is running baseband version VRLG1 and kernel version 3.0.8. From reading the posts on the auto-update, it seems my phone should need to auto-update. Is that correct?
Late last night, if I understood correctly, it seemed community members suggested several possible steps:
Some people suggested that I could prevent the auto-update from running my using Titanium Backup to freeze SDM 1.0. Is that correct? After I return from work and get the kids to bed tonight, I intend to look up what SDM 1.0 does. But, if anyone wants to help here, it'd be appreciated.
Someone posted a suggestion to install Voodoo OTA Rootkeeper, which I did. Does that, in effect, do the same thing as freezing SDM 1.0? Is there a problem in doing both?
I also read that having a "custom recovery" makes the entire issue moot. If that's correct, why would that be?
If I dodged the bullet, it's my understanding that I should either (1) sit tight and wait for the community to develop guidance for n00bs or (2) re-lock and un-root the phone since I have no business doing this in the first place.
Am I understanding all this correctly? Am I missing anything? Any recommendations?
Thanks in advance for any help.

Yes you are correct you have a rooted, unlocked(bootloader), stock ROM, and a custom recovery. (clockwork mod recovery that you flashed through ROM Mamager)
Because you have the Clockwork recovery installed the update won't actually install. It may still download and annoy you though. The reason it won't install is because over the air updates(OTAs) rely on the stock Android recovery for installation. By flashing Clockwork recovery you have replaced the stock recovery and that causes the update installation to fail.
I don't know what SDM 1.0 is exactly. I do know that freezing it with Titanium Backup will stop the update from downloading and annoying you and doesn't seem to cause any other issues.
All in all with the custom recovery you will be safe from the OTA. However, I would freeze SDM 1.0 for good measure to stop your phone from trying to automatically download the update. (even though with custom recovery it will never install)
I highly suggest you go through and read read read all the sections in Verizon Galaxy S3 (especially stickies) and anytime you come across a term you don't understand Google it. Just keep reading and reading and Googling. That's the best way you can learn more about all this. Until you understand it all a bit better I wouldn't do more than what you already have. (i .e. Flashing ROMS and kernels etc...)

Thanks for the substantial reply. I'm resting a lot easier at work, now. It would have been a real pain to have a brick 2 days after my first root.
Sent from my SCH-I535 using xda premium

Related

Why do you need ClockworkMod?

Why do you need to set up a recovery or cwm for your phone after it's been rooted?
Almost all of the Kernels and ROM's are installed/Flashed through the Clock Work Custom Recovery. Plus you can use it to do Nandroid backups and clear cache and so on. It's really a great utility to have.
Ok thanks. I'm just really nervous about trying to CwM my phone again cause last week I had to get a new phone cause I did something wrong.
Do you think you could possibly give me step by step instructions on how to properly recover my phone using CwM? I'm not the brightest person and Im kinda clueless with all of this stuff.
EDIT:
Will this do the trick?
http://forum.xda-developers.com/showthread.php?t=997359
If I do this is my phone ready?
ketchkev000 said:
Ok thanks. I'm just really nervous about trying to CwM my phone again cause last week I had to get a new phone cause I did something wrong.
Do you think you could possibly give me step by step instructions on how to properly recover my phone using CwM? I'm not the brightest person and Im kinda clueless with all of this stuff.
EDIT:
Will this do the trick?
http://forum.xda-developers.com/showthread.php?t=997359
If I do this is my phone ready?
Click to expand...
Click to collapse
First of all, most people around here aren't experts when they begin this process - but they definitely AT LEAST have a clue - so I suggest you take some time doing research before you even attempt any of these things. If you're not wanting to do so, try to find someone that you know that has done some modding and see if they can help you. Our references around here are pretty clear and cover all bases, so there shouldn't be too many questions to ask after reading around.
To answer your question, that thread you linked has an odin package that includes a custom recovery (clockworkmod) along with a complete 2.2 stock image, so it would be a good place to start.
Do you need to use cwm if you just wanna use apps that require your phone to be rooted? Sorry for all of the questions.
CWM and Rooting aren't really connected. Some background info, from what I've learned thus far:
Rooting just changes a couple files in the OS portion of Android to allow you to have Superuser access (like Administrator on a Windows machine). All of that goes on in the OS partition.
CWM Recovery, its full, proper name, is a custom Recovery. The default recovery allows just a factory reset for the most part. CWM Recovery allows that, but also allows many more options; clearing user/Dalvik cache, performing Nandroid backups and restores, enabling or disabling Voodoo (note that you need to have a separate Voodoo-compatible kernel installed), flashing things from ZIP files on your SD card, and so on.
The short answer then is no, you don't even need to think about CWM if all you want to do is root your phone and use apps that require it to be rooted.
ketchkev000 said:
Do you need to use cwm if you just wanna use apps that require your phone to be rooted? Sorry for all of the questions.
Click to expand...
Click to collapse
If you are just wanting to use apps that require root access then no you don't have to use CWM. You need CWM if you are going to flash a kernel or ROM or any other Mod for your phone. Rooting and CWM are two different things. As long as your phone is rooted, then you shouldn't have trouble using apps that reuire root access, with or without CWM on your phone. At least I didn't when I first began doing this stuff. Granted Im still a noob to an extent but my phone was rooted for a long time before I ever installed CWM and I never had an issue with the root apps
Edit: didnt' mean to be redundant. Chromewolf posted while I was typing mine
add144 said:
I think its full, proper name would be ClockworkMod Recovery
Click to expand...
Click to collapse
Damnit! I needed to have found someone else I could have bet money on that not only would I get corrected on that, but that it would be by add. No money for me. XD
But seriously, while add is correct on the matter of semantics, the point I was trying to make is that CWM is just a custom Recovery (which I've sort of taken to needlessly capitalizing lately to emphasize the difference a bit more), as opposed to an app or something.
Brief off-topic: A present for you add, especially if you're a gamer. I hope you lol at it, I know I always do (and I'm the *functional* rules lawyer of the group, LOL), and I'm not the one who wears it!
http://www.warehouse23.com/item.html?id=OWD45013-2XL

Questions about using Bootstrap on Atrix 2

I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
There's a script in the thread that gives you cwm on boot. The catch is it goes to recovery first EVERYTIME you boot.
ubersoft said:
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
Click to expand...
Click to collapse
In the situation that you describe, even the CWM on boot that mtnlion mentioned, still may not get you into CWM. In that case your ONLY option is to flash the fxz file with rsd lite, that will restore you to a full stock out of the box atrix 2, which you then have to re-root, then re-install bootstrap, then restore your backup.
Sorry there is not an easier way right now, but until the bootloader is unlocked we can't flash CWM, so that we can get to it, as you would the default android recovery, because that does require the default recovery to be replaced, and an unlocked bootloader is required for that to work.
Safestrap is really a tool that is only useful to those actually developing, or people that we have asked to test something out, and since lfaber06 and I don't have a version to release to the public that we are happy with yet, that is not an option.
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
ubersoft said:
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
Click to expand...
Click to collapse
No, if you get a bad flash you still may not be able to get into CWM, since it requires files that are actually in the Android ROM, to fully work. Read my post above ^^^
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
ubersoft said:
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
Click to expand...
Click to collapse
No, it is perfectly safe, but the restore is just a little more complex than you had to deal with, with other phones. I have done exactly what I mentioned above SEVERAL times, with out issue, since I am doing a ton of dev work on this phone.
The ROMs that are out there are great right now, and lfaber06s ROM is really good, and I will be releasing a version of CM7 very soon. If you wait for a bootloader unlock, it may never come, or at least it may not be very soon.
The worst thing that happens is that you have to flash the fxz, which it is documented how to do that with RSD lite very well in the noob thread here. then you can restore your backup with out issue, it is just a few extra steps.
Bootstrap is really safe as is all of lfaber06 Roms right now. I have no problem recommending either of his roms to anyone. They are both very good. As Jim has stated the only problems we have is if something wrong happens on boot, but with the fastboot files, RSD lite, and the one click root method you have everything available to get you right back to where you were before you flashed.
I can promise you everything works very good as I have soft bricked my phone so many rimes in the last 2 weeks that I have become very efficient at getting back to stock, rooting and then flashing a backup with bootstrap and can be back in business n around 20 mins. Just always be near a computer when you start flashing things. One thing that will help out is to keep a backup of the bootstrap on tour SD card so if you have something go wrong you don't have to redownload it again.
We have a very good group of people here and if anyone has any problems we can get you through them and back running
Well there we are then!
So after getting a clearer picture of the situation (thanks for the explanation) I blocked off most of the night, installed bootstrap, then installed lfaber06's Supercharged v4. It took forever, but it worked flawlessly.
Thanks everyone for your patience and encouragement.

[Q] Best Root Method / Preference -- DooMLoRD's, EasyRoot, or SuperOneClick

Great site and forum you guys have here. I've been lurking in the background for about a month now since converting to Android from Crackberry, studying as much as possible about rooting my new Skyrocket.
I've narrowed down the method that I'll be using shortly to the 3 subject options, and was just wondering, what you recommend and why? I've also watched videos on each, and they all seem like they work and I can handle the task. But I want to avoid tripping the flash counter or getting myself in other more complicated trouble that I'd need your help with.
My plan is to root, flash CWM, do a Nandroid backup, then just freeze some things up using Titanium Backup to start. I think I said that right. Maybe not. But that's the plan for now, without new ROMs or kernels. Thanks in advance for any suggestions, and I apologize for the rookie questions. Again, great forum.
I can tell you a little trick that might save you from ever having to trip you flash counter. Use the odin method of rooting, its in the dev section. After you push cwm with odin, boot into cwm and make a backup of stock unrooted. Then proceed to flashing the superuser zip and rooting. Take the stock unrooted backup and save it to your desktop or something. Now your rooted with cwm . If you ever have to restore to stock you can restore the unrooted stock backup, then push the stock recovery with odin and presto your back to stock without tripping counter. Only works if you backup stock firmware before rooting. Also I've noticed that usually when I softbrick I can get away with just flashing cwm in odin, booting into recovery and proceeding from there. If I could start all over that's how ide do it I think. Just an idea. Also this method gets you farmiliar with odin, which you'll desperately need someday, if you already know how to use it you'll be set. A good thing to do is know is how to fix your phone "before" you break it lol(cause you surely will at some point). Then there's no panic when it happens cheers and good luck!
Here's a link to the root method I've suggested
http://forum.xda-developers.com/sho...CWM | ODIN | SGH-I727 and SGH-I727R Skyrocket
And were always here to help if you have questions.
Sent from my SAMSUNG-SGH-I727 using xda premium
pls4ms said:
Great site and forum you guys have here. I've been lurking in the background for about a month now since converting to Android from Crackberry, studying as much as possible about rooting my new Skyrocket.
I've narrowed down the method that I'll be using shortly to the 3 subject options, and was just wondering, what you recommend and why? I've also watched videos on each, and they all seem like they work and I can handle the task. But I want to avoid tripping the flash counter or getting myself in other more complicated trouble that I'd need your help with.
My plan is to root, flash CWM, do a Nandroid backup, then just freeze some things up using Titanium Backup to start. I think I said that right. Maybe not. But that's the plan for now, without new ROMs or kernels. Thanks in advance for any suggestions, and I apologize for the rookie questions. Again, great forum.
Click to expand...
Click to collapse
I'm no expert but when I updated from 2.3.5 to 2.3.6 using S.O.C was no longer an option. I had to use the all power ODIN. link
But I suggest reading, googling, and rereading steps until you're confident of what to do without guessing if you're doing it right or not.
BTW, don't discount ROMs, they will make you love your phone more than you thought possible. And with the initial Nandroid bup you can always revert...
Good luck...
.
cdshepherd said:
I can tell you a little trick that might save you from ever having to trip you flash counter. Use the odin method of rooting, its in the dev section. After you push cwm with odin, boot into cwm and make a backup of stock unrooted. Then proceed to flashing the superuser zip and rooting. Take the stock unrooted backup and save it to your desktop or something. Now your rooted with cwm . If you ever have to restore to stock you can restore the unrooted stock backup, then push the stock recovery with odin and presto your back to stock without tripping counter. Only works if you backup stock firmware before rooting. Also I've noticed that usually when I softbrick I can get away with just flashing cwm in odin, booting into recovery and proceeding from there. If I could start all over that's how ide do it I think. Just an idea. Also this method gets you farmiliar with odin, which you'll desperately need someday, if you already know how to use it you'll be set. A good thing to do is know is how to fix your phone "before" you break it lol(cause you surely will at some point). Then there's no panic when it happens cheers and good luck!
Here's a link to the root method I've suggested
http://forum.xda-developers.com/sho...CWM | ODIN | SGH-I727 and SGH-I727R Skyrocket
And were always here to help if you have questions.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
This^^^^ I use odin and only odin
After a few days of research and trying to figure out how not to trip the flash counter, this is the best way. Huge thumbs up for the suggestion!
Wow. That is really great information. Thank you! I had written off the Odin method, as it seemed a little complicated for a rookie like myself -- hence why it wasn't included in the subject options.
But after reading what you had to say, it makes complete sense. The Odin method is the only way to make a complete backup (using CWM) of my truly unrooted device, where the other methods, the mirror (backup) would be of a rooted device so a restore back to stock would be more difficult. Correct?
I just read all 20 pages of the link you supplied, and it seems I've got a pretty good understanding of what to do and what not to do. Will give it a whirl today and let you know. By the way, someone posted a video which talks about how the superuser.zip file is not necessary -- this is not true if you aren't putting on a new ROM. Which I am not. Just a heads up for anyone else out there looking at it. Thanks again man, you nailed it.
cdshepherd said:
I can tell you a little trick that might save you from ever having to trip you flash counter. Use the odin method of rooting, its in the dev section. After you push cwm with odin, boot into cwm and make a backup of stock unrooted. Then proceed to flashing the superuser zip and rooting. Take the stock unrooted backup and save it to your desktop or something. Now your rooted with cwm . If you ever have to restore to stock you can restore the unrooted stock backup, then push the stock recovery with odin and presto your back to stock without tripping counter. Only works if you backup stock firmware before rooting. Also I've noticed that usually when I softbrick I can get away with just flashing cwm in odin, booting into recovery and proceeding from there. If I could start all over that's how ide do it I think. Just an idea. Also this method gets you farmiliar with odin, which you'll desperately need someday, if you already know how to use it you'll be set. A good thing to do is know is how to fix your phone "before" you break it lol(cause you surely will at some point). Then there's no panic when it happens cheers and good luck!
Here's a link to the root method I've suggested
http://forum.xda-developers.com/sho...CWM | ODIN | SGH-I727 and SGH-I727R Skyrocket
And were always here to help if you have questions.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
A restore to stock wouldn't necessarily be any more complicated because we have odin files for that too. But it will trip your counter. Sometimes tripping the counter is unavoidable, I pretend like mine doesn't even exist. Let us know if you need any help
Remember to make the nandroid backup of stock unrooted before you flash the superuser.zip.
When you do flash the superuser zip, it might throw up an error and not flash, this is ok, happens to me everytime, just keep trying to install it and eventually she will take:thumbup:
Sent from my SAMSUNG-SGH-I727 using xda premium
Perfect success! Couldn't have gone any better. From the driver installs, to the Odin launch, CWM backup, and finally the SU flash -- each step was flawless. It took 3 tries on the Superuser.zip file before it installed without errors, which was expected. Thank you, thank you, thank you!
I just updated Superuser to the latest version, but now I'm seeing that Busybox seems to be an important add-on now that I'm rooted for some apps to work properly. Agreed? If so, is the popular version on Play the one to download?
Also, whats the best way for me to send the backup I just made from my phone to computer as you mentioned? Where is it located on phone? Thanks again. You've been a huge help, and I'm stoked to be part of the club -- maybe just a junior member still, but learning more each day.
cdshepherd said:
A restore to stock wouldn't necessarily be any more complicated because we have odin files for that too. But it will trip your counter. Sometimes tripping the counter is unavoidable, I pretend like mine doesn't even exist. Let us know if you need any help
Remember to make the nandroid backup of stock unrooted before you flash the superuser.zip.
When you do flash the superuser zip, it might throw up an error and not flash, this is ok, happens to me everytime, just keep trying to install it and eventually she will take:thumbup:
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
The cwm backup will probably be on you external SD under clockworkmod>backup. If not on external use internal. Just mount USB storage on your computer. After you get the stock backup off your SD , boot back into recovery and make a backup of your rooted stock firmware if you already haven't. You want to always have atleast one nandroid on your SD in case boo boo's occur.
As for the busy box thing I'm not exactly sure. All I can say on that is if any app request you to update it just allow it to. Maybe try the market app you mentioned. I'm not entirely too sure. Also maybe consider flashing a rom. You'll have that rooted backup on your SD you can restore whenever you'd like.
Glad everything went well for you. That's a good example of what reading before attempting does. Good job
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks again for the help and props. More success yesterday; moved the full stock ROM (unrooted) Nandroid to my computer, and then made another Nandroid of my rooted stock ROM. That too I put on the computer, but also left a copy my SD card.
Installed Titanium Backup Pro, and am now studying up on which .APK files I can safely freeze. Found a spreadsheet from the SG2 forum, and I'm guessing it's applicable for our device. Would post the link, but I'm not allowed to yet.
Lastly, I picked up the Nexus 2100 mah battery for which I'll be installing shortly as well. Starting to get more tuned up now, but you are right, once all this is complete I'll look at some custom ROM's as well. I guess freezing all of these files wouldn't really be necessary if I put on a new ROM anyway. Oh well. Baby steps.
samsung infuse
bought rooted Samsung infuse, but can not get my contacts.
At&t phone.
infuseal said:
bought rooted Samsung infuse, but can not get my contacts.
At&t phone.
Click to expand...
Click to collapse
You just brought a year old thread back to life and your talking about an infuse which has nothing to do with the skyrocket. Search on the infuse topics.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Stock GB Rogers to JB questions

I've been sitting on my stock Rogers Infuse 4G since I got it, hoping that they would at the very least release an update to ICS. I've pretty much given up all hope, especially now since the Infuse was listed as one of the "violators" in the recent lawsuit. So, in giving up there, I've started to try and get up to speed with what's available in terms of custom ROMs for the Infuse, etc...
I previously had a Captivate (seems like I pick the wrong phones) and have kept that one stock as well (now my wife's phone) aside from the official 2.3.3 update Samsung came out with for it. I checked in here once in a while to try and keep track of some of the updates as I thought about going for a custom rom, but I never had the balls to try anything (I've only ever flashed one phone in my life, and it was bought 2nd hand for $20 ) since I actually *must have* a working phone due to having a kid (daycare calls are kind of important!). However checking today, it seems like I am totally out of the loop and I just don't have the time to try and wade through thousands of pages on various threads to find out what the current "ways" are and such... but I know what I want to achieve so I'm hoping you folks are nice enough to at the very least give me a "search you noob" and point me to some threads :silly:
Since I'm totally stock, from what I'm gathering I think I need (and really I more of need a complete checklist of things to do rather than a "do it for me" kind of thing) to do is:
1) jot down my modem and apn settings and such (already done)
2) back up everything i need, pop out sd card (know how to do this)
3) wipe/clear to factory default (... and this)
4) back up the current rom - everything in case I want to return back to exactly the way the phone is stock
5) figure out what i need to do to flash CWM or something so I have the necessary recovery mode options?
6) flash to ICS (since from what I gather, I need to do that if I want to go to JB)?
7) follow instructions I found on the unnoficial CM10 JB thread to flash to JB
?) flash a new kernel? (is this done already during a rom flash; are there any new kernels?)
As commented, I can figure out 1-3 since I'm not stupid, but I have no idea what is even needed to do 4, nor do I know exactly all the tiny, necessary, steps to do the rest after that... especially since reading some things it seems like most of this is for AT&T users and since I'm on Rogers with a I997R (I assume the R means Rogers), I don't want to mess up my modem or other things to prevent the phone working for me... and these are the steps I'm hoping people can help me with.
So far, in prep, I've noted my phone info (basically everything in Phone settings) and I can back up all my apps and such that I care about, and I've downloaded the unofficial CM10 JB download and the Google apps apk as well, and on the same thread was a link to a 1-click ICS flash or something... so I got that too. Since I want to end up with JB, I'm not too concerned (or should I be?) with it being AT&T stuff to get to ICS, since it's the JB flash that I'd really want to ensure works for me.
Is anyone willing to help me out? I really wish I didn't have to be the "next loser" to make a thread like this but I just haven't had the time to be able to keep up with all the info going around (voodoo mods and whatever else?!) to be able to make sense of all this myself!
Thank you!
This looks like a good place for you to start
http://forum.xda-developers.com/showthread.php?t=1197248&highlight=how+to+root+rogers
First thing to do of course is read, read, read. Understanding what you are doing and why you are doing it is the most valuable resource you can have.
The gist of it is though: to install the custom updated roms, you need root. For Rogers infuse users that is very easy to do; all you have to do is install a rooted kernel in odin. After you do that you make a nandroid (and/or EFS) backup, and install whatever rom you want. CM9 and CM10 have their own kernel, so don't worry about that.
adfurgerson posted the step-by-step guide above me, although the links in the OP may be down. I have the mirrors here: http://minus.com/moAvVibed/
the 3 files in there are:
Odin_Infused_Gingerbread_Kernel_v1.zip - This is the rooted kernel you are flashing
Odin_Stock_Rogers_UXKG3_Kernel.zip - This is the stock rogers unrooted kernel if you want to unroot and go COMPLETELY stock for whatever reason (I doubt you will ever need to use this tbh)
Odin_UXKG3_rooted_no_bootloaders_v2.zip - The stock Rogers FIRMWARE. If you ever mess up you use this to "start from scratch". You will still be rooted though if you don't use the stock kernel above.
So yeah, just flash the kernel in odin as described in the above thread and you will have root + cwm.
From there you reboot into cwm (turn off, turn on holding vol+ and vol- buttons) and make a nandroid backup of your stock rogers rom (or an EFS backup with the infuse toolkit: click here), flash CM9 as per the instructions in the OP, and finally CM10 as per the instructions in the OP.
Also remember:
1. The infuse is almost impossible to hard brick. The only real way to do so is to improperly flash bootloaders, which a rogers infuse user will never have to do. Only AT&T users coming from Froyo have to do it. So keep that in mind.
2. On the chance that you get soft-bricked (screen won't go past samsung logo for example) you can always go back to flashing the stock rom/rooted kernel again in odin and start all over again.
The only thing that I can add to Threi's excellent reply is to mention the one click to ICS. It is in the first post of Scott's CM10 thread,it should give you the ICS recovery that is needed to flash JB without flashing a full ICS ROM.
I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).
j.smith said:
I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).
Click to expand...
Click to collapse
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.
adfurgerson said:
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.
Click to expand...
Click to collapse
Aha, perfect description. I didn't realize I had to get a new kernel to have CWM... and I'm guessing because of signing and such, that a custom kernel (with CWM) is required in order to flash a non-signed rom, which is why you couldn't just do it on stock, right?
Ok, so now armed with that info that clears up a lot, I guess I have just one question left (which I can probably find the answer to with some searching). I have read what that voodoo lagfix is and is this something that is standard now on all kernels (because if it can cause issues, I'd rather just have a kernel without it)? Are there any "rooted" kernels without the lagfix built in so I don't have to remember about disabling the lagfix? ...or is there a way to install CWM on to my current kernel?
*edit* Ok, I realize I might be a bit too picky about the voodoo lagfix thing. I found two good threads on dealing with Rogers specifically, so I'll read over those (and suck it up about voodoo) and see how it goes. Since my vacation got unfortunately cancelled due to a sick kid, I have some time to experiment this weekend... hopefully ending up with JB on my phone!
Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.
adfurgerson said:
Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.
Click to expand...
Click to collapse
Yep, just flashed the rooted cwm kernel and performed a backup. I read somewhere that you can/should back up your efs in case you lose your imei... so I'm just going to quickly look in to that, then i wipe and do some flashes to jb... shouldn't take long hopefully!
Ok, I seem to be stuck at trying to get the one-click ICS install to work. I've got the EZUpdater package to ensure I have the right drivers, yet everything I try with the one-click seems to tell me that the drivers aren't installed and then launches an installer which also doesn't seem to detect the phone... yet EZUpdater will run fine, etc...
I'm just about to reboot and launch device driver in a mode to list all hidden/previously installed devices and nuke them from history to hopefully purge my system of all traces of any drivers and install EZUpdater one more time to get the drivers installed.
Any reason why my phone wouldn't show up in this one-click (it uses heimdall or whatever) program, but seems to work in most everything else (adb even runs fine)?
*edit*
Got it all working! I couldn't get the one-click ICS to work for the life of me... it just didn't see the drivers even though they were there and working. I guessed maybe it had to do with me running Windows 7 x64 and having x64 drivers, but the one-click maybe being 32bit. I even tried installing the x64 Java JRE but didn't seem to make any difference.
I ended up having to flash CM9 which worked fine, then going to CM10. Had no issues doing that... wish I had just tried that before since that one-click wasted hours of my day and got me somewhat frustrated!

[Q] Want to wipe and keep root in 9.16.6 Razr Maxx HD - what are my options?

The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
dlc2001 said:
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
Click to expand...
Click to collapse
to get rid of the slowness of the phone i recommend going to a lolipop rom , LP has to be the quickest my phone has ran... ever.
-step 1 use rsd lite to flash [4.4.2] 183.46.10 fxz (make sure it ends with a 10 not a 14 or 15 or you wont be able to unlock bootloader)
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
-step 2 root and unlock use TR.apk (root)and motopocalypse.apk (bootloader unlock)
http://forum.xda-developers.com/showthread.php?t=2783912
-step 3 use ADB fastboot to Flash custom recovery, i personally use twrp there are others you can use if you decide to do the research
http://www.droidrzr.com/index.php/topic/51883-recoverytwrp-2810-11-01-14/
-step 4 flash LP custom rom, i use blisspop, it seems to have the most updates at the moment . it has really impressed me
http://www.droidrzr.com/index.php/topic/60153-rom502lollipopmsm8960-kkbl-blisspop-official/
that rom comes with supersu built in so you will have root. if your reason for having root is to have exposed, it doesnt work on lolipop so stop at sstep 3 and either flash a KK custom rom or just flash supersu which will give you root on stock kitkat
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
dlc2001 said:
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
Click to expand...
Click to collapse
yes you can install it from playstore, but once your bootloader is unlocked you can always root by flashing in custom recovery. you dont need exploits anymore
All done, worked great!

Categories

Resources