Related
I am ready to install the latest update to my x2, but i am currently rooted and have the pulldown toggle zip and crt animation on my device, as well as the supercharger script, i know its very easy to remove the supercharger script,but would the crt or pulldown effect the install? Anyone encountered this issue yet?
thanks for the help.
amancini92292 said:
I am ready to install the latest update to my x2, but i am currently rooted and have the pulldown toggle zip and crt animation on my device, as well as the supercharger script, i know its very easy to remove the supercharger script,but would the crt or pulldown effect the install? Anyone encountered this issue yet?
thanks for the help.
Click to expand...
Click to collapse
In order for you to update your gonna have to sbf back to 2.3.3 if that's what your on. If not, then the update will fail because of the root. You will be able to update once you sbf & wipe data in stock recovery as well just to be safe. Hope that helps
Edit: this is for if you are trying to get the ota...sorry I should clarified that first
thanks for the help that basically clears it all up, seeing as im fairly happy with it right now im going to leave well enough alone, when they roll out a bigger update i will consider it, thats what i figured i was going to have to do.
amancini92292 said:
thanks for the help that basically clears it all up, seeing as im fairly happy with it right now im going to leave well enough alone, when they roll out a bigger update i will consider it, thats what i figured i was going to have to do.
Click to expand...
Click to collapse
Just use titanium backup then and back to stock, do the update and reload ur apps. Takes all of about an hour, tops.
Droid X2 - Eclipse v1.0
yeah i have all of that done already, i might give it a try, thanks
Rp...I don't think it will fail just due to root. U WILLA lose ur root.
It most likely WILL fail due to the mods/or rom u run due to missing files that are necessary.
if u are stock rooted I think it would work...but either way good idea to go back bone stock just to avoid any issues altogether
im running the completely stock rom, removing the script i have isnt an issue what so ever, is there any way to remove installed zips that were installed in the recovery?
ashclepdia said:
Rp...I don't think it will fail just due to root. U WILLA lose ur root.
It most likely WILL fail due to the mods/or rom u run due to missing files that are necessary.
if u are stock rooted I think it would work...but either way good idea to go back bone stock just to avoid any issues altogether
Click to expand...
Click to collapse
True always better to be safe than sorry
if your on stock and you want to return your animations to stock you could possibly extract framework-res.apk from /system/framework/ of the stock gingerbread and push it via adb to your phone or you could use root explorer to do so as well. that should erase your mods to animations. and you'll most likely have to reboot after. but animations should retrun to stock after, than unroot and take the ota. but its never a bad idea just to go to bone stock via sbf as rp076 suggested
For taking off the toggles u can just flash the stock notification zip from one of those threads I think it is there somewhere. Or ask the creator of the toggle zip u flashed for the stock one...
But ur safest bet is sbf and data wipe. It's not hard to do at all and is just a good thing to know how to do
I recovered my stock rooted backup from eclipse .8 and took the OTA no problem. You will lose root but Pete's one click will work to root again. You won't lose any apps.
Sent from my eclipsed DROID X2 using xda premium
rp076 said:
In order for you to update your gonna have to sbf back to 2.3.3 if that's what your on. If not, then the update will fail because of the root. You will be able to update once you sbf & wipe data in stock recovery as well just to be safe. Hope that helps
Edit: this is for if you are trying to get the ota...sorry I should clarified that first
Click to expand...
Click to collapse
Steve125 said:
I recovered my stock rooted backup from eclipse .8 and took the OTA no problem. You will lose root but Pete's one click will work to root again. You won't lose any apps.
Click to expand...
Click to collapse
Why do people keep thinking that just because you have root you have to SBF.. Root has nothing to do with the OTA update..
If you try and it fails it's not due to root, it would have to do with something frozen, or you have OTA Blocked with Rom Manager, or something else changed...
Of all the phones out there I can't think of any (ever) that have blocked OTA updates just because of root access.. In fact OTA Blocking had been added in to Rom Manger a few years back to prevent the OTA updates so people wouldn't update and lose root on updates that were not rooted yet.
On a side note, why would you SBF to 2.3.3 instead of just going to 2.3.4? You're just adding an extra step there. That would be like flashing back to Froyo SBF (what's the point?) if you want 2.3.4 GB..
masters said:
Why do people keep thinking that just because you have root you have to SBF.. Root has nothing to do with the OTA update..
If you try and it fails it's not due to root, it would have to do with something frozen, or you have OTA Blocked with Rom Manager, or something else changed...
Of all the phones out there I can't think of any (ever) that have blocked OTA updates just because of root access.. In fact OTA Blocking had been added in to Rom Manger a few years back to prevent the OTA updates so people wouldn't update and lose root on updates that were not rooted yet.
On a side note, why would you SBF to 2.3.3 instead of just going to 2.3.4? You're just adding an extra step there. That would be like flashing back to Froyo SBF (what's the point?) if you want 2.3.4 GB..
Click to expand...
Click to collapse
Calm down killa...just stating what I know thru past experiences & I'm not the only one who's had the problem before. When the 2.3.3 update first came out I couldn't update because my phone still was rooted, NOTHING FROZEN OR REMOVED. I read in other threads at the time that sbf'ing was the way to fix the problem. Once i did that, i was able to get the update installed successfully. Its not a wrong procedure, but a way to be sure to get a clean install. And as for flashing back, I was saying to do that if he wanted the ota
Side note...rom manager isn't or hasn't even been available yet for this phone ...surely you knew that
Noticed System Update on my droid Razr. So I pulled it and here it is totally legit
Blur_Version.6.12.173.XT912.Verizon.en.US
Installation:
1. Copy the Blur_Version.6.12.173.XT912.Verizon.en.US.zip to SD card
2. Boot in Recovery Mode (STOCK Motorola Recovery)
3. Flash
4. Enjoy!
Download:
http://www.4shared.com/zip/PA_2fa2S/Blur_Version612173XT912Verizon.html
How do you pull these update.zip?
Well we lose root?
xlightwaverx said:
Well we lose root?
Click to expand...
Click to collapse
Voodoo OTA Root keeper.
I have OTA RootKeeper. The update fails after the process completes and then reboots. Wants to download again (.181 Update)
X
Edit: Factory Resetting Phone / ReRooting / Applying .181 Update
Results: Still failed, but this is irrelevant to this post, since this is about .173
Seems like 181 wont take over a rooted device.
has anyone tried to unroot, update, and reroot?
Yes i did temp unroot then installed the update and restored root zero issues
Sent from my DROID RAZR using Tapatalk 2
I'm stock rooted, got the notification this morning, used OTA Rootkeeper to backup su, applied update, restored root. No un-rooting required.
You need to be stock with no bloat removed for this update to work. If anything's frozen in TiBU it will not work. Custom ROMs obv will not work as well. Fully stock, rooted or unrooted only.
As for the update, meh.
I keep getting "signature verification failed."
thought it was the 181 update not 173???? confussed
sporty377 said:
thought it was the 181 update not 173???? confussed
Click to expand...
Click to collapse
It's just the way Motorola names their updates. It's always named the version you should be on to use it. The update to 748 was called 744. The update to 173 was called 748 and so forth.
Sent from my DROID RAZR using Tapatalk 2
Tiburon41 said:
You need to be stock with no bloat removed for this update to work. If anything's frozen in TiBU it will not work. Custom ROMs obv will not work as well. Fully stock, rooted or unrooted only.
Click to expand...
Click to collapse
so if i deleted stuff i should just factory reset and then update?
sorry if stupid question but new to moto devices
I am currently unrooted and I did receive the latest OTA (March 8) release. its 17MB
orcsbane13 said:
It's just the way Motorola names their updates. It's always named the version you should be on to use it. The update to 748 was called 744. The update to 173 was called 748 and so forth.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Ok....gotcha.......i come from tbolt to razr...thanks for the heads up
Sent from my DROID RAZR using XDA
lewi3069 said:
I keep getting "signature verification failed."
Click to expand...
Click to collapse
I am also getting this error can someone either post a link to a stock rom or an update that doesnt have the sig error please.
i appreciate everyones help in here
Tiburon41 said:
I'm stock rooted, got the notification this morning, used OTA Rootkeeper to backup su, applied update, restored root. No un-rooting required.
You need to be stock with no bloat removed for this update to work. If anything's frozen in TiBU it will not work. Custom ROMs obv will not work as well. Fully stock, rooted or unrooted only.
As for the update, meh.
Click to expand...
Click to collapse
So mistakenly, I ran the update without unfreezing the bloatware in TiBu
The update went through but now I lost root access
Do I need to reset my Razr back to stock in order to re-root it or what its the best course of action?
Sent from my DROID RAZR using XDA
Theres no reason you should have an issue. As I updated of this file. I pulled it directly from ota i didnt get it from someone else I pulled it myself.
Besides those 2 anyone else have troubles. Also if you installed speak up. Also I didnt loose root on this update at all didnt have to restore or nothing.
So first I used TB and defrosted bloat...
I am rooted with stock Rom.
Used Voodoo OTA Rootkeeper and it was very easy to unroot.
1) Voodoo Root Keeper>Protect Root>Temp. Un-root
2) Download and install 6.12.181 OTA
3) Use Voodoo to re-apply root
I'm sorry to say this but "it was so easy even a caveman could do it"
Everything back to normal...I'm not sure if my sq_lite hack for hotspot works however as my Razr is my secondary phone, so my Razr is not active with Verizon for now. I may switch back from my Rezound for a while tomorrow. I go back an forth with these 2. Weird I know.
Good Luck to all.
tiger505 said:
So first I used TB and defrosted bloat...
I am rooted with stock Rom.
Used Voodoo OTA Rootkeeper and it was very easy to unroot.
1) Voodoo Root Keeper>Protect Root>Temp. Un-root
2) Download and install 6.12.181 OTA
3) Use Voodoo to re-apply root
I'm sorry to say this but "it was so easy even a caveman could do it"
Everything back to normal...I'm not sure if my sq_lite hack for hotspot works however as my Razr is my secondary phone, so my Razr is not active with Verizon for now. I may switch back from my Rezound for a while tomorrow. I go back an forth with these 2. Weird I know.
Good Luck to all.
Click to expand...
Click to collapse
can the new update be rooted? i unknowingly updated before i rooted...
chinkster said:
can the new update be rooted? i unknowingly updated before i rooted...
Click to expand...
Click to collapse
Yes use dr utility
Sent from my DROID RAZR using Tapatalk 2
so I am very excited for my Jellybean update.
I am running an original Droid Razr Maxx with the (until now) latest ICS release from Motorola and Verizon. The phone is rooted but I have never loaded any other ROMS (I don't even know how).
So can I update with the OTA Jellybean update while I am rooted? If I need to unroot my phone how can I do that? I used the "DroidRazrRoot404" tool but I cannot seem to use it to unroot my razr maxx.
Any advice is greatly appreciated.
So you have the OTA? Or this is in anticipation of the OTA?
~SU!C!D3~ on Tapatalk
You should be able to update with root, however you should have all official bloat installed or frozen because the OTA will check for it.
However, you will lose root after update....
??? Where did you get that JB OTA update? I am very exited as well, but most probably, it won't come out until next year...
Will OTA occur when the bloatware is frozen? Obviously not a big issue since I can unfreeze but just curious. Also, if I have a ROM on Slot 1 in SS for example, would I just go back to stock ROM and use the OTA when it comes out? Or are there any ROM/SS issues I need to consider or simply delete. And the OTA Rootkeeper app should solve my problems about losing root too right?
for those that want the download and more info about it
http://www.droid-life.com/2012/12/2...-331mb-update-as-build-98-72-8/#disqus_thread
ACEstrom said:
so I am very excited for my Jellybean update.
I am running an original Droid Razr Maxx with the (until now) latest ICS release from Motorola and Verizon. The phone is rooted but I have never loaded any other ROMS (I don't even know how).
So can I update with the OTA Jellybean update while I am rooted? If I need to unroot my phone how can I do that? I used the "DroidRazrRoot404" tool but I cannot seem to use it to unroot my razr maxx.
Any advice is greatly appreciated.
Click to expand...
Click to collapse
Using the download already provided, I had to do a few things to get mine to work.
1. Make sure you are on .211 Stock (if on .214 or .215 SBF back to .211)
2. Remove Safestrap or Bootstrap
3. Make sure all apps are thawed (if they were frozen)
4. Download the OTA update file DO NOT UNZIP IT
5. Place it in the root of your SD card
6. Boot into Stock Recovery holding down Power, Vol+, and Vol- and the same time.
7. Select down to Recovery and press up.
8. When you see the android laying on its back PRESS Vol+ and Vol- simultaneously.
9. Select wipe cache (this will not delete any data)
10. Select install update from External SD and select the zip file.
11. Let it run and update, should work.
I encountered an error so I had to SBF back to .211 and start over fresh, but honestly a fresh restart may not be a bad idea for performances sake.
The only issue that I see is my Razr didn't keep root. I am not sure that this is possible to keep root with this upgrade.
Used voodoo OTA rootkeeper. Protected root, temp unroot. Install, restored and used @matt's root restore fix. Works like a charm.
~SU!C!D3~ on Tapatalk
R1pTheJacka said:
Will OTA occur when the bloatware is frozen? Obviously not a big issue since I can unfreeze but just curious. Also, if I have a ROM on Slot 1 in SS for example, would I just go back to stock ROM and use the OTA when it comes out? Or are there any ROM/SS issues I need to consider or simply delete. And the OTA Rootkeeper app should solve my problems about losing root too right?
Click to expand...
Click to collapse
Hey, I've been looking at the posts about the update, and it seems that If you have safestrap/bootmenu/bootstrap, you will not be able to upgrade.... If you want the upgrade, you should go back to stock .211...
If you just have some frozen apps, you will be able to update correctly
Follow the instructions that chadgauth posted...
lost root
Stock 211 rooted. Voodoo root keeper backed up protect root, temp unroot.
Installed 4.1.2 update all good. Failed to get root back thru vodoo.
FYI cannot go back to 211 after flash 4.1.2 so now stuck
Without root till some dev comes out with a root method for us
Restore with voodoo rootkeeper then use Matt's rootfixer forum.xda-developers.com/showthread.php?t=2064074&page=19 post#187
Make sure you have USB debugging enabled in development
Enable "Unknown Sources" in privacy
Go to settings/storage menu soft key
Computer connect - select MTP
~SU!C!D3~ on Tapatalk
Tried that. For some reason it did not save the such file with vodoo so root fixer says cannot be found. Prolly some mistake I made or uncommon glitch
queberican351 said:
Restore with voodoo rootkeeper then use Matt's rootfixer forum.xda-developers.com/showthread.php?t=2064074&page=19 post#187
Make sure you have USB debugging enabled in development
Enable "Unknown Sources" in privacy
Go to settings/storage menu soft key
Computer connect - select MTP
~SU!C!D3~ on Tapatalk
Click to expand...
Click to collapse
As I was installing through recovery I got an error because it was checking my preinstalled apps for ForestWallpaper.apk which I'm assuming I deleted ages ago, in addition to
e:error in /tmp/sideload/package.zip
(status 7)
Installation aborted.
..but according to this I'm screwed? http://forum.xda-developers.com/showpost.php?p=19468147&postcount=15
R1pTheJacka, You can SBF back to .211.
Also, all of you guys that are using OTA Rootkeeper, why are you temp unrooting after protecting root? On my Droid X upgrade to ICS a while back and on this OTA to JB today on the RAZR Maxx, I just protected with OTA Rootkeeper but left it rooted. Didn't temp unroot. Then upgraded and then simply restored root. No need for an extra step of fixing it after trying to restore root.
85gallon said:
You can SBF back to .211.
Also, all of you guys that are using OTA Rootkeeper, why are you temp unrooting after protecting root? On my Droid X upgrade to ICS a while back and on this OTA to JB today on the RAZR Maxx, I just protected with OTA Rootkeeper but left it rooted. Didn't temp unroot. Then upgraded and then simply restored root. No need for an extra step of fixing it after trying to restore root.
Click to expand...
Click to collapse
As far as sbf back to 211 you can't it just throws you into a black screen boot loop then you have to play with the power and volume buttons yo get into recovery to reflash the job update
sttierney said:
As far as sbf back to 211 you can't it just throws you into a black screen boot loop then you have to play with the power and volume buttons yo get into recovery to reflash the job update
Click to expand...
Click to collapse
It didn't for me. And even the directions that everyone is following from droidrzr.com tells you not to "temp unroot". It is kind of buried in the instructions, but it says not to temp unroot.
85gallon said:
It didn't for me. And even the directions that everyone is following from droidrzr.com tells you not to "temp unroot". It is kind of buried in the instructions, but it says not to temp unroot.
Click to expand...
Click to collapse
Once your on jb I tried sfb back to 211 and it was a nightmare to get recovery to come back up got the eye then black screen. And of course I updated before the instructions came out so that's how I ended up being where I am with no root
sttierney said:
Once your on jb I tried sfb back to 211 and it was a nightmare to get recovery to come back up got the eye then black screen. And of course I updated before the instructions came out so that's how I ended up being where I am with no root
Click to expand...
Click to collapse
I went up and edited my post to clarify that I was responding to R1pTheJacka. He never made it to JB. He errored out trying to upgrade. Never made it to JB. You are correct, if you make it to JB you can't go back from the posts I am seeing.
unable to root ota using voodo
I have successfully flashed jelly bean but was unable to restore root using voodoo root keeper. If you guys have any luck please let me know... Missing my tethering. :/
Chadwick108 said:
I have successfully flashed jelly bean but was unable to restore root using voodoo root keeper. If you guys have any luck please let me know... Missing my tethering. :/
Click to expand...
Click to collapse
You can use this to get root back if you used voodoo root keeper.
http://forum.xda-developers.com/showthread.php?p=35863089
Sent from my JellyBeaned Droid RAZR Maxx
error unable to use restore root
klabit87 said:
You can use this to get root back if you used voodoo root keeper.
http://forum.xda-developers.com/showthread.php?p=35863089
Sent from my JellyBeaned Droid RAZR Maxx
Click to expand...
Click to collapse
root keeper will not work superuser app is installed is checked and /system supports root protection but will not allow restore root.
also tried matts restore root.zip but get error message of system/bin/sh su not found....
Hi everyone, I have a quick question. I am currently running Stock ICS rooted with Safestrap 3.11 installed. Can I perform the OTA JB 98.72.16.en. update? I know I should use OTA Rootkeeper to temp unroot before attempting to upgrade. Then restore root after upgrading via the saved backup. Yesterday I tried to install the update but it failed at some point during the process. I did not have Safestrap installed at that time. Not sure if there was something wrong with the downloaded update or not, but I don't want to try again until I know it will work and not screw anything up. Has anyone else updated to JB using OTA from a rooted Stock ICS ROM? If someone can point me to a detailed procedure that would be great. Thanks
I actually just did the same thing. Just beware, the kernel upgrades with the OTA as well, so if you're running any custom ROMS, they may not work with the new update. In order to perform the OTA update, you should unfreeze any bloatware apps you may have frozen with TItanium Backup. I also used Voodoo's OTA Rootkeeper and maintained root without a problem, although I've heard mixed things. I left Safestrap installed when I upgraded, but I don't know if that was a good idea or not.
I actually had problems upgrading with safe strap installed. Gave me a failed update 3 times until I finally un installed. Flashed fine after that. Safe strap does indeed work after for me. That is with the official cm10.1 nightly rom. So far so good. Still dual booting on a phone with a locked bootloader. Ha...
Sent from my large and in charge GN2 using Forum Runner
immikevalentino said:
I actually just did the same thing. Just beware, the kernel upgrades with the OTA as well, so if you're running any custom ROMS, they may not work with the new update. In order to perform the OTA update, you should unfreeze any bloatware apps you may have frozen with TItanium Backup. I also used Voodoo's OTA Rootkeeper and maintained root without a problem, although I've heard mixed things. I left Safestrap installed when I upgraded, but I don't know if that was a good idea or not.
Click to expand...
Click to collapse
UrbanDroid said:
I actually had problems upgrading with safe strap installed. Gave me a failed update 3 times until I finally un installed. Flashed fine after that. Safe strap does indeed work after for me. That is with the official cm10.1 nightly rom. So far so good. Still dual booting on a phone with a locked bootloader. Ha...
Sent from my large and in charge GN2 using Forum Runner
Click to expand...
Click to collapse
So uninstalling Safestrap might be the best bet. I am running a rooted Stock OTA ICS ROM, nothing special, just what came from Verizon. I actually started with Gingerbread 2.3.6, rooted that, and when ICS came along, I did the OTA after temp unrooting with OTA Rootkeeper. Been running that since. Now I just recently got the message on my Razr that JB is available. I tried updating but it failed. I think the download might have been corrupted or something. I redownloaded the update earlier today but have put off updating until posting on here. So i guess I will uninstall SS and then try the update again and hope I keep root. Then reinstall SS after that. If anyone else has any input or ideas please feel free to post your methods and results.
Anyone else have any experience performing the OTA update to JB or installing Stock Verizon JB in some other fashion. I would like to hear about it as I am still a little unsure about performing this update and don't want to lose root priviledges. Thanks.
Well I just tried to perform the OTA JB update again and it failed again. I temp unrooted using Voodoo OTA Rootkeeper, set SuperUser to OTA Survival, rebooted my phone, and then attempted the update to JB and about 1 minute into the process it craps out and gives the triangle exclaimation point and then reboots 30 seconds later. Nothing seems broken, its right back to my Stock verizon ICS 6.16.211.XT912. Of course I am rooted but as i stated in a previous post, I have been rooted since GB 2.3.6 and was able to perform the update to ICS using the same method I tried here for JB. What gives? Is anyone else having these issues. I have seen on other forums something called the DroidRazrUtility which is supposed to update you to JB and provide root if needed. Is this the only option for me? Also if I perform a factory reset will that screw my phone up since it is rooted? Will I lose root if I factory reset it? Will a factory reset then allow me to update to JB with ease? Lots of questions but I want to be sure of what I am doing. Any help is much appreciated. Thanks in advance.
Tried two more times and the update failed each time. I think I am going to try a factory reset and see what that does. As a note I did have CWM Touch 5.8.4.5 installed with ROM Manager but uninstalled both and also had Safestrap after that and I made sure I removed that too. Unless I didn't get it all removed. Is there a procedure to ensure they have been fully removed?
For those of you who are having touble getting JB to load on your XT912 Razr, use the following script by Developer mattlgroff. http://forum.xda-developers.com/showthread.php?t=2192467
Follow the instructions as he says to and it works perfect, to include rerooting using the Razr Blade script. Be sure to not only thank him but donate if you can. Developers like this are a life saver to all us that rely on them to provide us the freedom we deserve on our mobile devices. I spent 2 days doing everything I knew how to do to get JB installed and all to no avail. Used mattlgroff's Droid Razr Utility and life is once again good.
I have a rooted Razr Maxx and can not get the update to work. It has failed 3 times now. Any suggestions?
Sent from my DROID RAZR using Tapatalk 2
lockg300 said:
I have a rooted Razr Maxx and can not get the update to work. It has failed 3 times now. Any suggestions?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
use the link in the post right above yours
Should I do a backup first? If so what is the best for that?
Sent from my DROID RAZR using Tapatalk 2
Just got a invite for new firmware test from Motorola, could this be just small fixes or possibly 4.3? Anyone else get a invite?
cmay227 said:
Just got a invite for new firmware test from Motorola, could this be just small fixes or possibly 4.3? Anyone else get a invite?
Click to expand...
Click to collapse
Droid-Life states that it is just a patch of some sort, and is still 4.1.2. I didn't get an invite despite getting them in the past.
just lou said:
Droid-Life states that it is just a patch of some sort, and is still 4.1.2. I didn't get an invite despite getting them in the past.
Click to expand...
Click to collapse
Thanks, gave my razr to my wife over a year ago and haven't been around much in the razr forums. Didn't think it would be anything to big, but thought I'd ask anyway.
cmay227 said:
Thanks, gave my razr to my wife over a year ago and haven't been around much in the razr forums. Didn't think it would be anything to big, but thought I'd ask anyway.
Click to expand...
Click to collapse
Yeah. I still have mine, but I'm getting ready to retire it.
soon we will all know what moto did to razr for the last time ;p just be patient ;p
I didn't get an invite. No matter to me since there's likely nothing new [exciting] except possibly losing root. Not willing to risk it at this time anyhow.
No Invite either
Despite beign on the Motorola support group.
Regardless, now the RAZR is relegated to my wife. I am just too sick of waiting for nothing from MOTO.
The Devs here have done a great job, but I need the HDMI, and with "Noto" not releasing the code no one has been able to make an updated ROM with HDMI.
Happy with my new Sony xPeria ZL. (Never thought I would go to SONY, but I love the 5" HD screen, Great battery, Great camera)
Good luck with the RAZR's and the soak test. Please post your results/ findings. Maybe it will be worth commign back (but I doubt it)
C.
Unfortunately, only new motos will be upgraded. Moto G is already receiving kit kat, despite being launched nearly 2 months ago
Enviado desde mi XT910 usando Tapatalk 2
droid 4 users report that root and ss works after new update
http://forum.xda-developers.com/showthread.php?t=2595419&page=2
Bug
or may be it is about some roaming bug fixes......i wonder will it come to GSM razr or not
http://www.androidpolice.com/2014/0...-the-original-droid-razr-and-droid-razr-maxx/
Drunkula said:
I didn't get an invite. No matter to me since there's likely nothing new [exciting] except possibly losing root. Not willing to risk it at this time anyhow.
Click to expand...
Click to collapse
Is that true? The update could break rooting?
bobloy said:
Is that true? The update could break rooting?
Click to expand...
Click to collapse
I did take the update last night and it did break my root. He's a quick summary:
1. Did a check for updates and was notified that 165 was available. I postponed.
2. Downloaded/installed Voodoo OTA Root Keeper. I backed up root but didn't temp remove it.
3. Uninstalled SS 3.65
4. Installed the 165 update, checked root and it was broken.
5. Tried reinstalling root with voodoo and it wouldn't take.
6. Used Matt's Utility to restore root and it took successfully - I don't know why but for me, Matt's utility only runs if it's unzipped to my C; drive (not my desktop) and I have to put my phone storage in MTP mode, not mass storage.
7. Matt's Utility restored root just fine but when I went ahead and tried reinstalling SS 3.65, I put my phone into a Moto Logo Boot Loop. :crying:
8. Thought I was done for - starting checking on the status of my warranty and insurance deductable but the forums helped dig me out of the mess by getting me to the AP Fastboot screen.
At the end of it I had to completely wipe and reinstall stock JB using Matt's Utility, re-installed the 165 update, re-rooted (again w/ Matt's Utility and NO issues doing so on top of the 165 update) re-installed all user apps, and finally re-installed SS 3.65 with NO issues on top of the 165 update. Haven't re-created a slot 1 and re-loaded CM 11 just yet but i don't expect there to be any issues going further.
In retrospect I think the Moto Logo Boot Loop was a function of something that got corrupted when trying to re-install SS 3.65 on top of it all, perhaps because I dodn't bother to wipe caches or even do a re-start between some of the major steps outlined above.
* I do recommend taking the time to wipe caches and reboot after uninstalling custom recoveries if you're heading down this path.
jeff_roey said:
I did take the update last night and it did break my root. He's a quick summary:
1. Did a check for updates and was notified that 165 was available. I postponed.
2. Downloaded/installed Voodoo OTA Root Keeper. I backed up root but didn't temp remove it.
3. Uninstalled SS 3.65
4. Installed the 165 update, checked root and it was broken.
5. Tried reinstalling root with voodoo and it wouldn't take.
6. Used Matt's Utility to restore root and it took successfully - I don't know why but for me, Matt's utility only runs if it's unzipped to my C; drive (not my desktop) and I have to put my phone storage in MTP mode, not mass storage.
7. Matt's Utility restored root just fine but when I went ahead and tried reinstalling SS 3.65, I put my phone into a Moto Logo Boot Loop. :crying:
8. Thought I was done for - starting checking on the status of my warranty and insurance deductable but the forums helped dig me out of the mess by getting me to the AP Fastboot screen.
At the end of it I had to completely wipe and reinstall stock JB using Matt's Utility, re-installed the 165 update, re-rooted (again w/ Matt's Utility and NO issues doing so on top of the 165 update) re-installed all user apps, and finally re-installed SS 3.65 with NO issues on top of the 165 update. Haven't re-created a slot 1 and re-loaded CM 11 just yet but i don't expect there to be any issues going further.
In retrospect I think the Moto Logo Boot Loop was a function of something that got corrupted when trying to re-install SS 3.65 on top of it all, perhaps because I dodn't bother to wipe caches or even do a re-start between some of the major steps outlined above.
* I do recommend taking the time to wipe caches and reboot after uninstalling custom recoveries if you're heading down this path.
Click to expand...
Click to collapse
Oh jeez, that's a horror story right there. I didn't get the invite, but I know I'll avoid it if I do.
bobloy said:
Oh jeez, that's a horror story right there. I didn't get the invite, but I know I'll avoid it if I do.
Click to expand...
Click to collapse
I didn't get the invite - the update seems to be available for whoever wants to pull it from Settings - About Phone - System Updates.
Got the invite, downloaded, clicked install and went through the motions then got the dreaded sideways android with open heart triangle :laugh: went into reboot the got update failed lol, rooted, stockrom
U wont install the update on rooted device... u have to disable it temporary or root it after clean update again with matts utl ...
jeff_roey said:
I did take the update last night and it did break my root. He's a quick summary:
1. Did a check for updates and was notified that 165 was available. I postponed.
2. Downloaded/installed Voodoo OTA Root Keeper. I backed up root but didn't temp remove it.
3. Uninstalled SS 3.65
4. Installed the 165 update, checked root and it was broken.
5. Tried reinstalling root with voodoo and it wouldn't take.
6. Used Matt's Utility to restore root and it took successfully - I don't know why but for me, Matt's utility only runs if it's unzipped to my C; drive (not my desktop) and I have to put my phone storage in MTP mode, not mass storage.
7. Matt's Utility restored root just fine but when I went ahead and tried reinstalling SS 3.65, I put my phone into a Moto Logo Boot Loop. :crying:
8. Thought I was done for - starting checking on the status of my warranty and insurance deductable but the forums helped dig me out of the mess by getting me to the AP Fastboot screen.
At the end of it I had to completely wipe and reinstall stock JB using Matt's Utility, re-installed the 165 update, re-rooted (again w/ Matt's Utility and NO issues doing so on top of the 165 update) re-installed all user apps, and finally re-installed SS 3.65 with NO issues on top of the 165 update. Haven't re-created a slot 1 and re-loaded CM 11 just yet but i don't expect there to be any issues going further.
In retrospect I think the Moto Logo Boot Loop was a function of something that got corrupted when trying to re-install SS 3.65 on top of it all, perhaps because I dodn't bother to wipe caches or even do a re-start between some of the major steps outlined above.
* I do recommend taking the time to wipe caches and reboot after uninstalling custom recoveries if you're heading down this path.
Click to expand...
Click to collapse
What's the root alternative for XT910 users? I'm not updating but it would be nice to know.
deleted.....
Updated ota fine. Rootkeeper worked fine.
Sent from my DROID RAZR using xda app-developers app
Drunkula said:
Updated ota fine. Rootkeeper worked fine.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
So what is the update for? What is being updated specifically? Any reason reason to update?
XT912 RaZR SpYdEr CDMA
hit ThAnKs if I was helpful!!!