awww ok, not sure how to do that, so I will probably run the RUU go back to 4.2.2 then unlock, and flash Dedoxe 4.4.2 tomorrow, thx for the info
problem with one mini
- Thread starter abracadabra19
- Start date
-
- Tags
- question
Do y'all need a modified boot.IMG for cm11? I can post one
Sent from my One Mini using Tapatalk
Sent from my One Mini using Tapatalk
Well, I suppose it would help some people. There is already one in #16 on the previous page. But probably a new one from the latest nightly would be nice.
Personally I still stick with the stock rom. At the moment I'm trying to figure out why TWRP isn't able to unlock the /data partition which I encrypted on the stock system before. Maybe HTC modified something with the encryption process?
Personally I still stick with the stock rom. At the moment I'm trying to figure out why TWRP isn't able to unlock the /data partition which I encrypted on the stock system before. Maybe HTC modified something with the encryption process?
Did you try using dd if=/dev/zero of=/dev/block/mmcblk0p37 from terminal in twrp then reformat?
Sent from my One Mini using Tapatalk
Sent from my One Mini using Tapatalk
I just modified fstabs of the original 2.7.0.5 as follows:
Code:
diff -urN ramdisk-contents.orig/etc/recovery.fstab ramdisk-folder/etc/recovery.fstab
--- ramdisk-contents.orig/etc/recovery.fstab 2014-04-03 11:24:52.580058600 +0900
+++ ramdisk-folder/etc/recovery.fstab 2014-04-03 11:34:30.489058600 +0900
@@ -1,8 +1,8 @@
# mount point fstype device [device2] [parameters]
-/boot emmc /dev/block/mmcblk0p31
-/recovery emmc /dev/block/mmcblk0p32
-/devlog ext4 /dev/block/mmcblk0p24
-/system ext4 /dev/block/mmcblk0p33
-/cache ext4 /dev/block/mmcblk0p34
-/data ext4 /dev/block/mmcblk0p35
+/boot emmc /dev/block/mmcblk0p33
+/recovery emmc /dev/block/mmcblk0p34
+/devlog ext4 /dev/block/mmcblk0p25
+/system ext4 /dev/block/mmcblk0p35
+/cache ext4 /dev/block/mmcblk0p36
+/data ext4 /dev/block/mmcblk0p37
/external_sd auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable
diff -urN ramdisk-contents.orig/fstab.m4 ramdisk-folder/fstab.m4
--- ramdisk-contents.orig/fstab.m4 2014-04-03 11:24:52.590058600 +0900
+++ ramdisk-folder/fstab.m4 2014-04-03 11:32:44.026058600 +0900
@@ -1,8 +1,8 @@
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
-/dev/block/mmcblk0p31 /boot emmc defaults defaults
-/dev/block/mmcblk0p32 /recovery emmc defaults defaults
-/dev/block/mmcblk0p24 /devlog ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait
-/dev/block/mmcblk0p33 /system ext4 rw,noatime,barrier=0 wait
-/dev/block/mmcblk0p34 /cache ext4 nosuid,nodev,noatime,barrier=0 wait,check
-/dev/block/mmcblk0p35 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0,discard wait,check,encryptable=/dev/block/mmcblk0p29
+/dev/block/mmcblk0p33 /boot emmc defaults defaults
+/dev/block/mmcblk0p34 /recovery emmc defaults defaults
+/dev/block/mmcblk0p25 /devlog ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait
+/dev/block/mmcblk0p35 /system ext4 rw,noatime,barrier=0 wait
+/dev/block/mmcblk0p36 /cache ext4 nosuid,nodev,noatime,barrier=0 wait,check
+/dev/block/mmcblk0p37 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0,discard wait,check,encryptable=/dev/block/mmcblk0p30
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=usbdisk:autoI will upload cwm 6.0.4.7.
Here is a clockworkmod recovery 6.0.4.7 for new partition layout compiled from cm11.
Here is an updated boot.img for new partition layout.
Thanks for the tip. Did it. May have helped or not. I'm not sure.
Just to share my insights so far. After completely erasing /data I flashed CM11 (with adjusted boot.img thanks to @kyasu), encrypted the /data partition again and rebooted to TWRP (the adjusted version) and voilà, it works. TWRP can unlock the encrypted /data partition. So everything seems fine. Just don't know exactly whether it is due to the dd-ing of the data partition or the result of having CM on the device now.
However I'm still wondering what's the reason for this strange behaviour. Since everything worked so flawlessly with CM I suspect HTC having modified the encryption process. I'd usually say this is quite unlikely but there is another thing I noticed: Running the encryption with the Stock ROM took less than 10 minutes. But with CM11 it took about 30 minutes or even more. In both cases the data partition was almost empty though it shouldn't make any difference since I expect the encryption to run on block level and therefore include the empty parts of the partition anyway.
That's it for now. Probably I stay with CM now and hope that the remaining bugs get sorted out soon. Runs pretty well already.
Thanks to @kyasu again for providing new recoveries and boot.img.
quick question im trying to run RUU nut i get 155 error, heres my info from my bootloder
Relocked
S-off
hboot 2.22.0000
radio 1.25.40g.00.19
os 3.10.502.3
ruu is ofr 1.32.502 is that why i am unable to run it? and is there a way to get back to stock 4.2.2? im having a hard tim flashing any roms do to the partition changes from 4.4.2
Relocked
S-off
hboot 2.22.0000
radio 1.25.40g.00.19
os 3.10.502.3
ruu is ofr 1.32.502 is that why i am unable to run it? and is there a way to get back to stock 4.2.2? im having a hard tim flashing any roms do to the partition changes from 4.4.2
Have a look over there for error codes from running RUU: http://forum.xda-developers.com/showthread.php?t=2659109
I'm not sure, if your RUU is too old. Probably it can't run properly due to the modified partitions, too.
Don't you have a nandroid backup from your stock 4.4.2?
I can provide one. It's from a German 4.4.2 (3.10.111.4). Don't know if it will work on your device (there could be connectivity issues). However, I can't upload it until tonight.
I'm not sure, if your RUU is too old. Probably it can't run properly due to the modified partitions, too.
Don't you have a nandroid backup from your stock 4.4.2?
I can provide one. It's from a German 4.4.2 (3.10.111.4). Don't know if it will work on your device (there could be connectivity issues). However, I can't upload it until tonight.
TBH i just want to get deodox of this rom [4.4.2][Sense 5.5][3.10.401.4][Stock]. would a nandroid from another person be able to get me to this>?
I can upload a nandroid of the latest cm build I'm running for all of you. Make it easier.
Sent from my One Mini using Tapatalk
---------- Post added at 03:09 PM ---------- Previous post was at 02:52 PM ----------
Actually Ill upload a the boot.IMG and meta.inf folder. Then all you have to do is download the newest cm11 build unzip and replace the files i give you with the ones in the new cm11 you download rezip and flash.
Sent from my One Mini using Tapatalk
Sent from my One Mini using Tapatalk
---------- Post added at 03:09 PM ---------- Previous post was at 02:52 PM ----------
Actually Ill upload a the boot.IMG and meta.inf folder. Then all you have to do is download the newest cm11 build unzip and replace the files i give you with the ones in the new cm11 you download rezip and flash.
Sent from my One Mini using Tapatalk
Additionally here is a ready to flash version of the 0403 CM11 nightly for the new partition layout: https://dl.dropboxusercontent.com/u/5035075/m4kk/cm-11-20140403-NIGHTLY-m4kk.zip (MD5: 3bc8d4694f1ee80992665138b252431f)
Remember you need the modified TWRP 2.7.0.5 to flash this successfully (or the modified CWM 6.0.4.7, but didn't test it).
Maybe I will make another one from one of the latest nightlies in the next few days.
Remember you need the modified TWRP 2.7.0.5 to flash this successfully (or the modified CWM 6.0.4.7, but didn't test it).
Maybe I will make another one from one of the latest nightlies in the next few days.
Last edited:
Well there ya go just use the files from this zip. Thanks saved me some drive space
Sent from my One Mini using Tapatalk
Actually the deodexed 3.10.401.4 from over there is a 3.10.631.5. Nevertheless, here you can find a ready-to-flash version for the new partition layout: http://forum.xda-developers.com/showthread.php?p=51779967
If your actually a member of xda. The only reason for stock is warranty.lol after all custom is what is all about.
Sent from my One Mini using Tapatalk
Sent from my One Mini using Tapatalk
What changes did you made to boot.img? Did you only modify the ramdisk? Or did you modify the kernel, too? If yes, how did you do that?
I only know the way of splitting boot.img, modifying fstab of ramdisk and merging ramdisk and kernel back to a boot.img.
Or did you build the kernel from source?
I just wanted to fully understand the changes you made. So I took your boot.img, splitted it and compared the files to a splitted boot.img from the CM11 nightlies. Strangely the kernel files (zImage) differ, that is, they have a different MD5. So does this mean there have been changes to the kernel, too?
Last edited:
I just modified fstab but compiled from source for my hobby.
You can edit boot.img by using Android Kernel Kitchen (http://forum.xda-developers.com/showthread.php?t=1659584).
Here is a modified 0411-NIGHTLY boot.img that is edited by using Android Kernel Kitchen. I just replaced fstab.m4 in ramdisk. The kernel file (zImage) is the same as the original.
Last edited:
Thanks for clearing this up. :good: :good: :good:
So I know what to do whenever I want to flash a new nightly.
Compiling from source would be an option, too, yeah and is quite a cool thing.
I'm afraid I'm just too lazy to this everytime a new nightly pops up.
So I know what to do whenever I want to flash a new nightly.
Compiling from source would be an option, too, yeah and is quite a cool thing.
I'm afraid I'm just too lazy to this everytime a new nightly pops up.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone