Database Info

[HOW TO] HTC Desire Custom Splash screen

Hi All,
After applying the S-OFF method (http://forum.xda-developers.com/showthread.php?t=794314) I noticed that the Splash screen changed from the white screen with HTC on it to an image with The Joker (from Batman) on it. Although I do like Batman movies, I wanted to change the splash screen.
For those who don't know, the splash screen has nothing to do with the bootanimation, which comes after the splash screen.
I searched the forum and found a thread to change the boot screen on the Droid Incredible. I followed part of the steps and tried it on my HTC Desire. The results are fine. I decided to make a little guide to change your splash screen.
In order to make a custom splash screen, you need the following:
1. Image editing program such ash Photoshop, Gimp etc
2. NBIMG command-line splash<-->image converter tool [Windows Download] or [Linux Download] (Original Dev Thread)
3. Android SDK http://developer.android.com/sdk/index.html
How to:
Download and extract the files linked above and place them somewhere familiar to you.
In your image creation/manipulation program, create a new image. Set the image size to 480x800. (If you already have an image in mind, open that and resize it)
Create/modify/customize the image however you like.
Save the image as splash1.bmp file. Ensure that you are saving the file as a 24bit RGB color bitmap. To make things easy, save the image in the same folder where you extracted the nbimg tool.
Open a command or terminal window and CD to your nbimg folder.
Type in the following command: nbimg -F splash1.bmp -w 480 -h 800
If successful, nbimg should have created an nb file called 'splash1.bmp.nb'.
Rename 'splash1.bmp.nb' to 'splash1.img'.
Boot your Desire into Bootloader and connect it to your computer
Open een command or terminal window and browse to the Tools folder which should reside in your Android SDK folder when you unzipped it.
Type in the following command: fastboot flash splash1 splash1.img
The output should be something like this:
Code:
D:\Android\AndroidSDK\android-sdk-windows\tools>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)... OKAY [ 0.125s]
writing 'splash1'... OKAY [ 0.218s]
finished. total time: 0.343s
13. Reboot your Desire and enjoy your new splash screen.
Thanks to:
* ieftm for S-OFF
* All the others who made S-OFF possible
* deficitism for the custom splash screen guide
REMEMBER: When you do follow this guide, you do it at your own risk. I do not, I repeat, DO NOT, take any responsibility when things go wrong. Feel free to submit any improvements whatsoever.
finally, the short version for (ubuntu) linux users:
read through the thread for minimum-requirements, such as s-off etc. i don't know if the phone needs to be rooted and am to lazy to find it out (since mine already was anyway).
download and install nbimg from http://pof.eslack.org/2008/07/03/nbimg-htc-splash-screen-tool/
create your .img-file as described in the first posting in steps
download fastboot.zip from the attachment of the following posting: http://www.pocketpc.ch/htc-desire-hd-root-rom/116448-anleitung-desire-hd-s-off-bootloader-flashen.html#post871105
you also might want to decide in which folder you want to keep it on your computer as a "program". if you are unsure, your /home/%USER/ folder will do just fine. – ... btw. unless you are familiar with creating symbolic links on command line i advise you to abandon any second thoughts about this issue after this step.
now open a terminal and type the following to "install" fastboot and make it easier to use later on command line (in fact just unzipping the fastboot archive and creating a symbolic link in /usr/bin/:
Code:
sudo apt-get install unzip
cd /path/to/where/you/are/storing/the/fastboot-zip-file/
unzip fastboot.zip -d fastboot
sudo ln -s fastboot/fastboot-linux /usr/bin/fastboot
do NOT move the folder "fastboot" or the file "fastboot-linux" afterwards, or you will break the symbolic link in /usr/bin/
keep the terminal open.
now change to the directory where you saved your splash-image files (those with the .img extension you created earlier with the nbimg-tool):
Code:
cd /path/where/your/splash/files/are/stored/
still keep the terminal open.
now boot your phone into bootloader mode (htc desire: press "power" and "volume down")
connect your phone to the computer and enable "FASTBOOT" mode in the bootloader (in my case, with clockworkmod, the line "FASTBOOT USB" in red uppercase letters appears on the screen, among other information shown)
now change back to your terminal/command line tool and flash the splash image on the phone:
Code:
sudo fastboot flash splash1 name-of-your-splash-image-file.img
voilà!
in my case, i got a "waiting for device"-message, and sometimes those error some got (something with splash -1 ...). firstly i thought that was due to me using a 64-bit computer, a faulty fastboot executable and so on. finally i found out, that i simply needed super user rights to successfully flash the image
Click to expand...
Click to collapse

I hope the phone number on the splash screen doesn't belong to the SIM-Card in your Desire
Good work btw!

geminga said:
I hope the phone number on the splash screen doesn't belong to the SIM-Card in your Desire
Good work btw!
Click to expand...
Click to collapse
lol +1..make sense.
Nice guide. Thanks.

Great guide! I like the idea of your contact details on the boot screen

Dude.. if you would like to make things a tad bit easier for people. Link them to my 1-click splash converter and flasher. Nice guide. Bit hard on the noobs lol. Anyway.. I'll leave a link.
http://forum.xda-developers.com/showthread.php?t=794638
Dan

danward said:
Dude.. if you would like to make things a tad bit easier for people. Link them to my 1-click splash converter and flasher. Nice guide. Bit hard on the noobs lol. Anyway.. I'll leave a link.
http://forum.xda-developers.com/showthread.php?t=794638
Dan
Click to expand...
Click to collapse
This didn't work for me, the program kept throwing a .NET error which is weird as Windows7 comes with .NET 3.5 with all service packs etc.
Even installed .NET 4.0

Mekrel said:
This didn't work for me, the program kept throwing a .NET error which is weird as Windows7 comes with .NET 3.5 with all service packs etc.
Even installed .NET 4.0
Click to expand...
Click to collapse
Strange.. can you post the error? or was it to do with nbimg?

danward said:
Dude.. if you would like to make things a tad bit easier for people. Link them to my 1-click splash converter and flasher. Nice guide. Bit hard on the noobs lol. Anyway.. I'll leave a link.
http://forum.xda-developers.com/showthread.php?t=794638
Dan
Click to expand...
Click to collapse
Great work man... Didn't see your thread. Actually this thread can be closed then.
And no the phone number on the screen doesn't belong to the sim inside the phone

Manual way is always better. At least you learn how to use the commands. I was going to post this
Oh and if your image is already the right size you only need "nbimg -F splash1.bmp".
Oh and no need to type >fastboot. Just fastboot works.

danward said:
Strange.. can you post the error? or was it to do with nbimg?
Click to expand...
Click to collapse
Sure thing mate, happens when I select the splash1.bmp
Uploaded with ImageShack.us
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.IOException: The process cannot access the file '.\splash1.bmp' because it is being used by another process.
at Microsoft.VisualBasic.FileSystem.FileCopy(String Source, String Destination)
at SPLASH_Flasher.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
SPLASH Flasher
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Mekerz/Downloads/SPLASH%20Flasher_1.2.2/SPLASH%20Flasher/SPLASH%20Flasher.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Click to expand...
Click to collapse

THX ... worked like a charm !
The 1Click Solution didnt work for me.... no error was displayed, but the splash didnt change....
Greetings

I am getting this error
C:\1\tools>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s
Followed all instructions but still getting that error.
Help

C:\1\tools>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s

chucic said:
C:\1\tools>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s
Click to expand...
Click to collapse
Try reconvert. Have you used my tool?

yes, I used both your tool and tools inside SDK too.
But, if use i-click tool, will shows that image already used by other program and stop....
if use command by fastboot.....will shows Failed like that.

You've both flashed S-OFF first, correct?

chucic said:
yes, I used both your tool and tools inside SDK too.
But, if use i-click tool, will shows that image already used by other program and stop....
if use command by fastboot.....will shows Failed like that.
Click to expand...
Click to collapse
Yeah, I've got a easy bugfix coming out in the next 3 hours. Until then all you have to do is copy the "splash1.bmp" out of the "SPLASH Flasher" folder into another one and then open it from there. I tested it, I was able to reproduce the error. That is the fix.
Dan

ephumuris said:
Manual way is always better. At least you learn how to use the commands. I was going to post this
Oh and if your image is already the right size you only need "nbimg -F splash1.bmp".
Oh and no need to type >fastboot. Just fastboot works.
Click to expand...
Click to collapse
Manual is generally better for everything! lol

danward said:
Dude.. if you would like to make things a tad bit easier for people. Link them to my 1-click splash converter and flasher. Nice guide. Bit hard on the noobs lol. Anyway.. I'll leave a link.
h t t p://forum.xda-developers.com/showthread.php?t=794638
Dan
Click to expand...
Click to collapse
It is good to have the manual method written up for people that cannot use your tool i.e. everyone that refuses to run windows

chucic said:
yes, I used both your tool and tools inside SDK too.
But, if use i-click tool, will shows that image already used by other program and stop....
if use command by fastboot.....will shows Failed like that.
Click to expand...
Click to collapse
I also had this issue when trying to use ADB to flash new boot screen. Then realised that I actually had to enter fastboot on the phone as well... rookie error I guess - never done this before - but worked perfectly once I had entered fastboot - not just pressed Power+Vol down...

[APP]SuperOneClick v2.3.3 - Motorola Exploit Added!

SuperOneClick
FOR ANDROID GINGERBREAD AND EARLIER DEVICES
​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads available at http://shortfuse.org/
v2.3.3
------
Motorola ADB Patching
Checks for shell root before applying exploits
Unroot has been fixed to work more reliably
LG devices no longer need to use alternate ADB
v2.3.2
------
Better LG phone support
v2.3.1
------
Auto driver installation
v2.2 is up!
zergRush and Superuser 3.0.6 included
----------------------------------------------
v2.1.1 is up!
Driver pack comes later!
---
I made it. I tested it. It works. You can get it from shortfuse.org or use the links below (if you're a registered XDA member).
Here's a one-click root with almost all phones and all android versions. (including the i9000, Droid, Nexus One, etc)
YOU CAN ROOT ALMOST ALL ANDROID PHONES!
The program requires Microsoft .NET Framework 2.0+ or Mono v1.2.6+
Operations systems with native support:
Windows Vista
Windows 7
Ubuntu Hardy (8.04 LTS)
Ubuntu Jaunty (9.04)
Ubuntu Karmic (9.10)
Ubuntu Lucid (10.04 LTS)
Ubuntu Maverick (10.10)
Debian Lenny (5.0)
Debian Squeeze (testing)
Debian Sid (unstable)
Debian Experimental
If you run Microsoft Windows XP, install .NET Framework v2.0 or above
If you run Mac or another Linux flavor, make sure you install Mono:
http://www.go-mono.com/mono-downloads/download.html
For more information about making it work in linux:
See here
You NEED to put your phone on USB Debugging mode
You NEED to install make sure the Android drivers for your phone are installed
Make sure you DO NOT mount your SD card.
If you still can't get something to run, try doing it in recovery mode.
Read me: (READ BEFORE POSTING)
2/24/2011:
I registered my website shortfuse.org so you can grab SuperOneClick from there now.
2/22/2011:
Great news. -1Day roots AT&T Motorola Atrix4G!!! YAY!
11/29/2010:
I'm sorry I haven't been updating lately!!! The problem is, I no longer have an Android phone and I can't play around or test anymore. I'm going to see if I can find one on craiglist or ebay.
11/10/2010:
I finally figured out how to root without looping. After rooting 13 phones, this is how I did it on the first try.
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
All BEFORE it says "Waiting for device..." again
11/1/2010:
Hey guys! I'm sorry I haven't been able to respond to lots of posts. I've been really busy lately with work. I've been reading some posts and I've made some changes in v1.5.2
Let me know what bugs and issues you guys have.
10/17/2010:
Thanks to all that donated! I was worried for a bit but you guys proved me wrong. So, I fixed the NMA (non market apps) button. It should now install sqlite3 and busybox into a temporary folder if you don't have it. I added an unroot (by popular demand). I did some major code clean up, so you can expect faster releases from here on out. Next version will add sqlite3 and busybox to the /system partition included in root.
If you're having issues with "wait for device" or if RATC is looping, try this
Unplug your USB Cable
Go to Settings > Applications > Development
Uncheck USB Debugging
Plug in your USB Cable
Unplug your USB Cable
Check USB Debugging
Plug in your USB Cable
10/13/2010:
I need people with issues to post their device model and if they tried rooting in recovery mode. All posts ignoring the read me will be ignored. (meaning nma complaints and those NAND locked devices).
I'm getting flooded with replies, PMs and emails. Seriously, try reading a few posts back.
The program has been downloaded over 5000 times and only 2 people have have donated. I see donations as signs of gratitude. Even if it's 25 cents, please donate.
When I find the time (and will) I will work on the v1.5 release.
The rageagainstthecage looping is by design. Bad usb cables and ports can cause ratc to not run properly so I have it loop until it works. The "waiting for device" hang is for the same reason. There's nothing wrong with my application. It's usually your usb cable or port. This is not a cop-out answer. This is not an excuse as if I didn't know why it happens. This has been investigated and the problem is USB connectivity. It happens with my Captivate as well.
10/11/2010:
Enabling market apps isn't working unless you have busybox installed. I plan to fix this in the next version. The problem is, different devices have different locations for the com.provider.android.settings/settings.db and I was using the 'find' command to find your settings.db location. I didn't realize this was a busybox command not internal. That will be fixed.
I also added some information about root that I think people should read and classified different root levels.
By classifying root levels, I make it easier for the users to know if certain options will work or not. For example, enabling non-market apps will only require a Level 1 root, meaning it will work with the HTC Aria
Donate
Donate if you wish...
Compatibility list
Please note that if you device is not listed here, it doesn't automatically make it incompatible. The list is definitely incomplete.
Use the search feature to search for your phone model: http://forum.xda-developers.com/search.php?searchthreadid=803682
Acer Liquid Metal
Dell Streak
HTC Magic (Sapphire) 32B
HTC Bee
LG Ally
Motorola Atrix4G
Motorola Charm
Motorola Cliq
Motorola Droid
Motorola Flipside
Motorola Flipout
Motorola Milestone
Nexus One
Samsung Captivate
Samsung Galaxy 551 (GT-I5510)
Samsung Galaxy Portal/Spica I5700
Samsung Galaxy S 4G
Samsung Galaxy S I9000
Samsung Galaxy S SCH-I500
Samsung Galaxy Tab
Samsung Transform M920
Samsung Vibrant
Sony Ericsson Xperia E51i X8
Sony Ericsson Xperia X10
Sprint Hero
Telus Fascinate
Toshiba Folio 100
Incompatibility list
With the absolutely beautiful ADB exploit I use, titled rageagainstthecage (ratc), absolute ALL devices can be rooted. This is because it exploit is ADB which all devices use. There is an issue though. Some devices have a NAND lock which does not allow you to write to the /system mount. Because of this, you can't copy su, sqlite or busybox to /system/bin. This creates some issues but there is a work around. For things that don't need access to /system (like enabling non-market apps) I can use the ratc exploit to make those changes. If your device cannot use su in /system/bin then you can simple select a checkbox (as of v1.5) that says to use ratc.
There are 3 levels of "root" we can define:
Level 1: Shell Root (with ratc rooting the adb shell but no /system write access)
Level 2: Temporary Root (/system/bin/su installed but lost on reboot)
Level 3: Full Root (/system/bin/su installed and sticks)
Some devices have a NAND lock. SuperOneClick will only give a Shell root until you remove this lock.
The following phones can use http://unrevoked.com to remove this lock:
Sprint EVO 4G (HTC Supersonic)
Droid Incredible (HTC Incredible)
HTC Desire GSM
HTC Desire CDMA (HTC BravoC)
HTC Aria
Droid Eris (HTC DesireC)
HTC Wildfire (HTC Buzz)
THe HTC Legend and My Touch 3G 32A also have a NAND lock and need more specific methods to unlock.
The T-Mobile (HTC) G2 has something different which may or may not be a hardware flaw. I have yet to really research the device, but while it may root, it won't be permanent since copying /su to /system/bin/su has problems. I believe this is a Level 2 root, but to be honest, I need to research more.
All other devices has a Level 3 root via SuperOneClick
Version changes:
v1.9.5
Driver Installation Fix
Force Administrator on Vista/Win7
Fixed Non-Market Apps not working for some devices
v1.9.1
GingerBreak support! (I think)
v1.9
Bug fixes!
Should work better now on XP systems and Linux
v1.8
Automatic driver installation
Removed RageAgainstTheCage (no virus flags)
New folder structure
Major code clean up
v1.7
Hopefully fixed Linux hangs
Theoretical honeycomb support (still needs testing)
v1.6.5
Fixed major bug. Oops!
v1.6.4
Installs busybox to /system/xbin and installs syslinks
Added a 30 second timeout check (should eliminate all lock ups)
v1.6.3
Mounts with busybox first
Includes version in first line
v1.6.2
Fixed wrong su version being sent
Fixed issue when getting OS version
Prints device info on failure.
v1.6.1
Falls back to previous mount path method if busybox method fails
v1.6
Uses psneuter for exploit instead of rageagainstthecage by default (should root Sony Ericsson devices easily now)
Added detection for 1.x Donut/Eclair kernels
Uses busybox for getting mount path
Updated Windows ADB to latest version (I'll update the Mac/Linux ones next build)
v1.5.5
Unroot uninstalls Superuser from /data/app
Returned installation of Superuser to /system/app
v1.5.4
Fixed superuser install issue
Added a prompt to tell you to allow superuser on your phone, for the test.
Fixed unroot.
v1.5.3
Fixed ADB-pushing problem
v1.5.2
Administrative rights in Windows Vista/7 are automatically requested.
Fixed the settings.db search. (Tries default two locations, then uses busybox is all else fails).
Set Superuser to install (to data/apps) instead of copy to /system/apps. You can manually remove it from your phone like any other app. (You can also update it with the Market).
Fixed NMA not working if you didn't have Shell Root
v1.5.1
Untested Mac and Linux support (you need Mono)
v1.5
Fixed Non Market Apps
Added Unroot
Added separate Shell Root (rageagainstthecage) button
Lots of internal code clean up.
v1.4
Changed main form's name to SuperOneClick from RageAgainstTheCageGUI
Enabled Captivate - Get Unlock Code button
Added a messagebox to confirm if Non Market Applications are enabled
Made "Enable Non Market Apps" FULLY universal
Added initial message telling you to remember to allow superuser commands (when enabling Non-Market Apps)
v1.3
Removed busybox for space reasons. Changed the layout. Fixed issue where application stayed running in the background. Added Non Market App button.
v1.2
Added a detection to see if RATC was already working.
v1.1
Universal device support. Application now finds your /system path.
v1.0
Initial release.
Development Plan:
Scheduled for next major release
Linux support via mono-project
Add a check box to use su or rageagainstthecage for other scripts (like Enable NMA)
Better error handling for devices with NAND lock on /system
Have options show what level root is needed (0,1,2,3)
To do list:
Jupiter fixes
Custom scripts support
Plugin support
Mac support via mono-project
Linux support via mono-project
Wishlist:
None
Thanks to basily, I have an Captivate v2.1 nv_data.bin I can test with to create the unlock button.
I need a mac/linux user to help me. PM so we can chat on AIM/Google
Courtesy of TheUnlockr.com, here's a step-by-step video:
Mod Edit: this app will set off some anti virus software...here's a small explanation by pulser_g2:
rageagainstthecage is a root exploit via a fork bomb.
It IS a potentially malicious payload, BUT it is being used with owner's consent to root the phone.
The DreamDroid malware use exactly same payload - they are trojans, but this is a helpful tool.
It IS a dangerous tool in the wrong hands, but this is a root exploit, so you should exercise common sense and a little understanding of what it does and how it works.
Click to expand...
Click to collapse

First reply!
Thanks!!! Even I won't be needing them at the moment
Now the next project... ability to sign the update.zip so recovery mode works!

Cool!! Thank you! =)

Good job i cant wait to try this out

ROCK ON
thanks

What does this mean(in bold).
CLShortFuse said:
I made it. I tested it. It works.
Here's a one-click root that works with Froyo on our Captivates. It's not just the Captivate. It works with almost all phones and all android versions. (including the i9000, Droid, Nexus One)
I've included busybox and sqlite3 because i wanted to. I'll make a full-fledged UI later (where you can select what apk to install, with or without busybox, etc);
If you don't have your Google SDK path set, include adb.exe in your folder (or just copy it to the sdk\tools folder).
It's Windows only at the moment (and you need .NET Framework 2.0+) but I'll port it to mac/linux later on (if you guys are that interested).
.
Click to expand...
Click to collapse

ziphoward said:
What does this mean(in bold).
Click to expand...
Click to collapse
yep im wondering the same as i dont have any adb or or sdk installed on computer, as i dont know how to use either one. can i still use this?

Couldn't have been easier. However when I launched TiB after seeing the successful ROOT message box from the unroot app, I am not rooted.
Update to my post: ran again and Busy Box states that I am rooted.
Thanks...

When i run this .. The GUI just hangs with a blank screen .. no errors.. if i go to task manager there are two adb.exe processes and if i force close one the GUI closes.
Any ideas?

joelmassee said:
Couldn't have been easier. However when I launched TiB after seeing the successful ROOT message box from the unroot app, I am not rooted.
Update to my post: ran again and Busy Box states that I am rooted.
Thanks...
Click to expand...
Click to collapse
You should reboot the phone, but I didn't want to make it mandatory. I'll add a prompt asking if you want to reboot.
aramsumair said:
When i run this .. The GUI just hangs with a blank screen .. no errors.. if i go to task manager there are two adb.exe processes and if i force close one the GUI closes.
Any ideas?
Click to expand...
Click to collapse
Plug in a device

kamots said:
yep im wondering the same as i dont have any adb or or sdk installed on computer, as i dont know how to use either one. can i still use this?
Click to expand...
Click to collapse
Me too have no clue about that!! Can anyone just type a "Step by step" to use this please?
Thanks

For those of you who don't understand what ADB is:
http://tinyurl.com/35ba2wz
It's a little scary for people to be rooting their devices without even knowing the basics...

Cl,
When I unzipped I clicked the gui and ok. It gives me an uncaught exception error. I figured I would just have to have USB debugging enabled, is there something else I am missing.
I figured I would give this a shot so I don't have to go though ADB to do my root all over again. I will post the details of my error.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at RageAgainstTheCageGUI.Form1.runCommand(String arguments)
at RageAgainstTheCageGUI.Form1.button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3615 (GDR.050727-3600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
RageAgainstTheCageGUI
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Brian/Desktop/Android%20Central/Rooting/Captivate%20one%20click%20root/Froyo/RageAgainstTheCageGUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3614 (GDR.050727-3600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Click to expand...
Click to collapse

flashman2002 said:
Cl,
When I unzipped I clicked the gui and ok. It gives me an uncaught exception error. I figured I would just have to have USB debugging enabled, is there something else I am missing.
I figured I would give this a shot so I don't have to go though ADB to do my root all over again. I will post the details of my error.
Click to expand...
Click to collapse
System.ComponentModel.Win32Exception: The system cannot find the file specified
Your ADB path isn't set
Try looking at http://androidcommunity.com/forums/f28/what-is-adb-made-easy-17732/

Worked great the first time I ran it on XP! Thanks so much.

CLShortFuse said:
System.ComponentModel.Win32Exception: The system cannot find the file specified
Your ADB path isn't set
Try looking at http://androidcommunity.com/forums/f28/what-is-adb-made-easy-17732/
Click to expand...
Click to collapse
Ok I'll give it a shot. I am assuming when you said this has to go in my sdk-tools you were talking about the gui from your OP. If that is the case I did not pay attention very well. Thanks.

Worked like a charm! (win7x64)
EDIT: Its rooted alright, MarketAccess was installed ok, however I tried to install another app and got the "for security your phone is set to block installation of applications not obtained from Android Market"
....... Ideas?

Seemed to work fine for me. I have the android sdk's tools dir added to my PATH. On Win7 x86 and using 2.2. Didn't try busybox or anything yet. Thanks CLShortFuse!

OK ... got it done ...
But now what? I got the Superuser Icon but I still can't replace system files.
Is there anything else to do?
How can I get rid of the AT&T apps?
How do I access the "open" market?

It worked but I can not send emails with attachement from my exchange.
It crashes and force close.
The gmail has no issues.

EmuTempRoot - Root tool for Android Virtual Device

This is my tool to apply a temporary root to the (already open) android's emulator. If you're a developer or simply want to run apps with root access in the emulator you may find this useful.
Please note, launching the AVD directly from EmuTempRoot is highly recommended (especially if root fails).
The emulator can also be launched from this tool;
this option is recommended since the AVD will be automatically configured in order to ensure a succesful root process.
You can still deploy apps to the emulator from eclipse.
Requirements:
- Windows Vista (it should work on XP and 7, not tested)
edit: i still can run it successfully on windows 8
- .NET Compact Framework 3.5 or higher
- Android SDK for 2.1 or higher
Usage:
- Unzip to desktop or any folder where special rights are not required
(e.g. do not unzip to the program files folder)
- Open EmuTempRoot (double-click)
- Open the AVD (better to open AVD from EmuTempRoot)
- Root! it lasts untill the AVD is rebooted
Download from the link below. Optionally

- Windows 7 Ultimate
-. NET Framework 4
- Android SDK for 2.2
Will not start. Falls with an error.

It is an useful tool
I run it successfully. It is very usefully for everyone want to develop on emulator. Thanks!
Anglejoy!

Thanks very much for this, it works perfectly.
I am new to the world of Android, loving it though!

got a error message when try to apply root how to fix it?
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at EmuTempRoot.EmuTempRoot.run_command(String path, String args, Boolean wait)
at EmuTempRoot.EmuTempRoot.emuRootButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
EmuTempRoot
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Jeff/Desktop/EmuTempRoot/EmuTempRoot.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5458 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Click to expand...
Click to collapse

Doesn't work!
When I click 'Apply Root' it says 'please wait...' and after a few seconds, it says 'failed: cannot connect to emulator.':crying:
But my Emulator is still open!

Paresh Kalinani said:
When I click 'Apply Root' it says 'please wait...' and after a few seconds, it says 'failed: cannot connect to emulator.':crying:
But my Emulator is still open!
Click to expand...
Click to collapse
Excuse me for taking so long to answer you should try to launch the AVD directly from EmuTempRoot, once the AVD is up and running apply the root.

xdaid said:
Excuse me for taking so long to answer you should try to launch the AVD directly from EmuTempRoot, once the AVD is up and running apply the root.
Click to expand...
Click to collapse
Hehe... I wanted to root the emulator 'cause I was afraid of rooting my phone... but now I've rooted.. no need now.. thanks for not answering for so long! Otherwise, I'd never root my phone!!
Sent from my One V

liujeffqi said:
got a error message when try to apply root how to fix it?
Click to expand...
Click to collapse
Same, how come?

Helpp!!
I have made a adt folder in d drive and in that i have extracted the three files (sdk,eclipse and SDK Manager.exe)..
so my directory is D:\adt\
I have made an emulator of name "mob"
So i wanted to know in which text box what to fill(what directory)??
I filled by my own this way(Pic)..
But i got error..
Am i filling wrong details??

[Q] How can I root my Infuse without a computer or through linux mint 11

My computer has very low ram, as a result anything related to flash or anything having high memory requirement crashes and usually freezes ie resulting in a restart
So I would like to keep the computer out of the equation
I am wondering if one can root a phone without a computer
This may seem like an odd request/question but I am in a terrible place, my stuff was stolen, I am even more broke than before.
Thanks for any help

You can try z4root.apk but it may or may not work....really need a computer with superoneclick
Sent from my SAMSUNG-SGH-I997 using xda premium

use virtualbox to run Windows and use superoneclick using the virtual Windows.
here's the website with info for getting it going and downloads
https://www.virtualbox.org/
good luck

hollywood528 said:
use virtualbox to run Windows and use superoneclick using the virtual Windows.
here's the website with info for getting it going and downloads
https://www.virtualbox.org/
good luck
Click to expand...
Click to collapse
his computer has low ram. running a vm will make that situation much much worse!
look in the dev section for a root/unlock tool from lost1 it includes adb, ragagainst the cage binary and a batch script for windows and shell scripts for linux and mac. just extract the package to a convienient place like c:\ in windows or your home or root directory in linux then using comand line cd into the extracted folder and run the approraite script.

I can do this within linux ?

GreenAce92 said:
I can do this within linux ?
Click to expand...
Click to collapse
yes, there are different scripts for different os's the root.sh is the one for Linux. under the assumption you are a Linux newb to execute a ascription you may need to change permissions to executable first. you can usually set this in gnome or whatever window manager you like. or with chmod
chmod 0755 root.sh
then to execute the script you just type
./root.sh
this is all assuming you are within the folder that contains the script.
it appears all it does it move a binary to /data/local wait a few seconds and then copy su to /system/bin. you could easily do that through adb if you are familiar with it.

So uhh
Could you dumb this down even further, I am a complete linux newb as you say and I have just installed Linux Mint 11 32bit on an old HD of mine so Linux is here to stay, I'm interested in learning it too
But anyways... what can you suggest so that I can catch up / understand what you have just told me to do?
Thanks for this

GreenAce92 said:
So uhh
Could you dumb this down even further, I am a complete linux newb as you say and I have just installed Linux Mint 11 32bit on an old HD of mine so Linux is here to stay, I'm interested in learning it too
But anyways... what can you suggest so that I can catch up / understand what you have just told me to do?
Thanks for this
Click to expand...
Click to collapse
first download the root/unlock package from this thread
forum.xda-developers.com/showthread.php?t=1081072
unzip the package and find the root.sh file.
ok, Linux sets file permissions that tell the system who can access the file and how. on Ubuntu new files are set as non executable by default. mint being based on Ubuntu is the same. the permissions are set with a 4 digit number, the first number is special permissions and you wont use that very often. the second digit is for the user that owns the file, the 3rd is for the group and the 4th is for the others.
if you use command line the chmod command will set these permissions. 7 designates read write and executable, 6 is read write, 5 is read and executable, 4 is read only.
but you can also set a file as executable in gnome. right click the icon and choose properties. there should be a box that says "is executable" or "alow execution of file as program" or something. check that box for the "script.sh" file.
once you do that right click in the widow of the folder that the root.sh script is in and choose "open in terminal" or "open window terminal here" this will open a command line window open to that directory.
make sure debugging is enabled in settings>applications on the phone and connect with the data cable. don't mount the SD card.
now type ./root.sh
that should start the script and root the phone. reboot when it's done.

Excellent
Many thanks to you good sir, I shall report back when I have tried this

Try looking here, works on Windows, Mac, and Linux: http://forum.xda-developers.com/showthread.php?t=1081072

GreenAce92 said:
Excellent
Many thanks to you good sir, I shall report back when I have tried this
Click to expand...
Click to collapse
oh forgot, you might need to set adb as executable as well. same thing. right click and go to properties>permissions>allow execution... or whatever it says in gnome. (I use kde and occasionally xfce for low performance hardware, but mostly kde)

Use heimdall to flash a custom kernel

Iball Slide Tablet Rooted..(Perm Root)

I am not Responsible for any kind of damage..This post is for educational purpose only...
This forum contains Farhan's method of rooting..I have not personally achieved root access employing that..So I am writing down an easy method which grants root permission to your Iball tablet..
Download(See the attachments..)
1. Root explorer(preferably v2.17.1)
2. Gingerbreak v1.20
3. Root Check.
See the attachments..
These are enough for rooting.. Install RootExplorer and open it. Navigate via RootExplorer to /default.prop..
1. Press it for 2 seconds, then "open it" via text editor.
2. Edit the file default.prop to change the value ro.secure=0 (instead of the given value stock ro.secure=1)
3. Now press the back button, which gives a 'save" dialogue..Save it, and you see the original file is saved with the name "default.prop.bak".
4. Open your cmd.exe in windows and type adb shell..You should see a # instead of $..Now install and open the Root Checker, click "Verify Root Access", and then with a lot of frustration you will see "Sorry, you don't have root access"..
Don't be frustrated, I am here to help you out!!
5. Now install Gingerbreak, and open it, click "Root device"..It will take some time to run the exploit..then the device will automatically shut down..
6. Power on your device manually, it will take a little bit time more than usual. leave it for 1 minute after you see your unlock screen, then unlock it.
7.Go straight to menu>root Check..It will ask for SuperUser permission, Click ok>Veryfify Root Access..And then you will obviously see "Congratulations! You have root access!"
If you own success, please thank me, I have not copied someone's procedure, this procedure is completely discovered by me after going through lots of tutorials regarding android development, and now I am also capable of building some basic apps for android..

gourab4u said:
I am not Responsible for any kind of damage..This post is for educational purpose only...
This forum contains Farhan's method of rooting..I have not personally achieved root access employing that..So I am writing down an easy method which grants root permission to your Iball tablet..
Download(See the attachments..)
1. Root explorer(preferably v2.17.1)
2. Gingerbreak v1.20
3. Root Check.
See the attachments..
These are enough for rooting.. Install RootExplorer and open it. Navigate via RootExplorer to /default.prop..
1. Press it for 2 seconds, then "open it" via text editor.
2. Edit the file default.prop to change the value ro.secure=0 (instead of the given value stock ro.secure=1)
3. Now press the back button, which gives a 'save" dialogue..Save it, and you see the original file is saved with the name "default.prop.bak".
4. Open your cmd.exe in windows and type adb shell..You should see a # instead of $..Now install and open the Root Checker, click "Verify Root Access", and then with a lot of frustration you will see "Sorry, you don't have root access"..
Don't be frustrated, I am here to help you out!!
5. Now install Gingerbreak, and open it, click "Root device"..It will take some time to run the exploit..then the device will automatically shut down..
6. Power on your device manually, it will take a little bit time more than usual. leave it for 1 minute after you see your unlock screen, then unlock it.
7.Go straight to menu>root Check..It will ask for SuperUser permission, Click ok>Veryfify Root Access..And then you will obviously see "Congratulations! You have root access!"
If you own success, please thank me, I have not copied someone's procedure, this procedure is completely discovered by me after going through lots of tutorials regarding android development, and now I am also capable of building some basic apps for android..
Click to expand...
Click to collapse
is this all that has to done to root the iball slide i7218 ?? if not can u please explain what other prerequisites are necessary.

gourab4u said:
4. Open your cmd.exe in windows and type adb shell..You should see a # instead of $..Now install and open the Root Checker, click "Verify Root Access", and then with a lot of frustration you will see "Sorry, you don't have root access"..
Don't be frustrated, I am here to help you out!!
Click to expand...
Click to collapse
when i type adb shell in cmd the response is 'adb' is not recognised as an internal or external command, operable program or batch file.
what does it mean ?

vivdutta said:
when i type adb shell in cmd the response is 'adb' is not recognised as an internal or external command, operable program or batch file.
what does it mean ?
Click to expand...
Click to collapse
this means that you do not have adb.exe in the same directory as the commands you are typing

I can't root my iball slide q45. I tried farmroot, towelroot, kingroot, king pro root, kingo root, gingerroot, z4root. Plz give me solution.