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.
Hello,
I've been searching the forums for this but basically I did Gingerbreak/Gingerblur 4.5 from the now zombified post. I have since over looked the update 4.5.91 because I don't want to hard brick the phone, but now it looks as though I'm stuck on Gingerblur.
1) I CANNOT restore to factory settings via the phone (Get stuck in Failed to Boot 2 Starting RSD Mode lock out) no matter what I do.
2) After going into RSD protocol support, It will not recognize my phone at all on RSDLite v5.0 (so can't flash SBF files)
3) If I select Android Recovery it will result in "Failed to Boot 2"
I've been looking at the threads for the latest stuff, but none of them seem to address my issue. Any thoughts on how the heck I get this thing fixed? I'd like ideally to get Android 2.3.4 and the latest and greatest, but don't want to brick the phone. Any help would be greatly appreciated
BTW it works just fine in Gingerblur, but I'd like not to be stuck with that forever...
You are not unlocked. Feel free to flash an sbf as hard brick has to do with unlock and bootloader stuff.
My thoughts would be to just unlock your bootloader. Start with the pudding thread
sent from my Atrix via XDA premium
Well, perhaps I should have gone back to stock image first before doing Pudding.
Soft bricked my phone now. Stuck in Failed to Boot 2 - Starting RSD Mode
I will download the 1.26 from here:
http://forum.xda-developers.com/showthread.php?t=991072
and try to do a restore...I hope I haven't screwed my phone up...
I did the same and flashed it back to stock i used rsdlite 5.5 and used my country specific SBF.
It is back to stock but webtop Isnt working
Actually sorry. To clarify, I'm using this thread instead for the SBF.
http://forum.xda-developers.com/showthread.php?t=1125944
Will see if web top is a concern IF the stock file flashes properly...
Being on anything won't effect an sbf flash. Go ahead and rsd to gingerbread. Or pudding
sent from my Atrix via XDA premium
I got it back to 1.26
One thing people don't mention is if you have an older version of RSD Lite it will NOT recognize the phone with the latest drivers...(and there are a wealth of older RSDLites floating around so to a newer person it's not quite evident which is latest)
It's now on 1.26. I will try the bootloader unlock, pudding, etc later when I feel more comfortable...
I have been reading a whole bunch of stuff but can't seem to piece together what to do. My atrix is unlocked and rooted. I was flashing a rom and it started to boot loop. I would like to just flash it back to stock now. Confused if I should use fastboot or rsd. Some of the possible fixes I have found have bad links for downloads. I also saw a few things that said flashing back to stock with rsd could brick the phone??
After unlocking the phone I /would not/ recommend using RSD to flash /anything/.
When you unlock your phone, you burn a bit fuse that tells the phone you've unlocked it. There is no way to undo that. Using RSD improperly can cause your phone to hard brick and render it useless.
To avoid possibly breaking your phone from this point I would recommend taking a close look at what ROMs are available in the development section to see which one(s) suit your needs. Listed below are the ones I use on any of my three Motorola Atrix 4G's ( US ATT )
Neutrino ( CyanogenMod 7 Base )
NottachTrix ( Closest Stock Experience IMO and more customizable )
Currently I run NottachTrix because I like webtop, but prior to getting a lapdock for this phone I ran solely on Neutrino EE with 0 issues.
You'll want to take a look at setting up Motorola's USB drivers for ADB / Fastboot usage these are a must.
For either ROM to flash properly, AFAIK, you'll need to use ROMRacers Recovery found here.
These are just my personal favorites, as there are a plethora more ROMs out there in the development section. There may be a stock ROM that I just am not aware of you can flash through recovery, but I wouldn't know off the top of my head.
As far as fixing the boot-loop issue goes I would go into recovery and wipe cache / data / dalvik cache, under advanced in recovery, and then reflash the ROM you're trying to use.
That got me on the right track. Thanks it's fixed.
Awesome! Glad to have helped. =)
IMPORTANT: This guide is for users with a Motorola Photon 4G (MB855) running the 2.3.5 OTA update only. For the lucky ones still running 2.3.4, you want this thread. For those of you who don’t know what version of Android you are running, DO NOT try this. Please read these forums carefully and learn everything you can before attempting this.
This guide is based on the work of halfevildruid and his thread for unlocking GSM for Photon users on 2.3.4 with unlocked bootloaders. All users should take the time to carefully read through that thread here and keep in mind that it was written for 2.3.4/unlocked bootloader users. Some files and steps in that thread will not work on Photons that have had the 2.3.5 OTA applied.
Unlocking US GSM Carriers on 2.3.5 OTA
Before You Start:
Doing this will remove the domestic GSM carrier lock on the Sprint Photon running 2.3.5 OTA. This process will most likely break your ability to return to Sprint service, so please DO NOT DO THIS if you want to keep your Photon running on Sprint. There are ways to fix this, but none have been tested on 2.3.5 OTA devices. As far as I know, this method has been confirmed to work on three phones (including mine), so consider this experimental and high risk. I am not responsible for bricked phones, warranty issues, cats chasing dogs or hot snow falling up if you try this.
Things You Need:
1.Windows PC (tested on Win 8) with the following software installed:
-Motorola USB Drivers [Download]-RSD Lite [Download]-ADB Tools/Android SDK [Download] (Not really necessary, but helpful if you have USB issues.)2. Micro USB cable and wall charger (needed for bootstrap recovery)
3. Standard (full size) SIM card for US GSM network. (ATT/T-Mobile/Straight Talk)
4. Micro SD card (not necessary, but good just in case)
5. Motorola Photon running 2.3.5 OTA ONLY
Files You Need:
1.Full US Cellular Electrify SBF [Download]
-1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.sbf2. Unbrick SBF [Download]
- 2.3.5_45.4.13ota_unbrick.sbf3. Electrify/Photon (almost) One Click Root [Download]
-su.zip4. Bootstrap Recovery [Download]
-MOTODX2_Bootstrap_signed.apk5. Peetr’s Hybrid Locked 2.3.5 ROM [Dev Thread/Download]
-HybridGBv20locked.zip6. KDDI Radio [Download]
- KDDI_Radio_udate.zip
If any links do not work, most can be found at www.motosunfire.com.
Steps
1. Backup Your Stuff!
2. Shutdown phone and remove SIM/SD card (if applicable)
-Tip: Leave your battery cover off. There’s going to be a lot of battery pulls…3. Open RSD Lite on your computer.
4. Start phone in RSD mode:
-With phone unplugged hold volume-down and power
-It should say fastboot in the top left corner, press volume-down until RSD appears
-Connect phone to computer
-Press volume-up to enter RSD mode5. Select the full US Celluar SBF in RSD lite and press start.
-This process takes a few minutes and will end in an error, this is normal.
-The phone may hang on the dual core screen, if so pull the battery.
-The phone will either do two things:
-Bootloop with the US cellular logo
-Boot normally to home screen-In either case, pull the battery and follow the steps to enter RSD mode again.6. Once you are in RSD mode again, flash the Unbrick SBF
-This should not end in an error, but RSD may say you need to manually reboot your phone, this is normal.
-Once your phone reboots you may experience bootlooping, if so do a factory reset (See below)
-With the phone off pess vol-down + power
-Press vol-down until Android Recovery is shown, press vol-up to enter.
-Press both vol-up + vol-down to see menu.
-In the recovery screen, use the volume buttons to scroll and select factory restore.
-Press power to wipe the phone.
-When complete, reboot phone and you should successfully boot to home.7. Once you have flashed the two SBFs, you should be able to get to the stock US Celluar rom.
8. After everything has loaded, you need to obtain root access. (See below)
-Make sure all USB drivers are installed on your computer.
-Enable USB debugging mode on phone (System>Applications>Development)
-Unzip the su.zip on your computer and open root.bat, the program will take you through the rest.9. Once rooted, place the KDDI zip and Peetr’s ROM on either the internal or external storage.
-This is also a good time to install your SIM card.10. Install the Bootstrap recovery and follow the instructions to boot into recovery.
-Remember: You need to be on AC power to get into Bootstrap recovery.11. In recovery, flash the KDDI zip and then Peetr’s ROM
12. After installing the ROM, flash KDDI again.
-Flash KDDI as many times as you want, it will give an error but will still work.13. Reboot phone and enjoy the GSM radio.:highfive:
-If you bootloop again, just do another factory reset. Peetr’s ROM will still be there.
-You may have to root and install Bootstrap again.
-It never hurts to flash KDDI one more time just to be sure.
See next post for Q&A
Q&A
When You’re Done:
Q: How can I go back to Sprint?
A: The only way that worked for me was by flashing 2.3.5. Photon 4.5.1A-1_SUN-254_13 from this thread. This will take the phone back to mostly stock, but there may be residual radio issues.
Q: What carriers can I use now?
A: Any GSM carrier that uses a standard SIM card. These include:
-ATT (3G)
-T-Mobile (2G/EDGE unless you live in a re-farmed area.)
-Straight Talk (3G w/ATT SIM, 2G w/T-Mobile SIM)
Q: Can I unlock my bootloader now?
A: Nope. This only unlocks the GSM radio.
Q: Can I install a different ROM than Peetr’s hybrid?
A: SIM unlocking has only been confirmed to work on Peetr’s locked hybrid rom.
Q: I’m pissed at Motorola for canceling the ICS upgrade. How can I sleep at night?
A: As of right now (and probably forever) there is no way to install any version of Android higher than 2.3.5 on any Photon with the 2.3.5 OTA. However, Peetr’s ROM can be modified to make it look and function like ICS. Planters76 has made an excellent theme for the hybrid ROM that can be flashed in Bootstrap. It can be found here.
Once you flash that theme there are several applications on the Play Store that replicate the ICS/JB experience. Developer Moblynx offers replacements for the clock, camera and gallery. Mobint Software makes home and lockscreen replacements as well. I’m not affiliated with these developers, but their work is solid. This is as close as were going to get to ICS on 2.3.5.
Q: Which developers contributed to this?
A: halfevildruid, mof9336, peetr_, Noncs, Lightsword1942, Planters76, and many others. If anyone else would like to be mentioned, let me know and I’ll add you in. Without these developers we’d be left out in the cold, so give them some thanks.
Q: Who are you and what are you doing here?
A: I am not a developer myself, so just think of me as the person gathering all of the information and trying to simplify it. I can’t stand planned obsolescence, so the Photon is a sore point for me. I’ve stayed in the shadows before now because I haven’t had a reason to speak up, but the locked down OTA and cancelled ICS update bugged the hell out of me. I was in the first soak test for the 2.3.5 OTA, so I had no warning that Motorola was about to screw me and many others. If I can help anyone else that was locked down eek any more life from their phones, then I’ve done my job.
Q: I’m lost! Can you help?
A: Just reply with your questions and I’ll try my best. Keep in mind that I am not a developer, so there are some questions I may not have an answer to.
Finally, if anyone finds any incorrect information in my post or some other error, please let me know so I can fix it. I’d like to prevent any unnecessary phone damage if possible.
Works great. thanks.
now 3G shows 4 bars instead of 1 earlier.
I had to use libmoto_198_7
peetr's ROM is cool. and I like the keyboard!
great work.
Works, but WIFI shows error
I followed the steps and I have my Sprint Photon working in AT&T. But the issues is, the Wifi shows error and doesnt start at all. is there something that can be fixed. Also, How can I get my Google Play up and running. The market icon in the stock Peeters ROM doesnt seem to work and time and again just goes to a browser Window.
Thanks a lot for compiling the steps here...
The combination of a WiFi and apk error makes me think that the ROM needs to be flashed again. Also try downloading a new copy of the zip in case the first one was corrupted. If that doesn't fix it, there was another zip floating around the dev forums that fixed WiFi and MMS issues on the USC ROMs. The file is USCMMSWIFI.zip, I just don't know exactly where it is. As for Play store issues, look around for a recent copy of vending.apk or a flashable zip version and install it manually.
Sent from my MB855 using xda app-developers app
flashing 2.3.5_45.4.13ota_unbrick.sbf at the end fixes wifi issues.
Thanks portman and makakalo. I will do the same. I found the USCMMSWIFI.zip, but it is not in a SBF fashion. Any steps that I could follow to include this fix would help me. Thanks again and Merry Christmas!!
Reflashing Peetr's ROM didnt help with Wifi
I reflashed Peetr's ROM, but still stuck with WiFi Error...Installed USCMMSWIFI.zip using Bootstrap Receovery Mode and the installation completed. Yet, Wifi Error is persistent and cant use Wifi
If you haven't already done so, do what portman suggested and flash the unbrick sbf again. If that still doesn't fix it the only other thing I can think of is going back to stock and redoing the entire process. You may need the 254_12 radio sbf and libmoto zip as well as the 254_13 modules zip to completely reset. Those files are in the 2.3.5 sv2 unbrick thread in the dev forum.
Sent from my MB855 using xda app-developers app
Dear all
Thanks..Got it working. Realized that there was some issue in the Peetr's zip file downloaded. Went through the process meticulously after redownloading and got my phone working in an amazing manner!! Thanks a lot to all.
regards
Ram
Thanks for putting this together, I am still waiting on my SIM, should be in the mail today.
Just one question on the root method..does it really mater which root method I use?
The last time I rooted this phone I used torpedo direct v1.1
I seem to be stuck in the unbrick sbf??
Manually powered up my phone a couple of times.
Never mind stuck in bootloop...DOH!
Wipe data/cache
Sent from my MB855 using xda app-developers app
Something strange
I was stuck in a bootloop after flashing the Hybrid ROM/kddi and I could not even get to bootstrap soo, I went back to the beginning and after the first SBF step the phone starts normally and my baseband is N_02.29.04P.
Now I have a US cellular phone with a GSM radio:silly:
The phone is not rooted at this time nor did I run the unbrick sbf.
I am tempted to use it like this to see if I can activate it on my carrier...heh why not.
Update:So what does the unbrick do? Do I need to run it?
wifi works now and it did not work before the phone seems fine, still want to root and load bootstrap though.
My carrier cannot activate me until after the holiday, but the phone shows me on the Tmo network.
After flashing the unbrick sbf, my phone is probably bricked as it is now stuck on : Failed to boot 4, starting RSD mode
Any idea how to recover ?
Thanks !
portman said:
Wipe data/cache
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
As many times as I have done this you would think I would remember that, but no.
After wipe data/cache I got the hybrid rom to load and ran fine except I could not get the radio to work??
Tried rebooting several times, reinstalling kddi several times, but no go.
Fortunately I made a backup, so went back to USCell ROM and the radio was back
khatta said:
After flashing the unbrick sbf, my phone is probably bricked as it is now stuck on : Failed to boot 4, starting RSD mode
Any idea how to recover ?
Thanks !
Click to expand...
Click to collapse
The failed to boot 4 means there's a problem with that partition meaning, whether its corrupt or not there, it just won't boot and will relay that if to you.
To recover, I'd imagine that you need to try the steps over after wiping your data/cache but to make sure that the phone boots after flashing a full sbf.
http://forum.xda-developers.com/showthread.php?t=1759997 (This has lots of info on the sbfing you are doing)
Sent from my sunfire using xda premium
you need to flash anyone of the following using bootstrap recovery
198_7 radio sbf ----- 198_7 libmoto_ril.so
254_12 radio sbf ----- 254_12 libmoto_ril.so
(thanks to Peetr_)
in my case 198_7 radio sbf ----- 198_7 libmoto_ril.so did the trick even when my phone had a locked bootloader.
after this flash KDDI radio
DXM31 said:
As many times as I have done this you would think I would remember that, but no.
After wipe data/cache I got the hybrid rom to load and ran fine except I could not get the radio to work??
Tried rebooting several times, reinstalling kddi several times, but no go.
Fortunately I made a backup, so went back to USCell ROM and the radio was back
Click to expand...
Click to collapse
portman said:
you need to flash anyone of the following using bootstrap recovery
198_7 radio sbf ----- 198_7 libmoto_ril.so
254_12 radio sbf ----- 254_12 libmoto_ril.so
(thanks to Peetr_)
in my case 198_7 radio sbf ----- 198_7 libmoto_ril.so did the trick even when my phone had a locked bootloader.
after this flash KDDI radio
Click to expand...
Click to collapse
I flashed the 254 before and it was a no go for the radio.
I just did a backup and just to be clear on what I need to do:
wipe data/cache/dalvik
flash hybrid ROM
flash 198_7
flash 254_12
flash radio
and I should be golden, correct?
thanks
as a side note:
the phone is currently working great with the usc rom except the network shows T-Mobil the 'e' gets loped off and I have not actually activated the phone yet because my carrier was closed yesterday(wonder why) they said after Wednesday I should get an email.
DXM31 said:
As a side note:
the phone is currently working great with the usc rom except the network shows T-Mobil the 'e' gets loped off and I have not actually activated the phone yet because my carrier was closed yesterday(wonder why) they said after Wednesday I should get an email.
Click to expand...
Click to collapse
Thank God, I thought I was the only one with the T-mobil issue. It happens on every ROM. I noticed if I dial *#*#4636#*#* and go to phone info, it sticks the e on the end for a little while but other than that, I randomly have it.