Develop Bugs

[Oct-27] Replacement Bootsplashes (every ROM) & Animated Bootscreens for HTC Roms

Replacement Bootsplashes (every ROM) & Animated Bootscreens for HTC Roms
Hello Everyone,
I was getting sick of hearing the same boot noises and pictures. The HTC startup is pretty ok, but I think mine's a little more polished. I made 2 themes.
1. The first theme follows HTC new advertisement campaign - Quietly Brilliant. There are 2 effects to pick from, Blend or Burn-in.
2. The second theme has the same old HTC logo, but with better animations and the ubuntu logo at the beginning.
Each Bootscreen pack has a bootsplash file as well for replacing the T-Mobile Screen.
The sounds are from www.gnome-look.org, however I have edited them to match. Let me know what you think!
HOW TO APPLY:
HTC ROMs:
1. ADB push the boot.gif to /system/media/boot.gif
Code:
adb remount
adb push %pathtosavedfiles%\boot.gif /system/media/boot.gif
2. ADB push the boot.mp3 to /system/media/boot.mp3
Code:
adb remount
adb push %pathtosavedfiles%\boot.mp3 /system/media/boot.mp3
3. Search on the forums for 'boot screen flasher 3000'
4. Download and extract the folder to C:\Temp\BootScreenFlasher3000\%zipcontents%
5. Place the file called 'mysplash.rgb565' from my zip into the folder in step 4.
5. Open a command prompt (Start Menu > Run > cmd > ok) and type
Code:
cd C:\Temp\BootScreenFlasher\
bootflash.bat
6. Follow the instructions to flash it.
To do it though the terminal:
1. After downloading the zip to your sdcard (download crutch-much?), extract the contents to the root of your SD card.
2. Remount your file system as Read Write (can't remember how to do it, search )
3. Open Terminal Emulator
4. Type:
Code:
su
cp -f /sdcard/boot.gif /system/media/boot.gif
cp -f /sdcard/boot.mp3 /system/media/boot.mp3
This will only update the animation, I'm not sure how to update the bootsplash from on the phone. You need fastboot, and I think that's only do-able on a computer.
You will now have both the T-Mobile replacement and the HTC animated replacement screens.
ALL OTHER ROMs:
1. Search on the forums for 'boot screen flasher 3000'
2. Download and extract the folder to C:\Temp\BootScreenFlasher3000\%zipcontents%
3. Place the file called 'mysplash.rgb565' from my zip into the folder in step 4.
4. Open a command prompt (Start Menu > Run > cmd > ok) and type
Code:
cd C:\Temp\BootScreenFlasher\
bootflash.bat
5. Follow the instructions to flash it.
That's all. Thanks ccunningham83 for reminding me about instructions...

Any way to do this on a linux system? Wold like to try it out. Thanks

Hey, not sure yet. I'll have to get back to you...do you want to take a look at how to setup adb in linux. It's around here. I'll see if I can figure out how to do the bootflash...

Can you do it through terminal?

will this work with cyanogenmod?

Terminal Instructions
No, HTC only. Sadly. I'm working on converting all of my boot animations to the Nexus one...stay tuned!
To do it though the terminal:
1. After downloading the zip to your sdcard (download crutch-much?), extract the contents to the root of your SD card.
2. Remount your file system as Read Write (can't remember how to do it, search )
3. Open Terminal Emulator
4. Type:
Code:
su
cp -f /sdcard/boot.gif /system/media/boot.gif
cp -f /sdcard/boot.mp3 /system/media/boot.mp3
This will only update the animation, I'm not sure how to update the bootsplash from on the phone. You need fastboot, and I think that's only do-able on a computer.

By HTC do you mean HTC Phones, or a specific phone?

Macrophage001 said:
By HTC do you mean HTC Phones, or a specific phone?
Click to expand...
Click to collapse
dunno what he means by HTC phones, but I know animated bootscreens won't work on anything below Android 2.0.

r3s-rt said:
dunno what he means by HTC phones, but I know animated bootscreens won't work on anything below Android 2.0.
Click to expand...
Click to collapse
I meant HTC ROMs. The HTC ROMs for the G1 have animated boot support.

so why doseny cyanogen?

olvap377 said:
so why doseny cyanogen?
Click to expand...
Click to collapse
cyanogen is 1.6. roms like open eclair and the such are 2.0 - 2.x. only 2.0 - 2.x have support for animated boot screens.

olvap377 said:
so why doseny cyanogen?
Click to expand...
Click to collapse
Because Cyanogen uses the Google build. HTC builds are built by HTC not Google. There source code is different.

[Q] how to root defy on mac?

I was trying to root my defy with my macbook. I tried superoneclick, but it doesn't work on mac.
I tried z4root on this website [http://forum.xda-developers.com/showthread.php?t=833953]. But it didn't work for me as well it was stuck with "acquiring root shell". But on the website, it said it's compatible with defy.
Does anyone know how to root defy on a mac
Thanks a lot

Even if you could root your defy using a Mac, you'd still need Windows to run RDS lite.
Sucks, I know... but there it is.

On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.

Being under Linux, I use sbf_flash for flashing and root the phone manually via adb.
Though I don't know about any macos alternatives.
sbf_flash has been updated; there's now a mac os x port, in addition, support has been added for the Defy, Charm and possibly the Atrix.
Click to expand...
Click to collapse
So it's also working for Macos, great.

MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
oh really? thanks a lot

Can u please put down the steps when ur free
MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App

Wow! I didn't know about sbf-flash.
Thanks for the heads-up.

My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC

MisterWB said:
My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC
Click to expand...
Click to collapse
I am kind of stuck, What do u mean by "USB..." for step 5? Is it usb connection? and for step 6 is it "charge only" for "none"?
I typed "adb shell" in terminal and it was like "command not found".
What should I do now? Btw, thanks for helping

Right, step 5 is "USB Connexion"
and step 6 "Charge only", text may change with language and rom version.
Regarding "adb" it's part of Android SDK: http://developer.android.com/sdk/index.html
So you have to download full SDK kit and install it....
...or use adb executable for mac attached below
On my mac I putted it into /usr/bin
1) In Finder put adb.zip into Download directory
2) In Finder Download directory, extract adb.zip, you'll get an "adb" file
3) Open Terminal
4) Go into Download directory
cd ~/Download
5) Copy adb file into /usr/bin with executable permissions
sudo cp adb /usr/bin/ -> and type your session's password
sudo chmod 755 /usr/bin/adb -> and type your session's password
next you can use "adb shell" like any unix command
Keep me inform

