• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

"Jellybean 4.1.2 update"

Advice? I flashed the Christmas leak a couple weeks ago. I see that there is already a flashable version of this current release for the people who are on that Christmas accident. Are we sure this is the right one? Should I just go ahead and flash the proper update, or it is possible that the OTA version could be slightly different? Do they make any changes at all after the release, to maybe fix small issues they might be learning about during the big release? Do any of you guys wait until the release is totally out before updating, just to make sure they have worked out all of the bugs?
 
zoxxo said:
Did anyone download and apply the update to a rooted phone? I've read in places that people had there phone bricked because of doing just that. I'm not worried about losing root, I just don't want to brick...
Click to expand...

I did and I'm a noob with all this. It was the same process. Just get OTA Rootkeeper, protect root, temp unroot, restore root, temp unroot again then restore root THEN turn off and install it like normal, then when it comes on, restore root again. DO NOT temp unroot before installing. I had no issues. They must've done something wrong. That or they didn't flash back to .211 if they messed with it. It has to be stock .211 or it won't work.
 
So this all boils down to this being the soak test OTA right? So I have it, never rooted and will continue to stay stock. I will implore you all to do an FDR once you get the update. I have learned my lessons in the past and hold Thom in high regard for helping me down the path of FDR's after a software update. Why risk having a bunch of bugs after 2 months of smooth operating? Just do the reset. I actually set a new record for myself this time around by having my phone back the way I had it before the update in about a day.

Anyways, here are some things that I have noticed. One while I know ALL of my pictures were on my SD card, they are not showing up anymore on my phone when I go into gallery. I'm sure if I plug my phone into my lap top I'll find them right away. Also, I don't see where the new beam feature is on the phone now? We are suppose to all have it with this but I'm not finding it unless it's the part where you have to connect to devices thru wifi. That I find odd because the S3 does it over bluetooth.

I don't use smart actions, I don't use maps, I don't use google search, I already had google chrome browser, I don't use music, I don't use bluetooth, and I don't use wifi. For everything but bluetooth and wifi on my phone that I don't use I have disabled them. I also don't use the voice parts of the phone. So out of everything that is suppose to make our phones better what differences have you all seen so far? I know mine is smoother, has a faster response, and no lag at all.

On my last note, the actual push will probably come to the masses sometime in the middle of this coming week. Having been part of a soak test in the past, normally it's a 5 day soak and then one day to 2 at the most that they look over all the issues reported and then they start slinging it out there. Most issues they figure a quick work around for them and post up pretty fast. If the issues they make work arounds for become greater in number then they will probably make a patch that eliminates said problem. I think that's all that I can input for now. Honestly I wouldn't know as much as I do without a lot of you guys here on the forum. So what little help and advice that I have provided right now I want to give thanks to all the people that have helped me get to where I am now. I was once a scared newbie that thought he had bricked his phone a few times in the past. Only to be saved by the people here!
 
CoyotesFan4Evr said:
Also, I don't see where the new beam feature is on the phone now? We are suppose to all have it with this but I'm not finding it unless it's the part where you have to connect to devices thru wifi. That I find odd because the S3 does it over bluetooth.
Click to expand...
Android Beam requires NFC (Near Field Communications), which the Droid RAZR does not officialy have. The weird thing here is that I read on-line that the RAZR has an NFC controller on board, but for some reason, Motorola has chosen not to support it in our phones...
 
catiebugx3 said:
I did and I'm a noob with all this. It was the same process. Just get OTA Rootkeeper, protect root, temp unroot, restore root, temp unroot again then restore root THEN turn off and install it like normal, then when it comes on, restore root again. DO NOT temp unroot before installing. I had no issues. They must've done something wrong. That or they didn't flash back to .211 if they messed with it. It has to be stock .211 or it won't work.
Click to expand...
Well I used VooDoo Root Keeper to perserve root before I installed the JB update and it did not work. When I tried to run VooDoo after the installation, it (VooDoo) froze up on me. I'll be looking for another method to restore root...
 
CoyotesFan4Evr said:
Anyways, here are some things that I have noticed. One while I know ALL of my pictures were on my SD card, they are not showing up anymore on my phone when I go into gallery. I'm sure if I plug my phone into my lap top I'll find them right away. Also, I don't see where the new beam feature is on the phone now? We are suppose to all have it with this but I'm not finding it unless it's the part where you have to connect to devices thru wifi. That I find odd because the S3 does it over bluetooth.
Click to expand...

