ive never been able to get 1.8.3 to flash from either of my pcs, or any os in vmware. it either wont start, or has errors. 1.2.6 on the other hand, has never given me a problem. I would advise avoiding 1.8.3 entirely.
[WARNING] Don't Hard Brick Your Atrix! Look Here.
- Thread starter kennethpenn
- Start date
-
- Tags
- tag2
Tried to install the OP'er version of GingerAtrix and did not have any luck so went to 1.8.3 and tossed in the 4.5.91 and so far ok.
Going to do pudding and root and stick with that for a while until we figure it all out.
Going to do pudding and root and stick with that for a while until we figure it all out.
It may only be an issue with 1.8.3 because pudding sbf flashes fine..? Hoping 1.2.6 proves to be our way back.
i just bricked my atrix like that to bad i didnt see this post few mins earlier. i want to return it and i had an error saying there is no OS on it at all so will at&t change it with no issues? also what should i tell them how it happend?
Tell them you had a update available and your phone rebooted during the process.
That's what I would say.
Sent from my MB860 using XDA Premium App
tell them you were part of the soak test and that when downloading the update something went wrong.
ill just tell them i tried to clean my atrix because it was laggy by doing full restore and something went wrong
reverting back thanks to samcripp
http://forum.xda-developers.com/showpost.php?p=15478397&postcount=129
http://forum.xda-developers.com/showpost.php?p=15478397&postcount=129
restored via cwm to an older backup i had 2.3.4->1.8.3. now touch screen is all messed up =P did a pds restore and it did nothing LOL =/
any fix for backward touch?
any fix for backward touch?
did you try to manually move the pds back? if not try that, if that has no effect you may need to try to do samcripp's revert method then maybe flash back to the 126. the flashing part i would hold off on for a bit tho, until alltheway can test this.
looks like a couple users with the same error were able to recover by leaving the battery out for an extended period of time. Some folks are testing in IRC now.
will post more results
not really sure why this would work but I've seen two people do it now!
will post more results
not really sure why this would work but I've seen two people do it now!
backed up using cwm =/
it just doesn't help it seems. i'm going to try to just restore to 2.3.4 using that backup now.
for now i'd say that 2.3.4->1.8.3 even cwm is no go or at least not for me =P
1
edit: restored from my 1.8.3 restore back to my 2.3.4 restore. all is back to normal. so i guess my backup was bad. =/
Last edited:
anyone had issue with 2.3.3 (4.5.40) -> 1.83 sbf (no cwm)? I flashed a few time between 2.3.3 and 1.83 without any issue.
I left my battery out for a whole day, but no dice.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone