yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Android Development] quejo:
Mine has a locked bootloader and bricked after flashing 1.8.3 over 2.3.4 OTA.
[Atrix 4G Android Development] eval-:
This is a well-known fact that all users of AT&T gingerbread (via official OTAs) will brick on downgrade to Froyo. Only Pudding (AT&T 4.5.47 unreleased 2.3.3 bootloader) or Pudding inserted into 1.8.3 .sbf is safe. Flashing anything else will hard brick. The hypothetical reason is described in the first post, you can read our understanding of ReservedOdm[1] there. It does not matter whether your bootloader is unlocked. Same may be true for users like cctv35 as perhaps china phones and bootloader are different than hong kong and korean models, basically chinese bootloader

may

be able to brick all international phones the way any Froyo .sbf or bootloader will brick any AT&T user who downgrades.

BUT WE NEED MORE

/sys/firmware/fuse/ReservedOdm from Chinese, Hong Kong and Korean users (models MT870, ME860, MB861) before we understand!

We think we understand why AT&T users brick and you all have been warned many times already about it. Motorola made this very explicit in their e-mail to AT&T SOAK users:

*** Once you update to the latest Atrix 4G release, do not downgrade to a previous version or you will likely break your phone.

Lastly, this upgrade will make some changes*** to your phone that will not allow the phone to be flashed back to previous versions. If you typically do that sort of thing, we wanted to let you know in advance.

It is also stickied in the Atrix 4G Android Development forum:

[WARNING] Hard Brick with Official 4.5.91 Update
[Atrix 4G Android Development] quejo:
Do you think that we will be able to unbrick it?
[Atrix 4G Android Development] eval-:
I do not want to say 'never' but I can say 'not so soon.' If I were you I would not hold onto it, or wait to replace it. Some Acer and Asus devices have found their SBKs. We are a long way off. And it is very possible we will never get it. If you have arm asm or any disassembly/IDA skills or speak mandarin and are very systems savvy, PM.
[Atrix 4G Android Development] bl0wf1sh:
So it seems nobody has managed to connect to a hard-bricked device yet, even using factory cable? (Good thing I haven't ordered one yet.)

I could imagine that to connect to a hard brick, one would need a special device driver and/or a special software that writes raw to the usb port. I would think, looking at the random reboot above, that with the right signal sent from the PC (via raw usb?), it should be possible to get access to it.

My device is with Moto Service now, will see if they can fix it. If not, then really I would not hold much hope.
[Atrix 4G Android Development] quejo:
So lets give some chance to moto service. I would do the same if they fix yours. theres still some hope
[Atrix 4G Android Development] t0dbld:
Guy's a little reading of the forum you are posting in would help you a lot!! Motorola will have no problems fixing your phone from this because Motorola has the SBK, you do not that is why there is no fix :-)
[Atrix 4G Android Development] bl0wf1sh:
A little reading of your own would help, too. Sbfs we have. They fix soft bricks only. we cannot even get access to the the phone in a way that would allow us to flash one.

Edit: sorry for mixing up sbf and sbk. But nevertheless, even if we had an sbk, I'm still not sure we can unbrick it, seeing as we cannot get the phone recognized on the pc.
[Atrix 4G Android Development] eval-:
If this thread becomes a flame war it gets closed. t0dbld is talking about the SBK and not SB

F

s. He is quite right that Moto can probably pull most devices out of nvflash (0x1000 error leads to nvflash mode) mode and flash a good system because they have our Secure Boot Key for every device. This is what he suggests you read up on. Getting our SBK is what un-bricking the 0x1000 people depends on. Chances are slim we will figure ours out. Even if it was a straightforward manipulation of the device UID like on A500, (you can use fastboot menu, holding volume down to find yours) --how are you going to get the UID out of a bricked device?

People seeing 0x1000 shouldn't wait to return their phones

. Unless they see the full menu like here and then they (AT&T users only, so far) can go to fastboot mode and 'fastboot oem unlock' their way out, or they could RSD flash 4.5.91 from here (if they want to stay locked.)
[Atrix 4G Android Development] aggielover:
I had 0x1000 but was able to recover from it. I tried to flash pudding from the OTA update and the phone rebooted to 0x1000. I ne zomg-lite.sbf and it said failed but I was able to unlock my BL. I then downloaded the new pudding (2.3.4) and flashed that and BOOM! Phone booted normally. Hope this helps someone else, cause I got lucky!
[Atrix 4G Android Development] anupash:
You flashed the 2.3.4 sbf for unlocked users from edgan or used Kenneth's method for flashing 2.3.4
[Atrix 4G Android Development] aggielover:
The new one for unlocked users
[Atrix 4G Android Development] hvelo:
This is from Hong Kong Atrix ME860, unlocked BL with IHOP_Bell. I wish it helps.

# cat /sys/firmware/fuse/ReservedOdm

cat /sys/firmware/fuse/ReservedOdm

20002000200004000
[Atrix 4G Android Development] bl0wf1sh:
Just to add to this, everyone - I have an update from Moto Service. They seemed to have deemed it under warranty.

However, according to a call I just had with a Moto Service Guy, they did not repair the phone, but sent me a replacement unit instead. Will try to confirm this when I get the unit, as the IMEI and ESN should be different in that case.

I guess that spells bad news for people trying to fix such a hard brick, if even Moto Service gives up.

*EDIT* confirmed that I am getting a replacement unit. The ESN is different.
[Atrix 4G Android Development] aj009:
I had 0x1000 but was able to recover from it. :(:(:(
[Atrix 4G Android Development] jrmccracken:
My atrix went to 0x1000 while upgrading bootloader with pudding
[Atrix 4G Android Development] jrmccracken:
how did you do it?
[Atrix 4G Android Development] BravoMotorola:
I was putting CM7 on a friends Atrix yesterday and he had upgraded to ATT 2.3.4 already. When I flashed the unlock sbf it displayed that error and it freaked me out at first but it had the options. When I rebooted to do the fastboot commands it just showed the failed to boot 0x1000 error for like 3 whole seconds before the options finally showed up. It scared the piss out of me.
[Atrix 4G Android Development] p0xer:
replacement unit doesnt say moto gave up nor say that moto tried.. we have no idea for now.

I'm sure if an atrix engineer will look into this, a way will be found to overcome it. maybe by writing the whole system to the emmc using a JTAG interface & "defusing" or something else..

I'm no engineer but we most keep our thought positive.. if we'll look behind for a second.. in 4 months we've very got far with our knowledge about the device and im sure that 4 months from now, things will be even brighter ;)

:)
[Atrix 4G Android Development] barry99705:
Yea, a better phone will be available. ;)
[Atrix 4G Android Development] geokhentix:
U.S Atrix here, over from Captivate. Started to unlock the bootloader(via http://xdaforums.com/showthread.php?t=1138204), and after the first .sbf flash, it showed the dreaded 0x1000 error.

This was after updating fresh to 2.3.4 OTA. All I had to do to get out of this error is connect the phone to USB, put the phone into fastboot, and use fastboot via cmd windows side, with the following;

- fastboot oem unlock ([i]will spit out a long character sequence, used for the next command[/i])
- fastboot oem unlock [#####'s that you observed from above]
example; fastboot oem unlock 009139a948841ab0

This probably has been mentioned before. At least I hope it has. Successfully rooted and installed CWM with no problems whatsoever after recovering from a 0x1000.

I think in most scenarios, you should be able to recover from the 0x1000 "Hard" brick, as long as you don't try to .sbf out of it first.
[Atrix 4G Android Development] velvetmxo:
I am not sure if i follow but what does mine mean? I'm rooted but not unlocked i went the .zip method of the beta to get 2.3.4. (i don't have the ken beta version)

10000000000010001000300000000
[Atrix 4G Android Development] velvetmxo:
I am not sure if i follow but what does mine mean? I'm rooted but not unlocked i went the .zip method of the beta to get 2.3.4.

10000000000010001000300000000
[Atrix 4G Android Development] bl0wf1sh:
Ok can everyone who does NOT have a hard brick (e.g., the soft brick resulting in the normal course of events when using pudding) refrain from posting in this thread? This is for real, actual hard bricks where there is so far no way to fix it.

And, to add to my own moto repair return: they sent me a SIM-locked phone, so going to be without Atrix for another few days until I get the unlock code from cellunlock.net ... I know it is their fault, but the repair center online chat guy could not help me, no matter how hard I tried. Only recourse would be to call the Repair Escalation Team at 1-800-734-5870 during Mon-Fri 9am-7pm (Eastern Time). Not gonna wait for that.
[Atrix 4G Android Development] geokhentix:
Soft brick, hard brick, anyone who sees it for any reason is going to come to this thread because of 0x1000. Maybe this should be highlighted among the wall of text that is the OP, that it does occur naturally while using pudding. That way someone doesn't have to look like a fool of a took.
[Atrix 4G Android Development] eurosport360:
PLEASE HELP ME

I just go the phone yesterday.

I updated OTA to 4.5.91, and then used RSD 5.3.1 to unlock the bootloader using

ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares (Pudding).

I then get the error

SVF: 105:1:2

Failed to boot 0x1000

No OS detected, going to RSD mode in 5 seconds

The gives a list of avaiable modes.

Starting Fastboot protocol support

I thought I followed all the directions. I updated my phone to the official gingerbread update, and installed the Window 7 drivers and latest RSD.

What did I do wrong? How can I fix this?
[Atrix 4G Android Development] mramirezusa:
Just choose fastboot mode from the menu navigate with vol up and vol down select with power key

After that follow procedure

Fastboot commands
[Atrix 4G Android Development] eurosport360:
Thanks for the reply,

but after its unlocked and I do fastboot reboot, the phone reboots and is stuck at the dual core technology screen, with the word unlocked on the top left.

Should I pull the battery?

Edit: I pulled the battery anyway because I couldn't do anything. I am charging the phone now and the battery icon shows up...if that means anything.

My problem is that it its stuck at the boot screen in the beginning.
[Atrix 4G Android Development] hoaca388:
My hard brick atrix :
[Atrix 4G Android Development] t0dbld:
^^^ sounds like something you flashed didnt mix and match most likely a kernel, fast boot your self a new boot.img
[Atrix 4G Android Development] NextExile:
To stay on topic, I experienced a hard brick last night after flashing an earlier sbf over gingerbread. Absolutely didn't pay attention.

Some people are saying that moto has been doing this kind of locking and fusing on their devices for a while now. If so, have those barriers on older devices been broken? Consequently, can we learn something from those devices?
[Atrix 4G Android Development] Taguiera:
My experience

Brand new stock 1.8.3 atrix straight from Asurion/AT&T. OTA update to 2.3.4 GB, then tried to unlock, ran into the first x1000 fail to boot, then did the dumbest thing imaginable, the thing I knew I wasn't supposed to do and did anyway, tried flashing back to 1.8.3. Phone locked up, boots, lasts 3 seconds, then shuts off.

Fortunately, i still had the old phone, which I had broken by trying to replace the digitizer and tearing the LCD ribbon cable. I removed the main board from the old phone and put it in the new phone. Turned it on, and, wouldn't you know, it worked just fine. The old phone/new phone hybrid is stock GB with an unlocked BL, rooted and with the PiCrust theme applied. The ReservedOdm code is 10000000000010001000300004000.

Template:

1: Brand new stock 1.8.3 atrix

2: No

3: OTA was OTA from AT&T over wifi

4: Tried to unlock, failed and went into 0x1000 fail to boot

5: No

6: Yes, tried flashing 1.8.3

7: N/A

8: Yes

9: No

10: Bootloop, not able to get into fastboot or RSD menus.

Get 0x1000 and, after about 3 seconds, get the NVFlash thing, i think. Hard to read, it goes by very quickly. Then have to pull the battery in order to try and reboot.
[Atrix 4G Android Development] mlhope:
Hey all, this may be my first time posting on the forum. I'm not computer scientist, but what little I do know of using Linux terminals and some light programming, I learned on my own.

Anyway, I came back from a hard brick about a month ago. I believe I was rooted post-Gingerbread OTA update, and I think I was trying to flash Pudding (it's been a while, and I can't remember.)

I was given the option to still use Fastboot, so I was able to bounce back, install the stock image, for which I have since unlocked the bootloader and eventaully rooted again.

Here's my output:

# cat /sys/firmware/fuse/ReservedOdm

cat /sys/firmware/fuse/ReservedOdm

10001000300004000

Like I was saying, I'm kind of a dummy, so if there are any additional outputs you need give me the lines and I'll run 'em! :)
[Atrix 4G Android Development] bl0wf1sh:
So can I just summarize the new findings in the first post:

- Moto/ATT decided to have a fuse that is burnt on installing a significantly new android version, and serves no apparent purpose except to brick the phone when somebody tries to downgrade.

- If we could flash pudding BL on a hard brick, we could fix it; but since the software chokes on the burnt bit, it is impossible to do anything with it. I.e., the BL refuses to enter a mode that could be helpful

I see only two ways to resolve a hard brick, then:

- Get the MBK in order to be able to enter to "force flash" a different BL

- Trick the BL to think that the fuse is not burnt. Not sure how that can happen, though. I would think it would involve some hardware tinkering... if the fuse can be burnt, would it be physically located somewhere? Would be big enough / outside a processor/ram, so that it can be replaced? Or maybe "just" replace one chip somewhere? Remember, the fix need only be temporary, giving enough time to load a different BL.

That kind of hardware tinkering is way beyond me, but if this is what anyone here wants to do, I recommend iFixit : http://www.ifixit.com/Teardown/Motorola-Atrix-4G-Teardown/4964/2
[Atrix 4G Android Development] ntonhd2:
I had this problem as well as with a "Failed to Boot 2" and "sec exception" (wrong model = ie: Telstra/International vs ATT). Anyway: point is I had the BATTERY TOO LOW.

You can easily get out of this without another battery - if TOO LOW TO FLASH.

All you do is:

Cut up and make a factory cable and connect it as per factory instructs etc...

JUST-nike-it: dont be scared; FACTORY CABLE GOES INTO COMPUTER.

Get another spare usb cable and cut it - leaving the large (not micro/mini) end and plug into a power charger that is OVER 5VOLT (ie 5.1 or 5.2) and OVER 500ma (ie: 700ma or 1000ma/1A) because BATTERIES DO NOT RECHARGE AT EQUAL OR LESS THAN VOLTAGE: ONLY HIGHER: I PERSONALLY USE A SIERRA 5.2V 1A CHARGER TO RECHARGE MY MOUNT OLYMPUS ZEUS. Factory cable goes into computer not charger though. now you need to focus on/with the spare cable - with a flat/low batt (and having factory cable in micro usb- use the other cable (dont get confused: factory cable is for factory - separately - and this goes into usb and into COMPUTER)).

so, digress etc, sorry, now, with the usb in computer (factory) plug the large usb head connector on the OTHER (2nd/CUT) usb cable into CHARGER and then use the RED (+) and BLACK (-) wires:

directly line up RED (+) of charger-usb-cable wire with the side-most-(+) metal terminal of the battery and same for BLACK (-) as per the + and - signs on batt.

I didnt even use tape or anything: I just carefully put the wires over the terminals and held in place about 1cm before I PUSHED THE BATTERY INTO SLOT (IN BACK OF PHONE) SO:

YOU HAVE BATTERY CONNECTED TO PHONE IN PLACE BUT YOU HAVE TWO WIRES GOING DIRECTLY TO CHARGER AS WELL AND THIS LITERALLY CHARGES THE BATTERY (IF CONNECTED TO BATT AND PHONE AND THE PHONE IS ON).

THIS WORKS WITHOUT ANY DAMAGE OR OVERHEATING OR DRAMA BECAUSE OF A SIMPLE RULE IN ELECTRONICS:

EVEN THOUGH THE BATT IS ONLY 3+V IT IS OK: THERE IS REGULATION ON BOARD AND IT IS NOT ENOUGH V+ ANYWAY TO OVERLOAD ANYTHING:

THE SIMPLE RULE IS:

SERIAL=VOLTS.

PARALLEL=AMPS.

IF YOU CAN UNDERSTAND THIS AND KNOW HOW/WHERE/WHY (SITUATIONS) WHERE 12V 1A AND 12V 1A CAN EQUAL 24V AND 1A AND WHERE 12V 1A+12V1A CAN EQUAL 12V-2AMPS THEN YOU WILL GET THIS IS SAFE 100%.

HOLD DOWN VOL UP FOR 30 SECONDS ETC - DO SO ONCE AGAIN PRIOR TO INSERTION OF BATTERY. YOU WANT RSD.

FACTORY CABLE CONNECTED USE RSD-LITE.

IF YOU CAN NOT CONNECTED TAKE FACTORY CABLE OUT AND USE NORMAL USB BUT YOU MUST USE FACTORY CABLE FIRST WHEN (PRIOR TO) CONNECTING BATTERY.

Follow normal factory instructions and then:

FLASH 21/12/2012 00:00 PM 1,532,989,638

OLYEM_U4_1.4.2_SIGNED_USAOLYEMTELSTRA_P029_A020_M005_HWolympus_1g_1FF.sbf

anyway you can thus manually charge your battery! :).

0.) Do factory cable and manual force charge with phone on and RSD etc.

1). Once sbf is done:

2). use sevenpreps.

3). then do IHOP.

4). then do OEM FASTBOOT UNLOCK.

5). UNLOCK.
[Atrix 4G Android Development] ntonhd2:
By the way, Hello to Coutlla if your around my friend:

sorry but family sick - had to travel interstate... You still on LEO?

Thx again for password to and tetris secret ;) - sorry - i mean normal copy of - MAGLDR.
[Atrix 4G Android Development] ntonhd2:
In the end I finally got the MICROSOFT (TRADE SECRET/COPYRIGHT/UNDER-NDA) CONFIDENTIAL OEM WINDOWS OS BUILDER *AND* ACCESS TO ALL CURRENT BUILDS (SERVER AND MOBILE) WINDOWS SOURCECODE (EXCEPT WINDOWS 8 WHICH I DO NOT HAVE EXCEPT LATEST BUILDS AND A UNRELEASED REDPILL).

Welcome down the rabbit hole.

Surely this post will stir up some trouble but those special Russians and Chinese will understand.

So will Julian Assange: this is really a message covertly sent out regarding wikileaks containg an embedded cryptographic key that is the latest version of _NSAKEY - yes - Microsoft are still giving NSA backdoor access but specially for ECHELON to auto logon to every machine in the world: that is the real scam of Windows Activation Technologies.

