problem with one mini

A

abracadabra19

Member
Dec 30, 2011
13
0
0
Mar 11, 2014 at 12:49 PM
hi for all
am have big problem with one mini after unlock bootloader and whem am try to flash custom recovery phone hang and now whem am try to flash any rom by recovery give me failed by twrp and cwm and am havnt ruu file for it
phone info
m4_u_pvt ship s-on
hboot -2.22.0000
radio-1.24.40e

cid is HTC__038

build no 3.10.707.3
on recovery give e
E:cant mount cashe
cant mout open cashe
please help me how ican slove any one have this ruu for india
 
cmvienneau

cmvienneau

Senior Member
Apr 29, 2011
511
267
0
32
washburn
drive.google.com
Mar 18, 2014 at 10:49 AM
Are you s-off?

Sent from my One Mini using Tapatalk

---------- Post added at 05:49 AM ---------- Previous post was at 05:47 AM ----------

Nvm.lol i see you are not. If you have twrp recovery. Go into wipe and press the wipe data button. Enter "yes" let it format then go to advanced wipe and only put a check by cache.

Sent from my One Mini using Tapatalk
 
K

kyasu

Senior Member
Sep 23, 2012
488
2,234
123
Tokyo
Mar 18, 2014 at 2:13 PM
I also have the same problem. this is because the emmc partition was changed from 4.4.
I have a HongKong version (HTC__622) and EMMC info of 4.3 (2.12.708.3) was:

Code: 
$ adb shell cat /proc/emmc
dev:        size     erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 85fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 29fffe00 00000200 "cache"
mmcblk0p35: 2d8000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 01fffc00 00000200 "reserve"
mmcblk0p27: 00004000 00000200 "control"
Now EMMC info of 4.4 (3.10.708.4) is:

Code: 
$ adb shell cat /proc/emmc
dev:        size     erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"
You have to modify ramdisk of recovery image.
 
K

kyasu

Senior Member
Sep 23, 2012
488
2,234
123
Tokyo
Mar 21, 2014 at 12:40 AM
cmvienneau said:
Do you have soff or access to custom recovery or unlocked bl?
Click to expand...
My one mini is working perfectly as 4.4 (3.10.708.4) and the partition modified TWPR 2.6.3.0 by myself is also working.
And my home build CM11 with modified partition is working perfectly.
My conclusion is that an asian version of one mini (or my one mini only) has new partition from 4.4 (3.10.708.4).
Unbelievable!
 
  • Like
Reactions: tirlol
K

kyasu

Senior Member
Sep 23, 2012
488
2,234
123
Tokyo
Mar 22, 2014 at 11:41 PM
I modified /etc/fstab. the following is a diff of CM11:

Code: 
diff --git a/rootdir/etc/fstab.m4 b/rootdir/etc/fstab.m4
index d83a00a..5bb45c9 100644
--- a/rootdir/etc/fstab.m4
+++ b/rootdir/etc/fstab.m4
@@ -8,12 +8,12 @@
 /dev/block/mmcblk0p17   /firmware_q6    vfat    ro,shortname=lower                                      wait
 #/dev/block/mmcblk0p18  /firmware_wcnss vfat    ro,shortname=lower                                      wait
 
-/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
 
 # USB Storage
 /devices/platform/msm_hsusb_host/usb	auto	auto	defaults	voldmanaged=usbdisk:auto
diff --git a/rootdir/etc/remount.m4 b/rootdir/etc/remount.m4
index c5960dd..8789c5e 100644
--- a/rootdir/etc/remount.m4
+++ b/rootdir/etc/remount.m4
@@ -3,4 +3,4 @@
 # The filesystem that contains the filesystem checker binary (typically /system) cannot
 # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
 
-/dev/block/mmcblk0p33	/system	ext4	remount,ro,noatime,barrier=0	wait
+/dev/block/mmcblk0p35	/system	ext4	remount,ro,noatime,barrier=0	wait
 
GixxGle

GixxGle

Member
Aug 27, 2011
17
1
0
Mar 26, 2014 at 9:56 AM
How, help please

kyasu said:
My one mini is working perfectly as 4.4 (3.10.708.4) and the partition modified TWPR 2.6.3.0 by myself is also working.
And my home build CM11 with modified partition is working perfectly.
My conclusion is that an asian version of one mini (or my one mini only) has new partition from 4.4 (3.10.708.4).
Unbelievable!
Click to expand...
I'm new, How you do? or Link Please.

Thanks
 
GixxGle

GixxGle

Member
Aug 27, 2011
17
1
0
Mar 31, 2014 at 11:36 AM
kyasu said:
I modified /etc/fstab. the following is a diff of CM11:

Code: 
diff --git a/rootdir/etc/fstab.m4 b/rootdir/etc/fstab.m4
index d83a00a..5bb45c9 100644
--- a/rootdir/etc/fstab.m4
+++ b/rootdir/etc/fstab.m4
@@ -8,12 +8,12 @@
 /dev/block/mmcblk0p17   /firmware_q6    vfat    ro,shortname=lower                                      wait
 #/dev/block/mmcblk0p18  /firmware_wcnss vfat    ro,shortname=lower                                      wait
 
-/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
 
 # USB Storage
 /devices/platform/msm_hsusb_host/usb	auto	auto	defaults	voldmanaged=usbdisk:auto
diff --git a/rootdir/etc/remount.m4 b/rootdir/etc/remount.m4
index c5960dd..8789c5e 100644
--- a/rootdir/etc/remount.m4
+++ b/rootdir/etc/remount.m4
@@ -3,4 +3,4 @@
 # The filesystem that contains the filesystem checker binary (typically /system) cannot
 # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
 
-/dev/block/mmcblk0p33	/system	ext4	remount,ro,noatime,barrier=0	wait
+/dev/block/mmcblk0p35	/system	ext4	remount,ro,noatime,barrier=0	wait
Click to expand...
thanks for your reply :)

I'm not advanced user (new noop). i not modified /etc/fstab by myself :( , can you guide me step by step !?
 
cmvienneau

cmvienneau

Senior Member
Apr 29, 2011
511
267
0
32
washburn
drive.google.com
Apr 2, 2014 at 9:37 AM
kyasu said:
I modified /etc/fstab. the following is a diff of CM11:

Code: 
diff --git a/rootdir/etc/fstab.m4 b/rootdir/etc/fstab.m4
index d83a00a..5bb45c9 100644
--- a/rootdir/etc/fstab.m4
+++ b/rootdir/etc/fstab.m4
@@ -8,12 +8,12 @@
 /dev/block/mmcblk0p17   /firmware_q6    vfat    ro,shortname=lower                                      wait
 #/dev/block/mmcblk0p18  /firmware_wcnss vfat    ro,shortname=lower                                      wait
 
-/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
 
 # USB Storage
 /devices/platform/msm_hsusb_host/usb	auto	auto	defaults	voldmanaged=usbdisk:auto
diff --git a/rootdir/etc/remount.m4 b/rootdir/etc/remount.m4
index c5960dd..8789c5e 100644
--- a/rootdir/etc/remount.m4
+++ b/rootdir/etc/remount.m4
@@ -3,4 +3,4 @@
 # The filesystem that contains the filesystem checker binary (typically /system) cannot
 # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
 
-/dev/block/mmcblk0p33	/system	ext4	remount,ro,noatime,barrier=0	wait
+/dev/block/mmcblk0p35	/system	ext4	remount,ro,noatime,barrier=0	wait
Click to expand...
hey bro.. i can confirm its not an asian issue i recieved the att update. it seems as if maybe they have merged sources with the htc one? it looks as tho the partition schemes after the 4.4.2 update from att are the same as the original htc one..please correct me if im wrong?
 
  • Like
Reactions: TRIBLAST
K

kyasu

Senior Member
Sep 23, 2012
488
2,234
123
Tokyo
Apr 3, 2014 at 4:42 PM
GixxGle said:
thanks for your reply :)

I'm not advanced user (new noop). i not modified /etc/fstab by myself :( , can you guide me step by step !?
Click to expand...
Steps for installing cm11 to new partition after ota 4.4.2 update:

  1. Flash recovery that supports new partition.
    (TWRP2630-KKOneMine.zip or twrp-2.7.0.5-m4kk.img.zip)
  2. Download the latest nightly from http //download.cyanogenmod.org/?device=m4.
    (cm-11-201404xx-NIGHTLY-m4.zip)
  3. Edit nightly zip file by replacing boot.img and META-INF/com/google/android/updater-script with attached files.
    (boot.img and updater-script(updater-script.zip))
  4. Flash the editied nightly zip file from the recovery.
 

Attachments

  • Like
Reactions: TRIBLAST, GixxGle and RuffBuster
M

morschesholz

Senior Member
Apr 3, 2014
87
17
0
Apr 7, 2014 at 12:52 PM
@kyasu: The 2.7.0.5 version isn't able to mount my encrypted data partition. It asks for the password and then keeps telling me the password is wrong (which definitely isn't). The phone is booting fine and during startup my password is accepted. Do you have any ideas? Is there more modification needed to match the new partition layout?
Btw, the 2.6.3.0 version linked in this thread isn't working at all. Doesn't ask for a password to decrypt /data in the first place. And /system can't be mounted, too.
 
R

romy134

Senior Member
Sep 21, 2010
264
17
0
Apr 8, 2014 at 8:10 AM
If I am on stock 4.4.2 with twrp-2.7.0.5-m4kk.img.zip recovery can I flash [4.4.2][Sense 5.5][3.10.401.4][Stock]? so far iv tried 3-4 times and it never works im HBOOT 2.22 s-off. or will i need to use a different rom? should have just stayed on the ddoxed 4.4.2 instated of going stock...
 
M

morschesholz

Senior Member
Apr 3, 2014
87
17
0
Apr 8, 2014 at 8:31 AM
As I already said over there (http://forum.xda-developers.com/showthread.php?t=2708997) you can. But you have to edit the update-script within the update zip file to match the new partition layout.
So you have to change every line referring to one of the partitions which have changed now: system (previously mmcblk0p33, now mmcblk0p35), data (previously mmcblk0p35, now mmcblk0p37) or boot (previously mmcblk0p31, now mmcblk0p33).

As far as I know for now you can use the boot.img provided with the [4.4.2][Sense 5.5][3.10.401.4][Stock] as well as the boot.img from your recovery backup (that is, the stock kernel with absolutely no modifications). Since you're S-OFF you're probably ok with just flashing the zip from the recovery. Nevertheless you could play it safe and flash the boot.img via fastboot after you have done flashing.
 
  • Like
Reactions: TRIBLAST, GixxGle and romy134
You must log in or register to reply here.

New posts

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