Database Info

How to Change Boot Screen To Nexus Boot?

I was wondering how i can change my boot screen to the Nexus Boot, i have the files to do it but dont now how, any help would be appreciated!!
If this is in the wrong section sorry!!
Also i am using the rom MLIGNv.1.1

It depends...
Hi - It depends on the rom you are using. I hope the following helps.
This is how I changed mine (you mentioned that you already have the animation):
(This will only work for Hero ROMs such as CaSense, MyHero, MLIGN. Will not work for CynanogenMod)
The bootscreen is stored in the /system/media/bootscreen folder. I suggest you open up the rom zip file to see the files in this folder. The file boot_animation.xml defines the animation scheme.
You should scan through the file to find something like this:
Code:
<BootConfiguration>
<BootAnimation image="/system/media/bootscreen/hvga_android_006spf.gif"
image2="/system/media/bootscreen/hvga_htc_in_006spf.gif"
loopimage="/system/media/bootscreen/hvga_htc_loop_006spf.gif"
image_bg="/system/media/bootscreen/boot_bg.gif"
audio="/system/media/bootscreen/android_audio.mp3"
screenX="0"
screenY="55"
useAudio="1" />
</BootConfiguration>
"image" is the first animated image displayed (of what I have seen of the different ROMs, this usually has Google's Androids in some form or the other, either with a Hero written or without). "image2" is a static image (in my case, it shows a static HTC logo). "audio" is the sound that is played. "loopimage" is the animation (in my case, it showed the HTC logo with a flare running across"). The "loopimage" is the one that you have to change.
From here on you have two options:
1) More risky, but correct: Modify the boot_animation.xml file based on the above description, change the file to use your file (replace the filenames) and push into the system/media/bootscreen folder
Don't add the words in brackets:
Code:
adb remount (mount the root filesystem in read-write mode)
adb push boot_animation.xml /system/media/bootscreen (this assumes that the boot_animation.xml file is in the same folder as adb)
adb push nexus_animation.gif /system/media/bootscreen (replace nexus_animation.gif with whatever is the filename for the nexus one animation that you have. Also make sure that this is the name of the image in boot_animation.xml)
2) Less risky, but its more of a workaround: In the boot_animation.xml file, check the name of the image under the "loopimage" tag (in the above case it is hvga_htc_loop_006spf.gif). Then make a backup of this image, and then replace this file with the nexus animation.
Don't add the words in brackets:
Code:
adb pull system/media/bootscreen/hvga_htc_loop_006spf.gif (backup)
ren hvga_htc_loop_006spf.gif backup_animation.gif (rename)
ren nexus_animation.gif hvga_htc_loop_006spf.gif (assuming that the nexus_animation.gif is in the same folder)
adb remount (mount the root filesystem in read-write mode)
adb push hvga_htc_loop_006spf.gif system/media/bootscreen/
The advantage with this method is that if something goes wrong, the android bootup will be displayed, instead of the nexus animation, and we have not modified the boot_animation.xml file in anyway. So chances of screw-ups are low.
In either case, restart the phone and you should see the nexus animation.
Obligatory warning: Though I can confirm this has worked, I will not take responsibility for any bricked phones, however remote the possibility for this to happen as you are not making any big changes.
Best of luck!
Slash

Simple
Just update to an Eclair rom both ManUp and Eugene have the Nexus one boot animation.

slash .. that was really interesting idea .. can u provide a vid .. that shows the step works .. splash image>animates boot > home screen > setting > about phone
but i did notice that .. custom ROM eg.CyanMod .. does not have any kind of this folder u said in ur post
/system/media/bootscreen
/system/media/bootanimation
this .zip file only avail in 2.0 custom ROM ..
if i did follow ur step .. then how about our normal boot image setup ?? coz currently i change my boot image to my custom made design that had been told in this thread
http://forum.xda-developers.com/showthread.php?t=527200
is it the custom .png image will disturb/effect our new animation boot image ..
consider we use CyanogenMod
hoping for ur great reply
thx in advance

hey i tried the second one and when i connect my phone to the SDK and then type:
Code:
pull system/media/bootscreen/hvga_htc_loop_006spf.gif
all i get is
Code:
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
idno wat the problem is?

....
OK. This is getting interesting:
tera89: The instructions I had were for Hero ROMs (I am really sorry for not mentioning that). I see from the link that you gave that the basic version of Android (and Cyanogen's mod for that matter) create animations VERY differently. Hero ROMs just show an animated GIF. I don't think the Nexus One boot screen animation can be used with Cyanogenmod. In case you decide to shift to a Hero Rom just to have the Nexus One animation (I dont see that happening, but anyways), I would suggest CaSense (http://forum.xda-developers.com/showthread.php?t=576445 - very stable, have been using it since the past 1.5 months now).
crisvillani: I suggest exploring the filesystem to check whether the /system/media/bootscreen folder exists and what files are there. One way is to check the zip file you downloaded for flashing the rom and checking the system/media folder inside that (of course, if you are using Cyanogen's mod, it wont be there). The other way is to open up the command prompt in windows: For example here's what my directory structure looks like (make sure you are in the folder where you have the android sdk installed, or you have the path in your system path):
Code:
D:\Downloads\Android\android-sdk-windows-1.6_r1\android-sdk-windows-1.6_r1\tools
>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# cd /system/media/bootscreen
cd /system/media/bootscreen
# ls
ls
←[0;0mBootup_020609.gif←[0m ←[0;0mboot1.gif←[0m
←[0;0mhvga_android_006spf.gif←[0m
←[0;0mandroid_audio.mp3←[0m ←[0;0mboot2.gif←[0m
←[0;0mhvga_htc_in_006spf.gif←[0m
←[0;0mboot.gif←[0m ←[0;0mboot_animation.xml←[0m
←[0;0mhvga_htc_loop_006spf.gif←[0m
←[0;0mboot.mp3←[0m ←[0;0mboot_bg.gif←[0m
# exit
exit
D:\Downloads\Android\android-sdk-windows-1.6_r1\android-sdk-windows-1.6_r1\tools
>
In between the random characters (←[0;0m), you should see the filenames that exist. I suggest starting with the boot_animation.xml. In case the system/media/bootscreen folder does not exist, you will get an error at the second command (cd /system/media/bootscreen)
Let me know if this helps.
Best,
Slash

Mlign
So I downloaded MLIGN's rom from http://forum.xda-developers.com/showthread.php?t=593759 and checked it. The structure is very similar to the CaSense ROM.
Sorry for the wrong commands (am editing my previous post in a moment)
Try:
Code:
adb pull system/media/bootscreen/hvga_htc_loop_006spf.gif c:\
or any other folder instead of c:\ where you want to backup the image.
Another thing, before you will be able to push the new file, you will need to remount the filesystem in a read-write mode using:
Code:
adb remount
I am correcting the original post so that you have all the commands in the right order for method 2.
Best,
Slash
PS> I don't have a webcam handy, so I can't show the phone booting with the Nexus animation. But, it does work

thxs will try the new commands now

Alright did it got the first two commands right but when i do:
Code:
adb push hvga_htc_loop_006spf.gif system/media/bootscreen/
i get this:
Code:
C:\AndroidSDK\tools>adb remount
remount succeeded
C:\AndroidSDK\tools>adb push hvga_htc_loop_006spf.gif system/media/bootscreen/
failed to copy 'hvga_htc_loop_006spf.gif' to 'system/media/bootscreen//hvga_htc_
loop_006spf.gif': No space left on device
C:\AndroidSDK\tools>
what now?

Try flashing this update.zip file (after nandroid backup of course!!!)
http://www.theandroidkitchen.com/CursorSense/CursorSense32A-NexusBootscreen-signed.zip

tried it didnt work!
just to clarify i have an htc magic 32A with MLIGN v.1.1

crisvillani said:
tried it didnt work!
just to clarify i have an htc magic 32A with MLIGN v.1.1
Click to expand...
Click to collapse
What was the error, if any?

Free some space
Looks like you ran out of space on your system partition. I searched through the forums for options. One I got was to restart the device and try again.
The only other thing I can suggest is to delete some safe files from the system folder (such as ringtones/wallpapers that you never have and never will use) to make some space.
Fire up a shell (adb shell) and then check in the system/media/audio/ringtones folder and delete (for example, rm Bubble.mp3) some files. Wallpapers are in system/customize/resource/
Slash

there was no error it flashed with no errors but when i reboot iget the same bootscreen

crisvillani said:
there was no error it flashed with no errors but when i reboot iget the same bootscreen
Click to expand...
Click to collapse
Oh, OK, MLIGN must have his bootscreen in a different folder...

the bootscreen is in system/media/bootscreen

slash12345 said:
Looks like you ran out of space on your system partition. I searched through the forums for options. One I got was to restart the device and try again.
The only other thing I can suggest is to delete some safe files from the system folder (such as ringtones/wallpapers that you never have and never will use) to make some space.
Fire up a shell (adb shell) and then check in the system/media/audio/ringtones folder and delete (for example, rm Bubble.mp3) some files. Wallpapers are in system/customize/resource/
Slash
Click to expand...
Click to collapse
could u plzz tell me exactly what to do not to familiar with adb shell

>adb shell
#adb remount
#cd /system/media/audio/ringtones
#ls
You'll see a list of files. Delete the one's you don't want using the rm command. For example,
#rm Bubble.mp3
(replace Bubble.mp3 with the filename you want to remove)
I think deleting 1-2 files should be enough. Then try pushing in the nexus animation again.

hey removed a couple of ringtones still get no space error!
wat ever it fine ill just stay with wat i got, ill wait until MLIGN adds it to his ROM in a future update
Thank you for the help though it was greatly aprreciated !!

Its the space!
I checked the filesizes of the animations, and now the error makes sense. The normal HTC logo animation is some 207K, while the Nexus One animation is ... wait for it ... 1,348K! The difference is more than 1 MB!
No wonder removing some ringtones did not make a difference. Each ringtone is less than 100K.
It seems that the best bet is to wait it out.
Hopefully, someone will cook a Nexus One ROM for us as a New Year present

[GUIDE] set up ADB on linux to recognize tf700

This post is adapted from a post in the android hacking general thread by user jackattack79.
I just changed the udev rules to work with our tf700's. Perhaps it can be helpful here. Thanks again to jackattack79 for the original post.
Anyone wanting to use adb with your ASUS Infinity through Ubuntu/Linux... follow these steps (these steps will make accessing adb much easier and allow abd to recognize your phone)[Please note - modifying the .bashrc in step 1 is not required; it will just make using Android SDK much easier for beginners]:
1. Modifying the PATH Environment Variable will help out immensely when it comes down to making use of SDK tools like ADB. Doing this will also allow you to execute certain protocols like ADB from ANY location. So if you're operating from the Desktop, you don't have to redirect to the SDK's platform-tools folder to make use of ADB if you need to make use of it.
To modify the PATH variable of your system, you need to edit your .bashrc file. To do so, in a terminal, execute the following command:
$ nano ~/.bashrc
You will now have the Nano text editor enabled on the terminal. Now, at the very top of the file(yes, that means go to the top and hit enter to create some space at the top. Then just copy and paste - a caveman really could do it!), enter the following:
#AndroidDev PATH
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
Once you're finished, press CTRL + X, Y, and then hit Enter to save your changes and exit the Nano text editor.
2. Now that we have our PATH variable set up, we need to make sure our hardware will be detected once we initialize ADB. However, Ubuntu won't allow ADB access to the Android phone via USB unless the appropriate udev rule is set. This is Bug #316215. In order to get around this rule, you need to create a rule file as root.
In a terminal, execute the following command that will create the rule file. This will utilize the graphical sudo command, so that we can still have control over the file if we're not a root user.
Now, you create a file:
sudo nano /etc/udev/rules.d/51-android.rules
Copy and paste the following udev rule in the text editor that opened up which contains the new rule file we created:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c91", MODE="0666" #Normal tf700
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4daf", MODE="0666" #Fastboot tf700
Once you've copied and pasted the udev rule in the text editor which contains your newly created rule file, save your changes and quit (Control+X, Y, Enter). Now that you've set your udev rule you have to reboot (shut down terminal and reopen; I also recommend unplugging your phone from usb and plugging it back in) so that ADB will be in your path.
To test your changes, open up a terminal and execute the following:
$ adb devices
You should now see:
List of devices attached
C61DAXXXXXXX device
If you see:
List of devices attached
???????????? no permissions
Reread this post and try again.
more helpful udev info here http://wiki.cyanogenmod.com/wiki/Udev

Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis

Mackis said:
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Click to expand...
Click to collapse
Yes, use the values you got with lsusb.
Did you set the permissions on the rules file to 0644 so all can read?

Yepp
ls -al /etc/udev/rules.d/51-android.rules
-rw-r--r-- 1 root root 194 okt 22 14:34 /etc/udev/rules.d/51-android.rules
And i even reloaded the udev rules by:
udevadm control --reload-rules
That way i don't have to reboot. But i tried rebooting to.....
Hmmmm in some mysteroius way USB debugging was disabled, i'm 100% confident i enabled it.......
Now i find my device puhhhhhhhhhh Was so near of reinstalling linux and going back to ubuntu 12.04 as a last resort.
Thanks for the help!!
Best regards Mackis

Mackis said:
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Click to expand...
Click to collapse
Are you using a US tf700 ASUS Infinity?
Just wondering why the product code was different for you.
Thanks

lowreeds said:
Are you using a US tf700 ASUS Infinity?
Just wondering why the product code was different for you.
Click to expand...
Click to collapse
lsusb with USB debugging disabled:
Bus 002 Device 070: ID 0b05:4c90 ASUSTek Computer, Inc.
lsusb with USB debugging enabled:
Bus 002 Device 071: ID 0b05:4c91 ASUSTek Computer, Inc.

64 bit used to require certain 32 bit libs to be installed once upon a time. Not sure if it's still the case, but you could try:
sudo apt-get install ia32-libs

_that said:
lsusb with USB debugging disabled:
Bus 002 Device 070: ID 0b05:4c90 ASUSTek Computer, Inc.
lsusb with USB debugging enabled:
Bus 002 Device 071: ID 0b05:4c91 ASUSTek Computer, Inc.[/QUOTE
Ahhh.
i see.
Click to expand...
Click to collapse

Yeah you are right, for some reason debugging was unchecked and im 100%sure i checked it. I have it up and running now. Thanks!!
//Mackis
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

lowreeds said:
List of devices attached
C70KASXXXXXX device
Click to expand...
Click to collapse
Just a heads up. I'm not sure it's such a good idea to out your serial number like that (I censored it in my quote for you)...

[q] Every rom gets stuck at bootscreen!...and I am terrified!!!!!!!!

Ok, here's the rundown. I tried to install a custom rom on my phone. Used the all in one tool thing to root and unlock bootloader. I've tried three different ROMs and so far, they keep getting stuck at their respective boot logo screens (Cyanomods circle thing, AOKP Unicorn picture, ETC). I don't know what I am doing wrong. I found an error thread that mentioned something about me needing to flash the boot image in the CMD prompt but when I do this (used the "fastboot flash boot boot.img" command), it shows me no improvement. As I am not knowledgeable enough to even figure out how to restore my phone to factory, I am freaking the hell out! Is there one of you gurus would could save me from my madness. I saw all these cool ROMs, wanted to try them and now my phone is little more than a moving graphic. Please help!!!!

Your extracting the boot IMG from the ROM zip?
Then fastboot flash boot.img
Sent from my HOX w/CM10.1

subarudroid said:
Your extracting the boot IMG from the ROM zip?
Then fastboot flash boot.img
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Thanks for responding. Yes, I took the boot.img from the ROM and have tried repeatedly to do the fastboot thing. For some reason, whenevr I enter the command, I get a rush of gibberish (I pasted what I get below). Then I reboot and all and nothing changes, it'll sit at the bootloop forever.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Eric>adb>fastboot flash boot boot.img
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Eric>

OK let try and make this easy.
Download a stock ROM ie Scotts ROM then flash that in recovery and it should boot up just fine.
Then us the apk in this thread to flash the boot.IMG. http://forum.xda-developers.com/showthread.php?p=33463262
for any ROM you want. If you get some time read up on downgrading the Hboot with jet. But that should get you going. Let me know if you need anymore help
Sent from my HOX w/CM10.1

subarudroid said:
OK let try and make this easy.
Download a stock ROM ie Scotts ROM then flash that in recovery and it should boot up just fine.
Then us the apk in this thread to flash the boot.IMG. http://forum.xda-developers.com/showthread.php?p=33463262
for any ROM you want. If you get some time read up on downgrading the Hboot with jet. But that should get you going. Let me know if you need anymore help
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Ok, where do I find Scotts ROM? It will somehow circumvent the issue? I will use the apk you gave me when I get this up and running. Thanks so much man, I'm still super new to this.

http://forum.xda-developers.com/showthread.php?p=37672182
There you go. Because your on a stock kernel or stuck with that till you can flash a boot.img this should boot up after you flash it.
Sent from my HOX w/CM10.1
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
One more thing for some light reading to help you out.
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my HOX w/CM10.1

subarudroid said:
http://forum.xda-developers.com/showthread.php?p=37672182
There you go. Because your on a stock kernel or stuck with that till you can flash a boot.img this should boot up after you flash it.
Sent from my HOX w/CM10.1
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
One more thing for some light reading to help you out.
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Thanks so much for all the help guys, but I am still hitting the same error. In the TWRP window, the one that pops up once I swipe to confirm that I wish to flash, i am still seeing "E:Unable to mount '/data', and then when I reboot , I get stuck. Do I need to start looking for a new phone here? Starting to worry me now

Forget what twrp says, when you plug into PC check for the drive you may have to format. You are very far from needing a new phone!
Sent from my HOX w/CM10.1

subarudroid said:
Forget what twrp says, when you plug into PC check for the drive you may have to format. You are very far from needing a new phone!
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Glad to hear that lol Not showing up on my computer, though I can reset into recovery, mount the drive and find it that way. Should I reformat, place them on there and try again? Right now it flashes some white squares every 2 mins or so and then powers down and then on again.

http://forums.team-nocturnal.com/showthread.php/1050
Check out this link
3.0 USB can be a problem. Make sure you HTC drivers are installed.
Sent from my HOX w/CM10.1
---------- Post added at 07:18 PM ---------- Previous post was at 07:10 PM ----------
gulley81283 said:
Thanks so much for all the help guys, but I am still hitting the same error. In the TWRP window, the one that pops up once I swipe to confirm that I wish to flash, i am still seeing "E:Unable to mount '/data', and then when I reboot , I get stuck. Do I need to start looking for a new phone here? Starting to worry me now
Click to expand...
Click to collapse
Are you able to transfer the ROM zip? If so unchecked md5 before you flash.
Sent from my HOX w/CM10.1

I also am suddenly unable to boot any rom...

Lets learn how to hit the thanks button for a guy thats totally saving your ass huh..?
Sent from my HTC One XL using xda premium

These guys can't figure out how to do anything right. They can't be expected to figure out how to thank anyone
Sent from my HTC One XL

954wrecker said:
These guys can't figure out how to do anything right. They can't be expected to figure out how to thank anyone
Sent from my HTC One XL
Click to expand...
Click to collapse
Or we're just decently new the site and thus don't know all of the protocols and customs. Don't be a ****, son.

Being a **** would be sending folks on a wild goose chase or perhaps help permabrick your device. We take time away from our family,work,lives to help ungrateful people fix there devices. And all we freakin ask is for them to hit the thanks button.
Sent from my HOX w/CM10.1 4.2.2 s-off

I'm on a meme kick today tgif
Sent from my HOX w/CM10.1 4.2.2 s-off

The first question to all of these threads should be "DO YOU HAVE THE RIGHT FORUM?" I bet at least one of these complaints is someone with a quad-core....

subarudroid said:
I'm on a meme kick today tgif
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
Again, I'm ungrateful because I don't know the customs of the site? Once your rude buddy up there brought it up, I went back and actually clicked the "thanks" button. is there anything further needed to justify my thanks or will that suffice? You guys take this stuff a bit too seriously, me thinks.

Hold on..... I never said you were or are ungrateful. it just so happens if sinco or wrecker did not make a "rude" statement you would have not hit the thanks. You just confirmed that's why you did so. I do the same for them when they are helping out in a thread. Its just constructive criticism. There was no need for name calling like penis or vagina. We are here to help. that's the worst hazing you get..... For now
Sent from my HOX w/CM10.1 4.2.2 s-off

gulley81283 said:
Again, I'm ungrateful because I don't know the customs of the site? Once your rude buddy up there brought it up, I went back and actually clicked the "thanks" button. is there anything further needed to justify my thanks or will that suffice? You guys take this stuff a bit too seriously, me thinks.
Click to expand...
Click to collapse
Dude, get some thicker skin or kindly eff off, will you? Jesus. Hissy fit over nothing.

[GUIDE]( Easiest) All about ADB, logcat, shell

ADB:-
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as reooting and rebooting in recovery ode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
A little amount of brain
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. Howeve, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
Forgot next ones, will write later
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
My Uncle: For gifting me this Phone
My Teachers: For teaching me English(I would not be here without them)
You: For future Thanks
Till now, thats it, will add some more things later
If any problem, I will add it too
Suggestion? They are welcome

[GUIDE][ADB] How to take a logcat

iamareebjamal said:
ADB:-
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as rebooting and rebooting in recovery mode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
A little amount of brain
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
USB Debugging MUST be turned ON in the device for ADB to see it & Developer options is hidden in Android 4.2 and
above, Hitting Build number 10 times in
About Phone/Tablet reveals the menu (Thanks lilHermit for reminding me to add it)
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE (If you however want to set environment variables. Click on Show Content)
We can easily append the sdk platform-tools and tools folder to your systems environmental path variable directly from command line(cmd) by simply issuing one command and performing a system reboot:
Code:
SETX PATH "%PATH%;[COLOR="Indigo"]SDK_Install_Path[/COLOR]\platform-tools;[COLOR="Indigo"]SDK_Install_Path[/COLOR]\android-sdk-windows\tools" -m
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
(Thanks to WugFresh for telling me :victory
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. Howeve, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Note:
If you have spaces in path of apk, you can execute the command without breakage if you include the path inside quotes. (Thanks to etcman)
Eg:-
Code:
adb install "G:\Program Files\AreeB.apk"
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
ls: Shows list of directory
cd: Changes working directory
rm: Removes the file
logcat: Displays logcat
mount: Mounts the partition
busybox: Busybox Applets
Forgot next ones, will write later
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
paxChristos for amazing logcat guide
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
My Uncle: For gifting me this Phone
My Teachers: For teaching me English(I would not be here without them)
You: For future Thanks
Till now, thats it, will add some more things later
If any problem, I will add it too
Suggestion? They are welcome
Click to expand...
Click to collapse
This should help the new members in appealing their problems in a deeper and better way.
Originally posted by iamareebjamal
Original thread here.