Database Info

Meteorit MMB-322

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

SuperCID K2_PLC_CL Cricket & K2_CL CDMA Boost Mobile

Also, see post #13 for another method. It makes it possible without needing to use fastboot, but from your device.
Must be S-Off (which would imply you are rooted as well) - that is the way the cookie crumbles with the 2.0 HBoot. Will update this once I receive 4.2.2.
Insure you have the proper ADB and Fastboot files on your PC, open command and change its directory to the location of your proper ADB and Fastboot file(s). Dragging and dropping in to the CMD Window is the fastest method - that I am aware of.
-in cmd, type or copy/paste code:
Code:
adb devices
-if you get your serial number back, boot to bootloader:
Code:
adb reboot bootloader
-check for connectivity
Code:
fastboot devices
-if you get a serial number back, check your cid first, in case you want to restore it later - copy it while you still can
Code:
fastboot getvar cid
or
Code:
fastboot getvar all
(will return other variables as well )
-change CID
Code:
fastboot oem writecid 11111111
(eight ones)
-reboot bootloader
Code:
fastboot reboot-bootloader
-check CID again
Code:
fastboot getvar cid
or
Code:
fastboot getvar all
-verify CID=11111111
-reboot
Code:
fastboot reboot
---------- Post added at 11:51 PM ---------- Previous post was at 11:14 PM ----------
I have a K2_CL and by following my above instructions you WILL gain SuperCID without any chances of bricking your phone. This works on JB with the 2.0 HBoot. Profit! A simple thanks will suffice lol
---------- Post added 14th November 2013 at 12:06 AM ---------- Previous post was 13th November 2013 at 11:51 PM ----------
I wanted to add this for those certain viewers/readers who don't fully understand what is being discussed in this guide will actually better understand its importance.
Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed.
While SuperCID may seem handy, note that if you are only interested in debranding your phone, the OTA (over the air) updates which HTC sends will not be available for your phone, since there is no specific region defined. So, in such cases, you should choose a specific CID for your region.

Modding.MyMind said:
I have a K2_CL and by following my above instructions you WILL gain SuperCID without any chances of bricking your phone. This works on JB with the 2.0 HBoot. Profit! A simple thanks will suffice lol
Click to expand...
Click to collapse
hey cowboy,
are you saying you did accomplish superCID on your CDMA boostmobile OneSV?
I bricked my (first) boost by attempting it (with HxD hex editor)
just trying to clarify if your saying the fastboot command actually worked for you......?

russellvone said:
hey cowboy,
are you saying you did accomplish superCID on your CDMA boostmobile OneSV?
I bricked my (first) boost by attempting it (with HxD hex editor)
just trying to clarify if your saying the fastboot command actually worked for you......?
Click to expand...
Click to collapse
Yes, it worked for me. Just follow my instructions bro and profit!

good to know, any...um...actual benefits though?
that you can assume anyways?

Will be going for 4.2.2 here soon. superCID allows you to install any rom without restrictions to your specific provider which in my case would be (boost). Now, this is in theory though this theory is back by some facts, and of course being based on the CID itself. CID 11111111 is overall universal so technically I should be able to throw down on a K2 LTE 4.2.2 OTA. Will be testing this soon enough and will give feed back on the results. This is really the only thing I can think to be useful - for now lol.

Modding.MyMind said:
Will be going for 4.2.2 here soon. superCID allows you to install any rom without restrictions to your specific provider which in my case would be (boost). Now, this is in theory though this theory is back by some facts, and of course being based on the CID itself. CID 11111111 is overall universal so technically I should be able to throw down on a K2 LTE 4.2.2 OTA. Will be testing this soon enough and will give feed back on the results. This is really the only thing I can think to be useful - for now lol.
Click to expand...
Click to collapse
just be very careful my friend.
all the other variants of the OneSV have different partition layout than boost variant.
meaning K2_UL, K2_U, & K2PLC_CL all have the same partition layout because the all require SIM cards
boost mobile partitions are not the same

Which comes the tricky part

http://forum.xda-developers.com/showthread.php?t=2208315
[K2_u]Result of adb shell cat /proc/emmc
check this link out

russellvone said:
http://forum.xda-developers.com/showthread.php?t=2208315
[K2_u]Result of adb shell cat /proc/emmc
check this link out
Click to expand...
Click to collapse
That just gave me a headache haha

