Develop Bugs

[Q] [Problem] bootanimation

I a newbie and I am trying to change my bootanimation.
I have
HTC Desire
OS: Android 2.2 (froyo) I updated it though OTA
HBoot: 0.93.0001
Radio: 5.09.05.30_2
Actually my device was unlocked but branded with UK O2 and loaded with Android 2.1 (Eclair). I used GOLDCARD procedure to make the device unbranded and then updated the OS. I also rooted the device using unrevoked 3.21 and it was successful.
Now the last thing I want to do is to change the bootanimation and I cant make it work. I am using rootexplorer to copy the bootanimation.zip file to
/system/customize/resources
/data/local
But no luck .. the bootanimation screen remains the same “HTC quietly brilliant”
I am also trying to copy bootanimation.zip file in
/system/media
But after copying the file use to disappear. I cant see you though root explorer. I never checked by using "ls" command. Can you please help me guys

Moved to Q&A as not development

I think i dont have completely rooted device
here is the thing i am doing using "abd"
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
Permission denied
$
Click to expand...
Click to collapse

Ok,
Super user permission issue is solved
just have to keep the screen active to see the authentication messages from "Super user permissions" and then it works like a charm.
See the uploaded snapshots as a reference
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
#
Click to expand...
Click to collapse

ok now i also managed to put bootanimation.zip in /system/media path and its still not working
... really i am out of ideas ... need some help
DO I NEED TO PLAY WITH THE PERMISSIONS OF THE bootanimation.zip FILE.... I am still seeing htc quietly brilliant at start up

helscream said:
ok now i also managed to put bootanimation.zip in /system/media path and its still not working
... really i am out of ideas ... need some help
DO I NEED TO PLAY WITH THE PERMISSIONS OF THE bootanimation.zip FILE.... I am still seeing htc quietly brilliant at start up
Click to expand...
Click to collapse
you cant write to /system/ when the device is booted even if your rooted, because we dont have an unlocked spl yet the nand protection prevents it, you need to put your device into recovery, and use adb to push the bootanimation.zip to /system/customise/resource/ and if that dosent work try pushing it to /system/media/

AndroHero said:
you cant write to /system/ when the device is booted even if your rooted, because we dont have an unlocked spl yet the nand protection prevents it, you need to put your device into recovery, and use adb to push the bootanimation.zip to /system/customise/resource/ and if that dosent work try pushing it to /system/media/
Click to expand...
Click to collapse
hmmm .. ok now i am going to ask you a very stupid question
how i can use adb in recovery mode
my device is turned off
Then I pressed "power + volume down" and I entered HBOOT menu
my device is connected to the PC though a USB
so i have options
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
i chose RECOVERY and then i had an other menu
ClockworkedMod Recovery v2.5.0.7
what to do now

helscream said:
hmmm .. ok now i am going to ask you a very stupid question
how i can use adb in recovery mode
my device is turned off
Then I pressed "power + volume down" and I entered HBOOT menu
my device is connected to the PC though a USB
so i have options
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
i chose RECOVERY and then i had an other menu
ClockworkedMod Recovery v2.5.0.7
what to do now
Click to expand...
Click to collapse
Thats it your in recovery, you can now issue commands to your device using adb just make sure the usb cable is connected,

AndroHero said:
Thats it your in recovery, you can now issue commands to your device using adb just make sure the usb cable is connected,
Click to expand...
Click to collapse
ok now
when I try its saying some thing like this
Code:
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb push bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\android-sdk_r07-windows\android-sdk-windows\tools>
sorry ... i cant understand

AndroHero said:
Thats it your in recovery, you can now issue commands to your device using adb just make sure the usb cable is connected,
Click to expand...
Click to collapse
Ok i tried the same command several times without making any change on the device and suddenly it worked. BUT THIS DIDNT SOLVE THE PROBLEM OF CHANGING THE BOOT ANIMATION. ITS STILL THE SAME
Code:
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb sh
ell
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>abd pu
sh bootanimation.zip /system/customise/resource/
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
failed to copy 'bootanimation.zip' to '/system/customise/resource/': Is a direct
ory
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
* daemon started successfully *
1941 KB/s (4509259 bytes in 2.268s)
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>

