Related
Excuse my noobishness please,
The Atrix is my first android phone. (Finally got bored of the iPhone).
I was looking at installing GreyBlur. Currently I'm on a rooted 1.8.3 (used afterroot.bat/gladroot).
My question is:
If installing GreyBlur using CWM, does it affect any of my existing data on the phone's internal storage, SD card, etc?
Would I be reinstalling apps and losing messages, etc, or does it retain everything?
Thank you!
No worries!
It should retain all of your data, music, etc. It's a pretty simple process.
My only advice: if you're switching to a different P-ROM (like from GingerBlur to GladAtrix), reflash your phone with RSD. I went from GingerBlur to GladAtrix and had tons of problems.
drumercalzone09 said:
No worries!
It should retain all of your data, music, etc. It's a pretty simple process.
My only advice: if you're switching to a different P-ROM (like from GingerBlur to GladAtrix), reflash your phone with RSD. I went from GingerBlur to GladAtrix and had tons of problems.
Click to expand...
Click to collapse
Awesome!
I'm probably going to stick with one PROM for now. If I was to reflash using RSD to switch over to a different rom, what's the deal with existing data?
Also, I know these roms are deodexed, and that causes an issue with receiving OTA updates. Assuming Motorola releases a new update sometime soon, how would I go about flashing to the updated firmware while retaining my information, or is it not possible?
I believe I had to use SBF recovery or something?
Thanks!
silentecho13 said:
Awesome!
I'm probably going to stick with one PROM for now. If I was to reflash using RSD to switch over to a different rom, what's the deal with existing data?
Also, I know these roms are deodexed, and that causes an issue with receiving OTA updates. Assuming Motorola releases a new update sometime soon, how would I go about flashing to the updated firmware while retaining my information, or is it not possible?
I believe I had to use SBF recovery or something?
Thanks!
Click to expand...
Click to collapse
When you flash an sbf, your data and info will be reset so make sure to do a complete backup before flashing an sbf file.
As far as OTA updates go, I'm not well versed but I believe it is recommended to do a fresh sbf -> update OTA -> then install whatever P-ROM.
I THINK, devs are pretty quick about releasing the latest update though so you might just be able to flash from old P-ROM to update P-ROM ? again, just my assumptions.
k00ey said:
When you flash an sbf, your data and info will be reset so make sure to do a complete backup before flashing an sbf file.
As far as OTA updates go, I'm not well versed but I believe it is recommended to do a fresh sbf -> update OTA -> then install whatever P-ROM.
I THINK, devs are pretty quick about releasing the latest update though so you might just be able to flash from old P-ROM to update P-ROM ? again, just my assumptions.
Click to expand...
Click to collapse
Option 2 sounds pretty damn convenient lol.
backup
k00ey said:
When you flash an sbf, your data and info will be reset so make sure to do a complete backup before flashing an sbf file.
As far as OTA updates go, I'm not well versed but I believe it is recommended to do a fresh sbf -> update OTA -> then install whatever P-ROM.
I THINK, devs are pretty quick about releasing the latest update though so you might just be able to flash from old P-ROM to update P-ROM ? again, just my assumptions.
Click to expand...
Click to collapse
I was just wondering what people always mean by 'complete backup'.
What I do is I backup my sd / ext-sd and also all the user apps/data with TitaniumBackup.
But is there a way to create a full image of the system to be able to recover it with CWM?
If yes, how?
Thanks
redThd said:
I was just wondering what people always mean by 'complete backup'.
What I do is I backup my sd / ext-sd and also all the user apps/data with TitaniumBackup.
But is there a way to create a full image of the system to be able to recover it with CWM?
If yes, how?
Thanks
Click to expand...
Click to collapse
I'd like to know this as well before I even attempt to install any custom ROM.
Just as a precursor and in advance--I apologize if I missed a thread on this topic here. I searched a number of different times and ways but didn't find any so hopefully I am speaking for others with the same problem with this newly generated one!
So I got a brand new Atrix about 2 days ago and just like every Android I get, I came straight to XDA right after initial boot and a little play-around with it to get the rooting process started . I downloaded the Gingerbreak .apk (I believe it was v 1.0) and rooted with no problem. However, later on while checking the phone out a little more, I stumbled upon the "System updates" section under the "About phone" category in the settings and out of curiosity (and not knowing anything about software updates etc.) thought I'd check it. Well it detected that the 1.57 update was available as the phone obviously came stock with the 1.26 to begin with. So I went and ahead, downloaded it and then attempted an install.
It would get about...oh, I'd say 40% of the way through the install process and then fail (I'm guessing this was the case anyway as the arrow coming out of the package pointing to the android suddenly just turned into the dreaded "!". So I just pulled the battery and rebooted and thought, "Hmm, well it's probably because I've got it rooted--must be something in the system files that's preventing it from pushing the update through successfully."
Next, I figured I'd try a different route and push the update through RSD Lite 5.0. Followed all instructions to a T and just about the same thing happened during install THAT way (i.e. Process failed about 40% or so of the way through).
Following that, I searched to see what unrooting methods were available following the previously botched attempt at a solution. I found a thread mentioning that v 2.0 of Gingerbreak had an unroot option>followed instructions>unrooted (no detected problems there)>attempted to push OTA update again and no dice. Same issue again. I'm both beginning to run out of solutions and am exhausting myself as I usually only have time to do this late at night when I should probably be sleeping (pssh, who needs that, right? )
Anyway, if someone who has experienced similar issues or knows what is going on here could point me in the right direction it would be GREATLY appreciated as I feel like I've got a phone that's not working to it's full potential (after having read what all the updates do)! Thanks a TON in advance for any help!
Save yourself some frustration..
Backup your stuff using titanium backup
Download the stock 1.2.6 SBF
-flash it using RSD lite
-root your phone using gladroot
-update to .57 from your phone (system updates)
-run afterupdate.bat
-update to .83 from system updates again
-run afterupdate.bat
Done.
Restore from titanium backup (batch restore is your friend..)
Sent from my MB860 using XDA App
FYI - you don't need to run afterupdate between 157 and 183 upgrades. Worked fine for me twice.
Sent from my MB860 using XDA App
nsaia said:
FYI - you don't need to run afterupdate between 157 and 183 upgrades. Worked fine for me twice.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I figured that from the part of the script that asks if you intend to update. I did it anyway, it was reassuring to see I still had root before the upgrade lol. Good to know for next time though
Sent from my MB860 using XDA App
Save yourself some frustration..
Backup your stuff using titanium backup
Download the stock 1.2.6 SBF
-flash it using RSD lite
-root your phone using gladroot
-update to .57 from your phone (system updates)
-run afterupdate.bat
-update to .83 from system updates again
-run afterupdate.bat
Done.
Restore from titanium backup (batch restore is your friend..)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thank you kindly sirs (knlgSeeker and nsaia) for the help. Cool. Sounds like a plan. I've already got a backup w/ Titanium on my phone actually (it's always something I keep a copy of on the trusty ext SD) so that should be good to go. Do you by chance have the links for the SBF's you were referring to? I think I might already have the 1.57 one (as I had mentioned in the original post) but I'm sure it wouldn't hurt to post it again. Thanks again in advance!
jz4467 said:
Thank you kindly sirs (knlgSeeker and nsaia) for the help. Cool. Sounds like a plan. I've already got a backup w/ Titanium on my phone actually (it's always something I keep a copy of on the trusty ext SD) so that should be good to go. Do you by chance have the links for the SBF's you were referring to? I think I might already have the 1.57 one (as I had mentioned in the original post) but I'm sure it wouldn't hurt to post it again. Thanks again in advance!
Click to expand...
Click to collapse
No problem..here's all the info/ links you should need:
http://forum.xda-developers.com/showthread.php?t=991072
Just remember, 1.26 is the only one you will need to flash from RSD.. Just do an OTA update for .57 & .83
Sent from my MB860 using XDA App
No problem..here's all the info/ links you should need:
http://forum.xda-developers.com/showthread.php?t=991072
Just remember, 1.26 is the only one you will need to flash from RSD.. Just do an OTA update for .57 & .83
Click to expand...
Click to collapse
Cool. I had actually gone ahead last night and eventually found it myself. Was good to come back though and get some reaffirmation as to whether or not the location I had found and instructions were the correct ones. After clicking on the link you provided I found that it was the exact same thread/post that I had used to do it. So thank you again!
I also had some interesting info to pass along as well. I just thought after flashing 1.2.6 again from RSD Lite that I'd go ahead and just do the OTA updates for .57 and .83 to make sure that they worked and they did. Obviously my concern while going ahead and skipping to those steps was whether or not I'd still be able to get root and I'm happy to report that I was still able to get root after doing so. I just sideloaded the Gingerbreak 2.0 app and it rooted no problems at all! Thanks again for your help guys!
Another random question to throw out there (I figured I might as well just post it in here to see if there's an easy fix: I've got ClockworkMod Recovery on here and I was trying to flash the recovery for the Atrix. However, when the "Confirm Phone Model" comes up, I don't see/find an option for the Atrix. Are we supposed to use a different phone model's version of recovery? Thanks again in advance for any help!
jz4467 said:
Cool. I had actually gone ahead last night and eventually found it myself. Was good to come back though and get some reaffirmation as to whether or not the location I had found and instructions were the correct ones. After clicking on the link you provided I found that it was the exact same thread/post that I had used to do it. So thank you again!
I also had some interesting info to pass along as well. I just thought after flashing 1.2.6 again from RSD Lite that I'd go ahead and just do the OTA updates for .57 and .83 to make sure that they worked and they did. Obviously my concern while going ahead and skipping to those steps was whether or not I'd still be able to get root and I'm happy to report that I was still able to get root after doing so. I just sideloaded the Gingerbreak 2.0 app and it rooted no problems at all! Thanks again for your help guys!
Another random question to throw out there (I figured I might as well just post it in here to see if there's an easy fix: I've got ClockworkMod Recovery on here and I was trying to flash the recovery for the Atrix. However, when the "Confirm Phone Model" comes up, I don't see/find an option for the Atrix. Are we supposed to use a different phone model's version of recovery? Thanks again in advance for any help!
Click to expand...
Click to collapse
All's well that ends well! Not sure what exactly you're trying to flash, but I use Tenfar's CWM..
http://forum.xda-developers.com/showthread.php?t=1019143
It's pretty straightforward, you can boot to recovery in 2 steps
Sent from my MB860 using XDA App
All's well that ends well! Not sure what exactly you're trying to flash, but I use Tenfar's CWM..
http://forum.xda-developers.com/show....php?t=1019143
It's pretty straightforward, you can boot to recovery in 2 steps
Click to expand...
Click to collapse
Sweet. I think I had run into that same thread earlier on (and had actually already installed that same app on my Atrix) and had completely forgotten about it. So thank you for refreshing my memory on it and directing me to it again! Thanks for all your guys' help in general as well!
Got another question for ya: How do you delete all the bloatware off of the phone? I've got Root Explorer and what I usually do is just navigate in like fashion: system>app>and then just delete any of the bloatware apps. However, I've found with this phone that there isn't a single one of the at&t apps found inside this "app" folder. I HAVE found them in the following way however: system>preinstall> BUT there's no way to change how the files found within are accessed (i.e. mounting them as r/w rather than r/o) and so as a result there is no way to delete them. The option to mount the files as r/w is simply not there. Any info on this would be great! Thanks in advance again.
By the way, if you have any questions concerning the Samsung Captivate, I'm pretty knowledgeable about that phone--gained quite a bit of knowledge during the time that I owned it which was probably about 6 months.
So I originally rooted using SuperOneClick, then I got an OTA that broke root. I then found gingerbreak and rooted using that method. I have done a few cool things, like change the boot animation and lock/unlock sounds, enabled sideloading, etc.
Anyway...
With rumors and speculation about Gingerbread coming out in the coming months (hopefully), I am wondering if the boot animations, lock sounds, and/or SuperUser access will deny the OTA from installing. Is it a good idea to return the ROM to stock to avoid any bugs?
Second,
Specifically on the Atrix, if I performed a factory reset, I assume I won't lose root access, but would I lose the boot animations, and lock/unlock sounds? Let's say I wanted to return it to a 100% stock ROM (un-root, stock boot animation, EVERYTHING) before the 2.3 update comes, how would I do it? I feel as though if I perform an OTA with the mods I've done to it, some unknown bugs/issues would appear (I've seen PLENTY of bugs as is). Can anyone shed some light on this? Call me paranoid, but I've seen too many software issues with this phone, and I'm hoping 2.3 will address them, and I hope I don't introduce any new bugs by updating a modded phone.
You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.
If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.
rytymu said:
If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.
Click to expand...
Click to collapse
Try this.
Motorola
brewstermax said:
Try this.
Motorola
Click to expand...
Click to collapse
I have 4.1.83, and this will not work for it.
I would be interested in learning more about this too
Sent from my MB860 using XDA Premium App
This is a thread I commented on over at the Motorola forums. I actually got the forum manager to comment on the issue:
"rytymu
What do I do if I'm on 4.1.83 and want to return to stock (rooted)? The software given just says my device is up to date...
Mark (Forums Manager)
With next update/upgrade you will go up to next stock version. You have to
wait til then.
rytymu
So if I understand right:
I most likely will not get an OTA notification because of the root access, so when I run the Motorola Software Update program after the next update comes out, it will then flash a 100% stock image as if I just pulled it out of the box? This includes removing/wiping busybox, root access, boot animations, and EVERYTHING else?
Mark (Forums Manager)
If you are on 4.1.83 but modded you will get ota notification but will
likely fail on install. If MSU is made available you can update /upgrade to
that version. Root and other sideloaded things will be removed. Stock ATRIX
Att software. Not AOSP Android."
I guess this is what I'm looking for, unless someone interprets otherwise...
brewstermax said:
You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.
Click to expand...
Click to collapse
OTA update should be fine if you have not deleted any of the original Moto files/bloatware, or leave any of the original Moto bloatware frozen. The updates only throw up at you when there are missing or frozen Moto apps and/or files.
If you are on 4.1.83, (or any firmware), and rooted only, you will get the update fine, but will lose root.
If you have flashed for example GladiAtrix, you will more than likely have to flash back to stock first.
If you have rooted on any version and then frozen any apps, thaw those apps and you will update fine, but again lose root.
Every time you update you lose root.
So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860
beazie0885 said:
So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860
Click to expand...
Click to collapse
If you installed a newer version of the same Swype, this should I imagine be the same as updating Swype. I'm thinking this would allow you to just unfreeze all the bloatware and update OTA. Only thing I can think of is that you try the OTA when it's available, and if it balks at you, flash back to stock.
I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager at Motorola instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App
rytymu said:
I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. Now, I'm actually in the "soak" beta feedback over at the motorola forums, and I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
The Moto Software Update is not needed, and Mark, or whoever over on the Moto forums did not "tip" you off to this. This is no secret, and is well known. (BTW, you are breaking the NDA just by saying you are in beta, (soak feedback forums are down in any event as they are always taken down between betas), but that's another story, and being in beta doesn't make you more knowledgeable either).
You have made this sound more complex than it is.
To go back to stock (and the instructions are all over the forums BTW) --->
Flash 4.1.26, OTA to 4.1.57, OTA to 4.1.83!..............Done!
Or ------------>
Flash 4.1.57 sbf, OTA to 4.1.83!..................Done!
People who were having the OTA notification issues, (continually popping up), were those who flashed the 4.1.83 sbf which is floating around, and that's why they were told to flash 4.1.83 through the Moto Update portal.
(Edited above statement)
Sent from my MB860 using XDA App
I simply can't figure this out. I have an A500 that I have rooted successfully back a few months ago and installed HoneyVillain 1.04 ROM. It has worked flawlessly for months. Now I can't get root access with Titanium BU, BusyBox, Root Explorer or anything! I've tried re-rooting it using GingerBreak 1.2 with no success. I can access a backup that I made right after I rooted a few months ago, but that doesn't bring back root either. Can someone please tell me what to do before I make a 10.1" frisbee out of this thing. The tab's batery has been allowed to go completely dead once, but I don't think that would be the problem. I'd like to install the latest version of HoneyVillain if I can get root back. I sincerely appreciate anyone's help.
Sounds weird. You hadn't flashed anything else had you or installed a system update?
What's your kernel version & build number?
Have you tried using IconiaRoot?
Bubbamanlarry said:
I simply can't figure this out. I have an A500 that I have rooted successfully back a few months ago and installed HoneyVillain 1.04 ROM. It has worked flawlessly for months. Now I can't get root access with Titanium BU, BusyBox, Root Explorer or anything! I've tried re-rooting it using GingerBreak 1.2 with no success. I can access a backup that I made right after I rooted a few months ago, but that doesn't bring back root either. Can someone please tell me what to do before I make a 10.1" frisbee out of this thing. The tab's batery has been allowed to go completely dead once, but I don't think that would be the problem. I'd like to install the latest version of HoneyVillain if I can get root back. I sincerely appreciate anyone's help.
Click to expand...
Click to collapse
Did you by chance do a restore using cwm..? Every time I did a full restore I would loose root.
I haven't flashed anything and no system update. I'm about to try IconiaRoot 1.3. Still looking for the answer...I'll report back. Thanks!
I tried Iconia Root. It goes through the steps and says Done...Have Fun! Then a message says Iconia Root has been denied root privileges. I tried to unroot and it says something went wrong and I'm still rooted. I must be somewhere between rooted and unrooted! What now????
evangineer said:
What's your kernel version & build number?
Have you tried using IconiaRoot?
Click to expand...
Click to collapse
Kernel version is 2.6.36.4HoneyVillain-1.0+
Build number is HoneyVillain 1.04
Bubbamanlarry said:
I tried Iconia Root. It goes through the steps and says Done...Have Fun! Then a message says Iconia Root has been denied root privileges. I tried to unroot and it says something went wrong and I'm still rooted. I must be somewhere between rooted and unrooted! What now????
Click to expand...
Click to collapse
Don't use backup, reflash your rom and re root.
shaun298 said:
Don't use backup, reflash your rom and re root.
Click to expand...
Click to collapse
I'm giving that a go right now...
Bubbamanlarry said:
I'm giving that a go right now...
Click to expand...
Click to collapse
When that works I will give you the full story of what I found, if it works.
shaun298 said:
When that works I will give you the full story of what I found, if it works.
Click to expand...
Click to collapse
Well, you're right - it did work. I didn't even have to root again. Everything is back after the reflash of the ROM. Now tell me the full story. I'm wanting (I think) to try the latest HoneyVillain ROM.
By the way, thank you VERY much for you help.
Bubbamanlarry said:
Well, you're right - it did work. I didn't even have to root again. Everything is back after the reflash of the ROM. Now tell me the full story. I'm wanting (I think) to try the latest HoneyVillain ROM.
By the way, thank you VERY much for you help.
Click to expand...
Click to collapse
You must not have wiped anything...? (Not that that is bad just more tech info for me), still learning.
Anyway, I have used honey vill and taboonay many version and with different kernals and love both roms.
What happans to me is I use cwm after I get the tab set the way I want and then do a full backup using cwm. Then I always want to fire test my backups so I immediately do a full restore using cwm, soon after I start getting denials from super user..? And after checking using a app from the market to check root, I have now lost root and can't get back, same as you.
I now just reflash the rom and if I do full wipe I reroot and all is well.
So I went with a different rom, backup and immediately do full restore and now no root again.
It happaned with every rom I have tried. Someone told me to delete the android.secure.image folder from the backup set that cwm makes. I tried that and that did let the restore, restore the flex rom folder but had the same problem. I have two a500 and both do this. I don' t know if stock rooted will do this as I have not tried yet. So what good is a full backup if it fudges your system. Maybe someone has a answer, but I have not found one. Sorry if this ain't your problem at all, but might be related. Later
shaun298 said:
You must not have wiped anything...? (Not that that is bad just more tech info for me), still learning.
Anyway, I have used honey vill and taboonay many version and with different kernals and love both roms.
What happans to me is I use cwm after I get the tab set the way I want and then do a full backup using cwm. Then I always want to fire test my backups so I immediately do a full restore using cwm, soon after I start getting denials from super user..? And after checking using a app from the market to check root, I have now lost root and can't get back, same as you.
I now just reflash the rom and if I do full wipe I reroot and all is well.
So I went with a different rom, backup and immediately do full restore and now no root again.
It happaned with every rom I have tried. Someone told me to delete the android.secure.image folder from the backup set that cwm makes. I tried that and that did let the restore, restore the flex rom folder but had the same problem. I have two a500 and both do this. I don' t know if stock rooted will do this as I have not tried yet. So what good is a full backup if it fudges your system. Maybe someone has a answer, but I have not found one. Sorry if this ain't your problem at all, but might be related. Later
Click to expand...
Click to collapse
That's amazing. I want to move up to the new HoneyVillain, so I guess I can count on rooting again? Wow. I love my Iconia though. I just remembered that I recently had trouble with WIFI so I DID do a restore via CWM. I guess I just realized that things weren't rooted! Oh well, you have provided some much needed info for me. At least now, I will know what to expect. Thanks again. Have a blessed evening.
I also had the wifi problem, and that is what started the whole thing with the full restore. Have a good one.
The same thing happened to me. I just installed another ROM to fix it.
Kinda ridiculous though. At least we know how to deal with it.
Thanks for this thread -- confirmed my sanity when I lost root after a CWM restore. Does anyone know if the updated version (1.6) of CWM for the A500 fixed this problem?
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
ogal said:
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
Click to expand...
Click to collapse
why dont u just make a nandroid, fastboot back to stock ics with rsd, dont root your phone or do if you think it doesnt matter which ur right ive flashed the leak and official multiple times already both rooted and not, boot back to recovery and try it again...i heard this might help although i never have had to but rename it update.zip.
heres the one i used have never had a problem:
http://forum.xda-developers.com/showthread.php?t=1982934
Hi, I've downloaded the OTA update from Verizon for my Razr M three times this morning because each install shows "The Software Update Failed". It'd be just peachy if they didn't make me download all 250 MB each time I tried. Sheesh.
Aside from that, it's still not updating. This phone is rooted, but has never had a custom ROM put on it.
Hmmm...now that I think about it, I do have a bunch of apps disabled, including some Verizon apps, etc. I'll try enabling them and trying this all again.
Hmmm...didn't work. Still getting the failed error message. Going to back everything up and do a Factory Reset.
lostpilot28 said:
Hmmm...didn't work. Still getting the failed error message. Going to back everything up and do a Factory Reset.
Click to expand...
Click to collapse
I am currently having the same issue in attempting to download/install the latest VZ update. I've done a factory reset and tried voodoo rootkeeper to temp unroot the phone to no avail. The only modifications I had made before the reset were deleting some of the bloatware manually with root explorer- those apps were subsequently restored from the reset.
Any idea how I can update the phone? Given that there is currently no way to install a custom ROM currently and can only delete bloatware, I'm thinking rooting this phone doesn't really help much if we are then not able to update it
Update
fiendebass said:
I am currently having the same issue in attempting to download/install the latest VZ update. I've done a factory reset and tried voodoo rootkeeper to temp unroot the phone to no avail. The only modifications I had made before the reset were deleting some of the bloatware manually with root explorer- those apps were subsequently restored from the reset.
Any idea how I can update the phone? Given that there is currently no way to install a custom ROM currently and can only delete bloatware, I'm thinking rooting this phone doesn't really help much if we are then not able to update it
Click to expand...
Click to collapse
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
ogal said:
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
Click to expand...
Click to collapse
I upgraded to JB via OTA from Verizon, you will not lose anything if you upgrade that way, nor will you have to setup anything again. If you flash it through RSD lite than you probably will lose everything plus have to go thru the setup process again. Hope this helps. Make sure you uninstall safe strap recovery and if you're rooted make sure you backup and save root via the voodoo app, before accepting the OTA. I found out the hard way. If you don't uninstall the safe strap recovery the OTA will fail every time.
Being rooted does not have anything to do with the OTA failing. Its safe strap if you are using that.
Sent from my XT907 using xda app-developers app
fiendebass said:
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
Click to expand...
Click to collapse
I used this method phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock-ICS-from-the-JB-leak_id35580 .
Followed all the links and tried to RSD back to stock and then OTA, but now Im bricked....any suggestions on flashing a fresh copy of ICS using RSD LITE??
fiendebass said:
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
Click to expand...
Click to collapse
Could you direct me to somewhere I can find out details about this? What is the fastboot method?