Related
So i rooted my phone, and deleted like 3 or 4 system apps, forgeting to backup. Now I'm afraid if I try to do a software update or something of the sort (after unrooting), or when if I have to bring it in to fix (have to unroot for that too) it'll brick my phone. What should I do? Any help would be appreciated.
HTC Evo 4g
Bkbitar said:
So i rooted my phone, and deleted like 3 or 4 system apps, forgeting to backup. Now I'm afraid if I try to do a software update or something of the sort (after unrooting), or when if I have to bring it in to fix (have to unroot for that too) it'll brick my phone. What should I do? Any help would be appreciated.
Click to expand...
Click to collapse
It would make it a little easier if we knew what phone you are working with. I saw you look in the Captivate section, but I don't know for sure. If it is for that phone then this would be your last resort
http://fonefrenzy.com/2010/12/19/how-to-revert-your-captivate-to-stock-with-odin3-one-click/
Most of the time the needed files can be found in custom roms. Just let us knew what phone and we can point you in a more positive direction.
Also what files are you looking for?
Sorry, HTC Evo
Also, the Sprint ones I deleted before I stopped were Blockbuster, Amazon mp3, and kindle, which are all available from the marketplace. The only htc one i deleted was the Peep. Does any of this matter?
Bkbitar said:
Sorry, HTC Evo
Click to expand...
Click to collapse
To get back to stock you would download the RUU file, and run it from windows. It will completely erase everything, and take you back to stock.
http://shipped-roms.com/index.php?category=android&model=Supersonic
As for the missing files, most files you can be found if you do a search for system dumps. You might have a hard time finding one that is not already deodexed.
Bkbitar said:
Sorry, HTC Evo
Also, the Sprint ones I deleted before I stopped were Blockbuster, Amazon mp3, and kindle, which are all available from the marketplace. The only htc one i deleted was the Peep. Does any of this matter?
Click to expand...
Click to collapse
Their should not me any problem with removing those files, your phone should still run as normal.
The phone runs fine now, what I'm worried about is when Gingerbread comes and I want to update, since I don't have all the stock apps I'm worried I might screw up my phone.
Bkbitar said:
The phone runs fine now, what I'm worried about is when Gingerbread comes and I want to update, since I don't have all the stock apps I'm worried I might screw up my phone.
Click to expand...
Click to collapse
There should be no problem when gingerbread comes out. Most people that root the phone will run a custom rom, and that rom will include any and all needed files. Also most of the time leaked gingerbread roms will come out before the real one that you can go ahead and flash.
I understand I can flash blah blah blah, but I don't like to flash in fear of bricking my phone, so I want the OTA.
Bkbitar said:
I understand I can flash blah blah blah, but I don't like to flash in fear of bricking my phone, so I want the OTA.
Click to expand...
Click to collapse
Yes, I understand you don’t want to flash and that is fine. It is almost impossible to brick it when running Unrevoked S-OFF and having a RUU file as a backup. The RUU can be used to un-brick the phone.
If you used Unrevoked to root your phone, then it installed ClockworkMod Recovery, and this will stop the OTA from being installed. If you used SuperOneClick or one of the other’s out there, you will still have your stock recovery and be able to install the OTA upgrade. The upgrade will most likely undo your root, and you will have to do it again.
please be understanding, I'm asking for guidance not ridicule. I'm not used to the Samsung came from Dinc. need to know how i would create a backup before installing a rom? any help is welcome
My opinion is that Titanium Backup is a great tool if you think you may switch ROMs/phones a lot as you can select what to restore fairly easily. If you're on the Charge now, and are just going to install the Debloated ROM, you don't have to wipe data when flashing, so you shouldn't loose your settings and such.
Another vote for Titanium to back up apps and data.
Apparently CWM isn't working properly for nandroid restores, so we're kind of screwed there. The development section has a thread by imnuts on how to do dumps of the partitions on the phone to use to restore in Odin. Should work as a fallback if you can actually get Odin to work (I can't, Heimdall won't work for me either).
If you just want to back up all your Apps / Data / Pictures (not a ROM image), MyBackupRoot does a great job. I found the User Interface to be simpler than TiBackup.
Titanium Backup is a great app to have on your device.
imnuts said:
My opinion is that Titanium Backup is a great tool if you think you may switch ROMs/phones a lot as you can select what to restore fairly easily. If you're on the Charge now, and are just going to install the Debloated ROM, you don't have to wipe data when flashing, so you shouldn't loose your settings and such.
Click to expand...
Click to collapse
i forgot to mention i now have the CHARGE(rooted but on stock ED1) and coming from DINC. the ways of rooting and roming are different and if i may say confusing to me.
i read most of the threads in the Samsung Charge section, at this moment to tell you the truth i feel i should wait till things are clear (how to root & rom 4 dummies) up a bit.
what would you recommend?
spjetrovic said:
i forgot to mention i now have the CHARGE(rooted but on stock ED1) and coming from DINC. the ways of rooting and roming are different and if i may say confusing to me.
i read most of the threads in the Samsung Charge section, at this moment to tell you the truth i feel i should wait till things are clear (how to root & rom 4 dummies) up a bit.
what would you recommend?
Click to expand...
Click to collapse
IMO titainium backup is all you ever really need. It can backup all your data and apps and even be programed to do so on a schedule. Everything else can be flashed w/ CWM or odin. I never nandroid backup.
I am able to select make backup of current rom.
The samsung charge reboots into clockwork.
But there is no option to make a backup.
Just: reboot
install zip
clear cache
format internal sd
thats it.
WTF!
Its driving me crazy.
what do i need to do first.
I flashed cwr ok.
Lost!!!!!
He took backup off of cwr for now because it will brick your phone if you try to use it as of now.. He working on it trying to get it to work.. Thats what I'm waiting on also.. I like to have a full backup before playing.
Sent from my SCH-I510 using XDA App
CWM cannot be used to backup right now. It needs a serious fix from Kousch to work correctly.
If you think you really really need a full backup of your entire system all as one file, you can use the instructions here for using Odin to do this:
http://forum.xda-developers.com/showthread.php?t=1082288
However, most people will be better off using something like Titanium Backup.
Thank you!
Ok then who is He?
And where or when or how will i know when it will be ready?
Will it just say update in rom manager?
Or will i have to check out a forum topic?
Is there a link to this information you have posted?
thanks again, and happy rooting.
First, don't use the version from ROM Manager! Last I heard it would mess up your phone. Koush is the author of Clockwork Mod and ROM Manager.
Only way to know is to keep an eye out here for one of the devs to get a working version. imnuts has been reporting the problems to Koush, so he would likely be first to say anything.
You can search for information about it, but there's not a good singular point for this info.
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.
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!
Okay, so it seems from the official OTA thread that there seems to be no problem with being rooted while updating. I will probably do OTA rootkeeper anyways just for safe measure, though.
Do I need to revert/uninstall any of my root apps? The one I have in question is Chainfire3D, since it changed some of the graphics drivers. Do I need to revert this before the update? And if so, or if it uninstalls the drivers with the update, will I need to reinstall the drivers? Nobody seems to be answering that question in the thread
Thanks to whoever helps. I am just a noob, sorry!
toastthemost said:
Okay, so it seems from the official OTA thread that there seems to be no problem with being rooted while updating. I will probably do OTA rootkeeper anyways just for safe measure, though.
Do I need to revert/uninstall any of my root apps? The one I have in question is Chainfire3D, since it changed some of the graphics drivers. Do I need to revert this before the update? And if so, or if it uninstalls the drivers with the update, will I need to reinstall the drivers? Nobody seems to be answering that question in the thread
Thanks to whoever helps. I am just a noob, sorry!
Click to expand...
Click to collapse
You need to be stock 2.3.6 to install the ICS OTA, meaning no changes to build.prop or files or so on. If you're referring to the Chainfire 3D plugins, yes you'll need to reinstall them if you're still going to be using Chainfire...
Sent from my rooted Mayan Calendar
Apex_Strider said:
You need to be stock 2.3.6 to install the ICS OTA, meaning no changes to build.prop or files or so on. If you're referring to the Chainfire 3D plugins, yes you'll need to reinstall them if you're still going to be using Chainfire...
Sent from my rooted Mayan Calendar
Click to expand...
Click to collapse
Okay, thanks! What other root apps mess with the build.prop file? Like I'm running an ad-blocker (shame, I know), Titanium Backup, some root options on juicedefender, and others I can't remember?
toastthemost said:
Okay, thanks! What other root apps mess with the build.prop file? Like I'm running an ad-blocker (shame, I know), Titanium Backup, some root options on juicedefender, and others I can't remember?
Click to expand...
Click to collapse
Just make sure you are completely stock, meaning that no system files are touched, and if they have been, make sure you restore them to stock. As for the root apps, just delete them and their files. Applications such as Ad Blocker, JD, and TiB won't hinder your ability to install the update, but get rid of them prior just to make sure there's no unforseen comlications. Also, if you have the Atrix 2 Bootstrap and CWM Recovery installed, you'll need to delete those files as well -the logwrapper, andy CWM files, etc...
Apex_Strider said:
Just make sure you are completely stock, meaning that no system files are touched, and if they have been, make sure you restore them to stock. As for the root apps, just delete them and their files. Applications such as Ad Blocker, JD, and TiB won't hinder your ability to install the update, but get rid of them prior just to make sure there's no unforseen comlications. Also, if you have the Atrix 2 Bootstrap and CWM Recovery installed, you'll need to delete those files as well -the logwrapper, andy CWM files, etc...
Click to expand...
Click to collapse
Is it more advantageous just to backup with titanium, FXZ to stock, then update and root?
Also, I saw that some people who had an mount_ext3.sh edit were getting soft bricks :/ since I edited this before the 2.3.6 update, would that hurt this process? I am honestly thinking that FXZing back to 2.3.5 might be my best option at this point to minimize problems.
toastthemost said:
Is it more advantageous just to backup with titanium, FXZ to stock, then update and root?
Also, I saw that some people who had an mount_ext3.sh edit were getting soft bricks :/ since I edited this before the 2.3.6 update, would that hurt this process? I am honestly thinking that FXZing back to 2.3.5 might be my best option at this point to minimize problems.
Click to expand...
Click to collapse
I can give you my opinions, which can be taken however you choose. TiB isn't something I recommend to people, since it has been known to cause more headaches than it does good. If you're worried about your apps being re-installed easily, just make sure before you update that you back up with Google's servers (everything), so that if you have a WiFi connection at home or at the office or wherever, you can install the OTA, and once it has installed you can re-enter your Google account info, go to the Play Store, and in a few minutes your perviously installed applications will re-install.
I haven't looked into the issues with the mount_ext3.sh, but if I were doing this, I would just FXZ back to 2.3.6 (however seen best to do so) so that I have the assurance that when installing the OTA I won't run into any problems. Now, you can do whatever you are most comfortable with, and that would be my recommendation, but again it's all up to you. Whatever you do, and however you choose to go about updating, it is probably safer to be "safe" than sorry. I wish I could be of more usefulness, but my Atrix 2 is currently in the hands of Mototola after the whole 'leak #2 to GB' test FXZ, which I worked with the dev team to some great lengths to get this resolved, but opted to send out for warranty before my time expired to do so.
My point in saying all of that is this, you're dealing with the official OTA, regardless of whatever you've installed, tweaked, modded, etc., so all you need to worry about is that you're bone stock, and then you can worry with everything else afterward -unlike many of us that tested the leaks only to find that we just didn't know enough about this to avoid bricks, as in some situations...
Just wanted to thank you again for the extra knowledge. Just FYI, it would not upgrade, even after removing all of those tweaks, so I had to FXZ down to 2.3.5 and start over. Not sure why, but it was probably a tweak I did at some point that I forgot about.