helscream said:
ok now
when I try its saying some thing like this
Code:
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb push bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\android-sdk_r07-windows\android-sdk-windows\tools>
sorry ... i cant understand
Click to expand...
Click to collapse
ive never come across this error before i found a thread in the hero section about it tho, maybe you should take a look
http://forum.xda-developers.com/showthread.php?t=582378

this seems to be the remedy to your problem acording to that thread
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse

AndroHero said:
ive never come across this error before i found a thread in the hero section about it tho, maybe you should take a look
http://forum.xda-developers.com/showthread.php?t=582378
Click to expand...
Click to collapse
Thankx AndroHero
I think, I found out the problem but I am not sure its the actually reason or not. If it worked I will come back to post my results.

helscream said:
Thankx AndroHero
I think, I found out the problem but I am not sure its the actually reason or not. If it worked I will come back to post my results.
Click to expand...
Click to collapse
i hope you can sort it out

adb question help please! FIXED Please remove

ok so.... im running ubuntu and have had system wide adb for ever now. all of a sudden it wont let me push to system.
pushing to the sdcard is fine but other than that its a no go
i have tried adb devices and i show up
adb remount says operation not permitted.
and can reboot go to recovery all from my terminal.i tried flashed a new kernel but its just not going.I just switched over from Xplod to stock OTA just to theme it a bit .
any help would be appreciated guys
these are the results i get after i do a computer restart and phone restart.
[email protected]:~$ adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
[email protected]:~$ adb devices
List of devices attached
HT0C6HL02189 device
[email protected]:~$
*update! i flashed cm7 and adb is working again..hmmmm.. im going re-flash OTA again and see if that works.
*ok i flashed back to the OTA and adb wont work again. usb debugging is on.

Strange problem with ADB and Linux (both as root and as a normal user)

I've recently been trying to get TWRP working on my KF so I can flash Jellybean, but whenever I go to ADB to have my Kindle reboot to fastboot, it won't work. For example:
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
[email protected]:~$
Now, I know that running ADB as a normal user is a bit janky, so I went and tried it as root. No dice:
Code:
[email protected]:~$ sudo '/home/evan/android/sdk/platform-tools/adb' devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:~$
I'm on LMDE, my computer recognized my Captivate on Ice Cream Sandwich (my Kindle is also on ICS, a custom CM9 build I did), and this same exact issue occurs with it in recovery mode.
I've done the udev rules, made sure everything's up to date in my android_usb.ini file, etc... But nothing I've tried works. I'm at my wits end, and while this isn't the most important thing in the world to me, I'd love to be able to run Jellybean at some point soon without completely reverting to stock. Thanks for your time in advance...

ytt3r said:
I've recently been trying to get TWRP working on my KF so I can flash Jellybean, but whenever I go to ADB to have my Kindle reboot to fastboot, it won't work. For example:
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
[email protected]:~$
Now, I know that running ADB as a normal user is a bit janky, so I went and tried it as root. No dice:
Code:
[email protected]:~$ sudo '/home/evan/android/sdk/platform-tools/adb' devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:~$
I'm on LMDE, my computer recognized my Captivate on Ice Cream Sandwich (my Kindle is also on ICS, a custom CM9 build I did), and this same exact issue occurs with it in recovery mode.
I've done the udev rules, made sure everything's up to date in my android_usb.ini file, etc... But nothing I've tried works. I'm at my wits end, and while this isn't the most important thing in the world to me, I'd love to be able to run Jellybean at some point soon without completely reverting to stock. Thanks for your time in advance...
Click to expand...
Click to collapse
yeah pm me I will help you get it sorted

Rooting Issues

