I JUST undated to 2.3.4, from 1.8.3 on gingerblur there were no problems. Then I tried to unlock using the unlocker SBF on this thread: http://forum.xda-developers.com/showthread.php?t=1136261
Flashing the SBF failed, and now I am receiving this error from RSD lite. failed flashing process. Unable to retrieve interface handle (ox7027) phone is connected
When I put my battery in the phone fails to boot and goes to RSD mode, but I still cant flash anything to it. I have tried a few SBF files from the above metioned thread, but they all fail, with the same error message. Does anybody have any ideas for me?
Warning!
Don't try to flash any more SBF files because flashing to a lower build than 2.3.4 will hardbrick your device...as in for good!
Instead, try unlocking your bootloader, flashing over Tenfar's recovery, and then installing an atrix gingerbread stock image. It's your best bet.
fixed
Thanks, though you did not give specifics, I got it working. I guess I was just too tired at 2 am
hello, same thing happened to me, could you solve?
Should have went to stock 1.8.3 before updating. You updated over a deodexed file system, thus it screwed things up. Did you Ota update or flash a fruitcake. If you ota updated to 234 you can never use rsd again. Pudding is the only thing that can be used with rsd. If you unlocked then delete rsd.
Sent from my MB860 using XDA App
Related
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.
Has anyone done this? i bricked my phone in this process. it fails while flashing at the BP pass through stage and asks for some driver which i dont have and while switching phone it writes modem did not power up switching to rsd mode.
Try RSD to 1.2.6 first then after that try sbf 1.5.7 or 1.8.3
Sent from my Over Clocked Rooted Debloated Gingerblured4.5 ATRIX4g
I RDS'd straight to 1.8.3 the first time I tried out the rom, before all the fixes and whatnot.
amrutpritam said:
Has anyone done this? i bricked my phone in this process. it fails while flashing at the BP pass through stage and asks for some driver which i dont have and while switching phone it writes modem did not power up switching to rsd mode.
Click to expand...
Click to collapse
I had the same issue, scared the crap out of me. I flashed second time, artist again. Third time sbf flash worked. Don't know why, but taking out external sd card and sim card helped.
Sent from my MB860 using XDA Premium App
I did it twice. flashed 1.83 thru RSD lite then unlocked the bootloader and used gingerbreak to root.
I used the full SBF of 1.57 so I could use the OC kernel and I didn't have any issues.
I just did last night. Just reboot into RSD mode, flash the full (not service) 1.8.3 SBF, boot and sign into Motoblur (Probably not needed but its what I did), reboot back into RSD, flash the pudding SBF, reboot into fastboot and flash CWM. No issues.
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 tried to reload the stock 4.5.141 image using the instructions in post 4 of the Solutions to Common Problems thread.
I erased cache, erased userdata, flashed boot and flashed system, and all the messages looked OK. On reboot I got the dreaded message. I can't get back to fastboot.
I have downloaded RSD Lite 6.1.4 and it sees the phone, so I hope it's possible to get something on the phone.
What now?
kjmck said:
I tried to reload the stock 4.5.141 image using the instructions in post 4 of the Solutions to Common Problems thread.
I erased cache, erased userdata, flashed boot and flashed system, and all the messages looked OK. On reboot I got the dreaded message. I can't get back to fastboot.
I have downloaded RSD Lite 6.1.4 and it sees the phone, so I hope it's possible to get something on the phone.
What now?
Click to expand...
Click to collapse
C
Download 4.5.141 sbf use rsd lite..rsd always fixed mine bricked many times.if u was on 234 must lock boot loader use 234 sbf rsd.then go up.to 236
markwoo said:
C
Download 4.5.141 sbf use rsd lite..rsd always fixed mine bricked many times.if u was on 234 must lock boot loader use 234 sbf rsd.then go up.to 236
Click to expand...
Click to collapse
Thank you. I kept looking after I posted, but all the links to .sbf from this forum were dead. I was on Android 2.3.6, build 4.5.141.
The only .sbf I could find was entitled "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf".
Now I need to find someplace to charge the battery to attempt the re-flash. Screwing up the previous flash also killed the battery.
I understand that if I'm "Starting RSD mode" the only thing I can do to get a working phone is flash a .sbf using RSD Lite.
Is that true?
kjmck said:
Thank you. I kept looking after I posted, but all the links to .sbf from this forum were dead.
Click to expand...
Click to collapse
All SBF files have been removed from XDA because they are too dangerous.
ravilov said:
All SBF files have been removed from XDA because they are too dangerous.
Click to expand...
Click to collapse
Can you recommend a "safe" alternative for me?
kjmck said:
Can you recommend a "safe" alternative for me?
Click to expand...
Click to collapse
Did you go through this thread? There's a common solution to the "failed to boot" problem.
That said, there are times when you just have to use a SBF and there is no alternative. However, since dealing with SBFs is potentially dangerous, no one around here with experience will ever recommend you that, nor will they give you support. It's just too much responsibility. Kinda sad to say, but if that is really the case (that there is no other way but SBF), you're pretty much on your own.
It's worse now.
I went back to the linked thread, downloaded Automatic Bootloader Unlock 4.2 and fired it up.
Option 3 only works for people who can get to fastboot. That's not me.
I looked at the bold note below about flashing the 4.5.91 sbf using RSD Lite 5.3.1. So I uninstalled RSD Lite 6.x and installed RSD Lite 5.3.1. When I tried to flash 4.5.91 it got to the end and gave a message "Internal error programming phone".
Now I still see "Failed to boot 4" (NOT 0x1000) and "Starting RSD mode", but now RSD doesn't see the phone.
Am I REALLY SCREWED now?
It's better now.
I tried nottach's way of getting fastboot: hold power and volume-up while inserting the battery.
Once I had fastboot I tried again flashing 2.3.6, with the same result.
I still had fastboot, so I tried to flash recovery using Autounlock 4.2. It failed with
Code:
erasing 'recovery' ... FAILED (status read failed (too many links))
sending 'recovery' ... OK
writing 'recovery' ... FAILED (status read failed (too many links))
My phone came newly-refurbished from Motorola, with 2.3.6 build 4.5.141. I had rooted (but not unlocked) my previous phone and backed up everything with Titanium Backup. I had rooted and restored everything to the new phone, but the system would not allow me to register fingerprints and would not perform a factory reset. So I had tried to flash a fresh system; that's how I got to "Failed to boot 4".
I may still be able to return this phone to Best Buy on the grounds that it would not do fingerprints or resets, so I am reluctant to try unlocking the BL unless I'm reasonably sure it will work, but if I can get to a working system I could at least use the phone.
I have a working Eclipse environment on my laptop. Might this be a way to re-format the partitions on the phone so I can flash recovery, boot and a system?
I reviewed more carefully posts 2 & 4 in the Solutions to Common Problems thread, and realized I had slightly different command files (no fastboot.exe, just moto-fastboot.exe). I downloaded the one specified in the post, and tried to flash AT&TGB234_boot.img and AT&TGB234_system.img (I renamed them to boot.img and system.img).
When I rebooted this time I got
Code:
SVF:108:2
Failed to boot 3
Starting RSD mode
I'm still looking for a way to a working phone.
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
ravilov said:
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
Click to expand...
Click to collapse
SORRY for ur problem i know they say sbf are not safe but me i never had 1 single issue using it mine said the same thing and went failed to boot fastboot all i did was plug the phone into rsd used the 236.sbf you mentioned early and restored it back never failed me used rsd over 100 times with 5 different atrixes never had a single issue i can recall...i had to cut a usb cable tape red wire to + and black to - on the battery my phone was in fastboot that was all had to work with but it ran rsd fixed it i have seen failed to boot a few times using rom manager to install recovery before if u can get the sbf u talked about its worth trying i have it but dont know how to share it with u. mine was under warrranty i told AT&T i got the over the air 236 update and it said failed to boot they called motorola moto said give that man a new phone i didnt however share the fact the bootloader was unlocked and rooted and had tried many diffrent roms on it over a period of time but however i did end up fixing it and sent the replacment back.if u are usa att not sure about internation the sbf u mentioned is the 1 i use....not sure what u was trying to do that got u into this the sbf pudding mentioned is safe and have used it in the 234 days but to me since 236 has come out rsd never seemed to me to be an issue..mine is 4.5.151 now they say u cant go back haven't tryed that..lol but i dont use the phone now got me htc one x+ now.hope u fix ur phone man....
ravilov said:
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
Click to expand...
Click to collapse
THANK YOU!
I knew I had seen "pudding" before, and I found it in the Automatic Unlock 4.2 folder. I had tried doing this from the menu, but it failed. I opened Main.bat and found the SDL command line to flash pudding, and when I did it from the command line it worked!
Installing 4.5.141 from fastboot failed, so I tried to flash recovery but that failed too.
I went back to Automatic Unlock. Unlock completed successfully, but the follow-ons did not. I should have made notes as I went.
I was able to boot the phone into 4.5.141, and installed SuperUser.apk, SetCPU and Titanium Backup * Root. SetCPU runs, so I'm both unlocked and rooted.
If I hadn't seen your message I'd have taken the phone to Best Buy today. Your suggestion was the key. I have my phone back, and you have my thanks.