russellvone said:
K2_cl
Code:
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
[COLOR="Red"]mmcblk0p35: 54fffc00 00000200 "system"[/COLOR]
mmcblk0p29: 00140200 00000200 "local"
[COLOR="Red"] mmcblk0p36: 0dfffe00 00000200 "cache" [/COLOR]
mmcblk0p37: 49fffe00 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
[COLOR="Red"] mmcblk0p38: 1097fe000 00000200 "fat" [/COLOR]
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p32: 01900000 00000200 "carrier"
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"
mmcblk0p31: 00040000 00000200 "skylink"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 04729a00 00000200 "reserve"
HTC One SV Boost Mobile
Click to expand...
Click to collapse
old.splatterhand said:
I thought maybe someone will need this for future development:
Code:
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
[COLOR="Red"]mmcblk0p33: 54fffc00 00000200 "system"[/COLOR]
mmcblk0p29: 00140200 00000200 "local"
[COLOR="Red"] mmcblk0p34: 0dfffe00 00000200 "cache" [/COLOR]
[COLOR="Red"] mmcblk0p35: 49fffe00 00000200 "userdata" [/COLOR]
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
[COLOR="Red"] mmcblk0p36: 1097fe000 00000200 "fat" [/COLOR]
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"
mmcblk0p31: 00100000 00000200 "cdma_record"
HTC One SV; k2_u; european non-LTE
Click to expand...
Click to collapse
just a few differences highlighted
---------- Post added at 11:48 PM ---------- Previous post was at 11:47 PM ----------
sorry for the off topic OP
DELETE if necessary

I noticed that the latter one is non lte. Would need results from an lte outside of Boost for better clarification on my part.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
Having trouble getting the phone to even recognize the OTA in general anyways as of right now.
Sent from my C525c using XDA Premium 4 mobile app

Modding.MyMind said:
I noticed that the latter one is non lte. Would need results from an lte outside of Boost for better clarification on my part.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
Having trouble getting the phone to even recognize the OTA in general anyways as of right now.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the non LTE is K2_U and the LTE is K2_UL, they have identical partition I think
EDIT: I don't want to put my foot in my mouth, so I added 'i think'
---------- Post added at 12:13 AM ---------- Previous post was at 12:03 AM ----------
Modding.MyMind said:
Having trouble getting the phone to even recognize the OTA in general anyways as of right now.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
android-info.txt must be changed inside the firmware zip first.
please please do this with complete caution, I am glad to see you putting you device on the line, I just hope everything goes well enough to not brick the device.
first you should compare sizes of files like Hboot and what not because +/- 1kb could = brick
---------- Post added at 12:15 AM ---------- Previous post was at 12:13 AM ----------
good luck to you sir
:thumbup:

@old.splatterhand @russellvone
K2_CL(Boost Mobile) - (S-Off)
K2_PLC_CL (Cricket) - (S-Off)
Terminal Emulator with SU rights.
Supercid (K2_CL, K2_PLC_CL)
Code:
echo -ne '\x31\x31\x31\x31\x31\x31\x31\x31' | dd of=/dev/block/mmcblk0p4 bs=1 seek=532
CID: SPCS_003 (K2_CL Boost Mobile Only)
Code:
echo -ne '\x53\x50\x43\x53\x5F\x30\x30\x33' | dd of=/dev/block/mmcblk0p4 bs=1 seek=532
CID: CRICK001 (K2_PLC_CL Cricket Only)
Code:
echo -ne '\x43\x52\x49\x43\x4B\x30\x30\x31' | dd of=/dev/block/mmcblk0p4 bs=1 seek=532
Sent from my C525c using XDA Premium 4 mobile app

Modding.MyMind said:
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you gonna keep superCID till the update, to see if it affects receiving early.......or not at all?

russellvone said:
you gonna keep superCID till the update, to see if it affects receiving early.......or not at all?
Click to expand...
Click to collapse
Yup
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 10:48 PM ---------- Previous post was at 10:36 PM ----------
I believe it will receive early. I was reviewing the file and noticed it is prepped for supercid - which surprised me. So my theory is that since I have changed to supercid the file recognizes it in the system due to the imprint already being prepped. This may be a good thing, but only time will confirm. Either way, we will have our answer.
Sent from my C525c using XDA Premium 4 mobile app

Modding.MyMind said:
Yup
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 10:48 PM ---------- Previous post was at 10:36 PM ----------
I believe it will receive early. I was reviewing the file and noticed it is prepped for supercid - which surprised me. So my theory is that since I have changed to supercid the file recognizes it in the system due to the imprint already being prepped. This may be a good thing, but only time will confirm. Either way, we will have our answer.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
alrighty, I'll hold tight with stock CID, ....what file were you reviewing? one of the OTA that we received already?

