i got my Atrix yesterday and immediately ota updated to 2.3.4, unlocked, fastboot "flashed?" my recovery with cwm, and installed alien. i winged it. thank god i'm not bricked. i had to use fastboot to flash my recovery twice, but since then i've been trying to get UOT to cook something that actually works and cwm seems stable now.
the question is, if i flash a rom based on 1.8.3 will that brick my device? or does the brick only happen if you go back to an unlocked rom? hmm..
anyway, thanks for all the hard work devs! keep it coming =D
edit: i did actually unlock first then update.
you will hard brick your phone if you go back to 1.8.3 after installing the OTA 2.3.4
why do you want to go back to 1.8.3?
i don't! i'm worried about flashing a custom rom based on 1.8.3 by accident not knowing that's what its based on
aaron.a said:
i don't! i'm worried about flashing a custom rom based on 1.8.3 by accident not knowing that's what its based on
Click to expand...
Click to collapse
Right now, most roms are flashed via CWM, which shouldnt touch your bootloader. The bricking occures because the official SBF files include an older bootloader which is now seen as an invalid version thanks to the burnt fuse. I dont want to say its impossible, but your not likely to hard brick through CWM. Just dont ever touch RSD/SBFs again and you should be set.
Not to mention, most of the Froyo based roms were made for the old CWM and probably dont work right on the unlocked version of CWM.
If you do decide to go back to Froyo for whatever reason, look for the fruitcake thread. That has CWM flashable firmwares without bootloaders in them, so there's no chance of a hard brick compared to SBFs.
Nevermind mispost
that's basically what i wanted to know. cheers!
Hey guys quick question.
I am on Kennenths 4.5 beta of gingerblur using r1 of Faux's kernel. Recently I have been experiencing screen problems like it's not getting enough power so I want to flash back to complete stock 2.2.
I have an unlocked bootloader as well.
So to do this. Can I use RSD Lite and the 1.8.3 sbf and just flash that? Or is there a seperate way. I am not on the OTA update of 2.3.4
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1190502
There is a sbf there that WILL NOT BRICK you if you flash via RSD Lite. It just flashes you back to Stock GB like it just came right OOB. I softbricked yesterday trying to manually deodex and I flashed that sbf back to stock GB.
Prior flash I was rooted, BL unlocked and running faux's kernel. After I flashed it which took a while, it went back to stock GB where I then had to reroot, unlock the BL and install the kernel again for OCing.
This is the ONLY sbf without pudding that is official from MOTO that will not brick you when you flash via RSD.
I'm not on gingerbread nor do I want to be. I want to go back to stock 2.2
Tejh said:
I'm not on gingerbread nor do I want to be. I want to go back to stock 2.2
Click to expand...
Click to collapse
just use fruitcake...it's much safer then RSD...it's flashable via CWM...download that file from here
http://forum.xda-developers.com/showthread.php?t=1163009
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
its been said before that once you're unlocked, you're always unlocked. Flash a fruitcake for a stock setting.
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
xploited said:
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
Click to expand...
Click to collapse
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Pizzaapu said:
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Click to expand...
Click to collapse
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
Lol hes returning back to Moto anyways ha ha! I'll try it out, I fastbooted to Gingerbread (via Kenn) So I never did the OTA.... so I guess I am safe.
Per this post, you can tell if you've flashed OTA 2.3.4. If it has been flashed already, then DO NOT downgrade to a official 2.2.2 build.
mysticdrew said:
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
Click to expand...
Click to collapse
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Sass86 said:
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Click to expand...
Click to collapse
Yeah but doesn't using the pudding 2.3.4 (4.5.91) still makes you have the "Unlocked" thing on the boot setting? which is what the OP wants to avoid so if he takes it to like AT&T if they see it and see Unlocked they will void the warranty, I am pretty sure the retail story wont extract his phone to see if the fuse it sparked and unlocked.
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
I am not sure about the sbf, but I can tell you for sure fruitcake will not get rid of the unlock logo, flashing a fruitcake is only a stock ROM.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
No. Only if you haven't upgraded via ota update. If you did, then there is no way of removing "unlocked" yet.
My overclocked alien atrix
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Just a thought... did you ever back up your PDS partition?
Touchscreen issues sometimes are due to pds issues. If you have made a backup, wouldn't be a bad idea to try restoring it to see if that fixes your issue.
If you didn't back it up, take a look at this thread with a pds file that helped others.
http://forum.xda-developers.com/showthread.php?t=1131649
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
Probably a long shot but, I used to have very similar issues with other phones in the past when I've had a screen protector on for awhile and it gets scratched up. Maybe try remove the screen protector if there is one and see what happens.
If it is going back for repair. why not intentionally hard brick it? The first thing they will do is the full blown factory flash, erasing all evidence.
If you do this, make certain you give them a story that somehow describes both the actual problem and the bricked condition (else they might think the un-bricking fixed it and not catch the other issue.
EDIT: Maybe not all evidence, the fuse that was blown when you unlocked a 2.3.4 might be a real hardware type fuse and never be cleared. Don't know.
My device is doing this exact same thing and I'm in the same position you are in. I never backed up the PDS partition, but a backup using the image in the linked thread did not solve the problem. Nor did flashing multiple new ROMs.
I'm not sure if this is a hardware or software problem. It problem seems to go away if you lock the screen a few times, but then later reapers.
Sorry to hijack this thread, but does anyone know if replacing the digitizer will fix this problem? Since I'm in New Zealand this would be an economic solution as shipping to and from the US is pricey.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Pizzaapu said:
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Click to expand...
Click to collapse
I just saw this. I ended up using the stock 2.3.4 sbf, and then doing a factory reset in the privacy menu. Now has all the stock info in the "about phone" section. I'll let you all know how it goes. Thanks for the suggestions.
Just got back from AT&T! they said it was a software issue! They gave me the warranty and gave me a refurbished Atrix with 1.8.3, stock froyo on it! I'll stay OTA until CM7 comes out of pre-beta then see how to root it after OTA : )
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...
Hi,
I've got a .DE Atrix, updated via MSU to 2.3.4
The update operation failed two times and I've got an half updated phone.
Then I've successfull updated the phone on the third time.
I don't know if all the failed attemps could have created a corrupted firmware (the atrix works well but it seem a little "sluiggish), so I've thinked to reflash the 2.3.4 sbf .DE to my phone via RSD. What do you think?
Hello,
I think it's hard to made a "corrupted firmware" with SBF...
What do you mean by "sluggish" ? Fluidity, data connexion speed...?
Where did you want to use this Atrix ?
There (http://forum.xda-developers.com/showthread.php?t=1125944) you can found all what you need.
Come back if you need !
Regards.
The GUI is not fluid as expected, the phone is really fast but it lag sometimes.
I've write "corrupted" because, on the first failed flash, the atrix rebooted with 2.3.4 os but with the old radio, for example.
Anyway, I've the SBF for my Phone (the 2.3.4 .DE Retail from the link you give me), do you think I could encounter issue if I'll flash it with RSD?
Ty a lot!
There wont be an issue if the. Sbf is for your model. And DON'T flash back to a previous version of android or you'll hard brick.
Sent from my MB860 using Tapatalk
I got It!
I'll try and I'll tell you the result!