Database Users

Unlocking the HTC G1 from germany!

Hello,
I new here, i'm from germay, and i only found a way for unlocking USA Phones.
Now my question is if anyone knows a way hot to unlock my phone which is from germany and also locked on german t-mobile.
Sorry if there was this question before but i havnt found it.
Merry Christmas! tollmar

Afaik the german g1 do not have a Netlock or Simlock, only the austrian have. I rooted my german g1 with a goldcard.

yes,yes,bastards is right, you need a goldcard and root our germany G1 canbe very easy , do it ,you can

My german G1 never had a Netlock. Are you sure that your one really have it?
And the first Android Devices released here in Austria also never had a Netlock, the G1 and the Magic (at least the Vodafone ones).

Well i mean the Austria one But t-mobile austria and german is the same
SO anyone got an idea?

I tried to unlock it with a code i get from a site. But it havnt worked..
Now there is not any longer the screen where i can enter the code..
Is it normal that after 1 fals entering i cant enter it anymore ?
When i Start the phone now, i just see the screen to log in google account, but cause the handy is not unlocked i dont get connection to it.
What shall i do?

Which release are you on? On 1.5 or 1.6 you could just skip it for now and use wifi later, after activating it in the settings. If it's older you have to search the forums, I've seen a few threads about that.

Well the its the fact, that the phone isnt UNLOCKED... I asked at HTC and they ment if the phone isnt Unlocked i cant logged in Google!

The best solution
I performed this procedure during rooting my G1 without a T-Mobile data plan. I don't remember who published this info so I can't give credit where it's due. I found a root kit along with specific instructions here: http://forums.t-mobile.com/t5/Opera...oot-G1-even-if-it-has-1-6-android/td-p/237395. Once you downgrade then upgrade to 1.5 or cupcake, you are within the 'security hole' to root you G1. In order to proceed from this point, you must have a data plan or follow this procedure to enable wifi and log into google. Also, this process works without a sims card. Here goes.
Activate Stock G1 over WiFi
I've seen a few guides around the internet in regards to activating a G1 over wifi without a data package, and decided to test it myself. Since it worked, I'm compiling the information that I've gathered into one easy-to-read thread.
Standard disclaimer:
Bricked phones, not my fault.
The Setup
1x Stock G1 running cupcake, this phone has no root modifications on it.
1x USB cable
1x SD card, at least 128MB
The image file to downgrade to version RC29 of Android, download here
ADB for your computer:
Linux Download
Mac Download
Windows Download
Windows Only:
Windows Drivers for Android (XP only)
--End Setup--
1. Ensure that your SD card is formated FAT32, and place the DREAIMG.nbh, that came out of the DREAIMG-RC29.zip file, in the root directory of the SD card. (No, DREAIMG is not a typo.)
2. With the phone off, insert the SD card into your G1.
3. While holding down the camera button, turn on the phone.
3a. You should see a rainbow screen, followed almost immediately by a gray screen. (mileage and colors may vary)
3b. One of the lines on the phone should read: "Press power button to start update image".
3c. Press the power button
3d. Wait for the entire process to complete, do not interrupt! It will tell you it is done updating.
4. Reboot phone.
Download the appropriate ADB file for your system, if you're on a Windurrs machine you'll need to download and install the Android drivers as well.
Ok, we're done rolling back to RC29; and we have access to the 'sploit which gives us terminal access without seeing the terminal.
Until I tell you to later on, do not touch the screen for any reason. During the rollback process the screen has turned into hot lava and will burn your hand if you touch it. If you can't resist, and touch the screen not only will you be sans one digit but you get to reboot your phone and start over.
You should now be at this screen:
<pic>
5. Hit <enter>, type "reboot"(no quotes), and hit enter again.
5a. If all went well your phone just rebooted, yay good thing!
6. We're back to the last screen.
7. Plug your phone into your computer using your USB cable.
8. If you mistype this step or it doesn't work(because you mistyped), you'll need to reboot your phone and try, try again.
9. Hit <enter>, type "setprop persist.service.adb.enable 1"(no quotes), hit <enter>
9b. If all went well you should get an error message saying something like "cannot dial 7387767 7377478.7378423.232.362253 1, it's not an emergency number. This is a good thing, we hope.
10. Set your phone down.
11. Open a terminal on your computer, and navigate to the folder containing the adb file you downloaded earlier.
edit: First cd 'drag and drop the folder Tools into the terminal window. I will copy the proper directory path.
12. If all is well, you should be able to type "adb" and get a big screen of options.
13. Type "adb devices".
13a. You should see the following: <pic>
13b. If all you see is "list of devices attached", and nothing below it, reboot your phone and move back to step 8.
13c. type "adb shell" (no quotes)
14. Copy and paste "am start -a android.intent.action.MAIN -n com.android.settings/.Settings" into your terminal.(no quotes)
15. If your copy+paste-fu is strong, you'll see this screen: <pic>
At this point you're in. You will see the 'Settings' window allowing you to set up wifi, and connect to google data and hence the internet.
Regards, davidrol

