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

a collection of Custom ROMS and kernels for for Alcatel ot 991 hier --->

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

Just had another minor 50mb update from t-mobile

Hey i just another update as mentioned, but NO Jelly bean sadly...
HTC one S using xda premium

Did it change your radio?
Sent from my HTC One S using xda app

1.13 baseband

dis you have that update some where? iy would be mice to have the new baseband.
Sent from my One S using Tapatalk 2

blackwing182 said:
dis you have that update some where? iy would be mice to have the new baseband.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
http://fotadl.htc.com/OTA_Ville_U_I...2.35.531.7_release_306848u5s8i4b18xs094yw.zip
y'all should know who's got it by now j/k lol

Behold_this said:
http://fotadl.htc.com/OTA_Ville_U_I...2.35.531.7_release_306848u5s8i4b18xs094yw.zip
y'all should know who's got it by now j/k lol
Click to expand...
Click to collapse
you always lol thanx man!
Sent from my One S using Tapatalk 2

No problem bro! Now if someone would be willing to help me that would be nice.
I'm interested in the stock build.prop from this update. If someone that has applied this patch can post that here or pm me I'd appreciate it. TIA

https://www.dropbox.com/s/62gkif9hu5rhvqa/build.prop
I just dl and installed this update and here is the build.prop I am unrooted but doubt that makes a difference.

Sent from my HTC One S using xda From the build.prop:
#device supports LTE
ro.config.lte=true
I know there have been mentions of LTE in the build.prop in the past but does the One S really support LTE?

lampel said:
Sent from my HTC One S using xda From the build.prop:
#device supports LTE
ro.config.lte=true
I know there have been mentions of LTE in the build.prop in the past but does the One S really support LTE?
Click to expand...
Click to collapse
noop no lte chip
Sent from my One S using Tapatalk 2
---------- Post added at 10:23 PM ---------- Previous post was at 10:08 PM ----------
why t mobile troll us like that -_-
Sent from my One S using Tapatalk 2

Could someone make a flash able zip for the new radio? Be nice esp with soff now
Sent from my One S using xda app-developers app

droidkevlar said:
Could someone make a flash able zip for the new radio? Be nice esp with soff now
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
talk to tecardo
Sent from my One S using Tapatalk 2

blackwing182 said:
talk to tecardo
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
I posted in his thread in the dev section. Thanks for the heads up.

droidkevlar said:
I posted in his thread in the dev section. Thanks for the heads up.
Click to expand...
Click to collapse
any time man
Sent from my One S using Tapatalk 2

