Hidden Name165
Lurker
Hello,
this is my first post here, and I need help. Hopefully I did everything correctly selecting "Support".
I've got an old Xperia M (nick) C1905 smartphone with Android 4.1.2 (not the newer 4.3), Firmware is 15.1.C.2.8 . I used towelroot from geohot to get supersu binaries in the system and installed SuperSU 2.82 as system app (pseudo-pro activated).
Now I discovered this: https://forum.xda-developers.com/showthread.php?t=2480556
So I flashed /boot partition because the device doesn't support recovery itself - it doesn't have a stock recovery and also TWRP made for "nicki" isn't flashable via TWRP App - well it tells me that it flashed but you cant boot it. So I typed after unlocking the bootloader "fastboot flash boot combined-boot-image.img" and now I can boot into clockworkmod recovery (when the boot logo appears the led turns pink, I press one volume up and if I do this, it turns into cyan. Now the recovery boots instead of Android's linux kernel.
But I am afraid flashing cyanogenmod 12.1 or 13 because I want to keep this recovery and be able to get back from cm 12 or 13 to stock rom.
So now the IMPORTANT question:
Does flashing cyanogenmod or any other ROM than the stock rom replace the modified bootloader? Will I have to install another recovery that works with cyanogenmod? And if cyanogenmod is installed and bootloader replaced (if that happens), can I flash the working recovery boot image, making cyanogenmod eventually unbootable (?), and therefor get the recovery back an flash the nandroid backup of the stock rom?
As far as I know, eventhough if the guy on xda says, that he would put the kernel into the image and do something "combined", i believe this is the boot image + cwm image what he combines, he only modifies the bootloader, right?
Here's the technical info from xda:
"The Xperia M doesn't have a recovery partition, therefore the recovery is packed into a boot image. There is an init script which checks whether it should boot into recovery, and if it should, the script will extract the recovery ramdisk and boot it. Otherwise it will extract the boot ramdisk and boot Android normally. The packer linked above is designed to pack the boot image."
Please help me! Thanks for every reply!
Pascal
this is my first post here, and I need help. Hopefully I did everything correctly selecting "Support".
I've got an old Xperia M (nick) C1905 smartphone with Android 4.1.2 (not the newer 4.3), Firmware is 15.1.C.2.8 . I used towelroot from geohot to get supersu binaries in the system and installed SuperSU 2.82 as system app (pseudo-pro activated).
Now I discovered this: https://forum.xda-developers.com/showthread.php?t=2480556
So I flashed /boot partition because the device doesn't support recovery itself - it doesn't have a stock recovery and also TWRP made for "nicki" isn't flashable via TWRP App - well it tells me that it flashed but you cant boot it. So I typed after unlocking the bootloader "fastboot flash boot combined-boot-image.img" and now I can boot into clockworkmod recovery (when the boot logo appears the led turns pink, I press one volume up and if I do this, it turns into cyan. Now the recovery boots instead of Android's linux kernel.
But I am afraid flashing cyanogenmod 12.1 or 13 because I want to keep this recovery and be able to get back from cm 12 or 13 to stock rom.
So now the IMPORTANT question:
Does flashing cyanogenmod or any other ROM than the stock rom replace the modified bootloader? Will I have to install another recovery that works with cyanogenmod? And if cyanogenmod is installed and bootloader replaced (if that happens), can I flash the working recovery boot image, making cyanogenmod eventually unbootable (?), and therefor get the recovery back an flash the nandroid backup of the stock rom?
As far as I know, eventhough if the guy on xda says, that he would put the kernel into the image and do something "combined", i believe this is the boot image + cwm image what he combines, he only modifies the bootloader, right?
Here's the technical info from xda:
"The Xperia M doesn't have a recovery partition, therefore the recovery is packed into a boot image. There is an init script which checks whether it should boot into recovery, and if it should, the script will extract the recovery ramdisk and boot it. Otherwise it will extract the boot ramdisk and boot Android normally. The packer linked above is designed to pack the boot image."
Please help me! Thanks for every reply!
Pascal