yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Android Development] eval-:
Cool, I had no idea it was a false (low battery) alarm. Thanks! Still, hopeless without factory cable and SBK, eh?

Yes, AFAIK the2dcour did this, actually 1.8.3+pudding (2.3.3 BL) is safe, since the 2.3.3 BL lets you have this 'bad' fuse bit burned if you are unlocked..

AFAIK from the reports in this thread they enter Nvflash proper?

Ie, they see "Entering NvFlash Recovery mode"

Not "Entering NvFlash recovery mode / Nv3p Server"

But either way, without the SBK they are cooked... =(

Anyhow this much we already understand, that it is a fuse. The question is how 4.5.91 burns a DIFFERENT fuse, *without* you unlocking even, that breaks downgrade. The 2.3.3 'pudding' everyone flashed did not break downgrades, whether you unlocked or not. Yet 2.3.4 leaves you unable to downgrade (below 2.3.3) whether you unlocked or not. Also, according to these reports, 2.3.3 behaves differently in the face of fuse failures (leaves you with fastboot menu options instead of in nvflash), and ceases to 0x1000 once you unlock. But I think everything is a bit clearer thanks to t0dbld below...

I haven't talked to so many, but I think the2dcour has, AFAIK they are still locked out, if they had factory cable + SBK they might be able to nvflash out...

THANK YOU!! That is a huge clue.

This is how virgin ReservedOdm[3..0] look:

locked:
00000000 00000001 00000001 00000000 (have also seen 10001000100000000)
(2.3.3) unlocked:
00010000 00000001 00010001 00004000
2.3.4 unlocked (yours):
00010000 00000001 00010003 00004000

So ReservedOdm[1] u32 went from:

0000 0000 0000 0001 0000 0000 0000 0001

to:

0000 0000 0000 0011 0000 0000 0000 0001

And this screws with any bootloader 1.8.3 (froyo-2.2.2) or below.

Interestingly, this bit set to 1 also screws 'pudding' 4.5.4? (gb-2.3.3) but instead of dropping you into nvflash, it gives you the same 0x1000 error, but then the full fastboot menu. And IF you unlock, setting ReservedOdm[0] to 0x00004000, then the 2.3.3 bootloader gives you a pass and lets you boot, even though it found an unexpected bit set in ReservedOdm[1]

BUT, to test this theory

I need more people like t0dbld to actually read the first post and follow step 2!!

If you applied 4.5.91 via OTA (copy to /sdcard..) and you still have a working phone, please

root and cat /sys/firmware/fuse/ReservedOdm

!!

For now, assume that seeing a '3' in the 9th position from the rightmost is a bad sign, and that you should never downgrade to any bootloader below 2.3.3! (aka, 'Pudding') Still remains to be determine where/when/why this fuse gets blown from this 4.5.91/2.3.4 OTA if indeed the above assessment is accurate...

PS. What do you guys make of relation between this fuse and the switch between SE and NS (presume NF is typo)? And is there still hope for some means of determining the SBK...
[Atrix 4G Android Development] mramirezusa:
Did you ever flash pudding in 1.83? I know you tried pudding after 2.3.4 but I was wondering before GB Did you tried pudding in 1.83 before
[Atrix 4G Android Development] nsaia:
I am like t0dbld. I was on 183 gingerblur, then flashed pudding and unlocked, flashed the stock 183 sbf, ran the the update.zip to 234 and then flashed pudding again to unlock. Hell, maybe I got lucky. But, right now I'm on 234, rooted and unlocked.

I don't have access to a computer right now. Is there any way I can get the info you want easily via a terminal emulator.
[Atrix 4G Android Development] t0dbld:
I have an unlocked bootloader "AKA PUDDING" so i think this assumption is wrong, have i ever tried flashing back to an older sbf no, why would I? The reason for the bricks are simply 2 things 1. What kholk posted, 2. BP CHANGED this is the problem as to why you cant go back

now as for part about what you see, even though the message is entering nvflash mode, kholk is correct that if its forcing it there it is more than likely going to nv3p no matter what your screen says , he would know better than anyone on this as we bricked his dev atrix worse than this with in a few hours of having it, how ever like he replied to me if you, unlike him (no sbk on dev device) still can not access nvflash or nv3p do to sbk than this is the real problem and this is what needs to be worked on... because this is the only way to recover at this point is using those protocalls
[Atrix 4G Android Development] knigitz:
Just posting my ReservedOdm - a little history first. I was on 1.8.3 with pudding and an unlocked BL. I upgraded to the 2.3.4 OTA through the stock recovery after a stock 1.8.3 .sbf flash.

After the 2.3.4 OTA update, I got pudding again through RSD, then I flashed CWM and preinstall through fastboot. That is where I am now.

# cat /sys/firmware/fuse/ReservedOdm

cat /sys/firmware/fuse/ReservedOdm

10000000000010001000300004000
[Atrix 4G Android Development] t0dbld:
yes do the same instructions from a root prompt in terminal emulator
[Atrix 4G Android Development] stinebd:
Borderline noob in Atrixland, but I can verify results similar to t0dbld...

# cat /sys/firmware/fuse/ReservedOdm
10000000000010001000300004000

This is on ATT Atrix 4G, running the gingerbread OTA update, from a previous 1.8.3 SBF (which was flashed as a downgrade from the testing Gingerbread HKTW image leaked shortly before the OTA).

Hope it helps your investigation... Good luck and thanks for everything.
[Atrix 4G Android Development] nsaia:
Don't know how to copy and paste from terminal emulator, but this is my result as well.
[Atrix 4G Android Development] eval-:
**** man! Long time no see! I <3 xdandroid... was on my Touch Pro2 until quite recently... I figured out the double-tap touchscreen fix on tssc_manager.c (or something) quite by accident, about a year ago, in a fit of procrastinating my thesis. Excited to see you in Atrix land! =) Sorry you made your phone unable to downgrade =( (to official Moto .sbfs) At least you can still flash 'pudding' (2.3.3) BL and then "fastboot flash" to your hearts content.

PS. Plans are floating to replace ubuntu (9.04, jaunty) webtop with gentoo, once we determine how to best preserve libflashplugin.so and other nice functionality like android-in-window, the libpulse<->binder<->audioflinger hack.. I'll catch you on #htc-linux sometime if you're still there
[Atrix 4G Android Development] stinebd:
Yeah I'm not too worried about mine honestly. I can handle fastboot just fine, as long as we keep getting SBFs that I can unpack to get boot and system images.

This sounds cool. If you need any help with the userland side, you know where to find me. ;) Also I've been thinking about working on an olympus device tree for us (I hate hate hate Blur and manufacturer frameworks/launchers in general). XDAndroid's hardware is becoming quite dated. :D

Anyway nice to see you again too and I'll kindly refrain from further derailing the thread. If you need any more info from devices that are still working, I'll gladly help where I can.
[Atrix 4G Android Development] t0dbld:
Some interesting logs i dug up... maybe a place to start working from

07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): Running enc_mgt_tool to setup device encryption for normal power up...
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): setenv(PATH,/system/bin)
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): setenv(LD_LIBRARY_PATH,/system/lib)
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): Setting persist.sys.mot.encrypt.mmc already defined to [0]
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): Cipher choice: aes256
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): key-sig file length will be 80 bytes
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): Not an OMAP device; /system/bin/smoduled is not found.
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): SBK is programmed; will use TPA_AES_KEY_ENTERPRISE
07-12 19:54:54.887: DEBUG/enc_mgt_tool(1367): GroupID temporarily set to mot_tpapi=9007, status=0
07-12 19:54:54.907: DEBUG/enc_mgt_tool(1367): DEVICE_ENCRYPTION_KEY_ID not found! Creating one...
07-12 19:54:54.907: ERROR/enc_mgt_tool(1367): Error: DEVICE_ENCRYPTION_KEY_ID not found and unable to create it.
07-12 19:54:54.907: ERROR/enc_mgt_tool(1367): Error: Unable to set up key and signature, tool is exiting.
07-12 19:54:55.635: DEBUG/(1369): MOTO_PUPD: mot_boot_mode
07-12 19:54:55.635: DEBUG/(1369): MOTO_PUPD: mot_boot_mode : normal
07-12 19:54:56.097: ERROR/logwrapper(1424): executing /system/bin/busybox failed: No such file or directory
[Atrix 4G Android Development] SGTShark:
ReservedOdm 10000000000010001000300004000 for me.