I dumped mmcblk0p4 to my sdcard then pulled it to my laptop. I don't have any of our OTA's saved on my pc at this moment so that was the only way to review it. Just search and find 11111111. Its there lol, but apart from where our actual cid is listed and found in the file.
Afterwards I just viewed the hex and wrote out the dd command above for gaining supercid and for restoring back to our stock cid.
Sent from my C525c using XDA Premium 4 mobile app

Modding.MyMind said:
I dumped mmcblk0p4 to my sdcard then pulled it to my laptop. I don't have any of our OTA's saved on my pc at this moment so that was the only way to review it. Just search and find 11111111. Its there lol, but apart from where our actual cid is listed and found in the file.
Afterwards I just viewed the hex and wrote out the dd command above for gaining supercid and for restoring back to our stock cid.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
confirmed......

any working method for Cricket users on JB?

zomgitsanoob said:
any working method for Cricket users on JB?
Click to expand...
Click to collapse
lucky you,
@Modding.MyMind is looking for a tester.......
will you pull a file for him and post it here?
open terminal emulator on you device and you type
su
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4.img
then upload here please....
then we'll know for sure

problem with one mini

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.

Dumping rom, weird case

Hello,
Trying to make a custom rom for a device i just got (it has no specific brand).
Tried dumping with romdump but boot.img was empty, so i had a look around and finally queried mtd:
Code:
cat proc/mtd
dev: size erasesize name
mtd0: 00040000 00040000 "misc"
mtd1: 00500000 00040000 "recovery"
mtd2: 00500000 00040000 "kernel"
mtd3: 00300000 00040000 "ramdisk"
mtd4: 0aa00000 00040000 "system"
mtd5: 04000000 00040000 "cache"
mtd6: 10800000 00040000 "userdata"
In all exemples i saw there was an entry with the name 'boot' and neither 'kernel' nor 'ramdisk'.
Code:
dd if=/dev/mtd/mtd2
and
Code:
dd if=/dev/mtd/mtd3
are not recognized as valid by the kitchen.
I am guessing that somehow if i managed to merge kernel and ramdisk i would probably get a proper boot.img but my (maybe wrong) thoughts stop right here.
Has anyone seen such a case before?
thanks

Aftermath
Finally, few month later, I was not dumping the right partitions and my kernel was corrupt. I also found that working in a Linux environment is much better and less error prone.

[RECOVERY] TWRP touch recovery v2.8.6.0

Since there has been some confusion about which recovery to use when flashing KitKat and Lollipop ROMs, here is the thread for it.
This is NOT my work, all thanks go to @mdmower
This recovery is REQUIRED for flashing KitKat ROMs and Lollipop ROMs
To install, go to bootloader and type in: fastboot flash recovery (filename).img
Official TWRP (All Hboots) - 2.8.6.0
Unofficial TWRP (All Hboots) - 2.8.5.5
Material Design TWRP Themes (thanks @letsurock)
​

MDMower TWRP Changelog
Changelog
Code:
Update to 2.8.6.0
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
Updated to 2.8.1.1
CPU performance profiles – speeds up compressed and/or encrypted backups
Support both data/media and dedicated storage variants
Updated to 2.8.0.1
Built with cm-11.0 base
Add recovery-agnostic charging LED indicator service
Change USB VendorID:ProductID for ADB/ADB+MTP to match HTC’s stock configuration
[2.7.1.3-beta] Built with cm-11.0 base
[2.7.1.3-beta] Refactor battery charging indicator into lib (gerrit 9332)
Correctly write bootloader messages to /misc partition without wiping everything else
Track backup and restore progress
Color in the console
Refresh after partition changes
Do not restore file system on data/media devices
libtar: don’t set parent dir’s context when extracting a file
HTC LED charging indicator
Updated to 2.7.1.0
libtar: don’t set parent dir’s context when extracting a file
HTC LED charging indicator

For flash Recovery via Android you can use Flash Image GUI app.
ROOT required.
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Download link from above threat:
http://goo.gl/T6GsJ

Maybe it is a good thing to put also the changelog in OP. I was wondering what's the difference to the official TWRP builds and others may ask as well. Also state that this is an unofficial TWRP build
Unofficial 2.7.1.0a: Important changes since official 2.7.1.0
- libtar: don’t set parent dir’s context when extracting a file
- HTC LED charging indicator
Unofficial 2.7.1.0a: Known issues and limitations
- This should be fixed with 2.7.1.0, but I have not confirmed: When upgrading from some other maintainers’ TWRP builds, it may be necessary to delete the settings file /sdcard/TWRP/.twrps or TWRP will loop its startup routine at the splash screen.
- Off-mode charging does not display charging images; the LED works though.
Click to expand...
Click to collapse
Original mdmower page for Ville