Hey, first here's some information on my phone:
Arc S
Model Number: LT18i
Android Version: 4.0.3
Build Number: 4.1.A.0.562
Bootloader Unocked: Yes
So, I unlocked the bootloader and I'm now trying to root the device; in order to install Cyanogenmod. I've tried both methods at (I can't post links =__=):
techdraginfo.blogspot.com/2012/06/root-sony-xperia-arc-arc-s-official.html
Click to expand...
Click to collapse
neither have worked for me.
Here's what I've done and what isn't working.
For method 1:
I've installed the ADB drivers, get up to step 8, put the phone in fastboot mode, enter the command fastboot boot ARC-DooMKernel-ICS-BETA-v04-lower-boot.img and I'm prompted with:
Device Waiting
Click to expand...
Click to collapse
It never gets past this point.
For the One-Click method;
I've installed the ADB drivers, extracted DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su.zip to C:\, run the .bat script and I get a whole bunch of issues related to ADB, such as:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- creating temporary directory
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
It continues like this for the rest of the script. I don't understand why it will not connected to the ADB server. I've killed any ADB processes previously running prior to running this script and turned off my anti-virus changes.
Any idea why this is?
Cheers

Slycs said:
I've tried both methods at (I can't post links =__=):
Click to expand...
Click to collapse
Use the methods from xda, you can find them in the stickys or browsing general, or what you should have done first, searching - root arc s

If you want to install CyanogenMod and you have unlocked your bootloader, then just install kernel and install ROM from it. No root necessary.
Sent from LT18i with custom firmware by myself.

[Q] [Root] Help running Bin4ry script on Ubuntu 13.04

hi there,
After some hours reading and trying to fix it myself, I have to admin that I need help with rooting my new KFHD8,9 Firmware 8.4.1:
I would rather post in the referring development threads, but I am not allowed to yet. So i am asking here for help
The thing is that all my devices at home are running Linux (Ubuntu 13.04) and I am not trusting the "use-Windows-in-a-VM-and-use-USB-to-root" method
Now I was following the Tutorial from seokhun and decided to use the Bin4ry method to root, because it is delivered with the RunMe-script as a windows-batch and a shell-script.
The android-tools (android-tools-adb, android-tools-fastboot and android-tools-fsutils) have been successfully installed via apt-get and are working (I can use adb and fastboot to get device information).
When I try to execute the RunMe.sh (have made it executable via chmod +x before) and choose the option 1 it is stuck:
Code:
Make a choice:
Please enter a valid number(1 to x):
1
Checking if I should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
The script hangs at the line with the first use of the delivered adb with the wait-for-device parameter (inside the stuff folder).
Code:
mytest() {
echo "Checking if I should run in Normal Mode or special Sony Mode"
echo "Please connect your device with USB-Debugging enabled now"
echo "Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!"
./stuff/adb wait-for-device
./stuff/adb pull /system/app/Backup-Restore.apk . > NUL
./stuff/adb pull /system/bin/ric . > NUL
If I run my installed version of adb it terminates successfully with
Code:
adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]: ...
But when I call the delivered adb inside the stuff folder it never terminates:
Code:
../Root_with_Restore_by_Bin4ry_v30/stuff$ ./adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
has anybody a clue?

Its me again
I am wondering if i can exchange the delivered ADB with my installed and Working ADB.
If it can be replaced, why is it delivered for Windows and Linux and why most tutorials set them AS requirement proceeding :what:
Sent from my Incredible S using xda app-developers app

Create a live usb with persistent must be an 8 gig usb flash drive for maximum persistent. Use this creator http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ . Use linux mint maya the mate one with codecs 32bit http://www.linuxmint.com/edition.php?id=105. Boot it and use this script http://forum.xda-developers.com/showthread.php?t=2162973 . That is all you will need good luck. You can use 32bit ubuntu12.04 as well the reason to use these distros is that the newer ones don`t run soupkit installer properly in a terminal it makes the installation much cleaner I have been able to force install on some of the later distros but it`s a serious pain in the rear.

thanks for your reply!
I will try it with Ubuntu 12.04 the next days!

worked fine with Ubuntu 12.04. Thank you very much for the hint!

badbutz said:
worked fine with Ubuntu 12.04. Thank you very much for the hint!
Click to expand...
Click to collapse
Your welcome anytime.:highfive:

Glad i checked forums first
Was going to help a friend root, twrp and cm 10.1 his KF 8.9 after work today. his laptop is running 13.04 ubuntu. glad i ran across this post before wasting significant time. 1'll bring a 12.04 laptop with me. Thanks to Thepooch for sharing this info and have a great week!