For now: replace WatAdminSvc.exe (BEFORE YOU DO OOBE) with a copy of a w7lxe.exe loader - via command prompt use shift+f10 and EXPLORER.EXE)...

tHEN RUN ANOTHER EXPLORER.EXE AND RIGHT CLICK WATADMINSVC.EXE AND CHANGE OWNER TO ANONYMOUS-LOGON AND THEN HIDE. ALSO REMOVE *ALL* PERMISSIONS INCLUDING THE SYSTEM. SO NOBODY CAN RUN OR MOVE WATADMINSVC.EXE

then create keys (replace* above = create not REPLACE because its not there yet) under Windows and Windows NT ' current version called exactly as

"Windows Activation Technologies".

once again - TAKE OWNERSHIP INHERIT AND *ALL* EVERY SINGLE ONE *** OWNERS OFF AND CHANGE OWNER TO ANONYMOUS (YOU ARE RUNNING AS s1518 remember so NT AUTHORITY is all good powerful)...

With these keys in place and UNCHANGEABLE - you should get access denied now when you try click on them (even as \SYSTEM):

this means you will not get a UUID/GUID issued to you from Windows Update Servers or genuine.microsoft.com which are all fronts for the NSA ECHELON SYSTEM: this is how we track everything in the world - this is how we run the DARPA TOTAL INFORMATION AWARENESS OFFICE which does exist... within M$ too..

