Related
I've got the HTC Hero from Orange and noticed that the ROM version is higher than the one posted in this forum (Build 1.76.61.3). If somebody could explain how to pull the ROM from the phone I'd be happy to post it.
can u adb into it? if so you just need to type the following in command prompt if your using windows:
adb pull /system
Sweet god you can be a hero if you can use adb and type the following command:
adb pull /proc/config.gz .
and attach the file here!
You can load the 1.3.1 recovery (i think) and nandroid backup the system!
*************THIS IS A GUESS ON HOW TO DO IT!*****************
I bet someone will help you get this dumped!
but you can probably dump the following like so:
adb pull /system ./system (make the folder in your adb directory)
adb pull /data ./data (make the folder in your adb directory)
adb pull /etc ./etc (make the folder in your adb directory)
cat /dev/mtd/mtd1 > /sdcard/recovery.img
cat /dev/mtd/mtd2 > /sdcard/boot.img
adb pull /sdcard/recovery.img . < there is a . after it and it needs to be there! >
adb pull /sdcard/boot.img . < there is a . after it and it needs to be there! >
This would be my guess on how to do it, but i could be wrong.
I'm downloading the SDK now, will post back if I managed to get anything from the phone.
PS: If I post all those things will any of my personal settings/data be included?
I've tried all those commands, the only one that worked is the adb pull /system ./system , it didn't work for etc and data, reckoned there weren't any files to copy. the cat... ones just didn't do anything. I'm guessing this is because I'm not rooted on the phone. Any suggestions?
herman3101 said:
I've tried all those commands, the only one that worked is the adb pull /system ./system , it didn't work for etc and data, reckoned there weren't any files to copy. the cat... ones just didn't do anything. I'm guessing this is because I'm not rooted on the phone. Any suggestions?
Click to expand...
Click to collapse
System is enough Now please upload it to megaupload/rapidshare
Does system include any user modified files or is it read only during use?
herman3101 said:
Does system include any user modified files or is it read only during use?
Click to expand...
Click to collapse
system is readonly
Excellent, it's still uploading and I will update my other post with the link once it's done. I've also uploaded the config.gz as somebody requested it.
Thank you very much I thing JAC can make a great rom out of this!
upload finished, link on other thread
this thread is done
for more info and the rom look here
http://forum.xda-developers.com/showthread.php?t=540680
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.
Root Galaxy Nexus (Either GSM or LTE) in Linux (Personally in Ubuntu)
Disclaimer: I am not at fault for anything you have done to your phone (ie. Brick, break, etc.). You are doing this at your own discression. I am merely stating what I did to unlock/root my phone.
Tutorial Broken Down Into Three Sections
I. Unlocking the bootloader
II. Installing Clockwork Mod Recovery
III. Installing SuperUser
Resources
1. Super User (used by flashing in Clockwork): http://download.clockworkmod.com/test/su.zip
You can get the latest version here: SuperUser by ChainsDD
2. Clockwork – based by carrier
1. Verizon (CDMA) version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.4-toro.img
MD5:*b2d31c29b7ef785f9c0802a12264d322
File size:*5,263,360*(bytes)
2. GSM version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.2-maguro.img
MD5:*445887336a863573997ccbaeedddc984
File size:*5,427,200*(bytes)
Unlocking Bootloader
Part 1: Unlock
1. First off, you need to download the adb drivers. There have been mentions of just getting the drivers, but I actually have the entire SDK. You can download it here. http://developer.android.com/sdk/index.html
2. Plug in your device, then open up Terminal (Ctrl + Alt + T) and type in: “lsusb” (without quotes). This will pull up all the devices plugged into your usb slots. Look for the one that says samsung (others have found google, but please make note).
3. Find the device, then find where it says ID. After where it says ID, it should have a number/letter mix such as “04e8” or such. Make note of that for later.
4. Go to http://developer.android.com/guide/developing/device.html . This will give the instructions on how to Install the device drivers (specific to each manufacturer). Start from where it says “4. Set up your system to detect your device.”
5. Go to your internal and cd to platform-tools. (This should include both adb and fastboot.) Put your phone into fast boot. (Do this by holding the power, volume up, and volume down buttons while phone is off).
6. Once in fastboot, go back to your computer and type in “sudo fastboot oem unlock”. This will bring up the option to unlock your phone's bootloader on your device's screen. It will give you a disclaimer, and it will say that if you unlock, it will wipe all of your phone's data. Scroll to Yes using the vol up or vol down buttons, and select it with the power button.
7. If you boot straight from there, you will go through a series of boot loops (it was 2 for me) then will be prompted to go through the process of setting up your Google account again. again.
Congratulations, your phone is now unlocked. However, this doesn't mean that you have rooted your phone.
Rooting
Part 2: Putting Clockwork Mod Recovery On Your Phone
(do step one for preparation of Part 3)
1. First, we will want to push su.zip to your phone's Internal storage or “sdcard” partition. Open up Terminal and type the command “adb push 'directory_of_su.zip'/su.zip /sdcard/”. Hit enter/return and it should transfer over. (Based on the quality of usb cord, times of transfer may vary.)
To make this easier, put su.zip into the directory of adb. Then all you have to use for the command is “adb push su.zip /sdcard/”.EDIT:
After you root, you have to delete /system/recovery-from-boot.p and reflash or else every time you reboot, the recovery partition will be written over by android. This can either be done in terminal (phone or comp) or by a file manager with root access (such as Root Explorer).
Reference: http://forum.xda-developers.com/showthread.php?t=1392336
Thanks vihil
2. Put your phone in fastboot mode again (vol up + vol down + power)
3. Go back to Terminal and type in “fastboot flash recovery 'whatever the file name is'”. This will flash CWM (Clockwork Mod) onto your phone, deleting your phone's stock recovery image.
EDIT: If it doesn't work, i.e. due to permissions, run with sudo
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.
Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Special Thanks to scary alien on androidforums.com and jcarrz1 on XDA
Reserved
Reserved......
Thanks a lot I was looking for exactly this. Appreciated. Will try in a few hours when I get my phone.
Downloaded the sdk file but have no idea what to do. My windows computer died and it would be a lot easier on that to do all this but all I have is a computer with linux currently so if anyone would be kind enough to tell me how to install sdk I'd appreciate it. I seen the read me and seen it says execute "android" first but I don't know how to do that. I realize this is incredibly annoying to the xda hive mind trust me I hate needing help like this I'm nothing close to a noob as far as rooting flashing and all that good stuff I'm just unfortunately stuck with only Linux. I'd really really appreciate it.
under the tools folder there is a script called android, u can either run it in a terminal or hopefully if u were to click it, it was ask if u want to run it!
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Seems like my fastboot is stuck on `waiting for device`. I have the fastboot screen on my GN.
Before rebooting into fastboot `adb devices` successfully showed a device (i.e., usb debugging is enabled, dunno whether it is needed for the unlocking):
$ fastboot oem unlock
< waiting for device >
Any idea?
EDIT: Found the solution. After doing a `fastboot devices` it told me "no permissions fastboot" so I needed to be root on my computer for it to work.
FadedLite said:
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Click to expand...
Click to collapse
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
C-4Nati said:
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
Click to expand...
Click to collapse
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
For simplicity, you can shorten that to: mount -o rw,remount /system
You can also delete it from a terminal on the phone or any file manager that allows root access. I think the free ES file explorer has root options.
vihil said:
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
Click to expand...
Click to collapse
for needing to type in lsusb, i found that as somewhat of a precaution. I had seen on other threads that others had their device show up as either google or samsung. So i just figured rather check first instead of installing both or something.
for the preparation, basically you do that since your phone is already on. after flashing cwm, you would have to boot back into your phone, push the file to your sdcard, then boot back into recovery. All it does is that it saves just a bit of time.
As for the sudo fastboot, I didn't actually have to do that, but i'll add it, Thanks.
As for the cwm terminal commands, i'll add that as well. Thanks again.
FadedLite said:
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Click to expand...
Click to collapse
not yet. after flashing su-bin-3.0.3.2-efghi-signed.zip (which is just the binary), the user still needs to flash Superuser-3.0.7-efghi-signed.zip, to have Superuser.apk placed in /system/app, otherwise GUI apps won't have access to su. (unless, of course, the zip you are linking here has them both)
It's preferable to have users linked to ChainsDD website, there people will find latest binaries and Superuser.apk. I also don't see any mention to him in the OP. Even if this is a tutorial, don't forget to give credit where needed.
Some help for an Ubuntu Noob/Not a Noob to Windows
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
jmartino5920 said:
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
Click to expand...
Click to collapse
Are you getting a "waiting on device" message or something similar when you run adb or fastboot?
Forget about the udev nonsense (not important really until you start developing full time) and just drop a sudo before your commands.
You can shoot me a PM or a gtalk (same username as my xda) if you want and I'd be more than happy to help you get your system going.
Thanks, still a bit more annoying that Windows but this tutorial makes it easy.
Sorry if this is ignorant, but can I use these instructions with Unix & terminal on Mac OS X? I'm thinking yes???
I rooted mine in linux as well... No problems. For some reason I was able to do it much easier though...
I did the fastboot oem unlock step above (Part 1). Rebooted then installed superuser from the android market. Then I installed Clockworkmod from the android market.
Done.
Not sure if I'm missing out on something by doing it this way but so far I've had no issues....
Script to flash via CWM to fix fix perms has been done by minotauri (sorry if miss spelled will fix when on a computer) he deserves credit for the edify:
To Run Fix Perms While in Recovery Flash this file each and every time you need it run [for now]:
http://goo.gl/hrL7E
The Next Script is one you can flash via CWM and it will replace the file ROM Manager uses so this will remain between restarts and you can use it via ROM Manager or Script Manager anytime you want!:
Thank Minotauri again for another beautiful Edify!
http://goo.gl/qPpC3
Flash via CWM and it well work for that flash just flash anytime you need to run it via recovery until I see about permanently copying it over existing script or still can run manually with this guide if you choose [scroll down below the additional update on how to fix the script to run using ROM Manager while in OS!].
I posted this in a couple ROM threads and was asked to throw it out here as folks from different ROMs are all affected. I can only speak for TMobile Galaxy S2 as that is what I own, drive and work on...
I will be cleaning up the post a bit when I get time just want it posted so others can use the information add it really seems to help clean up small issues (even some report fixing multiple FCs after running fix perms this way!)
NEWEST UPDATE 2012.04.19
OK FIX FOR RUNNING FIX PERMS INSIDE OS VIA ROM MANAGER
If you adjust first line in script to #!/system/xbin/sh viola ROM Manager does not freeze [finally]
I did this with Ghost Commander [don't forget settings> check auto root] and long press fix_permissions and choose edit tapping it will have GC try to execute it.
I also moved down to set variables piece and placed 1s instead of 0s next to mount system, mount data, and remove (as in REMOVE stale data ) [should be all caps in /data/data/com.koushidutta.rommanger/files/fix_permissions
I am still working on finding a way of making those changes permanent in /sbin under recovery boots
Fix Permissions Work Around ICS
Run Fix Permissions via ADB Shell with Phone in Recovery
I have taken the time to document what should be a complete guide to running fix permissions while the phone is in the Recovery menu using adb.
I am posting the quick steps right after this, but if you scroll below that this is an extended step-by-step guide.
Code:
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Supplies [Phone, USB Cable and Android SDK (http://developer.android.com/sdk/index.html)
Follow the link to install Android SDK [they have directions on site]
first time installing adb? [Skip otherwise]
To Add ADB to your computers path [to run it from any directory]
Windows:
Open Command Prompt [Click Start, Click Run, Type in cmd and hit Enter [XP]]
Open Command Prompt [Click Start, type cmd in whitebox and hit Enter [Vista and 7]]
type set PATH=%PATH%;C:\android-sdk\platform-tools [or wherever you put android sdk just add platform-tools to the end [it is a hidden folder]
Linux [OSX should be same]:
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved it]
export PATH
Now That You Have ADB and path set, time for good stuff
Opening a Command Processor
Open a Command Prompt [Windows] or Terminal [Linux or OSX]
Windows: Click Start, Click Run, Type cmd and hit enter [XP]
Click Start, type in to Whitebox cmd and hit Enter [Vista and 7]
Linux: Hold alt and hit F2 on keyboard [should see a run box now]
Type in xfce4-terminal and hit Enter [or substitute your terminal command this is xubuntus]
Once a Black and White Screen Opens...
Gaining Elevated [Admin or Root Privileges]
Ok, some further testing shows me you should have root or admin access to command processor before running ADB.
In Windows
Type The Following in to the command prompt window already open...
runas /user:%computername%\administrator cmd
hit enter when done
[yes just like that including %computername% windows will fill it in with proper info copy/paste if needed right clicking in command window should paste text for you [if not right click on the icon in left hand corner of title bar choose properties and place checks in the quick edit and insert mode boxes under Options tab]
now it will ask for a password if you have not set one you need to go to control panel users and set a password on admin account before this will work
Once you enter the password and hit enter a second command window will open and will have Administrator in the title
Now You can continue on
In Linux
With Terminal window open type:
gksudo xfce4-terminal& [sub your terminal command if not using xubuntu]
once you hit enter it may take a second but you will get a password prompt enter in your password and a new terminal will open and it will have [email protected] in the title
Now you can continue on...
Checking USB Connection
type in adb devices and hit enter
[if you get a command not found you will have to use cd to move to directory with adb [ie cd c:\android-sdk\platform-tools]
If it comes back with ?????? as serial number it is not connecting correctly follow the next steps otherwise skip the next bit if you didnt get all ?
I get ?????, what gives?
This seems due to not running command prompt or terminal as administrator or root user [Windows / Linux Respectively]
You will need to do the following in order
Disconnect USB from phone
On Phone: In Advanced menu choose restart recovery
On Computer: type in adb kill-server and hit enter
Reconnect USB cable
Be Sure To Follow Section above labeled: Gaining Elevated [Admin or Root Privileges] and then continue on
On Computer: type adb devices and you should see a mix of letters and numbers
and that means we are good to go on
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
Known Issues:
-------
Issue: My computer does not connect when I use adb shell [or I get ????? when I use adb devices]
Resolution:
I have found that i have to connect my phone 2x to computer to get it to work correctly most of the time, do the following
Disconnect USB from phone
In advanced menu on phone choose Restart Recovery
on computer: adb kill-server
Reconnect USB cable
on computer: adb devices
and you should now see a mix of numbers and letters and not ????? and now adb shell should connect
Issue when I try sh fix_permissions it says it can not find the file
Resolution: This is normally caused when you have not mounted /system [via phone]
or you did not use sh /sbin/fix_permissions [or be sure to do cd /sbin before sh fix_permissions
Issue: I get UID Read-only variable error and fix permissions does not run
Resolution: This is normally caused by either not mounting /system [via phone]
or not using sh fix_permissions.
Issue: Some of my apps are listed as /data/blah and it says it can not find the file
Resolution: This is normally caused by not mounting /data [via phone]
Issue: CWM will not mount /system or /data saying it can not find or read them
Resolution: I have found CWM does not like to load mounts once they are encrypted. If you have encrypted your device /system and /data are affected, try unencrypting your phone and trying again.
(this is a good thing it shows third parties tools trying to get around booting OS to read data will not be able to get at the information in your phone)
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
SEE This post for the current script
http://forum.xda-developers.com/showpost.php?p=25023284&postcount=22
Sent from my SAMSUNG-SGH-T989 using xda premium
Well judging by the title that you have there referred to running the script via recovery adb to begin with.
A lot of users don't realize if fix perms says complete in 2 secs it had a problem so I didn't know of that thread, but hope this will be a catch all for fix perms and not just for those who already tried via recovery and adb shell and got that specific error.
Thanks for looking out though
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
jangst123 said:
This is already and has been in the Q & A section.... Not development, but I wish the developers would look at it and figure out why we have issue on ICS
http://forum.xda-developers.com/showthread.php?t=1595806[Q] Problem with Fix Permissions (line 64: UID readonly variable) [WORK AROUND FOUND]
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I think posting this in Dev section is perfect sense. Also, thanks for the fix. This has stumped me for a while trying to figure out what to do.
When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?
Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem
would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?
Dougshell said:
would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?
Click to expand...
Click to collapse
+1 I'm completely stumped!
I can't get adb to even reconize the damn phone im on ravers remix to ics
peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
turn on debugging
RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
Raverx3x any idea why we are having this problem!?
Should we be running a different fix_permissions on ICS?
Also see..
http://forum.xda-developers.com/showthread.php?t=1595806
being that we seem to be determined to have this discussion in 2 different threads
l-levit said:
Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem
Click to expand...
Click to collapse
Or you could have devs talk here and keep users in QA so this doesn't get flooded with chatter.
Our should we delete all those ROM threads in Dev that exist in QA as well?
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
OGWisdom said:
When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?
Click to expand...
Click to collapse
Did you forget to mount /data in mounts and storage (on phone) before running?
Did you encrypt your device? I have CWM fail to load mounts after encryption
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
Oh and other thread just ganked my fix which is cool but I did this on my own not in response to anything so seeing as how I had to put in 2 hours of actual research, scratching my head, trying many different ways and seeing as how this is more of a process then simply loading a script I wanted to maintain it here until I can edit script or another Dev does making it cleaner and easier to manage and thus ready for more casual users found in QA threads.
Sheesh, sorry I figured this out maybe next time I won't pass on the info for fear of debating where it should be posted rather than the content and how to make it better going forward.
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information
peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
I have instructions on that issue on post.
Did you run adb devices and get ????? unknown device?
I had to run terminal as administrator, then I issued adb kill-server and reconnected phone and then did adb devices again and then it will say starting adb blah blah blah and then I got 6f7y88 [made up it should be a series of numbers and letters and no ?]
make sure adb devices gives you a valid response and not ????? I have found I almost always have to connect phone twice and at least do the above [with regular terminal I only used admin on first run but there in case it does make a difference].
So everytime I conect [or just about] I have to connect the phone
run adb devices get ????? and then
Disconnect USB
on phone in advanced menu choose restart recovery
on computer adb kill-server
Reconnect USB
Run adb devices and get a good serial number listed
I have to do actual work for a couple hours and then will be cleaning up main post on top and adding that bit in a place it get noticed more easily bear with me as I make my boss happy [he is wondering why things aren't getting done round here now ut-oh LoL] then I will clean up the information.
l-levit said:
u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information
Click to expand...
Click to collapse
Um, actually I just noted they used my solution and said it was cool to do so, it appears you have an axe to grind with me and are just nit picking anything I say. I am sorry if yoyu do not feel my work is not to the same level as other folks, but since I put in work and this is more of a manual fix you have to work at rather than an easy to use script [yet], I did not want to post it in QA and all until I have something better for general release.
Also, I am not mad, just wondering why you would rather start silly arguments over placement of usable useful information rather than helping to make said information better and more stable for release to others.
Are you mad I figured this out and posted it before you or something as I have never talked with you and given you no reason to troll my threads?
When I do have a stable script [well at least semi stable for release to dev then more stable for QA]. The way I view QA is for general users questions and answers and since I was going to work on DEVELOPING a script that does work I was holding off on a QA thread, once I do get a script together I will be releasing it. In the meantime I was hoping to have more advanced users and devs dissect my process here and give me feedback towards a full script.
ALSO, by using sh /sbin/fix_permission OR doing cd /sbin and then fix_permissions you negate any need to do any path variable adjustments BUT if you rather then here is how...
when in adb shell before anything
PATH=$PATH:/sbin
export PATH
will then make it so you can just fix_permissions regardless of where you are in directory tree [but so will sh /sbin/fix_permissions so either way is up to you]
or if you are reffereing to adb on the computer
in Windows with command prompt open
set path=%path%;C:\android-sdk\platform-tools [or adjust for where you saved adb]
so if setting a batch program you could use the following to copy/paste [just adjust directories if you saved files differently]
The following is off the cuff until I begin writing the full script and automate things but it is a very basic start
Code:
@Echo Off
Set Path=%PATH%;C:\android-sdk\platform-tools
adb devices
Echo If you see ????? then restart recovery and reconnect the phone
Echo and run adb kill-server and re-run this batch script
pause
Echo when you hit any key this will start adb and put you in the shell you
Echo Will have to run fix_permissions -l -r manually
Echo Be sure to mount /storage /data via phone first
adb shell
or in Linux [OSX should be similiar if not the same]:
from terminal
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved adb
export PATH
No it just bothers me when people ignore the rules and the Developers! Raver even told you were it belonged, and you chose to ignore Raver and the rules!
The fix will be to modify recovery for use with ICS on our devices or a modified fix-permishions script baked into the ROMS
RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
I did bro just having trouble getting the cmd to recognize adb I have it downloaded I changed it still nothing don't know what the hell is wrong with it but IM fixing to improve on my golf swing on this damn vista desk top !
Sent from my SAMSUNG-SGH-T989 using xda premium
Want closed till me and 8trix figure what the hboot update IMG is called
PLEASE HIT THANKS.... READ ALL BEFORE PROCEEDING
FIXED COMMANDS HAD A COMMON MISTAKES
Hi, I am a developer from the " HTC Droid Incredible 4G LTE " My Rom http://forum.xda-developers.com/showthread.php?t=2065615 and I am still a newbie at this developing thing.. So with this being said I am not resposable for anything that could or may happen.*
Now I'm this TUTORIAL I will be providing the links and the instructions on how to proceed on the rooting process
*Requirments*:
-Android SDK - http://developer.android.com/sdk/index.html
-HTC drivers -*http://www.htc.com/us/support/
-The Su .zip - attachment
-And.... The HTC One Xv of course.
STEPS:
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4. To makes matter safer your gonna need to Temp Root, download this : http://uploaded.net/file/h44f6vni
5.Once downloaded, unzip it to C:\Root. Navigate to the folder in the command Prompt by typing *please follow directions CLEARLY
- *cd c:\Root\stuff
- *adb devices
- *adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet! Now type:
- *adb shell "while ! ln -s
/data/local.prop /data/data/com.android.settings/a/file99; do
:; done"
(errors will appear, ignore) Accept the restore on the device, then type:
-adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.) After reboot type:
- adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over. At this point, you can optionally do this ONLY if you want to revert changes:
- rm /data/local.prop
- exit
- adb reboot
Close cmd and start a new one then type
- adb devices
- adb install /system/apps/superuser.apk
- adb push su /system/bin or try adb push su /system/bin/su
6. - adb reboot
7. reboot twice, and if this don't work then please leave a comment and I will explain a new way.
ATTENTION
2nd way to try to root
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4.read carefully
5. create a folder were the superuser.apk and Su file is and name it system and inside that make a bin folder and place the Su file in the bin folder
6.Go to the folder were you extracted root folder in the last root alternative
7.Open cmd in that folder and make sure to extract the files ( superuser.apk and Su file to the root of the root folder )
8.Type : adb devices
9. Type: adb shell
10. Type: adb install ( locate were apk is on your pc.... Here is an Example of what ide put: adb install c:/root/nameOf app.apk , then press enter )
11. Type: adb push su /system/xbin or try adb push su /system/xbin/su or try adb push system/xbin/su /system/xbin/su
12. Use the following command to add the correct permissions to the su binary on the device adb shell chmod 6755 /system/bin/su
13. Adb reboot
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
I'll try when I get ack home tonight,
thanks for this
avid.aria said:
I'll try when I get ack home tonight,
thanks for this
Click to expand...
Click to collapse
Download a ruu to be on the safe side too... There's 2 ways on how you could root
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
Reserved
Another reserved
Hope this helps everyone
Not working
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.
8trix said:
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.
Click to expand...
Click to collapse
Me and you will work on finding a way
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.
hasoon2000 said:
Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.
Click to expand...
Click to collapse
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
To unlock the bootloader is easy, its like any other htc. Go to htc dev site and choose "all other supported devices" and follow the guide. It'll give you the file to fastboot flash to unlock. We're just working on getting root now. HTC definitely did something different with this phone because none of the other methods seem to work. Seems like there are some smart dedicated people working with us so please be patient and keep a watch on this thread!
lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
24ky said:
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
Click to expand...
Click to collapse
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?
flipinfin said:
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?
Click to expand...
Click to collapse
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app
jose51197 said:
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip
8trix said:
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip
Click to expand...
Click to collapse
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium
jmztaylor said:
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium
Click to expand...
Click to collapse
I know this is old and not needed anymore since you're putting up root tomorrow, but I wanted to close this with yes, I did re-lock, and it kind of almost worked, like it finished sending the file, but then errored out with some other bs. No woory now though, I am back to fully stock unlocked and will test your root tomorrow if it's up then. Thanks again jmz, great work!
So... how do I get the UI working again? I'm stuck with an unusable UI ._. !
zeratos said:
So... how do I get the UI working again? I'm stuck with an unusable UI ._. !
Click to expand...
Click to collapse
Whats wrong?
None of the methods described on the main post work and I got stuck on the unusable UI, I google how to do a factory reset and now it's working again.
Thanks.
Also, is there a way to root this thing?