yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] bongostl:
Yes--thank you everyone...I am already aware of the many ways to get into recovery.

The issue is getting into recovery in a situation where you can't fully boot into android (boot loop, etc...)

In such cases, it is really nice to be able to select recovery from the bootloader.

However, right now I need to be near a computer so I can flash the recovery all over again
[Galaxy S II Q&A, Help & Troubleshooting] funkyirishman:
Question is in the title.

Using latest Litening Rom with litening kernel.

Every time I post a status update FB crashes?

Reinstalled & same thing only happened recently removed app that recently installed & same issue

At a loss as to what is causing this?

Any suggestions?

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] Deleted member 4038153:
android-support@fb.com
[Galaxy S II Q&A, Help & Troubleshooting] Immortalis:
Use other Facebook client or use mobile web version.
[Galaxy S II Q&A, Help & Troubleshooting] saywhatt:
Facebook bug.. i can't even post photos :p
[Galaxy S II Q&A, Help & Troubleshooting] AlamVasquez:
I had the same issue with some apps when i was testing some ROMs, i realized that the ROM had the bugs, try an other ROM
[Galaxy S II Q&A, Help & Troubleshooting] jantonio23:
I had this problem and found out that it was due to bad date and time settings.

What I did was to untick the network auto time sync and changed my GMT settings.

I cleared the cache and data via manage app then find facebook. I then reboot to recovery then wiped the cache and dalvik cache.. bam! It is working fine now.
[Miscellaneous Android Development] balamu96m:
Nice one bro.....will be helpful for many.......!!:good:

Good to see you back......!

--------------------

P.S: Thinking of creating a Multi-tool for MTK6573.......what are features that can be added bro ??
[Miscellaneous Android Development] yuweng:
Yo, Bala bro, been quite busy with work, until now only manage to finish this tut... :o

Yeah, i was thinking about that too, to mod dsixda's android kitchen just for MT6573 platform that includes Bruno Martins's unpack/ repack boot.img, unpack/ repack recovery & port it to CWMR like this tut, replace a2sd with data2ext or ad2sdx; only this two mod stable on MT6573 platform so far that i have tested...

actually did try but give up half way as my scripting skill is still at novice level... :o

did read it on some other forum that someone is actually doing that too but i never see it got release though...:p

Well i guess we need dsixda expertise to be able to do that but he is retired now...

Added on Sept 04, 2012

Info Update

Dark Tremor's a2sd/ Apps2sd works well on MT6573 platform after all... :o

i was using the last version 2.7.5.3 Beta 04 all this while & i always use a2sd datasd all the time & it FC all apps after a few weeks of using/ sometimes a few days even after a fresh install...

After all, DT_a2sd/ apps2sd is actually apps to sd & i always push it as data2sd... :o

Only until recently that i play with Android Kitchen, use it to extract my system.img & update it with its built-in Darktremor Apps2SD version 2.7.5.2, it works extremely well because 2.7.5.2 doesn't support a2sd datasd feature...

So guys, if you are using DT_a2sd beta 4, don't use the command a2sd data2sd instead use a2sd cachesd...

You can checkout my other post here
[Miscellaneous Android Development] y2yu:
great tools and description
[Miscellaneous Android Development] yuweng:
hello y2yu,

Glad you find it informative... :D

According to this site, there will be another 2 new cpu after MT6575/ MT6577... (use google chrome for translation)

This means MT6573 is 5 generation behind MT6588 & it is still unexploit with all info/ tools scattered all over the web...

Thats where i decided to compile all these info & put it here... :good:

Now that i check, i've bought my first mediatek back in 2008...( never knew it until i check it just now ) :silly: It has serve me well for almost 2 years in spite of dropping, a few times from 8 feet height when i was on a ladder & it still works ! It was the last drop that spoilt the mic & render it unuseful. It can still make & receive call to date but the other side can't hear what i say... :o

At that time, made in china phone was famous for its extra loud speaker/ ringtone but doesn't support android back then...

haha, enough of history, have you manage to port CWMR to your MT6573 ? In fact, i have manage to create a plugin for dsixda's Android Kitchen which can port CWMR to any MT6573 with a few copy & paste features just like Android Kitchen... :good:

Still testing it, may be you would like to be the first beta tester... :confused:
[Miscellaneous Android Development] jason_cheng:
Thank you so much for this. I managed to "port" cwmr to my phone without going through the build hassle. Thanks also go to koush for the builder. I had downloaded the source but hadn't managed to completely set up my build environment as there are a couple of gotchas to iron out for ROM development.

Anyway, this serves as a good precursor to actually porting a custom recovery to new devices. Just one problem - cwmr does not recognise any of the hardware buttons for the select action. I can only scroll. The phone has 2 side buttons for volume control, 1 power button on top, and at the bottom on the home row there is a home button, the menu (these 2 also scroll, in stock recovery the home button selects), the previous, and the search. [1][2]

Do you happen to have any cure for this? Is there some place I could remap hardware buttons? One more thing. I made sure root shell access was configured but adb shell will not work (insufficient permissions). Also, adb devices, as is the case for stock recovery, will return question marks. Any idea?

edit: It is important to mention that the flashing had some errors:

/mnt/sdcard # flash_image recovery recovery.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: recovery successfully wrote block at 0x00000000
mtd: recovery successfully wrote block at 0x00020000
mtd: recovery successfully wrote block at 0x00040000
mtd: recovery successfully wrote block at 0x00060000
... <snip>
... <snip>
... <snip>
mtd: recovery successfully wrote block at 0x00420000
mtd: recovery successfully wrote block at 0x00000000

The flash of the stock recovery goes without any error.

[1] http://symphony-mobile.com/index.php?route=product/product&path=63&product_id=75

[2] http://www.tinno.com/en/productinfo.aspx?proid=128
[Miscellaneous Android Development] yuweng:
u r most welcome, jason... :D

i think the button key map is actually built inside /sbin/recovery so there is nothing much you can do about it unless you build the whole recovery from sources & change it from there...

i do have feedback from fellow xda member that has the same problem flashing recovery with error however he reported back, all menu options at cwm works fine...why don't you use mobileuncle tools, its easier that way...found another flashing tool for ZTE, reported unknown image but it works fine on MT6573 platform too...

As for the adb shell at cwmr, it should work by default & if it doesn't then you have the check default.prop & make sure ro.secure=0 As for stock recovery, mine doesn't work at all... :p

i think after 6.0.0.3 version, ported cwmr has the camera button as enter key for MT6573 if you built it from koush builder...
[Miscellaneous Android Development] jason_cheng:
Crap, then I have to dig through the sources really hard. This phone has no camera button.

If I'm not wrong the last time I checked "mobileuncletools" uses flash_image. Either that, or nandwrite, or failing that, dd. Coming from a Linux and UNIX background I'm more comfortable with the simpler underlying commands rather than a complex front-end wrapper around those commands. NAND images have some peculiarities so we kinda have to deal with it I guess.

I had triple-checked that ro.secure != 1 :P I think this is probably a hardware issue where during recovery there is no bridging interface exposed.

Anyway a couple of other things related to the documentation side of this:

* Why not just upload your own recovery.fstab to the builder instead of editing it later?

* Changing the fstab is only needed for those who have an ext-sd, i.e. a second partition for the memory card

* The bin/ folder is empty, and the lib/ folder only contains the ext2 module, so if above not needed, this is also not needed

So in the end, I think we can simply advocate use of the builder as-is. What do you think of putting up a list/database of MTK phones and some details? Like rootable or not, cwmr available or not, etc. I think RootzWiki would be a good place for that?
[Miscellaneous Android Development] yuweng:
AFAIK, most readers at xda are non-registered, only when they are stuck somewhere or they really needed help then only they'll register & start posting; that is including me ! :o

You can see my other post where it is nearing to 300 over downloads while the MTK phones list feedback from users is less than 10 ! :o

AFAIK, all MT6573 are root-able & all needs data2sd mod. There are so many apps & games at google play, MT6573's 256 or 512MB internal memory gets filled up pretty fast !

On adb shell, did you have all the three adb files (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll) & on linux, i use ./adb shell to get it to work...
[Miscellaneous Android Development] jason_cheng:
Very true.

Indeed. I actually want to try just bind-mounting data to a second partition, but I don't know whether init scripts are supported on this phone (would be better instead of editing the init itself). But I will also try this data2sd mod, haven't looked at it yet. After clearing out loads of preincluded apps I was happy for a while, but am now running out of space again!

Actually I have the Android SDK set up already on my system, so everything is conveniently there including adb. I will have to find some other day to troubleshoot why the bridge would not work during recovery.
[Miscellaneous Android Development] breaky9973:
re-packing error

Now I am doing this on Xubuntu so maybe that's why it doesn't work:

I get the following when trying to repack:

MTK-Tools by Bruno Martins

MT65xx repack script (last update: 31-07-2012)

Repacking recovery image...

Ramdisk size: gzip: unpack/ramdisk-repack.cpio.gz: No such file or directory

Could not open ramdisk file: ramdisk-repack.cpio.gz

Any ideas?

Unpacking is no problem.
[Miscellaneous Android Development] yuweng:
This Android Kitchen plugins only work with cygwin... :o

Even unpacking shouldn't have work because mkbootimg & 7z is windows exe...

i'm in the mid of modding it so that it can work on linux too... :D
[Miscellaneous Android Development] breaky9973:
Thanks for your reply yuweng. 7z is available as a plugin for Ubuntu too.

In the mean time I will try another website which I already posted a link before.

http://www.slatedroid.com/topic/32450-how-to-unpack-repack-systemimg-properly-using-linux/
[Miscellaneous Android Development] jason_cheng:
It will work on any GNU/Linux as long as you have the proper tools installed. Almost all tutorials for Android "modding" are Cygwin-based, which basically emulates a GNU system on Windows (so you can skip all parts about "setting up" anything). Here your file does not exist, please double-check that it does. This is a perl script which utilizes gzip, gunzip, and cpio. Make sure these are available as well.

Btw, this is independent of Android Kitchen. You don't need that if you're using the builder. Android Kitchen is just a front-end to modifying ROMs. So skip the Kitchen for now and do this manually.

Again, the "another website" you link to is about backing up real filesystems (which the boot and recovery partitions are not). See: http://xdaforums.com/showthread.php?t=1744265&page=2

yuweng: What benefit does using the Android Kitchen have over simply using the builder? All you need is a rebuilt /sbin/recovery along with the resources in /res, and optionally an ext2.ko if it does not exist on the phone itself.
[Miscellaneous Android Development] yuweng:
This is just a simple tool for n00b/ newbie...

i was a n00b six months ago & even now my android knowledge is still half empty... :D

As the first post says, there are hundreds if not thousands of android phone based on MT6573 SoC design, each with their own recovery.img-kernel.img & AFAIK, non is compatible for use on others...

i simply provided a plugins based on Android Kitchen so that even a n00b/ newbie can port cwmr to their MT6573 simply by just drag & drop files to it... You are a programmer by profession i presume, so this is chicken feet to you but to a n00b/ newbie they don't no even where to start, like i did... :laugh:

you'll be surprise if i tell you the top download of my tuts is rooting & installing busybox !

As for the builder, you still need to unpack it, copy few files over & repack it with bgcngm's MTK-tools for it to work on MT6573...not alot of n00b/ newbie know how to do that ! :D

the intention of this plugins is to be able to port cwmr to any mt6573 based android phone...
[Miscellaneous Android Development] jason_cheng:
yuweng, and I thought you were the programmer! :D (other than bgcngm I see you as our local MTK expert)

Seriously, we are all noobs. That was my main concern :silly: Android Kitchen interface is command-based whereas the builder you just need to upload an image and you will get an image in return.

So do you mean using Android Kitchen there is no need to go through setting up Cygwin, repack, unpack, etc.? Just download the Kitchen, enter some commands, and you will have a recovery.img which you can flash directly?
[Miscellaneous Android Development] yuweng:
i'm a half-cook programmer... :D

yaya, but you need to setup java, Android Kitchen & the plugins scripts will do everything... :laugh: That is for linux...For windows, you already know... :o

As for the builder, it works on major brands where it can be flash directly but not on mt65xx...
[Miscellaneous Android Development] jason_cheng:
Ahh OK in that case I do suppose the Kitchen would be much simpler.

Ya, the MTK partitions and images are not the same as those of other devices. That's why Bruno wrote the script to help us :)
[Miscellaneous Android Development] breaky9973:
Hi Jason,

I have cpio and can execute perl scripts. gzip and gunzip are setup too. The script just cannot find the file ramdisk-repack.cpio.gz and I cannot find it anywhere.

Maybe the dump of the recovery.img was not good. I will try again.
[Miscellaneous Android Development] breaky9973:
*UPDATE*

The mkbootimg executabe I download was not correctly installed. Now the script finishes without error.

However the recovery.img doesn't do anything. I think I have to look for another mkbootimg or compile one from source myself...

For people who are interested to try the Ubuntu way:

Unpacking:

sudo perl ./unpack-MT65xx.pl recovery.img

Re-packing:

sudo perl ./repack-MT65xx.pl -recovery ./recovery.img-kernel.img ./recovery.img-ramdisk ./recovery.img

I will attach the mkbootimg once I succeed :)
[Miscellaneous Android Development] iVolcaNoz:
really thanks for your reply...but i really don't know how to do it..this is what i done..

i copy the recovery.img into the folder u gave me for cwm..

then i drag the recovery.img and drop to cwmr_6028 bat file..

it runs..then i select my device that is mtk6575 with emmc and press enter..

then i just error..just like the screenshot i attached..

PS: my father bought this brand-less note 2 clone in china and totally get scam..

the built-in antutu is hacked and it showed 20000 score for antutu test ==

and the properties show that it has 1g of ram..720p screen resolution with mt6589 processor ==

But all of them are fake..the real specs are..

- 5.3' screen

-jelly bean (it writes 4.1.1 but i dont know whether is real or not)

-480x 854 screen res

-512 ram

-mtk6575

can you help me to find which model is this?

i had found all over google and chinse forum for mtk(i m chinese)

still cant found a similar specs device like this..sry for making problems..
[Miscellaneous Android Development] yuweng:
To check your CPU -> adb shell -> cat /proc/cpuinfo -> HARDWARE : MT657X

To check type of partition -> adb shell -> cat /proc/dumchar_info if there is info meaning you got emmc or cat /proc/mtd meaning you got mtd partition

There has been many cases that they downgrade the CPU to MT6575 as there are confirmed cases here... :D

Upload your recovery.img & i'll have a look at it... :o Mean while backup you Factory ROM using this tut here before trying any mod or you'll might end up here... :cool:
[Miscellaneous Android Development] BHARDIK:
awesome info dear thank you so much again.....:):thumbup::thumbup:
[Miscellaneous Android Development] iVolcaNoz:
thanks for the advice..

the recovery.img i attached is taken from my backup through the backup progress in mtk droid tools..

i dont know whether can take from there or not..or u might tell me where to get the correct recovery.img..

thanks..
[Miscellaneous Android Development] ynj:
any idea on how to to create the recovery for N7100 clone for mtk 6575 platform for the cwm .i cant seems to get it done..besides i think i deleted my stock recovery.
[Miscellaneous Android Development] yuweng:
bro, upload your stock recovery here, how to port then... :rolleyes:
[Miscellaneous Android Development] ynj:
the problem is this my stock recovery went missing cannot be booted..

i think 1 recovery here..this.
[Miscellaneous Android Development] 2x1:
CWMR 6028 for Zhou Xing i9300 ported

Thanks, yuweng

Regarding your first link, I already ported TWRP 2.4.2 ;)

2nd link: I have now ported CWMR 6028 for the Zhou Xing i9300 as well. You can find it at the same location as the TWRP port.

I preferred the TWRP version as it is a touch recovery (particularly handy since my volume up and down keys are not working any more). However, after porting CWMR and having a go at it, by chance I actually noticed that the Home key also works as the volume up key. Therefore... I can move around the menus, only in one direction, but hey, that's better than nothing!

Thanks again, my friend :)
[Miscellaneous Android Development] Johnbalz:
CWM Port to Goo phone i5 MT6575 Display 854 x 480

Hi guys is there a working CWM port for Goo phone MT6575 ARMv7 2000MHz Display 480x854 if there is not could some

one port it over to my device please will give donations also I am looking for a compatible rom thank you and please reply
[Miscellaneous Android Development] 2x1:
I ran into some problems with my first port as well. It seems that long paths can mess the process. Try this:

- Extract the zip file with Mitchfood's tool at C: root (that is, just C: root, not on desktop).

- DO NOT put the recovery.img from your stock ROM inside the Mitchfood folder (It can be anywhere else, e.g. your desktop).

- Open two windows side by side, one where you can see the Mitchfood files extracted and one wherever you have your original recovery.

- Drag the original recovery and drop it onto cwmr_6028.bat

Good luck!

[EDIT] I downloaded the Recovery file you attached to your message (#184) and I had a go myself at porting it. It worked just fine. Here is your cwmr_6028 port :)
[Miscellaneous Android Development] 2x1:
I do not mind making the port for you. Please attach your original recovery.img file, confirm what partition system your phone has and what Recovery would you like (CWMR or TWRP).

Below instructions from yuweng to find out your partition system:

As to the donations, head to operation RMD where you will find the details to support all these wonderful guys who develop the tools and share them with us. Hat off to them!
[Miscellaneous Android Development] Johnbalz:
Porting CWM to MT6575!

If you could port that to my phone i would appreciate it I havn`t got the orignal recovery image file is there a way you can still port it i would rather a CWM Recovery and how do i check the partion can it be done through terminal emulater or i have to run adb through command prompt on the adroid sdk please reply thank you
[Miscellaneous Android Development] 2x1:
First, I need the original Recovery.img file.

Try getting it with MTK Droid Tools. Here is the original thread by Master Rua1. Please read the few lines on how to use it if you have never done it, and do not forget to hit his "Thanks" button.

Secondly, I need to know what phone you have (MT6577 or MT6575).

If it is an MT6575 phone I also need to know what partition type is (emmc or mtd). This is done through a terminal window (under Windows, just run cmd) and navigate (

CD

) to wherever you have the ADB installed. If you have not renamed the folder, it should be something like android-sdk-windows/platform-tools or under android-sdk-windows//tools. Rest of the instructions from Yuweng supplied in my last post (#191).

[EDIT]

I have had a look at your posts and I have seen that there is a bunch of contradictory info in the System details from your phone. So the most reliable data should be whatever ADB returns.

Before connecting the phone to the PC, Make sure first that you have ticked USB debug option on your phone (Settings > Developers Options)

In case it is not clear yet, here is a step-by-step with screenshots to get the info.

1) Open a browser window and check where the SDK is installed on your PC. Navigate to "Platform-Tools" folder as this is where "adb.exe" should be (in older versions it was under "Tools" folder).

2) Select the path in the address bar leaving out the drive letter, the colon and the back-slash.

3) Right click and "Copy" the path.

4) Start > Run, and type "cmd" to open a terminal window.

5) Navigate to C: root (typing "cd.." as many times as needed until you are at "C:\".

6) Optional: I have the SDK installed on a different partition, so I had to first move to that drive typing "D:". If your SDK is on "C:" just skip this step.

7) Type "cd " (note the space after "cd "), right click and "Paste" the path you just copied.

8) Type "adb shell"

(root@android:/# will be displayed)

9) Type "cat /proc/cpuinfo"

Several lines will appear and among these the processor details.

10) Type "cat /proc/dumchar_info"

Several lines will be displayed and this is where you see your partition details if applicable.

I hope it helps. :)Let us know what you find out.
[Miscellaneous Android Development] mightymouse2045:
Here's a working recovery for the N7100 MTK6575 (SMDK4x12?) Fake exynos or fake MTK i dunno.

Upload it with SP flash tools.
[Miscellaneous Android Development] gusduenas:
help making the port for recovery image for mtk 6575 tablet dual sim dual cameras

I would love to have a recovery rom based on my cwmr ....my phablet is a ed88 ananda mtk 6575 7" phablet with two sim cards 3g and 2g inside bluetooth , gps, fm radio and tv ...let me know what do you need I have the zip with the original installer (rom)

gus
[Miscellaneous Android Development] 2x1:
Please do not take this wrong. Have you even tried doing it yourself? This is what this thread is about. If you come across some problem, we will gladly help. C'mon, try first on your own. Trust me, it is rewarding! :)

Here are a couple of hints:

As to what is needed:

- You need the original "Recovery.img" file. You should find it in the zip file you mention.

- You say your device has an MTK6575 processor, so check out my post #193 since you will also need to find out the partition type.

- To make sure you get the process right, have also a look at my post #190.

Good luck!
[Miscellaneous Android Development] gusduenas:
do you mind to tell me step by step what do I need to do?

I have the recovery.img with me.

Gus
[Miscellaneous Android Development] pratikmore:
on first page,first post of yuweng there are image guides for how to port cwm recovery,lewa recovery and twrp recovery.just go through it.

twrp recovery guide - http://www.mediafire.com/view/?u1zzzkkiz52p79s

cwm with mtd partition - http://www.mediafire.com/view/?1zc473vx18g69bn

cwm 6.0.2.8 with mtd and emmc partition - http://d-h.st/xww