I can say all this BECAUSE people will think I am just a crazy man.

But the proof is this:

ADAM WEISHAUPT registered ILLUMINATI and owns the company name ILLUMINATI in AUSTRALIA and WASHINGTON DC as well as the TRADEMARK = this man = who is he? = ADAM WEISHAUPT = owns ILLUMINATI trademark seriously as well as all ILLUMINATI domain names...

ADAM WEISHAUPT=does anyone know anyone who uses this name NOW - ie: not the guy born in 18th century but an assumed identity name?

Anyway: the proof is this:

ILLUMINATI PROPRIETARY LIMITED

C/- ROBERT STARY LAWYERS

333 QUEEN STREET

MELBOURNE

VICTORIA

3000.

Omega.
[Atrix 4G Android Development] armonwilson888:
LOL what?....
[Atrix 4G Android Development] quejo:
is that the fix for hardbrick?
[Atrix 4G Android Development] daniel0612:
no solutions yet#
[Atrix 4G Android Development] gatorp003@aol.com:
device support center

This is what i did, took the phone to my nearest devices support center and stated that during the unpacking of the new ota update my device randomly rebooted and this is what i am stuck at. They passed it off as devices os failure and exchanged. HOPE THIS HELPS SOME PEOPLE. :D
[Atrix 4G Android Development] tonyneoh:
my device also like this problem,but it just show this . connected to Pc no any function whit detected . also have send to motorola dealer to check it ,they say can't do any more. it is die totally?
[Atrix 4G Android Development] Fighto3:
Flashed zomgunlocker-lite.sbf to atrix running 4.5.91 without root (yes ik stupid) got error "failed to boot 0x1000" and proceeded to freak out. pulled myself together and flashed http://xdaforums.com/showthread.php?t=1181932 sbf file. managed to reboot and after which i tried to unlock my bootloader again, with the pudding unlocker though, which gave me the same error message, which i then flashed the same sbf again and now it works fine... still cant unlock my bootloader though... fml

