yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] fifo171:
That means that your flash counter didn't increase. BTW you flashed ICS? :confused:
[Galaxy Ace II Android Development] tornado92:
Flashing stock factory firmwares wont increase the count rate. ..
[Galaxy Ace II Android Development] Shadowcareful:
Lol :D there is no ics for our phone only Gingetbread (GB) and jeallybean (JB) and yes your falsh counter is normal so no problems :D
[Galaxy Ace II Android Development] any_body:
Ok man, sorry for my mistake... I just try- to say i go Android 4.x the come back Android 2.3.6 :-$
[Galaxy Ace II Android Development] saintetienne:
can't figure this one out , keep coming up with operation aborted status code 7 ,

any one got any ideas .

tia
[Galaxy Ace II Android Development] tofueatsbread:
Which varient do you use?

What firmware are you on?
[Galaxy Ace II Android Development] upilguebu:
You can't use that flashable zip on CM10.1/10.2/11 ( based from my experience xD )
[Galaxy Ace II Android Development] Ryccardo:
Use Triangle Away, it's even easier :)
[Galaxy Ace II Android Development] saintetienne:
Using with Cyanogen 10.2 , after many attempts manged to finally get it to work after using a temp version of cmw , I could get triangle away to work - said it was an incompatible phone.
[Galaxy Ace II Android Development] tofueatsbread:
I used it with gb a few times previously and it actually worked xD
[Galaxy Ace II Android Development] tricampeao23:
This method works in Kitkat (CM 11) of Maclaw?
[Galaxy Ace II Android Development] nshntshrm7:
reset flash counter...

sir, plz tell me a way to reset flash counter in galaxy core duos I 8262....
[Galaxy Ace II Android Development] ayushchauhan:
help..
[Nexus 10 Q&A, Help & Troubleshooting] malikalhaji:
Is it possible for me to install whatsapp on my nexus 10?
[Nexus 10 Q&A, Help & Troubleshooting] Herman76:
I tried transferring it from my Galaxy Nexus, but it kept FC'ing. There is a way to get it working, but i requires root, so I ditched that idea for the time beeing (It involves using Titanium backup to transfer data).
[Nexus 10 Q&A, Help & Troubleshooting] malikalhaji:
My nexus 10 is already rooted, the problem is my my i9100 is faulty and I don't have a backed up titanium available that's why I need to start using my nexus 10
[Nexus 10 Q&A, Help & Troubleshooting] Paincake:
I installed it via their website:

http://www.whatsapp.com/android/current/WhatsApp.apk

On first launch it shows a message, something like "currently not supported on tablets".

After I denied the permission to "read phone identy and state" via srt-appguard I was able to start whatsapp. ("pdroid" or "lbe privacy guard" are maybe alternatives but they didn't work when i bought my nexus 10)

Next problem is that whatsapp needs to send a sms or get the call. This is not possible. You have to get the window where you can type that number you get on your cellphone.

Switching apps to appguard and permitting the right again while having whatsapp still running in background activated it for me.

Before quitting whatsapp I denied "read phone id..." again.

Sounds complicated and it is annoying, for sure but it worked :D

Now I have a backup of whatsappdata and just need to install apk via website, deny permission and get the old data files via titanium backup.

Maybe there is an easier workaround out now:p
[Nexus 10 Q&A, Help & Troubleshooting] malikalhaji:
Tried our method but I keep getting whatsapp has been modified, try getting whatsapp from blah blah blah
[Nexus 10 Q&A, Help & Troubleshooting] malikalhaji:
finally got mine working with root. . . . got it from http://www.android-hilfe.de/asus-ee...whatsapp-auf-tablet-jetzt-auch-ohne-root.html

Download Whatsapp http://www.whatsapp.com/android/current/WhatsApp.apk and LBE Privacy Guard http://dl.dropbox.com/u/37033686/LBE_Security.apk

First install Whatsapp

2nd install LBE Privacy Guard

3rd Open LBE Privacy Guard

- Allow superuser rights

-4 Menu's are there on the next page wipe

-Active Defense Select -> Managing Permission -> All Apps

Whatsapp-search and select

-"Phone ID" click select "Deny" -> "SMS Sending" select (Deny) -> "Phone Call" select (Allow)

4th Open Whatsapp -> Continue and Agree -> Security Warning from LBE accept up (Allow), select your country and input your phone number, get your six digits code sent from whatsapp and input it after the countdown. If LBE wants something always agree.

5th Important: If you have everything set up, then give over LBE Whatsapp all rights again or simply uninstall LBE.
[Nexus 10 Q&A, Help & Troubleshooting] ndirish2001:
Thank you so much for sharing this! It worked perfectly. I still don't know why WhatsApp makes us jump through these hoops.
[Nexus 10 Q&A, Help & Troubleshooting] malikalhaji:
You are welcome, I also have no idea since we still need to verify our number
[Nexus 10 Q&A, Help & Troubleshooting] Dodazza:
Hi, I've tried to do as yousuggest, but as I click on the 'continue' button in whatsup I've a window saying that tablets are not supported.... What I'm missing???

Inviato dal mio Nexus 10 con Tapatalk 2
[Nexus 10 Q&A, Help & Troubleshooting] malikalhaji:
Did u install LBE Security and followed the instructions? Cos it seems u did not
[Nexus 10 Q&A, Help & Troubleshooting] lKBZl:
Does it work on 2 devices? Some people says they can use it on both devices, however I can't, everytime I try to on a different device, tablet or phone, it asks me to verify number, and then it works only on 1 device.
[Nexus 10 Q&A, Help & Troubleshooting] malikalhaji:
Don't think it works on more than 1 device
[Nexus 10 Q&A, Help & Troubleshooting] Dodazza:
Of course I did.... For root permissions I've SuperSu. Is it right for LBE?? Because I've heard that some programs need particular suprr user support....

Inviato dal mio Nexus 10 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] buffo1987:
How to build CWM Recovery

You may also use http://builder.clockworkmod.com/, there you can build touch and non-touch version. Always latest version.

Files needed for this you can find within device files: AriesVE Dev Connection Team github

File location:

/recovery.fstab

/recovery/graphics.c

/recovery/postrecoveryboot.sh

+ any recovery.img, which works on your device​

Manually build CWM (non-touch)

(Base is arco cm9, other possible sources and their included CWM Version second post)

Install android sdk http://developer.android.com/sdk/index.html

Install Java

http://wiki.ubuntuusers.de/Java/Installation/Oracle_Java

Install needed libs (Ubuntu 13.04)

sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev python

Create Directories

$ mkdir -p ~/bin && mkdir -p ~/android/system

Install repo

$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Add "~/bin" to PATH of execution

$ gedit ~/.bashrc

add:

#Android
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin

Initialize Repo & sync

$ cd ~/android/system/
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
$ repo sync

Add device files //possible sources on second post

$ cd ~/android/system/device && mkdir samsung && cd samsung
$ git clone git://github.com/AriesVE-DevCon-TEAM/android_device_samsung_ariesve -b cm-10.1

Add vendor files ////possible sources on second post

$ cd ~/android/system/vendor && mkdir samsung && cd samsung
$ git clone git://github.com/ivendor/android_vendor_samsung_ariesve.git -b jellybean ariesve

Prepare device specific code

$ cd ~/android/system/
$ . build/envsetup.sh
$ lunch //choose -> cm_ariesve-userdebug

Compile recovery

make clobber && make -j[COLOR="Red"]#[/COLOR] recoveryimage //[COLOR="Red"]#[/COLOR] CPU-Cores+1

Credits

DevConnection_Team

arco68

ivendor

cyanogenmod
[Galaxy S Plus I9001 Android Development] buffo1987:
Versions of CWM

https://github.com/CyanogenMod/android_bootable_recovery -> choose branch -> Android.mk -> Version

cm-9.0 -> 5.5.0.4

ics -> 6.0.1.2

jellybean -> 6.0.2.8

cm 10.1 -> 6.0.3.4

Sources for building CWM

CM9

Arco:

Device files

git clone git://github.com/arco/android_device_samsung_ariesve -b ics-2.6 ariesve

git clone git://github.com/arco/android_device_samsung_ariesve -b ics-3.0 ariesve

Vendor files

git clone git://github.com/arco/android_vendor_samsung_ariesve.git -b ics ariesve

Ivendor:

Device files

git clone git://github.com/ivendor/android_device_samsung_ariesve.git -b ics-2.6 ariesve

git clone git://github.com/ivendor/android_device_samsung_ariesve.git -b ics-3.0 ariesve

Vendor files

git clone git://github.com/ivendor/android_vendor_samsung_ariesve.git -b ics ariesve​

CM10

Ivendor:

Device files

