[Q&A] [MOD] SD-EXT Boot MOD - CM12

[Magrat_young]

@hinxnz , Hello! I can't fastboot flash zimage zImage.img, an error "FAILED (remote: not allowed)". I have S-off, unlocked bootloader, hboot 1.29. What is the problem? Thx.

 

[hinxnz]

Well, I've tried the repairing option in the advanced wipe menu for sd-ext in TWRP, to no avail unfortunately. So I cleaned the SD card completely with the "clean all" command in Windows 7's diskpart utility. Then I partitioned the SD card in TWRP-2.8.6.0-r10 (4096 MB sd-ext, 0 MB swap), tried letting the filesystem be ext4 and also tried changing it to f2fs, encryption still unsuccessful with boot-mod-plus 1.5. Weird thing (which wasn't documented here on the forum yet as far as I'm concerned) is that it always restarts into recovery and runs some OpenRecoveryScript that always fails, I took a photo of it here (recovery logs can also be found at the link). When the script finishes, it always restarts the phone into system automatically and everything works fine but without any boot-mod.
Then the boot-mod-plus 2.0 was made available so I booted live Ubuntu and split the 4096 MB ext4 partition into two 2048 MB ext4 partitions in GParted (their sizes are actually 1953 MB since the sd-ext partition created by TWRP was 3906 MB in size). Again, wiped everything except MicroSD card in Advanced wipe menu, flashed latest CM 12.1, zero gapps and then the boot-mod-plus 2.0. This time, it already gave me an error right after the flashing procedure: "E:Unable to mount '/cache'". That never happened with version 1.5. Stuck on boot animation after restart. So I tried flashing it again, still stuck on boot animation (boot.img from CM12.1 was flashed via fastboot).
So is it possible that I'm unable to install either boot-mod because the 16 GB Kingston SD card is not made for linux filesystems or is straight damaged and I should opt for replacement?

Hey been busy, hence the late reply but it must not work for users that are s-on then.
You could s-off with the rumrunner method, there's a guide in the sensation forum.

@hinxnz , Hello! I can't fastboot flash zimage zImage.img, an error "FAILED (remote: not allowed)". I have S-off, unlocked bootloader, hboot 1.29. What is the problem? Thx.

Hi, you can't flash the zImage because your bootloader is locked, flash hboot 1.27 from the universal firmware thread.
Edit: Just to let you know, I just made a flashable zip for the zImage too.
http://forum.xda-developers.com/showpost.php?p=62273851&postcount=162

 

[Magrat_young]

Thank you for answers and for help, hinxnz. Why is it after flashing BOOT-MOD-PLUS-ZIMAGE.zip phone to become unstable if the screen off after 3 minutes, the phone is switched off, and if you do not turn off the screen then everything is stable,. I placed after the Rom 12.1 And BOOT-MOD-PLUS 2.3. What is the problem? Thx.

 

[hinxnz]

Thank you for answers and for help, hinxnz. Why is it after flashing BOOT-MOD-PLUS-ZIMAGE.zip phone to become unstable if the screen off after 3 minutes, the phone is switched off, and if you do not turn off the screen then everything is stable,. I placed after the Rom 12.1 And BOOT-MOD-PLUS 2.3. What is the problem? Thx.

Your welcome. Possibly couple of things maybe, first can you enter code in terminal and see if it fixes it and let me know.

su
echo 0 > /sys/module/board_pyramid_panel/parameters/panel_uv

 

[Magrat_young]

Your welcome. Possibly couple of things maybe, first can you enter code in terminal and see if it fixes it and let me know.

su
echo 0 > /sys/module/board_pyramid_panel/parameters/panel_uv

not Fixed.

 

[hinxnz]

not Fixed.

Enter this code and reboot.

su
echo > /system/etc/init.d/00system

 

[Magrat_young]

Enter this code and reboot.

su
echo > /system/etc/init.d/00system

Did not help. Another remarked that sometimes does not turn the screen after a while, but have read that you have decided it. I will return to a stable kernel. Thx.

 

[hinxnz]

Did not help. Another remarked that sometimes does not turn the screen after a while, but have read that you have decided it. I will return to a stable kernel. Thx.

Could be the undervolt script then, you could remove it and reboot with code below or maybe it was just a bad flash, works fine here. Possibly could be with the kernel though but I not experiencing anything like that, maybe it could be related to panel type and panel uv.

su
echo > /system/etc/init.d/00uv
reboot

 

[Magrat_young]

Could be the undervolt script then, you could remove it and reboot with code below or maybe it was just a bad flash, works fine here. Possibly could be with the kernel though but I not experiencing anything like that, maybe it could be related to panel type and panel uv.