My process was ulocked CWM gingerblured 4.1.83 > sbf 4_1.5.2 > Moto Software Update Tool > Sock 4.1.83 > update.zip > 4.5.91 Rooted and Unlocked. No issues and no errors through the very lengthy process.

Hope it helps! Be nice to have a somewhat stock escape avenue when this gets figured out.
[Atrix 4G Android Development] robonoob:
Would having one of the hardbricked phones help the devs at all? I may be willing to lend mine to a dev if it will help everyone.
[Atrix 4G Android Development] bl0wf1sh:
To pick up a thread from two pages ago...

Yes, I read about the SDK part... but... it seems that for this kind of hard brick, nvflash is the only mode it will enter - I have tried everything (I believe). So for fixing a hard brick, one would either need to use the steps as for ASUS Transformer in principle, or "trick" the nvflash another way into accepting files.

Either way, I am doubtful hard bricks can be fixed without a dev cable. It seems one can trick the device to display the fake LOW BATTERY message by plugging it into the outlet, powering on with volume up, and THEN inserting the battery once the low battery message is displayed. I don't see the device though when I connect to a PC afterwards in device manager, so not sure whether this will actually work.

Also, after reading the thread more, it seems that I need to confess to Moto Service that I had 2.3.4 installed... they would see it anyway due to the blown fuses...
[Atrix 4G Android Development] nate_benji:
Not sure if this can help at all, but this is from a locked bootloader on a Bell atrix.

ReservedOdm: 20002000200000000
[Atrix 4G Android Development] briggie108:
was on 1.8.3. unlocked from there. I reflashed 1.8.3 sbf, then I did the OTA. I then flashed the pudding sbf and have been fine since.

Reserved0dm: 10000000000010001000300004000
[Atrix 4G Android Development] bl0wf1sh:
In way of a short update, and as bad news for all international Atrix users: Moto Service refuses to repair out-of-country devices, as they are not "authorized" to do this. (And don't have the files, it seems US won't share.) So looks like I will have to move to Singapore Atrix (it is out here now), unless we can find a way quickly to unbrick the Atrix.

A few bits of information I got from the repairman though (don't kill the messenger - this is what I got out of him)

- Motorola uses an internal (confidential) software to repair devices that are in this state by flashing an SBF or something similar. He would not tell me the name of the software, though. Not sure whether it can be found through "unofficial" means / channels.

- A normal USB cable should be enough to flash an image, provided one has the right software above (and, well, assuming the keys as well)

- The Atrix's hardware in Asia/Pacific is slightly different from the US one, but consistent across the region (well, except China I guess). The software should also be pretty much the same across Asia/Pacific. (Not sure where Australia belongs to.) Trying to flash a local build on a US Atrix could damage its hardware permanently (!)
[Atrix 4G Android Development] tan G:
Other fuse burned

hi kholk,

according to what you said, probably flashing the 2.3.4 OTA update may have burn another fuse (2,3,4,...).

Or possible, the OTA bootloader did a ckeck to the fuse 1 that was burned before (by flashing the pudding sbf). Bootloader did not recognise it and return 0 value insteed of 1 then put the phone to nvflash rescue mode.

correct me if I'm wrong

cheer *g* tangi ;)

ps: no, I didn't bricked my phone yet
[Atrix 4G Android Development] tan G:
hi,