git clone git://github.com/ivendor/android_device_samsung_ariesve.git -b jb-2.6 ariesve

git clone git://github.com/ivendor/android_device_samsung_ariesve.git -b jb-3.0 ariesve

Vendor files

git clone git://github.com/ivendor/android_vendor_samsung_ariesve.git -b jellybean ariesve​

CM10.1

blackmamba97:

Device files

git clone git://github.com/blackmamba97/android_device_samsung_ariesve.git -b cm-10.1 ariesve

davidteri91:

Device files

git clone git://github.com/Davidteri/android_device_samsung_ariesve.git -b cm-10.1 ariesve

Vendor files

git clone git://github.com/Davidteri/android_vendor_samsung_ariesve.git -b jellybean ariesve

Xistance:

Device files

git clone git://github.com/xistance21/android_device_samsung_ariesve.git -b jb-3.0 ariesve

Vendor files

git clone git://github.com/xistance21/android_vendor_samsung_ariesve.git -b jellybean ariesve

Doomsday94:

Device files

git clone git://github.com/doomsday94/CyanogenMod-10.1-ariesve.git -b master ariesve​
[Galaxy S Plus I9001 Android Development] buffo1987:
reserved
[Galaxy S Plus I9001 Android Development] anuseb89:
Good work man...now you are our dedicated person for recovery it seems.....
[Galaxy S Plus I9001 Android Development] buffo1987:
I'll do my best :p.

In fact i hope that we can get more stability if more people know how to compile. Especially twrp has some interesting flags e.g. TARGET_PREBUILT_RECOVERY_KERNEL := path/to/kernel -- use to specify a kernel specifically for building recovery.
[Galaxy S Plus I9001 Android Development] XeLLaR*:
I would like to say that you can use CWM 5.5.0.4 for Gingerbread, ICS & Jellybean without any problems. Its more reliable than any other CWM or TWRP we have. :good:

Only the usage of the volume rockers for going up and down in the menü is a little bit annoying and not that good for the device.
[Galaxy S Plus I9001 Android Development] Harshraj:
background wallpaper change

how to change the backgroung wallpaper of my cwm recovery ..??
[Galaxy S Plus I9001 Android Development] miki2o:
R: [GUIDE] Build CWM recovery

Is there a way to manually build a touch version?

Inviato dal mio GT-I8150 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] buffo1987:
AW: [GUIDE] Build CWM recovery

Never thought about that, so i do not know

Noway
[Galaxy S Plus I9001 Android Development] Harshraj:
Please do think about that !!!
[Galaxy S Plus I9001 Android Development] amank22:
Hey sir,how to use dat recovery builder???wat file to add in that recovery image file??
[Galaxy S Plus I9001 Android Development] buffo1987:
any recovery image you want ;), stock twrp cwm shouldn't matter. It only has to be for your device (as all files)
[Galaxy S Plus I9001 Android Development] amank22:
I want to make recovery for celkon ct2 tablet. It does'nt have a custom recovery.how to get/extract the stock one??

Or do I need to do that manual method??
[Galaxy S Plus I9001 Android Development] daniel3x:
After build the recovery using http://builder.clockworkmod.com/ I get two files recovery.img and inputrecovery.img, what should I use to flash with odin/terminal emulator?
[Galaxy S Plus I9001 Android Development] buffo1987:
AW: [GUIDE] Build CWM recovery

recovery.img is the one to choose. Inputrecovery.img is the one u uploaded.
[Galaxy S Plus I9001 Android Development] amank22:
Plss tell me hw I can get recovery.img for my tablet(no cwm exist as of now)
[Galaxy S Plus I9001 Android Development] buffo1987:
AW: [GUIDE] Build CWM recovery

I don't know your device, sry.
[Galaxy S Plus I9001 Android Development] amank22:
Ohk ohk..no prob. I too don't knw dat.gifted. one.got to knw dat it's already rooted.so thought If I can make cwm.nways,thnx.
[Galaxy S Plus I9001 Android Development] Bhg73:
I want to create ClockworkMod Touch Recovery v6.0.3.1 for my Micromax A110 jelly bean 4.1.2 how can i make recover for it
[Galaxy S Plus I9001 Android Development] buffo1987:
Only with builder.clockworkmod possible read first post
[Galaxy S Plus I9001 Android Development] rahulrai:
Hey Buffo, it would be gr8 if u can help some of us to make CWM recovery for low budget tablets. As I see you got some good knowledge.
[Galaxy S Plus I9001 Android Development] alireza7991:
Porting a bootable recovery from 0 for a device which has'nt any recovery sources needs lots of knowledge in cwm porting ! easiest way is to build one by cwm builder !
[Galaxy S Plus I9001 Android Development] rahulrai:
Can u help build one as i'm completely new rom dev and reading & trying to figure out thiings.
[Galaxy S Plus I9001 Android Development] alireza7991:
I'm not an advanced recovery dev but I can help you as much I can .