su
echo > /system/etc/init.d/00uv
reboot

After this script has started to reboot the phone. After init.d 320 phone is loaded immediately restarts. I flash BOOT-MOD-PLUS-ZIMAGE.zip and everything after it is turned off when the screen turns off the phone.

 

[hinxnz]

After this script has started to reboot the phone. After init.d 320 phone is loaded immediately restarts. I flash BOOT-MOD-PLUS-ZIMAGE.zip and everything after it is turned off when the screen turns off the phone.

Possibly your phone can't handle GPU at 320MHz or CPU at 1728MHz, more than likely GPU.
I think all sensations can handle 300 for GPU and 1674 for CPU as that is stock speed from Qualcomm.

 

[n5ane]

Encyrption Error with MOD; MicroSD card will not mount after partition

HTC Sensation 4G; S-Off, unlocked bootloader, rooted; HBOOT 1.27.111; running CM12.1-20150809 and it works great; Ivanich TWRP 2.8.7

Encryption Error on Boot: After android name appears, encryption error message appears similar to previous post. Fixing permissions does not help. I have not resolved the issue. Note: TWRP was able to mount one 3GB ext4 partition on my 32gb, but other partitions hidden...so I could install MOD from the 3GB partition, but got the error. After partitioning again, I am not able to get any partition to mount in TWRP.
I would like to flash MOD SD-EXT, but cannot get sdcard to mount in TWRP

.....many, many hours of attempts and 2 days later....

Partions not recognized in TWRP
32 GB g.skill microSD class 10 card partioned with gparted as follows:
FAT32-22GB
ext4-4096 mb
ext4-3072 mb
...all primary partions aligned to mb using MSDOS partition table (should I try GPT?).

I am able to mount all three partitions in Ubuntu, read/write files to partitions, see devices in gparted, etc. However, none of the partitions are recognized in TWRP regardless of what I do (wipe, mount, unmount, default settings, remove battery, full reset, load ROM, remove ROM, wipe again, learing looks, yell at it, etc.) When I switch to a single FAT32 partion on my 8GB microSD, everything is fine, the sdcard is recognized, and I can install ROM. I am not able to get TWRP to recognize the 32GB partioned microsd and, therefore, unable to install ROM or Mod from sdcard.

I have reviewed many sdcard partioning methods. TWRP sdcard partition tool does not work either. Does the android mount point need to be changed through adb shell & busybox? example: biemmeitalia(dot)net/blog/how-mount-sd-card-android-works/

I feel that TWRP is able to mount /dev/sdf but not /dev/sdf1 or /sdf2 or /sdf3. The working 8gb card is shown on android path as /dev/block/platform/msm_sdcc.1 and /sms_sdcc.3
-----
ADB Push option for SD-EXT boot MOD?
I am able to adb push Mod to internal memory and perhaps install from there with 3 partition card installed (unmounted, unrecognized by TWRP). Is this a good idea? Do you have a preferred directory for the MOD adb push?
Note: I was not able to get adb sideload to work on TWRP. Adb devices are shown before sideload, but when sideload enabled, adb devices disappear and cannot sideload. I have all current USB and ADB drivers, current ADB sdk, current TWRP by Ivanich.

*I understand TWRP mounting & partitioning problems are better asked in a different threads specific to TWRP and microsd partitioning, but any help is appreciated since I have not found a good solution after much research.

 

[hinxnz]

HTC Sensation 4G; S-Off, unlocked bootloader, rooted; HBOOT 1.27.111; running CM12.1-20150809 and it works great; Ivanich TWRP 2.8.7

Encryption Error on Boot: After android name appears, encryption error message appears similar to previous post. Fixing permissions does not help. I have not resolved the issue. Note: TWRP was able to mount one 3GB ext4 partition on my 32gb, but other partitions hidden...so I could install MOD from the 3GB partition, but got the error. After partitioning again, I am not able to get any partition to mount in TWRP.
I would like to flash MOD SD-EXT, but cannot get sdcard to mount in TWRP

.....many, many hours of attempts and 2 days later....

Partions not recognized in TWRP
32 GB g.skill microSD class 10 card partioned with gparted as follows:
FAT32-22GB
ext4-4096 mb
ext4-3072 mb
...all primary partions aligned to mb using MSDOS partition table (should I try GPT?).

I am able to mount all three partitions in Ubuntu, read/write files to partitions, see devices in gparted, etc. However, none of the partitions are recognized in TWRP regardless of what I do (wipe, mount, unmount, default settings, remove battery, full reset, load ROM, remove ROM, wipe again, learing looks, yell at it, etc.) When I switch to a single FAT32 partion on my 8GB microSD, everything is fine, the sdcard is recognized, and I can install ROM. I am not able to get TWRP to recognize the 32GB partioned microsd and, therefore, unable to install ROM or Mod from sdcard.

I have reviewed many sdcard partioning methods. TWRP sdcard partition tool does not work either. Does the android mount point need to be changed through adb shell & busybox? example: biemmeitalia(dot)net/blog/how-mount-sd-card-android-works/

I feel that TWRP is able to mount /dev/sdf but not /dev/sdf1 or /sdf2 or /sdf3. The working 8gb card is shown on android path as /dev/block/platform/msm_sdcc.1 and /sms_sdcc.3
-----
ADB Push option for SD-EXT boot MOD?
I am able to adb push Mod to internal memory and perhaps install from there with 3 partition card installed (unmounted, unrecognized by TWRP). Is this a good idea? Do you have a preferred directory for the MOD adb push?
Note: I was not able to get adb sideload to work on TWRP. Adb devices are shown before sideload, but when sideload enabled, adb devices disappear and cannot sideload. I have all current USB and ADB drivers, current ADB sdk, current TWRP by Ivanich.

*I understand TWRP mounting & partitioning problems are better asked in a different threads specific to TWRP and microsd partitioning, but any help is appreciated since I have not found a good solution after much research.

Not sure why your having issues but make sure you create the partitions in the correct order, first create the fat32 partition and then the sd-ext's or you could try repartitioning the sdcard with 4ext recovery, you may need to format the whole card as fat32 first.

 

[Sertleris]

Hi alll! Last time updated while ago. Do I need just one sd-ext partition update to V3?

 

[john0312]

I've got this mod to work with my HTC Sensation (ivanich's CM11) S-ON, though it requires a bit more actions on the users part.

All I did is modify modboot.sh, and instead of dd to write to boot partition, I copy /tmp/newboot.img to /sdcard/.
( I also added mount /sdcard to updater-script )

Then, I manually copy newboot.img to my computer and manually flash the newboot.img with "fastboot flash boot newboot.img".

PS: I'm posting here because I'm a new user and can't post to the development thread.

 

[hinxnz]

I've got this mod to work with my HTC Sensation (ivanich's CM11) S-ON, though it requires a bit more actions on the users part.

All I did is modify modboot.sh, and instead of dd to write to boot partition, I copy /tmp/newboot.img to /sdcard/.
( I also added mount /sdcard to updater-script )

Then, I manually copy newboot.img to my computer and manually flash the newboot.img with "fastboot flash boot newboot.img".

PS: I'm posting here because I'm a new user and can't post to the development thread.

Hi, just seen your post but yeah that's the reason s-off is needed, what you did will work fine.

 

[andy hall]

Hi, have just done a CM12.1 build using latest ROM V4 boot mod and open GAPPS. Cannot install or restore Facebook. Have not tried any playing yet but in the out of the box form is V4 fully ready.
Sorry if that sounded rude, was not meant to be, I appreciate these things are very much a work in progress and everyone has time constraints. Am going to rebuild again, it looks like some parts may not have taken properly.

 

[hinxnz]

Hi, have just done a CM12.1 build using latest ROM V4 boot mod and open GAPPS. Cannot install or restore Facebook. Have not tried any playing yet but in the out of the box form is V4 fully ready.
Sorry if that sounded rude, was not meant to be, I appreciate these things are very much a work in progress and everyone has time constraints. Am going to rebuild again, it looks like some parts may not have taken properly.

Hi, I haven't had the time to test with cm12.1 yet but what's not working? Is it sdcard related?

 

[andy hall]

Hi, I haven't had the time to test with cm12.1 yet but what's not working? Is it sdcard related?

I am still using the same SD card, reverted to 3.14 and all was ok.
Facebook is horrid to install and I think there is some optimisation or read ahead or possibly zram setting that needs to be in place to combat the cack installer, everything else I tried seemed to work ok.
was a bit surprised to see dalvik on sdext by default but looking back makes sense to start especially in view of MM.

 

[hinxnz]

I am still using the same SD card, reverted to 3.14 and all was ok.
Facebook is horrid to install and I think there is some optimisation or read ahead or possibly zram setting that needs to be in place to combat the cack installer, everything else I tried seemed to work ok.
was a bit surprised to see dalvik on sdext by default but looking back makes sense to start especially in view of MM.

Yeah I'll make a note on second post that v4 is for cm13 only instead of making it compatible because as you say v3 is complete for cm12.1 and I can easily update init.d script for v3 if needs be.