Hi,
The Meteorit MMB-322.HDTV is an Android based MultimediaPlayer for TV's.
Currently it's mainly selled in Germany and there are many owners which are interested in the Box and in Modding them.
Before we can start building custom Firmwares we need a way to recover the System. We are in contact with the manufacturer and he said, that there is no Software-Recovery. And to update to a new Firmware the system must be bootable.
Because here are many experts in this forum, I hope youcan and want to help us developing a recovery-method like Nandroid or a little NANDFlashMode.
Now all information I already have and which could be useful for you:
The Partitions MTD-based
That's the list of MTD-partitions:
dev: size erasesize name
mtd0: 00020000 00020000 "block0"
mtd1: 00100000 00020000 "bootloader"
mtd2: 01900000 00020000 "bootimgs"
mtd3: 01900000 00020000 "bootimgs-B"
mtd4: 00080000 00020000 "u-boot.env"
mtd5: 0c000000 00020000 "system"
mtd6: 08000000 00020000 "userdata"
mtd7: 06800000 00020000 "cache"
mtd8: 00400000 00020000 "factory_setting"
mtd9: 00400000 00020000 "factory_data"
mtd10: 01000000 00020000 "sysconf"
mtd11: 20000000 00020000 "mv_nand"
Click to expand...
Click to collapse
This are the Kernel-bootargs:
sata_reset_done
nfc_shared
androidboot.console=ttyS0
console=ttyS0,115200
root=/dev/mtdblock5
rootfstype=yaffs2
ro
root_part_name=system
init=/init
mtdparts=mv_nand:131072(block0),
1048576(bootloader),
26214400(bootimgs),
26214400(bootimgs-B),
[email protected](u-boot.env),
[email protected](system),
134217728(userdata),
109051904(cache),
4194304(factory_setting),
4194304(factory_data),
16777216(sysconf)
initrd=0x4e00000,0x47b5a
macaddr=00:25:92:14:47:94
Click to expand...
Click to collapse
There is a binary "oureboot" which can reboot the system with adding args to the kernel. This would result in using /2ndinit to boot Linux:
oureboot "init=/2ndinit"
Click to expand...
Click to collapse
The system-partition is mounted to / and contains everything which normally is located on the ramdisk.
I think, the best progress would be, if anyone of you could find out how the boot-partitions(bootloader, bootimgs and bootimgs-B) can be extracted.
Here is the FW-Updatefile: ftp://ftp.pearl.de/treiber/PX1534_12_103600.zip
In the Archive is a file named "ouimg.bin". You can open this and the contained file "ouimg" with 7Zip and then there will be a file ./uniimg/uniimg.bin
This is the file which will be flashed on update. I don't know if it's flashed partially or if this is a direct NAND-Backup.
I hope that you can and do help us.
Best regards,
M1cha
This looks like (at least on the outside) the same box as:
NAXA NGT-20:
http://www.naxa.com/lcd-and-led-tel...t-systems/googler-androidtm-internet-box.html
SuperSonic sc-66g:
http://forum.xda-developers.com/showthread.php?t=1292472
Here is another site with some info on it:
http://www.mobiflip.de/erster-eindruck-hdmi-multimedia-web-tv-box-meteorit-mmb-322-mit-android/
cifs.ko
Hello all,
does anyone of you have a cifs.ko and a slow-work.ko(if needed) for the meteorit mmb-322 or do u know where i can get it.
2 nd question: where can i get the meteorit mmb-322 - toolbox from
the download link here and on adroid-hilfe does not work.
best regards
Dietmar
Somebody know cust roms and kernels (cust) then pls posht hier a link and Write down everything.
I want just make a collection for this phone Alcatel OT991.
Thankyou
hekinen5830i said:
Somebody know cust roms and kernels (cust) then pls posht hier a link and Write down everything.
I want just make a collection for this phone Alcatel OT991.
Thankyou
Click to expand...
Click to collapse
Maybe someone first upload the original ROMs for this phone.
nice post!!! hope some1 will upload!!
Working on new ROM
Hello everyone,
Currently I'm working in a new ROM for 991 and 991D. It is a very basic ROM. The standard ROM (2.3.6)+Root+Remove Apps+Support for Ext3-Ext4 and App2SD.
The main problem is that we have few memory to work.
Hello guys,
First of all, this might not be the proper section, but still, the problem I'm referring to was solved on other devices using custom ROM.
I have the same phone and I have a weird problem. I can make skype calls but the sound is played through the speakerphone, and not through the earpiece. The same is true for other VoIP apps - Kakao Talk, Line..... When I tried to use Viber I couldn't hear the other person, yet they could hear me.
I read somewhere, that the same problem occurred with ZTE Blade and it was solved by using Cyanogenmod 7. So I guess this could be solved with a custom ROM.
Here's a link to a forum thread with people experiencing the same problem.
modaco.com/topic/331808-skype-speaker-fix
and how to upload the stock rom because i dont know :\
VitaminX said:
Hello guys,
First of all, this might not be the proper section, but still, the problem I'm referring to was solved on other devices using custom ROM.
I have the same phone and I have a weird problem. I can make skype calls but the sound is played through the speakerphone, and not through the earpiece. The same is true for other VoIP apps - Kakao Talk, Line..... When I tried to use Viber I couldn't hear the other person, yet they could hear me.
I read somewhere, that the same problem occurred with ZTE Blade and it was solved by using Cyanogenmod 7. So I guess this could be solved with a custom ROM.
Here's a link to a forum thread with people experiencing the same problem.
modaco.com/topic/331808-skype-speaker-fix
Click to expand...
Click to collapse
Try the audio profiles. In settings. I will investigate later. It could be a stupid error in audio routing.
sacreew said:
Hello everyone,
Currently I'm working in a new ROM for 991 and 991D. It is a very basic ROM. The standard ROM (2.3.6)+Root+Remove Apps+Support for Ext3-Ext4 and App2SD.
The main problem is that we have few memory to work.
Click to expand...
Click to collapse
take your time but remeber that we wait your rom
gp.triple said:
take your time but remeber that we wait your rom
Click to expand...
Click to collapse
For sure. It will take a looooong time. It is my wifes phone, so I only can steal it sometimes. And I am a complete newbie cooking Roms.
sacreew said:
For sure. It will take a looooong time. It is my wifes phone, so I only can steal it sometimes. And I am a complete newbie cooking Roms.
Click to expand...
Click to collapse
do you have some link of tutorial about cooking roms for newbie?
gp.triple said:
do you have some link of tutorial about cooking roms for newbie?
Click to expand...
Click to collapse
Yes and no Do you know spanish?
Fist step (with a rooted phone). Get all the ROM img files:
1) Conect the phone throught adb.
2) adb shell
3) su
4) cat /proc/mtd
It will write down somenthing like this (this is from my LG P500 so it will be different for OT991D)
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
5) Now you can get files with cat. For exapample to get boot and recovery:
cat /dev/mtd/mtd1 > /sdcard/mtd1.img
cat /dev/mtd/mtd2 > /sdcard/mtd2.img
The files will be stored in the sd. Mount and copy.
Those are the basic files from our original ROM. But the boot.img. That is the vulnerable boot.img that we used to root the phone.
sacreew said:
Yes and no Do you know spanish?
Fist step (with a rooted phone). Get all the ROM img files:
1) Conect the phone throught adb.
2) adb shell
3) su
4) cat /proc/mtd
It will write down somenthing like this (this is from my LG P500 so it will be different for OT991D)
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
5) Now you can get files with cat. For exapample to get boot and recovery:
cat /dev/mtd/mtd1 > /sdcard/mtd1.img
cat /dev/mtd/mtd2 > /sdcard/mtd2.img
The files will be stored in the sd. Mount and copy.
Those are the basic files from our original ROM. But the boot.img. That is the vulnerable boot.img that we used to root the phone.
Click to expand...
Click to collapse
sorry but i don't know spanish
in the next day i root my phone then start to dump :good:
991D Files
Files for Alcatel 991-991D:
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00080000 00020000 "pro_info"
mtd3: 00300000 00020000 "nvram"
mtd4: 00020000 00020000 "seccnfg"
mtd5: 00060000 00020000 "uboot"
mtd6: 00600000 00020000 "boot"
mtd7: 00600000 00020000 "recovery"
mtd8: 00120000 00020000 "secstatic"
mtd9: 00060000 00020000 "misc"
mtd10: 00300000 00020000 "logo"
mtd11: 000a0000 00020000 "expdb"
mtd12: 07300000 00020000 "system"
mtd13: 09100000 00020000 "custpack"
mtd14: 00120000 00020000 "watchdog"
mtd15: 03c00000 00020000 "cache"
mtd16: 09e80000 00020000 "userdata"
Just remenber that boot.img is the vulnerable one NOT the factory one. Also system is modified with less applications (basically all that garbage that we don´t need) and the Alcatel keyboard is removed (also its languajes). System also includes root and busybox.
https://docs.google.com/folder/d/0B4Mx65V6aE-mRHU3dTdEcHc2cFk/edit
Be carefull updating with flash tool
Boot image with app2sd
Hi everyone,
finally I have a new boot image with A2SD support.
Mod Edit Link Removed as it is stated in next post not to use.
Please be carefull:
1) I don´have the 991D. So I can no test it by the moment.
2) It is the vulnerable image+app2sd DT.
3) Allways have the "new-boot.img" by mrdoubble by hand. Just in case you need to rollback.
4) Use flash tool to apply it.
There is somenthing strange with our boot.img so I have to separate the kernel from ramdisk by hand with hexeditor. I have done the new image with mkboot, so I don´t know if Alcatel it is not using the standard headers it is going to work.
You have to do a partition in your SD to store the apps (ext2). Try it and use app2sd gui to test if everything works.
sacreew said:
Hi everyone,
finally I have a new boot image with A2SD support.
Mod Edit Link Removed as it is stated in next post not to use.
Please be carefull:
1) I don´have the 991D. So I can no test it by the moment.
2) It is the vulnerable image+app2sd DT.
3) Allways have the "new-boot.img" by mrdoubble by hand. Just in case you need to rollback.
4) Use flash tool to apply it.
There is somenthing strange with our boot.img so I have to separate the kernel from ramdisk by hand with hexeditor. I have done the new image with mkboot, so I don´t know if Alcatel it is not using the standard headers it is going to work.
You have to do a partition in your SD to store the apps (ext2). Try it and use app2sd gui to test if everything works.
Click to expand...
Click to collapse
DON'T USE
I had just tested it. An it don´t work. I will do not boot. I had just removed the file.
but is possible use part of code of other mtk6573 device?
a lot of "china-phone" ar based on mtk soc
you can look here or here
did any1 of you done full 100% backup and how did you do it ?
is there CWM Recovery for 991?
Any news?
Sent from my ALCATEL ONE TOUCH 991D using xda app-developers app
this is a good thread, i would allso be interested in having the original rom and customes ones. Anyone knows if android 4.0 or 4.1 can be installed on alcatel ot-991?
thanks and hi everybody!
Problems flashing ot-991
sacreew said:
Yes and no Do you know spanish?
Fist step (with a rooted phone). Get all the ROM img files:
1) Conect the phone throught adb.
2) adb shell
3) su
4) cat /proc/mtd
It will write down somenthing like this (this is from my LG P500 so it will be different for OT991D)
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
5) Now you can get files with cat. For exapample to get boot and recovery:
cat /dev/mtd/mtd1 > /sdcard/mtd1.img
cat /dev/mtd/mtd2 > /sdcard/mtd2.img
The files will be stored in the sd. Mount and copy.
Those are the basic files from our original ROM. But the boot.img. That is the vulnerable boot.img that we used to root the phone.
Click to expand...
Click to collapse
Hi,
I've tried to flash my ot-991 following the instructions givens by tutorial 'how to root 991-d', using the file root991-D, the scatered file and teh 'new-image'. After then my phone is dead and when I try to flash again I have a message like : BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054). Doing memory test I have the same problem, but it works fine when I 'Read back' the boot image. Can you have any idea ?
I understand spanish, cause I'm spanish.
Thank you for your help
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
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
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.
Nope you flashed a firmware package from an htc one. Hahahaha
Sent from my One Mini using Tapatalk
cmvienneau said:
Nope you flashed a firmware package from an htc one. Hahahaha
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
I flashed an OTA update (OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip).
Any useful information to share?
Do you have soff or access to custom recovery or unlocked bl?
Sent from my unknown using Tapatalk
cmvienneau said:
Do you have soff or access to custom recovery or unlocked bl?
Click to expand...
Click to collapse
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!
what do you mean modified partition?
Sent from my One Mini using Tapatalk
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
Hmm? That's weird because even stock I never had p036 or 37
Sent from my One Mini using Tapatalk
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...
Click to collapse
I'm new, How you do? or Link Please.
Thanks
GixxGle said:
I'm new, How you do? or Link Please.
Thanks
Click to expand...
Click to collapse
Try this one
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...
Click to collapse
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 !?
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...
Click to collapse
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?
tirlol said:
Try this one
Click to expand...
Click to collapse
Try another derived from http //mdmower.cmphys.com/twrp-m4/
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...
Click to collapse
Steps for installing cm11 to new partition after ota 4.4.2 update:
Flash recovery that supports new partition.
(TWRP2630-KKOneMine.zip or twrp-2.7.0.5-m4kk.img.zip)
Download the latest nightly from http //download.cyanogenmod.org/?device=m4.
(cm-11-201404xx-NIGHTLY-m4.zip)
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))
Flash the editied nightly zip file from the recovery.
kyasu said:
Try another derived from http //mdmower.cmphys.com/twrp-m4/
Click to expand...
Click to collapse
Great! :good::good::good:
This saved my a**. I was tinkering around for hours and couldn't get the recoveries to work properly. Thought I was going mad.
What a relief.
@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.
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...
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.