Which device do you want to build recovery for ? Does it have a recovery partition ? which kernel do you have ? Could you please provide a partition map of your device ? with this informations you may build a cwm with cwm builder
[Galaxy S Plus I9001 Android Development] alireza7991:
Hi

Please provide a logcat or a recovery log . So we can help you more

And one suggestion . Please try to use another vendor files also re check your recovery.fsatb
[Galaxy S Plus I9001 Android Development] broodplank1337:
I'm having the same issue with broodRecovery.. it seems when its compiled from source it bugs? I don't know what branch he built it on, but I used the cm-10.0 (jellybean) branch. seems this is a general issue
[Galaxy S Plus I9001 Android Development] alireza7991:
I used branch jellybean 10.1 m3 for the first time but after I used auto builder due to my net problem but no one had this problem ! I guess its related to kernel or vendors . But a log should be good :p
[Galaxy S Plus I9001 Android Development] 其实我也不懂:
There is the last_log
[Galaxy S Plus I9001 Android Development] 其实我也不懂:
The CPU is MT6589,here is the related file.Please help me look at my profile for errors,thanks a lot.

the official recovery.fstab ,my config and partitons informations.
[Galaxy S Plus I9001 Android Development] 其实我也不懂:
i upload myconfig files and the partitions informatios in #29

the cwm source code repo from https://github.com/C3C0/android_bootable_recovery ..The branch is mt6589.

thank you very much .
[Galaxy S Plus I9001 Android Development] STEVE_MARS:
Hi.

Two weeks ago I received my new tablet, Voyo A15, Exynos 5250 with ARM A15.

After too many troubles, I make a custom ROM with root and other things, and now I want build a CWM Recovery.

The problem is I can´t find recovery.img, or recovery.fstab.

The tablet don´t mount partition, cat /proc/mtd is empty.

And cat /proc/partitions only had 4 partitions mmcl, the smallest is 400 mb.

It´s possible that not had a Recovery?

For update firmware it´s based off utscript, no menu.

Sorry for my english, I´m spanish and hate Google Translator :cool:

Thanks.
[Galaxy S Plus I9001 Android Development] alireza7991:
Hi

Could you a give me output of this code in your tablet :

su
fdisk -l /dev/block/mmcblk0
[Galaxy S Plus I9001 Android Development] STEVE_MARS:
Of course:

Thanks for your help.
[Galaxy S Plus I9001 Android Development] sooorajjj:
i searched google for the cwm (recovery.img) for iball slide 6318i tablet

but i found nothing

when i tried to make one myself

http://xdaforums.com/attachment.php?attachmentid=2087810&stc=1&d=1372829222

i typed cat /proc/mtd i got this

what should i do now

iam completely new to making recovery .img

pls help me
[Galaxy S Plus I9001 Android Development] sdfee:
delete pls
[Galaxy S Plus I9001 Android Development] bayustev:
hi.. i was read the needed files for making cwm through server...

my device is gt-s6310

first recovery image..i had.., the second file recovery.fstab ?? no such file,...third is graphic.c..doesn't have either..

oi only had stock recovery .img...can can u help me into these file..or maybe where i can find it..??

theres already cwm..for gt-s6310..but seems many user had problems with stuck on recovery if you choose reboot recovery..

enlightment please..??

(sorry my bad english)
[Galaxy S Plus I9001 Android Development] anabhi:
fs.tab

graphic.c

recovery.img

how to find this file in android or by pc, adb etc

please I want too know that
[Galaxy S Plus I9001 Android Development] alireza7991:
you may find fstab and graphics.c and postboot in official repository of cyanogenmod for your device . or if you do'nt have CM for you device :

fstab -> use adb in recovery and dump it from /etc/

postboot -> use adb in recovery and dump it from /sbin/

