Related
Hey Guys at first sorry for my english i'm not good in it. And I'm a Android newbie I just gained a bit exerience with my Touch Diamond but it's broken now..okay but that's not the probleme....
If got a question:
After about 2 days of searching for an android 2.0 or 2.1 ROM I was a little bit confused of the diffrent news everybody was talking about. I'm root on my Hero. That was the first an last thing I made with my device.
1. Everybody is gonna talk about MoDaCo 3.0 but when I was trying to download his ROM my browser never got a request. Is the site down, where that ROM is hosted ?? Could someone give me a working link with this ROM ??
2. Is there a ROM with Android 2.0 or 2.1 outside or even not ??? And if yes are they working well ???
Would be nice if someone can help me =) thanks a lot.
Please answer soon if you know something about that =)
Greetz BassdoxXx
you can get modaco's roms at his website, www.modaco.com.
in the android development section there are some 2.0/1 roms, none of them works flawless, see for yourself if it fits your needs.
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
BassdoxXx said:
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
Click to expand...
Click to collapse
What? Does ISP's block that site? Lol, would never happened in Norway
there is a few 2.0+ roms out there for the hero.
most seem to be very usable now.
best sense ui would be lox/behnaam community release on 1.6.
http://htcpedia.com/forum/showthread.php?t=1448
there are two aosp roms worth looking at.
lox aosp ( im using that on a daily basis)
http://htcpedia.com/forum/showthread.php?t=1416
jnwhiteh aosp
http://htcpedia.com/forum/showthread.php?t=1528
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
sorry for the double posting. I've accidentally posted twice and I am unable to remove the post.
Hope anybody can help me please.
pvdeejay said:
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
Click to expand...
Click to collapse
i am on mcr3.0, i looked in the market, i can find 8 apps for eyesfree, tts is one of these. i didn't try to install one of these, but usually it works. the search for talkback returned nothing.
not that i want to be rude, but wouldn't you be better off with another phone if you are blind? i can not imagine a touchscreen only phone would be suitable for someone who is not able to see... especially because there are great devices out there that have a full qwerty keyboard, and come with android 2.0 out of the box... imho this would be a better solution.
again, the last thing i want to be is rude, but maybe this was your mistake: you posted in the htc hero section of this forum, the hero is a touch screen only device, including a virtual keyboard on the screen. it has only six buttons and a trackball, and two rocker buttons for the volume. just to make clear we are talking about the same device
if you are still up for the hero you could try the 2.1 rom from here: http://htcpedia.com/forum/showthread.php?p=30418&posted=1#post30418
best you try for yourself, it has some drawbacks, but maybe in areas you don't need (afaik syncing with exchange does not work for example, which wouldn't be a problem for me...). otherwise it might be worth to wait another week or two, we all are waiting unpatiently for the official eclair release from htc
keep asking if you need to know more, but maybe open a new thread, since your problems are very specific, and might drown between all the newbies question about "how to root my phone".
Hello,
Thanks for your reply and a great attitude.
Yes it may sound strange I have really got HTC Hero here. I know I'll be having problems with virtual keyboard but also I am afraid accessibility features of Android phones are not really such mastered one can use it daily. For example reading emails and content from the web browser is not yet possible. I just want to try how things work and I would also like to touch the virtual keyboard. If I can memorize computer keyboard and use it daily, typewriter keyboard, nokia mobile phone keyboard, then perhaps I might be able to make some use of this too.
I am sory but here are some more questions:
I haven't yet verified with some sighted friends but... is it possible my hero is running even older version of android like Android 1.5? I've based the assumption that it's most likelly running 1.5 because majority of the devices I was reading on the net are running it.
You've been triyng to locate eyes-free applications on the market but you were unable to find talkback. Are you sure you are running newer version of Android than 1.5?
Talkback is supposed to be installed with Android 1.6 andd 2.0 by default and you should be able to find it in the accessibility menu of your phone. I am not sure how well this applies to the custom roms.
Talkback requires google's accessibility api which is reported to be available on Android 1.6 upwards.
To tell you the full story first I've asked on the eyes-free google group whether some accessibility experts from there can help me but no one knowledgeable enough has replied to my query, so I'm trying my luck here then.
Oh I am really excited since I've got really well formed informative reply.
Thanks again
Edit:
Also, I've seen somewhere in the forums here this leaked HTC rom does not support the market. Has this been rectified already? You know if market does not work then most likelly I won't be able to install these applications I am tallking about.
Also you are mentioning possibility to wait a few weeks until HTC guys role out the official update for Hero. Wouldn't that break chances I will be able to root my device later?
Edit2:
Ooops, I should read better next time. Market works on this rom. The problem is paid apps can't be installed which is hopefully not a big issue for me since most of the accessibility enabled applications are free.
Which of the downloads from Hero 21 do I need?
63.18.55.06JU_6.35.09.26) or No Wipe Download. I will need a wipe I am sure but since this link says nowipe I am ehmmm. confused.
pvdeejay,
Unfortunately there is not an 'official' update for Android 1.6, 2.0 or 2.1 as of yet. There are rumours of one coming out soon, but nothing cast-iron yet.
You are correct in that the Hero runs 1.5. It does say it under Settings | About Phone (bottom item on list)| Firmware Version (bottom on list again), although without a working screen reader, there is probably little use in knowing how to find that.
If you did want to upgrade, I'm sure plenty of people could help find a ROM that would suit. The only issue with that is that you would need a rooted phone with a custom recovery image installed. Unfortunately, a lot of the procedures would not be easy for you, as the software that you might need to use to go through the procedure is probably not designed that well for accessibility tools. I don't know what kind of software you are using, but some of the instructions for making goldcards are quite complex, and involve editing some numbers in a 'table' which could be quite difficult for you, I would imagine.
I'm sure a friend would be able to help you out with making a goldcard/rooting if you did want to install a custom ROM (you'll probably be waiting a while otherwise ). They could even root their phone while doing yours (just share the goldcard between the devices).
Nonetheless, there is probably a ROM out there with little removed from it. I'll have a look just now, but you would need to have your phone rooted to do anything just now.
When it comes to rooting and installing custom recovery image. Do you thing the following instructions might work for me?
These instructions don't require a gold card:
- How to Root HTC Hero and Install Amon Ra Recovery Image
- How to install a custom rom on a HTC Hero
Hello,
Here are some numbers I've asked my friend to read from system -> about screen. The phone interface is in czech so I am unable to get some names translated to english, but I believe some of the geeks will understand these identifiers and might be able to help me what is best:
Code:
firmware: 1,5
63.118.55.O6U|6.35.04.25
2.6.27-a5504199
Build number: 1.76.405.6 146733 CL# 47214 release-keys
Software version: 1.0.0.A6288
pvdeejay,
to sum it up:
the hero definitly runs on android 1.5. there are no roms for older android versions, and a few homebrewn for newer versions, as we said already.
i searched for talkbalk on my 1.5 rom, so it is obvious that i couldn't find it...
about rooting of newer roms: it is just a matter of time, sooner or later there will be always methods of rooting a rom. what i meant by waiting is: wait until the official update is out, then wait a few more hours until the first rooted and customized rom is out
@pvdeejay,
I would have to agree with kendong2 that waiting for the official ROM is probably the best idea for you at the moment. There are no guarantees that an unofficial ROM would help, and it would be another user interface to try and learn.
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Sorry guys originally I believed I am slowly getting into the matter and am begining to understand how flashing / rooting / upgrading home brew firmwares works on these phones.
After these 2 posts I feel like a total noob again.
Now again some very concrete questions:
What about these 2 guides I've posted links to?
Can I somehow got [Recovery] [13-Dec-2009] RA-hero-v1.5.2 installed so I will be able to do nandroid backup and then possibly flash some new roms?
Can I really brick my phone by trying to install amon ra?
Originally I thought the process works as follows:
1) get the custom recovery image installed (that's the amon ra in this case),
2) do a nandroid backup which will dump everything usefull on to the memory card,
3) backup and reformat the card,
4) download a rom, rename it to update.zip, put it onto the root folder of the cart, reboot the hero in recovery mode, do the wipe of the data partition, and run update,
5) reboot again and believe it's good.
Also some very significant bit is the thing you are all calling the radio. I am afraid I've not identified this bit thus it's missing in this summary.
Which files will I need to download if I decide to try Android 2.1 community edition 1.8? Are these files I've copied links to a few posts earlier both needed?
Can you please check this list, identify the things I am missing, and make suggestions and corrections why this may not work on my device based off of those number I tried to put down here?
Even if I won't be able to do this right now I'd be happy to get corrections as I can learn something new.
Of course I won't be doing all this on my own. I will ask my bro to read all the stuff to me and we'll do it according to your advices.
To give some bits about me and my computer skills, I believe I am a Windows power user, Basically I do also understand unix, I know what's bash how the files are arranged in a file system, can use command-line tools, telnet, ssh. I am working as a network administrator here so some background is there really.
Hi pvdeejay,
Answers to your questions here.
You can actually use fastboot to 'temporarily' load up the AmonRA recovery image into memory and run it from there. I do that on my phone, for the simple reason that I can't be bothered ) ) to flash the recovery. Once you get AmonRA running, the first thing you should do is make a Nandroid backup. It will be saved to your SD card, so then get the nandroid directory of your card and save it to your PC (just in case!)
So, here's how you'd go about this.
(Make sure you have the android sdk installed, and that adb and fastboot commands are working). USB cable should be plugged in throughout.
Before you begin, put the ROM you want (ie. Android 2.1 community edition 1.8) into the root of the microSD card (a .zip file).
Code:
adb devices
Should list your phone's serial number
Now turn off the phone, and turn it on with the back key held down (the one at the very bottom right of the device).
You should enter fastboot mode. Now type
Code:
fastboot devices
and you should see the serial number again.
Now type
Code:
fastboot boot AmonRA.img
where AmonRA.img is a file in your present working directory that is the filename of the latest custom recovery image. This does NOT flash your phone, it merely runs the image (pretty much as close as you get to risk free, other than sitting there with a tinfoil hat on )
See screenshot of the recovery image here:
http://www.sizzledcore.com/wp-content/uploads/2009/12/RA-hero-recovery-image-500x375.jpg
Make the Nandroid backup by choosing 'Nandroid Vx.x Backup' and waiting a while.
If your ROM needs a wipe first (most new ones do), select Wipe data/factory reset. You will lose all your user data on the device (but you've got a nandroid backup just in case)
You're now good to go. So choose "Apply sdcard:choose zip"
Now select the custom ROM zip file you downloaded. It doesn't even need to be called update.zip! Choose it from the list and push trackball.
Wait for the update.zip to go in. Do NOT turn off the device or pull the battery. First boot can take a very long time (upto 30 minutes). Just keep it plugged in via USB and wait...
As for radios, see http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/ and look at the section titled radios. The latest one is in bold. It is a .zip file as well, that you use these exact same instructions for to install (don't do the wipe or anything like that. Just install the .zip file)
anon2122 said:
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Click to expand...
Click to collapse
this is correct so far, i did the same, except i installed the recovery. i play a lot with my phone, the installed recovery image with the nandroid backup is the best i have ever seen for a phone...
@pvdeejay
you always write so much...
i try to answer everything:
the two guides you posted are good for your situation. i never tried flashrec, but from what i read it is safe to use. i installed my recovery image through fastboot, the guide is here: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
i have no idea how this works out for you, but my honest suggestion would be that you have someone seeing assisting you, you CAN brick your phone, though it is not likely if you follow the instructions precisely. the process is not very time consuming at all, so you don't need to bother anyone for days of their time.
edit: and now i read your post to the end and saw that your brother will be helping you, so you are on the right track
once you have the recovery installed you can make nandroid backups, and i would suggest that you do this first thing after installing the recovery, better make a backup too much than one too less...
the 5 steps you described are correct, except there is no need to rename the zipfile anymore, you can select any .zip from your sdcard.
the radio part is the number that begins with 63.18.55.06, then comes two letters and then more numbers. as by now the version can be identified by the letters, with JU being the up-to-date one. in general you can say the newer the better, but you have to try for yourself. start with the newest one, if you have problems go back.
thanks this seems to be pretty doable plus I will easily be able to restore the current data backed using nandroid backup.
Which android SDK do I need the latest one?
The commands I need to type are supposed to be typed on the PC or on the phone? I assume on the PC but I just would like to ensure.
Hero21 1.8 community edition has a recommended radio listed in the first post. Is it necessary to install that one as well? What should I install first the actual rom or the radio? Do I need installing radio at all? Should i do the same with radio i.e. renaming it to update.zip and using amonra to install it?
Also will I be able to use this method even if I install another rom (running amonra without actually flashing it)?
Edit:
sorry guys did not realize renaming to update.zip is no longer needed.
Edit2:
is there an easy way on how to access sd card from windows? I can't just remove the card from phone and insert it into my laptop because I don't have the proper adapter. Previously my boss was using the hero and perhaps it would be nice to backup the sd card first.
Edit3:
uhmmm, installing android sdk is perhaps not as simple as it sounds.
I have just seen this article.
I am on a limited gprs internet connection, can you please suggest sdk features I won't need to save some download bandwith?
- you need only the adb binary (thats adb.exe for windows) from the sdk, the rest is not needed for this.
- install the radio from the 2.1community-rom-thread, it is the newest. install the radio first. DO NOT PULL THE BATTERY until the phone has rebooted completely. if you pull the battery during radio upgrade your phone will be dead. it takes a few minutes, do not panic!
- you can copy the contents of the sdcard via the usb-cable, plug it into your pc and pull down the notification bar...
Do I need to run SDK Setup.exe when I have downloaded android sdk for windows?
Or can I simply run that binary from the command-line without the installation?
Do I need any USB drivers so my phone can be recognized?
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
Greetings people ^ First of all Hi,im new to XDA
Awesome forum btw.
My question is : I have a SE X10i branded in Spain, Vodafone ES ...on R2BA024 (i think) and i wanna unbrand it to SE X10i UK Generic R2BA020 (That way i can get the 2.1 update faster,cause vodafone will take alot i think to get it rolling around)
Will it all work perfectly? I mean,will i concur with any problems?
Thanks in advance ^^
PS : My SIM Lock is off so i think ill be able to use any SIM i got
PS2: Sorry if this has been asked already ,i just couldnt find any posts regarding this.
I'm unlocked but branded Vodafone UK, build R2BA024 and would like some help in debranding too - so I can get the 2.1 faster.
I'm not sure how to debrand and what method will work
I have however managed to get root and have superuser permission (so i'm not a complete blonde)
Any help would be greatly appreciated
tia x
P.S. Hello and welcome xtrmshadow , I hope you dont mind me piggybacking your post
Please search the forums first before opening a new thread.
Go to one of the debrand threads where they have guides.
Sent from my X10i using XDA App
Ty ^^ And no mate i dont mind =) happy my thread will help more than just me out =)
xtrmshadow said:
Ty ^^ And no mate i dont mind =) happy my thread will help more than just me out =)
Click to expand...
Click to collapse
But there are already threads out there to help you out, before you posted yours- just a friendly reminder thats all, the more threads people open the more clogged up the forum and the harder to search
Anyway here you are
http://www.esato.com/board/viewtopic.php?topic=195467
Sent from my X10i using XDA App
jayman1986 said:
But there are already threads out there to help you out, before you posted yours- just a friendly reminder thats all, the more threads people open the more clogged up the forum and the harder to search
Anyway here you are
http://www.esato.com/board/viewtopic.php?topic=195467
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Thanks you for your time and effort Jayman
I had already searched the forum and came across the same method in that link you posted but I'm unsure if it works
this method doesnt work anymore need to debrand my other x10
Click to expand...
Click to collapse
Didn't work with mine either as all the Orange browser bookmards are still there.
Click to expand...
Click to collapse
I've tried this so many times now but it's just not working.
Click to expand...
Click to collapse
im having exactly the same problem, ive debranded my phone before also but i cant get it to work right now because the file name has changed and SEUS keeps overwriting the firmware im trying to put in my X10a
Click to expand...
Click to collapse
Try this I've copied this from Synlar's post.
****
There seems to be a lot of questions regarding the steps laid out in the official thread, so here I'll try doing a STEP BY STEP guide for those who are confused with the steps.
I borrowed some stuff from the original guide, so thanks Bin4ry, jerpelea and biktor_gj for everything!
NOTE: Before you begin, you should know that this process will wipe everything off your phone. So backup your contacts, and text messages and everything on your phone! Download a free backup program from the market to make backups onto your SD card, and after you're done everything, download that program again and restore everything from SD card. Your SD card remains fine.
1) Install SEUS (Sony Ericsson Update Service).
You can get it from here: http://www.sonyericsson.com/cws/download/1/110/61/1275980198/Update_Service_Setup-2.10.6.21.exe
2) Run SEUS, follow the prompts. You don't need to update the phone through it, but get the phone ready for updating. This process should install the drivers necessary for the rooting process.
Note: I suggest you keep your USB cable attached to that USB port. Remember which USB port of your computer it's attached to, as changing USB ports can lead to a bit of confusion for the next 2 steps!
3) To check if #2 was successful, click on Start, click Run, and type: regedit
In the Registry Editor that pops up, click on Computer, press CTRL+F, and search for this: USB\Vid_0fce&Pid_adde\
After it's finished finding, on the right side you'll see DeviceInstance, then it says REG_SZ, then it says something like USB\Vid_0fce&Pid_adde\5&270d2a78&0&3
You'll need that last bit (in this example: 5&270d2a78&0&3 Yours would probably be different). This is your DeviceID (you'll need it soon!)
Note: You may have multiple of these if you plugged the USB cord into many USB ports on your computer. Each USB port will give a different DeviceID, so if you have more than one DeviceID, you'll have to choose one, and if it doesn't work (you'll find out when you reach #5!) you will have to choose another one.
Alternatively, download the file in the next step and extract it, go to the folder called 1st, and run the DeviceID.jar file. It should give your DeviceID
4) Download this:
http://filevo.com/1nlq8wryo11u.html
or from here: http://rapidshare.com/files/404363083/i_R1FA16_ft.rar.html
Extract it.
In the step1 folder, you'll see a file called DeviceID.txt
Open it up, delete whatever's there, and put YOUR DeviceID (that you found from the previous step).
Save the file and close notepad.
Note: Make sure there are no extra spaces or lines after/before the DeviceID. The ONLY thing that should be in the file is your DeviceID, NO SPACES/LINES (for example, only this: 5&270d2a78&0&3 [yours will probably be different])
5) Take out the USB cable from your phone (leave it plugged into your computer)
Turn your phone OFF
Open up step1.cmd (it's not inside the step1 folder, but outside it), but DON'T PRESS ANYTHING
Now we have to put the phone into flash mode. This is how you do it:
Hold the Back button on your phone, and while holding the back button, insert the USB cable into the phone.
A green light should come on the phone (like when it's charging or a missed call)
Quickly "Press any key to continue..." in the open step1.cmd window.
Let it finish what it's doing. It will say "Press any key to continue..." after it's finished. Until then, DON'T touch anything!
If you get problems in this step, refer to this post:
http://forum.xda-developers.com/showpost.php?p=6970868&postcount=3
Here's a helpful video for common java issue: http://forum.xda-developers.com/showthread.php?t=713457
After completion, this will give you a Generic X10i R1FA016 firmware (check it by pressing the left button, go to settings>about phone and at the very bottom under build number)
Keep your phone plugged into the USB.
6) Download this:
http://filevo.com/yzmh8wlyrgtz.html
or from here: http://rapidshare.com/files/404359845/ROOT_F2v2.rar.html
Extract it.
DELETE step4 folder, step5 folder, step4.cmd and step5.cmd
Now we're going to put the phone into Debugging mode:
Turn your phone on if it's not already on.
Press the left button, go to Settings>Applications>Development and check on USB debugging, press OK in the popup. Plug the USB into the phone (in case you disconnected it). You should see an exclamation mark at the very top left of the screen of the phone.
Do NOT have the SD card mounted to your computer!
Note: This next step can take a while!
Open step2.cmd, don't press anything!
On the phone, a list of buttons will come up eventually. Press the 6th option (something about update from SDcard). ONLY PRESS IT ONCE!
Leave your phone alone. Go to the washroom or eat a snack.
You'll see the progress on the phone screen, as it installs the package. Leave everything alone.
After completion, this will give you a Generic X10i R2BA023 firmware.
If you get problems, try this post: http://forum.xda-developers.com/showpost.php?p=7003121&postcount=1122
7) The phone should be on, USB plugged in, and already in USB debugging mode.
Open step3.cmd, and 'Press any key to continue'
Let it finish what it's doing, it will say 'Press any key to continue' at the end after it's finished.
After completion, this will give you ROOT! And it also installs some programs for you.
_____________________________________________________________________
Additional steps for X10a:
Download this:
http://filevo.com/okknxk23pbnr.html
or from here: http://hotfile.com/dl/52357616/84b4027/ROOT_F2v2_X10a.rar.html
Extract it.
Inside the step4 folder, there is a DeviceID.txt file. Remember you've seen this before? Copy the same one from step1 folder that you did in #4, and put it into the step4 folder.
Follow #5 (except with step4.cmd)
Next, turn the phone on (if it doesn't turn on, unplug the USB from the phone, and try turning it on again, then plug the USB back in). Put it in USB debugging mode if it's not (if you forgot how to, look back in #6)
Open step5.cmd
After it's done, press the left button on the the phone, go to Settings>About phone and under Model number it should say X10a
_____________________________________________________________________
Market Fix:
If you have an X10i, follow this: http://forum.xda-developers.com/showthread.php?t=719486
Otherwise if you have an X10a, use this file instead, but follow the same instructions as in the link above: http://rapidshare.com/files/405188255/Market-Fix-X10a.rar
_____________________________________________________________________
To delete preinstalled programs you don't want, such as Moxier:
Put phone in debugging mode if it's not already.
I recommend you unplug USB from phone so you don't end up running some file and messing your phone
Open up the step3 folder. Right-click on cleanup.cmd, and click on edit.
Whatever is there in that list of "@adb shell rm /blah/blah/blah" will get wiped off your phone. So change the list as you want. If you're unsure, REMOVE IT FROM THE LIST!
After you're done making your list of apps to remove, save the file, plug USB into phone, and run the file.
Here is a thread that says what some of the applications are, and additional ones you can add to the list, to remove from the phone: http://forum.xda-developers.com/showthread.php?t=714021
Alternatively, you can install Titanium Backup from the market (it's free!) and use that to uninstall some applications. Also, it's really great for making a backup of your stuff (you can backup more things now since you have access to more things since you now have root!)
_____________________________________________________________________
If you are experiencing difficulties, try reading through this thread, since it may already be answered: http://forum.xda-developers.com/showthread.php?t=711969
Check out this post if you are having troubles; hopefully it can clear up some common problems people may be having: http://forum.xda-developers.com/showpost.php?p=7099515&postcount=1927
I hope this step-by-step guide helps!
Sent from my X10i using XDA App
If you still have problems, try reading a recent thread by Seansmit17.
Thread titled "that was easy"
he seems to have another solution to debranding.
Sent from my X10i using XDA App
xtrmshadow said:
Will it all work perfectly? I mean,will i concur with any problems?
Click to expand...
Click to collapse
Run steps 1-5 HERE, then run SEUS which will update you to R2BA026.
Ah o.o i finally did from here http://forum.xda-developers.com/showthread.php?t=717949&page=22 and worked perfectly for me ,im at last step7 and so far its working great...after this ima update to 026 and done ^^
Thanks for the help people =)
My Phone is working great ^^
And Damn fast now
Ty Again =) Now to wait for update 2.1 :3
xtrmshadow said:
Ah o.o i finally did from here http://forum.xda-developers.com/showthread.php?t=717949&page=22 and worked perfectly for me ,im at last step7 and so far its working great...after this ima update to 026 and done ^^
Click to expand...
Click to collapse
If you'd have stopped at step 5 and run seus you would flash straight to 026, instead of having to flash to 023 and then 026.
I've tried this method
http://www.esato.com/board/viewtopic.php?topic=195467
when I get to step 12 SE's PC Companion just re-downloads the Vodafone files again :'(
still stuck on uk 024 :'(
Same thing happens on the SEUS swap method, it doesn't attempt to download the files as they are already there so I don't get the opportunity to swap :'(
@debs ,that method doesnt work anymore mate,use the one from here : http://forum.xda-developers.com/show...717949&page=22 .
That one works,i just tried it myself.
Regards ^^
PS: Just be careful on the steps,read em carefully before doing anything,you can brick your phone doing that.
Thank you sooooo much XperiaX10iUser and xtrmshadow. Chuffed to bits now I have finally got 026 on. I did it the way you both suggested but only up to part 5, then let SEUS update me to 026.
I'm one happy bunny now
xtyx
I also read something about replacing just one file? I can't find the post anymore and don't remember the filename. I unbranded my phone months ago. But my wife has the same phone from Vodafone, but branded. If someone can tell me the name of the file and whether I can copy mine file to her phone to unbrand it?
olafski72 said:
I also read something about replacing just one file? I can't find the post anymore and don't remember the filename. I unbranded my phone months ago. But my wife has the same phone from Vodafone, but branded. If someone can tell me the name of the file and whether I can copy mine file to her phone to unbrand it?
Click to expand...
Click to collapse
No you can't exactly copy it.
Go to the debrand thread posted on first page and read through carefully then you'll see that the files are copied to a certain folder on your pc. Since you've done it before I'm sure it will come back to you if you simply reread the obstructions.
Edit:Btw the links posted by XperiaX10User and xtrmshadow are actually same post with I copy and pasted on first page. Just so you don't get confused.
Sent from my X10i using XDA App
I found it, I mean the build.prop. What if I replace her build.prop with mine? Would that work?
I know about the SEUS and then during the process replace the files etc. But that is not what I mean ;-)
Thanx again!
olafski72 said:
I found it, I mean the build.prop. What if I replace her build.prop with mine? Would that work?
I know about the SEUS and then during the process replace the files etc. But that is not what I mean ;-)
Thanx again!
Click to expand...
Click to collapse
Sadly I'm not experienced enough on this subject to answer that question, maybe pm jerplea or bin4ry?
Sent from my X10i using XDA App
Hi, i have been looking through some of the rooting, flash threads on here and there is a bit too much information,lol.
Can anyone detail the basic steps, software required to roll my X10 back to the 1.6 OS?
I am still having connectivity issues when trying to use the handset in the car.
The vehicle manufactures website shows that the Xperia X10i is compatible with their factory fitted handsfree systems, but only on OS 1.6.
1. Download this and extract in any folder of your computer:megaupload.com/?d=HCWX4KO3 (The credits of this goes for its creators)
2. Open the folder that its named 1_firmware and in the fileDeviceID.txt copy yours, save and close. (This is the same as the one used on the flashtools of Bin4ry)
This is how you can get your DeviceID on Windows: (Again thanks tojimbo77)
2.1: Connect your phone to the computer on the USB port you are going to use to flash it.
2.2: Press start (or windows icon) and in the run box type regedit
2.3: Click edit>find, and type in Vid_0fce&Pid_adde. You should find "DeviceInstance". If that fails, make sure Match whole stringis un-ticked, and click find next or press f3, if that fails, tryUSB\VID_0FCE&PID_ADDE. Copy the last section of that, it should look something like "5&2888d0ff&0&1".
Note: It changes with every diffrent USB port you use....3. Download your Firmware, extract it and copy all the files on it to the 1_firmware folder. You don't have to erase anything from this folder, unless you got the message to replace a file.
4. Now run the RootX10a_v2.cmd and select step 1 and follow the instructions. If done correctly you will see a window that starts to write and write and write a lot of things. This process will take around 5 minutes, so be patient. (It is like if you were flashing your phone)
5. Turn your phone on and wait until you get the configuration screen.
6. Now connect the phone to the PC and run PC Companion or SEUS. If it shows that there is a new software for your phone, follow the instructions and update if you want.
7. Enjoy your phone on Android OS 1.6 or 2.1 with your operator
Thank you on anticipation to any help offered.
I have had a look here, but am not 100% if this is all that i need to do?
Sorry, not able to post the link, being a new user.
The one part that is not clear to me is where they say, "Open the folder that its named 1_firmware and in the fileDeviceID.txt copy yours, save and close"
What is it that im supposed to copy?
No.. no...
You need the flashtool and the 1.6 files..
I cant seem to find the 1.6 files...
Why do you need 1.6?
SE seem to have done something with the update 2.1 where the phones Bluetooth will connect to my vehicle, but only for about 40 seconds, then removes its self and then re attaches, then removes its self again and this goes on for the duration the handset is in the car with me.
The handset i have just now was a replacement for my original and came with the 2.1 OS already updated.
The original 1.6 OS that was on the phone connected to my vehicle and gave me phonebook access.
I have neither now hence why i wish to roll back to the software that is compatible with my vehicles system. 1.6 buildR1FA016 Kernel 2.6
Get your phone rooted, load Xrecovery.
and flash Wolfbreaks CM rom.
And watch the magic.
OmegaRED^ said:
Get your phone rooted, load Xrecovery.
and flash Wolfbreaks CM rom.
And watch the magic.
Click to expand...
Click to collapse
Thanks for the above, but can you break this into more simple instructions, links etc as this is way above me. I'm not totally useless, but i have never done anything like this, so it is all double dutch to me at this point in time,lol.
Download the flashtool from androxyde's thread then follow the instructions to flash the latest FW, then reboot your phone plug it in and press root on the flashtool and then reboot and install XRecovery and use it to install a custom ROM by following the directions in a ROM thread.
Just start by reading the Flashtool thread.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
CMoney87 said:
Download the flashtool from androxyde's thread then follow the instructions to flash the latest FW, then reboot your phone plug it in and press root on the flashtool and then reboot and install XRecovery and use it to install a custom ROM by following the directions in a ROM thread.
Just start by reading the Flashtool thread.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Click to expand...
Click to collapse
Had a read at the flash tool thread and even more confused now, too much information and no understanding of what it all means.
I am looking for someone who can supply links to what i actually need to roll the phone back.
What software do i require.
Do i have to root the phone and if so, how do you do this?
I did say in the thread title an "Idiots Guide". Simple and straightforward instructions that a first timer can comprehend, similar to the text in my first post, bullet points?
Thanks.
Bonzo67 said:
I am looking for someone who can supply links to what i actually need to roll the phone back.
What software do i require.
Do i have to root the phone and if so, how do you do this?
I did say in the thread title an "Idiots Guide". Simple and straightforward instructions that a first timer can comprehend, similar to the text in my first post, bullet points?
Thanks.
Click to expand...
Click to collapse
Dude.. all the threads have the answers.
Read abit it won't kill you.
OmegaRED^ said:
Dude.. all the threads have the answers.
Read abit it won't kill you.
Click to expand...
Click to collapse
I did and it's version this and version that. So which version is it that i actually need without screwing up my phone?
Suppose i'm more looking for something along the lines of what you would get if you downloaded a torrent file, where everything is in the one folder, inc the instructions.
Anyway, hopefully problem is sorted, as i am ditching SE after 10 years of using their handsets and going to Samsung which is compatible with my vehicles factory fitted system.
Bonzo67 said:
I did and it's version this and version that. So which version is it that i actually need without screwing up my phone?
Suppose i'm more looking for something along the lines of what you would get if you downloaded a torrent file, where everything is in the one folder, inc the instructions.
Anyway, hopefully problem is sorted, as i am ditching SE after 10 years of using their handsets and going to Samsung which is compatible with my vehicles factory fitted system.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1060703
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"
CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs
Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.
Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8