if i somehow stumbled across a breakthrough feel free to pm me
[Atrix 4G Android Development] Javi97100:
When you get the failed to boot screen, just continue the process ,you are in fastboot, so type the commands
[Atrix 4G Android Development] Ciloteille:
Well I try this, and I get a failed to load (because it could not switch something. so lame, its because im not using factory cable provided with my phone? Im using a quality cable i purchased earlier.

It says.....

Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP pass through mode (0x70BE0); phone connected

im stuck like you on 0x1000... poop
[Atrix 4G Android Development] Ciloteille:
Well I did fix this by...

http://xdaforums.com/showthread.php?t=1182871

Now to flash a newer recovery and flash into CM7. Just like my main handset, now I have 2 atrix phones with CM7, sweet.... :D
[Atrix 4G Android Development] Sparx10:
I was helping a friend of mine unlock his BL today. He had 4.5.91 OTA from AT&T, downloaded correct pudding, flashed with RSDLite, but it failed and he got "0x1000 failed to boot". We aren't sure why, he thinks that it's because he was using a virtualmachine (VM) because he couldn't get his computer to recognize the phone, but the VM did, so he flashed through there. Apparently his computer was beeping, so he thinks that USB communication may have been interrupted and that's why it failed. It then restarted into what it said was RSD mode but was actually in fastboot mode. He was just able to "fastboot oem unlock" and he hasn't had a problem since.
[Atrix 4G Android Development] redtank22:
helpz

i was on 2.3.4, rooted using the one click root, flashed the pudding .rar with RSD lite, and RSD lite said it failed, rebooted and it was bricked with 0x1000. help? thanks. will post more info if needed.
[Atrix 4G Android Development] lovfors:
can you get into fastboot? did you do the fastboot unlock?