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

[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

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.

[Q] Partition details

Hi all,
does anyone know, where I could find details about the partitions available on SM-P900 (what's in there, what effect might a change to them habe, on which operations might a chnge to them happen, etc.)? I'm trying to figure out, what is necessary to be backed up, so that I'll be able to restore the device even in the worst case of an SW damage.
I.e. I'm trying to understand which partitions need to be restored in what kind of situation. Partitions like boot, recovery, cache, system, hidden, userdata are clear to me, more or less. But what about the others?
I'm not sure, but I think, it's not a question specific to SM-P900, but to all (new Samsung) devices, probably to all KitKat devices.
So far I could figureout following partitions on the SM-P900:
dev size name
mmcblk0p1: 0001000 "bota0"
mmcblk0p2: 0001000 "bota1"
mmcblk0p3: 0005000 "efs"
mmcblk0p4: 0001000 "m9kefs1"
mmcblk0p5: 0001000 "m9kefs2"
mmcblk0p6: 0001000 "m9kefs3"
mmcblk0p7: 0001000 "carrier"
mmcblk0p8: 0002000 "param"
mmcblk0p9: 0002000 "boot"
mmcblk0p10: 0002800 "recovery"
mmcblk0p11: 0002800 "ota"
mmcblk0p12: 0001000 "cdma-radio"
mmcblk0p13: 0005000 "modem"
mmcblk0p14: 0001000 "tombstones"
mmcblk0p15: 0001000 "tdata"
mmcblk0p16: 0003000 "persdata"
mmcblk0p17: 0001000 "reserved2"
mmcblk0p18: 0252000 "system"
mmcblk0p19: 0032000 "cache"
mmcblk0p20: 0005000 "hidden"
mmcblk0p21: 1a74000 "userdata"
Thanks,
bruzzy