4 replies to this topic

[gilbertiddi0]

So I bought a used razr i on ebay to replace an i that got damaged recently. It appears to have been on the "Claro" network from Puerto Rico. It has the SIM locked, after looking into this, it may be possible to unlock the SIM so I attempted that. I have had no luck with that.

 

The firmware is also extremely Claro-centric so I attempted to modify this, The only firmware I can even get to load are latin versions. The message I get is "downgrading secure version flash failed." I have attempted such with RSD and with fastboot. It simply soft bricks the phone. I did manage to find an Argentinian version that is somewhat generic. The SIM is still locked.

 

I have attempted to unlock the bootloader through Motorola, but they do not recognize it as an unlockable device. It's still on 4.0.4, I'm not going to let it upgrade until I am sure that is the right thing to do.If it will even OTA.

 

Is there a way past this?

[gilbertiddi0]

Okay, I got the bootloader unlocked. I am trying to get off the latin versions. Simple reason; I think that is the problem. I can now get RSD to go to step 3: fails with the error:

 

E:Downgraded security version for logo

[tucstwo]

logo is just the icon that flashes on the screen when you first hit the power button. If you want, you can go into that fastboot files xml and delete the line that references "logo" and try again. But downgraded secure version is a weird error with the bootloader unlocked. Not too sure, I don't know a whole lot about that device. I know mattlgroff used to have one, maybe he could give you more info?

[gilbertiddi0]

Actually, it was the reason for failure if I tried to fastboot the individual images too - that was part of flashing bootloader I believe.

 

Installing "jellybean" solved that: I was able to flash an English ("Orange") version with no problem. I had no luck with that so I fastbooted cwm in recovery and jumped to Matt's version of jellybean. I did foolishly notice I no longer had a copy of rootkeeper so I tried to re-root - ended up bricking it but was able to find a tool on XDA that recovered so I am still in the running.

 

Still no luck on unlocking the Sim however. I opened it in "radiocomm" but it looks completely different from the "m" I was able to open up to GSM, The Key I got still is not recognized. The IMEI has remained constant though-out this process.  I am sure there must be some way of using radiocomm to enter the key or at least allow unlocking, but I can't find any procedure documented.

[gilbertiddi0]

Okay, this is turning into a blog. It is now hard bricked, maybe permanently. I found the solution: xfstk-dldr-solo.exe - it flashes files still to it - it fixed it once before, so I still have hope. I see many people are having problems very similar to mine, again leading me to believe there is a way out.

 

The problem as I see it, is in the present "un-bricking" usage, you flash two files, "drix" and "ifwi" to repair the boot loader. Obviously more than two files are mismatched or corrupted by the process of unlocking the bootloader and introducing clockwork mod recovery. This software is capable of flashing more then two files, why not replace all files so they match? the forum on xda-developers has two topics covering this so eventually I will have to register and post to those also, but this is the forum I find most answers and seems to have the most experts, so my question of the day is, what other files need to be replaced to match the ifwi and drix ones?

 

Z:\brick\unbrick>xfstk-dldr-solo.exe --help

XFSTK Downloader Solo 1.1.0a
Copyright (c) 2011 Intel Corporation

Command Line Options:
  -h [ --help ]               Print usage message
  --fwdnx arg (=BLANK.bin)    File path for the FW DNX module
  --fwimage arg (=BLANK.bin)  File path for the FW Image module
  --osdnx arg (=BLANK.bin)    File path for the OS DNX module
  --osimage arg (=BLANK.bin)  File path for the OS image
  --miscdnx arg               File path for miscellaneous DNX module
  --gpflags arg (=0x80000000) Optional argument. 32 Bit Hex Value of the
                              GPFlags.
  --transfer arg (=USB)       Optional argument. Determines how the image will
                              be transferred.
  --idrq arg (=0)             Optional argument. Indicates whether IDRQ is
                              used. 1 means idrq is used, 0 means idrq is not
                              used.
  -v [ --verbose ]            Optional argument. Display debug information. 1
                              means show debug information, 0 means hide debug
                              information.