or even relocking the bootloader ?
my atrix is on stock 2.3.4
rooted i guess
career unlocked by unlock code
Well I have had a strange month with my Atrix. The story goes like this. First I was trying to get back to Stock. I had dropped my Atrix and the screen was not calibrating in the top inch of the screen. At the time I was on the Jokersax ICS CM9 KANG. I had hopes that a quick flash back to stock would allow me to fix the issue since I was reading reports about touch issues.
Instead I hard bricked my phone. Luckily I was 2 days before my warranty ran out and I got the call in time to get my replacement sent out. So I got my new (Refurbished) Atrix in with the 141 update. Needless to say I wasnt happy.
So first I tried to unlock it, but naturally all my means didnt work. I tried to see if I could unlock the bootloader which lead me to the dreaded:
Failed to boot 0X1000
I thought it was done for. But I got it fixed with this:
Option #3 fixed the issue, unlocked my bootloader and got the phone booted back to Android. It was still unrooted, but the simple fact was it was working again. From there I installed CWM and flashed a new ROM as quickly as I could and have my Atrix back up and running.
Not sure if it will help anyone else out there. But this tool worked for me to get my phone away from the dreaded Failed to Boot.
I went through this update fiasco with two different Atrixs, One unlocked, one locked.
I could not get the OTA update to work no matter how "back to stock" I was.
I kept receiving Failed to Boot 2 errors and could only solve them using RSDlite.
I also received a Failed to Boot 1 when using the auto-update tool and RSDlite again was the only solution.
Each time I used the pre-unlocked 4.5.91 sbf to fix.
After returning that device, for unrelated issues, I got a brand new, locked, device.
I applied the OTA update before unlocking.
Then I flashed pudding.sbf and got:
SVF message: 105:1:2
Failed to Boot 0x1000
I thought I was done for.
But after trying many different button combos I was somehow able to get to fastboot.
I think it was holding vol up and power while inserting the battery that got me into fastboot.
From there I tried to flash different 4.5.91 partitions starting with boot but it kept failing.
So, I proceeded to finish the unlock by, fastboot oem unlock.
That got me into a bootloop and I was able to reboot into fastboot the normal way where I then installed the stock 4.5.91 system and boot images.
I was then able to boot into 4.5.91.
If you get to this point I recommend waiting for a fruitcake or trying out NottachTrix.
It was a real pain to get the update flashed and booting, more trouble than it's worth unless you plan on ripping it apart. I believe it's because there were apk patches opposed to full apks. Also boot patches that I think checked for an unlocked bootloader. But I'm not sure about that.
I hope this helps anybody who may find themselves in a similar situation.
|4.5.141 ota, 4.5.141 sbf, hardbrick, possible fix, warning|
|Thread Tools||Search this Thread|