Database Users

[TUTORIAL] Rooting ALL Non-Sprint CDMA Heros Stuck On 1.5 From Sprint's 2.1 RUU

Before I even begin the tutorial I need to point out something:
THIS WILL VOID YOUR WARRANTY AND YOU MAY LOSE SUPPORT FROM YOUR CARRIER. THIS ALSO HAS THE POTENTIAL TO BREAK YOUR ABILITY TO UPGRADE TO YOUR CARRIERS OFFICIAL 2.1 UPDATE WHEN RELEASED
What is an RUU?
RUU (or radio unit update) is a factory restore update which will wipe your handset and re-program it. Sometimes this is done as a troubleshooting step to fix a corrupt operating system, sometimes it is done as a clean update.
How can a Sprint RUU break your ability to update to 2.1 from your carrier?
Most RUU updates include updates for the bootloader (HBOOT). HBOOT does NOT take kindly to being downgraded. If you run an RUU from Sprint then find out that the RUU from your carrier for 2.1 has an older version of HBOOT then your official RUU will fail with an error of "Main version is older!"
Why does using a Sprint RUU void my warranty or remove my carrier support?
You are removing the software which was tailored specifically for your carrier. This can have undesirable results and potentially break things. You can't expect your carrier's technical support to help you with Sprint software or with bugs because of a custom ROM from the XDA community.
Anytime you mess with your phones operating system and firmware you also have the potential to cause serious problems. DO NOT attempt this process unless you are certain you know what you are doing!
THIS SHOULD WORK ON ALL HTC HERO PHONES CURRENTLY RUNNING OS 1.5 (CUPCAKE)​
LINK IS FINALLY UP! CLICK HERE FOR THE ZIP FILE
Documents in the linked ZIP file (in the order you should use them)
Android - Setting Up ADB Access
HTC Hero - Installing Sync and Drivers
Android - Creating a GoldCard
HTC Hero - Flashing RUU from microSDHC
Android - Flashing Custom Recovery Image
HTC Hero - Flashing 2.1 ROM
Files in the linked ZIP file
HERCIMG.zip (RUU rom.zip from Sprint's latest 2.1 test build)
flash_image
recovery-RA-heroc-v1.6.2.img
READ ALL OF THE INSTRUCTIONS BEFORE YOU GET STARTED!​
DO YOU REALLY WANT A $500 PAPERWEIGHT BECAUSE YOU WERE TOO IMPATIENT TO SPEND 10 MINUTES READING?​
GETTING STARTED
There are THREE things you must have to proceed:
A CDMA HTC Hero (not a GSM version)
The ZIP file linked to above
Your MSL code*
*The MSL code is a six digit code used to access your phones programming. Some carriers use a generic 000000 or one code for all of their devices. Other carriers have an MSL which is device specific. I am NOT going to help you find your MSL code! If you don't know it, contact your carrier and ask for it or search the forum for other means of obtaining it.
Basic Setup
Complete the steps in the following guides (which are in attached zip)
Android - Setting Up ADB Access.docx
HTC Hero - Installing Sync and Drivers.docx
Before you begin following the rest of the guides in the attached ZIP file you will need to backup your PRL. PRL is the preferred roaming list and tells your phone which carriers/towers it can use. If this file is incorrect you could end up with poor service or potentially roaming charges.
WHEN YOU USE A SPRINT RUU YOU WILL END UP WITH A SPRINT PRL! YOU MUST BACKUP YOUR PRL BEFORE GETTING STARTED SO YOU CAN RESTORE IT AFTER THE RUU.
PRL Backup
(the following instructions are adapted from THIS link)
1. Download and install the latest version of QPST from HERE
2. Dial ##3424# on your Hero to put it into diagnosic mode and connect to your computer via USB
3. Open QPST Configuration and go to the PORTS tab
4. Click on "Add New Port".
5. Select the port listed as USB/QC Diagnostics (may vary, just don't use the data modem one)
6. Go to Start Clients Dropdown and select Service Programming
7. From Service Programming your phone should be selected - Click OK
8. Click "Read from Phone" and Enter MSL. Various fields should populate, don't worry about what tab you are one
9. Click "Save to File" and save to wherever you want (just remember where)
The prl will be located in the directory you saved the file in and labeled as <yourphoneesn>_sp.rl0
Advanced Tasks
Complete the steps in the following guides (which are in attached zip)
Android - Creating a GoldCard.docx
HTC Hero - Flashing RUU from microSDHC.docx
Android - Flashing Custom Recovery Image.docx
HTC Hero - Flashing 2.1 ROM.docx
EDIT:
Because the RUU file updates HBOOT before it goes on to update the system it's possible that this will invalidate your current goldcard. DON'T FREAK OUT IF THE RUU FAILS AFTER THE FIRST TWO STEPS! Just pull the battery to reboot and redo the goldcard from scratch again. You should find that this time the RUU will complete.
PRL Restore
Copy the PRL file to the root of your microSD card
Dial ##775# on the handset and enter the MSL code when prompted for password
Tap on Update PRL
If it read your microSD card correctly your PRL file should be listed in the bottom half of the screen to select
Select your PRL and click OK
Press the MENU button and tap on Commit Modifications (which will reboot the phone)

Here's a simple clean-up script attached to remove what I consider to be useless applications. I've copied the script into this thread so you can see what it will remove before you run it. If there's anything you want to keep just right click the batch file, select EDIT, then remove the line deleting the program you want to keep.
adb remount
adb shell rm /system/app/LiveWallpapers.apk
adb shell rm /system/app/LiveWallpapersPicker.apk
adb shell rm /system/app/Sprint_Core.apk
adb shell rm /system/app/Sprint_TVWidget.apk
adb shell rm /system/app/Sprint_TV.apk
adb shell rm /system/app/Sprint_Nscar.apk
adb shell rm /system/app/Sprint_Navigation.apk
adb shell rm /system/app/Sprint_NFL.apk
adb shell rm /system/app/SDSA.apk
adb shell rm /system/app/sfl-prod-release.apk
adb shell rm /system/app/Flickr.apk
adb shell rm /system/app/com.htc.MusicWidget.apk
adb shell rm /system/app/com.htc.TwitterWidget.apk
adb shell rm /system/app/HtcTwitter.apk
adb shell rm /system/app/IM.apk
adb shell rm /system/app/OMADM.apk
adb shell rm /system/app/Facebook.apk
adb shell rm /system/app/HtcFacebook.apk
adb shell rm /system/app/IQRD.apk
adb shell rm /system/app/Launcher2.apk
adb shell rm /system/app/com.htc.StockWidget.apk
adb shell rm /system/app/Stock.apk

I just threw this together this morning so it might have some errors. If you find anything that needs to be corrected please post here or PM me and I'll get to it as soon as I can.

is there a way around the htc sync / sdk conflict?

cyanfrost said:
is there a way around the htc sync / sdk conflict?
Click to expand...
Click to collapse
I've never been able to get them to play nice on the same PC. If you're planning on sticking with Android phones for a while keep the SDK on your PC and instead of using the HTC Sync application use Missing Sync.

Nevermind, I figured out the answers to my questions on my own.

Thanks for the guide. This worked perfectly. ACS wireless here. Use the attatched PRL and you can skip the qpst backup step. This should in theory work for converting a gci hero to acs, but i have not tested that.
UPDATED: Now attached is the official radio update from the ACS RUU that dropped today. Version is 2.42.01.04.23

Got it to work on my hero on GCI/AK Digitel.
I ran into a couple of problems but I was able to get around it.
The first problem I ran into was hercimg.zip wouldn't install. It installed initially and updated my hboot and radio but it would just go back to the hboot menu every time it would extract and check. I finally got it to install after removing my battery during the green htc logo then going into hboot. I tried re-creating the gold card and formatting my sdcard but I couldn't get it to work until the battery got pulled on the htc logo which I did on accident.
The second problem I had was when I was installing the custom recovery image. I tried both methods in the tutorial but it wouldn't work in the end I had to follow the How-To repair your bootloader after using the 2.1 RUU tutorial at androidcentral and it work out great
But now I am rooted and running fresh 2.1.1 so everything is great!!!
Thanks for the tutorial!!!

Thanks
Thanks for all the hard work on this, but it would be nice if you posted document files that do not require office 2007 or better as I do not have it or want it. Plain old text works great and is quite cross platform and document viewer compatible.

Damn! Wish this was here before I rooted a month ago! lol.

Thank you very much for the work you put into this awesome post!!! After reading it over and over I am ROOT!!!!! I really want to thank YOU, ipfreelytech, and d-shade for the help you guys gave me. Now I'm off to flash!
Thanks guys!!!!!!

was looking for this tutorial, thanks!

These can be opened in pages on a mac, or in openoffice on linux or windows. you could also download a viewer. Seems like a really stupid complaint as he put A LOT of effort into this and you can't download a viewer?
webfeind said:
Thanks for all the hard work on this, but it would be nice if you posted document files that do not require office 2007 or better as I do not have it or want it. Plain old text works great and is quite cross platform and document viewer compatible.
Click to expand...
Click to collapse

I wish I found this before giving up a week ago!

sorry for being a noob but if i rooted a long time ago using a sprint ruu (i think it was like 1.5 something) (also im on cellular south) and have successfully been rooted for awhile can i update to 2.1 by following this guide?

if you already have root, just flash a 2.1 rom from your recovery console. I'd reccommend flashing a newer recovery image if you haven't done so. but there is no reason to go through all this BS if you have root. to get updated baseband you can flash my radio update i pulled from the ACG RUU or you can flash the signed sprint radio update thats floating around here.

A very important step is missing here....Backup before installing the new ROM (as the phones comes from your company)... specially since this post is targeted to Non-Sprint CDMA and there is no way to RUU back to Non-Sprint; no RUU available, right?

I don't understand what your saying here. you CANNOT backup the stock 1.5 rom, there is simply no way. you can use mybackup to backup system settings and apps on a non rooted phone.
Now that there are 2.1 ruu for non sprint carriers; if for some reason you wanted to take it back to stock and screw yourself out of root for as long as you have the phone you can just flash the RUU from your carrier. The ACG ruu is many versions newer than the sprint ruu so overwrite is not a problem. once again i don't know why anyone would do this.
bicione said:
A very important step is missing here....Backup before installing the new ROM (as the phones comes from your company)... specially since this post is targeted to Non-Sprint CDMA and there is no way to RUU back to Non-Sprint; no RUU available, right?
Click to expand...
Click to collapse

ipfreelytech said:
I don't understand what your saying here. you CANNOT backup the stock 1.5 rom, there is simply no way. you can use mybackup to backup system settings and apps on a non rooted phone.
Now that there are 2.1 ruu for non sprint carriers; if for some reason you wanted to take it back to stock and screw yourself out of root for as long as you have the phone you can just flash the RUU from your carrier. The ACG ruu is many versions newer than the sprint ruu so overwrite is not a problem. once again i don't know why anyone would do this.
Click to expand...
Click to collapse
Thanks for pointing out that in no way you can return back. Non-Sprint Heros users using those ROMs that are all over here, suffer from lack of voicemail notifications.
If your Non-Sprint company has no RUU, THEN DO NOT ROOT your phone if you want to keep voicemail notifications. No backup possible, point of no return! Good advice? ...or Non-Sprint Heros can get voicemail notifications in particular ROM? ...or using an app?
Answering your question about why would you want to go back... To get back your voicemail notifications... or otherwise, keep calling your voicemail, lest say, every 30 minutes.. just to know if you have voicemail.

voice-mail notification is only broken on roms that are based of the sprint RUU. the zen (tmobile mytouch 3gslide port) has working voice mail notification. as do the AOSP based roms such as buufed.
you cannot get a voicemail without a missed call unless your phone is off. so you only would need to check after a missed call.
at one point i was trying to make a rom from the 2.1 update that was used by a bunch of carriers including mine, nothing special just add superuser, but it didn't go well and haven't figured out what went wrong, and lost interest because I started using buufed. The rom booted but didn't have a proper version in the about software. also the mobile radio didn't work nor did wifi.
bicione said:
Thanks for pointing out that in no way you can return back. Non-Sprint Heros users using those ROMs that are all over here, suffer from lack of voicemail notifications.
If your Non-Sprint company has no RUU, THEN DO NOT ROOT your phone if you want to keep voicemail notifications. No backup possible, point of no return! Good advice? ...or Non-Sprint Heros can get voicemail notifications in particular ROM? ...or using an app?
Answering your question about why would you want to go back... To get back your voicemail notifications... or otherwise, keep calling your voicemail, lest say, every 30 minutes.. just to know if you have voicemail.
Click to expand...
Click to collapse

HOW TO: Enable Wireless N on The Aria

EDIT:alot of people are unable to do this method because of errors writing to the system. it seems to restore the original bcm4329.ko upon reboot, so this patch has been cooked into the Roms. And wireless N is confirmed to work.
Just flash one of the below roms
Go Here For attn1's Liberated Beta 4 Rom with The Wireless N Patch Cooked in. http://forum.xda-developers.com/showthread.php?t=708434
heres his Beta 3 with wireless N cooked in - http://www.mediafire.com/?wenzltywoom
So i realized that the htc nexus one, htc desire, and htc evo all have the Bcm4329 wireless chip. And they all have wireless N enabled with hacks. Well I know from porting roms for the Aria that the aria also has a BCM4329 wireless chip. So i said to myself, why havent i enabled wireless N on my Aria.
well none of the methods worked except the manual method which isnt too difficult if you have some adb knowledge.just follow the exact steps and youll have no problem.
Prerequisites
-Must Be Rooted
-Must have clockwork recovery installed
-Must have the android sdk installed
ENABLING WIRELESS N
step 1- Download a hex editor
step 2-in a command prompt navigate to the /android-sdk/tools folder and type the following
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko.old
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko
(this makes a backup of the original in case you want to go back to wireless G)
Step 3- in the hex editor open up the file you pulled(bcm4329.ko). Now the same as the htc Evo 4g, Htc added 2 strings that say "nmode" without the quotes. Use the search function to find the 2 strings. now you need to replace nmode with any different string. i used "-----" without the quotes for both.
when you're done save the file.
Step 5-now reboot into clockwork recovery and go the partitions menu. go down to mount /system and press the power button.
Step 6-now type this in the command shell.
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
reboot your phone when its done and you now have wireless N enabled.

since the Aria has the same chip as the nexus,, then why wifitether does not work..?

Will try this on my Aria when I get home. Thank you in advance! Now, back to the wifi tethering debacle
Sent from my SAMSUNG-SGH-I897 using XDA App

We Aren't Sure why wireless tethering isn't working yet. But we're pretty sure its gotta be something disabled at the kernel level. It will only be a matter of time before we figure it out.

Is it confirmed that Wireless N is enabled after doing said method?
*edit*
Just tried it, and it's not picking up my Wireless N network, nor does my Wireless router show it connected to a Wireless N. Only Wireless G.
I also did a adb pull of the file I pushed back just to confirm the changes were made, and they are, but for some reason it's not working.

there are some others who are having problems getting this to work as well.
im gonna test it on a rom real quick.
try this-> forgetting the network then reconnecting and re entering the password. not sure if that will fix it but that is what i did when i first connected so maybe that had something to do with it.

I'll give that a try in a few min, and report back.
*edit*
Tried that, the scanning doesn't even pick up the Wireless N network, it only see's the 'G' network. (I have a dual band G & N router)

Well after reading the EVO thread regarding this method, it shows that people who did it are connected at over 54mbps, which is the max for G speeds.
I'm currently connected at 69mbps, so maybe I am on my N?

try to change your wireless N router to N-only and see if it connects and remains connected.

Seems I have no luck, router is in N only mode, but the wifi on the Aria is just 'scanning'.
It's a great idea, just wish it would work.

i dont know why anyone else is unable to get it working, but im patching a rom with this and gonna have someone test it and then ill know. there just seems to be problems with the writing files to the system.

I was starting to think it was a permissions issue, but I'm at a loss as to this one. It might need to be done from a update.zip file in ClockworkMod.

yeah, maybe.
Since there were problems writing files to /system i tried pre-patching a rom and it works. So we're going to just patch the liberated Rom and upload it. check the liberated Rom thread in a little while if you cant get this to work.

[How To] Root

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

[GUIDE] Enable ad-hoc tethering on your Transformer (needs root!)

Update: If you are using the official firmware 8.6.5.9 (and obviously above) or any custom ROM based on it, you don't have to do anythink described here, because ad-hoc works natively. Thankfully ASUS fixed Googles unintelligible inability to enable connection to ad-hoc networks.
This renders this thread pretty much obsolete, but I won't delete it, just in case anyone doesn't want to or cannot update his device for whatever reason
Hi!
As there are only [Q]uestion threads about ad-hoc tethering by now, I thought I'd write a little guide how to enable it on our Transformer.
edit: If you are using Prime v1.5 (and above I guess), you don't have to do this. Roach2010 already included the modified wpa_supplicant, so you can already use ad-hoc tethering.
All credits and many thanks go to szym for the edited wpa_supplicant that makes ad-hoc possible for us!
!!! Always make a nandroid backup via recovery first! You can then reflash your backup if something fails !!!
I. Via root explorer (obviously requires root access):
If you bought root explorer from the market, you should be able to easily copy and replace the file.
1.) Go to /system/bin and copy the file „wpa_supplicant“ to your sd card as a backup.
2.) Then copy the „wpa_supplicant“ from the attached zip file and paste it into /system/bin.
3.) Long press the file and set permissions to rwxr-xr-x, like this:
User: read, write, execute
Group: read, execute
Others: read, execute
4.) Reboot
Finally tried it myself and works fine
II. Alternative method via adb (requires root access):
This is a forwarded guide from the Xoom section. I tried it myself and it works like a charm. You can find it here.
All credits for the following guide go to kelvie !
1.) Your Transformer has to be rooted! (you'll find a guide how to root here)
2.) Make a backup of your system/bin/wpa_supplicant first!
3.) Unpack the attached wpa_supplicant_xoom_wifi_adhoc.zip file to your adb folder. (if you don't know how to use adb, google for one of the many guides, or look below for another option via root explorer )
4.) push the file to system/bin/wpa_supplicant:
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
5.) Because zipfiles don't store permission, you have to make it executable as well:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
6.) You also have to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
7.) reboot
Again, many thanks to kelvie for the guide!
III. Easiest method (requires ClockWorkMod recovery and root):
1.)Download the attached CWM_adhoc_wpa_supplicant_TF101.zip to your sd-card. Make sure to copy it to /Removable/MicroSD, because /mnt/sdcard cannot be accessed from CWM
2.) Boot into CWM recovery.
3.) Hit "install zip from sdcard" --> "choose zip from sdcard", select the zip and confirm.
4.) Reboot
Done. You should now be able to tether your ad-hoc connection
This method doesn't seem to work because I missed an option and don't know right now how to fix it. So if somebody knows how to do this via edify script, please help me out:
Code:
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Use one of the methods above in the meantime, they works flawless.
__________________________________________________
Q&A
Q: Which app should I use for tethering on my phone? Do I need root access for tethering apps?
A: If your phone doesn't support native tethering, just search the Android Market for 'Wifi tether'. There are a lot of apps for that . I tested Barnacle Wifi Tether on my Sony Ericsson Xperia X10 with 2.3.4 MIUI ROM, which worked fine, but I guess all/most tether apps should work fine now. And yes, unless you have native tethering, your phone has to be rooted.
Q: Barnacle gives me the following error on the phone: "DHCP could not bind to DHCP port, address already in use", and my TF is stuck at "obtaining IP Address from barnacle". What should I do?
A: rpavich has found a solution for that. Thanks rpavich!
rpavich said:
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
__________________________________________________
Regards
qwer23
Edit: I wasn't sure if this belongs in General or Android Dev section, so mods feel free to move it where it fits best.
Edit2: Attached original wpa_supplicant files for 3.0 and 3.1 (don't know if there's a difference, but I doubt it) if someone wants to reset to stock.
If you find this guide helpful, consider pressing the thanks button
Click to expand...
Click to collapse

awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye

philsuf said:
awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye
Click to expand...
Click to collapse
No need to wait, you could just try it. If you back up your original wpa_supplicant first, you can always undo your changes. I also added an easier way via root explorer that should be easier.

i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.

Skeldave said:
i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.
Click to expand...
Click to collapse
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms

I've done this last week and noticed when stopping my hotspot on the phone the connection on the transformer shows it is still connected. So you have to manual disconnect if you want to reconnect again for later use. This is on my Nokia N8 Phone using JoikuSpot.

I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"

rpavich said:
I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"
Click to expand...
Click to collapse
On the top of your system directory in root explorer is a button, that says r/w. Push it and you'll get read/write mode.
Sent from my rooted X10i using awesome custom roms

thank you VERY much....I'll let you know how my tethering goes.

qwer23 said:
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Yes, the barnacle symbol was in the notification bar and my TF appeared on the 'client' tab, also the TF said that it was connected to barnacle wifi.
I'm going to try again now
EDIT: Worked perfectly this morning, thanks!
I did it via root explorer FYI

This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...

Ok...trouble getting this to work.
1.) On my Xperia X10; message in Barnacle:
"DHCP could not bind to DHCP port, address already in use"
2.) On my TF: it's stuck at "obtaining IP Address from barnacle"

Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)

rpavich said:
Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms

jake21 said:
This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...
Click to expand...
Click to collapse
I don't have a clue either why this isn't enabled by default, but I think they'll add this in the 3.1 update. But it's just a suggestion, didn't read anything about it though.
Sent from my rooted X10i using awesome custom roms

qwer23 said:
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Not at all....as i said...I got that from another part of the XDA forum...

I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?

sanfaz said:
I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?
Click to expand...
Click to collapse
At the moment you need to root both your TF and your phone. But if you use Clockworkmod, you probably don't need a rooted TF, because I'm preparing an update.zip to flash via CWM
Your phone has definitely to be rooted, ecxept it supports wifi tethering from stock.
edit: darn, amend scripting is no longer supported in Honeycomb. Anyone knows how to change the zip for edify scripting?
edit2: ok, probably got it solved. we'll see...

Ok, I added a zip file for easy install through ClockWorkMod to the OP. It installed fine on my TF101 and tethering works, but please backup your wpa_supplicant before installing this and report any errors. I didn't work with edify scripts before
I also restructured the guide itself, from easiest to most complicate method
Cheers
qwer23

Would this mod work with an old TP2 windows mobile phone? Will the TF then be able to use it's wifi signal?
Also, if the TF is rooted, will we be able to accept the 3.1 HC update?

Root for ICS TPT! This time the REAL thing!

Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
WARNING!
If you dont know the slightest bit of Windows or Linux shell and never did more than USE the device, be warned... If you kill it, its dead!

emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Click to expand...
Click to collapse
I confirm it works perfectly. ICS TPT _A400_03_0070_0132_US :good:

God, this is so wonderful. CWM works, Koshu's CM10 JB Firmware, too. I LOVE THE DEVICE AGAIN!

Great news! Who might have thought that a working exploit is already out there?

This is wonderful news, a friend of mine recently lost root after he had to send his TPT in for repair and got a new board already updated to ICS.

FANTASTIC - worked on UK running OTA 3.5
Booyah! Thanks Emuandco for your diligence!

Thank you. Had lost hope of root for ICS. My TPT may finally be the tablet I paid for.

22 hours and 5 badly needed factory resets were worth it ^^

Thanks a lot :good: :good: :good:
I just rooted my ThinkPad (WE version). Works like a charm.

emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
Click to expand...
Click to collapse
wonderful!!!
Thanks a lot!!!
Just tried and it worked!!!

after some trouble installing the adb drivers it worked fine on my WE tablet..finally, awesome, thanks

Amazing how much of a difference having root on this tablet makes.:good:

Stylus and Pressure Sensitivity
Been waiting a long time for this. I had one question that I can't seem to find the answer to. I use my TPT for sketching, allot, it's why I bought the tablet. I was wondering, if I root and then upgrade to Jelly Bean, will I lose stylus and pressure sensitivity?

