[One (M7) Q&A, Help & Troubleshooting] davidrol:
Your cellular network is radio/modem specific. When this happens, your modem and its software is suspect. When there is corruption in the partitions, or any partitiion, things go haywire. 'Haywire' is a technical term, lol, when there is a corrupted sddrive. When reformatting the sdcard is not an option, you could buy a damaged phone, another case, and swap logic boards. Once the partitions are damaged, one must know what they are doing to restore the device's partitions correctly/permanently to avoid later complications. Overlapped partitions causing constant reboots is a common occurrence. There is a way the check your partitions using e2fsck via adb shell to compare your partition sizes against stock, with the mmcblk0p31 containing your radio. You can google for the one's original partition map.

Here is an example of several overlapped partitions due to a failed sddrive:

~ # e2fsck -n -v -f /dev/block/mmcblk0p37

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37

Filesystem mounted or opened exclusively by another program?

mmcblk0p22: 01400000 00000200 "devlog"

Free blocks count wrong (610, counted=596).

Fix? no

Free inodes count wrong (1174, counted=1173).

mmcblk0p24: 00040000 00000200 "pdata"

# e2fsck -n -v -f /dev/block/mmcblk0p24

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24

mmcblk0p27: 00010000 00000200 "extra"

# e2fsck -n -v -f /dev/block/mmcblk0p27

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p27

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

mmcblk0p31: 04b00200 00000200 "radio"

# e2fsck -n -v -f /dev/block/mmcblk0p31

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p31

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

mmcblk0p16: 03c00400 00000200 "adsp"

2fsck -n -v -f /dev/block/mmcblk0p16

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p16

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p17: 007ffa00 00000200 "radio_config"

mmcblk0p20: 00400000 00000200 "modem_st1"

mmcblk0p21: 00400000 00000200 "modem_st2"

mmcblk0p28: 00100000 00000200 "cdma_record"

mmcblk0p18: 02000000 00000200 "reserve_1"

mmcblk0p30: 034ffa00 00000200 "reserve_2"

mmcblk0p32: 05fffc00 00000200 "reserve_3"

mmcblk0p29: 06069e00 00000200 "reserve"