I flashed the 1.83 sbf using rsdlite and then flashed greyblur 2.1 over it, now in the "about phone" section it says I'm running 1.57 and always askes me to update.
Help?
This is happening to me too
Sent from my MB860 using XDA Premium App
Is it the same update pop up that was on stock? I had an update in my notification bar but it did not say what it was or let me cancel it.
It's the OTA 1.83 update for users that are on 1.57, but i already upgraded
Yeah this happened to me too. I was rooted on 1.57 and updated. Ran afterupdate and got root back. Than I installed GreyBlur and im back to 1.57 now.. :-/
Sent from my MB860 using XDA App
Its because greyblur isn't compatible with 83 yet. A lot of psuedo roms make changes to /system, and that include their own build.prop file. That makes it look to the phone that its on 57 and not on 83. Wait until greyblur gets updated or dive into the zip yourself and make your own changes.
Sent from my screaming Atrix *4G* using the XDA App
I'm really having a hard time here with this. This is my first custom rom I've installed. If I should wait for 83 compatibility. How do I uninstall the rom? If I accept the OTA update will it uninstall the rom for me?
Should I settle with GingerBlur instead? I really hate sounding like a newb here, but I've been digging deep into the forums and not really finding a clear answer about this issue.
ZombieChris said:
I'm really having a hard time here with this. This is my first custom rom I've installed. If I should wait for 83 compatibility. How do I uninstall the rom? If I accept the OTA update will it uninstall the rom for me?
Should I settle with GingerBlur instead? I really hate sounding like a newb here, but I've been digging deep into the forums and not really finding a clear answer about this issue.
Click to expand...
Click to collapse
Did you make a backup in Tenfar's recovery before you installed the rom? If so, its a simple process of restoreing the backup. If not, I personally would flash using the sbf available to whatever version. That basically will just reinstall your system, but keep your data (I.e. music not apps). I don't know what will happen if you update on greyblur... maybe try it? You could fall back on using the sbfs if needed. Gingerblur is great, although there are mixed repotlrts on bad batterylife with it. I'm personally on stock with LauncherPro until the next gladiatrix comes out.
Its good that you are asking questions before doing things.
Oh, P.S. you could use titanium backup to backup your apps.
Sent from my screaming Atrix *4G* using the XDA App
Actually I think this more to do with the fact that GreyBlurr came out when 1.57 was the current firmware version. It has that listed in the build.prop file. So the phone thinks it is 1.57 even though it is really 1.83. If you have root explorer you can safely edit that file to show the correct version (its the top line).
If you don't want to do that and you have Titanium Backup, you can freeze the Updater app.
Thanks for the advice Tyler.
I ended up flashing back to 1.26 and just rerooting again with GladRoot.
I now have GingerBlur installed and am very pleased with the results. =)
I've only had this phone for a weeks and it's my first droid, so I'm definitely learning a lot.
ZombieChris said:
Thanks for the advice Tyler.
I ended up flashing back to 1.26 and just rerooting again with GladRoot.
I now have GingerBlur installed and am very pleased with the results. =)
I've only had this phone for a weeks and it's my first droid, so I'm definitely learning a lot.
Click to expand...
Click to collapse
I'm glad you found something that works, and I'm glad to help anytime
Sent from my screaming Atrix *4G* using the XDA App
Related
Hey all, been traveling around the world for a couple months and now that I'm back my poor DroidX needs some ROM lovin =)
I currently have RubiX 1.6, Android 2.2, System Version 2.3.15.
I've been reading and reading all the forums and I'm getting a little confused on what my upgrade path should be. Some have said I can just do the OTA update and it should work, others have said to do an SBF back to 2.2 Vanilla, then OTA, then root and ROM to rubiX 1.90 or whichever I would like.
I dont feel like the OTA would work with mine, but I would love to hear what xda thinks. Im on info overload right now, read too many posts by too many people that dont seem to know wtf they are talking about =)
I believe (someone correct me if I'm wrong...) But if you are running a custom rom, most devs recommend an sbf before updating just to reduce the chance of additional problems when trying to update.
I don't think you can pull the update with your current setup and have it install correctly as rubix has stripped out some bloatware I believe.
I would recommend using the full 2.3.15 sbf and a factory wipe. Be sure to create a nandroid backup before all this and backup any apps/data you would like to save as well
Sent from my DROIDX using XDA App
I'm runng rubix 1.9 on 2.3.15...
Best bet would be to look at the thread for the most recent version (or version you are looking top update to) as the dev well usually include a path for updates... could be wrong, but I feel like this is somewhat common
Sent from my DROIDX using XDA App
Perfect, thanks, just need to search more!
tahoe916 said:
Perfect, thanks, just need to search more!
Click to expand...
Click to collapse
No problem. Just make sure before performing an sbf for 2.3.15 version, that that is tryout actual version and your bootloader version is 30.03
Sent from my DROIDX using XDA App
So I couldnt find a thread that quite answered my question. I have many ideas, but no sure answer, and I dont want a brick.
I have a rooted and Deodexed X on 2.2 that couldnt update to 340 for whatever reason. I want to update to OTA 340 and run the ApeX 141 ROM on that. Should I undo the root and reodex the phone before updating? Can I update it somehow as is and not have a brick? I saw something about doing an SBF, but Im not entirely sure if thats what I do...
Ive been away too long... ha
You could do an sbf, it is not too hard but if you don't know much about it you might as well try to stay away from it. What system version are you on exactly?
If you end up doing an sbf back to stock there are a few videos on youtube that walk you though the process. I watched xdroidroms and it worked perfect for me.
Sent from my DROIDX using XDA App
http://www.youtube.com/watch?v=N0jrXqqiepI&feature=youtube_gdata_player
Video walkthrough
Sent from my DROIDX using XDA App
If you decide to sbf it will automatically put you on 2.3.340. Just download the full version not the system only file. After that z4 to root. Install bootstrap make a backup and flash away. Good luck. Don't worry doing an sbf is not hard. Just read and read some more.
Sent from my DROIDX using XDA App
SoundZombie said:
So I couldnt find a thread that quite answered my question. I have many ideas, but no sure answer, and I dont want a brick.
I have a rooted and Deodexed X on 2.2 that couldnt update to 340 for whatever reason. I want to update to OTA 340 and run the ApeX 141 ROM on that. Should I undo the root and reodex the phone before updating? Can I update it somehow as is and not have a brick? I saw something about doing an SBF, but Im not entirely sure if thats what I do...
Ive been away too long... ha
Click to expand...
Click to collapse
I'm running that now, it's awesome.
2.2.1 rooted apex 1.4.1 honeybread v2
What I ended up doing was the Materstcok method. Seemed to be a lot easier then trying to learn sbf. Unfortunately I ended up having to do an sbf anyway because I tried deodexing for some reason. Haha. It all worked out in the end anyway. Loving the ApeX ROM as well!
Sent from my DROIDX running ApeX using XDA App.
Sbf wasn't as difficult as I thought, I used it to get back to stock in order to be able to flash gingerbread.
Droid X 2.3.3 Rooted
My Atrix 4g is rooted on 4.1.57 and I am not seeing the latest 1.8.3 update. help!
Me either. I'm pretty sure its not because of root though since others with root have gotten the update
Thats what I was wondering. I was able to update with the root last time, I don't see why this would be different
So we need to unroot and then update ?
And then root 1.8.3 with Gingerbreak?
Nothing should effect your ability to see it. If you have one of the pseudo roms installed, that will prevent you from installing it, however.
I don't think we need to un-root to see the update - that really shouldn't effect anything. Once we get to 1.8.3 GingerBreak will root it fine, the issue is just getting to that point via OTA Update which we aren't seeing
no root here and I'm still not seeing it yet.
1.8.3 isn't live yet FFS. So much damn misinformation floating around.
Sent from my MB860 using XDA App
dcarpenter85 said:
1.8.3 isn't live yet FFS. So much damn misinformation floating around.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://www.engadget.com/2011/04/30/atandt-brings-hsupa-to-atrix-4g-and-inspire-4g-one-requires-wifi/
frowny face?
And for a more solid piece of evidence that the previously mentioned article cited
http://www.wireless.att.com/answer-center/main.jsp?t=solutionTab&solutionId=KB117611
I would guess they're still in the process of "rolling out" the update. Just give it a little time.
My mom's Atrix is NOT rooted and isn't able to find the update. I have to flash the SBF through RSD Lite.
On a side note, the hell is
These software updates need to be installed in order, and are available to users via Wi-Fi only for the first 100 days
Click to expand...
Click to collapse
supposed to mean D:
That makes no sense. Let me use my" 4g" to download the update. But thanks everyone keep up to date if you get the update
Sent from my MB860 using XDA App
rocketboy6885 said:
http://www.engadget.com/2011/04/30/atandt-brings-hsupa-to-atrix-4g-and-inspire-4g-one-requires-wifi/
frowny face?
Click to expand...
Click to collapse
Rolling out doesn't mean live for everyone. Also, this update isn't official until ken releases Gingerblur 3.0 anyway, since the stock experience is pretty much a joke.
Is GingerBlur the best rom? // easy to install/update?
Sent from my MB860 using XDA App
Just flash the sbf it doesn't wipe any data of course im not running any mods or "roms" other than root. It did get rid of root though and running gingerRoot wiped my internal storage (like it said it would), but i backed that up no harm ;-)
So my area in NC is not "live" yet it seems.
Not live in Philadelphia either
Sent from my MB860 using XDA App
The patch isn't live yet folks! It's still being pushed out in testing.
I believe it's not root, but deodexed files which cause issues with updating. People with root have managed to update, but people like me who had GreyBlur had to flash back to 4.1.26, update to 4.1.57, update to 4.1.83, then root and sideload again. Also, before rooting, it's adviseable to use Kennethpenn's deodex flash for 4.1.83 first.
rooted, running gingerblur 2.5.. no update available yet here in south Florida. not too concerned about it though.. i did the HUSPA mod & i'm content for now
Morning all,
Is anyone running the Gbread 595 leak yet? I am thinking about trying it out this morning, as everything I read indicates it will be the launching point for what could be the official 596 release on the 13th.
Let me know if you have any observations on this.
Thanks,
Steve
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
owenbeals said:
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I agree. Apex is amazing. I will wait for it to update
Weird issue I am running into....
I upgraded to 588 with no problems from 340 Froyo. I used DroidX recovery to accomplish this. When I rebooted 588 I tried to go to 595. I tried using DroidX recovery but this did not allow me to boot into recovery...it only gave me a blank screen. When I got back to 588 I uninstalled DroidX recovery and then installed Droid2 recovery. I was then able to reboot into recovery and try to install 595. The install aborted saying it was looking for 3 arguments and got 4.
Any ideas? Which recovery should I be using thoughtout this?
Thanks,
Steve
Both recoveries (AFAIK) are the same clockwork recovery, it's just a different method of "bootstrapping" so that you can get into the recovery. Droid2 bootstrap works on gbread unless USB debugging is disabled, then droidx bootstrap works.
Sounds like you got a bad file.
Just redownload the file and it should work
Yes the one I downloaded yesterday was bad, and a new one was uploaded. I just downloaded the new one and am going to try again to move back up to 595. Once that happens I am hanging on til the 13th.
I would assume once this official update comes out then VZW will no longer support the DX with official updates. We really need to get Moto to unlock the bootloader for us, so we can continue to develop for the DX.
Steve
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
stevefxp said:
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
Click to expand...
Click to collapse
P3Droid released three different versions of .595: full stock, rooted and odexed, and rooted and deodexed.
You can try flashing one of the rooted .595 releases.
Sent from my DROIDX using XDA App
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
You shouldn't need Gingerbreak on the rooted ones, as they are already rooted.
stevefxp said:
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
Click to expand...
Click to collapse
If you are going to flash a rooted version what do you need gingerbreak for?
smiteme said:
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Click to expand...
Click to collapse
So you're not running it at all then... lol. You downgraded it back to .591 when you installed Liberty.
Sent from my DROIDX using Tapatalk
Curious, I'm running .573 now, if I flashed the latest rooted & deoxed, do I really have to sbf back to Froyo before hand like I've read in other places? OR can I just flash over it and roll on?
You only need to flash back if you don't have root, I believe.
Sent from my DROIDX using XDA App
Not having luck.
I tried to install, initially from my rooted deoxed stock .340 to rooted deoxed .595, first got a corrupted file report....would not upgrade.
Next got boot loop (repeating M), so SBF back to stock 340...Rooted and tried again with the same file and got a very unstable phone, reboots etc.
The only thing I can think of is that the phone was stock rooted but not deoxed, so when I tried loading the deoxed version it didn't like it? no idea.
I did a wipe before each load but can't seem to get it to work on my phone. My phone is very new.
SBF'd back to stock unrooted and I'll leave it like that to see if I can get the update from VZW.
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
I'm on 2.2 and waiting. Just not convinced about 595 and getting the update. How do we know its going to be 596.
Sent from my DROIDX using XDA App
infazzdar said:
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Not completely accurate.. I went from .588, to .595 without any adverse effects. Phone is a bit snappier than before too, app drawer scrolls more fluidly, etc.
Hello all, first poster here. I want to root my Atrix, but I already have 4.1.83. Will this cause any problems? Also could somebody give a basic outline of rooting and installing custom roms on this particular phone? Thank you in advance for the info.
go to development section and search gingerbreak. everything u need is there. requires sd card
Sent from my MB860 using Tapatalk
anemoneman said:
Hello all, first poster here. I want to root my Atrix, but I already have 4.1.83. Will this cause any problems? Also could somebody give a basic outline of rooting and installing custom roms on this particular phone? Thank you in advance for the info.
Click to expand...
Click to collapse
Please use the search option in the future as it will save you time in getting the answers you need.
http://forum.xda-developers.com/showthread.php?t=960336
http://briefmobile.com/motorola-atrix-4g-root
The first link is the thread over in the dev section that will link you to the second link I posted that will actually walk you through rooting and enabling side loading.
Good luck and back up your data first. You've been warned.
Ill tell you in a nutshell;
Flash 1.26
Run gladiroot
Upgrade to 1.57
Upgrade to 1.83
Run "afterupdate" gladiroot
Now you're on 1.83 rooted!
Sent from my MB860 using XDA App
roharia said:
Ill tell you in a nutshell;
Flash 1.26
Run gladiroot
Upgrade to 1.57
Upgrade to 1.83
Run "afterupdate" gladiroot
Now you're on 1.83 rooted!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That route works as well, but takes much longer and is tougher to do if he is already on .83
From what I understand he would be better off using the Gladiroot method, but he may not be able to do all of that depending on his skill level.
update didn't screw up root
I am new to rooting as well and new to android (messed around a lot with WinMo with generous help from xda thanks).
Rooted my atrix just prior to the OTA update with intentions to try out how rooting worked and hoping that the new update will give me a fresh start if I screw up.
Installed my update 4.1.83 and looked to see if I lost my superuser status, and lo and behold it was still there. Also managed to side-load an apk (original intent for rooting) successfully after the update.
Haven't come across similar experience along the way so far.
(I used gingerbreak).
I had GreyBlur on 4.1.57, did Titanium backup to the EXTERNAL CARD (not internal storage), ran RSD with the 4.1.83, re rooted, reinstalled recovery, reflashed GreyBlur and most of my apps and settings stayed. the missing apps just got installed by Titanium and I had to resetup my home screens, but it was pretty painless. if you go all the way back to 4.1.26, it will put your phone back to stock and you will have to start over again. The last PITA is to modify the build.prop to get rid of the OTA message.