Ok, here is what I've done and where I am.
I'm using a Nexus S I9020T (original T-Mobile version). In the past I've used cwm custom recovery, flashed custom roms and obviously was rooted. The last flash I did, I upgraded to 4.0.3 stock and all went smooth, but as of right now I'm just not a fan of it.
So now, I've downgraded back to 2.3.6 stock rom. I'm also now sporting stock recovery and am rooted. I know this is a little weird, but I'm wanting the ability to do OTA updates using stock recovery, but also want root access, which is all working well at the moment.
But, I don't want to go back to 4.0.3 as of right now. So, is there an easy way for me to disable the system update notifications and stay on 2.3.6 right now and later on just re-enable them to do the update later.
From what I've read online, my best bet is to probably edit the build.prop file, but I'm not sure what content would need to go in there. I've also seen about freezing files, but I'm already getting 4.0.3 update notifications, so I'm not sure that will work.
Any help is appreciated
Related
So I want to do the new sw update but can't because I deleted some stock apps so the checksum wouldn't match and a hard reset won't restore them I guess so I would flash a stock rom but am I right thinking there isn't one yet? So how can I get to an original rom and then update or maybe make the new update work?
D2G stock rom
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
@evil yeah im kind of in the same boat, let me know if srensber solution works for you.
I froze a bunch of apps with Titanium Backup and renamed some stuff with Root Explorer. I recently just re-named everything i changed back to the factory stuff (bak -> apk) but it still doesnt seem to do any good.
I did create a number of back ups using Rom manager but i cant seem to find out where they are located and how to restore them. hmm. Not sure what to do.
Ah i realize what ive done wrong ... i didnt know you had to have bootstrap installed along with clockwork recoveryy in order to make a backup hmm. Going to need a rom of stock d2g lol.
clockwork recovery installs a boot hijack, which might be the culpirt
srensber said:
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
Click to expand...
Click to collapse
I cant seem to find the download link anywhere... and after you loaded this rom did you try to update to 2.4.3 ?
If anyone else has any input about this please help!
I have two questions...
1. I had rooted my A2 when it was 2.3.5 and deleted a few apps. When the OTA update to 2.3.6 rolled around, I couldn't update because ATT is a grouch. Anyway, to solve that problem, I had to flash stock 2.3.5 back onto the phone removing root access and everything. I then proceeded to update to 2.3.6 which is fine. that's running stock as I type this. My question is, if I root it again on 2.3.6 (I know it's there...) and I freeze apps, when another OTA update rolls around, will I be able to update again? I don't want to have to flash it back to 2.3.6...(can I even do that yet?) so any help here would be appreciated.
2. I was out and about, and was looking at one of my friend's phones. She has this HTC HD2 running Android 2.3.3 AOSP. She uses ADWLauncher, etc etc. This is a Windows Phone, originally. That got me thinking...is there a AOSP version of Gingerbread for my A2? Without Blur? I'm kinda scared to do anything to it, because I want to be able to get ICS come July. Any tips here would help.
Sorry for not using the searchbar, I was just having trouble finding this info. Thanks guys!
1. Yes. Freezing apps / removing bloat as root will almost definitely keep you from the any OTA. Its the nature of the beast. You can always return to stock and apply the updates later. Also, any major update like ICS will produce a lot of posts here about how to update from an altered rom.
2. There is development work on getting CM7 to work on our phone. Currently the only released ROM that I am aware of is lfaber06's ROM
SeekerLoki said:
1. Yes. Freezing apps / removing bloat as root will almost definitely keep you from the any OTA. Its the nature of the beast. You can always return to stock and apply the updates later. Also, any major update like ICS will produce a lot of posts here about how to update from an altered rom.
2. There is development work on getting CM7 to work on our phone. Currently the only released ROM that I am aware of is lfaber06's ROM
Click to expand...
Click to collapse
When a major update such as ICS is released, there will be alternate ways to install such as through bootstrap. Hopefully we'll find a leaked version of ICS before that, and pull the radio get CM9 working
Okay. So I'm planning on rooting it...now...but when I flashed 2.3.5 from the fxz someone provided, it said that once you updated to 2.3.6 you could never go back...but...
I'll try it.
What's bootstrap? I've heard about it and no one has been able to dumb it down for me...could anyone do that?
You can flash the FXZ after the update. It just requires a bit of modification and care. You might want to read the noob thread. It has lots of useful info.
Bootstrap is a way to backup, restore, and flash zips before android boots.
I just rooted the 2.3.6 it's running wonderfully.
Should I install the ibfaber deoxed rom? I mean I know I can do it per instructions but is it worth it?
It depends on what you want to do. If you want to apply any themes you will need to be running the deoxed rom. He also has a supercharged rom that has a lot more customization.
Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks
marclabrosse said:
Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks
Click to expand...
Click to collapse
no, u need to flash su, gb or ics its still the same process, maybe w/oneclick but i never tried that method
but whats the problem using cwm, its very safe todo and its y we can do so many things with our phones, and if need b u can always flash back to stock ics w/sammobile.com firmware files
afraid to say you'll have to have a cumstom recovery. SuperOneClick wont work. It actuallt will only work on GB 2.3.5. 2.3.6 wont. And I'm pretty certain ICS wont either.
Thanks guys, yeah I tried GB methods or rooting without CWM Recovery before posting, no go...should have rooted before upgrading her phone via Kies...
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store.
I've had mine running CWM recovery from day one, but I can restore it to stock without a problem, she's not technical at all... its her "Facebook" phone...
I guess CWM recovery will be going on there shortly...
marclabrosse said:
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store...I guess CWM recovery will be going on there shortly...
Click to expand...
Click to collapse
You can flash back to 3e recovery without losing root. Unrooting is covered in post #10 here: http://forum.xda-developers.com/showthread.php?t=1726445
Well I was running stock 404(i9020t) rooted with matrix kernel, and trying to prepare for jb ota in a few days I decided to go back to stock thinking having a non stock kernel, I would miss out on jb ota. So I proceeded to flash what I thought was my stock image for my phone (i9020t) but it turns out it was for (i9020a). After I realized that wasn't the correct image I halted my process. I'm currently on stock 404(i9020a),but my bootloader is still unlocked. So my question is 1. Will this affect me getting jb ota 2. If not will the ota correct my phone baseline 3. What steps should I take to achieve the stock 404 for my specific phone? I've read through multiple posts so I'm guessing I need some simple explanation. Thanks in advance.
Mod plz remove. I solved my problem. thx.
Since I got the phone, I've been stock rooted/unlocked the entire time, and managed to disable OTA updates in fear of losing root and etc. Is anyone still on the original firmware and is there any good reason for me to upgrade?
I think the next OTA I'd probably take is if Jelly Bean comes out, and even then I'd most likely simply Odin-flash a stock rooted image whenever the time comes. Any advice on how to go about a possible Jelly Bean OTA from Verizon?
Thanks
dunderball said:
Since I got the phone, I've been stock rooted/unlocked the entire time, and managed to disable OTA updates in fear of losing root and etc. Is anyone still on the original firmware and is there any good reason for me to upgrade?
I think the next OTA I'd probably take is if Jelly Bean comes out, and even then I'd most likely simply Odin-flash a stock rooted image whenever the time comes. Any advice on how to go about a possible Jelly Bean OTA from Verizon?
Thanks
Click to expand...
Click to collapse
I still use LF2 and have seen zero good reasons to switch. I have a custom kernel and several customizations to things such as framework.res and such so I'm not exactly stock rooted.
dunderball said:
Since I got the phone, I've been stock rooted/unlocked the entire time, and managed to disable OTA updates in fear of losing root and etc. Is anyone still on the original firmware and is there any good reason for me to upgrade?
I think the next OTA I'd probably take is if Jelly Bean comes out, and even then I'd most likely simply Odin-flash a stock rooted image whenever the time comes. Any advice on how to go about a possible Jelly Bean OTA from Verizon?
Thanks
Click to expand...
Click to collapse
Why not take the OTA then reroot/unlock? There are some minor changes in the menus and such and also the radio is a good reason to update. Much faster switching between 3g/4g and such, better signal strength. Or if you are running custom recovery you can just flash a updated radio. Also there is a thread floating around here with a customized updater that will keep root and your bootloader unlocked. As for the OTA to jelly bean you can just flash a jelly bean rom ontop of your F2 baseband.
crabapples said:
I still use LF2 and have seen zero good reasons to switch. I have a custom kernel and several customizations to things such as framework.res and such so I'm not exactly stock rooted.
Click to expand...
Click to collapse
Same, stock rooted since day one to change kernal, add wif tether and to use things like titanium back up. I use apex and SwiftKey. Everything works. No reason to break something...
Sent from my SCH-I535 using xda app-developers app