This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
OK, someone smarter than me needs to check this out before unleashing to the masses. Here's the story.
I already had an update.zip in my sdcard folder (from the previous manual update).
After bumbling around for a bit, I found a file in my cache folder called "Blur_Version.2.2.20.A955.Verizon.en.US.zip". I said that this can't be the right file. I'm looking for a 2.3.20 file... Copied the file anyway. Bumbled all around the folder structure and couldn't find anything "better".
After installing the update this file has vanished from my cache folder, so perhaps it is actually the correct file??? I don't know. The file is posted at http://dl.dropbox.com/u/10937565/Droid/Blur.zip but please use carefully.
I'm not going to post directions for how to manually update, as I'm not sure that this will work and would like someone who actually knows to test it first
Depends on what you mean by without issue. OTA update will occur, but you will not have root once it is done. If you got root to start with it shouldn't be too hard to get it back.
I think it will be a slow answer. we don't know if they're sending out anything in the update that ****s up root users.. who wants to be a guinea pig??? dancedroid
^^^I second this, and to add to it, is there a sure-fire way to re-root after the update? Secondly, if we're running a custom ROM, say Fisson 1.2, is it going to break it if we were to update, re-root, and flash back to it?
I think it will be a slow answer. we don't know if they're sending out anything in the update that ****s up root users.. who wants to be a guinea pig??? dancedroid
Root is just a file named su in the system partion superuser apk is a app that interfaces with it. The update will either delete it or reset the permissions on the file causing it to not work anymore the rest of the system isn't affected
Post update permissions are changed. After I updated I tried su and received a "permission denied" message. The files were still there, but I wasn't allowed to use them anymore.
jason
According to Motorola the update hasn't gone out to everyone yet. I was rooted and received the update last night, so I don't think root status has anything to do with it. If you are running a custom ROM, that could certainly change things.
^^^I second this, and to add to it, is there a sure-fire way to re-root after the update? Secondly, if we're running a custom ROM, say Fisson 1.2, is it going to break it if we were to update, re-root, and flash back to it?
Custom roms are different you will have to sbf back to default to update. As for rerooting if Motorola didn't patch the exploit allowing the su file to get on the system you will be able to run it again I would think