wait, I don't fully understand, I was able to flash back 1.2.6 sbf after flash the sbf pudding and unlocked the bootloader. I think it's all about the OTA 2.3.4 update...
[Atrix 4G Android Development] fernandoavc:
Hi guys... as I have a different result doing the cat /sys/firmware/fuse/ReservedOdm command I decided to share ... I hope it's ok for you all... I know that the thread is for the ones who came back to life from a brick (what never happened to me thanks god).

First my history: I was born in 1979... just kidding...:

1-)Bought the ATT Atrix version with 1.26 firmware

2-)Updated OTA to 1.57

3-)I've participated into the beta-testers from motorola and was picked to install the OTA 1.83 version but I've changed somethings such rooted/webtop modded and wasnt able to do it OTA so I did a SBF to 1.57 'so-called' official version that someone leaked then I was able to update it to 1.83 OTA (I can find it here in my computer if any of you think necessary to).

4-)Unlocked my bootloader with the sbf procedure (zomgunlock-lite.sbf)

5-)Installed the Gingerbread HKTW through fastboot method (moto-fast to win32).

6-) and finally installed from the Kenneth briefmobile link the gingerbread.zip (beta 4.5) through the CWM with no problems at all...

And finally the numbers I have :

10000000000010001000100004000

Like some of you have the number 3 (tob0ld) instead of the number 1 that I have even with the 2.3.4 - 4.5.91...

I hope it can help somebody.... feel free to ask me further information or help but no downgrade I am scared even to turn off my phone ;)
[Atrix 4G Android Development] narta:
Same here

It seems that the 4.5.91 update.zip that includes a Bootloader is the culprit. The BL of the 4.5.91 update is blowing(?) the fuse so you can't go back to a previous bl. So from now own everyone that flashed or updated to the new bl should stay the hell away from sbf and use fastboot to flash system.img and boot.img until we can have a solution
[Atrix 4G Android Development] knigitz:
Has anyone considered that maybe the new bootloader is not burning a fuse because it's unlocked, but simply because it's a new bootloader? Maybe they really discourage downgrades.

In any case, it seems to be a new function of the new bootloader which makes it not compatible with the old one.
[Atrix 4G Android Development] j_r0dd:
Ding ding ding you hit the nail on the head. Moto does not let you downgrade bootloaders. You can flash sbf's with the same bootloader version. Basically if you flash a new bootloader don't use older sbf's. What's the point in using an sbf after you are unlocked anyways?? To wipe your phone clean?? People just need to use fastboot at that point. This is the same situation from the Cliq days. Downgrading using RSDLite will fail and SOFT brick the device. What did we do?? We waited for the newer sbf to get released and we were able to revive. I don't have a brick but I have one question to ask you "hard bricked" users. Does RSDLite detect your device?
[Atrix 4G Android Development] rickriego:
NO. no it doesnt. No RSD..no Fastboot.
[Atrix 4G Android Development] knigitz:
Different hardware, different results? Ultimately we need to understand that this build (currently) is not meant for public consumption, and could have bugs. This could be an overlooked mishap, or an intended side-effect of this build and maybe even future OTAs.
[Atrix 4G Android Development] GuerillaZhou:
I hope this helps. I started the process on 1.8.3 Rooted and LOCKED. I downloaded the OTA 4.5.91 from the thread and updated through the SD card. RSD(5.3.1) flashed the unlock SBF(Not the international version) that was on the pudding page. The process "failed" and I was greeted with 0x1000, but I still had fastboot and rsd access. After issuing fastboot oem unlock, the phone turned back on.

My fuse is

# export PATH=/data/local/bin:$PATH

#cat /sys/firmware/fuse/ReservedOdm

10000000000010001000300004000
[Atrix 4G Android Development] Spectre51:
Not sure if mine will help but didn't see a post similar to my update process so I figured i would post it. My phone is working 100% and never bricked.

Started at 1.83 rooted with Cement locked. Reflashed back to stock 1.83 using the full sbf. Updated via stock recovery with the OTA update.zip on SD card. Once updated to 2.3.4 I rooted via preinstall did not unlock boot loader.

Here is what my file had in it.

10001000300000000

Sent from my MB860
[Atrix 4G Android Development] kholk:
Exactly.