I have a TMobile with (downgraded to) hboot 1.06, 1.08ts radio and S-OFF. It did not flash via fastboot, still shows tampered and unlocked after my attempts.
PHP:
mkdir TMP
cd TMP
unzip ../OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.12-2.35.531.7_release_306848u5s8i4b18xs094yw.zip
unzip firmware.zip
# fastboot flash radio radio.img
sending 'radio' (34345 KB)...
OKAY [ 2.980s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 3.013s
# fastboot flash wcnss wcnss.img
sending 'wcnss' (5120 KB)...
OKAY [ 0.715s]
writing 'wcnss'...
FAILED (remote: not allowed)
finished. total time: 0.747s
# fastboot flash radio_config rcdata.img
sending 'radio_config' (0 KB)...
OKAY [ 0.142s]
writing 'radio_config'...
FAILED (remote: not allowed)
finished. total time: 0.175s
For future references, I save all the md5's...
PHP:
# md5sum ../OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.12-2.35.531.7_release_306848u5s8i4b18xs094yw.zip
cca668e517ac0be8306c604e7a43f0e9 ../OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.12-2.35.531.7_release_306848u5s8i4b18xs094yw.zip
Code:
[[email protected] 0]# unzip firmware.zip
Archive: firmware.zip
warning [firmware.zip]: 256 extra bytes at beginning or within zipfile
(attempting to process anyway)
inflating: android-info.txt
inflating: boot.img
inflating: hboot_ville_1.14.0005_signedbyaa.nb0
inflating: radio.img
inflating: rcdata.img
inflating: recovery.img
inflating: wcnss.img
[[email protected] 0]#
[[email protected] 0]# md5sum *
0746b4f96db3631b0805da251c988e9f android-info.txt
e83588964ca99dba369e4d350d2552df boot.img
dacc8eab2f1a565d491fe582567ddb46 firmware.zip
44edc8b0eda79f5499d9dbd2fca7a2e5 hboot_ville_1.14.0005_signedbyaa.nb0
6d03e5be9cbdfe456dbcbb64cf0fea61 radio.img
f2d2d61f58a9f41324303c1362101cdb rcdata.img
4a4e3d77449a6bf1f2d8b9ee5a214424 recovery.img
1490d5147aa788c604135177f6017225 wcnss.img
[[email protected] 0]#
radio.img
Code:
# mount -o loop -t vfat radio.img /mnt
# ls /mnt
image MODEM.B02 MODEM.B07 MODEM_F1.B03 MODEM_F1.B07 MODEM_F1.B13 MODEM_F1.B23 MODEM_F1.MDT MODEM_F2.B03 MODEM_F2.B07 MODEM_F2.B13 MODEM_F2.B23 MODEM_F2.MDT
MDATA.CFG MODEM.B03 MODEM_F1.B00 MODEM_F1.B04 MODEM_F1.B08 MODEM_F1.B14 MODEM_F1.B25 MODEM_F2.B00 MODEM_F2.B04 MODEM_F2.B08 MODEM_F2.B14 MODEM_F2.B25 MODEM.MDT
MODEM.B00 MODEM.B04 MODEM_F1.B01 MODEM_F1.B05 MODEM_F1.B09 MODEM_F1.B21 MODEM_F1.B26 MODEM_F2.B01 MODEM_F2.B05 MODEM_F2.B09 MODEM_F2.B21 MODEM_F2.B26 RADIOVER.CFG
MODEM.B01 MODEM.B06 MODEM_F1.B02 MODEM_F1.B06 MODEM_F1.B10 MODEM_F1.B22 MODEM_F1.B29 MODEM_F2.B02 MODEM_F2.B06 MODEM_F2.B10 MODEM_F2.B22 MODEM_F2.B29
# md5sum /mnt/*
md5sum: /mnt/image: Is a directory
ed3fb5a6d4e06115f733746910c7331e /mnt/MDATA.CFG
4212f211660f904e776a7147ebc714bf /mnt/MODEM.B00
0a970960db74b24e07833fef35596993 /mnt/MODEM.B01
2b334560d8a48745050b6aee310cd490 /mnt/MODEM.B02
6ef98608f2e49fb55f72f4da5932089f /mnt/MODEM.B03
66557b0d0e160a9ed2f045cd3c1f6073 /mnt/MODEM.B04
fb37367e92d6c0188023beb387727ec0 /mnt/MODEM.B06
a2fe203af2ab82d9c182fadf059a873e /mnt/MODEM.B07
0cade6f85876909eaa856780f6e64268 /mnt/MODEM_F1.B00
751581083c77ff0374d44ea427d617ed /mnt/MODEM_F1.B01
6a210a29e843676eaf3e2c276773e606 /mnt/MODEM_F1.B02
98dbb06c42244a4275be4cb4e5bf324c /mnt/MODEM_F1.B03
d2977aadbad2986ae720afb08b56225b /mnt/MODEM_F1.B04
5b9a53d96b3852e23b8e14a932bb8e8c /mnt/MODEM_F1.B05
bae565bc385845e730347df331491051 /mnt/MODEM_F1.B06
71f4f900263c1c96f57fe73531cf442c /mnt/MODEM_F1.B07
6a8bf382be3d2df8fda0726e0bbb7fc7 /mnt/MODEM_F1.B08
5b4f2e5595431849e34118117f59304a /mnt/MODEM_F1.B09
1b78d37f8627c507d0a4f23c51b53f7c /mnt/MODEM_F1.B10
32cfa9bb441dc99750974cafc4ca234b /mnt/MODEM_F1.B13
447c1fca37c202e05330d243332f2b0d /mnt/MODEM_F1.B14
30a9d6a8f45597faa2288a3432cd7010 /mnt/MODEM_F1.B21
68d73ba97e2a7a440c97e16b3a9ed000 /mnt/MODEM_F1.B22
a55506862be5096d3c4250d4877ecb2b /mnt/MODEM_F1.B23
f8e80ec79567444666247cf12d68d5a4 /mnt/MODEM_F1.B25
6ff79aaa14e2b4ff96469cc72a108273 /mnt/MODEM_F1.B26
9b5345cc6516022fcea4691dfc7e772b /mnt/MODEM_F1.B29
9713a6578b15dcc6f59fb7ae467f7885 /mnt/MODEM_F1.MDT
1a25e70d6932eb7b0b3e302a26205244 /mnt/MODEM_F2.B00
f92ce637cec4935a95ec9781e6d4148f /mnt/MODEM_F2.B01
1652c79ef509d46816f85feedf35ee53 /mnt/MODEM_F2.B02
976aeaf87b1745ba7f322c5310a2e83c /mnt/MODEM_F2.B03
62ed3b9cb754ee3e0858cf32725fb042 /mnt/MODEM_F2.B04
dcaa38b7abbb04a7acf3d18e7b81f59e /mnt/MODEM_F2.B05
bae565bc385845e730347df331491051 /mnt/MODEM_F2.B06
71f4f900263c1c96f57fe73531cf442c /mnt/MODEM_F2.B07
94f8992326d2f7efae06f350f39f81d9 /mnt/MODEM_F2.B08
008083cfe601a50799bf49c86aead6c2 /mnt/MODEM_F2.B09
c172a002e426e8eb536367968b535988 /mnt/MODEM_F2.B10
3abc99ee5f821779f711a339dc5e4471 /mnt/MODEM_F2.B13
193ca32e6a5aa2e6d5c872e5f9548b68 /mnt/MODEM_F2.B14
30c5c776c548057546556f005b3112bd /mnt/MODEM_F2.B21
68d73ba97e2a7a440c97e16b3a9ed000 /mnt/MODEM_F2.B22
d9045d31a4b937ab1e58451212a13ea6 /mnt/MODEM_F2.B23
f8e80ec79567444666247cf12d68d5a4 /mnt/MODEM_F2.B25
be3c7b59f71be2221618c8d12e619843 /mnt/MODEM_F2.B26
05c5d793d3ebd84fce471abe9cf688f4 /mnt/MODEM_F2.B29
348ded456ea65ef6fef9de30a20847e1 /mnt/MODEM_F2.MDT
ad9b7f8617b17468bb1943797a416572 /mnt/MODEM.MDT
9dcf9d20a505f0567dc0dcf65ff890ac /mnt/RADIOVER.CFG
# cat /mnt/RADIOVER.CFG
SSD:1.13.50.05.25
wcnss:
Code:
# mount -o loop -t vfat wcnss.img /mnt
# ls /mnt
wcnss.b00 wcnss.b01 wcnss.b02 wcnss.b04 wcnss.mdt
# md5sum /mnt/*
84a7472b20e0b3af6453757552c8207d /mnt/wcnss.b00
d6068dc9434a48089033a65e147502e6 /mnt/wcnss.b01
7da2f96f44b8d25686403732da451afc /mnt/wcnss.b02
e4867c182ac1e1409c439a1a329de1cf /mnt/wcnss.b04
c726afbd8bd521af41eecbccb4a070da /mnt/wcnss.mdt
#
No idea on the radio config filesystem format:
PHP:
# strings rcdata.img
QCT_UMTS_RADIO_VER=1
DisH=4
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=24
HSUPACat=6
IMEISVN=17
GEA3=0
AGPSNVSetting=1
QCT_UMTS_RADIO_END=1
#
---------- Post added at 09:25 PM ---------- Previous post was at 09:04 PM ----------
at first I use force, when that doesn't work I use Violence. The Radio @ the bootloader now shows 1.13.50.05.25 ( still tampered and unlocked showing ). The HSDPA data+ (cat16) seems 10-20% faster.
Thanks heaps for posting this too. :good:
PHP:
Boot into recovery (TWRP)
adb into phone and do a "mkdir /sdcard/2fl"
push files to phone:
# adb push radio.img /sdcard/2fl/
3431 KB/s (35169280 bytes in 10.007s)
# adb push rcdata.img /sdcard/2fl/
3 KB/s (141 bytes in 0.042s)
# adb push wcnss.img /sdcard/2fl/
3405 KB/s (5242880 bytes in 1.503s)
adb to phone:
# cd /sdcard/2fl
/sdcard/2fl # dd if=radio.img of=/dev/block/mmcblk0p17
68690+0 records in
68690+0 records out
35169280 bytes (33.5MB) copied, 9.181901 seconds, 3.7MB/s
/sdcard/2fl # dd if=wcnss.img of=/dev/block/mmcblkp19
10240+0 records in
10240+0 records out
5242880 bytes (5.0MB) copied, 0.169724 seconds, 29.5MB/s
/sdcard/2fl # dd if=rcdata.img of=/dev/block/mmcblkp20
0+1 records in
0+1 records out
141 bytes (141B) copied, 0.000336 seconds, 409.8KB/s
This is how to tell the partitions...
/sdcard/2fl # 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: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
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"
/sdcard/2fl #

http://forum.xda-developers.com/showpost.php?p=38298666&postcount=29
http://forum.xda-developers.com/showpost.php?p=38298666&postcount=29 worked like a charm. Only unlocked (and s-off) is now showing.

Shud we update or no ?
Sent from my HTC One S using xda app-developers app

bluebenno said:
I have a TMobile with (downgraded to) hboot 1.06, 1.08ts radio and S-OFF. It did not flash via fastboot, still shows tampered and unlocked after my attempts.
PHP:
mkdir TMP
cd TMP
unzip ../OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.12-2.35.531.7_release_306848u5s8i4b18xs094yw.zip
unzip firmware.zip
# fastboot flash radio radio.img
sending 'radio' (34345 KB)...
OKAY [ 2.980s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 3.013s
# fastboot flash wcnss wcnss.img
sending 'wcnss' (5120 KB)...
OKAY [ 0.715s]
writing 'wcnss'...
FAILED (remote: not allowed)
finished. total time: 0.747s
# fastboot flash radio_config rcdata.img
sending 'radio_config' (0 KB)...
OKAY [ 0.142s]
writing 'radio_config'...
FAILED (remote: not allowed)
finished. total time: 0.175s
For future references, I save all the md5's...
PHP:
# md5sum ../OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.12-2.35.531.7_release_306848u5s8i4b18xs094yw.zip
cca668e517ac0be8306c604e7a43f0e9 ../OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.12-2.35.531.7_release_306848u5s8i4b18xs094yw.zip
Code:
[[email protected] 0]# unzip firmware.zip
Archive: firmware.zip
warning [firmware.zip]: 256 extra bytes at beginning or within zipfile
(attempting to process anyway)
inflating: android-info.txt
inflating: boot.img
inflating: hboot_ville_1.14.0005_signedbyaa.nb0
inflating: radio.img
inflating: rcdata.img
inflating: recovery.img
inflating: wcnss.img
[[email protected] 0]#
[[email protected] 0]# md5sum *
0746b4f96db3631b0805da251c988e9f android-info.txt
e83588964ca99dba369e4d350d2552df boot.img
dacc8eab2f1a565d491fe582567ddb46 firmware.zip
44edc8b0eda79f5499d9dbd2fca7a2e5 hboot_ville_1.14.0005_signedbyaa.nb0
6d03e5be9cbdfe456dbcbb64cf0fea61 radio.img
f2d2d61f58a9f41324303c1362101cdb rcdata.img
4a4e3d77449a6bf1f2d8b9ee5a214424 recovery.img
1490d5147aa788c604135177f6017225 wcnss.img
[[email protected] 0]#
radio.img
Code:
# mount -o loop -t vfat radio.img /mnt
# ls /mnt
image MODEM.B02 MODEM.B07 MODEM_F1.B03 MODEM_F1.B07 MODEM_F1.B13 MODEM_F1.B23 MODEM_F1.MDT MODEM_F2.B03 MODEM_F2.B07 MODEM_F2.B13 MODEM_F2.B23 MODEM_F2.MDT
MDATA.CFG MODEM.B03 MODEM_F1.B00 MODEM_F1.B04 MODEM_F1.B08 MODEM_F1.B14 MODEM_F1.B25 MODEM_F2.B00 MODEM_F2.B04 MODEM_F2.B08 MODEM_F2.B14 MODEM_F2.B25 MODEM.MDT
MODEM.B00 MODEM.B04 MODEM_F1.B01 MODEM_F1.B05 MODEM_F1.B09 MODEM_F1.B21 MODEM_F1.B26 MODEM_F2.B01 MODEM_F2.B05 MODEM_F2.B09 MODEM_F2.B21 MODEM_F2.B26 RADIOVER.CFG
MODEM.B01 MODEM.B06 MODEM_F1.B02 MODEM_F1.B06 MODEM_F1.B10 MODEM_F1.B22 MODEM_F1.B29 MODEM_F2.B02 MODEM_F2.B06 MODEM_F2.B10 MODEM_F2.B22 MODEM_F2.B29
# md5sum /mnt/*
md5sum: /mnt/image: Is a directory
ed3fb5a6d4e06115f733746910c7331e /mnt/MDATA.CFG
4212f211660f904e776a7147ebc714bf /mnt/MODEM.B00
0a970960db74b24e07833fef35596993 /mnt/MODEM.B01
2b334560d8a48745050b6aee310cd490 /mnt/MODEM.B02
6ef98608f2e49fb55f72f4da5932089f /mnt/MODEM.B03
66557b0d0e160a9ed2f045cd3c1f6073 /mnt/MODEM.B04
fb37367e92d6c0188023beb387727ec0 /mnt/MODEM.B06
a2fe203af2ab82d9c182fadf059a873e /mnt/MODEM.B07
0cade6f85876909eaa856780f6e64268 /mnt/MODEM_F1.B00
751581083c77ff0374d44ea427d617ed /mnt/MODEM_F1.B01
6a210a29e843676eaf3e2c276773e606 /mnt/MODEM_F1.B02
98dbb06c42244a4275be4cb4e5bf324c /mnt/MODEM_F1.B03
d2977aadbad2986ae720afb08b56225b /mnt/MODEM_F1.B04
5b9a53d96b3852e23b8e14a932bb8e8c /mnt/MODEM_F1.B05
bae565bc385845e730347df331491051 /mnt/MODEM_F1.B06
71f4f900263c1c96f57fe73531cf442c /mnt/MODEM_F1.B07
6a8bf382be3d2df8fda0726e0bbb7fc7 /mnt/MODEM_F1.B08
5b4f2e5595431849e34118117f59304a /mnt/MODEM_F1.B09
1b78d37f8627c507d0a4f23c51b53f7c /mnt/MODEM_F1.B10
32cfa9bb441dc99750974cafc4ca234b /mnt/MODEM_F1.B13
447c1fca37c202e05330d243332f2b0d /mnt/MODEM_F1.B14
30a9d6a8f45597faa2288a3432cd7010 /mnt/MODEM_F1.B21
68d73ba97e2a7a440c97e16b3a9ed000 /mnt/MODEM_F1.B22
a55506862be5096d3c4250d4877ecb2b /mnt/MODEM_F1.B23
f8e80ec79567444666247cf12d68d5a4 /mnt/MODEM_F1.B25
6ff79aaa14e2b4ff96469cc72a108273 /mnt/MODEM_F1.B26
9b5345cc6516022fcea4691dfc7e772b /mnt/MODEM_F1.B29
9713a6578b15dcc6f59fb7ae467f7885 /mnt/MODEM_F1.MDT
1a25e70d6932eb7b0b3e302a26205244 /mnt/MODEM_F2.B00
f92ce637cec4935a95ec9781e6d4148f /mnt/MODEM_F2.B01
1652c79ef509d46816f85feedf35ee53 /mnt/MODEM_F2.B02
976aeaf87b1745ba7f322c5310a2e83c /mnt/MODEM_F2.B03
62ed3b9cb754ee3e0858cf32725fb042 /mnt/MODEM_F2.B04
dcaa38b7abbb04a7acf3d18e7b81f59e /mnt/MODEM_F2.B05
bae565bc385845e730347df331491051 /mnt/MODEM_F2.B06
71f4f900263c1c96f57fe73531cf442c /mnt/MODEM_F2.B07
94f8992326d2f7efae06f350f39f81d9 /mnt/MODEM_F2.B08
008083cfe601a50799bf49c86aead6c2 /mnt/MODEM_F2.B09
c172a002e426e8eb536367968b535988 /mnt/MODEM_F2.B10
3abc99ee5f821779f711a339dc5e4471 /mnt/MODEM_F2.B13
193ca32e6a5aa2e6d5c872e5f9548b68 /mnt/MODEM_F2.B14
30c5c776c548057546556f005b3112bd /mnt/MODEM_F2.B21
68d73ba97e2a7a440c97e16b3a9ed000 /mnt/MODEM_F2.B22
d9045d31a4b937ab1e58451212a13ea6 /mnt/MODEM_F2.B23
f8e80ec79567444666247cf12d68d5a4 /mnt/MODEM_F2.B25
be3c7b59f71be2221618c8d12e619843 /mnt/MODEM_F2.B26
05c5d793d3ebd84fce471abe9cf688f4 /mnt/MODEM_F2.B29
348ded456ea65ef6fef9de30a20847e1 /mnt/MODEM_F2.MDT
ad9b7f8617b17468bb1943797a416572 /mnt/MODEM.MDT
9dcf9d20a505f0567dc0dcf65ff890ac /mnt/RADIOVER.CFG
# cat /mnt/RADIOVER.CFG
SSD:1.13.50.05.25
wcnss:
Code:
# mount -o loop -t vfat wcnss.img /mnt
# ls /mnt
wcnss.b00 wcnss.b01 wcnss.b02 wcnss.b04 wcnss.mdt
# md5sum /mnt/*
84a7472b20e0b3af6453757552c8207d /mnt/wcnss.b00
d6068dc9434a48089033a65e147502e6 /mnt/wcnss.b01
7da2f96f44b8d25686403732da451afc /mnt/wcnss.b02
e4867c182ac1e1409c439a1a329de1cf /mnt/wcnss.b04
c726afbd8bd521af41eecbccb4a070da /mnt/wcnss.mdt
#
No idea on the radio config filesystem format:
PHP:
# strings rcdata.img
QCT_UMTS_RADIO_VER=1
DisH=4
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=24
HSUPACat=6
IMEISVN=17
GEA3=0
AGPSNVSetting=1
QCT_UMTS_RADIO_END=1
#
---------- Post added at 09:25 PM ---------- Previous post was at 09:04 PM ----------
at first I use force, when that doesn't work I use Violence. The Radio @ the bootloader now shows 1.13.50.05.25 ( still tampered and unlocked showing ). The HSDPA data+ (cat16) seems 10-20% faster.
Thanks heaps for posting this too. :good:
PHP:
Boot into recovery (TWRP)
adb into phone and do a "mkdir /sdcard/2fl"
push files to phone:
# adb push radio.img /sdcard/2fl/
3431 KB/s (35169280 bytes in 10.007s)
# adb push rcdata.img /sdcard/2fl/
3 KB/s (141 bytes in 0.042s)
# adb push wcnss.img /sdcard/2fl/
3405 KB/s (5242880 bytes in 1.503s)
adb to phone:
# cd /sdcard/2fl
/sdcard/2fl # dd if=radio.img of=/dev/block/mmcblk0p17
68690+0 records in
68690+0 records out
35169280 bytes (33.5MB) copied, 9.181901 seconds, 3.7MB/s
/sdcard/2fl # dd if=wcnss.img of=/dev/block/mmcblkp19
10240+0 records in
10240+0 records out
5242880 bytes (5.0MB) copied, 0.169724 seconds, 29.5MB/s
/sdcard/2fl # dd if=rcdata.img of=/dev/block/mmcblkp20
0+1 records in
0+1 records out
141 bytes (141B) copied, 0.000336 seconds, 409.8KB/s
This is how to tell the partitions...
/sdcard/2fl # 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: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
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"
/sdcard/2fl #
Click to expand...
Click to collapse
If you upgrade your hboot to 1.14, it should remove it. Few people have confirmed that if you on lower hboot, you cant remove it. I am on 1.14 and it is removed from mine.

bluebenno said:
PHP:
Boot into recovery (TWRP)
adb into phone and do a "mkdir /sdcard/2fl"
push files to phone:
# adb push radio.img /sdcard/2fl/
3431 KB/s (35169280 bytes in 10.007s)
# adb push rcdata.img /sdcard/2fl/
3 KB/s (141 bytes in 0.042s)
# adb push wcnss.img /sdcard/2fl/
3405 KB/s (5242880 bytes in 1.503s)
adb to phone:
# cd /sdcard/2fl
/sdcard/2fl # dd if=radio.img of=/dev/block/mmcblk0p17
68690+0 records in
68690+0 records out
35169280 bytes (33.5MB) copied, 9.181901 seconds, 3.7MB/s
/sdcard/2fl # dd if=wcnss.img of=/dev/block/mmcblkp19
10240+0 records in
10240+0 records out
5242880 bytes (5.0MB) copied, 0.169724 seconds, 29.5MB/s
/sdcard/2fl # dd if=rcdata.img of=/dev/block/mmcblkp20
0+1 records in
0+1 records out
141 bytes (141B) copied, 0.000336 seconds, 409.8KB/s
This is how to tell the partitions...
/sdcard/2fl # 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: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
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"
/sdcard/2fl #
Click to expand...
Click to collapse
There's a recovery flasher available now. But it does not include rcdata.img. Should I dd that?

[DISCUSSION] Burnt Nand? Get Help

If your phone looks like this:
Well you are at right place!
Method by cute_prince doesnt work at all, what to do?

Can you get into recovery? (TWRP)
If recovery works then just mount system, cache, userdata
Goto Advanced -> Terminal Command and select any start directory
Then type
erase_image system
erase_image cache
erase_image userdata
Now reformat the 3 partitions from recovery and then you can restore your nandroid backup or install a new rom

delete...

Sachin Thomas said:
Can you get into recovery? (TWRP)
If recovery works then just mount system, cache, userdata
Goto Advanced -> Terminal Command and select any start directory
Then type
erase_image system
erase_image cache
erase_image userdata
Now reformat the 3 partitions from recovery and then you can restore your nandroid backup or install a new rom
Click to expand...
Click to collapse
Is this something different? I wiped everything and flashed the rom...

DanceOff said:
Is this something different? I wiped everything and flashed the rom...
Click to expand...
Click to collapse
yes its different but its strange to see this because i used cm9 build 14 with oc for 4 days and dint even burn 1 mb but still recover it dude before further damage

Re: Nand Burnt Totaly
immortal_yash said:
yes its different but its strange to see this because i used cm9 build 14 with oc for 4 days and dint even burn 1 mb but still recover it dude before further damage
Click to expand...
Click to collapse
I almost recovered it.... Still 4.7 mb burnt u guess
Sent from my HTC Explorer A310e using xda premium

Re: Nand Burnt Totaly
immortal_yash said:
yes its different but its strange to see this because i used cm9 build 14 with oc for 4 days and dint even burn 1 mb but still recover it dude before further damage
Click to expand...
Click to collapse
True... To be honest I set the min and max to 800mhz and faced no issues...
Sent from my HTC Explorer A310e

error
I am getting error when typing the commands. the error is like this. mtd: not erasing bad block at 0x something like this.

ex-plorer said:
I am getting error when typing the commands. the error is like this. mtd: not erasing bad block at 0x something like this.
Click to expand...
Click to collapse
Are you doing this from recovery? And which command is giving error?

thanks
system and user data is giving me errors. i dont know i followed the cute prince guide but my phone is having the problem.

Try doing a factory reset from bootloader

any other guide.
Can you provide any other guide how to do it. i think cute prince guide is missing the mtd1 mtd 3 and other mtds

Remove and reinsert the battery then press vol-down and power to enter HBOOT. Then select factory reset.

did that but again giving me erros

Erasing other mtd's is not necessary because
mtd0 = misc
mtd1 = recovery
mtd2 = boot
mtd3 = system
mtd4 = cache
mtd5 = userdata
mtd6 = devlog

mtd ones.
should i type all the mtds. example
mtd0: 00500000 00020000 "boot"
mtd1: 00600000 00020000 "recovery"
mtd2: 00600000 00020000 "recovery_bak"
mtd3: 00040000 00020000 "LogFilter"
mtd4: 00300000 00020000 "oem_log"
mtd5: 00100000 00020000 "splash"
mtd6: 10400000 00020000 "system"
mtd7: 08c00000 00020000 "userdata"
cute prince is flashing the mtd2 , 4,5.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
is it dangerous to remove all other ones.
than what should i do.
oops my one is not correct.

ex-plorer said:
should i type all the mtds. example
mtd0: 00500000 00020000 "boot"
mtd1: 00600000 00020000 "recovery"
mtd2: 00600000 00020000 "recovery_bak"
mtd3: 00040000 00020000 "LogFilter"
mtd4: 00300000 00020000 "oem_log"
mtd5: 00100000 00020000 "splash"
mtd6: 10400000 00020000 "system"
mtd7: 08c00000 00020000 "userdata"
cute prince is flashing the mtd2 , 4,5.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
is it dangerous to remove all other ones.
than what should i do.
oops my one is not correct.
Click to expand...
Click to collapse
They are different for different devices. splash, oem_log etc are not accessible on our device
Type cat /proc/mtd in adb shell to know the correct names

so what should i do now.
what should i do know what is the problem i dont get it. is is dangeruos to remove all other ones.
ps
i think i should remove the -N command.
-n write without first erasing the blocks

ex-plorer said:
what should i do know what is the problem i dont get it. is is dangeruos to remove all other ones.
ps
i think i should remove the -N command.
-n write without first erasing the blocks
Click to expand...
Click to collapse
boot,system,cache and userdata can be safely erased. Erasing misc is dangerous

what about.
what about -N command
is that necessary

[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?