Rapier said:
Maybe it is a good thing to put also the changelog in OP. I was wondering what's the difference to the official TWRP builds and others may ask as well. Also state that this is an unofficial TWRP build
Original mdmower page for Ville
Click to expand...
Click to collapse
I will and do u know what partition is recovery on for HBOOT 2.16, on 2.15 its at /dev/block/mmcblk0p22. Need to know as I'm making recovery-flashable .zips

dd98 said:
I will and do u know what partition is recovery on for HBOOT 2.16, on 2.15 its at /dev/block/mmcblk0p22. Need to know as I'm making recovery-flashable .zips
Click to expand...
Click to collapse
/recovery | /dev/block/mmcblk0p22 | Size: 15MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p22
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
From recovery log. Couldn't extract via terminal with /dev/block/platform or cat proc/partitions. So i guess it's same block.
Востани Сербие, востани царице.

Loreane Van Daal said:
/recovery | /dev/block/mmcblk0p22 | Size: 15MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p22
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
From recovery log. Couldn't extract via terminal with /dev/block/platform or cat proc/partitions. So i guess it's same block.
Востани Сербие, востани царице.
Click to expand...
Click to collapse
try "cat /proc/emmc"

It's the same. mmcblk0p22 is recovery partition.
[email protected]/$ su
[email protected]/# cat /proc/emmc
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 310000000 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 030d4000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p32: 0616a000 00000200 "reserve"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
mmcblk0p32: 0616a000 00000200 "reserve"
[email protected]/#
Востани Сербие, востани царице.

Loreane Van Daal said:
It's the same. mmcblk0p22 is recovery partition.
[email protected]/$ su
[email protected]/# cat /proc/emmc
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 310000000 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 030d4000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p32: 0616a000 00000200 "reserve"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
mmcblk0p32: 0616a000 00000200 "reserve"
[email protected]/#
Востани Сербие, востани царице.
Click to expand...
Click to collapse
Thanks, there will be two recovery flashable zips coming soon

Flash from goo manager app..... boom you're welcome
Sent from my One S using XDA Premium 4 mobile app

Hi! is this compatible with MaximusHD? After the recovery update, can I backup and restore my MaxHD rom?

Jeeza said:
Hi! is this compatible with MaximusHD? After the recovery update, can I backup and restore my MaxHD rom?
Click to expand...
Click to collapse
It should, but just to be safe make a backup with TWRP 2.6.1.0 that came with Maximus and try to restore with TWRP on this thread, if it doesn't work then flash TWRP 2.6.1.0

Did it work?

I'm on HBOOT 2.16 and recovery 2.7.0.8 I tried flashing the zip file and it's giving me an error "E:Error executing updater binary in zip..." I deleted the .twrps file so not sure whats going wrong in the flash.

nate51 said:
I'm on HBOOT 2.16 and recovery 2.7.0.8 I tried flashing the zip file and it's giving me an error "E:Error executing updater binary in zip..." I deleted the .twrps file so not sure whats going wrong in the flash.
Click to expand...
Click to collapse
It might be my fault, just flash it in fastboot or flash image gui

dd98 said:
It might be my fault, just flash it in fastboot or flash image gui
Click to expand...
Click to collapse
I tried the flash image GUI but it's not responsive for some reason, I open the app grant SU permission and it just gives me a blank screen. I tried Fastboot but something about Sense 6 does not allow ADB to read my phone anymore, I didn't have the problem when using CM11. Just Sense 6 4.4.2. So flashing in recovery was kind of my last ditch option.
---------- Post added at 09:39 PM ---------- Previous post was at 09:25 PM ----------
dd98 said:
It might be my fault, just flash it in fastboot or flash image gui
Click to expand...
Click to collapse
My bad, I just had to update Superuser binary and the GUI app worked, I successfully flashed 2.7.1.0a img. Thanks for the help.

Hi. I have noticed that Internal storage mount doesn't work??? Does anybody else have same issue ?

Spakainz said:
Hi. I have noticed that Internal storage mount doesn't work??? Does anybody else have same issue ?
Click to expand...
Click to collapse
Well known common problem. Make sure to have your ROM zip on internal storage before you wipe system. Or search how to adb sideload.

Spakainz said:
Hi. I have noticed that Internal storage mount doesn't work??? Does anybody else have same issue ?
Click to expand...
Click to collapse
Its purposely done, its the same on my M7 with official TWRP

Hi. Is there any way to make the same TWRP2.7.1.0 for VilleC2?