"safe" or safe? :P Anyway, that happens because they've compiled a similar code...

Erm... It was an

"Entering NvFlash recovery mode"

or

"Starting Nv3p Emergency Server..."

Anyway, nope. They aren't cooked. They're properly _fucked_. It's poor. I think who unlocked should use only FastBoot and delete RSD from their minds. FastBoot is safe...unless you do ./fastboot flash motoboot motoboot.bin ... erm.. :)

A fuse or multiple fuses. Anyway, it happens because Moto doesn't want you to downgrade your BL. It's like that from Moto V Series (starting from V3)....

Anyway, anyone knows that prerelease software is _prerelease software_. If it's a kernel your device may crash. If it's a bootloader, the thing is a bit more dangerous...

All locked out. No SBK, No Party.
[Atrix 4G Android Development] SoberGuy:
My money is on the latter. I seriously think this was intentional. Moto came up with the eFuse, and they have done absolutely everything they can to ensure that eFuse will properly **** a device. It's not about protection, as a company could easily release appropriate recovery tools. To me, it's all about ensuring people don't do exactly what we do: make their **** better.
[Atrix 4G Android Development] Taas:
i am locked, rooted on 2.34, used android recovery with update.zip on sd card. went from rooted 1.83..did not flash 1.83 before flashing update .zip

10000000000010001000300000000
[Atrix 4G Android Development] Taas:
i want to unlock bl. but do not want a brick
[Atrix 4G Android Development] bl0wf1sh:
Anyway, that. The components we would need to un-hardbrick would be:

1) Factory cable: Can be ordered from TBH for $35 or can be made on your own, if your soldering skills are up to par.

2) nvflash: can be downloaded. I am assuming that nvflash is fairly device-independent, and could be used to flash any Tegra 2 device.

3) SBK: Yup, that's where the beef's at. Currently unavailable, cannot even be read. So the only way to get it is through a Moto leak.

With the SBK, I think we should be able to flash the 2.3.4 bootloader (if we assume that is what is messed up on some devices) and then 2.3.4 .img files via fastboot. We would need a factory cable as well, most likely, but $35 is still a lot less than the $500+ you would need to spend for a new phone.

That said, it is possible that even nvflash cannot help us, but only the Moto recovery software could. Which is company-internal and has not been leaked to my knowledge.
[Atrix 4G Android Development] Taas:
Are u unlocked ?....I wanna flash pudding but afraid
[Atrix 4G Android Development] eval-:
It seems, only people who updated to 4.5.91 the 'Official' way (putting it in your /sdcard, booting into stock android recovery) are at any risk for hard bricks. Unless you are on Movistar Spain, in which case please paste the contents of your /sys/firmware/fuse/ReservedOdm (and buy an insurance policy?) before flashing any 'Pudding' :p
[Atrix 4G Android Development] NFHimself:
From unlocked:

20002000200004000

Also my SE is now NS in rsd-lite.

Cheers!
[Atrix 4G Android Development] Foka002:
Hi guys

I'm not sure but I've possible bricked my mobile. What I have done:

I got t-mobile uk atrix:

1. I have Unlocked BL using pudidng for international.

2. Flashed via fastboot system.img for 2.3.4 OrangeFR

3. Applied fix for RAM

4. Installed CWM for Unlocked

5. Nand Backup

6. Applied cherry blur in CWM

7. Applied RAM fix for 4.5.91

Up to this point - no problems. I restored all apps via titanium. I went to sleep and when I woke up this morning my mobile was off and I couldn't switch it on.

I have connected to the charger and then the mobile went on immediately. After few sec went off again and then on. I thought the battery is dead untill I've read this thread.

Things I can do ONLY while my mobile is connected to charger:

1. Enter fastboot - but I'v got msg that battery is to low to flash...

2. Enter CWM Recovery

3. Once I'm in CWM I can unplug from Charger and connect to PC.

3. ADB sees my device

What I can do ? Is it hard Brick ?

//edit

Sorted guys.