graphics.c : this has been compiled so you have to rewrite it or use the one from a device with exactly same framebuffer format .
[Galaxy S Plus I9001 Android Development] anabhi:
command for adb please, for dump this file? :)
[Galaxy S Plus I9001 Android Development] Xperia_Modder:
this guide is very nice, but how can I build a cwm touch version (excluding the cwm site)?
[Galaxy S Plus I9001 Android Development] alireza7991:
Write touch pad driver and merge into cwm event handler parts .
[Galaxy S Plus I9001 Android Development] XeLLaR*:
CWM-Touch is not available for self compiling(only via build.cwm.com). Dunno why.
[Galaxy S Plus I9001 Android Development] krislibaeer:
i think it is possible you have to set a flag in boardconfig.mk

ifdef BOARD_TOUCH_RECOVERY

https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-10.2/Android.mk

but i am not sure
[Galaxy S Plus I9001 Android Development] alireza7991:
CWM touch needs touch input handler which I think does not exist on normal cwm ( in cm git ) so you have to rewrite it as I think what Phil and TWRP have done . The flag only enables use of touch but will work when you have touch event handler inside sources .
[Galaxy S Plus I9001 Android Development] sinnerz2000:
Can someone please compile a cwm for my phone? Its a karbonn a7+, I'll provide the required files, just let me know
[Galaxy S Plus I9001 Android Development] d3kilo:
I Have stock recovery.img for BCM2157 Froyo 2.2.2

I want to build CWM recovery.img Which repo should i used?

repo init -u git://github.com/CyanogenMod/android.git -b froyo

or

other repo

and

git clone or git pull ?
[Galaxy S Plus I9001 Android Development] alireza7991:
1-Use lastest branch ( 4.3 ) , if you have CM 10.2 port for your device .

2-use `repo sync"
[Galaxy S Plus I9001 Android Development] d3kilo:
The problem it is not support for CM10. I think the chipset is same with the ZTE Racer II. It is only support GB OS (CM7).

Should i still used the CM10 or CM7 (gingerbread)?

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

repo init -u git://github.com/CyanogenMod/android.git -b CM10.2

since my connection is slow, so it will take lot of time for downloading when fetching project.

Btw, what should i used from stock ROM. boot.img or recovery.img?
[Galaxy S Plus I9001 Android Development] alireza7991:
Use CM10.2 , and stock boot.img . if not booted use CM 7 ( since it uses kernel 2.6 ) .
[Galaxy S Plus I9001 Android Development] d3kilo:
working it, but the repo sync taking a lot of time for downloading. I wish have 10Mbps connection.
[Galaxy S Plus I9001 Android Development] d3kilo:
repo sync done.

But why i can't unpackbootimg

i tried http://builder.clockworkmod.com but it is same failed in unpackbootimg

i'm using boot.img and recovery.img from the flash tool

i tried cat /dev/mtd/mtd7 (it is for boot.img) and i tried dump using gscript bash23 but not working at all.

This is boot.img and recovery i dump : http://www.mediafire.com/#1lzb8oa35glu6

maybe some one can help with this step.
[Galaxy S Plus I9001 Android Development] alireza7991:
use my boot image tools for unpacking . if did not work . your boot.img is not a standard one or you did'nt dump it correctly
[Galaxy S Plus I9001 Android Development] d3kilo:
where should i put the files?

I put in usr/bin and out/host/linux-x86/bin

But still show this error

$ build/tools/device/mkvendor.sh bcrm bcm2157 ~/Downloads/romdump/boot.img
Arguments: bcrm bcm2157 /home/ari/Downloads/romdump/boot.img
unpackbootimg not found. Is your android build environment set up and have the host tools been built?
[Galaxy S Plus I9001 Android Development] alireza7991:
I think I've forgot to tell you that my tools are compiled for ARM and you can not run them on i686 . you should build them for i686 , find sources in my github http://github.com/alireza7991
[Galaxy S Plus I9001 Android Development] feiplane:
hello, I've some recovery questions to ask if you don't mind to answer it, THX

I've compiled CM10.1 branch's CWM recently with success for everything.

Later I tried the CM10.2 branch, compiled ok, but after I flashed it to my devices, it just gives me a black screen with flashes in certain interval everytime going into recovery.

This issue applied to every recoveries ranging from CWM, Philz and TWRP compiled using the same CM10.2 branch source.

Is it that CM10.2 source is not compatible with 4.1.2 device?
[Galaxy S Plus I9001 Android Development] alireza7991:
you should try to check if adbd has been started , then try to pull recovery log and dmesg and upload them here, so it will be easier to help you

But I guess :