Tag Info

New answers tagged

1

The reason it is bootlooping is probably because cyanogenmod was installed and it isn't for that device. There should be serial/model number on the back of the device. This is a requirement (AFAIK) by the FCC. The certification mark is a stand-alone logo (as shown above) for the part 18 class of devices while, for the part 15 class, along with the ...


0

That device doesn't have a button configuration to boot into recovery. You are going to have to run sh reboot-recovery.sh from the SDcard, (posted in my original answer) after your device gets past bootloader.


2

CyanogenMod - Xperia SP maintainer here. If you are sure about having a Xperia SP then you can safely remove that assert check in the install script of the zip :) you should have the right prop id so you can continue on with normal releases. i've never seen this issue before.


1

FYI, I found out what the problem was: The stock rom needs to be updated to 4.2 (you can get the official rom here if there is no update available), I think because of the bootloader.


0

Just flash the recovery like you flashed it before, simple as that.


0

It's even easier than that. Just flash the new recovery from CWM as you would any other flashable zip.


2

Factory images are not supposed to be flashed in recovery. Instead, you should follow the instructions on the page you linked to. Open the tar file, it's probably just a compressed file, just like a zip. But first, let me point you to some "Custom ROMs" that ARE flashable in recovery: Stock Rastakat Cyanogenmod 12 (unofficial) However, those may all ...


2

Try doing what it suggests... run e2fsck -b 8193 /dev/block/platform/msm_sdcc.1/by-name/userdata. If that doesn't work, try running mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata. You can also boot into fastboot mode and run fastboot erase userdata. If none of these work, please elaborate on this "long story". How did you mess up your data ...



Top 50 recent answers are included