I downloaded 1.83 signed and flashed it to my atrix. when it rebooted it says my system is running 1.83 but it still says its trying to download the update and it cant because it is not available at the time. Just curious if i should proceed with the root or if i need to wait untill the download is available again
hmm same thing happened to me, and it wouldnt go away... I than flashed to 1.2.6 and connected my phone to teh comp than updated with motorola software updater to 1.8.3 and its fixed now
Related
Ok this morning i found out the official Froyo OTA was just released. I was running 2.1 EA28. I attempted the official OTA manual update, but kept on getting that stupid message, so I reflashed my phone to dl01 via Odin so i could do the OTA but failed, Then i reflashed my phone again to a newer build the dl09 and attempted the OTA and still failed. So i attempted the sd card method in safe mode, first using the ea28 update zip file, couldn't even do that. On all the methods i get stuck on my unpacking screen on my phone about 30% on "updating modem". Now im stuck on the dl09. If anyone has any suggestions please let me know, i've been at this, this whole morning and mid afternoon and losing my patience! All i want is to run Froyo on this stupid phone, but there are so many freakin problems!
try files from here, sometimes these phones are picky.
http://http://forum.xda-developers.com/showthread.php?t=1026746
I have an AT&T Atrix and have done very minor mod's. Gingerbreak to get root, the radio fix, and allowed tethering by changing the true/false flag in the config.
Runing 1.57 at the moment and figured I should get around to updating to 1.83 (i had frozen this with titanium backup), however it fails and I get the triangle/exclamation mark/robot picture on boot and have to pull the battery and restart.
Am I going to have to somehow go back to defaults and wipe phone to be able to update? If so how?
Help appreciated, this is my first android phone
I was having the same problem. So i flashed back to 1.26 thru rsd lite and then with the phone completely unmodded I downloaded and installed the OTA update. Then proceeded to apply mods.
Quickest way would be the 1.8.3 sbf followed by the 1.2.6 sbf then ota to 1.8.3 in a close second. Both options wipes the phone AFAIK so backup user data
Sent from my GT-I9100 using XDA Premium App
SBF to 1.8.3 Gingerbreak. Done. wipes your internal sd, so backup.
Great thanks for the advice, I had a feeling I was going to have to reflash it in some way.
ok I picked up some directions from brief mobile (it wont let me show the link) ... however it keeps failing during the update.
Everything works fine does exactly what the guide says, it start executing and then after about a minute or so it fails.
Anyone have some better directions or another sbf file? Preferably an sbf for 1.83?
Never mind, sorted it out, just my work computer being retarded for some reason.
GladRoot is still my preferred method of root, whenever moto releases a new update all I have to do is accept it and run afterupdate.bat.
Guys I'm new to the forum but have been messing around with custom pseudo-roms for the Atrix for a little while now. I was running Adeo, then Gingerblur, then Greyblur all without a hitch when I heard about the new OTA update coming to the phone and Gingerbread coming up, so I wanted to go back to any build that would allow me to get the HSUPA update as well as the gingerbread update, but when I went to flash my phone to sbf using rsdlite, it said internal programming fail and nothing else happened. I installed gingerblur over greyblur in an attempt to see if it would flash, but nothing. Have done a factory data wipe, still can't flash. I can't even get into the stock Android Recovery, all that comes up is a triangle and exclamation point. Could someone please help me out here, I'm running gingerblur on a rooted Atrix on 1.5.7 and cannot get it to flash sbf, all I want to do is go back to stock att rom for the coming updates.
Thanks,
BK
Hey,
I have the same exact set up as you. It seems vague in your post if you re-flashed back to 1.26, and that may be why you're getting errors? Every time I update roms, I re-flash to 1.26 using the method in the link below.
http://forum.xda-developers.com/showthread.php?t=991072
Then I ran Gladroot to unlock, enable sideloading, etc.
http://forum.xda-developers.com/showthread.php?t=1016060
Downloaded and install the 1.83 update online (not on-air because I didn't get prompted)
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=9098bc50a569f210VgnVCM10000081bbb00aRCRD
I ran the 'afterupdate.bat' on Gladroot after installing the update.
And I now have 2.2.2 / 1.8.3
Thanks bud, what I ended up doing was trying to manually uninstall gingerblur and greyblur and the adeo rom by using scripts etc but it never worked. My phone started acting weird, the home button stopped working, no 3g connectivity, it would say I have superuser but it wouldn't be rooted... something was seriously messed up. I tried to get into the stock android recovery but it wouldn't boot, I think something was corrupted. I knew sbf files rewrite system and boot data, so I went into tenfar's custom recovery (after rooting for the 10th time) and deleted system and boot data, system data was deleted, but boot data had an error. I wiped the caches and all and I tried to sbf flash to 1.8.3 but nothing and the phone bricked. I then tried it on another computer with more memory than mine (mine was running kind of low because of a linux partition) and the flash worked and I'm on 1.8.3. I think I'll wait for official gingerbread and unlocked bootloader in July before I mess with my phone again.
I just pulled and installed the 2.3.4 OTA.. after the install and reboot I am stuck at the Motorola M... I have tried a Factory Reset as I can get into FastBoot etc..
What would be my best course of action? Should I just flash a ROM like Ninja?? or try to go back to stock 1.26 then update from there or will I Brick going that route? Any help would be greatly Appreciated!
What were you on before the update?
Beamed from WinBorg 4G via XDA Premium
I was running stock 1.83 Rooted. Only other thing was flashed 2.3.4 radio..
Same issue as OP (stock 1.83) but I didn't flash a radio, I only rooted with gingerbreak. OTA update installed and rebooted, went to the M logo screen (the version that isn't flashing/pulsing) and stays there. Grabbed the update off motorola's site, put it on my SD card, booted to recovery and installed with that, rebooted, same result
I've got the same issue. Was running stock 1.83 before, rooted and with a custom boot animation. Applied the update and now stuck at the dual core splash screen, even after a factory reset from the Android Recovery screen.
Adrian, I am now up and running....
I unlocked the bootloader using pudding and then flashed 2.3.4 using fastboot from KennethP...
However now there seems to be an all-in-one SBF that I actually just installed on my phone as well that is at the top of the pudding thread:
http://forum.xda-developers.com/showthread.php?t=1136261
Where it says Update July 23... where it says "Download ATT 2.3.4 Pudding+root here... " After flashing that via RSDLite you can click on the link right before that link in the same statement.. "root in preinstall (don't ask questions, read the post in this link)" to Root the 2.3.4 Atrix.. Hope this helps!
Thanks- I tried that route but ended up totally bricking. As in will not even turn on. Hopefully that's so bad that AT&T will replace the phone.
Adrian, I am sorry to hear that.. I would try AT&T and tell them that you pulled and installed the OTA. Hopefully they will do a replace.
Hi everyone,
I tried to update from Gingerbread 2.3.4 to ICS using KIES. When i ran KIES from my computer it found that my mobile needed to update. Now whilst it was updating it stopped at 87%.
So i followed the instructions to revert back to its original 2.3.4. however when it restarted it now says that i have the 4.0 update.
When i went through the mobile, i found that its kind of a mix between the 2.3.4 and 4.0 (some updates are there and some are not).
I tried to run the update again and it cannot find the update.
Is there a way to run the update again?
thanks guys
if your phone is messed up by the Keis, and no more recognizing your phone, I think the option left for you is to flash a Stock rom from ODIN.