A few freezing and root questions

[kach474]

Hello I have a few questions about freezing. I have seen someone else ask it but could not find the answer. Hope this answers others questions also.

I have rooted my phone and installed Titanium Backup. I froze some apps with no real issues. However I noticed that they are listed differently in TB as in the thread "Droid Bionic: apps that are safe to remove once rooted." There are apps or files listed such as "com.motorola.atcmd.plugin 2.3.4", "blur.res 2.3.4", "Admin Notifier 2.3.4" etc. I was wondering if there is a list or if anyone had suggestions of which ones were safe to freeze or those to leave alone?

I have the following frozen with no issues.

Amazon Kindle 3.0.2.7.1
Blockbuster 0.9
Bookmarks Widget 2.3.4
Citrix Receiver 2.1.1078
City ID 1.1.7
Flickr Authenticator 2.3.4
FMRadioService 2.3.4
Forest Wallpaper 1.0
GoTo Meeting 1.0
Guided Tours 2.3.4
IM 3.0.4.6
IM Presence 2.3.4
IPSec VPNs 1.0
Live Wallpaper Picker 2.3.4
Magic Smoke Wallpapers 2.3.4
Myspace Authenticator 2.3.4
News 2.3.4
Quickoffice, Inc 4.1.80
Skyrock Authenticator 2.3.4
Slacker 3.0.535
Twitter Authenticator 2.3.4
V Cast Music 03.72.110
V Cast Tones 4.5.12
VideoSurf 1.1.9
VPN Services 2.3.4
VZ Navigator 7.2.0.353
Weather 2.3.4

Also a question about Ram. Is there specific apps or services that can be turned off to boost Ram? I keep getting the memory warning on the lapdock.

And my last question is about the Motorola update coming. (if it ever does). First, will I need to unfreeze apps to accept the update or will I have to unroot also? And what is the best course of action, wait for the Motorola update? or install the update available on this site amd does it fix the dropping of 3G issues?

Thanks for any help.
Matt

 

[LDubs]

I would stick with the list in the stickied thread at the top of this subforum.

Not sure about the ram question, hopefully someone else can chime in on that.

As for the ota update, yes you'd have to unfreeze everything, you have to be totally stock. I believe the leaked update does address the data issue. Or you could take the plunge like I did and install a custom rom....the one I'm running is based on 5.7.893 and is super smooth and fast.

Sent from my [P]URIFI3D Droid Bionic

 

[kach474]

I would stick with the list in the stickied thread at the top of this subforum.

Not sure about the ram question, hopefully someone else can chime in on that.

As for the ota update, yes you'd have to unfreeze everything, you have to be totally stock. I believe the leaked update does address the data issue. Or you could take the plunge like I did and install a custom rom....the one I'm running is based on 5.7.893 and is super smooth and fast.

Sent from my [P]URIFI3D Droid Bionic

Ya I froze mostly the ones on that list but there is a few on that list that I couldn't positively identify on the list on TB. For example VzWBAService.apk, VzWBAClient.apk, VzWBAClient.odex, vzw_vnav_DROID3_rel_PROD_signed.apk, Vvm.apk, etc these are not listed on the list on TB. Are those apps or files in a specific program or app? That essentially was my question. Just translation of some of the file names in the sticky list applied to the list of apps and programs on TB.

I have been debating on installing a custom rom (is that the same as a leaked update?) Are there any cons to the rom your running? You say smooth and fast? Do you thing the CPU operates faster then the stock OS?

Thanks for the info.

 

[JStrider]

If we are totally stock and unrooted or normal rooted, and we do the OTA update when it comes out, we will lose the ability to root, at least for the time being?

We want to be stock with forever root for the OTA right?

I'll probably wait to do the OTA until people are starting to report back with what works/doesnt work.

 

[LDubs]

Ya I froze mostly the ones on that list but there is a few on that list that I couldn't positively identify on the list on TB. For example VzWBAService.apk, VzWBAClient.apk, VzWBAClient.odex, vzw_vnav_DROID3_rel_PROD_signed.apk, Vvm.apk, etc these are not listed on the list on TB. Are those apps or files in a specific program or app? That essentially was my question. Just translation of some of the file names in the sticky list applied to the list of apps and programs on TB.

I have been debating on installing a custom rom (is that the same as a leaked update?) Are there any cons to the rom your running? You say smooth and fast? Do you thing the CPU operates faster then the stock OS?

Thanks for the info.

Can't help that much with the freezing question, take a look in \system\app using Root Explorer and you should see the .apk's that are listed there.

I haven't seen any con's to the custom ROM yet. The one I'm running is completely deblurred (i.e. no Moto Blur) and has your choice of 3rd party launcher replacements, including ICS Launcher. I believe it runs faster, it has a battery booster script built in, and a lot of the bloat is removed as part of the package. Downside would be that if a Moto OTA fix does eventually push, I wouldn't be able to install it (and actually you would need to unfreeze everything to install it on yours), but the ROM Devs usually get that stuff leaked earlier than the OTA, so an update would be pushed through the ROM. The ROM I'm on right now is built off of 5.7.893 so I didn't even bother to update to that first.

 

[LDubs]

If we are totally stock and unrooted or normal rooted, and we do the OTA update when it comes out, we will lose the ability to root, at least for the time being?

That's the rumor, yes.

We want to be stock with forever root for the OTA right? Yes. If the OTA does block root then you'd still be good to go.

I'll probably wait to do the OTA until people are starting to report back with what works/doesnt work.

 

[2defmouze]

General answer, you'd want to root and apply the forever root script before doing the OTA in order to keep root.

However, we don't know what the final version of the OTA will look like, and one version (5.7.894 I believe) actually blocks it from installing if you have forever root in place. Best bet would be to NOT install the official OTA when it comes out until you read that its been safely rooted or a method has been confirmed to let you keep root after installing it.

On another note, if you forever root and get yourself to the current safe leaked version (5.7.893), I really don't think you'll need to worry much. Like right now that's where I am (with full upgraded kernal and radio files) and I could care less about getting the "official" OTA whenever its released. My bionic has zero issues so I don't see what I could possibly be missing when the official one comes along. Plus the dev community will figure out ways for us early upgraders to get it safely, if we so choose, in minimal time I'm sure.

 

[LDubs]

General answer, you'd want to root and apply the forever root script before doing the OTA in order to keep root.

However, we don't know what the final version of the OTA will look like, and one version (5.7.894 I believe) actually blocks it from installing if you have forever root in place. Best bet would be to NOT install the official OTA when it comes out until you read that its been safely rooted or a method has been confirmed to let you keep root after installing it.

On another note, if you forever root and get yourself to the current safe leaked version (5.7.893), I really don't think you'll need to worry much. Like right now that's where I am (with full upgraded kernal and radio files) and I could care less about getting the "official" OTA whenever its released. My bionic has zero issues so I don't see what I could possibly be missing when the official one comes along. Plus the dev community will figure out ways for us early upgraders to get it safely, if we so choose, in minimal time I'm sure.

How to ensure I have full upgraded radio and kernel? Does Purity have this built in or do I have to do back and update to the safe leaked version first?

 

[2defmouze]

How to ensure I have full upgraded radio and kernel? Does Purity have this built in or do I have to do back and update to the safe leaked version first?

Purity does not have it built it... since we have locked bootloaders, nobody except for an official update can touch your kernal or radio files. Yeah if you get the safe leaked version at Easily Upgrade To 5.7.893, Keep Root And Webtop - RootzWiki That will upgrade them.

Purity and Shift3r are just built off the 5.7.893 OS, so you have all the OS tweaks that came with those updates, but NOT the kernal and radio update. If you go through the method above and update it, you will get the kernal/radio upgrades, and those cannot be undone even if you restore yourself back to stock for whatever reason, they be permanent (but good permanent )

EDIT: to OP... those VzWBA files are backup assistant files. You SHOULD be able to freeze them, if you don't use backup assistant, and be just fine. Cautious man would tell you that with any files your unsure of just freeze one at a time, play around and make sure you don't run into any issues, since its easy to unfreeze if you do.

 

[LDubs]

Purity does not have it built it... since we have locked bootloaders, nobody except for an official update can touch your kernal or radio files. Yeah if you get the safe leaked version at Easily Upgrade To 5.7.893, Keep Root And Webtop - RootzWiki That will upgrade them.

Purity and Shift3r are just built off the 5.7.893 OS, so you have all the OS tweaks that came with those updates, but NOT the kernal and radio update. If you go through the method above and update it, you will get the kernal/radio upgrades, and those cannot be undone even if you restore yourself back to stock for whatever reason, they be permanent (but good permanent )

Crap, I thought I might have missed a step... ok, more crack flashing for me...!

 

[LDubs]

Has anyone ever run the R3L3AS3D script to flash all the way back to stock (option 1)? It's asking me for a password. I have a pattern lock on my device, no pw, is it looking for a root password? Don't know what that would be.

 

[2defmouze]

Has anyone ever run the R3L3AS3D script to flash all the way back to stock (option 1)? It's asking me for a password. I have a pattern lock on my device, no pw, is it looking for a root password? Don't know what that would be.

Used it only when I was doing the OTA update.. never saw anything about a PW request. You figure it out? Try running it again?

EDIT: Might wanna try posting in the main ReleasedRoot thread.. the devs or some more knowledgeable users I'm sure could help

 

[LDubs]

Yeah ran it 3 times, asked me for a pw each time. Posted question in the ReleasedRoot thread, waiting for response(s).

When I get a few mins (and after a phone call I'm waiting for to come in), I'm going to try just restoring it first, then going back and rooting/forever rooting.

 

[pappy53]

I think it is speaking of the password to log in to your computer.

 

[LDubs]

I think it is speaking of the password to log in to your computer.

huh. lol never thought of that - thought it was tied to my phone.... I'll try that...

EDIT: GENIUS, man, GENIUS!!! Dhacker from Rootzwiki confirmed that it's looking for Mac password. Who'd a thunked? Gotta run now but will try this later...

 

[LDubs]

DONE. Now on leaked 5.7.893 with webtop. Sweet. Off to reflash Purity... Stock is so incredibly boring.

 

[2defmouze]

DONE. Now on leaked 5.7.893 with webtop. Sweet. Off to reflash Purity... Stock is so incredibly boring.

Congrats... I'd say now would be a great time to make a cwr backup of your 7.893 "stock" system... I did at that point... before you go romming again

 

[LDubs]

oh boy. I backed up the 5.886 system... I think I forgot to backup 7.893... ugh.

Too late, I'm almost all the way back... oh well.

 

[2defmouze]

oh boy. I backed up the 5.886 system... I think I forgot to backup 7.893... ugh.

Haha.. eh don't beat yourself up. Could probably even send you mine if it came down to it and we needed them for something.

 

[akorcovelos]

you guys are really making me rethink waiting for the official OTA and just use .893 so I can finally try out a new ROM... just got my go launcher the way I like it too...