I found the link to download sbf_flash for mac
http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html

[A] How to Root Defy Android OS 2.1 on mac
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.

beefinit said:
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.
Click to expand...
Click to collapse
I followed the simple directions in the thread recommended by beefinit. The root.command script that comes with the G2xRootMacLinux_v0.5.zip package appears to have successfully rooted my Defy. The script is designed for a Tmobile LG G2x, but is based on SuperOneClick 1.8, so the fact that is seems to work for the Defy is not that surprising.
Here is the terminal log from when I ran the script:
Last login: Thu May 17 10:41:29 on console
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2604 KB/s (585731 bytes in 0.219s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
100 KB/s (26324 bytes in 0.255s)
Pushing busybox to /system/bin/busybox...
3162 KB/s (1062992 bytes in 0.328s)
Installing Superuser.apk android application...
775 KB/s (196521 bytes in 0.247s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
I'm very new at rooting phones but Superuser app is now installed and I've also installed ROM Toolbox Pro and confirmed that I can get a # prompt via it's Terminal Emulator.
My Defy is an unlocked MB525, Android 2.2.1, System version 34.4.9.MB525.T-Mobile.en.US, Kernel 2.6.32.9-g8431013, Build number 3.4.2-107_JDN-9

[GUIDE] Mini guide to root Gnex manually

1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.

it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )

cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.

Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.

You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium

smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]

Need help

so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.

To Root HTC One VX
LordXombie said:
so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.
Click to expand...
Click to collapse
First Unlock Bootloader And Then Root. :silly:

i have unlocked the phone. but it will not allow me to access the bootloader unless threw other means. while in the bootloader it says tampered followed by unlocked. i cannot seem to figure out what is going on.

How to root htc one vx
HTC One VX comes from the
HTC One series of
smartphones consisting of
high-end specifications, such
as Dual-Core processors and
the latest version of Android
on-board. While we already
have a root guide for the
One VX, another root
method has popped-up on
XDA and to help users root
their devices with this new
method, here we’re
presenting a tutorial
explaining everything you
need to root your device.
So, let’s see how you can
root your HTC One VX
smartphone.
I. Before You Begin:
1. This will void the warranty
of the device. However, you
can reinstate it by unrooting
the device if there’s any
unrooting procedure
available.
2. The following procedure
works on Windows based
PCs only.
II. Downloading
Required Files:
download file. http://forum.xda-developers.com/showthread.php?t=2123359
III. Rooting the HTC
One VX:
1. Place the Root Package
archive on the Desktop of
your PC.
2. Extract files from the
archive to your Desktop.
Don’t launch any files just
yet.
3. Turn ON the USB
debugging option on your
device by heading to
Menu>>Settings>>Developer
options>>USB debugging .
4. Turn OFF the device.
5. Reboot the device into
Fastboot mode. To do so,
simply hold down the
Volume DOWN+Power
buttons together.
6. Once inside the Fastboot
mode, connect the device to
your PC using the USB cable.
7. Open a Command Prompt
Window on your Desktop. To
do that, hold down the Shift
button on your keyboard
and right-click on any empty
area on the screen, then
select Open command
window here .
8. Type in following
command into the Command
Prompt Window:
fastboot flash boot boot.img
9. Once it’s done, issue the
following command:
fastboot reboot
10. Your device will reboot.
Once it boots up, enter the
following command:
adb remount
11. Next, enter following
commands into the
Command Prompt Window
one-by-one. Press ENTER
after each line you type:
adb push Superuser.apk /system/app/
adb push su /system/xbin/
adb shell mkdir /system/bin/.ext
adb push .su /system/bin/.ext/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 6755 /system/bin/.ext/.su
adb shell chmod 777 /system/bin/.ext
adb shell ln -s /system/xbin/su /system/bin/su
adb reboot
12. Your device will reboot
in normal mode.
13. Once it boots up, simply
open the Superuser app
from your App Drawer.
14. Tap the Update binaries
button in the app and let it
do the rest of the work.
15. And you’re all done!
Brilliant! Your device has
been successfully rooted and
the SU binaries have also
been updated. Now load-up
some root-only apps on
your device to realize the
power of root-access!