yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] feiplane:
adbd is started but no recovery log yet for just booting into CWM without any work done I guess, because the log I pulled was from the last TWRP I used. And I doubt that it's not related to graphics.c since it worked on CM10.1's CWM, both branches graphics.c are actually identical.

I'll try to get the dmesg, in the meantime, here's the logcat of CWM

logcat
--------- beginning of /dev/log/system
I/Vold ( 138): Vold 2.1 (the revenge) firing up
--------- beginning of /dev/log/main
E/rmt_storage( 144): rmt_storage user app start.. ignoring cmd line parameters
E/rmt_storage( 144): rmt_storage open success
E/rmt_storage( 144): 2 supported partitions found
E/rmt_storage( 144): rmt_storage open event: handle=1
E/rmt_storage( 144): Opened /boot/modem_fs1
E/rmt_storage( 144): rmt_storage events processing done. (handle=1)
E/rmt_storage( 144): rmt_storage client thread started... (handle=1)
E/rmt_storage( 144): rmt_storage client thread waiting... (handle=1)
E/rmt_storage( 144): rmt_storage send user data event: handle=1
E/rmt_storage( 144): rmt_storage events processing done. (handle=1)
E/rmt_storage( 144): rmt_storage open event: handle=2
E/rmt_storage( 144): Opened /boot/modem_fs2
E/rmt_storage( 144): rmt_storage events processing done. (handle=2)
E/rmt_storage( 144): rmt_storage client thread started... (handle=2)
E/rmt_storage( 144): rmt_storage client thread waiting... (handle=2)
E/rmt_storage( 144): rmt_storage send user data event: handle=2
E/rmt_storage( 144): rmt_storage events processing done. (handle=2)
E/rmt_storage( 144): rmt_storage write event: handle=2
E/rmt_storage( 144): Try to unblock rmt_storage client thread... (handle=2)
E/rmt_storage( 144): rmt_storage events processing done. (handle=2)
E/rmt_storage( 144): rmt_storage client thread is unblocked. (handle=2)
E/rmt_storage( 144): rmt_storage fop(1) fd(11) handle(2): bytes required=314521
6, offset=0
E/rmt_storage( 144): rmt_storage fop(1) fd(11) handle(2): bytes transferred=314
5216
E/rmt_storage( 144): rmt_storage fop(1) fd(11) handle(2): bytes required=512, o
ffset=3145216
E/rmt_storage( 144): rmt_storage fop(1) fd(11) handle(2): bytes transferred=512

E/rmt_storage( 144): rmt_storage_send_status fop(1) fd(11) handle(2): error_cod
e = 0
E/rmt_storage( 144): rmt_storage client thread waiting... (handle=2)
I/ARMAssembler( 142): generated scanline__00000077:03545404_00000A02_00000000 [
30 ipp] (52 ins) at [0x411151f0:0x411152c0] in 153334 ns
I/ARMAssembler( 166): generated scanline__00000077:03545404_00000A02_00000000 [
30 ipp] (52 ins) at [0x411451f0:0x411452c0] in 123334 ns
I/ARMAssembler( 182): generated scanline__00000077:03545404_00000A02_00000000 [
30 ipp] (52 ins) at [0x40fbb1f0:0x40fbb2c0] in 126667 ns

and keep repeating the above I/ARMAssembler......

---------- Post added at 07:56 PM ---------- Previous post was at 07:13 PM ----------

here comes the dmesg output

https://docs.google.com/file/d/0B-2vLCGQ7rPTajBxVHpyMlRRYkk/edit?usp=sharing

as you can see, the screen keeps powering itself on and off, on and off......
[Galaxy S Plus I9001 Android Development] alireza7991:
It seem recovery has not been started yet . check ramdisk
[Galaxy S Plus I9001 Android Development] feiplane:
for what?

---------- Post added at 04:18 AM ---------- Previous post was at 03:40 AM ----------

alright, I managed to get the recovery log

here it goes

CWM-based Recovery v6.0.4.4
E:failed to read /etc/recovery.fstab
W:Unable to get recovery.fstab info for /cache during fstab generation!
W:Unable to get recovery.fstab info for /data during fstab generation!
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /system during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!