I can't verify this ... but it is worth a try ... power it off and then power it on. See if your pictures magically appear. On some the index is built/rebuilt when the uncial load occurs after a power on.

... Thom
 
zoxxo said:
Well I used VooDoo Root Keeper to perserve root before I installed the JB update and it did not work. When I tried to run VooDoo after the installation, it (VooDoo) froze up on me. I'll be looking for another method to restore root...
Click to expand...
Ditto here- the sideload install worked perfectly but Voodoo failed to save root access for me. The funny thing is that Voodoo DID work last summer when I got the 4.0.4 upgrade OTA. Poor Voodoo, what have you done?
 
catiebugx3 said:
I did and I'm a noob with all this. It was the same process. Just get OTA Rootkeeper, protect root, temp unroot, restore root, temp unroot again then restore root THEN turn off and install it like normal, then when it comes on, restore root again. DO NOT temp unroot before installing. I had no issues. They must've done something wrong. That or they didn't flash back to .211 if they messed with it. It has to be stock .211 or it won't work.
Click to expand...

socobandit said:
Voodoo worked for me... did you back up root then temporarily unroot? If you don't unroot you will lose it
Click to expand...

No, I did not un-root before applying the update. I read the post by catiebugx3 and thought it applied to Voodoo as well. Do different root-keepers require different methods of protection after updating?
 
I know this much...I didnt unroot before the major jb update from ics and lost root...I unrooted before the new update and was able to use voodoo to restore root.
 
I also did not unroot before updating via SafeStrap. My root access survived the update. I had Voodoo save the backup file, but I also had SuperSU in "Survival Mode." I suspect it was SuperSU that actually kept my root access.
 
I installed the Christmas version, do I need to do a FDR to get the new Ota update or will it come to my phone still? I have not received it yet.
 
Not sure if there is much difference between the Razr and MAXX other than the battery but I have the MAX so I'd hope that with the MAXX we get beam.
 
CoyotesFan4Evr said:
Not sure if there is much difference between the Razr and MAXX other than the battery but I have the MAX so I'd hope that with the MAXX we get beam.
Click to expand...



Don't think it will happen because neither the Razr or Razr Maxx have NFC(Near Field Communication) in the phones, like the SIII has.
 
BKline2003 said:
Don't think it will happen because neither the Razr or Razr Maxx have NFC(Near Field Communication) in the phones, like the SIII has.
Click to expand...
According to some articles on the web, the RAZR and RAZR Maxx both have an NFC controller on board. However, for some reason, Motorola has chosen not to implement it...
 
I have been reading this thread from day one and I am excited that I may soon be getting the jb update. I have a Razr and someone was telling me you can go into settings and then go into another part of settings and force the update. This person couldn't remember how he did it when he was updating to jb on his S1. I know about setting - about phone - then system updates but I was told there is another way to do this and the phone actually goes out and searches for the update rather than waiting til it's in queue. Does anyone have knowledge of this?
 
You go to system settings, about phone, system update. It will check for an update but unless the ota with them to your phone you're not going to be able to get it
 
Thanks but that is the way I knew about. I was just told another way to check is below and it checks a more direct way. I am unable to check my phone to see if this works since I am not allowed to bring my phone into work.

Settings > Apps > All > Google Services Framework > Clear date and force stop - then go to about phone > System update and press check now. If the update is available you'll be notified. You may have to try several times until you succeed and it may not work for you, but you certainly won't endanger your device whats-o-ever.
 
Alternate update method.
Dial *#*#checkin#*#* (using the numbers on the dial pad for the letters) but it will not update if there is no update available.
 
I think something is wrong with the information that is out there about beam. If you look at the announcement page that motorola put out saying that JellyBean was being launched you will see that it clearly says we will have beam. So, with that being said.....we are being lied to or something else is up.

Yeah I'm willing to beat thiis until it's like beating a dead horse. I know what I read and what I saw.
 
CoyotesFan4Evr said:
I think something is wrong with the information that is out there about beam. If you look at the announcement page that motorola put out saying that JellyBean was being launched you will see that it clearly says we will have beam. So, with that being said.....we are being lied to or something else is up.

Yeah I'm willing to beat thiis until it's like beating a dead horse. I know what I read and what I saw.
Click to expand...

Do you have a link to this announcement page?
 
You must log in or register to reply here.
Back
Top Bottom