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
Hi, guy. I have been spending all my free time trying to root my g2. But i can't even start rooting. Cause i can't set up adb on computer. I am doing everything right, watched tens of youtube instructions but nothing can help. I have extracted android-sdk_r12-windows.zip file on my local C disk. connected the phone launched cmd.exe but it is not showing the serial number as it was supposed to. I am new to android world switched from iOS world. I am already ready to give up with rooting. can anybody have any instructions how to downgrade to froyo and root the G2. Any help will be appreciated.
No need to use full ADB afaik. There are mini-adb programs that don't require a full SDK install.
You can also accomplish things using the terminal emulator app on the phone instead of the cmd prompt on the computer.
Make sure you have enabled usb debugging on the phone.
-Nipqer
sturabekov said:
Hi, guy. I have been spending all my free time trying to root my g2. But i can't even start rooting. Cause i can't set up adb on computer. I am doing everything right, watched tens of youtube instructions but nothing can help. I have extracted android-sdk_r12-windows.zip file on my local C disk. connected the phone launched cmd.exe but it is not showing the serial number as it was supposed to. I am new to android world switched from iOS world. I am already ready to give up with rooting. can anybody have any instructions how to downgrade to froyo and root the G2. Any help will be appreciated.
Click to expand...
Click to collapse
Did you update your PATH variable? Have you installed the proper drivers? There is a great thread here on how to set up ADB. It's a great resource if you haven't read it already.
Where can i find drivers for G2? i could not find one neither on htc support website nor t-mobile site. and i also updated PATH variables.
sturabekov said:
Where can i find drivers for G2? i could not find one neither on htc support website nor t-mobile site. and i also updated PATH variables.
Click to expand...
Click to collapse
I don't know where to find JUst the drivers, but I know if you install HTC Sync, the software used to sync phone contents with HTC Sense ROMs, it will also install the drivers you need along with it.
All the links on the official HTC site are broken, but I found the Sync software here:
http://htc-sync.software.informer.com/
After the initial setup, I found that I could uninstall the actual Sync software and leave the drivers with no problems.
The links are not broken. They are designed for european version of te website. That's why we can't find them
sturabekov said:
The links are not broken. They are designed for european version of te website. That's why we can't find them
Click to expand...
Click to collapse
I don't think so... I had no problem using them myself a few months ago.
I just googled htc sync and went to thee link for htc's site boom done! Did it list week. Ps I rooted following the sticky for rooting using gfree no adb. It was a cinch.
killj0y said:
I just googled htc sync and went to thee link for htc's site boom done! Did it list week. Ps I rooted following the sticky for rooting using gfree no adb. It was a cinch.
Click to expand...
Click to collapse
I had the same experience a few months ago, but last night I could not track down the official Sync software from HTC's website. If you don't mind, could you link me to where you found it? Just to ease my curiosity... this is bugging me.
Edit: Nevermind - found it.
Made hard on purpose. The newer the g2 the harder it is. The path and making sure giving permission (esp on w7 cpus) is imp.
Sent from my HTC Vision using XDA Premium App
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
I am inclined to agree with you with so many different instructions with different levels of experience how the new user can achieve root and proper driver installation has become muddled to the point where people are getting stuck in modes rendering thier devices unseen by thier computers. Stuck in fastboot or recovery or soft and hard bricked with batteries draining and time running out to achieve a fix. There is a serious need for a clear easy exploit for very low experience level OS dedicated. KFU worked perfect for me and so did adb but with others it has created a problem if I had the knowledge base to build a one click wonder I would but its way out of my experience level even though I have successfully rooted every device I have 2 kindles a galaxy tab 10.1 and my droidx after the .621 ota for droidx. So where do we go from here?
kinfauns said:
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
Click to expand...
Click to collapse
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
That being said, the people that I told to do it the "hard" way haven't needed any further help.
And if it does come back to bite me in the ass, you can rest assured, I'll eat my words.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him.
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
marcelloLins said:
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Click to expand...
Click to collapse
So, instead of totally hijacking this thread for the sake of an argument...
I think you need to confirm that your drivers are installed properly. Regardless of what path you take to get them installed, pay attention to the middle part of this post...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and make sure that you are seeing the right things in the device manager. You'll have to verify that part of it is working right, so Windows and the Kindle Fire are able to communicate with each other before moving ahead in your troubleshooting.
kinfauns said:
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him
Click to expand...
Click to collapse
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Believe me, I'm not offended by this discussion. We are just having a respectful disagreement over a mutually shared desire to help people who want to mod their KF. I understand that you aren't doing anything wrong. I'm not wagging my finger at you or yelling, "my way or the highway!" It's just my belief that going the SDK route is error prone and the cost/benefit of doing it that way may be too high for most users to bear.
Let me share an experience I had with someone who PM'd me for help after deciding to install the drivers from the SDK. After days of back and forth, he figured out that he had created the adb_usb.ini file as a text file and Windows was hiding the file suffix. So, he actually had an adb_usb.ini.txt file and with Windows Explorer only showing the adb_usb.ini part, he hadn't really considered the possibility that the file could have been named incorrectly. It's the silly things that will trip up even a knowledgeable user.
I'm not saying never to the SDK... I'm just saying it shouldn't be the first choice. I certainly won't be upset if you decide to instruct users to install the SDK just for the drivers, but they might be if they figure out they could have gotten to the same place with KFU's driver installer in 1/20th of the time.
Hi all,
After countless checks on forums and other threads on XDA, I've decided to post this thread as I couldn't find a similar case anywhere.
Situation is I have a TPT from China. Long story short, it was from my company, and when I moved back to Europe I got to keep it.
Anyway, the problem is that it comes with a blocked Lenovo Store, meaning I can't access any of European/US/international apps. Going to Google Play store online doesn't work ("you haven't used any device with this account") - tried from tablet or from computer.
So I thought I would root and install a custom ROM that could enable me to get to the store and personalization/optimization of the device.
I managed to root my TPT thru this thread: http://forum.xda-developers.com/showthread.php?t=1925025
Everything went OK but then I am stuck at the next stage.
If I understand well from this thread http://forum.xda-developers.com/showthread.php?t=1846044, I need to install CWM and then install the custom ROM.
The thread about installing CWM, http://forum.xda-developers.com/showthread.php?t=1831161, just doesn't work, maybe I'm doing something wrong.
If anyone can help it would be very helpful, right now my TPT is just useless...
Thanks all, any help will be very much appreciated.
M0t3l
Here are the specs:
Thinkpad Tablet 32GB
Android version 4.0.3
Kernel: 2.6.39.4-g9b8008b-dirty
Build number: A400_03_0070_0132_SC
Machine Type/model: 183825C
I am on Windows 7 and Mac OSX
Needing a few more details than "just doesn't work"... Are you getting an error message?
Thinkpad Tablet from China
da_reeseboy said:
Needing a few more details than "just doesn't work"... Are you getting an error message?
Click to expand...
Click to collapse
Hi Da Reeseboy, thanks for answering first.
ADB drivers have already been installed on my windows machine in order to root the TPT.
Then at step 3 of the tutorial ("backup your old recovery"), I tried to input the commands into the TPT but nothing happens.
I have installed an application from the chinese lenovo store called SuShell in order to do that (I do speak some chinese). SuShell just tells me "command executed", that's it.
Actually I am not clear if I have an "old recovery" or if it's only for people already with CWM.
So I went on to step 4.
I did copy the file "recovery.img" to an SD card, stick it into the TPT and tried to proceed on the TPT via SuShell again, but when I type in the commands, SuShell tells me "command executed", but nothing happens again.
So I am a little confused if I am doing something the wrong way or typing the commands not thru the right channel or something else.
That's where any help will be very useful.
Thanks again!
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
TPT from China
da_reeseboy said:
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
Click to expand...
Click to collapse
Thanks da_reeseboy, that made it!
I had a few gliches on the way but nothing major that I couldn't overcome.
I did follow the steps on the tutorials and now CM seems to be working fine on the tablet. It seems that a couple of functions on the TPT are either crashing or not working correctly, will try to look into it, but mainly I am now able to access the Play Store and said goodbye to the Chinese Lenovo Store.
Cheers again!
M0t3l