Try One-Click UnBrick... If that doesn't work:
Try "3 button combo".. If that doesn't work:
Try a "301k Factory Mode jig"... If that doesn't work:
Try UnBrickable Mod http://forum.xda-developers.com/showthread.php?t=1236273 (if available on your platform)
If you require additional help, send me a private message, we can work something out.
Background
I've been working on stopping the bricking problem on our phones for a while now.
Ever tried JTAG unbrick recovery?--superhuman soldering skills no longer required for JTAG
Developing methods to recover bricks without JTAG - I keep this updated with current information as it develops.
ALL JIG VALUES here! --this will give you some resistor values to try
Altered water damage indicators --um... just in case you lick your battery and need warranty replacement
The Galaxy S Hack Pack--A compilation of resources for Galaxy S Phones.
I wanted to write some software which will help the user to understand what they are doing.. So I began the Heimdall One-Click project. http://code.google.com/p/heimdall-one-click/ Heimdall One-Click is not yet finished, but the Unbrick is complete. Heimdall One-Click is based on binaries from another Open-Source project, called Heimdall by XDA member Benjamin Dobell.
About One-Click UnBrick
This Software:
Will work on all Samsung devices which use Odin3
Is a single, portable executable
Is the first one-click anything for our devices on Linux
Works on Mac
Works on Windows
Is open source
Is programmed in Java
Deploys and installs Heimdall for your OS
Is super easy to use.... Only one button!
Demonstration video:
Image captured on Ubuntu 11.04:
{
"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"
}
This software is completely safe. It is a part of my Heimdall One-Click project. I wanted to release this to work out any cross-platform difficulties which may be encountered before I release Heimdall One-Click.
Instructions
1. Copy OneClick.jar to your Desktop-- or any other folder on your computer, It won't work on a network share.
2. Double click. -- As long as you have Java installed On Linux and Mac you are up and running.
For some versions of Windows as a work around to UAC (User Access Control, the annoying popups), a executable called "OneClickLoader.exe" has been deployed to the same folder as OneClick.jar. It is important that you do not rename OneClick.jar until after runnning OneClickLoader.exe
3. right click OneClickLoader.exe and select "Run as Administrator" -- Setup should be run-of-the-mill.
Fate-Silver said:
It works with all softbricked condition basically.
Stuck in a boot loop?
Is it still able to boot into CWM(Recovery Mode) or Download Mode.
If it's still able to go back into Download Mode, you don't need this software.
Just turn your Captivate into the Download Mode and flash back to STOCK Eclair or Froyo using Odin 1 Click or whatever similar.
Click to expand...
Click to collapse
Problems and Comments
If you would like to comment on something post here on XDA
If you're unsure of something, post here on XDA
If you have a show-stopping bug, please use this form: http://code.google.com/p/heimdall-one-click/issues/entry
This is a list of all bugs reported: http://code.google.com/p/heimdall-o...+Priority+Milestone+Owner+Summary&cells=tiles
I am very interested in feedback. If you would like to test this, just put your phone into download mode and click the unsoft brick button. It will simply reboot your phone. It will not flash any firmware and it does not have the capability to do anything except release the locks which prevent a phone from booting if they are present.
Click Here to Download One-Click UnBrick 10July11 from GoogleCode
You will need Java installed on your computer: Do you have java?
Disclaimer: All materials presented are for informational purposes. This content is not an authorization, advertisement, nor a suggestion to flash your phone with custom firmware. In no event shall I be held liable for any direct, indirect, incidental, spcial, exemplary, or concequential damages, including but not limited to loss of data, business interruption or damage to equipment. This information is released AS-IS with no written or express warranty or liability.
Linux users, mark this file as executable:
Code:
chmod +x OneClick.jar
All platforms: Double Click to run, OR, right click and open with Java, OR from command line:
Code:
java -jar OneClick.jar
Releases
-Version1.0 3July11 initial release
-Version1.b 4July11 fixes windows 7 & Vista UAC. Thanks to Roddreick for windows UAC workaround binary.
-Version1.IIX 5july11 fixes Winodws 7 and Vista. Adds countdown to non-imperative notifications. Adds real-time monitoring to determine if dependencies are actually required on Windows, rather then blindly installing. Since windows is such a PITA, this was alot of work. This version will work if you have Java installed and OneClick.jar on your computer (no network shares) on Windows XP, Windows Vista, Windows 7, Mac OS X Snow Leopard, and all Debian based Linux distributions including Ubuntu and Mint.
-Version 1.SVNR33 9july11 Much smaller package size, decreased by 5 megs. Fixes browser launching on Linux/mac. Decreases logging level to 1. Adds Log to temp folder at level 4. Adds optional donations to Heimdall or One-Click. Adds Windows Problem Resolution Center.
-Version 1.FINAL 10July11 Fixed UAC issues, File may now be renamed on Windows, Left launcher as alternate method, added linux asthetics, fixed driver link
Major Operating Systems requiring testing
Mac OS-X Leopard
Mac OS-X Snow Leopard
Mac OS-X Lion
Linux Ubuntu 32
Linux Ubuntu 64
Linux Mint
Linux Debian
Windows XP
Windows Vista
Windows 7
note: If you are having problems with drivers, This is caused by an invalid USB Device ID in the ROM installed on the phone.
If you'd like to contribute to the next version
Testing on your platform is as simple as putting your phone into download mode and clicking the button. It will simply reboot the phone if the phone is not bricked.
Grab the code from the SVN: checkout http://heimdall-one-click.googlecode.com/svn/trunk/
You can modify the code with NetBeans: http://netbeans.org/downloads/
If you come up with a positive change, I'll add you to the SVN as a contributor or a committer to ensure you get credit for your work.
I'm always looking to make a new version. Please give feedback.
wow this looks neat...i will definitely fire it up next time i brick my epic! great job AdamOutler!
edit: tested and it did kick my epic out of download mode in windows
if the command above gives you issues on windows 7 then do the following:
click the start button
goto programs>accessories>
right click on 'command prompt' and select run as administrator
cd to your download folder (ie: cd c:\downloads\oneclick\)
then type 'java -jar OneClick.jar'
you should only have to do all of that the first time so drivers for heimdall can be installed correctly
AdamOutler is working a better solution for the windows crowd
Awesome will try it out went nesesary!
Gotta check this out it's probably gonna have to wait til tomorrow looks cool
Sent from my phone on vacation
Nice work man! Hope I don't have to try it out anytime soon, but I really appreciate the effort you've put into this and all your other projects.
A definite must-have, thanks for this!
awesome this makes me less stressed out when flashing! thanks!will use when necessary!
just as a heads up, not every environment will play nice with the "doube click to run" as the file is stored now on google code. if you're on linux, simply either chmod +x the file or do "java -jar ./OneClick.jar" to run it (assuming java is in your path). seems ubuntu (and derivatives, I guess) assume the jar file wants to be opened with archive manager by default, so set it to run with java beforehand (launched with sun java 6, didn't try openjdk)
add to that the application doesn't seem to reliably recognize heimdall 1.0.1 CLI... attempting to run it returns a blank version string but after updating to 1.0.2b it recognized it fine. not world-ending, but just something I thought you should be aware of.
I'm a bit more interested in your heimdall one-click attempts though, as I'd like to see something like that implemented for 2.2 (since not every captivate can go back to JF6 it seems)... I've been pointing people at the leaked JI6 odin one-click for now, as it contains all the necessary files and is usable on every device.
edit: looking a bit more over heimdall's implementation, does this simply run the "heimdall close-pc-screen" command in an easy to use GUI?
Kaik541 said:
just as a heads up, not every environment will play nice with the "doube click to run" as the file is stored now on google code. if you're on linux, simply either chmod +x the file or do "java -jar ./OneClick.jar" to run it (assuming java is in your path). seems ubuntu (and derivatives, I guess) assume the jar file wants to be opened with archive manager by default, so set it to run with java beforehand (launched with sun java 6, didn't try openjdk)
add to that the application doesn't seem to reliably recognize heimdall 1.0.1 CLI... attempting to run it returns a blank version string but after updating to 1.0.2b it recognized it fine. not world-ending, but just something I thought you should be aware of.
I'm a bit more interested in your heimdall one-click attempts though, as I'd like to see something like that implemented for 2.2 (since not every captivate can go back to JF6 it seems)... I've been pointing people at the leaked JI6 odin one-click for now, as it contains all the necessary files and is usable on every device.
Click to expand...
Click to collapse
True... I'll add that to the first post.
Heimdall one-click is operational. I'm working the kinks out of it with the one-click unbrick first. I've sucessfully flashed my phone on all three platforms using heimdall one-click. I don't feel comfortable releasing something like that without thorough testing. This is basically testing for my one-click platform.
can you do a write up on how to brick your phone, and the many ways to it.
Awesome work. Very good and very useful tool, Adam!
Stev3-o said:
can you do a write up on how to brick your phone, and the many ways to it.
Click to expand...
Click to collapse
Sure.. too easy.
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
AdamOutler said:
Sure.. too easy.
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
Click to expand...
Click to collapse
Quick question: Does the Odin 1-click flash the primary bootloader? I think I may have hardbricked my cappy tonight. I went from cognition beta 1 (2.3.3) with new bootloaders and one-clicked to 2.1 the phone made it to rfs and then froze. Now it will do nothing. You think I killed it? Thanks.
Coldskiesfullofblue said:
Quick question: Does the Odin 1-click flash the primary bootloader? I think I may have hardbricked my cappy tonight. I went from cognition beta 1 (2.3.3) with new bootloaders and one-clicked to 2.1 the phone made it to rfs and then froze. Now it will do nothing. You think I killed it? Thanks.
Click to expand...
Click to collapse
that's a question for Q&A.
You'd need to check it out with UART for any answers.
So if I read the op and the links right there still isn't a non jtag solution for hard bricks? I asked toys becuase it seemed that with refering to the herr bricks and what causes them as well that you have found a work around... I probably just misunderstand it though.
SIGNATURE : Life is like a box of captivates, you never know if your gps will work
AdamOutler said:
Sure.. too easy.
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
Click to expand...
Click to collapse
Can this software fix the hard bricks? If yes.. too good, many thanks. You made the life less stressfull.
Haven't had to use it and hopefully never will but thank you Sir!
bigbyte.me said:
Can this software fix the hard bricks? If yes.. too good, many thanks. You made the life less stressfull.
Click to expand...
Click to collapse
NO. Hard Bircks are mainly because of wrong Bootloaders, if that the phone is unable to boot, so can't access it. If its HardBricked my guess is only Samsung can unbrickit. BTW new GB bootloaders are un-brickables. They now has the hability to re-download a ROM on Phone<---->PC Screen.
thanks, you are genius, huge help!
Related
[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting! v1.2
Hey XDAers. Getting ADB setup and working is an essential part to rooting your Android device and helps layout the foundations to better understanding the language and using it in this environment. While not going into extreme detail, this is just a quick guide or overview on the first part of rooting; Getting ADB setup and working.
** Make sure your Transformer is not currently connected to your PC yet. We will be installing device drivers first (Step 7) and modify a setting on your tablet first before connecting to your PC (Step 8).
Step 1 :
Download and install the Android SDK.
You can download the SDK from the Google Developer's website. I have linked for you the download page and a direct link to the installer (Note: the direct link may change in the future with future versions, I will try stay on top of this and change the link)
http://developer.android.com/sdk/index.html
http://dl.google.com/android/installer_r10-windows.exe
*New Version : http://dl.google.com/android/installer_r11-windows.exe
You may or may not be prompted to install the latest version of Java if you haven't done so already, install it, and you may or may not have to reboot your computer.
Step 2 :
Once the install is complete, navigate to the directory in which you installed the SDK and launch the SDK Manager executable. It may or may not ask you to download and install the Java JDK, do so if you haven't already.
*When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already*
Answer :
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead.
Thanks Crimton!
Click to expand...
Click to collapse
Step 3:
Once the SDK Manager is launched, it will look something similar to the window below.
{
"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"
}
You will want to do something along the lines of update all or install all. This way it will download all the latest packages and you willhave the latest SDK tools installed.
Once that is complete, you can exit out of the SDK Manager.
Step 4:
Open up a command prompt window. You can do so by holding the WinKey+R, a run window will appear, type CMD, and hit enter.
Step 6:
Within the Command Prompt window, navigate to the Android SDK folder\platform tools folder (Command Prompt command : CD foldername\foldername\foldername\etc)
Step 7:
Now install the ASUS Sync software if you haven't loaded it previously. http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download. Just select your operating system, hit download, then install.
Why are we installing the ASUS Sync software you ask?
Well mainly because it has USB drivers that will help your PC operating system detect and display your ASUS Transformer. Without the drivers, ADB wouldn't be able to detect your device most likely!
*For other android devices, you will need similar software from that manufacture. HTC Sync for HTC devices as an example.
Click to expand...
Click to collapse
Step 8:
Enable USB Debugging on your android device / Transformer.
Go to Transformer Tablet, go to settings -> applications->Development, turn on USB Debugging.
Step 9:
Connect the USB cable from your android device / Transformer to the PC. It will begin to automatically install drivers, let it do so and complete. May ask to reboot machine.
Step 10:
Once that is done, go back to the command prompt. Run ‘ADB Devices’
You should see something like above, indicating it detected the transformer, if not, run the following ‘adb kill-server’, ‘adb start-server’, ‘adb devices’
Ok, if you are seeing something like the screenshot above then success, you have successfully gotten ADB up and working! Congratulations! That wasn't too hard now was it? You can now follow one of the root guides and follow the directions and you should be on your way to a fully rooted device. Cheers!
-------
Troubleshooting:
In the event you complete the steps above but your computer either will not recogonize the Transformer in Windows as a device, or ADB will not see it please try the following to see if this will fix it for you. You only need to try these if the above steps aren't working for you, but most people, they work fine.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
-------
Notes:
-If you want another guide on something else, let me know, and I will see what I can do.
-Yes this has been posted a million times I know, but I thought this might help out those few people that don't feel like looking around. Plus, it has nice color illustrations. Who doesn't like picture books?
-------
Credits
Crimton for Java JDK workaround when not showing as installed
sourworm for new link to SDK installer
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
stuntdouble said:
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
Click to expand...
Click to collapse
Will do when I get home, thanks for the tip.
Ill add this to the FAQ
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
Glad you got it resolved, I will edit the guide and make note about java installation.
Daughain said:
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
Click to expand...
Click to collapse
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
neilkarunatilaka said:
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Click to expand...
Click to collapse
at a glance, even that thread makes it look like more trouble than it is. but good info
RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
How did you fix it? I've been struggling with this same issue for at least a month now.
n25philly said:
How did you fix it? I've been struggling with this same issue for at least a month now.
Click to expand...
Click to collapse
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Crimton said:
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
lol, simple solutions are good. Just wish it didn't take me a month to find that one out.
Very simple and easy to follow. Thanks OP.
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
randy_c said:
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
Click to expand...
Click to collapse
Sorry to hear that. Off the top of my head, I'm not sure what could be causing this. But here are a couple things you can try. And please let us know what happens next.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
andrew53517 said:
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
Click to expand...
Click to collapse
1) First thing you can try is the famous 'adb kill-server' 'adb start-server' commands and see if that will get it going. Also 'adb usb' will restart the daemon listening on USB, so maybe that could make it usable. If not, make sure the ASUS Sync app is not running, and perhaps see if there are any running services/apps on your Transformer that could be causing the conflict. Download System Panel Lite from Market and tell it to end all apps, then try again (make sure USB Debugging is enabled)
If you tried all of that, and still no dice, make sure no USB Drives or Memory Cards are connected, then connect the Transformer (w/ USB Debugging), go to Device Manager, uninstall the USB drivers for the device if you can find it or it may show up as a USB Mass Storage device under USB Controllers, then disconnect the Transformer, reconnect the Transformer, it should reinstall the drivers for the Transformer since you already have ASUS Sync installed, then retry.
If again still no dice, try using the ASUS USB Windows Drivers and going to Device Manager and updating the drivers with those you downloaded (download the correct ones for your particular operating system, and then try again.
Now, if this still doesn't work, let me know, and I'll try think of something else. Maybe someone else has had this issue and come up with a workaround or solution, but I'm drawing a blank currently. I'll sleep on it and see if I can think of anything else
2) You don't have to type that up all the time. What you can do is navigate the platform tools folder (or whatever folder has the adb files), then if on Win 7, hold shift and right click on the folder (Platform Tools for example), and you will see an Open Command Prompt here. Hit that, and it will already be in that root folder. But in general, in a command prompt window, once you have navigate to the specified folder, you will be in that folder, so you will only need to type ADB 'command' if that makes sense.
[/LIST]
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
andrew53517 said:
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
Click to expand...
Click to collapse
If you get a chance, try this on a Windows XP or Windows 7 machine that you haven't connected the Transformer too yet, and follow the guide exactly, and I'm pretty sure it will work without a problem I'm just thinking something has happened when it loaded up the drivers for you initially and that is why you are having the issues, or some background process on either Windows or the Transformer is making the device seem "busy", thus giving you the not ready error, as this process has worked for many many other users.
I was just thinking about it. Maybe I can try that on my downstairs computer. Ill give it a shot Sunday night and see how it goes...ill let you know...
How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"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"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!
I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.
Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?
Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!
I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.
ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.
sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.
+1 for sticky
sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.
Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App
bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.
sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.
bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse
Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App
Introduction
This is an Open Beta of the Heimdall One-Click flashing utility.
I began the Heimdall One-Click project at the start of June. Heimdall One-Click is based on Heimdall by XDA Senior Member Benjamin Dobell. The goal is to reduce the number of problems we've seen in flashing packages. Once "Connected" is working on all platforms The beta test is complete.
There has already been some serious beta testing done to date. All that is left is cross-platform compatibility
Beta Test
You don't have to flash to test. Just verify "connected" appears.
1. Ensure you have the latest version of Java installed on your computer: http://www.java.com/en/download/installed.jsp?detect=jre&try=1
2. Download and run this: http://oneclick.adamoutler.com/files/Modem-KC1-One-Click.jar
3. Put your phone into Download mode, and connect to the computer. Verify you see "Connected" displayed. see image here:
{
"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"
}
4. reply to this post with the OS you use, result and any problems!
5. optionally click flash to upgrade to the KC1 modem.
Platforms requiring test
Linux Ubuntu/Debian 64
Linux Ubuntu/Debian 32
Windows 7 -on hold
Windows Vista -on hold
Windows XP -on hold
Mac OS-X Lion
Mac OS-X Snow Leopard
Mac OS-X Leopard
Please note: the final version will be roughly 10 megs, this beta contains alot of extra fat to be trimmed.
Beta7 31July2011 Fixed installation of VCC redistributable on each start of program for windows. No changes for Linux or Mac.
no known issues.
Beta6 31July2011 No fixes. Added live PIT View to show what has been flashed and keep an up-to-date log of what's going on in the background.
noted problem with Windows installation of Visual C++ on every run.
Beta5 31July2011 Revised windows installation. No longer installing heimdall.exe to program files. It is now created in temp folder on each start of the application. Visual C++ redistributable is installed when required. Drivers are installed on first click of "flash" button if connection to device is not possible. No changes for Linux or Mac.
Beta 4 30July2011 Fixed installation order for Windows so no reboot/restart is required. Added log into Details window. Each instance gets its own unique and randomized folder. Added logging for flash operations. Fixed unused imports. Fixed links for windows. Reduced memory usage. No changes for Linux or Mac.
Installation of drivers is still a problem on some systems. Use of "Program Files" is not acceptable as a "repository" for binaries, must have an uninstaller or create a binary instance installation.
Beta 3 29July2011 Fixed installer for Windows and Mac. No changes for Linux.
Windows installer is demonstrating problems with order of verifications... VCC redistributable should be installed before heimdall is verified. This leads to having to close the application out and retry. Windows not reporting heimdall installed after installation without reboot. All windows hyperlinks are inoperative.
Beta 2 29July2011: Initial Release.
problem with windows platform installer renders platform unusable. Problem with mac platform does not install newest version of Heimdall.
why not just flash modems thru CWM?
Thegodfather156 said:
why not just flash modems thru CWM?
Click to expand...
Click to collapse
Because he choose something "safe" to flash for the screen shot. Cuz some ppl will want to toy with this, but for the very first time will not actually flash unless they see it exactly the screen shot Adam posted.
it is an EXAMPLE
Also, he is showing just what this "one-click" can do.
Nice job sofar keep it up
Sent from my SAMSUNG-SGH-I897 using XDA App
The hits just keep coming. (;~)
Sent from my SGH-I897
DaNaRkI said:
Because he choose something "safe" to flash for the screen shot. Cuz some ppl will want to toy with this, but for the very first time will not actually flash unless they see it exactly the screen shot Adam posted.
it is an EXAMPLE
Also, he is showing just what this "one-click" can do.
Click to expand...
Click to collapse
he seems to be pretty nifty when it comes to Heimdall. i like it, i was just curious what the advantages of this method in comparison to flashing modems thru CWM
you dont have to bold your words, i wasnt trying to be a ****.
Thegodfather156 said:
why not just flash modems thru CWM?
Click to expand...
Click to collapse
As was stated, this is a beta test. I'm not going to release a full package with kernel, factoryFS, Cache and bootloaders for a beta. However, this method makes it much simpler to flash a modem then any other method.
The simplest method for flashing a modem with CWM
1. download package with phone via barcode or transfer to /sdcard/Download
2. Start phone in recovery mode
3. Select install zip from SDCard
4. select Choose zip from sdcard
5. select "download" and then select "modem.zip"
6. scroll down to "yes" and select it
7. select reboot
One-Click:
1. connect phone in download mode
2. download/run this package
3. click flash.
Also, I'll be providing one-click packaging... simply select the Heimdall 1.3 tar.gz file and it will make a one-click out of it.
I've got the mac problems worked out. I'm currently working on windows. A beta 3 will be up shortly.
AdamOutler said:
As was stated, this is a beta test. I'm not going to release a full package with kernel, factoryFS, Cache and bootloaders for a beta. However, this method makes it much simpler to flash a modem then any other method.
The simplest method for flashing a modem with CWM
1. download package with phone via barcode or transfer to /sdcard/Download
2. Start phone in recovery mode
3. Select install zip from SDCard
4. select Choose zip from sdcard
5. select "download" and then select "modem.zip"
6. scroll down to "yes" and select it
7. select reboot
One-Click:
1. connect phone in download mode
2. download/run this package
3. click flash.
Also, I'll be providing one-click packaging... simply select the Heimdall 1.3 tar.gz file and it will make a one-click out of it.
I've got the mac problems worked out. I'm currently working on windows. A beta 3 will be up shortly.
Click to expand...
Click to collapse
you are on another level when it comes to developing dude. keep up the good work.
Works fine on Ubuntu 32bit (I already have udev rules configured from a heimdall source build)
-.-;
@Adam - so.. does this thread mean your hijacking and near constant post in the official Heimdall thread will cool? You were making that thread a lil hard to keep up with. Granted seeing such an interested dev at work was pouring out tons of really neat info
@godfather - Just putting it up there as a preventive incase someone else might consider jumping on your question and going off all "I can flash most of that thru CWM, and have never had a problem with ODIN" crap. I've seen some ppl here post things like how Heimdall is bad cuz it was reverse engineered by some guy, and that they would rather stick with such a poorly written program just cuz it came from samsung... Cuz clearly we all love the stock cappy
Tried to run it under windows 7 64Bit. Says I must run as administrator. Although I am logged in as administrator, I atttempted to use the runas command from a command window. Looks like your command line just come back with a syntax error for me. Maybe I did something wrong since I've never used that command before. In any case...problematic to get it installed here.
kb9nvh said:
Tried to run it under windows 7 64Bit. Says I must run as administrator. Although I am logged in as administrator, I atttempted to use the runas command from a command window. Looks like your command line just come back with a syntax error for me. Maybe I did something wrong since I've never used that command before. In any case...problematic to get it installed here.
Click to expand...
Click to collapse
I'm uploading a new version which corrects that problem now. I didn't realize the changes in 1.3 would ripple the installation across all the platforms.
I've finished uploading commits and a new version of the KC1 beta. Please give feedback on Windows and Mac. Linux has been tested working.
working as connected here!!! After a few installs of drivers and C++ redistributable...then it said I had to install heimdall manually..clicked OK and they I saw the connected message. Looks like no joy on the KC1 upload...I'm perpetually "handshaking with loke" Phone has yellow digger guy on it and it says downloading on the front..??
Adam, this looks nice, I finally figured out how to install the drivers and find my device. I downloaded the Heimdall suite 1.3.0 and when I click on drivers, it sees the device. Question: if I install the drivers, will it effect the drivers I have intalled for Odin? Also, if I want to use the Heimdall suite for flashing custom ROMs does it work the same as Odin as far as the files and where to put them?
Rhiannon224 said:
Adam, this looks nice, I finally figured out how to install the drivers and find my device. I downloaded the Heimdall suite 1.3.0 and when I click on drivers, it sees the device. Question: if I install the drivers, will it effect the drivers I have intalled for Odin? Also, if I want to use the Heimdall suite for flashing custom ROMs does it work the same as Odin as far as the files and where to put them?
Click to expand...
Click to collapse
Yes. Heimdall uses the well known and understood Open-Source LibUSB drivers. Odin uses closed source proprietary drivers.
kb9nvh said:
working as connected here!!! After a few installs of drivers and C++ redistributable...then it said I had to install heimdall manually..clicked OK and they I saw the connected message. Looks like no joy on the KC1 upload...I'm perpetually "handshaking with loke" Phone has yellow digger guy on it and it says downloading on the front..??
Click to expand...
Click to collapse
Which version of windows is that?
Win 7, professional, 64bit
Win7 ultimate x64 issue
Everything seemed to work fine at first, showed device connected then after a few seconds it would disconnect and reconnect over and over and over. I tried to recreate the issue but could not. I tried a few more times and it only disconnected and reconnected once after 30 seconds and it wouldn't do it again. Anyone else see anything like this. I attached a screen shot.
I posted this on the Rootzwiki forum at
http://rootzwiki.com/topic/31737-possible-root-method-for-droidx-on-621-reported-working/
and figured might as well post it here as well.
Since all these devices (Droid 2/R2D2/D2G/DX2 and DX seem to be vulnerable to the same exploit found by phifc at
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
I have assembled rooting methods for all of them in EzSbf style CD. I have tested it on my D2G, and the same method has been tested by multiple users on the D2/R2D2, and has worked fine.
Credit for this method go to phifc, djrbliss, and the others who developed the method.
I have simply taken the method, and assembled the tools.
Credit for the idea behind the CD method should go to 1KDS, as I have mostly patterned this CD after his method.
Credit should also go to Skrilax_CZ, as without his Motorola Android Firmware (De)packer, we wouldn't be able to have a 55 meg CD that covers multiple devices.
Special thanks also to themib for testing and troubleshooting on the DroidX2. In fact, since I don't have a DX2, he actually did a majority of the work in finding a method that would work (the method for the D2 and D2G doesn't quite work), and then we worked together to get it assembled and working.
Several people on the rootzwiki forum have reported this to work on the Droid X as well.
This CD is for the D2,R2D2, D2G, and DX on Android version 2.3.4, and the DX2 on 2.3.5.
Of course, like all other things here, I have done my best on this, but there are no guarantees, and anything you do on your phone is at your own risk.
So, without further ado, here is a link for the CD
http://www.mediafire.com/?mim304k214kl41h
and the md5 is
7baee9c34f6ef7ad0b4fa219ae387c68
If any one here can confirm this works this thread should be stickied.
Nice job finding this.
Sent from my LG-P930 using Tapatalk 2
So.. how do you use this? My rezound is my primary phone but just acquired this dx in a barter of sorts today and want some aosp goodness.
My rezound is s-off so I've never had to use cd's or linux or whatever it is you need to do to root this thing. Any help would be GREATLY appreciated. All the other tutorials out there confused the §hit out of me and I've got no experience in linux.
Stock .621
zac41189 said:
So.. how do you use this?
Stock .621
Click to expand...
Click to collapse
Its pretty self explanatory, it seems.
You would be doimg the community a great service if you tried it out and posted back. I unfortunately got rid of my dx ad have a dx2 so otherwise i would try it.
Oh.... the dreaded .621 lol
No seriously if ypu go to the wiki link maybe more info.
Post back please
Sent from my LG-P930 using Tapatalk 2
This root method has been confirmed to work by several members over at Rootzwiki.
Sent from my Black Iced X
Tried this on a used replacement Droid X. Worked like a charm.
Hey all, pretty big n00b here. Long post, I apologize in advance.
Background:
So I had a droid X running on GB ApeX that my friend had helped set up for me, and I recently had to get a replacement bc the screen became pixilated. I figured I'd try to be self-sufficient and back up my old phone, then root this new one, etc., only to find out that apparently .621 is much harder to root.
I tried and failed at the linux milestone SBF method of rooting my new, replacement stock .621 Droid X to .604--for some reason I couldn't boot my macbook into linux mode after burning the disc. Probably my own fault.
Question:
I'm kind of unsure how to utilize the CD you have to download. Do I have to burn it to a disc? And if so, are there specific instructions? I'm pretty fritata when it comes to all of this, so please be gentle!
Thanks in advance!
How do you use this
Sent from my DROIDX using xda app-developers app
Dr. J said:
I tried and failed at the linux milestone SBF method of rooting my new, replacement stock .621 Droid X to .604--for some reason I couldn't boot my macbook into linux mode after burning the disc. Probably my own fault.
Question:
I'm kind of unsure how to utilize the CD you have to download. Do I have to burn it to a disc? And if so, are there specific instructions? I'm pretty fritata when it comes to all of this, so please be gentle!
Thanks in advance!
Click to expand...
Click to collapse
You burn the iso image to a disc.
After you have burned the image to a disc put it in your computer and shut your computer down.
Now turn it back on and hold the 'c' key on your keyboard. This should boot you into the inserted disc.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 09:10 PM ---------- Previous post was at 09:07 PM ----------
htcdroidincredible23 said:
How do you use this
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
Download the image, burn it to a CD, place it in your computer, shut down said computer, turn the computer on and boot from the CD. From there it should be self explanatory.
Note: booting into the disc can be tricky. Some computers require you to press a button (F8 or F12, usually); however, this is completely dependant on the computer you have so it may require some searching to find the instructions for your specific computer.
Sent from my Galaxy Nexus using Tapatalk 2
updated many times see change log
bhigham/beh modified the root method
based on New D2 root method for stock 2.3.4 (621/622) found (Droid2, R2D2)
How this works
Originally Posted by phifc
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
originally posted by bhigham/beh
Since all these devices (Droid 2/R2D2/D2G/DX2 and DX seem to be vulnerable to the same exploit found by phifc at
http://rootzwiki.com...nd-droid2-r2d2/
I have assembled rooting methods for all of them in EzSbf style CD. I have tested it on my D2G, and the same method has been tested by multiple users on the D2/R2D2, and has worked fine.
Credit for this method go to phifc, djrbliss, and the others who developed the method.
I have simply taken the method, and assembled the tools.
Credit for the idea behind the CD method should go to 1KDS, as I have mostly patterned this CD after his method.
Credit should also go to Skrilax_CZ, as without his Motorola Android Firmware (De)packer, we wouldn't be able to have a 55 meg CD that covers multiple devices.
Special thanks also to themib for testing and troubleshooting on the DroidX2. In fact, since I don't have a DX2, he actually did a majority of the work in finding a method that would work (the method for the D2 and D2G doesn't quite work), and then we worked together to get it assembled and working.
This CD is for the D2,R2D2, D2G, and DX on Android version 2.3.4, and the DX2 on 2.3.5.
One note if you have troubles with it not working. It might be necessary to disconnect the phone after it flashes the preinstall and reboots. It seems that some phones may not complete the reboot process before being rebooted by ADB, so you may need to disconnect the phone when it starts booting, and let it boot fully before hooking it back up. when hooked back up, it will be rebooted, and should go on with the process like normal.
Of course, like all other things here, I have done my best on this, but there are no guarantees, and anything you do on your phone is at your own risk.
So, without further ado, here is a link for the CD
http://www.mediafire...mim304k214kl41h
and the md5 is
7baee9c34f6ef7ad0b4fa219ae387c68
Click to expand...
Click to collapse
mirrors posted Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
How to verify the file was downloaded correct with
MD5/SHA-1 Hash Checksums
what is ezSBF?
original [TOOL] ezSBF (not for 2.3.4)
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
Click to expand...
Click to collapse
1KDS said:
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP) or (Load to a USB flash drive)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"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"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
________________________________________________
You will now be in the script and ready to flash.
Click to expand...
Click to collapse
basically read onscreen directions
select DX
don't use numbers on right side of your keyboard, just use the ones above qwerty
turn phone on, connect to pc with usb cable
check usb debugging (settings/apps/development)
select charge only usb mode in top status bar
press continue
adb will push
Code:
data/local.prop /data/preinstall_md5/magic.md5
program will prompt you to
manually reboot phone to bootloader (Hold volume up+down buttons and power button, or hold Vol.Down and Camera and wait for the screen to flash)
program will will be flash repacked sbf (less than 50mb)
Program will reboot phone twice, very important (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
adb pushes su,superuser, and busybox
program will reboot to recovery,
manually wipe cache (should auto reboot to recovery, at android andy press both volume buttons, if it doesn't press home button and hold it in then press your power button, hold it in also till you see a triangle on the screen w/ android andy then press both volume buttons)
then select reboot
rooted
error info
when running the program you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
after flashing files in bootloader, phone reboots to bootloader, instead of normal android operating system..... now what?try disconnecting usb, pull battery,wait a few secs, replace battery, reboot, wait for reboot to complete, reconnect usb
Using Oracle VM VirtualBox, and Magic MD5 root iso
If you planning on making nandroid backups or flashing roms
read [HOW TO] Install/Use Droid 2 Bootstrap
My Lists
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
edit:
02 Oct 2012 added mac info
16 Nov 2012 reworded
13 Dec 2012 major rewrite
Help
Ok I am having some problems loading up the .iso. I am trying it on a 4gb usb drive and I put the files onto the usb with unetboot. I reboot after all of that and I press F12 for boot options. I click enter on USB Drive, but after that it says operation system not found.
couple things to try
did you verify iso md5 checksum before putting on usb drive
when you have windows running, do you have a boot folder on usb drive, it should be 50mb
sd_shadow said:
couple things to try
did you verify iso md5 checksum before putting on usb drive
when you have windows running, do you have a boot folder on usb drive, it should be 50mb
Click to expand...
Click to collapse
Sorry I am a nooby at rooting a DX, but How would I verify the iso md5 checksum. And I deleted everything on my usb till I figure that part out.
md5 creates a check sum number using an algorithm, if you compare your file with the original md5
you can be 99.9% sure that your file is not corrupt
use this http://download.cnet.com/md5-checker/3000-2092_4-10410639.html
original md5 is in op
edit: and here 7baee9c34f6ef7ad0b4fa219ae387c68
Ok it said the codes match, so what do I do from there?
you followed these instructions
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)
Download UNetBootin for Windows
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
Yes I did follow those directions.
after you flash iso, to usb drive
you should have one folder named BOOT
in Boot 3 items isolinux folder, bzimage, and rootfs.gz
Correct, I do have those in the boot folder.
maybe a incompatibility issue, not all PCs can boot from usb drives
try a different usb port
different usb drive
try burning cd
different pc
Hello there,
This thread isn't finished yet. It's a Work In Progress thread, for setting up a working Environment for Developing Apps and also a quick guide for developing ROMs from source. I hope to see you again when there are more updates!
Click to expand...
Click to collapse
Are you on Windows or OS X and do you want to develop for Android with(out) dual-boot or installing a whole new operating system on your PC? Well, then you have come to the right place!
In this guide I'am going to show you how to set-up a virtual machine with Java, the Android SDK, the Eclipse IDE and the Android Source Code.
I will be using Windows in this tutorial, but you can use pretty much every OS out there; The setup is pretty much the same. I use Ubuntu 12.10 for the VirtualBox guide and 12.04 for the other guides in this thread, but you can use every version of Ubuntu you'd like.
So let's get started.
1. Setting up VirtualBox (You can skip this step if you want to develop apps with your current OS, or if you don't want to build ROMs from source code)
VirtualBox is a cross-platform virtualization application. What does that mean? For one thing, it installs on your existing Intel or AMD-based computers, whether they are running Windows, Mac, Linux or Solaris operating systems. Secondly, it extends the capabilities of your existing computer so that it can
run multiple operating systems (inside multiple virtual machines) at the same time. So, for example, you can run Windows and Linux on
your Mac, run Windows Server 2008 on your Linux server, run Linux on your Windows PC, and so on, all alongside your existing applications. You can install
and run as many virtual machines as you like -- the only practical limits are disk space and memory.
VirtualBox is deceptively simple yet also very powerful. It can run everywhere from small embedded systems or desktop class machines
all the way up to datacenter deployments and even Cloud environments.
Click to expand...
Click to collapse
a. Go to virtualbox.org and select your proper operating system, in my case this will be the Windows Hosts download.
{
"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"
}
b. Once downloaded, run the installer and leave all boxes ticked as they are and hit ''Install'' at every pop-up.
c. Now go to ubuntu.com and download the 32 or 64 bit image. I'd recommend 32 bit, since it'll run smoother in VirtualBox, but if your intention is to develop ROMs, you should pick the 64 bit.
d. When it has downloaded, open VirtualBox and hit the ''New'' button in the upper left corner. Call it Ubuntu12.10 and make sure it looks like the following.
e. Add at least 1000MB of RAM and if you can spare more, but make sure it's not more than half of your host PC RAM, otherwise you're PC could crash. Then click ''Next".
f. Now choose ''Create new Virtual Harddisk and hit ''Next'', then choose ''VDI'' and then the ''Dynamic'' option. Now choose you amount of storage in the Virtual Harddisk, I'd recommend at least 40GB, but if you've in mind developing from source, I should go for 70GB or more. After that, click the ''Create'' button.
g. Click on the Ubuntu12.10 tab on the left side and then hit ''Storage'' in the right pannel.
h. Now hit ''Empty'' button underneath ''Controller IDE'', click in the right pannel the disk image and click ''Choose virtual CD/DVD-Image''
i. Navigate to the Ubuntu12.10 Image you've downloaded earlier and open it. After that, hit ''OK'' on the downright corner.
j. Now click the option ''Display'', in the same tab as in step ''g''. Move the ''Videomemory'' all the way up to the top and hit ''OK'' again.
k. Just hit ''Start'' and Ubuntu should right boot to the installer screen.
l. First pick your language on thee right side, then we want to ''Install Ubuntu''.
m. Tick the boxes ''Download updates while installing'' and ''Install this third-party software''. Make sure you are connected to the internet and your good to go; hit ''Continue''.
n. Leave the installation type on ''Erase Disk and install Ubuntu'', don't worry, this will only wipe your Virtual Harddisk. Hit ''Continue'' again; this will start the installation process.
o. While installing, Ubuntu will ask you for your location, keyboard layout, name and give you some information about Ubuntu 12.10. For me this installation took around 50 minutes.
p. If it says ''Remove Disk please'' or something simular, just press ''Enter''. When the VM has booted up, login, then click at the top ''Devices''. At the bottom it says:''Install Guest additions..''. Click it and follow the instructions on screen. It'll auto-reboot.
q. The last step: Search for the programm: ''Software Updater'' in ''Dash Home''. Open it and it will check for updates, then click ''Install now''. This will install the latest Ubuntu updates.
Now you have a complete Ubuntu OS running in VirtualBox. Congratulations!
Reserved for further updates
Reserved for further updates
Reserved for further updates
I don't know about OS X but eclipse works in both Linux and windows. Why would anyone want to setup virtualbox for app development?
pedja1 said:
I don't know about OS X but eclipse works in both Linux and windows. Why would anyone want to setup virtualbox for app development?
Click to expand...
Click to collapse
If you are a developer you can definately use linux, because of the android and linux integration; when developing for Android, Linux provides more features than Windows or OS X does.
Thatgrass.
Thatgrass said:
If you are a developer you can definately use linux, because of the android and linux integration; when developing for Android, Linux provides more features than Windows or OS X does.
Thatgrass.
Click to expand...
Click to collapse
No really. You get all the same features in OS X and Windows, I can't think of one reason to use Linux over any of the other areas.
Thatgrass said:
c. Now go to ubuntu.com and download the 32 or 64 bit image. I'd recommend 32 bits, since it'll run smoother in VirtualBox.
Click to expand...
Click to collapse
If you're going to build parts Android (the OS, I mean) from source, I believe JB *requires* a 64-bit VM.
Tungstwenty said:
If you're going to build parts Android (the OS, I mean) from source, I believe JB *requires* a 64-bit VM.
Click to expand...
Click to collapse
There is still more to come
pedja1 said:
I don't know about OS X but eclipse works in both Linux and windows. Why would anyone want to setup virtualbox for app development?
Click to expand...
Click to collapse
My Windoze side is really just for gaming & a bit of photoshop work. I much prefer developing on the Linux side for ease of use, especially with command line stuff. It all just works 'better'. I've been using Ubuntu 12.04 64bit with Eclipse Juno as a guest on my hosting Win 7 machine for over a year now. I find it much better to compartmentalize my work, especially since I routinely reformat my win partition for various reasons.
No, really, please tell me what, if any, improvements there are in developing in *nix over windows or osx?
I develop in osx at work and windows at home, and the only differences I've found are really in the underlying OS features (god, Finder SUCKS!). OSX does have a better, one stop ADT/Eclipse install, but that's it. What does *nix offer?
The only thing a VM can offer is using it to run android itself, so you don't need the emulator, but I think that's a bit of hassle for no improvement.
But if there are reasons, I really want to know! I'm always up for a better workflow.
MacDegger said:
No, really, please tell me what, if any, improvements there are in developing in *nix over windows or osx?
I develop in osx at work and windows at home, and the only differences I've found are really in the underlying OS features (god, Finder SUCKS!). OSX does have a better, one stop ADT/Eclipse install, but that's it. What does *nix offer?
The only thing a VM can offer is using it to run android itself, so you don't need the emulator, but I think that's a bit of hassle for no improvement.
But if there are reasons, I really want to know! I'm always up for a better workflow.
Click to expand...
Click to collapse
Development environments are really up to the developer. I personally never developed in a mac os environment, I am just too inexperienced with mac os, I use my mac basically for its garage band application.
That said, I prefer linux when developing mainly for the control it gives me with regards to the total environment as opposed to windows very restricted nature. One feature I like with linux is the ability to overclock the cpu without restarting for when compiling especially custom kernels. Another is the ability to use high-end graphics card gpu to aide in compiling process. (http://hackaday.com/2012/12/14/leveraging-the-gpu-to-accelerate-the-linux-kernel/) The ability to create a chrooted environment to isolate your toolchains. Many more actually but mostly unrelated to android app development. Best reason so far is you can use an outdated machine to dev with linux coz it's free and supports some ancient machines.
Edit:
@MacDegger: Mac and linux are like distant relatives. So it's really not much difference. But if you're up to it installing a virtual linux machine might give you the chance to try the environment and see for yourself if there are benefits for your workflow.
Hi Folks
Sybregunne said:
The ability to create a chrooted environment to isolate your toolchains. Many more actually but mostly unrelated to android app development.
Click to expand...
Click to collapse
I was doing that until very recently, It became a bit of a pain however, Having to basically install an OS and set the user(s) , It leave my mount points in a state and plus I use a lot of bash aliases so they all where messed up as well.
There's another way! use update-alternatives to set up a gcc with g++ slave for any version of the toolchain you want, Install them all if you want and some cross compiler to boot. It makes cross compiling as easy as typing gcc and also makes compiling against the androideabi using standard make file "fun" as well
http://askubuntu.com/questions/182027/how-to-use-gcc-4-7-in-place-of-4-6-ubuntu-12-04
The links for 12-04 , it's good for 12-10 , should be good for any really , It's linux init'
Here's my list
Code:
Selection Path Priority Status
------------------------------------------------------------
0 /usr/bin/gcc-4.2 80 auto mode
1 /media/android/build/toolchains/android-arm-standalone/bin/arm-linux-androideabi-gcc 60 manual mode
2 /media/android/build/toolchains/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-gcc 60 manual mode
3 /usr/bin/arm-linux-gnueabi-gcc-4.7 40 manual mode
4 /usr/bin/gcc-4.2 80 manual mode
5 /usr/bin/gcc-4.4 40 manual mode
6 /usr/bin/gcc-4.5 60 manual mode
7 /usr/bin/gcc-4.6 60 manual mode
* 8 /usr/bin/gcc-4.7 40 manual mode
9 /usr/bin/x86_64-unknown-linux-gnu-gcc-4.8.0 60 manual mode
I just set a bash alias called setgcc like this "sudo update-alternatives --config gcc" , combine that with a java-5 install which automatically sets up alternatives and you can build any version of android you like all from the comfort of Lubuntu 12.10 ......Just for s**ts and giggles I built version 1.0 ( manifest ) after stumbling on the manifest file, seems google rebased and dropped some early branches after the kernel.org hack, were as the down stream mirrors obviously didn't!
LOL, All of that's a little OT so I'll close by saying you can do all this on virtual box!
i still like VMware Player better'
because it wont use like 100 GB ( for linux ) in once
it will have a max of 100
and will reshape its hdd according to the data you have so you wont have lost space
If someone needs a german tutorial
http://www.youtube.com/watch?v=b8LpWiq9VW8
here is one
How can i install Android 4.2?
mertemur said:
How can i install Android 4.2?
Click to expand...
Click to collapse
How do you mean? In virtualbox?
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
How do you mean? In virtualbox?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes in virtualbox. i see this in your scrennshot http://d.pr/i/SUGQ
mertemur said:
Yes in virtualbox. i see this in your scrennshot http://d.pr/i/SUGQ
Click to expand...
Click to collapse
Exactly the same thing, but dont use the ubuntu image but download an image from android-x86.com.
Sent from my GT-N7000 using xda app-developers app
Thatgrass,
You better also add the steps form my tutorial for USB 2.0 support.
http://www.stacydevino.com/?p=245