I'm sorry If I wrote in the wrong thread. All I have done was Installing fruit cake for international via CWM and eventually I managed to lunch system!
[Atrix 4G Android Development] tan G:
why flashing using so many things??

that is all you need to do

good luck
[Atrix 4G Android Development] Foka002:
Don't want to spam in this thread but without installing cwm I still woud be looking for the solution...My battery was completely drained by cherry rom and I couldn't do anything. I'm more than happy what I've done. Always trusted cwm.

I'm not the only one with this problem which is also related to cherryblur rom.

Sent from Motorola Atrix
[Atrix 4G Android Development] cctv35:
Using the factory cable, no batteries, display SVF: 105:1:2

Failed to boot 0x1000, infinite restart.
[Atrix 4G Android Development] eval-:
Plugged into wall outlet (not PC), still infinite restart? No matter if you put battery in after plugging in, or not? Also, with factory cable, nothing in 'lsusb' output?

Can you post zips of bootloader(fastboot)+NvUboot CGs of the last (bad) flash and previous (good) .sbf flashed? If flashing Froyo 2.2.x it would be CG44 & CG47.

I presume you have a hong kong branded phone? Or china? AT&T phones behave differently on 0x1000 (nvflash or fastboot, always, no bootloops) but specifics depend on the bootloader version...
[Atrix 4G Android Development] cctv35:
Plugged into OTG power supply (not PC), still infinite restart.

'lsusb' no output.

CG44 is From IHOP_Bell.sfb.

After flashing Froyo 2.2.2 china OTA.

Updated package have mbm_combo.bin, baseband_ota_rdl.bin.
[Atrix 4G Android Development] eval-:
This is bad. Please let me know exactly: Who sells your phone? Can another user with your phone please paste contents of "

/sys/firmware/fuse/ReservedOdm

" (requires root to be able to read)

ALSO, if anyone you know has also flashed IHOP_Bell on a device just like yours,

could they also provide

/sys/firmware/fuse/ReservedOdm

(please tell them it

may not be safe to flash

ANY chinese .sbf or apply any OTAs until we know more!!)

Please make sure I understand the order:

1) Flash IHOP_Bell.sbf

(then, 'oem unlock' or no?)

2) fastboot or RSD (which?) flash 2.2.2 chinese and apply OTA ?

Or, you

already

had chinese 2.2.2 + OTA, and

just flashing IHOP_Bell.sbf caused this brick

? Does IHOP_Bell.sbf work to unlock your phone? Hong Kong or China? Which carrier? You can "fastboot flash" after?

If IHOP_Bell can brick a phone, or if it can lead to a brick after downgrade to Froyo BL, we need to put this in BIG RED LETTERS in the Pudding thread! Let me know if you can get that /sys/firmware/fuse/ReservedOdm value from some friends... thanks

PS. mbm_combo.bin is the bootloader + nv-microboot as you may know
[Atrix 4G Android Development] adlx.xda:
well, I think the big red letters would definitely be usefull and great. Yet, I already knew perfectly the bricking risks when I flashed it myself, it would hopefully reduce the bricks!
[Atrix 4G Android Development] cctv35:
@eval-

I was MB861, modify OLYEM_U4_2.1.1_SIGNED_UCAOLYPORTFR_P014_A004_M001_HWolympus_1g_1FF.sbf, replacing China's CG5, CG57 ~ CG62.smg, then Flash IHOP_Bell.sbf, followed by Flash OTA update.zip
[Atrix 4G Android Development] eval-:
Can you send mbm_combo.bin from the OTA?

Also, can you find a China friend who did NOT flash IHOP_Bell and send their

/sys/firmware/fuse/ReservedOdm

Also, if any other friend with same phone flash who DID flash IHOP_Bell please send

/sys/firmware/fuse/ReservedOdm

I think we cannot save your phone (yet?) .. but maybe we can know why it happened.
[Atrix 4G Android Development] cctv35:
NOT flash IHOP_Bell

/sys/firmware/fuse/ReservedOdm ： 30003000300000000