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

[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!

adb not working marshmallow

Hey guys!
I've definitely missed something obvious.. and please forgive me in advance
I used to have cyanogenmod 12 installed and had some minor issues that was bugging me. I decided to update the phone with RUU GPE marshmallow.
The phone is working fine now, but I can't use adb commands through usb anymore...
it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH43BWM00xxx offline
I would like to install TWRP 3 but I can't send any commands
how can I get it to work?
phone is S-OFF
and yes.. I have activated usb debugging

check your adb version, command adb version
You need at least 1.0.31 or better 1.0.32

ckpv5 said:
check your adb version, command adb version
You need at least 1.0.31 or better 1.0.32
Click to expand...
Click to collapse
Thanks a lot... I was on my macbook and it didn't work. Tried on my PC and I had a newer version installed there.
Updated the mac adb and everything works on it too

Can't do IMEI/NVRAM backup MTK, can't root

Hey, guys.. I can't get through following issues. Phone's firmware is full vanilla since the very beginning - only updated from Jelly Bean/ICS to 4.4.2 with OTA.
I want to install TWRP Recovery and then try some custom firmwares. I started with making a backup of IMEI/NVRAM by MTK Droid R&T just to be safe.
I can't, IMEI/NVRAM button is greyed out. Log:
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
I've looked for solutions. They suggest e.g. searching for MTK app from different source. It doesn't help.
Setting up a root is also a trouble. I tried to use the simpliest, well known method within the reach based on Batch script.
Log:
Code:
[*] Waiting for device...(Connect your LGOG via USB in Charge Only Mode)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
Beginning Root Process
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
Press any key to continue . . .
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
Device is properly connected to adb.
Code:
(...)\ZV9-ZVB-Universal-Root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
LGE9751acf27d9 device
I'm aware that those problems might be trivial to fix. In that case, sorry for wasting your time. Still, thank you greatly for help. I can provide all needed info.
<< I can't post screenshots :/ - newbie user.

Glaeqen said:
Hey, guys.. I can't get through following issues. Phone's firmware is full vanilla since the very beginning - only updated from Jelly Bean/ICS to 4.4.2 with OTA.
I want to install TWRP Recovery and then try some custom firmwares. I started with making a backup of IMEI/NVRAM by MTK Droid R&T just to be safe.
I can't, IMEI/NVRAM button is greyed out. Log:
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
I've looked for solutions. They suggest e.g. searching for MTK app from different source. It doesn't help.
Setting up a root is also a trouble. I tried to use the simpliest, well known method within the reach based on Batch script.
Log:
Code:
[*] Waiting for device...(Connect your LGOG via USB in Charge Only Mode)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
Beginning Root Process
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
Press any key to continue . . .
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
Device is properly connected to adb.
Code:
(...)\ZV9-ZVB-Universal-Root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
LGE9751acf27d9 device
I'm aware that those problems might be trivial to fix. In that case, sorry for wasting your time. Still, thank you greatly for help. I can provide all needed info.
<< I can't post screenshots :/ - newbie user.
Click to expand...
Click to collapse
How I root my device:
1. Download the towelroot apk http://towelroot.en.uptodown.com/android
2. Go to Settings > Security > Unknown Sources (enable/allow it)
3. Select the towelroot on the notification dropdown and install
4. Launch towelroot and root your device
5. Download Root Checker on Playstore to double check if you've successfully rooted your device

@erkasmoter
App returns message: "This phone isn't currently supported". :/ Thx, tho. I really want to get TWRP working..

adb sideload cannot read .....

Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.

ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
Click to expand...
Click to collapse
More info would be a pleasure ur on twrp? Boot into it type adb push Filename /sdcard/ it should push the file to /sdcard/ so you can manually flash it.

ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.
Click to expand...
Click to collapse
Most of the times the problem is really on the desktop configuration, ie usb drivers, adb version, usb port power, user profile permissions, etc. Note that you need a newer adb version to do stuff such as sideload. From the top of my head, I think you need 1.0.32 or newer. I know it seems overkill, but until google decides to distribute the platform tools in a separate minimal bundle, the best option is to install the android SDK. You can choose then to selectively install only the platform tools that include adb.
Sent from my ONEPLUS A3000 using Tapatalk

https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47 is definitely the best fix i found, if it doesn't work reboot your PC and do it again it worked for me.
Hope it can helps