Related
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
NOTICE: MY DROPBOX ACCOUNT SHARING FUNCTIONALITY IS DISABLED DUE TO EXCESS TRAFFIC
POST YOU EMAIL ID IN COMMECTS ILL SEND SHARE MY ROM FOLDER
ROM SECTION
STOCK ROM 2.3.4
1. bloatware removed
2. deodex (for easy theme)
CUSTOM ROMs SECTION
SHOT_V-1 2.3.4
1. deodexed
2. bloatwares removed
3. a2sd support
4. various build property tweaks
5. various inti.d scripts ( loopy smoothness, Cleaning script, Sqlite optimizer ..etc )
6. zipaligned
7. disabled verify bit-code for more free ram
8. bravia image engine (doesn't feel any difference)
9. beats audio libs
10. sony xperia launcher
RECOVERY IMAGES
newrecovery.img = working version ( PORTED BY ME )
pls test and verify
recovery.img = stock version
RECOVERY FLASHING INSTRUCTION
download mobile uncle tool
install it
now copy recovery.img to your sd card
open mobile uncle tool and select flash recovery option
now browse to recovery image and select it
you are done
check out 2.3.5 update at http://forum.xda-developers.com/showthread.php?p=26406717
HOW TO ENABLE A2SD
download A2SD UPDATE.ZIP
apply by cwm recovery
phone may take 2-3 restart (at least in my case)
credits to yuweng for editing init.rc i had just replace kernel
More info about our device is HERE
HOW TO ROOT
Download spice-mi350 drivers from spice site
Unzip the contents
Enable USB debugging on your device in Settings > Applications > Development.
Connect your MI-280 to your computer via USB cale
goto device manager and look for "?" mark appear next to the name Spice mi280
right click on this and update driver and choose manual installation and point to the source as the folder created in step 2
now the driver will get installed. this may take 5-10 minutes.
now download gingerbreak.rar
and click on runme.bat
allow it to complete and you are done
HIT THANX IF YOU ARE HELPED
HOW TO DUMP ROM
then after rooting your device go to terminal emulator
and type
cat proc/mtd
now a list came something like
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00300000 00020000 "nvran"
mtd3: 00020000 00020000 "secconfg"
mtd4: 00060000 00020000 "uboot"
mtd5: 00600000 00020000 "boot"
mtd6: 00600000 00020000 "recovery"
mtd7: 00120000 00020000 "secstatic"
mtd8: 00060000 00020000 "misc"
mtd9: 00300000 00020000 "logo"
mtd10: 000a0000 00020000 "expdb"
mtd11: 00fa00000 00020000 "system"
mtd12: 03c00000 00020000 "cache"
mtd13: 0aa20000 00020000 "userdata"
now to backup anything from above you need to type(follow below format)
su
dd if=/dev/mtd/mtd6 of=/sdcard/recovery.img bs=4096
_____________mtd(no.)________(name ).img________
cannot Root spice MI280
i still cannot Root spice MI280,my computer is not showing ?' under other devices,nor it installs android_winusb.
pl. help
ayubgamim said:
i still cannot Root spice MI280,my computer is not showing ?' under other devices,nor it installs android_winusb.
pl. help
Click to expand...
Click to collapse
connect your phone and then check
then must be a yellow mark on spice mi280 in device manager
if it isn't then uninstall previous driver
Please Help
Can you help me ?
Please do these for me (On Spice Mi 280)
Got to Root Explorer
And then go to system
then click app
then click Mount as R/W on the top
then find and copy Phone.apk and paste it in your sd card
then find and copy phone.odex and paste it in your sd card
then find and copy telephonyprovider.apk and paste it in your sd card
then find and copy telephonyprovider.odex and paste it into your sd card
And then please mail me these files
Thanks in advance !
Tech.Lover said:
Can you help me ?
Please do these for me (On Spice Mi 280)
Got to Root Explorer
And then go to system
then click app
then click Mount as R/W on the top
then find and copy Phone.apk and paste it in your sd card
then find and copy phone.odex and paste it in your sd card
then find and copy telephonyprovider.apk and paste it in your sd card
then find and copy telephonyprovider.odex and paste it into your sd card
And then please mail me these files
Thanks in advance !
Click to expand...
Click to collapse
below is attached file
spice mi-280
hi
please someone make custom recovery for
spice mi-280
Thanks
in advance
somebody pls upload stock rom of spice mi280
unfortunately i had bricked my spice mi280 while deodexing it
backup tool andd instruction are at
http://forum.xda-developers.com/showthread.php?t=1528414
Hmm....
Seems another Indian android phone.
Indiedevers already support mmx A60,A70,A85.
Maybe we will support your too
I need some information
1. Is it rooted?
2. Any custom ROM yet?(I know u people don't have a custom recovery but we are here for that )
Sent from my Micromax_A70 using Tapatalk 2
varun.chitre15 said:
Hmm....
Seems another Indian android phone.
Indiedevers already support mmx A60,A70,A85.
Maybe we will support your too
I need some information
1. Is it rooted?
2. Any custom ROM yet?(I know u people don't have a custom recovery but we are here for that )
2
Click to expand...
Click to collapse
1 yes it is rooted
2 no we dont have custom rom and custom recovery
Ok how many of u have Mi-280?
Will be making a new all in one thread as I need some info from u Guys.
Will put the link here when new thread is created
Sent from my Micromax_A70 using Tapatalk 2
Plz make a custom ROM for Spice MI 280
Join this group by us
Indiedevers™-Spice Mi-280
Here the development will proceed little faster
Try to gather as many users of Mi-280 there
Regards
Want a modded recovery for your phone-mi 280??? give me your stock recovery.img and what you got after typing,
cat proc/mtd
In terminal emulator.....
Can i use data provided in 1st page??!
I ported one for mi-270!!!
Hi there,
Below is the listing of proc/mtd. Can you help me how to do it so that I can experiment from my side as well?
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00300000 00020000 "nvram"
mtd3: 00020000 00020000 "seccnfg"
mtd4: 00060000 00020000 "uboot"
mtd5: 00600000 00020000 "boot"
mtd6: 00600000 00020000 "recovery"
mtd7: 00120000 00020000 "secstatic"
mtd8: 00060000 00020000 "misc"
mtd9: 00300000 00020000 "logo"
mtd10: 000a0000 00020000 "expdb"
mtd11: 0fa00000 00020000 "system"
mtd12: 03c00000 00020000 "cache"
mtd13: 0aa20000 00020000 "userdata"
(Sorry copy paste on mobile spoiled text)
The recovery image is posted in the facebook group that varun has posted in above indiedevers link
Sent from my Spice Mi280 using XDA
kkc.balaji said:
dev: size erasesize name mtd0: 00040000 00020000 "preloader" mtd1: 000c0000 00020000 "dsp_bl" mtd2: 00300000 00020000 "nvram" mtd3: 00020000 00020000 "seccnfg" mtd4: 00060000 00020000 "uboot" mtd5: 00600000 00020000 "boot" mtd6: 00600000 00020000 "recovery" mtd7: 00120000 00020000 "secstatic" mtd8: 00060000 00020000 "misc" mtd9: 00300000 00020000 "logo" mtd10: 000a0000 00020000 "expdb" mtd11: 0fa00000 00020000 "system" mtd12: 03c00000 00020000 "cache" mtd13: 0aa20000 00020000 "userdata"
Sent from my Spice Mi280 using XDA
Click to expand...
Click to collapse
This looks annoying.........please post like the one in first page..............!
Well, I guess that's not necessary anymore
I have done it
@everyone
Join the group
Burned from my laser torch using pencil cells
varun.chitre15 said:
Well, I guess that's not necessary anymore
I have done it
@everyone
Join the group
Burned from my laser torch using pencil cells
Click to expand...
Click to collapse
Can you upload it...or any screen shot ?
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
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?
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