Can someone post the steps to get this working starting from a clean OTA 4.0.3 rom? I just started messing with the TPT. What boot options are there? I see the hold-down-rotate-and-power boot which looks like what is needed for nvflash, but I can't seem to get any other bootloaders booting here. The debugfs script seems to want to talk to a recovery boot, yes? How do I boot into recovery mode?
Sorry for the TPT newbie questions. Is there a wiki someplace with all the boot modes and other info?

First, load this one: LINK
Its the Driver needed for the TPT to communicate with the PC over ADB protocol.
Go to your TPT Settings below inside Developer Options and check USB Debugging. Attach to your PC and hand the new unknown Device in Device manager the loaded ADB Driver. Then download and unzip everything from the Exploit into a directory; then run RootDebugfs.bat from that directory. This should do it for the rooting of the Stock Firmware. You can verify it by getting "Root Checker" from Play Store. If its green, next load this one: LINK and this one LINK. Its the ClockWorkMod aka modded Recovery Mode making it possible to flash unsigned Updates and making nice Full Backups and the JB Firmware itself.
Install this way from a windows console bein inside the folder where the adb.exe from the exploit is, Step one is making a backup of your previous Recovery Mode for future reverting if you want to do so. Step two is the actual install. You need to copy the loaded recovery.img from the CWM thread to the SD in your TPT, same goes for the JB ZIP File and maybe the 3G Patch for the 3G Card you might have.
BE SURE ALL FILES ARE COPIED ON THE SD AND ITS INSIDE THE TPT AGAIN!
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/orig_recovery.img
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/external_sd/recovery.img of=/dev/block/mmcblk0p1
exit
exit
This should be enough. Now reboot and while the Lenovo mini Logo shows up, push Vol UP rapidly. This should boot up CWM6, our modded recover Mode. Here Vol UP is upwards, Vol DOWN is downwards and ON/OFF is Enter. First thing, DO A FULL BACKUP TO EXTERNAL SD in "backup and restore", "backup" !!! Then let it do a "wipe data/factory reset", then select "install zip from sdcard" and in there "choose zip from external sdcard". Choose the CM10 JB ZIP first, then the 3G Patch for your Card.
Reboot and youre done.

i have updated to the latest ota and i am not rooted.. A400_03_0070_0132_US
when i run it and choose option 1 the window automatically closes after like 2 seconds
am i supposed to use the asus drivers or what? if anyone can please help...

Somebody buy that man a beer.!!!!!!

Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.

pwstein said:
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
Click to expand...
Click to collapse
I have already tried that doesn't work. when in cmd i write adb devices it shows the device is connected
i have put it to transfer files and MTP settings with unknown sources and debugging on ..when i run the .bat file
after the *demon started successfully* it suddenly closes after which nothing happens..what do you think is wrong?

Open a CMD prompt and run the bat file from there. then show us the output of the script please.
AAND be sure that theres not any adb.exe coming from the system path variable, like in system32 or syswow64. kill these