why it failed to read recovery.fstab, the fstab was the same I used on CM10.1.........
[Galaxy S Plus I9001 Android Development] alireza7991:
It seems fstab generation has been changed in recent recoveries . change fstab related config ( I can'nt remember its name)in Android.mk to get recovery working with your fstab
[Galaxy S Plus I9001 Android Development] feiplane:
oh yes, I've got info from #koush, CM10.2 is using v2 fstab, so I have to convert the old v1 recovery.fstab of my device manually to v2 format, thx for your help anyway, really appreciate:highfive:
[Galaxy S Plus I9001 Android Development] Arinio:
syntax error near unexpected token `newline'
[Galaxy S Plus I9001 Android Development] Keff91:
Use this one,

curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

Then try run repo init and repo sync again. ;)
[Galaxy S Plus I9001 Android Development] Arinio:
Thanks Keff.

Definitely I will try this.
[Galaxy S Plus I9001 Android Development] Keff91:
It seem you haven't configure your git account. You can refer to this thread.

http://xdaforums.com/showthread.php?t=1877040

And check Creating an account.
[Galaxy S Plus I9001 Android Development] Arinio:
Thanks Keff, you are extremely helpful. I will do the needful and let you inform.
[Galaxy S Plus I9001 Android Development] Arinio:
Keff,

Changed the argument of repo command. Previously it was

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

repo sync

Now changed to

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

repo sync -j16

However it is still downloading for more than 72 hours.!!!

Is this natural?

Also, I want to create the device tree for Galaxy Grand Quattro. Shabbypenguin and Anand both created separately the device tree however the CWM created by Shabbypenguin have bootlooping problem (occationally while one restarts phone instead of loading the Androin OS it loads CWM and the only way to get rid of that is to install stock recovery image via odin. There is also graphics problem in that CWM. I want to create a bug free CWM. Please help.

Another thing to mention that though $ adb devices shows device number $ cat /proc/mtd shows nothing as there is no mtd file. Unable to detect the connected phone from fstab file. Here also I need your help. Please guide me.

Regards
[Galaxy S Plus I9001 Android Development] stallionrider21:
Hello to everyone. Can anybody guide me how to build cwm recovery for voyo A18. Please
[Galaxy S Plus I9001 Android Development] stallionrider21:
Please Help in making CWM recovery

Can someone please compile a cwm for my tablet? Its VOYO A16 I'll provide the required files, just let me know

it uses utscript for flashing we have very difficulty in flashing any help please?
[Galaxy S Plus I9001 Android Development] geek-baba:
[Q] builder.clockworkmod.com - error

I am trying to port HTC One Dual Sim (802w) recovery using the cwm builder, getting the following error

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.1
CM_VERSION=10.2-20140102-UNOFFICIAL-unknown
TARGET_PRODUCT=cm_unknown
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=
HOST_ARCH=x86
HOST_OS=darwin
HOST_OS_EXTRA=Darwin-13.0.0-x86_64-i386-64bit
HOST_BUILD_TYPE=release
BUILD_ID=JLS36I
OUT_DIR=/Volumes/Data/hudson/workspace/android/cm-10.2/out
============================================
bionic/libc/Android.mk:429: TARGET_CPU_VARIANT is not defined
bionic/libc/arch-arm/arm.mk:30: *** "TARGET_CPU_VARIANT not set or set to an unknown value. Possible values are cortex-a5, cortex-a7, cortex-a8, cortex-a9, cortex-a15, krait, scorpion. Use generic for devices that do not have a CPU similar to any of the supported cpu variants.". Stop.
build error!
Build failed.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE

I am using the attached img file to build the cwm recovery - https://mega.co.nz/#!YhcFUDKQ!IR8HByGafWTPTC7GX06YpR0hB9VgFIW4hostTAz4Fxs
[Galaxy S Plus I9001 Android Development] pug1:
Help with syncing the repo

can someone plz tell me how i have to edit these lines in bashrc file...

#Android

export PATH=${PATH}:~/android-sdk/tools

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

export PATH=${PATH}:~/bin

i assume that the {PATH} needs changing but keep getting

error repo not known or somet like that.

i am just setting up my laptop and cant remember how to get it to sync

Thanks
[Galaxy S Plus I9001 Android Development] dams161:
hello

I'm looking for someone to help me make a custom recovery for ot6034r

I extracted the stock recovery but I want to try to have the option to save my stock rom

I saw on a topic that you know the recovery.

I love to learn and understand what I did.

thank you for your help
[Galaxy S Plus I9001 Android Development] dams161:
hello

if anyone can help

I give you the img.

recovery.img : https://www.dropbox.com/s/mwxm2rc4x1lsor7/recovery.img

boot.img: https://www.dropbox.com/s/lbdcu7jcjvns37k/boot.zip

I try with cwm but the builder does not work

please help

it is an idol alcatel s ot6034r with a 400 processor snapdragonn

thank you
[Galaxy S Plus I9001 Android Development] sim_tcr:
Hello,

I am a Samsung Galaxy tab 2.7.0 p3100 user. And I have CWM 6.0.4.5 Installed.

Currently when backing up any ROM, CWM does not backup /0/Android/data and /0/Android/obb (this is where the game files resides)

Any one ever built CWM for p3100 for above requirement?

If is that doable?

P.S. I know that when including /0/Android/data and /0/Android/obb it is going to increase the backup size. But still it would be nice to have it rather than re-downloading the big files.)

Thanks,

Simon Mandy
[Galaxy S Plus I9001 Android Development] manojkumar8552:
video , picture guide appriciated bro !! pls something like that ! so its make concept clear for evern nOOB !!! so rare case device can also get benifit man !!!
[Galaxy S Plus I9001 Android Development] linhbs:
Has anyone explain for me this command ( make clobber && make -j# recoveryimage //# CPU-Cores+1 ). Thanks so much.
[Galaxy S Plus I9001 Android Development] corsicanu:
make clobber && make -j# recoveryimage //# CPU-Cores+1

make clobber - clean build directory

make -j# recoveryimage - make cwm img where "#" is the number of jobs, usually 4

//# CPU-Cores+1 argument - tells "make" command to use "#"+1 cpu cores.

You can make cmw only with:

make clobber && make -j4 recoveryimage
[Galaxy S Plus I9001 Android Development] yakamuz88:
I9300i CWM Request

Hi

Is it possible for \any one to make it for i9300i samsung galaxy S3 Neo??!!

it will be so useful for many users

Thanks and Regards .
[Galaxy S Plus I9001 Android Development] blttalas:
blttalas@acer:~/android-sdk-linux/platform-tools$ make -j4 otatools

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.1.2

TARGET_PRODUCT=full

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.13.0-29-generic-x86_64-with-Ubuntu-14.04-trusty

HOST_BUILD_TYPE=release

BUILD_ID=JZO54K

OUT_DIR=/home/blttalas/android-sdk-linux/platform-tools/out

============================================

Checking build tools versions...

************************************************************

You are attempting to build with an unsupported version

of java.

Your version is: java version "1.8.0_05".

The correct version is: Java SE 1.6.

Please follow the machine setup instructions at

https://source.android.com/source/download.html

************************************************************

************************************************************

You are attempting to build with the incorrect version

of javac.

Your version is: javac 1.8.0_05.

The correct version is: 1.6.

Please follow the machine setup instructions at

https://source.android.com/source/download.html

************************************************************

why?
[Galaxy S Plus I9001 Android Development] corsicanu:
you need to install and use java se 1.6.. check the first page for download links and tutorial.. :good:

Sent from my Nameless phone
[Galaxy S Plus I9001 Android Development] Martini3001:
Hello,

I searched at my whole device (LG G3) for recovery files (img / fstab) but I didn't find anything. What have I to do if I want to build a custom recovery. Cyanogen isn't available for this the device right now.

Can anybody tell me how to find some useful information about the android system? I use it for years - programmed a lot of stuff, but I don't get any idea how this system works and how to build ROMs or Recovery images.. Every time I tried to do customizing / hacking, I get fed up by my damn slow internet connection and the very unsatisfying fact that I seem to be to stupid to find some files at my device. THIS is a real pain in the ass. Every tutorial I found is just a instruction of copy-pasting commands and forking crap from people I don't know and I don't want to know.

Is it so hard to find a reliable documentation how android works? I feel so helpless in this ocean of inexperience :eek:

Thanks in advance

Martin
[Galaxy S Plus I9001 Android Development] ibub:
First a warning. OEM has likely burned a sha256 verification into the device. This will effectively lock the bootloader. That will, in turn, have it's own verification of recovery, kernel, etc. Also, there are backup partitions for additional verification. Any attempt to alter these will likely result in a shiny brick. But I am still searching the code.

Recovery resides on its own partition on the device. And fstab is compiled into it, in the ramdisk. You can start by installing partition table, from play store. It will show up in advanced view. It will show the path to copy (dd). You can also get this path by looking at /dev/block/platform/msm_sdcc.1/by-name/. This contains symlinks to partitions. For example, on mine, recovery >>/dev/block/mccblk0p17. Your G3 may be different, but since it's LG it's probably the same. So now that you have your path to recovery Partition, you can dump content (I use terminal emulator) by

dd if=/dev/block/mccblk0p17 of=/cache/recovery.img

Cache is in ext4 format (better to decompile).Since you have dumped the whole partition, most of it is just zeros. You can use APKTOOL to decompile, and then you will have ramdisk folder. fstab is there. [emoji4]
[Galaxy S Plus I9001 Android Development] Martini3001:
Wow, you are really awesome! Thank you so much. Now I got the image on my computer :) And I think I learned a quiet bit about the mechanisms in the system, too.

EDIT:

Hmm, actually I got the "raw" recovery.img at my computer and on my computer. At the computer I don't know how to decompile it and using my phone (via apktool-app) results in an error "gunzip: invalid magic" <- linux terminology :D hmm, does anybody know how to solve this? How are you building CWMs?

Best wishes

Martin
[Galaxy S Plus I9001 Android Development] ibub:
No problem brother. [emoji4] A little more about security:

http://source.android.com/devices/tech/security/dm-verity.html
[Galaxy S Plus I9001 Android Development] ibub:
[MENTION=4497161]Martini3001[/MENTION]

Full instructions for Apktool here:

http://xdaforums.com/showthread.php?t=2659302
[Galaxy S Plus I9001 Android Development] BetoL21:
Does this work for all samsung devices?
[Galaxy S Plus I9001 Android Development] katinatez:
You could use this tool, super easy

http://xdaforums.com/showthread.php?t=2073775
[Galaxy S Plus I9001 Android Development] evrkusd:
Thanks for the info, this is very helpful. I've been thinking about creating CWM recovery for my VZW Galaxy Tab 4. I read through this thread and others and want to clarify what might be a basic question: If a bootloader is currently locked in some way by OEM (as described above), as it is on the Tab 4, does flashing a CWM recovery completely remove these restrictions? Or can these restrictions persist in some multilayer way, like on other partitions or aspects of a device?
[Galaxy S Plus I9001 Android Development] ibub:
No, flashing CWM will not change bootloader locked status. Primary bootloader is first partition to be loaded at power on. It verifies the kernel (signature and SHA-1), and then (if verification succeeds) loads it. The kernel, in turn verifies any partition or memory block that it has been tasked to police by the manufacturer (including recovery). So CWM, without bootloader unlocking, will likely not load, and very likely brick the device. There are hacks like Loki, which installs a modified CWM, and tricks the verification process. But manufacturers have since patched against it.
[Galaxy S Plus I9001 Android Development] evrkusd:
Ok, that's very helpful to know. So the difference between devices that can have CWM installed and those that cannot is that some devices have this primary bootloader unlocked, either by the manufacturer or through some other means. And in general, flashing a bootloader doesn't unlock your bootloader, it just means you already had an unlocked bootloader in order to do so! Sound right?

So with some of these later Samsung Verizon devices, most or all of them have entirely locked primary bootloaders, right?

What I don't understand is why some of these devices, like the Galaxy Tab S for instance, seems to have a TWRP version for it. Without a hack like Loki, how could this have happened?

Thanks again for all the info. I hope it's on topic enough to warrant being in this thread - it's very helpful!
[Galaxy S Plus I9001 Android Development] ibub:
[MENTION=5554896]evrkusd[/MENTION]

Forgot to mention that some devices still come bootloader unlocked, or unlockable with a code from manufacturer.
[Galaxy S Plus I9001 Android Development] quanqw:
http://builder.clockworkmod.com/ can not use.
[HTC Incredible S] androidindian:
Hey friends

For sometime I have been having signal drop issues with my incredible S .. I have changed radios (ics ones)

and also roms.. but it doesnt seem to go away

basically the signal drops randomly and says no network and after a while comes back on..

any help or solutions? highly appreciate it..

Thank you!
[HTC Incredible S] androidindian:
Any advice my friends?
[HTC Incredible S] InsertDumbNick:
Maybe it's the service providers issue? Are any other phones at your disposal facing the same issue?

You Jelly Bruh??
[HTC Incredible S] androidindian:
Don't think it's the service bro.. Using another device in the same area and it's totally cool..

I'm jelly bro
[HTC Incredible S] xsouthernburnx:
Same issue here can't find a fix
[HTC Incredible S] zulmajdi:
There is an copper anthena at the back cover of the phone. If damage it. The signal will dropping and will not increase
[HTC Incredible S] Tierlord:
same issue here. signal is fine most of the time, then suddenly no signal for a few minutes. but restart is fixing it, so It's

neither the antenna, nor our provider.. hmm ._.
[HTC Incredible S] xsouthernburnx:
I'm guessing I would have to take the phone apart completely simplay taking the back cover off shows no wire. I saw a post earlier about the signal cable was disconnected. I did not see one and as stupid as this may sound would all phones have one?
[HTC Incredible S] androidindian:
Could it be radio related then since many if us are having this?

Has anyone been getting this issue on an ICS ROM?
[HTC Incredible S] FCArsenal:
I hv this issue with my mobile data. It keeps DC and then comes back. doesn't happen with the network though.
[Nexus S Android Development] thethiny:
Not sure if this works , but I will eventually try it , but not now , on my free time.

stagefright indeed is not included , my phone too doesn't have stagefright , if you go to youtube and search for android developement tutorials by "thenewboston" . you'll find 200 videos series , just watch the first 20 ones and you'll learn to use Media which replaces stagefright...I didn't try it yet.

It includes

Our_Player and Media Player and the directory of the song....check it out and give us heads ups!
[Nexus S Android Development] ethan_hines:
I appreciate the info, I took a look at his tutorials esp the ones involving animation, he really knows his stuff. I am not a Java programmer by any means and to be honest I find it quite tedious, it's like trying to teach a baby (this case the Dalvik VM) to do basic stuff like draw a green ball took like 20 lines of code!

What I need to know essentially is, do I have to use JAVA to get this to work now? In the past ie ICS and lower, there wasn't a problem with Custom Boot Audio, now with JB it seems it has disappeared from the radar.

I know the binary /system/bin/bootanimation (is this written in JAVA?, is there a source code for this bin?) is called at boot time by init.rc in the following manner:

service bootanim /system/bin/bootanimation
class main
user graphics
group graphics
disabled
oneshot

/system/bin/bootanimation (at least from what I gather) looks in /system/media for bootanimation.zip (zipped in store mode) decompresses it , looks at desc.txt for the code and displays the animation png by png.

In some desc.txt there is an s line, example:

# mobility
p 1 0 SOUND
s transdroid.mp3

which is SUPPOSED TO call a custom boot audio from /system/media (.mp3?) at the same time. This appears not to work. So logicaly I think the binary needs some tweaking. Can you offer any suggestions?

As you can see I have spent ALLOT of time mulling over why this,one would think, simple task: display a series of images and play audio at boot time I mean how hard can that be?

I am not trying to be a pest I just need to know WHY this doesn't work in JB (CM10.1) :(
[T-Mobile Samsung Galaxy Note II] k1ng617:
**FYI SALE IS NOW OVER** Feb 5th

I know this isn't specifically related to our Note 2's but I wanted to give my forum mates a headsup that Amazon is having a huge sale on Sandisk products and now is a great time to pick up one of these cards if you are in the market. I have been looking for over a month and prices have been around $60 to $80.

Linky: http://www.amazon.com/SanDisk-Micro..._m=ATVPDKIKX0DER&pf_rd_r=0RFYBD4AZ8C61FDQEV3N

I ended up getting one of their 64gb thumb drives for $31.99 too. Not a bad day!

:victory::laugh::D clicky thanks if you're in for one too!
[T-Mobile Samsung Galaxy Note II] sleepys4:
Good stuff man thanks!
[T-Mobile Samsung Galaxy Note II] horr1blek1tten:
Belongs in the accessories thread fyi thanks for the heads up wish this was a week ago.
[T-Mobile Samsung Galaxy Note II] Classick206:
Saw this earlier. I'm definitely considering it, especially since it was about $56 when I added it to my Wish List last night. Maybe it's a sign?
[T-Mobile Samsung Galaxy Note II] horr1blek1tten:
I hope it'll last a while I have a 32 and about 25 gbs worth of music I have about 12.6 gb of videos and movies between my sd space and the internal this'll definitely keep everything in one place.
[T-Mobile Samsung Galaxy Note II] k1ng617:
That's the plan! I'm OCD and want to keep everything together, but all of my 16gb ext and remaining internal is maxed so that's pretty tough to maneuver.

BTW I think Goldbox sales only last a day :eek:
[T-Mobile Samsung Galaxy Note II] ericshmerick:
Beware. The Note 2 eats these cards for breakfast.

Source: RMA'd my second one and I'm not alone. Good luck to whoever buys one. Your data will suddenly disappear at any given time.

Just stick to Samsung cards.
[T-Mobile Samsung Galaxy Note II] k1ng617:
I've been reading up that they don't behave properly in exfat format. Was that how yours was formatted?
[T-Mobile Samsung Galaxy Note II] SMARTPHONEPC:
I grabbed another http://www.amazon.com/SanDisk-MicroSDXC-Memory-Adapter-SDSDQU-064G-AFFP-A/dp/B009QZH6JS - Thnx:cool:

"Product Features

Size: 64GB | Style: Frustration Free Package

Reformat into file system other than exFAT may cause instability

Only compatible with SDXC enabled device in exFAT format per SD Standard"