Obviously, my g1 was unlocked, after my first attempt.
After entering he APN data i got from my provider and reading further newbie hints on the modmygphone forum i could create a g-mail account and us the phone! with my own provider!! I didnt get it mate to root the phone but i always got a massage "not allow".
Very big thx for ur help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Greetings Marc!

[GUIDE] Gain root access HTC Hero TMobile

I have finally managed to root my phone. after trying for a rather long time, i did it yesterday and am running modaco custom ROM which is superb. I have listed the instructions I followed in case anyone else is having the same issues as i had
(unable to backup via amon RA image - backup failed)
Text in Bold indicates something you need to type
(Instructions taken from various sites - for XP only - Credits to Unlocker & Modaco)
If your current build number is 2.73.405.5 you can skip the Goldcard section
Phone Details:
Model Number
T-Mobile G2 Touch
Firmware Version
1.5
Baseband Version
63.18.55.06FU_6.35.07.08
Kernel Version
2.6.27-0078c992
Build Number
2.73.110.26 CL#69351 release-keys
Software Version
1.0.0.A6288
In order to root the phone, I had to downgrade the build number from 2.73.110.26 to 2.73.405.66.
Setting UP ADB on XP
First things first, we need to download and setup android SDK,
1) sdk can be downloaded from developer.android.com/sdk/
2) Extract the file to c:\AndroidSDK
3) Plug your phone in to the pc via USB cable. Windows should automatically find the drivers and you should get a message in the bottom right corner saying "device is setup and ready to use" (or something similiar).
Any issues here, google is your friend, find the drivers for your device
4) Now that windows can "see" your hero, click on Start, Run, type cmd and hit enter.
5) on this screen we need to check if adb is working so change the directory to where we extracted the sdk folder:
cd\ press enter
cd\ AndroidSDK\tools press enter
adb devices press enter
You should get something similiar to:
List of devices attached
HT9BTL900210 device
6) If you see this number, all is ok so far.
Now that adb is setup and we can communicate with our phone from the pc we need to create a Goldcard
Create Goldcard
( I tried with a 8GB ScanDisk and it worked)
Take a bakup of your sd card data, copy the files to your pc, before creating
a Goldcard as we need to format the card.
1) Ensure SD card is in your phone, click on Menu | Settings | SD Card & Phone Storage | Unmount SD card, wait a few ticks, then click on Format SD Card
2) Press back a few times and go to Settings | Application | Development and put a tick in USB Debugging
3) Connect the phone to the pc, then click on Start | Run | enter cmd and hit enter, we get the same command window as before
4) Now we need to obtain a code so that we can create the gold card. in the command prompt enter the following:
cd\ press enter
cd\ AndroidSDK\tools press enter
adb devices press enter
you should see a serial number displayed
5) Now type the following
adb shell press enter
cat /sys/class/mmc_host/mmc1/mmc1:*/cid press enter
You should get something similiar to this:
045354535230384780705c3088008a10
Make a note of this code.
6) Next go to this website >> http://hexrev.soaa.me/ , enter your code and click on Submit and make a note of the new code
7) Now go to http://revskills.de/pages/goldcard.html, fill in your details and paste the code, click on submit and check your e-mail. The godcard will be e-mailed to you, save this to your desktop.
8) Now we need to download and install a HexEditor so click the following link, download and install
http://download.cnet.com/HxD-Hex-Ed...068.html?part=dl-HxDHexEdi&subj=uo&tag=button
9) On your phone, pull down the notification bar and click to copy files to your computer, Click on Mount
10) Open the HexEditor and click on Extras | Open Disk | Under Physical Disk select Removable disk, uncheck "Open as Read Only" and click OK
11) Click on Extras | Open disk image | select the goldcard.img file (sent to you via email) Click ok when prompted for the disk size (512 Hard Disk/Floppy Disk)
12) You should have 2 tabs, one is your sd card and the other the goldcard. click on the goldcard, click on Edit | Select All, then Edit | Copy.
13) Click on the sdcard (removable disk) tab, highlight from offset 00000000 to 00000170, click on Edit | Paste Write. The highlighted cells should go red.
14) Click on File | Save and close the HexEditor
15) On your phone, pull down the notification bar and select to turn of USB storage. Pull down the notification bar again and click to copy files to your computer, Click on Mount. If XP opens the SD card all has worked ok.
16) On your phone, pull down the notification bar and select to turn of USB storage. Reboot your phone with the goldcard (sdcard) still inside.
Downgrade to an older ROM
1)You should already have HTC Sync installed on your computer, if not head over to http://www.htc.com/www/SupportDownload.aspx?p_id=283&cat=3&dl_id=852 | download and install HTC Sync
2) Next we need to down load the ROM, RUU_Hero_HTC_WWE_2.73.405.5_WWE_..exe which can be downloaded from here http://www.megaupload.com/?d=RCQ6V92U
3) Connect your phone to the pc and ensure HTC Sync picks up your phone, any issues here, either reboot your pc or phone until the phone\pc can see each other.
4) Double click the file you downloaded RUU_Hero_HTC_WWE_2.73.405.5_WWE_..exe and follow the instructions. they are very straight forward. It can take up 10 mins to complete.
Hopefully you should now have a phone with the Build Number as 2.73.405.5
If this is the case, continue reading.
Download Custom ROM
Now would be a good time to download the ROM you want to use, I am currently using Cronos which is based on 2.1 and is super quick
http://www.cronosproject.org/forum/viewforum.php?f=16&sid=332f8bccd0147f4ee8eb093920eb428d
1) Once downloaded, rename the file to Update.zip
2) Connect your phone to your pc and pull down the notification bar again and click to copy files to your computer, Click on Mount.
3) Copy the file, Update.zip to the root of your SD card.
4) On your phone, pull down the notification bar and select to turn of USB storage
Gain ROOT access
1) On your phone, click on Menu | Settings | Applications | put a tick in "Unknown Sources"
2) Connect the phone to your pc and on your phone, pull down the notification bar and click to copy files to your computer, Click on Mount
3) Download the following 2 files and save them to your desktop
http://zenthought.org/content/project/flashrec Version 1.1.3
http://www.megaupload.com/?d=WP29CWHK recovery-RA-hero-v1.5.2.img
You can also use recovery-RA-hero-v1.5.3.img but I found version 1.5.2 worked for me.
4) Copy both of these 2 files to the root of your SDcard, should show as Removable disk\media within "My Computer"
5) On your phone, pull down the notification bar and select to turn of USB storage. Disconnect your phone from the pc
6) Go to the market place and download a file manager, I used ASTRO
7) Open ASTRO and select flashrec-1.1.3.apk (the file you copied over), if prompted select package installer. click in Install if it doesnt automatically install the app
8) Open FlashRec (click on open after install) and click on Backup Recovery Image. Should take a few seconds to backup
9) Now click on the empty text box and type the following
/sdcard/recovery-RA-hero-v1.5.2.img then click on Flash Custom Recovery Image . It should take to long doing this, 10 seconds maybe
10) Power of your phone, once shutdown, hold down the Home and Power button together until the phone boots in to recovery mode
11) On the Recovery Screen, select Backup/Restore (using the trackball) and then Nand backup, this should take a minute or so
12) Next click on Wipe and select Wipe data/factory reset
13) Now select Flash zip from sdcard, this can take up to 5-15 mins. Once this is done, it should prompt you to reboot your phone, if not select "Reboot system Now"
14) Done, hopefully if everything when according to plan your phone should boot with Cronos (whichever rom you chose), the first time it boots it can take ages.
Update Radio
Check to ensure the radio version is 63.18.55.06JU_6.35.09.26, If yes skip this section, if not you can download it from the Modaco site
http://android.modaco.com/content/h...oms-radios-in-update-zip-format-for-gsm-hero/
1) Connect the phone to your pc and on your phone, pull down the notification bar and click to copy files to your computer, Click on Mount
2) Remove the update.zip file from the SD card
3) Rename the radio from 63.18.55.06JU_6.35.09.26 to Update.zip
4) On your phone, pull down the notification bar and select to turn of USB storage. Disconnect your phone from the pc
5) Power down your phone, select HOME and POWER to boot in to Recovery mode
6) Select Flash zip from sdcard, this should take roughly 5 mins, reboot the phone.
Thats it your done, If you click on Menu | Settings and nothing shows, reboot the phone again ( I had this rather strange issue)
Setting up SD CARD to work with A2SD
Follow this guide, its very good
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
Hopefully you now have a rooted phone all setup and working. As someone on here said, Road to Freedom

Thanks for this.
I'm still stuck. The goldcard seemed to work twice but when I tried the RUU_Hero_HTC_WWE_2.73.405.5_WWE_..exe it said "waiting for bootloader" and the screen on the Hero had changed to the white screen with 3 skateboarding androids and what looked like a selectable option "?RUU USB", can't quite remember but there was no way of selecting it and no buttons advanced the process.
Don't know if anyone else got this? Any tips on what I'm doing wrong?

did you receive any erros on your pc, i,e the RUU setup should be running andupdating you with whats happening, did that throw an error?

I will do it again tonight but got something along the lines of "waiting for bootloader.....timed out" Will confirm in the next hour, but some other threads said they needed to create a gold card a few times before one worked.
Any advice welcome

On the windows RUU update utility I get
ERROR [171]: USB CONNECTION ERROR
This is despite the device syncing well and being fully recognised by RUU until failing waiting for bootloader....
On the HTC Hero I get a white screen with 3 skateboarding androids on it.
On the white screen at the top I get
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.07.08
Aug 4 2009, 19:43:30 (not the current time)
RUU USB <---- Highlighted in orange. making me think you could select it, however, no buttons on the device do anything. The Hero stays like this until I pull the battery out but then it boots normally (even after the RUU.exe exits). If I pull the USB cord out, the USB text dissapears and only RUU remains highlighted.
Any ideas? The SD card used is the stock one shipped with the device which others have said works fine. If no one has a better idea, I will try later using my other 8gb card, but this is a pain as I have to back it all up.

I formatted the SD card ie non-gold card version and repeated the RUU and got the same message so I'm assuming the goldcard didn't work. Sigh... not to back up my 16Gb card...

So i got a SD card another member recommended as working as a gold card = no go.
This is getting beyond a joke now. Nobody has information on what the actual
credentials are for a card to be use able? I've spent too much money on this crap
I think I'll just sell this ****.

So I tried my 16Gb card but that didn't work either.
I don't think I'm that unlucky to get two cards which won't work as Goldcards and am very confident I have followed the instructions correctly.
The only thing I can think of is that as my phone was returned from being fixed only two weeks ago, they may have patched the kernal so even Goldcard will not work. Sigh, I might just have to wait for T-mo to pull their finger out with the 2.1 upgrade.
For what it's worth, Kernel version:
2.6.27-0078c992
Build : 2.73.110.26
Software version: 1.0.0.A6288

Kernel Version:
2.6.27-0078c992
[email protected] #821
Build Number:
2.73.110.26 cl#69351
Software Version
1.0.0.A6288
Bought and last updated in December 2009
Anyone with the same build etc that was able to gold card?

Thanks for this info.
Looks like it's the same. No-one with a goldcard in south london wants a little visit from me and my Hero ?!?

Chaps, I tried 3 times and on my fourth attempt I was successful, I used a 8GB Scandisk Card which worked. I gave up twice but eventually got lucky and it worked so I understand your frustration
It maybe worth uninstalling and re-installing your drivers, or you can try this:
USBDeview >> http://download.cnet.com/USBDeview/3000-2094_4-10614190.html, download and install
Whilst the phone is plugged in, open USB Deview, find all the htc drivers and delete them, after deleting them, disconnect your phone and plug it back in, drivers should re-install,
Try again with a different USB port on your machine, let me know how you get on

For the guys having problems with goldcards,....
Once you have made the changes to the SD, saved and closed the HEX editor,... re-open it again to make sure the changes have actually saved.
...... Alternatively,... Check to see if there are any differences in the tutorial from this thread, compared to the one here ---> [Guide] Newbie Guide to Install a Custom Rom [Updated 14/04]
Hope something there helps.

Maybe OS may be an issue,... Mine failed on Win7 64bit but worked 1st time with an XP machine.

Complete success!
Seems it was a problem with Win 7 (32-bit).
Worked first time in Vista with the stock 2gb card already created using Win 7 earlier.
Happily now enjoying a custom 2.1 Rom!
Angry yet again with M$.
So pleased I've moved to Ubuntu as my main OS.

I managed to get my goldcard work first time round, fortunately. I used a SanDisk 2Gb card, but curiously, I realised afterwards I forgot to format it, I still had all the hidden linux files (starting with a .) on it
I think all T-mobile branded hero's use the same firmware initially.
Also, I couldn't get the USB to work on Win7, had to go onto XP.
Finally, a guy at my work had the same problem, not being able to goldcard his Hero, I suggested to him, when he goes into the hex editor, include all off the offsets, like when you get down to 170, highlight all the way down to the right of that line.

drspikes said:
Complete success!
Seems it was a problem with Win 7 (32-bit).
Click to expand...
Click to collapse
Wahey!! Glad your sorted now.

I wasnt able to use either of my Win7 (32 or 64) to do this, but behold my daughters Netbook with XP was the winner!!! worked perfect..now...whats the best rom currently?

j_simon208 said:
I wasnt able to use either of my Win7 (32 or 64) to do this, but behold my daughters Netbook with XP was the winner!!! worked perfect..now...whats the best rom currently?
Click to expand...
Click to collapse
I highly recomend MCR3.2 (MoDaCo Custom ROM for GSM Hero) ,... Fast, stable,.... No complaints at all. I flashed this on the 1st day i got my HERO,... Now waiting for a stable Android 2.1 release,... Probably MCR4.0.

ddotpatel said:
I highly recomend MCR3.2 (MoDaCo Custom ROM for GSM Hero) ,... Fast, stable,.... No complaints at all. I flashed this on the 1st day i got my HERO,... Now waiting for a stable Android 2.1 release,... Probably MCR4.0.
Click to expand...
Click to collapse
I have to agree, modaco 3.2 is fantastic, even when memory is running low its still quick, Paul has done an excellent job, flashed the hero with modaco 3.2 as soon as it was rooted, havent tried anything else yet

akhtar1817 said:
I have to agree, modaco 3.2 is fantastic, even when memory is running low its still quick, Paul has done an excellent job
Click to expand...
Click to collapse
Definately,.... Has been just over 6 week with my Hero now and haven't felt the need to even try another ROM.

So Frustrated with Rooting my incredible

Ive had my Incredible for 7 days, and have been trying to root it since.
I got this one from Best Buy, and have another on the way from Verizon due tomorrow (which i will just refuse shipment since I got lucky finding this one at Best Buy)
I have had no luck in getting root. I have tried every technique that a google search would bring up, short of getting the Kingston Class 4 4gb card.
I have tried a PNY 2 gb card, Lexar 2GB, Sandisk 2gb, Da?? something or another 8gb class 4 card.
I have turned debugging on and off. I have pulled batteries, reseated the sd card at all times of the whole process (ive done this at least 200+ times.
Once the phone is booted up for use, I get the $ prompt from adb shell, but thats the only time (with debugging on of course).
The loop just NEVER lets me in. Ive tried winxp, win7 x86 and x64, and desktops to laptops. You name it.
So, since I've already put alot of wear and tear on this phone from trying to root it, should I just accept the phone from verizon tomorrow (and maybe it will be able to root? Who knows), then just take back my phone to best buy and say it keeps rebooting or something.
Or should I stay with what i got and wait for a new root to come up thats alot easier (and avoid the hassle of taking stuff back, dealing with the mail in rebate from verizon, etc).
Any advice would be appreciated.
gv

There is supposed to be another root method out within the week, for what that's worth. I don't really have any advice on which direction you should go, and sorry that rooting isn't working for you. Took me about 30 tries.

Sandisks seem to work best with the click in and out during recovery boot method. I own two 2gb sandisks (actually one I "borrowed" from my Bro) a 16gb sandisk, and a kingston 2gb all class 2. I've gotten all the sandisks working with root about 1/10 with click in and out. Still can't get the Kingston working but I'm stubborn and I HAVE to get all my cards working with root Haha. Also I was ONLY able to get these working in mac or Linux. Win was a no go for me. In short, (lol) use your sandisk, click in and out while booting recovery, while running a adb loop in mac, Linux, or a live cd and see how it goes. Be patient and Good Luck!

lol 7 days. I wish I rooted 7 days after I had my phone or even after the root was discovered. I think I spent 7 hrs a day since root was found. root will elude u. bring a pillow and some mtn dew and get comfy its gonna be a long road for you
Sent from my ADR6300 using XDA App

socalracer said:
lol 7 days. I wish I rooted 7 days after I had my phone or even after the root was discovered. I think I spent 7 hrs a day since root was found. root will elude u. bring a pillow and some mtn dew and get comfy its gonna be a long road for you
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Actually, was told by the devs in another threads that it will be 'days' before the new root is coming out. So if thats what you meants by a 'long road', i'll take it

I've now rooted 5 Dinc's using the same SDCard using the very original method (even before the loop script). The sdcard I use is a Patriot 8gb which is apparently very slow which makes the process work almost everytime.
My own Dinc was rooted using a SanDisk 16GB Class 4 but that appears to have been a fluke as most have had trouble with SanDisk.
With the others, I just use the same Patriot sdcard, and when I get to the point where you do the update.zip the first time to mount the card, I switch to whatever card that phone will be using and continue from there so the Patriot card is only used to get to the rootable point.
I carry that sdcard in a sdcard container and keep it with me in my Netbook case.

Can you clarify at what point you remove your SD card and reinstall the other persons?
Sent from my ADR6300 using XDA App

I start out with the patriot card in the phone.
When you get to the point where the exec /system/bin/sh failed.... your next step would be to Press the volume-up and Power at the same time.
I switch the sdcard before that step and then follow the instructions from that point on.

I had problems rooting at first too... and I hope this helps you some...
My biggest problem was the drivers, and getting them loaded properly. After I switched to Windows 7 and the Unrevoked drivers (rather than modding the SDK drivers), I used a combo of methods to get rooted in under 10 minutes.
For what its worth, I'm using the 16 gig Sandisk class 2 that came in my Moto Droid.
I used a combination of the following instructions...
Finally got Root with 2gig card that came with phone - xda-developers
public:adb_in_recovery [RootWiki]
and instead of modifying the USB drivers that the SDK downloads, I used the drivers from -> public:windows_hboot_driver_install [RootWiki]
I couldn't get the drivers loaded in XP sp2, so I switched to Win 7 and it was fine.
to sum it up..
1. Download SDK (android-sdk_r06-windows.zip) from Android SDK | Android Developers
2. unzip the SDK to the root of drive C
3. download the "unrEVOked modified USB driver" from public:windows_hboot_driver_install [RootWiki]
4. unzip the "unrEVOked modified USB driver" to the C drive
5. make sure USB Debugging is enabled on the INC. (settings->applications->development->check the box for USB Debugging)
6. Power the phone on, connect via USB cable to PC, and select "charge only"
7. load the drivers. For the ADB driver, Windows add new hardware wizard should prompt you about not having a correct driver, point it to the unzipped "unrEVOked modified USB driver"
8. create a loop.cmd or loop.bat in the SDK\Tools folder which just loops "ADB SHELL"
Code:
:top
adb shell
goto top
9. open command prompt, navigate to your SDK\Tools folder and type in: adb devices. when you hit enter it should list your phone as being connected.
10. at the prompt type: adb reboot recovery and press enter
11. as soon as the prompt is back type: loop and hit enter to start the adb shell loop. As soon as the loop starts running, the phone should show the white HTC Incredible screen, start clicking in and out the sd card before you hear the device disconnected sound on your pc. keep clicking the card in and out until you hear device connected sound on you pc. Look for "failed: No such file or directory" message on PC, if you see it, you're in Recovery Mode and ready to go onto the next step. If you don't see "failed: No such file or directory (2) for after another 10, 15 seconds stop clicking the card. take the battery out of the phone, put it back in, wait for it to reboot and repeat this step.
12. Once in recovery mode, I finished up by using the instructions under the heading of "I just got ADB running in recovery mode! Now what?" on -> public:adb_in_recovery [RootWiki]
Credit go to the above links... I just took what I used from each and summarized them here..
I did not purchase a new card.
And again, I had problems loading the driver in XP, so I had to use Win7, and I imagine Vista would have worked too.
Sorry if this doesn't help any.

I can confirm after many many many( u get the point) hours of trying to root that the correct driver and the ten minute root video did the trick. Use the root wiki like the post above says and you will b golden.
Edit: I also used the 16 gig from my motor without problem. Its all about the drivers
Sent from my Incredible using XDA App

Sent you a PM

[Q] EVo user trying to root my girls epic

Hey guys I an having the darnest time root this guy should be easy with these one clickers programs.
Pretty sure its a driver thing, note I can see the device when in cmd and doing the adb devices that shows up. just gets hung up at the end there.
attached a pic of what the cmd line looks like
anybody have the current drivers, googling for them just yields me to forum posts asking where the drivers are

thirty views and nothing

ok its not a driver issue if your loading root.sh (the big block of text) the issue is that the adb server isnt starting back up in time in order for your device to be recognized. solution? open up the bat file and copy and paste the commands one at a time; or if you have a linux/osx computer try doing it there with my scripts in my sig

couple ideas..
1.open up the run.bat file in notepad or similar and go through all the commands manually, that way you have control on speed of commands and allow enough time for adb to startup again.
2. open up the run.bat file and increase the wait time in the script.. -w 3000 or something like that..
i would suggest you do commands manually. The one-click root did not work for me but doing things manually worked right away.

How to do it
Hey man this is how I got it to work. I was having all the problems device not found etc etc. Have been trying since Sunday. What I finally did after installing the drivers was restart the computer and Phone. After that i tried to run the program it failed with device not found again so i unplugged the usb cable from the phone and closed the cmd window. And also brought up Task manager and killed the adb.exe process. then i reran the run.bat file and this time when it gets to the adb restart relogin apart i killed the SMALLEST ADB.EXE IN THE PROCESS TAB OF TASK MANAGER and that is when it finally got it to work. Had to do the same when I tested it with the uninstaller. So that seems to work. If anyone has any questions feel free to pm me.
But thank god it finally worked.
David
other people have done this and it worked for them also.

I tried all kinds of stuff ultimately I ended up using an xp machine. I later remembered the whole xp mode in windows 7 but didn't actually try it ... win7 just gave me a hard time although the post about changing the amount of time to restart adb makes sense
Sent from my SPH-D700 using XDA App

will try all of that thankyou gents

[Q] ADB error: device unauthorized and device offline

I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.

HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.

ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.

HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.

Perfect, worked. Thanks!

I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...

usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.

I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.

Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!

legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe

maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway

legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards

c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.

legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.

I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.

SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.

after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.

I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.

thanks to the adb kill-server guy! worked for me

gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto